Mechanical Integrity, Human Factors and Change

Learning objective. Analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system.

Linked synthetic case. A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration.

What an adequate output contains. Change classification must consider chemical, technology, equipment, procedure, people and facility interactions, not just purchase price.

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, analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system. 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 19: Exponential component survival](../labs/lab-19.html) — Illustrate constant-failure-rate survival over a mission duration. Boundary: Failure rate constant; a hypothetical generic component is not a certified SIF.
• [Lab 20: Independent two-channel unavailability](../labs/lab-20.html) — Calculate dual-channel unavailability only when independence holds. Boundary: No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural verification.
• [Lab 21: Proof-test coverage thought experiment](../labs/lab-21.html) — Estimate detection count from a hypothetical cohort of latent defects. Boundary: Illustration of coverage only, not a method to infer actual defect populations.

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: Reliability, failure rates and limitations

For a constant hazard rate, exponential survival is a mathematical model for time-to-failure. Real degradation, maintenance and duty cycles may create nonconstant hazards and dependence. Key analytical anchor: R(t) = exp(−λt). Investigate the following case: An illustrative λ=10⁻⁵ /h over 10,000 h gives R≈0.9048 with ideal independence of time intervals. The most likely conceptual error is using catalog mtbf as a measured probability for a specific safety function. In the lesson, assemble failure mode evidence, mission profile, environment and maintenance records before drawing the operational conclusion: use reliability proxies to direct investigation, not substitute for field proof. Further discussion: Contrast constant failure rate with wear-out and describe how inspection could reveal the difference.

Lesson 2: Mechanical integrity and inspection effectiveness

Inspection programs manage specific degradation mechanisms by verifying actual condition and performance, including pressure vessels, piping, relief systems, sensors and emergency shutdown elements. Key analytical anchor: Verified coverage = inspected relevant items / items due. Investigate the following case: If 76 of 80 safety-critical inspections due were completed, coverage is 95%, but the missing four may dominate consequence. The most likely conceptual error is interpreting inspection completion alone as equipment fitness-for-service. In the lesson, assemble inspection findings, thickness history, metallurgy, damage mechanisms and deferred action approvals before drawing the operational conclusion: highlight critical overdue tasks and defect severity rather than only aggregate percent. Further discussion: Develop an inspection plan separating detection capability, interval and remedial action times.

Lesson 3: Human factors, work permits and contractors

Work design affects cognitive load, error opportunities and recovery. Lockout/tagout, permit-to-work and confined space processes require physically verified isolation and role clarity; contractor training cannot replace engineering controls. Key analytical anchor: Error pathway = task demands + interface design + organizational conditions. Investigate the following case: Two similar valves without position indication complicate a maintenance isolation; a second signature alone may not prevent wrong-line work. The most likely conceptual error is assigning root cause to human error without studying design and supervision. In the lesson, assemble task observations, human-machine interface review, near-miss narratives and permit audits before drawing the operational conclusion: design out error where possible; verify isolation and ownership at interfaces. Further discussion: Propose a physical poka-yoke or labeling change and specify how to prove it helps.

Lesson 4: Management of change and temporary modifications

MOC evaluates proposed changes to chemicals, equipment, procedures, controls, staffing and process technology before implementation. Temporary changes can become long-lived hazards if expiry and rollback are not controlled. Key analytical anchor: MOC cycle = request → hazard review → authorization → implement → verify → close. Investigate the following case: A pump replacement increases its maximum discharge capacity by 25%; downstream relief, alarms and piping must be reconsidered. The most likely conceptual error is calling a modification like-for-like based on purchase description alone. In the lesson, assemble old and new data sheets, marked-up p&ids, action log, training and pssr records before drawing the operational conclusion: treat uncertainty and temporary bypasses as triggers for review. Further discussion: Draft change acceptance criteria that include startup support, procedural updates and reversal plan.

Unit completion checkpoint

The minimum acceptable submission contains an annotated process boundary for mechanical integrity, human factors and change, 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 7 · Lesson 1: Reliability, failure rates and limitations

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

The engineering question

For a constant hazard rate, exponential survival is a mathematical model for time-to-failure. Real degradation, maintenance and duty cycles may create nonconstant hazards and dependence. This lesson belongs to Mechanical Integrity, Human Factors and Change, where the course objective is to analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system. 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. An illustrative λ=10⁻⁵ /h over 10,000 h gives R≈0.9048 with ideal independence of time intervals. 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 R(t) = exp(−λ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 reliability, failure rates and limitations is the following: For a constant hazard rate, exponential survival is a mathematical model for time-to-failure. Real degradation, maintenance and duty cycles may create nonconstant hazards and dependence. 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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: An illustrative λ=10⁻⁵ /h over 10,000 h gives R≈0.9048 with ideal independence of time intervals. 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 using catalog mtbf as a measured probability for a specific safety function. 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 failure mode evidence, mission profile, environment and maintenance records. 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 19: Exponential component survival](../labs/lab-19.html). The printed equation is R = exp(−λt). Illustrate constant-failure-rate survival over a mission duration. 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: Calculate R at two mission times; why could wear-out make the estimate optimistic? The major simplification is Failure rate constant; a hypothetical generic component is not a certified SIF.. 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 20: Independent two-channel unavailability](../labs/lab-20.html). The second model's relation is P(both unavailable) = p₁ p₂, and its stated limitation is No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural 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 using catalog mtbf as a measured probability for a specific safety function. 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: Use reliability proxies to direct investigation, not substitute for field proof. 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 reliability, failure rates and limitations, 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: Contrast constant failure rate with wear-out and describe how inspection could reveal the difference. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 19. 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 use reliability proxies to direct investigation, not substitute for field proof. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why using catalog mtbf as a measured probability for a specific safety function 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 7 · Lesson 2: Mechanical integrity and inspection effectiveness

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

The engineering question

Inspection programs manage specific degradation mechanisms by verifying actual condition and performance, including pressure vessels, piping, relief systems, sensors and emergency shutdown elements. This lesson belongs to Mechanical Integrity, Human Factors and Change, where the course objective is to analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system. 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. If 76 of 80 safety-critical inspections due were completed, coverage is 95%, but the missing four may dominate consequence. 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 Verified coverage = inspected relevant items / items due. 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 mechanical integrity and inspection effectiveness is the following: Inspection programs manage specific degradation mechanisms by verifying actual condition and performance, including pressure vessels, piping, relief systems, sensors and emergency shutdown elements. 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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: If 76 of 80 safety-critical inspections due were completed, coverage is 95%, but the missing four may dominate consequence. 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 interpreting inspection completion alone as equipment fitness-for-service. 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 inspection findings, thickness history, metallurgy, damage mechanisms and deferred action approvals. 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 20: Independent two-channel unavailability](../labs/lab-20.html). The printed equation is P(both unavailable) = p₁ p₂. Calculate dual-channel unavailability only when independence holds. 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: Show effect of an unmodeled 2% common-cause path. The major simplification is No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural 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 21: Proof-test coverage thought experiment](../labs/lab-21.html). The second model's relation is Detected = coverage × hidden defects, and its stated limitation is Illustration of coverage only, not a method to infer actual defect populations.. 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 interpreting inspection completion alone as equipment fitness-for-service. 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: Highlight critical overdue tasks and defect severity rather than only aggregate percent. 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 mechanical integrity and inspection effectiveness, 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: Develop an inspection plan separating detection capability, interval and remedial action times. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 20. 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 highlight critical overdue tasks and defect severity rather than only aggregate percent. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why interpreting inspection completion alone as equipment fitness-for-service 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 7 · Lesson 3: Human factors, work permits and contractors

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

The engineering question

Work design affects cognitive load, error opportunities and recovery. Lockout/tagout, permit-to-work and confined space processes require physically verified isolation and role clarity; contractor training cannot replace engineering controls. This lesson belongs to Mechanical Integrity, Human Factors and Change, where the course objective is to analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system. 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 similar valves without position indication complicate a maintenance isolation; a second signature alone may not prevent wrong-line work. 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 Error pathway = task demands + interface design + organizational conditions. 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 human factors, work permits and contractors is the following: Work design affects cognitive load, error opportunities and recovery. Lockout/tagout, permit-to-work and confined space processes require physically verified isolation and role clarity; contractor training cannot replace engineering controls. 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 similar valves without position indication complicate a maintenance isolation; a second signature alone may not prevent wrong-line work. 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 assigning root cause to human error without studying design and supervision. 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 task observations, human-machine interface review, near-miss narratives and permit audits. 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 21: Proof-test coverage thought experiment](../labs/lab-21.html). The printed equation is Detected = coverage × hidden defects. Estimate detection count from a hypothetical cohort of latent defects. 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: What does successful testing of 40 defects leave unknown? The major simplification is Illustration of coverage only, not a method to infer actual defect populations.. 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 19: Exponential component survival](../labs/lab-19.html). The second model's relation is R = exp(−λt), and its stated limitation is Failure rate constant; a hypothetical generic component is not a certified SIF.. 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 assigning root cause to human error without studying design and supervision. 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: Design out error where possible; verify isolation and ownership at interfaces. 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 human factors, work permits and contractors, 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: Propose a physical poka-yoke or labeling change and specify how to prove it helps. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 21. 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 design out error where possible; verify isolation and ownership at interfaces. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why assigning root cause to human error without studying design and supervision 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 7 · Lesson 4: Management of change and temporary modifications

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

The engineering question

MOC evaluates proposed changes to chemicals, equipment, procedures, controls, staffing and process technology before implementation. Temporary changes can become long-lived hazards if expiry and rollback are not controlled. This lesson belongs to Mechanical Integrity, Human Factors and Change, where the course objective is to analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system. 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 pump replacement increases its maximum discharge capacity by 25%; downstream relief, alarms and piping must be reconsidered. 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 MOC cycle = request → hazard review → authorization → implement → verify → close. 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 management of change and temporary modifications is the following: MOC evaluates proposed changes to chemicals, equipment, procedures, controls, staffing and process technology before implementation. Temporary changes can become long-lived hazards if expiry and rollback are not controlled. 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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 pump replacement increases its maximum discharge capacity by 25%; downstream relief, alarms and piping must be reconsidered. 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 calling a modification like-for-like based on purchase description alone. 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 old and new data sheets, marked-up p&ids, action log, training and pssr records. 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 19: Exponential component survival](../labs/lab-19.html). The printed equation is R = exp(−λt). Illustrate constant-failure-rate survival over a mission duration. 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: Calculate R at two mission times; why could wear-out make the estimate optimistic? The major simplification is Failure rate constant; a hypothetical generic component is not a certified SIF.. 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 20: Independent two-channel unavailability](../labs/lab-20.html). The second model's relation is P(both unavailable) = p₁ p₂, and its stated limitation is No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural 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 calling a modification like-for-like based on purchase description alone. 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 uncertainty and temporary bypasses as triggers for review. 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 management of change and temporary modifications, 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: Draft change acceptance criteria that include startup support, procedural updates and reversal plan. Label at least one fact, one assumption and one unknown.

2. Quantitative check: Reproduce one result from Lab 19. 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 uncertainty and temporary bypasses as triggers for review. Specify the additional observation that could change your conclusion.

5. Critical review: Explain why calling a modification like-for-like based on purchase description alone 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 07 — Mechanical Integrity, Human Factors and Change

Scenario and objective

Scenario: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration.

Target: Analyze inspection intervals, deterioration, maintenance backlog, contractor interfaces, operational competence and management of change as a joined system.

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 replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration.. 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 19 — [Exponential component survival](../labs/lab-19.html). Compute the baseline from R = exp(−λt) and export a one-parameter sweep. Calculate R at two mission times; why could wear-out make the estimate optimistic? The condition Failure rate constant; a hypothetical generic component is not a certified SIF. 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 20 — [Independent two-channel unavailability](../labs/lab-20.html). Compute the baseline from P(both unavailable) = p₁ p₂ and export a one-parameter sweep. Show effect of an unmodeled 2% common-cause path. The condition No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural 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.

Lab 21 — [Proof-test coverage thought experiment](../labs/lab-21.html). Compute the baseline from Detected = coverage × hidden defects and export a one-parameter sweep. What does successful testing of 40 defects leave unknown? The condition Illustration of coverage only, not a method to infer actual defect populations. 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: Change classification must consider chemical, technology, equipment, procedure, people and facility interactions, not just purchase price. 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 07 — Assessment: Mechanical Integrity, Human Factors and Change

Scenario: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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: Change classification must consider chemical, technology, equipment, procedure, people and facility interactions, not just purchase price.

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 — Reliability, failure rates and limitations

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 R(t) = exp(−λt) in the following case: An illustrative λ=10⁻⁵ /h over 10,000 h gives R≈0.9048 with ideal independence of time intervals. 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 19](../labs/lab-19.html), Exponential component survival. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: Calculate R at two mission times; why could wear-out make the estimate optimistic? Evaluate the specific restriction Failure rate constant; a hypothetical generic component is not a certified SIF.; provide a case where this restriction matters and state what additional physical model would be needed.

Q03 — Hazard and barrier chain (10 marks). Examine reliability, failure rates and limitations using this hazard background: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 using catalog mtbf as a measured probability for a specific safety function. 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: Contrast constant failure rate with wear-out and describe how inspection could reveal the difference. The recommendation should be use reliability proxies to direct investigation, not substitute for field proof but you must justify or challenge it. List the real-world records needed: Failure mode evidence, mission profile, environment and maintenance records. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 2 — Mechanical integrity and inspection effectiveness

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 Verified coverage = inspected relevant items / items due in the following case: If 76 of 80 safety-critical inspections due were completed, coverage is 95%, but the missing four may dominate consequence. 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 20](../labs/lab-20.html), Independent two-channel unavailability. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: Show effect of an unmodeled 2% common-cause path. Evaluate the specific restriction No common cause, diagnostics, bypass or partial-stroke proof; not hardware architectural verification.; provide a case where this restriction matters and state what additional physical model would be needed.

Q07 — Hazard and barrier chain (10 marks). Examine mechanical integrity and inspection effectiveness using this hazard background: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 interpreting inspection completion alone as equipment fitness-for-service. 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: Develop an inspection plan separating detection capability, interval and remedial action times. The recommendation should be highlight critical overdue tasks and defect severity rather than only aggregate percent but you must justify or challenge it. List the real-world records needed: Inspection findings, thickness history, metallurgy, damage mechanisms and deferred action approvals. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 3 — Human factors, work permits and contractors

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 Error pathway = task demands + interface design + organizational conditions in the following case: Two similar valves without position indication complicate a maintenance isolation; a second signature alone may not prevent wrong-line work. 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 21](../labs/lab-21.html), Proof-test coverage thought experiment. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: What does successful testing of 40 defects leave unknown? Evaluate the specific restriction Illustration of coverage only, not a method to infer actual defect populations.; provide a case where this restriction matters and state what additional physical model would be needed.

Q11 — Hazard and barrier chain (10 marks). Examine human factors, work permits and contractors using this hazard background: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 assigning root cause to human error without studying design and supervision. 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: Propose a physical poka-yoke or labeling change and specify how to prove it helps. The recommendation should be design out error where possible; verify isolation and ownership at interfaces but you must justify or challenge it. List the real-world records needed: Task observations, human-machine interface review, near-miss narratives and permit audits. Separate a hypothetical mathematical statement from an engineering action and identify the competent approver and a falsifiable follow-up test.

Lesson 4 — Management of change and temporary modifications

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 MOC cycle = request → hazard review → authorization → implement → verify → close in the following case: A pump replacement increases its maximum discharge capacity by 25%; downstream relief, alarms and piping must be reconsidered. 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 19](../labs/lab-19.html), Exponential component survival. Tabulate at least seven points for its first variable, calculate one independent output, then change its second variable. The lab asks: Calculate R at two mission times; why could wear-out make the estimate optimistic? Evaluate the specific restriction Failure rate constant; a hypothetical generic component is not a certified SIF.; provide a case where this restriction matters and state what additional physical model would be needed.

Q15 — Hazard and barrier chain (10 marks). Examine management of change and temporary modifications using this hazard background: A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration. 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 calling a modification like-for-like based on purchase description alone. 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: Draft change acceptance criteria that include startup support, procedural updates and reversal plan. The recommendation should be treat uncertainty and temporary bypasses as triggers for review but you must justify or challenge it. List the real-world records needed: Old and new data sheets, marked-up P&IDs, action log, training and PSSR records. 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 mechanical integrity, human factors and change. Include the case A replacement pump with nominally equivalent capacity changes its seal arrangement, spare parts and alarm configuration.. 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.