Operational configurations catalog

This page describes the catalogue of authorised operational configurations — not what a given aircraft carries right now. For the configuration actually hung on a specific aircraft (hooking up, unhooking, compliance), see Decomposition and its “Operational configuration” page.

The catalogue, not the reality

Notion	Answers	Where to see it
Authorised configuration	Which station → reference combinations are published and approved?	This page — the catalogue
Actual configuration	What does this aircraft carry, right now?	Aircraft sheet, Configuration tab
Compliance	Does the actual configuration match an authorised configuration?	Aircraft sheet, computed at read time

Authorised operational configuration: A station → reference combination, published and approved by a document (flight manual, clearance sheet), applicable to certain individuals (family, variant, version), carrying its own limitations. One entry of the catalogue.

An authorised configuration only exists because a document validated it: each configuration’s Source document field (reference + revision index) carries the trace of that document. Nothing is catalogued without one.

Exact match makes duplication the everyday move

An actual configuration is compliant if, and only if, it matches an authorised configuration EXACTLY — neither a subset nor a superset. Leaving a station empty makes a different configuration, which must itself exist in the catalogue to be authorised.

This exactness has a direct consequence on data entry: there is no “generic” configuration that would cover several close combinations. Two configurations that differ by only one station, or by only one reference on the same station, are two distinct entries of the catalogue. That is why duplication is the most frequent gesture: start from an existing, close configuration, copy it under a new code, then adjust the line or lines that differ — rather than re-entering an entire configuration for every variant.

Create a configuration by duplication

Find a close configuration
In the catalogue, locate the configuration closest to the one you want to create — same family of stations, neighbouring applicability.
Duplicate under a new code
The “Duplicate” button opens a deep copy (stations, applicabilities, limitations) under a NEW code you choose, revision A, status “Planned”.
Adjust, then publish
Edit the lines that differ, fill in the source document, then flip the status to “Active” once the configuration is ready to serve as a compliance reference.

Duplicating is not revising

Two gestures look alike on the surface but answer opposite needs:

Duplicating creates an independent configuration, under a new code. That’s the gesture described above — one more variant in the catalogue, with no functional lineage to the original beyond its initially copied content.
Revising creates a new revision of the same code, which supersedes the previous one (which automatically flips to “Superseded”). That’s the act to perform when the source document itself changes — a new edition of the flight manual, for instance — and the configuration must stay identified by the same code across its successive editions.

What flew under the old revision stays true: compliance checks already recorded are not rewritten when one revision supersedes another.

POST/operational-configurations/:id/revise —

Refuses the revision (409) if the source configuration is already “Superseded”, or still “Planned” — only an “Active” configuration can be revised. The error message is shown verbatim: it explains why.

Station compatibilities must be declared FIRST

No separate stores referential exists: a store is an ordinary catalogue article, and it is the compatibilities declared on the station (in the applicable configuration) that say what it may carry. That single declaration serves twice: it filters the reference picker when building a catalogue line, and it guards the physical hook-up on the aircraft.

Direct consequence on entry order: a station’s compatibilities must be declared before it can be used in an operational configuration. The creation form shows the number of admitted references next to each station, and disables the ones with none — rather than offering an empty reference picker. See Applicable configurations to declare those compatibilities.

Limitations are text, never a calculation

Every configuration can carry limitations — maximum load factor, limit speed, any constraint the source document states. The value entered is free text restituted verbatim: Envergure does not compute it, does not check it, does not compare it to anything. That is what makes tenable the absence of any mass or centre-of-gravity engine on this page — the application only claims to compute what it can actually compute.