skip to content
Your session has expired.

Your authenticated session has expired due to inactivity. You can close this message and continue as a guest or sign in again before proceeding.

New in PremierOne CAD - RELEASE 4.6.3

We're excited to announce the availability of PremierOne 4.6.3 and feature updates to 4.5.3! To upgrade your system reach out to your tier three support manager.

RapidSOS Location as Default

Customers have been requesting the option to use RapidSOS location as the location of their incidents..  PremierOne can now be provisioned to insert the RapidSOS location into the address field.   RapidSOS location can be more accurate than any other location provided through ANI/ALI.

The customer makes a change in provisioning to set RapidSOS as their default location, they can then use a button labeled “Switch” on the II form to change between RapidSOS, Legacy ALI, and Manual Location.  


Update to Active Directory

Previous versions of PremierOne support integration with Active Directory for user authentication, but can not handle user names that include a '.'   This feature updates PremierOne to be able to handle user names that include a “.”.  This is critical to the integration with Active Directory when the User Name is passed to the PremierOne client so the user can successfully gain access to PremierOne when the email has a period in the email.

 

The user will specify their user name in the CAD client (their active directory user name). This user name (which is their email address) would then be sent to Active Directory and after validation the CAD Client would be logged on.   If an Active Directory user name contains a “.”, the “.” is dropped from the internal username used within CAD.

New in PremierOne CAD - RELEASE 4.6

We're excited to announce the availability of PremierOne 4.6! To upgrade your system reach out to your tier three support manager.

Phone Number Query to Work With Smart911 - Provide First Responders Critical Information

Citizens subscribe to the Smart911service. When they call 911 the Calltaker/Dispatcher needs a means to view the information associated with the caller. The Information included in the Smart 911 record could be critical to the first responders. That information may include medical information, access directions, emergency contacts, descriptions of pets or vehicles. This feature enables the call taker to access the information from Smart911 and provide it to the first responders.

During the call taking process PremierOne will pull information from Smart911 through a query. When the call is answered and the ANI/ALI is displayed into the II form, a query is triggered off the phone number. When the query goes to CSI the Smart911 information is retrieved that is associated with the phone number and returns a query containing the URL which can be accessed from the query response. The information will now be associated with the incident through the query. To include the information in the incident history the user will need to copy/paste from Smart911 into the Incident comments.

Integrated Call Control with VESTA

CAD and 9-1-1 call handling are historically different applications with no workflow integration and limited data sharing.Integrated Call Control with VESTA unifies call handling into the CAD workflow and eliminates separate keyboards, monitors, and mice. Data is seamlessly shared from VESTA to the CAD system.

By bringing the telephony functions into CAD, the user is able to focus on a single application, use a single map, and a single address book. In addition to ANI/ALI, call data record information is stored in the CAD Report Data Warehouse, allowing true cradle to grave reporting on call processing and response times.

SMS to 9-1-1 support with ICC/Callworks

PremierOne Integrated Call Control with CallWorks now supports Text to 9-1-1.

New in PremierOne CAD - RELEASE 4.5.1

We're excited to announce the availability of PremierOne 4.5.1! To upgrade your system reach out to your tier three support manager.

Incident Checkpoints - Provide Current State of an Incident

You can now provision Incident Checkpoints to mark the progression of an incident from when the incident is first reported, to the time the incident becomes a working incident, to when the incident is finally under control (or, for example, when a fire is considered completely out).

Agencies that use Proactive Recommendations can enable or disable Automatic and Manual Proactive Recommendations for an Incident Checkpoint. All Incident Checkpoints that are assigned to an incident are available for reporting purposes.

The Incident Checkpoint status assigned to an incident displays next to the incident's status on the Summary tab of the Incident Management form in both CAD and Mobile. The Incident Checkpoint only displays when the incident is in an Active status.

 

The Incident Checkpoint and Incident Checkpoint description can be displayed in the Incident and Unit status monitors in CAD and the Incident Status Summary, Incident Assigned, Incident Monitor, and Unit Status Details status monitors in Mobile.

The Incident Checkpoint assigned to an incident can only be updated by a CAD operator from the command line using the CK; identifier with the IU (Incident Update) command.

Incident Checkpoints are provisioned on the Incident Management–Incident Checkpoint page. You can configure the following:

  • Checkpoint Code
  • Description
  • Whether the checkpoint is the default checkpoint. Every incident created will be initially assigned this Incident Checkpoint. 
  • You can optionally designate only one Incident Checkpoint as the Default Checkpoint per agency. If no Incident Checkpoint is designated as the Default Checkpoint, no Incident Checkpoint is assigned to an incident when it is created for that agency.
  • Whether the checkpoint is included in proactive recommendations. This option is selected by default.

Clear this check box to exclude any incident assigned to this Incident Checkpoint from Automatic and Manual Proactive Recommendations, such as when the incident is under control and units are being released from the incident, or when individuals are being transported from the incident.

 

 

Universal Map Capture Geofence Entry and Exit Data

This feature provides administrators an understanding of the movement and activities of units inside and around geo fences to ensure proper and authorized units are within defined geofences. This information is captured so it can be reviewed and examined later.

When a unit enters or exits a geofence, the Mobile Client sends a transaction to the PremierOne Server. This transaction is treated as a Unit History transaction with a distinct transaction type(s). If the unit is assigned to an incident at the time of the entry/exit/event acknowledgment, the audit record also carries over to the assigned incident history. Only the following events are captured with the use of the Universal Map.

  • Mobile user enters a Geofence 
  • Mobile user acknowledges entry of a Geofence
  • Mobile user exits a Geofence
  • Mobile user acknowledges exit of a Geofence

The Unit History transaction contains the following information:

  • Event Type (Entry, Exit AckEntry, AckExit) 
  • Unit Agency
  • Unit ID (Call Sign)
  • Geofence Name 
  • GPS Entry/Exit Coordinate 
  • UTC Date/Time of event 
  • Unit Added to/Removed from Message Group Flag (true/false) Additionally, a timestamp is captured upon acknowledging the geofence entry and exit notifications.

Route Premise Locations to Street Centerline - Provide Better Routing for Units

In the past, it was possible that a unit could be routed to a location geographically close to an address, but not physically accessible to that address. In order to allow those access points to be routed much more accurately, PremierOne now allows the GIS Administrator to associate a street centerline with an address point (AP) and common place (CP).

The street centerline represents the routing access point for the address. The Street Centerline data import tool allows optional importing of an internal Street ID. The Address Point and Common Place import tools allow optional importing of the Street ID value that corresponds to the access street for the AP/CP location.

The Routing Service (GIS Server and Offline GIS Server) calculates the destination point for routing to an incident location. If the incident location is an AP/CP with a Street ID, the routing end point is the point on that street centerline nearest to the AP/CP location.

If the incident location is an AP/CP that does not have a Street ID, the routing end point is the Street Centerline geocoded location of the AP/CP's address. If a street centerline containing the address does not exist, the destination route point is the lat/long of the AP/CP.

Other New Features Now Available

  • Log Missing Recommendations to the Audit Trail 
  • Assign ORI to a Unit of Multiple units 
  • Add Blank to the Options for “Contact Compliant”
New in PremierOne CAD - RELEASE 4.5

We're excited to announce the availability of PremierOne CAD 4.5! To upgrade your system reach out to your tier three support manager.

Support Two Run Card Sets

Administrators can now manage their run cards in an inactive set at their leisure without affecting live run cards/recommendations during the important process. This ability to support two run card sets enables agencies that do a lot of maintenance on run cards on a continual basis to manage those changes off line in the inactive set, and then update those without impacting the production system or affecting any of the recommendations while upload of the run cards is occurring.

In provisioning, there is a new option to select whether you want to be managing set run card set A or set B.

 

 

These two screenshots below show the additional areas where it will tell you which run card set you are working off of.

 

 

Current Response Mode Window - Quickly access Response Mode Information

Right now, when an agency is in an active response mode, users must scroll through the incident history to know what response mode is currently active. This new feature, with an accompanying screen, enables users to more quickly access information letting them know what response mode an agency is in. 

On the command line, type RM and press Enter. The Response Mode window appears, listing all active response modes and the beats with those response modes.

 

 

The form displays a collapsed row showing the agency and active Response Modes, sorted by agency and then Response Mode. The agency is not displayed unless there is a least one Response Mode active against a beat. Only agencies that the user has permissions to use the RM command against are displayed. Expand the row to show all the Beats with that Response Mode along with the current Area and Sector for the beat.

Display All Jurisdictional Information on the II and IM Forms

Right now, the jurisdiction for all associated agencies does not display. Many call types trigger both a police and fire call. A call-taker needs to know who handles the fire and police for an address/location upon location verification, not only after a type code is entered. This new feature enables the call-taker to quickly determine if a call needs to be transferred to an outside agency and expedites said contact.

 

 

The jurisdictional information is displayed at the bottom of the location section of the Initiation form. If an agency is displayed in red text that signifies that agency is out of jurisdiction and the call taker must call that agency for response. The information will also be displayed at the bottom of the IM form for reference when the dispatcher needs to know what agencies are responsible for the location of that incident.

Display Block Numbers for Intersections

Agencies often include streets that intersect the same other street in several places, or intersections of minor streets that may not be familiar to responders. This feature allows an administrator to configure the block numbers of streets in an intersection to appear along with the cross street names to assist in determining the correct intersection.

Synch Duration (On US Form) with Update Duration (on Status Monitor)

The Update Duration field on the Status Monitor now reflects the same time as the Duration field on the Unit Status form. When a unit status is changed either by the UO command or by placing the unit in the same status, the two fields are reset to 00:00:00 (form) and 00:00 (status monitor).

Restrict copying of Query Responses

This feature provides agencies that are subject to CJIS requirements against redistribution of sensitive information the ability to restrict CAD and Mobile users’ ability to copy query responses, forward query responses using email, or attach query response information to incidents. This feature can also be configured to disable the Windows right-click–Copy and Ctrl+C copy/paste operations. When enabled, these restrictions apply to all query response displays, including the Raw and Formatted Query Response tabs, Work Assist Area Query tab, orphaned query response windows, and hot hit response dialogs.

 

New in PremierOne CAD

Transitioning GPS - Equipped Units from Stale to Not Reporting

With this feature, agencies can now provision how long a unit can remain in a stale state before moving to a "not reporting" state. The unit can then be recommended from its last known reported location or it's station location (based on a separate provisioning option).

Send Information to All Associated Incidents When Appending During Duplicate Incident Check

Users can now add updated information from an incident to a specified duplicate as well as any associated Law, Fire or EMS incidents. This information will then be distributed to all responding units, eliminating the need to update each associated incident individually.

There is a new provisioning setting called “Include Associated Incidents". After turning on this setting, all information being appended will go to all associated incidents.

Identifier Added to II Command to Create Incidents based on Existing Incidents

This feature enables the user to clone/copy an incident, change the location and bring over all of the information from the original incident. For example, when there is a burglary followed by a chase that results in an accident, the user can clone the incident and add a different address to the cloned incident while retaining incident information.

The incident initiate (II) command now includes an incident number identifier (I;). From the command line the user specifies II. Incident number and an initiation form is then displayed with all the information from the original incident. All fields are editable with the exception of the comments. The user can now update any field including the location field. After submitting the form, the cloned incident is created and automatically associated with the original incident (just as it does with the cloning command).

Destination for Unit Statue Updates

This feature enables the user to provision PremierOne to track the destination of a unit for common locations, such as a unit on the way to training, an ambulance transporting to a hospital, or a police vehicle on the way to the jail. When units are transporting to locations that are unfamiliar or new, drive directions are available to ensure the quickest arrival to those destinations.

Add Destinations in provisioning and then associate the destinations with unit statuses in the existing unit management –unit status codes–unit status codes window. In the Unit status codes window, there is a new option to require a destination.

 

 

On the settings tab, you can provision whether the unit location is automatically updated when a unit reaches its destination. Provisioning can be done at both agency andagency type levels.

 

 

Search Incident Comments From CAD and Mobile IR Forms

Users can now use the incident recall form in CAD and Mobile to search for specific words or terms within the comments of an incident. For example, when searching for something with very limited information, i.e. Red Car, this feature allows users to enter such information and search all incidents that included “Red Car” or “Red” and/or “Car”. This saves critical time eliminating the need to look at each individual incident to find a “Red Car”.

Go to the incident recall (IR) form and enter the information you would like to search for in the comments field. Then, choose to search for the exact text entered (Red Car), all the text entered (will find incidents with Red and Car anywhere in the comments), or any (will find any incidents with Red and/or Car in the comments).

 

 

Road Closure Enhancements - Scheduling and Comments

Users are now able to schedule road closures. This is helpful for pre-scheduled events such as parades, road construction, sporting events, etc. Label road closures and add comments for ease in identification if there are many closures in the list. This allows the agency/user to plan ahead and prepare for the event without last minute map updates before the event occurs.

The “Road Closure” tab includes new fields for scheduling and adding comments to a road closure.

 

 

Status Monitor Right-Click Enhancements 

This new feature streamlines the number of windows that an agency would need to configure. Users can now perform Incident and unit right-click menu functions from either an incident or unit status monitor.

For example, from within a status monitor (Unit or Incident), the user can right-click on a unit assigned to an incident or on an active incident number and the provisioned right-click menu functions appear and can be selected.

The administrator can now build status monitors with unit and incident information in the same window.

 

 

Proactive REcommendations by Unit and/or Incident 

When a dispatcher brings up a call for dispatch, the system will always recommend the closest unit. However, the closest unit may be several minutes away at the time the unit was recommended. While enroute to the incident, other units become available. The dispatcher can perform a PR (Proactive Recommendation) command to see if there is now a unit that is closer and qualified to replace the unit responding to the incident. If the dispatcher agrees with the Proactive Recommendation suggestion, they can submit the PR form to have the closer unit automatically swapped with the unit that is currently responding.

Here’s how it works:

PR by Unit ID - Allows the dispatcher to identify the nearest incident to the unit that the unit can be better utilized on than any of the responding units that are currently enroute, or can fulfill missing capabilities from that incident.

“Are there any incidents that this unit is qualified for and is either closer than a responding unit, or can fulfill one or more missing capabilities on that incident?"

PR by Incident Number - Allows the dispatcher to evaluate all of the assigned units that are currently enroute to the incident, as well as all required capabilities that are missing from the incident against all units that are currently available.

“Are there any units currently available that are qualified for this incident and are either closer than a responding unit, or can fulfill one or more missing capabilities on the incident?"

PR by Incident Number and Unit ID - Allows the dispatcher to evaluate the qualifications of a unit against a particular incident.

"Can this unit be better utilized on this incident than any of the responding units that are currently enroute, or can it fulfill one or more missing capabilities on the incident?"

Add Postal City Data Attribute to PremierOne Geodatabase

Previously, PremierOne GIS supported a single “city” attribute for every common place, street center line, and address point defined within GIS. This enhancement adds a “Postal City” attribute to the existing incident location managed in PremierOne so that this value is stored with verified incident locations and then propagated with the incident when other systems/applications, for example, PremierOne Records, are utilizing PremierOne incident data.

  • The GIS administrator can edit the “Postal City” attribute associated with an address point, street centerline, or common place record that is managed by GIS.
  • The PremierOne reporting user can use the “Postal City” values associated with Incident Locations.
  • The PremierOne Records data feed includes the new “Postal City” attribute as a value associated with an incident’s location.

The following new features are also now available:

  • Status Monitor Profiles Saved at the User Level - A user with the proper permission can now use the DC command to set and save their own preferred display configuration, which acts as a “follow me” setting, displaying as configured for that user’s future CAD sessions. The user can use the new RPS (reset personal settings) identifier with the DC command to cancel their personal display configuration and return to the agency-level display configuration settings.
  • Highlight Missing Units from Recommendations - The CAD Dispatch window is now enhanced so that capabilities missing from the recommendation are more apparent - now displayed in BOLD font.
  • Modifications to the Incident/Report Number Display Formats - Agencies can now define the minimum number of digits to display as part of the Incident Number or Report Number format; numbers are padded with zeros. This allows an agency who resets daily or monthly to limit the number of zeros that display in their number formats. For example, when specifying three as the minimum number of digits, the first incident would be FD-2018-10-01-001
  • Built-In Queries For Incident, Location, Vehicle, and Person Information - A APremierOne user (CAD, Mobile, Handheld, or the SmartClient) can query the RDW for previous incident, location, person, and vehicle information with the use of four default queries that are now installed as part of a new PremierOne system. A new interface, “P1CAD,” supports the four queries: P1CAD-Incident, P1CAD-Person, P1CAD-Location, and P1CAD-Vehicle.    
  • Previous Vehicle Check Without Using State - An option was added to Provisioning so that previous vehicle checks do not require the state ID code for a vehicle. In cases where the state is not known, this helps to ensure that any plate that is entered will be returned in the search results. This feature can be turned on at the agency level using the provisioning setting located in Service Settings.
  • Display Phone Type Labels in Ready Reference Items - Ready Reference contacts configured in Provisioning have a label for every phone number associated with a contact. The label associated with each phone number now displays when viewing a Ready Reference contact in CAD and Mobile.

Unit Location Identifier Added to ID Command - Dispatchers can now update the unit's location while dispatching them onto an incident using the Incident Dispatch command. Previously a unit would need to be dispatched to an incident, and then the dispatcher would have to manually change the location for each unit. The identifier was added to the end of the command string.