Nexus Aero
Follow us
Stay updated
NEXUS AVIATION JOURNALPractical knowledge · Considered analysis · Clear sources
Practical guideDigital aviation & data4 min read

Connect aviation records without creating a second source of truth

One giant table is not the same as one reliable system. Use stable identities, clear ownership and controlled views so public offers and private work can share facts safely.

Nexus editorialPublished:
Illustrative aviation image; not evidence of a specific item, approval, applicant or customer

Illustrative image—not evidence of a real case or verified capability.

Decide who owns each fact

An airline may already use a controlled maintenance system, an ERP and a stores process. Adding a marketplace should not silently replace those authorities. Begin by identifying who owns the part identity, quantity, technical status, installation relationship and commercial commitment. Different facts can have different responsible systems. A coordination platform may hold a reference or a dated statement rather than the authoritative record itself. Document this distinction before importing data. Otherwise two screens can display plausible but contradictory truths, with users changing whichever is easiest. The goal is a reliable chain of responsibility, not a declaration that one new database automatically governs every aviation and business decision.

Use stable identities and explicit relationships

A part-number definition, a serialized unit, a stock position, an offer and an order are related records, not the same record with a different page title. Keep stable identifiers and link them. An offer can reference the unit and the commercial terms published at that time; an order can preserve the accepted terms even if the seller later changes the offer. A fleet installation links the physical component to a parent and period. It must not create another component merely because the item moved from a shelf to an aircraft. This structure reduces contradictory copies while preserving the history needed to explain a transaction after current data changes.

Publish a projection, not the private record

A public sourcing card and a member's inventory screen can share an underlying identity while revealing very different information. Define the public fields deliberately, including what is masked or omitted, and apply the rule on the server. Hiding a column in the browser is not access control if the full private record is still delivered. The same principle applies to company catalogues, personal profiles and intelligence summaries. A service catalogue may expose a published capability statement without exposing customer work or private approval evidence. An installation record can support internal planning without becoming a public fleet claim. Shared data should make controlled views consistent, not make every fact visible everywhere.

Treat migration as a reconciliation exercise

Before a bulk import, map identifiers, units, dates, conditions and ownership meanings from the source. Keep the source file reference and import batch so a later correction can be traced. Missing values should remain unknown rather than becoming zero, serviceable or today's date. Preview representative rows from each tracking category and review duplicates before saving. Reconcile counts and quantities against the agreed source, including rejected rows and unresolved differences. A successful file upload only proves that a file was accepted; it does not prove that the physical stock, technical status or ownership was correct. Preserve the organisation's approval process for accepting the migrated operational baseline.

Define the event that changes each view

Synchronization becomes clearer when each change has a named event: stock received, quantity reserved, offer published, terms accepted, item dispatched, discrepancy reported or custody returned. Identify which record owns the event and which views must reflect it. Preserve an accepted commercial snapshot instead of rewriting history from the latest inventory description. Handle retries without creating duplicate movements or duplicate orders. Show freshness and reconciliation failures rather than displaying a reassuring stale total. ATA's public standards material illustrates separate records-exchange areas; it does not mean that merely using similar field names implements a standard. Actual integration needs an explicit mapping, validation and responsibility agreement with the counterparty system.

Prove one loop before widening the data lake

Choose one synthetic item and follow it from inventory to a published offer, an accepted transaction, partial delivery and a return. Compare the public, seller, buyer and administrator views. Each should show the permitted facts and the same relevant event history, while private evidence stays private. Then repeat with a service offer that has no physical stock and a fleet relationship that is not a sale. This exposes whether the model understands different business meanings. The aim is a small dependable core that can grow, not a giant table with every future column. Strong identities, provenance and controlled relationships usually matter more than the number of screens or the size of the database.

Sources & scope

This is editorial educational analysis. Licensed manuals are not reproduced; Iranian applicability and independent technical approval are not established. Actual operations require current controlled sources and authorized decisions.

ATA e-Business Program — Standards catalogue — opens in a new tabLimited reference to distinct procurement, material and records-exchange areas. The proposed data model, migration exercise and access design are original engineering guidance, not an ATA implementation claim.Source link checked: 17 Oct 2026

Continue with the Library tools

Related reading

On this page
ONE MINUTE TO THINK

Test the idea, not just your memory

Short learning scenarios with explained answers—not a qualification test, training certificate or operational decision.

Inventory and a public offer share an item identity. Should they expose the same fields?
About Nexus editorial

Educational and analytical writing with explicit references—not maintenance instructions, airworthiness decisions or authority approval. Analysis, news, experience and sponsored content must remain distinguishable.

Suggest a topic or report a correction