The capability-level Vendor-Agnostic Reference Specification.
An EPC spec writer should be able to receive it, lift sections directly into a tender's functional specification chapter, and produce a defensible 2026 BAS+VTMS spec — without writing it from scratch. 45 pages, A4 portrait, light theme, bookmarked TOC, ~1 MB. Free to qualified requesters; email-gated.
Anonymous download is not offered. The Metratek Telematics team manually reviews each request and responds by email with the appropriate next step. This keeps the distribution audited and lets us version-pin per recipient.
What's inside.
- §1 Purpose & scope — context for the document, what it's for, what it isn't
- §2 Reference framework — assurance requirements inventory, normative references, version-pinned
- §3 Functional capability specification — eight sub-sections covering observability, physics, analytics, evidence, alerting, recall, integration, administration
- §4 Performance — measurable acceptance targets per capability
- §5 Architecture — base-system topology, modules, deployment patterns
- §6 Project requirements — commissioning, training, documentation, support
- §7 Assurance matrix — capability ↔ evidence ↔ scope (Full / Partial / Conditional)
- §8 Acceptance criteria — site acceptance test (SAT) checkpoints + signoff
- Appendix A — sensor reference (laser, lidar, AIS, weather, cameras)
- Appendix B — alert component library (25 nodes, 7 categories)
- Appendix C — engineering evidence samples (runtime physics traces, operation-report extracts)
- §12 About Metratek Telematics — company, parent brand, contact
Lift directly into your tender.
§3 (functional capability) and §7 (assurance matrix) are the two sections most often lifted into tender functional-specification chapters. The matrix uses Full / Partial / Conditional scoping so you can adjust scope to your project's assurance posture without rewriting the capability text.
Use the acceptance criteria.
§8 (acceptance criteria) provides the SAT checkpoints suitable for incorporation into a project's procurement framework. The performance budgets in §4 give the numeric benchmarks you can cite without re-deriving them.