Sparrow Production Readiness R1
ETT00000002 · Rev R0
in_progressgenericinformalAvstämning
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.
0%
Coverage
0%
Done
0
Requirements
3
Blockers
12
Open Entries
Timeline
Color = derived gate state · hover a tile for its note.achieved
Gate 1 — Design Release (all sub-assemblies at Manufacturing in MES; ESH10000634 R3 approved)
achieved
Gate 2 — Inventory Procurement (superseded by MS-G3B + MS-G5)
marker
Gate 3 — Test & Production Infrastructure (ESH10000654 verified; test procedure complete; DUT serials defined)
overdue / blocked
First Article BOM Complete (parts for 2 units, ETA 2026-06-09)
overdue / blocked
Gate 4 — First Article (S/N 001 assembled and passed production test)
overdue / blocked
Gate 5 — Production Run (20 systems + standalone deliverables 10×636, 20×614, 20×637, 20×EPN1000786)
overdue / blocked
Gate 6 — Delivery (final QC, packaging, delivery documentation complete)
not started
🏁 Release
Status & gates
Chronological — Release is the final gate. Derived & read-only; edit viatrace_milestone_* tools.MS-G1Gate 1 — Design Release (all sub-assemblies at Manufacturing in MES; ESH10000634 R3 approved)
achieveddue 2026-05-15MS-G2Gate 2 — Inventory Procurement (superseded by MS-G3B + MS-G5)
achieveddue 2026-06-05MS-G3Gate 3 — Test & Production Infrastructure (ESH10000654 verified; test procedure complete; DUT serials defined)
markerdue 2026-06-05MS-G3BFirst Article BOM Complete (parts for 2 units, ETA 2026-06-09)
overdue / blocked
4/6 metdue 2026-06-09
pending Blocked by E-046: ESH10000539 R2 — 60 raw PCBs in-house, assembly ETA 2026-06-05; Sparrow allocation 2+18
- E-046 still open
met
Blocked by E-045: 2026-05-28: ESH10000158 — 40 pcs R6 delivered; build preference R6-only, contingent on R5↔R6 diff + acceptance
pending Blocked by E-047: ESH10000539 — verify R67 + R61 mounted (R2 BOM) before any board enters Sparrow; R1 stock IS patchable
- E-047 still open
met
Blocked by E-048: ESH10000158 R6 — reflow ETA 2026-06-05 (Darek); Sparrow allocation 2+18
met
Blocked by E-049: ESH10000534 R4 (M2Top PoE) — 28 pcs in-house assembly, ETA 2026-06-05
met
Blocked by E-050: ESH10000634 R3 (Sparrow IDC N-Top) — 50 pcs in-house assembly, ETA 2026-06-05
MS-G4Gate 4 — First Article (S/N 001 assembled and passed production test)
overdue / blocked
2/5 metdue 2026-06-12
pending Blocked by E-041: 2026-06-03: Use OLD revs of ESH10000522 / ESH10000544 / ESH10000572 for first article build
- E-041 still open
pending Blocked by E-060: Talk to Felix — Sparrow Accordion top lid fastening; are the specified spacers good?
- E-060 still open
met
Blocked by E-061: ESH10000636 BOM completeness — fan, heatsink, gap-filler, screws missing from MES BOM? (Elsa to verify)
met
Blocked by E-062: ESH10000636 BOM — EGP10001723 SSW-110-04-G-D should NOT be on this BOM (Elsa to verify)
pending After MS-G3B: First Article BOM Complete (parts for 2 units, ETA 2026-06-09)
- MS-G3B not yet achieved
MS-G5Gate 5 — Production Run (20 systems + standalone deliverables 10×636, 20×614, 20×637, 20×EPN1000786)
overdue / blocked
0/10 metdue 2026-07-06
pending Blocked by E-051: G-05: ESH10000637 (PSU Power Cable) — need 40, stock 0 — BUILD in-house (Elsa to coordinate)
- E-051 still open
pending Blocked by E-052: G-06: EPN1000677 (5-port USB wall charger) — 2 short of 20-unit need (Elsa to order)
- E-052 still open
pending Blocked by E-053: ESH10000183 (Accordion A2 Top PCBA, R6) — 25 pcs incoming, ETA 2026-06-12
- E-053 still open
pending Blocked by E-054: Test fixture with tablet for Sparrow — initial conversation with Felix (2026-05-28)
- E-054 still open
pending Blocked by E-055: Operator instructions needed — assemble + test procedure for Sparrow Complete Product
- E-055 still open
pending Blocked by E-056: ESH10000571 (N-Top Kontaktkropp) — 20 pcs on order ETA 2026-06-25; first article covered
- E-056 still open
pending Blocked by E-057: ESH10000536 R2 (M2Top Active Load) — 40 new PCBs on order ETA 2026-06-25; 20 pcs Sparrow spare ETA 2026-07-10
- E-057 still open
pending Blocked by E-058: EPN1000068 (RPi Fan) — short 5 vs need 20; ORDER (Elsa)
- E-058 still open
pending Blocked by E-059: EPN1000439 (Hammond box blue) — 20 stock vs 20 need (no margin); ORDER (Elsa)
- E-059 still open
pending After MS-G4: Gate 4 — First Article (S/N 001 assembled and passed production test)
- MS-G4 not yet achieved
MS-G6Gate 6 — Delivery (final QC, packaging, delivery documentation complete)
overdue / blocked
0/1 metdue 2026-07-13
pending After MS-G5: Gate 5 — Production Run (20 systems + standalone deliverables 10×636, 20×614, 20×637, 20×EPN1000786)
- MS-G5 not yet achieved
Release / Readiness not started 0/4 met
pending Requirements approved
- No requirements in scope
pending Coverage ≥ 100%
- No requirements in scope
pending All test cases pass
- No test cases in scope
pending No blocking issues open
- E-055: open blocker
- E-046: open blocker
- E-047: open blocker
Coverage — 0.0% · Done — 0.0%
| Code | Title | Category | Coverage | Status |
|---|