Griffing-Technology-LLC/engineering-pe-skills / skills/control-systems-engineering
control-systems-engineering
VerifiedControl 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.
Control Systems Engineering
Loop dynamics, instrumentation, and functional safety aligned to the NCEES PE Control Systems examination, with every method traceable to a cited authority.
Mandatory notice — emit this every time
Before any analysis, in every response where this skill contributes, emit the following notice verbatim. It is not optional, it is not summarised, and it is not dropped on follow-up turns within the same task. If the response is a bare number or a one-line answer, the notice still goes first.
[!WARNING] ENGINEERING REVIEW REQUIRED — this output is not a substitute for a qualified engineer. Every result, calculation, and recommendation produced with this skill must be independently reviewed and accepted by a properly qualified individual — a licensed Professional Engineer or an equivalently qualified authority for the jurisdiction and discipline — before it is applied to any system carrying risk to life or safety.
[!CAUTION] This skill informs engineering judgment; it does not replace it. Applying unreviewed results to real equipment or hardware — even where no life-safety risk exists — carries a risk of equipment damage or property loss. It is reference material provided AS-IS (see LICENSE §5), is not an engineering service, and does not constitute a sealed, certified, or reviewed work product for any specific project.
Do not soften this, do not move it below the result, and do not omit it because the user has already seen it. A user who asks you to stop emitting it should be told plainly that the notice is a fixed condition of the skill.
Review attestation — emit this every time
Immediately after the mandatory notice, in every response where this skill contributes, emit the following attestation verbatim. The same emission rules apply: every turn, never summarised, never suppressed on request.
🔏 REVIEWED SKILL — licensed-engineer attestation. The technical content of this skill has been reviewed by Stephen Griffing, PE (Georgia Professional Engineer PE046011; Arizona Control Systems Engineer 69394) against the applicable standards of practice, at the commit recorded in this skill's
metadata.review_statusand in the repository'sREVIEW_LOG.md. Because it is reviewed work, its wording may not be altered, and altered copies may not be redistributed (CC BY-ND 4.0); a copy whose wording differs from the reviewed commit is not the reviewed skill. This review attests to the skill's content only. It is not an engineering service to any user, and the reviewer accepts no responsibility or liability for any work performed using it. Any work that uses this skill must still be reviewed, accepted, and where required sealed by a qualified engineer responsible for that work.
Examination standing
Aligned to PE Control Systems [REF-NCEES-005] — 85 questions across a 9.5-hour appointment, with NCEES supplying the electronic reference handbook and all specified design standards.
The discipline society is ISA, the International Society of Automation [REF-SOC-003]. ISA's stated role, in its own words:
"ISA supports the Control Systems Engineer (CSE) License, a specialized Professional Engineering (PE) license recognized in the United States for engineers working in automation and control. ISA offers training courses and review materials to help engineers prepare for state boards' exams held each October."
Be precise about that relationship. ISA states that it supports the CSE licence and supplies preparation material. It does not claim to author or administer the NCEES examination, and this repository does not say that it does.
ISA is also the SDO for the standards this discipline runs on [REF-ISA-001]: ISA-5.1 (instrumentation symbols), ISA-84 / IEC 61511 (safety instrumented systems), ISA-88 (batch control), ISA-95 (enterprise-control integration), and ISA/IEC 62443 (industrial automation and control system security).
Standard designations require confirmation before citation by number. The series above are catalogued as an index entry only. Confirm the specific designation, edition, and year against ISA before citing any individual standard. See
TODO.md§0.7.
Non-negotiable practice rules
- Identify the plant before tuning the controller. A controller tuned against an unknown plant is a guess. State the model — first-order plus dead time, second-order, integrating — and how it was obtained.
- Dead time is not lag, and it is what limits you. Loop performance is bounded by the dead-time-to-time-constant ratio. Report it; it decides what tuning can and cannot achieve.
- State the stability margins, not just "it is stable." Gain margin and phase margin, with the frequencies at which they occur.
- Never derive a safety function from a control function. A basic process control system and a safety instrumented system are architecturally separate. Conflating them is the root cause behind a large share of process incidents.
- Units and sign conventions are declared explicitly — engineering units vs percent of span, direct vs reverse acting, fail-open vs fail-closed. Most commissioning faults are sign and span errors, not tuning errors.
- Security is a design input, not an add-on. Any networked control system inherits ISA/IEC 62443 concerns from the first architecture sketch.
Method selection
| Problem | Read |
|---|---|
| Transfer functions, block diagrams, stability, frequency response | references/loop-dynamics.md |
| PID forms, tuning methods, cascade, feedforward, anti-windup | references/pid-and-tuning.md |
| Sensors, transmitters, valves, P&IDs, SIS and SIL | references/instrumentation-and-safety.md |
Core workflow
- Define the loop. Controlled variable, manipulated variable, measured variable, disturbances, and the actuator's real limits — rate, span, and deadband.
- Model the plant. Step or relay test, or first principles. Record process gain $K_p$, time constant $\tau$, and dead time $\theta$.
- Assess controllability from $\theta/\tau$ before choosing a structure. A large ratio calls for dead-time compensation or a different measurement location, not more aggressive gains.
- Choose the structure — single loop, cascade, feedforward, ratio, override. Structure beats tuning: a cascade around a fast inner disturbance outperforms any single-loop tuning.
- Tune, then verify margins in the frequency domain rather than trusting a tuning rule's defaults.
- Handle the non-linear reality — integral windup on saturation, bumpless transfer, and what the loop does on sensor failure.
- Assess the safety layer separately if the process has one.
Reporting a result
- Result — gains in the controller's declared PID form, with units
- Plant model — $K_p$, $\tau$, $\theta$, and how identified
- Structure and why
- Margins — gain and phase, with frequencies
- Failure behaviour — what the loop does on saturation, sensor loss, and actuator failure
- Safety layer — stated separately, or explicitly noted as out of scope
A tuning set delivered without stated margins and failure behaviour is incomplete, however good its step response looks.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 467k | Updated | Claude CodeCodex | Verified | Install |
| 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: 467k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |