OPEN · VENDOR-NEUTRAL · FREE TO IMPLEMENT

One agreed schema for PIA.
One definition of done.

A canonical, community-agreed representation of the PIA process and every piece of evidence a submission carries — the interchange your systems read and write. Built for the build partners, altnets and vendors who implement against it.

// A55 · PIA NOTICE
pia_noi_reference
"NOI-2026-0114"
a55a
point-based · reactive
a55b
stage-based · civil
evidence[]
slot_code + file_hash
infrastructure
24 types → 5 cats
validation
37 rules ✓ pass

WHAT IT COVERS

Everything a compliant submission is made of.

01

Job-type taxonomy

Named for what physically happens on the ground — reactive works, civils — not any vendor’s internal field names.

02

Evidence taxonomy

What is captured, and for A55b at which stage. Every slot carries an explicit code and a content-address file_hash.

03

Validation rules

37 declarative rules that decide whether a pack is complete and compliant — before it is ever submitted.

04

Versioning

Semantic versioning, so the schema evolves without breaking the implementations built against it.

SCOPE

The standard — and what’s built on it.

OpenPIA defines the interchange, not the product. Your systems read and write it — they don’t have to agree on it first, or reverse-engineer one another to interoperate.

IMPLEMENTATIONS

what crews & back-offices actually use

Mobile appsBuild packsSubmission portals

read & write the schema

THE STANDARD

OpenPIA — one agreed schema

A55a · point-based reactive worksA55b · stage-based civil evidence

The shared data model, evidence taxonomy and validation rules — spanning A55a and A55b alike. Vendor-neutral, versioned, and free to implement. This is what OpenPIA is; the app you build and the portal you submit into are yours.

named for what physically happens

GROUND TRUTH

the physical works, captured on site

Reactive worksSurvey & buildBlockagesEvidence

NEUTRAL BY DESIGN

The moment one party owns it, everyone else stops trusting it.

So neutrality is not good manners here — it is the precondition for the schema being adopted at all. No vendor owns or steers it.

01

No single-vendor capture

Decisions are taken in the open, on a public repo — the reasoning recorded, not settled behind a closed door.

02

Royalty-free for anyone

Read it, implement it, and build on it without a licence fee — CC-BY 4.0 for the docs, Apache-2.0 for the schema. The schema is a public good, not a product.

03

Physical reality first

Job types and evidence are named for what happens on the ground, never for a portal’s internal field names.

04

Stewardship, not ownership

Heading toward an INCA-style industry body — many members, no single owner steering the direction.

STATUS: v0.1 · BUILT & VALIDATED

Implement against it today.

The A55a and A55b schemas, the evidence slots, and the validation rules are in place and checked against real submissions. Read it, build against it, and open an issue where it is still thin.