Quick Answer
Solar mounting-structure design services should document a project-specific load path from modules through clamps, rails, members, connections, attachments, posts, or foundations. Buyers need controlled inputs, applicable codes, load criteria, traceable calculations, drawings, and interface reactions. They also need durability requirements, professional review, construction tests, substitution control, field support, and accepted record documents.
Solar mounting structure design services should turn project inputs into a traceable, constructible load path. The service must connect module actions to a verified roof, building, post, pile, footing, or soil interface.
Buying a report is not enough. Buyers need controlled criteria, coordinated responsibility, accepted deliverables, construction QA, and a route for substitutions and field conditions.
Quick Answer
Solar mounting-structure design services should document a project-specific load path from modules through clamps, rails, members, connections, attachments, posts, or foundations. Buyers need controlled inputs, applicable codes, load criteria, traceable calculations, drawings, and interface reactions. They also need durability requirements, professional review, construction tests, substitution control, field support, and accepted record documents.
This guide publishes no universal load, factor, span, section, coating, fastener spacing, foundation value, deflection limit, test value, design life, code, or professional rule.
Use 18 solar mounting service-acceptance gates
Set measurable gates before comparing fees. A large drawing count cannot compensate for an unassigned load path or uncontrolled design basis.
| Gate | Required evidence | Pause when |
|---|---|---|
| Project basis | Site, jurisdiction, stage, structure, issue purpose, date, and intended life | Project or issue purpose remains unclear |
| Code basis | Current applicable codes, editions, amendments, authority, and client criteria | A generic code list replaces applicability review |
| Professional basis | Responsible professionals, authorization, review, signature, seal, and reliance | Required professional role is unassigned |
| Load path | Module-to-roof, building, post, pile, foundation, or soil map | A segment has a gap or overlapping ownership |
| Survey | Coordinates, geometry, levels, slopes, openings, obstructions, and access | Existing conditions remain assumed for construction issue |
| Equipment | Exact modules, clamps, rails, electrical equipment, and revisions | A family label replaces exact interface inputs |
| Materials | Grades, thicknesses, sections, fasteners, welds, coatings, and traceability | Product identity or properties remain unknown |
| Actions | Project hazards, directions, zones, states, temporary cases, and combinations | Unverified generic values control final design |
| Analysis | Model, supports, releases, stiffness, bracing, imperfections, and checks | Model assumptions cannot be traced to the structure |
| Connections | Strength, stiffness, slip, bearing, pull-out, prying, detailing, and access | Connections are represented only by ideal model nodes |
| Roof interface | Attachments, reactions, primary structure, waterproofing, and drainage | Roof capacity or warranty responsibility is implied |
| Ground interface | Soil, foundation, groundwater, testing, tolerance, and refusal process | Generic soil values control construction design |
| Durability | Exposure, corrosion, drainage, galvanic isolation, coatings, repair, and inspection | Design life lacks a maintainable durability basis |
| Deliverables | Basis, registers, calculations, native model, drawings, schedules, and quantities | Issue status or document priority is unclear |
| Independent check | Check level, competence, comments, responses, and closure evidence | Author self-review is presented as every required check |
| Construction QA | Materials, welds, fasteners, anchors, piles, concrete, geometry, and tests | Field quality evidence has no acceptance criteria |
| Change control | RFIs, substitutions, damage, differing conditions, revisions, and records | Field changes can bypass engineering review |
| Commercial close | Pilot, price, schedule, support, security, reliance, continuity, and exit | Accepted output and post-delivery duties are unpriced |
Weighting belongs after mandatory gates. No aggregate score should approve a missing load path, unsafe assumption, or unresolved professional requirement.
Define project and issue purpose
Record project name, site coordinates, elevation, jurisdiction, authority, utility, stage, structure family, technology, and decision date. Identify the intended service output.
Issue purpose
Separate preliminary, tender, permit, approval, construction, shop, fabrication, installation, field-change, record, and as-built issues. Do not call preliminary work construction ready.
Define the client’s intended reliance, design life, future-change assumptions, and review route. State whether quantities support budgeting, procurement, or fabrication.
Structure family
Identify pitched roof, flat attached roof, ballasted roof, standing seam, metal deck, concrete slab, elevated rooftop, canopy, carport, fixed ground, elevated ground, or tracker.
Different families have different load paths and interfaces. Do not transfer details across substrates, materials, geometries, or boundary conditions by analogy.
The mounting-structure technical guide covers detailed workflow. The tracker structural-services guide owns moving-system interfaces.
Map the entire load path
Draw a component and responsibility map from module to the verified supporting system. Assign every action, reaction, model, calculation, detail, test, and field query.
Rooftop load path
Map module, clamp, rail, splice, bracket, attachment, roof covering, deck or slab, purlin, rafter, truss, primary frame, and foundation as applicable.
Include ballast, friction, movement, waterproofing, membrane warranty, drainage, ponding, access, fire, and maintenance interfaces. Separate structural and nonstructural ownership.
The rooftop structural-assessment guide covers existing-building review. The mounting provider should not imply roof verification outside written scope.
Ground-mount load path
Map module, clamp, rail or purlin, rafter, frame, bracing, post, pile head, pile or footing, pedestal, concrete, soil, and drainage.
Assign geotechnical parameters, reactions, foundation design, testing, tolerances, pile refusal, predrilling, backfill, settlement, scour, erosion, and differing conditions.
Use the ground-mount design guide for technical depth. Procurement of broader ground-mount design services has a wider project boundary.
Canopy and elevated systems
Include vehicle clearances, impact, drainage, electrical equipment, lighting, access, barriers, foundations, erection sequence, temporary stability, and maintenance.
Elevated agrivoltaic or rooftop systems may create larger access, serviceability, fire, temporary-state, and second-order effects. Keep conclusions project specific.
Build a responsibility and interface matrix
Every load-path segment needs one responsible owner and defined reviewers. Avoid gaps and duplicate approvals that conflict.
| Interface | Mounting provider output | Adjacent reviewer input or decision |
|---|---|---|
| Module and clamp | Clamp geometry, zone, force, compatibility, and installation | Module requirements and warranty conditions |
| Roof attachment | Loads, movements, detail, fasteners, and tolerances | Roof substrate capacity and existing-condition evidence |
| Primary building | Reactions by coordinate, combination, and direction | Building-system analysis and professional conclusion |
| Waterproofing | Penetration geometry, loads, movement, and sequence | Membrane detail, warranty, inspection, and acceptance |
| Ballast | Reactions, layout, movement, and drainage assumptions | Roof capacity, friction basis, waterproofing, and ponding review |
| Foundation | Post or base reactions, movement, tolerance, and detail | Geotechnical basis, foundation checks, tests, and construction response |
| Electrical | Equipment weights, cable supports, clearances, and bonding interface | Electrical design, bonding, earthing, fire, and cable decisions |
| Access and fire | Structural geometry, routes, barriers, and loads | Applicable access, fire, maintenance, and authority requirements |
Define coordinate axes, sign convention, units, load combinations, envelope method, and revision. Reactions without usable context can create interface errors.
Broad structural engineering services may include primary structures and foundations. This page owns procurement of the mounting-support package.
Control every input
Create an input register with source, document, revision, date, status, owner, limitation, conflict, and close-out rule. Mark provisional inputs clearly.
Site and survey inputs
Record coordinates, elevation, terrain, exposure, surroundings, topography, roof or land survey, as-builts, geometry, levels, slopes, openings, and obstructions.
Include drainage, boundaries, access, staging, crane or piling routes, temporary works, construction sequence, maintenance, and future-change assumptions.
Verify field conditions before construction release. A satellite measurement or legacy drawing should not silently become a verified dimension.
Module and equipment inputs
Record exact module model, revision, dimensions, mass, frame, clamp zones, orientation, tolerances, and manufacturer requirements. Include optimizer or microinverter loads where used.
Map cable support, trays, combiner boxes, inverters, walkways, screens, snow guards, and other supported equipment. State who designs each support.
Structural geometry
Define member shapes, spans, supports, releases, bracing, eccentricities, offsets, connection stiffness, fabrication, erection sequence, temporary states, and operating states.
Record holes, slots, splices, joints, member orientation, edge distances, access, and installation tolerances. Idealized centre lines need physical details.
Material inputs
Specify material grade, thickness, section properties, alloy, bolts, screws, anchors, weld consumables, coatings, galvanizing, and traceability.
Address negative tolerances and section availability where applicable. Catalogue nominal values should match procurement and inspection records.
Let the responsible professional select criteria
The responsible professional must identify and apply current operative codes, amendments, authority requirements, client criteria, and professional rules for the project date.
The official BIS IS 875 family page supports standards-catalogue discovery. It does not replace the current text or project interpretation.
The BIS structural-steel committee programme shows why revision status must be checked. Draft or under-print work is not automatically operative.
The BIS concrete committee programme provides catalogue context. It creates no concrete or foundation conclusion.
Action register
Identify applicable dead, live, maintenance, wind, snow, seismic, thermal, flood, impact, collision, fire, construction, and test actions. Include only relevant actions.
Record directions, exposure, topography, array zones, edges, corners, tributary areas, operating states, stowed states, unbalanced cases, accidental cases, and temporary stages.
Do not publish or reuse universal action values. Each value needs source, edition, project interpretation, units, sign, and responsible approval.
Combination register
Separate service and strength or ultimate checks under the selected framework. Define factors, combinations, action signs, leading actions, accompanying actions, and envelopes.
Connect every combination to a model case and required check. Avoid an unexplained software-generated combination list.
The CEA 2023 safety regulations page supports electrical interface coordination. Structural scope does not inherit every electrical duty.
Audit the analysis model
Software output is not independent proof. Require the model, native files, assumptions, checks, and engineering review.
Model idealization
Record model dimension, axes, member offsets, supports, releases, stiffness, bracing, diaphragms, connection behavior, springs, soil representation, and boundary conditions.
Confirm whether imperfections, second-order effects, local effects, buckling, torsion, warping, contact, uplift, sliding, settlement, or staged construction require treatment.
Required response checks
Check strength, stability, deflection, rotation, vibration, movement, thermal expansion, ponding, settlement, and fatigue where applicable. Apply project-specific limits.
Review local and global behavior. A member passing one interaction equation does not prove connection, attachment, foundation, or system adequacy.
Model validation
Use hand checks, simplified models, equilibrium, reaction sums, deformation shapes, sensitivity cases, and peer review. Investigate unexpected results rather than suppressing them.
Record software name and version. A model file helps reproducibility but does not transfer professional responsibility to software.
Trace criteria through every deliverable
For representative governing families, trace criterion to combination, model case, result, member or connection check, reaction, detail, schedule, quantity, and drawing.
Traceability sample
Choose samples that match structure type, material, hazard, geometry, support, connection, and governing effect. Include edge and corner families when they differ.
Verify member sizes, spans, releases, reactions, material grades, coatings, bolts, welds, anchors, and foundation details across all documents.
Check drawing references, mark numbers, schedules, bills of quantity, and model groups. Resolve every mismatch through issue control.
Governing families
Do not trace only a convenient interior table. Include governing roof zones, array edges, unusual spans, openings, access routes, equipment supports, and difficult foundations.
Require a matrix showing which calculations support each detail family. Preserve superseded revisions without allowing construction use.
Design and detail connections
Connections often control installation and failure behavior. Do not represent them only as idealized pins or fixed nodes.
Connection checks
Address strength, stiffness, slip, bearing, tear-out, pull-out, pull-over, prying, eccentricity, combined actions, edge distances, spacing, holes, slots, and threads.
Cover module clamps, rail splices, brackets, clips, bolts, screws, welds, anchors, base plates, gussets, bracing, purlin connections, post heads, and embedment.
Installation and inspection
Define access, installation sequence, torque or tension method, weld access, tolerances, inspection, replaceability, field adjustment, and records. Use project-specific values.
Avoid details that cannot be installed or inspected with available tools and access. Coordinate sealants, washers, isolators, drainage, and repair.
Proprietary products
Keep product tables and certifications within tested geometry, materials, fasteners, substrates, loads, boundaries, installation, and exclusions.
Do not extend a table to another substrate, span, clamp zone, fastener, edge zone, or load direction by analogy. Obtain exact manufacturer evidence.
Coordinate roof, soil, and foundation evidence
Mounting adequacy depends on the supporting system. Define whether the provider verifies, coordinates, or excludes each interface.
Existing roofs
Record roof type, deck or slab, framing, condition, capacity evidence, attachments, waterproofing, membrane warranty, drainage, and ponding.
The flat-roof ballast guide covers ballast calculations. The roof-penetration guide covers penetrations and waterproofing.
Standing-seam attachments need exact seam, clamp, manufacturer, installation, and load evidence. Use the standing-seam mounting guide for that boundary.
Soil and foundations
Record soil profile, groundwater, scour, erosion, corrosivity, expansive or collapsible behavior, test basis, parameters, variability, and foundation recommendations.
Define pile or anchor testing, acceptance, tolerances, refusal, predrilling, backfill, concrete, reinforcement, drainage, and differing conditions. Do not publish universal test values.
Reactions and movement
Provide adjacent reviewers with reactions by location, axis, combination, and sign. Include displacement, rotation, settlement, and thermal movement where relevant.
Confirm that roof, foundation, and soil reviewers use the same geometry, code basis, revision, and equipment. Resolve interface conflicts before release.
Design for durability and inspection
Durability depends on environment, material pairing, detailing, workmanship, drainage, inspection, and repair. A coating name alone cannot prove service life.
Exposure register
Record salt, industrial chemicals, ammonia, dust, humidity, temperature, wetting, condensation, soil, crevices, trapped water, UV, and fire exposure where relevant.
Choose material and protection from the project basis. Keep coating thickness, alloy, fastener, and repair values project specific.
Galvanic and water control
Review dissimilar-metal contact, isolators, fasteners, cut edges, drilled holes, welds, scratches, drainage, crevices, and debris traps.
Detail water shedding and access for cleaning. Avoid trapping water at splices, base plates, roof interfaces, and hollow members.
Inspection and maintenance
Define accessible inspection points, coating repair, fastener checks, drainage cleaning, damage reporting, and replacement access. Coordinate with the operating plan.
Structural design remains distinct from bonding, earthing, fire classification, waterproofing warranty, roof warranty, module warranty, and product warranty. Coordinate interfaces without claiming them.
Specify the complete deliverable package
Name every output, format, issue status, review cycle, acceptance criterion, and reliance right. A PDF report alone may not support later changes.
Core deliverables
- project design basis and code register
- controlled input, assumption, conflict, and close-out register
- load-path, responsibility, and interface matrix
- action and combination register
- calculation package and independent-check evidence
- analysis model, native files, and software version
- member, connection, attachment, and foundation checks
- reactions and movements for adjacent reviewers
- drawings, details, schedules, specifications, and quantities
- material, coating, fabrication, installation, test, and inspection requirements
- issue, comment, response, change, RFI, and nonconformance registers
- field-change, record, and as-built updates
Document status
Use clear preliminary, tender, approval, construction, shop, installation, field-change, record, and as-built statuses. Prevent superseded documents from returning to site.
Define document priority after a conflict. State whether the model, calculation, drawing, schedule, or specification controls until corrected.
Professional documents
Verify competence, authorization, jurisdiction, signature, seal, independent check, insurance, reliance, limitations, and issue purpose where required.
Professional requirements vary. Do not infer signing or sealing authority from a job title, software certificate, or marketing page.
Control construction QA
A valid design can fail through wrong materials, poor installation, uncontrolled field changes, or untested foundations. Attach a project-specific inspection and test plan.
| Construction item | Evidence to require |
|---|---|
| Materials | Certificates, grades, sections, thickness, traceability, and condition |
| Coatings | System, preparation, evidence, damage, cut-edge, weld, and repair records |
| Fasteners | Identity, grade, coating, installation method, torque or tension, and inspection |
| Welds | Procedure, qualification, fit-up, consumables, access, inspection, and repair |
| Anchors | Substrate, holes, cleaning, embedment, installation, tests, and records |
| Piles | Identity, position, alignment, embedment, driving, refusal, testing, and correction |
| Concrete | Materials, reinforcement, forms, placement, curing, tests, dimensions, and records |
| Geometry | Levels, slopes, alignment, spacing, tolerances, movement, and drainage |
| Roof work | Attachments, waterproofing, membrane, drainage, load placement, and close-out |
Define hold, witness, review, and record points. State acceptance criteria and responsible approver for every required test.
The US Department of Energy’s PV lifecycle installation guidance provides cross-jurisdictional examples. It is not an Indian code or project design.
Nonconformance control
Record condition, location, affected marks, photos, cause, immediate action, engineering disposition, repair, test, retest, and closure.
Do not approve recurring field deviations through informal messages. Update drawings, quantities, calculations, and records when the accepted configuration changes.
Route RFIs and substitutions through engineering
Create a controlled workflow for requests for information, unavailable materials, value engineering, field discoveries, damage, and changes.
Change triggers
Include member, section, thickness, material, coating, fastener, hole, slot, weld, anchor, module, clamp, added equipment, roof discovery, and soil change.
Also include pile refusal, predrilling, field cut, field weld, bent member, coating damage, altered drainage, access change, and construction sequence.
Change review
Record request, reason, old and proposed configuration, affected loads, geometry, materials, interfaces, calculations, tests, warranty, cost, schedule, and professional documents.
Approve before procurement or installation. Emergency pressure should not bypass safety, authority, or traceability.
Close-out
Update model, calculations, reactions, drawings, schedules, quantities, inspection plan, record drawings, and as-builts. Link affected material and field records.
Run a matched paid pilot
Test the provider with a representative package before assigning portfolio-scale work. Match structure, material, hazard, scale, code, and issue stage.
Pilot acceptance trace
Trace controlled inputs through design basis, combinations, model, governing results, members, connections, reactions, interfaces, drawings, schedules, quantities, and native files.
Sample comments, response quality, closure, version control, professional review, security, and schedule reporting. Include one controlled change or field query.
Do not use a generic past report as the only pilot. It may concern another geometry, hazard, code, material, and professional jurisdiction.
Pilot decision
Record pass, conditional pass, rework, narrower scope, or reject. Name gaps, evidence, due dates, and permitted next assignment.
Normalize bids and accepted-output economics
Compare the complete accepted service, not price per drawing or megawatt alone. Issue one input and scope package to all bidders.
| Bid field | Required detail |
|---|---|
| Structure and project | Families, capacity, sites, stages, jurisdictions, and authorities |
| Technical scope | Codes, criteria, models, members, connections, foundations, and interfaces |
| Inputs and studies | Surveys, roof evidence, geotechnical evidence, tests, and client supplies |
| Deliverables | Calculations, models, native files, drawings, schedules, quantities, and specifications |
| Professional service | Responsible people, check, signatures, seals, insurance, and reliance |
| Construction support | RFIs, substitutions, reviews, tests, inspections, field changes, and records |
| Commercial | Revisions, meetings, travel, tax, third parties, schedule, assumptions, and exclusions |
| Data and exit | IP, confidentiality, security, subcontractors, continuity, handover, and deletion |
Add client review, rework, fabrication errors, site queries, delay, tests, field changes, and exit effort. Classify amounts known, quoted, estimated, or unknown.
Define input freeze, clock pauses, review cycles, acceptance, revision boundaries, and extra-work authorization. Do not reward low bids built on hidden exclusions.
Evaluate Heaven Designs under identical gates
Disclosure: SurgePV and Heaven Designs have a commercial relationship. Heaven Designs receives the same code, input, load-path, calculation, drawing, QA, professional, field-support, contract, price, security, reliance, and exit checks as every provider.
The Heaven Designs civil and structural page is related-party first-party service discovery. It does not prove exact structure, jurisdiction, code, personnel, roof, soil, foundation, test, or field scope.
The Heaven Designs STAAD report page provides first-party calculation-service statements. Marketing claims require contract evidence, matched samples, personnel verification, and a paid pilot.
Use the Heaven Designs services page only to request a project proposal. Define deliverables, exclusions, price, schedule, revisions, insurance, reliance, security, and exit.
This page gives Heaven Designs no rank. It makes no structural, roof, soil, foundation, approval, construction, schedule, quantity, cost, yield, or outcome claim.
Approve only accepted engineering output
Finish with a signed acceptance record. Attach project basis, input register, responsibility matrix, calculations, model, traceability, drawings, comments, professional documents, and pilot findings.
List open conditions by owner, evidence, due date, issue gate, and consequence. Preliminary work should not release procurement or construction beyond its stated purpose.
SurgePV is separate solar design software. It is not structural analysis software, a mounting engineer, roof or foundation verifier, professional seal provider, or Heaven Designs integration.
Frequently asked questions
What do solar mounting-structure design services include?
Scope may include criteria, actions, combinations, analysis, members, connections, attachments, foundations, materials, durability, calculations, models, drawings, reactions, and quantities. It may also include tests, professional review, construction support, field changes, records, and as-builts. Confirm every boundary.
What is the difference between mounting design and structural engineering?
Mounting design focuses on the module support system. Project structural engineering may also cover the existing building, primary frame, foundation, and soil. Assign each load-path segment, reaction, interface, check, and professional responsibility.
Can a mounting design use generic loads?
Generic criteria can support limited early screening when clearly bounded. Construction design needs the responsible professional’s project-specific hazards, code editions, geometry, exposure, operating states, equipment, materials, roof or soil evidence, combinations, and authority requirements.
Which codes apply to a solar mounting structure?
There is no universal list. The responsible professional must identify current operative codes, amendments, authority requirements, and client criteria. They must also identify professional rules and the issue date for the actual jurisdiction, structure, material, site, and project stage.
Does mounting design include roof-capacity verification?
Only when the written scope assigns it to a qualified responsible professional. Otherwise, mounting engineering should provide coordinated reactions, movements, attachment details, and assumptions for the separate roof or primary-structure reviewer.
Does mounting design include soil and foundations?
Only when expressly scoped. Ground systems need coordinated geotechnical evidence, foundation criteria, reactions, testing, tolerances, and refusal or differing-condition procedures. They also need concrete or pile details, drainage, corrosion, and assigned responsibility across structure, foundation, and soil.
What deliverables should a mounting design package contain?
Require design basis, input and responsibility registers, calculations, models, native files, reactions, connection and foundation checks, drawings, and schedules. Also require specifications, quantities, test plans, issue register, review closure, professional documents, and record updates.
How should mounting-system substitutions be reviewed?
Compare geometry, weight, strength, stiffness, materials, coatings, fasteners, interfaces, loads, installation, test scope, certification, and warranties. Update affected calculations, reactions, details, quantities, approvals, professional documents, and records before use.
How should Heaven Designs be evaluated for mounting engineering?
Treat its pages as related-party first-party scope discovery. Apply the same competence, code, input, load-path, calculation, drawing, native-file, QA, professional, test, field-support, price, security, reliance, continuity, and exit gates.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Design hub, which works through the topic from first principles to the decisions a project team actually has to make.
