Protection Layers and Functional Safety

Learning objective. Separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations.

Linked synthetic case. A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter.

What an adequate output contains. Never credit a layer twice, and never infer a real SIL target, safety integrity verification or tolerability decision from a slider.

Why this unit is needed

Process safety concerns preventing and limiting catastrophic releases of hazardous substances or energy, rather than merely maintaining a low count of routine injuries. A real project cannot infer its safety from a single score, accident-free period or calculation. For this unit, separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations. The basis of this reasoning is the physical configuration of equipment and operations, not the appearance of a matrix or dashboard. Assign each critical assertion an owner and identify how field observations could contradict it.

The case used across the lessons is deliberately hypothetical: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. It contains no named real chemicals, equipment certificates, actual incident frequencies or approved operating limits. That distinction is central to interpreting models. For a plant, process safety information must describe what can be hazardous, how the process can deviate, and which barriers genuinely remain functional in abnormal conditions. A model may reveal sensitivity while omitting the mechanism that actually dominates a serious accident.

The five-layer engineering argument

1. Hazard and inventory: Identify substances, energy and populations or environmental receptors that could be exposed. Document what remains unknown before assigning a numerical risk category.

2. Initiating mechanism: State a credible cause, including external utilities, human-machine interfaces, maintenance, abnormal startup and non-routine conditions; separate initiating cause from the loss-of-control top event.

3. Prevention: Identify physical design limits, independently verified interlocks, procedures and maintenance controls. Do not assume independence without checking power, instruments and common personnel.

4. Mitigation: Assess containment, shutdown, relief and emergency arrangements in the context of the actual consequence mechanism. A mitigation may reduce severity without reducing the initiating frequency.

5. Assurance: Specify evidence, proof tests, field observations and responsible action owners. Controls that are unavailable, bypassed or degraded must not be credited as if fully available.

How to use the three numerical laboratories

These interactive models intentionally isolate individual relationships rather than claiming to predict a hazardous plant. Before moving a slider, write the governing equation and the physical units. Decide which outcomes should rise or fall when one parameter changes. After moving it, check whether the response and the plotted curve agree with that expectation. Export numerical data and calculate one point independently. If a curve seems favorable, identify a missing mechanism that could reverse the real decision.

This unit's laboratories are:

• [Lab 13: Illustrative barrier-chain success](../labs/lab-13.html) — Calculate total success of two independently functioning barriers on demand. Boundary: Does not model common-cause, bypass, diagnostics or quality of barrier claims.
• [Lab 14: Conditional LOPA arithmetic](../labs/lab-14.html) — Demonstrate arithmetic of a claimed set of independent protective layers. Boundary: Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance.
• [Lab 15: Low-demand proof-test approximation](../labs/lab-15.html) — Explore the linearized average probability of dangerous undetected failure. Boundary: Small λT approximation; omits coverage, repairs, architecture and systemic failures; not IEC 61511 verification.

How to review evidence

For each lesson prepare a three-column evidence ledger: declared fact, supporting observation/source, and status (measured, specified, assumed, inferred, or unresolved). Do not promote an assumption to a measurement when an equation happens to give a precise answer. In a team review, challenge the source of every probability and time constant. If an engineering standard is cited, verify the correct edition and legal applicability; standards differ by jurisdiction and project date. For serious events, methods used by qualified specialists should replace these elementary illustrations.

The course encourages deliberate disagreement: two reviewers should independently identify the hazardous deviation and potentially defeated safeguards before reconciling their lists. Record both the agreement and remaining uncertainty. The presence of a highly consequential unresolved scenario should not be hidden inside a low composite average. Closure means that a response has been implemented and verified to work, not that a spreadsheet cell has been colored green.

Progression and assessment

Complete the four lessons in order. Each assessment demands a short derivation, a sensitivity or limitation check, a scenario analysis and a documented decision. A numerical result without a stated boundary, units and credible evidence should receive no engineering credit. The final unit project asks for an auditable decision memo that separates a screening observation from an approval to build or operate. Peer review should specifically challenge common-cause failures and untested assumptions.

Lesson 1: Bow ties and barrier assurance

A bow tie links threats to a central loss-of-control event and then to consequences. Preventive barriers lie before the top event; mitigating barriers act after it. A barrier needs a performance standard, responsible owner and verification method. Key analytical anchor: Threat → preventive barrier → top event → mitigation → outcome. Investigate the following case: For tank overflow, compare independent high-high shutdown with secondary containment; each interrupts a different point in the chain. The most likely conceptual error is counting a warning label, operator procedure and shared alarm as independent hardware barriers. In the lesson, assemble barrier definitions, independence review, inspection records and response competence before drawing the operational conclusion: translate a bow tie into a testable barrier register. Further discussion: For three controls, define functionality, reliability, availability and assurance evidence.

Lesson 2: Independent protection layer screening

LOPA is a structured semi-quantitative method, not a general risk-reduction spreadsheet. Independence, specificity, effectiveness and auditable testing are preconditions for any credited layer. Key analytical anchor: f_mitigated ≈ f_initiating × Π(PFD_i) under justified assumptions. Investigate the following case: A synthetic f_i=0.02/y with independent PFDs 0.1 and 0.05 produces 0.0001/y in a teaching-only arithmetic example. The most likely conceptual error is giving duplicate credit to alarms and trips that share sensors or power. In the lesson, assemble independent design review, credible initiating frequencies, demand rates, proof-test data and site risk criteria before drawing the operational conclusion: treat the calculated number as conditional on assumptions, never certification. Further discussion: Trace whether two barriers share detection, logic solver, final element or maintenance procedure.

Lesson 3: Failure on demand and common-cause failure

A protection layer can be unavailable on a demand even when it has operated reliably during normal production. Common-cause failures, bypasses, diagnostic limits and systematic errors complicate combinations of safeguards. Key analytical anchor: P(2 failures) = p1 p2 only for independent events. Investigate the following case: Two nominal 0.1 PFD devices have independent combined PFD 0.01; a shared defeat mechanism changes this conclusion. The most likely conceptual error is assuming identical hardware components automatically provide independent risk reduction. In the lesson, assemble cause-and-effect matrices, power distribution, proof-test documentation and bypass logs before drawing the operational conclusion: require common-cause and systematic-failure review before taking credit. Further discussion: Map which two supposed safeguards fail together during lost instrument air.

Lesson 4: Safety instrumented functions and proof testing

Safety instrumented systems are engineered lifecycle controls with defined hazards, demand modes, sensors, logic and final elements. A first-order low-demand approximation is useful pedagogically but is not an IEC 61511 verification. Key analytical anchor: PFD_avg ≈ λ_DU T/2 for small λ_DU T. Investigate the following case: With λ_DU=2×10⁻⁶ /h and T=4000 h, the simplified contribution is PFD_avg≈0.004. The most likely conceptual error is selecting a sil from this single-parameter approximation or ignoring common cause and repair. In the lesson, assemble sif requirements, diagnostic coverage, testing effectiveness, architectures and applicable standards before drawing the operational conclusion: separate arithmetic demonstration from qualified lifecycle design and verification. Further discussion: Explain how proof-test coverage, bypass duration and systematic errors can invalidate the approximation.

Unit completion checkpoint

The minimum acceptable submission contains an annotated process boundary for protection layers and functional safety, a cause-to-consequence pathway, a register of assumptions, an independent numerical reproduction of each model, and an unresolved-information list. In the synthetic case, a high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Identify which missing single item is most likely to change your recommendation and why. Then state who would have authority to accept or reject the real project after a specialist review.

Unit 5 · Lesson 1: Bow ties and barrier assurance

[Unit overview](../units/unit-05.html) · [Interactive lab 13](../labs/lab-13.html) · [Assessment](../assessments/unit-05.html) · [Applied project](../projects/unit-05.html)

The engineering question

A bow tie links threats to a central loss-of-control event and then to consequences. Preventive barriers lie before the top event; mitigating barriers act after it. A barrier needs a performance standard, responsible owner and verification method. This lesson belongs to Protection Layers and Functional Safety, where the course objective is to separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations. The governing issue is not whether one can calculate a number; it is whether that number describes the failure mechanism under study. A competent analysis separates a claim about what happens, an argument about why it would happen, and evidence that the safeguards could withstand real operation.

Specific thought experiment. For tank overflow, compare independent high-high shutdown with secondary containment; each interrupts a different point in the chain. Work from the equipment boundary outward. Name the initiating event, the operating mode, the top event, the potentially exposed people or environment, and the time over which the consequences could develop. If any one of these is unspecified, maintain the uncertainty rather than inventing a value.

Principles and analytical relationship

The working relation or structured method is Threat → preventive barrier → top event → mitigation → outcome. It is useful because it forces an analyst to state inputs and ask whether the units, time basis and conditioning assumptions match. A rate per year cannot be multiplied by an arbitrary probability without asking what event that probability conditions upon. Similarly, an ordinary fraction is not a mass fraction until the relevant mass balance has been declared. In a causal diagram, an arrow represents a proposed physical or organizational dependency; it is not, by itself, proof of causality.

The physical interpretation for bow ties and barrier assurance is the following: A bow tie links threats to a central loss-of-control event and then to consequences. Preventive barriers lie before the top event; mitigating barriers act after it. A barrier needs a performance standard, responsible owner and verification method. Thus the result needs an audit trail back to observations, design documents or a controlled estimate. There is no universal conversion from a neat calculation to safe operation. Where the relationship is qualitative, a complete answer explains the conditions for each step and which alternative cause could produce the same observed symptom. When the relation is quantitative, a complete answer supplies units, ranges and a check against a limiting case.

For the course case, a high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Consider three boundaries before deciding whether the model is applicable: the system under study, the observation period, and the intervention boundary. System boundaries determine which inventories and energy flows are included. Observation periods distinguish transient loss of control from a steady process average. Intervention boundaries identify where automatic protection, human response or passive containment can plausibly act. A safeguard that acts after the harm does not prevent the initiating event, although it may limit the consequence.

Worked reasoning example

Unverified numerical or qualitative illustration: For tank overflow, compare independent high-high shutdown with secondary containment; each interrupts a different point in the chain. Begin with the stated conditions only. Write the relationships that must hold, then identify at least one variable not specified in the example. If an exact arithmetic result is given, reproduce it independently and add a clear qualifier about the simplified model. If the example is qualitative, draw a two-branch argument: one where the existing barrier is available and one where it is defeated by a plausible condition. Do not fill missing branches with assumed success simply to obtain a final score.

A useful way to test the claim is to ask what change would produce the opposite conclusion. For this topic, the specific analytical trap is counting a warning label, operator procedure and shared alarm as independent hardware barriers. Try to construct a counterexample with the same nominal process equipment but an altered startup, maintenance, utility, human or instrument condition. A single plausible counterexample indicates that the original claim was conditional. It does not automatically establish that the process is unsafe; it establishes which fact must be investigated before any stronger judgment.

Evidence and traceability

The minimum relevant evidence set is barrier definitions, independence review, inspection records and response competence. For each item record source, revision, date, scope, owner and confidence. Separate field-measured values from vendor guarantees, industry generic estimates and deliberately fictional learning inputs. For example, two pumps sold at the same nominal capacity do not necessarily share seal arrangements, failure modes or instrument interfaces. Even an authoritative standard does not substitute for actual testing or determine whether a particular facility falls within its legal scope.

An effective review checks whether evidence is current for the operating mode. Startup differs from steady production; temporary operation after a maintenance outage may differ from both. Procedures, alarms and emergency equipment must be evaluated for those modes explicitly. A reliability assertion based on one short interval must not silently be extended to years of service. Missing evidence should generate a specific work request instead of a generic recommendation to “improve safety.”

Laboratory investigation and sensitivity

Use [Lab 13: Illustrative barrier-chain success](../labs/lab-13.html). The printed equation is P(success of ≥1) = 1−p_fail,1 p_fail,2. Calculate total success of two independently functioning barriers on demand. Start from each slider's default, record the displayed metric and vary the first parameter over five or more settings. The graph and CSV should agree with your hand calculations. Next, change one other parameter while keeping the first fixed; this distinguishes a mathematical sensitivity from a trend caused by simultaneous input changes.

Investigation target: How would shared instrument power alter independence? The major simplification is Does not model common-cause, bypass, diagnostics or quality of barrier claims.. A good lab report predicts the sign of the derivative or change before observing the plot, then explains what physical process that derivative represents. If an output is nonphysical or a limiting denominator becomes zero, it should be reported as an invalid domain rather than manipulated into a finite reassuring result. Place the lesson's analytical relationship alongside the lab relation; explain whether they describe the same physical quantity or different levels of abstraction.

As a challenge, compare this model with [Lab 14: Conditional LOPA arithmetic](../labs/lab-14.html). The second model's relation is f_residual = f_i PFD₁ PFD₂, and its stated limitation is Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance.. The comparison is not an invitation to combine numbers blindly. Explain what would need to be measured so the two simplified relationships could appear in one defensible engineering argument.

Failure-first decision review

The unacceptable shortcut is counting a warning label, operator procedure and shared alarm as independent hardware barriers. Make a table with columns assumption, possible failure, observation that would expose it, cheapest credible check, owner, and decision consequence. For this particular topic the review should prioritize the evidence sources above rather than produce a broad list of every conceivable failure. Then ask what is the most important remaining uncertainty if all routine checks pass. Low-frequency high-consequence scenarios often cannot be validated simply by waiting for an incident.

The recommended analytical action is: Translate a bow tie into a testable barrier register. This recommendation is a learning exercise, not a control-system change or site-specific directive. Describe its boundaries. What would have to be established by independent qualified review? How would an operator learn that the intended protective measure had become unavailable? Which record would demonstrate closure after a modification? A paper action with no verification is not the same as an effective protective function.

Interpreting uncertainty and competing explanations

Uncertainty enters from input data, model structure, operating variability and human or organizational factors. Input uncertainty might be reduced by a calibrated measurement, whereas model-structure uncertainty demands a different physical model or field trial. Increasing the number of decimal places addresses neither. Separate uncertainty that could reverse the conclusion from uncertainty that changes only the reported numerical precision. The severity of a credible major-accident scenario should influence how urgently an evidence gap is reviewed, even when its probability is difficult to quantify.

For bow ties and barrier assurance, an apparently successful barrier test may demonstrate only the modes exercised by the test. It might not probe lost utilities, common-cause failure, maintenance bypass or the specific initiating condition. A useful counterfactual question is: If the expected result were wrong tomorrow, which observation would reveal it first? Identify an observable precursor and a clear escalation action. This turns an educational calculation into a disciplined evidence requirement without representing it as a plant certification.

Independent exercises

1. Boundary and mechanism: For three controls, define functionality, reliability, availability and assurance evidence. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 13. Show units, the governing relationship and a simple limiting-case or conservation check.

3. Scenario variation: Replace one favorable assumption with an unfavorable but plausible operating condition. Explain which safeguarding claim is weakened and why.

4. Decision note: Summarize in 200–300 words whether translate a bow tie into a testable barrier register. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why counting a warning label, operator procedure and shared alarm as independent hardware barriers would be misleading when a high-consequence scenario is involved.

Lesson outcome checklist

• A credible scenario chain is drawn, without conflating initiating cause, top event and outcome.
• Model assumptions and units are explicit and the numerical output is checked independently.
• Any barrier credit is tied to function, independence, availability, evidence and an owner.
• The decision specifies what remains unverified; it does not present an educational model as a safe operating limit.

Unit 5 · Lesson 2: Independent protection layer screening

[Unit overview](../units/unit-05.html) · [Interactive lab 14](../labs/lab-14.html) · [Assessment](../assessments/unit-05.html) · [Applied project](../projects/unit-05.html)

The engineering question

LOPA is a structured semi-quantitative method, not a general risk-reduction spreadsheet. Independence, specificity, effectiveness and auditable testing are preconditions for any credited layer. This lesson belongs to Protection Layers and Functional Safety, where the course objective is to separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations. The governing issue is not whether one can calculate a number; it is whether that number describes the failure mechanism under study. A competent analysis separates a claim about what happens, an argument about why it would happen, and evidence that the safeguards could withstand real operation.

Specific thought experiment. A synthetic f_i=0.02/y with independent PFDs 0.1 and 0.05 produces 0.0001/y in a teaching-only arithmetic example. Work from the equipment boundary outward. Name the initiating event, the operating mode, the top event, the potentially exposed people or environment, and the time over which the consequences could develop. If any one of these is unspecified, maintain the uncertainty rather than inventing a value.

Principles and analytical relationship

The working relation or structured method is f_mitigated ≈ f_initiating × Π(PFD_i) under justified assumptions. It is useful because it forces an analyst to state inputs and ask whether the units, time basis and conditioning assumptions match. A rate per year cannot be multiplied by an arbitrary probability without asking what event that probability conditions upon. Similarly, an ordinary fraction is not a mass fraction until the relevant mass balance has been declared. In a causal diagram, an arrow represents a proposed physical or organizational dependency; it is not, by itself, proof of causality.

The physical interpretation for independent protection layer screening is the following: LOPA is a structured semi-quantitative method, not a general risk-reduction spreadsheet. Independence, specificity, effectiveness and auditable testing are preconditions for any credited layer. Thus the result needs an audit trail back to observations, design documents or a controlled estimate. There is no universal conversion from a neat calculation to safe operation. Where the relationship is qualitative, a complete answer explains the conditions for each step and which alternative cause could produce the same observed symptom. When the relation is quantitative, a complete answer supplies units, ranges and a check against a limiting case.

For the course case, a high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Consider three boundaries before deciding whether the model is applicable: the system under study, the observation period, and the intervention boundary. System boundaries determine which inventories and energy flows are included. Observation periods distinguish transient loss of control from a steady process average. Intervention boundaries identify where automatic protection, human response or passive containment can plausibly act. A safeguard that acts after the harm does not prevent the initiating event, although it may limit the consequence.

Worked reasoning example

Unverified numerical or qualitative illustration: A synthetic f_i=0.02/y with independent PFDs 0.1 and 0.05 produces 0.0001/y in a teaching-only arithmetic example. Begin with the stated conditions only. Write the relationships that must hold, then identify at least one variable not specified in the example. If an exact arithmetic result is given, reproduce it independently and add a clear qualifier about the simplified model. If the example is qualitative, draw a two-branch argument: one where the existing barrier is available and one where it is defeated by a plausible condition. Do not fill missing branches with assumed success simply to obtain a final score.

A useful way to test the claim is to ask what change would produce the opposite conclusion. For this topic, the specific analytical trap is giving duplicate credit to alarms and trips that share sensors or power. Try to construct a counterexample with the same nominal process equipment but an altered startup, maintenance, utility, human or instrument condition. A single plausible counterexample indicates that the original claim was conditional. It does not automatically establish that the process is unsafe; it establishes which fact must be investigated before any stronger judgment.

Evidence and traceability

The minimum relevant evidence set is independent design review, credible initiating frequencies, demand rates, proof-test data and site risk criteria. For each item record source, revision, date, scope, owner and confidence. Separate field-measured values from vendor guarantees, industry generic estimates and deliberately fictional learning inputs. For example, two pumps sold at the same nominal capacity do not necessarily share seal arrangements, failure modes or instrument interfaces. Even an authoritative standard does not substitute for actual testing or determine whether a particular facility falls within its legal scope.

An effective review checks whether evidence is current for the operating mode. Startup differs from steady production; temporary operation after a maintenance outage may differ from both. Procedures, alarms and emergency equipment must be evaluated for those modes explicitly. A reliability assertion based on one short interval must not silently be extended to years of service. Missing evidence should generate a specific work request instead of a generic recommendation to “improve safety.”

Laboratory investigation and sensitivity

Use [Lab 14: Conditional LOPA arithmetic](../labs/lab-14.html). The printed equation is f_residual = f_i PFD₁ PFD₂. Demonstrate arithmetic of a claimed set of independent protective layers. Start from each slider's default, record the displayed metric and vary the first parameter over five or more settings. The graph and CSV should agree with your hand calculations. Next, change one other parameter while keeping the first fixed; this distinguishes a mathematical sensitivity from a trend caused by simultaneous input changes.

Investigation target: Identify a shared-cause case where this figure grossly understates risk. The major simplification is Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance.. A good lab report predicts the sign of the derivative or change before observing the plot, then explains what physical process that derivative represents. If an output is nonphysical or a limiting denominator becomes zero, it should be reported as an invalid domain rather than manipulated into a finite reassuring result. Place the lesson's analytical relationship alongside the lab relation; explain whether they describe the same physical quantity or different levels of abstraction.

As a challenge, compare this model with [Lab 15: Low-demand proof-test approximation](../labs/lab-15.html). The second model's relation is PFD_avg ≈ λ_DU T / 2, and its stated limitation is Small λT approximation; omits coverage, repairs, architecture and systemic failures; not IEC 61511 verification.. The comparison is not an invitation to combine numbers blindly. Explain what would need to be measured so the two simplified relationships could appear in one defensible engineering argument.

Failure-first decision review

The unacceptable shortcut is giving duplicate credit to alarms and trips that share sensors or power. Make a table with columns assumption, possible failure, observation that would expose it, cheapest credible check, owner, and decision consequence. For this particular topic the review should prioritize the evidence sources above rather than produce a broad list of every conceivable failure. Then ask what is the most important remaining uncertainty if all routine checks pass. Low-frequency high-consequence scenarios often cannot be validated simply by waiting for an incident.

The recommended analytical action is: Treat the calculated number as conditional on assumptions, never certification. This recommendation is a learning exercise, not a control-system change or site-specific directive. Describe its boundaries. What would have to be established by independent qualified review? How would an operator learn that the intended protective measure had become unavailable? Which record would demonstrate closure after a modification? A paper action with no verification is not the same as an effective protective function.

Interpreting uncertainty and competing explanations

Uncertainty enters from input data, model structure, operating variability and human or organizational factors. Input uncertainty might be reduced by a calibrated measurement, whereas model-structure uncertainty demands a different physical model or field trial. Increasing the number of decimal places addresses neither. Separate uncertainty that could reverse the conclusion from uncertainty that changes only the reported numerical precision. The severity of a credible major-accident scenario should influence how urgently an evidence gap is reviewed, even when its probability is difficult to quantify.

For independent protection layer screening, an apparently successful barrier test may demonstrate only the modes exercised by the test. It might not probe lost utilities, common-cause failure, maintenance bypass or the specific initiating condition. A useful counterfactual question is: If the expected result were wrong tomorrow, which observation would reveal it first? Identify an observable precursor and a clear escalation action. This turns an educational calculation into a disciplined evidence requirement without representing it as a plant certification.

Independent exercises

1. Boundary and mechanism: Trace whether two barriers share detection, logic solver, final element or maintenance procedure. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 14. Show units, the governing relationship and a simple limiting-case or conservation check.

3. Scenario variation: Replace one favorable assumption with an unfavorable but plausible operating condition. Explain which safeguarding claim is weakened and why.

4. Decision note: Summarize in 200–300 words whether treat the calculated number as conditional on assumptions, never certification. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why giving duplicate credit to alarms and trips that share sensors or power would be misleading when a high-consequence scenario is involved.

Lesson outcome checklist

• A credible scenario chain is drawn, without conflating initiating cause, top event and outcome.
• Model assumptions and units are explicit and the numerical output is checked independently.
• Any barrier credit is tied to function, independence, availability, evidence and an owner.
• The decision specifies what remains unverified; it does not present an educational model as a safe operating limit.

Unit 5 · Lesson 3: Failure on demand and common-cause failure

[Unit overview](../units/unit-05.html) · [Interactive lab 15](../labs/lab-15.html) · [Assessment](../assessments/unit-05.html) · [Applied project](../projects/unit-05.html)

The engineering question

A protection layer can be unavailable on a demand even when it has operated reliably during normal production. Common-cause failures, bypasses, diagnostic limits and systematic errors complicate combinations of safeguards. This lesson belongs to Protection Layers and Functional Safety, where the course objective is to separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations. The governing issue is not whether one can calculate a number; it is whether that number describes the failure mechanism under study. A competent analysis separates a claim about what happens, an argument about why it would happen, and evidence that the safeguards could withstand real operation.

Specific thought experiment. Two nominal 0.1 PFD devices have independent combined PFD 0.01; a shared defeat mechanism changes this conclusion. Work from the equipment boundary outward. Name the initiating event, the operating mode, the top event, the potentially exposed people or environment, and the time over which the consequences could develop. If any one of these is unspecified, maintain the uncertainty rather than inventing a value.

Principles and analytical relationship

The working relation or structured method is P(2 failures) = p1 p2 only for independent events. It is useful because it forces an analyst to state inputs and ask whether the units, time basis and conditioning assumptions match. A rate per year cannot be multiplied by an arbitrary probability without asking what event that probability conditions upon. Similarly, an ordinary fraction is not a mass fraction until the relevant mass balance has been declared. In a causal diagram, an arrow represents a proposed physical or organizational dependency; it is not, by itself, proof of causality.

The physical interpretation for failure on demand and common-cause failure is the following: A protection layer can be unavailable on a demand even when it has operated reliably during normal production. Common-cause failures, bypasses, diagnostic limits and systematic errors complicate combinations of safeguards. Thus the result needs an audit trail back to observations, design documents or a controlled estimate. There is no universal conversion from a neat calculation to safe operation. Where the relationship is qualitative, a complete answer explains the conditions for each step and which alternative cause could produce the same observed symptom. When the relation is quantitative, a complete answer supplies units, ranges and a check against a limiting case.

For the course case, a high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Consider three boundaries before deciding whether the model is applicable: the system under study, the observation period, and the intervention boundary. System boundaries determine which inventories and energy flows are included. Observation periods distinguish transient loss of control from a steady process average. Intervention boundaries identify where automatic protection, human response or passive containment can plausibly act. A safeguard that acts after the harm does not prevent the initiating event, although it may limit the consequence.

Worked reasoning example

Unverified numerical or qualitative illustration: Two nominal 0.1 PFD devices have independent combined PFD 0.01; a shared defeat mechanism changes this conclusion. Begin with the stated conditions only. Write the relationships that must hold, then identify at least one variable not specified in the example. If an exact arithmetic result is given, reproduce it independently and add a clear qualifier about the simplified model. If the example is qualitative, draw a two-branch argument: one where the existing barrier is available and one where it is defeated by a plausible condition. Do not fill missing branches with assumed success simply to obtain a final score.

A useful way to test the claim is to ask what change would produce the opposite conclusion. For this topic, the specific analytical trap is assuming identical hardware components automatically provide independent risk reduction. Try to construct a counterexample with the same nominal process equipment but an altered startup, maintenance, utility, human or instrument condition. A single plausible counterexample indicates that the original claim was conditional. It does not automatically establish that the process is unsafe; it establishes which fact must be investigated before any stronger judgment.

Evidence and traceability

The minimum relevant evidence set is cause-and-effect matrices, power distribution, proof-test documentation and bypass logs. For each item record source, revision, date, scope, owner and confidence. Separate field-measured values from vendor guarantees, industry generic estimates and deliberately fictional learning inputs. For example, two pumps sold at the same nominal capacity do not necessarily share seal arrangements, failure modes or instrument interfaces. Even an authoritative standard does not substitute for actual testing or determine whether a particular facility falls within its legal scope.

An effective review checks whether evidence is current for the operating mode. Startup differs from steady production; temporary operation after a maintenance outage may differ from both. Procedures, alarms and emergency equipment must be evaluated for those modes explicitly. A reliability assertion based on one short interval must not silently be extended to years of service. Missing evidence should generate a specific work request instead of a generic recommendation to “improve safety.”

Laboratory investigation and sensitivity

Use [Lab 15: Low-demand proof-test approximation](../labs/lab-15.html). The printed equation is PFD_avg ≈ λ_DU T / 2. Explore the linearized average probability of dangerous undetected failure. Start from each slider's default, record the displayed metric and vary the first parameter over five or more settings. The graph and CSV should agree with your hand calculations. Next, change one other parameter while keeping the first fixed; this distinguishes a mathematical sensitivity from a trend caused by simultaneous input changes.

Investigation target: Halve interval; explain why actual PFD may not halve when common-cause errors dominate. The major simplification is Small λT approximation; omits coverage, repairs, architecture and systemic failures; not IEC 61511 verification.. A good lab report predicts the sign of the derivative or change before observing the plot, then explains what physical process that derivative represents. If an output is nonphysical or a limiting denominator becomes zero, it should be reported as an invalid domain rather than manipulated into a finite reassuring result. Place the lesson's analytical relationship alongside the lab relation; explain whether they describe the same physical quantity or different levels of abstraction.

As a challenge, compare this model with [Lab 13: Illustrative barrier-chain success](../labs/lab-13.html). The second model's relation is P(success of ≥1) = 1−p_fail,1 p_fail,2, and its stated limitation is Does not model common-cause, bypass, diagnostics or quality of barrier claims.. The comparison is not an invitation to combine numbers blindly. Explain what would need to be measured so the two simplified relationships could appear in one defensible engineering argument.

Failure-first decision review

The unacceptable shortcut is assuming identical hardware components automatically provide independent risk reduction. Make a table with columns assumption, possible failure, observation that would expose it, cheapest credible check, owner, and decision consequence. For this particular topic the review should prioritize the evidence sources above rather than produce a broad list of every conceivable failure. Then ask what is the most important remaining uncertainty if all routine checks pass. Low-frequency high-consequence scenarios often cannot be validated simply by waiting for an incident.

The recommended analytical action is: Require common-cause and systematic-failure review before taking credit. This recommendation is a learning exercise, not a control-system change or site-specific directive. Describe its boundaries. What would have to be established by independent qualified review? How would an operator learn that the intended protective measure had become unavailable? Which record would demonstrate closure after a modification? A paper action with no verification is not the same as an effective protective function.

Interpreting uncertainty and competing explanations

Uncertainty enters from input data, model structure, operating variability and human or organizational factors. Input uncertainty might be reduced by a calibrated measurement, whereas model-structure uncertainty demands a different physical model or field trial. Increasing the number of decimal places addresses neither. Separate uncertainty that could reverse the conclusion from uncertainty that changes only the reported numerical precision. The severity of a credible major-accident scenario should influence how urgently an evidence gap is reviewed, even when its probability is difficult to quantify.

For failure on demand and common-cause failure, an apparently successful barrier test may demonstrate only the modes exercised by the test. It might not probe lost utilities, common-cause failure, maintenance bypass or the specific initiating condition. A useful counterfactual question is: If the expected result were wrong tomorrow, which observation would reveal it first? Identify an observable precursor and a clear escalation action. This turns an educational calculation into a disciplined evidence requirement without representing it as a plant certification.

Independent exercises

1. Boundary and mechanism: Map which two supposed safeguards fail together during lost instrument air. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 15. Show units, the governing relationship and a simple limiting-case or conservation check.

3. Scenario variation: Replace one favorable assumption with an unfavorable but plausible operating condition. Explain which safeguarding claim is weakened and why.

4. Decision note: Summarize in 200–300 words whether require common-cause and systematic-failure review before taking credit. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why assuming identical hardware components automatically provide independent risk reduction would be misleading when a high-consequence scenario is involved.

Lesson outcome checklist

• A credible scenario chain is drawn, without conflating initiating cause, top event and outcome.
• Model assumptions and units are explicit and the numerical output is checked independently.
• Any barrier credit is tied to function, independence, availability, evidence and an owner.
• The decision specifies what remains unverified; it does not present an educational model as a safe operating limit.

Unit 5 · Lesson 4: Safety instrumented functions and proof testing

[Unit overview](../units/unit-05.html) · [Interactive lab 13](../labs/lab-13.html) · [Assessment](../assessments/unit-05.html) · [Applied project](../projects/unit-05.html)

The engineering question

Safety instrumented systems are engineered lifecycle controls with defined hazards, demand modes, sensors, logic and final elements. A first-order low-demand approximation is useful pedagogically but is not an IEC 61511 verification. This lesson belongs to Protection Layers and Functional Safety, where the course objective is to separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations. The governing issue is not whether one can calculate a number; it is whether that number describes the failure mechanism under study. A competent analysis separates a claim about what happens, an argument about why it would happen, and evidence that the safeguards could withstand real operation.

Specific thought experiment. With λ_DU=2×10⁻⁶ /h and T=4000 h, the simplified contribution is PFD_avg≈0.004. Work from the equipment boundary outward. Name the initiating event, the operating mode, the top event, the potentially exposed people or environment, and the time over which the consequences could develop. If any one of these is unspecified, maintain the uncertainty rather than inventing a value.

Principles and analytical relationship

The working relation or structured method is PFD_avg ≈ λ_DU T/2 for small λ_DU T. It is useful because it forces an analyst to state inputs and ask whether the units, time basis and conditioning assumptions match. A rate per year cannot be multiplied by an arbitrary probability without asking what event that probability conditions upon. Similarly, an ordinary fraction is not a mass fraction until the relevant mass balance has been declared. In a causal diagram, an arrow represents a proposed physical or organizational dependency; it is not, by itself, proof of causality.

The physical interpretation for safety instrumented functions and proof testing is the following: Safety instrumented systems are engineered lifecycle controls with defined hazards, demand modes, sensors, logic and final elements. A first-order low-demand approximation is useful pedagogically but is not an IEC 61511 verification. Thus the result needs an audit trail back to observations, design documents or a controlled estimate. There is no universal conversion from a neat calculation to safe operation. Where the relationship is qualitative, a complete answer explains the conditions for each step and which alternative cause could produce the same observed symptom. When the relation is quantitative, a complete answer supplies units, ranges and a check against a limiting case.

For the course case, a high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Consider three boundaries before deciding whether the model is applicable: the system under study, the observation period, and the intervention boundary. System boundaries determine which inventories and energy flows are included. Observation periods distinguish transient loss of control from a steady process average. Intervention boundaries identify where automatic protection, human response or passive containment can plausibly act. A safeguard that acts after the harm does not prevent the initiating event, although it may limit the consequence.

Worked reasoning example

Unverified numerical or qualitative illustration: With λ_DU=2×10⁻⁶ /h and T=4000 h, the simplified contribution is PFD_avg≈0.004. Begin with the stated conditions only. Write the relationships that must hold, then identify at least one variable not specified in the example. If an exact arithmetic result is given, reproduce it independently and add a clear qualifier about the simplified model. If the example is qualitative, draw a two-branch argument: one where the existing barrier is available and one where it is defeated by a plausible condition. Do not fill missing branches with assumed success simply to obtain a final score.

A useful way to test the claim is to ask what change would produce the opposite conclusion. For this topic, the specific analytical trap is selecting a sil from this single-parameter approximation or ignoring common cause and repair. Try to construct a counterexample with the same nominal process equipment but an altered startup, maintenance, utility, human or instrument condition. A single plausible counterexample indicates that the original claim was conditional. It does not automatically establish that the process is unsafe; it establishes which fact must be investigated before any stronger judgment.

Evidence and traceability

The minimum relevant evidence set is sif requirements, diagnostic coverage, testing effectiveness, architectures and applicable standards. For each item record source, revision, date, scope, owner and confidence. Separate field-measured values from vendor guarantees, industry generic estimates and deliberately fictional learning inputs. For example, two pumps sold at the same nominal capacity do not necessarily share seal arrangements, failure modes or instrument interfaces. Even an authoritative standard does not substitute for actual testing or determine whether a particular facility falls within its legal scope.

An effective review checks whether evidence is current for the operating mode. Startup differs from steady production; temporary operation after a maintenance outage may differ from both. Procedures, alarms and emergency equipment must be evaluated for those modes explicitly. A reliability assertion based on one short interval must not silently be extended to years of service. Missing evidence should generate a specific work request instead of a generic recommendation to “improve safety.”

Laboratory investigation and sensitivity

Use [Lab 13: Illustrative barrier-chain success](../labs/lab-13.html). The printed equation is P(success of ≥1) = 1−p_fail,1 p_fail,2. Calculate total success of two independently functioning barriers on demand. Start from each slider's default, record the displayed metric and vary the first parameter over five or more settings. The graph and CSV should agree with your hand calculations. Next, change one other parameter while keeping the first fixed; this distinguishes a mathematical sensitivity from a trend caused by simultaneous input changes.

Investigation target: How would shared instrument power alter independence? The major simplification is Does not model common-cause, bypass, diagnostics or quality of barrier claims.. A good lab report predicts the sign of the derivative or change before observing the plot, then explains what physical process that derivative represents. If an output is nonphysical or a limiting denominator becomes zero, it should be reported as an invalid domain rather than manipulated into a finite reassuring result. Place the lesson's analytical relationship alongside the lab relation; explain whether they describe the same physical quantity or different levels of abstraction.

As a challenge, compare this model with [Lab 14: Conditional LOPA arithmetic](../labs/lab-14.html). The second model's relation is f_residual = f_i PFD₁ PFD₂, and its stated limitation is Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance.. The comparison is not an invitation to combine numbers blindly. Explain what would need to be measured so the two simplified relationships could appear in one defensible engineering argument.

Failure-first decision review

The unacceptable shortcut is selecting a sil from this single-parameter approximation or ignoring common cause and repair. Make a table with columns assumption, possible failure, observation that would expose it, cheapest credible check, owner, and decision consequence. For this particular topic the review should prioritize the evidence sources above rather than produce a broad list of every conceivable failure. Then ask what is the most important remaining uncertainty if all routine checks pass. Low-frequency high-consequence scenarios often cannot be validated simply by waiting for an incident.

The recommended analytical action is: Separate arithmetic demonstration from qualified lifecycle design and verification. This recommendation is a learning exercise, not a control-system change or site-specific directive. Describe its boundaries. What would have to be established by independent qualified review? How would an operator learn that the intended protective measure had become unavailable? Which record would demonstrate closure after a modification? A paper action with no verification is not the same as an effective protective function.

Interpreting uncertainty and competing explanations

Uncertainty enters from input data, model structure, operating variability and human or organizational factors. Input uncertainty might be reduced by a calibrated measurement, whereas model-structure uncertainty demands a different physical model or field trial. Increasing the number of decimal places addresses neither. Separate uncertainty that could reverse the conclusion from uncertainty that changes only the reported numerical precision. The severity of a credible major-accident scenario should influence how urgently an evidence gap is reviewed, even when its probability is difficult to quantify.

For safety instrumented functions and proof testing, an apparently successful barrier test may demonstrate only the modes exercised by the test. It might not probe lost utilities, common-cause failure, maintenance bypass or the specific initiating condition. A useful counterfactual question is: If the expected result were wrong tomorrow, which observation would reveal it first? Identify an observable precursor and a clear escalation action. This turns an educational calculation into a disciplined evidence requirement without representing it as a plant certification.

Independent exercises

1. Boundary and mechanism: Explain how proof-test coverage, bypass duration and systematic errors can invalidate the approximation. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 13. Show units, the governing relationship and a simple limiting-case or conservation check.

3. Scenario variation: Replace one favorable assumption with an unfavorable but plausible operating condition. Explain which safeguarding claim is weakened and why.

4. Decision note: Summarize in 200–300 words whether separate arithmetic demonstration from qualified lifecycle design and verification. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why selecting a sil from this single-parameter approximation or ignoring common cause and repair would be misleading when a high-consequence scenario is involved.

Lesson outcome checklist

• A credible scenario chain is drawn, without conflating initiating cause, top event and outcome.
• Model assumptions and units are explicit and the numerical output is checked independently.
• Any barrier credit is tied to function, independence, availability, evidence and an owner.
• The decision specifies what remains unverified; it does not present an educational model as a safe operating limit.

Applied Project 05 — Protection Layers and Functional Safety

Scenario and objective

Scenario: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter.

Target: Separate prevention, control and mitigation; test independence assumptions in illustrative barrier and safety-instrumented-function calculations.

The task is a supervised conceptual study. It is not permission to change operating procedures, introduce hazardous chemicals, bypass protection or size relief devices. Assume that a multidisciplinary panel must decide whether to commission additional analysis, not whether this student workbook certifies a plant. Your deliverable must identify the claim being made, what evidence supports it, and what uncertainty remains. The board values clear red flags over cosmetic completion percentages.

Work package A: describe the situation

Draw a block-flow boundary showing process inventory, incoming feeds or energy, manipulated variables, utilities, protective controls and relevant maintenance interfaces. Record the operating mode, unit conventions, material identity gaps and any location- or jurisdiction-dependent regulatory questions. Write one plausible hazardous event without guessing its annual frequency. For each asserted safeguard, identify what action it takes, when it acts relative to the top event, and which elements it shares with other protective controls.

The case provides a starting point only: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter.. Ask how equipment failure and incorrect operating information could combine. Check a routine operation, startup, shutdown and an interrupted utility condition. Treat any missing process safety information as a question with an owner; do not silently assume that a procedure exists or a transmitter is independent. Make a compact register of at least eight assumptions grouped into physical properties, instrumentation, human response and external conditions.

Work package B: model and verify

Lab 13 — [Illustrative barrier-chain success](../labs/lab-13.html). Compute the baseline from P(success of ≥1) = 1−p_fail,1 p_fail,2 and export a one-parameter sweep. How would shared instrument power alter independence? The condition Does not model common-cause, bypass, diagnostics or quality of barrier claims. must appear as a red-line limitation in the report. Record at least one changed parameter set and reproduce one plotted point without JavaScript. Explain whether a favorable change in this model would genuinely improve the identified hazard or merely change one simplified quantity.

Lab 14 — [Conditional LOPA arithmetic](../labs/lab-14.html). Compute the baseline from f_residual = f_i PFD₁ PFD₂ and export a one-parameter sweep. Identify a shared-cause case where this figure grossly understates risk. The condition Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance. must appear as a red-line limitation in the report. Record at least one changed parameter set and reproduce one plotted point without JavaScript. Explain whether a favorable change in this model would genuinely improve the identified hazard or merely change one simplified quantity.

Lab 15 — [Low-demand proof-test approximation](../labs/lab-15.html). Compute the baseline from PFD_avg ≈ λ_DU T / 2 and export a one-parameter sweep. Halve interval; explain why actual PFD may not halve when common-cause errors dominate. The condition Small λT approximation; omits coverage, repairs, architecture and systemic failures; not IEC 61511 verification. must appear as a red-line limitation in the report. Record at least one changed parameter set and reproduce one plotted point without JavaScript. Explain whether a favorable change in this model would genuinely improve the identified hazard or merely change one simplified quantity.

Work package C: argue the controls

Prepare a bow-tie-style diagram with three credible threats and two possible consequence pathways. Describe at least one prevention design measure, one operating or inspection control, one possible protective-system layer and one mitigation measure. Do not treat all of these as independent or calculate a cumulative protection factor without justified evidence. Identify a shared-cause vulnerability (for example, common power supply, blocked sensing line or maintenance isolation) and show how your recommended verification would detect it.

Create a control register with columns control purpose, covered initiating mechanism, physical element, mode of demand, availability evidence, testing method, owner, and unresolved dependency. A valid control should have a documented performance claim that can be tested in the field. If field testing would introduce danger, propose a qualified nonintrusive verification method or documentation review instead of suggesting an uncontrolled trial.

Work package D: decision, uncertainty and follow-up

Deliver a 600–900-word decision memo with a recommendation of further analysis, redesign for inherent safety, or insufficient evidence to proceed. The answer must not state that a student's simulation proves safety or regulatory compliance. Begin with the most serious potentially unmitigated scenario. Include a one-page assumptions register and a prioritized list of the five most valuable additional data items. Differentiate uncertainty in inputs from uncertainty in the basic model structure. Show how one new piece of evidence could reverse your recommendation.

The expected project artifact is: Never credit a layer twice, and never infer a real SIL target, safety integrity verification or tolerability decision from a slider. Describe at least three acceptance tests, responsible roles and the evidence each would produce. Finish with a handover list for a qualified engineer or hazard-analysis team. A statement like “we will improve training” is insufficient without specifying which error pathway it is intended to reduce and how the effect would be checked.

Assessment criteria

• Process and time boundaries are explicit and aligned with the chosen hazardous event.
• Equations reproduce the baseline, limits are visible, and CSV data agree with an independent computation.
• Claimed safeguards have separate mechanisms and credible evidence; common-cause weaknesses are challenged.
• Unknown chemical properties, actual frequencies and code requirements are not invented.
• The conclusion is proportional to evidence and contains accountable next actions rather than a blanket approval.

Unit 05 — Assessment: Protection Layers and Functional Safety

Scenario: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. This assessment contains 16 separately numbered, multi-part tasks, four per lesson. Students should complete the numerical parts independently and explicitly distinguish illustrative assumptions from measured or regulated inputs. There is no site-specific pass/fail safety conclusion.

Learning standard: Never credit a layer twice, and never infer a real SIL target, safety integrity verification or tolerability decision from a slider.

Scoring rubric

Each task is worth ten marks: physical or causal boundary (2), correct relationship or defensible logic (2), evidence and units (2), explicit limitation (2), and transparent action or interpretation (2). A risk claim without necessary provenance receives no numerical credit regardless of apparent precision. Students may challenge an ill-posed input as part of the solution if they explain which information is missing.

Lesson 1 — Bow ties and barrier assurance

The four problems below require different kinds of evidence; do not copy a single stock paragraph as four answers.

Q01 — Physical reconstruction (10 marks). Start from Threat → preventive barrier → top event → mitigation → outcome in the following case: For tank overflow, compare independent high-high shutdown with secondary containment; each interrupts a different point in the chain. Identify each term or causal link, the relevant units or event definition, and a reasonable limiting case. Describe at least one operational state in which the relationship would no longer be adequate. For numerical examples, reproduce the printed result with no more significant figures than the inputs justify.

Q02 — Interactive computation and falsification (10 marks). Run [Lab 13](../labs/lab-13.html), Illustrative barrier-chain success. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: How would shared instrument power alter independence? Evaluate the specific restriction Does not model common-cause, bypass, diagnostics or quality of barrier claims.; provide a case where this restriction matters and state what additional physical model would be needed.

Q03 — Hazard and barrier chain (10 marks). Examine bow ties and barrier assurance using this hazard background: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Name an initiating mechanism, the loss-of-control top event, one possible consequence, an inherently safer alternative and an independent barrier if credible. The analysis must explicitly challenge the misleading assumption counting a warning label, operator procedure and shared alarm as independent hardware barriers. Which shared utility, maintenance activity or human action could defeat the claimed protections?

Q04 — Evidence-led technical memo (10 marks). Prepare a 250-word memo answering: For three controls, define functionality, reliability, availability and assurance evidence. The recommendation should be translate a bow tie into a testable barrier register but you must justify or challenge it. List the real-world records needed: Barrier definitions, independence review, inspection records and response competence. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 2 — Independent protection layer screening

The four problems below require different kinds of evidence; do not copy a single stock paragraph as four answers.

Q05 — Physical reconstruction (10 marks). Start from f_mitigated ≈ f_initiating × Π(PFD_i) under justified assumptions in the following case: A synthetic f_i=0.02/y with independent PFDs 0.1 and 0.05 produces 0.0001/y in a teaching-only arithmetic example. Identify each term or causal link, the relevant units or event definition, and a reasonable limiting case. Describe at least one operational state in which the relationship would no longer be adequate. For numerical examples, reproduce the printed result with no more significant figures than the inputs justify.

Q06 — Interactive computation and falsification (10 marks). Run [Lab 14](../labs/lab-14.html), Conditional LOPA arithmetic. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: Identify a shared-cause case where this figure grossly understates risk. Evaluate the specific restriction Teaching illustration only. Never use for site LOPA, SIL assignment or risk acceptance.; provide a case where this restriction matters and state what additional physical model would be needed.

Q07 — Hazard and barrier chain (10 marks). Examine independent protection layer screening using this hazard background: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Name an initiating mechanism, the loss-of-control top event, one possible consequence, an inherently safer alternative and an independent barrier if credible. The analysis must explicitly challenge the misleading assumption giving duplicate credit to alarms and trips that share sensors or power. Which shared utility, maintenance activity or human action could defeat the claimed protections?

Q08 — Evidence-led technical memo (10 marks). Prepare a 250-word memo answering: Trace whether two barriers share detection, logic solver, final element or maintenance procedure. The recommendation should be treat the calculated number as conditional on assumptions, never certification but you must justify or challenge it. List the real-world records needed: Independent design review, credible initiating frequencies, demand rates, proof-test data and site risk criteria. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 3 — Failure on demand and common-cause failure

The four problems below require different kinds of evidence; do not copy a single stock paragraph as four answers.

Q09 — Physical reconstruction (10 marks). Start from P(2 failures) = p1 p2 only for independent events in the following case: Two nominal 0.1 PFD devices have independent combined PFD 0.01; a shared defeat mechanism changes this conclusion. Identify each term or causal link, the relevant units or event definition, and a reasonable limiting case. Describe at least one operational state in which the relationship would no longer be adequate. For numerical examples, reproduce the printed result with no more significant figures than the inputs justify.

Q10 — Interactive computation and falsification (10 marks). Run [Lab 15](../labs/lab-15.html), Low-demand proof-test approximation. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: Halve interval; explain why actual PFD may not halve when common-cause errors dominate. Evaluate the specific restriction Small λT approximation; omits coverage, repairs, architecture and systemic failures; not IEC 61511 verification.; provide a case where this restriction matters and state what additional physical model would be needed.

Q11 — Hazard and barrier chain (10 marks). Examine failure on demand and common-cause failure using this hazard background: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Name an initiating mechanism, the loss-of-control top event, one possible consequence, an inherently safer alternative and an independent barrier if credible. The analysis must explicitly challenge the misleading assumption assuming identical hardware components automatically provide independent risk reduction. Which shared utility, maintenance activity or human action could defeat the claimed protections?

Q12 — Evidence-led technical memo (10 marks). Prepare a 250-word memo answering: Map which two supposed safeguards fail together during lost instrument air. The recommendation should be require common-cause and systematic-failure review before taking credit but you must justify or challenge it. List the real-world records needed: Cause-and-effect matrices, power distribution, proof-test documentation and bypass logs. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 4 — Safety instrumented functions and proof testing

The four problems below require different kinds of evidence; do not copy a single stock paragraph as four answers.

Q13 — Physical reconstruction (10 marks). Start from PFD_avg ≈ λ_DU T/2 for small λ_DU T in the following case: With λ_DU=2×10⁻⁶ /h and T=4000 h, the simplified contribution is PFD_avg≈0.004. Identify each term or causal link, the relevant units or event definition, and a reasonable limiting case. Describe at least one operational state in which the relationship would no longer be adequate. For numerical examples, reproduce the printed result with no more significant figures than the inputs justify.

Q14 — Interactive computation and falsification (10 marks). Run [Lab 13](../labs/lab-13.html), Illustrative barrier-chain success. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: How would shared instrument power alter independence? Evaluate the specific restriction Does not model common-cause, bypass, diagnostics or quality of barrier claims.; provide a case where this restriction matters and state what additional physical model would be needed.

Q15 — Hazard and barrier chain (10 marks). Examine safety instrumented functions and proof testing using this hazard background: A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter. Name an initiating mechanism, the loss-of-control top event, one possible consequence, an inherently safer alternative and an independent barrier if credible. The analysis must explicitly challenge the misleading assumption selecting a sil from this single-parameter approximation or ignoring common cause and repair. Which shared utility, maintenance activity or human action could defeat the claimed protections?

Q16 — Evidence-led technical memo (10 marks). Prepare a 250-word memo answering: Explain how proof-test coverage, bypass duration and systematic errors can invalidate the approximation. The recommendation should be separate arithmetic demonstration from qualified lifecycle design and verification but you must justify or challenge it. List the real-world records needed: SIF requirements, diagnostic coverage, testing effectiveness, architectures and applicable standards. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Synthesis: no-go evidence check

Construct an evidence table for protection layers and functional safety. Include the case A high-level trip is credited alongside an operator alarm on a tank with a common level transmitter.. State one safety-critical condition that cannot be closed by the calculations above. Propose a technically reasonable way to obtain missing evidence, an owner and a hold point. Explain why a numerically appealing dashboard could still hide an unacceptable unresolved scenario.