Determine the purpose and triggering conditions for an Emergency Oxygen Supply Connection (EOSC)
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the EOSC's purpose: to allow connection of a temporary auxiliary oxygen source during an emergency, maintenance shutdown, or primary source failure, without interrupting facility oxygen supply
Confirm EOSC is required (per NFPA 99) where the bulk cryogenic liquid central supply system is located outside of and remote from the building it serves, unless there is a connected in-building oxygen reserve sufficient for roughly a day's average supply
Confirm EOSC is also required where multiple freestanding buildings are served from a single bulk oxygen source such that damage to the interconnecting line could cut off supply to one or more buildings
Confirm that a more recent NFPA 99 edition (commonly cited starting with the 2021 edition) requires the EOSC to include a master alarm monitoring connection point — verify this against the edition actually adopted by the AHJ
Confirm EOSC siting coordinates with NFPA 55 bulk oxygen siting rules (e.g., not located over asphalt or similar paving) since the connection is part of the bulk supply system
Known gotchas
EOSC applicability depends on the specific supply configuration (remote bulk source, multi-building distribution) — do not assume every facility with bulk oxygen needs an EOSC if an adequate in-building reserve exists
The master-alarm-monitoring requirement at the EOSC is edition-specific — confirm it applies under the locally adopted NFPA 99 edition before treating it as mandatory
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?