PURVIS and the seconds before the siren

In Pittsburgh, the trouble was partly what firefighters heard when they were not being sent anywhere. Hundreds of dispatches circulated among 30 firehouses and 14 EMS stations each day. Crews had to pick their own assignments out of radio traffic that often concerned someone else. An emergency elsewhere could still occupy attention here.

The city’s account of its PURVIS installation describes a different arrangement: relevant information delivered to the crews assigned to respond. Screens, reader boards, and other displays bring the details into the station. The practical benefit is both less distraction and more information at departure. There is something pleasing about an alarm company helping a workplace become quieter.

PURVIS Systems occupies this easily overlooked stretch of emergency response. A dispatcher has made a decision; a crew needs to act on it. Between the two sit software, communications networks, speakers, lights, and human beings. Each connection is a place where information can wait, become muddled, or fail to arrive.

“we get out of the station with more information.”Chief Darryl Jones · Pittsburgh Bureau of Fire

A speaker is only the beginning

The PURVIS Fire Station Alerting System, or FSAS, is an IP-based combination of hardware and software. It takes information from computer-aided dispatch, usually shortened to CAD, and distributes incident details through the channels an agency uses. Voice announcements, radio, station displays, and mobile alerts can serve different people in different places.

Simultaneous notification matters. Multiple stations can receive instructions without waiting for a dispatcher to repeat the same work one station at a time. System monitoring gives dispatchers visibility into alert status. Redundant configurations provide alternative paths or components when something stops working. These are operating features, with value that depends on how the installation is designed and tested.

Some of the most revealing parts are physical. A dorm remote lets a firefighter select the unit types that should activate a room’s alerts. Speakers can incorporate red lighting for nighttime movement. A turnout timer can stop when personnel acknowledge an incident, when a detector registers that the apparatus has left, or when other configured criteria are met. The system’s definition of departure deserves as much attention as its stopwatch.

PURVIS says more than 250 fire and EMS departments use its FSAS, with more than 1,200 fire station installations. Its named customers include Boston and Jacksonville, alongside county systems serving multiple departments. Those settings ask for different configurations; a common product still has to accommodate local practice.

The site visit that changed the purchase

Charleston County’s 2013 council minutes offer an unusually candid view of how such a purchase happens. The county initially authorized negotiations with US Digital Designs in May 2012. Those negotiations failed in October. Staff then refined their understanding of the dispatch center’s needs, considered a revised Motorola proposal and demonstration, and visited a working PURVIS system in Washington, DC.

After those reviews, PURVIS became the preferred vendor. Council approved authorizing negotiations with the company and reallocating $1.23 million in bond funds to the station alerting system. That figure describes the project funding decision, rather than a standard PURVIS price.

The discussion included doubt. One council member questioned whether the procurement had sufficient checks and balances and argued for rebidding. Another, having previously sought more information, said the additional material had convinced her to proceed. The lesson for buyers is fairly concrete: clarify the requirements, see a system operating, and leave room for scrutiny. A site visit cannot replace procurement discipline, but it can make an abstract specification intelligible.

Keeping the old speakers was the clever part

Washington’s installation gives that visit some context. Its FSAS went into operation in August 2012 and covered 36 locations, including 32 fire stations, dispatch facilities, a fire boat, and the radio shop. PURVIS connected it to the District’s CAD and radio systems, with audible and visual alerts and two-way voice communications.

The company’s case study also records a less photogenic decision: reuse an existing reader board and some speakers, and remove unnecessary relays. The savings went toward functionality beyond the original specification, including front-door cameras with two-way audio. Existing equipment became part of the modernization budget rather than an automatic casualty of it.

This is a useful distinction in a market with credible alternatives. Municipal bids place PURVIS alongside US Digital Designs, Bryx, Locution, and Westnet. Integration and automated announcements are buying criteria across the category. PURVIS’s case rests on the configuration it can deliver, its engineering services, and its support relationships. Buyers still need to compare those offers against their own systems.

Waco illustrates the replacement trigger. PURVIS’s January 2024 account describes a radio-based alerting system that had reached the end of its serviceable life after more than two decades. The department wanted a more efficient, stable replacement capable of alerting different stations simultaneously. Its attraction was a change in the dispatch workflow as well as newer equipment.

The bill after installation

PURVIS earns money through government technology projects and continuing service contracts. For FSAS, that includes proprietary software, hardware, configuration, installation, and maintenance. A cooperative purchasing agreement with Sourcewell offers eligible agencies another route to procurement. Its published pricing sheet specifies a 3% discount from MSRP or published list prices; the actual project still needs a defined scope.

Naperville makes the continuing obligation visible. It installed PURVIS FSAS in 2017. In October 2025, the city approved maintenance costing no more than $204,250 for a three-year term running from November 2025 through October 2028. Support includes maintaining the platform and upgrades to improve security.

The city identified PURVIS as the single source because of its proprietary software and hardware configuration. PURVIS’s accompanying letter says it is the only FSAS supplier and has no resellers. Once installed, therefore, this system brings a specific vendor relationship with it. A buyer should read the maintenance terms while evaluating the initial purchase.

A destroyer, then a fire department

The company’s history helps explain its interest in maintaining complicated systems. PURVIS began in 1973 with sea trials and sonar experiments aboard USS Hugh Purvis. Two years later it started its relationship with FDNY. Naval engineering and public safety became the two persistent strands of the business.

Today its defense work includes testing, alteration development, technical documentation, configuration management, and lifecycle support. In April 2025, it announced a $19.9 million contract for integrated product support and configuration management at the Naval Undersea Warfare Center in Newport. In September 2026 came a $6.2 million, five-year follow-on task order supporting electronic warfare and electromagnetic maneuver warfare laboratories. These are contract values, with work performed over their terms.

That work requires attention to records, installed configurations, and security. PURVIS reported achieving CMMC Level 2 certification in July 2025 using internal expertise, with all 110 assessed security controls satisfied. Its hiring descriptions provide another glimpse of the organization: employees assemble devices, check systems before shipping, troubleshoot audio and network components, and rotate through after-hours support. The advertised values of teamwork and responsibility have a practical setting.

Buy the whole departure

A public agency can use PURVIS to connect an existing dispatch environment to station and remote personnel, modernize aging alerting equipment, or obtain engineering and support for defense systems. For a fire department, the productive first step is to map the complete notification path: who receives which information, through which devices, and what happens when a component becomes unavailable.

The design needs reliable infrastructure, accurate CAD data, agreed operating procedures, and a funded support plan. An automated announcement cannot fix a wrong address upstream. A quieter dorm depends on correct unit assignments. Redundancy needs testing under the failures it is meant to cover. Where those conditions are neglected, purchasing another alerting device leaves the larger problem intact.

Washington’s equipment reuse and Charleston’s site visit offer practices worth borrowing outside emergency services. Keep what works. Inspect the handoffs. Watch a proposed system in use. Budget for its working life. PURVIS’s subject happens to be the firehouse, but the management problem belongs to anyone whose decision must travel through several systems before someone can act.