How silicon programs are run, and why they slip.
Plain answers to the questions engineering and operations leaders ask about holding a silicon program to its date.
Guides
-
What is silicon program management?
Silicon program management is the work of holding every team, tool and supplier on a chip, equipment or qualification program to one date. Here is what it covers and why it is hard.
-
Why tape-outs slip: the anatomy of a schedule slip
Most tape-out slips are not engineering failures. They are changes that were visible in a tool on day one and reached the people who could act two weeks later. Here is how a slip actually unfolds.
-
First-silicon success is at a 20-year low. What it costs you
Only 14% of chip projects achieve first-silicon success, according to the 2024 Siemens / Wilson Research Group study. Here is what a re-spin costs and what moves the odds.
-
Firmware readiness: keeping software on the silicon date
When silicon slips, firmware usually keeps working to the old date. Here is why firmware and silicon drift apart, and how to hold bring-up software, drivers and SDKs to the same date as the chip.
-
Beta-tool programs: holding an equipment platform to its insertion window
A new semiconductor equipment platform has one deadline that does not move: the customer's insertion window. Here is how beta-tool programs slip, and what tracks the date across PLM, software and suppliers.
-
Qualification tracking for foundries and OSATs
Foundries, OSATs and test houses run dozens of customer qualifications at once, and are paid only after sign-off. Here is how quals slip, and how to make sure the customer hears it from you first.
-
Air-gapped AI for semiconductor design floors
Advanced-node, ITAR and foundry-restricted programs cannot send data to a cloud model. Here is what air-gapped AI means, what it needs, and how it runs on a sealed appliance.
-
The authority envelope: how much should AI be allowed to do on a chip program?
The useful question about AI on an engineering program is not whether to trust it, but what exactly it may do without asking. Here is how to set that boundary.
-
Decision receipts: auditing what an AI did on your program
If an AI takes an action on an engineering program, someone will eventually ask who approved it and why. Here is what a usable audit record contains.
-
The coordination tax: how much engineering time goes to finding out what is true
Roughly a third of engineering time on a large program goes to coordination, by industry estimate. Here is what that is, what it costs, and how to work it out for your own program.
-
Program memory: why the next chip program repeats the last one's mistakes
Every chip team learns hard lessons and loses most of them when the program ends. Here is what a program memory is, and what it can answer.
-
Tape-out checklist: what has to be true before a chip goes to the fab
A tape-out checklist for program leads: block-by-block sign-off evidence, waivers with owners, the downstream dates that must still hold, and the go/no-go a person makes.
-
ASIC tape-out timeline: a realistic schedule from spec to samples
What a realistic ASIC or SoC schedule looks like phase by phase, where the time really goes, why plans built on linear progress fail, and how to hold the dates you commit to.
-
What a silicon re-spin really costs
The full cost of a re-spin: the mask set, the fab cycle, the team's quarter, the customer's launch, and the market window. Why the cheapest re-spin is the one that is never needed.
-
Third-party IP on a chip program: managing delivery risk
Why licensed IP is the most common outside cause of a tape-out slip, how to contract and track IP drops, and what to do in the first hour after a vendor moves a date.
-
Semiconductor NPI phase gates: what each gate should prove
The phase gates of a semiconductor new-product introduction, from architecture freeze to production release, what evidence each gate needs, and why gates reviewed from slides let slips through.
-
RTL freeze: what it means, when to call it, and how to hold it
RTL freeze explained for program leads: what freezes and what does not, the evidence that says the design is ready to freeze, and how to keep the freeze from thawing through ECOs.
-
The insertion window: why an equipment program lives or dies by one date
What an insertion window is for a semiconductor equipment maker, what moves it, why missing it can cost a fab for a generation, and how to hold a platform program to it.
-
AI agents for semiconductor program management: what they can run, and what they must not
AI agents are arriving on chip programs. Here is the work they can take off a program manager today, the decisions that stay with people, and how to tell an agent that runs the program from one that summarises it.
-
NPI program management software for semiconductor: holding the phase gates to the date
New product introduction on a chip, module or tool runs through phase gates that each prove something. Here is what software has to do so each gate is reached on the planned date with the proof already assembled.
-
Tape-out schedule software: what has to be true for the schedule to be believed
A tape-out schedule in Microsoft Project or Smartsheet is as current as its last edit. Here is what software needs in order to hold a tape-out date rather than describe it.
-
How to prevent a chip schedule slip, rather than explain one
Schedule slips on chip programs are explained in retrospectives and rarely prevented. Here is the operating discipline that keeps the date where it was committed.
-
Silicon program risk management: from a risk register to risks that get worked
A risk register lists what might go wrong. On a chip program the risks that matter are already moving somewhere in the tools. Here is how to manage risk against evidence.
-
Dependency tracking on a chip program: the dependencies that cross tools and companies
The dependencies that break a chip schedule are the ones no single tool can see: between an IP vendor and verification, between PLM and the build, between the fab and firmware. Here is how to hold them.
-
Two programs, one team: settling an engineering resource conflict before it costs a date
When two programs need the same engineers in the same month, the conflict is usually discovered when one of them slips. Here is how to see it early and settle it on the numbers.
-
Post-silicon bring-up: a plan that is ready the day the samples arrive
The weeks after first silicon are the most schedule-critical on a chip program and the least planned. Here is what a bring-up plan has to hold, and how to keep it true as the samples date moves.
-
What a chip program manager actually does, and what the job becomes when the collection is automated
The chip program manager role is mostly collection and chasing, with judgment squeezed into the gaps. Here is the job as it is, and the job as it becomes when software holds the date.
-
The semiconductor PMO: running programs to their dates instead of reporting on them
A semiconductor PMO is usually measured on the quality of its reporting. Here is how a PMO is set up to be measured on dates held, and what it needs to get there.
-
When the foundry shuttle date moves: what has to happen in the next hour
A shuttle or hot-lot date moving is routine for a foundry and a crisis for the program that was built around it. Here is what has to be re-planned immediately, and how to make that automatic.
-
Semiconductor equipment program management: holding a tool program to its insertion window
A capital equipment program is mechanical, process, firmware and software work converging on one customer insertion window. Here is what has to be held, and how to hold it.
-
Holding an AEC-Q100 qualification to its date: the lots, the ovens and the customer
Automotive qualification is a long chain of stress lots, reads and reports with a customer sign-off at the end. Here is how the schedule slips, and how to hold it.
-
Running an engineering program across sites and time zones without losing a day a week
A chip or systems program spread across three sites loses time at every hand-off. Here is where the days go and how to hold the program as one thing.
Use cases
-
How to catch a supplier delay before it moves your tape-out
A late IP delivery is announced in an email. Here is how that email turns into a missed tape-out, and the four steps that stop it.
-
Tape-out readiness: how to answer “are we ready?” in minutes
A tape-out readiness review usually runs on slides that took days to build. Here is what readiness really consists of, and how to read it from the tools instead.
-
Verification coverage closure: how to see it falling behind early
Coverage rarely fails suddenly. The curve flattens weeks before anyone calls it late. Here is how to forecast coverage closure against the date.
-
How to run a program review on exceptions instead of status
Most program reviews spend two hours establishing what is true. Here is how to make the review twenty minutes about what needs deciding.
-
Root-cause analysis for a missed silicon milestone
After a slip, the usual finding is the last visible symptom. Here is how to find the decision that actually caused it.
-
What to tell a customer when a qualification slips
A qualification delay is survivable. A customer finding out from a late shipment is not. Here is what to send, and when.
-
ECO impact: tracing an engineering change across a chip program
A late engineering change order looks small where it is made and expensive where it lands. Here is how to see the whole impact before approving it.
Comparisons
-
Jira for chip design: what it holds, and what it can't see
Most chip teams run Jira. It tracks tickets well and cannot see a coverage curve, a timing report or a foundry email. Here is where it fits on a silicon program and what sits above it.
-
AI Employees, agents and copilots in semiconductor engineering
Copilots help one engineer. Agents do one task inside one tool. An AI Employee holds a role in a program, with an identity, a scope and a record. Here is the difference and why it matters for governance.
-
Can ChatGPT or Claude manage a chip program?
General AI models are capable and cannot run a silicon program on their own. Here is what they lack — and it is not intelligence.
-
EDA AI agents and the program layer: who holds the date?
EDA vendors now ship AI agents that do engineering work. They are useful, and they stop at the edge of their own tools. Here is what sits above them.
-
Program management tools for semiconductor teams: what each one owns
Jira, PLM, ERP, EDA dashboards and spreadsheets each own part of a silicon program. None owns the date. Here is the map.
-
Semiconductor program management software: the tools teams use, and what each one is for
A buyer's guide to the best-known program management software for semiconductor companies: Planview, Planisware, Siemens Teamcenter, ServiceNow SPM, Broadcom Clarity, Microsoft Project, Smartsheet, Jira, ONES.com, Jama Connect, and where Tymeline sits above them.
-
Hardware program management software: why the tools built for software fall short on silicon
Hardware programs have long-lead parts, suppliers, fabs and physical samples. Here is what program management software has to do differently for them, and which tools do it.
-
Engineering program management software: the difference between planning a program and running one
Most engineering program management software plans and reports. A program is run between the reports. Here is what to look for in software that runs it, for chip, systems and equipment companies.
-
Tymeline compared with Planisware, Planview, Jira Align and Smartsheet on a semiconductor program
An honest comparison for teams evaluating portfolio and planning platforms for chip, equipment or qualification programs, and where a layer that runs the program fits beside them.
Briefings
-
AI regulation for engineering programs: EU AI Act, NIST AI RMF and ISO 42001
Three frameworks now shape how AI may be used inside engineering organisations. Here is what each one is, and what they ask for in common.
-
AI coding agents in firmware teams: who holds them to the release?
Firmware organisations now run dozens of AI coding agents. They produce a great deal of code and none of them answers for the release date.
-
Autonomous program management: what the phrase should mean on an engineering program
Vendors are starting to say autonomous. On a chip or systems program the phrase should mean something precise: software that holds the date and acts inside a boundary people set. Here is the definition and the test.
-
An immutable audit trail for engineering decisions: what Tymeline ID records and who can read it
When AI and people both act on a program, the record of who did what has to be permanent and tamper-evident. Here is what Tymeline ID records, how it is anchored, and who gets access.
-
Every chip program is run on information that is two weeks old
Shrikar Nag, founder and CEO of Tymeline, on why programs with the best engineers in the world still slip: the people deciding can only see the program as it was at the last review.
-
An AI should earn authority on a chip program one action at a time
Shrikar Nag on why he distrusts 'autonomous' pitches, and how Tymeline's AI earns authority: observe, diagnose, recommend, then act, each kind of action inside a limit a person sets.
-
Give every AI employee an identity, or keep it away from your program
Shrikar Nag on the difference between an AI that chats and one that works: a name in your identity provider, a scope, a signed record of everything it did, and a switch that turns it off.
-
Why we built Tymeline for silicon first
The founder's account of why a company born from research on organisational intelligence chose the semiconductor program as the first thing to run: it is the hardest program there is, and the one where a slip costs the most.
-
What the first-silicon numbers are really telling us
Shrikar Nag on the industry's own data: first-silicon success at a twenty-year low and most projects late. The numbers are not an engineering problem, and treating them as one is why they are not improving.
References
-
Semiconductor program glossary: the terms a program lead needs
Plain definitions of the terms used on chip, equipment and qualification programs: tape-out, RTL freeze, coverage closure, ECO, re-spin, beta tool, insertion window and more.
-
What a program layer is: the always-on layer above the engineering tools
A program layer sits above Jira, source control, EDA, PLM, ERP and the test floor, holds every commitment to one date, and acts when one moves. The definition, and how it differs from the tools below it.