What are Automation Rules?
At its core, automation rules allow you to define a set of conditions or “triggers” (e.g., “look for XYZ”) and then specify an automated “action” for the system to take in response. This “then” action is where the magic happens – the system performs something automatically, limiting clicks, reducing effort and directing users precisely where they need to be.
Why are Automation Rules so Valuable?
Enhanced Efficiency & Automation: It takes the burden off operators by automating routine or critical responses, allowing them to focus on decision-making rather than manual navigation.
Empowering Day-One Users: Rules essentially enable your people to use the product on day one. This is invaluable for ensuring usability, especially when experienced personnel aren’t available.
Consistency & Reliability: Ensures that critical events are always handled with a consistent, pre-defined response, reducing human error.
Improved Situational Awareness: Automatically pushes relevant information to the forefront, ensuring users are immediately aware of high-priority incidents.
Common Examples and Best Practices for Setting up Rules
Emergency Situation Activations
Trigger: An emergency button is activated on a portable radio or a Rave Panic Button.
Action: Automatically center the map on the unit’s location, pull up nearby video feeds (if integrated), and change the unit’s icon color to signify the emergency.
Benefit: Immediate visual and contextual awareness during critical officer or school emergencies.
High-Priority Call & Incident Alerts
Trigger: A Computer-Aided Dispatch (CAD) incident with a specific priority level (e.g., “Priority 1”), or a specific incident type (e.g., “shots fired,” “stolen vehicle” or “active shooter”).
Action: Automatically move the map to the incident location, highlight the incident with a distinct color or initiate an automated process to gather related information.
Benefit: Ensures immediate focus on the most critical events, streamlining response.
Visual Status & Color-Coding
Trigger: Changes in unit status (e.g., “available,” “on scene” or “in pursuit”) or specific 911 call information (e.g., RapidSOS location, phase information).
Action: Apply dynamic color-coding to unit icons or call markers on the map to provide instant visual cues.
Benefit: Improves visual interpretation, making it easier for operators to quickly grasp the status of multiple units or calls. This helps with user adoption by making these things look like systems they may already be using, such as CAD (e.g., existing CAD color schemes).
Key Considerations for Administrators
Identify Critical Workflows: Work with your operational teams to identify events or data points that demand immediate attention or could benefit significantly from automation.
Start Simple: Begin with a few high-impact rules to gain familiarity, then gradually expand.
Test Thoroughly: Always test your new rules in a controlled environment to ensure they behave as expected without unintended consequences.
Document Your Rules: Keep clear documentation of each rule’s conditions and actions for future reference, troubleshooting and training.
By strategically implementing automation rules, you can transform CommandCentral Aware from a reactive tool into a proactive operational asset, enhancing your agency’s ability to respond quickly and effectively to any situation.
For more CommandCentral Aware knowledge, visit the CommandCentral Aware Manual.
