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

Synopsys Support Agreement

ETT00000007 · Rev R0

in_progressgenericinformalAvstämning

Project covering the E-Sharp / Synopsys support agreement — contract documents, spare parts stocking decisions, CM site management (Kitron, Sanmina), consigned inventory SOPs, support channel processes, and trade compliance references.

Reports Audit Log

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
39 Open Entries

Timeline

Color = derived gate state · hover a tile for its note.
not started
🏁 Release
· 1/4

Status & gates

Chronological — Release is the final gate. Derived & read-only; edit via trace_milestone_* tools.
Release / Readiness not started 1/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
met No blocking issues open
Attention 32 open entries

Coverage — 0.0% · Done — 0.0%

0 Done 0 Partial 0 Not Started 0 Missing0 Obsolete
Entries
43 of 43
CodeKindTitleSeverityScopeStatusMilestoneCreated
E-008 notice Management escalation contacts info record open — 2026-06-02
E-009 notice Technical owners per test station type (full names) info record open — 2026-06-02
E-010 notice Phone support SOP — call handling procedure info record open — 2026-06-02
E-011 decision Spare parts — ownership and consignment model info record open — 2026-06-02
E-019 notice Ticket system workflow (JSM/support portal) info record open — 2026-06-02
E-022 notice Reporting schedule, content and recipients info record open — 2026-06-02
E-023 notice Consigned inventory — order confirmation and receiving procedure info record open — 2026-06-02
E-028 issue Open process gaps — items still needing definition warning action open — 2026-06-02
E-029 notice SOW — Full summary (term, compensation, SLA, KPI, scope) info record open — 2026-06-02
E-030 decision Replenishment recommendation policy — when and how to notify Synopsys info record open — 2026-06-02
E-031 notice Jira Assets — purpose and current implementation status info record open — 2026-06-02
E-032 notice CM spare part usage and consumption reporting procedure info record open — 2026-06-02
E-033 notice MES inventory transfer — E-Sharp to CM info record open — 2026-06-02
E-034 notice Customer-owned inventory — storage requirements info record open — 2026-06-02
E-035 issue Handover documentation — missing procedures to write up warning action open — 2026-06-02
E-037 notice How to create the monthly report info record open — 2026-06-03
E-038 notice How to create the weekly inventory & transaction report info record open — 2026-06-03
E-040 notice KPI Data Reconciliation info action open — 2026-06-04
E-041 notice Spare Parts Testing Documentation info action open — 2026-06-04
E-042 notice Ticket Aging Metrics Report info action open — 2026-06-04
E-043 issue KPI Data Reconciliation info action withdrawn — 2026-06-04
E-044 issue Spare Parts Testing Documentation info action withdrawn — 2026-06-04
E-045 decision Automated tool — SUP Ticket Aging Report info record open — 2026-06-04
E-046 decision Automated tool — SUP Stale Ticket Reminder info record open — 2026-06-04
E-049 notice ACTION (Elsa): Check Fremont shipment status and report back to Huy Tran warning action closed — 2026-06-08
E-050 notice ACTION (Mikael, Elsa): Decide whether to ship one set of loopback boards now or wait info action open — 2026-06-08
E-051 notice ACTION (Mikael): Sync with Andreas to clarify Halo test status — disabled tests and Ethernet IT issues info action open — 2026-06-08
E-052 notice ACTION (Mikael): Respond in SUP-124 with debugging steps for missing MPIO on Accordion board info action open — 2026-06-08
E-053 notice ACTION (Jerry): Monitor 3.3V during CD zero test and document findings in SUP-125 info action open — 2026-06-08
E-054 notice ACTION (Elsa): Add updated return-for-repair shipment guide link to the Synopsys portal info action closed — 2026-06-08
E-056 notice Contact list — Synopsys, Kitron, Sanmina info record open — 2026-06-09
E-057 notice Access requirements — systems needed to operate the support agreement info record open — 2026-06-09
E-058 notice Safety stock & replenishment — lead times, warn levels, and process info record open — 2026-06-09
E-059 notice Month-end inventory report — how to create and send info record open — 2026-06-09
E-060 notice Stock taking procedures — E-Sharp warehouse and CM sites info record open — 2026-06-09
E-061 notice Shipping spare parts to partners — step-by-step process info record open — 2026-06-09
E-062 notice Meeting cadence and agendas — bi-weekly Synopsys meetings info record open — 2026-06-09
E-063 notice Summary schedule — weekly, bi-weekly, and monthly cadence info record open — 2026-06-09
E-064 decision Ticket ownership definition: "Pending" and "Replenishment process" statuses have no active owner info record open — 2026-06-16
E-065 decision ESIN — Roles & Responsibilities (E-Sharp vs Synopsys vs CM) info record open — 2026-06-16
E-066 notice Meeting notes — Inventory Disposition Planning (Jeanette, Bobby, Elsa) warning action open — 2026-06-16
E-067 decision Maintenance document scope: SSJ to provide general Harmonix tester docs, not fixture-specific info record open — 2026-06-18
E-068 notice Bi-weekly meeting notes — 2026-06-18 (loopback boards, I2C, MPIO, CD0, Halo) info record open — 2026-06-18