Integrated_modular_avionics

# Integrated modular avionics Integrated modular avionics (IMA) is the architecture that turned an [[Aircraft|airliner]]'s [[Avionics|avionics]] from dozens of dedicated boxes into a shared, partitioned [[Computer_architecture|computer platform]]: standardized [[Computer_hardware|processing modules]] in a cabinet run many functions of different criticality side by side, isolated by a [[Real-time_computing|real-time]] operating layer so rigorously that a failed cabin application cannot disturb the [[Fly-by-wire|flight-control]] software on the same silicon. Proven at scale on the Boeing 777's AIMS system (1995) and generalized on the Airbus A380 and Boeing 787, IMA trades the physical separation of the old federated design for enforced logical separation — buying hundreds of kilograms of weight, power, spares, and wiring, at the price of a formidable certification and [[Systems_engineering|integration]] problem. Its load-bearing ideas are time-and-space partitioning, deterministic networking, and [[Redundancy_(engineering)|redundancy]] engineered against both random hardware failure and common-mode design error. ## From federated boxes to a shared cabinet Classical avionics allocated one function per line-replaceable unit: its own processor, power supply, enclosure, and point-to-point wiring. Safe, simple to certify — and heavy, power-hungry, and obsolescence-prone, since every box aged on its own schedule of bespoke [[Computer_hardware|hardware]]. IMA replaces the fleet of boxes with racks of common processing modules built from commercial [[Integrated_circuit|silicon]], hosting applications as [[Software_engineering|software partitions]]. The 777's AIMS consolidated flight management, displays, maintenance, and data functions; the A380 spread some two dozen common modules and remote [[Sensor|data concentrators]] across the [[Aircraft|airframe]]; the 787's Common Core System hosts on the order of a hundred applications from many suppliers on one platform. The [[Electronics|electronics]] win compounds: fewer enclosures and connectors raise [[Reliability_engineering|reliability]] (connectors are a dominant failure site), common spares simplify [[Maintainability|maintenance]], and processor refreshes can ride [[Very-large-scale_integration|Moore's law]] without re-engineering every function — an [[Aerospace_engineering|aerospace]] answer to the upgrade treadmill of commodity [[Computer_architecture|computer architecture]]. ## Time and space partitioning: the load-bearing idea The platform's contract is robust partitioning, standardized in ARINC 653 (late 1990s onward): each application receives fixed windows of processor time in a static major frame, and a hardware-enforced memory region, with the operating layer policing every boundary. Spatial isolation rides the [[Computer_architecture|memory-management unit]]; temporal isolation forbids one partition from stealing another's microseconds — a deliberately harsher regime than desktop [[Multithreading_(computer_architecture)|multithreading]], because [[Real-time_computing|worst-case timing]], not average throughput, is what certifies. This is what lets software of different Design Assurance Levels share a module: flight-critical Level A code (its [[Probability|failure probability]] budgeted below 10⁻⁹ per flight hour for catastrophic conditions) coexists with Level D cabin utilities, each certified to its own rigor under DO-178C, with the platform itself certified once under DO-297's incremental-acceptance scheme. The intellectual debt is to [[Real-time_computing|hard real-time]] scheduling theory and to [[Correctness_(computer_science)|program-correctness]] discipline: static worst-case execution analysis, no dynamic allocation in [[Computer_programming|flight code]], and [[Software_quality_assurance|software quality assurance]] processes that treat the [[Software_engineering|engineering]] of evidence as seriously as the code. ## Deterministic networks: AFDX and its ancestors Shared computing demands shared communication with guarantees. The lineage runs from [[Avionics|ARINC 429]] (one-way buses at 12.5 or 100 kbit/s, one label at a time) through MIL-STD-1553's command-response megabit bus to AFDX — ARINC 664 Part 7 — the avionics profile of switched full-duplex [[Telecommunications_engineering|Ethernet]] introduced with the A380. AFDX carves 100 Mbit/s links into virtual links, each with a contracted bandwidth allocation gap and frame size, so worst-case latency and jitter are provable by network-calculus arguments descended from [[Queueing_theory|queueing theory]]; every frame travels twice, over independent A and B networks, with sequence integrity checked at the receiver. Determinism here is not average-case speed but bounded worst case — the network analogue of the partition clock — and it is what allows [[Sensor|sensor]] data, [[Inertial_navigation_system|inertial reference]] outputs, and [[Signal|display streams]] to share copper without arbitration surprises. [[Error_detection_and_correction|Error detection]] wraps every layer, from frame checksums to end-to-end integrity words. ## Failure containment: voting, dissimilarity, radiation Partitioning contains software faults; hardware faults need [[Redundancy_(engineering)|redundancy]]. IMA systems replicate modules and lanes in command/monitor pairs and triplex voting sets, and against common-mode design error they deploy dissimilarity: the A320 pioneered [[Fly-by-wire|flight computers]] built on different processors programmed by separate teams, and the 777's primary flight computers vote three lanes of three dissimilar processor types. The environment adds a physics problem: at 10–12 km the [[Atmosphere_of_Earth|atmospheric]] [[Neutron|neutron]] flux runs a few hundred times sea level, flipping bits in dense [[Computer_hardware|memories]], so IMA hardware leans on [[Error_detection_and_correction|error-correcting memory]], lockstep cores, scrubbing, and selective [[Radiation_hardening|radiation hardening]]. Safety cases assemble all of this with [[Fault_tree_analysis|fault trees]] and [[Failure_mode_and_effects_analysis|FMEA]] under ARP4761, allocating the 10⁻⁹ budgets down through cabinets, partitions, and virtual links — [[Safety_engineering|safety engineering]] as an accounting discipline, with the [[Probability|probability]] arithmetic audited by regulators. ## What IMA buys, what it costs, where it goes The ledger favors integration: airframers report large savings in mass, power, volume, and part count, plus incremental certification when one hosted function changes — the platform's evidence stands while the application's is redone. The costs are systemic: a platform supplier becomes critical infrastructure; integration testing explodes [[Combinatorics|combinatorially]] as hosted functions multiply; and shared resources concentrate what federation dispersed, so the isolation proofs must be airtight precisely because the architecture removes physical firewalls. Current fronts include distributed IMA (processing pushed toward [[Sensor|sensors]] and effectors), certified use of [[Multithreading_(computer_architecture)|multicore processors]] — where interference through [[Computer_hardware|shared caches and memory controllers]] reopens the temporal-isolation problem the single-core era had closed, addressed by 2020s regulatory guidance — and export of the pattern beyond air transport: the same partitioned, [[Robustness_(computer_science)|robustness]]-first stack now flies in military platforms and spacecraft, where [[NASA]]-heritage fault-protection philosophy and IMA practice have effectively merged into one [[Computer_engineering|computer-engineering]] tradition for machines that are not allowed to crash in either sense. **On the spine:** [[Avionics]] · [[Fly-by-wire]] · [[Real-time_computing]] · [[Redundancy_(engineering)]] · [[Fault_tree_analysis]].  **Microsim — three.js (Wikitube framework):** *Integrated modular avionics* <div class="wt-sim" data-src="https://wikitube-3d-microsims.netlify.app/flight/Integrated_modular_avionics.html" data-title="Integrated modular avionics"></div> *Built from `MICROSIM_GUIDE/specs/sims/Integrated_modular_avionics.json`; part of the [[Aviation]] · [[Avionics]] flight set.*   **Part of the [[Avionics]] hub** — main article for section X2, *Modern avionics*. Related sections: [[Radiation_hardening]] · MIL-STD-1553 · [[Fly-by-wire]].  ## Wikipedia : Wikitube **Strict pair:** [Wikipedia](https://en.wikipedia.org/wiki/Integrated_modular_avionics) : [Wikitube](https://en.wikitube.io/wiki/Integrated_modular_avionics) ## Previous hub tags Hubs: —. Portals: [[PORTAL_Avionics]]. --- *Repopulated 2026-08-12 · redlink fill · 0 deletions.*