Envergure documentation
The complete help content of Envergure, publicly available and in-app via the F1 key. Organised by topic.
Getting started
Operations
- Maintenance workbenchCentral screen for operational maintenance: open WPs, due limits, CRS signature.
- Projects & KanbanGeneric kanban steering tool: projects, items, configurable columns, drag-and-drop.
- Technical dataCounters, measurements, observations, photos and notes — data model, capture drawer, journaling.
- Data exchangesSteering the interfaces with your partners, and the screen where you rule on what an incoming file is allowed to change. A package never applies while one of its rows awaits your decision.
- Export / compareThe workshop that produces exchange files for your partners — aircraft configuration, location-oriented catalogue, purchase order, receipt confirmation, spare parts list, codification, part number changes, observations — or checks theirs against your data, without ever changing anything.
Fleet
- Module decompositionInstall and remove modules within the applied configuration, counter propagation.
- Applicable configurationEmployment points, compatible parts, and the three codes that identify a location — ATA, CSN, ISN — whose confusion costs the most.
- Station pointingThe configurations that carry stores and how far their pointing has gone; calibrating the underside image (two points + a third mirror guard), positioning stations in metres, explicit symmetry assistant.
- Family categoriesClassifying product families, and the "Carries stores" box that decides which configurations may declare stores stations.
- Operational configurationHanging and unhooking a store with no work package, station compatibilities, counter propagation.
- Operational configurations catalogThe catalogue of authorised configurations: exact match, duplication versus revision, station compatibilities declared upfront, limitations as verbatim restituted text.
- Configuration proposalsWhich authorised configuration needs the least effort for a given aircraft and need: the movement as ranking criterion, realisability against available stock (including technical reception), non-realisable ones never hidden.
- Applied configurationsActual state of the modules installed on an aircraft: tree, statuses, AEP divergences.
- Store drawingAttaching a store silhouette to its reference: two-point calibration (nose and tail), side or underside projection, pair symmetry, and the plan’s three degradation levels.
- Fleet managementList/map/sheet views, aircraft enrolment, lifecycle, multi-base and air-gapped.
- Aircraft lifecycleThe 7 aircraft statuses, why "To enrol" and "Enrolment in progress" cannot be edited by hand, how to start/close an enrolment, how to re-enrol.
Supply chain
- Technical receptionComponent intake workflow: warehouse + technical phases, EASA Form 1.
- Prepare a shipmentTwo-column workbench: item selection with multi-select location filters + container proposal (smallest single or multi-case), segregation, margin, full-screen 3D view, audited casing.
- Transfer notesNumbered transit documents (repair, loan, inter/intra-site transfer, entry/issue): draft → in transit → received → closed lifecycle, generating stock movements.
- Requirements planWhat will you run out of, and when? Requirement derived from the maintenance plan crossed with real stock, three honesty counters, projected stock curve. Read-only screen, no ordering.
- Purchase requestsExpress a need before any commitment: the plan proposes, a human creates. Draft → to approve → approved cycle, with separation of duties — the approver can never be the requester.
- Supplier invoicesReceive supplier invoices in electronic format (Factur-X, CII, UBL) and match them against the order AND the receipt: price, quantity and VAT discrepancies, recorded arbitration, regulatory statuses of the 2026 reform.
- Issued invoicesInvoice a completed order: numberless draft, then issuance that assigns the legal number (continuous, per fiscal year), freezes amounts and produces the downloadable electronic CII file. An issued invoice can no longer be edited.
- Customer quotesPrice a job before committing to it: offer validity, supplementary quote after teardown (revisions), mandatory refusal reason, and conversion into an order that copies the lines verbatim.
- Customer ordersRecord what was promised to a customer and at what price: sold services (no article) or parts, VAT captured at sale time, and the Chorus Pro references to collect with the order so the invoice is not rejected.
- Purchase ordersCommit approved requests into supplier orders: workload to engage, per-supplier consolidation, draft → to approve → approved → sent → received cycle, per-line remainders.
- Stock policiesHow much to keep on hand, per item and per scope (storage > site > instance). Reorder point, min/max, lead time, ABC class — structure and input, no pretence of calculation.
- « Sourcing » tab on the part recordEffective policy, reorder-point suggestion, external sources (catalog⨝ASL, non-approved struck through) and internal, interchangeable group (logistical + contextual technical, to validate).
- Approved suppliers (ASL)Sources whose fitness the organisation has validated (Part-145). Distinct from the catalog: an order is only possible from a valid approved source. Scopes by item, category or ATA; expiries first.
- Sourcing derogationsAuthorize a purchase from a NON-approved source (AOG, single source), but never silently: reason + expiry required, approver, sealed audit. Effective blocking outside the ASL lives in engagement (coming).
- Goods-receipt certificateProof that the ordered supply arrived compliant — the document that justifies paying the supplier. Issued automatically per delivery, with a PDF frozen on the quantities observed that day.
- Receptions to processThe logistics inbox of expected receptions (repair returns and purchase orders). Processing a reception places the item in stock; for an order it settles the remainder, updates the status and issues the goods-receipt certificate.
- Supplier catalogPurchasing offers across all items: price, lead time, vendor ref, packaging, preference rank, validity. Global screen (also editable per item in the Sourcing tab). Admin-secret writes.
- SuppliersA supplier in one line: approval, channel, catalog, in-progress and signals to watch. The approvals / derogations / catalog views also read flat, in this screen’s tabs.
- Approval thresholdsEscalation tiers: an order’s total determines the role required to approve it. Smallest tier whose ceiling covers the amount; above the highest, the top role. Admin-secret writes, sealed audit.
- Occupancy rateFill dashboard: occupancy (item count vs maxItemCount capacity) aggregated by storage → zone, global KPIs, fill bars and breakdown by class (empty/partial/full/over/uncapacitated).
- Component lifecycle recordPDF/A + JSON restitution for M.A.305 audit — DGAC / DSAÉ.
- Zones & quarantineAllowed stock conditions per zone: blocking putaway and condition changes (quarantine, scrap, receiving).
- BuildingsPhysical building of a site (above the storage): optional dimensions, 3D and printable 2D plan, mouse editing (move, rotate, dimensions, add regions/fixtures).
- Building regionsFloor surfaces of a building: storage footprints (realising the storage×building M:N) or greyed neutral surfaces (offices, technical, circulation, obstacle).
- FixturesFurniture placed in a zone: location-bearing units (rack, cabinet, vertical carousel) with bay×level generation, or workshop furniture (workbench, machine, work station).
- Equipment fleetSerialized items and their permanent equipment number (stable across RA:CE re-identifications).
- « NSN » tab on the part recordAn item’s NATO codification number: what its digits say, and why its supply class is checked at entry.
- Contextual variants of a partOverride of a PartNumber’s attributes depending on usage context (family, variant, version, company, BU, aircraft).
Maintenance engineering
- Maintenance programmesPEA, PRE, limit scheduler, lifecycle of a maintenance programme.
- Stores proceduresThe hang or unhook gesture described once: steps, times, tooling, consumables. Degrading scope and a single movement step.
- Support levels (NSO / NSI)Maintenance support-level referential (NSO operational, NSI industrial…), assignable to PRE/PEA tasks. First building block of the rotable repair loop.
- Removal reasons and findingsThe two coded vocabularies of in-service feedback: why it was removed, and what was found. The code makes the fact countable, the note makes it understandable — they add up.
- Repair capabilities (who repairs what)Who-repairs-what referential: internal/external provider × support level × scope (PN/category/ATA) × company/site applicability. Rotable repair-loop routing block.
- Repair orders (rotable loop)Lifecycle of an unserviceable rotable: send to repair (internal or external Part-145 shop), return, serviceable/scrap requalification, and the re-installation safeguard.
- Materials & required resourcesOperation BOM template: parts, consumables, tooling, standard duration per PEA operation.
- Work Order materials & consumptionBOM snapshot on WO creation, 5 statuses, consume/check-out/check-in/cancel actions, planned vs. actual variance, Part-145 §145.A.30 traceability.
- Tooling maintenanceTooling calibration, overhaul and inspection via the same PRE/PEA/DT/OT engine as aircraft. Part-145 §145.A.40.
- BOM PRE → PEA: inheritance and synchronizationThe BOM is defined on the PRE (constructor), inherited by derived PEAs, locally overridable, and synchronizable on user action (preview + apply). Explicit detaching to customize without suffering the sync.
- Airworthiness: SB / AD / MOD, applicability and complianceAirworthiness documents (service bulletins, directives, modifications), per-fleet applicability rules, compliance tracking and due dates, per-individual derogations (aircraft/unit), and work-order generation from sections.
- Supplementary Maintenance Directive (DES)Airworthiness document issued by the operator (DES kind): sub-type, "equivalent to AD", technical level, application deadline — same applicability/due-date/verdict engine as SB/AD/MOD.
- « Usages » tab on the part recordInverse view of the catalogue: where this PartNumber is referenced (stock, installations, employment points, component-level PEA tasks, PRE and PEA materials).
Reference
Administration
- PDF editionsBranding and mentions carried by the produced documents: issuing organisation, logo (PNG/JPEG), palette colours, FR/EN footer mentions, and a preview on a sample invoice. Regulatory layout is not editable.
- Edition templatesVisual layout editor for non-regulatory documents: sortable blocks (drag and drop), data-bound fields as pills (palette, click, {{ autocompletion), anomaly counter, inline preview of the unsaved template, restore to default. Invoice/credit note: appearance frozen at issuance.
- Accounts & sign-inEmail/password authentication (interim, before Keycloak): sign-in, admin/user roles, account management (create, reset password, activate, delete).
- Roles & permissionsLocal access control (pre-Keycloak RBAC): named roles → permissions, 4 system purchasing roles (requester/approver/buyer/receiver separation), user assignment, sealed audit.
- PartnersThe referential of the organisations you exchange with — suppliers, manufacturers, workshops, authorities — and, for each, the exchange agreement: which channel, which messages, what it must answer and within what delay.
- External identitiesThe correspondence table between your identifiers and your partners’. Without it every import is a one-shot: the same partner’s second package does not recognise what the first created, and duplicates it.