Export / compare

The workshop produces an exchange file for a partner, or checks theirs against your data. It is the second entry of the Interoperability section: the Data exchanges cockpit follows what circulates, the workshop makes or compares.

Why a separate workshop

File exchanges do not mix with business screens. An aircraft page is there to follow the aircraft, a delivery record to receive goods: an export button at the bottom of each scattered exchanges across as many screens, and nobody knew where to look any more. Here, every message you can produce on demand is in one place, and every package produced shows up in the cockpit journal.

Three steps

  1. The message — what you want to exchange. Messages come in two families: those about a specific object (an aircraft configuration, the location-oriented catalogue of an applicable configuration, a purchase order, a receipt confirmation) and those that issue a selection the product builds itself (spare parts list, codification request, part number change, observations).
  2. The object — the aircraft, configuration, order or delivery concerned. The picker only offers what suits the message. A message that issues its own selection has no object: you go straight to the action.
  3. The action — export, compare, confirm, or produce.

The message and the object live in the page address: “export the configuration of that aircraft” can be shared as a link, and comes back with the back button.

Export, compare

Export opens an outbound package and produces the file, in one action, on the format’s outbound flow (declared once in the cockpit). The package produced is named; its reference leads to its screen, where the file is downloaded.

Compare reads a received file and checks it against your data. It changes nothing: a difference is resolved by a real, traced business action, never from a file. The verdicts are the same everywhere — different, only in the file, only on our side, identical — differences first, identical positions folded behind their count.

Aircraft configuration (S2000M seripd)

Pick the aircraft, then one of the two actions. The workshop talks with a manufacturer or an authority about what is installed on this aircraft, by serial number and by position.

  • Export configuration opens and produces a batch on the outbound configuration flow (declared once in the exchanges cockpit). The aircraft is identified by its manufacturer serial number; the registration travels as a remark. Each position carries the installed part — part number, CAGE, serial number — and its installation date; sub-modules installed in an equipment follow.
  • Compare with a received file matches the configuration sent by the partner against yours, position by position: different, only in the file, only on our side, identical. Discrepancies first; identical positions unfold on demand.

The comparison changes nothing. A discrepancy is resolved by an actual, recorded installation or removal — never from a file: creating installations from what a third party says would fabricate a history that never happened. A file describing another aircraft (another serial number) is refused rather than compared.

How a position is identified. The figure carries the employment point’s ATA (72-00-00), the item carries its CSN (A3020). This is our convention: if a partner numbers differently, it is agreed with them. Not sent, and the batch report says so: a position without ATA or CSN (fill them in the applicable configuration), a store on a station (a stores station is not a catalogue item), and a part housed in an equipment without a recorded installation (no position, no date).

Location-oriented catalogue (S2000M locipd)

Pick the applicable configuration, then one of the two actions. It travels as an illustrated catalogue: figures, items (the positions), and at each item the admitted variants with their ISN and interchangeability codes (ICY).

  • Export catalogue opens and produces a batch on the outbound “location-oriented catalogue” flow (declared once in the exchanges cockpit).
  • Compare with a received catalogue matches a manufacturer’s catalogue against this configuration, position by position and variant by variant: another part at the same ISN, another PIY or SIY code, a variant missing on one side.

The comparison changes nothing. Updating the configuration remains a human action, point by point, knowingly. Automatic intake of a manufacturer’s catalogue will come, but on a real file.

Same rules as for an aircraft configuration: the figure carries the ATA, the item carries the CSN. Not sent, and the batch report says so: a point without ATA or CSN, a stores station, and a variant without ISN — the schema requires it, fill it in.

Producing a message on its flow

For the purchase order, the spare parts list, the codification request, the part number change and the observations, the action is Produce the package: the package opens on the message’s outbound flow, then the file is written, checked against the schema and stored.

The flow is never picked at random. One active flow carries the message: it is taken, and named on screen. Several: you choose — observations go to the manufacturer of the flow, and a wrong choice would send them to someone else. None: the screen says so and leads to the cockpit, where a flow is declared once and for all.

An order goes through its supplier’s channel. Only that supplier’s flows are offered; failing that, a flow with no declared partner serves as a generic channel. Never another supplier’s. The picker only offers approved orders or beyond: a draft, or an order awaiting approval, would get delivered what nobody has committed yet.

A refused production leaves the package open. File rejected by the schema, empty selection: the reason is shown, with the package reference. Fix the data at fault, then produce it from its screen — no need to open a second one.

What each message carries, and what it leaves out, is described in Data exchanges.

Receipt confirmation (S2000M shipmentinf)

Pick the delivery: the picker only offers purchase-order deliveries where something has actually arrived — with no received quantity there is nothing to confirm, and the server would refuse. One action, Confirm to supplier: the product finds the supplier’s flow, opens the package and produces the file. What the message carries, and what it leaves out, is described in Data exchanges.