Chapter 10 — Engineering ethics and safety

Lesson map

Lesson 10 published. Map, example, EX028.

flowchart TD
  N0["Learning outcomes"]
  N1["10.1 Duties of an engineer"]
  N2["10.2 Safety versus security"]
  N3["10.3 Pressure to misreport"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX028"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["10.1 Duties of an engineer"]
  N2["10.2 Safety versus security"]
  N3["10.3 Pressure to misreport"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX028"]

[Learning outcomes]
    |
    v
[10.1 Duties of an engineer]
    |
    v
[10.2 Safety versus security]
    |
    v
[10.3 Pressure to misreport]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX028]

Learning outcomes

You will (1) apply engineering ethics to governance decisions; (2) weigh safety against security and compliance; (3) handle pressure to misreport.

10.1 Duties of an engineer

Nadia studies professional codes that place public safety first. At Ardwell, governance decisions affect electricity supply to homes, hospitals and businesses, so they carry safety consequences. She learns that an engineer who signs off a control or a risk assessment takes responsibility for its accuracy. Ethics also means competence: not claiming expertise in an area where one has none, and asking for help when a judgement exceeds one's knowledge. These duties apply equally to compliance work, which can seem administrative but shapes real decisions about public infrastructure.

10.2 Safety versus security

Some security controls can harm safety. Locking an operator out after failed sign-ins could prevent them from responding to a grid emergency. Nadia learns that in industrial settings, availability and safety often take priority, so controls must be designed with operators. She proposes monitoring and alerting for repeated failures at control consoles instead of lockout, with a physical access restriction to the control room. The decision is documented with its reasoning, so auditors understand why a standard control was adapted rather than applied unchanged.

10.3 Pressure to misreport

In a case study, a manager asks an analyst to mark a failed control test as passed so a certification audit goes smoothly. Nadia discusses the options: refuse, record the true result, escalate through the proper channel and protect the evidence. She learns that misreporting control results undermines the whole management system and may break laws or contracts. Prof. Brenner adds that organisations should make honest reporting safe, because a culture that punishes bad news drives problems out of sight until they cause harm.

Worked example

Nadia applies safety-first ethics, adapts lockout to monitoring at control consoles and plans an honest response to pressure to misreport.

Synthetic case. The case study and decisions are synthetic.

Errors and limits

Codes give principles, not answers. Escalation can carry personal risk.

Exercises

• EX028 — Sign-off duty. What does signing off a risk assessment mean for an engineer?
  Show marking criteria

  Rubric: 3 = taking responsibility for its accuracy;; 2 = responsibility;; 1 = vague;; 0 = none.
• EX029 — Console alternative. What did Nadia propose instead of lockout at control consoles?
  Show marking criteria

  Rubric: 3 = monitoring and alerting with physical access restriction;; 2 = monitoring;; 1 = lockout;; 0 = none.
• EX030 — Honest culture. Why should organisations make honest reporting safe?
  Show marking criteria

  Rubric: 3 = punishing bad news hides problems until they cause harm;; 2 = culture;; 1 = vague;; 0 = none.

Synthesis

Engineering ethics put safety and honest reporting at the heart of governance work.

Continue studying — chapter 10 of 50

← Chapter 09 (draft) · Course chapter index · Chapter 11 (draft) →