How do requirements flow through AGL design?

Start from how the aerodrome will operate and which documents govern, then carry every requirement into layout, circuits, equipment and review.

HOW REQUIREMENTS TRAVEL THROUGH AGL DESIGN 1 OPERATIONAL BASIS Runway use, category, code and aerodrome data OUTPUT: LIGHTING NEEDS 2 GOVERNING DOCUMENTS Regulation and contract call-up, editions fixed OUTPUT: REQUIREMENT LIST 3 LIGHTING LAYOUT Light types, patterns and positions OUTPUT: LAYOUT DRAWINGS 4 CIRCUITS & POWER Series circuits, loads, CCR and transformer sizing, cables, earthing OUTPUT: CIRCUIT DESIGN 5 EQUIPMENT & SPEC Fixtures, CCRs and transformers named to their standards OUTPUT: SPECIFICATION, MATRIX STARTED 6 DESIGN REVIEW Check against the requirement list; approve deviations OUTPUT: DESIGN ISSUED FEEDBACK LOOP A change in operations updates step 1 first; any change or rejected deviation then returns to step 2 and the list is updated. REQUIREMENTS FIRST · THEN LAYOUT, CIRCUITS AND EQUIPMENT · THEN REVIEW SIMPLIFIED SEQUENCE · REAL PROJECTS OVERLAP STAGES AND ITERATE
operational basis
requirement list
design development
review gate
The Fact Design flow

The design requirement flow starts with the operational basis and the governing documents, which together produce a requirement list. That list is carried into the lighting layout, the circuit and power design and the equipment specification, and checked at a design review.

Designs go wrong when equipment is chosen first and requirements are found later. Keep one requirement list with sources and editions, and when anything changes, send it back through that list so drawings, calculations and the compliance matrix stay consistent.

  1. Fix the basis. Record runway use, category, code and aerodrome data.
  2. Fix the documents. Confirm what applies and which editions.
  3. Carry requirements forward. Trace each into drawings, calculations and the specification.
  4. Review against the list. Check every requirement is met or has an approved deviation.
  5. Control changes. Return any change to the list and update what it affects.
Requirements first

Basis and documents define the need, then layout, circuits and equipment are chosen to meet it.

Equipment first

Products are picked early and gaps against the requirements are found late, causing rework.

InputsOperational data and the governing documents
Requirement listOne list, with source and edition for each item
LayoutDrawings of light types, patterns and positions
Circuit designLoads, CCR and transformer sizing, cables, earthing
SpecificationEquipment named to its standards and tests
Compliance matrixStarted at design, completed through testing
ReviewDesign checked against the requirement list
Change controlChanges logged and traced back to requirements
A simplified sequence for learning, not a design procedure. Real projects overlap and repeat stages. Follow your regulator’s requirements, your contract and your organisation’s design process.
Entry 11 · Mandatory versus advisory requirements Entry 13 · Inspection requirement flow

Frequently Asked Questions

Q1Where does AGL design start?

With the operational basis: how the runways and taxiways will be used, their category and code, and the aerodrome data. That decides which lights are needed, and the governing documents decide the rules they must meet.

Q2Why fix the document editions early?

Requirements and test methods can differ between editions. Fixing the edition at the start keeps layout, calculations and specification on one basis and avoids rework when a newer edition appears mid-design.

Q3What happens if a requirement changes during design?

Send it back to the requirement list, update it, and check which drawings, calculations and specification clauses it touches. Record the change so the design, the compliance matrix and later tests stay in step.

Q4Who approves a departure from a requirement?

The party with authority under the contract or regulation, such as the specifier, client or regulator. Record the approval and carry the deviation into the compliance matrix so it stays visible.

Q5How does the design link to inspection and testing?

Each requirement carried into the design should also carry its verification method forward. That is what lets inspection and test plans be built from the same requirement list, so nothing is designed that cannot later be proved.

Precision AGL Academy

See It. Understand It. Then Learn How to Engineer It.

Recognising an AGL system visually is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.

Build Practical AGL Engineering Skills

Go deeper with structured training from Precision AGL Academy, covering:

AGL Fundamentals Design & Electrical Engineering Approach Lighting Photometry Installation & Commissioning Maintenance & Troubleshooting

Learn how each light, sign and circuit works as part of a complete airport lighting system, not just as an isolated diagram.

See. Understand. Apply. Engineer.

Continue Exploring