« Usages » tab on the part record

The part record (catalogue) exposes a Usages tab that aggregates, in a single view, every reference pointing to this PartNumber — both physical and documentary. It is the inverse view of the catalogue: instead of listing parts, it lists the usages of a given part. Handy for assessing the impact of replacing a PartNumber, tracing where a tool is mobilised, or simply understanding what a catalogue entry is for.

The tab is structured in seven sections, grouped into two blocks: physical usages and documentary references.

Physical usages

Where this PartNumber exists as a real exemplar

  1. Physical stock

    The StockItem rows matching the PartNumber, listed by serial number (serialised mode) or aggregated by storage location (quantity mode). Each row links to the stock record for detailed movements, condition (serviceable, new, quarantine…) and location.

  2. Active installations

    The components currently fitted on an aircraft of the fleet. The table shows the target aircraft, the exact position (employment point), the install date and a shortcut to the aircraft decomposition. Only active installations are listed — removals show up in the history of the relevant stock record, not here.

Documentary references

Where this PartNumber is referenced in the referential

  1. Applicable airworthiness documents

    The airworthiness documents (SB, AD, MOD) whose applicability rule targets this PartNumber — all serial numbers, a specific S/N, or an S/N range. The table shows the kind (SB / AD / MOD), reference and revision, status and S/N scope; a Mandatory badge flags imposed documents, an Excluded badge an exclusion rule (the component is explicitly out of scope). Each row links to the airworthiness document. Essential to know, from the part, which directives/bulletins apply to it.

  2. Employment points accepting this component

    The EmploymentPoint rows (decomposition referential) that accept this PartNumber as a candidate. Each line shows the parent applicable configuration (CA), the ATA code of the employment point, and a Primary flag when the PartNumber is the nominal candidate for that EP. Useful to verify compatibility before installation.

  3. PEA tasks tracking this component

    The MaintenancePlanTask rows with trackingLevel='component' and this PartNumber as their target. This is the list of PEA tasks whose due dates run on the counters of one exemplar of this PN, not the aircraft. Typical for tooling or LRUs with their own cycle.

  4. PRE operations requiring this material

    The MaintenanceOperationMaterial rows (manufacturer Bill of Material) where this PartNumber appears as part, consumable or tooling. The table walks the parent context up: programme (PRE) → task → operation, plus role, quantity and the mandatory flag.

  5. PEA operations requiring this material

    Same on the maintenance plan (PEA) side. An Origin column tells whether the line is inherited from a PRE (« PRE » badge) or added locally to the PEA (« Local » badge). See PRE → PEA synchronisation.

Day-to-day usefulness

  • Before swapping a PartNumber (retire from catalogue, replace with a successor PN): the list reveals every impact point to handle (EPs, component-level tasks, PRE/PEA BOM, stock to burn down).
  • Tooling diagnosis: the « PEA tasks tracking this component » section gives the list of scheduled maintenance to plan for the tool, and the PRE/PEA material sections show where it is mobilised as a means.
  • Part-145 audit: trace where a part or consumable is referenced in the maintenance referential without querying the database directly.

Technical notes

  • The tab exposes no raw ULID: every line embeds the human-readable code (PartNumber formatted PN:NCAGE, name, operation code, PEA name…) with a link to the parent record.
  • Sections are scoped to the current instance: a PartNumber is global to the catalogue, but its usages depend on the active instance (PEA, installations, stock).
  • Each section counter reflects the actual number of entries found (« 0 » when empty — no error shown).

V1 limitations

  • No UI filters: when a section grows too long (large catalogue, heavily-used PartNumber), there is no pagination or filter yet. Planned.
  • No shortcut to create: the view is read-only. To add a usage (e.g. declare the PN on a new employment point) you go through the parent record.

See also