For the CEO, COO, or owner rolling AI across a network of plants, not a single line. How to sequence it, which plant to start with, and how to standardize the data layer once so plant two is a repeat and not a rebuild. Written at the level of the person who owns the P&L and the decision.
Read this first · Who this is for
This is a decision document for the person who signs the check, not an implementation guide for the plant floor. If you run more than one facility, the AI question is not really about models. It is about whether you build one operating standard your whole network inherits, or a different pile of tools at every site that no one can govern and no one can compare.
There are no invented numbers on this page. Every figure that matters here is one you already have on your own books, giveaway, re-keyed hours, unplanned downtime, recall exposure, or is a public rule with a link. We do not quote adoption rates or industry averages, because the only benchmark that should move a capital decision is your own network.
Why you sequence this, and never run it everywhere at once
The instinct at the top of a plant network is to move fast and even. Announce an AI initiative, hand every plant manager a budget, and let each site pick a tool. It feels decisive. It is the single most expensive way to do this, because it produces a different stack at every location and no way to roll any of it up.
The reason is structural, not cultural. AI runs on data a system can read, and most high-production plants still run on paper batch sheets, one person's spreadsheet, and machines that talk to nothing. When every site solves that gap on its own, you get five different data models, five vendors, five naming schemes, and five integration bills. A copilot at Plant A cannot answer a question about Plant C because the two plants do not describe the same thing the same way. You have spent real money and still cannot see your network as one thing.
Sequencing fixes this at the source. You solve the data problem once, at one plant, deliberately, and you turn that solution into the standard every other plant inherits. The first plant is not a pilot in the throwaway sense. It is the template. That is the whole thesis of this playbook.
What is actually on the table, in P&L terms
Before the how, the why it is worth your attention at all. These are the line items a disconnected network leaks into, and every one of them is something you can measure on your own books rather than take on faith.
Cost
Duplicated spend per site
A separate tool, integration, and support contract at every plant, plus the staff hours spent re-keying the same numbers into systems that do not share them. Multiply your own per-site figure by your plant count.
Risk
Recalls and audit exposure
When a trace has to cross receiving, production, quality, and shipping by phone and binder, the clock a regulator sets does not care that it is hard. The exposure compounds with every site that cannot answer fast.
Position
Competitive drift
A network that can see itself live schedules, forecasts, and reacts as one. A network of disconnected plants reacts a shift late at each site. The gap widens quietly, then shows up in margin.
The order it has to happen in, at every plant
Whatever plant you start with, the work inside it follows the same unglamorous order the ready plants all followed: digitize, connect, unify, before any AI. Digitize gets records off paper at the station. Connect gets machines and systems sharing what they already know. Unify pulls all of it into one live layer that is current and entered once. Only then does AI have something to stand on. Many controllers can already share data at the PLC over OPC UA, so the common problem is not a plant that cannot measure. It is a plant whose measurements stop at the panel. You are not buying a model. You are building the floor the model stands on, and you are building it in a way plant two can copy.
The five parts of the full playbook
Here is the shape of it. Each part is one decision you make once for the whole network. You can see the headings and the logic free. The full playbook under each, the actual how, opens to your work email or right here on this page.
Part 01
Which plant goes first
Decision: pick the template site
The pilot site is chosen on evidence, not on which plant manager is loudest or which site is largest. The full logic weighs readiness, willingness, how representative the site is, and the size of the P&L the fix would move.
Part 02
How to standardize the data layer
Decision: define the corporate standard
Digitize, connect, and unify once, then freeze the result as the standard every other plant inherits: one data model, one set of names and units, one live layer. This is the part that makes the rest repeatable.
Part 03
How to templatize the rollout
Decision: turn plant one into a pattern
Everything the first plant taught you, documented so plant two is a repeat of a known pattern and not a fresh discovery project. What to reuse, what is genuinely local, and how to shorten each site after the first.
Part 04
How to avoid one-off tools per site
Decision: standardize the stack
The trap that quietly doubles your spend: a different point tool at every plant that nobody can compare or govern. How to standardize the platform and data model so you integrate once, not once per site.
Part 05
Governance across plants
Decision: name the owner
Who owns the data-layer standard, the naming conventions, the security posture, and the rollout sequence, so consistency holds as sites come online and does not drift back into five stacks.
If you have not yet confirmed the first plant is even ready to be the template, the AI Readiness Checklist is the plain list to work through, and the AI Readiness Assessment scores a single site in twelve questions. For a dollar figure on what the gaps cost, the ROI Calculators & Tools price it on your own inputs.
The full playbook
Get the full rollout playbook.
You have seen the five parts and the logic above. Enter your work email and the full playbook opens right here on this page, and a copy goes to your inbox to share with your leadership team.
The full pick-your-first-plant scorecard, with the four factors weighed against each other
How to standardize the data layer once so every other plant inherits it
How to templatize the rollout so plant two is a repeat, not a rebuild
How to avoid a one-off tool per site, and how to govern the network centrally
Work email only. We use it to send the playbook and nothing else you did not ask for. Unsubscribe anytime.
Unlocked. The full playbook is open below, and a copy is on its way to your inbox. If you checked the box, a Harmony engineer will reach out to map it against your network.
Part 01 · Which plant first
Pick the template site on evidence
The first plant sets the standard for every plant after it. Choose it the way you would choose any capital bet: on the numbers, not on politics.
The mistake is starting at the largest, most complex, or most troubled plant because it feels like the one that most needs help. The first site is not where the need is greatest. It is where you can prove the pattern cleanly and produce a template worth copying. Score your candidates against four factors and let the evidence, not the loudest plant manager, decide.
Readiness. How much of this site already exists as data a system can read. A plant where machines already share counts over OPC UA and half the records are digital reaches a working template faster than one that is all paper.
Willingness. A plant manager who wants this and will free up their team beats a bigger plant that will resist every step. The first site has to be a partner, not a conscript.
Representativeness. The site should look enough like the rest of the network that its template transfers. A one-of-a-kind flagship teaches you little about the other nine plants.
P&L leverage. Of the sites that pass the first three tests, choose the one where the fix moves the most money you can measure: giveaway, re-keyed hours, unplanned downtime, trace time.
How to run the scorecard
Rate each candidate plant on the four factors, then weight readiness and willingness highest for the first site only. Speed to a working template matters more than size at this stage, because the template is the asset you are building. Save the hardest, most valuable, least ready plant for later in the sequence, once the pattern is proven and the rollout is fast. The goal of plant one is a repeatable win, not the biggest possible win.
Part 02 · Standardize the data layer
Build the standard once, then freeze it
This is the part that makes the whole network coherent. Digitize, connect, and unify at the first plant, then treat the result as the corporate standard, not a local build.
At the first plant you do the sequence in order, and as you do it you are writing the standard the network will inherit. Every choice you make here gets copied, so you make each one deliberately and once.
Digitize at the station. Get batch sheets, quality checks, downtime logs, and handoffs off paper where the work happens. A record written by hand does not exist to any software until someone re-keys it.
Connect the machines and systems. Get counts, states, faults, and cycle times off the PLCs and HMIs, and get the ERP, MES, quality, and warehouse systems sharing without a person carrying numbers between them.
Unify into one live layer. Pull all of it into a single current layer, entered once, that a scheduler, a search tool, or an agent can actually read.
Freeze the conventions. Name things once. One set of names for lines, shifts, defects, and units of measure, defined at the first plant and non-negotiable at the rest. This is what lets you compare Plant A and Plant C at all.
Why the standard, not the tool, is the point
A common failure is treating the first plant as a software install and moving on. The install is the easy part. The durable asset is the data model and the conventions, the agreement on what a record is, what it is called, and where it lives, because that is what every later plant copies and what lets your network report as one entity. If plant two invents its own names, you are back to five stacks even if every stack runs the same software.
Part 03 · Templatize the rollout
Make plant two a repeat, not a rebuild
Everything the first plant cost you in discovery is a cost you pay once, if you capture it. The output of plant one is not just a running plant. It is a documented template.
The difference between a network that rolls out fast and one that grinds is whether the first plant produced a reusable pattern. As you finish the first site, write down what transfers and what is genuinely local, so the second site starts from a template instead of a blank page.
Reuse the data model and conventions verbatim. Names, units, and the shape of the live layer do not get re-invented per site. They are inherited.
Reuse the sequence and the checklist. The order of digitize, connect, unify, and the list of capture points to close, is the same everywhere. Only the specifics of each station change.
Isolate what is truly local. Machine makes, line layouts, and a handful of site-specific processes are genuinely per-plant. Everything else is template. Name the local list explicitly so it does not expand.
Expect each site to get faster. Plant two is quicker than plant one, and plant three quicker again, because the template absorbs the discovery. If each site takes as long as the last, the template is not being used.
A first-party benchmark on template speed
Harmony runs the first plant as a fixed-scope engagement so the template is a known quantity, not an open-ended project: a one-time cost of $15,000 to $20,000, four to six weeks, with working software in your hands by the end of the pilot. That is a Harmony offer, stated plainly, not an industry average. The point for your planning is that plant one can be a bounded, repeatable unit rather than a bottomless integration, which is exactly what makes a network rollout forecastable.
Part 04 · Avoid one-off tools
Standardize the stack, integrate once
The most expensive outcome is not buying the wrong tool. It is buying a different tool at every plant and paying forever to reconcile them.
When each plant picks its own point solution, you do not get one problem five times. You get five problems that fight each other. Each tool has its own data model, its own export format, and its own contract, and the cost of making them talk lands on you every quarter, not once.
Standardize the platform, not just the goal. A shared mandate to "use AI" without a shared stack produces divergence. Pick the platform and data layer at the network level.
Integrate the data model once. When every plant lands in the same live layer, a new site is a configuration, not a fresh integration project with its own line item.
Refuse per-site data schemas. A local tool that stores records only its own way is a future migration you have not budgeted for. The standard is the price of admission for any tool that touches the floor.
Buy for the network, negotiate for the network. One relationship across all sites gives you leverage, one support path, and one roadmap, instead of five vendors each optimizing for one plant.
The test to apply to any tool
Before a tool goes into any plant, ask one question: does it write into the network standard, or does it create its own island. If it creates an island, the real cost is not this year's license. It is every future year you spend keeping that island in sync with the rest of the network, plus the day you have to rip it out to see your plants as one.
Part 05 · Governance across plants
Name one owner, or it drifts back to five stacks
Standards do not hold themselves. Without a single accountable owner, every plant slowly bends the standard to its own habits until you are back where you started.
Governance here is not bureaucracy. It is the one thing that keeps the money you spent on the standard from leaking away as each site quietly customizes. It is a small, senior function that owns the parts that must stay common, and leaves the rest to the plants.
One owner of the data-layer standard. A named person or small team that controls the data model, the naming and unit conventions, and what "done" means at a new site. Changes go through them, not around them.
One security and access posture. Set at the network level and inherited, so a new plant is not a new hole. Who can see what, and how the live layer is protected, is decided once.
One rollout sequence, reviewed. The order plants come online is a leadership decision that is revisited as you learn, not a free-for-all where sites jump the queue by lobbying.
Network-level reporting as the proof. The moment you can put every plant's numbers side by side, on the same definitions, the governance is working. If you cannot, a standard has already drifted.
The one external clock you do not set yourself
Most of this playbook is governed by your own standards. One thing is not. If you handle food, the pace of a trace is set by regulation, and it applies at every plant regardless of how hard it is. Under the FDA Food Traceability Rule, which implements section 204 of the Food Safety Modernization Act, covered firms must make required traceability records available to an authorized FDA representative within 24 hours of a request, and during an outbreak, recall, or other public health threat must provide the required information in an electronic sortable spreadsheet within that same window. A network where any single plant still traces by phone and binder is a network that cannot meet that clock everywhere, which is a board-level exposure, not a plant-floor one.
Source: 21 CFR 1.1455, paragraphs (c)(1) and (c)(3)(ii), FDA Food Traceability Rule.
Where a network rollout maps: the three phases
Every plant you bring online moves through the same three phases, and the sequencing above is just the order you take your sites through them. Plant one gets to Phase 1 the slow, deliberate way, because it is also building the template. Every plant after inherits the template and moves faster.
Phase 1
Lay the Data Foundation · Digitization
Every pen-and-paper record digitized at the station, every software system connected, and all of the data unified into one live layer. The digital transformation starts here, and this is the phase the template is built in.
Phase 2
Production & Operations Scale
Factory operations turn proactive: live sensors and machine data, the AI scheduling board, predictive maintenance before failure. Now repeatable across sites on the same standard.
Phase 3
AI-Native Operations
Agents across the floor and the back office act on the live layer: quality signals, reports, copilots. Humans approve. At the network level, this is where plants stop being islands.
The first plant is where Harmony builds the template with forward-deployed engineers on-site, doing the digitize, connect, unify work alongside your team, then hands you a pattern the rest of the network inherits. Phase 1 first, because that is the order it has to happen in. See what the live layer looks like.
