DenseChip

STA Mastery · All levels

OCV / AOCV / POCV Mechanisms: Step-by-Step Walkthrough

Step-by-Step Walkthrough for OCV / AOCV / POCV Mechanisms.

Step-by-step analysis walkthrough

Use when you own OCV / AOCV / POCV Mechanisms in a timing war room.

  1. Open signoff scenario list — note worst WNS corner.

  2. report_timing -max/-min on failing group.

  3. Trace launch and capture clocks on critical path.

  4. Check exceptions and generated clocks on path.

  5. Break down cell vs net delay.

  6. Compare implementation vs signoff view if delta suspicious.

  7. Assign owner: RTL, synth, PD, CTS, SI.

  8. Propose ECO with hold/SI check plan.

  9. Run regression matrix.

  10. Update closure dashboard and memo.

Artifacts to collect

  • variation report, derate table, depth histogram, POCV policy doc

  • SDC file

  • SPEF tag

  • MMMC scenario list

  • ECO ticket

Decision memo template

diagram
STA DECISION MEMO — OCV / AOCV / POCV Mechanisms
corner/mode:
WNS/TNS:
hypothesis:
ECO:
regression:
owners: STA lead, library team, foundry interface

Reference visuals

OCV vs AOCV depth effect

diagram
DERATE PESSIMISM vs PATH DEPTH

OCV:   fixed % on every stage  -> over-pessimistic on long paths
AOCV:  derate reduces with depth -> less pessimism on long paths
POCV:  statistical sigma model  -> signoff-grade distribution

Short hold paths still need careful min-delay analysis.

STA deep dive

Variation policy is negotiated margin, not a tool checkbox.

Concept diagram

diagram
VARIATION STACK

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

Metric graph

diagram
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

Variation models add margin for on-chip delay spread; AOCV/POCV reduce over-pessimism by accounting for path depth and statistical correlation.

Metric: OCV derate %, depth-adjusted pessimism, POCV sigma contribution

Practice this lesson