Silicon PPA and closure impact

Bad budget hygiene becomes expensive ECO churn near tapeout.

Area drivers

• Guardband margins

• late ECO spillover

Power drivers

• Emergency frequency guards

• clocking overhead

Timing impact

• Cross-domain path regressions

• late closure churn

PD consequences

• Route congestion from top-level fixes

• package-driven detours

Verification burden

• Re-validation of waived assumptions

PPA RISK — Integration Milestones
area/power/timing confidence vs integration velocity

PPA takeaways

• Integration discipline reduces expensive late-stage silicon risk.

Design option PPA snapshot

BEFORE / AFTER FIX — Integration Milestones

risk index
 0 |                    --- target
40 |    ● regression
65 |         ● before fix
20 |              ● after fix
    +-------------------------------> iteration
Always verify collateral, regression suite, and owner signoff.

SoC deep dive

Budget and ownership contracts are technical artifacts, not PM slides.

Concept diagram

HIERARCHY CONTRACT FLOW
partition -> block budget -> owner signoff -> integration checkpoint

Metric graph

BUDGET RISK TREND
open risks ████████
owned fixes ███████
unowned risks ██

Reports and artifacts

• budget delta dashboard

• ownership matrix

• milestone health report

• risk register

Mini case study

A timing overrun was solved only after budget ownership moved from shared to single-threaded.

Debug branches

• Validate contract revision

• Check owner signatures

• Audit milestone readiness

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.

Principal SoC review addendum

Milestones align RTL freeze, collateral handoff, floorplan lock, and signoff criteria so teams converge instead of iterating blindly.

Metric: milestone slip rate, integration blocker burn-down