AMS Signoff Dashboard: Review Checklist

Review checklist

Review Checklist for AMS Signoff Dashboard focuses on cross-domain signoff readiness score, unresolved waivers, tapeout blockers. The goal is to connect observed symptom to boundary mechanism, ownership, and signoff risk.

• Boundary assumptions are versioned and signed.

• Mode matrix (power/clock/reset/stress) is explicit.

• Physical context (floorplan/package/power) is included where relevant.

• Metric and artifact references are reproducible.

• Waivers have owner, expiry, and mitigation.

• Owners signed: signoff lead, program manager, AMS integration lead.

Sign-off ownership

OWNERSHIP MAP — AMS Signoff Dashboard

artifact                  owner
----------------------    -----------------------------
integration artifact    signoff lead
implementation artifact program manager
signoff artifact        AMS integration lead

Every boundary issue needs a named owner before fixes start.

AMS deep dive

AMS signoff is a combined noise, IR, timing, and package decision.

Concept diagram

BOUNDARY SIGNOFF

noise + IR + package + timing -> release decision

Metric graph

RISK DASHBOARD

open blockers █████
waivers       ███

Reports and artifacts

• supply ripple spectrum

• IR around analog islands

• package PI summary

• release dashboard

Mini case study

IR hotspot at analog island caused jitter spikes only under burst traffic.

Debug branches

• Correlate droop and jitter

• Check package return path

• Validate mode-specific activity profile

Senior review question

Ask: what boundary condition proves this topic is actually closed?

Key takeaways

• State boundary, mode, and evidence tag with every claim.

• Always align analog, digital, and physical owners before signoff decisions.

Common pitfalls

• Fixing averages while tails still fail.

• Skipping package/supply evidence in jitter or SerDes issues.

• Shipping with waivers that lack owner and expiration criteria.

Principal AMS review addendum

A unified AMS dashboard ties timing, noise, IR, SI, PV, and bring-up evidence so release decisions are based on complete cross-team risk visibility.

Metric: cross-domain signoff readiness score, unresolved waivers, tapeout blockers