Railway parts traceability, from manufacturing to disposal

A bogie, a relay or a compressor passes through the hands of the manufacturer, the integrator, the operator and maintenance workshops for decades. Trainparts.online gives each part a unique GS1 identity and a shared history, so that everyone can find out what happened to it with a single scan.

Identify every part unambiguously

Traceability starts with reliable identification. Trainparts.online applies the identification levels defined by the GS1 application standard “Identification of parts and components in the rail industry” (version 1.0, December 2016):

  • the part category, identified by its GTIN (AI 01);
  • the production batch: GTIN + batch number (AI 10, up to 10 characters);
  • the serialised instance: GTIN + serial number (AI 21, up to 18 characters, unique for a given GTIN);
  • the individual asset: GIAI (AI 8004, up to 30 characters), for equipment managed as fixed assets;
  • the refurbishment batch: workshop GLN (AI 416) + refurbishment lot (AI 7020).

A complete life-cycle history

Every step in the life of a part is recorded as a dated event, linked to the organisation that performed it and, where relevant, to the location (GLN).

  • production, shipping, receipt;
  • installation on a parent assembly, removal;
  • inspection, maintenance, repair, refurbishment, test;
  • usage readings (kilometres, hours, cycles);
  • (re)marking and disposal.

A shared, tamper-proof log

The event log can neither be modified nor deleted: a mistake is corrected with a new event, never by rewriting history. This is what allows manufacturers, integrators, operators and workshops to rely on it.

The holder of the part is updated automatically: a shipment makes the receiving organisation the holder; a receipt, an installation or a refurbishment makes the recording organisation the holder.

Share without losing control of your data

Each organisation remains the owner of its data. The owner of a product decides which customers and partners it is shared with; the current holder of a part and the players who recorded an event on it have access to it. Access rules are enforced in the database itself, including for API exchanges.

Who is it for?

Component manufacturers, system suppliers, rolling stock integrators, railway operators, infrastructure managers, maintenance workshops (MRO) and logistics providers: each records the events that concern it and consults the history relevant to its business.

Frequently asked questions

What is the difference between a batch number and a serial number?

A batch number (AI 10) groups parts produced under the same conditions; a serial number (AI 21) identifies a single part. To follow the maintenance history of a specific part, serialisation (or a GIAI) is required.

Can an event recorded by mistake be corrected?

No: the log is tamper-proof. A new event is recorded to rectify the situation, so the history keeps track of the correction.

Who can see a part's history?

The product owner, the organisations it was shared with, the current holder of the part and the organisations that recorded an event on it.

Join the platform

Create your organization in minutes and invite your partners.