Case Study 3 (Outline): Preparing for a Turnaround

Status: DRAFT outline. Placeholders only. Follows Playbook DRAFT v0.2 (rules 5 and 6, section 5). Do not publish until every placeholder is filled from a real, permitted source. Audience: Mechanical / Instrumentation & Electrical (I&E) / Both TBD: owner to supply Product used: TBD: owner to supply, e.g., Turnaround track, turnaround prep workshop, turnaround coordination sheet

1. Headline

TBD: owner to supply, written from the real result, no superlatives.

2. Who

• Organization type: TBD: owner to supply, anonymized unless approved
• Turnaround type and scope, described generically: TBD: owner to supply, only what the client approves
• Team involved: TBD: owner to supply
• [EMPLOYER REVIEW: owner to confirm this subject has no link to the owner's employer or its contractors. Turnaround details are often commercially sensitive; check approval carefully.]

3. Starting point

• Planning challenges the team reported: TBD: owner to supply, e.g., late scope, materials, contractor coordination

4. What they did

• Course modules, workshops or templates used: TBD: owner to supply
• Scope control approach: TBD: owner to supply
• Materials and contractor preparation: TBD: owner to supply
• Mechanical and I&E coordination: TBD: owner to supply
• Scheduling tool used, e.g., SAP Plant Maintenance (SAP PM), Microsoft Project or Primavera P6: TBD: owner to supply, only if the client approves naming it

5. Results

• Qualitative change: TBD: owner to supply
• Measured result (optional): TBD: owner to supply, only if measured, with definition, period and data source; otherwise delete this line

6. Quote

TBD: owner to supply, a real quote with written permission, or leave this section out.

7. Permission and review checklist

• Written permission on file for names, titles, quotes and numbers
• No confidential scope lists, schedules, costs, tags, screenshots or documents
• [EMPLOYER REVIEW: owner checked for any employer link or employer-specific detail]
• Owner verified all technical statements
• Disclaimer added (see README)

Verification log

• Verified by: [owner] | Date: [ ] | Notes: [ ]