We’re Tracking the Future of Security

Category: Command & Control

VMS, PSIM and unified command-and-control platforms that bring multiple security systems into a single operational view.

  • Denver Police to Let ShotSpotter Gunshot-Detection Contract Expire After a Decade

    Denver Police to Let ShotSpotter Gunshot-Detection Contract Expire After a Decade

    City Will Phase Out Acoustic Sensors by Year’s End

    The Denver Police Department says it will let its contract for ShotSpotter gunshot-detection technology expire at the end of 2026, ending more than a decade of automated gunfire alerting in the city, according to CBS Colorado and Denver7 reporting on the department’s August 20-21, 2026 announcement. The system uses acoustic sensors mounted on utility poles to detect the sound of gunfire and alert Denver’s 911 dispatch center, often before a human caller reports a shooting. Denverite reported the city’s contract with SoundThinking, the company behind ShotSpotter, is worth roughly $4.7 million and expires at the close of the year.

    Rather than an abrupt shutdown, DPD says it will begin removing sensors from areas generating the fewest alerts first, with most of the network remaining active through the rest of 2026. According to Denver7, the department said it is evaluating “whether a new vendor can provide greater public safety benefits” and plans to launch a bidding process to assess alternative gunshot-detection capabilities while gathering community input on how to reallocate resources. As part of the initial ramp-down, DPD said it will begin phasing out ShotSpotter coverage specifically in the Sun Valley and Park Hill neighborhoods.

    A Decade of Data on Alerts, Arrests and Recovered Firearms

    In its release announcing the change, the department said that from 2020 through June 2026 the program generated 25,217 alerts, leading to 655 arrests and the recovery of 721 firearms, according to CBS Colorado. Officers also located shell-casing evidence tied to 6,672 of those alerts. Denver’s decision comes amid what Denver7 described as broader nationwide scrutiny of police gunshot-detection and surveillance technology, as cities weigh the systems’ operational value against their cost and questions about alert accuracy and community impact that have been raised in other jurisdictions.

    What Happens Next

    City officials have not yet named a preferred replacement vendor or detailed the criteria for the planned bidding process. The wind-down gives Denver several months to evaluate alternative gunshot-detection platforms and to solicit public feedback before the current sensor network is fully retired, according to the reporting from Denver7 and Denverite.

    Sources

  • AI Agents in Security Operations Centers

    AI Agents in Security Operations Centers

    Security operations centers receive events from cameras, access control, intrusion, fire, cyber, intercom and building systems. AI agents are emerging as a software layer for gathering and presenting that context.

    What an AI agent does

    An agent can receive an event, gather context, summarize what happened, suggest a response and, within defined permissions, execute an approved workflow.

    Useful early applications

    Drafting reports, classifying alarms, generating shift summaries, searching procedures and locating related video or access events can reduce repetitive work without automating high-consequence decisions.

    Permissions and human supervision

    Automatically unlocking doors, disabling alarms or changing surveillance configurations creates risk. Sensitive actions should require operator confirmation and clear authorization boundaries.

    Data quality and auditability

    Incorrect names, outdated maps or unsynchronized timestamps can mislead an agent. Recommendations and actions should preserve evidence, uncertainty, user approval and system state.

    The changing SOC interface

    Conversational tools may allow operators to query multiple systems through one layer, but the underlying integrations and source data must remain visible and verifiable.

    Conclusion

    The realistic direction is human-supervised autonomy: agents handle routine correlation and documentation while operators retain judgment and accountability.

  • Unified Security Platforms: Integration vs True Unification

    Unified Security Platforms: Integration vs True Unification

    Security vendors often use integration and unification interchangeably, but they describe different architectures. Integration connects separate products; unification begins with shared data, identity, workflows and administration.

    Traditional integration

    A VMS, access-control system and intrusion platform may remain independent applications that exchange events through APIs or middleware, while retaining separate users, databases and upgrade cycles.

    What true unification changes

    A unified platform can provide one operator interface, common permissions and shared event handling across video, access, alarms and other systems.

    Operational benefits and data model

    Shared workflows can reduce training and speed response. The deeper distinction is whether identity and event objects are genuinely shared or merely displayed together.

    Vendor dependence and best-of-breed systems

    Unification may increase dependence on one vendor. Buyers should examine open APIs, third-party device support and export options. Specialized sites may still justify best-of-breed subsystems.

    Cybersecurity and migration

    A unified platform can simplify identity and patching but also concentrates risk. Many enterprises should migrate gradually through federation or integration as legacy systems reach end of life.

    Conclusion

    A single dashboard is not proof of unification. The correct architecture depends on scale, legacy investment, specialized requirements and long-term platform strategy.

  • VMS, PSIM and Command & Control Systems Explained

    VMS, PSIM and Command & Control Systems Explained

    Understand how VMS, PSIM, alarm management, GIS, sensor fusion and security operations center platforms turn security data into operator decisions.

    Security technology produces events faster than people can interpret them. Cameras create video and metadata, access systems create credential events, perimeter sensors create alarms, fire systems create life-safety signals and building systems add another layer of operational data. Command-and-control software exists to turn that flow into a manageable picture.

    VMS: video first

    A Video Management System is primarily designed to manage video. It connects cameras, controls streams and recording, manages users, displays live and recorded video, and increasingly hosts analytics and integrations. For many sites, the VMS is the main operator interface because visual verification is central to incident response.

    Modern VMS platforms often integrate access control, intercom and analytics, but the depth of those integrations varies. A system that can display an access alarm is not necessarily a full access-control platform.

    PSIM: process and integration first

    Physical Security Information Management was developed to aggregate events from multiple security systems and guide operators through consistent procedures. A PSIM may sit above VMS, access control, intrusion, fire interfaces, GIS and other systems. The key value is not simply showing everything on one screen; it is correlating events, applying rules and creating an auditable response workflow.

    For example, a perimeter radar detection might automatically cue a PTZ camera, display the target on a map, check nearby access-control states and present the operator with a response procedure. That is more useful than five independent alarms arriving in five applications.

    Command & control

    The term command and control is broader. In critical infrastructure or public-safety environments, the platform may combine security, operational technology, communications, mapping, incident management and external data. The design goal is shared situational awareness and coordinated action.

    Alarm management and prioritization

    A common failure in security operations centers is alarm overload. If low-priority technical faults are presented with the same urgency as a confirmed intrusion, operators lose attention. Good alarm management applies severity, confidence, location, time, dependencies and escalation rules.

    Sensor fusion goes further by combining evidence. A single radar track may be interesting; a radar track plus thermal detection plus a fence vibration event is more compelling. Fusion logic should be transparent enough for operators to understand why the system raised priority.

    Interoperability and metadata

    ONVIF Profile M standardizes metadata and events for analytics applications and can help move structured information between compatible systems. Standardized event data matters because automation depends on software understanding not just a video stream, but what the system believes happened.

    GIS and maps

    Maps are particularly useful for large campuses, airports, borders and energy sites. Spatial context allows operators to see where alarms occur relative to gates, cameras, patrols and assets. Good GIS integration should support action, not just decoration.

    How to choose the right layer

    A small site may need only VMS plus integrated access control. A larger enterprise may benefit from a unified security platform. A critical-infrastructure operator with many legacy systems may need PSIM or a broader command-and-control layer.

    The key questions are operational: how many systems must operators use, which events need correlation, what workflows must be enforced, how incidents are escalated and what evidence is required afterward.

    FAQ

    Is PSIM the same as VMS? No. VMS is video-centric; PSIM is typically multi-system and workflow-centric, though modern platforms increasingly overlap.

    What is sensor fusion? It is the combination of signals or events from multiple sensors to improve confidence or context.

    Does one interface guarantee integration? No. True integration should be evaluated at the data, control and workflow levels.

    Verification note

    Avoid claiming a “single pane of glass” unless a tested integration actually supports the required control functions, not just event display. This article describes general architecture, not vendor-specific performance claims.