P1 — IPA P2 — LOA P3 — OTB P4 — SOP P5 — URS P6 — FRS P7 — ACM

P2 is a managed service engagementCTRL Designer works with your engineering team to conduct the LOA classification, rather than a standalone software purchase.

P2 Service Engagement Phase 2 — Classification

Level of
Automation™

LOA — ISA‑106 SBC & SqBC Classification Matrix

The LOA assessment classifies every unit operation and procedure in your facility across a structured Level of Automation matrix — determining whether each should be Manual, State-Based Control (SBC), Sequence-Based Control (SqBC), or fully automatic.

This is a critical design decision point in the ISA‑106 work process. The LOA output directly defines the scope and architecture of the URS and FRS that follow. Getting it right before committing to detailed design saves significant rework cost downstream.

LOA Classification Levels
L0
No Automation
Fully manual — operator-executed without DCS support
Manual
L1
Operator Initiated
DCS guides the operator step-by-step
Assisted
L2
Semi-Automatic
Operator confirms; DCS executes steps
Semi-Auto
L3
State-Based Control
DCS manages states and transitions automatically
SBC
L4
Sequence-Based Control
Ordered step sequences executed automatically
SqBC
L5
Fully Automatic
No operator intervention required
Auto

The Most Critical Design Decision Before URS Development

Before any User Requirement Specification can be written, the engineering team must agree on what level of automation is appropriate for each procedure and unit operation. This is the LOA assessment.

Assigning the wrong LOA — too high or too low — leads to over-engineered or inadequate automation. Both outcomes cost more to fix after implementation than during the design phase. The CDL LOA service ensures these decisions are made systematically, with the right stakeholders, against a consistent matrix.

  • Defines scope of SBC and SqBC automation for each Unit Module
  • Aligns operations, engineering, and management on automation intent before commitment
  • Prevents scope creep and rework in URS and FRS phases
  • Produces a traceable, documented rationale for each classification decision
  • Directly feeds into the URS structure — one LOA decision per UM
Outcome A — State-Based Control

SBC (ISA‑106 Levels 3)

The unit operation is governed by defined operational states with automatic transitions between them. The DCS monitors process conditions and moves between states without operator intervention — while still allowing manual override.

State Model Design P5 URS → P6 FRS CM / CCM Library
Outcome B — Sequence-Based Control

SqBC (ISA‑106 Level 4)

The unit operation follows a defined ordered sequence of steps — typically for batch operations, startup/shutdown procedures, or processes where step order is critical and non-negotiable.

Step Sequence Design P4 SOP → P5 URS Step / Transition Logic
Outcome C — Retained Manual

Manual or Assisted (Levels 0‑2)

Some operations are better left as manual or operator-assisted — particularly where process variability is too high, consequences of automation failure are severe, or frequency is too low to justify the engineering investment.

Operator Guidance DCS Advisory Only No SBC Required

The LOA Matrix in Detail

Each Unit Module and operation in your plant is evaluated against the following six-level LOA matrix. The CDL service engagement leads your team through this classification systematically, with documented rationale for each decision.

Level Classification Operator Role DCS Role ISA‑106 Type CDL Tooling
L0 No Automation Executes all steps manually without DCS support or guidance None — DCS is not involved in the procedure Manual Not applicable — no SBC design required
L1 Operator Initiated & Guided Initiates each step and follows DCS prompts and guidance displays Displays step instructions, monitors conditions, and alerts on deviations Assisted Operator guidance pages via P6 FRS; no ACM code generation
L2 Semi-Automatic Confirms each step before DCS proceeds; retains authority over sequence progression Checks pre-conditions and executes the step action upon operator confirmation Semi-Auto Step logic in P6 FRS; partial ACM code via P7
L3 State-Based Control Monitors operation; can intervene, override, or hold at any time Manages operational states and executes transitions automatically based on process conditions SBC Full URS (P5) → FRS (P6) → DDS → ACM Code (P7)
L4 Sequence-Based Control Monitors operation; authorises start of sequence; can abort Executes ordered step sequence automatically; manages interlocks and transition conditions SqBC SOP (P4) → URS (P5) → FRS (P6) → ACM Code (P7)
L5 Fully Automatic No routine intervention required — supervision only Initiates, executes, and completes procedures autonomously based on process triggers Auto Full CDL pipeline P1‑P7; advanced control integration

How the LOA Service Engagement Works

The LOA service is delivered as a structured workshop engagement with your process control and operations engineering teams. It typically follows a completed IPA (P1) — using the loop performance and operability findings to inform the classification decisions.

1
Plant Area & Unit Module Definition
Review the ISA‑106 Physical Model and agree on the PA / UM / EM hierarchy for your facility — the classification units for the LOA matrix.
2
SOP & P&ID Review
Existing Standard Operating Procedures and P&IDs are reviewed to understand current operational practice for each Unit Module before classification begins.
3
LOA Classification Workshop
Each unit operation is evaluated against the LOA matrix in a structured workshop with operations, process control, and engineering stakeholders — producing a consensus classification with documented rationale.
4
SBC vs SqBC Determination
For all L3 and L4 operations: determine whether State-Based Control or Sequence-Based Control is the appropriate design pattern, and identify the P4/P5/P6 tooling path for each.
5
LOA Report & URS Scope Definition
Deliver the completed LOA matrix with classifications, rationale, and a defined scope for the URS phase — ready to feed directly into P5 URS Builder.
LOA Service Deliverables
PA / UM Hierarchy Document
Agreed ISA‑106 physical model structure for the facility — Plant Areas, Unit Modules, Equipment Modules.
LOA Classification Matrix
Full Level 0–5 classification for every unit operation, with stakeholder-agreed rationale for each decision.
SBC / SqBC Determination Report
Identifies which operations require State-Based Control vs Sequence-Based Control and the design path for each.
URS Scope Definition
A defined list of Unit Modules requiring URS development — the direct input to P5 URS Builder.
CDL Tool Path Map
Maps each UM classification to the relevant CDL tools (P4, P5, P6, P7) and deliverables for the next phase.

LOA Classification Requires Engineering Judgment — Not Just Software

The LOA decision is one of the most consequential choices in the ISA‑106 work process. It cannot be automated — it requires experienced process control engineers working with your team's operational knowledge.

Cross-Functional Alignment

The workshop format brings operations, process control, safety, and management stakeholders together — ensuring LOA decisions reflect the full range of operational requirements and constraints.

Documented Rationale

Every classification decision is documented with the reasoning behind it — creating an auditable record that supports future modifications and regulatory review.

Prevents Costly Rework

A wrong LOA decision discovered during detailed design (P5/P6) or commissioning is expensive to fix. Getting it right at P2 is the most cost-effective quality gate in the entire CDL pipeline.

IPA-Informed Decisions

When P1 IPA has been completed first, the LOA classification is informed by actual plant performance data — loop rankings, oscillation findings, and operability indices — not just engineering assumptions.

Request a 30‑Minute Zoom Overview

A comprehensive presentation of the LOA service — scope, methodology, deliverables, and fit with your project — is available by Zoom. Contact us at info@CtrlDesigner.com with your company email to request a session.

Request Session
Next in the Pipeline
P3 — Operational Trend Builder (OTB)
Visualise your plant hierarchy and develop initial SBC step lists from historian data.
View P3 — OTB