A turnkey label without a written boundary leaves gaps to resolve during installation. Define the included work, exclusions and named owners, then tie requirements to FAT/SAT evidence. The table is a scope worksheet, not a claim that every contract includes these items.
| Category | Included work to list | Exclusions / others’ work to list | Responsibility to name |
|---|---|---|---|
| Equipment | Machines, formats, conveyors and auxiliaries | Existing or buyer-supplied machines | Supplier / plant per item |
| Connections | Mechanical transfers, signals, network and controls | Plant-system links outside the boundary | Integrator + adjacent-machine owners |
| Safety | Combined assessment, safeguards and validation | Site tasks allocated to the plant | Safety designer / validator / plant |
| Building | Installation and connection points | Foundations, utility supply, access and permits | Site owner / installer |
| Trials | FAT/SAT, materials, witnesses and handover | Unassembled interfaces requiring later tests | Test owner / signatories |
Use integration ownership to compare delivery arrangements and line design to establish the output requirements.
What turnkey means
In its plainest form, a turnkey packaging system is a complete packaging line, or a complete section of one, supplied by one party that is accountable for the whole result. It is often described as covering everything from product feeding through primary packaging, secondary packaging, and end-of-line work such as case packing and palletizing. One supplier writes the line controls, runs one acceptance test of the combined line, and delivers one documentation set.
Three features separate a true turnkey scope from a bundle of machines sold together. First, one party is accountable: if the combined line fails to meet the specification, that supplier answers for it, and it cannot blame another vendor’s machine unless the contract says the buyer supplied that machine. Second, the deliverable is a defined end state, a line that meets a written performance specification, not a list of delivered items. Third, interfaces are the supplier’s job. Mechanical transfers, signals, safety zones, and network connections between machines are all inside its scope.
A scope that sells a palletizer, a conveyor, and a stretch wrapper in one quote but leaves the buyer to connect them is not turnkey in this sense, however it is marketed. Look at what the supplier promises about the finished line, not about the delivered boxes.
The word is not the contract
“Turnkey” does not replace a written scope, and neither party should assume that anything not listed is included. Buyer and supplier still need to state which machines, conveyors, controls, services, site work, trials, training, and handover evidence are in scope, and which items are excluded or supplied by others.
Technical meaning: one line, one control philosophy
Technically, turnkey integration pays off most when it gives the line a single control philosophy. Machines coordinate through defined signals and states. A line controller or a clear set of permissions decides what happens when a machine stops, when a buffer fills, or when a downstream machine is not ready. Alarms and downtime reasons are reported in a consistent way.
PackML offers a common machine-state vocabulary. OMAC’s public overview explains its role; the ISA edition listing identifies ISA-TR88.00.02-2022. Accessed October 8, 2026; the cited edition is 2022, alongside OMAC’s 2022 Implementation Guide, without a “latest” claim. Ask which project signals and states are implemented and tested.
A turnkey scope normally covers:
- process and package handling design, including how each package is oriented, grouped, and buffered
- mechanical design of transfers, guides, and conveyors between machines
- line controls, operator interfaces, and any link to plant systems
- a safety concept for the entire line, with a combined risk assessment
- electrical and pneumatic distribution, as far as the scope defines
- installation supervision or installation itself
- commissioning, acceptance testing, training, and documentation
Define the scope in writing
Scope definition is the most valuable single task on a turnkey project. A proposal that cannot be compared with another proposal line by line has not been scoped.
What to list as included
The scope should state the equipment boundary, the product and package formats, conveyors, controls, safety interfaces, utilities, installation, trials, training, documentation, and support responsibilities. For each interface, state who owns the mechanical transfer, the signals, the network connection, and the safety circuit.
What to list as excluded or supplied by others
Common gray areas are building modifications, foundations, incoming electrical power, compressed air supply, process water, ventilation, lifting equipment, internet access for remote support, trial material, local permits, and waste removal. Any of these could fall to either party, so write them down and assign each one.
Existing equipment
Many projects include machines the buyer already owns. A supplier cannot take full responsibility for equipment it did not choose and cannot inspect. The usual answer is to list the existing machines, define their condition, and either assign a defined interface scope for them or carve them out of the performance guarantee. This is also where the line between turnkey and multi-vendor blurs, and the scope should say so plainly.
Controls scope
For controls interfaces, list start and stop permissions, ready and fault signals, accumulation logic, alarm behavior, safety interfaces, network requirements, and who is responsible for each connection. Also settle the program source: whether the buyer receives it, whether it is documented well enough to modify, and what access the supplier keeps for support.
The user requirement specification
The user requirement specification (URS) is the buyer’s document. It states what the line must do in terms the supplier can design against and the buyer can test. Suppliers can help draft one, but a URS written entirely by the party who will be judged against it is weak. The buyer should own it.
| Section | What it should state |
|---|---|
| Products and formats | Every package type, size range, and weight range, including difficult cases, and which format is the hardest |
| Rate | Required sustained rate for each format, defined over a shift and not as a short peak, and what counts as a stop |
| Changeover | Number and type of changeovers expected per week, target time, and who performs them |
| Environment | Available floor area, ceiling height, floor loading, utilities, temperature, washdown or dry cleaning |
| Hygiene and materials | Sanitation level, materials of construction, and any food, beverage, or pharmaceutical requirements |
| Safety and standards | Applicable regulations, guarding approach, and lockout needs |
| Controls and data | Platform preferences, network, reporting needs, remote access policy |
| Documentation | Drawings, manuals, software, parts lists, and training materials, and the language and format |
| Acceptance | FAT and SAT conditions, test materials, duration, and pass criteria |
Mark each item as a requirement or a preference. Requirements must be met. Preferences guide design when there is a choice. A URS made entirely of requirements leaves no room for engineering judgment, and one made entirely of preferences cannot be tested.
Link each requirement to the test that will verify it. This traceability makes acceptance objective. Without it, the end of the project becomes an argument over what was promised.
Copyable URS-to-evidence record
This proposed matrix is a record structure, not predetermined pass criteria. Enter the actual URS clause, test protocol revision and named person; leave unsupported results open.
| URS clause / requirement | FAT / SAT test | Evidence / result | Responsible person |
|---|---|---|---|
| ___ Sustained rate and SKU | FAT ___; SAT ___; duration and allowed stops per clause | Count/stop log ___; pass/fail ___ | ___ |
| ___ Changeover | Operator-run change between specified formats | Timed record ___; pass/fail ___ | ___ |
| ___ Interface / controls | Ready, fault, blocked and restart sequence | Trace and drawing revision ___ | ___ |
| ___ Safety / access | Approved safeguarding validation procedure | Validation file ___; unresolved blocking items ___ | ___ |
| ___ Documentation / training | Handover review and backup recovery check | Document register and training record ___ | ___ |
For each deviation, add class ___; action ___; owner ___; closure date ___; closure evidence ___. Use the commissioning acceptance record for stage-by-stage tracking.
Project phases
Turnkey projects differ in detail, but the phases are consistent.
1. Requirements and concept
The buyer writes or confirms the URS. The supplier proposes a concept: machine types, rough layout, conveying approach, and control architecture. This is the cheapest stage at which to change direction, and many rate and layout questions are settled here. The packaging line design page explains the reasoning behind rates, buffers, and machine selection.
2. Detailed design and contract
The supplier produces detailed layouts, electrical and control designs, and interface lists. The contract is finalized with the scope, schedule, payment milestones, acceptance criteria, and warranty. Review the interface list carefully, because any boundary nobody has claimed will turn up later as a change order.
3. Build and software
Machines are built, conveyors are fabricated, and the control software is written. On a multi-machine line, parts may be built at different sites. Ask how often progress will be reviewed, and whether the buyer can see drawings and software structure before the test.
4. Factory acceptance test
The line, or as much of it as can be assembled, is tested at the supplier’s site. A factory acceptance test is worth running when it checks a function agreed in advance against a written requirement, with representative product and a defined method. Items that cannot be tested at the factory, such as those that depend on site utilities or connected machines, should be assigned to a later stage in the protocol. Open items should have an owner and a route to closure.
5. Shipment, installation, and commissioning
Equipment is shipped, installed, connected to utilities, and brought up in stages. Commissioning tunes sensors, speeds, and sequences with actual product. Plan who attends, who has authority to sign off, and who trains operators.
6. Site acceptance test and handover
The site acceptance test checks the installed line against the agreed criteria using the buyer’s utilities, materials, and operators. Documentation, spare parts and training are handed over according to the agreed milestones. Warranty starts at the trigger written in the contract, which may be shipment, delivery or signed site acceptance; SAT alone does not establish that trigger. This matches the commissioning warranty guidance. A written punch list tracks anything outstanding. The commissioning and acceptance checklist summarizes the points a FAT and SAT protocol should state.
Acceptance testing
Acceptance testing is where a turnkey contract proves its value or shows its weakness. Three principles keep it useful.
Agree the test before the contract is signed. SAT conditions should identify the product, material, staffing, test duration, sample quantity, inspection method, and permitted planned stops. Disputes arise when the test is not defined until the line is ready.
Use the same core criteria for FAT and SAT. If FAT uses one definition of rate and SAT another, neither result can be compared with the other, and neither can be tied back to the URS.
Supply representative material. A line tested on ideal cases will pass, then struggle on the warped, overfilled, or damp cases that arrive in production. The contract should say who supplies test material and what range of difficulty it includes, with the hardest format and at least one changeover.
Define what counts as a pass. A rate target should specify the duration, the products, the allowed stops, and how stops are logged. Reject criteria, fault recovery, and safety device checks belong in the same protocol. Formal acceptance should record the protocol revision, witnesses, deviations and their classification, and the closure evidence for any open item.
Risk allocation
A turnkey contract moves risk; it does not remove it. Be specific about which risks sit with which party.
| Risk | Typically with the supplier | Typically with the buyer |
|---|---|---|
| Machine performance on specified products | Yes, if the products are defined in the URS | Defining the products accurately |
| Interface failures between supplied machines | Yes | No, unless the buyer supplied a machine |
| Existing or buyer-supplied equipment | Only for the agreed interface | Condition and performance of the equipment |
| Product and packaging variability | Within the stated range | Outside the stated range |
| Utilities and building | As scoped | Anything excluded from scope |
| Schedule | For supplier activities | For site readiness, access, and approvals |
| Changes to requirements | Assess impact and agree treatment under the change clause | Approve scope, price and schedule changes as agreed |
| Validation, where regulated | Protocol work as scoped | Accountable for the qualified state |
Two sources of risk deserve particular attention. The first is change control. A line is specified against a URS, and if the buyer adds a format after signing, price and schedule effects should be negotiated under the agreed change-control clause; no automatic entitlement is assumed here. Agree how changes will be proposed, priced, and approved before any are needed.
The second is hidden speed assumptions. The packaging line design literature warns that vendors often rely on a simple speed profile that ignores the interactions between every machine and every accumulation zone. Ask a turnkey supplier how it set machine speeds, buffer sizes, and surge capacity, and whether the guaranteed rate came from the combined line or from the rating of the slowest machine. The page on packaging line design explains why this matters.
In regulated industries the supplier may create and run validation protocols, but the buyer remains the owner of the qualified state. The buyer should approve the supplier’s validation plan and supporting documents before testing begins.
How the equipment fits
A turnkey line is made of the same equipment categories as any other line. At the end of the line, a typical sequence is case packing, case sealing, conveying, palletizing, and stretch wrapping. The turnkey supplier’s task is to make those machines behave as a unit. Read about case packers for the machine at the top of the end-of-line sequence, case conveyors and accumulation conveyors for the buffering between machines, and robotic palletizers or conventional palletizers for the machine at the end.
For sector-specific examples of how the same machines are arranged, see the beverage packaging and food packaging pages. Selection guidance for the final machine is in how to choose a palletizer, and cost context is in the palletizer cost guide.
When turnkey is a poor fit
A turnkey contract is not the right answer to every project. Consider another structure when any of these applies.
- Requirements are still changing. A turnkey price depends on a stable URS. If product formats, rates, or building constraints are unsettled, a phased approach or an engineering-only first stage costs less than repricing changes.
- The line depends on specialized machines from several sources. A single supplier may only be able to guarantee what it builds or knows, and a multi-vendor project with a named integrator may produce a better line.
- The buyer wants to own and modify the controls. If the plant expects to change sequences, add machines, or integrate with its own systems, source code access and documentation become central, and some turnkey contracts limit them.
- The project is a small addition to an existing line. A single machine such as a new palletizer at the end usually needs a well-defined interface scope, not a turnkey contract.
- The buyer has strong engineering resources. Plants with capable controls and project teams can often manage a multi-vendor build and keep the flexibility it provides.
- The market for suppliers is thin. If only one supplier can bid, the buyer has little bargaining power on price or terms, and a more modular purchase may help.
- The schedule cannot absorb a single point of failure. If one supplier’s delay holds up everything, parallel contracts may reduce schedule exposure, though they raise coordination effort.
Checklist before signing
- The URS is written by the buyer and covers products, rate, changeover, environment, hygiene, safety, controls, documentation, and acceptance.
- The scope lists what is included, what is excluded, and what is supplied by others, including utilities and building work.
- Every interface has a named owner for the mechanical, electrical, controls, and safety parts.
- The rate guarantee states the product, the duration, the stops allowed, and the measurement method.
- FAT and SAT protocols exist in draft, use the same core criteria, and name the test materials.
- Documentation, program source access, spare parts, and training are listed with delivery dates.
- Change control, payment milestones, and warranty terms are agreed.
- The buyer has named an owner for site readiness, utilities, and sign-off.