Derate Policy & Approval: Pitfalls & Red Flags

Pitfalls and red flags

Pitfalls & Red Flags for Derate Policy & Approval focuses on approved derate set, waiver count, signoff pessimism budget. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.

• A path looks clean in one view but fails in signoff SPEF.

• The SDC allows behavior that the implementation team assumed was illegal.

• A generated_clock definition shifts capture edge silently.

• Hold fails on short paths after setup-focused ECO.

• The fix improves one corner but regresses another MMMC scenario.

Layer responsibility check

STA OWNERSHIP LAYERS — Derate Policy & Approval

layer              owns                         failure mode
----------------   --------------------------   ---------------------
constraints        clocks, IO, exceptions       false violations
implementation     cells, nets, placement       real path delay
extraction         SPEF/RC corners              view mismatch
signoff policy     derate, MMMC matrix          margin disputes
closure           ECO order, regression        fix breaks other corner

STA deep dive

Variation policy is negotiated margin, not a tool checkbox.

Concept diagram

VARIATION STACK

nominal delay + OCV/AOCV/POCV margin = signoff delay

Metric graph

DERATE IMPACT ON WNS

OCV only     WNS -120ps
AOCV         WNS -45ps
POCV         WNS -60ps (policy dependent)

Reports and artifacts

• derate table

• AOCV depth report

• POCV sigma

• hold/setup split

Mini case study

Switched to AOCV without re-baselining hold — short paths failed min analysis.

Debug branches

• Short paths for hold

• Policy approval for derate changes

Senior review question

Ask: what corner/mode/view proves this topic is closed or failing?

Key takeaways

• State corner, mode, view, and database tag with every slack claim.

• Run setup and hold plus MMMC regression after every ECO.

Common pitfalls

• Comparing STA runs with different SPEF or SDC tags.

• Broad false_path to green-wash violations.

• Setup-only ECO without hold check.

Principal STA review addendum

Derating policy is a contractual margin between implementation and signoff; changes need documented approval and regression.

Metric: approved derate set, waiver count, signoff pessimism budget