How to prepare your fleet for NOM-068

If your operation hauls federal freight or deals with physical-mechanical requirements, NOM-068 shows up in compliance, shop, and verification talks. This guide covers what to document in the fleet, what Karvia provides today, and how that complements the UV or authority’s verification act.

What NOM-068 is (in fleet language)

Operationally, NOM-068 is about keeping the unit in proper physical-mechanical condition and verifying it where required. Maintenance, the service log, and the vehicle file are the operator’s or permit holder’s duty. The dictamen, hologram, or certificate — when applicable — is issued by the UV or authority.

• Operator / permit holder: maintain the unit, log services, and keep operational evidence.
• UV / authority: issue the legal verification act when the framework requires it.
• Karvia: centralizes signals, alerts, and documents to prepare the file and follow up on operations.

What Karvia contributes in the process

Karvia is a web platform + operational WhatsApp: OBD/GPS monitoring, Health Score, Actions inbox, service logs, and a copilot. It helps you detect, document, and close the loop before inspection. Official verification and the legal act are completed by the UV or the relevant authority.

Where fleets struggle today

• Incomplete logs stuck in spreadsheets or chat — no credible completed-service history at inspection time.
• Preventive plans that stay as scheduled stubs and never become completed records.
• Alerts without close-out: the issue was seen, discussed on WhatsApp, and never documented or verified.
• Stale registration-card / plate expiries (NOM-001-adjacent, often requested with the file).
• Mixing NOM-068 (physical-mechanical) with NOM-167 (OBD / environmental verification where it applies): OBD informs engine status; physical-mechanical inspection is a separate process.

How Karvia helps you prepare for NOM-068

1. Actions and “why it fired”

The Actions inbox holds alerts (battery, DTCs, hours, geofences, and more). Each can show why it fired (fixed threshold, baseline, custom rule). Closing the loop — acknowledge, act, verify with OBD readings and fault codes when applicable — leaves an operational trail useful for an internal audit or for assembling a prep file.

2. Completed service logs (not only “scheduled”)

Plan AI and the maintenance calendar tell you what is due by km/class. For NOM-068 prep, maintenance evidence is the service logged as completed — not a “[Plan AI] scheduled” stub. Use the plan to anticipate; use the log to prove the work was done.

3. Inspection packet + NOM prep map

From Reports / NOM prep or Actions you can export the Inspection packet: evidence themes (maintenance, faults/engine, operations, documents, driving coaching, OBD snapshot) plus a compact prep map (NOM-068, NOM-167, docs, and more). It is an operational dossier you can take to your UV or an internal audit.

4. Copilot (web and WhatsApp)

Ask “Am I ready for NOM-068?” or “prepare inspection.” The copilot uses the prep map and flags gaps (e.g. no completed log, no recent OBD reading). Channels: web dashboard and operational WhatsApp — Karvia has no native mobile app.

Practical path in 5 steps

• Close open alerts in Actions and review “why it fired” on the critical ones.
• Log completed services (internal shop or marketplace); do not leave only the scheduled plan.
• Update document expiries you capture (registration card / plates).
• Export the Inspection packet and review the NOM-068 prep map.
• Ask the copilot what still needs documenting; take the PDF to your UV or internal audit.

Theme ↔ Karvia evidence ↔ official verification

Product scope and related norms

• NOM-167: OBD and DTCs in Karvia support prep and operational diagnostics; official environmental verification (where it applies) is completed through that process.
• Brakes: harsh-brake / stress alerts support coaching and recommended inspection; they do not measure pad millimeters or certify remaining life.
• Karvia is not an ELD or a fatigue / NOM-087 product.
• NOM-236 (light physical-mechanical) was cancelled. For federal physical-mechanical, the current reference framework is NOM-068.
• Geotab or Karvia OBD fleets share the same evidence pipes; maintenance dollars appear in summaries when you log services with cost.

Next step

Read the Standards section of the technical FAQ, export an Inspection packet for a pilot unit, and book a demo if you want to land Detect → Verify and the prep map on your operation. You arrive at the UV with an organized operational evidence file.