Division 25 of 25 · Final Division · Intelligence Layer

Innovation Database & Project Intelligence

The master database and intelligence layer of the entire AGL Innovation Framework — the same role the AGL Failure Database plays for failures, RCA and reliability. Division 25 does not just store project information: it connects every innovation project, prototype, PoC, pilot, patent, research paper, product, asset, failure record, standard and engineering tool into one interconnected knowledge system, so that at any moment the framework can answer what is being innovated, why, how mature it is, what it cost, what it achieved and what should happen next.

38 / 38
Record Fields Scoped
17 + 21
Standard Record + Intelligence Fields
Intelligence
Layer · Database & Governance
Rev 0
Initial Issue

The question this division answers — How do we turn every AGL innovation project into a single authoritative, interconnected record, so the framework becomes actionable innovation intelligence rather than a topic library?

Division 25's Role in the Innovation Hub

Divisions 01–17 generate innovation opportunities and technology domains. Division 18 builds prototypes. Division 19 runs PoCs and pilots. Division 20 evaluates technology. Division 21 handles IP and commercialization. Division 22 covers research and collaboration. Division 23 tracks technology watch and future trends. Division 24 captures case studies and lessons learned. Division 25 captures, links, analyzes and governs all of it.

18–20 — Prototype, PoC & Pilot, Technology Evaluation
21–22 — IP & Commercialization, Research & Collaboration
23–24 — Technology Watch, Case Studies & Lessons
25 — Innovation Database & Project Intelligence

A. Standard Innovation Project Record

17 of 17 fields scoped · REC-01 → 17
REC-01Project ID
Purpose

Every innovation project receives a unique, permanent Innovation Project ID that is never reused.

Structure
INNInitiation YearCategory CodeSequential Number
Example
INN-2026-AI-001
REC-02Innovation Title
Purpose

A short, technically meaningful title that immediately communicates the engineering purpose of the project.

Example

AI-Based Automated Runway Fixture Defect Detection — not a vague title such as "AI Project."

REC-03Problem Statement
Purpose

Describes the engineering problem being solved.

Should Answer
  • What is wrong?
  • Where does it occur?
  • How frequently?
  • What is the operational consequence?
  • What is the current limitation?
  • Why does the problem require innovation?
REC-04Existing Solution
Purpose

Documents the current method before innovation, establishing the baseline against which innovation performance is later measured.

Includes
  • Existing technology
  • Existing process
  • Existing equipment
  • Current performance
  • Current limitations
  • Current cost
  • Current maintenance requirement
REC-05Proposed Innovation
Purpose

Describes the proposed technology or methodology.

Includes
  • Technology concept
  • Architecture
  • Major components
  • Operating principle
  • Intended improvement
  • Integration requirements
REC-06Expected Benefits
Purpose

Benefits should be measurable wherever possible, across five categories.

Categories
  • Technical — better performance, improved accuracy, improved reliability
  • Operational — reduced inspection time, faster fault identification, improved availability
  • Financial — reduced maintenance, energy and lifecycle cost
  • Safety — reduced personnel exposure, faster critical-defect identification
  • Sustainability — lower energy and material consumption, longer asset life
REC-07Technical Feasibility
Assess
  • Technology availability
  • Engineering feasibility
  • Integration feasibility
  • Environmental suitability
  • Testing feasibility
  • Manufacturing feasibility
  • Maintenance feasibility
  • Safety feasibility
Rating

Low / Medium / High, or a numerical score.

REC-08Implementation Roadmap
Purpose

Documents the complete development path from problem to deployment.

Path
ProblemConceptFeasibilityResearchPrototypeLab TestingPoCPilotTech. EvaluationProduct DevelopmentCommercializationDeployment
REC-09Risks & Limitations
Purpose

Every innovation record explicitly documents its limitations across eleven risk categories.

Categories

Technical · Safety · Operational · Financial · Reliability · Environmental · Cybersecurity · Supply-chain · Regulatory · User-acceptance · Commercial.

Also Records

Known limitations · Unknowns · Dependencies · Assumptions.

REC-10Pilot Validation Plan
Purpose

Defines how the innovation will be proven in the field, linking directly to Division 19 — Proof-of-Concept & Pilot Projects.

Includes
  • Pilot objective
  • Pilot site
  • Equipment
  • Baseline condition
  • Test methodology
  • Duration
  • Test parameters
  • Acceptance criteria
  • Safety requirements
  • Data collection
  • Performance evaluation
  • Final decision
REC-11Estimated Cost
Records

Research · Engineering · Prototype · Testing · Pilot · Installation · Software · Hardware · Training · Maintenance cost — distinguishing CAPEX and OPEX where possible.

REC-12Success Metrics
Purpose

One of the most important fields — every innovation needs measurable success criteria.

Examples

Reliability — MTBF improvement · Maintenance — maintenance-hours reduction · Inspection — detection accuracy · Photometry — measurement accuracy · Energy — kWh reduction · Cost — lifecycle-cost reduction · Safety — personnel-exposure reduction.

REC-13Related Standards
Records

Applicable standards — ICAO, FAA, DGCA, IEC, IS and other technical references — with standard, clause/section, applicability and compliance status.

REC-14Related Products
Links To

Runway fixture · Taxiway fixture · CCR · Isolation transformer · Connector · Cable · PAPI · Sign · ALCMS · Photometry equipment.

REC-15Related Topics
Purpose

Connects the project to the wider Innovation Framework and enables topic-based intelligence searches.

Example — AI

Predictive Maintenance · Computer Vision · Smart AGL · Automated Inspection.

REC-16References
Records

Research papers · Technical reports · Manufacturer documentation · Test reports · Standards · Patents · Airport reports · Engineering studies · Internal technical documents.

REC-17Revision History
Purpose

Every innovation record maintains a controlled revision history and preserves historical changes rather than overwriting important project history.

Structure
RevisionDateChangePrepared ByReviewed By
R0—Initial record——
R1—Technical update——
R2—Pilot results——

B. Database Intelligence Fields

21 of 21 fields scoped · INT-01 → 21

These fields transform the record from a simple project register into an Innovation Intelligence Database by classifying, scoring and cross-linking every project.

INT-01Innovation Category
Purpose

Classifies every project against a shared category list, with a Primary Category and optional Secondary Categories.

Categories

Smart AGL · AI · IoT · Digital Engineering · Robotics · Sustainability · Product Innovation · Engineering Innovation · Emerging Technology · Automation · Photometry · Predictive Maintenance · Safety & Reliability · Materials · Manufacturing · Control & Monitoring.

INT-02Technology Maturity
Classification
ConceptResearchExperimentalPrototypePoCPilotValidatedCommercialOperational
INT-03Technology Readiness Level (TRL)
TRL Scale
TRLGeneral Stage
1Basic principles
2Technology concept
3Experimental proof
4Laboratory validation
5Relevant-environment validation
6Demonstration
7Operational prototype
8Qualified system
9Proven operational system
Records

Both Current TRL and Target TRL.

INT-04Safety Impact
Classification

Positive — improves safety · Neutral — no significant impact · Negative/Potential Risk — introduces concerns requiring mitigation.

Fields

Safety impact · Safety risk · Mitigation · Safety validation status.

INT-05Operational Impact
Purpose

Assesses the effect on airport/AGL operations.

Categories

Positive · Neutral · Negative · Unknown.

Measured Where Possible

Downtime · Inspection time · Maintenance time · Availability · Operational disruption · Human intervention.

INT-06Sustainability Impact
Captures

Energy impact · Carbon impact · Material impact · Waste impact · Equipment-life impact · Maintenance impact · Lifecycle impact.

Rating

High / Medium / Low / Neutral.

INT-07Reliability Impact
Assesses Effect On

MTBF · MTTR · Availability · Failure frequency · Component life · System resilience.

Records Both

Expected reliability improvement (e.g. +20%) and, later, Validated improvement (e.g. +14%) — the distinction between the two is important.

INT-08Estimated ROI
Structure
InvestmentAnnual Benefit
Potential Benefits

Energy savings · Labour savings · Maintenance savings · Downtime reduction · Asset-life extension · Reduced failures.

Also Records

Estimated Payback Period and, after implementation, Actual Payback Period.

INT-09Development Stage
Purpose

Shows where the project currently sits, from idea through to closure.

Values

Idea · Screening · Feasibility · Research · Design · Prototype · Laboratory Test · PoC · Pilot · Validation · Product Development · Commercialization · Deployment · Operational · Closed · Abandoned.

INT-10Prototype Status
Values

Not Started · Planned · In Design · Fabrication · Testing · Passed · Failed · Modified · Completed.

Also Records
Prototype V3.2
INT-11PoC Status
Values

Not Planned · Planned · In Preparation · Active · Completed · Passed · Failed · Repeated · Scaled · Closed.

Link

Links directly to the PoC ID in Division 19.

INT-12Pilot Status
Values

Not Planned · Site Selection · Planned · Ready · Active · Completed · Validated · Failed · Scaled · Closed.

INT-13Commercialization Status
Values

Not Applicable · Not Assessed · Under Assessment · Commercial Potential · Business Case · Product Development · Market Validation · Commercial Launch · Commercialized · Licensed · Technology Transfer · Abandoned.

INT-14Patent Status
Link

Connects directly with Division 21.

Values

Not Assessed · Idea Identified · Patent Screening · Patentability Assessment · Patent Concept · Filing Planned · Filed · Granted · Rejected · Licensed · Abandoned.

Link Field
PAT-2026-037
INT-15Collaboration Status
Link

Connects directly with Division 22.

Values

Internal · University · Research Institute · Airport · Manufacturer · Technology Company · Startup · Multi-Partner · Joint Venture.

Additional Fields

Partner · Agreement status · Collaboration role · IP arrangement.

INT-16Related Failure Record
Purpose

A powerful database connection — innovation can originate from an actual AGL failure. Links directly to the AGL Failure Database.

Chain
Failure IDRoot CauseInnovation ProjectPrototypePoCNew Product
INT-17Related Asset
Purpose

Links the innovation to the actual asset affected — runway edge light, taxiway centreline light, PAPI, CCR, isolation transformer, primary cable, connector, sign, ALCMS, approach-lighting system.

Linkage Fields

Asset ID · Asset Type · Location · System.

INT-18Related Product
Link

Links to the AGL Product Encyclopedia / Product Library, creating a direct connection between Innovation Intelligence and Product Intelligence.

Example
InnovationNew LED Fixture ConceptProduct IDProduct FamilyManufacturerDatasheet / Test Report
INT-19Related Research Paper
Fields

Paper ID · Title · Authors · Institution · Publication · Date · Relevance · Key findings.

INT-20Related Design Method
Purpose

Links the innovation to engineering methodologies, allowing innovation knowledge to flow back into engineering practice.

Examples

Reliability-based design · Lifecycle design · Automated circuit design · Photometric modelling · Risk-based design · Optimization · Digital engineering.

INT-21Related Calculator / Tool
Purpose

Especially valuable for the engineering knowledge platform — links innovations to practical engineering tools.

Examples

Voltage-drop calculator · Cable-sizing calculator · Transformer-selection calculator · CCR-selection tool · Photometry analysis tool · Reliability calculator · Energy calculator · Lifecycle-cost calculator · ROI calculator · Risk calculator.

Chain
InnovationEngineering MethodCalculatorPractical Engineering Application
No fields match your search. Try a different term.

Innovation Database Relationships

The real power of Division 25 comes from the relationships between records, not the records in isolation. A single Innovation Project connects outward to a Failure Record, an Asset Record and a Product Record, and forward through Research, Prototype and PoC into a Pilot, a Technology Evaluation, and finally a Patent, a Product or a Commercial outcome — all feeding back into Lessons Learned and Future Innovation.

STAGE 1
Origin Links
Failure Record · Asset Record · Product Record
STAGE 2
Innovation Project
The master record — problem, solution, feasibility, roadmap, risk
STAGE 3
Development
Research → Prototype → PoC → Pilot
STAGE 4
Technology Evaluation
TRL, validated performance, ROI, safety/operational/sustainability/reliability impact
STAGE 5
Outcome Links
Patent · Product · Commercial launch
STAGE 6
Lessons Learned → Future Innovation
Closes the loop back into Divisions 01–17

Innovation Portfolio Matrix

A dashboard-level view classifying every active project on Innovation Value against Technology Maturity, to help decide where to invest.

Explore

Low TRL, low current value — early-stage ideas worth watching, not yet worth heavy investment.

Pilot

Low TRL, high value — promising concepts that justify moving into prototype/PoC/pilot.

Adopt

High TRL, low current value — mature but marginal; candidates for narrow or conditional adoption.

Scale

High TRL, high value — validated technologies ready for broader deployment and commercialization.

Low TRLHigh TRL

Stage-Gate Integration

The database supports eight formal innovation gates, with every gate decision recorded in the project history.

G0
Idea — is the problem worth investigating?
G1
Feasibility — is the concept technically feasible?
G2
Prototype — can a working solution be built?
G3
PoC — does it work in a controlled environment?
G4
Pilot — does it work operationally?
G5
Adoption — safe, reliable, economically justified?
G6
Commercialization — can it become a product?
G7
Scale — can it be deployed more broadly?

Recommended Master Registers

Division 25 ultimately contains twenty linked databases/registers built on top of the field set above.

Innovation Project Master
Innovation Category Register
Technology Maturity Register
TRL Register
Innovation Risk Register
Prototype Register
PoC Register
Pilot Register
Innovation Cost Register
Innovation KPI Register
Patent Link Register
Collaboration Link Register
Failure Link Register
Asset Link Register
Product Link Register
Research Paper Link Register
Design Method Register
Engineering Tool/Calculator Register
Innovation Lessons Register
Innovation Revision Register

Dashboard & KPI Intelligence

Six dashboard categories keep the innovation programme measurable at portfolio, technology, development, IP, commercial and impact level.

Portfolio

  • Total innovation projects
  • Active / completed / abandoned
  • Projects by category
  • Projects by airport/project

Technology

  • Average TRL
  • Technologies at TRL 1–3
  • Technologies at TRL 4–6
  • Technologies at TRL 7–9
  • Ready for adoption

Development

  • Concepts
  • Research projects
  • Prototypes
  • PoCs
  • Pilots
  • Validated technologies

IP

  • Patent ideas
  • Patentability assessments
  • Patent filings
  • Granted patents
  • Licensed technologies

Impact

  • Energy savings
  • Reliability improvement
  • Maintenance reduction
  • Cost savings
  • Safety improvement

Each active project can also carry an Innovation Health Score (e.g. 82/100 — Healthy / Attention Required / At Risk / Critical) built from technical feasibility, TRL progression, schedule and cost performance, safety, reliability, PoC/pilot progress, and commercial and IP potential — plus lifecycle tracking of how long each project takes to move Idea → Feasibility → Prototype → PoC → Pilot → Commercialization, to surface bottlenecks in the Innovation Cycle Time.

Database Governance

Clear ownership keeps the master database trustworthy as it grows.

Innovation Database Owner — data quality, registration, classification, record integrity, relationships, reporting
Project Owner — technical updates, milestones, results, risks, lessons
Technical Reviewer — technical accuracy, feasibility, validation
Innovation Governance Committee — stage-gate decisions, priority, investment, continuation/termination

Division 25 — Integration With the Innovation Hub

Division 25 is the data backbone connecting every preceding division into one intelligence platform.

Divisions 01–17 — generate the innovation opportunities and technology domains that seed new project records
Division 18 — Prototype: supplies Prototype Status and Prototype Version
Division 19 — PoC & Pilot: supplies PoC Status, Pilot Status and the Pilot Validation Plan
Division 20 — Technology Evaluation: supplies TRL, validated performance and impact data
Division 21 — IP & Commercialization: supplies Patent Status and Commercialization Status
Division 22 — Research & Collaboration: supplies Collaboration Status and related research papers
Division 23 — Technology Watch: feeds emerging-technology candidates into new project records
Division 24 — Case Studies & Lessons Learned: closes the loop back into Lessons Learned and Final Decision

Ultimate Vision for Division 25

Division 25 should not be treated as an Excel register alone. The long-term objective is to grow it into an AGL Innovation Intelligence Platform:

Problem → Failure → Asset
Technology → Innovation Project → Research
Prototype → PoC → Pilot → Testing
TRL → Benchmark → Patent
Product → Commercialization
Lessons Learned → Future Innovation

Every other division builds innovation. Division 25 remembers, connects and governs it.

That single source of truth is what lets the framework answer, at any time: what are we innovating, why, what technology is involved, how mature is it, where is it being tested, what did it achieve, what did it cost, what risks exist, who is collaborating, is there patent potential, which asset/product/failure does it relate to, what did we learn — and should we continue, stop, adopt, scale or commercialize it. That is what turns the 25-division Innovation Hub from a topic library into a genuine AGL Innovation Management & Intelligence System.

Frequently Asked Questions

Quick answers about Innovation Database & Project Intelligence in the AGL Innovation Hub.

Q1What is Division 25 — Innovation Database & Project Intelligence in the AGL Innovation Hub?

Division 25 is the master database and intelligence layer of the entire AGL Innovation Framework — the same role the AGL Failure Database plays for failures, RCA and reliability. It covers 17 topics (REC-01 to REC-17).

Q2What question does Division 25 answer?

How do we turn every AGL innovation project into a single authoritative, interconnected record, so the framework becomes actionable innovation intelligence rather than a topic library?

Q3Which topics does Division 25 cover?

Division 25 covers 38 fields in two groups. The 17 Standard Innovation Project Record fields are Project ID, Innovation Title, Problem Statement, Existing Solution, Proposed Innovation, Expected Benefits, Technical Feasibility, Implementation Roadmap, Risks & Limitations, Pilot Validation Plan, Estimated Cost, Success Metrics, Related Standards, Related Products, Related Topics, References and Revision History. The 21 Database Intelligence Fields are Innovation Category, Technology Maturity, Technology Readiness Level (TRL), Safety Impact, Operational Impact, Sustainability Impact, Reliability Impact, Estimated ROI, Development Stage, Prototype Status, PoC Status, Pilot Status, Commercialization Status, Patent Status, Collaboration Status, Related Failure Record, Related Asset, Related Product, Related Research Paper, Related Design Method and Related Calculator / Tool.

Q4Where does Division 25 sit in the Innovation Hub?

Divisions 01–17 generate innovation opportunities and technology domains. Division 18 builds prototypes. Division 19 runs PoCs and pilots. Division 20 evaluates technology. Division 21 handles IP and commercialization. Division 22 covers research and collaboration. Division 23 tracks technology watch and future trends. Division 24 captures case studies and lessons learned. Division 25 captures, links, analyzes and governs all of it.

Q5What is “Innovation Database Relationships” in Division 25?

The real power of Division 25 comes from the relationships between records, not the records in isolation. A single Innovation Project connects outward to a Failure Record, an Asset Record and a Product Record, and forward through Research, Prototype and PoC into a Pilot, a Technology Evaluation, and finally a Patent, a Product or a Commercial outcome — all feeding back into Lessons Learned and Future Innovation. STAGE 1 Origin Links; Failure Record · Asset Record · Product Record; STAGE 2 Innovation Project; The master record — problem, solution, feasibility, roadmap, risk; STAGE 3 Development; Research → Prototype → PoC → Pilot; STAGE 4 Technology Evaluation; TRL, validated performance, ROI, safety/operational/sustainability/reliability impact; STAGE 5 Outcome Links; Patent · Product · Commercial launch; STAGE 6 Lessons Learned → Future Innovation; Closes the loop back into Divisions 01–17.

Q6What is “Innovation Portfolio Matrix” in Division 25?

A dashboard-level view classifying every active project on Innovation Value against Technology Maturity, to help decide where to invest. Explore; Low TRL, low current value — early-stage ideas worth watching, not yet worth heavy investment; Pilot; Low TRL, high value — promising concepts that justify moving into prototype/PoC/pilot; Adopt; High TRL, low current value — mature but marginal; candidates for narrow or conditional adoption; Scale; High TRL, high value — validated technologies ready for broader deployment and commercialization; Low TRL High TRL.

Q7How does Division 25 integrate with the rest of the AGL Innovation Hub?

The database supports eight formal innovation gates, with every gate decision recorded in the project history. G0; Idea — is the problem worth investigating?; G1; Feasibility — is the concept technically feasible?; G2; Prototype — can a working solution be built?; G3; PoC — does it work in a controlled environment?; G4; Pilot — does it work operationally?; G5; Adoption — safe, reliable, economically justified?; G6; Commercialization — can it become a product?; G7; Scale — can it be deployed more broadly?.

Q8Which registers does Division 25 recommend maintaining?

Division 25 ultimately contains twenty linked databases/registers built on top of the field set above. It includes Innovation Project Master, Innovation Category Register, Technology Maturity Register, TRL Register, Innovation Risk Register, Prototype Register, PoC Register, Pilot Register, Innovation Cost Register, Innovation KPI Register, Patent Link Register, Collaboration Link Register, Failure Link Register, Asset Link Register, Product Link Register and Research Paper Link Register.

Q9Which KPIs does Division 25 recommend?

Six dashboard categories keep the innovation programme measurable at portfolio, technology, development, IP, commercial and impact level. Portfolio: Total innovation projects, Active / completed / abandoned, Projects by category, Projects by airport/project; Technology: Average TRL, Technologies at TRL 1–3, Technologies at TRL 4–6, Technologies at TRL 7–9, Ready for adoption; Development: Concepts, Research projects, Prototypes, PoCs, Pilots, Validated technologies; IP: Patent ideas, Patentability assessments, Patent filings, Granted patents, Licensed technologies; Impact: Energy savings, Reliability improvement, Maintenance reduction, Cost savings, Safety improvement; Each active project can also carry an Innovation Health Score (e.g. 82/100 — Healthy / Attention Required / At Risk / Critical) built from technical feasibility, TRL progression, schedule and cost performance, safety, reliability, PoC/pilot progress, and commercial and IP potential — plus lifecycle tracking of how long each project takes to move Idea → Feasibility → Prototype → PoC → Pilot → Commercialization, to surface bottlenecks in the Innovation Cycle Time.

Q10What is “Database Governance” in Division 25?

Clear ownership keeps the master database trustworthy as it grows. It includes Innovation Database Owner — data quality, registration, classification, record integrity, relationships, reporting, Project Owner — technical updates, milestones, results, risks, lessons, Technical Reviewer — technical accuracy, feasibility, validation and Innovation Governance Committee — stage-gate decisions, priority, investment, continuation/termination.

Q11What does Revision History (REC-17) cover?

Every innovation record maintains a controlled revision history and preserves historical changes rather than overwriting important project history.

Q12What does Problem Statement (REC-03) cover?

Describes the engineering problem being solved. Should Answer: What is wrong?, Where does it occur?, How frequently?, What is the operational consequence?, What is the current limitation? and Why does the problem require innovation?.

Q13What does Existing Solution (REC-04) cover?

Documents the current method before innovation, establishing the baseline against which innovation performance is later measured. Includes: Existing technology, Existing process, Existing equipment, Current performance, Current limitations, Current cost and Current maintenance requirement.

Precision AGL Academy

Turn Project Intelligence Into Innovation Capability.

The innovation database and project intelligence start with understanding how records, evidence and cross-project data are captured, structured and reused. The next step is building the technical knowledge required to evaluate, develop and apply this intelligence across future AGL innovation work.

Build the Foundation for Future AGL Engineering

Develop structured knowledge across:

AGL Fundamentals Electrical Systems Design Photometry Testing Maintenance Troubleshooting Digital Engineering Emerging AGL Technologies

Understand how engineering problems become opportunities, technologies, concepts, validation activities and measurable improvements.

Understand today's AGL. Build tomorrow's capability.

Talk to Precision AGL Academy

Follow the Academy