premierone release notes version 4 - ohiogis3.oit.ohio.gov/ziparchives/marcs/map_updates/p1... ·...

©

PremierOneTM

CAD/Mobile Release Notes Version 4.4

2018

2018 Motorola Solutions, Inc. All rights reserved. Motorola Solutions Confidential

MN005525A01-A

2Motorola Solutions Confidential

Copyrights

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.

Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.

AccuracyWhile reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.

TrademarksMotorola, Moto, Motorola Solutions, PremierOne, and the stylized M logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license.

Microsoft, Windows, Windows 7, Windows 8, Windows 10, and Windows Server are registered trademarks of Microsoft Corporation. All other product or service names are the property of their respective owners.

Build date: November 7, 2018

Contents


ContentsTechnical Support ......................................................................................................................................................... 2

Provisioning and IE ....................................................................................................................................................... 3

Software ......................................................................................................................................................................... 3

Issues Resolved ............................................................................................................................................................ 3

CAD New Functionality ................................................................................................................................................. 5

Miscellaneous Enhancements ..................................................................................................................................... 5

Update CAD Client Logon Screen to Allow User to Enter Device ID (309980)................................................. 5

Covering Dispatcher Clears All Updated Flags (298368).................................................................................. 6

Modifications to Verifying an Incident's Jurisdiction within the Field Initiation (FI) Form (305239).................. 11

Remove Unused Tool Icons From the Admin Console (the System Management Tool Portal) (314073) ...... 11

Delta/Compass Broker interface to limit the transactions to ETIX (313617) ................................................... 11

New Option for Automated Incident Notifications (315825) ............................................................................ 11

APCO IntelliComm Interface (297383)............................................................................................................ 12

Transitioning GPS-Equipped Units from Stale to Not Reporting (291111)...................................................... 13

Modifications to the Incident/ReportNumber Display Formats (269605)......................................................... 14

Cascading Emergency Notification Popups (253473)..................................................................................... 16

Skill Search (SS Command) (159519) ............................................................................................................ 16

Add Postal City Data Attribute to PremierOne Geodatabase (265818) .......................................................... 18

Previous Vehicles Check Without Using State (243822) ................................................................................ 21

Send Information to All Associated Incidents When Appending During Duplicate Check (169583) ............... 22

Display Phone Type Labels in Ready Reference Items (277482)................................................................... 24

In-Station Alert: Include Full Incident Number and Map Book Information in SMTP Messages(302634) ....... 25

Lat/Long in Degrees & Decimal Minutes in CAD (176124) ............................................................................. 25

CAD Radio Device Alias Synchronization (300197)........................................................................................ 26

Support for Both CADICAD and Radio Services (309786) ............................................................................. 28

Support Modifying Circumstance With QA Software (301191) ....................................................................... 28

Add Current Active Plan Label to the Active Plan Form (301247) .................................................................. 29

Improve IH Display in Orphan History Window (303762)................................................................................ 30

RapidSOS Integration (297285) ...................................................................................................................... 31

Command Enhancements ......................................................................................................................................... 33

UL Identifier Added to ID Command (225744) ................................................................................................ 33

I Identifier Added to II Command - Create Incidents Based on Existing Incident (279009) ............................ 34

New Fields ................................................................................................................................................................. 35

Destination for Unit Status Updates (145406)................................................................................................. 35

Add APT Field to Field Initiate Screen (242723) ............................................................................................. 37

Additional Fields in Pager Messages (297226)............................................................................................... 37

Incident Comments.................................................................................................................................................... 38

Contents


Search Incident Comments From CAD and Mobile IR Forms (262645) ......................................................... 38

Copy and Paste Incident Comments From the WAA (271705)....................................................................... 41

Copy Premise/Hazard Records Into Incident Comments (288144) ................................................................ 42

Road Closure Enhancements.................................................................................................................................... 42

Auditing Creation and Clearing of Road Closures (297390) ........................................................................... 42

Road Closure Enhancements - Scheduling and Comments (107913)............................................................ 44

Query Enhancements ................................................................................................................................................ 45

Built-In Queries For Incident, Location, Vehicle, and Person Information (137469) ....................................... 45

Query Response Orphan Window Follow-me Settings (310107).................................................................... 46

Query Response Printing (301500)................................................................................................................. 46

Move Query Building Blocks Configuration to Provisioning (304673) ............................................................. 47

Option to Include Query Response Data in RDW (308749)............................................................................ 48

Expand Hot Hit Response Redistribution Options (312418) ........................................................................... 49

Add Query Parameters in Query Header (310106)......................................................................................... 50

Expand Multiple Query Responses (173572).................................................................................................. 50

Status Monitor Enhancements................................................................................................................................... 50

Display <Unit ID>/<Shift ID> in Radio PTT Status Monitor Window (309773) ................................................ 50

Status Monitor Right-Click Enhancements (268516) ...................................................................................... 51

Status Monitor Profiles Saved at the User Level (149749) ............................................................................. 53

Recommendations-Related Enhancements .............................................................................................................. 55

Personnel Cross-Staffing (276538) ................................................................................................................. 55

Re-evaluating Recommended Units for Additional Capabilities for Reuse (248229) ...................................... 56

Highlight Missing Units From Recommendations (105664) ............................................................................ 56

Proactive Recommendations (Evaluate Assigned Units set of Recommendable Capabilities) (296655) ....... 57

Proactive Recommendations (PR Command) (299589. 299088) ................................................................... 58

Proactive Recommendations (Incident-Based Proactive Recommendations) (299197)................................. 58

Proactive Recommendations (Incident+Unit Proactive Recommendations 4.4) ............................................. 58

AIO Enhancements (298330) .................................................................................................................................... 58

Other All-In-One Installer Improvements......................................................................................................... 59

Import/Export Support................................................................................................................................................ 60

Resource/Device (Radio, Workstation/MDT/Handheld) (308674)................................................................... 60

Workstation/MDT/Handheld Devices (259539) ............................................................................................... 60

Incident Management Coverage Groups, Dispositions, and Incident Type Alias (302469) ............................ 60

Modifying Circumstances, Premise/Hazard Types, and Premise/Hazard (303200) ....................................... 60

Incident Types(298954)................................................................................................................................... 60

IRF (300605) ................................................................................................................................................... 60

Jurisdiction (Area, Beat, Location, Sector) (308676)....................................................................................... 60

Resources (Capability Group, Capability/Skill, Personnel, Vehicle) (307588) ................................................ 61

Contents


Response Card (301198) ................................................................................................................................ 61

Unit Management (Riding Position, Unit IDs, Unit Preassignments) (303895) ............................................... 61

LSM (LSM, LSM Vehicle Make, and LSM vehicle) (310912) .......................................................................... 61

Plan Management (310915)............................................................................................................................ 61

Agency (Trusted) (Permission Set) (311147).................................................................................................. 61

Contractor Rotation (311148).......................................................................................................................... 61

Query (311149) ............................................................................................................................................... 61

Talkgroups Configuration (311150)................................................................................................................. 61

Alerting In-Station Record (311151)................................................................................................................ 61

Limit Data Import and Export (314592) ........................................................................................................... 62

CAD-to-CAD .............................................................................................................................................................. 62

Move Send All Local Dispatches and Include All Assigned Units to Provisioning (309339) ........................... 62

Orion Interface with PremierOne's On Duty Unit Assignment Data (304695) ................................................. 64

Include Disposition Description in CFS Update Messages (297246).............................................................. 64

Suppress IDTL Messages for Closed Incidents (298727)............................................................................... 64

Receiving Child-to-Parent Comments in an IDTL Update Message (300675)................................................ 64

Receiving Parent-to-Child IDTL Update Messages with Radio Channel Updates (300677)........................... 65

Receiving Parent-to-Child and Child-to-Child Comment Entries in an IDTL Update Message (300678)........ 65

Receiving R2I2 Requests: Address Verification Process................................................................................ 65

Receiving R2I2 Responses: Rejected Units Priority Comment (300680) ....................................................... 65

Receiving General Notifications: Subject Line Refinement (300685).............................................................. 65

Receiving Comment Entries in an R2I2 Request Message (304931) ............................................................. 65

Suppress Priority Comment Notifications for Updates to Associated Incidents (307319)............................... 65

Secondary Incident Not Updated When IDTL Received (310193).................................................................. 65

Include Lat/Long values Within an R2I2 Message (310224)........................................................................... 66

Add Initial Caller to R2I2 Requests (310257) .................................................................................................. 66

IM_Call_Association Table Added (311154) ................................................................................................... 66

Security and Login Integration With Callworks and Call Control (297284)...................................................... 66

Call Control Support for CCI 1.1 SP2(303826) ............................................................................................... 67

Mobile Features ........................................................................................................................................................... 67

Mobile Login Pre-assignments Check Box (105659)................................................................................................. 67

Mobile Login with Personnel Still Assigned to the Unit (265725) .............................................................................. 67

Managing Non-Trusted Agency Incident Assignments (118429) .............................................................................. 69

Mobile Client Unit Details Tab (123646) .................................................................................................................... 69

Built-In Queries For Incident, Location, Vehicle, and Person Information (137469).................................................. 71

Expand Hot Hit Response Redistribution Options (312418)...................................................................................... 71

Mobile Mapping Toolbar Display (238632) ................................................................................................................ 71

Mobile Map Server Side Mapping Services (311671) ............................................................................................... 73

Contents


Actionable Premise/Hazard Icon in Mobile Mapping (259479) ....................................................................... 73

Static Location and Orientation of Vehicle Chevron on Mobile Map (238635) .......................................................... 75

Mobile Client UI Customization by Role (130388) ..................................................................................................... 78

Automatic Unit Status Changes (130390) ................................................................................................................. 79

Field Configurable Logon Form (185387).................................................................................................................. 81

Extended Mobile Client's Follow Me Settings (212949)............................................................................................. 81

Skill Search from Mobile (227256)............................................................................................................................. 82

Time Synchronization for Mobile and Other Devices (238703) ................................................................................. 84

Highlight Hot Hit Trigger In Query Responses (257990) ........................................................................................... 84

Expand Hot Hit Response Redistribution Options - Mobile (312418)........................................................................ 85

Add Postal City Data Attribute to PremierOne Geodatabase - Mobile (265818) ....................................................... 85

Log Incident Views to Incident History (272473) ....................................................................................................... 86

Display Incident Comments on the Mobile Mapping Page (264816)......................................................................... 88

Mobile Road Closure Enhancements - Scheduling and Comments (107913) .......................................................... 89

Display Incident Location on Every Incident Management Tab (269849) ................................................................. 89

Reports Service Button Launches PremierOne Records Mobile (273590) ............................................................... 90

Mobile Mapping Tracks Units in Emergency Status Regardless of MUD Settings (276848) .................................... 92

Expanded Incident Search Criteria (290425)............................................................................................................. 93

The Report Number (RP) Command is Available on the Mobile Command Line (290426) ...................................... 93

Add Priority Comments on Mobile Self-Dispatch (291467) ....................................................................................... 93

History Enhancement (297878) ................................................................................................................................. 95

Add Plate Month to Mobile Traffic Stop Form (172861) ............................................................................................ 96

Display the City on the Dispatch Notification (299171).............................................................................................. 97

Modified Incident Summary Form.............................................................................................................................. 97

Modified Clear Screen ............................................................................................................................................... 98

Free Text Name in Ready Reference (277482/300283)............................................................................................ 99

Associated Units on the Incident Summary (301188).............................................................................................. 100

Expanded Emergency Alert and Provisioning Options (304674)............................................................................. 104

PremierOne Handheld New Functionality ............................................................................................................... 105

Built-In Queries For Incident, Location, Vehicle, and Person Information (137469)................................................ 105

Other Enhancements ................................................................................................................................................ 105

SQL 2017 Support (302545).................................................................................................................................... 105

ArcGIS 10.6.1 Required for CAD/Mobile/Admin Workstations (315736)................................................................. 105

Ensure That PremierOne Can Handle 2M Location Reports Per Hour (298005).................................................... 106

Move CN Cache to New Windows Service (297439) .............................................................................................. 106

CAD Client Status Monitor and Mapping Optimizations (302817)........................................................................... 106

Primary/Secondary CN Cache Server (Cluster Design) (302821)........................................................................... 106

CAD Client Status Monitor Optimization - Phase 1 (304657) .................................................................................. 107

Contents


Reduce CAD Client Dependency on SQL Server (308019) .................................................................................... 107

Records New Functionality ...................................................................................................................................... 107

Hardware and Software Requirements.................................................................................................................... 107

PremierOne CAD Workstation Specifications.......................................................................................................... 108

PremierOne Mobile Workstation Specifications....................................................................................................... 109

PremierOne Records Workstation Specifications.................................................................................................... 109

Supported PremierOne Handheld Operating System Versions............................................................................... 109

Test Environment ...................................................................................................................................................... 110

Using PremierOne Help ............................................................................................................................................ 111

Open Source Legal Notices...................................................................................................................................... 113

Contents


PremierOne Release Notes Version 4.4


PremierOne Release Notes Version 4.4 1

The PremierOne Suite contains CAD, Mobile, and Records applications.

• PremierOne CAD is used by communications centers to track available resources, information, and hazards, and to dispatch emergency personnel.

• PremierOne Mobile is an advanced mobile communications solution for the public safety industry for law, fire, and emergency units.

• PremierOne Records is an intranet application for storing, retrieving, and analyzing data collected by law enforcement personnel. For details on Records, see the PremierOne Records Release Notes Version 4.4.

Information about PremierOne CAD, Mobile, and Records can be found in the following resources:

• PremierOne CAD User Guide and Online Help

• PremierOne CAD Quick Reference Guide

• PremierOne CAD and Mobile Provisioning Guide and Online Help

• PremierOne Mobile User Guide and Online Help

• PremierOne Reporting Guide

• PremierOne CAD System Tools Portal User Guide

• PremierOne Handheld Installation and Administration Guide

• PremierOne Handheld User Guide

• PremierOne Records System Administrator Guide

• PremierOne Records User Guide and Online Help

• PremierOne Records Mobile User Guide and Online Help

• PremierOne Records Provisioning Guide

• PremierOne Records Administrator Guide

• PremierOne Records Development Guide

• PremierOne Advanced Configuration Tool User Guide

• PremierOne GIS Configuration Guide

• Premier MDC Client Installation Guide

• Premier MDC Client Release Notes

• Premier MDC Client User Guide

• Premier MDC Client Quick Reference

• Premier MDC Message Switch Release Notes

• Premier MDC Message Switch Install Guide



• Premier MDC Message Switch System Administrator Guide

• Remote Administration Module (RAM) Install Guide

• RAM Release Notes

• RAM User Guide

• PMDC online help

• Interface Components Installer (ICI) Release Notes

• ICI Installation Guide

• ATM Mobile (ATMM)

• ATMM User Guide

• ATMM Release Notes

• ATMM Install Guide

• ATMM Configuration Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Support

You can obtain support by phone from Technical Support at 1-800-323-9949.

International customers, call 1-302-444-9800. After you are connected, use the following information to obtain product-specific support.

During regular business hours, your call is routed directly to available technical support personnel. After regular business hours, a 24/7 support engineer is contacted and will immediately return your call. Have the following information ready:

Table 1: Customer Technical Support Phone Tree Path

Products Phone Tree Path

For PremierOne CAD and PremierOne Mobile, and Handheld,as well as PREMIER CAD (PCAD), Managed CAD, Motorola CAD (MCAD), and Friends of CAD

press 2-6-1

For PremierOne Records and Jail, as well as NetRMS, NetCAD, Cruiser, or Evalis

press 2-6-2

For PMDC as well as Airmobile, Text, and Video Surveillance press 2-6-3

For Offendertrak press 2-6-4

For Infotrak (LRMS) press 2-6-5

For CSR 311 press 2-6-6

For Public Engines, Command Central Crime Reporting, TipSubmit press 2-6-7

For all other products, press 2-6-0 press 2-6-0



• Product name and version number

• Description of the problem

• What you were doing when the problem occurred

• Steps you took to try to solve the problem

• Hardware description

• Exact wording of any messages appearing on your screen

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Provisioning and IE

Internet Explorer 11 is now supported for the Provisioning console. Internet Explorer is the only supported browser for Provisioning.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software

This release now requires .NET Framework 4.7.2. As a prerequisite, 3.5.1 must also be installed.

ArcGIS 10.6.1 is now required. Previous versions are no longer supported (287095).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Issues Resolved

Miscellaneous bugs were fixed in this release.

The full list of bugs addressed in this release will be provided by your support representative/Motorola contact in a separate document.

• In Provisioning, an error occurred when accessing Peripherals/GPS. (297839)

• An application exception error occurred on the II screen. (298380)

• In CAD Proactive Recommendations, an exception error occurred when an incident did not have a valid lat/long value. (299517)

• There was a memory leak in the Mobile client. (300146)

• GPS location information sporadically froze because IPChanges caused the GPS device to stop receiving data. (300248)

• In Provisioning, an error occurred when clicking the Next button on the Peripherals/GPS page. (301418)

• In Provisioning, an error occurred when exporting Handheld PRData. (301536)



• CAD became unresponsive and a database error occurred when creating multiple incidents in one transaction. (302250)

• In Provisioning, an error occurred when clicking the “Show Details” button on the Active Plan page a partial active plan. (302380)

• Call Control became unresponsive when transferring a call. (302395)

• The CAD dispatch console went to offline mode and the query plan went bad for the status monitors. (303466)

• Agency Icon updates caused Provisioning to fail when previously uploaded icon paths no longer existed. (304269)

• In Provisioning, an error occurred when editing the Call Control–Incoming Line–Queue page. (304319)

• The CAD client became unresponsive during logout on a Crowd6 Window10 machine. (304830)

• The CAD client became unresponsive with the CACH interface taking over 98% of CPU. (304957)

• The CAD client became unresponsive during logout when Pictometry was opened. (305504, 306545)

• One or more unexpected Provisioning errors occurred on the Status Monitor Display window when clicking Move up. (306602)

• An application exception error occurred on incident dispatch when the recommendation had a second row. (308144)

• The CAD user was unable to create a scheduled incident. (308391)

• CAD became unresponsive and recorded multiple exception errors to the log. (308442)

• In Mobile, the Incident and status screens were not updating. Mobile became unresponsive when attaching a query response in CAD and viewing it in Mobile. (308444)

• The CAD user received the “CAD client stopped working” error during logoff. (308612)

• Mobile became unresponsive for 5-10 minutes during login if ArcGIS is un-authorized. (308883)

• In CAD, an Activate Plan exception occurred when a Unit Assignment conflicted with a Unit Move Up Area. (309441)

• The Mobile user was unable to complete a Field-Initiated incident when no Modifying Circumstances are provisioned for IRF. (310183)

• System slowdown with Long Running Transaction and restart of services occurred on the App Server. (310525)

• Slow performance issues occurred due to the PremierOne_UnifiedCADPruneExpiredIncident SQL job after an upgrade. (311600)

• Unit locations were not current/refreshing on the Mobile maps. (312405)

• CAD positions lost their CAD printers and only showed their local printers when logged into the Dispatcher or Lead role. (313833)

• In Mobile, comment scrolling (Comments tab) caused erratic behavior. (314798)

• In Proactive Recommendations, an exception error displayed when switching work area very quickly in CAD. (315114)



• 4.3 PRData could not be synced into a 4.3 client when over 1000 unit status were provisioned. (315156)

• The CAD client became unresponsive when logging off using the SF command. (315721)

• In CAD, an unexpected application shutdown error appeared while signing off or doing a session transfer. (316611)

• Logging in randomly caused a status monitor error when the Supervisor status monitor pulled over 90,000 records. (316994)

• In CAD, an “Object reference not set” error occurred after dispatching two units. (317423)

• A GDI Exception Error occurred when the CAD user put in a long command line entry with spaces. (317820)

• In CAD, an exception error occurred during session transfer. (317933)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CAD New Functionality

The following CAD features are included in this release. The TFS (Team Foundation Sever) number is included for reference.

Miscellaneous Enhancements

Update CAD Client Logon Screen to Allow User to Enter Device ID (309980)

When the CAD Client Configuration tool is run without a device ID, the CAD Logon form now displays fields for the Device Agency and Device ID. This feature allows for Cloud migration.



Covering Dispatcher Clears All Updated Flags (298368)

When only one user is responsible for an area, it is critical for that user to see and respond to updates to an incident. With this enhancement, when the “controlling user” reviews and responds to an incident update, the Updated flag that displays when an incident has an update is cleared for all other CAD users assigned to or monitoring the incident. This feature introduces the concept of a controlling user, laying the groundwork for providing a meaningful way to direct messages and events to the appropriate user.

This feature required updates to several Provisioning windows, as well as to the CAD Login form.

Figure 1: PremierOne CAD Dispatch Login Dialog Box



In Provisioning, on the Agency window, a new field, Allow only one controlling user per area, was added.

When this field is selected, if a second CAD user with a “controlling user” role tries to cover an area (at login or using the CC command) that is already covered by another controlling user, a message advises the second user that another controlling user is already covering the area(s). The second user can either cancel, or continue to take control of the area from the first user. In this case, the first user is advised that the second user has taken over control of the area(s).

Figure 2: Provisioning–Agency–Agency Window



In the Role Permissions–Roles window, a new field, Controlling Users: All users logged in under this role will control their coverage area(s), was added.

When this field is selected, users with this role are given “controlling user” permission. When the controlling user on an incident has reviewed and responded to an incident update, the Updated flag is cleared for all other CAD users assigned to or monitoring the incident.

Figure 3: Provisioning–Role Permissions–Roles–General Window



On the Incident Management–Coverage Groups–General tab, the Areas section was redesigned to appear as a table with columns for Area, Cover, and Monitor. Each area in the Coverage Group can be provisioned for coverage, monitoring, or both.

The areas selected on the Cover and Monitor tabs display in the Preview Selected Coverage section of the Login window. Areas selected as a Cover area, or as both a Cover and Monitor area, appear with an asterisk (*) next to the area. Areas that are selected only for Monitor display with no asterisk.

Figure 4: Provisioning–Incident Management–Coverage Groups Window



On the CAD client Login form, several changes were made. The Coverage Areas section now contains two tabs: Cover and Monitor. A new field, Working Agency, was added at the lower right of the form.

From the Coverage Groups list, users can now select multiple Coverage Groups, which may contain both coverage areas and/or monitored areas.

The Cover and Monitor tabs enable users to select agencies and areas for coverage and for monitoring. All selections for both covered and monitored areas display in the Preview Selected Coverage area. Areas selected as a Cover area, or as both a Cover and Monitor area, appear with an asterisk (*) next to the area. Areas that are selected only as Monitor display with no asterisk.

The Working Agency list contains all selected Cover and Monitor agencies. Working Agency is the agency used for commands issued by the user.

• The Working Agency is set by default to the Working Agency defined for the selected Coverage Group.

• If multiple Coverage Groups are selected, the Working Agency is set to that of the first Coverage Group selected.

• If the user manually selects agencies (not using coverage groups), the first agency selected from the Agency list is set as their Working Agency.

• The user can also select one of the agencies from the Working Agency list to be their Working Agency.

Figure 5: PremierOne CAD Dispatch Login Dialog Box



Modifications to Verifying an Incident's Jurisdiction within the Field Initiation (FI) Form (305239)

The verification of incident jurisdiction in the FI form was modified to use the following rules:

• Jurisdictional information is only obtained if the following are known:

• A uniquely identifiable On Duty unit

• A verified location

If the jurisdiction cannot be determined based on the Unit and Location values, then jurisdictional information does not display within the FI form.

• Whenever the Unit ID is updated, immediately remove any jurisdictional information in the FI form. If the user tabs out of the Unit ID field, try to obtain jurisdictional information according to the first bullet.

• Whenever the location is updated and becomes unverified, immediately remove any jurisdictional information in the FI form. If the user tabs out of the Unit ID field, try to obtain jurisdictional information according to first bullet.

• If the user submits the form and the jurisdictional fields are blank, re-evaluate the jurisdictional information according to first bullet.

• If jurisdictional information can be obtained based on the first bullet, create the incident accordingly.

• If jurisdictional information cannot be obtained based on the first bullet display the appropriate error.

Remove Unused Tool Icons From the Admin Console (the System Management Tool Portal) (314073)

Icons in the System Management Tool Portal that were not linked to any functionality were removed.

Delta/Compass Broker interface to limit the transactions to ETIX (313617)

This feature modifies the Delta+/Compass Broker interface to only accept the transactions that are sent from ETIX as a source. The transactions received from other sources such as CAPWIN are ignored.

New Option for Automated Incident Notifications (315825)

Previously, an Incident Notification message was sent only upon incident creation when the incident being created matched the “Triggering Criteria” provisioned for the notification message. With this enhancement, incident notifications can also be provisioned to be sent whenever there is an incident update that also matches the provisioned triggering criteria.



In Provisioning, a new option was added on the Notifications–Automated–Incident Notification window. In addition to the two existing radio buttons, Send at the time of incident creation, and Send at the time of initial dispatch, a third option is now available. The Send at the time of incident creation and every time the incident is updated with matching Triggering Criteria option enables the administrator to provision incident notifications to be automatically sent on incident creation as well as anytime an incident update occurs with matching “triggering criteria.”

APCO IntelliComm Interface (297383)

APCO IntelliComm is the replacement for APCO 911Adviser. IntelliComm generally works in a similar fashion as the PowerPhone CACH and Paramount interfaces. IntelliComm is unique in that it is a cloud-based solution that is accessed through a browser. PremierOne is interfacing with version 1.0 of the IntelliComm interface. CSILight v. 3.3.71.0 or higher is required for this interface.

In PremierOne 4.4 this feature has the following limitations:

• Once a CAD incident is created for a discipline (Medical, Fire, or Law), the user cannot change the discipline of the call in Intellicomm. For instance, if a Medical incident is created, the user cannot then request a Fire dispatch from within the same Intellicomm case. CAD will not be able change the discipline nor will it be able to create a new incident for the newly requested discipline.

• Once a call has been started with CAD and Intellicomm, the user should not close the Intellicomm browser or close the associated work area in CAD until the call is complete. At present there is no way of re-establishing the association between the two systems.

Figure 6: Notification–Automated–Incident Notification Window



Transitioning GPS-Equipped Units from Stale to Not Reporting (291111)

A configuration item was added to PremierOne so that GPS-equipped units transition from Stale to Not Reporting after the GPS Failure Notification interval is met. The unit’s state is transitioned if a report is not received in the notification interval or the unit remains in a stale state for the configured interval. The default setting for this is True.

To disable the feature, the GPSTransitionStaletoNotReporting setting must be set to False in the Configuration file. In this case, a GPS-equipped unit is only placed into a Not Reporting state when a report is not received within the Failure Notification interval.

To inform dispatchers of units that are in a Stale or Not Reporting state, the Indicate when recommended GPS-Equipped units are stale or not reporting check box was added. Dispatchers receive a Notification message regarding the unit’s status.

Figure 7: ARL Configuration File



Modifications to the Incident/ReportNumber Display Formats (269605)

Provisioning was updated to allow agencies to 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.

Agencies can now also optionally position various separators (dash, dot, and slash) in the Incident Number or Report Number format. For example, FD-2018-01-01-00000001 (current functionality) could become FD/20180101-001.

The new settings are in the Incident Management–Service Settings–Service Defaults window.

Figure 8: Unit Recommendations–Settings Tab



• Multiple separators cannot be adjacent to each other in the Display Elements in this order list due to potential formatting issues in the CAD and Mobile clients.

• Leading and/or trailing separators are not allowed.

Figure 9: Incident Management–Service Settings–Service Defaults Tab



Cascading Emergency Notification Popups (253473)

Previously, when multiple users pressed the Emergency key at the same time, all the popup windows were stacked on top of each other in CAD so that only one popup window was visible. This made it appear to the CAD user that only one Emergency notification was activated. To avoid this confusion, the CAD client now displays the popup windows in cascading style, with each title bar displaying the Unit ID of the initiator to the CAD user.

Skill Search (SS Command) (159519)

NOTE:

For details on skill search in Mobile, see Skill Search from Mobile (227256) on page 82.

The legacy Premier CAD had a command called Special Skills (SS). It allowed for a search of skills and provided a list of personnel with the skills specified. Until now, there was no equivalent in PremierOne. This feature provides a CAD user the capability to find both on and off duty personnel with a particular skill and provide the user with contact information. Users can perform a skill search using the command line or the Skill Search form.

In PremierOne CAD, a new command, SS (Skill Search) was added. The default command order is: SS.SK<skill(s)>.AG<agency(s)>.SOF<show off duty>.

Figure 10: Multiple Emergency Notifications - Cascading Display



A new tab, Skills, was added to the Incident Recall window in CAD. This tab can be used for entering search criteria, and also displays search results.

To search for personnel skills for the Skill Search form:

1 From the Skills list, select the personnel skill you want to search for. You can select more than one skill.

2 From the Agency ID list, select the agency or agencies you want to search. The default is ALL.

The Agency ID list includes trusted agencies for your use of the SS command.

3 From the Show Off Duty list, select Yes to show off-duty personnel who possess the skill you are searching. To show only on-duty personnel, leave the default of No.

4 Press F12 to begin the search.

The results of your search appear in the results table. Results include the Agency ID of the person with the matching skill(s), their User ID, their name, Unit/Device ID, and all skills associated to that person.

Figure 11: Personnel Skills Search Form



You can click any column heading to sort the results (ascending or descending) by that column.

5 To view the Address Book information for one of the results, you can select the row and then click View Contact, or you can simply double-click the row to open the Address Book entry. You can then use the Address Book information to contact the person with the desired skill(s).

Add Postal City Data Attribute to PremierOne Geodatabase (265818)

Previously, PremierOne GIS supported a single “city” attribute for every Common Place, Street Centerline, 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 can be stored with verified incident locations and then propagated with the incident when other systems/applications, for example, PremierOne Records, are utilizing PremierOne incident data.

When a PremierOne application performs the location verification process utilizing PremierOne GIS, the “Postal City” attribute is now returned with the location verification results

The Postal City attribute is now available for the following:

• 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.

Figure 12: Personnel Skills Search Results



CAD and Mobile now display the “Postal City” when issuing the Location Detail (LD) command. On the CAD Location Detail form, Postal City displays on both the Jurisdiction and Recommendations tabs.

Figure 13: CAD Location Details–Jurisdiction Tab

Figure 14: CAD Location Details–Recommendations



Postal City also displays in CAD when viewing the expanded version of a possible location match during the verification routine.

Figure 15: CAD Location Details–Matching Addresses



In Mobile, the Location Detail window displays Postal City for verified addresses.

Previous Vehicles Check Without Using State (243822)

An option was added to Provisioning so that previous vehicle check disregards the state 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.

A new field, Match only Plate when searching Previous Vehicles, was added to the Incident Management–Service Settings–Search Defaults tab in the Previous Person/Vehicles section for this feature.

Figure 16: Mobile Location Detail Window



Send Information to All Associated Incidents When Appending During Duplicate Check (169583)

Previously, when a CAD user selected an incident from the Potential Duplicates list in the WAA, and then clicked Append To or Add Caller, the information was only sent to the selected incident. This feature, sends this same information not only to the selected incident, but to all incidents associated with the selected incident.

Figure 17: Incident Management–Service Settings–Search Defaults



In Provisioning, a new check box, Include all associated incidents when adding caller or appending information to a Potential Duplicate incident, was added to the Incident Management–Service Settings–Search Defaults window.

When selected, all associated incidents are updated when the CAD user selects Append To or Add Caller during a potential duplicate check. When this field is not selected (unchecked), only the selected potential duplicate incident is updated.

Figure 18: Incident Management–Service Settings–Search Defaults Window

Figure 19: CAD–Potential Duplicates



Display Phone Type Labels in Ready Reference Items (277482)

Ready Reference contacts configured in Provisioning have a label for every phone number associated to the contact. However, when displaying the contact in previous versions of PremierOne CAD or Mobile, only the phone numbers for the contact displayed, and not the labels associated with the phone numbers. With this enhancement, the label associated with each phone number now displays when viewing a Ready Reference contact in CAD and Mobile.

In addition to viewing phone labels in CAD and Mobile, the ability to add or edit these labels when editing or adding Ready Reference contacts in CAD and Mobile was also added. In CAD, when the user clicks the Edit Entry tab, the fields become editable, including a free-text field for editing phone labels.

Figure 20: Ready Reference - Results in WAA

Figure 21: Ready Reference Entry In Edit Mode



The Phone Number “Name” field is 50 characters in length and is a free text field allowing the entry of any alpha/numeric or special characters, and spaces. A value in the phone “Name” field is required when entering a phone number for a Ready Reference contact.

In Mobile, the same enhancement allows users to view or edit the phone name on an existing Ready Reference contact, and to specify a phone name when adding a new Ready Reference contact.

In-Station Alert: Include Full Incident Number and Map Book Information in SMTP Messages(302634)

Previously, when sending incident alerts from CAD using SMTP email messages, only part of the incident number was sent. For example, the message might contain Inc # 00000013, although the incident number in the heading of the message is: APT1800000013. With this enhancement, SMTP In-Station Alert messages include the following information:

• Full Incident Number

• Map Book Name

• Map Book Page Number

• Grid Reference

Lat/Long in Degrees & Decimal Minutes in CAD (176124)

Previously in CAD, the entry and display of Latitude and Longitude could only be done in Decimal Degrees (Decimal) and Degree, Minute, Seconds (DMS) formats. This enhancement allows the user to also enter and display Latitude and Longitude in Degree and Decimal Minutes (DM) format. Three forms that manage lat/long information are impacted by this change:

Figure 22: Ready Reference Address Book New Contact



• Incident Initiation (II) form

• Incident Update (IU) form (also referred to as the IM form)

• Location Detail (LD) form

This enhancement is for CAD only; it does not apply to Mobile or Handheld.

Nothing changes regarding the storage or “behind the scenes” usage/calculations made with latitude and longitude values in PremierOne. The translation of Decimal <-> DMS <-> DM format for display and user entry are all that is affected by this enhancement.

A new radio button, DM, was added to the Location section. When selected, the Lat/Long fields change to allow for entry of Degree and Decimal Minutes format.

CAD Radio Device Alias Synchronization (300197)

This feature provides administrative users of the CAD system and the radio system with the capability to provision the two systems to automatically synchronize radio aliases between the systems. The intention is that as updates are made in one system, those updates are automatically reflected in the other system without the need for intervention by the administrative user.

Figure 23: Location Section Showing DM Fields



In Provisioning, on the Interface–Radio–Radio System Settings screen, a new section called “Alias Synchronization” was added.

To configure radio alias synchronization, the user selects Enable to turn on automatic synchronization of radio aliases between CAD and the radio system, and in the Synch Options field, selects one of the following:

• Send and Receive (Default): Radio Alias updates are both sent and received by CAD.

• Send Only: – CAD only sends alias updates and does not use aliases sent by the radio system.

• Receive Only: CAD does not send alias updates; it only uses updates sent from the radio system.

To create a radio device record in CAD when a record received from the radio system does not exist, the user can select Allow creation of CAD radio device records.

When Allow creation of CAD radio device records is selected, from the Default Device Profile list, the user can select the device profile to use when creating radio device records in CAD.

Field Restrictions for Radio Alias Synchronization

Since the Radio Alias fields for CAD and the radio system differ in the type of characters allowed, the following restrictions apply for the naming of Radio Aliases for the Radio Alias Synch feature to work. Neither system fully enforces these rules, so it will be up to the administrator to keep these rules in mind when creating aliases.

Figure 24: Radios Form – Radio System Settings Tab



The Radio Alias must be:

• No greater than 16 characters

• Composed of upper-case alpha characters and/or numeric characters (A-Z and 0-9).

• Spaces are permitted.

Support for Both CADICAD and Radio Services (309786)

PremierOne now supports both the CADICAD and Radio Services interfaces for receiving notifications from radio systems. The administrator can select ANY ONE system for use at the time of installation.

There is no change in the functionality. The messages that were coming from CADICAD arrive from Radio Services through Websocket.

NOTES:

Radio Services supports GroupCall, EmergencyCall, Affiliation, Deaffiliation, and Status. It does not support PrivateCall and InterconnectCall.

Instructions for configuring and turning on Radio Services can be found in the PremierOne 4.4 Server Software Installation Guide.

Support Modifying Circumstance With QA Software (301191)

When sending information between CAD and a QA application, there is usually a single field that represents an incident type for both systems. Because some agencies want to use CAD’s Modifying Circumstance as well as the Incident Type, this enhancement allows the Provisioning user to map both of these PremierOne CAD fields to a single incident code that can be used within the QA application. Conversely, when the QA application sends PremierOne CAD an incident code containing both pieces of information, the QA incident code must be mapped to populate both the Incident Type and the Modifying Circumstance fields in PremierOne CAD.

NOTES:

– CACH is bi-directional and does not use a sub-code.

– ProQA Paramount is unidirectional and only sends a code to PremierOne CAD. It does not use the sub-code.

– Codes that are not mapped are passed straight through. So, only items that need to be translated need to be provisioned.

– IRF Mapping can also be used to simply change the incident type/code, if the QA system is not using the Modifying Circumstance.

Two new forms were added to Provisioning for performing this Incident Response Factor (IRF) mapping. The IRF Mapping (Inbound) window is used to map a QA incident code and sub-code to a PremierOne CAD Incident Type and Modifying Circumstance. The IRF Mapping (Outbound) window is used to map outbound PremierOne Incident Response Factors (Agency Type, Incident Type, and Modifying Circumstance) to the QA system’s incident code.



Add Current Active Plan Label to the Active Plan Form (301247)

This Provisioning enhancement is intended to mitigate confusion for the user who is attempting to change an agency’s active plan. When an administrator switches the active geodatabase to a geodatabase that contains new beats, all of the current plans in any agency with new beats become “partial plans” (because those new beats do not have area/sector assignments yet). On the Provisioning Active Plan page, the new active plan does not always appear in the Active Plan ID list because the drop-down does not include any partial plans. This could lead the customer to believe that there is not an active plan.

This enhancement adds a new label, Current Active Plan, above the Active Plan ID drop-down list. This field displays the current active plan so that the user does not have to rely on the Active Plan ID drop-down to display the ID of the plan that is currently active.

Figure 25: Interface–QA–IRF Mapping (Inbound) Window

Figure 26: Interface–QA–IRF Mapping (Outbound) Window



Improve IH Display in Orphan History Window (303762)

The display of the Incident History (IH) orphan window was improved for usability. The following changes were made:

• Columns can be sorted

• The window can be resized

• The Filter By label was added

• Multiple orphaned IH windows can be opened simultaneously

• The default size of the window was changed

Figure 27: Active Plan Window



RapidSOS Integration (297285)

In this release, RapidSOS was integrated with Call Control and PremierOne CAD. Rapid SOS is a third-party application that sends location and medical information to CAD systems. The location is based on the GPS coordinates of the phone.

A RapidSOS button was added to the Call Control ANI/ALI window. When selected, the window refreshes to show the RapidSOS information and the map repositions to show the new location. Note that selecting the Rebid button in the RapidSOS window only rechecks the RapidSOS information and not the ANI/ALI information.

In CAD Systems not using the Call Control, the ANI/ALI information displays in the Location field, and the RapidSOS information displays in the Comments field.

A new tab was added to the Resources–Systems window in Provisioning for RapidSOS configuration.

Figure 28: Incident History Orphan Dialog Box

Figure 29: Caller Information Area–ANI/ALI Tab



Additionally, a tab was added to Mapping for RapidSOS icons.

Figure 30: Resources–Systems–RapidSOS Window



Command Enhancements

UL Identifier Added to ID Command (225744)

The UL identifier was added to the ID command. This allows units to be dispatched to a location other than the incident’s location (useful for traffic control). 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.

The UL identifier was also added to Provisioning in the Command Line–Commands window.

NOTE:

Address Verification is not performed when multiple units are specified with the US command that uses the UL identifier.

Figure 31: Mapping–Icons Window



I Identifier Added to II Command - Create Incidents Based on Existing Incident (279009)

The Incident number identifier ( I ) was added to the Initiate Incident (II) command so that new incidents can be created based on an existing incident. All other incidents that reference the original incident are automatically associated with the original incident. The identifier was added to end of the command string.

This is useful when an agency has an incident at one location that results in another incident at a different address, such as a burglary followed by a chase that results in an accident.

Number of units Validation Action

One or more unit IDs If the unit’s location does not have to be validated

Apply {Unit Location} directly to the specified units

One or more unit IDs If the unit’s location must be validated Apply {Unit Location} directly against the specified units

Address Verification is not performed when multiple units are specified with the US command that includes the UL; Identifier

Single unit ID If the unit’s location must be validated AND

{Unit Location} can be uniquely verified

Apply verified {Unit Location} directly against the specified unit

Single unit ID If the unit’s location must be validated AND

{Unit Location} cannot be uniquely verified THEN

Dispatch the unit to the incident’s location, and display the Unit Management Overlay form where the user to verify {Unit Location}



New Fields

Destination for Unit Status Updates (145406)

You can now 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 jail. You add Destinations to a new window 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, an option was added to require a destination.

A configuration item was added for Destination IDs. A location is not required.

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 and agency type levels.

Figure 32: Destination–General Tab



Figure 33: Destination–Settings Tab For Agency Type

Figure 34: Destination–Settings Window For Agency

Figure 35: Unit Management–Unit Status Codes



Add APT Field to Field Initiate Screen (242723)

To maintain consistency with the II and IM form, the Apt field was added to the Field Initiate window. The AP identifier was also added to the FI command and is at the end of the FI command string. The Apt field is included in the verification process but the existing Floor field does not.

The Apt identifier was also added to Provisioning to the Command Line–Identifier window.

Additional Fields in Pager Messages (297226)

Currently within PremierOne, the fields relating to a newly dispatched incident available for inclusion in a paging message are managed within the PR_Pager_Incident_Config table, which resides within the UnifiedCAD database. With this release the following additional fields are available for paging messages:

Incident Field Name Length Comment

City 150 (“CityName” from UnifiedCAD.IM_Incident)

Zip 20 (“ZipCode” from UnifiedCAD.IM_Incident)

Lat 10 (“Latitude” from UnifiedCAD.IM_Incident)

Long 11 (“Longitude” from UnifiedCAD.IM_Incident)

Priority 2 This is the “Priority” associated to an incident. (CurrentPriorityKey in IM_Incident)

Map Book 600 (“MapBookName” (200), “MapBookPageNumber” (200), “GridReference” (200) for incident Location). These fields related to the incident reside in the UnifiedCAD.dbo.IM_MapBook table. Display as <MapBookName>, <MapBookPageNumber>, <GridReference>

All of the 3 fields that make up the MapBook reference = 600.

Caller Name 150 (“Name” (150) from UnifiedCAD.IM_Person table for row.)



Incident Comments

Search Incident Comments From CAD and Mobile IR Forms (262645)

This feature adds the capability to use the Incident Recall form in CAD and Mobile to search for specific words or terms within the comments of an incident. The search functionality includes the use of wildcards for added flexibility, and matching terms are highlighted in the incident comments when the user opens an incident from the list returned by the search.

On the Incident Recall form, a new section called Comments was added.

Figure 36: CAD Incident Recall Form - Comments Section



The following table describes the use of the new search options:

Figure 37: Mobile Incident Recall Form - Comments Section

Table 2: Incident Recall Field Descriptions - Comments Section

Format Description

Search Terms Enter the words you want to search for in incident comments. You can use wildcards (%, _) in your search:

Examples:

• Begins With – %123 returns 123, ABC123, A123

• Ends With – ABC% returns ABC, ABC123, ABC1

• Contains – %BC% returns any word containing BC – ABC123, BC678, 443BC

• Single Character – A_C123 returns A7C123, ABC123, ADC123

Matching search words are highlighted in the incident comments when you open the incident from the list of results.

Exact Returns incidents containing the exact phrase as entered. RED CAR returns RED CAR.

All Incident comments must contain all provided words. Individual words can appear anywhere in the comments. RED CAR could return “A BLUE CAR IN FRONT OF THE RED HOUSE.”

Any Incident comments must contain at least one of the words provided.



When the user opens an incident that is returned by a search, the matching search terms are highlighted in the Incident’s comments:

Figure 38: CAD Incident Comments With Matching Search Terms Highlighted



Copy and Paste Incident Comments From the WAA (271705)

This feature allows the CAD user to select incident comment text from the WAA and paste the text in another window in CAD, a Word document, or any other application. This is useful if the user has accidentally added a comment to the wrong incident, or wants to duplicate a comment in multiple places in CAD, or just wants to copy the text to use for any other purpose.

With the Incident Management window’s Cmnt tab selected in the Work Assist Area, the user can click the comment row that contains the text to be copied, and the text box is selected.

NOTE:

The text box only remains selected while the cursor remains on the comment text. When the cursor is moved off the text, the text box is no longer selected.

The user can click-and-drag to highlight text to copy, and then press Ctrl+C, or right-click and select Copy. In the new location, the user can then press Ctrl+V, or right-click and select Paste to paste the text in the new location.

Figure 39: Incident Management Form–Comment Text Highlighted For Copying



Copy Premise/Hazard Records Into Incident Comments (288144)

CAD users can now add premise/hazard information to the comments of an incident. This is particularly helpful for agencies that use PMDC, since the premise/hazard information is more readily available to the responding units when it appears as a comment.

On the CAD Premise/Hazard Record overlay, a new button, Add as Cmt, was added to the bottom of the window. The CAD user can click this button, or use the ALT + M shortcut, to add the premise/hazard record to the current incident.

If the incident has not yet been created, the premise/hazard information is placed into the Comments field and is submitted when the user submits the form to create the incident. If the incident was already created, the premise/hazard information is immediately added to the incident as a comment. If the user has made other updates to the incident, the user must resubmit the incident to save those changes.

Road Closure Enhancements

Auditing Creation and Clearing of Road Closures (297390)

Tis feature adds auditing of road closure activities and transfer of the data to RDW for reporting purposes. A new Road Closure database table was created to store road closure “Activation” and “Cancellation” audit transactions. This table contains the following attributes:

Figure 40: Premise/Hazard Overlay

Value Description

TransactionType Contains a domain value that indicates whether the audit record is for a road closure Activation or Cancellation.

InsertedTimeStamp The system date/time indicating when the audit record was inserted into the table.



* ClosureName, Scheduled, and Comment were added to the audit table as part of the construction of this feature. However, support for these values will be implemented in future construction.

NOTES:

– Data from this new table is transferred to RDW in the same way as other audit tables. To view this audit data, the user must write a report against the RDW audit table (RST_RoadClosure) using the PremierOne Reporting Tool.

– Expired data from the Road Closure audit table is purged from the PremierOne database in the same way as other existing audit tables. Configuration of the expiration of these audit records must be performed by a Motorola support engineer.

ClosureName* A value indicating the name of the Road Closure. This value is only supported for an Activation transaction and may be blank.

Scheduled* A Boolean value indicating whether the Activation/Cancellation was scheduled.

StreetSegment A value indicating the street segment affected (i.e. 2200-2299 MAIN ST).

Latitude A value indicating the latitude of the road closure point for the street segment.

Longitude A value indicating the longitude of the road closure point for the street segment.

UserId A value indicating the Personnel ID of the user who performed the activation or cancellation.

DeviceId A value indicating the Device ID of the device used to perform the activation or cancellation.

Comment* A comment associated with the activation or cancellation. Length=240 characters.



Road Closure Enhancements - Scheduling and Comments (107913)

Previously, Road Closures took effect immediately after they were submitted and could only be canceled through a manual user action. Also, there was no way to specify a name for a set of closed roads (for example, “Rose Parade Route”) or to add comments specific to the closure. With this enhancement, the CAD and Mobile road closure forms in both CAD and Mobile were modified to support scheduling detailed dates and times for when the road closure should be in effect, assigning a meaningful name to a closure name (for example, “Rose Parade Route”), and the ability to add comments specific to the road closure.

The Road Closure tab in the Map Assist Area now includes new fields for scheduling and adding comments to a road closure.

Figure 41: CAD Road Closure Form



Query Enhancements

Built-In Queries For Incident, Location, Vehicle, and Person Information (137469)

This feature provides the capability for a PremierOne user (CAD, Mobile, Handheld, or the SmartClient) to 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.

Figure 42: Mobile Road Closure Form



Previously, Motorola Solutions field personnel would have to add and configure each of these queries during the process of setting up a new PremierOne system. With this enhancement, the pre-configured P1CAD interface and queries are automatically installed and appear to users in the list of available queries.

Query Response Orphan Window Follow-me Settings (310107)

The CAD user can adjust the orphaned Query Response window to their preference, but previously, the user had to make those adjustments every time they logged in. This feature makes the user settings to the orphaned Query Response window a Follow-me setting, so that the user’s preferences are retained and applied the next time the user logs in.

Query Response Printing (301500)

Previously, when printing query response lists or details, the printed output did not match the view that displayed on the CAD or Mobile client screen. With this enhancement, the printed formatted or raw response list or details are identical to what the user sees on their client display. Three print options are available to the user when printing query responses:

• Selected List View: Prints the selected response item in the WAA.

• Entire List View: Prints all the list view responses in the WAA.

• Entire Details: Prints all details of all the responses, including the header and response sections of the WAA.

Figure 43: CAD–List of Available Queries



CAD Print Options:

Mobile Print Options:

Move Query Building Blocks Configuration to Provisioning (304673)

Previously, to create a query type and its corresponding fields for a non-CommSYS interface, the field team had to create scripts aligning with the interface metadata, and import the details to the PremierOne database. This operation was time consuming and also required some database knowledge to perform. With this enhancement, the field team members or system administrator can use the Provisioning console to import and export the non-CommSYS interface metadata.

In Provisioning, on the Query–Suite Level Setting–Interfaces window, three new buttons were added at the bottom of the Interface panel on the left side of the screen:

Figure 44: CAD Print Options - WAA

Figure 45: Mobile Print Options



• Add Interface: Add a new interface and import a corresponding metadata XML file.

• Update Interface: Import an updated metadata XML file for an existing interface.

• Export XML: Export the metadata XML file for an existing interface to update the metadata for the interface.

Option to Include Query Response Data in RDW (308749)

Previously, CAD sent all query responses to the RDW. An option was added to disable this transmission. This feature adds a new field, QueryResponseAudit, to the CSQuery–Query section of the configuration file, where an administrator can indicate, at the Suite level, whether or not query responses should be sent to the RDW. The default value is true. To send query responses to the RDW, the administrator can change this setting to true.

Figure 46: Query–Suite Level Setting–Interfaces Window

Figure 47: Configuration File–CSQuery–Query



Expand Hot Hit Response Redistribution Options (312418)

Previously, when query hot hit redistribution was turned on, all of the originally received query responses were redistributed to all configured recipients. This enhancement adds a redistribution option to send only the response that triggered the hot hit.

In Provisioning, on the Query–Suite Level Setting–Query Types–Hot Hit tab, two new radio buttons were added to the Redistribute Hot Hit Recipients section. In addition to the option to specify if redistributed hot hits should go to the originator’s agency, sector, area, beat, or My Dispatcher, the administrator can now choose to Redistribute all associated query responses, or only the response that triggered the hot hit.

This feature applies to CAD, Mobile, and Handheld.

Figure 48: Query–Suite Level Setting–Query Types–Hot Hits Window



Add Query Parameters in Query Header (310106)

On the CAD Query Responses tab, new Request field was added to display the query request parameters in the Query Header section where the Summary field displays the query response summary. If the request parameters are longer than two lines, a scroll bar appears for viewing the entire query. Users can also use the Up and Down arrow keys for scrolling.

Expand Multiple Query Responses (173572)

Previously, when multiple query responses were displayed on the WAA, the CAD user could press the “+” button in any of the Query responses to expand the entry. However, if the user attempted to expand another query responses, then the previously expanded item was collapsed. With this enhancement, the user can now expand multiple query responses in the WAA at the same time.

Status Monitor Enhancements

Display <Unit ID>/<Shift ID> in Radio PTT Status Monitor Window (309773)

The unit's Shift ID is now concatenated when displayed on the Radio Push-to-Talk (PTT) status monitor window. The ID displays as UNITID-SHIFTID, such as UNIT1-DAY, UNIT1-EVE, and UNIT1-NIGHT.

Figure 49: CAD Query Responses Tab



Status Monitor Right-Click Enhancements (268516)

With this enhancement to CAD status monitors, Incident and Unit right-click menu functions can now be performed from either an Incident or Unit status monitor. For example, on an Incident status monitor (Incident or CallTaker), the user can right-click on a unit assigned to the incident and the provisioned unit-based right-click menu functions appear and can be performed on that unit. And on a Unit status monitor, the user can right-click on an incident assigned or stacked to a unit and the provisioned incident-based right-click menu functions appear and can be performed for the selected incident.

Previously, the entire row on an Incident status monitor was treated as incident information, and the entire row on a Unit status monitor was treated as unit information. With this enhancement, each “cell,” or column heading in a row is considered individually as containing either incident information or unit information. In the following figure, the information under INC#, STATE, TYPE, or LOCATION is incident-related; right-clicking on any of these cells causes the provisioned incident-based right-click command options to display (as shown). The values under UNIT and STATUS are unit-related; right-clicking on either of these cells causes the provisioned unit-based right-click command options to display.

Figure 50: CAD Incident Status Monitor



To enable this functionality in Provisioning, a new field, Valid to use on, was added to the Status Monitor–Agency Defaults–General Settings tab and to the Status Monitor–Displays–CAD tab. With this field the administrator can indicate whether the right-click command being provisioned should be available for use on Incident information within the status monitor window, Unit information within the status monitor window, or both.

Figure 51: Status Monitor–Agency Defaults–General Settings–Right Click Menu Tab



If the CAD user selects one or more incidents and then right-clicks, only the right-click menu functions provisioned with Valid to use on set to Incident or Both are displayed on the right-click menu. If the CAD user selects one or more units and then right-clicks, only the right-click menu functions provisioned with Valid to use on set to Unit or Both are displayed on the right-click menu.

Status Monitor Profiles Saved at the User Level (149749)

Previously, the DC command was used only by administrators, as a means of setting the basic console display, at the agency level, for all users, workstations, and roles provisioned to use a specific status monitor display. These display sets include status monitors, Call Control main window and status monitors, the map display, the Information Panel, and the CAD client positions.

With this enhancement, 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.

Figure 52: Status Monitor–Displays–CAD–Windows–Rt. Click Menu Tab



Provisioning for this feature is done on the Role Permissions–Roles–General window. A new check box, Manage CAD display configuration settings per user, was added to enable this capability for the selected role.

When Manage CAD display configuration settings per user is selected, a CAD user signed on with that role can arrange their console to their personal preferences, and then perform the DC command to lock the display configuration as they have configured it. As a follow-me setting, the user’s saved personal display configuration will appear for future sessions, from any console, whenever that user signs on to CAD with the same role.

To restore the display configuration from a saved personal configuration to the agency-level configuration associated with the role, the user can type the DC command along with the new RPS (Reset Personal Settings) identifier. Typing DC.RPS;y resets the display.

Because a user might have multiple roles, and an administrator might also be a user (for example, a dispatcher or a calltaker), a user might try to save a personal display configuration when their current logged-in role is administrative. To prevent an unintentional use of the DC command, a dialog box now appears, confirming the user’s intention to save the Display Configuration settings at the agency level.

Figure 53: Roles–General Window



Recommendations-Related Enhancements

Personnel Cross-Staffing (276538)

Personnel cross-staffing is used with the Orion interface and allows a person to be assigned to riding positions on multiple units. The Primary Position is the position that the person is assigned to whenever the person and unit are both In Station. Each person can only be assigned to one Primary Position.

The Primary Position is used for assigning personnel to units when placing the units on duty or updating their personnel assignments. If the unit with the person’s Primary Position is Out of Station, then the person remains on their last assigned unit until the unit with their Primary Position returns to the station.

Personnel are assigned to physical seats that are defined for each unit. Each seat is assigned a riding position and a radio ID. Each seat also identifies whether a personnel assignment is required for the seat for the unit to be considered available. Additionally, a minimum staffing level is defined for each unit.

A person is only allowed to have one “on duty” assignment at a given time.

As part of personnel cross-staffing, the following functionality is supported:

• Receive personnel cross-staffing assignments directly from the Orion Personnel Management System and immediately process the assignments against their respective units.

• Support personnel cross-staffing assignments within unit recommendations.

Only consider recommending units that continue to meet their Personnel Cross-Staffing requirements based on the personnel assignments of other units that are being recommended.

• Apply personnel cross-staffing assignments whenever a unit leaves their Home Station.

Place units that remain In Station into their {Unavailable Due to Cross-Staffing} status whenever they do not meet their Personnel Cross-Staffing Assignments due to the personnel assignments on units leaving their home station.

• Reconcile personnel cross-staffing assignments whenever a unit returns to their Home Station.

Place cross-staffed units that are currently {Unavailable Due to Cross-Staffing} into their {Clear from Unavailable Cross-Staffing Status} whenever they are able to meet their Cross-Staffing requirements due to the personnel assignments on units returning to their home station.

• Display personnel cross-staffing assignments within the CAD client as part of the Station Status form.

Figure 54: DC Confirmation Of Agency Level Change



The following standard Unit History transactions are generated as part of the transaction that causes a Personnel Cross-Staffing unit to leave the station: Transaction Type: UNIT MGMT and Transaction Description: On Duty Assignment Update.

No new provisioning is required for personnel cross-staffing.

Re-evaluating Recommended Units for Additional Capabilities for Reuse (248229)

PremierOne's “Combine With Any Recommended” functionality previously chose a recommended unit for a capability that is provisioned as Combine with Any within a response, regardless of whether another unit was closer. An option was added to Provisioning to re-evaluate a recommended unit for an additional capability within a response, only if it is closer than any other unit with that capability. This helps to ensure that the minimum response requirements for the incident are met.

The following new options were added to Provisioning on the Unit Recommended–Response Card–Incident Response Factor–Response subtab:

• No restriction to proximity of incident – the proximity of the recommended unit to the incident does not matter.

• Must be closest to incident – the unit must be the closest of the recommended units.

Highlight Missing Units From Recommendations (105664)

The CAD Dispatch window was enhanced so that capabilities that could not be recommended are more apparent. The following changes were made to both the Fixed and Preferred forms.

• A line separator was added between the Incident Data and Unit Recommendations section.

• The Dptch List label was changed to: Dispatch Units (Bold Label: Units in normal font)

• The Missing from Rec label was change to MissingCaps (Bold Label: Bold Missing Capabilities)

Figure 55: Unit Recommended–Response Card–Incident Response Factor–Response



• The Capability column heading was changed to Caps.

• The Dispatch Units and Missing Caps labels were aligned with the Incident Number.

• The Missing Caps label is now hidden when no Capabilities are missing from the Unit Recommendations.

Proactive Recommendations (Evaluate Assigned Units set of Recommendable Capabilities) (296655)

This feature determined the required capabilities for all of the pre-arrival units assigned to the incident by comparing their respective working capabilities against the corresponding Response Card capability requirements.

The following were considered:

• Primary Response Card

• Alternate Response Cards

• Complementary Recommendations

• Supplemental Recommendations using the Initial Response

• Supplemental Recommendations using the Secondary Response

Figure 56: New CAD Dptch Units Window



Proactive Recommendations (PR Command) (299589. 299088)

This feature defined the functionality surrounding the PR form and refined the recommendation evaluations required for proactive recommendations.

Proactive Recommendations (Incident-Based Proactive Recommendations) (299197)

The PR (Proactive Recommendations) command permissions implemented in the previous release were reevaluated to determine the appropriate security permissions for the following:

• Executing a PR Command (base and cross-agency security)

• Accepting a Proactive Recommendation by submitting the PR Form (base and cross-agency security)

Proactive Recommendations (Incident+Unit Proactive Recommendations 4.4)

This technical feature refined the recommendation evaluations required for proactive recommendations.

AIO Enhancements (298330)

The following enhancements were made in this release for the AIO (All in One) Install and Upgrade Utilities tool:

• The complexity of the AIO interface was reduced by removing tabs, renaming tabs, combining fields, making groups collapsible, and so on.

• On the PremierOne Client tab, an option was added for updating the PremierOne Error Reporting configuration tool from AIO.

• On the Advanced tab, an additional field was added for a script to run before Client Configuration, the execution of Powershell for scripts was enabled, and an option was added for downloading any files that are used by the scripts.

• On the Advanced tab, two options were added to allow updating of protected Files and Directories; backups are made and restored after the client is installed.

• The Configuration file was modified to handle the patches for prerequisites (.NET Framework, SQL Server, ArcGIS, and Windows Debugging tools).

• The Deployment Device Configuration was modified so that a SubNetIP is now allowed.

• The Map Builder was consolidated into the AIO tool. The following updates were made:

• Zip files are now used for map packages instead of self-extracting packages.

• Map data files are versioned as Data Sets and the map version identification was moved away from the File Name to a Map Set Name. This makes map packages easier to read and makes updates easier.

• The TPK file type was added to support the Mobile Client.

• The DataSet option is by default set to Both.

• Support was added for Mobile client online map data files.



The following changes were made to the AIO Engine:

• The current user can now access SQL Server as part of the admin group check, and if the user is not part of the admin group, the user is added.

• A compatibility check ensures no existing issues might prevent a deployment: both .NET Framework 3.5 SP1 and SQL Express.

• AIO can now de-authorize ArcGIS License and then re-authorize it.

• AIO now allows a machine to be rebooted and have the AIO installation continue after reboot.

• AIO now identifies the map dataset in use and only updates other map datasets when the import setting is “Automatic.”

• AIO now resumes files copying from the UNC (Universal Naming Convention) if network connectivity is interrupted.

• AIO can now use BITS (Background Intelligent Transfer Service) for UNC transfers.

• AIO now stages the download files when deployed from the Deployment Console.

• AIO now requires ArcGIS 10.6.1 and will install the release if it is missing.

• AIO now requires .NET 4.7.2 on Windows 7 and 8.1.

The following changes were made to the Deployment Console:

• The PremierOne patch version can be selected to avoid creating a new package.

• Different installation options can be selected: Prerequisites, PremierOne Client, Client UI Customization, Configuration, Maps, .NET Framework, SQL Server, ArcGIS, Windows Debugging Tools, Scripts, Deployment Agent, PremierOne Error Report.

• AIO packages can be scheduled for deployment.

The following change was made to the CAD and Mobile Deployment Agents:

• The AIO engine can now manage standalone offline deployments, with local presence of the required files.

This behavior allows standalone installations where AIO is used as part of a system preparation for imaged customer machines. In this case, Motorola has defined the PremierOne client installation files in a standard configuration file and the customer provides the configuration files and data.

Other All-In-One Installer Improvements

The Install and Upgrade Utilities, also known as the PremierOne All-In-One Installer (AIO), consolidates the multiple steps required for a CAD or Mobile Client installation or upgrade. Using the PremierOne Deployment Portal with an AIO package, all the tools and files are sent to the client machine to automate the installation.

The following improvements were made:

• Added capability to identify the map dataset in use so incorrect updates are less likely

• Added ability to handle patches for prerequisites in certain situations.

• Added compatibility check to AIO to check that no existing issues prevent a deployment.



• Merged map builder into install and update application.

• Changed pre- and post-script names to be more meaningful to end users.

• Performed resiliency testing.

• Gracefully handle post prerequisite software install reboot scenario.

Import/Export Support

Provisioning now supports the import/export of the following information.

Resource/Device (Radio, Workstation/MDT/Handheld) (308674)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Resource/Device) window in Provisioning.

Workstation/MDT/Handheld Devices (259539)

Provisioning was enhanced so that you can now export Workstation/MDT/Handheld Devices, change the records, and then import the records with the new changes.

Incident Management Coverage Groups, Dispositions, and Incident Type Alias (302469)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Coverage Groups, Dispositions, and Incident Type aliases windows in Provisioning.

Modifying Circumstances, Premise/Hazard Types, and Premise/Hazard (303200)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Modifying Circumstances, Premise/Hazard Type, and Premise/Hazard windows in Provisioning.

Incident Types(298954)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Incident Types window in Provisioning.

IRF (300605)

Provisioning was enhanced so that .xslx files can be imported into and exported from the IRF window in Provisioning.

Jurisdiction (Area, Beat, Location, Sector) (308676)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Jurisdiction window in Provisioning.



Resources (Capability Group, Capability/Skill, Personnel, Vehicle) (307588)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Capability Group, Capability/Skill, Personnel, and Vehicle in Provisioning.

Response Card (301198)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Response Card window in Provisioning.

Unit Management (Riding Position, Unit IDs, Unit Preassignments) (303895)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Unit Management window in Provisioning.

LSM (LSM, LSM Vehicle Make, and LSM vehicle) (310912)

Provisioning was enhanced so that model can be imported into and exported from the LSM window in Provisioning.

Plan Management (310915)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Plans window in Provisioning.

Agency (Trusted) (Permission Set) (311147)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Agency (Trusted) (Permission Set) window in Provisioning.

Contractor Rotation (311148)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Contractor window in Provisioning.

Query (311149)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Agency Level Setting–Agency Interfaces window in Provisioning.

Talkgroups Configuration (311150)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Radio–Talkgroups Configuration window in Provisioning.

Alerting In-Station Record (311151)

Provisioning was enhanced so that .xslx files can be imported into and exported from the Alerting–In-Station Record window in Provisioning.



Limit Data Import and Export (314592)

For security reasons as well as performance, PR Data can now be limited on a client machine to what is necessary for an agency’s operations. This feature enables Admin users to filter the data that gets exported from the server DB and into the client (CAD, Mobile, Handheld) local storage by selected agency/agencies and trusted agencies.

When exporting data from the CAD client’s Tool menu, a popup dialog now appears, providing the user the option to select specific agencies for which to download PR data. By default, All is selected, so that if the user does not want to limit exported data by agency, they can simply press OK or Enter to begin the export.

CAD-to-CAD

Move Send All Local Dispatches and Include All Assigned Units to Provisioning (309339)

Two new tabs were added to Provisioning to the External Systems window to control the messages that are sent from PremierOne to the External System.

The Receiving Messages tab allows users to configure any messages that should not to be sent to the external system; currently only address verification can be configured.

Figure 57: Export CAD PRData Select Agencies To Export Dialog Box



.

The Sending Messages tab allows users to configure the unit assignment data, unit activity data, non-narrative comment entries, and Request for Resource messages that are sent to the external system by PremierOne.

Figure 58: External System–System Identification–Receiving Messages Window



Orion Interface with PremierOne's On Duty Unit Assignment Data (304695)

On Duty Unit assignment data in Provisioning is now sent through the CAD-to-CAD interface in USU (Unit Status Update) messages.

Include Disposition Description in CFS Update Messages (297246)

As part of the Call for Service (CFS) Update message, the disposition description is now included with the disposition code. Disposition codes are agency-specific and not always easily translated to something meaningful for the external system. Providing the description, such as assisted, cited, and arrest made is clearer than a code such as 57, 39 or 42K.

Suppress IDTL Messages for Closed Incidents (298727)

Incident detail transaction (IDTL) messages are no longer sent for closed incidents.

Receiving Child-to-Parent Comments in an IDTL Update Message (300675)

When an IDTL (incident details) message is received and contains a new comment entry for a primary incident, the information is now added to the R2I2 incident.

Figure 59: External System–System Identification–Sending Messages Window



Receiving Parent-to-Child IDTL Update Messages with Radio Channel Updates (300677)

Comment entries are now sent whenever a Parent-to-Child IDTL Update message updates the Radio Channel on a secondary incident.

Receiving Parent-to-Child and Child-to-Child Comment Entries in an IDTL Update Message (300678)

Previously, all IDTL transactions were logged as comments against a secondary incident. During testing it became apparent that the comments did not provide the CAD operators with any operational information and therefore, were very distracting. IDTL transactions are now captured internally and will only add comments to a secondary incident when there is a new comment entry within the IDTL message.

IDTL transactions containing Location and IRF updates will continue to update their respective fields directly.

Receiving R2I2 Requests: Address Verification Process

A hierarchical Address Verification Process was added to R2I2 Requests for more accurate Lat/Long and Jurisdictional information when available: verify location, verify Lat/Long, verify Beat, and then bypass incident.

Receiving R2I2 Responses: Rejected Units Priority Comment (300680)

Whenever a R2I2 (Request for Resource with Incident Information) requested unit is rejected by a foreign agency, a concise Priority Comment message is now sent with the notification. The prefix text R2I2 RESPONSE was deleted from the Priority Comment entry.

Receiving General Notifications: Subject Line Refinement (300685)

The internally-generated Subject line was modified to include the sender’s Agency ID.

Receiving Comment Entries in an R2I2 Request Message (304931)

All comment entries now have the prefix of the submitter’s agency as in {Submitter's Agency ID}: {Comment Text}.

Suppress Priority Comment Notifications for Updates to Associated Incidents (307319)

Priority comment notifications for updates to associated incidents are now suppressed. For secondary incidents, the comment had no meaning to the parent or other child incidents on external systems.

Secondary Incident Not Updated When IDTL Received (310193)

Modifications were made so that secondary incidents are now updating IDTL messages where only beat values are changed.



Include Lat/Long values Within an R2I2 Message (310224)

Latitude and longitude values are now included within R2I2 messages when available.

Add Initial Caller to R2I2 Requests (310257)

The initial caller was added to R2I2 requests.

IM_Call_Association Table Added (311154)

The IM_Call_Association table was added to the RDW. This table contains call control association data.

Security and Login Integration With Callworks and Call Control (297284)

PremierOne was integrated with the backend telephony system of Callworks. After a Callworks user logs on, the PremierOne Call Control window automatically displays and is ready for use. There are no differences in the Call Control window.

To configure use with Callworks, the following tasks must be completed:

• Callworks must be added to the already existing Resources–Systems–911 tab in Provisioning.

• Credentials for each user must be added to the new ECW Credential section in the Resources–Personnel–Authorization window.

• The position ID for each ECW user must be added to the existing Resources–Devices–Workstation window.

Figure 60: Resources–Personnel–Authorization Window

Figure 61: Resources–Devices–Workstation Window



Changes were made to the PremierOne CAD Configuration Tool to support the CallWorks implementation. The ECW URL was added to the Gather Information Common Setting tab and the option IsCallControlECWEnabled was added to the Mode Selection window.

Call Control Support for CCI 1.1 SP2(303826)

When Call Control supports a West-based telephony source, the required A9C telephony device communicates with Call Control using the Call Control Interface (CCI). Each version of CCI has a corresponding schema that defines all messages and their elements. CCI version 1.18 is based on schema 1.10 and CCI version 1.20 is based on schema 1.12.

Support was added for CCI 1.1 SP2 (1.2 specification) so that both CCI 1.1 SP1 and SP2 are supported. The status monitor Window Type Queue now has a new field titled Number of Calls on Hold.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Features

The following new Mobile features are included in this release. The TFS number is included for reference.

Mobile Login Pre-assignments Check Box (105659)

An option can now be added to the Mobile Login window for agencies the use preassigned coverage areas. The Preassigned Coverage Areas check box is checked by default and replaces the need to enter area, sector, beat, or station information. The check box is enabled in Provisioning in the Customization–Mobile UI Customization–Login Options window.

Mobile Login with Personnel Still Assigned to the Unit (265725)

When logging into Mobile, it is possible that another user or crew are still assigned to that unit and logged into Mobile. This can happen in multiple ways and can affect the next login. For example:

• When logging out of Mobile, if the Keep unit on duty in CAD option is selected then the user and crew are still assigned to that unit.

• Also, if Mobile is closed without logging out, the existing user and crew will still be logged in and assigned to that unit.

Figure 62: Simple Login Window



When a user logs into Mobile, and the unit identified during login is still on duty and any of the personnel still assigned to that unit are different than the personnel identified during login, Mobile displays an additional login dialog box. This dialog box allows the user to individually retain or remove the existing or entered personnel assigned to the unit..

• The Logged In Mobile User field shows the user that is currently logged into the mobile device. Selecting the check box keeps them logged into mobile and assigned to the unit. By default, the Logged in Mobile User check box is unchecked.

In order for more than one user to be logged into the same device, the device must be provisioned with Allow concurrent logins.

• The Entered User field is a read only field and shows the user that is attempting to log into the mobile device.

• The Existing Crew field(s) shows the crew currently assigned to the unit. Selecting the check box(es) keeps them assigned to the unit. The Existing Crew fields are read only. Only the corresponding check boxes can be selected.

• The Entered Crew field(s) shows the crew being added to the unit. Selecting the check box(es) assigns them to the unit. The populated Entered Crew fields are read only. Only the corresponding check boxes can be selected.

In some cases, this dialog box also adds one empty field for adding a new user under the Entered Crew section. In one possible case, the new user wants to log off the Logged in Mobile User from the system, but the new user wants to add this Logged in Mobile User as one of the crew members, so the empty field can be used for this purpose.

• The Login button allows the user to continue with the login once the crew assignment changes are made by the user.

Figure 63: Assigned Personnel Login Dialog Box



• The Cancel button on the pop up dialog returns the user to the Simple or Detailed login form depending on which was displayed when first selecting Login.

NOTE:

The personnel assigned to units at the time of the upgrade will not be accounted for with the new crew login process. This process only takes into account login/unit assignments generated after the R4.4 client upgrade.

Mobile Client – Expand Width of Scroll Bars (112793)

With this release, the scroll bar sizes have been increased by 40% to improve usability in a Mobile environment. Drop-down sizes have also been increased to minimize the need for scrolling.

Managing Non-Trusted Agency Incident Assignments (118429)

Previously, when a Mobile user was signed on to a role that did not have trusted agency permissions for the Incident Recall (IR), Unit Status (US), or Incident Update (IU) commands, and was somehow assigned to an incident owned by that agency, the user would receive the error “You do not have permission” whenever they attempted to access the incident.

With this enhancement, a Mobile user assigned to a non-trusted agency incident can now view, update their status, or clear from the incident even without the proper permissions. The Mobile user is prevented from updating the incident, but they are able to manage their non-trusted incident assignment, and clear themselves from that assignment.

Mobile Client Unit Details Tab (123646)

The new Unit Details tab can be provisioned to display in Mobile through the Navigation bar of the Mobile UI Customization Navigation panel of the Customization form in Provisioning. The Unit Details tab displays in the left hand navigation similar to the Persons, Vehicle, and Incident History tabs and shows the number of units assigned to the incident, including associated incidents.

The Unit Details tab displays a list view of all the units of the currently viewed incident, including units of associated incidents.



The association of incidents is only performed in CAD. Mobile has a read-only view to associated incidents. However, Mobile users can add comments to incidents and their associated incidents. To add comments to associated incidents, the Mobile user types the comment into the Comments field of an incident, selects the Add to associated check box below the Comments field, and clicks Submit. If there are no associated incidents, this check box does not display.

Figure 64: Unit Details Tab




This feature provides the capability for a PremierOne user (CAD, Mobile, Handheld, or SmartClient) to 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. For details, see Destination for Unit Status Updates (145406) on page 35.

Expand Hot Hit Response Redistribution Options (312418)

Previously, when query hot hit redistribution was turned on, all of the originally received query responses were redistributed to all configured recipients. This enhancement adds a redistribution option to send only the response that triggered the hot hit. For details, see Expand Hot Hit Response Redistribution Options (312418) on page 49.

Mobile Mapping Toolbar Display (238632)

On laptops that support higher display resolutions, previous versions of the Mobile Map Toolbar buttons appeared quite small and were not conducive for touch-screen use. This feature enlarged the buttons on the Mobile Mapping toolbar (the toolbar running down the left side of the Mobile Mapping client), and also doubled the height and width of the North Arrow/Map Scales tool. To make room for the larger toolbar buttons, some of the existing buttons were removed or moved as follows:

• Scale Bar Toggle (Show Scale Bar/Hide Scale Bar) – Moved to Options menu.

• Lat/Lon Grid Toggle (Show Grid/Hide Grid) – Moved to Options menu.

• Feature Info Tool – Moved to Search For menu.

• Center Map – Removed entirely.

• Clear Mouse – Combined the behaviors of Select and Clear Mouse into one button.



Figure 65: Mobile Mapping Window



Mobile Map Server Side Mapping Services (311671)

Previously, the Mobile Configuration Tool’s IsMobile setting label did not convey a clear understanding of its purpose. This field was renamed to UseLocalGisServiceOnly. Its functionality remains unchanged. In configuration files and parameter backup files, the IsMobile setting name can still be used to represent this setting’s value.

Actionable Premise/Hazard Icon in Mobile Mapping (259479)

Previously, the only way to display premise/hazard information on the Mobile map was to press the Locate on Map button from the Options tab of an Incident screen within the Mobile client. The Map Assist Area then displayed information (including attachment links) about the premise/hazard records associated with the incident location. There was inadequate security surrounding display of premise/hazard information; users were able to see premise/hazard locations from agencies for which the user’s agency was not trusted. Further, the Premise/Hazard layer displayed only dots, without labels or priority identification, and offered no way for the user to interact with the icons to obtain additional information.

This feature adds new premise/hazard icons for the Mobile map. Users now see the locations of premise/hazards on the map based on their role and trusted agency permissions. If a user’s role has not been granted a premise/hazard privilege (Read Only and/or Read/Write), the user cannot see any premise/hazard locations in the Premise/Hazard layer on the Mobile map. If a premise/hazard privilege is included in the Mobile user’s role, the Mobile user only sees premise/hazard locations for their own agency. If other agencies have set up a trusted permission to the Mobile user’s agencies, granting the View Record privilege for premise/hazards, the Mobile user can also see the premise/hazard locations for those agencies.

Figure 66: PremierOne Configuration Tool – Mode Selection Tab



Premise/hazard locations are displayed using one of three triangle icons, which are colored based on their Priority: black for Normal, yellow for High, and red for Critical. If a location contains multiple premise/hazard records, a single icon representing the highest priority record at that location will display. The map scale is configurable to set a zoom level at which the icons become visible on the map.

Hovering over a premise/hazard icon on the map displays a popup with detailed information next to the icon. When the user clicks a premise/hazard icon on the map, the details display in the Map Assist Area, including links to launch any attachments associated with the premise/hazard record. If there is exactly one premise/hazard record at the clicked location and that premise/hazard record has exactly one attachment, the attachment is automatically opened.

Mobile map users have the ability to turn the Premise/Hazard map layer on or off by selecting Search For–Map layers–Premise Hazard from the Action Bar. The user’s preference for showing or hiding the Premise/Hazard map layer is saved as a Follow-me setting.

Icon Priority

Normal

High

Critical

Figure 67: Premise/Hazard Information in Map Assist Area



Static Location and Orientation of Vehicle Chevron on Mobile Map (238635)

Previously, when the Mobile Mapping client was configured to use Windshield View mode, the user’s current location indicator (chevron) displayed near the bottom of the map with a mostly “upwards” orientation, providing a view of what lies ahead of the unit, while the map rotated around it based on the GPS device’s directional bearing. However, the chevron did not remain in a static position. The chevron moved towards the top of the map and, once it entered a configurable buffer at the top of the map, the map panned so that the chevron remained in the center of the map.

Figure 68: Mobile Map–Windshield View



When configured to use True North mode, the map was always oriented so that North was “up” and the user’s chevron rotated to indicate its current directional bearing. As with Windshield Mode, the chevron moved on the map and, once it entered a configurable buffer on any edge of the map, the map panned so that the chevron remained in the center of the map.

This enhancement modifies the Mobile map behavior, allowing the chevron representing the user to remain stationary while the map moves in the background, to avoid driving off the edge of the map, or not seeing the next turn while the chevron displays near the edge of the map.

However, the movement of the ESRI map behind the units in Windshield mode requires the map to continually repaint both the map layer and the label layer, causing a “flashing” effect that can be distracting to the user. To address this problem, support for “tile packages” was implemented. Tile packages are a collection of map images that can be created with ArcGIS Desktop to be implemented for use with the Mobile Mapping client. The tile package comprises a single layer rather than multiple GIS layers, so the rendering of the map moving in the background is smooth and seamless to the user.

Figure 69: Mobile Map–True North View



Currently, the use of tile packages is set using two new fields in the Mobile Configuration Tool. The TilePackagePath_Pro and TilePackageLayerName_Pro fields set the location and the name of the tile package to be used with the Mobile client.

This configuration item might be moved out of the Config Tool to an xml configuration file in the future.

NOTES:

There are several limitations to the use of tile packages that should be weighed against the flashing issue when using standard ESRI maps.

– File size: tile package files can be up to several gigabytes in size--very large for use with a Mobile client.

– Zooming issues: tile packages are created with a pre-defined map scale; when zooming the Mobile map to a scale that does not match the tile package scale, some blurring and/or pixelating of the map can occur.

– Label orientation: because tile packages consist of fixed map images, when rotated, street names and other labels can potentially appear upside-down.

– If the Mobile client is configured for offline and online maps, tile packages are only loaded for offline maps.

Figure 70: Mobile Configuration Tool–Tile Packages



Mobile Client UI Customization by Role (130388)

A role option was added in Provisioning to the Customization - Mobile UI Customization window for provisioning specific roles. To configure a separate display for each role within an agency, select Role on the Provisioning filter page, select the role, and then click OK. Agency Type or Agency can still be selected without selecting a role.

In Provisioning, on each tab of the Mobile UI Customization form, the Clone and Reset buttons are combined into a single Clone and Reset Operations drop-down menu.

After the user clicks one of the Clone Customization drop-down options, a Clone Mobile UI Confirmation Dialog box appears. Both agency and role have multi-select drop-down options. Once the user selects the agency (or agencies) and role(s) combination, and clicks the OK button, a confirmation box appears; the user clicks OK to dismiss the box.

If the user selects one of the Reset Customization drop-down options, a Mobile UI Confirmation Dialog box appears. The user clicks Yes to proceed with resetting Mobile UI tab(s) to the default values or clicks No to cancel the reset operation.

Also, to consolidate Mobile customization, the Status Monitor Color and Status Monitor Display tabs were moved to the Mobile UI Customization configuration item in Provisioning.

Figure 71: Mobile UI Customization Selection

Figure 72: Clone Operations Selections

Clone and Reset Drop-Down Options Description

Clone Customization for Current Tab This option clones only the UI customization settings for the tab that is selected and displayed.

Clone Customization for ALL Tabs This option clones the UI customization settings for all of the tabs and not just the currently selected tab.

Reset Customization for Current Tab This option resets only that selected tab to the default configuration settings.

Reset Customization for ALL Tabs This option resets all Mobile UI customization tabs to the default configuration settings.



Automatic Unit Status Changes (130390)

This feature allows an administrator to provision automatic unit status updates for a PremierOne Mobile computer or PremierOne Handheld device based on telemetry and location information reported by its GPS device. A PremierOne Mobile workstation or PremierOne Handheld device can change from any status to any other status automatically when the provisioned criteria are met. Automatic status update triggers can be based on the unit reaching a certain speed, traveling a specified distance, or arriving at a specified distance from the assigned destination incident or station location. This behavior is only available to units associated with a PremierOne Mobile computer or PremierOne Handheld device that is configured to receive data from an integrated GPS device.

Provisioning options for this feature are on the Unit Management–Unit Status Codes–Unit Status Codes–Properties subtab, where a new section called Automatic Status changes was added at the bottom of the Options section. Administrators can configure an automatic status change from the status provisioned on this tab to the next logical status (for example, Assigned to Enroute), based on the provisioning criteria defined in the fields in this new section.

Figure 73: Provisioning - Status Monitor Color and Status Monitor Display tabs



The Unit Status Codes window’s import/export functionality supports these new settings.

Figure 74: Unit Management–Unit Status Codes–Unit Status Codes Window–Properties Subtab



Field Configurable Logon Form (185387)

A new subtab was added to the Mobile UI Customization window in Provisioning for Logon options for the Mobile client. The tab is split into two sections: Simple Login Form Options and Detail Login Form Options. The Login Options tab does not display for provisioning by roles, but only for provisioning by agencies.

Extended Mobile Client's Follow Me Settings (212949)

When selecting the priority of an email message, the text format settings (font, size, style, color) are Follow-me settings. The next time you log in, your selected settings are remembered.

Figure 75: Mobile UI Customization Window–Login Options Tab

Mobile Priority Mail Options



Skill Search from Mobile (227256)

The personnel skill search operation can be performed from the Mobile client using the existing Incident Recall form. A skill search must be provisioned before it can be performed in Mobile or CAD.

To provision the skill search for a role:

1 In Provisioning, from the navigation panel, select Role Permission, and then select Roles.

2 Click the Permissions tab and then click the Features subtab.

3 Select the role from the Role list to which you want to grant skills search permission.

4 Click View/Modify.

5 Select Commands from the Services list.

6 Select Skill Search command under the Features list.

7 Click Save.

Once provisioned, you can search personnel for specific skills and return a list of personnel with the skills specified.

To search skills:

1 Do one of the following:

• Open the Incident status monitor, and on the Action bar, select Search.

• From any form, type IR and then press Enter.

The Incident Recall window appears.

2 On the Navigation bar, select Skill Search.

Figure 76: Provisioning–Search Skills Command



The Search Skills window appears.

3 From the Skills list, select the personnel skill you want to search for. You can select more than one skill.

From the Agency list, by default, the user's signed on Agency is displayed.

4 The Also include Off-duty units check box is unchecked by default, meaning that the skill search will only include on-duty units. To expand the search to include off-duty units, select the Also include Off-duty units check box.

5 On the Action bar, select Search.

6 To view the results of your search, click Skill Result on the Navigation bar.

Figure 77: Search Skills Window

Figure 78: Skill Result Window



Results include the Unit ID of the unit with the matching skill(s), the unit’s status, the person’s name, the unit’s location, and all skills associated to that person.

7 To view the details for one of the results, you can select the row and then click View on the Action bar, or you can simply double-click the row to open the Unit Details window. You can then use the Unit Details information to contact the person with the desired skill(s).

8 To save the search, on the Action bar, select Save Search.

The saved search displays on the Navigation bar.

9 To return to the Incident Recall window, select the Close Result button on the Action bar.

Time Synchronization for Mobile and Other Devices (238703)

The Mobile client time is synchronized with the server and the CAD client. This time synchronization is required for some important operations, such as unit status change and Incident update for example.

The Mobile client time synchronization can happen multiple times during a day. The Mobile clients are synchronized when logging into the system. The time accuracy can be +/- 500 ms between the PremierOne system and the Mobile client.

Highlight Hot Hit Trigger In Query Responses (257990)

This feature enables CAD and Mobile clients to highlight the provisioned hot hit keywords or text that trigger a hot hit query response. This enhancement will help Mobile users to quickly identify the hot hit response content for evaluating valid hits. For example, if an agency has provisioned the text “Wanted” as a hot hit trigger, then the client highlights this word when it is found within a query response. If multiple trigger keywords appear in the same response, all words are highlighted.

Figure 79: Mobile–Hot Hit Query Response With Keyword Highlighted



The client highlights the hot hit keyword in both day and night modes, and for both formatted and raw responses. If query responses have been configured with different colors in the Response Format Designer, those colors are overridden by the hot hit highlight colors when a hot hit occurs. By default the highlight colors are white text on a red background, but different colors can be configured at the suite level.

Expand Hot Hit Response Redistribution Options - Mobile (312418)

Previously, when query hot hit redistribution was turned on, all of the originally received query responses were redistributed to all configured recipients. This enhancement adds a redistribution option to send only the response that triggered the hot hit. For details, see Expand Hot Hit Response Redistribution Options (312418) on page 49.

Add Postal City Data Attribute to PremierOne Geodatabase - Mobile (265818)

A new Postal City” field now displays on the CAD and Mobile Location Detail window. For details, see Skill Search (SS Command) (159519) on page 16.



Log Incident Views to Incident History (272473)

Some agencies require that an audit record is written every time a user views an incident. This can be used for security purposes as well as for validating workflow. Agencies can now enable this feature in Provisioning to write an audit record to the Incident History every time the incident is viewed in the Incident Management form. This feature was implemented for CAD in version 4.2. This enhancement adds the capability for Mobile and Handheld.

This feature is provisioned on the Incident Management–Service Settings–Service Defaults window. A new check box, Log to Incident History each time an incident record is viewed in CAD was added to enable this logging feature. This window was updated to allow the administrator to enable the functionality for CAD, Mobile/Handheld, or both.

Figure 80: Incident Management–Service Settings–Service Defaults



With this feature enabled, each view of an incident is logged to Incident History. These records can be filtered by the Incident History filter “INC VIEW.”

Figure 81: Mobile Incident Management Form–Incident History



Display Incident Comments on the Mobile Mapping Page (264816)

Previously, when a Mobile user responded to an incident with the Mapping module displayed, the user was unable to see incoming changes to incident comments without toggling back and forth between the Mapping and Incident modules. This presented a potential officer safety issue.

This feature enhances the Mapping module with a new Comments panel on the right side the screen. The Mobile user can view information such as incident type, address, comments, and responding units for the user’s assigned incident without leaving the Mapping screen. The user can display the comments panel using a new Display Comments/Hide Comments toggle button. The state of the Comments panel (displayed or hidden) is saved with the user’s preferences as a Follow-me setting. If a Follow-Me setting has not been saved for a particular user, the panel displays by default.

Figure 82: Mapping Screen With New Comments Panel



The Comments panel is different from the Map Assist area, which is accessed using the expander icon on the right side of the Mapping screen. When both are displayed they appear side-by-side on the right side of the Mapping screen.

Mobile Road Closure Enhancements - Scheduling and Comments (107913)

The Road Closure tab in the Map Assist Area now includes new fields for scheduling and adding comments to a road closure. For details, see “Road Closure Enhancements - Scheduling and Comments (107913)” on page 44.

Display Incident Location on Every Incident Management Tab (269849)

Every incident management tab now displays the incident location right below the Status bar.

Figure 83: Mapping Screen With Comments Panel and Map Assist Area Displayed



Reports Service Button Launches PremierOne Records Mobile (273590)

When provisioned, selecting the Reports Secondary service button on PremierOne Mobile or typing Alt + R launches the mobile records software and the focus changes to the mobile records software. The mobile records software is either PremierOne Records Mobile or a third-party field-based reporting (FBR) application. An auto-sign-on is performed if the user has not already logged into the mobile records software at the time they select the Reports button. PremierOne Mobile can also invoke the mobile records software during offline mode.

Figure 84: Incident Summary Window



The FbrInterfaceConfig tab of the PremierOne Configuration Tool was renamed to FieldBasedReporting and controls whether the PremierOne Records Mobile client or the third-party FBR application is launched when the Reports Secondary service button in the PremierOne Mobile client is selected. The FBRClientPath setting was removed.

Figure 85: PremierOne Configuration Tool - FieldBasedReporting Tab



In the ExternalDataAgent tab of the PremierOne Configuration tool, the IsPOneRecordsEnable field controls whether the Reports Secondary service button on the PremierOne Mobile client is enabled or disabled. If this field is set to false, then the Reports Secondary service button is grayed out and disabled.

Mobile Mapping Tracks Units in Emergency Status Regardless of MUD Settings (276848)

Previously, PremierOne Mobile and PremierOne Handheld prevented the display of a unit-in-emergency on the Mobile/Handheld map if the unit was not included in the provisioned MUD (Multi-Unit Display) settings. With this enhancement, the Mobile or Handheld user can view and track a unit-in-emergency on the Mobile or Handheld map, regardless of whether the unit is included in the provisioned MUD settings.

The pop-up notification dialog box that appears when another Mobile or Handheld unit activates emergency status now includes a Track It button (previously called “Map It”), which, when pressed by the Mobile/Handheld user, causes the icon of the unit-in-emergency to display at the center of the Mobile/Handheld user’s map. The unit-in-emergency’s GPS continues to report the unit’s movement and location

Figure 86: External Data Agent Tab



for as long as the unit remains in emergency status. As part of this enhancement, the frequency of GPS reporting on a unit in emergency status was increased from once every 60 seconds to once every 5 seconds, enabling other Mobile/Handheld users to accurately track the movement of the unit-in-emergency.

If, while tracking one unit-in-emergency on the map, an additional unit or units activate emergency status, and the Mobile/Handheld user selects Track It on the notification dialog box, the additional (most recent) unit-in-emergency displays at the center of the map. The first, and any subsequent units-in-emergency continue to display on the map as long they remain in emergency status.

Expanded Incident Search Criteria (290425)

The Incident Search window was enhanced to include the following fields:

• Under the Date Range tab: time fields were added to enter the start time (format as hh:mm:ss) and the end time (defaults to current time).

• Under the Location Information tab: Area, Sector, and Beat dropdowns were added.

• Under the Incident Information tab: Incident Description drop-downs were added. If a user selects the Incident Code field, then the corresponding Incident Description is selected and vice-versa. Similarly, this behavior also works for the Dispo Code and Dispo Desc fields.

• The Mod Circum field now displays dropdown values based on the Incident type selection.

The Report Number (RP) Command is Available on the Mobile Command Line (290426)

The Report Number command is now available on the Mobile command line with similar functionality as the CAD command line, although Mobile does not support the F10 and F12 function keys. The RP command can be used to manually request a report number using the RP command line parameters; see the PremierOne Mobile User Guide for more information.

Add Priority Comments on Mobile Self-Dispatch (291467)

This enhancement provides an administrator the ability to provision a role so that a priority comment is added to an incident when a Mobile or Handheld unit with that role self-dispatches to an incident that does not have any active units. This is a separate option from the existing option to send a priority comment anytime someone self-dispatches. This is meant to reduce the overall number of self-dispatch notifications.

Figure 87: Emergency Notification From Other User



In Provisioning, on the Role Permissions–Roles–General form, the existing Allow mobile/handheld user to Self-Dispatch field was modified to include a drop-down list with the following three options for generating a priority comment upon self-dispatch.

• Never – No priority comments are written when this role self-dispatches from a Mobile/Handheld client.

• For all Self Dispatches – Every self-dispatch from this role causes a priority comment to be added to the incident.

• Only when the unit is the sole active unit – A priority comment is added to the incident if this role self-dispatches to an incident when no other units are currently active on that incident.

NOTES:

– On a new installation the option defaults to Never.

– On an upgrade:

– If the original box was checked, the option should be set to For all Self-Dispatches.

– If the original box was unchecked, the option should be set to Never.

Figure 88: Roles–General Window–Priority Comment on Self-Dispatch Options



History Enhancement (297878)

There was a performance issue with loading thousands of Incident History records on a Mobile UI screen. This enhancement allows for the initial loading of 200 Incident History records by default, and adds the ability for an administrator to configure the Mobile client to retrieve any number of records, or all Incident History records at once.

Within the ...\MobileClient\config\SystemConfig_Production.xml configuration file (...\Motorola\PremierOne\MobileClient\config\SystemConfig_Production.xml or SystemConfig_Staging.xml or SystemConfig_Training.xml) on every Mobile client, the <IncidentHistoryPageNumber> setting can be changed from its default of “200” to “0,” (which produces the current behavior) or to another specified number of records to retrieve and display at one time.

When displaying less than all Incident History records on the first page, the Mobile client displays “First,” “Last,” and page-numbered links at the bottom right of the form to enable the display of additional records. The pagination-enabling links only appear when the number of Incident History records that exist exceeds the value set for the <IncidentHistoryPageNumber>. This enhancement is intended to activate only for very large incidents. Checking the history of random existing live data reveals that only 0.2% of all incidents exceed 200 Incident History records. Most incidents will not show any change to the Incident History display or behavior.

The Mobile Incident History listing now shows a count of records at the bottom of the listing. This count of the number of records being displayed appears at the bottom of the Incident History list regardless of whether this large-incident pagination is activated.

Figure 89: Mobile Client Incident History - All Records



Add Plate Month to Mobile Traffic Stop Form (172861)

This enhancement adds a Plate Month field to CAD and Mobile vehicle query forms, as well as on the incident management Vehicle form, to support out of state vehicle plate searches. Certain states require a 2-digit month, and this could not be provided from the previous incident management forms. This new “Month” field is for the plate registration expiration month that is displayed on a small sticker in the corner of the license plate. The new field is a two-digit drop-down list with values from 01 to 12. The field is optional, used mainly when running out-of-state queries, so a blank/null value is the default. The user can choose to enter a value from the drop-down list if desired.

In Mobile, the Plate Month field was added to the Traffic Stop incident summary form, as well as the Incident Management Vehicle form:

Figure 90: Mobile Client Incident History - Updated



Display the City on the Dispatch Notification (299171)

With this release, the City is included with the new incident dispatch notification. Local streets can run through multiple cities or suburbs; adding the city ensures that responders understand an incident location.

Modified Incident Summary Form

When a PremierOne Mobile user views an incident, the incident is retrieved and displayed within the Incident Summary form in View mode. All Dispositions that were previously added to the incident are presented to the user under the Incident Info tab. This functionality remains unchanged.

When placed into Edit mode, however, the Incident Summary form previously loaded all Dispositions into data entry fields that were disabled, so that none of the existing Disposition values and corresponding comments could be modified by the Mobile user. In cases where a large number of Dispositions existed on an incident, this caused a delay in the user’s ability to access the form while the Dispositions were populated into the form. And when the form became accessible, the user had to scroll past all of the existing Dispositions to view or edit any of the fields that followed this list of Dispositions.

With this release, the Mobile Incident Summary form’s Edit mode was modified to display cleared units’

Figure 91: Mobile: Dispatch Notification Window

Figure 92: Mobile Incident Summary Form in Edit Mode–Old Format



dispositions and comments more efficiently. The list of existing Dispositions was removed, to improve performance in accessing the form, and to provide the user with an efficient means of reviewing and editing all of the pertinent data available within the Incident Info tab.

Modified Clear Screen

Previously, after executing a large scale incident with around 300 units on it, if all other units were cleared with a disposition, the Clear screen took approximately 11 seconds to display, and when it did, there was no place for the unit to enter their clearing disposition from Mobile. Additionally, the form would not scroll to the bottom so the user could not access the fields to clear their own unit.

With this enhancement, the Mobile Clear screen only displays a maximum of the most recent 10 dispositions logged to the incident. If there are more than ten dispositions entered with the same most recent date/time stamp, any of those most recent dispositions may be selected for display.

When there are more than 10 existing dispositions associated to the incident, the text “You can view all dispositions on the Incident Info tab” below the title text on the “Clear…” dialog displays. When there are ten (10) or less dispositions already associated to the incident, all of the dispositions that are associated to the incident are displayed, and the text “You can view all dispositions on the Incident Info tab” below the title text on the “Clear…” dialog does not display.

Regardless of how many dispositions are displayed on the “Clear…” dialog, the system displays a new disposition’s fields when the dialog initially displays.

Figure 93: Mobile Incident Summary Form in Edit Mode–New Format



Figure 94 shows the new “Clear Incident” dialog in PremierOne Mobile. The three dispositions displayed in the example do not have associated units. If units were associated to these dispositions, the <agencyID>/<unitID> would be displayed to the right of the Disposition field (this is current behavior that remains the same). This example also shows the text “You can view all dispositions on the Incident Info tab” due to there being more than 10 dispositions existing on the incident being cleared by unit DC/MZTEST.

Free Text Name in Ready Reference (277482/300283)

The phone number label associated with each phone number in Provisioning now displays when viewing a Ready Reference contact in CAD and Mobile. For details, see Display Phone Type Labels in Ready Reference Items (277482) on page 24.

Figure 94: Mobile Clear Incident Dialog Box



Associated Units on the Incident Summary (301188)

On the Incident Summary page, the Mobile client displays all associated units in a new field (Associated Units) under the Units field. The display (font color, background color) for associated units is the same as that defined for units on the Status Monitor, Agency Defaults, and Mobile screen. Clicking the hyperlinks associated with the associated units performs the same action as clicking the existing primary Unit ID hyperlinks. The Associated Units field only displays when associated incidents with assigned units exist.

The Mobile client follows the existing incident update process whenever the associated field is updated. For instance, if there is no associated unit ID, then this Associated Units field is hidden. Similarly, if the existing associated incident relationship is removed using the disassociate feature and the viewing incident doesn’t have any associated units, then this field is hidden.

All Associated Incidents are displayed in the existing Inc. Number field. To differentiate the viewing incident from the associated incident(s), the Mobile client displays the viewing incident first in the list of the incidents. Also, the viewing incident font is bold text and the associated incidents are in a normal font. To locate associated units, send messages, or check associated unit history, clicking the hyperlinks associated with the Associated Units will open a pop-up menu as the following figure shows.

Figure 95: Incident Summary - Associated Units Field



The Units Details tab, on the Incident Summary page, displays a list view of all the units of the currently viewed incident including units of associated incidents. Incidents can not be associated or disassociated from Mobile. The association of incidents is only performed in CAD while Mobile has a read-only view to associated incidents. However, Mobile can add comments to incidents and their associated incidents.

Figure 96: Incident Summary - Associated Units Pop-Up Menu



Additional Incident Management Summary Customization (301533)

The Incident Summary window City field can be configured to change the font or increase the font size to aid in making incident location information easier to read. The font and font size for the Units identifier is also configurable. The fonts for units and cities on the Incident Summary page can be changed by modifying the IncidentView.xml file.

To prevent users from having to toggle between multiple windows, configure the Map Page information to be viewable on the Incident Summary window by modifying the IncidentView.xml file.

Map Page information includes the map book name, map book page number, and the grid reference.

To change the font of the City field on the Incident Summary page:

1 If open, close the Mobile client.

2 Open the IncidentView.xml file in a text editor.

Figure 97: Incident Summary - Unit Details

3 Under the  line item, find the <Label Name="lblCityContent"... line item and add the desired font such as Font="Arial, 14pt, style=Bold" or Font="Arial, 20pt" as shown in the following figure.

4 Save and close the IncidentView.xml file.

5 Run the Mobile Client Configuration Tool. For more information, see the Mobile Client Configuration section of the PremierOne Mobile Installation Guide.

To change the font of the Units field on the Incident Summary page:



3 Under the  line item, find the <LinkLabel Name="lblBackUpUnitsContent"... line item and add the desired font such as Font="Arial, 14pt, style=Bold" or Font="Arial, 20pt" as shown in the following figure.



Figure 98: IncidentView.xml File - Changed City Field Font

Figure 99: IncidentView.xml File - Changed Unit Field Font

To make Map Page information viewable on the Incident Summary page:



3 Under the  line item, find the <Label Name="lblMapPage"... line item and set Visible to true as shown in the following figure.

4 Under the same  line item, find the <Label Name="lblMapPageContent"... line item and set Visible to true as shown in the following figure.



Expanded Emergency Alert and Provisioning Options (304674)

A custom audible tone or message can now be provisioned for any emergency alert. The “Emergency has been sent” confirmation window can also be provisioned not to display if desired.

1 In Provisioning, navigate to Unit Management–Settings–Transactions.

2 From the Emergency row, select the status for a unit in emergency status.

Available statuses in this list belong to the Other Activity category of unit statuses.

3 From the Additional Property section, select any of the following additional properties:

• For there to be no indication of emergency status on the activating device, select Silent Emergency.

• To present a confirmation of any unit status change, select Mobile status change confirm.

Figure 100: IncidentView.xml File - Visible Map Page



This applies to any status change and not just emergencies.

• To display the emergency cancellation option, specify how many seconds the alert should be delayed for in the seconds field.

• To sound an audible alert for the emergency notification, select the Audible tone when activating an emergency check box and then click the Browse button and navigate to and select the audible file. Adjust the volume if necessary.

• Select Display “Emergency has been sent” confirmation to display a confirmation window once an emergency has been sent.

• To set how the emergency confirmation occurs for recipients, select a value from the Emergency confirmation type for recipients list: None, Audible, Visible, or Both.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PremierOne Handheld New Functionality

The following enhancements and changes are included in the PremierOne Handheld version 4.4 release.


This feature provides the capability for a PremierOne user (CAD, Mobile, Handheld, or SmartClient) to 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. For details, see Built-In Queries For Incident, Location, Vehicle, and Person Information (137469) on page 45.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Other Enhancements

The following miscellaneous changes and enhancements are also included in this release.

SQL 2017 Support (302545)

PremierOne CAD/Mobile now supports Microsoft SQL Server 2017 Enterprise.

There is a Records prerequisite for 4.3.0. CU02 for suite installations. They cannot update to PremierOne CAD/Mobile 4.4. with a Records client less than 4.3.0 CU 02.

ArcGIS 10.6.1 Required for CAD/Mobile/Admin Workstations (315736)

PremierOne 4.4 requires ArcGIS 10.6.1 to support mapping functionality. This is applicable to ArcGIS Server, ArcGIS Desktop for the Data Import Tools, and ArcGIS Engine Runtime for the CAD client and Mobile client.



Ensure That PremierOne Can Handle 2M Location Reports Per Hour (298005)

ASTRO Infrastructure now requires Enhanced Data Channels by default. Enhanced data increases location data capacity. Third-party applications like PremierOne should expect increased radio location load. In addition, Radio Infrastructure has a new feature that delivers location on PTT. Whenever the PTT button is depressed, a location message is sent.

This feature included the building of a radio traffic simulator to test PremierOne’s ability to handle a location message rate of 2 million messages per hour.

Move CN Cache to New Windows Service (297439)

Previously, the CN cache was included in CS service, but also caused a load on CADS service. This enhancement consolidates all CN cache data, logic, WCF endpoints, and DAL into one new (CN) service. This provides the following improvements:

• Reduces load on CS and CADS services

• Puts all CN code in one VS project

• Eliminates WCF calls to other services (reduced serialization and network load)

• Makes all DAL calls from the same service

• Also supports running services from the command line

• To POC to run this inside a Windows Container

CAD Client Status Monitor and Mapping Optimizations (302817)

This CN data processing enhancement includes the following:

• Optimized CN data storage on CAD Client disk, including optimization of the current CAD Client database schema and optimization of Units and Incidents tables.

• Optimized CN data storage in CAD Client memory, including optimizing CN Data DTO (data transfer objects) and reducing garbage collection, which is CPU-intensive.

• Implemented data caching for PR data, and resolved all SM and Map data in-memory (no DB calls).

Primary/Secondary CN Cache Server (Cluster Design) (302821)

This enhancement reduced SQL Server CPU load caused by CN servers by implementing a primary/secondary CN cache.

The following configuration parameters were added in the GenericClientNotification configuration section to <CNCacheConfig CacheName="CADS">:

• UsePrimaryCache: true/false. Default is false.

If UsePrimaryCache is false, then CADS CN cache works using our current model: Each server gets changes from the database. If this parameter is true, then CN cache servers form a primary/secondary cache cluster.

• PrimaryCacheDetectionTimeout (milliseconds) Default is 2000.



Quickly determines if the primary cache is up, running, and healthy. This timeout must be smaller than the default timeouts set in WCF config. 2 seconds is a good value to start with.

• SecondaryCacheUpdateIntervalFactor. Default is 0.5.

Avoids CADS CN data delays caused by the cache clustering, the secondary cache must update data more frequently than the primary cache, which gets updates from the database. In our model the update interval for the secondary cache is UpdateInterval*SecondaryCacheUpdateIntervalFactor, which by default is 1000*0.5 = 500 ms.

• SecondaryCacheUpdateErrorIntervalFactor Default is 2.0.

If the primary cache cannot be detected in the cluster, then all the servers obtain changes from the database because they do not have another choice, but because the whole idea of this feature is to reduce SQL Server usage resources, the UpdateInterval needs to be increased.

So, if the primary cache is not available, then all CN servers obtain changes from the database with interval UpdateInterval*SecondaryCacheUpdateErrorIntervalFactor.

CAD Client Status Monitor Optimization - Phase 1 (304657)

In the first phase of the CAD Client Status Monitor Optimization initiative, existing queries were optimized.

Client Status Monitor stored procedure parameters that are not related to data retrieval were removed. For example, parameters responsible for data formatting were removed, and the code responsible for data formatting was moved from SQL script to C#.

Additionally, agency/area/route type selectors were also optimized.

Reduce CAD Client Dependency on SQL Server (308019)

Frequent calls to procGetIncidentUpdatesFromHistory were replaced by querying the in-memory cache that is refreshed after a GetChanges call updates the data. The cache is constructed as a dictionary keyed by IncidentKey. The value is a sorted list of incident history time stamps.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Records New Functionality

For a list of enhancements and changes in the PremierOne Records version 4.4 release, see the PremierOne Records Release Notes Version 4.4.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware and Software Requirements

The following sections describe the client hardware and software requirements.

Windows Server Support Tools are needed on the server.

NOTE:

These requirements assume no other software is being run on the workstations. If you are running additional software at the same time, you need additional RAM and/or processing power.



PremierOne CAD Workstation Specifications

• 3.5 Ghz Processor Intel® Xeon® E5-1620 v4 or similar

• 6 GB memory

• Although not needed for the PremierOne client, inclusion of additional memory (example, 16GB) in new workstation purchases is common for future capacity.

• 20 GB available disk space; solid state drive (SSD) required for optimal performance

• 100 Mbit or faster (Gigabit recommended) Ethernet network adapter

• Note that network latency will impact system performance.

• At least one 1024x768+ pixel, 16+ bit color display

CAD Status Monitor windows and maps are resizable, but to ensure consistent user experience the CAD client workbench window has a fixed dimension of either 1024x768 or 1280x1024.

• Three monitors is typical for a CAD position; specific monitor size, quantity, and configuration varies by agency.

• The CAD client workbench window has a fixed dimension of either 1024 x 768 or 1280 x1024. The Call Control window is resizable with a minimum size of 980 x 685.

NOTENOTE:Scaling of the CAD display more than 100% is not supported.

CAUTION:In Windows 10, you can increase the font for outside applications to greater than 100%. Increasing the font to greater than100% will distort the CAD and Mobile displays.

• QWERTY keyboard with 12 function keys

• Microsoft Windows 10 Professional (64-bit recommended); Windows 7 SP1 Professional and Windows 8.1 Professional supported

• Graphics adapter with at least 512MB RAM per monitor, 24-bit capable graphics accelerator, OpenGL v2.0 runtime or higher. Latest available drivers. Shader Model 3.0 or higher is recommended.

• SQL Server Express 2012 SP3 64-bit

• .NET Framework 4.7.1 and above

• ArcGIS Engine 10.6.1 (included with PremierOne CAD client software)

• SQL Server Express 2017 (recommended). SQL Server Express 2016 & 2012 are also supported. CU level supporting TLS 1.2 is required.

NOTES:

Workstation specifications are representative of workstations used in the testing of the latest release of PremierOne software and do not take into account any other applications. Future releases of PremierOne may dictate changes to the workstation specifications. Each agency should consider their own technology replacement lifecycles and policies for specific purchase decisions.

Future versions of PremierOne will no longer support Windows 7 or 8.1, 32-bit client architecture, or pre-2017 versions of SQL Server Express.



PremierOne Mobile Workstation Specifications

“Business grade” tablets with i3, i5 or i7 Intel processors are required.

• 2.6 GHz processor

• 4 GB memory

• 20 GB available disk space

• 1024x768, 16+ bit color display. 11.6” or larger screen recommended

• Usage on devices with alternative resolutions and smaller screens should be tested and screen settings optimized. Example: On a 10.1” WUXGA screen, use a resolution of 1280x800 and a font size of 125%.

• Radio / Wireless communications device, 3G or 4G network

• Standard QWERTY keyboard and Touchpad / Point Stick (or equivalent mouse device)

• Touchscreen optional

• Microsoft Windows 10 Professional (64-bit recommended); Windows 7 SP1 Professional and Windows 8.1 Professional supported

• Graphics adapter with at least 256MB RAM, 24 bit capable graphics accelerator, OpenGL v2.0 runtime or higher. Latest available drivers. Shader Model 3.0 or higher is recommended.

• .NET Framework 4.7.1 and above

• ArcGIS Engine 10.6.1 (Mobile clients with mapping) (included with PremierOne Mobile with Mapping client software)

• Adobe PDF reader (for help files)

• SQL Server Express 2017 (recommended). SQL Server Express 2016 & 2012 are also supported. CU level supporting TLS 1.2 is required.

PremierOne Records Workstation Specifications

For workstation specifications for PremierOne Records, see the PremierOne Records Release Notes Version 4.4.

Supported PremierOne Handheld Operating System Versions

Following are the support operating systems for PremierOne Handheld:

• Android: 4.0.3 - 7.1.1

• iOS: 9.0 - 11.0.3



Test Environment

The following table contains the version levels of third party software and firmware that was used in testing of this release.

Software/Firmware Version

HP DL380G9 SPP version Apr-16

iLO version 4.2.40

For the extremes:

Model number, firmware version, boot version

670, 15.6.2.12, 1.0.2.1

Nimble CS300

Firmware version 2.3.15.0-352557-opt

Fortigate model/version 600D 5.2.5

Windows server version as well as latest update dates

2012 R2, 10/2016

nCache 4.4

IE version 11.0.35

.Net framework version 4.6.01055

Silverlight version 5.1.50709.0

SQL version with patch 11.0.6020.0

SCOM version with patch 2012 R2 (7.1.10226.1239)

CommSys version 2.8.43

Esri version 10.3.4322

CSI version 3.3.0.0



. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using PremierOne Help

Sometimes, the default settings for Internet Explorer prevent a Help file from opening. When a user tries to open the Help system, a message displays and the Help window does not open.

You can follow the instructions in the message and open the initial help screen. However, every selection you make in the Help system will be blocked in a similar manner.

To avoid this problem, you can configure Internet Explorer to allow active content in files. Use the following procedure.

To allow PremierOne Help files to open in Windows:

1 Open Internet Explorer.

2 From the Tools menu, select Internet Options.

The Internet Options dialog box appears.

3 Click the Advanced tab.

The Settings list appears.



Figure 101: Internet Options Dialog Box–Advanced Tab



4 Scroll to the Security section in the list.

5 Click the Allow active content to run in files on my computer check box, and then click OK.

6 Close Internet Explorer.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Open Source Legal Notices

Open Source Legal Notices are posted on the Motorola Solutions Learning Management System:

Motorola Solutions LMS

Search for “Open Source Legal Notices” to access information on open source software used by PremierOne.

Figure 102: Internet Options Dialog Box–Advanced Tab Security Section

https://learning.motorolasolutions.com/

premierone release notes version 4 - ohiogis3.oit.ohio.gov/ziparchives/marcs/map_updates/p1... ·...

Documents