Vectorless vs Vector-Based Power

On-call / interview prompt

You own Vectorless vs Vector-Based Power on a block nearing implementation freeze — what do you verify first?

CLOSURE CHAIN

1. METRIC     — name the failing report line (WNS, DRV, DRC count, IR %)
2. HYPOTHESIS — 2–3 likely causes ordered by probability
3. EXPERIMENT — one cheap check (corner, clock, report, map)
4. FIX        — minimal physical or constraint change
5. REGRESSION — what you re-run and what must not regress

Topic overview

Use complementary analysis styles to capture conservative bounds and realistic switching stress for signoff confidence.

Mechanism to narrate

• Section: Power Signoff

• Primary artifact: vectorless/vector comparison report by hotspot and domain

• Downstream dependency: next PD stage

Staff/principal ownership model

Own Vectorless vs Vector-Based Power as a release decision, not a page of notes. A senior PD engineer names the metric, the physical mechanism, the cross-team dependency, and the smallest evidence-producing experiment.

STAFF REVIEW MEMO — Power Signoff / Vectorless vs Vector-Based Power

1. Current state
   - Failing / watched metric: vectorless/vector comparison report by hotspot and domain
   - Database tag, corner/mode, tool version: <fill before review>
   - Physical scope: block, hierarchy, macro region, clock domain, or net class

2. Root-cause hypothesis
   - Most likely mechanism: <name physical or constraint mechanism>
   - Competing hypothesis: <name the second plausible cause>
   - Evidence still missing: <report/map/schematic/check>

3. Proposed action
   - Minimal reversible fix: <physical, constraint, ECO, or methodology change>
   - Expected improvement: <metric delta>
   - Regression risk: late-stage schedule slip, silicon risk, or cross-stage regression

4. Regression and signoff
   - Re-run: vectorless/vector comparison report by hotspot and domain
   - Must not regress: timing, routing, power, PV, DFT, package, or tapeout signoff
   - Decision owner: PD owner

Sub-lessons in this topic

1. mechanism — Mechanism

2. inputs-outputs — Inputs & Outputs

3. reports — Reports & Metrics

4. debug-playbook — Debug Playbook

5. worked-example — Worked Example

6. pitfalls — Pitfalls & Red Flags

7. interview — Interview Drills

8. checklist — Review Checklist

Related topics

• IR hotspot interpretation

• Policy and evidence review gates

Key takeaways

• Master Vectorless vs Vector-Based Power through reports, not GUI habit.

Deep dive: how this shows up in real closure

Power signoff validates whether the physical grid supports real activity.

Reports and artifacts to inspect

• static IR and dynamic IR maps with max drop percentage

• EM ratio report by wire/via segment

• activity source: vectorless, SAIF/VCD, or scenario-specific waveform

• low-power cell placement: isolation, level shifter, retention, power switch

Mini case study

Dynamic IR fails near a clock-gated compute island during wake-up. Adding a far-away ring is not enough. Strengthen local straps/vias, add decap, and check wake sequencing.

Debug branches

• If dynamic IR fails but static passes, correlate with switching vectors and clock domains.

• If EM fails on vias, add via ladders or parallel straps rather than only widening wire.

• If leakage fails, use HVT swaps on non-critical paths before reducing performance mode.

Senior review question

Ask yourself: what single report line would prove this page's concept is either passing or failing?

What changes at 10+ years

• You are expected to predict what your fix can break before running it.

• You should recognize when the issue is methodology, not one block's implementation.

• You should communicate risk in tapeout language: owner, evidence, impact, mitigation, and decision date.

Principal-level review bar

Lesson pages in this course should be read like real closure review material. For a 10+ year PD engineer, the bar is not remembering terminology; it is making a release-quality decision under ambiguity.

What excellent looks like

• Names the failing metric, corner/mode, database tag, and analysis switches before proposing a fix.

• Separates data, constraint, physical, tool, and methodology root causes instead of treating all failures as optimization problems.

• Chooses experiments by information gain and reversibility, not by habit.

• States regression blast radius across timing, route, power, PV, DFT, package, and tapeout manifest.

• Turns recurring failures into methodology guardrails, dashboards, or checklist items.

Closure note template

STAFF / PRINCIPAL CLOSURE NOTE

Context:
  stage: <pre-CTS | post-CTS | post-route | post-fill | signoff>
  tag: <database / netlist / SDC / library stack>
  failing metric: <exact report line>
  affected scope: <block / hierarchy / path group / power domain / region>

Hypotheses:
  H1: <most likely physical or constraint mechanism>
  H2: <competing explanation>
  H3: <methodology or input-data issue>

Decision:
  next experiment: <cheap check that can falsify H1>
  fix candidate: <minimal reversible change>
  rollback trigger: <metric that says the fix is wrong>
  regression set: <timing / route / power / PV / DFT / package>
  escalation owner: <team or reviewer>

Tradeoffs a senior engineer must discuss

Technical tradeoff

Power signoff validates whether the physical grid supports real activity. Explain not only the preferred fix, but what margin or schedule you are spending to get it.

Cross-team tradeoff

• What must RTL, synthesis, CAD, STA, DFT, package, IP, or foundry agree to before this decision is final?

• Which artifact becomes the source of truth after the decision: report, waiver, manifest, ECO script, or methodology deck?

• What is the cost of being wrong: one rerun, ECO churn, mask risk, performance loss, or silicon escape?

Leadership communication

"The current blocker is <metric> in <corner/mode/stage>. The leading cause is <mechanism>. I recommend <fix> because it is bounded and reversible. The regression surface is <domains>. If it fails, we escalate to <owner> with <evidence>."

Key takeaways

• Always connect the concept back to a measurable signoff artifact.

• A fix is not complete until you can name the regression checks.

Common pitfalls

• Optimizing by habit instead of reading the current report.

• Forgetting that a local fix can regress timing, routing, power, or PV elsewhere.