Establish the basic historian-to-FOPDT workflow and compare identified Kp, tau, and theta with known ground truth.
Take the lesson with you
Download a free reflection and repetition worksheet for each verified native exercise. These files are learning companions, not graded answer keys or certificates. The original ChatGPT-hosted 84-case simulator is preserved separately; this collection covers only the exercises that can be verified from the native LoopIQ source.
Public practice (60)
Choose a case to print or save a PDF study sheet; editable plain-text worksheets remain available.
The synthetic case is identifiable, but students should learn that an undersized field bump can be buried by real measurement noise and disturbances.
Students see that process gain comes from the relationship between delta PV and delta OP, not from assuming every bump is positive.
The identifier should remain stable, while the student learns to inspect signal-to-noise evidence instead of assuming every trend is equally trustworthy.
Use this case to recognize a balanced theta/tau ratio and compare it with the faster flow examples.
Students can contrast lag-dominated behavior with balanced and delay-dominated cases.
Higher process gain means smaller controller gain is usually appropriate; this case makes that relationship visible.
No excitation means no identification evidence. The safe behavior is refusal.
Introduce slower thermal time constants and show why the same tuning aggressiveness should not be copied across loop types.
A larger excitation improves identifiability in the presence of ordinary measurement resolution, while real plants still require safe operating limits.
Students should compare fit quality and signal-to-noise evidence before trusting a recommendation.
A valid bump test needs a stable pre-step baseline so noise and the initial PV can be estimated.
Use this case to introduce conservative tuning for slow inventory behavior.
Students learn to separate slow dynamics from low process gain; they are different model parameters with different tuning consequences.
A model may be computable without the test being ideal. Students should notice the unsettled flag and extend the window when possible.
Possible causes include the wrong tag, blocked actuator, insufficient test authority, or a failed measurement. LoopIQ should not invent a model.
Introduce dead time explicitly and show how it shifts the PV response after the output moves.
Students can compare the theta/tau ratio with the more delay-dominated analyzer cases.
This case helps students visually distinguish dead time from the process time constant.
A long-dead-time process requires a long enough test. LoopIQ should ask for more data rather than guess.
The identifier must preserve negative process gain so downstream controller action is not accidentally inverted.
Students should recognize that a high process gain typically drives the recommended controller gain downward.
Identification should remain finite, but the student should inspect fit quality and signal-to-noise before trusting gains.
Signal-to-noise below the identification floor should trigger a refusal and a request for a cleaner or larger test.
Separate process sensitivity from response speed and observe how both influence tuning.
Reinforce correct sign handling and prove that a useful bump test does not require an upward step.
Students should recognize that a simple FOPDT fit can be useful while still missing an oscillatory mechanism that deserves separate diagnosis.
The correct action is to improve the test or instrumentation evidence, not tune from an unreliable fit.
Slow thermal processes punish aggressive tuning; compare the baseline against the recommended rule and inspect settling and robustness.
Students see why historian windows and simulation horizons must scale with the actual process dynamics.
A mathematically fitted model can still be weak evidence. Extend the test window when process conditions allow.
Too little post-step response means the key response crossings cannot be resolved reliably.
This case reinforces conservative inventory-loop tuning and long observation windows.
Students compare the combined effect of lag and delay against the simpler introductory level cases.
Drift can bias gain and steady-state estimates even when a model can be fitted. Students should review trend stationarity.
Treat this as a failed test or process/instrument problem, not as permission to fabricate gains.
Dead-time-dominated loops need conservative tuning; the transport delay should be obvious in both trend and recommendation.
Use the theta/tau ratio to understand why one analyzer loop may tolerate more aggressive tuning than another.
Students should check confidence and fit instead of treating a visually plausible curve as sufficient proof.
Long analyzer delays demand longer test windows; a fit without response evidence is unsafe.
Fast loops require adequate historian sample rate. Here the dense sampling makes the short dynamics identifiable.
Students learn the difference between reduced resolution and truly inadequate sampling.
A single FOPDT model can summarize the dominant response while a separate oscillation diagnostic may still be required.
Even an apparently shaped response should be rejected when the quantitative signal-to-noise floor is not met.
This case exercises the lag-dominated edge of the rule-selection logic.
Students should see why delay-dominated loops demand conservative closed-loop targets.
Students should recognize that disturbances can bias steady-state estimates even when the initial step response is sound.
The application should force investigation of tag selection, actuator response, or process connectivity before any tuning work continues.
Students should see why slow does not automatically mean low sensitivity; gain and time constant must be considered separately.
Sign handling must remain correct even on slow delayed loops where a wrong action assumption would be especially costly.
Students should treat nonstationary tests cautiously because apparent process gain can include background heat-balance movement.
Without enough baseline points LoopIQ cannot establish pre-step noise or a reliable initial condition.
Students must choose observation and simulation horizons that are long enough to reveal the actual process behavior.
The case connects process configuration to controller action: outlet valves commonly invert the sign relative to inlet manipulation.
The model may remain usable for study, but the combined evidence quality should trigger explicit engineering review.
Students should learn to size the historian window from expected process dynamics rather than a fixed clock duration.
This case exercises the extreme delay-dominated regime and should lead to especially conservative tuning.
Students must keep controller action and process delay concepts separate; both matter to the final tuning decision.
Students should distinguish "a fit can be computed" from "the test evidence is strong enough to act on."
The correct result is a quantitative refusal, preserving the distinction between visual pattern matching and defensible identification.
Angel graded lab (23)
Choose a case to print or save a PDF study sheet; editable plain-text worksheets remain available.
Identify and tune a well-behaved fast flow loop.
Tune a flow loop whose transport delay makes aggressive settings fragile.
Recognise valve stiction and avoid tuning around it.
Tune without mistaking output saturation for a need for more gain.
Tune an integrating level loop without inducing cycling.
Practice intentionally slow tuning for inventory control.
Tune a representative self-regulating pressure loop.
Reject an untrustworthy identification rather than tune on it.
Recover a pressure loop from overly aggressive initial settings.
Tune a slow thermal process with meaningful lag and dead time.
Detect and refuse to tune a loop configured with the wrong action.
Spot a fragile tuning from margins and detune to a safe Ms.
Tune a thermal process where delay is a large part of the apparent dynamics.
Tune a slow analyzer loop dominated by sample-system delay.
Diagnose a weak analyzer bump test and require better evidence.
Tune one local pH operating region and recognize the limits of fixed tuning.
Practice conservative tuning on a slow composition measurement.
Tune an exchanger outlet temperature loop in a representative operating region.
Tune a representative furnace temperature loop conservatively.
Practice conservative decision-making on a high-consequence reactor temperature scenario.
Tune a representative compressor pressure loop with conservative margins.
Separate tuning quality from pump/output capacity limits.
A comprehensive single-loop capstone; multi-loop expert structures remain a separate staged track.
Advanced control practical (8)
Choose a case to print or save a PDF study sheet; editable plain-text worksheets remain available.
Tune the fast inner flow loop first, then the slower outer temperature loop.
Cancel a measurable load disturbance before feedback has to react to the resulting error.
Make the controlled additive flow track a changing wild-flow stream at a defined ratio.
Use one temperature controller to hand off smoothly between cooling and heating final elements.
Let a constraint controller take control of a shared final element when the primary objective threatens a limit.
Vary tuning continuously across operating regions when process gain changes sharply with operating point.
Use an internal process model to remove known dead time from the controller-facing prediction.
Use RGA to choose the pairing, then verify static decoupling reduces cross-loop disturbance.
L4 design challenge (8)
Choose a case to print or save a PDF study sheet; editable plain-text worksheets remain available.
Choose inner-loop speed and prove adequate time-scale separation before releasing the master loop.
Enter feedforward gain, lead, lag, and delay and prove disturbance rejection against feedback-only control.
Set the blend ratio and prove the follower tracks a changing wild-flow stream.
Choose the handoff point and final-element polarity and prove stable heat/cool control.
Choose selector direction and tracking behavior so the constraint takes over safely.
Choose low, neutral, and high-region process gains and prove continuous scheduling across the nonlinear region.
Enter the internal FOPDT model and prove dead-time compensation remains robust under seeded mismatch.
Choose the loop pairing and enter static decoupler terms; prove cross-loop disturbance is reduced.
Competency review (12)
Choose a case to print or save a PDF study sheet; editable plain-text worksheets remain available.
The language of loops: signals, action, gain, and proportional band.
Gain, dead time, and lag — and why dead time limits performance.
Bump testing, FOPDT fitting, and judging identification quality.
What each measurement type actually senses, its typical dynamics, and where its own limitations show up in a loop.
What each term does, controller forms/units, derivative & anti-windup.
Choosing a method and computing gains with SIMC/IMC/lambda.
The performance/robustness trade-off and spotting fragile tunings.
Stiction, deadband, and why you must not tune around a sick valve.
Recognising coupling between loops and detuning for interaction.
Pre-tuning safety hard-stops and the maker–checker MOC workflow.
Performance monitoring KPIs and deciding when to re-tune.
An unaided critical-loop workflow proving independent expert competence.
These worksheets do not grant controller access. Use the in-app assessment engine for actual proficiency and credential decisions. Live process changes always require site authorization.