Procedure Automation for Continuous Process Operations ⌂ Table of Contents
Chapter 1

Scope

50% Summary Edition

What This Standard Covers

This standard provides the framework for automating operational procedures in continuous process operations — chemical plants, refineries, and power generation facilities. It defines models, implementation styles, control strategies, design philosophies, and the complete lifecycle approach for procedure automation.

Definition

Procedure automation refers to the systematic conversion of manual operating procedures into automated control sequences executed by a DCS or PLC.

What Procedures Are Covered

The standard covers procedures for continuous process operations including: start-up, shutdown, abnormal situations, hold steps, and transitions between product grades. These procedures typically already exist as manual documentation before automation begins.

Primary objectives of automation: increase uniformity and consistency, reduce operational risks from human error, lower long-term costs, and minimize programming errors when converting manual procedures to control logic.

System Levels and Boundaries

This standard applies to automated procedures running on control systems at ISA-95 Levels 1 and 2 — basic control (field devices, PLCs) and supervisory control (SCADA, HMIs). It does not cover Level 3 (MES/operations management), batch processes, or Safety Instrumented Systems (SIS) with a claimed SIL rating. It does cover BPCS interfaces with SIS systems.

Note

SIS systems are intentionally excluded because they require separate, more stringent standards due to their critical safety functions.

Two Automation Styles

Two styles are defined in this standard:

The choice between styles depends on the company's automation philosophy and the capabilities of the selected DCS.

Mandatory Requirements

The standard separates mandatory requirements from informational content by marking each requirement with a "Requirement" heading. Every mandatory clause specifies which party (system integrator, end user, equipment manufacturer) must implement that requirement. A complete list of responsible parties is in Table 10.