B12 CB Test Station Upgrade Path
ETT00000005 · Rev R0
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_tracereconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?).closes_looprecords 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.
Timeline
Color = derived gate state · hover a tile for its note.Status & gates
Chronological — Release is the final gate. Derived & read-only; edit viatrace_milestone_* tools.MS-008Standoff Sleeve Solution Mechanical
achieveddue 2026-06-12MS-002Accordion A2 hardware + firmware upgrade ready
markerdue 2026-06-17MS-003All ~22 A1→A2 PSU tests ported and passing
achieveddue 2026-06-21MS-004Manual regression test complete — zero failures
markerdue 2026-06-26MS-005Deployed to Synplex and validated via OperatorUI
markerdue 2026-06-30MS-006Documentation and CM upgrade instructions complete
markerdue 2026-07-10MS-007Receiving party confirmation — project complete
markerdue 2026-07-31MS-001R1.0 HW BOM revision approved
markerdue 2026-08-31MS-009Completed Deployment and Current Release OK at CM
markerdue 2026-08-31MS-0102x Test Stations Upgraded at CM
markerdue 2026-08-31Release / 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
Test Cases
Coverage — 0.0% · Done — 0.0%
| Code | Kind | Title | Severity | Scope | Status | Milestone | Created |
|---|---|---|---|---|---|---|---|
E-006 |
decision | Replace Accordion A1 with Accordion A2 as programmable PSU in B12 CB test station | info | record | open | — | 2026-06-08 |
E-007 |
decision | Two test repositories — CB0 and CB1 separate repos | info | record | open | — | 2026-06-08 |
E-008 |
decision | A1 PSU control is centralized in one shared file — not 22 separate tests | warning | action | open | — | 2026-06-08 |
E-009 |
notice | A2 fresh firmware makes existing accordion.py wrapper potentially obsolete — API unknown, porting blocked | blocking | action | open | — | 2026-06-08 |
E-010 |
notice | CRPS 12V/75A bulk PSU on A2 — full fix required (ARM64 handler port + udev rule for MCP2221A) | blocking | action | open | — | 2026-06-08 |
E-011 |
notice | udev rule for MCP2221A HID access must be baked into A2 OS image | warning | action | closed | — | 2026-06-09 |
E-012 |
decision | M2Top PSU channel mapping confirmed: CH1=standby (TA/AWO), CH2=testboard (B6_PROD_TB) | info | record | open | — | 2026-06-10 |
E-013 |
notice | R1.0 BOM near-complete — A2 top cover ESH number pending from Felix G | warning | action | closed | — | 2026-06-10 |
E-014 |
decision | Standoff sleeve prototype accepted — 5 pcs in production (Felix G) | info | record | open | MS-008 |
2026-06-18 |
E-015 |
decision | R1.0 BOM review deferred to 2026-08-31 with Martin J — known delta items noted | info | record | open | MS-001 |
2026-06-23 |