Back to all posts
Projects & Retrofits4 min read·September 26, 2026

What a Functional Design Specification Should Contain

TB
ThynkBlox Automation Team
Automation Engineering

What is a functional design specification?

A functional design specification, or FDS, describes what an automation system will do before anyone builds it. It sets out how the plant is operated, how each sequence runs, what every interlock protects, what the operator sees and how the system will be tested. Once signed, it becomes the contract for the build: the code is written to it, and the acceptance tests check against it.

It often decides whether an automation project finishes as planned, yet it is one of the first things cut short when a project is in a hurry.

Why sign it before any code is written?

Changes are cheap on paper and expensive on a panel. A disagreement about how a sequence should behave takes a meeting to settle during design. The same disagreement found during commissioning can cost a shutdown window.

A signed FDS protects both sides. Operations can check that the system described is the one they need. The integrator has a fixed scope to price against. When someone asks for a change later, there is a clear reference for whether it is a change at all, and it can be priced in writing before the work is done. See how to map a production process before automating it.

What should an FDS contain?

The contents vary with the size of the job, but a useful FDS for a PLC, SCADA or process project usually covers the following.

SectionWhat it answers
Scope and boundariesWhich equipment, areas and interfaces are included, and which are not
Control philosophyHow the plant is run: modes, start-up, normal operation and shutdown
SequencesEach step, the condition to move to the next, and what happens on a fault
InterlocksEach cause and effect, and what it protects
AlarmsEach alarm, its priority and the action the operator is expected to take
Operator screensWhat each screen shows and the order in which operators use them
I/O and tag scheduleEvery signal, with its range, units and name
InterfacesMessages exchanged with MES, ERP or other systems, and what happens if a link fails
NetworkThe architecture, and the separation between control and business networks
Acceptance testsHow each function will be proved at factory and site acceptance

What is often left out?

  • Failure behaviour. What happens when a sensor fails, the link to the MES drops, or power returns after an outage. Normal operation is easy to specify. Abnormal operation is where equipment gets damaged and production gets lost.
  • Manual and maintenance modes. How equipment runs while it is being cleaned, repaired or set up, and which protections stay active.
  • The purpose of each alarm. An alarm without a defined operator response is noise. If nobody can say what the operator should do, it probably should not be an alarm. Our guide to alarm management explains how to choose alarms an operator can act on.
  • Ownership of interfaces. When two systems exchange data, one party must own the message definition. Without that, each side assumes the other will adapt.
  • Test criteria. "The system works" is not a test. Each function needs a pass condition someone can witness.

Where do standards fit?

Standards give an FDS a shared vocabulary. IEC 61131-3 defines the programming languages used for PLCs, such as ladder diagram and structured text. ISA-95, also published internationally as IEC 62264, sets out models and terms for how control systems and business systems such as MES and ERP exchange information. Referring to them helps everyone read the document the same way. Referring to a standard is not a claim that a system is certified against it, and an FDS should not suggest otherwise. Where the project involves safety functions, their design should be carried out with a qualified functional-safety assessor, and the FDS should record that. Our guide to ISA-95 and where MES fits explains the levels in more detail.

Who should review it?

Management sign-off matters, but it is not enough. Ask the people who will live with the system to read the parts that affect them: operators for the screens and sequences, maintenance for the fault handling and manual modes, IT for the network and interfaces, and quality for anything that affects records or traceability. Their questions during review cost far less than their complaints after handover.

What does an FDS lead to?

The FDS feeds the acceptance tests, the I/O schedule, the code and the final as-built documentation. If plant data is part of the project, the tag names defined here are the ones every report and dashboard will depend on. Our article on what OEE tells you and what it hides shows why those definitions matter. For a plant that cannot stop, see how to plan a PLC retrofit around a shutdown window.

A good FDS is also yours to keep. If you choose a different integrator for the build, a complete specification lets them price and build the same system.

Related reading: SCADA vs MES and what each does and how to choose a system integrator for a plant project.


Planning an automation project or a retrofit? Our process starts with a fixed-fee assessment and a signed FDS before anything is built, and our services explain what each type of project delivers. For questions on ownership, pricing and safety, see our FAQ.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.