Skip to content

Manage Privacy Options

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Cookie Policy

Always active
Functional Always active

The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.

Your consent ID: not set yet

How to Create an ERP for a Multi-Building Campus

  • July 31, 2026
  • 5 min read

An effective ERP for a multi-building campus must centralize facilities, asset, maintenance, safety permits, chemical inventory, and incident records while preserving building-level control, location traceability, and auditable workflows. For EHS professionals, this is not an administrative preference but a compliance and risk-control imperative: inconsistent permit-to-work procedures, fragmented lockout/tagout (LOTO) records, or missing confined-space documentation across buildings increase the likelihood of regulatory citations (OSHA, NFPA, EPA) and can magnify the human and financial costs of incidents — from costly lost-time injuries and remediation to multi‑jurisdictional fines and potential shutdowns. The complexity of coordinating contractors, shift changes, and building-specific hazards makes centralized, accurate data essential to demonstrate due diligence and to drive timely corrective actions.

Managing these requirements across dozens or hundreds of structures introduces operational friction — paper forms, disparate spreadsheets, and siloed systems lead to delayed incident response, incomplete corrective action closure, and weak audit trails. Enterprise EHS software that consolidates inspections, LOTO and permit workflows, incident tracking, corrective action management, job hazard analyses, asset and chemical inventories, and audit reporting is therefore the practical approach to scaling compliance and safety across a campus. Simple But Needed (SBN) provides an integrated platform to unify those functions, enabling consistent procedures, auditable records, and faster corrective-action cycles across multiple buildings.

 

 

How to perform a building-by-building hazard identification and risk assessment including shared systems and interdependencies

Start with a documented baseline walkdown for each building tied to a standard scope: structural envelope, mechanical spaces, electrical rooms, finished spaces, loading docks, roof equipment, and subterranean interconnections. Use a consistent asset checklist and tag each asset by building/room/ID; inspect teams should carry the building’s SDS-based chemical inventory and permit lists during the walkdown. Regulatory cross-checks must include OSHA 29 CFR 1910.1200 (Hazard Communication) for chemical hazards, 29 CFR 1910.119 (Process Safety Management) where covered processes or threshold quantities exist, and 29 CFR 1910.146 for confined spaces. Establish the baseline within a defined timeframe—complete initial campus-wide walkdowns and inventories within 90 days, then update building files after any change-in-use, renovation, or chemical/process change that affects hazard profiles.

Quantify risks using tiered methods: task-level JHA/JSA for routine operations, HAZOP/PSM reviews for process areas covered by 1910.119, and FMEA/LOPA for systems with cascading potential. For each identified hazard document consequence metrics (injuries, fatalities, property damage in $K, downtime in hours) and likelihood (events/year). Use a scoring matrix to prioritize actions; for example, treat any condition with potential for multiple fatalities or >24-hour operational downtime as a top-tier priority requiring engineered controls within 180 days. Explicitly identify single points of failure — a single 480V main feeder, a single-fire-pump serving multiple buildings, or a Building Management System (BMS) on one network segment — and require redundancy or compensating administrative controls where elimination is not feasible.

Map shared systems and interdependencies at the campus level before integrating building-level controls. Produce one-line electrical diagrams showing utility feeds, automatic transfer switches, generator kW ratings and run-time fuel capacity; annotate chilled water/steam loops, fire-water zone boundaries, primary/secondary transformers and HVAC economizer dependencies. Model cascading failure scenarios (e.g., utility loss → elevator outage → inability to evacuate non-ambulatory occupants) with simple event trees and document required mitigation timelines — e.g., temporary generator installed and tested within 10 business days for critical life-safety systems, permanent remediation within 90 days. Where life-safety systems span buildings, verify compliance with the appropriate testing cadence (weekly/monthly/annual) and retention of test records to satisfy inspectors and AHJs.

Simple But Needed (SBN) operationalizes building-by-building HIRA through specific modules: use the Inspections module to schedule and record standardized walkdowns per building (90‑day baseline, then event-driven updates), the Chemical Inventory module to store SDSs and quantify stock by building against PSM/EPCRA thresholds, and the JHA/confined space modules to capture task-level controls identified during assessments. Link findings to Incident Tracking so past events auto-populate risk history for the same building or asset, and create CAPA items with owners, due dates, and verification evidence to enforce remediation timelines (e.g., 10-business-day temporary fixes, 90-day permanent fixes). Dashboards and exportable risk matrices let EHS leaders demonstrate compliance with 29 CFR requirements and show status by building at audit time.

 

How to design a unified mass notification and incident communication system across disparate buildings and networks

Design begins with regulatory and performance requirements. OSHA’s Emergency Action Plan rule (29 CFR 1910.38) and the OSHA employee alarm systems regulation (29 CFR 1910.165) require employers to establish and communicate emergency procedures and maintain alarm systems; NFPA 72 (National Fire Alarm and Signaling Code) provides the performance framework for emergency communications (audibility, survivability, supervision). For a multi‑building campus you must translate those requirements into measurable service-level objectives (SLOs) — for example, voice or text delivery to primary devices for 95% of occupants within 60–120 seconds for life‑safety alerts, and documented training/testing programs tied to the campus EAP. Specifying these SLOs up front lets you select technologies and acceptance tests that meet OSHA/NFPA expectations rather than relying on vendor marketing claims.

Architecturally, a unified system uses multiple delivery layers (primary wired voice paging, IP-based voice evacuation, SMS and MMS, push notifications, desktop pop-ups, building digital signage and strobes) with shared back-end control via a Common Alerting Protocol (CAP)-capable gateway. On the network side, implement VLAN segmentation for critical audio/video streams, DiffServ QoS markings to prioritize SIP/RTP traffic, and multicast where appropriate to reduce WAN load for simultaneous voice paging. Provide at least N+1 redundancy for core servers and dual SIP trunks (primary and PSTN fallback) and locate redundant servers in separate buildings or data centers to survive a single-building loss. Integrate with building automation systems (BACnet or OPC) so life‑safety triggers (sprinkler, smoke detectors, HVAC shutdown) can auto-activate message paths, and ensure battery-backed power/UPS and generator survivability for controllers and edge amplifiers per the electrical survivability risks you document.

Operationally, codify message governance and verification workflows in the ERP: pre-approved message templates for fire, severe weather, active assailant, chemical release and utility failure; a four-tier incident classification with time-to-notify SLAs (Tier 1 — immediate life-safety: notify <2 minutes and auto-override verification; Tier 2 — imminent threat: notify <15 minutes; Tier 3 — localized advisory: notify <60 minutes; Tier 4 — informational); and a verification requirement that non-life-safety alerts require two independent confirmations within 2–5 minutes to reduce false alarms. Testing and maintenance schedules must be explicit: automated health checks every 5–10 minutes, building-level voice paging tests monthly, subsystem (SIP trunk, CAP gateway) failover tests quarterly, and an annual full-campus notification exercise. Retain detailed logs (message content, originator identity, approval chain, per-device delivery timestamps and failures) to satisfy OSHA 1910.38 training/documentation expectations and to support after‑action reviews under ICS/NIMS principles. Simple But Needed (SBN) operationalizes the above by tying tests, events and corrective work into one EHS workflow. Use SBN Inspections to schedule and record the weekly automated health checks and monthly building paging tests (device‑level pass/fail, GPS/photo evidence, and automated timestamping); SBN Incident Tracking captures the alert originator, approval chain, exact message content, and per-recipient delivery timestamps so you can validate your 95%/120s SLOs and produce audit-ready logs for OSHA/NFPA reviews. When a device or path fails, SBN automatically opens a CAPA with priority based on your incident tier, assigns technicians, and links corrective actions to subsequent inspections so outages remain tracked until verification. The SBN Audits module produces consolidated compliance reports (test frequency, drill attendance, delivery metrics) to demonstrate alignment with 29 CFR 1910.38/1910.165 and your internal ERP standards.

 

 

How to coordinate ERP roles, mutual aid agreements, and ICS/NIMS integration with local emergency responders and contractors

ERP role definition for a multi-building campus must mirror NIMS/ICS span-of-control principles: assign an Incident Commander (IC) and at minimum Operations, Planning, Logistics, Finance/Admin, Safety Officer, Liaison Officer, and Public Information Officer roles as described in NIMS/ICS doctrine. For campuses with 5+ buildings or over 100,000 ft² total footprint, designate building-level Incident Coordinators who report to a campus IC to maintain a 1:3–1:7 supervisor-to-subordinate ratio under strong and verifiable span-of-control. Require qualified personnel to complete ICS-100 and ICS-200 within 90 days of assignment and ICS-300/400 or equivalent for command-level staff within 12 months, and document completion using course numbers (ICS-100, ICS-200, ICS-300, ICS-400, IS-700, IS-800) consistent with FEMA guidance.

Mutual aid agreements and MOUs must be typed and version-controlled, specifying minimum deliverables such as resource type (e.g., Type 3 structural suppression, hazardous materials team), guaranteed response time windows (e.g., engine response within 8 minutes urban / 20 minutes mutual aid), liability and indemnification language, workers’ compensation arrangements, reimbursement rates or reference to state EMAC terms, and expiration/review cadence. Align agreements to NFPA 1600 program elements and OSHA 1910.38 (Emergency Action Plans) expectations, and schedule contractual reviews at least annually with tabletop validation every 12 months plus full-scale interoperable exercises at minimum every 3 years to validate response time commitments and resource typing.

On-scene integration with local emergency responders and contractors requires pre-incident coordination of access, staging, and credentialing: map primary and secondary access gates, mark fire lanes to a minimum clear width of 20 feet, and identify hydrant locations with typical spacing metrics (hydrants within 250–350 ft of facility entrances per common municipal codes). Require contractors performing hot work, confined space entry, or energized work to provide proof of training (HAZWOPER 24/40-hour where applicable under 29 CFR 1910.120, and confined space rescue qualifications under 29 CFR 1910.146) and to be added to a pre-approved roster with badge access linked to permit-to-work issuance. Use Unified Command protocols and pre-assigned Liaison Officers during multi-jurisdictional incidents to ensure single point of contact for agencies and contractors, and maintain an on-call contact list with 24/7 phone and minimum 15-minute callback expectations documented in the ERP.

Simple But Needed (SBN) supports operationalizing these coordination requirements by providing an incident tracking module that timestamps ICS activations, captures assigned roles (IC, Safety Officer, Liaison), logs resource typing and arrival times, and links to specific MOUs; an audits module to schedule and record annual MOU reviews and exercise outcomes with version control and sign-offs; a CAPA/workorder feature that converts exercise findings into assigned corrective actions with owners, due dates, and verification checklists; and confined space and chemical inventory modules that store contractor qualifications, permit histories, rescue plans, and mapped SDS locations tied to floorplan GIS layers for responder pre-planning.

 

5. How to develop training, drills, recordkeeping, and performance metrics to validate and maintain the campus ERP

Design the training matrix to meet and document the specific regulatory thresholds that apply across a multi‑building campus: comply with OSHA 29 CFR 1910.38 for Emergency Action Plans (EAP) by designating and training employees to perform evacuation and other emergency duties, and with 29 CFR 1910.120 (HAZWOPER) where employees will engage in hazardous‑substance emergency response (initial training hours vary by duty — commonly 24–40 hours for hands‑on responders, with an 8‑hour annual refresher for many responder roles). Assign role‑based curricula (floor wardens, shelter‑in‑place coordinators, building systems operators, communications operators, and search teams) with minimum competencies (alarm initiation recognition, ICS position checklists, stairwell management, radio proficiency) and document refresher cadence — at least annual for most roles and more frequent (quarterly) for high‑risk or high‑turnover positions. Capture training completion dates, lesson plans, instructor qualifications, and assessment scores in a single audit‑ready repository so that proof of compliant training (HAZWOPER, EAP role briefs, respirator fit testing per 29 CFR 1910.134 where applicable) is available for each employee and each building assignment; SBN’s CAPA and training audit features centralize gaps, link required refreshers to specific buildings, and track corrective actions to completion.

Structure drills and exercises to validate both building‑level procedures and campus interdependencies through a graduated program: conduct tabletop exercises annually to validate communications, mutual‑aid triggers, and ICS interfaces; run functional exercises (communications, mass notification, and accountability systems) semiannually for clusters of interconnected buildings; and perform at least one full‑scale evacuation or multi‑agency exercise every 1–3 years for the largest or highest‑hazard sites. For each exercise define measurable objectives — e.g., alarm‑to‑evacuation‑start time, total clearance time, accountability reconciliation time, and ICS activation time — and instrument them: use synchronized time stamps (±1 second) from loggers, radio recordings, and entry/exit scans to produce defensible metrics. Record notification latency targets (for example, end‑to‑end mass notification within 120 seconds for critical alerts) and establish a post‑exercise AAR with assigned corrective actions and owners; SBN’s inspections and drill checklist modules schedule exercises, log the timed measurements, and keep the AAR items linked to subsequent inspection rounds.

Maintain recordkeeping practices that satisfy OSHA retention rules and make records easily retrievable during reviews and post‑incident analysis: retain OSHA 300/300A/301 logs and related documentation for five years as required by 29 CFR 1904.33, and preserve HAZWOPER training and qualification records (per 29 CFR 1910.120) for the duration specified by the program and by site policy; maintain exposure and medical records consistent with 29 CFR 1910.1020 access/retention expectations. Use standardized, timestamped drill logs (including participant rosters with employee IDs, building QR scan times, and mass notification delivery receipts) and link them to incident reports and equipment maintenance records so deficiencies in alarms, PA systems, or stairwell lighting are clearly attributable to a cause. SBN’s audits and incident‑tracking capabilities consolidate training certificates, drill logs, and equipment maintenance into one searchable record set and automatically link the resulting findings to CAPA items and closure evidence.

Define a concise set of KPIs that drive continuous improvement and are practical to measure across multiple buildings: sample KPIs include drill participation rate (target ≥95% of assigned occupants per drill), first‑alarm‑to‑assembled‑headcount time (establish baseline from three drills and then set a goal to reduce baseline by ≥10% within 12 months), accountability reconciliation accuracy (target ≥99% match against payroll/occupant lists), average corrective‑action closure time (target ≤30 days for priority items), and mass‑notification delivery success rate (target ≥99% within the campus network). Schedule an annual formal review of the ERP and after any significant change in occupancy, building use, or life‑safety systems; use trend charts to spot degradation (for example, steady increase in evacuation times or repeated failures in the same stair core) and convert those trends into CAPAs with measurable verification steps. SBN’s combined incident‑tracking and CAPA dashboards enable rolling KPI calculations, trend visualization by building or system, and verification evidence attachment so safety teams can quantitatively demonstrate ERP validation and sustained performance.

 

 

Frequently Asked Questions

 

How do I centralize permit‑to‑work and LOTO records across multiple buildings to be audit‑ready for OSHA?

Centralize permit‑to‑work and lockout/tagout records by tagging each permit and LOTO event to building/asset IDs, retaining annually audited histories and certifications (LOTO training per 29 CFR 1910.147(c)(7) and annual procedure inspections per 1910.147(g)(3)(i)). Use a single ERP that enforces electronic permit workflows, required attachments (SDS or isolation diagrams), and role‑based approvals so each entry is auditable by building and by asset. SBN’s Permit/LOTO and Incident Tracking modules provide building/asset tagging, approval chains, training links, and time‑stamped audit trails while CAPA ties incomplete permits or failures to corrective work and verification evidence.

What are the required retention periods for OSHA injury logs, drill records, and HAZWOPER training across a campus?

Maintain OSHA 300/300A/301 logs and related documentation for five years as required by 29 CFR 1904.33; retain drill after‑action reports, timed notification logs, and exercise rosters for at least the same five‑year window to demonstrate trends and corrective actions to AHJs. HAZWOPER and other responder training/qualification records should be kept per the specific standard (29 CFR 1910.120) and site policy—typically for the duration specified by the program or employment—and respirator/fit‑test records per 29 CFR 1910.134. SBN’s Audits, Training and Incident Tracking modules centralize and timestamp OSHA logs, drill evidence, and training certificates for searchable, audit‑ready retention and automated retention scheduling.

How should I conduct building‑by‑building confined‑space assessments to comply with 29 CFR 1910.146?

Perform documented baseline confined‑space walkdowns for each building within your 90‑day campus baseline, identify permit‑required spaces, atmospheric hazards, and rescue capabilities, and require written entry permits and attendant/entrant training per 29 CFR 1910.146. Update assessments after any change‑in‑use or equipment change and link each permit and rescue plan to the specific building/space and responsible rescue resources. SBN’s Confined Space and Inspections modules store space inventories, entry permits, training proof, rescue plans, and permit histories tied to floorplan/GIS locations and auto‑generate CAPAs for any assessment findings.

How do I validate mass notification performance to meet OSHA/NFPA SLOs across disparate buildings and networks?

Set measurable SLOs consistent with OSHA 29 CFR 1910.38/1910.165 and NFPA 72 (for example, deliver life‑safety alerts to ≥95% of occupants within 60–120 seconds) and validate them with instrumented tests: automated health checks (every 5–10 minutes), monthly building paging tests, quarterly subsystem failover tests and an annual full‑campus exercise. Capture per‑recipient delivery timestamps, device failures, and verification chains during tests to produce audit‑ready evidence and link outages to corrective actions. SBN’s Inspections schedule tests and record device‑level pass/fail with GPS/photo evidence while Incident Tracking logs message content and per‑recipient timestamps and CAPA routes failed paths to technicians for resolution.

What KPIs should I report to demonstrate ERP effectiveness to AHJs and leadership, and how do I measure them?

Report practical, auditable KPIs such as drill participation rate (target ≥95%), first‑alarm‑to‑assembled‑headcount time (use a three‑drill baseline and aim to reduce baseline by ≥10% in 12 months), accountability reconciliation accuracy (target ≥99%), average corrective‑action closure time (target ≤30 days for priority items), and mass‑notification success (target ≥99% within SLAs). Measure these with synchronized timestamps, entry/exit scans, and automated delivery receipts, convert trends into CAPAs, and include assigned owners and verification evidence for executive and AHJ review. SBN’s Dashboards, Incident Tracking and CAPA modules compute rolling KPIs, visualize trends by building or system, and attach verification artifacts for audit and management reporting.

 

Simple But Needed (SBN) is a global EHS platform that provides industries such as Oil & Gas, Insurance, Government and Public Entities, Utilities, Pharma and Biotech Laboratories, Education, Manufacturing, Food and Beverage, Healthcare and Construction with a simple yet powerful tool to manage all of their EHS needs. We handle Inspections, LOTO procedures, complex Chemical Asset Inventory, Ergonomics, JHAs, Safety Walkthroughs, Asset Inventory, Confined Space, Fire and General Safety, Toolbox Talks, Training and Certification tracking, CAPA, Near Miss and Incident Management, Epermitting, Safety Observations, Compliance and more. We offer sophisticated dashboarding and reporting capabilities with the push of a button.

 

See why teams choose SBN

Inspections, corrective actions, audits and compliance — made simple, easy and effective. Start a free trial and see it in your own workflow.

Start your free trial