Derate Policy & Approval: Worked Example

Worked example

Worked Example 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 signoff run shows approved derate set, waiver count, signoff pessimism budget. The first review mistake is to blame implementation without checking constraints. A better review starts by pinning one critical path, proving where slack was lost, and checking whether the SDC rule is correct for Derate Policy & Approval.

Sequence under inspection

TIMING PATH — Derate Policy & Approval

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: approved derate set, waiver count, signoff pessimism budget

Derate approval flow

DERATE CHANGE REQUEST
  -> STA lead review
  -> PD director sign
  -> foundry policy check
  -> re-run full MMMC matrix
  -> archive before/after WNS

1. Capture report_timing and the relevant SDC excerpt.

2. Tag corner, mode, view, and path group.

3. Find the first cell or net that dominates critical delay.

4. Compare against derate approval memo, signoff policy PDF, before/after WNS comparison.

5. Choose one reversible ECO and write the regression matrix before editing netlist or constraints.

Did the fix work?

BEFORE / AFTER ECO — Derate Policy & Approval

WNS (ps)
  0 |                    --- target
-50 |    ● regressed
-80 |         ● before ECO
-20 |              ● after ECO
    +-------------------------------> ECO iteration
Prove setup AND hold moved safely.

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