Emergency Dispatch System

Rationale: Integration test at the gateway-to-ACD boundary validates the most critical internal interface in the call processing pipeline. P50/p95/p99 percentile measurement catches latency outliers that average measurements would mask. 150 concurrent sessions represents full system load.

Rationale: Location data accuracy directly determines whether the correct unit is dispatched to the correct address. Testing against known addresses validates the full location pipeline from query to display. Schema completeness check ensures no downstream rendering failures when optional fields are missing from specific location sources.

Rationale: Mixed-media load testing validates that text sessions do not degrade voice call routing under concurrent load. The 20 text plus 100 voice scenario represents a realistic peak ratio. Verifying skill-based routing for text sessions ensures dispatchers with text-handling training receive text calls, as required by ADA compliance.

Rationale: Recording completeness verification is essential because any recording gap creates an evidentiary void. The latency measurement with and without recording tap active validates that the recording system does not degrade live call quality. SIPREC metadata correlation check ensures recordings can be associated with specific incidents for legal discovery.

Rationale: Concurrent incident creation validates that the CAD interface handles peak dispatcher activity without queuing delays. Malformed payload injection validates input sanitization at the workstation-to-CAD boundary, critical because this interface crosses trust domains between call-taking and dispatch subsystems.

Rationale: The SIP Gateway is the single entry point for all emergency calls, making its capacity the system bottleneck. Load testing at full rated capacity for 10 minutes validates sustained performance, not just burst handling. TLS and SRTP failure at any session breaks the security chain mandated by NENA i3.

Rationale: Gateway failover is the highest-risk failure scenario because all active calls traverse this component. Testing three failure modes (process, network, power) ensures the failover mechanism handles different failure signatures. The zero-calls-dropped criterion is absolute because any dropped 911 call during failover could result in a caller being unable to reconnect.

Rationale: Integration test validating IME-to-event-logger interface throughput under peak load. 200 concurrent incidents simulates a major metro disaster scenario. Latency measurement confirms the interface does not bottleneck CAD event persistence.

Rationale: Integration test validating unit tracking data store performance. 2000 units at 5-second intervals represents a large metro PSAP with mutual aid activation. Verifies the shared store handles sustained write throughput without query degradation.

Rationale: Integration test validating dispatch recommendation delivery to dispatcher workstations. 50 concurrent messages simulates peak multi-incident scenario.

Rationale: End-to-end test validating the dispatcher command interface to the incident management engine. Covers the critical dispatch path.

Rationale: Stress test validating CAD event persistence under extreme throughput. 5000 events per minute exceeds normal operations by 10x to verify the database handles surge conditions during major incidents.

Rationale: Performance test validating supervisor dashboard responsiveness under realistic operational load. 500 active incidents and 2000 units represents a major metropolitan emergency scenario.

Rationale: Stress test for radio console to gateway interface at maximum channel capacity. 48 simultaneous channels represents full console utilization. Verifies audio quality is maintained under peak load.

Rationale: Functional test for talkgroup management operations including multi-group patching. These are critical interoperability functions used during multi-agency responses.

Rationale: Interoperability test validating ISSI gateway connections to external P25 systems. Multi-vendor testing is essential because interoperability failures only manifest at system boundaries between different vendor implementations.

Rationale: Endurance test validating radio logging recorder under sustained multi-channel recording. 24 talkgroups over 8 hours simulates a full operational shift. 100% capture rate is required because missed recordings have legal and evidentiary consequences.

Rationale: Security test validating Over-The-Air Rekeying of subscriber radios. OTAR is critical for key compromise recovery — if rekeying fails, compromised encryption keys remain in use across the fleet.

Rationale: Integration test validating automated talkgroup assignment from CAD dispatch. This interface determines which radio channel a responding unit monitors — incorrect assignment means the unit cannot communicate with the incident commander.

Rationale: Failover test for radio gateway — verifies that voice communications survive hardware failure. This is a life-safety test: if the radio gateway fails without automatic recovery, field units lose voice communication with dispatch.

Rationale: Performance test for routing engine throughput. 100 concurrent route requests validates that the dispatch decision support module can compute optimal unit assignments for multiple simultaneous incidents.

Rationale: Load test for map tile serving under realistic multi-dispatcher usage. 24 workstations with simultaneous pan/zoom represents peak shift operations. Verifies map rendering remains responsive during high-activity periods.

Rationale: Accuracy test for geocoding engine using realistic ALI data quality. Raw ALI address strings with misspellings and abbreviations represent actual field conditions. MSAG validation ensures dispatch to valid response zones.

Rationale: Hardware interface test validating MDT-to-LTE module connectivity. USB 3.0 throughput test confirms the physical interface supports concurrent voice and data streams without bandwidth contention.

Rationale: Scale test for mobile data gateway under full fleet connectivity. 200 concurrent WebSocket sessions validates the server handles all field units simultaneously. Heartbeat and reconnection testing validates reliability over cellular links.

Rationale: Security compliance test for CJIS query encryption. Packet capture confirms AES-256 IPsec encryption is applied end-to-end. FIPS 140-2 compliance is a federal mandate — failure means loss of CJIS access.

Rationale: Throughput test for dispatch assignment delivery via REST API. 50 concurrent transactions per second validates the interface under mass-casualty incident conditions where many units receive simultaneous dispatch.

Rationale: Integration test for AVL position report delivery. Verifies the Unit Tracking module receives and processes GPS updates at the required rate for accurate unit tracking on the dispatch map.

Rationale: Data integrity test for incident record replication from CAD to Records Management. Ensures closed incidents are faithfully replicated for long-term retention, FOIA response, and statistical reporting.

Rationale: Integration test for audio recording linkage to incident records. Verifies recordings are retrievable by incident case number, which is essential for evidentiary chain of custody.

Rationale: Search performance test for Records Search and Retrieval Engine. Index synchronization within 5 minutes ensures recently closed incidents are searchable for active investigations.

Rationale: Security test for PSAP perimeter. Validates that the firewall correctly enforces inter-VLAN segmentation required by CJIS Security Policy v5.9. Unauthorized lateral movement between zones would compromise criminal justice data.

Rationale: Security test for WAN traffic inspection. Ensures all ESInet and internet traffic passes through the firewall before reaching internal systems. Bypass would expose life-safety systems to external threats.

Rationale: Integration test for network monitoring via SNMP v3. Validates encrypted polling, syslog aggregation, and alerting. Network faults must be detected within the NFPA 1221 two-minute notification window.

Rationale: Accuracy test for time synchronization infrastructure. NTP and PTP accuracy are verified against reference clocks. Timestamp accuracy is critical for incident timeline reconstruction and multi-channel audio correlation.

Rationale: Functional test for UPS power conditioning and status reporting. Validates battery runtime meets the 30-minute requirement and SNMP alerts reach the Network Management System before battery depletion.

Rationale: Performance test for SIP signalling over the dedicated voice VLAN. 150 concurrent sessions validates system capacity requirement. DSCP EF marking verification ensures voice traffic receives priority queuing.

Rationale: Precision time test for PTP distribution via core switches. PTP boundary clock mode is required for sub-microsecond accuracy to latency-sensitive subsystems. Verifies call recording timestamp alignment.

Rationale: Security test for field MDT CJIS query path through the firewall. Validates IPsec VPN termination and source authentication ensure only authorized MDTs can query NCIC databases.

Rationale: Functional test for DNS and DHCP infrastructure. Validates active-active redundancy, zone transfer replication, and IP phone provisioning. DNS failure would halt NG9-1-1 SIP URI resolution.

Rationale: Security test for IPS signature update mechanism and alert generation. Validates that the firewall maintains current threat intelligence and notifies operators of detected intrusion attempts.

Rationale: Degraded mode verification requires systematic fault injection to confirm each subsystem can be lost independently without violating the minimum dispatch capability. Testing at 150 concurrent calls validates the stated capacity floor under realistic load conditions. The 95th percentile measurement for call-to-dispatch time accounts for statistical variation while ensuring the 120-second ceiling is met for the vast majority of Priority Emergency incidents.

Rationale: Site failover is a high-consequence, low-frequency event that must be validated before it is needed. A full-site disconnection drill is the only way to confirm the 60-second failover target and verify that no calls are lost during transition. The 30-second RPO for CAD data replication ensures dispatchers at the backup site have near-current incident state and do not lose recently created incidents.

Rationale: Rapid-succession dispatch testing validates the 2-second station alerting latency under burst conditions, not just single-incident scenarios. 20 fire and EMS incidents exercises the interface under realistic multi-alarm conditions. Exact data match verification ensures the API does not corrupt or truncate incident details during high-throughput operation.

Rationale: Spatial query verification requires a realistic data volume (1 million records over 12 months) to stress-test index performance and confirm the 3-second response ceiling is achievable at production scale. Testing multiple radius values and polygon filters covers the full range of query patterns used by investigators and analysts in real PSAP operations.