01Step
Submit
Upload your TMH-18 dataset (UTF-8 CSV today, additional formats on the roadmap). Up to 50 MB per file; the ingest schema maps headers to the TMH-18 field set, full reference in the documentation.
Road-asset data,
certified on co-sign.
A validation pipeline for the COTO TMH-18 standard. Submit, run the rules, co-sign with a registered engineer — receive a cryptographic certificate any third party can verify.
Pre-pilot · South African road authorities, consultants, contractors
Telemetry · Live from the platform
Recomputed on every page load · Counters fill as pilot organisations submitWhat the pipeline has done so far.
0Rows validated
0Submissions
0SLA hit rate
0Avg turnaround
How it works
Submit, validate, certify.
Three deterministic steps between a raw CSV and a third-party-verifiable certificate. Every action — every override, every co-sign — is written to an immutable audit log.
02Step
Validate
The rule engine runs structural and domain checks on every row — required headers, encoding, monotonic chainage, deflection ratios, temperature correction. Warnings can be overridden with a justification; every override is recorded in the immutable audit log.
03Step
Certify
A principal engineer co-signs. The platform hashes the stored file bytes (SHA-256) and issues a verifiable certificate at tmh18.com/verify — no login required for the public verifier.
Standard alignment
The standards that govern us.
Meridian/V is built around the Technical Methods for Highways (TMH) series published by COTO and the Department of Transport. TMH-18 is the live ingest; adjacent documents land as schemas as they enter the engine.
| Standard | Published | Platform support | Scope |
|---|---|---|---|
| TMH-18 | v5 | In progress | Road Asset Data Electronic Exchange Formats — primary ingest |
| TMH-9 | May 2016 | Roadmap | Manual for Visual Assessment of Road Pavements |
| TMH-22 | Draft V8b · Mar 2013 | Roadmap | Road Asset Management Manual |
Source documents: transport.gov.za/tmh-documents.
Frequently asked
Common questions.
What is Meridian/V?
A web platform that validates road-asset CSV submissions against the TMH-18 (Road Asset Data Electronic Exchange Formats) specification published by the Committee of Transport Officials (COTO). When a registered engineer co-signs, Meridian/V issues a SHA-256 certificate over the stored file bytes that any third party can verify without an account.
Which version of TMH-18 does Meridian/V align with?
Version 5 — the COTO release published by the Department of Transport. The current rule set covers required-header presence, UTF-8 encoding, monotonic chainage, deflection-sensor ratio, and temperature-correction presence. Additional sections of TMH-18 land as schemas as they enter the engine.
Is Meridian/V live with paying customers?
Not yet. We are pre-pilot, accepting applications from South African road authorities, consulting engineers, and contractors. Each application is reviewed by hand before access is granted.
Who is the platform for?
South African road authorities (SANRAL and provincial departments — Western Cape Mobility, Gauteng Roads and Transport, Eastern Cape Transport, Mpumalanga Public Works), and the consulting engineers and contractors that submit pavement and road-asset data on their behalf.
How does a third party verify a certificate?
Open tmh18.com/verify and enter the certificate ID. The verifier returns dataset metadata, signers, issued time, and SHA-256 hash — enough for any independent party to re-hash their copy and confirm it matches the certified bytes. No login required.
How is data residency handled under POPIA?
Submitted files and audit metadata are processed on managed cloud infrastructure under a POPIA-aligned data-handling regime. South African residency is on the roadmap before commercial launch — the migration plan is published in the documentation.
How much does it cost?
Free and unmetered for invited organisations during pilot. Commercial pricing has not been published — we are shaping tiers with current pilot orgs.
Is there an API?
Tokens can be issued from the app today. A documented REST API for programmatic submissions and webhooks for co-sign events is on the post-MVP roadmap.
Pre-pilot intakeSubmit today.
Submit today.
Hold a signed certificate by Friday.
Pre-pilot access is reviewed by hand. Apply on the request-access page — we respond within 48 hours with a decision and a one-time admin invite for accepted organisations.
Request access
Application takes about 2 minutes. No payment required during pilot.