Study guide

12.2 Software Configuration Management and Part Numbering

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

12.2 Software Configuration Management and Part Numbering

Key Takeaways Explain This Topic AI

Hardware LRU part numbers identify the physical box; software part numbers identify the loadable software aircraft part (LSAP) actually resident in that box.

The approved configuration is the combination of aircraft identity, hardware identity, software identity, effectivity and embodied modifications — not the hardware data plate alone.

Effectivity states which manufacturer serial numbers, models or modification states a software part is approved to occupy.

The IPC (or equivalent parts data) identifies the authorised software part; the AMM provides the approved loading, test and recording procedure.

Media or distribution part numbers name the carrier; the airworthiness article to verify after loading is the resident LSAP part number.

Last updated: September 2026

12.2 Software Configuration Management and Part Numbering

Once software has been classified and released, airworthiness depends on knowing exactly which programme is on the aeroplane . Configuration management is how design organisations satisfy DO-178C/ED-12C configuration objectives, and it is how Part-145 and continuing-airworthiness organisations prove that the aircraft still matches the type design. The maintenance restrictions historically detailed under topic 5.13 are enforced in the hangar through part numbers, effectivity and approved publications , not through informal filenames.

Hardware part number versus software part number

A hardware part number identifies a physical LRU, module or cabinet: the metal, connectors, circuit cards and any resident firmware that is not field-loadable. A software part number identifies a loadable software aircraft part (LSAP) — the executable, calibration file or database that is installed into that hardware. These identities are not interchangeable :

One hardware P/N can legally host several authorised software P/Ns over its life (different software standards, operator options, or service-bulletin upgrades).

The same software P/N may be loadable into more than one hardware dash number if the type-design holder has shown compatibility.

Changing software does not automatically change the hardware P/N printed on the data plate, which is why software status must be read from BITE, a configuration report, a software status page or a load report , not only from the hardware plate.

Treat the approved configuration as a tuple : aircraft identity + hardware identity + software identity + modification and service-bulletin status. Recording only the hardware P/N after a software load is an incomplete airworthiness record.

Loadable software aircraft parts (LSAP)

Industry practice, reflected in documents such as ARINC 667 guidance for field-loadable software and in certification material on loadable software aircraft parts, is to treat field-loadable software as an aircraft part . That means:

It has a unique software part number (and often a media or distribution part number as well).

It appears in the Illustrated Parts Catalogue (IPC) or equivalent parts data for the aircraft effectivity.

It is procured, stored, quarantined and issued under the organisation’s parts procedures, not as a casual computer file.

Loading it is a maintenance task accomplished in accordance with the Aircraft Maintenance Manual (AMM) or other approved data, not an informal information-technology update.

Students routinely confuse four related identities in examination questions. Keep them separate:

Identity What it names Typical use Common error

Hardware LRU P/N The physical box Removal and installation, IPC hardware chapter, data plate Assuming the plate proves the software standard

Software (LSAP) P/N The resident programme or database Configuration list, software status, post-load verification Using a similar P/N from another fleet or another MSN range

Media / distribution P/N The disc, USB device, file-set or loader package that carries the LSAP Stores, media control, loader prompts Loading media that does not match the IPC software P/N

Hardware–software compatibility Allowed pairings published by the type-design holder AMM effectivity, service bulletin, compatibility matrix “The connector fitted, so it must be right”

Some manufacturers encode a software configuration index or loadable-software information in central maintenance computers so that a printout lists every resident LSAP. That printout is only as good as the last authorised load and the last successful interrogation. If the computer cannot be interrogated, the AMM will state the alternative method — often a front-face display, a dedicated status page, or a loader read-back.

Effectivity

Effectivity is the rule that says which aeroplanes a given software part may occupy. It may be stated by:

  • Aircraft manufacturer serial number (MSN) or line-number ranges
  • Model or variant (for example a different engine, weight variant or flight-control standard)
  • Embodied service bulletin or modification number
  • Operator-unique options that still sit inside the approved type design or an approved change

Loading a software part that is in the IPC for a different MSN range is an unapproved configuration even if the part is genuine, sealed and supplied by the manufacturer for another aeroplane. Effectivity is as much an airworthiness limit as the part number itself. Two aeroplanes of the same type design can legally require different software parts because one has embodied a flight-control software service bulletin and the other has not.

Note

Media is not the part. A compact disc or approved USB device is a carrier . The airworthiness article is the LSAP part number that the AMM tells you to verify on the target after loading. If the media label and the resident P/N disagree, stop; do not release the aircraft.

AMM and IPC control

The IPC (or illustrated parts data) answers: what software part is authorised for this effectivity? The AMM answers: how is it loaded, tested and recorded? Related approved data include service bulletins for software upgrades, airworthiness directives that mandate a software standard, and the operator’s approved maintenance programme references. Part-145 staff use the current revision of that approved data. A workshop notebook, a forum screenshot or a copied file from another operator is not approved data.

Typical AMM software-load tasks require the following sequence:

Confirm aircraft identity and effectivity .

Confirm target hardware P/N, location and, where specified, channel (left/right, A/B, COM1/COM2).

Confirm the authorised software P/N from the IPC, service bulletin or airworthiness directive as applicable.

Use approved media and the specified data loader (often ARINC 615 or ARINC 615A ).

Carry out the integrity checks specified in the task.

Verify the resident software P/N on the target or via the central maintenance system.

Record the load in the technical log and aircraft records, including software P/N, media identity, date, and who accomplished and who inspected where dual inspection is required.

Configuration management also forbids uncontrolled mixing . Flight-control channels, dual flight-management databases and IMA hosted applications often have compatibility sets . Loading Channel A to one standard and Channel B to another, or mixing a navigation-database cycle with an incompatible operational programme, can produce comparator faults — or worse, undetected disagreement.

Continuing-airworthiness organisations

The CAMO (or equivalent continuing-airworthiness organisation) owns the configuration baseline for the fleet: which software standards are embodied, which service bulletins are open, and which aircraft may accept a given LSAP. The maintenance organisation executes the load. If the two are not coordinated, a technically successful load can still place the aircraft outside the operator’s approved configuration. Release to service after a software load is a statement that identity, effectivity, procedure and records all match.

Stores control belongs in the same story. An LSAP issued from quarantine with a goods-inwards check against the purchase order is a controlled part. A file copied onto a personal USB device in the crew room is not. Electronic distribution systems used by some operators are acceptable only when they remain inside the approved procedure: access control, virus checking as specified, checksum or signature verification, and retention of the issue record.

Category B3 Level 1 knowledge is the recognition that software has part numbers and must not be swapped casually. Category B1/B2 Level 2 knowledge is the ability to use AMM and IPC effectivity, distinguish hardware from software identities, and record LSAP status as an airworthiness artefact.

Loading diagram... Software configuration control from type design to aircraft records