Prepared in minutes
Technical values are prepared in minutes rather than entered by hand from separate sources.
Today, an operator looks up figures across manufacturer documents and registries, then transcribes them into a certificate template, one vehicle at a time. The platform MILCODE built gathers the values and prepares the authority's own form in minutes.
Technical values are prepared in minutes rather than entered by hand from separate sources.
Over 100 certificates prepared in production for an accredited body.
Every operator override is recorded with its timestamp, user, previous value, previous source and new value.
Send one VIN and sticker photoThe proven path is for US-market vehicles: federal vehicle data is available, manufacturer stickers are standardised and information-dense, and the document maps FMVSS requirements to European regulations. Other non-EU vehicles are handled case by case, with coverage depending on what the manufacturer sticker and supplied documents provide.
| Registration-document code | Field | Prepared value | Review |
|---|---|---|---|
| J | Category | M1 | Review |
| J.1 | Body shape | Passenger vehicle | Review |
| D.1 | Make | Example Motors | Review |
| D.2 | Type / variant / version | MX-47 / A3 / 02 | Review |
| D.3 | Commercial name | Northline | Review |
| F.1 | Max permitted weight | 2,240 kg | Review |
| (N) | Axle loads | 1,160 kg / 1,220 kg | Review |
| G | Curb weight | 1,682 kg | Review |
| P / P.1 / P.2 / P.3 | Engine / displacement / power / fuel | EA-22 / 1,998 cm³ / 142 kW / petrol | Review |
| S.1 | Seats | 5 | Review |
| — | Dimensions / emissions / CO₂ / consumption / noise | 4,680 mm / Euro 6 / 178 g/km / 7.8 l/100 km / confirm after inspection | Missing |
The platform removes transcription work. The operator reviews every field and remains responsible for the final values.
The operator supplies a VIN, optionally a type-approval number, and supporting documents. The platform reads the manufacturer sticker from uploaded photos alongside the supplied material.
The platform gathers technical values from external registries and the uploaded sticker, then assembles them in the authority's own template and registration-document field codes.
The operator checks each field, corrects any value and regenerates the document. The authority then reviews and issues the document under its own authority.
The authority's document includes a correspondence table between FMVSS and ECE requirements, marking each subject as met or not met. It is part of the prepared document, not a separate research exercise.
| Field | US specification example | EU document context |
|---|---|---|
| Refrigerant | R-134a may appear in source data | R-1234yf is the European requirement |
| Exterior noise | No US federal limit for the comparable field | ECE R51 sets the exterior-noise requirement |
| Emissions | US emissions classification | Map to the European classification for authority review |
| Consumption | US consumption measure | Convert to the European format for authority review |
Every prepared value carries its source, and every operator correction is retained with the job record.
Each prepared value carries a source tag. The manufacturer sticker and operator-entered values take precedence over external sources; external data fills gaps and never overwrites them.
Each job retains per-stage logs, an archive of processing steps, access history and every operator correction.
Missing and estimated values use distinct styles. Out-of-range figures receive a verification flag, and an unknown body shape requires confirmation. The platform never fills a gap silently.
The system is designed to surface uncertainty to the operator, rather than turn an incomplete source into a guessed value.
When a safety-critical field is uncertain, the job stops and the interface asks the operator for exactly the fields that need a decision.
Operator corrections are recorded and promoted into curated reference tables, so repeatedly seen models need less correction over time.
After a correction, the authority's certificate regenerates in its own language and form without re-querying external sources or re-reading the manufacturer sticker.
Onboarding a new authority means configuring its certificate template, field codes and language. The platform fills that authority's form, not a MILCODE form.
Multiple operators can work on and hand off jobs, supported by an administrative activity view.
The platform is installed as a single-tenant system on the authority's own server.
A submitted VIN reaches vehicle-data registries and document-processing services. Uploaded sticker photos are read for technical values.
No vehicle inspection. No approval issued. No transfer of liability. The authority reviews the prepared values and issues the document under its own authority.
Send a VIN and a photo of the manufacturer sticker. MILCODE will return a prepared sample for review.