2.1 Technical Feasibility Studies & Automation Architecture Alternatives

ISA CAP Certified Automation Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the ISA CAP Exam (2024 Content Outline)

2 Chapter 1: Feasibility Study — Scoping & Justification

1.1 Business Needs, Scope Definition & Operational Strategies 1.2 Automation Opportunity Assessment & Technology Screening 1.3 Benefit-to-Cost Analysis, Payback & Financial Metrics (NPV, ROI, IRR)

3 Chapter 2: Feasibility Study — Technical Analysis & Risk

2.1 Technical Feasibility Studies & Automation Architecture Alternatives 2.2 Preliminary Risk Assessment, Process Safety & Environmental Constraints 2.3 Preliminary Project Cost Estimating, Scheduling & Resource Requirements

4 Chapter 3: Definition — Requirements & Specifications

3.1 User Requirements Specification (URS) & Stakeholder Analysis 3.2 Functional Requirements Specification (FRS) & Functional Safety Requirements 3.3 Process & Control Strategy Determination (Continuous, Discrete, Batch & Hybrid) 3.4 Automation Boundaries, High-Level System Architecture & Scope Definition

5 Chapter 4: Definition — Safety, Cybersecurity & Cost Baseline

4.1 Regulatory Compliance & Safety Criteria (OSHA PSM, EPA RMP, 21 CFR Part 11) 4.2 Preliminary Security Architecture & Industrial Cyber Threat Assessment (ISA/IEC 62443) 4.3 Baseline Cost Estimating, Financial Justification & Project Viability Analysis

6 Chapter 5: System Design — Control Architecture, Field Devices & Motion

5.1 Control System Architecture Selection: PLC, DCS, SCADA & Hybrid Systems 5.2 Process Instrumentation, Sensor Selection & Analytical Measurement 5.3 Final Control Elements: Control Valves, Actuators & Variable Frequency Drives (VFDs) 5.4 Hazardous Location Classification, Electrical Safety & Enclosures (NEC, NFPA, ATEX/IECEx) 5.5 Discrete Devices, Motor Control, Motion Control & Mechatronics

7 Chapter 6: System Design — Safety Systems & Cybersecurity

6.1 Safety Instrumented Systems (SIS) & Safety Lifecycle (ISA-84 / IEC 61511 / IEC 61508) 6.2 SIL Determination, Verification & Layer of Protection Analysis (LOPA) 6.3 Industrial Cybersecurity by Design: Zones, Conduits & Security Levels (ISA/IEC 62443) 6.4 Hardware/Software Specifications, Procurement & Detailed Engineering Packages

8 Chapter 7: System Design — Networks, Continuous Control & Standards

7.1 Industrial Fieldbuses & Digital Communications (HART, Fieldbus, Profibus, Modbus) 7.2 Industrial Ethernet & Open Protocols (EtherNet/IP, PROFINET, OPC UA, MQTT) 7.3 Continuous Control Strategies: Feedback, Feedforward, Cascade, Ratio & Advanced PID 7.4 Batch Control Architecture, Recipes & Procedural Standards (ISA-88 / S88)

9 Chapter 8: System Design — HMI, Alarms, Enterprise Integration & Data

8.1 Human-Machine Interface (HMI) & High-Performance Graphics Design (ISA-101) 8.2 Alarm Management Lifecycle, Rationalization & Performance (ISA-18.2) 8.3 Enterprise Integration & Manufacturing Operations Management (ISA-95 / S95) 8.4 Data Flow Analysis, Historians, Relational Databases & Reporting

10 Chapter 9: Development — Software Logic & Programming

9.1 IEC 61131-3 Programming Languages: LD, FBD, ST, SFC and Legacy IL 9.2 Discrete Control Logic, Sequencing, State Machines & Interlock Implementation 9.3 Safety Logic Development, Burner Management & Interlock Verification 9.4 Software Configuration Management, Version Control & Change Tracking

11 Chapter 10: Development — Simulation, Tuning & FAT

10.1 Loop Tuning Methodologies & Dynamic Process Response (Ziegler-Nichols, Cohen-Coon, Lambda) 10.2 Simulation, Emulation & Hardware-in-the-Loop (HIL) Verification 10.3 Factory Acceptance Testing (FAT): Planning, Test Protocols, Execution & Punch Lists 10.4 Software Quality Assurance, Code Review & Validation Documentation

12 Chapter 11: Deployment — Installation, Wiring & Pre-Commissioning

11.1 Field Installation Oversight, Wiring Practices, Grounding & Shielding 11.2 Pre-Commissioning Checkout: Cold Loop Checks, Hot Loop Checks & Calibration 11.3 Site Safety Protocols, Lockout/Tagout (LOTO) & Permitting during Deployment 11.4 Installation Punch List Management & Defect Resolution

13 Chapter 12: Deployment — Commissioning, SAT & Turnover

12.1 Site Acceptance Testing (SAT): Execution, Environmental Validation & Variance Management 12.2 Commissioning & Startup Sequencing (Cold/Hot Commissioning & Fluid Runs) 12.3 Cutover Strategies, Legacy System Migration & Contingency Fallback 12.4 System Turnover, Operator/Maintenance Training Delivery & As-Built Documentation

14 Chapter 13: Operation & Maintenance — Diagnostics, Reliability & Training

13.1 Maintenance Strategies: Reactive, Preventive, Predictive & Reliability-Centered (RCM) 13.2 Troubleshooting Methodologies & Root Cause Failure Analysis (RCFA) 13.3 Calibration Management, Proof Testing & SIS Periodic Validation (IEC 61511) 13.4 Spare Parts Strategy, Critical Spares Analysis & Obsolescence Management 13.5 Asset Performance Management (APM) & Overall Equipment Effectiveness (OEE) Tracking 13.6 Training Needs Analysis, Training Delivery & Competency for Automated Systems

15 Chapter 14: Operation & Maintenance — Optimization, MOC, Security & Decommissioning

14.1 Loop Auditing, Process Variability Analysis & Control Optimization 14.2 Management of Change (MOC) Procedures & Software Modification Controls 14.3 Backup, Disaster Recovery & Disaster Recovery Testing for Industrial Systems 14.4 Operational Cybersecurity: Patch Management, Vulnerability Monitoring & Incident Response 14.5 Decommissioning Planning, Asset Retirement & Environmental Disposition

2.1 Technical Feasibility Studies & Automation Architecture Alternatives

Key Takeaways Explain This Topic AI

Automation system platform selection (DCS vs. PLC/PAC vs. SCADA vs. Industrial PC) hinges on process dynamics, loop density, determinism, and physical topology rather than raw I/O count alone.

Distributed Control Systems (DCS) excel in continuous process control with tight analog loop execution (100–500 ms) and unified databases, whereas Programmable Automation Controllers (PACs) lead in high-speed discrete logic (<10 ms scan times).

Supervisory Control and Data Acquisition (SCADA) systems address geographically distributed assets using telemetry, store-and-forward buffers, and low-bandwidth communications to remote RTUs.

Control equipment room feasibility requires calculating thermal dissipation (Q = 3.412 × P_watts), clean instrument grounding isolated from power grounds, and continuous compliance with ANSI/ISA-71.04 environmental corrosion limits (G1 through GX).

Fiber optic cabling selection balances bandwidth and distance: OM3/OM4 multi-mode fiber accommodates intra-plant runs up to 300–550 m, while OS2 single-mode fiber extends to 10–40 km with complete immunity to plant electromagnetic interference.

Last updated: October 2026

Engineering Feasibility and Control System Architecture Selection

In the initial lifecycle phases governed by the ISA Certified Automation Professional body of knowledge (Domain 1: Feasibility Study), selecting an automation platform is among the most consequential technical decisions an engineer faces. An inappropriate architecture selected during conceptual screening introduces severe operational bottlenecks, unmanageable lifecycle maintenance costs, or outright project failure. The objective of a technical feasibility study is not simply to identify hardware that can physically interface with field instrumentation, but to evaluate how well architectural alternatives satisfy the fundamental operating characteristics of the target process.

Automation systems are broadly grouped into four architectural families:

Distributed Control Systems (DCS) : Engineered natively for large-scale, continuous process facilities (refineries, petrochemicals, large power utilities) where regulatory analog control loops, unified tag databases, integrated alarm management, and high availability take precedence.

Programmable Logic Controllers (PLC) and Programmable Automation Controllers (PAC) : Engineered natively for high-speed discrete manufacturing, assembly, packaging, and unit machine control requiring rapid scan execution (typically 1 to 10 ms 1\text{ to }10\text{ ms} 1 to 10 ms ), modular I/O, and flexible programming under IEC 61131-3 standards.

Supervisory Control and Data Acquisition (SCADA) : Engineered for wide-area, geographically distributed infrastructure (pipelines, municipal water distribution, electrical transmission grids) where communication links may be intermittent, high-latency, or low-bandwidth, and remote assets require autonomous Remote Terminal Units (RTUs).

Industrial PCs (IPC) and Embedded Soft-PLCs : Engineered for computationally intensive specialized applications, including machine vision inspection, edge AI/ML inference, high-axis coordinated motion, and advanced algorithmic processing running on hard real-time operating system (RTOS) kernels.

Platform Comparison Matrix

Platform Architecture Primary Process Dynamics Typical Loop Execution Time Database & Tag Model High-Availability Redundancy Common Industrial Application

DCS Continuous fluids, thermal processes, large batch 100 to 500 ms 100\text{ to }500\text{ ms} 100 to 500 ms (deterministic) Single, globally unified tag database; controller and HMI synchronized 1:1 bumpless hot standby controllers ( < 20 ms <20\text{ ms} < 20 ms switchover); redundant field networks Oil refining, ethylene crackers, power boilers, pulp and paper

PLC / PAC High-speed discrete, sequential, packaging, skid systems 1 to 20 ms 1\text{ to }20\text{ ms} 1 to 20 ms (scan-cycle dependent) Controller-resident tags; separate HMI tag database requiring tag-mapping Optional 1:1 hot/warm standby; dual chassis sync modules Automotive assembly, high-speed bottling, turbine governor, OEM skids

SCADA Geographically dispersed, wide-area remote assets 1 to 10 s 1\text{ to }10\text{ s} 1 to 10 s supervisory; sub-second local RTU Centralized SCADA server database with asynchronous field RTU polling Redundant central servers; localized RTU store-and-forward buffering Crude oil pipelines, municipal wastewater networks, electrical distribution

Industrial PC (IPC) Complex math, edge analytics, multi-axis motion Sub-millisecond to 5 ms 5\text{ ms} 5 ms (RTOS kernel) Object-oriented, dynamic memory, relational or time-series structures Software clustering; dual-NIC bonding; redundant power supplies Semiconductor fabrication, automated optical inspection (AOI), pharmaceutical packaging

• Architectural Trade-Off Analysis
• Determinism, Scan Cycles, and Execution Timing

A critical distinction on the ISA CAP exam is the difference between deterministic execution and best-effort processing . A control loop is deterministic if its execution time is mathematically bounded and guaranteed within a fixed schedule.

Continuous Processes : Thermal inertia and fluid hydraulic dynamics typically exhibit process dead times ( t d t_d t d ​ ) and time constants ( τ \tau τ ) measured in seconds or minutes. For these systems, a controller loop execution period of 100 to 250 ms 100\text{ to }250\text{ ms} 100 to 250 ms provides adequate controllability without overloading controller processors.

High-Speed Discrete Processes : Packaging lines, parts sorting, and mechanical stamping require sensor evaluation and solenoid actuation within 2 to 10 ms 2\text{ to }10\text{ ms} 2 to 10 ms . If a controller exhibits scan-time jitter of ± 15 ms \pm 15\text{ ms} ± 15 ms , parts miss registration, causing mechanical jams.

Operating System Architecture : PLCs and DCS controllers execute proprietary firmware running on deterministic RTOS kernels (such as VxWorks or QNX). Industrial PCs hosting "soft-logic" engines require dedicated real-time extensions (e.g., hypervisor partitioning) that isolate control loops from non-deterministic general-purpose operating system (GPOS) tasks such as Windows background services or file system logging.

Database Tag Management and Engineering Overhead

In a DCS, the controller code, I/O assignment, engineering units, alarm trip points (ISA-18.2), and HMI display attributes reside in a single global object-oriented database . Creating an analog input block automatically instantiates the tag, assigns faceplate graphics, establishes trending, and configures historical data collection. In large plants with thousands of I/O points, this unified model substantially reduces configuration and tag-maintenance effort.

In contrast, traditional PLC/PAC architectures separate the controller tag engine from the supervisory HMI software. Modifying a high-temperature alarm limit in the controller requires manual or scripted synchronization with the HMI tag dictionary. For small systems ( < 1,000 I/O <1{,}000\text{ I/O} < 1 , 000 I/O ), this separation offers flexibility and lower software licensing costs. However, in large continuous processes, maintaining dual databases introduces substantial configuration management risk and human error.

Redundancy Architectures and Failure Modes

System availability directly dictates plant uptime. Technical feasibility assessments must quantify the mean time between failures (MTBF) and mean time to repair (MTTR) for control architectures:

1:1 Hot Standby Redundancy : Dual controllers execute code synchronously. The secondary processor continuously mirrors internal state variables, timers, and I/O image tables across a dedicated high-speed fiber-optic synchronization link. If the primary processor fails (watchdog timeout, hardware fault, power loss), the secondary assumes control bumplessly within 10 to 20 ms 10\text{ to }20\text{ ms} 10 to 20 ms without upsetting field actuators.

Warm Standby : The backup controller is powered on but does not mirror dynamic memory state. Upon primary failure, the backup initializes its executive program, reads current field I/O states, and begins execution after a delay of 500 ms to 5 s 500\text{ ms to }5\text{ s} 500 ms to 5 s . This latency is unacceptable for continuous reactors or critical compressors, but acceptable for slow thermal furnaces or wastewater aerators.

Triple Modular Redundancy (TMR) : Employs three isolated processing channels executing identical logic in parallel with two-out-of-three (2oo3) hardware voting. TMR architectures tolerate a single hardware fault without losing operational continuity and are standard in Safety Instrumented Systems (SIS) and turbomachinery governors.

Plant Physical Infrastructure Constraints

A technically viable automation architecture cannot function without adequate physical and environmental support. During the feasibility study, automation engineers must verify physical space, power supply stability, thermal management, environmental air quality, and cabling infrastructure.

Loading diagram...

Heat Dissipation and Thermal Loading Calculations

Industrial control cabinets house heat-generating hardware: switching power supplies, processor modules, I/O field terminal blocks, network switches, and intrinsic safety isolation barriers. Standard electrical efficiency dictates that virtually all electrical power consumed by control equipment inside an enclosure converts to thermal energy.

To size control room HVAC cooling capacity, calculate the total heat dissipation using the thermal conversion equation:

Q BTU/hr = 3.41214 × P watts Q_{\text{BTU/hr}} = 3.41214 \times P_{\text{watts}} Q BTU/hr ​ = 3.41214 × P watts ​

Where:

• Q BTU/hr Q_{\text{BTU/hr}} Q BTU/hr ​ is the sensible heat dissipation rate in British Thermal Units per hour
• P watts P_{\text{watts}} P watts ​ is the total active electrical power consumed inside the enclosure in watts

Good practice adds a future growth margin (commonly 20% to 25%, set by the project specification) to the calculated equipment power load before final HVAC specification. Failure to manage internal cabinet temperatures shortens semiconductor life; a common Arrhenius-based rule of thumb is that electronic failure rates roughly double for every 10 ∘ C 10^\circ\text{C} 1 0 ∘ C rise in operating temperature.

Clean Instrument Power and Grounding Architectures

Automation systems require high-integrity "clean" power isolated from inductive electrical loads (large electric motors, variable frequency drives, arc welders) that induce electrical noise, harmonics, and voltage sags:

Online Double-Conversion UPS : Feasibility studies must specify true online double-conversion UPS systems. The utility AC supply is continuously converted to DC to charge batteries and supply an inverter that generates a clean, regulated sinusoidal AC output. There is zero transfer time ( 0 ms 0\text{ ms} 0 ms ) during a utility power failure, preventing controller power-supply dropouts.

UPS Sizing Formula : Apparent power rating ( S UPS S_{\text{UPS}} S UPS ​ ) must account for the equipment power factor ( PF \text{PF} PF ) and future growth margin ( M growth M_{\text{growth}} M growth ​ ):

S UPS = P load PF × ( 1 + M growth ) S_{\text{UPS}} = \frac{P_{\text{load}}}{\text{PF}} \times (1 + M_{\text{growth}}) S UPS ​ = PF P load ​ ​ × ( 1 + M growth ​ )

Signal Grounding vs. Safety Grounding : Control systems mandate a Single-Point Ground (SPG) topology—frequently called an Isolated Instrument Ground (IIG). Instrument cable shields must be grounded at one end only (typically at the control cabinet marshalling terminal strip) to prevent ground loops caused by earth potential differences between field transmitters and the control room.

Environmental Airborne Contaminants (ANSI/ISA-71.04)

In chemical, pulp and paper, and refining plants, atmospheric corrosive gases such as hydrogen sulfide ( H 2 S \text{H}_2\text{S} H 2 ​ S ), sulfur dioxide ( SO 2 \text{SO}_2 SO 2 ​ circuit-board corrosion), and chlorine ( Cl 2 \text{Cl}_2 Cl 2 ​ ) react with copper and silver electrical traces. ANSI/ISA-71.04 classifies environmental severity into four standard categories using reactive coupon monitoring:

Class G1 (Mild) : Copper reactivity < 300 A ˚ /30 days <300\text{ \AA/30 days} < 300 A ˚ /30 days ; silver reactivity < 200 A ˚ /30 days <200\text{ \AA/30 days} < 200 A ˚ /30 days . Well-controlled office or high-grade control room. Unprotected commercial electronics survive.

Class G2 (Moderate) : Copper reactivity 300 to 1,000 A ˚ /30 days 300\text{ to }1{,}000\text{ \AA/30 days} 300 to 1 , 000 A ˚ /30 days ; silver reactivity 200 to 1,000 A ˚ /30 days 200\text{ to }1{,}000\text{ \AA/30 days} 200 to 1 , 000 A ˚ /30 days . Light industrial environment; copper creep corrosion begins on exposed circuit traces.

Class G3 (Harsh) : Copper reactivity 1,000 to 2,000 A ˚ /30 days 1{,}000\text{ to }2{,}000\text{ \AA/30 days} 1 , 000 to 2 , 000 A ˚ /30 days ; silver reactivity 1,000 to 2,000 A ˚ /30 days 1{,}000\text{ to }2{,}000\text{ \AA/30 days} 1 , 000 to 2 , 000 A ˚ /30 days . High probability of corrosive failure in standard electronics; protection such as gas-phase filtration of the room air and conformally coated electronics is normally needed.

Class GX (Severe) : Copper reactivity ≥ 2,000 A ˚ /30 days \ge 2{,}000\text{ \AA/30 days} ≥ 2 , 000 A ˚ /30 days ; silver reactivity ≥ 2,000 A ˚ /30 days \ge 2{,}000\text{ \AA/30 days} ≥ 2 , 000 A ˚ /30 days . Electronics will fail rapidly. Control equipment needs a pressurized room or enclosure supplied with chemically filtered air (for example, potassium permanganate and activated carbon media).

Industrial Transmission Media: Copper vs. Fiber Optics

When evaluating field network topology during feasibility, the physical distance between field marshalling cabinets and central control rooms determines the transmission medium:

Category 6A Shielded Twisted Pair (STP) : Maximum transmission distance is strictly limited to 100 m 100\text{ m} 100 m ( 328 ft 328\text{ ft} 328 ft ) for industrial Ethernet (100BASE-TX / 1000BASE-T). Copper cable is susceptible to electromagnetic interference (EMI) and radio frequency interference (RFI) when routed near high-voltage motor feeder cables.

Multi-Mode Fiber (MMF — OM3 / OM4) : Utilizes a larger core ( 50 / 125 μ m 50/125\text{ }\mu\text{m} 50/125 μ m ) driven by 850 nm 850\text{ nm} 850 nm vertical-cavity surface-emitting lasers (VCSELs). Maximum distance for gigabit transmission is 300 to 550 m 300\text{ to }550\text{ m} 300 to 550 m . Ideal for intra-building or localized process unit backbones.

Single-Mode Fiber (SMF — OS2) : Utilizes an ultra-thin core ( 9 / 125 μ m 9/125\text{ }\mu\text{m} 9/125 μ m ) driven by 1310 nm 1310\text{ nm} 1310 nm or 1550 nm 1550\text{ nm} 1550 nm solid-state laser diodes. Transmits optical signals up to 10 to 40 km 10\text{ to }40\text{ km} 10 to 40 km without repeaters. Fiber optics are 100% dielectric, providing total immunity to EMI, RFI, and ground potential differences.

The optical link loss budget equation verifies link feasibility before detailed design:

α total = ( L × α cable ) + ( N splices × α splice ) + ( N connectors × α conn ) + M safety \alpha_{\text{total}} = (L \times \alpha_{\text{cable}}) + (N_{\text{splices}} \times \alpha_{\text{splice}}) + (N_{\text{connectors}} \times \alpha_{\text{conn}}) + M_{\text{safety}} α total ​ = ( L × α cable ​ ) + ( N splices ​ × α splice ​ ) + ( N connectors ​ × α conn ​ ) + M safety ​

Where α \alpha α represents optical attenuation in decibels ( dB \text{dB} dB ), L L L is fiber distance in kilometers, and M safety M_{\text{safety}} M safety ​ is an engineering design margin (typically 3 dB 3\text{ dB} 3 dB ).

Important

An exam favorite tests grounding rules: cable shields must be grounded at one end only . Grounding both ends of an instrument cable shield creates a closed circuit path for ground loop circulating currents driven by slight voltage potentials between field and control room earth grounds, corrupting 4 – 20 mA 4\text{--}20\text{ mA} 4 – 20 mA signals.

Tip

When evaluating DCS vs. PLC in feasibility studies, loop count alone is deceptive. A facility with only 400 I/O 400\text{ I/O} 400 I/O points may warrant a DCS if the majority are complex analog interactions (cascade, ratio, feedforward) requiring a single unified tag database and online code modifications without stopping the controller.