The dedicated product-level reliability classification connecting the AGL Failure Database with the AGL Product Encyclopedia. Divisions 01–18 describe what failed in the field, system, equipment, installation, environment, testing or maintenance. Division 19 asks whether that failure indicates a product, component, material, design, manufacturing, supplier or lifecycle reliability problem — surfacing repeat product failures, weak components, supplier-quality trends, batch problems and premature-life failures.
Core principle — A single component failure does not automatically constitute a product reliability failure. Division 19 classification should normally be strengthened by repeat occurrence, premature-life evidence, common failure mode, batch correlation, supplier evidence, design analysis or other credible reliability evidence — making the Failure Database technically defensible and feeding directly into the Product Encyclopedia, supplier evaluation, product selection, BOQ specifications and warranty analysis.
A component fails significantly earlier than its expected or specified service life under the applicable operating conditions.
Compare expected life, actual service duration, operating conditions, failure history, batch/supplier and maintenance history.
One of the most important categories for MTBF and product reliability analysis.
An LED module demonstrates a reliability problem beyond an isolated individual failure.
Cross-reference with Division 01 — Lighting Fixture Failures where the actual field failure is LED module failure.
The LED driver demonstrates repeated, premature or systematic reliability problems.
Isolation transformers demonstrate abnormal premature/repeated reliability problems.
Cross-reference with Division 04 — Isolation Transformer Failures.
A connector type or product family demonstrates repeated or systematic reliability problems.
Cross-reference with Division 05 — Cable & Connector Failures.
A cable product/type demonstrates abnormal or repeated failures under its intended operating conditions.
An isolated cable damaged by excavation is normally an installation/mechanical failure, not automatically a product reliability failure. Division 19 should be used when evidence indicates the cable product itself or its material/systematic quality is contributing to repeated failures.
A component within the CCR demonstrates a reliability problem.
Cross-reference with Division 03 — CCR Failures.
A component used within an illuminated airfield sign demonstrates a product-level reliability problem.
Cross-reference with Division 12 — Airfield Sign Failures.
A PAPI/APAPI component demonstrates repeated or systematic reliability problems.
Cross-reference with Division 11 — PAPI/APAPI Failures.
Material used in an AGL product deteriorates during service in a manner that affects product performance, durability or reliability.
Determine whether degradation is environmental, installation-related, maintenance-related, or material/product-related.
A defect originating during manufacturing affects the product's performance or reliability.
A defect introduced during product assembly causes or contributes to failure.
Manufacturing defect is the broader manufacturing-origin category. Assembly defect specifically identifies a defect associated with the assembly process.
A product design characteristic contributes systematically to inadequate reliability, maintainability, performance or durability.
This category should generally require stronger evidence than an isolated failure before being assigned.
Two components or systems are not adequately compatible, resulting in degraded performance or failure.
Evidence indicates that supplier-related product quality is contributing to repeated or abnormal failures.
Do not classify an individual failure as a supplier-quality issue solely because the component came from a particular supplier. There should be evidence of a supplier/product quality relationship.
Failures are concentrated within a particular manufacturing or supply batch.
Extremely useful for identifying:
Product performance progressively deteriorates as the product approaches or progresses through its service life.
Premature failure = failure occurs earlier than expected. Product-life degradation = deterioration associated with ageing/service life.
Trend:
Product reliability, maintainability or service continuity is affected because a component/product is obsolete or no longer adequately supported.
Obsolescence is not necessarily a physical component failure. It is a product lifecycle reliability/maintainability issue that can eventually create operational failures.
Standard product reliability record, failure-chain relationships, investigation workflow, diagnostic matrix, evidence layer and Product Encyclopedia linkage that apply across all 18 Division 19 topics.
Every Division 19 event should ideally be converted into a standard reliability record with the following fields:
Product Identification
Service History
Failure Information
Reliability Analysis
Quality Investigation
Corrective Action & Verification
Division 19 becomes much more valuable when the database captures relationships between reliability findings rather than treating each as isolated.
This distinction is built into the Failure Database — a field failure is logged against its own division; a reliability finding is logged against Division 19 once a pattern is evident.
Field failure: LED module failed. → Division 01
Product-level finding: Multiple LED modules from the same product family fail prematurely. → Division 19
Field failure: Connector has high contact resistance. → Division 05
Product-level finding: Same connector model repeatedly develops high contact resistance under normal conditions. → Division 19
Field failure: Transformer winding failure. → Division 04
Product-level finding: Multiple transformers from the same batch develop winding failures prematurely. → Division 19
Field failure: Cable damaged during excavation. → Division 05 / relevant mechanical category
Product-level finding: Cable insulation repeatedly deteriorates under normal specified installation/service conditions. → Division 19
| Failure | Primary Investigation |
|---|---|
| Component premature failure | Service life/failure history |
| LED module reliability issue | LED failure trend |
| LED driver reliability issue | Driver failure trend |
| Transformer reliability issue | Transformer life/failure trend |
| Connector reliability issue | Connector failure trend |
| Cable reliability issue | Cable failure trend |
| CCR component failure | CCR component history |
| Sign component failure | Sign component history |
| PAPI component failure | PAPI component history |
| Material degradation | Material/service condition |
| Manufacturing defect | Manufacturing origin |
| Assembly defect | Assembly process |
| Design weakness | Product design |
| Component incompatibility | Compatibility |
| Supplier-quality issue | Supplier/product quality |
| Batch-related failure | Batch/failure correlation |
| Product-life degradation | Age/lifecycle trend |
| Obsolescence-related failure | Lifecycle/support status |
A suspected Division 19 failure should follow this sequence:
Compare failure population across same model → same batch → same airport → same installation period → same failure mode.
Division 19 links every reliability finding to the Root Cause Analysis Database. The most relevant RCA categories are:
Every Division 19 finding also receives a severity/impact classification consistent with the rest of the Failure Database:
Critical / Safety-Critical — widespread population affected, safety impact
Major / Operationally Critical — significant repeat-failure rate across fleet
Moderate — reduced reliability, not yet fleet-wide
Minor / Non-Critical — isolated or low-impact trend
Degradation / Latent — emerging or unconfirmed reliability pattern
Visual evidence
Technical evidence
This is where Division 19 becomes especially valuable for the AGL Product Encyclopedia — turning it from a simple product catalogue into a field-reliability knowledge base. Each product entry can eventually contain:
Product Identity & Technical Information
Reliability Information & Field Experience
Reliability Indicators
Recommended database architecture: Product → Manufacturer → Model → Part Number → Batch/Lot → Installation Date → Operating Hours → Field Failure → Failure Mode → Failure Population → Reliability Pattern → Manufacturing/Material/Design/Supplier Analysis → RCA → Corrective Action → Post-Action MTBF → Reliability Trend → Product Encyclopedia Update.
The Troubleshooting Atlas answers “I have a fault now — how do I diagnose and fix it?” The Failure Database answers “this failure happened — what happened, why, what evidence proves it, what was done, and how do we stop it recurring?” Division 19 is the layer that turns individual, isolated failures into fleet-wide product intelligence. It connects directly with Division 01 Lighting Fixture Failures, Division 03 CCR Failures, Division 04 Isolation Transformer Failures, Division 05 Cable & Connector Failures, Division 11 PAPI/APAPI Failures, Division 12 Airfield Sign Failures, Division 21 RCA and Division 23 Reliability Trend Analysis — and feeds directly into the AGL Product Encyclopedia.
Quick answers about product and component reliability failures, as covered in Division 19 of the AGL Failure Database.
Division 19 connects the Failure Database with the AGL Product Encyclopedia. It contains 18 published topics (PCR-01 to PCR-18) covering premature component failure, LED module and driver reliability, transformer, connector and cable reliability, material degradation, manufacturing and assembly defects, design weakness, component incompatibility, supplier-quality and batch-related failure, product-life degradation and obsolescence.
They fall into six groups: Component Reliability (6 topics), Equipment-Specific Component Reliability (3), Material & Manufacturing (3), Design & Compatibility (2), Supplier & Batch Quality (2) and Product Lifecycle (2).
A field failure is logged against its own division, while a reliability finding is logged against Division 19 once a pattern is evident. For example, one failed LED module is a Division 01 field failure, but multiple LED modules from the same product family failing prematurely is a Division 19 product-level finding. The same applies to connectors, transformers from one batch and cables.
The workflow starts by identifying the field failure and asking whether it is isolated or repeated. It then checks operating conditions and product information, compares the failure population, classifies reliability, runs a supplier or manufacturer RCA, applies corrective and preventive action and monitors performance. The population comparison runs from same model to same batch, same airport, same installation period and same failure mode.
Division 19 records relationships between reliability findings. In the premature-component chain, a premature failure leads to repeated same-component failures, an identified reliability trend, a product investigation, a supplier or manufacturer RCA and corrective action. In the LED-driver chain, a driver design or manufacturing issue leads to repeated driver failures and LED fixture outages.
It turns the Product Encyclopedia from a simple product catalogue into a field-reliability knowledge base. Each product entry can eventually hold product identity and technical information alongside reliability information drawn from failure records.
Visual evidence includes product, nameplate, batch and serial photographs, photographs of failed components across the population, and degradation, corrosion or defect comparisons. Technical evidence includes failure-rate and repeat-failure data, manufacturer or supplier investigation reports, test reports, operating-hours records and batch traceability.
Every failure receives a severity classification, plus operational-impact tagging. The classes are Critical / Safety-Critical (immediate operational or safety risk), Major / Operationally Critical (significant availability impact), Moderate (reduced performance, not yet critical), Minor / Non-Critical (limited or no operational effect), and Degradation / Intermittent / Latent (a developing or hidden fault).
The Troubleshooting Atlas answers “I have a fault now — how do I diagnose and fix it?” The Failure Database answers “this failure happened — what happened, why, what evidence proves it, what was done, and how do we stop it recurring?” Kept strictly separate, then linked end to end, the two form an AGL Failure Intelligence Engine rather than a simple fault list.
A single component failure is a repair — a recurring failure across the same batch, manufacturer or design is a reliability problem — real troubleshooting means understanding component construction well enough to tell the difference.
Take that knowledge further with Precision AGL Academy.
Learn how to connect:
Develop structured knowledge across AGL fundamentals, components, electrical systems, testing, photometry, troubleshooting, maintenance and commissioning.
Find the failure. Understand the cause. Build the engineering skill.
Please read before relying on any content on this page or on any record downloaded from it.