Coming soon · OEM and industrial
We are exploring records for manufacturers: a signed record for each serialized part, connected to your own systems through an API. OEM is in development and is not offered as a standard plan.
SERIALIZATION
Manufacturers already give critical parts a serial number. Outlast would give each serialized part a signed record and a tag that opens it with a tap, using the part numbers and serial schemes you already have, such as GS1 identifiers.
Assemblies, kits and replacement parts would link to each other, so the record shows what is installed where.
TRACEABILITY
In regulated industries such as aviation, a part’s paperwork matters as much as the part: release certificates such as FAA Form 8130-3 or EASA Form 1, inspections, repairs and removals. Counterfeit and unapproved parts get in when that trail is broken.
The planned record would keep each certificate and service event with the part, signed by whoever made it, so a technician can check the trail on the spot.
API AND INTEGRATIONS
Records would be created and updated through an API from ERP, manufacturing and maintenance systems, rather than typed in by hand. Events such as installation, inspection and replacement would post to the part’s record as they happen.
Each integration is scoped as a development project. Nothing here is available yet, and there is no standard plan or launch date.
ACCOUNTS · PLANNED
Planned: a manufacturer would authorize distributors and repair stations to issue records and sign release and service events for its parts. Operators would see the history of what they run, and auditors what is shared with them. Nothing here is available yet.
| ManufacturerWould issue and control the record | Approved partnerDistributor or repair station | OperatorRuns the equipment | AuditorWhen the record is shared | |
|---|---|---|---|---|
| Issue a record for a part | Yes | If the manufacturer allows | No | No |
| Sign release and service events | Yes | If the manufacturer allows | No | No |
| Record installation and removal | Yes | Yes | Yes | No |
| See the full history | Yes | What is shared with them | What is shared with them | What is shared with them |
| Check the tag | Yes | Yes | Yes | Yes |
OEM is not on the standard plans. Access and pricing would be set for each development project.
No safety certification, airworthiness or fitness-for-use decision, interoperability guarantee or live OEM integration is implied.
PROPOSED
Nothing here is available yet. It shows the record we would design together.
Planned record
WHO WOULD BE INVOLVED
HOW WE WOULD START
Agree how part numbers, serials and assemblies map to records, using the schemes you already have.
Decide which systems create records, and which events, such as installation, service or replacement, are added to them.
Agree the evidence, integration and validation work before any operational promise.
Development discussions only, with no launch date or standard plan.