Skip to content

Griffing-Technology-LLC/engineering-pe-skills / skills/control-systems-engineering

control-systems-engineering

Verified

Control systems engineering aligned to the NCEES PE Control Systems exam — PID tuning, loop dynamics, transfer functions, stability and frequency response, process instrumentation and P&IDs, final control elements, safety instrumented systems and SIL, and industrial control security. Use when tuning or diagnosing a control loop, building a transfer function or block diagram, checking stability or phase and gain margin, sizing a control valve or selecting a sensor, reading or drafting a P&ID, doing a SIL or LOPA assessment, or designing a feedback controller for a physical plant.

references/instrumentation-and-safety.md

View on GitHub
# Instrumentation, Final Elements, and Functional Safety

Reference file for the `control-systems-engineering` skill.

## 1. Measurement

The loop cannot outperform its measurement. Consider, and state:

* **Accuracy vs repeatability** — control needs repeatability; accounting needs
  accuracy. They are different specifications and are often confused.
* **Range and turndown** — accuracy quoted as a percentage of *span* becomes poor
  in absolute terms at the low end of a wide range.
* **Response time**, including sensor lag and any thermowell — a thermowell can
  add tens of seconds of lag to a temperature loop, which appears in the model as
  additional dead time and directly limits achievable performance.
* **Installation effects** — straight-run requirements for flow meters, impulse
  line filling for DP, and sensor location relative to the process.

Sensor location is a design decision with more leverage than tuning: moving a
measurement closer to the process action reduces dead time, and reducing dead
time is the only way to raise the performance ceiling.

## 2. Signal standards

4–20 mA remains dominant because **live zero distinguishes a real zero reading
from a broken wire** — a 0–20 mA signal cannot. HART overlays digital data on the
same pair; fieldbus and Ethernet-based protocols carry it fully digitally.

Declare engineering units vs percent of span explicitly at every interface. Span
and zero errors at controller boundaries cause more commissioning faults than
tuning does.

## 3. Final control elements

**Control valves.** Size for the *controllable* range, not the maximum flow.
An oversized valve operates nearly closed, where its gain is highest and most
non-linear, and the loop becomes untunable across the range.

* **Inherent characteristic** — linear, equal-percentage, quick-opening.
  Equal-percentage is common where valve pressure drop varies with flow, since
  the *installed* characteristic then approaches linear.
* **Fail position** — fail-open, fail-closed, or fail-in-place is a **process
  safety decision**, not a convenience. Determine it from what the process needs
  on loss of air or power, and document the reasoning.
* **Stiction and deadband** cause limit cycling that no tuning will remove.

**Variable-speed drives** are often a better final element than a throttling
valve, since pump power scales with the cube of speed.

## 4. P&IDs and documentation

ISA-5.1 [REF-ISA-001] defines instrumentation symbols and tag identification —
the letter conventions for measured variable and function, and the balloon
conventions for mounting and accessibility.

> Confirm the current ISA-5.1 designation and edition before citing it by number.
> See `TODO.md` §0.7.

A P&ID is the authoritative interface between process, control, and safety
disciplines. Loop numbering, tag consistency, and fail positions belong on it.

## 5. Safety instrumented systems

**The single most important architectural rule in this discipline: a safety
instrumented system is separate from the basic process control system.**

The BPCS controls the process. The SIS takes it to a safe state when the BPCS
and operator have failed. Deriving the safety function from the same sensor,
logic solver, or final element as the control function creates a common-cause
failure that defeats the protection layer entirely. ISA-84 / IEC 61511
[REF-ISA-001] governs the lifecycle.

**Safety Integrity Level (SIL)** expresses required risk reduction, determined by
hazard analysis — usually LOPA — not chosen by preference. Higher SIL demands
more capable architecture, better diagnostics, and more frequent proof testing.

Terms that must not be blurred:

* **PFD** — probability of failure on demand, for low-demand functions
* **Proof test interval** — directly drives PFD; a SIL claim without a stated
  test interval is incomplete
* **Safe failure fraction** and **hardware fault tolerance** — architectural
  constraints that a SIL claim must satisfy independently of PFD

**A SIL number quoted without its verification basis is not a SIL claim.** State
the architecture, the failure data source, the proof test interval, and the
calculated PFD.

## 6. Security

ISA/IEC 62443 [REF-ISA-001] governs industrial automation and control system
security. Treat it as a design input from the first architecture sketch, not a
network-layer addition afterwards.

The core concept is **zones and conduits** — group assets by required security
level, and control the communication paths between them. Note that safety and
security interact: a security control that can block a safety function is itself
a hazard, and must be assessed as one.

> Confirm current ISA/IEC 62443 part numbers and editions before citing them
> individually. See `TODO.md` §0.7.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall