Authorship, review and evidence boundary
- Technical review
- East Baoyu Engineering Editorial Team
- Reviewed
- 2026-09-05
- Scope
- General engineering and procurement guidance. This article is not a project-specific design, capacity statement, certificate, warranty, code interpretation or contract requirement.
Evidence basis: Official and public references identified in the article. Project values and release decisions require qualified review under the applicable project responsibilities.
Read the Editorial PolicyA solar mounting system for a flat roof should be compared only after the host roof has a controlled technical identity. Before choosing ballasted, mechanically attached or hybrid racking, establish the roof construction, remaining condition, verified load path, current capacity assessment, waterproofing and insulation build-up, drainage routes, wind zones, fire access and maintenance constraints. Then require each option to state where loads go and which roof functions it changes. This article gives commercial-rooftop owners, EPC engineers and procurement teams a release method for that comparison. It does not select a mounting system, calculate loads, approve penetrations or replace the building engineer, roofing authority, fire reviewer, installer or local code process.
Release the Roof Before Comparing Racking
“Flat roof” is not a complete design input. It may describe the visible slope while leaving the deck, joists, beams, membrane, insulation, cover board, drainage falls, parapets and previous repairs unknown. It also says nothing about the roof’s current condition, the basis on which its capacity was assessed or the restrictions attached to its warranty.
Start with a roof evidence pack, not a preferred mounting catalogue. The pack should identify the building and roof areas on one controlled plan; record the structural and roofing documents available; show drains, scuppers, joints, curbs, skylights, hatches and rooftop equipment; and state which information was confirmed by records, survey, opening-up or calculation. Photographs help locate conditions, but they do not prove a concealed load path.
Use five release gates before asking suppliers for a comparable configuration:
| Release gate | Minimum evidence | If the gate is not closed |
|---|---|---|
| Host-roof identity | Deck and support system, roof build-up, slope/falls, condition, repairs and controlled roof plan | Limit work to screening; do not treat a generic roof type as a design basis |
| Structural path | Applicable actions, assessment basis, support locations, allowable reactions and governing limitations | Hold system selection or request bounded alternatives with declared assumptions |
| Envelope function | Membrane, insulation, cover/protection layers, movement joints, drainage and warranty authority | Do not approve pads, penetrations, adhesives or concentrated bearing details |
| Operational space | Fire routes, edge access, roof maintenance, equipment service, cable routes and fall-protection strategy | Revise the usable area before fixing layout or quantity |
| Approval route | Jurisdiction, adopted codes, responsible designers, roofing reviewer, owner approvals and required records | Treat every proposal as preliminary rather than released |
Passing a gate does not mean the roof is suitable for every system. It means the evidence is mature enough for the next responsible party to make a bounded decision.
Compare Load Transfer, Not the Penetration Label
Ballasted, mechanically attached and hybrid are useful configuration labels, but none is a verdict. The decisive question is how the complete array resists gravity, uplift, sliding, overturning, seismic movement where applicable and installation or maintenance actions, and how those effects reach the primary building structure.
| Configuration route | Primary restraint concept | Roof demand to expose | Interface evidence needed | Do not infer |
|---|---|---|---|---|
| Ballasted | Array self-weight and added ballast contribute to stability without relying only on regularly spaced structural anchors | Distributed and local gravity effects, bearing through roof layers, wind-zone ballast pattern, sliding/movement and drainage interaction | System-specific calculations, ballast map, bearing/protection detail, roof capacity acceptance and installation controls | “No penetration” does not mean no structural, membrane or movement risk |
| Mechanically attached | Defined attachments transfer actions through the roof assembly to verified deck or framing | Uplift, shear and moment at each attachment; local deck/framing resistance; waterproofing and thermal details | Reaction schedule, attachment test or design basis, support identification, fastening and flashing detail, inspection plan | A strong bracket does not prove the substrate, fastener, deck or waterproofing route |
| Hybrid | Ballast and selected attachments share restraint under a defined analytical model | Load sharing, stiffness assumptions, attachment demand, remaining ballast, membrane contact and construction tolerances | One coordinated model and drawing set showing what each restraint element does | Adding a few anchors to a ballast layout does not automatically create a verified hybrid system |
The U.S. Department of Energy’s 2021 weather-vulnerability guide discusses both ballasted arrays and hybrid corrective approaches. It is evidence that multiple restraint concepts exist, not permission to select one without a project design. The guide’s field observations also reinforce the need to look for array movement and to verify whether mechanical connections actually reach the building structure (DOE, 2021).
Ask each supplier to return a marked-up roof plan with the proposed array boundary, support points, ballast or attachment schedule, outgoing reactions, excluded areas and assumptions. The same drawing should reconcile with the structural assessment and roof-interface details. A component list without that spatial relationship is not comparable.
Keep the Racking Check and Building Check Separate
The racking system and the host building solve related but different problems. A racking calculation may show that rails, trays, frames, connectors and restraints can carry their assigned actions. It does not by itself show that an existing deck, joist, beam, column, connection or foundation can accept the resulting distribution. Conversely, a building with reserve gravity capacity does not prove that a proposed array has adequate wind restraint.
Require two linked calculation boundaries:
- The racking designer defines the exact array geometry, adopted actions, load combinations, response model, support conditions and reactions for every roof zone and operating condition.
- The responsible building professional checks those reactions, added dead load and construction effects against the actual structure, including local bearing, deck fasteners, member capacity, stability, deflection, ponding or drainage sensitivity where relevant.
For a U.S. design route, the current ASCE/SEI 7-22 page identifies loads including dead, live, snow, rain, seismic and wind, plus load combinations. A project outside that route may adopt another standard. Record the jurisdiction, edition, risk basis and project modifications instead of citing “ASCE” or “Eurocode” without scope.
FM’s 2026 Data Sheet 1-15, Roof-Mounted Solar Photovoltaic Panels, is a property-loss-prevention framework rather than a universal building code. It nevertheless demonstrates why the roof and PV system must be coordinated: its recommendations address wind securement, snow and rain loads, roof drainage, fire and the capacity of the supporting roof. Apply its requirements only where the owner, insurer or project basis adopts them.
Do not collapse the two boundaries into one “roof load allowed” number. State whether a limit is distributed, concentrated, line-based or tied to named support locations and combinations. Preserve its units, sign convention, tributary area and approval status.
Protect the Roof Assembly as a System
The visible membrane is only one layer of the roof interface. A support pad can transmit pressure through membrane, cover board and insulation before the deck sees the load. A mechanical attachment may cross those layers and create waterproofing, condensation, thermal or movement details. An adhesive or bonded solution introduces substrate preparation, compatibility, environmental and inspection questions. None should be approved from the trade name of the roof covering alone.
The roof evidence pack should therefore record:
- membrane type, manufacturer where confirmed, installation system, age, condition and repair history;
- cover board, insulation type and thickness, vapor-control layers and deck construction where relevant;
- permitted contact materials, protection/slip layers, local bearing limits and movement allowances;
- drains, scuppers, overflow routes, crickets, falls, control joints and areas of known ponding;
- the party authorized to approve penetrations, flashing, welded patches, adhesives or warranty changes;
- inspection access and the repair method if a support point damages the assembly.
An older U.S. federal Solar Ready Buildings Planning Guide explains that roof-mounted solar adds static and dynamic actions and that penetrating mounts need structural support and suitable flashing. Use it as planning background, not as the current governing code. Its enduring lesson is the coordination sequence: identify roof construction and loads first, then select and detail the interface with the responsible roofing and structural parties.
The release record should also state who owns future roof work. If membrane inspection or replacement requires module removal, define access, temporary storage, electrical isolation, lifting and reinstatement responsibilities before award. A mounting route that is buildable on day one may still be incompatible with the building’s maintenance plan.
Coordinate Wind Zones, Layout and Movement Restraint
Flat-roof arrays are spatial systems. Wind effects can change with building height and proportions, roof-zone position, parapets, array height and tilt, row spacing, exposed edges, nearby terrain and topography. Ballast, anchor demand and member forces therefore need a controlled layout, not an average value applied to every module.
The current FM Data Sheet 1-15 explicitly connects roof-mounted PV wind design to defined wind criteria and current ASCE 7-22 provisions within its adopted route. It also distinguishes roof and PV-system ratings. This supports a general review principle: keep the site hazard, roof zones, array aerodynamics, racking resistance and building load path as separate evidence objects until their definitions and revisions reconcile.
For a ballasted option, request the ballast mass and position by named array zone, the friction or slip assumptions used, bearing areas and movement controls. For an attached option, request reactions and connection demands by attachment type and support location. For a hybrid option, require the analysis to show how load sharing changes if construction tolerances or contact conditions differ from the model.
Do not convert those outputs into a universal kilograms-per-module allowance. Geometry changes can alter both aerodynamic demand and load distribution. A supplier substitution, module change, parapet revision, relocated array or new rooftop obstruction should trigger a stated recheck.
Preserve Drainage, Fire, Electrical and Safe Access
The highest-yield layout is not automatically the usable roof layout. The array must coexist with water flow, fire-service access, electrical equipment, roof inspection, other services and safe installation and maintenance. Those constraints should reduce the candidate area before procurement fixes module count or racking quantities.
Map drains, scuppers and overflow paths, then show how rails, trays, ballast and cable supports avoid obstructing them. FM Data Sheet 1-15 specifically calls for keeping rainwater routes to drains, scuppers or roof edges unobstructed within its loss-prevention scope. The project team must still apply the actual roof-drainage design, local code and owner requirements.
For U.S. projects, UL Solutions’ PV mounting certification overview explains that UL 2703 covers mounting, clamping and grounding/bonding functions, and that a rooftop fire classification concerns a specific module-and-racking system. Do not treat a logo or generic “UL 2703 compliant” statement as proof that every required attribute, component combination and installation condition is covered. Verify the listing scope for the proposed assembly and adopted code route.
Access is also a design input. Roof edges, hatches, skylights, equipment service zones, lifting routes and emergency pathways need controlled clearances. OSHA’s solar fall-hazard guidance is a U.S.-specific safety source: it highlights roof edges, skylights and hatches and distinguishes construction from maintenance requirements. It does not replace the project safety plan or local regulation, but it demonstrates why access cannot be left until installation.
Coordinate bonding, grounding, cable support, equipment locations and penetrations with the electrical design. A structurally acceptable layout can still fail if the listed assembly, fire route, cable path or maintenance access changes after the racking was calculated.
Issue One Roof Interface Release Record
The final decision asset is a Roof Interface Release Record: one controlled table that connects each roof condition to the party who owns it, the evidence that closes it, the mounting options affected and the event that reopens the review. It should travel with the roof plan and supplier inquiry.
| Record field | Required entry | Control question |
|---|---|---|
| Roof area and source | Named zone, drawing/survey reference, revision and date | Can every proposal be mapped to the same roof geometry? |
| Condition or constraint | Structural, envelope, drainage, wind, fire, electrical, access or maintenance interface | Is the issue stated as a verifiable condition rather than a vague warning? |
| Evidence and status | Record, survey, calculation, listing, approval or test; confirmed, accepted assumption, open or held | Does the status permit the requested pricing or design decision? |
| Responsible party | Owner, building engineer, racking designer, roofer, fire reviewer, electrical designer, installer or authority | Who may answer, review and approve? |
| Option impact | Ballasted, attached, hybrid or all options | Would one route remain viable if the condition stays open? |
| Closure and change trigger | Required output, need-by date and events that require recheck | Will a later roof, module, layout or code change reopen the decision? |
Use the record to compare proposals on equal ground. If one supplier prices a confirmed roof basis and another assumes unlimited capacity, unrestricted ballast and no warranty impact, the totals are not alternatives to the same scope. Return the assumptions for closure or preserve the comparison as conditional.
The record does not approve a roof. It makes the approval boundary visible and prevents a catalogue selection from silently becoming a building decision.
Related Resources
- Solar Mounting Systems — establish the commercial product-family route and submit project information.
- Solar Mounting Design Inputs — control the broader module, site, load, durability and project baseline.
- Solar Mounting Wind Load — audit the wind evidence chain from site hazard to support reactions.
- Solar Panel Mounting Brackets — approve a bracket only as part of an identified assembly.
References
- FM — Data Sheet 1-15: Roof-Mounted Solar Photovoltaic Panels (2026)
- ASCE — ASCE/SEI 7-22
- U.S. Department of Energy — PV System Owner’s Guide to Weather Vulnerabilities (2021)
- U.S. Federal Energy Management Program — Solar Ready Buildings Planning Guide (2010)
- UL Solutions — PV Mounting Systems Certification
- OSHA — Solar Energy: Falls
Next Step: Release the Roof Interface Package
Before requesting a firm mounting proposal, issue one controlled roof plan and the Roof Interface Release Record. Include the building and roof construction, surveyed conditions, structural assessment basis, permitted reactions, roof build-up, drainage, wind and layout zones, fire and service access, electrical interfaces, maintenance constraints, responsible reviewers and approval status. Ask each supplier to return its exact configuration, load path, reactions, ballast or attachment schedule, roof details, assumptions, exclusions and change triggers against that same basis.
Submit the package through Solar Mounting Systems when you need East Baoyu to define a proposed mounting and document scope for project review. The responsible project parties retain authority for the building assessment, adopted codes, roof-system approval, fire and electrical compliance, installation method, safety plan and final acceptance.
References, disclosure and change record
References and further verification
- https://www.energy.gov/sites/default/files/2021-09/pv-system-owners-guide-to-weather-vulnerabilities.pdf
- https://www.asce.org/publications-and-news/codes-and-standards/asce-sei-7-22
- https://www.fm.com/-/media/project/publicwebsites/fmglobal/documentum-new/data-sheet-individual/01-construction/fmds0115.pdf
- https://www1.eere.energy.gov/femp/pdfs/46078.pdf
- https://www.ul.com/services/pv-mounting-systems-certification
- https://www.osha.gov/green-jobs/solar/falls
- https://eastbaoyu.com/solar-mounting/
- https://eastbaoyu.com/solar-mounting-design-input-checklist-epc-procurement/
- https://eastbaoyu.com/solar-mounting-wind-load/
- https://eastbaoyu.com/solar-panel-mounting-brackets/
Disclosure: East Baoyu manufactures and supplies products discussed on this website. Structured drafting tools may assist research and editing, but technical claims, project inputs and release decisions require qualified review under the applicable project responsibilities.
Version 1.0: Scheduled as EB50-014 on 2026-09-05.
View the public Content Change Log · Corrections: info@baolaipipes.com
