OrdinateDB

Company · Ordinate Systems Ltd

The product is free.
This is what we sell.

Ordinate Systems Ltd stewards the OrdinateDB project and sells the work around it. Every engagement is fixed scope with a written deliverable — no time-and-materials drift — run by engineers who spent their careers delivering PI System projects across mining, oil & gas, water, power and manufacturing. The historian changed. The discipline didn’t.

The service lines

01

Migration assessment

SPEC 11 §4

Fixed fee, fixed scope. We take a full inventory of the existing historian estate — tags, asset structure, displays, calculations, interfaces — and write a migration plan with effort and risk stated per item, including the items that don’t migrate cleanly. The plan is yours to execute with anyone: us, another integrator, or your own team. The self-serve version of the process is documented free at /migrate-from-pi.

What you get: a written migration plan — effort and risk per item — that stands on its own, whoever executes it.

02

PI extraction projects

SPEC 11 §4 · SPEC 04 §6

Fixed-scope delivery of the full path: extraction, parallel run, validation. The old historian and the new one ingest side by side, and the acceptance criterion is digit-matching evidence — the comparison report over the parallel-run window. Cutover happens when the numbers agree, not when the calendar says so.

What you get: your history in OrdinateDB and a validation report in which the digits match — that report is the acceptance criterion.

03

Health checks

An existing OrdinateDB install reviewed against the published specs: archive configuration, lifecycle policies, collector redundancy, backup and restore evidence, security posture. The specs are public, so the review criteria are too. Also offered pre-go-live, when a finding costs an edit rather than an outage.

What you get: a written findings report graded against the published specs, remediation ordered by risk.

04

Model & template design

SPEC 01 §3

The asset model and template architecture, designed with your engineers — not for them — so the fleet inherits it cleanly: series, limits, calculations, displays and entry forms defined once and applied everywhere. Get the templates right early and every asset added afterwards is nearly free. It is the highest-leverage week of any deployment.

What you get: a template architecture your own engineers designed with us, own outright, and can extend without us.

05

Training & enablement

Operator, engineer and admin tracks, on site or remote. Operators learn trends and episodes; engineers learn templates, calculations and the asset model; admins learn lifecycle policies, HA and upgrades. All course material cites the specs it teaches. The self-serve path — the docs plus a free demo instance — is a legitimate way to learn the product, and plenty of teams need nothing more.

What you get: a track per role, run against your own instance where possible, exercises left behind for the next hire.

Staffing

SPEC 01/07

Your PI engineers are a week away.

The usual objection to changing historians is not the software, it is the people: the team knows the current system, and retraining sounds expensive. OrdinateDB is deliberately learnable for historian-literate engineers. The concepts map — tag to attribute, AF to templates, EF to episodes — and where they deliberately don’t, the difference is documented with its reason.

We wrote A PI engineer’s guide to OrdinateDB precisely so your existing team stays the expert team. The training path is free: the guide, the docs, and a demo instance to break.

Read the guide
concept map · PI System → OrdinateDB
tagattribute on an asset
AF (asset framework)asset model & templates
EF (event frames)episodes
analysescalculations
displaysgenerated from templates

where the mapping breaks on purpose, the guide says so — and why.

Integrators who want to deliver OrdinateDB projects: write to us.

Describe the estate — tag count, AF depth, interface list if you have it — and we will reply with a scope and a price in writing.