Direct answer
An industrial automation project runs in this sequence: scope and process survey, control architecture and I/O list, detailed engineering documents, factory acceptance test (FAT), installation and site acceptance test (SAT), commissioning and startup, and formal acceptance. Each phase ends with a deliverable that the next phase depends on.
Institutional content: Authomathika
Published:
Automation projects fail less often from bad programming than from loose scope, late I/O changes and tests that were never defined. A clear sequence of phases, each with a named deliverable, keeps engineering, procurement, construction and operations aligned.
This guide follows the execution order and the documents that close each phase. For the conceptual background, see how industrial automation works and where it applies.
How do you survey the scope and the process to be controlled?
You start by defining what the process must do, what is being automated and what stays out. The output is a scope document that the client and the integrator both sign off on.
The survey is the foundation of every later phase. Gather these items before asking for a proposal:
- Process description, with P&IDs or process flow diagrams when they exist.
- Equipment list: drives, valves, instruments, analyzers and packaged units that bring their own controllers.
- Operating modes: automatic, manual, local, maintenance, startup and shutdown.
- Legacy systems to keep, replace or interface with (greenfield or brownfield).
- Safety, environmental and plant standards that apply.
- Interfaces with electrical, mechanical and piping disciplines.
- Site constraints: shutdown windows, access, utilities and who supplies what.
What is the role of the control architecture and the I/O list?
The control architecture defines which controllers, networks, operator stations and field devices make up the system and how they communicate. The I/O list is the inventory of every signal the system reads or writes. Together they size the project.
A control architecture is a diagram and a description of the hardware and communication layers, from field instruments to supervisory and enterprise levels. It answers questions such as where controllers sit, which PLC or DCS handles which area, which fieldbus or network each device uses, and where redundancy is required. The automation pyramid helps place each layer.
The I/O list is a spreadsheet or database in which each line is a signal, with at least:
- tag and description;
- signal type: digital input, digital output, analog input, analog output or network variable;
- range, units and signal standard;
- source equipment and location;
- alarm and interlock associations;
- assigned controller, rack or remote station.
Treat the I/O list as a controlled document. Every revision should be tracked, because panel design, programming, wiring and test procedures all derive from it. Where devices are distributed on a network, such as AS-Interface, the list should also record addressing and topology.
What engineering documents should you expect?
Expect a document set that lets someone else build, test, operate and maintain the system without the original designer. The exact list depends on scope, but the families below are standard.
| Phase | Typical deliverable | Main use | Usual owner |
|---|---|---|---|
| Scope | Scope of work, responsibility matrix | Contract baseline | Client and integrator |
| Basic design | Architecture diagram, I/O list, functional description | Sizing and approval | Integrator |
| Detailed design | Loop and wiring diagrams, panel drawings, cable list, instrument data | Construction and procurement | Integrator, with electrical discipline |
| Software | Control narrative, program, HMI screens, alarm list | Programming and review | Integrator |
| Testing | FAT and SAT procedures and reports | Acceptance evidence | Integrator and client |
| Handover | As-built drawings, backups, manuals, spare parts list | Operation and maintenance | Integrator |
For a deeper breakdown, read automation project documentation: what must be delivered. Panels are often a separate package, covered in industrial panel design stages and deliverables.
How do you plan factory (FAT) and site (SAT) tests?
A factory acceptance test (FAT) verifies the panels and software at the supplier's facility before shipment. A site acceptance test (SAT) verifies the same system after installation, connected to the real plant. Planning both from the start avoids discovering problems when the shutdown window is already running.
A good test plan includes:
- A written procedure approved before testing begins, listing each test, the expected result and the pass or fail criterion.
- The I/O list as the test base, so every signal is checked end to end, usually with simulation in the FAT.
- Functional tests of sequences, interlocks, alarms and operator screens against the functional description.
- A punch list for deviations, with a responsible party and a deadline for each item.
- Signed reports for both tests, with the software version tested.
The FAT reduces site risk because defects are cheaper to fix in the shop. The SAT confirms what the FAT cannot: field wiring, instrument calibration, communication with real equipment and behavior under real process conditions.
How do you organize commissioning and startup?
Commissioning is the staged energization and verification of the installed system, from loops and equipment up to the complete process. Startup is the first controlled operation with product or utilities.
A practical order is:
- Mechanical and electrical completion checks, including cable continuity and insulation checks by qualified personnel.
- Loop checks from field device to operator screen.
- Dry runs of equipment and sequences without product.
- Tuning of control loops and verification of interlocks and safety functions.
- Startup with product, with operations and engineering together on site.
- Operator training and a period of assisted operation.
When the work happens in a plant shutdown, such as an off-season maintenance stop, the commissioning plan must fit the window. The guide on how to develop an industrial project from start to handover shows how this connects with construction and handover.
Authomathika is an engineering integrator that covers electrical, automation, electromechanical assembly, panels and field services, and you can see how its automation business is organized.
Which acceptance criteria should the contract define?
The contract should state, in measurable terms, what counts as finished. Without this, acceptance becomes a negotiation after the work is done.
Useful acceptance criteria include:
- all FAT and SAT procedures executed, with reports signed by both parties;
- punch list items closed or formally accepted with a deadline;
- as-built documents and software backups delivered and matching the installed system;
- operating performance verified against the functional description, with the test conditions defined in advance;
- training completed and recorded;
- a defined support or warranty period after startup, with scope and response terms agreed in writing.
Avoid vague wording such as "system operating satisfactorily." Tie each criterion to a document, a test or a signature.
