The controlled data foundation of the AGL Asset Lifecycle Guide. Division 01 establishes what assets exist and the overall lifecycle strategy; Division 02 establishes how every asset is identified, recorded, maintained, validated and controlled as data — a single authoritative record connecting identity, technical information, location, ownership, condition, criticality, warranty, service life and full history for every managed AGL asset.
The question this division answers — How is every AGL asset identified, recorded, maintained, validated, and controlled as data, so that the register becomes a single trusted source of truth across its lifecycle?
Division 02 stays focused on data structure and control — it does not decide asset strategy (Division 01) and it does not run the detailed criticality/risk methodology (Division 03). It establishes the trusted record that both of those divisions, and every division after them, depend on.
The AGL asset register is the master controlled inventory of all managed AGL assets — a single authoritative record for each asset, not a scattered set of spreadsheets and site notes.
The full Standard Asset Record extends this to include health index, lifecycle cost, repair, refurbishment, upgrade, replacement forecast, disposal status, related documents and related standards — retained in the database even though their detailed management belongs to later divisions.
Asset identification fields establish the basic identity of the equipment so an engineer can identify the exact physical asset from the register alone.
Asset Type: Runway Edge Light · Asset Class: Runway Lighting · System: AGL · Subsystem: Runway Edge Lighting · Description: Runway edge light unit.
The asset tag is the physical identification attached to the equipment or its associated location.
The same identifier should appear in the asset register, equipment label, maintenance record, inspection record, testing record, failure record, replacement record, and relevant drawings.
Asset ID = controlled database identity. Serial Number = manufacturer's unique equipment identity. These should not be treated as the same field.
The manufacturer's serial number provides an additional level of traceability beyond the internal asset ID.
Serial numbers support warranty claims, manufacturer support, failure investigation, product traceability, replacement identification, product recalls, vendor communication and historical analysis. If an asset is replaced, the new serial number should be recorded while preserving the historical record of the previous equipment.
Manufacturer information identifies the original equipment manufacturer and should be linked to the asset rather than maintained only in a separate vendor list.
Model information identifies the specific product configuration — particularly important when an airport has multiple generations of AGL equipment.
Manufacturer: XYZ · Model: AGL-LED-120 · Type: LED Runway Edge Light
The installation date establishes when the physical asset was installed.
Supports asset age calculation, warranty administration, service-life estimation, replacement forecasting, lifecycle-cost analysis and age-based asset planning.
The commissioning date establishes when the asset was formally accepted for operational service. It should be recorded separately from installation — installation date and commissioning date are distinct asset data fields.
| Event | Date |
|---|---|
| Manufacture | 2025-01-10 |
| Delivery | 2025-02-05 |
| Installation | 2025-02-20 |
| Testing | 2025-02-25 |
| Commissioning | 2025-02-28 |
Location data should allow the asset to be physically located without ambiguity — sufficiently precise for maintenance personnel to find the asset.
Runway Edge Light: RWY 09/27 – Station 12+450 – North side
CCR: AGL Substation – CCR Room – Panel CCR-03
Isolation Transformer: Base Can BC-145 – RWY 09 Edge Light Circuit
The asset register should clearly identify who owns and who is responsible for the asset — reviewed whenever organizational responsibility changes.
| Responsibility | Responsible Party |
|---|---|
| Asset Owner | Airport |
| Operations | AGL Operations |
| Maintenance | AGL Maintenance |
| Technical | Engineering |
| Data | Asset Management |
| Vendor Support | Manufacturer |
Asset status identifies the current lifecycle state of the asset.
Status should represent the current lifecycle state, not simply whether equipment is physically present.
Asset condition describes the physical and functional state of the asset.
| Rating | Condition |
|---|---|
| 1 | Excellent |
| 2 | Good |
| 3 | Fair |
| 4 | Poor |
| 5 | Critical |
Detailed condition assessment belongs primarily to Division 15, but the current condition result must be available in the asset register.
Criticality identifies the importance of the asset. The register should store the result; the detailed methodology remains controlled under Division 03.
Criticality: High · Basis: Safety + operational consequence · Review: Annual
Warranty information should allow the organization to determine whether an asset is still covered. This connects to Division 14 — Warranty & Supplier Lifecycle Management.
Warranty: 5 years · Start: 01-04-2026 · End: 31-03-2031 · Status: Active
Expected service life is the planned useful operating life of the asset.
Installation: 2026 · Expected service life: 15 years · Initial replacement forecast: 2041
The forecast should not be treated as a fixed replacement date — condition, reliability, technology and obsolescence may change the decision.
Maintenance history records work performed on the asset.
Failure history provides traceability of asset failures and connects Division 02 with the AGL Failure Database / Reliability Engineering function (Division 11).
Asset: CCR-RWY-001 · Failure ID: FL-2026-014 · Failure: Output current instability · Cause: Control-module fault · Action: Module replaced
Testing history records technical tests performed on the asset.
Test date, test type, test equipment, calibration reference, test result, acceptance criteria, pass/fail, report number, tester, next due date.
Inspection history records the physical and operational inspections performed on an asset — providing evidence of how asset condition has changed over time.
Replacement history records when an asset or major component has been replaced — it should preserve the lifecycle history rather than deleting the old asset record.
Every important asset should be linked to its technical documentation, creating a complete digital asset history.
Asset data must be checked before it becomes trusted lifecycle information.
If Installation Date = 15-03-2026 but Commissioning Date = 10-03-2026, the system should flag the record for review.
Asset data must be controlled so that historical information is not unintentionally lost.
| Revision | Date | Change |
|---|---|---|
| Rev 00 | 01-04-2026 | Initial asset creation |
| Rev 01 | 10-06-2026 | Location corrected |
| Rev 02 | 25-08-2026 | Serial number updated |
The asset register should periodically be audited against the actual airport asset base — formalized as a governance activity under Division 23.
The 24 topics kept exactly as the controlled data structure, each mapped to the primary question it answers.
| No. | Topic | Primary Question |
|---|---|---|
| 01 | AGL Asset Register Structure | What is the master record structure? |
| 02 | Asset Identification Fields | What defines the basic identity of the asset? |
| 03 | Asset Tag Numbers | How is the asset physically identified? |
| 04 | Equipment Serial Numbers | What is the manufacturer's unique identity? |
| 05 | Manufacturer Information | Who made the asset? |
| 06 | Model Information | What product configuration is it? |
| 07 | Installation Date | When was it physically installed? |
| 08 | Commissioning Date | When was it accepted for service? |
| 09 | Location Data | Where exactly is it located? |
| 10 | Asset Ownership | Who owns and is responsible for it? |
| 11 | Asset Status | What lifecycle state is it in? |
| 12 | Asset Condition | What physical/functional state is it in? |
| 13 | Asset Criticality | How important is this asset? |
| 14 | Warranty Information | Is the asset still covered? |
| 15 | Expected Service Life | How long should it serve? |
| 16 | Maintenance History | What work has been performed on it? |
| 17 | Failure History | How has it failed before? |
| 18 | Testing History | What tests has it passed or failed? |
| 19 | Inspection History | How has its condition changed over time? |
| 20 | Replacement History | What was replaced, when and why? |
| 21 | Asset-Document Linkage | What documentation is connected to it? |
| 22 | Asset Data Validation | Is the data trustworthy? |
| 23 | Asset Data Revision Control | How is data change tracked? |
| 24 | Asset Register Audit | Does the register match reality? |
The mandatory outputs of Division 02.
Division 02 should remain the controlled data foundation. It defines how every asset is identified, recorded, maintained, validated and controlled as data — not what the overall strategy is (Division 01), and not the detailed criticality/risk methodology (Division 03).
One physical asset = one controlled asset identity = one continuously updated lifecycle record. The asset register becomes the single source of truth connecting the asset to its installation, commissioning, operation, maintenance, inspection, testing, failure, condition, warranty, replacement and eventual disposal.
This is why the framework places Division 02 immediately after Division 01: Division 01 decides what the asset strategy is; Division 02 establishes the trusted data structure needed to execute that strategy.
Quick answers about Asset Register & Data Management in the AGL Asset Lifecycle Guide.
Division 02 is the controlled data foundation of the asset lifecycle. It covers 24 topics on the asset register structure, identification, tagging, serial numbers, dates, location, ownership, status, condition, criticality, warranty, service life, maintenance/failure/testing/inspection/replacement history, document linkage, data validation, revision control and register audit.
The AGL asset register is the master controlled inventory of all managed AGL assets: a single authoritative record for each asset, not a scattered set of spreadsheets. It brings together asset identification, technical information, location, ownership and responsibility, status, condition, criticality, warranty, service life and the maintenance, failure, testing, inspection and replacement history.
Identification fields include the asset ID, type, description, class, system and subsystem, so an engineer can identify the exact physical asset from the register alone. The physical asset tag should be unique, legible, durable and permanently associated with the asset. The manufacturer's serial number adds traceability beyond the internal asset ID.
The installation date establishes when the physical asset was installed, while the commissioning date establishes when it was formally accepted for operational service. They are different lifecycle events, so the register records them as separate fields.
Location data should let maintenance personnel find the asset without ambiguity. It can include the airport, runway, taxiway or apron, approach area or circuit, station or chainage, and a grid reference or coordinates.
The register keeps maintenance, failure, testing, inspection and replacement history for each asset. Replacement history should preserve the lifecycle history rather than deleting the old asset record, recording the previous asset ID, replacement date and reason, and the old and new manufacturer, model and serial number.
Data is validated before it becomes trusted lifecycle information, for example by checking that the asset ID exists and is unique and that type, manufacturer, model and location are valid. Revision control records the revision number and date, the changed field with its previous and new value, the reason, and who changed and approved it. The register is also audited periodically against the physical asset base.
The register stores the criticality result, such as class, score and review date, while the detailed methodology stays under Division 03. Warranty fields such as provider, start date, end date and duration let the organization tell whether an asset is still covered, and connect to Division 14.
Effective AGL asset management starts with a register that captures the right data, accurately and consistently.
Learn how asset identification, tagging, serial numbers, location data, ownership, condition and history records connect across the complete AGL asset lifecycle.
Turn technical reference knowledge into a deeper understanding of how AGL assets are planned, managed, operated and sustained throughout their lifecycle.
Record better. Structure the data. Build technical capability.
Build structured knowledge in:
Please read before relying on any content on this page or on any record downloaded from it.