Fleet management

The Fleet is the overview of the aircraft managed by an Envergure tenant. It aggregates operational statuses, applied configurations and potential indicators.

Available views

Three main views

  1. List

    Filterable, sortable table: registration, type, status, last open limit. Ideal for weekly fleet reviews.

  2. Map

    Geographic d3-geo view of operating bases and known GPS positions. Shows deployed aircraft and their colour status. A Code / City toggle (top-left) chooses the label shown under each base: its code (default, e.g. BA118) or its city (e.g. Mont-de-Marsan).

  3. Aircraft sheet

    A page with collapsible sections (not tabs): counters & potentials, maintenance limits, airworthiness compliance, recent WPs, documents and assigned plans. The Decomposition (applied configuration) and Edit buttons open dedicated views. All the intelligence about an aircraft in a single place.

Enrolling a new aircraft

Enrolment is a two-step process: the aircraft is first created with its registration and product version, then an enrolment dossier (WP of kind enrolment) is opened to drive SN capture and initial counter readings from the Workbench.

Creation then enrolment

  1. Aircraft creation

    Registration, manufacturer serial number (MSN), target product version (family → variant → version), and optional links (owner company, operator business unit, current site). The aircraft is born in the “To enrol” status. API: POST/aircraft.

  2. Open the enrolment dossier

    From the aircraft sheet, click “Enrol aircraft”. The modal creates a WP of kind enrolment bound to a workshop; the status moves to “Enrolment in progress”.

  3. Initialise the applied configuration

    From the Workbench, the “Initialise applied configuration” button creates an empty CA from the source decomposition of the product version.

  4. Capture SNs per employment point

    In the CA tree, each empty employment point accepts a free-text SN entry that atomically creates the StockItem and the installation. This is the enrolment-specific install mode (create), distinct from the maintenance install mode (pick against inventory).

  5. Initial counters

    Inherited counters (hours, cycles) are captured on the aircraft via POST/aircraft/:aircraftId/meter-readings. Each installation freezes a MeterSnapshot recording the SN’s origin value.

  6. Close the enrolment dossier

    “Terminate maintenance” button in the Workbench → WP transition to completed. The aircraft status moves to “In service” and the aircraft becomes schedulable.

Aircraft lifecycle

Seven canonical statuses; transitions are triggered by business operations (WP creation, WP transitions, site/operator transfers). The immutable audit log keeps the full history.

  • To enrol (to_enrol) — aircraft created, waiting for the enrolment dossier to be opened.
  • Enrolment in progress (in_enrolment) — an enrolment WP is active (in_progress).
  • In service (in_service) — flight-ready, active limits, schedulable.
  • In maintenance (maintenance) — a curative / preventive / mixed WP is in progress.
  • In storage (storage) — pulled out of operations without being retired.
  • Transferring (transferring) — moving to another site or operator.
  • Retired (retired) — definitive fleet exit, kept for traceability.

A re-enrolment remains possible on an aircraft “In service”, “In storage” or “Transferring” through the admin action “Re-enrol” (POST /aircraft/:id/mark-to-enrol) — useful to rebuild a configuration from scratch after a major industrial overhaul.

For the full transition matrix, who triggers what, and why some statuses cannot be edited by hand, see Aircraft lifecycle.

Multi-base and remote deployment

An Envergure tenant can manage several bases. Each base carries its own stocks and storage, but aircraft and their CAs are shared at the tenant level.

In air-gapped mode, a remote tenant runs in complete autonomy. Resynchronisation on the next connection is handled by the federation module (out of scope for this page).

See also