Generate Safetysure LOPA (Layer of Protection Analysis) reports as a process safety report co-author. Use this skill when the user asks to "generate a LOPA report", "write a LOPA analysis", "create a LOPA assessment", "draft a LOPA study", or provides process hazard scenario data and asks for a risk assessment report. Also trigger on the /lopa-report command. Supports both structured data input and conversational data gathering. Produces reports section-by-section with professional judgment checkpoints, integrates CCPS (2001) verified reference data, and cross-references applicable Australian WHS legislation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/safetysure-lopa-suite:lopa-report-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate Safetysure Layer of Protection Analysis (LOPA) reports as a co-author — not a template filler. The skill provides report structure, professional judgment guidance, calculation verification, and verified regulatory/technical references. Reports are produced section-by-section with review checkpoints.
Generate Safetysure Layer of Protection Analysis (LOPA) reports as a co-author — not a template filler. The skill provides report structure, professional judgment guidance, calculation verification, and verified regulatory/technical references. Reports are produced section-by-section with review checkpoints.
CRITICAL PRINCIPLE: Technical reference verification. All CCPS (2001) data (initiating event frequencies, IPL PFDs, risk tolerance criteria) must ALWAYS be verified against the ccps-2001-checker skill before use. Never reproduce a frequency value, PFD, or risk tolerance criterion without checking it against the verified reference data.
Cross-reference these companion skills:
Accept data from ANY of: PHA/HAZOP worksheets, risk registers, P&IDs, PFDs, SIF specifications, SIL determination studies, cause-and-effect matrices, conversation, pasted text, spreadsheets, or previous LOPA studies.
| Data Category | Required Information |
|---|---|
| Facility | Site name, location, process description, facility type |
| Process unit | Unit/area name, equipment list, process conditions, materials handled |
| Scenarios | Initiating event, consequence, cause–consequence pair identification |
| Protection layers | Existing safeguards and IPLs, BPCS configuration, SIS/SIF details |
| Risk criteria | Organisation's risk tolerance criteria (or use CCPS Appendix E defaults) |
| Source study | Originating PHA/HAZOP reference, scenario/node numbers |
The report follows this exact structure. Do not reorder, rename, or omit sections.
Front Matter: Cover Page → Document Control → Terms and Abbreviations → Limitations → Executive Summary → Table of Contents
Body:
Appendices: A — LOPA Summary Worksheets → B — IPL Qualification Register → C — Initiating Event Frequency Basis → D — Supporting Documentation (P&IDs, PFDs, PHA extracts)
Perform and present ALL calculations for user verification before proceeding:
For each scenario:
Present calculations in a summary table for user verification. Do not proceed to Step 3 until user confirms all calculations.
Generate body sections in order (Sections 1–12):
Each scenario in Section 6 follows this worksheet format (per CCPS Tables 8.3/8.4):
SCENARIO [number]: [title]
═══════════════════════════════════════════════════════════
Scenario Number: [ID]
Equipment Number: [tag]
Scenario Title: [description]
Date: [date]
Consequence Description: [description of undesired outcome]
Consequence Category: [1–5 per Table 3.1]
Risk Tolerance Criteria: [applicable criteria and threshold]
INITIATING EVENT
Description: [what initiates the scenario]
Frequency: [value] per year Source: [Table 5.1 / plant data]
ENABLING EVENT OR CONDITION
Description: [if applicable] Probability: [value]
CONDITIONAL MODIFIERS (if applicable)
P_ignition: [value]
P_personnel: [value]
P_fatality: [value]
P_other: [value]
FREQUENCY OF UNMITIGATED CONSEQUENCE: [calculated value] per year
INDEPENDENT PROTECTION LAYERS
IPL 1: [description] PFD: [value] Source: [Table 6.x / site data]
IPL 2: [description] PFD: [value] Source: [Table 6.x / site data]
[... additional IPLs]
SAFEGUARDS (non-IPLs — listed but not credited):
- [safeguard 1]: [reason not credited as IPL]
- [safeguard 2]: [reason not credited as IPL]
TOTAL PFD FOR ALL IPLs: [product of PFDs]
FREQUENCY OF MITIGATED CONSEQUENCE: [calculated value] per year
RISK TOLERANCE CRITERIA MET? [Yes/No]
ACTIONS REQUIRED: [if criteria not met]
NOTES: [additional context]
REFERENCES: [PHA, P&ID, PFD refs]
LOPA ANALYST: [name(s)]
Flag these decisions for user review:
npx claudepluginhub teddychenfeiyang-png/safetysure-plugins --plugin safetysure-lopa-suiteAudits chemical laboratory safety for regulatory compliance, hazard control, and emergency preparedness using OSHA and ACS standards.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.