Procedural Automation Standard

The CDL
ISA‑106
Framework.

CTRL Designer provides the most complete commercial implementation of the ISA‑106 procedural automation standard — covering tools, work processes, and a published implementation guide.

ISA‑106 addresses continuous process operations including start-up, shutdown, abnormal situations, hold steps, and feed/output transitions — increasing uniformity and reducing automation risk, cost, and error.

CDL Tools for Excel™

A complete set of Microsoft Excel programs covering every ISA‑106 phase — from IPA through to ACM code generation.

ISA‑106 Implementation Guide

Being published on Amazon — a comprehensive reference covering the full CDL work process and ISA‑106 methodology.

Work Process Implementation

Converting your existing company work process to align with ISA‑106 using the CDL Lean Six Sigma DMAIC methodology.

ISA‑106 Module Library

Overview

CDL ISA‑106 Work Process Overview

High-level introduction to the complete CDL work process and how it maps to ISA‑106 procedural automation.

Read module
ISA106‑A

Overview & Framework

Introduction to ISA‑106 scope, purpose, and the procedural automation framework for continuous process industries.

Read module
ISA106‑B

Procedural Automation Models

Physical model hierarchy — Plant Area (PA), Unit Module (UM), Equipment Module (EM), and Control Module (CM).

Read module
ISA106‑C

Automation Styles

Classification of automation styles — from manual operations through to fully automatic state-based and sequence-based control.

Read module
ISA106‑D

State-Based Control (SBC)

Deep-dive into state model design: states, transitions, modes of operation, and step logic for Unit Modules.

Read module
ISA106‑E

Sequence-Based Control (SqBC)

Sequential automation design — defining ordered step sequences, interlocks, and transition conditions for batch and procedural operations.

Read module
ISA106‑F

Work Process Overview

The full ISA‑106 work process mapped across FEL1, FEL2, and FEL3 project phases — from feasibility through to implementation.

Read module
ISA106‑G

CDL Work Process Overview

How CTRL Designer's CDL toolset implements and extends the ISA‑106 work process for real industrial projects.

Read module
ISA106‑H

CDL Tools to Develop URS

Using P5 URS Builder to generate structured User Requirement Specifications aligned to IEC 63690 and ISA‑106.

Read module
ISA106‑I

CDL Tools to Develop FRS

Using P6 FRS Engine to design full Functional Requirement Specifications at UM, CM, and CCM level.

Read module

Procedural Automation for Continuous Process Operations

ISA‑106 is the international standard for procedural automation in continuous process industries. It addresses the full lifecycle of procedural operations — those situations that fall outside steady-state control: start-up, shutdown, abnormal situations, hold steps, and transitions between operating modes.

Before ISA‑106, these procedures existed only in manual written form. The standard's goals are clear:

  • Increase uniformity and consistency of procedure automation across facilities
  • Reduce the risk, cost, and errors associated with automating procedures
  • Provide a common language and model structure for engineering teams
  • Enable traceable, auditable automation design from SOP through to code

The CDL work process maps ISA‑106 to two industry-standard engineering frameworks: Front-End Loading (FEL) and the V-Model (GAMP) — making it compatible with how process engineering projects are actually managed.

URS — User Requirement Specification

"What to do" — not "How to do it"

Defines the purpose and justification of the procedural automation. Provides specific, measurable performance criteria. The URS is the owner's requirements document — technology-agnostic and system-independent.

FRS — Functional Requirement Specification

What the control system must do to satisfy the URS

Describes control system functionality without specifying implementation. Includes I/O definition, Step/Transition logic, and allocation of I/O to CM and CCM libraries. Specifies behaviour, not mechanism.

DDS — Detailed Design Specification

Everything needed to build the control system

A complete collection of CM and CCM definitions with all associated I/O and parameters. The DDS contains sufficient information to generate production-ready DCS code — which ACM does automatically.

V-Model & FEL Relationship

The CDL tools map precisely to both the V-Model lifecycle and the Front-End Loading (FEL) project framework — ensuring ISA‑106 work integrates with how process engineering projects are planned and executed.

FEL 1 FEL 2 — FEASIBILITY FEL 3 — REQUIREMENT & DESIGN / IMPLEMENTATION IPA Plant Assessment URS Plant Physical Model FRS Unit/Equipment Modules DDS Detailed Design Spec ACM Code DCS Code Generation DCS Simulation Unit Code Validation Commission Deploy to DCS Acceptance Testing Integration Testing Unit Testing Options Study Physical Model Requirements DDS Code Generation Validation Commissioning P1 IPA P5 URS Builder P6 FRS Engine P7 ACM

Front-End Loading (FEL) Implementation

The CDL toolset maps to each FEL phase — from performance baseline through to DCS code generation — providing a traceable, standards-aligned workflow for every project stage.

FEL 1
Options Study — Performance Baseline
  • 1 Development of performance baseline for existing plants utilizing IPA (Industrial Plant Assessment™ — P1).
FEL 2
Feasibility Study — Physical Model & URS
  • 1Review ISA‑106 Physical Model definition and terminology.
  • 2Develop the Plant Physical Model PM.
  • 3Review Standard Operating Procedures SOP and P&ID.
  • 4Divide PM into Unit Models UM and Equipment Models EM.
  • 5Develop Operating Trends OT for PM/UM using Operating Trends for Excel™.
  • 6Define the Mode of Operations MofO for each Unit Module.
  • 7Develop URS in CDL Tools™ package and import all PM tags.
  • 8Allocate tags to Units (UM) and define unit type: stand-alone, master, or reused/copy.
  • 9Generate FRS files automatically from the URS.
  • 10Review and develop CDL Generic CM and CCM Libraries for the project.
FEL 3 — Req.
Front-End Engineering Design — Requirements
  • 1Convert Standard Operating Procedures SOP to pseudo-Code pCode.
  • 2For each FRS, assign IO to objects in CM and CCM library.
  • 3Develop Operating Trends OT for Unit Modules using Operating Trends for Excel™.
  • 4Identify Steps from the OT analysis.
  • 5Add the Steps defined in OT to the FRS documents.
  • 6Add Step Transitions for each step in the FRS.
  • 7Import pCode to develop the Step‑CCM Matrix.
FEL 3 — Impl.
Front-End Engineering Design — Implementation
  • 1Select the DCS Vendor (Emerson DeltaV, Honeywell, ABB 800xA).
  • 2Map the User CM and CCM Library to the selected DCS library.
  • 3Generate the CDL Detailed Design Specification DDS.
  • 4Generate CDL code using the Automatic Code Maker ACM — P7.
  • 5Simulate the Unit CDL code to validate logic before DCS upload.
  • 6Generate the DCS Detailed Design Specification for deployment.

Front-End Loading (FEL) is used across process industries worldwide

ISA‑106 and the FEL framework apply wherever continuous process operations require structured procedural automation — from conceptual development through to commissioning. CTRL Designer has implemented CDL work processes across the following sectors:

Upstream Oil & Gas Petrochemical Natural Gas Refining Extractive Metallurgy Waste-to-Energy Pharmaceuticals Power Generation Chemical Processing Water Treatment Pulp & Paper Mining & Minerals Food & Beverage

Ready to Implement ISA‑106
at Your Facility?

Contact us to discuss your plant assessment, work process alignment, or a full ISA‑106 SBC implementation project using CDL tools.