What is requirement mapping in AGL?
Every requirement should be traceable from the document it came from to the test and record that prove it was met.
Requirement mapping links each requirement to its source document and clause, then to the project specification, the test or inspection that verifies it, and the evidence that shows it was done. It turns a pile of standards into a checklist that can be followed and audited.
Without it, requirements can be missed, duplicated or tested to the wrong edition. With it, anyone can see why a test exists and which named governing standard it answers to, whether that is ICAO, FAA, IEC or an Indian Standard.
- List the requirement. Write it as one clear, testable statement.
- Find the source. Note the document, edition and clause it comes from.
- Carry it into the specification. Give it a clause in the project documents.
- Assign verification. Decide the test or inspection that proves it.
- Record the evidence. Keep the report or record against that requirement.
Requirements float free: gaps, duplicate tests, mixed editions and no clear owner.
Each requirement has a source, a spec clause, a test and a record, so it can be traced both ways.
Frequently Asked Questions
Q1What is requirement mapping?
It is tracing each requirement back to where it comes from and forward to how it is proved. For every requirement you note the source document, edition and clause, the project specification clause that carries it, the test or inspection that verifies it, and the record that shows it was done.
Q2Why record the edition and clause?
Documents change, and the figures or test methods in one edition may differ from another. Quoting the edition and clause lets anyone find the exact wording later and tells you which version the supplier worked to.
Q3What if two documents give different requirements?
Do not pick the easier one silently. Check which document the contract names as governing, apply that one, and record the decision. If the contract is unclear, raise it with the specifier before ordering or testing.
Q4How is mapping different from a compliance matrix?
Mapping is the tracing work: requirement to source to test to evidence. A compliance matrix is the table where the result is usually recorded, showing whether each requirement is met, not met or covered by an agreed deviation.
Q5Who needs requirement mapping?
Anyone who has to show that AGL work meets its specification, such as designers writing specifications, suppliers preparing test evidence, and engineers commissioning or accepting a system. The depth depends on the contract and regulator.
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:
Learn how each light, sign and circuit works as part of a complete airport lighting system, not just as an isolated diagram.