2. References

This standard references several key technical documents that control engineers must follow as mandatory requirements (normative documents). The specific editions listed below were current when this standard was published, but these referenced documents get updated regularly with new revisions.

Important Note: Always verify you’re using the most recent version of these referenced standards before implementing any control system design or modifications. The standards organizations (ISA for automation, ANSI for American national standards, IEC for international electrotechnical standards, and ISO for international standards) maintain current lists of valid documents on their websites.

When this standard refers to these external documents, it references the technical content and requirements rather than pointing to specific section numbers. This approach ensures the references remain valid even when the referenced documents are reorganized or updated.

Practical Tip: As a control engineer, bookmark the standards databases from ISA, ANSI, IEC, and ISO to stay current with revisions that might affect your projects, especially for safety-critical applications where compliance is essential.

ISA-5.06.01-2007 Functional Requirements Documentation for Control Software Application

This standard provides guidelines for documenting the functional requirements of control software applications used in industrial automation systems. The functional requirements define what the control system must do rather than how it does it (the “what” versus the “how”).

Definition: Functional requirements specify the behavior, operations, and control logic that the software must perform to meet the process control objectives.

The documentation framework covers several key areas that control engineers need to address when specifying control software. These include defining the control strategy, operator interface requirements, alarm management specifications, and safety interlocks. The standard also addresses data handling requirements, such as how process variables are collected, processed, and stored.

Industrial Example: In a temperature control loop, a functional requirement might state “The system shall maintain reactor temperature between 180-185°C” rather than specifying the specific PID tuning parameters or control algorithm details.

The standard emphasizes the importance of clear, unambiguous language when writing requirements. Each requirement should be testable and verifiable during commissioning and ongoing operation. This approach helps ensure that the final control system meets the intended operational needs and safety requirements.

Note: Following this standard helps bridge the communication gap between process engineers who define what needs to be controlled and software developers who implement the control logic in DCS, PLC, or SCADA systems.

The documentation should also include interface requirements with other systems, performance specifications (response times, update rates), and any regulatory compliance requirements that impact the control software functionality.

ANSI/ISA-18.2-2016, Management of Alarm Systems for the Process Industries

This industry standard provides comprehensive guidelines for designing, implementing, and maintaining alarm systems in process control environments (such as chemical plants, refineries, and manufacturing facilities). The standard addresses the complete alarm lifecycle, from initial philosophy development through ongoing management and optimization.

Definition: An alarm system notifies operators of abnormal process conditions that require timely response to prevent safety hazards, equipment damage, or production losses.

The standard establishes key principles for effective alarm management, including alarm rationalization (the systematic review and justification of each alarm), prioritization based on consequence severity, and performance benchmarking. It emphasizes that alarm systems should support operators rather than overwhelm them with nuisance alarms or chattering (alarms that rapidly switch between active and inactive states).

Industrial Example: A well-designed alarm system in a distillation unit might prioritize high-pressure alarms as critical safety alerts while treating minor temperature deviations as lower-priority operational guidance.

ISA-18.2 defines specific performance metrics such as alarm rates (typically targeting fewer than 6 alarms per operator per 10 minutes during normal operations), response times, and standing alarm counts. The standard also covers alarm system documentation, training requirements, and change management procedures to ensure sustained performance.

Note: This standard is widely recognized as the benchmark for alarm management in process industries and is often referenced in safety management systems and regulatory compliance frameworks.

ANSI/ISA-88.00.01-2010 serves as the foundational standard for batch control systems, providing essential models and terminology that every control engineer working with batch processes needs to understand. This standard (commonly referred to as S88 or ISA-88) establishes a comprehensive framework for designing, implementing, and operating batch manufacturing control systems.

The standard defines batch control as the automation of batch processes through the creation of batch recipes, management of production resources, and execution of batch production. Definition: A batch process produces finite quantities of material by subjecting specific amounts of input materials to an ordered set of processing activities over a finite time period using one or more pieces of equipment.

ISA-88 introduces several critical hierarchical models that structure how we think about and implement batch control systems. The physical model defines equipment hierarchy from enterprise level down to control modules (the smallest controllable units of equipment). The procedural model outlines how recipes and procedures are organized, from general recipes down to specific control recipes that actually execute on the plant floor. The process model describes the relationship between products, formulas, and the actual batch processes.

Industrial Example: In a pharmaceutical manufacturing facility, the physical model might include a reactor vessel (unit) containing agitators and temperature control systems (equipment modules), while the procedural model would define the mixing and heating procedures required to produce a specific drug compound.

The standard emphasizes the separation of product-related information (what to make) from equipment-related information (how to make it), enabling greater flexibility in production scheduling and equipment utilization. This separation allows the same recipe to run on different equipment trains, provided they have compatible capabilities.

Note: Understanding ISA-88 concepts is crucial for control engineers because it provides a common language and methodology that facilitates communication between process engineers, automation engineers, and operations personnel throughout the entire lifecycle of batch control system projects.

The ANSI/ISA 95.00.01-2010 standard (which is a modified version of IEC 62264-1) provides the foundational framework for integrating enterprise business systems with manufacturing control systems. This standard defines the essential models and terminology needed to bridge the gap between business-level decision making and plant-floor operations.

Key Purpose: This standard addresses the critical interface between Level 3 (manufacturing operations management) and Level 4 (business planning and logistics) systems in the automation hierarchy. It establishes common data models and definitions that allow enterprise resource planning (ERP) systems to communicate effectively with manufacturing execution systems (MES) and other control-level applications.

What it covers: The standard provides standardized object models for production schedules, work orders, material definitions, equipment capabilities, and production performance data. These models ensure consistent information exchange between business systems that plan what to produce and control systems that execute the actual production.

Note: Understanding this standard is essential for control engineers working on MES implementations or any projects involving data exchange between the shop floor and enterprise systems. The terminology and models defined here form the backbone of most modern manufacturing integration architectures.

Practical relevance: When implementing production tracking systems, recipe management, or performance reporting applications, this standard provides the reference framework for structuring data and defining system interfaces in a way that both business and control system stakeholders can understand and utilize effectively.