Applied configurations

The applied configuration (CA) describes what is actually installed on an aircraft, as opposed to the AEP which describes what may be installed.

Reading the tree

The CA tree shows a root (the aircraft) and walks down slot by slot. Each node carries:

  • PN:NCAGE — identifier of the expected module type.
  • SN — serial number of the installed instance (empty if the slot is free).
  • Installation date — timestamp of the install, used to compute potential.
  • Occupancy status — Empty, Partial, Complete or Overload (based on the number of instances installed versus the slot’s maximum quantity).
  • Inherited counters — hours and cycles propagated from the aircraft counters.

Bold nodes are containers: they expose their own sub-slots. Click a node to open the detail drawer with the history of installations and technical data.

Occupancy statuses

Each slot’s badge reflects its occupancy — the number of instances installed versus the slot’s maximum allowed quantity:

Slot occupancy status

  1. Empty
    No instance installed (0 / max). Grey badge.
  2. Partial

    At least one instance installed, but the slot is not full. Amber badge.

  3. Complete

    The slot holds exactly its maximum quantity of instances. Green badge.

  4. Overload

    More instances installed than the maximum allowed — an anomaly to fix. Red badge.

This status reflects occupancy, not the condition (serviceable / unserviceable) of the installed modules. An airworthiness non-conformity on an installed instance is flagged separately, via a compliance alert badge on the installation row.

Difference with the AEP

The AEP is frozen by the product design office and carries the variants allowed for each slot. The CA is the reality at a given point in time. Three notable cases of divergence:

  • Waiver — a non-standard PN is temporarily allowed under operational conditions.
  • Modification — a manufacturer kit modifies the local AEP of a specific aircraft.
  • Major evolution — the AEP itself is updated; existing CAs are resynchronised.

The Maintenance programmes module consumes the CA to compute the active limits; see also Fleet for the aggregated view.

API

  • GET/aircraft/:aircraftId/applied-configuration —

    returns the full tree for the aircraft.
  • POST/aircraft/:aircraftId/applied-configuration/initialize —

    initialises the CA from the AEP of the aircraft type.
  • POST/aircraft/:aircraftId/applied-configuration/sync —

    resynchronises the CA after an AEP evolution.