Calculate worst-case toxic and flammable releases using the rule's scenario constraints

Use this document to connect an official requirement or behavior to observable evidence: Calculate worst-case toxic and flammable releases using the rule’s scenario constraints. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official 40 CFR 68.25 — Chemical Accident Prevention Provisions from Environmental Protection Agency via eCFR supports the following bounded statements:

• Under 40 CFR 68, Program 2 and 3 processes must report the flammable worst-case release scenario producing the greatest endpoint distance under section 68.22. The research record locates this support at 40 CFR 68.25(a)(2)(ii), read with 40 CFR 68.25(a)(2) (eCFR anchor p-68.25(a)(2)(ii)).
• Under 40 CFR 68, a Program 1 process must report one worst-case release scenario. The research record locates this support at 40 CFR 68.25(a)(1), read with 40 CFR 68.25(a) (eCFR anchor p-68.25(a)(1)).

The source support ends with the statements listed above. Use them to examine critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Applies only to stationary sources and processes subject to 40 CFR part 68 and the applicable program level. Confirm coverage, regulated substances, process conditions, and current EPA requirements; this is not legal advice or a universal emergency-management standard. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at 40 CFR 68.25(a)(2)(ii), read with 40 CFR 68.25(a)(2) (eCFR anchor p-68.25(a)(2)(ii)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 40 CFR 68.25(a)(1), read with 40 CFR 68.25(a) (eCFR anchor p-68.25(a)(1)), which observable configuration, record, or test can confirm applicability here?
• Which owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?
• What baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders must accompany the source-specific observation?
• Which success, stop, and escalation criteria are written before testing begins?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and sanitize protected material before retention.

Verification and evidence

Build a reproducible chain from 40 CFR 68.25(a)(2)(ii), read with 40 CFR 68.25(a)(2) (eCFR anchor p-68.25(a)(2)(ii)); 40 CFR 68.25(a)(1), read with 40 CFR 68.25(a) (eCFR anchor p-68.25(a)(1)) to the observed environment. Useful domain evidence includes facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions; label every item with scope, timestamp, collector, and stable identifier.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• 40 CFR 68.25 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR