Automatic line specification guide

How to Specify an Automatic Packaging Line

Create a supplier-ready requirement that defines what the line must do, the conditions it must handle and how successful performance will be judged.

Automatic packaging line being specified as a connected system

A useful packaging-line specification describes the production duty rather than prescribing machinery too early. It lets suppliers apply the right filling, handling and integration knowledge while keeping quotations comparable.

1. Begin with the production objective

State the business problem the project must solve. It may be labour availability, output growth, dose consistency, closure quality, traceability, product presentation, safety, ageing equipment or the need to launch a new pack.

Rank the objectives. A line designed primarily for maximum speed can look very different from one designed for many short campaigns and fast clean-down. The specification should make those priorities visible.

  • Current process and its main constraint
  • Required date or operational trigger
  • Expected production growth
  • Non-negotiable quality or safety outcomes
  • Functions that may remain manual

2. Build a complete product and format matrix

List every product, fill quantity, container, closure, label and downstream pack the line must handle. Group similar formats, but do not hide meaningful differences such as bottle taper, pump dip tubes, cap liners or label positions.

Mark the priority format, the smallest and largest formats, and any difficult combination. Include credible future packs where their dimensions or process needs could affect the machine choice.

Example format matrix fields
FieldExample informationWhy it matters
ProductFree-flowing liquid, cream, powderDetermines product path and dosing principle
ContainerMaterial, dimensions, neck, rigidityDetermines handling, tooling and transfers
ClosureScrew cap, pump, trigger, sealDetermines feed and application method
LabelSize, position, winding, variable dataDetermines labeller and coding arrangement
Secondary packBundle or case count and patternDetermines collation and end-of-line route

3. Describe product behaviour and product supply

The product name alone is not a filling specification. Record viscosity or bulk density range, temperature, foaming, particulates, static, corrosivity, solvent content, aeration and any tendency to string, drip or settle.

Explain how product reaches the line. Batch vessels, pumps, hoppers, mixers, heating, recirculation and level control can be part of the filling performance. Include cleaning and product-change expectations.

  • Representative product condition at the filler
  • Minimum and maximum fill quantity
  • Target accuracy and verification method
  • Product-contact material requirements
  • Cleaning method and frequency
  • Safety data and hazardous-area information where relevant

4. Define output as useful production

Avoid stating only a machine speed. Define the number of accepted packs required over a realistic period and show the production pattern that supports it. Include the format mix, product supply, component replenishment, quality checks, breaks, clean-down and changeovers.

Also state whether the line must recover from short stops and how much buffer is acceptable. These assumptions guide nozzle count, cap-feed capacity, conveyor accumulation and end-of-line equipment.

  • Normal sustained output
  • Maximum short-term rate
  • Good packs per shift
  • Shifts and operating hours
  • Campaign and batch size
  • Changeover and cleaning frequency

5. Map the required line sequence

Describe the process from the way empty packs arrive to the way finished goods leave. Mark manual operations, quality checks, rejects, sampling points and any existing machines that must remain.

Do not assume every stage needs automation. A controlled manual activity can be the correct choice where formats are highly variable or the volume does not justify complex component feeding.

  1. Container loading, unscrambling or rinsing
  2. Filling or dosing
  3. Closure feeding and application
  4. Sealing, coding, labelling and inspection
  5. Accumulation, collation and end-of-line packing
  6. Transfer to the next production or logistics operation

6. Define controls, data and quality responses

State the controls functions that matter to your operation: recipes, access levels, production counts, alarm history, line status, code data, inspection results or connection to site systems. Separate essential functions from optional reporting.

For every inspection, define what is checked, what constitutes failure and how a rejected pack is contained and confirmed. A sensor without a defined response is not a complete quality control.

  • No-container-no-fill and no-cap logic
  • Machine and line stop philosophy
  • Recipe ownership and access
  • Coding data source and verification
  • Reject confirmation and full-bin response
  • Required production or downtime data

7. Survey the site and working envelope

Provide a measured layout with columns, doors, drains, low ceilings, existing machines, operator routes and maintenance access. Confirm the delivery path as well as the final position.

List available utilities and site standards. Power, compressed air, extraction, product services, water, drainage and network connections can all affect cost, programme and layout.

  • Room dimensions and fixed obstructions
  • Access route and lifting constraints
  • Power and compressed-air details
  • Extraction, ventilation, drainage and washdown
  • Floor condition and loading
  • Guarding, safety and site integration standards

8. Set acceptance criteria before ordering

Acceptance criteria should reflect the operating objective and use representative formats. Define the test duration, output, allowed stoppages, quality measures, changeover demonstrations and the responsibilities for product and packaging materials.

Separate factory testing from site testing. Some conditions cannot be reproduced until the line is connected to the customer product supply, utilities and surrounding equipment.

Possible acceptance categories
CategoryExample criterionEvidence
OutputAgreed good packs over a defined runCounter and recorded rejects
FillDefined tolerance for selected samplesCalibrated measurement method
ClosurePresence and agreed application resultInspection and sample checks
Label/codePosition and readable required dataVisual or instrumented check
ChangeoverAgreed format restored safelyTimed or witnessed procedure

9. Compare proposals on the same assumptions

Ask suppliers to state exclusions, utilities, operator tasks, assumed component quality, effective speed, change parts, documentation, installation, training, spares and acceptance scope. A low equipment price can conceal integration or site work that remains with the buyer.

Compare the proposed operating model, not only the number of machines. Consider replenishment, cleaning, fault recovery, maintenance access and support throughout the expected life of the line.

Key takeaways

  • Specify the production duty and priorities before prescribing equipment.
  • Use representative product and component samples and a complete format matrix.
  • Define sustained good output, not only nameplate machine speed.
  • Include line interfaces, operator tasks, site services and quality responses.
  • Agree measurable acceptance criteria and responsibility boundaries before order.

Start with your product and production goal

Turn the guide into a project brief

Bring the product, pack format, output target and site information together. Lancing Ltd can then help narrow the appropriate automatic-line route.

Straight answers

Frequently asked questions

Should I write a user requirement specification before requesting quotes?

For complex or regulated projects, a structured user requirement is highly valuable. For simpler projects, a detailed line brief covering the same fundamentals may be sufficient.

Do I need samples before a budget quotation?

Basic budget guidance may be possible without samples, but representative product, containers, closures and labels are normally needed before a firm technical solution is confirmed.

How should output be stated?

State good packs per minute, hour or shift, plus shift length, format mix, planned breaks, cleaning and changeover assumptions. Distinguish required sustained output from short peak rate.

What should an acceptance test include?

Use agreed products and formats, a defined run length, measurable pass criteria, allowed interventions and a process for recording actions or deviations.

Next steps

Requirement traceability

Link every critical requirement to an owner, evidence source and acceptance check

A strong specification is traceable. Each critical requirement should identify why it matters, who provides the input, how the supplier proposes to meet it and how the result will be checked. This turns broad statements such as “easy changeover” or “high accuracy” into project decisions that can be reviewed.

Use an assumptions register alongside the specification. When information is unavailable, record the provisional basis and the sample, drawing, survey or trial needed to replace it with evidence.

Requirement traceability example
RequirementOwner or inputEvidence before acceptance
Sustained good outputBuyer demand profile and supplier line balanceDefined run using agreed products, formats and intervention rules
Format capabilityApproved component matrix and samplesWitnessed setup and production of selected boundary formats
Quality responseBuyer acceptance rule and supplier inspection designPass and fail challenges with confirmed reject handling
Interface completionNamed supplier or customer ownerApproved drawing, I/O test, utility check or site record

Information to prepare

  • Requirement identifier and priority
  • Source or business reason
  • Named owner and supplier response
  • Verification or validation method
  • Acceptance stage and record
  • Status, action and approved change

Continue the project

Use the related pages to turn this guidance into a clearer scope and a more useful technical discussion.

The separate FAT and SAT planning guide on Packaging Lines UK covers acceptance-test structure in more depth, avoiding a duplicate guide on this domain.

From user requirement to acceptance record

Build one controlled document set from production need to handover

The specification should not become one long document that tries to carry every drawing, sample, action and test result. Use a controlled set in which each document has a clear purpose, owner, revision and relationship to the other project records.

The main specification states what the line must achieve and the boundaries that apply. Supporting schedules then hold the changing detail: formats, interfaces, controls, trials, acceptance evidence and approved changes. Keep the same requirement references across the set so a decision can be followed from need to design and final proof.

Acceptance-ready automatic packaging-line document set
Controlled documentQuestion it answersDecision supported
Production duty and user requirementWhat accepted output, products, formats, shifts, quality outcomes and business constraints must the line support?Project objective, priority and line boundary
Format and sample matrixWhich product, container, closure, label, code, case and boundary combinations are approved?Machine range, change parts, trials and acceptance formats
Layout and interface scheduleWhere is each module located and who owns every mechanical, electrical, safety, utility, process and data boundary?Integration scope, site works and responsibility
Line-control narrativeHow should the complete sequence start, run, stop, starve, block, reject, change format and recover?Controls architecture, I/O, alarms and functional testing
Sample and trial planWhich uncertainties require representative materials, drawings or witnessed tests, and what result will close them?Technology selection and design-risk reduction
Acceptance protocolWhich formats, conditions, measurements, intervention rules and records will demonstrate the agreed requirement?Factory and site acceptance decisions
Change and action registerWhat changed, why, who approved it and what other documents, tests, price or programme items are affected?Controlled baseline through design and commissioning
Handover evidence indexWhich drawings, settings, software versions, backups, training records, spares and open actions describe the as-left line?Production ownership and maintainable support

Check each specification statement

  • What production or quality need does it support?
  • Which product, format and operating condition apply?
  • Who supplies the input or component?
  • How will the supplier respond?
  • How and where will the result be verified?
  • What record proves acceptance?
  • How will an approved change be controlled?

Use the same references through integration and site work

Carry the approved document set into interface control, factory testing, site readiness, commissioning and handover so requirements are not reinterpreted at each stage.

Complete the technical specification

Use specialist guides to close the highest-risk assumptions

The main specification identifies what the line must achieve. These guides provide the deeper schedules needed for controls, layout, utilities, trials, safety and acceptance.

Packaging Line Project Responsibility Matrix explains the project decisions, evidence and responsibilities that should be resolved before the relevant line scope is accepted.