ALGI Advisory e.U

Technical article · Industrial automation

Automation planning: clarify technical requirements before implementation

An automation project needs more than a suitable machine or a capable control system. What matters is how processes, equipment, operators and data work together in day-to-day operation. Sound technical planning therefore also addresses interfaces, faults and exceptional operating conditions.

By Alexander Girkinger · ALGI Advisory e.U

First understand the process and the intended outcome

Start with the operational task: which bottleneck needs to be relieved? Which processes need to become more stable? Where is data missing, or responsibility unclear? A faster individual machine does not automatically improve the entire process chain if material supply, changeovers or downstream equipment limit throughput.

Information on volumes, product variants, material flows, faults and manual interventions helps establish the technical requirements. Checking conditions on site is equally important: how is the work actually carried out, and where does practice differ from existing descriptions?

This leads to specific requirements. Instead of simply calling for a higher level of automation, define, for example, which product changeovers must be supported, what data operations need and how the plant should respond to an interruption.

Describe plant behaviour in concrete terms

A concept becomes useful for implementation when general objectives are translated into clear functions. Four areas deserve particular attention:

Plant structure and dependencies

Which sections of the plant form a functional group? What conditions must be met before that group can start? In what order are drives, conveying routes and auxiliary equipment started and stopped?

Operating modes and operator controls

Manual operation, automatic operation and local interventions need coordinated rules. The visualisation must show operators the current state, the actions available and why a function may remain disabled.

Faults and restart

A fault message alone is not enough. Define the response of the affected and connected plant sections, the acknowledgements required and the conditions for restarting. Material blockages and incomplete sequences also need to be considered.

Data points and technical identification

Equipment, sensors, drives and signals need consistent identification. A structured data point list connects technical functions with electrical engineering, PLC programming and visualisation.

Illustrative example: If a conveying unit is switched off during automatic operation, the behaviour of upstream equipment must also be defined. Otherwise, a single operator action may cause a material blockage in the process chain. These dependencies belong in the functional specification from the outset.

PLC and production IT: define data handovers clearly

An interface is more than a list of transmitted values. What matters is how both systems use those values and respond to missing, invalid or delayed information.

  • Input data: Which system supplies recipes, setpoints, orders or production targets?
  • Validation and acceptance: How is the completeness and plausibility of new data checked? How is acceptance confirmed or rejection reported?
  • Feedback: Which operating states, faults and quantities are reported back to IT?
  • Connection failure: How is a failure detected, and what response is specified for the particular process?
  • Material and traceability: How are quantities, sources, destinations and production batches kept correctly associated during changeovers or when material streams are combined?

When extending an existing plant, also check which interfaces and program functions can be retained and which need to be modified. Technical responsibilities and system boundaries should be explicitly documented.

Practical example: a technical automation concept for an industrial combined milling plant

Alexander Girkinger draws on experience from his earlier project work developing a detailed automation concept for an industrial combined milling plant. The following example describes his technical concept work and subsequent involvement in commissioning.

The technical task

The functions of a new milling plant had to be specified for PLC programming, visualisation and connection to an existing production IT system. Cleaning stages, milling and product discharge needed to be treated as one connected process, including their mutual dependencies.

His personal contribution

Alexander Girkinger prepared the technical specification and a supplementary data point list. These covered:

  • The functional structure of the plant, including prerequisites and sequences for starting and stopping.
  • Operator controls and visualisation functions for manual and automatic operation, fault acknowledgement and restart.
  • Data exchange between the PLC and production IT, including input data, status messages and connection monitoring.
  • Recipe handling, product and destination changeovers, and requirements for material transactions and production batch tracking.
  • Requirements for maintenance counters, yield monitoring and the technical identification of equipment and signals.

What the example demonstrates

For recipe transfer, the specification required the prescribed blend proportions to add up to 100%. If the total was invalid, the PLC was to reject the transfer, report this to IT and continue using the data already loaded. Triggers and data handovers were defined for material transactions. Product and destination changeovers were addressed in terms of sequence conditions and their effects on material flow.

This provided a documented technical basis for implementation: functions, dependencies and data handovers were described, while unresolved matters remained visible. Its value lies in translating the operational process into requirements that can be implemented.

Supporting the subsequent commissioning phase

In the subsequent project phase, Alexander Girkinger also supported and led commissioning on site. He accompanied the implementation of the specified PLC, visualisation and IT functions. The example therefore combines technical specification work with operational responsibility during start-up.

This anonymised example draws on technical specification documents and Alexander Girkinger's account of his subsequent commissioning leadership. The requirements described do not constitute evidence of individual acceptance tests. Safety engineering was addressed in a separate document.

How technical planning supports an investment decision

A clear description of functions and interfaces makes it apparent what a quotation or implementation contract must cover. It helps compare scope boundaries, identify unresolved prerequisites and determine the engineering and integration effort more precisely.

An economic assessment also needs reliable information on investment costs, ongoing expenditure and expected benefits. In addition to equipment purchase, relevant items may include control system modifications, interfaces, commissioning, training and start-up. Statements about benefits should be linked to actual operating conditions and the assumptions used.

Technical specification and economic assessment serve distinct but related purposes: the specification describes the required solution and its prerequisites. The economic assessment examines whether the expected benefits justify the expenditure.

If a key technical prerequisite remains uncertain, first determine what evidence is needed. Depending on the question, this may involve a test, a pilot or clarification of an interface. This helps distinguish the next steps that are already justified from those that still depend on further clarification.

What should be clear before implementation is commissioned

  • The operational objective and the process under consideration are clearly defined.
  • Key plant functions, operating modes and exceptional conditions are described.
  • Interfaces, data ownership and technical responsibilities are assigned.
  • Each open issue has an owner and a planned step for resolving it.
  • Requirements for operation, maintenance and technical documentation are considered.
  • The necessary safety assessments and evidence are planned for the specific project.
  • Testing, commissioning and acceptance have clear criteria.

The level of detail depends on the task. A short description may be sufficient for a limited modification. Several connected plant sections and IT systems require a correspondingly more detailed technical specification.

Frequently asked questions about automation planning

Is a quotation from the equipment supplier enough?

A quotation describes the scope offered. You should also check whether it fully covers the required operating functions, interfaces and responsibilities. When integrating equipment into an existing plant, some tasks may fall outside the supplier's scope.

Why must faults be addressed at the concept stage?

Because the response to an interruption is part of the plant's functionality. Shutdown, material flow, operator intervention and restart must work together. Gaps discovered only during commissioning may require additional coordination and technical modifications.

Is technical planning useful without financial figures?

Yes. It clarifies functions, technical prerequisites and the required scope. The subsequent economic investment assessment also needs cost and benefit data. A technical specification alone cannot establish a payback period.

What information helps with an initial assessment?

A short process description, the intended outcome and information on existing equipment provide a useful starting point. Existing concepts, quotations, plant overviews and known faults help clarify the task. Missing information is recorded as open issues.

Further reading

When the project is already under pressure

Bring the remaining technical scope, the team and operational leadership together.

Read the article on project stabilisation

Explore technical examination and assessment in more depth

The published specialist books explain the structured examination of technical substance, assessment and management reporting. The book series is available in German.

Explore the book series (German)