Live demo — data resets daily at 03:00 UTC. Nothing you enter is saved.

B12 CB Test Station Upgrade Path

ETT00000005 · Rev R0

in_progresstestmechanicsAvstämning

Test station upgrade path for B12 CB. Primary domain: test. Secondary domain: mechanics.

Everything here lives inside a Project (a code + revision, e.g. ESH10000540 R3). The backbone is the V-model, read top-to-bottom: define what the product must do, plan how to prove it, execute the proof on real units, then learn from the field — and the Loop closes back up to the top.
This map is live: a block is green with a count when this project actually has that entity, and dashed/dim when it’s empty. Click any block to open its tab; hover for details. Arrows are the meaningful links; the implicit “belongs to this Project” edge is left out for legibility.

What each thing means

Requirement
One thing the product must do or satisfy — the “what”.
Test Case
A defined check that proves one or more requirements — the “how we prove it”. A verified_by trace link ties a test case to the requirement(s) it covers; that link is exactly what Coverage % counts. (So: a test case refers to the requirements it verifies.)
Verification Plan
A named grouping of test cases, approved before a test campaign and optionally gated by a milestone.
Verification Record
The result of running one test case against one unit: pass / fail / error / na. This is the evidence a requirement is actually met.
DUT
Device Under Test — an individual physical unit (by serial number) that records and test data attach to.
Deviation
A documented waiver against a verification record (e.g. accept a known non-conformance, with justification).
Entry
A knowledge note: a decision (settled choice), notice (assumption / risk / open question), issue (tracked problem), or concept (idea under exploration). It can attach to any other entity.
Design Rule
A reusable, checkable engineering constraint. Running the checks turns each violation into a Conflict.
Conflict
An open flag raised by a failed design-rule check (or an end-of-life / component-library issue) that needs resolving.
Milestone
A dated gate; verification plans can be tied to it.
Field Issue (RMA)
A failure reported from the field on a returned unit; Root-Cause Analysis explains why it happened.
The Loop (S-16)
loop_trace reconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?). closes_loop records the corrective decision or design rule so the lesson is captured — and clears the project’s open-loop count.
Interface / Port
A contract between projects; each port can be driven by a requirement (and cascade one into the connected project).
BOM Component
A part on this project’s bill of materials, optionally linked to the shared Component Library.
GRR Study
A Gauge R&R study measuring how repeatable a test case’s measurement is.
Test Data
Production / Maestro run results recorded against DUTs — the population behind a single verification record.
0% Coverage
0% Done
0 Requirements
24 Test Cases
2 Blockers
6 Open Entries

Timeline

Color = derived gate state · hover a tile for its note.
achieved
Standoff Sleeve Solution Mechanical
Jun 12, 2026
marker
Accordion A2 hardware + firmware upgrade ready
Jun 17, 2026
achieved
All ~22 A1→A2 PSU tests ported and passing
Jun 21, 2026
marker
Manual regression test complete — zero failures
Jun 26, 2026
marker
Deployed to Synplex and validated via OperatorUI
Jun 30, 2026
marker
Documentation and CM upgrade instructions complete
Jul 10, 2026
marker
Receiving party confirmation — project complete
Jul 31, 2026
marker
R1.0 HW BOM revision approved
Aug 31, 2026
marker
Completed Deployment and Current Release OK at CM
Aug 31, 2026
marker
2x Test Stations Upgraded at CM
Aug 31, 2026
not started
🏁 Release
· 2/6

Status & gates

Chronological — Release is the final gate. Derived & read-only; edit via trace_milestone_* tools.
MS-008Standoff Sleeve Solution Mechanical achieveddue 2026-06-12
MS-002Accordion A2 hardware + firmware upgrade ready markerdue 2026-06-17
MS-003All ~22 A1→A2 PSU tests ported and passing achieveddue 2026-06-21
MS-004Manual regression test complete — zero failures markerdue 2026-06-26
MS-005Deployed to Synplex and validated via OperatorUI markerdue 2026-06-30
MS-006Documentation and CM upgrade instructions complete markerdue 2026-07-10
MS-007Receiving party confirmation — project complete markerdue 2026-07-31
MS-001R1.0 HW BOM revision approved markerdue 2026-08-31
MS-009Completed Deployment and Current Release OK at CM markerdue 2026-08-31
MS-0102x Test Stations Upgraded at CM markerdue 2026-08-31
Release / Readiness not started 2/6 met
pending Requirements approved
  • REQ-001: draft
  • REQ-002: draft
  • REQ-003: draft
  • REQ-004: draft
  • REQ-005: draft
  • REQ-007: draft
  • REQ-006: draft
  • REQ-008: draft
pending Coverage ≥ 100%
  • No requirements in scope
pending All test cases pass
  • 0/24 passed
  • 24 not yet run
pending No blocking issues open
  • E-009: open blocker
  • E-010: open blocker
met Deviations resolved
met Interfaces frozen

Test Cases

0 Pass 0 Fail / Deviated 0 N/A 24 Open24 / 24 Maestro impl.

Coverage — 0.0% · Done — 0.0%

8 of 8
CodeTitleCategoryCoverageStatus
REQ-001 Test station HW BOM revised to R1.0 Hardware
REQ-002 Accordion A2 BOM updated to include PSU module Hardware
REQ-003 A1 PSU power-control tests ported to Accordion A2 Software
REQ-004 Full regression test suite passes on upgraded station Verification
REQ-005 Upgraded station deployed to Synplex and validated via OperatorUI Deployment
REQ-006 Documentation updated for R1.0 changes Documentation
REQ-007 CM production personnel upgrade instructions produced Documentation
REQ-008 Confirmation sign-off obtained from all receiving parties Process