Standards
Standards are configured here, not bolted on.
Most standards do two jobs: they name what an operation is made of, and they set a format for exchanging it. The first is configured onto Selira's model, which is more general than any one standard and was shaped by them. The second needs an adapter — and the adapters are what we are building.
Manufacturing
Where the plan meets operations, and no deeper
Selira works at ISA-95 Levels 4 and 3, where business planning meets manufacturing operations: orders, material and lots, the equipment and people they need, and how each order performed. Below that line it only ever reads, and never writes to control — reading from the floor is the direction.
ISA-95 · IEC 62264
configuration · direction The levels, and what crosses between business planning (Level 4) and manufacturing operations management (Level 3) — the boundary Selira is built for. Its objects — personnel, equipment, material, process segments, schedules and performance — configure onto the model in the standard’s own terms. Where that boundary falls in your plant is your call, as the standard leaves it.
B2MML
adapter · direction ISA-95’s exchange format across the Level 4 ↔ Level 3 boundary: schedules down from business systems; performance, inventory and capability back up. The model has a place for each; the adapter that reads and writes the format is still to build. Today, records arrive through the API and import jobs.
ISA-88 · IEC 61512
configuration · direction For batch plants. Recipes — general, site, master and control — and the batch records they leave, configured onto the model; BatchML, the format that exchanges them, comes with its adapter.
OPC UA · IEC 62541
adapter · direction Reading from the floor, never writing to it: state changes, counts and order events — over OPC UA, or MQTT where a plant publishes that way — kept beside what the plan said. Raw process values stay in the historian. Today, floor events arrive through the API.
Measurement
A quantity is not a number in a column
Measurement is where operational systems quietly go wrong. Selira adopted a full calculus of quantities, on open standards — and it runs today.
Most systems check units inside their own walls; between them — an ERP’s unit code, a unit from the floor, a header in a spreadsheet — nothing does. So readings in different units get added, and figures of different kinds get compared, because both columns were called value.
In Selira a value never travels without its unit and the kind of quantity it is. Figures from different systems compare safely, a reading is checked against the specification in the specification’s own units, and a sum that makes no physical sense is refused rather than totalled.
UCUM · UN/ECE Rec 20
today Units follow the Unified Code for Units of Measure, with the Recommendation 20 codes that trade and manufacturing messages use — so a unit means one thing in every system that reads it.
QUDT
today Quantity kinds follow QUDT, the open vocabulary of what a measurement is — so a length is never mistaken for a duration, whatever its column was called.
Aviation
Parts, manuals and certificates, in the industry's own formats
Airside starts in maintenance and reaches into the airline. The model carries what these standards describe — parts, tasks, publications, certificates, schedules, flight events; the adapters that read their formats are the direction.
ATA Spec 2000
adapter · direction The industry’s data standard for parts: ordering and repair orders, part marking and identification, reliability data and traceability records — read with their origin, so a part’s history arrives as its own statements.
ATA iSpec 2200
configuration · direction The structure of maintenance data and the chapter numbering every hangar speaks — 29-10 is the main hydraulic power — so tasks, procedures and illustrated parts are keyed the way the manuals key them.
S1000D
adapter · direction Technical publications as data modules rather than pages: procedures and parts data read from the module, with its issue, so an answer can say which revision it stood on.
EASA Form 1 · FAA 8130-3
adapter · direction The release certificate a part stands on, held as a certified claim with its issuer and date — beside your approved maintenance records, never in place of them.
IATA SSIM
adapter · direction Airline schedules in the format they are exchanged in, so a maintenance slot and the flying it has to fit around sit in one model.
AIDX
adapter · direction Flight events as airlines and airports exchange them — times, stands, delays — each kept with its source and when it was known.
Why the model comes first
Standards are how your systems already talk to each other, and how integrators and partners will check us. Work aligned with a standard as written can be checked against it without asking us.
They also overlap and change. ISA-95 and Spec 2000 both describe a part, in different words, and each has editions still to come. A model more general than any one of them can carry several side by side and take a new edition as configuration — which is why we built the model first, and build the adapters on it.
Aligned is not certified — yet. We are a young company: where a standard has a scheme to certify against, we intend to go through it, and this page will say when we have.
Digital Twin Consortium
A twin of the operation, not only the machine
Many digital twins mirror an asset: a pump, a press, an airframe. Selira’s model mirrors the operation around it — orders, lots, tasks, certificates — each held with when it was so and where it came from.
Same idea, wider frame: a living reflection, built to stay in step with its sources. That is why Selira is a member of the Digital Twin Consortium, among people who have worked on this far longer than we have. We hope, in time, to bring something back.
Bring the interface between planning and operations that everyone works around.
Most plants have one. It makes a good first question.