Study guide
13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces
NENA Emergency Number Professional ENP
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the NENA ENP Exam
2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture
1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1
3 Chapter 2: Modern Location Technologies & MLTS
2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act
4 Chapter 3: NG911 i3 Core Network & Security
3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow
5 Chapter 4: NG911 Location Services & Call Routing
4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements
6 Chapter 5: Public Safety Radio, Broadband & FirstNet
5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services
7 Chapter 6: Call Processing, Accessibility & Protocol Systems
6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment
8 Chapter 7: Computer Aided Dispatch & Information Systems
7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents
9 Chapter 8: GIS for Next Generation 9-1-1
8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management
10 Chapter 9: Cybersecurity & CJIS Compliance
9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning
11 Chapter 10: Telecommunications Policy, Funding & Civil Rights
10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws
12 Chapter 11: PSAP Governance, Strategy & Facility Design
11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning
13 Chapter 12: Power Redundancy, COOP & Disaster Recovery
12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases
14 Chapter 13: Emergency Incident Management & NIMS/ICS
13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS
15 Chapter 14: Procurement, Contracts & Financial Management
14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management
16 Chapter 15: Staffing Models, Scheduling & Wellness
15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD
17 Chapter 16: Training, CTO Coaching & Quality Assurance
16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service
18 Chapter 17: Employee Relations, Labor Standards & Legal Protections
17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act
19 Chapter 18: Records Governance, Liability & Public Relations
18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach
20 Chapter 19: Recruiting, Hiring, Compensation & Retention
19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning
13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces
Key Takeaways Explain This Topic AI
A strict operational division of labor separates the PSAP from the Emergency Operations Center (EOC): the PSAP operates at the tactical level (real-time 9-1-1 intake, unit dispatching, safety timers, seconds-to-minutes horizon), while the EOC operates at the strategic level (macro resource allocation, policy resolution, disaster declarations, 12- to 24-hour operational periods).
EOCs scale through three activation tiers (Level 3 Steady State, Level 2 Enhanced/Partial, Level 1 Full Activation) and operate under ICS-like, Incident Support Model (ISM), or Departmental organizational structures.
Department Operations Centers (DOCs) coordinate internal agency resources (such as police, fire, or public works DOCs), acting as the vital operational buffer between field command/PSAP and the jurisdictional EOC.
The Joint Information System (JIS) and physical Joint Information Center (JIC) coordinate public messaging across participating agencies to speak with 'one voice', manage rumor control, and relieve PSAPs of overwhelming non-emergency citizen inquiry call volume.
The PSAP enforces on-scene responder safety through benchmark safety timers (Personnel Accountability Report [PAR] checks at intervals set by agency SOG, commonly 10 to 20 minutes), structured CAN reports (Conditions, Actions, Needs), and rigorous Mayday / Emergency Traffic protocols.
Last updated: September 2026
13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces
Quick Answer: The fundamental divide in emergency management separates on-scene tactical operations from strategic multi-agency coordination. The Public Safety Answering Point (PSAP) operates strictly at the tactical level —processing incoming 9-1-1 calls, interrogating callers, dispatching apparatus, tracking field units, and enforcing responder safety timers in real time (seconds to minutes). The Emergency Operations Center (EOC) operates at the strategic level —managing macro resource allocation, procuring scarce supplies, resolving interagency policy disputes, issuing disaster declarations, and planning across 12- to 24-hour operational periods. EOCs deploy three activation tiers (Level 3 Normal, Level 2 Enhanced/Partial, Level 1 Full) across three core organizational models (ICS-like, Incident Support Model, or Departmental). Critical coordination interfaces include Department Operations Centers (DOCs), the Joint Information System/Center (JIS/JIC) for unified public messaging, and PSAP tactical safety protocols (Personnel Accountability Reports / PAR checks, CAN reports, and Mayday channel-clearing procedures).
1. Tactical vs. Strategic: The PSAP and EOC Division of Labor
A critical failure mode during major disasters occurs when public safety leaders blur the operational boundary between the Public Safety Answering Point (PSAP) / Emergency Communications Center (ECC) and the Emergency Operations Center (EOC). When an EOC attempts to direct tactical field units or when a PSAP attempts to negotiate regional fuel contracts and disaster declarations, operations collapse into gridlock. ┌─────────────────────────────────────────────────────────────────────────────┐
- │ TACTICAL LEVEL (PSAP / ECC & ON-SCENE ICP) │
- │ • Immediate Life Safety & Incident Response (Seconds to Minutes) │
- │ • 9-1-1 Call Intake, Geolocation, and CAD Data Enrichment │
- │ • Unit Dispatching, Run Card Automation, and Staging Instructions │
- │ • Tactical Channel Assignment, Status Tracking & Safety Timers (PAR) │
- └──────────────────────────────────────┬──────────────────────────────────────┘
- │ (Resource Requests & Situational Awareness)
- ▼
- ┌─────────────────────────────────────────────────────────────────────────────┐
- │ STRATEGIC LEVEL (EMERGENCY OPERATIONS CENTER / EOC) │
- │ • Macro Resource Acquisition & Prioritization (12- to 24-Hour Windows) │
- │ • Multi-Agency Policy Resolution & Emergency Legal Declarations │
- │ • Infrastructure Restoration, Public Mass Care, Sheltering & Evacuation │
- │ • State / Federal Mutual Aid Coordination (EMAC, FEMA Interface) │
- └─────────────────────────────────────────────────────────────────────────────┘
- Operational Dimension Comparison
Dimension PSAP / Emergency Communications Center Emergency Operations Center (EOC)
Primary Mission Tactical dispatching, field safety tracking, real-time 9-1-1 call intake. Strategic coordination, high-level policy, macro resource allocation, disaster recovery.
Operational Horizon Real-time: seconds, minutes, hours. Strategic periods: 12- to 24-hour operational planning blocks; multi-day recovery.
Command Level Tactical command support to on-scene Incident Commander. Strategic support to community leadership and Multiagency Coordination (MAC) Groups.
Resource Authority Dispatches local apparatus based on established CAD run cards and SOPs. Procures scarce regional mutual aid, contracts commercial cranes, allocates bulk fuel.
Primary Communications LMR tactical talkgroups, CAD consoles, 9-1-1 telephone systems, P25 radio. WebEOC, GIS mapping, multi-agency video conferences, crisis management portals.
Public Interface Emergency 9-1-1 callers, Text-to-911, and field emergency responders. Media press briefings, Joint Information Center (JIC), citizen 3-1-1 info lines.
2. Standardized EOC Activation Levels
Under modern emergency management standards (NIMS and FEMA guidance), EOC operations scale across three standardized activation levels. Note that many jurisdictions number activation levels from 3 (lowest) to 1 (highest), matching federal standards: ┌─────────────────────────────────────────────────────────────────────────────┐
- │ EOC ACTIVATION HIERARCHY │
- ├──────────────────────────┬──────────────────────────────────────────────────┤
- │ LEVEL 1: FULL ACTIVATION │ • Catastrophic disaster, widespread destruction │
- │ (Highest Severity) │ • All Emergency Support Functions (ESFs) active │
- │ │ • 24/7 continuous multi-agency operations │
- ├──────────────────────────┼──────────────────────────────────────────────────┤
- │ LEVEL 2: ENHANCED / │ • Specific impending threat or major event │
- │ PARTIAL ACTIVATION │ • Designated lead agencies & key ESFs active │
- │ (Moderate Severity) │ • Extended monitoring and preparatory logistics │
- ├──────────────────────────┼──────────────────────────────────────────────────┤
- │ LEVEL 3: NORMAL / │ • Day-to-day steady state monitoring │
- │ STEADY STATE │ • Routine watch officer / EM duty staff │
- │ (Baseline Operations) │ • Daily situational tracking and readiness checks│
- └──────────────────────────┴──────────────────────────────────────────────────┘
Level 3: Normal Operations / Steady State: The routine baseline condition. The EOC facility is maintained in readiness; day-to-day operations are handled by standard emergency management staff and the 24/7 PSAP watch floor. Activities include tracking routine weather advisories, reviewing plans, and participating in scheduled training exercises.
Level 2: Enhanced Operations / Partial Activation: Initiated when a specific threat, severe hazard, or major planned event develops (e.g., a Category 2 hurricane approaching within 48 hours, a major winter storm warning, or a National Special Security Event like a presidential visit). Emergency management leadership activates designated lead agency representatives and specific Emergency Support Functions (ESFs) (such as Transportation, Public Works, and Public Safety) to coordinate specialized logistics and preposition resources.
Level 1: Full Activation: Initiated during catastrophic emergencies resulting in widespread community impact, mass casualties, severe infrastructure loss, or multi-jurisdictional disasters (e.g., major earthquake, tornado strike, massive chemical explosion, catastrophic flooding). All EOC staffing positions, agency liaisons, and all Emergency Support Functions (ESFs 1 through 15) are activated for continuous 24/7 round-the-clock operations .
3. EOC Organizational Models
NIMS identifies three primary organizational structures that jurisdictions may utilize to staff and organize an Emergency Operations Center, depending on administrative preference and statutory authority: ┌─────────────────────────────────────────────────────────────────────────────┐
- │ EOC ORGANIZATIONAL STRUCTURE MODELS │
- ├───────────────────────┬───────────────────────────┬─────────────────────────┤
- │ 1. ICS-LIKE MODEL │ 2. INCIDENT SUPPORT MODEL │ 3. DEPARTMENTAL MODEL │
- ├───────────────────────┼───────────────────────────┼─────────────────────────┤
- │ • Mirrors field ICS │ • Aligns EOC structure │ • Organizes EOC by │
- │ organization: │ with its core mission: │ existing municipal │
- │ - EOC Director │ supporting the field. │ departments: │
- │ - Operations Section│ • EOC Director │ - Police Department │
- │ - Planning Section │ • Situational Awareness │ - Fire Department │
- │ - Logistics Section │ • Planning Support │ - Public Works │
- │ - Finance / Admin │ • Resource Support │ - Health & Human Serv │
- │ • Familiar to field │ • Center Support │ • Minimizes training for│
- │ responders. │ • Prevents field microman-│ department heads, but │
- │ • Risk: blurring with │ agement. │ can perpetuate silos. │
- │ tactical operations.│ │ │
- └───────────────────────┴───────────────────────────┴─────────────────────────┘
ICS or ICS-Like Structure: Organizes the EOC using the familiar Command, Operations, Planning, Logistics, and Finance/Administration sections. While this model provides organizational familiarity for emergency responders, it carries the operational risk of EOC personnel attempting to micromanage tactical field operations under the guise of an 'Operations Section.'
Incident Support Model (ISM): Specifically restructures the EOC to reflect its true support role, eliminating the tactical Operations Section entirely. Instead, the ISM organizes personnel into: Situational Awareness Section (collecting and analyzing intelligence), Planning Support Section (long-term strategic action planning), Resource Support Section (sourcing and delivering scarce mutual aid and commercial contracts), and Center Support Section (internal EOC IT, facilities, and communications).
Departmental / Department-Based Structure: Organizes the EOC around existing municipal and county government departments (e.g., Police, Fire/Rescue, Public Works, Transportation, Public Health, Social Services). Department directors manage their agency's assets directly from the EOC. This structure leverages existing daily working relationships, but can struggle with inter-departmental silos during unprecedented multi-agency disasters.
4. Department Operations Centers (DOC)
A Department Operations Center (DOC) is an agency-specific coordination center that manages internal department resources, facilities, and personnel during an emergency:
Examples: A Police DOC manages law enforcement precinct shifts, prisoner transport logistics, and perimeter cordons; a Public Works DOC manages heavy earthmovers, snowplows, barricades, and water main repair crews.
Operational Bridge: The DOC sits organizationally between frontline field units/command posts and the multi-agency EOC. When an Incident Commander needs 10 dump trucks for levee fortification, the request flows from the on-scene ICP to the PSAP or directly to the Public Works DOC. If the Public Works DOC exhausts municipal equipment, it escalates the request to the central EOC for regional or commercial mutual aid.
Preventing EOC Overload: By resolving single-discipline tactical problems internally, DOCs protect the central EOC from being flooded with routine departmental administrative tasks.
5. Joint Information System (JIS) & Joint Information Center (JIC)
During a crisis, public misinformation, social media rumors, and conflicting statements from different agency spokespersons can cause panic and endanger lives. NIMS establishes the Joint Information System (JIS) to unify crisis communications across all participating jurisdictions. [Jurisdiction A PIO (Police)] [Jurisdiction B PIO (Fire)] [Public Health PIO]
- │ │ │
- └─────────────────────────┼─────────────────────────┘
- ▼
- ┌────────────────────────────────────┐
- │ JOINT INFORMATION CENTER (JIC) │
- │ • Single, Co-Located Media Center │
- │ • Unified Messaging ('One Voice') │
- │ • Rumor Control & Social Media │
- │ • Public Inquiry Hotlines (3-1-1) │
- └──────────────────┬─────────────────┘
- │
- ┌───────────────────────┴───────────────────────┐
- ▼ ▼
- [Coordinated Press Briefings] [PSAP Call Load Shedding]
- (Authoritative emergency info) (Citizens directed to 3-1-1;
- 9-1-1 lines protected for life safety)
Core Elements of the JIS / JIC Framework:
Joint Information System (JIS): The operational framework, policies, and processes used to integrate public information activities across multiple agencies and levels of government.
Joint Information Center (JIC): The physical or virtual location where Public Information Officers (PIOs) gather to collaborate, draft joint news releases, prepare elected officials for press conferences, and monitor news media and social channels.
The 'One Voice' Doctrine: Ensures that all releasing authorities disseminate verified, consistent, and synchronized public safety directives (e.g., evacuation routes, boil-water notices, shelter locations), eliminating contradictory messages.
PSAP Integration & Call Load Shedding: A primary failure in disaster management is anxious citizens flooding 9-1-1 lines seeking non-emergency information (e.g., 'What time does the power come back on?' or 'Which roads are flooded?'). The JIC actively protects the PSAP by advertising non-emergency public inquiry channels (such as 3-1-1 , 2-1-1, or dedicated toll-free disaster hotlines) across news broadcasts and social media, shedding non-critical calls from the 9-1-1 emergency trunk lines.
6. PSAP Tactical Safety Management: Bench Timers & PAR Checks
Inside the Emergency Communications Center, telecommunicators enforce on-scene personnel accountability through automated safety timers built into the Computer-Aided Dispatch (CAD) system.
Benchmark Safety Timers & PAR Protocols
Safety Timer (Bench Timer): CAD automatically initializes an elapsed timer upon dispatch or arrival of tactical units. At intervals set by agency Standard Operating Guidelines (commonly 10 to 20 minutes ), the CAD system generates an audible and visual prompt alerting the dispatcher to initiate an accountability check.
Personnel Accountability Report (PAR): A timed, structured roll call conducted over the tactical radio talkgroup. The telecommunicator broadcasts the PAR prompt (e.g., 'Dispatch to Main Street Command, you are at your 20-minute incident benchmark; confirm PAR').
Command Execution: The Incident Commander or Operations Section Chief polls Division and Group supervisors (e.g., 'Division Alpha PAR', 'Roof Group PAR'). Supervisors visually verify that all assigned crew members are present, accounted for, and physiologically stable before transmitting a positive PAR confirmation.
Operational Triggers for Immediate Unscheduled PAR Checks:
Transitioning from an offensive interior fire attack to a defensive exterior posture.
Sudden structural collapse, flashover, or backdraft.
Transmission of a firefighter Mayday or police officer distress activation.
Identification of an uncontrolled hazardous materials breach or explosion.
7. CAN Reports: Standardizing Situational Telemetry
To ensure rapid, unambiguous status reporting over congested tactical radio channels, public safety operations utilize the standardized CAN Report format: ┌─────────────────────────────────────────────────────────────────────────────┐
- │ THE CAN REPORT FORMAT │
- ├──────────────────────────┬──────────────────────────────────────────────────┤
- │ C: CONDITIONS │ What does the unit see, encounter, or face? │
- │ │ (e.g., 'Heavy fire and zero visibility on floor 2│
- │ │ with partial ceiling drywall failure.') │
- ├──────────────────────────┼──────────────────────────────────────────────────┤
- │ A: ACTIONS │ What tactical operation is the crew performing? │
- │ │ (e.g., 'Advancing 1.75-inch hose line to bedroom │
- │ │ Alpha; conducting primary search.') │
- ├──────────────────────────┼──────────────────────────────────────────────────┤
- │ N: NEEDS │ What additional resources are required? │
- │ │ (e.g., 'Need second hose line to cover stairwell │
- │ │ and ventilation opened on Side Charlie.') │
- └──────────────────────────┴──────────────────────────────────────────────────┘
Telecommunicators must be trained to parse CAN transmissions rapidly, logging conditions and tactical milestones into the CAD incident narrative and alerting the Incident Commander to unmet resource needs.
8. Mayday and Emergency Traffic Protocols for Telecommunicators
The ultimate tactical emergency occurs when a responder transmits a Mayday (fire/rescue) or Officer Distress / 10-33 / Signal 13 (law enforcement). Telecommunicators bear direct legal and operational responsibility for executing immediate life-safety radio protocols: [Responder Transmits MAYDAY or Activates Radio Distress Button (EMER BUTTON)]
- │
- ▼
- ┌───────────────────────────────────────────────────────────────────┐
- │ PSAP IMMEDIATE ACTION SEQUENCE │
- │ 1. Transmit Distinctive Alert Tone over Tactical Talkgroup │
- │ 2. Broadcast 'EMERGENCY TRAFFIC ONLY - CLEAR THE TALKGROUP' │
- │ 3. Acknowledge the Mayday Unit; Capture LUNAR / CAN Data │
- │ 4. Alert on-scene Command & Dispatch Rapid Intervention Team (RIT)│
- │ 5. Open Secondary Channel for Ongoing Non-Mayday Fire Operations │
- └───────────────────────────────────────────────────────────────────┘
The LUNAR Protocol for Mayday Information Gathering:
When a distressed responder transmits a Mayday, the telecommunicator or on-scene commander extracts vital information using the LUNAR mnemonic:
L — Location: Where is the responder trapped or injured? (e.g., 'Second floor, northwest corner, Division Alpha').
U — Unit: Apparatus or radio designation (e.g., 'Engine 4 Interior Team').
N — Name: Specific firefighter or officer identity (e.g., 'Firefighter Smith').
A — Air / Assignment: Remaining breathing air bottle pressure and assigned task (e.g., '1,200 PSI remaining; was conducting search').
R — Resources Needed: What specific rescue equipment is needed? (e.g., 'Trapped under heavy ceiling timbers; need jaws and rotary saw').
Channel Discipline During a Mayday:
Standard operating procedures dictate that the trapped responder remains on the primary tactical talkgroup , where they already have established communications. The telecommunicator and command staff order all non-involved working companies to switch their routine operations to a secondary tactical channel, ensuring the downed member's radio channel remains completely unobstructed.
9. Operational Traps & ENP Exam Watch
Tactical vs. Strategic Distinction: Remember: the PSAP is tactical (immediate dispatch, safety timers, unit status), while the EOC is strategic (macro resources, disaster policy, multi-agency coordination across 12- to 24-hour periods). A scenario where an EOC attempts to direct specific fire engines on scene describes a severe operational error.
EOC Activation Levels: Pay close attention to numbering: Level 1 is Full Activation (highest severity) , Level 2 is Enhanced / Partial Activation , and Level 3 is Normal Operations / Steady State .
Safety Timer Intervals: PAR and benchmark timer intervals come from local SOGs (commonly every 10 to 20 minutes on structure fires), not from a single national NENA or NFPA number.
Channel Management During Mayday: The distressed firefighter never switches channels; all non-emergency units clear the channel or migrate to a secondary talkgroup while the downed responder stays on the established tactical channel.