The institutional learning and knowledge-retention division of the AGL Innovation Framework. Its purpose is not simply to collect success stories — it captures what was attempted, why it was attempted, how it was tested, what actually happened, what failed, what was learned, and how that learning should influence future AGL projects. Divisions 18–23 continuously generate prototypes, PoCs, pilots, technology assessments, research and new ideas; without this division, valuable engineering knowledge disappears when a project closes or personnel change.
Core principle — Every significant innovation project should leave behind reusable engineering knowledge. Failure should become organizational knowledge rather than repeated organizational error.
Division 24 closes the loop on the entire innovation pipeline. Every prototype, PoC, pilot, successful technology, failed experiment and commercialization attempt flowing out of Divisions 18–23 is captured here as a structured case study and fed back into engineering standards, SOPs, training and future product development.
Documents real or pilot implementations involving intelligent AGL systems — the intersection of connected hardware, control logic and operational lighting performance.
Documents applications of AI within AGL, with a mandatory maturity check so an experimental system is never mistaken for a proven operational one.
Every AI case study must place the work on this chain, so it is never overstated:
Documents connected AGL assets and sensor systems, tracing data from the fixture through to a maintenance action.
Captures projects involving digital representations of AGL assets or systems, from a single fixture up to complete airport electrical infrastructure.
Documents robotic or autonomous inspection initiatives applied to AGL assets.
Documents innovations designed to improve environmental performance, compared against a reliable baseline where one exists.
Documents development of new or significantly improved AGL products.
Captures automation of engineering, testing, maintenance or documentation activities.
Documents attempts to move from reactive or preventive maintenance toward predictive maintenance.
Every significant prototype should have a documented engineering history, connecting directly to Division 18.
This creates an engineering development trail rather than a single snapshot.
Connects directly to Division 19 (PoC & Pilot) and formalizes every proof-of-concept as a repeatable, comparable record.
Documents why an emerging technology was adopted, building a valuable technology-selection knowledge base.
One of the most important topics in Division 24. Innovation management should not record only successful projects — a failed innovation can provide extremely valuable engineering knowledge.
Failure should become organizational knowledge rather than repeated organizational error.
Every pilot should conclude with a formal lessons-learned review before it is closed out.
Documents the complete journey from concept to commercially usable technology, particularly important for connecting Divisions 18, 19, 20 and 21.
Captures lessons related to engineering performance so the same design errors are not repeated project after project.
What technical knowledge should the engineering team carry into the next project?
Safety lessons should be documented separately from technical lessons, given their outsized importance to airside operations.
No innovation should be considered successful purely because it improves performance if it introduces unacceptable safety risk.
Captures what happened during actual deployment, separate from the design or technology decisions themselves.
Captures actual financial learning where reliable data is available, comparing what was estimated to what was actually spent or saved.
Did the innovation actually deliver the expected economic value?
Connects Division 24 with the broader reliability framework, capturing how innovations actually performed against expectations.
Technical success does not guarantee user acceptance — this topic captures feedback from everyone who has to live with the innovation.
Captures lessons from moving an innovation toward the market, connecting Division 24 to Division 21 (IP & Commercialization).
Why did the technology succeed or fail commercially?
Every major case study should follow this master template, moving from identification through problem, innovation, implementation, results, lessons, final decision and knowledge transfer.
Each case study receives a unique ID under the AGL Innovation Case Study Library, organized across fifteen categories mirroring Divisions 02–20.
A central AGL Innovation Lessons-Learned Register underpins the whole division. Each lesson is classified by type and rated by severity so management can focus on what matters most.
The most important feature of Division 24 is closing the loop: lessons don't just get filed, they flow back into SOPs, design standards, training and products, which in turn shape the next innovation project.
Recommended metrics across case studies, lessons and organizational learning to track whether the division is functioning as a continuous-improvement engine rather than a static archive.
| Metric | Status |
|---|---|
| Total Case Studies | — |
| Successful Innovation Case Studies | — |
| Failed Innovation Case Studies | — |
| PoC / Pilot Case Studies | — |
| Lessons Identified / Critical / Major | — |
| Lessons Implemented / Pending / Closed | — |
| SOPs, Design Standards & Training Updated | — |
| Products Improved / Future Projects Influenced | — |
| Repeat Failures Prevented | — |
| Innovation Cycle-Time Reduction | — |
Division 24 is the institutional memory of the entire AGL Innovation Programme. It does not compete with Divisions 18–23 — it receives their output. Prototype history stays in Division 18, PoC and pilot mechanics stay in Division 19, technology evaluation in Division 20, and IP/commercialization in Division 21. Division 24's job is to turn all of that raw activity into structured, reusable, classified knowledge.
Its defining feature is the closed loop: a case study is not complete until its lessons have been pushed into an SOP update, a design-standard update, a training update, or a product update. Every case study — successful, failed or inconclusive — should answer one question: "What should the next engineer do differently because we already learned this?"
Especially for failed innovations, case studies should go through technical, safety, commercial, confidentiality and IP review before publication, since sensitive project information needs careful handling even when the failure itself is valuable to record.
Governing philosophy: "Innovate once, learn permanently, and never repeat the same engineering mistake."
Quick answers about Innovation Case Studies & Lessons Learned in the AGL Innovation Hub.
Division 24 is the institutional learning and knowledge-retention division of the AGL Innovation Framework. Its purpose is not simply to collect success stories — it captures what was attempted, why it was attempted, how it was tested, what actually happened, what failed, what was learned, and how that learning should influence future AGL projects. It covers 22 topics (CSL-01 to CSL-22).
The 22 topics are Smart AGL Case Study, AI AGL Case Study, IoT AGL Case Study, Digital-Twin Case Study, Robotics Case Study, Sustainable AGL Case Study, Product Innovation Case Study, Automation Case Study, Predictive-Maintenance Case Study, Prototype Case Study, PoC Case Study, Technology-Adoption Case Study, Failed Innovation Case Study, Lessons From Pilot Projects, Innovation-to-Production Case Study, Technical Lessons, Safety Lessons, Implementation Lessons, Cost Lessons, Reliability Lessons, User Lessons and Commercialization Lessons.
Division 24 closes the loop on the entire innovation pipeline. Every prototype, PoC, pilot, successful technology, failed experiment and commercialization attempt flowing out of Divisions 18–23 is captured here as a structured case study and fed back into engineering standards, SOPs, training and future product development.
Every major case study should follow this master template, moving from identification through problem, innovation, implementation, results, lessons, final decision and knowledge transfer. It includes A. Identification — ID, title, category, project/PoC ID, date, team, contributors, B. Problem — original problem, existing condition, engineering gap, business impact, C. Innovation — proposed solution, technology, objective, expected benefits, D. Implementation — design, prototype, testing, pilot, deployment, E. Results — technical, safety, reliability, energy, cost, user performance, F. Lessons — what worked, what failed, unexpected findings, six lesson types, G. Final Decision — adopt, modify, scale, repeat, hold, stop and H. Knowledge Transfer — SOP, design standard, checklist, training, product, research.
Each case study receives a unique ID under the AGL Innovation Case Study Library, organized across fifteen categories mirroring Divisions 02–20. CS-AGL-AI-001 CS-AGL-IOT-001 CS-AGL-PHOT-001 CS-AGL-POC-001 CS-AGL-FAIL-001 CS-AGL-DT-001 CS-AGL-ROB-001 CS-AGL-SUS-001 CS-AGL-PROD-001 CS-AGL-AUTO-001 CS-AGL-PM-001 CS-AGL-PROTO-001 CS-AGL-TECH-001 CS-AGL-PILOT-001 CS-AGL-I2P-001.
A central AGL Innovation Lessons-Learned Register underpins the whole division. Each lesson is classified by type and rated by severity so management can focus on what matters most. It includes Technical — engineering knowledge, Safety — safety-related learning, Operational — workflow learning, Maintenance — maintenance learning, Financial — cost/value learning, Reliability — failure and lifecycle learning, Human — training/usability/competency learning, Commercial — market and commercialization learning, Strategic — lessons affecting future innovation strategy, L1 — Critical: immediate safety, reliability or major engineering implication, L2 — Major: significant impact on future projects, L3 — Moderate: useful improvement opportunity and L4 — Minor: small optimization.
The most important feature of Division 24 is closing the loop: lessons don't just get filed, they flow back into SOPs, design standards, training and products, which in turn shape the next innovation project. The steps or layers are: Innovation Project → Prototype → PoC → Pilot → Results; Case Study; Lessons Identified; Lessons Register; Engineering Review; SOP / Design / Training / Product Update; Future Project — Better Innovation.
Recommended metrics across case studies, lessons and organizational learning to track whether the division is functioning as a continuous-improvement engine rather than a static archive. Metric — Status; Total Case Studies; Successful Innovation Case Studies; Failed Innovation Case Studies; PoC / Pilot Case Studies; Lessons Identified / Critical / Major; Lessons Implemented / Pending / Closed; SOPs, Design Standards & Training Updated; Products Improved / Future Projects Influenced; Repeat Failures Prevented; Innovation Cycle-Time Reduction; Most Important Design Principle; Division 24 is the institutional memory of the entire AGL Innovation Programme. It does not compete with Divisions 18–23 — it receives their output. Prototype history stays in Division 18, PoC and pilot mechanics stay in Division 19, technology evaluation in Division 20, and IP/commercialization in Division 21. Division 24's job is to turn all of that raw activity into structured, reusable, classified knowledge; Its defining feature is the closed loop: a case study is not complete until its lessons have been pushed into an SOP update, a design-standard update, a training update, or a product update. Every case study — successful, failed or inconclusive — should answer one question: "What should the next engineer do differently because we already learned this?".
Documents real or pilot implementations involving intelligent AGL systems — the intersection of connected hardware, control logic and operational lighting performance. Study Areas: Intelligent runway lighting, Intelligent taxiway lighting, Smart intensity control, Adaptive lighting, Connected fixtures, Smart circuit monitoring, Remote monitoring, Self-diagnostic fixtures, Energy optimization and Intelligent fault indication.
Documents why an emerging technology was adopted, building a valuable technology-selection knowledge base. Questions to Answer: What problem did it solve?, What alternatives were considered?, Why was this technology selected?, What was its TRL?, What was its reliability?, What was the lifecycle cost?, What operational risks existed?, What training was required?, What maintenance changes were required? and What was the final outcome?.
Captures lessons from moving an innovation toward the market, connecting Division 24 to Division 21 (IP & Commercialization). Areas: Market demand, Customer requirements, Product cost, Manufacturing feasibility, Supply chain, Competition, Certification, Standards, IP and Sales model.
Innovation case studies and lessons learned start with understanding what worked, what failed and why, across real AGL innovation programs. The next step is building the technical knowledge required to evaluate, apply and avoid repeating these lessons with confidence.
Develop structured knowledge across:
Understand how engineering problems become opportunities, technologies, concepts, validation activities and measurable improvements.
Understand today's AGL. Build tomorrow's capability.
Please read before relying on any content on this page or on any record downloaded from it.