Fixed or retractable roof pathway
FASGAR · PROJECT AUTHORITY CENTRE
Move from product interest to a controlled project specification.
Coordinate fixed aluminium roofs and retractable waterproof PVC/fabric roof systems around plan geometry, support, drainage, wind, membrane performance, movement, controls, environment and local structural interfaces.
01 · PROJECT INPUTS
Define the conditions before the exact system is released.
These inputs are deliberately upstream of model selection so the product does not dictate the brief.
Overall dimensions, bay layout and support condition
Wall-mounted/freestanding/existing-structure interface
Rainwater collection, falls, gutters and discharge route
Wind, snow where relevant and coastal/environment exposure
Membrane/material/roof-panel requirements
Motor, control, sensor and power requirements for retractable systems
Foundation/fixing, freight, installation and local engineering responsibility
02 · EVIDENCE CONTROL
Keep project claims attached to what the evidence actually proves.
Generic declarations, outdated catalogues or unrelated certificates should not be carried into a project as exact-system evidence.
Exact aluminium/profile/material specification
Exact membrane construction and fire evidence where applicable
Structural/span/wind evidence for selected configuration
Motor/control/sensor documentation
Drainage/gutter/downpipe details
Coating/corrosion suitability
Exact-system drawings, installation information and warranty
03 · CAD / DRAWING REGISTER
Planning references are not exact-system construction drawings.
Every drawing/model status stays visible so consultants know what can be used now and what only exists after configuration or project-specific design.
| Resource | Status | Purpose |
|---|---|---|
| Architectural roof concept / planning layout | Public planning | Early scope, interface and consultant coordination only. |
| Generic technical reference / typical detail | Public planning | Explains system logic without representing an exact supplied configuration. |
| Exact-system GA / dimensional drawing | Exact-system | Issued only after the quoted system/configuration is known. |
| Native CAD / DWG / DXF | Verify availability | Availability and revision must be confirmed against the exact supplied system. |
| BIM / Revit / IFC object | Verify availability | Only described as BIM where a genuine verified native model exists. |
| Foundation / fixing / setting-out drawing | Project-specific | Depends on site/building conditions, local engineering and the selected system. |
| Services / electrical / controls interface | Project-specific | Coordinates the supplied system with local power, data, water, drainage or controls. |
04 · SPECIFICATION STARTER
Write the project around performance, interfaces and evidence.
These clauses are a project-planning structure, not a substitute for local professional specifications or exact-system documentation.
Roof pathway and geometry
Primary frame and roof/membrane material
Structural design criteria
Drainage/rainwater management
Movement and operating state
Motor/controls/electrical interface
Finish/coastal exposure
Foundation/fixing responsibilities
Evidence, drawings and maintenance
05 · TENDER / RFP SCHEDULE
Ask bidders for the same controlled information.
A consistent schedule makes technical comparison easier and reduces hidden assumptions.
Site/roof plan
Dimensions/bay layout
Fixed/retractable intent
Wind/snow/environment
Drainage route
Material/membrane requirement
Power/controls
Fixing/foundation interface
Evidence/drawings
Freight/installation scope
06 · OPERATIONS & HANDOVER
Specify how the system will be maintained after delivery.
Maintenance, spares, records and inspection should be defined before purchase, especially for remote or high-use projects.
Roof/membrane cleaning
Drainage/gutter inspection
Motor/control service
Track/moving-component inspection
Fastener/connection check
Coating/corrosion review
Storm/high-wind operating procedure
Replacement membrane/control/spare plan
DOWNLOADABLE PROJECT RESOURCE
Carry the authority pack into the project file.
Export the current project-control structure, then replace planning statements with exact project/system information as the design develops.