EXHIBIT E – CAD INTERFACE REQUIREMENTS MATRIX
TABLE OF CONTENTS
INFORMATION FOR RESPONDENTS .................................................................................................................................... 1
TABLE OF CONTENTS
Table 1—9-1-1 Interface ........................................................................................................................................... 2
Table 2—CAD-to-RMS .............................................................................................................................................. 3
Table 3—External Alarm Systems ............................................................................................................................ 5
Table 4—Law Enforcement Reporting Systems ........................................................................................................ 6
Table 5—Fire Service Reporting Systems ................................................................................................................ 7
Table 6—CAD-to-CAD Interface(s) ........................................................................................................................... 8
Table 7—Mobile Data Terminals ............................................................................................................................... 9
Table 8—Integrated Mapping .................................................................................................................................... 9
Table 9—Automated Vehicle Location ...................................................................................................................... 13
Table 10—Additional Interfaces ................................................................................................................................ 15
i|Page
INFORMATION FOR RESPONDENTS
The Interface Technical Specifications are provided in the table below and are divided into categories:
 Functionality: High level topical description of the MDT function
 Description: General description of the requirement
 Importance: Rating given by the ECD as to the importance of the requirement as follows:
 At the end of each requirement is a code that describes the importance of that requirement to the
Monterey County Emergency Communications Department (ECD). This code is provided to inform the
respondents of the weighting each requirement is given by the ECD.
 Mandatory – ECD reserves the right to reject any proposal that does not comply with a Mandatory
requirement
 Important – While not mandatory, the requirement is extremely important to the ECD
 Desirable – This function would enhance the overall product or service
 Optional – Optional/Future, not currently a requirement, but would like to have in the future or as an
option
 Compliance: Rating defining whether the respondent complies with the given requirement. The
Respondent provides the Compliance Code, defined below, and may provide additional response to
explain their compliance with the given requirement. If a Compliance Code is not provided, it will be
assumed that the proposal does not comply with the specific requirement.
 Complies – The requirement is met by the Respondent’s existing system and is included in the base
cost of the proposal
 Modification – The requirement requires a modification to the Respondent’s existing system, but is
include in the base cost of the proposal
 Option – The requirement is currently available from the Respondent, but at an additional cost above
the base system

New – the requirement is a new feature for the existing system and can be provided at an additional
cost
 Alternative – the proposed system does not meet the requirement, but an alternative is being suggested
 Exception – the proposed system does not meet the requirement.
Table 1—9-1-1 Interface
9-1-1 Interface
Functionality
Accessing
ANI/ALI
Accessing
ANI/ALI
Formats
Formats
GIS Locations
GIS Locations
GIS Locations
Description
The system shall import and attach/append, automatically or
upon user command, the automatic number information (ANI)
and automatic location information (ALI) from the 9-1-1
Customer Premise Equipment (CPE) to a new event entry
mask.
The system shall enable incoming E9-1-1 ANI/ALI data to be
automatically mapped to corresponding address and phone
data fields based on the Master Street Address Guide (MSAG)
in the event entry mask.
The system shall support all E9-1-1 ANI/ALI formats including
wireline, WPH1 and WPH2, VoIP, and input from Multi-Line
Telephone Systems (MLTS) databases.
The system shall enable the capture of additional fields
captured in the event, including ESN, call type (landline,
wireless), and ANI/ALI tracking ID (if available).
If a physical address is not available, the system shall use GIS
data, if available, to extrapolate the closest geographical
attribute (e.g. address, intersection, common place).
If GIS coordinates are used to determine the caller location,
then the coordinates used to determine the approximate
location shall be mapped to an appropriate field in the event
entry mask.
The radius used to extrapolate the closest geographical
attribute shall be a configurable item within the system.
Importance
Compliance
Mandatory
Enter
Text
Mandatory
Enter
Text
Mandatory
Enter
Text
Mandatory
Enter
Text
Mandatory
Enter
Text
Mandatory
Enter
Text
Mandatory
Enter
Text
Table 2—CAD-to-RMS
CAD-to-RMS Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Basic Interface
Functionality
Description
The system shall allow the user to view and manage data
provided by the RMS from within the CAD application through
a hyperlink or other means.
The system shall ensure that RMS records are fully integrated
with the CAD software.
Full integration shall include automatic, seamless transfer of
critical information between CAD, mobile computing, and
appropriate RMS.
The system shall interface with and be able to send data to
regional law, fire and EMS databases.
The system shall ensure that RMS records functions are
tightly integrated to the proposed CAD system.
The system shall ensure that RMS records functions are
tightly integrated to the proposed Mobile Data Terminal
(MDT) system.
The system, at a minimum, shall support the capture/transfer
from CAD of the following data elements for each CAD event:
 Event number
 Call Back field
 Report number
(date and time)
 Event location
 Free-form text fields
 Event type – initial
 Disposition (unlimited)
 Event type – final
 Time call received
 Caller location
 Time dispatched
 Caller name
 Time first unit
 Alternate call back
responded
number
 Time first unit arrived
 Event priority
 Time first unit cleared
 Time last unit cleared
The system, at a minimum, shall support the capture/transfer
from CAD of the following data elements for each unit logged
on during a day/shift:
 Unit ID
 Vehicle ID
 MDT log in times
 MDT log out times
 Personnel assigned
The system shall support the capture/transfer from CAD of
the following, at a minimum, data elements for each event to
which the unit was assigned:
 Time dispatched
 Time departed for
 Time acknowledged
transport
 Time en route
 Time arrived for
 Time arrived
transport
 User defined milestones
 Time available
(shots fired, in custody, in  Time cleared
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
CAD-to-RMS Interface
Functionality
Basic Interface
Functionality
Description
pursuit, pursuit
terminated)
The system shall provide a mechanism to create, record and
otherwise manipulate a report number (separate from the
CAD incident number) for cross-referencing purposes in the
two systems.
Importance
Compliance
Mandatory
Enter Text
Table 3—External Alarm Systems
External Alarm Systems
Functionality
Alarm Panel
Processing
ASAP
Alarm
Processing
Alarm
Processing
Alarm
Processing
Alarm
Processing
Alarm
Processing
Alarm
Processing
Alarm
Processing
Description
If the PSAP monitors alarm enunciator panels, the system shall
provide a feature where the location of an alarm can be retrieved
by the number displayed on the enunciator panel.
The system shall import (automatically) external alarm data that
conforms to the Central Station Alarm Association (CSAA)
published American National Standard (ANS) Automated Secure
Alarm Protocol (ASAP).
The system shall generate a new pending event upon receipt of
a new alarm notification.
The system shall receive alarm notifications and updates related
to the alarm notification from alarm monitoring companies.
The system shall use the alarm notification data to create an
event without call taker involvement if the address is valid and
minimum required fields have been provided.
The system shall spawn a copy of the event to other agencies, if
applicable.
The system shall process updates from the alarm company as
an update to the event and shown to the telecommunicator
responsible for dispatch operations with an audible and visual
indication that a new update has been received.
The system shall send the appropriate response messages to
each message received from the alarm company and enable
system users to send update messages to the alarm company
operator when additional information is required.
The system shall send an automatic update message to the
alarm company during the progression of the event—when the
primary agency has been dispatched, when the primary agency
has arrived on scene, and when the event has been closed,
including any disposition information reported by the primary
agency that responded.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Table 4—Law Enforcement Reporting Systems
Law Enforcement Reporting Systems
Functionality
State and
National
Criminal
Systems
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Querying
Description
Importance
Compliance
The system shall interface with the State Crime Information
System (CIS) and the National Crime Information Center (NCIC).
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall provide configurable query forms and response
displays and be able to be configured to accommodate different
federal, state and local database protocols.
The system shall provide authorization to perform various
queries, and the ability to read responses definable by the
individual agency and by role to the field level.
The system shall allow users to submit queries either with the
query form or the command line.
The system shall allow users to automatically submit queries for
persons and vehicles as part of other data entry processes, such
as event creation.
The system shall enable the query request type and the
database(s) to be selected from a predefined list, with automatic
narrowing of pertinent databases based on user data input.
The system shall provide intelligent updating of the query forms
based on other CAD forms that contain person or vehicle data.
The system shall provide a capability for entering new information
into the selected external database(s) provided the external
database(s) allow updating.
The system shall provide a method for multiple queries to be
submitted through a single form or command. This is sometimes
referred to as query spawning or cascading.
The system shall make query responses accessible either
through the query response form or from the command line.
The system shall allow users to submit new queries based on
data in the query response to logical links and shall also
reference attachments that are associated with the response,
which can be downloaded and viewed.
The system shall provide the capability to alert
telecommunicators, PSAP supervisors, and street-level
supervisors of “Hot Hit” responses to queries made by officers in
the field, or data run that exists elsewhere in the CAD system (i.e.
in an event).
The system shall provide audible and visual alerts that can be
configured by the system administrator.
The system shall log all queries and their responses (when
permitted) for audit purposes.
The system shall provide the ability to configure alerts for queries
run by unauthorized personnel or devices, as well as the ability to
monitor multiple queries of the same data or specified data.
Table 5—Fire Service Reporting Systems
Fire Service Reporting Systems
Functionality
Description
CAD-to-Fire The system shall provide CAD incident and resource information
RMS interface to the Fire RMS for use in reporting and case management.
The system shall be a data push triggered by definable incident
CAD-to-Fire
elements, such as incident status, incident disposition or manual
RMS interface
submission by a Telecommunicator.
The system shall interface with the Fire records system for the
CAD-to-Fire
retrieval of pre-plan information, fire event information, and
RMS interface
personnel information.
The system shall automatically send pre-formatted data to the
Federal Fire
National Fire Information Reporting System (NFIRS) on a userReporting
defined schedule.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Table 6—CAD-to-CAD Interface(s)
CAD-to-CAD Interface(s)
Functionality
Basic
Functionality
Basic
Functionality
Basic
Functionality
Basic
Functionality
Information
Sharing
Dispatching
Dispatching
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Event
Information
Transfer
Description
The system shall be capable of interfacing with other CAD
systems, regardless of vendor.
The interface shall use a communications network and
interface protocol between the two CAD systems that is
acceptable to both Systems Administrators and CAD vendors.
The interface shall communicate with the opposite CAD
system through one or more TCP/IP socket(s).
Telecommunicators can send messages back and forth to
each other, regardless of active events in the systems.
The CAD systems shall be interconnected so that both
systems have accessibility to the current unit status of all units
within the two systems.
Both CAD systems shall be able to dispatch any available
units in the system.
The host agency Telecommunicator shall receive a notice of
the dispatch.
The ECD shall be able to send new event information to
Telecommunicators at the other dispatch center and vice
versa.
New event information shall include, but not be limited to:
 Unit(s) Dispatched
 Location
 Event type
 Reporting party name
 Mandatory
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall allow unit status changes to be sent to the
opposite CAD system without telecommunicator intervention.
Mandatory
Enter Text
The system shall support each CAD system to be set up with
conversion tables that can translate event types from one
system to the other.
Mandatory
Enter Text
This new event information from one side of the interface
would show up as a dispatched event in the other system.
The CAD systems shall automatically send a confirmation
message to the opposite CAD system that it received the call.
Each agency shall have the ability to decide whether or not to
use or display this information.
The system shall allow both sides of the interface to send
updates related to the event as needed until the event is
terminated.
Telecommunicators shall be able to send and receive
administrative messages (not tied to an incident) to their
counterparts at the other agency.
CAD-to-CAD Interface(s)
Functionality
Event Activity
Message
Format
Description
Event comments entered into an event in one system will be
routed to the appropriate agency, and will appear as additional
comments in the other system’s event as defined by user
agency.
The system shall encode messages using XML version 1.0
defined by the World Wide Web Consortium (W3C).
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Importance
Compliance
Table 7—Mobile Data Terminals
Mobile Data Terminals
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Basic MDT
Functionality
Description
The system shall interface with vehicle and/or remote office
mobile data terminals.
The system shall provide access to MDT functions authorized
to the field level within each function by System Administrators
down to the role level (i.e. a patrol officer may not have access
to some functions that a street sergeant may have).
The system shall be capable of providing silent dispatch
orders to a mobile unit, in addition to providing the unit with
details of the event, pre-plan information, premise history
information, and other types of relevant information.
The system shall enable the mobile unit to: self-initiate
incidents, self-dispatch incidents from a queue, change its
status, query CAD and RMS information, and query local and
national databases (e.g. wanted person checks).
The system shall provide the ability for CAD users to drill down
into the details of summary incident and resource data, and
have the ability to configure what data is displayed, as well as
how it is displayed in terms of layout, font, font size, and
colors.
The system shall provide an integrated mobile mapping client
using the same base map as CAD.
The system shall provide the ability to view real-time AVL data
for user-selected units from the mobile client, and the ability to
interact with the units identified on the map display. The system shall include messaging and other unit-related
functionality.
The system shall interface to Automated License Plate Reader
(ALPR) software.
Table 8—Integrated Mapping
Integrated Mapping
Functionality
Description
Integrated Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Basic Mapping
Functionality
Location
Systems
Interfaces
Location
Systems
Interfaces
Location
Systems
Interfaces
Location
Systems
Interfaces
Location
Systems
Interfaces
Location
Systems
Interfaces
Location
Systems
Interfaces
Description
Each call entry position shall have an integrated mapping
screen.
This screen may appear as a window on the same monitor as
the call entry screen.
The system shall allow the Telecommunicator to zoom in/out
or pan the displayed map to provide the needed map detail.
Upon receipt of a 9-1-1 call or once a location has been
verified, an icon shall be displayed on a mapping screen
showing that location.
The Telecommunicator shall be able to print any map image
displayed on their screen.
The view of the map shall be selecting by a mouse with the
capability of zooming in and out or by entering a street name,
subdivision name, area name, and common place name.
The system shall have the ability to have customization of
AVL units shown on the map by color code.
The mapping display shall display the location of all active
incidents and/or resource availability within the system.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall have a seamlessly integrated computerized
map, which is a digitized map (GIS database) supporting
Tactical Map Display (TMD).
Mandatory
Enter Text
The system shall contain a map-centric TMD, in which the
GIS/map is fully integrated with the CAD system.
Mandatory
Enter Text
In the case of a separate TMD application linked to the CAD
system, the TMD shall support the automatic display of units
as derived from an AVL system.
Mandatory
Enter Text
The system shall integrate with aerial imaging technologies to
provide digital, oblique, aerial imaging.
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall interface with existing GIS.
The system shall link high-resolution aerial photos to mapping
systems; overlay shape files directly on top of both oblique
and/orthogonal images; and, display vector data.
The system shall enable users to obtain measurements such
as distance, height, elevation, and area directly from the 3D
imagery, as well as insert GIS content and other data.
Integrated Mapping
Functionality
Location
Systems
Interfaces
Geofile System
Geofile System
Geofile System
Geofile System
Geofile System
Geofile System
Geofile System
Geofile System
Description
The system shall include geographic data to support, at a
minimum, the following:
 System and boundaries registered to the street center
line in the geofile
 Boundary assignments (i.e. determining the response
zone for each incident) completed in real time by
processing the incident’s X,Y coordinates against the
RCL and boundary files to determine the incident’s
location and response zone
 Parcel-level GIS information, in which the approximate
location of the front door of all the parcels in the state are
stored in the geofile
 Address validation and to determine an incident’s location
 Bulk data uploading
 Weekly data updates
 Metadata
 FGDC standard format feed, like XML
(eXtensibleMarkupLanguage) and KML(Keyhole Markup
Language).
The system shall provide geo-fencing, and add the capability
to establish law enforcement on-the-fly response zones, fire
response areas, ambulance (EMS) response areas, street
networks, and other geographical layers using typical
mapping/GIS tools.
The system shall support valid MSAG names and multiple
“aliases” for street names, intersections, commonplace
names, landmarks, and street or highway route numbers.
The system shall stem geographically sensitive hazards,
dispatch policies, and other system functions from validated
locations.
The system shall initiate a location verification step to add the
coordinates of the incident location to the event and display
an incident icon on the TMD as the event is created.
The system shall make a duplicate event check based upon
the location and/or coordinates of the event, during the event
creation process.
The system shall notify the event entry position via a prompt
and show a list of the potential duplicate(s) if, during event
creation, a potential duplicate event in the area is found.
The system shall have a parameter (modifiable by the System
Administrator) specifying the distance in number of feet or
other unit of measurement, from the location of the incident
for duplicate checking.
The system shall define location databases such as hazards,
general premises information, street closures, and other user
definable databases.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Integrated Mapping
Functionality
Geofile System
Geofile System
Geofile System
Geofile System
Geofile System
Description
The system shall perform a distance search to identify the
existence of location information (e.g. hazards) during the
event creation process.
The system shall support different search distance criteria for
different types of locations.
The system shall support coordinate-based operations; The
system shall be capable of full integration with a GPS-based
AVL system and, the system shall be capable of accepting
named standards driven GPS reporting devices, such as
GPS-enabled smartphones and portable radios.
The system shall allow the System Administrator to be able to
modify parameters.
The system shall allow authorized users to configure their
tactical map display to show jurisdictional boundaries (e.g. city
boundaries) and to display potential valid incident locations by
jurisdiction.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Table 9—Automated Vehicle Location
Automated Vehicle Location
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Description
The system shall seamlessly integrate with the CAD system
and provide detailed, accurate, real- time vehicle tracking.
The system shall include the AVL ID (represented as an alias)
for each unit/user’s status.
The system shall include the indication that AVL is enabled for
each unit on the user’s status window. AVL can also be used
for reporting, messaging, response and alerting functionalities.
The system shall include a visual indication if units displaying
on the map and in the queues are AVL equipped.
The system shall be customizable by the System
Administrator.
The system shall be able to play back a unit’s AVL travel
history and see the unit icon move from location-to-location on
a map window.
The system shall be capable of integrating with the existing
GIS database.
The system shall have other interactive functionalities also
available, such as the ability to create and view unlimited
groups of vehicles.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall provide for an automated alert function.
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall provide for an automated alert for when the
vehicle is out of service.
The system shall provide the ability to determine and modify
all such alerts.
The system shall provide the following information on any unit
suffering loss of GPS signal (e.g. vehicle stopped, vehicle shut
off, loss of network signal, loss of GPS data):
 Last known position
 Time of signal loss
 Time lapse since signal loss
The system shall provide minimal AVL reports that include:
 Complete activity detail for specific date range
 Vehicle last stop/end time for date range
 Exception reports including all events that triggered an
alert
 Vehicle first start/begin time for date range
 Miles per day, stops per day, average and summaries per
vehicle
The system shall pass unit status information to the AVL
system whenever unit status is changed.
Automated Vehicle Location
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Basic AVL
Functionality
Description
The system shall pass any changes in unit location
information to the AVL system if unit location changes are
generated within the proposed system (as opposed to the AVL
navigation system).
The system shall display AVL updates on the map within two
seconds of their receipt from the AVL controller.
The system shall should be able to dispatch the nearest
appropriate unit based on its AVL location using an
appropriate routing engine to make that determination.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Table 10—Additional Interfaces
Additional Interfaces
Functionality
Push-To-Talk
(PTT) Interface
Time
Synchronizatio
n
Communicatio
ns Interfaces
Incident
Numbering
Integration /
Interfaces with
Other Systems
Call-Flagging
National SAR
Initiative
National SAR
Initiative
National SAR
Initiative
National SAR
Initiative
Emergency
Operations
Center
Interface
Emergency
Operations
Center
Interface
Description
The system shall have the ability to import and display the
radio ID (and optionally the officer ID) information to the
Telecommunicator by those keying mobile and/or portable
radios.
Importance
Compliance
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
Mandatory
Enter Text
The system shall have an EOC viewable setting that can be
initiated through a web viewer or license to allow the EOC to
view incidents and units specific to the emergency event.
Mandatory
Enter Text
The system shall allow for incident creation that is within the
area of the incident but be limited to certain incident types
depending on the type of disaster and user-defined type
codes.
Mandatory
Enter Text
The system shall have the ability to interface and synchronize
all servers and CAD workstations with the master time clock.
The system shall accept, depending on agency policy, nondispatch-able incidents across the Internet.
Incidents accepted across the Internet shall be of a general
nature, in which a case (report) number may be needed for
insurance purposes. The case number is generated and
recorded. The incident is recorded in the incidents/events
history database for statistical reporting.
The system shall allow the agency direct access to the
underlying system information stored in the database (ODBC,
FTP, web services) for future interface configuration, as well
as appropriate database and system documentation to
support this access.
The system shall provide a capability to flag a CAD call for
submission as a Suspicious Activity and submit that call to the
agency’s intelligence/counterterrorism unit or designated
Fusion Center.
This interface shall conform to the standards set forth by the
Nationwide Suspicious Activity Reporting (SAR) Initiative (NSI)
and contained in the Functional Standard (FS) Suspicious
Activity Reporting (SAR) Ver. 1.5.
The system shall allow users to flag an event as “suspicious”
with regard to the National Suspicious Activity Reporting
(SAR) Initiative.
The system shall send a “suspicious-flagged” event to an
external application, database, or Law RMS that handles SAR
reporting.
The system shall provide the capability to notify an intelligence
unit/counterterrorism unit when a SAR is submitted.
Emergency
Operations
Center
Interface
The system shall allow for the allocation of certain
apparatus/units that can be managed and dispatched out of
the EOC for a specific event (planned or unplanned) without
negatively impacting the CAD system. It is also preferred that
in this instance, all activities will be manually entered (i.e. the
system will keep track of all apparatus and personnel for both
the agency-wide response and the EOC response area).
Mandatory
Enter Text