Skip to content
DRAFT⚠OIML SMART pilot programme · internal use only · all documents and specifications are drafts and may change without notice

Use Cases

Certification, told as stories: who does what, what the system computes, and what lands on the record. Every story walks the live demo, not a mock-up.

What you do today

A type evaluation is a project run on files and folders: the application as a scanned form, the test schedule as a spreadsheet, the test report as a document assembled by hand, the certificate as a PDF. Progress is tracked by asking, and the audit trail is whoever kept the email thread.

What changes

The evaluation becomes one shared record the applicant, the laboratory, and the authority all work in. The forms derive from the Recommendation's model, the evidence attaches to the test it proves, the verdicts are computed, and the certificate is issued from the same record. Nothing is re-typed, and the record itself is the audit trail.

Who to talk to

Write to info@oimlsmart.org to walk through any of these stories with the programme team.

The stories

Type evaluation, end to end

The canonical arc as one continuous story: apply, review, dispatch, test, evaluate, decide, issue, publish to the register, verify anywhere. The five demo flows as chapters, the per-role pages linked.

Read the story →

The certification walkthrough

The hands-on companion: every role’s console walked step by step — file, review, request, ship, test, evaluate, issue — with on-demand role switching, stage jumping from anywhere, and the sample custody chain.

Read the story →

The sample lifecycle

One sample, one story: registered, shipped with tracking, received, held, tested, and returned, retained or disposed — with the branch flows for the damaged, the lost and the replaced, and the gate that refuses to close while custody stands open.

Read the story →

The deployment-mode matrix

One codebase, four postures: the CS-operated platform, IA-only, TL-only, IA+TL. What each runs, who signs in, what federates where, and the start-small path.

Read the story →

Continuous compliance via the twin

The SMART+ story: the instrument’s live twin monitored against its Recommendation’s promises, evidence accumulating for audit, suspension semantics when a promise breaks. Roadmap-anchored.

SMART+ · roadmap-anchored

Training on the SMI Simulation

Rehearse the full test program on a simulated instrument before touching hardware; the platform drives the twin directly, and the bench keeps the truth visible.

Read the story →

The member-state view

The designation chain as the honest registry story: your authorities and their scopes, the issued work on the public register, the utilizers’ access, verification without an account.

Read the story →

The additional-national-requirements flow

ANRs on top of the Recommendation: the Primmel-defined path and the tick-a-box path, moderated declarations, the dispatch and the certificate covering the declared set.

Read the story →