Command 360 · SCIKIQ IAF Demo

The apex Consume view. The Capability Diagnostic stitches the IAF FY2026-27 story end-to-end — each section carries data, AI commentary, a key insight and an action — and the Single Operational Picture is the same picture, live. Strategic figures are synthetic, grounded in the open-source diagnostic.

Executive synthesis

Stable doctrine and combat-proven defences — the deficit is in numbers and timeline, not will or budget

The IAF is a ~30-squadron force measured against a 42-squadron two-front benchmark, now funded at record capital levels. The prize is not more doctrine — it is closing the squadron gap before legacy fleets retire, and converting a funded pipeline into delivered aircraft.

~30/42Force structure · operational fighter squadrons Explore ›

₹2.19L crModernization · IAF capital outlay FY2026-27 Explore ›

Op SindoorReadiness · layered air defence, combat-validated Explore ›

Generating AI read…

✨ Ask

Key insight

Read the chain end-to-end: a shrinking fighter fleet retires faster than a funded-but-bottlenecked pipeline can replace it, while a combat-proven defensive layer buys time. Capacity, recapitalization and readiness are three links of one chain — each with a named, ownable decision in the sections that follow.

Action

Run the force as one chain, not three programmes: protect the backbone, unblock propulsion, and convert funding to contracts — in that order — and hold each link to a named owner.

What needs senior attention now

Engine cadence — F404 supply gates ~30 built Mk1A airframes and the entire indigenous fighter line.
Squadron drawdown — legacy types retire faster than replacements arrive; the gap widens before it narrows.
MRFA decision — the largest single drawdown-arrest lever (~114 jets) is still pending.
Enabler thinness — AEW&C and tankers remain in single digits and cap offensive reach.
Budget absorption — record capital must convert to signed contracts within the fiscal year.

Force structure · Squadron strength

The deficit is real and decades-deep — drawdown momentum is the headline, not doctrine

Operational fighter squadrons against the sanctioned 42, traced across the modern era. The trend, not any single year, is the senior-level signal.

~30squadrons today Explore ›

42sanctioned strength Explore ›

12squadron deficit Explore ›

35-36best case by 2035 Explore ›

Operational squadrons vs the sanctioned 42 — across the modern era

Mid-1980s 39.5

2006 32.0

2021 30.0

2024 31.0

2026 (today) 30.0

2035 (best case) 35.5

Generating AI read…

✨ Ask

Key insight

The gap opened gradually: Soviet-era fleets (MiG-21/23/27) retired faster than replacements arrived. The last MiG-21 squadrons stood down in September 2025 with no one-for-one replacement, and Jaguar/MiG-29/Mirage retirements queue behind them — the deficit widens before it narrows.

Action

Treat squadron count as the board-level metric: arrest the drawdown first (engine supply, Mk1A acceptance), then rebuild. Plan to a margin above 42 if two-front simultaneity is the planning assumption.

Fleet composition · Combat aircraft

The Su-30MKI is the franchise; the gap sits where the legacy fleets are retiring

Current fighter order-of-battle by type. The IAF runs more origins and generations in parallel than any peer air force — deliberate supply-line diversity, but a sustainment and integration burden.

Fighter squadrons by type

Su-30MKI 12

Jaguar 6

MiG-29 UPG 3

Mirage 2000 3

Rafale 2

Tejas Mk1 2

Type	Generation	Sqns	Role	Mission-capable	Posture
Su-30MKI	4.5-gen	12	Multi-role backbone	60	Sustain
Jaguar	Legacy	6	Deep strike	48	Retire late-20s
MiG-29 UPG	Legacy	3	Point defence / strike	50	Retire >2028
Mirage 2000	Legacy	3	Multi-role (upgraded)	58	Retire 2030s
Rafale	4.5-gen	2	Air dominance / strike	80	Grow
Tejas Mk1	LCA	2	Light fighter	75	Induct

Generating AI read…

✨ Ask

Key insight

Twelve Su-30MKI squadrons carry the force; the two newest types (Rafale, Tejas) total only four squadrons. As the three legacy types retire, the burden falls on the Su-30 fleet — driving up flying hours and sustainment stress on a single platform.

Action

Protect Su-30MKI availability (upgrade & spares), accelerate Tejas induction to backfill MiG-21, and lock the MRFA decision to replace the Jaguar/MiG-29/Mirage tranche before the retirement cliff.

Modernization · Recapitalization pipeline

The roadmap is sound on paper — the risk is the timeline, not the design

The programmes meant to rebuild the fighter fleet, with order size and current status. Blending indigenous development with foreign procurement manages risk; execution is the open question.

Tejas Mk1A order book — fully contracted, nothing delivered

Mk1A contracted (2021) 83

Mk1A contracted (2025) 97

Delivered to IAF 0

Built, awaiting engines ~30

Programme	Class	Quantity	Delivered	Status	Squadrons by
Tejas Mk1A	Indigenous light fighter	180	0 (+30 built)	0 delivered; first Aug-Sep '26, engine-gated	Late 2020s
MRFA (Rafale)	Foreign 4.5-gen, made-in-India	~114	0	Decision pending; ~₹3.25L cr / ~$43B	Early-mid 2030s
Tejas Mk2	Indigenous medium fighter	~120	0	F414 engine deal in negotiation	Early 2030s
AMCA	Indigenous 5-gen stealth	~120	0	PPP cleared May-25; prototype 2026-27	2030s
Existing Rafale	Foreign 4.5-gen	36	36	Inducted (2 squadrons)	In service

Generating AI read…

✨ Ask

Key insight

The pipeline is fully ordered and funded — 180 Tejas Mk1A contracted, MRFA at decision, AMCA cleared. The failure mode is not procurement intent; it is the gap between contract and cockpit, where ~30 Mk1A airframes sit built but undelivered for want of engines.

Action

Hold programme reviews to contract-to-cockpit milestones, not the order book: track engines-delivered and airframes-inducted as the true cadence metrics, and put the slowest link on a named recovery plan.

Critical path · Propulsion

The whole drawdown bottlenecks on one component — the fighter engine

Airframes are not the constraint; engines are. The GE F404 (Mk1A) and F414 (Mk2 / AMCA) supply chains gate the entire indigenous fighter plan.

~6/99F404 engines on hand vs batch-1 need Explore ›

~0.6/modelivery cadence vs 2+/mo target Explore ›

~30airframes built, awaiting engines Explore ›

F414next bottleneck · Mk2 / AMCA Explore ›

Why a single-supplier dependency dominates the schedule

Airframes built & waiting ~30

Engines on hand ~6

Engines needed (batch 1) 99

Generating AI read…

✨ Ask

Key insight

This is the single highest-leverage item in the diagnostic: every squadron-strength projection is downstream of engine throughput. Resolving F404 cadence and closing the F414 co-production deal de-risks Mk1A, Mk2 and AMCA simultaneously.

Action

Escalate engine supply to a government-to-government / OEM-CEO track; tie the F414 co-production agreement to a firm localization and throughput schedule. Treat propulsion as the programme's critical path, owned at the top.

Readiness · Air defence & combat enablers

The shield is combat-proven; the force-multipliers are still thin

Operation Sindoor (May 2025) validated the layered air-defence network in live combat. The persistent gap is in the enablers that let a smaller fighter fleet fight above its weight — AEW&C and aerial refuelling.

Layered air defence · combat-validated, Op Sindoor

System	Layer	Range	Status
S-400 'Sudarshan'	Long	up to 400 km	Growing
MR-SAM / Barak-8	Medium	70-100 km	Operational
Akash	Short	25-45 km	Operational

Combat enablers · the cheapest force-multiplier

Enabler	Plan	Status
AEW&C	+12 systems	On order
Netra Mk II (Embraer)	6 aircraft, AESA	Inducting
Aerial refuellers	6 (IAI / Boeing 767)	Ordered
MALE RPA / drones	Multi-programme	Funded

Generating AI read…

✨ Ask

Key insight

Sindoor's lesson cuts two ways: the defensive kill chain works (long-range intercepts, multi-system interoperability), but offensive reach and persistence depend on AEW&C and tankers that remain in single digits. The enablers are the cheapest force-multiplier per rupee while fighter numbers recover.

Action

Fast-track AEW&C and tanker inductions — they compound the value of every existing fighter. Expand the air-defence layer (S-400 follow-on, Akash, counter-drone) given the demonstrated saturation-attack threat.

Resourcing · Capital allocation FY2026-27

Money is not the binding constraint this year — absorption is

The FY2026-27 Union Budget raised defence capital sharply and ring-fenced the largest single capital head for aircraft. The Standing Committee's concern is now utilisation, not allocation.

₹7.85L crtotal defence budget FY2026-27 Explore ›

₹2.19L crcapital outlay (modernization) Explore ›

₹63.7k craircraft & aero-engines head Explore ›

+37%aircraft capital, year-on-year Explore ›

Capital outlay by head — aircraft is the fastest-rising

Other equipment ₹82.2k 37%

Aircraft & aero-engines ₹63.7k 29%

Naval fleet ₹25.0k 11%

Construction works ₹11.8k 5%

Balance / other ₹36.3k 18%

Generating AI read…

✨ Ask

Key insight

Aircraft & engines are the second-largest capital head and the fastest-rising service allocation. Parliament's Standing Committee has explicitly urged the IAF to spend the full allocation on MRFA, combat enablers and Mk1A — flagging under-utilisation, not under-funding, as the risk.

Action

Convert allocation into signed contracts within the fiscal year (MRFA decision, enabler orders) so funds are not surrendered; align cash-flow to delivery milestones rather than committed liabilities alone.

Threat environment · Two-front benchmark

The 42-squadron benchmark exists because the planning case is two fronts at once

Why the deficit matters operationally: the sanctioned strength is sized to a simultaneous western (Pakistan) and northern (China) contingency. A ~30-squadron force fights that case with a reduced 'Plan-B' posture.

Western front — Pakistan: Saturation drone / missile. Short-warning; saturation-attack axis (validated Op Sindoor, May 2025)
Northern front — China (LAC): Sustained pressure. Attrition axis; drives indigenous-tech emphasis
Peninsular / Reserve — —: Depth / reserve. Strategic depth and reserve posture

Force adequacy against the case

Full two-front benchmark 42

With simultaneity margin 50+

Today ~30

Generating AI read…

✨ Ask

Key insight

The deficit is not abstract: at ~30 squadrons the force executes the two-front case on a reduced-strength 'Plan-B', with every airframe carrying disproportionate strategic weight. This is what converts a procurement-schedule problem into a national-security one.

Action

Size the recapitalization target to the two-front simultaneity case (a margin above 42), and protect the readiness enablers that let a smaller fleet cover both axes until numbers recover.

Risk register · Sustainment & safety

A small fleet flown harder shows up as a safety and sustainment signal

As legacy types retire without one-for-one replacement, the remaining fleet absorbs more sorties and flying hours. The 2026 incident pattern is a sustainment indicator senior leadership should track alongside the numbers.

Risk	Driver	Exposure	Trend
Single-supplier engines	GE F404 / F414 dependence	Entire indigenous fighter line	Critical
Fleet over-tasking	MiG-21 retired, fewer airframes	Su-30MKI flying-hour stress	Rising
Retirement cliff	Jaguar / MiG-29 / Mirage	Multiple squadrons late-2020s+	Approaching
Accident rate	Ageing types + higher utilisation	4 incidents in ~4 months (2026)	Watch
Industrial throughput	HAL / private-sector ramp	Delivery-vs-contract gap	Mixed
Air-defence depth	Saturation-attack threat	Interceptor magazine depth	Improving

Generating AI read…

✨ Ask

Key insight

The 2026 incidents — a Su-30MKI loss, a damaged Tejas, and others — occurred against the backdrop of the deepest squadron deficit since the mid-20th century. Each event matters more when there are fewer airframes to absorb the loss; safety and force-structure risk are linked, not separate.

Action

Stand up a monthly fleet-health watch: flying-hour distribution by type, availability rates, and accident causal-factor tracking — and feed it into induction-pace decisions.

Where to focus · Decisions & priority

Quick capability wins first, then the structural recapitalization programmes

Prioritised across force structure, modernization and readiness. 'Lever' = the capability pool each decision unlocks. Effort and ownership noted for senior tasking.

Decision	Dimension	Lever	Effort	Owner	When
Resolve F404 engine cadence	Modernization	~30 built Mk1A → inducted	Low-Med	MoD / GE / HAL	1-2Q
Accept first Mk1A tranche	Force structure	First new squadron since Rafale	Low	IAF / HAL	2-3Q
Fast-track AEW&C + tankers	Readiness	Force-multiplier on whole fleet	Med	IAF / MoD	2-4Q
Close MRFA decision (~114)	Modernization	Largest drawdown-arrest lever	High	DAC / MoD	FY26-27
Sign F414 co-production	Modernization	De-risks Mk2 + AMCA	Med-High	MoD / GE-HAL	FY26-27
Expand air-defence layer	Readiness	Counter saturation attack	Med	MoD / DAC	Ongoing
Sustain Su-30MKI availability	Force structure	Protect the backbone	Med	IAF / HAL	Ongoing
Mature AMCA (PPP)	Modernization	5-gen deep-strike	High	ADA / industry	2030s

Generating AI read…

✨ Ask

Key insight

Start with the near-term capability wins this fiscal — fix engine supply, accept the first Mk1A squadron, and fast-track enablers — because they convert already-funded, already-built assets into fielded capability. The MRFA, F414 and AMCA decisions span years but carry the largest structural prize.

Action

Sequence the tasking: 1-2Q engine cadence + Mk1A acceptance; 2-4Q enablers + MRFA close; FY26-27 F414 co-production; out-years AMCA. Assign each line a named owner from the table.

Senior leadership dashboard · Report-up metrics

What to report up — the six numbers that tell the whole story

A standing scorecard for the apex review. Each metric maps to a decision on the prior section; together they track the chain from capacity to recapitalization to readiness.

Metric	Now	Target	Dimension	Status
Operational fighter squadrons	~30	42	Force structure	Below
Tejas Mk1A delivered (of 180)	0	180	Modernization	Blocked
F404 engine delivery cadence	~0.6/mo	2+/mo	Critical path	Behind
MRFA contract (~114)	Pending	Signed	Modernization	Decision
AEW&C / tanker inductions	Few	+12 / +6	Readiness	On order
Air-defence squadrons (S-400)	4	5 + 5	Readiness	Growing

Generating AI read…

✨ Ask

Key insight

Three of the six are red and self-reinforcing — squadrons, Mk1A deliveries and engine cadence are the same problem seen at three altitudes. Two readiness metrics are green and combat-proven. Engine cadence is the unlock for all three reds.

Action

Adopt these six as the standing apex scorecard; review monthly and tie each red metric to its named decision owner until it turns green.

Bottom line for the apex review

The IAF enters FY2026-27 doctrinally sound, combat-validated and, for once, well-funded — but structurally short of fighters and dependent on a single propulsion bottleneck to recover. The senior-level job this year is conversion: turn record capital into signed contracts, turn built airframes into inducted squadrons, and turn a proven defensive shield into an offensive force-multiplier through enablers. The squadron number is the scoreboard; the engine is the lever.

All figures synthesised from open-source material — Union Budget FY2026-27, Standing Committee on Defence reports, IISS Military Balance, HAL disclosures and reputable defence press (assessments vary; ranges shown where sources differ). An analytical synthesis, not an official IAF or MoD publication — no classified or operationally sensitive detail. The italic "AI read" under each section is generated live and grounded in this governed data.

IAF COMMANDER'S DASHBOARD · DIGITAL CONTROL TOWER SINGLE OPERATIONAL PICTURE · FY2026-27

Force KPIs

Fighter squadrons~30/42

Mission-capable rate62%

Tejas Mk1A inducted0/180

S-400 squadrons4 → 5

Capital budget YoY+37%

Budget executed58%

Theatre picture · Western · Northern · Peninsular

✨ AI insights & recommended actions

Induction risk: F404 cadence (~0.6/mo) puts the first Mk1A squadron at high schedule risk.

Supply risk: Su-30MKI spares demand rising as legacy fleets shed sorties onto the backbone.

Predicted decline: Jaguar / MiG-29 availability trending down ahead of retirement.

Recommended: escalate engine supply to a G2G / OEM-CEO track; fast-track AEW&C + tankers.

Aircraft / fleet readiness · mission-capable % by type live readiness →

Su-30MKI 60%

Jaguar 48%

MiG-29 UPG 50%

Mirage 2000 58%

Rafale 80%

Tejas Mk1 75%

Supply chain & logistics control tower supply chain →

Spares fill-rate71%

F404 engine supply6/99

Mk1A built (of 180)30

Live AOG34

Live stock-outs61

Critical path · propulsion (F404)

Airframes built & waiting~30

F404 engines on hand~6

F404 needed (batch 1)99

Cadence / month0.6

Personnel

~92%

manning vs authorised

Maintenance

incidents in ~4 months

Financial

₹63.7k cr

aircraft & engine capital

Operations

Op Sindoor

air-defence validated

One picture, seven domains

click a domain to drill into the detail

Force Structure & Readiness77.6% available Logistics & Sustainment34 AOG Modernization & Acquisition0/180 Mk1A Financial Management+37% capital Intelligence & Threattwo-front Personnel & Health~92% manned Operations & MissionsOp Sindoor

🔒 Source: s_* strategic layer · aircraft · spares · budget_lines (live) · governed & traceable

Purpose · From diagnostic to live control tower

A diagnostic answers "where are we?" — this blueprint answers "how do we keep knowing, continuously?"

The diagnostic established the metrics (squadron strength, engine cadence, fleet readiness). To run those as a standing operational picture, five architecture artifacts must be defined first. This document defines each, in the order they depend on one another.

Artifact	What it defines	Why it is needed for the control tower
Taxonomy	The classification — domains, categories and controlled vocabulary (the 'nouns', organised)	Without an agreed classification, the same aircraft, base or budget head is named differently in every source system; nothing aggregates.
Ontology	The entities, their attributes and the relationships between them (the semantic model / knowledge graph)	Lets the platform answer cross-domain questions — 'which squadrons are at risk because an engine line is slipping?' — by following relationships.
Process maps	The operational processes as swimlanes — who does what, in what order	Identifies where data is created and where decisions are made, so the tower instruments the right steps (e.g. the engine-to-induction bottleneck).
Data flows	How data physically moves: source -> fabric -> analytics -> tower (the 4C pipeline & stores)	The engineering backbone — ingestion, curation, governance and consumption — that keeps the picture current.
Business flows	The decision loop: sense -> analyse -> recommend -> decide -> act -> feedback	Closes the loop so the tower drives action, not just reporting — the difference between a dashboard and a control tower.

Key insight

These artifacts are sequential dependencies, not parallel chapters: taxonomy gives shared language, ontology connects it, process maps locate the data and decisions, data flows move the data, and business flows turn it into action. Build them in this order and the control tower in the diagnostic's appendix becomes implementable.

Taxonomy I · Domain & asset classification

One agreed classification across every source system

The taxonomy is a strict hierarchy ("is-a / part-of"). At the top sit the seven analytics domains the control tower spans; the asset/platform taxonomy below them is the most reused branch.

Analytics domains (top level)

Force Structure & Readiness
Logistics & Sustainment
Modernization & Acquisition
Financial Management
Intelligence & Threat
Personnel & Health
Operations & Missions

Asset / platform taxonomy

Combat aircraft
- 4.5-gen (Su-30MKI, Rafale)
- Light (Tejas Mk1/Mk1A)
- Legacy (MiG-29, Mirage 2000, Jaguar)
- 5-gen (AMCA — future)
Force enablers
- AEW&C · Aerial refuellers · Transport · RPA
Air defence
- Long (S-400) · Medium (MR-SAM) · Short (Akash)
Rotary & trainers

Force-structure hierarchy

Command (Western, Eastern, Central, South-Western, Southern, Training, Maintenance)
- Station / Air Base
Wing -> Squadron -> Flight
Aircraft (tail number)
Strength view: sanctioned vs authorised vs held

Readiness states (controlled vocabulary)

Mission-Capable (MC)
- Full-MC · Partial-MC
Not-Mission-Capable
- NMC-Maintenance · NMC-Supply
Availability · Serviceability rate
AOG (Aircraft-on-Ground) flag

Key insight

The controlled vocabulary is the unglamorous part that makes everything else work: if "Not-Mission-Capable" means the same thing at every base, squadron-strength and availability roll up automatically. Standardise the vocabulary before building any dashboard.

Taxonomy II · Logistics, acquisition, finance & threat

The supporting branches — where cost, supply and risk are classified

The remaining domain branches. These feed the supply-chain, financial and intelligence panels of the Commander's Dashboard.

Logistics & sustainment

Spares
- Rotables · Consumables · Repairables
Propulsion (engines)
- F404 · F414 · AL-31FP
POL · ground support equipment
MRO events
- Scheduled · Unscheduled · Depot-level
Supply nodes · fill-rate · lead-time

Modernization & acquisition

Programme (Tejas Mk1A, MRFA, Mk2, AMCA)
- Contract -> Tranche -> Delivery milestone
Status (sanctioned · contracted · in-production · delivered)
Indigenous content %
Dependency (engine / sub-system)

Financial management

Capital
- Aircraft & aero-engines · Other equipment · Construction
Revenue (O&M) · committed liabilities
Budget execution
- Allocated · Committed · Spent · Surrendered

Intelligence & threat / personnel

Sector (Western · Northern · Peninsular)
Threat type (air · missile · drone/swarm)
Air-defence coverage & magazine depth
Personnel: aircrew · technical · support
- Authorised vs held · skill currency

Action

Assign a domain steward for each top-level branch (Readiness, Logistics, Acquisition, Finance, Intelligence, Personnel). The steward owns the controlled vocabulary and approves changes — this is the governance hook that keeps the taxonomy from fragmenting again.

Ontology I · Core entities & attributes

From a list of categories to a connected model of the force

Where the taxonomy classifies, the ontology defines the entities (object types), their key attributes, and — on the next page — how they relate. These are the object types the knowledge graph instantiates.

operational coreactivity & sustainmentresourcing & acquisitionthreat & defence

Command

id, name, region

oversees bases in a sector

Base / Station

id, name, command, sector, geo

hosts squadrons

Squadron

id, number, type, status, strength

the force-structure unit

AircraftType

name, generation, role, origin

e.g. Su-30MKI

Aircraft

tail_id, type, status, hours, mc_state

the physical asset

Engine

serial, model, hours, status

F404 / F414 / AL-31FP

Sortie / Mission

id, type, date, duration, outcome

MaintenanceEvent

id, type, AOG?, start, end

scheduled / unscheduled

SparePart

nsn, name, category, stock, fill_rate

Programme

name, class, status, indig_%

Tejas Mk1A, MRFA…

Contract

id, qty, value, signed, milestones

Vendor / OEM

name, role

HAL, GE, Dassault, Almaz-Antey

BudgetLine

head, fy, allocated, committed, spent

AirDefenceSystem

name, layer, range, sector

S-400 / MR-SAM / Akash

Sector

name, command, threat_axis

ThreatAxis

name, threat_type, intensity

Western / Northern

PersonnelUnit

category, authorised, held, currency

DeliveryMilestone

programme, planned, actual, qty

Key insight

Note the colour groups — operational core, activity & sustainment, resourcing & acquisition, threat & defence. These map one-to-one to the dashboard panels — the ontology is the data behind the glass.

Ontology II · Relationship model / knowledge graph

The relationships are where cross-domain questions get answered

Entities connected by named relationships (a knowledge graph). Following the edges is how the tower links an engine-supply slip to a squadron-strength risk to a budget line.

Action

Implement the relationships as a graph/semantic layer over the lakehouse. The query "show squadrons whose AircraftType is produced by a Programme whose engine Contract is slipping" is one traversal — that is the cross-domain power the diagnostic's appendix promised.

Process Map I · Readiness reporting & force-strength governance

How a tail number's status becomes an apex-level squadron-strength decision

Swimlanes show who acts and where data is created. Follow the numbered steps left-to-right; the green step is where the control tower replaces manual aggregation.

Actor / Lane

Capture

Aggregate

Compute

Review

Act

Squadron / Base

Log MC state

per tail number

Command

Roll up availability

by type & base

Re-task / redeploy

within command

Control Tower

Compute squadron strength

vs sanctioned — auto

Flag deficit & trend

+ AI risk alerts

Air HQ / Apex

Apex review

single picture

Direct action

induction pace, sustainment

Key insight

Today steps 2–4 are manual and periodic; that is the lag between a problem and the apex seeing it. The control tower automates aggregate -> compute -> flag, so the squadron-strength number is always current and the review (step 5) starts from a trusted picture rather than reconciling spreadsheets.

Process Map II · Acquisition & engine-to-induction critical path

The recapitalization process — and the single step that gates the whole force

From requirement to inducted squadron. The red step is the propulsion bottleneck identified in the diagnostic; instrumenting it is the highest-value thing the tower can watch.

Actor / Lane

Requirement

Contract

Supply

Build & Test

Induct

IAF / Air HQ

Define requirement

qty, capability

Acceptance trials

sign-off

Induct squadron

strength +1

MoD / DAC

Approve & contract

DAC clearance

OEM (engine)

Deliver engines

F404 / F414 — bottleneck

HAL / Industry

Airframe ready

built, waiting

Mate & flight-test

integrate engine

Key insight

Steps 3 and 4 happen in parallel but step 5 cannot start until both complete — and airframes (4) are ready while engines (3) are not. The tower should track the gap between built-airframes and engines-on-hand as a live metric; it is the leading indicator for every squadron-strength projection.

Action

Wire an automatic alert when the airframe-to-engine gap exceeds a threshold, routed to the MoD/OEM escalation track — turning the diagnostic's static finding into a standing trigger.

Data Flows · The 4C pipeline (Connect · Curate · Control · Consume)

How data physically moves from source systems to the glass

The engineering backbone. Source systems feed an ingestion layer; data is curated into a governed semantic layer (the ontology), with governance as a foundation, and served to the control tower and AI.

Maintenance / MROtail status, AOG

Logisticsspares, engines

Finance / ERPbudget, contracts

Acquisitionprogramme, milestones

ISR / Intelthreat, sectors

▼

Connect

Ingest

Batch & streaming connectors
API / file / CDC ingest
Schema capture

Store: Raw / landing zone (immutable)

▶

Curate

Transform & quality

Store: Curated zone + semantic / graph layer

▶

Consume

Analytics & AI

Store: Domain marts / feature store

Control (governance foundation, spans all stages): data catalog · domain stewardship · access & classification (releasability) · data-quality SLAs · lineage & audit. This is what makes the picture trusted, not just available.

Commander's Dashboard

AI Recommendations & Alerts

Audit & Readiness Reporting

Key insight

"Connect -> Curate -> Consume" is the flow; Control is a foundation, not a stage — governance, lineage and releasability apply at every step. The Curate stage is where the taxonomy and ontology defined earlier are actually applied; without them, the raw zone never becomes a trusted picture.

Business Flows · The sense-to-act decision loop

What makes it a control tower, not a dashboard: the loop closes

The business value flow. Each stage produces an output the next consumes, and commander action changes the source systems — which the tower re-reads. The loop, not the report, is the point.

Sense

Source systems emit status, supply, cost, threat

▶

Aggregate

Curate to ontology; one trusted picture

▶

Analyse

AI: risk, forecast, anomaly across domains

▶

Recommend

Ranked options & predicted impact

▶

Decide

Commander selects course of action

▶

Act

Tasking / escalation / re-allocation

◀ Feedback loop: action changes the source systems · the tower re-senses · the picture updates — continuous, not periodic ◀

Business capability → data product → KPI (worked examples)

Business capability	Data product	KPI it drives	Loop trigger
Force-strength governance	Squadron-strength model (auto roll-up)	Operational squadrons vs 42	Deficit / trend breach -> apex review
Recapitalization assurance	Programme delivery-vs-contract tracker	Tejas Mk1A delivered of 180	Airframe-engine gap -> OEM escalation
Sustainment optimisation	Fleet availability & spares model	Mission-capable % by type	MC drop / AOG spike -> supply action
Budget execution	Capital execution dashboard	% allocation committed/spent	Under-execution -> contract acceleration
Air-defence readiness	Coverage & magazine-depth view	Sectors covered / interceptor depth	Coverage gap -> deployment decision

Governance · The layer that keeps it trusted

A control tower is only as good as the governance under it

The taxonomy, ontology and flows only stay coherent if owned and quality-controlled. This is the operating model around the platform.

Data governance roles

Role	Owns
Domain steward	Vocabulary & definitions for one domain
Data owner	A source system's data & releasability
Platform / architecture	Fabric, ontology, pipelines
AI / model owner	Model validity, drift, explainability
Apex sponsor	Decision rights & funding

Governance controls

Control	Purpose
Catalog	Discover & define every entity / metric
Lineage	Trace any number to its source
Classification	Releasability & access by clearance
Quality SLAs	Freshness, completeness, accuracy
Master data	One golden record per aircraft / base
Change control	Vocabulary & ontology versioning

Key insight

The single most common failure mode is a platform that aggregates fast but is not trusted — exactly what the DoD's Advana faced when it became "a victim of its own success." Governance (lineage, quality SLAs, master data) is what lets a commander act on the number rather than re-checking it.

Standing it up · Phased roadmap

Build the foundations first; the dashboard is the last 20%

The artifacts in this document map to a delivery sequence. Each phase produces usable value, so the programme is not a multi-year leap of faith.

Phase	Artifact delivered	Outcome	First live metric
0 · Align	Taxonomy + domain stewards	Shared vocabulary; governance stood up	—
1 · Connect	Ingest from maintenance, logistics, finance	Raw zone; sources flowing	Fleet status feed
2 · Model	Ontology + semantic / graph layer	Cross-domain queries possible	Squadron strength (auto)
3 · Instrument	Readiness & engine-to-induction processes	Bottlenecks watched live	Airframe-engine gap
4 · Consume	Commander's Dashboard + AI alerts	Single operational picture	Full KPI set
5 · Close loop	Recommend -> decide -> act workflows	Control tower, not dashboard	Action-to-effect tracking

Key insight

Resist starting at Phase 4. The dashboard is the visible part, but a dashboard on an ungoverned, unmodelled data layer is the failure mode this blueprint exists to prevent. Taxonomy and ontology are the moat; the glass is cheap once they exist.

Bottom line

The diagnostic told the IAF where it stands. This blueprint defines the taxonomy (shared language), ontology (connected model), process maps (where data and decisions live), data flows (the 4C pipeline that keeps it current) and business flows (the loop that turns insight into action) needed to keep knowing — continuously. Build them in order, govern them seriously, and the static deck becomes a living control tower.

Architecture design companion to the FY2026-27 Capability Diagnostic. Illustrative entities, attributes and processes — synthetic / open-source-grounded, not an official IAF or MoD publication, and containing no classified or operationally sensitive detail. "4C" (Connect · Curate · Control · Consume) is used here as a generic data-platform pattern.

🔍 Ask your data

Plain-language questions, answered from governed data — every answer is sourced and traceable. Free-text uses a backend AI model (key stays server-side).