In development · Phase 1

One thread from customer intent to shipped hardware.

ODM Trace is a simple requirements management tool for ODM IoT hardware teams — connecting Customer, Stakeholder, System, Hardware and Software requirements into a single auditable thread, with the right approvals at the right stage.

See what's coming ↓
5 requirement levels
1 traceability thread
Zero spreadsheets lost

Requirement lineage

Customer Requirement
CR-0142 · Approved
Stakeholder Requirement
STK-0033 · Approved
System Requirement
SYS-0311 · In review
Hardware / Software
Awaiting trace

What it does

Everything a requirement needs, in one place

Simple requirements management and full traceability, built for managers who need clarity and engineers who need structure — without asking either to change how they work.

Full requirement hierarchy

Customer → Stakeholder → System → Hardware → Software. Every child links back to its parent automatically, so coverage is never a guessing game.

Type-specific approvals

Each requirement routes to the right approver — PM, Tech Lead, HW Lead, SW Lead — with a mandatory comment enforced on every rejection.

Excel import, done right

Drop in a spreadsheet, map the columns, and catch duplicates or missing fields before anything hits the system.

Versioned artefact storage

Exports from Cameo, Rhapsody or Office live inside the project — versioned, timestamped, and linked back to the requirements they support.

Feature coverage mapping

Tag requirements against a shared feature list and see, at a glance, what's covered — and what's quietly falling through.

Dashboards for every role

Open requests, approval rate, cycle time, and a live traceability matrix — filtered to what each role actually needs to see.

How it flows

The path a requirement takes

From project kickoff to a traced, approved specification — the same seven steps, every time.

01
Project Manager

Set up the project

Create the project, invite the team, and assign roles.

02
Requester / PM

Enter the source requirements

Customer and Stakeholder Requirements go in directly, or arrive via Excel import.

03
PM / Approver

Review and approve

Requirements move through Draft → In Review → Approved, Rejected, or On Hold.

04
Experts / Engineers

Do the deep design work externally

Concept design and MBSE work happens in dedicated tools — Cameo, Rhapsody, and others.

05
Any team member

Bring the outputs back in

PDF, Word, and Excel exports are uploaded and stored with full version history.

06
Engineers / PM

Add System, Hardware and Software Requirements

Entered or imported as children, traced back to their approved source requirements.

07
Tech Lead / Approver

Close the loop

System, Hardware and Software requirements go through their own type-specific approval.