The Nexus operating catalogue
Connect the requirement. Coordinate the work. Keep the evidence.
AeroChain brings sourcing, inventory, Component Pooling, MRO and operational coordination into connected workspaces. Start with your aviation requirement, see the relevant pathway and understand who must approve each next step.
The common service loop
01Capture
02Qualify
03Orchestrate
04Decide
Nexusconnect · control · learn
The common service loop
One control pattern, adapted to the job at hand.
Nexus does not force procurement, MRO, Pooling, and AOG into one generic form. It gives each service its own technical detail while preserving one accountable path from intake to evidence-backed closure.
- 01Capture
Record the need, asset, capability, or future requirement.
- 02Qualify
Check organization, technical scope, evidence, and eligibility.
- 03Orchestrate
Connect demand to inventory, MRO capacity, or a Pool pathway.
- 04Decide
Compare options, record acceptance, and preserve accountability.
- 05Release
Reveal the right counterparty and data only at the approved gate.
- 06Learn
Monitor execution, evidence, exceptions, and the next decision.
The public surface explains the service. The controlled workspace carries the accountable record.
A shared prerequisite, not another product
Identity, organization representation, role, evidence and subscription scope are checked before the relevant action. Account creation or purchase does not grant operational authority or aviation approval.
Explore the access applicationCore service lanes
A connected operating catalogue for the work that keeps aircraft moving.
Stakeholders can enter through the job they need to accomplish, while Nexus keeps the relationships, records, technical evidence, commercial choices, and execution milestones connected underneath.
10product families8 governed or early access · 2 roadmap
01
AC01Marketplace & Sourcing
Turn a parts or service requirement into a structured sourcing conversation with a traceable decision history.
One clear technical requirement
What enters
- P/N, S/N, ATA, aircraft, engine, or APU context
- Quantity, condition, due date, priority
- Required documents and technical notes
Nexus controls
- Corporate users act within their organization role. Independents may submit their own enquiries without representing an organization.
- Public discovery does not disclose private stock, counterparties or protected evidence. An enquiry is not a purchase approval or an entitlement to receive protected information.
02
AC02Inventory & Warehouse
Connect material records, locations, movements and supporting evidence before making inventory available to another workflow.
A consistent material and location record
What enters
- Material identity and condition
- Custody, availability, and allowed modes
- Traceability and release evidence
Nexus controls
- An organization workspace, inventory permission and applicable site and evidence controls are required.
- A record in Nexus does not establish ownership, serviceability, airworthiness or installation eligibility. Personal accounts do not acquire organizational inventory authority.
03
AC03Component Pooling
Bring eligible component contributions and operational demand into a governed shared-resource programme.
Clear contribution and participation conditions
What enters
- Eligible idle or surplus component
- Condition, traceability, and availability
- Permitted commercial modes
Nexus controls
- Corporate access alone is insufficient: the relevant Pool programme, participation terms, contribution evidence and allocation authority must be satisfied.
- Joining Nexus does not guarantee stock, immediate allocation or dispatch. No automatic allocation, pooled ownership or aviation release is implied.
04
AC04AOG & Continuity
Coordinate urgent requirements, response evidence and accountable handoffs when operational continuity is under pressure.
A shared urgency and requirement record
What enters
- Aircraft and component context
- AOG severity, target recovery, and location
- Duty ownership and response constraints
Nexus controls
- Authorized organizational participation, an applicable AOG scope and named decision owners are required.
- No guaranteed recovery time, emergency dispatch service or substitute for operator safety decisions is promised.
05
AC05MRO Operations
Connect quotation, work intake, planning, technical execution, quality review and customer follow-up around the same maintenance record.
Continuity from quoted scope to work record
What enters
- Technical scope and acceptance criteria
- Capability, capacity, and certifying authority
- Materials, tooling, and required evidence
Nexus controls
- An MRO organization profile, reviewed capabilities and specific staff authorities are required. A customer may follow their own work without acquiring maintenance permissions.
- Software access, payment and Super Admin status do not confer certifying-staff authority or replace independent inspection and maintenance release requirements.
06
AC06Planning & Readiness
Connect future material and maintenance requirements to available evidence, unresolved dependencies and named decisions.
Structured future-demand visibility
What enters
- Forecast or scheduled requirement
- Due windows, quantities, and confidence
- Fleet, consumption, or maintenance context
Nexus controls
- Planning permissions and organization-scoped information are required; each downstream action has its own evidence and authorization gates.
- A planning signal is not a confirmed reservation, certified forecast, automatic procurement order or maintenance approval.
07
AC07Execution & Aftercare
Carry an authorized decision through obligations, handoffs, completion evidence, exceptions and aftercare.
A shared obligation and milestone history
What enters
- Released counterparty and transaction context
- Milestones, receipts, exceptions, and evidence
- Usage, outcomes, and service performance
Nexus controls
- Execution is bound to the underlying authorized case. Independent users may follow their own enquiries, but cannot release organizational execution or custody actions.
- A recorded milestone is not proof of payment settlement, customs clearance or technical acceptance. Protected disclosures remain separately controlled.
08
AC08Intelligence & DNA
Understand source-bounded aircraft, airline and airport relationships, with a clear separation between public aggregates and protected analysis.
Connected fleet and network context
What enters
- Explore the public aggregate projection
- Read source scope and freshness limitations
- Use permitted member tools after access checks
Nexus controls
- Public aggregates are available without buying organizational authority. Member tools require the applicable entitlement and identity scope.
- Dataset presence does not prove current operating authority, airworthiness or schedules. Public pages do not expose private aircraft records or member exports.
09
AC09Technical Assets & Tooling
A planned governed workspace for equipment identity, custody, calibration, inspection, servicing, reservations and toolkit readiness around authorized maintenance work.
Equipment identity and custody continuity
What enters
- Identify the equipment and responsible organization
- Review custody, condition and current evidence
- Reserve or restrict it for an authorized work need
Nexus controls
- This family is planned and is not yet available to purchase. Its future use requires organization ownership, authorized roles and accepted equipment evidence.
- A Nexus equipment status will not replace calibration certificates, approved tooling procedures, maintenance data or certifying-staff authority.
10
AC10Quality & Assurance
A planned evidence-led workspace connecting audits, findings, containment, corrective actions, independent review and controlled procedure revisions.
Traceable findings and corrective-action ownership
What enters
- Record the finding and immediate containment
- Assign cause analysis and corrective action
- Complete independent review and effectiveness check
Nexus controls
- This family is planned and is not yet available to purchase. Future workflows require an organization-owned quality scope, accountable roles and accepted evidence.
- Nexus will coordinate evidence and decisions; it will not issue regulatory approval, certification, maintenance release or substitute for an approved quality system.
Choose the job, not a generic account type
Every participant sees a useful path into the network.
Organizations can hold several identities. The first useful question is what the team needs to accomplish today—and which service lane should be activated next.
I need material or repair capacity
Start with a structured request, then monitor options, decisions, release, and execution.
Open demand pathI can repair, supply, or fulfill
Register capability and capacity, receive qualified opportunities, and respond with controlled offers.
Open capability pathI own idle inventory
Centralize eligible material and choose whether to offer Sale, Loan, Lease, Exchange, or Repair Support.
Open Pooling pathI need network evidence
Review operational performance, Data Quality, subscription usage, and governed improvement signals.
Open intelligence pathExpansion rails
The launch core can grow without losing its operating center.
Adjacent services are deliberately shown as connected future lanes. They should reuse the same organization, evidence, release, execution, and analytics controls rather than becoming disconnected products.
Logistics coordination
Extend execution milestones into freight, handover, customs, and delivery visibility.
Finance & insurance pathways
Add qualified partner workflows around risk, payment terms, and asset support.
Training & technical services
Make specialist knowledge, training capacity, and advisory services discoverable.
Enterprise integrations
Connect approved ERP, MRO, inventory, and data-exchange systems when the operating model is ready.
Future lanes are visually mapped, not represented as live capability until their contracts, data, and operating controls are connected.
A shared operating center for civil aviation
Bring the next maintenance or supply decision into the network.
Nexus is designed to make demand, capacity, technical evidence, and execution visible to the right participants—at the right stage—with the right controls.