Chapter 43 — Industry or public-service practice
Lesson map
Lesson 43 published. Map, example, EX127.
flowchart TD
N0["Learning outcomes"]
N1["43.1 Placement"]
N2["43.2 Sanitized reporting"]
N3["43.3 Translation"]
N4["Practice note"]
N5["43.1b Clearance and conflicts"]
N6["Field note — constraints appendix"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX127"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["43.1 Placement"]
N2["43.2 Sanitized reporting"]
N3["43.3 Translation"]
N4["Practice note"]
N5["43.1b Clearance and conflicts"]
N6["Field note — constraints appendix"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX127"]
[Learning outcomes]
|
v
[43.1 Placement]
|
v
[43.2 Sanitized reporting]
|
v
[43.3 Translation]
|
v
[Practice note]
|
v
[43.1b Clearance and conflicts]
|
v
[Field note — constraints appendix]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX127]
Learning outcomes
You will (1) adapt CNHP engineering to a host organization's constraints; (2) write a practice report without proprietary detail; (3) translate between process safety, ops and engineering.
43.1 Placement
In industry or public service, work-permit templates, residency and procurement differ.
On her placement at a contract manufacturer, Lena found different permit forms, a different procurement process and stricter rules on where data could be stored than at ABP. She adapted her methods to the host's process instead of importing ABP's forms. What did not change was the core of her practice: tools that stop safely when unsure, measurements with their denominators, and tests run only within the scope the host had approved in writing.
43.2 Sanitized reporting
Course deliverables use synthetic names and aggregates. Real plant identifiers stay inside the host's systems.
Lena's placement report described the vendor laptop risk without naming the host, its plants or its devices. Addresses and host names stayed inside the host's systems, and figures were given only as counts or ranges. The host's clearance review checked the report before it reached the university, and her supervisor graded the sanitized version, so nothing identifying left the organisation. Lena kept the originals on the host's systems.
43.3 Translation
Process safety hears independence and SIL. Ops hears windows and alarms. Engineering hears schemas and tests. Same facts, three dialects.
Synthetic case — Ashford Batch Plant. Lena's placement memo used only ABP synthetic figures; real partner plant names were omitted.
In her placement memo, Lena wrote the same laptop finding three ways: for process safety, as a threat to the independence of the line controllers; for operations, as a scheduling need for updates; and for engineering, as a configuration change. Each reader got the version they needed.
43.4 Errors and limits
"I can't tell you what I did" is not a practice report, even when the host plant's network details are confidential.
Lena's placement report could not include the host's real network details, so she agreed a synthetic reconstruction with her host mentor that kept the structure of the finding but replaced every identifying detail. Her constraints appendix stated what she had not been allowed to examine. This gave the university something to assess without exposing the host, and it is the standard for any placement where the work itself cannot be described directly.
Practice note
If your placement host sells OT scanners, disclose that and still refuse empty scores. Marketing decks are not measurement.
43.1b Clearance and conflicts
Public-service placements may involve clearances. Course artefacts stay at the lowest sensitivity: synthetic reconstructions. Never paste restricted text into GitHub. Practice reports include a constraints appendix graded as heavily as the technical work.
If the host forbids even sanitized metrics, use a fully synthetic twin scenario labelled as such.
Lena's own appendix followed this rule. Lena's agreement with her host mentor was written before drafting began, and it named the figures she could use and the ones she could not.
Field note — constraints appendix
A public-service host forbade foreign SaaS and required FOIA-ready logs. The practice report's constraints appendix explained why architecture C was impossible and why A was chosen. Graders marked the appendix as heavily as the code.
The constraints appendix lists each restriction with the role at the host that imposed it.
43.5 Worked example — translating a placement finding (synthetic ABP)
On placement at a contract manufacturer, Lena observes that the vendor laptop used for PLC updates also browses the internet. Her sanitized report omits host names and addresses, describes the risk in plant terms — "a single laptop carries both internet exposure and the ability to download logic to the line controllers (ATT&CK for ICS T0843)" — and recommends a dedicated, offline-updated engineering laptop. The host organisation's clearance review approves the report before it reaches her university, and the constraints appendix states what she was not permitted to examine.
Exercises
- EX127 — Dialect. Translate fail closed on missing policy for process safety. Rubric: 3 = safety/risk wording; 2 = partial; 1 = jargon dump; 0 = none.
- EX128 — Sanitize. Rewrite a sentence that leaks a real hostname. Rubric: 3 = synthetic substitute; 2 = partial; 1 = still leaks; 0 = none.
- EX129 — Constraint. Two public-service constraints that change architecture. Rubric: 3 = e.g. residency, procurement, FOIA; 2 = one; 1 = vague; 0 = none.
Synthesis
Practice is real constraints plus sanitized learning artefacts.
Continue studying — chapter 43 of 50
← Chapter 42 (draft) · Course chapter index · Chapter 44 (draft) →