00

Engineering process

8 STEPS

From site survey to supported system.

Automation projects fail in predictable places: unclear requirements, untested logic, rushed commissioning. Each of our eight steps ends with a signed deliverable, so risk is retired early rather than discovered on site.

00

Engineering process

From site survey to supported system.

Automation projects fail in predictable places: unclear requirements, untested logic, rushed commissioning. Each of our eight steps ends with a signed deliverable, so risk is retired early rather than discovered on site.

  1. 01Survey1–3 weeks
  2. 02Specify2–4 weeks
  3. 03Engineer4–10 weeks
  4. 04Build4–12 weeks
  5. 05FAT2–5 days
  6. 06Install1–3 weeks
  7. 07SAT1–4 weeks
  8. 08SupportOngoing
FIG. 1 · Project delivery · Rev A

01

Step by step

What happens at each step

01

Step by step

What happens at each step

01

Discovery & site survey

Typical duration · 1–3 weeks

Inputs

Production data, drawings, a walk of the line, the problem in your words.

Engineering work

Measure the line, record constraints, define the problem and the success measures.

Deliverable

Survey report and a budget estimate.

Your involvement

Operations, maintenance and engineering contacts available on the day.

02

Requirements & functional specification

Typical duration · 2–4 weeks

Inputs

Survey report, your standards, safety and IT requirements.

Engineering work

Write what the system must do: sequences, rates, interfaces, safety functions, acceptance criteria.

Deliverable

Functional specification and an FAT/SAT test plan.

Your involvement

Review and sign off the specification. This is the most important approval.

03

Concept & engineering

Typical duration · 4–10 weeks

Inputs

Signed functional specification.

Engineering work

Layout, reach and cycle simulation, electrical design, safety design, software structure.

Deliverable

Design review package: drawings, simulation results, risk assessment.

Your involvement

Design review meeting; approve layout and interfaces.

04

Build, software & integration

Typical duration · 4–12 weeks

Inputs

Approved design.

Engineering work

Panel build, mechanical build, PLC/robot/HMI programming, testing against a simulation model.

Deliverable

Assembled system in our integration hall, internal test record.

Your involvement

Optional progress visit; supply sample parts or products.

05

Factory acceptance test

Typical duration · 2–5 days

Inputs

Test plan, production parts, your operators.

Engineering work

Run every test in the plan: safety functions, cycle and rate, changeovers, fault recovery.

Deliverable

Signed FAT report with open items listed, owned and dated.

Your involvement

Attend FAT; operators run changeovers themselves.

06

Installation

Typical duration · 1–3 weeks

Inputs

Site readiness: floor, utilities, access, shutdown window.

Engineering work

Dismantle, ship, install, connect and dry-cycle; cutover for retrofit projects.

Deliverable

Installed system, interfaces connected.

Your involvement

Site access, permits, utilities, coordination with production.

07

Site acceptance & commissioning

Typical duration · 1–4 weeks

Inputs

Installed system, SAT plan.

Engineering work

Re-test safety in place, ramp to rate under production conditions, verify MES/WMS interfaces.

Deliverable

Signed SAT report, documentation, software backups.

Your involvement

Production time for the performance run; sign-off.

08

Training & lifecycle support

Typical duration · Ongoing

Inputs

SAT handover.

Engineering work

Operator and maintenance training, remote support, backups, health checks, spare-parts advice.

Deliverable

Training records, support agreement, spare-parts list.

Your involvement

Name support contacts; schedule health checks.

02

Risk controls

How the process reduces project risk

02

Risk controls

How the process reduces project risk

01

A signed specification

Acceptance criteria are agreed in numbers before design starts, so “done” is not a matter of opinion.

02

Simulation before FAT

Control logic is tested against a model of the line before hardware exists.

03

FAT with your operators

Your people run changeovers and fault recovery in our hall, not for the first time on site.

04

Open items on record

Anything not met at FAT or SAT is listed with an owner and a date — and published in our project records.

05

Shutdown-aware cutovers

Retrofit work is planned to your shutdown windows, with pre-wired panels and fallback plans.

06

Handover you can use

Documentation, backups and training are deliverables, not afterthoughts.

Starting a project?

Begin with step one: tell us about the line.

An engineer replies within one business day.

Starting a project?

Begin with step one: tell us about the line.

An engineer replies within one business day.

Create a free website with Framer, the website builder loved by startups, designers and agencies.