Primmel

Executable standards modelling

Standards are
programs, not PDFs.

Primmel turns ISO, BSI, and OIML standards into typed, machine-readablerunnable models. Process flows, data requirements, and evidence, in one plain-text .prl file.

Try it now →Get started
hello-world.prl
root HelloWorld
metadata {
  title "Hello World"
  namespace "HelloWorld"
}

role Greeter { name "Greeter" }

start_event Start { }
end_event Done { }

process Greet {
  name "Greet the world"
  actor Greeter
}

canvas Root {
  elements {
    Start { x 0 y 0 }
    Greet { x 0 y 100 }
    Done  { x 0 y 200 }
  }
  process_flow {
    E1 { from Start to Greet }
    E2 { from Greet to Done }
  }
}
One model. Five pillars. Full lifecycle.Understand the architecture →

Today

Standards as documents

  • PDFs that humans must read and interpret manually
  • Compliance checked by hand, slow, error-prone, subjective
  • Evidence scattered across systems, hard to trace
  • Updates require re-distributing hundreds of pages

With Primmel

Standards as programs

  • Typed .prl models a computer can parse and run
  • Process flows execute, automatic, deterministic, repeatable
  • Evidence built in, every requirement carries hooks
  • One source file: update once, everyone sees the change

Architecture

Five pillars, one lifecycle.

From the moment a reference model is published to the moment an auditor hands down a verdict, each pillar has a distinct actor and a distinct artifact.

Why Primmel

Built for the work standards actually do.

01

Executable standards

Process requirements and data requirements expressed in a language a computer can read and run — not just a document humans have to interpret.

02

Single source of truth

One canonical model per standard. Auditors, implementers, and certifiers all read from the same artifact.

03

Mapping and extension

Map your own processes and controls onto any Primmel-modelled standard. Reuse, extend, and specialise without forking the source.

04

Process and data primitives

Built-in primitives for classes, processes, gateways, provisions, and measurements.

05

Evidence built in

Every requirement carries evidential hooks. Auditors locate compliance evidence by following the model.

06

Open and vendor-neutral

A public language, available for any standards organisation to adopt.

Start modelling your standard in minutes.

Read the introduction, then build your first .prl model.

Get started →Browse examples

The Primmel SMART platform

One language, one platform. The platform is its component technologies, each real today, and each program built on it is a full SMART program in its own right, on its own site.

The components

The programs