Study guide
8.3 Remote Data Concentrators and Integrated Modular Avionics
EASA Part-66 Module 05 — Digital Techniques / Electronic Instrument Systems Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Numbering Systems
1.1 Numbering Systems: Decimal, Binary, Octal and Hexadecimal 1.2 Binary Arithmetic and Signed Number Representation 1.3 Binary Coded Decimal, Gray Code and Alphanumeric Codes
2 Chapter 2: Data Conversion
2.1 Analogue and Digital Signals, Sampling and Quantisation 2.2 Digital-to-Analogue Converters 2.3 Analogue-to-Digital Converters
3 Chapter 3: ARINC 429 Data Buses
3.1 ARINC 429 Specification, Physical Layer and Topology 3.2 ARINC 429 32-Bit Word Architecture 3.3 ARINC 429 Transmission, Timing and Troubleshooting
4 Chapter 4: Advanced Avionics Data Buses and Aircraft Ethernet
4.1 ARINC 629 Digital Autonomous Terminal Access 4.2 MIL-STD-1553B Military Avionics Data Bus 4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
5 Chapter 5: Combinational Logic Gates and Boolean Algebra
5.1 Basic Logic Gates, Truth Tables and Logic Levels 5.2 Boolean Algebra, De Morgan Theorems and Logic Simplification 5.3 Universal Gates and Aircraft Combinational Applications
6 Chapter 6: Sequential Logic, Registers and Logic Diagrams
6.1 Bistable Multivibrators: SR, JK, D and T Flip-Flops 6.2 Shift Registers and Data Storage Elements 6.3 Asynchronous and Synchronous Counters and Logic-Diagram Interpretation
7 Chapter 7: Computer Structure and Microprocessors
7.1 Computer Architecture, Terminology and the Bus System 7.2 Semiconductor Memory Technologies 7.3 Microprocessor Operation, Instruction Cycles and I/O
8 Chapter 8: Integrated Circuits, Multiplexing and Integrated Modular Avionics
8.1 Integrated Circuit Technology, Encoders, Decoders and Scale of Integration 8.2 Multiplexing and Demultiplexing Techniques 8.3 Remote Data Concentrators and Integrated Modular Avionics
9 Chapter 9: Fibre Optics in Aviation
9.1 Physics of Light Transmission and Optical Fibres 9.2 Fibre Cable Types, Signal Degradation and Optical Components 9.3 Fibre Optic Maintenance, Termination, Splicing and Inspection
10 Chapter 10: Electronic Displays and Flight Instrument Layout
10.1 Display Technologies: CRT, LED and LCD 10.2 Electronic Flight Instrument System Architecture 10.3 Cockpit Symbology, Colour Standards and Display Reversion
11 Chapter 11: Electrostatic Sensitive Devices
11.1 Physics of Electrostatic Charge and Device Susceptibility 11.2 ESDS Damage Mechanisms: Catastrophic versus Latent Failures 11.3 ESDS Handling, Storage, Packaging and Workshop Procedures
12 Chapter 12: Software Management Control and Airworthiness
12.1 Aviation Software Classification and RTCA DO-178C / EUROCAE ED-12C 12.2 Software Configuration Management and Part Numbering 12.3 Data Loading, Integrity Verification and Unapproved Changes
13 Chapter 13: Electromagnetic Environment
13.1 Electromagnetic Interference and Compatibility 13.2 High Intensity Radiated Fields and RF Hazards 13.3 Lightning Protection, Bonding and Static Dischargers
14 Chapter 14: Engine Indication, Warning and Monitoring Systems
14.1 Airbus ECAM — Electronic Centralised Aircraft Monitoring 14.2 Boeing EICAS — Engine Indicating and Crew Alerting System 14.3 Comparison, Failure Reversion and Sensor Interfacing
15 Chapter 15: Flight Management, Navigation and Surveillance Systems
15.1 Flight Management System and Control Display Unit 15.2 Inertial Reference, AHRS/ADIRU Context and GPS 15.3 Traffic Collision Avoidance and Terrain Awareness
16 Chapter 16: Fly-By-Wire, BITE, ACARS, Cabin and Information Systems
16.1 Fly-By-Wire Flight Control 16.2 Built-In Test Equipment and Central Maintenance Computers 16.3 ACARS, Cabin Systems and Information Systems
8.3 Remote Data Concentrators and Integrated Modular Avionics
Key Takeaways Explain This Topic AI
Integrated Modular Avionics (IMA) hosts several aircraft functions as partitioned software on shared computing, I/O and network resources in cabinets, instead of giving each function its own federated LRU.
Airbus-style teaching centres on the Core Processing Input/Output Module (CPIOM) in an IMA cabinet, talking over an avionics data network, with associated BITE in the central maintenance system.
Remote data concentrators sit near sensors and effectors, convert analogue and discrete signals into digital messages, and thereby cut the mass and complexity of dedicated wiring into the bay.
The former detailed 5.15 description treated IMA at knowledge level 1 for every licence category: general arrangement and associated BITE, not detailed software-design assurance.
Last updated: September 2026
8.3 Remote Data Concentrators and Integrated Modular Avionics
Current Module 5.15 is the broad heading Typical electronic/digital aircraft systems at level 1 for every category. Integrated Modular Avionics appeared in the pre-12 June 2024 detailed 5.15 examples; it is retained here as historical study scope, not as a name printed in the current consolidated Appendix I. This section stays at that level: what an IMA cabinet is, how shared processing differs from a federated LRU, where a Core Processing Input/Output Module (CPIOM) fits the teaching picture, why remote data concentrators exist, and how BITE names a cabinet, a module and a hosted function. It is not a software-design course; configuration control and the catastrophic effect of unapproved loads belong with topic 5.13, but the technician still needs to recognise that IMA functions are software-hosted and therefore part-numbered.
Federated LRUs: the architecture IMA replaces
In a federated avionics architecture each major function occupies its own line-replaceable unit. A flight-control computer, a flight-management computer, a flight-warning computer, a display generator and an EGPWS computer are separate boxes. Each box has its own processor, power supply, I/O cards, cooling path, BITE and, typically, its own dedicated sensor wiring. The advantages are isolation and simple mental mapping: the FMS is that tray, the warning computer is this tray. The costs are weight, volume, power, duplicated spare holdings, and a rats-nest of analogue and discrete wires from wing, engine and fuselage into the avionics bay. Classic-generation airliners are still largely federated; many radios, actuators and sensors remain federated even on IMA aeroplanes.
IMA cabinets and shared processing
Integrated Modular Avionics puts several hosted functions onto common computing resources. Hardware is organised as cabinets in the avionics bay containing processing modules, input/output modules, network switches, power supplies and cooling. Software applications — flight warning, display management, some utility-system controllers, and similar hosted functions — run as partitions on those shared processors. Time and space partitioning (the ARINC 653 teaching idea) keeps one hosted function from overwriting another’s memory or stealing its processor time. The cabinet is then a shared computer centre, not a stack of unrelated boxes that happen to share a rack.
Benefits that appear in every familiarisation brief are fewer unique LRUs, lower weight and volume, common spares, and the ability to add or move a function mainly as a software load rather than as a new dedicated computer. The corresponding maintenance shift is that “the warning computer” may no longer be a single tray you can hold; it is a hosted application on a module in a slot, plus the I/O and network that feed it. A module failure can affect several hosted functions at once, which is the opposite of federated isolation. Redundant cabinets and redundant network paths are therefore part of the general arrangement, not an optional extra.
Not every aircraft function is hosted. Radios, some flight-control actuation electronics, and many sensors remain specialised LRUs. IMA is a hosting architecture for a defined set of applications, not a claim that the aeroplane has only one computer.
CPIOM teaching (Airbus-style IMA)
On Airbus A380/A350-class IMA teaching, the Core Processing Input/Output Module is the shared processing and I/O brick. A CPIOM provides computing resource and a set of analogue, discrete and digital interfaces. Several partitioned applications can be hosted on one CPIOM type; identical hardware in different slots can carry different software loads. Input/output modules and remote devices extend the I/O where the cabinet itself should not collect every wire. Modules communicate over the avionics data network (AFDX / ARINC 664 teaching: switched Ethernet with virtual links), not over a private analogue loom for each function.
Boeing 787-class teaching uses different names — Common Core System, common computing resource cabinets, common data network — for the same architectural idea: shared cabinets, hosted functions, and remote concentration of I/O. Do not treat CPIOM as a Boeing part number or CCS as an Airbus part number; treat both as examples of shared IMA processing. Other types (for example the A220) also use IMA cabinets; the examination point is the architecture, not a single fleet.
At level 1 you should be able to say: the cabinet holds shared processors and I/O; hosted software is configuration-controlled; the network carries the data; BITE in the central maintenance function can name the cabinet, the module slot and the hosted application. You are not expected to recite partition budgets or design-assurance levels here.
Remote data concentrators and wiring
A remote data concentrator (RDC, sometimes remote interface unit in local manuals) sits physically near clusters of sensors and effectors — wing, landing gear bay, cabin, engine pylon — rather than in the avionics cabinet. It digitises analogue voltages, reads discretes, drives some analogue or discrete outputs, and forwards the results as digital messages on the aircraft network. The long run through the pressure bulkhead is then a data-bus or network cable instead of dozens of dedicated copper pairs for every thermocouple, proximity switch and position sensor.
That is the wiring-reduction argument. On a large aeroplane, federated analogue looms are a major mass item and a major source of connectors, shielding and troubleshooting time. Concentrating I/O locally also shortens analogue leads, which improves noise immunity — a practical link to topic 5.14 — and lets the IMA cabinet see a clean digital dataset. The RDC itself is a line-replaceable item with its own BITE: failed channels, power, and network links are reported, so a single missing parameter may be an RDC channel rather than a CPIOM or a sensor.
RDCs are supporting architecture for IMA; they are not a 1960s-only analogue multiplex box, and they are not a circuit-breaker panel. Older aircraft did use analogue multiplexers (section 8.2) inside a federated LRU. An RDC on an IMA aeroplane is a networked I/O node. Confusing the two is the usual examination mix-up: a 4051 on a card scans sensors for one computer; an RDC serves many hosted functions through the cabinet network.
Feature Federated LRU architecture IMA with RDCs
Computing One dedicated computer per function Shared processing modules (CPIOM / common core) hosting several partitions
I/O wiring Sensor/effector wires often run all the way to that LRU RDCs near the airframe convert I/O and send digital messages
Hardware identity The function is the box in the tray The function is software on a module in a cabinet slot
Failure effect Loss of that LRU loses that function Module or network loss can affect several hosted functions; redundancy is designed in
BITE view Box-level fail flag and shop message Cabinet, slot, hosted function and RDC channel named in central maintenance
- Spares Many unique computers Fewer module types; software load defines the personality
- General arrangement and associated BITE
Level-1 general arrangement, in cockpit and bay terms, is: IMA cabinets in the avionics compartment, often dual or more for dispatch; processing and I/O modules in numbered slots; network switches; power and cooling; RDCs out in the airframe; remaining federated LRUs still on the data network. Crew interfaces (ECAM/EICAS, FMS, displays) may be hosted or may remain separate display units fed by hosted display-management applications — fleet-specific, but always digital-bus-fed rather than a unique analogue loom per instrument.
Associated BITE is reported through the central maintenance computer / centralised fault display (the aircraft’s CMS/CFDS teaching names). Typical messages identify an IMA cabinet, a module type and slot, a hosted function name, and/or an RDC and channel. Trouble-shooting therefore starts with the message topology, not with “swap the warning computer” as if it were still a unique tray. Power, cooling and network links are first-look items because they are shared. Software part numbers and aircraft configuration lists must match the hosted load; an unapproved or mismatched load is an airworthiness event, not a harmless experiment, which is why IMA and topic 5.13 meet at the data-loader.
The MSI blocks from sections 8.1 and 8.2 still exist inside these VLSI modules — encoders, decoders and multiplexers remain the way a module scans discretes and analogue channels — but the line technician meets them as BITE on an RDC or I/O module, not as a 74151 you replace on the bench during a turnaround. That is the scale jump from 5.8/5.9 at B2 level 2 to 5.15 IMA at level 1 for all categories.