Release to Manufacturing (RTM): What It Means in Software and in Hardware

Release to manufacturing (RTM) has two meanings. In software, it is the final build of a version, handed over for duplication and distribution. In hardware, it is the frozen design package that a plant or contract manufacturer builds the product from.

Both share one idea: freeze one version, sign it off and hand it to the people who make the copies. After that, it changes only through a formal process. This glossary covers the terms around each meaning, plus the release package for a printed circuit board (PCB) assembly.

Software release terms

Release candidate (RC)

A release candidate is a build that is ready to ship unless significant bugs show up.¹ Its features are complete and no showstopper bugs are known. If testing finds one, the team builds the next candidate. This stage is also called “going silver”.¹

Release to manufacturing (RTM)

RTM is the point at which a software version is final and ready to be delivered.¹ The signed-off build goes to whoever makes the copies, whether a disc replication plant or a download server. After RTM, fixes ship as patches or new versions.

Going gold

“Going gold” is another name for reaching RTM.¹ The final build is called the gold master, and it goes to mass duplication. The name comes from mastering in the audio record-making industry.¹

General availability (GA)

General availability is the stage at which the product can be bought, because all commercialization work is done. That work includes security and compliance tests, localization and worldwide availability. Even then, availability can depend on language, region, and download versus physical media.¹

RTM vs GA

RTM is the day the build is final. GA is the day customers can buy and use it. The gap runs from days to months while the commercialization work is finished.¹ Put simply, RTM is an engineering milestone and GA is a commercial one.

Go-live in a running plant

Neither RTM nor GA decides when a new version reaches your shop floor. Putting a vendor update or an in-house tool into a running plant is a release of its own. It follows a release checklist with a rollback path and a smoke test, which our production release process page sets out for small manufacturing software and AI teams.

Hardware build gates: EVT, DVT and PVT

Hardware teams commonly reach a release through three build-and-test gates: the engineering, design and production validation tests (EVT, DVT and PVT).² What follows is common usage, not a standard. Each company defines its own gates and their order, and some merge, skip or rename them.

EVT: engineering validation test

Early prototypes answer one question: does the engineering concept work? The build checks core functions, key components and technical feasibility.² An Instrumental guide gives its purpose as finding all the issues the design needs fixed.³

DVT: design validation test

DVT asks whether the complete design meets its requirements: performance, durability and function together.² Contract electronics manufacturer BELI Technologies sets the DVT exit where the product meets its full spec and certification samples are submitted.⁴

PVT: production validation test

PVT asks whether the approved design can be produced reliably.² The Instrumental guide puts its purpose as verifying mass-production yields at mass-production speeds.³ Where the formal release sits is a company decision. Some release the design when DVT ends, so PVT builds from released documents. Others wait until PVT has proven the yields.

Names and order vary

The Instrumental guide notes that a few companies use slightly different nomenclature, and its own sequence adds a proto build before EVT and a ramp after PVT.³ Wikipedia expands EVT as engineering verification test.⁵ BELI calls merging EVT and DVT reasonable for a simple board derived from a proven reference design, and lists skipping DVT as a common failure mode.⁴

The hardware release package for a PCB assembly

The release package is the set of files a plant or contract manufacturer builds from. A contract manufacturer needs a file package even before the first EVT build;⁴ the release package is its final, frozen form. Every file in it must represent the same design revision,⁶ and after release it changes only through an engineering change order (ECO).

The first five rows follow the file list that PCB assembler Screaming Circuits asks for;⁶ the other four cover test, firmware, packing and records.

For the fields behind each BOM line, see Electronic Parts Data Management for Small EMS and OEM Teams.

Change control after release: ECR, ECO and ECN

After release, nobody edits the package directly. A change passes through three documents.

Engineering change request (ECR)

An ECR proposes a change and gives the reason for it. A change review board weighs its technical and business justification and plans it as a minor or major change.⁷ A rejected request stops here.

Engineering change order (ECO)

An ECO is the approved document that authorizes a change to the product and its documents.⁸ It names the affected parts and drawings, the reason, and the documents and departments involved. It also says when the change takes effect: immediately (scrapping current stock), at the next production run, or at another milestone.⁸

Engineering change notice (ECN)

An ECN is the official notice that a change has been approved. Many companies send a formal ECN to contract manufacturers and other partners so they build the product correctly.⁹ The names overlap, though: some companies call the change order itself an ECN.⁸

A different release: production orders in an ERP

In an enterprise resource planning (ERP) system, “release” is a planning step for a single production order, not a design hand-off. In SAP S/4HANA, releasing an order changes its status from created to released. Only then can the plant print order papers and post goods issues, confirmations and goods receipts.¹⁰ In PeopleSoft Manufacturing, released production is sent to the shop floor and is available to start.¹¹

FAQ

Do cloud and web products still have an RTM?

Often not as a separate step: Google Cloud moves products from Preview to General Availability, which it defines as open to all customers and ready for production use.¹² The term lives on in build names. Microsoft marks a SQL Server build “RTM” when no service packs or hotfixes have been applied.¹³

Is a design freeze the same as a release?

No: a freeze stops changes to part of the design, often gate by gate. In BELI’s gate table, the schematic is frozen at EVT exit, and the BOM and mechanical design at DVT exit.⁴ The release comes when the whole package is signed off and handed to production.

Who should sign off a hardware release?

The people who carry the cost of a bad release: the design owner, quality and manufacturing engineering, with purchasing reviewing the BOM. If a contract manufacturer builds the board, ask it to confirm in writing which revision it will build. Record names in the release record, not just roles.

What if PVT finds a design problem?

Treat it as a change, not a line fix: raise an ECR, approve an ECO and issue a new revision. BELI warns that every part swap after DVT invalidates some validation data and can trigger re-quoting, new fixtures or even re-certification.⁴ Weigh that cost before approving.

How do you stop purchasing from buying parts for an old revision?

Purchasing usually orders from the ERP, so compare the ERP’s BOM with the released one before every build. A line-by-line comparison shows added, removed and changed parts; How to Compare Two BOM Revisions in Excel walks through the method. Put your contract manufacturer on every ECN as well.