# Co-build a rail transport ontology

Canonical: https://codeatoms.ai/co-build/rail-transport/
Publisher: CodeNinja Atoms (https://codeatoms.ai)
License: CC BY 4.0

Track, rolling stock, signalling and the works programme are measured by different teams, and a condition record rarely reaches the people planning the work.

Recommended path: no rail transport design is published yet, so the first one is built with a partner, starting from the published neighbours.

## What we bring

- Nearest published work: [Field Ledger: An Open Source Agriculture Data Dashboard the Operator Fully Owns](https://codeatoms.ai/farm-data-dashboard-pakistan/) (agriculture and earth observation, Pakistan)
- Nearest published work: [Reliability Atlas: A Plant Reliability Assessment Study the Operator Can Audit](https://codeatoms.ai/plant-reliability-assessment-saudi-arabia/) (energy and utilities, Saudi Arabia)
- Nearest published work: [Steel Count Ledger: Independently Counted Production for Every Steel Mill in Pakistan](https://codeatoms.ai/steel-production-count-pakistan/) (heavy industry and construction, Pakistan)
- Nearest published work: [Port Twin: One Governed Digital Twin for Every Asset, Feed and Dollar](https://codeatoms.ai/port-digital-twin-us/) (maritime and ports, United States)
- Nearest published work: [Loop Integrity Watch: Ending Distorted Radar Level Readings and Tank-to-Tank Swapping Across the Tank Farm](https://codeatoms.ai/tank-gauge-integrity-pakistan/) (oil and gas, Pakistan)
- Praxis, the platform every design is made on: https://codeatoms.ai/praxis/
- Hyper Ontology, which stands an object model up over the operator's own systems: https://codeatoms.ai/hyper-ontology/

## What you bring

- The operation: One plant, terminal, mine, farm or network, and the outcome you want from it, in your own words. One operation, not a programme.
- The systems that already hold the records: Control systems, maintenance and ERP records, cameras, inspection sheets, whatever already exists. Nothing new has to be bought to start.
- One engineer who knows the place: Somebody who can say what an alarm really means on your site and where a number comes from.
- Where the data may sit: Your rule, not ours: in country, on your own hardware, air gapped, or in a region you name.

## What comes out

- A reference architecture for your operation: Sensing, edge, compute, the models and their licences, the sizing arithmetic and the three year cost against the alternatives.
- An object model you own: The operation written as objects and links in the hyper-ontology/1 package format, ready to load into Hyper Ontology over your own systems.
- A document your own engineers can argue with: Every number sourced, every choice stated against what it was chosen over, and the approvals and human control written down.
- Published or private, your call: Every design published on this site has the operator removed. Yours is published the same way, under CC BY 4.0, or stays private.

## Questions

### What does co-building an ontology mean?

CodeNinja Atoms designs the physical AI system for one of your rail transport operations and writes the operation as an object model you own, in the hyper-ontology/1 package format. You bring the operation, the systems that already hold its records and one engineer who knows the site. You get the reference architecture, the object model, the sizing arithmetic and the three year cost.

### Does our data leave our country?

That is your rule, not ours. Every published design is sovereign by default: open weight models on hardware the operator owns, in country, air gapped where the operation requires it.

### Is there already a rail transport design to read?

Not yet. 13 designs are published across 5 other sectors, and the nearest ones are linked on this page. The first rail transport design is built with a partner.

Ask to co-build: https://codeatoms.ai/co-build/rail-transport/#ask
Every sector: https://codeatoms.ai/co-build/