CERS_DAR_Reqt_Eval_Matrix_20130227.xlsx
XLSX spreadsheet 61 KB Posted
- Attached to
- CONSOLIDATED EMERGENCY RESPONSE SYSTEM Federal contract opportunity
- Solicitation number
- M67854-13-R-4953
- Issued by
- United States Marine Corps
About this file
M67854-13-R-4953 CERS RFP AMENDMENT 2
View the file
Other files for this federal contract opportunity
Show all 32
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CERS DAR Reqs Eval Matrix
| This is a key subset of specifications of the CERS DAR system. All specifications are located in the Requirements Traceability Matrix and the System Design Specification. These requirements are used for evaluation purposes only. | |||||
| Req ID | Category/Process | Sub-Category/ | |||
| Sub-Process | Priority | Requirement | Bidder's Response | ||
| (Please Select One) | Brief Description for Responses of Value 'A' or 'M' | ||||
| DAR-001 | Dispatch | Availability | T | The system shall exhibit a single installation system operational availability (Ao) of 99.7 percent as measured annually. | |
| DAR-002 | Dispatch | Availability | T | The system shall have an installation level system materiel availability of 97.5 percent as measured in a 24 hour period. | |
| DAR-003 | Dispatch | Availability | T | The system shall have an Uninterrupted Power Supply (UPS) of sufficient capacity to provide continuous operations when the facility cuts over from line power to back-up power. | |
| DAR-004 | Dispatch | CAD | T | The system shall auto-populate E911 ANI/ALI information into specified fields on the incident initiation form. | |
| DAR-005 | Dispatch | CAD | T | The system shall accept ANI/ALI electronically from the E911 CPE. | |
| DAR-006 | Dispatch | CAD | T | The system shall automatically initiate an event from received ANI/ALI. | |
| DAR-007 | Dispatch | CAD | T | The system shall store incident records. | |
| DAR-008 | Dispatch | CAD | T | The system shall provide resource recommendations based on available units. | |
| DAR-009 | Dispatch | CAD | T | The system shall provide GIS-based mapping. | |
| DAR-010 | Dispatch | CAD | T | The system shall automatically identify correct response jurisdictions 85 percent of the time when caller information is entered. | |
| DAR-011 | Dispatch | CAD | T | The system shall have the ability to support multiple Emergency Services department response to a single incident without having to recreate the incident record for multiple agencies. | |
| DAR-012 | Dispatch | CAD | T | The system shall have the ability to record information as an incident at the time of initiation. | |
| DAR-013 | Dispatch | CAD | T | The system shall allow for the addition of narrative/comments. | |
| DAR-014 | Dispatch | CAD | T | The system shall associate the source of the call to the incident record (i.e., phone call, field initiated). | |
| DAR-015 | Dispatch | CAD | T | The system shall support field-initiated incidents from a dispatcher. | |
| DAR-016 | Dispatch | CAD | T | The system shall support the definition of an unlimited number of incident types in the incident type database. | |
| DAR-017 | Dispatch | CAD | T | The system shall allow the user the ability to select an incident type from a drop-down menu. | |
| DAR-018 | Dispatch | CAD | T | The system shall validate user-entered incident type against the incident type database. | |
| DAR-019 | Dispatch | CAD | T | The system shall provide a pick list of incident type codes in the event that the system cannot locate the manually entered incident type in the incident type database. | |
| DAR-020 | Dispatch | CAD | T | The system shall allow the user to enter the incident priority. | |
| DAR-021 | Dispatch | CAD | T | The system shall support multiple user-defined premise information databases that are automatically searched and generate alerts to the user if new incidents occur and a match is found in the premise information file. | |
| DAR-022 | Dispatch | CAD | T | The system shall differentiate premise information alerts that occur in exact incident location. | |
| DAR-023 | Dispatch | CAD | T | The system shall have the option of searching all calls, open and closed, for a duplicate check. | |
| DAR-024 | Dispatch | CAD | T | The system shall display potential duplicate matches to the incident being entered. | |
| DAR-025 | Dispatch | CAD | T | The system shall search both open and closed incident records. | |
| DAR-026 | Dispatch | CAD | T | The system shall display user-defined instructions to the dispatcher for certain incident types (e.g., Emergency Medical Dispatch protocols, call handling guides). | |
| DAR-027 | Dispatch | CAD | T | The system shall support incident creation from an integrated mapping application via a point-and-click method. | |
| DAR-028 | Dispatch | CAD | T | The system shall be able to support multi-jurisdictional incidents. | |
| DAR-029 | Dispatch | CAD | T | The system shall have the ability to clone (or copy) incidents. | |
| DAR-030 | Dispatch | CAD | T | The system shall allow a dispatcher to override the automatic system routing. | |
| DAR-031 | Dispatch | CAD | T | The system shall send an audible tone to the dispatcher when an incident enters the pending queue. | |
| DAR-032 | Dispatch | CAD | T | The system shall support the ability to dispatch additional units to an incident from a command line, available unit list, or incident map. | |
| DAR-033 | Dispatch | CAD | T | The system shall display dispatch resource recommendations based on AVL data of available units in the response area of the incident. | |
| DAR-034 | Dispatch | CAD | T | The system shall display dispatch resource recommendations based on AVL data of unavailable units in the response area of the incident. | |
| DAR-035 | Dispatch | CAD | T | The system shall visually identify unavailable units to indicate that they are busy but recommendable. | |
| DAR-036 | Dispatch | CAD | T | The system shall be capable of dispatching recommended units to an incident with a single keystroke. | |
| DAR-037 | Dispatch | CAD | T | The system shall support alternate dispatch recommendations for different types of crisis modes (i.e., severe weather, special events and others). | |
| DAR-038 | Dispatch | CAD | T | The system shall allow a dispatcher to dispatch an enroute responding unit to another incident of higher priority. | |
| DAR-039 | Dispatch | CAD | T | The system shall flag an incident when placed in a pending status indicating that it was previously dispatched. | |
| DAR-040 | Dispatch | CAD | T | The system shall track times for each assigned unit. | |
| DAR-041 | Dispatch | CAD | T | The system shall display incident information. | |
| DAR-042 | Dispatch | CAD | T | The system shall update incident information when provided. | |
| DAR-043 | Dispatch | CAD | T | The system shall not limit the number of authorized users that may review an incident. | |
| DAR-044 | Dispatch | CAD | T | The system shall not limit the number of updates to an incident by authorized users. | |
| DAR-045 | Dispatch | CAD | T | The system shall alert the user when updated information is added to an incident. | |
| DAR-046 | Dispatch | CAD | T | The system shall allow a user to clear the alert after reviewing the update. | |
| DAR-047 | Dispatch | CAD | T | The system shall display incidents by defined areas. | |
| DAR-048 | Dispatch | CAD | T | The system shall be able to display active/pending incidents by Emergency Services departments. | |
| DAR-049 | Dispatch | CAD | T | The system shall be able to display active/pending incidents by incident status. | |
| DAR-050 | Dispatch | CAD | T | The system shall maintain timers for each dispatched incident. | |
| DAR-051 | Dispatch | CAD | T | The system shall alert the dispatcher if the incident has exceeded predefined required action times. | |
| DAR-052 | Dispatch | CAD | T | The system shall provide incident timers based on the priority of the incident. | |
| DAR-053 | Dispatch | CAD | T | The system shall allow incident timers be configurable by the system administrator. | |
| DAR-054 | Dispatch | CAD | T | The system shall support a function to acknowledge timers for incidents that have timed out. | |
| DAR-055 | Dispatch | CAD | T | The system shall allow users to recall on-scene units from an existing incident and dispatch those units to a higher priority incident. | |
| DAR-056 | Dispatch | CAD | T | The system shall allow for the display of incident search results on the map. | |
| DAR-057 | Dispatch | CAD | T | The system shall support attaching the content of a TDD conversation to an incident record. | |
| DAR-058 | Dispatch | CAD | T | The system shall respond to the initial dispatch by automatically date/time stamping the dispatch actions in the incident history. | |
| DAR-059 | Dispatch | CAD | T | The system shall attach results of any query made through the system RMS to the system incident. | |
| DAR-060 | Dispatch | CAD | T | The system shall assign priority levels based on incident type. | |
| DAR-061 | Dispatch | CAD | T | The system shall allow users to override the priority level incident creation. | |
| DAR-062 | Dispatch | CAD | T | The system shall have the ability to transfer control of an event from one dispatch workstation to another. | |
| DAR-063 | Dispatch | CAD | T | The system shall allow dispatching of multiple units at the same time. | |
| DAR-064 | Dispatch | CAD | T | The system shall allow tracking of multiple units at the same time. | |
| DAR-065 | Dispatch | CAD | T | The system shall allow changing multiple unit status at the same time. | |
| DAR-066 | Dispatch | CAD | T | The system shall allow the Emergency Services departments to define time allowed in a status. | |
| DAR-067 | Dispatch | CAD | T | The system shall include the following status details for units: available, dispatched, en route, arrived, administrative, out-of-service, off-duty and any other user-defined status. | |
| DAR-068 | Dispatch | CAD | T | The system shall alert the user when any unit has exceeded a prescribed maximum response time. | |
| DAR-069 | Dispatch | CAD | T | The system shall assign a timer as defined for a unit put into a particular status. | |
| DAR-070 | Dispatch | CAD | T | The system shall allow for a unit to be assigned to more than one incident. | |
| DAR-071 | Dispatch | CAD | T | The system shall have the ability to add special notes to addresses (e.g. gate code, elderly male at location with health problems send medical when responding, associated with gang members, etc.) that highlight prior calls for service to that location. | |
| DAR-072 | Dispatch | CAD | T | The system shall have text messaging capabilities at the workstations for purposes of texting between workstations or mobile units. | |
| DAR-073 | Dispatch | CAD | T | The system shall support the creation of dynamic messaging groups (i.e., when users sign on, the system shall determine what groups they are members of, based on rules that are managed by the system administrator). | |
| DAR-074 | Dispatch | CAD | T | The system shall provide an integrated map to display geographic information on the Dispatch Workstation. | |
| DAR-075 | Dispatch | CAD | T | The system shall generate an alert to the dispatcher for previous incidents that have occurred at the incident location. | |
| DAR-076 | Dispatch | CAD | T | The system shall check for duplicate incidents once the location has been verified. | |
| DAR-077 | Dispatch | CAD | T | The system shall be capable of monitoring audible alarms and sensors data. | |
| DAR-078 | Dispatch | CAD | T | The system shall display integrated alarm and sensor data on the map no greater than 30 seconds after alert. | |
| DAR-079 | Dispatch | CAD | T | The system shall receive and display AVL data with refresh no greater than 30 seconds while vehicles are in motion under normal operation. | |
| DAR-080 | Dispatch | CAD | T | The system shall provide visual indicators that include a counter showing the number of messages that have not been viewed. | |
| DAR-081 | Dispatch | CAD | T | The system shall flag an incident in a pending status indicating that it was previously dispatched. | |
| DAR-082 | Dispatch | CAD | T | The system shall be capable of transmitting an alert that provides recall notification to First Responder personnel. | |
| DAR-083 | Dispatch | CAD | T | The system shall provide an audible alert to a mobile client for First Responder notification 95 percent of the time. | |
| DAR-084 | Dispatch | CAD | T | The system shall send updates to and from the remote CAD terminal in no more than 2 minutes 95 percent of the time regardless of activity at the remote CAD terminal. | |
| DAR-085 | Dispatch | CAD | T | The system shall support user-defined windows for dynamically updated views of ongoing incident. | |
| DAR-086 | Dispatch | CAD | T | The system shall support user-defined windows for dynamically updated views of unit activities. | |
| DAR-087 | Dispatch | CAD | T | The system shall display active/pending incidents by area. | |
| DAR-088 | Dispatch | CAD | T | The system shall display active/pending incidents by incident status. | |
| DAR-089 | Dispatch | CAD | T | The system shall allow the unit status monitor to be user-definable. | |
| DAR-090 | Dispatch | CAD | T | The system shall allow a dispatcher to bring up two incidents simultaneously in a split screen format. | |
| DAR-091 | Dispatch | CAD | T | The system shall allow a dispatcher to display incidents onto one or many monitors. | |
| DAR-092 | Dispatch | CAD | T | The system shall use color to enhance status recognition. | |
| DAR-093 | Dispatch | CAD | T | The system shall use textual information to enhance status recognition. | |
| DAR-094 | Dispatch | CAD | T | The system shall be configurable to display incident number (if unit is currently assigned). | |
| DAR-095 | Dispatch | CAD | T | The system shall be configurable to display unit location information. | |
| DAR-096 | Dispatch | CAD | T | The system shall be configurable to display address or latitude/longitude of the unit location. | |
| DAR-097 | Dispatch | CAD | T | The system shall be configurable to display area(s) in which the unit is currently working. | |
| DAR-098 | Dispatch | CAD | T | The system shall be configurable to display unit timers. | |
| DAR-099 | Dispatch | CAD | T | The system shall be configurable to display active incidents. | |
| DAR-100 | Dispatch | CAD | T | The system shall be configurable to display incident type. | |
| DAR-101 | Dispatch | CAD | T | The system shall be configurable to display incident location. | |
| DAR-102 | Dispatch | CAD | T | The system shall be configurable to display vehicles dispatched to the incident (by dispatch level with the dispatch time for each). | |
| DAR-103 | Dispatch | CAD | T | The system shall be configurable to display unit status. | |
| DAR-104 | Dispatch | CAD | T | The system shall have the capability to display units for a specific zone. | |
| DAR-105 | Dispatch | CAD | T | The system shall have the capability to display units for a specific Emergency Services department. | |
| DAR-106 | Dispatch | CAD | T | The system shall have the capability to display units for a prescribed area. | |
| DAR-107 | Dispatch | CAD | T | The system shall have the capability to display pending incidents for a specific zone. | |
| DAR-108 | Dispatch | CAD | T | The system shall have the capability to display pending incidents for a specific Emergency Services department. | |
| DAR-109 | Dispatch | CAD | T | The system shall have the capability to display pending incidents for a prescribed area. | |
| DAR-110 | Dispatch | CAD | T | The system shall have counters that display the current number of pending and active incidents for the area being tracked at that time. | |
| DAR-111 | Dispatch | CAD | T | The system shall have counters that display the current total number of incidents for the area being tracked at that time. | |
| DAR-112 | Dispatch | CAD | T | The system shall allow users to dispatch new incidents immediately or placing them in the pending queue. | |
| DAR-113 | Dispatch | CAD | T | The system shall support the use of color to differentiate priorities in the pending queue. | |
| DAR-114 | Dispatch | CAD | T | The system shall allow users to search a location using a complete street address. | |
| DAR-115 | Dispatch | CAD | T | The system shall allow users to search a location using a landmark name. | |
| DAR-116 | Dispatch | CAD | T | The system shall have the ability to add procedures to addresses (e.g. gate code, elderly male at location with health problems send medical when responding, associated with gang members, etc.) that highlight prior calls for service to that location. | |
| DAR-117 | Dispatch | CAD | T | The system shall be capable of monitoring visual alarms and sensor data. | |
| DAR-118 | Dispatch | CAD | T | The system shall be capable of monitoring text alarms and sensor data. | |
| DAR-119 | Dispatch | Display Wall | T | The system shall be interfaced into the display wall monitors so that any incoming telephone calls will automatically mute the monitor with the ability to manually override the automated ability. | |
| DAR-120 | Dispatch | E911 | T | The system shall accurately display Automatic Number Identification (ANI)/ Automatic Location Identification (ALI). | |
| DAR-121 | Dispatch | E911 | T | The E911 CPE shall interface electronically with the CAD. | |
| DAR-122 | Dispatch | F&ES RMS | T | The system shall provide an interface to the current approved USMC Fire & Emergency Services RMS vendor. | |
| DAR-123 | Dispatch | F&ES RMS | T | The system shall be able to configure the F&ES RMS interface data transfer interval. | |
| DAR-124 | Dispatch | F&ES RMS | T | The system shall transfer data to the F&ES RMS service starting data transfer no greater than three (3) minutes after an event is recorded. | |
| DAR-125 | Dispatch | FSA | T | The system shall notify F&ES personnel of emergencies from the dispatch center via Fire Station and EMS Alerting. | |
| DAR-126 | Dispatch | FSA | T | The system shall provide audible announcement to PA system no greater than 30 seconds from initiation. | |
| DAR-127 | Dispatch | FSA | T | The system shall provide audible announcement to radios no greater than 30 seconds from initiation. | |
| DAR-128 | Dispatch | FSA | T | The system shall provide audible alerts in ramped heart saver tones no greater than 30 seconds from initiation. | |
| DAR-129 | Dispatch | FSA | T | The system shall provide amplitude lighting into the fire station no greater than 30 seconds from initiation. | |
| DAR-130 | Dispatch | FSA | T | The system shall provide a digital resource display board (scrolling marquee). | |
| DAR-131 | Dispatch | FSA | T | The system shall provide a digital light status bar. | |
| DAR-132 | Dispatch | FSA | T | The system shall provide rip and run printers for incident and route information. | |
| DAR-133 | Dispatch | FSA | T | The system shall allow for zoning of audible and visual alert notification. | |
| DAR-134 | Dispatch | FSA | T | The system shall provide audible announcements from defined message format to follow initial audible alert. | |
| DAR-135 | Dispatch | FSA | T | The system shall provide text to speech announcements from defined message format to follow initial audible alert. | |
| DAR-136 | Dispatch | Logging and Recording | T | The system shall be capable of storing and retrieving two-way TDD/TTY conversations. | |
| DAR-137 | Dispatch | Mapping | T | The system shall provide the user access to GIS based mapping software at the Dispatch Workstation. | |
| DAR-138 | Dispatch | Mapping | T | The system shall display on a map PLI/AVL to provide the dispatcher a common operational picture of available emergency response resources. | |
| DAR-139 | Dispatch | Mapping | T | The system shall provide an integrated map to display geographic and related information on the Dispatch Workstation. | |
| DAR-140 | Dispatch | Mapping | T | The system shall automatically display the location of the incident on a map to the Dispatch Workstation no more than 2 seconds after event creation and address verification. | |
| DAR-141 | Dispatch | Mapping | T | The system shall plot routing solution from first responder location to incident location. | |
| DAR-142 | Dispatch | Mapping | T | The system shall display/correlate alarm/sensor locations on the map display. | |
| DAR-143 | Dispatch | Mapping | T | The system shall refresh feeds supporting routing every 3 seconds. | |
| DAR-144 | Dispatch | Mapping | T | The system shall refresh data layer changes every 30 seconds. | |
| DAR-145 | Dispatch | Mapping | T | The system shall access location specific reference information such as floor plans as available. | |
| DAR-146 | Dispatch | Mapping | T | The system shall utilize a Map Display with standard mapping capability to hyperlink to external files. | |
| DAR-147 | Dispatch | Mapping | T | The system shall utilize a Map Display with standard mapping capability to measure. | |
| DAR-148 | Dispatch | Mapping | T | The system shall display possible matches when location information is entered (e.g. partial location name, common place name, intersection) | |
| DAR-149 | Dispatch | Mapping | T | The system shall allow the user to select the correct match from the list of possible address matches without having to retype the location information. | |
| DAR-150 | Dispatch | Mapping | T | The system shall automatically generate geographic location information (e.g., reporting area, zone, city, county). | |
| DAR-151 | Dispatch | Mapping | T | The system shall automatically generate geographic coordinates (e.g., latitude/longitude) for validated locations (e.g. common place names, street addresses). | |
| DAR-152 | Dispatch | Mapping | T | The system shall import Geographic Information System (GIS) information from existing DoD geospatial datasets without loss of fidelity. | |
| DAR-153 | Dispatch | Mapping | T | The system shall display associated capabilities of First Responder vehicles (such as tool tips with vehicle type, HAZMAT and status) with AVL track on the dispatch GIS map display. | |
| DAR-154 | Dispatch | Mapping | T | The system shall allow users to input road closures. | |
| DAR-155 | Dispatch | Mapping | T | The system shall have the ability to display geographic features on various dynamic scales. | |
| DAR-156 | Dispatch | Mapping | T | The system shall allow an authorized user to select centerline representation feature of streets. | |
| DAR-157 | Dispatch | Mapping | T | The system shall allow an authorized user to select double-line representation feature of streets. | |
| DAR-158 | Dispatch | Mapping | T | The system shall allow an authorized user to select connected route representation feature of streets. | |
| DAR-159 | Dispatch | Mapping | T | The system shall be capable of creating and editing geometric networks (e.g., transportation) in support of vehicle routing and tracking. | |
| DAR-160 | Dispatch | Mapping | T | The system shall be have the ability to incorporate network parameters such as time variables into geometric networks for turn-by-turn vehicle routing with applicable information (e.g., street name, turn directions, distance, time). | |
| DAR-161 | Dispatch | Mapping | T | The system shall be have the ability to incorporate network parameters such as cost variables into geometric networks for turn-by-turn vehicle routing with applicable information (e.g., street name, turn directions, distance, time). | |
| DAR-162 | Dispatch | Mapping | T | The system shall be have the ability to incorporate network parameters such as distance variables into geometric networks for turn-by-turn vehicle routing with applicable information (e.g., street name, turn directions, distance, time). | |
| DAR-163 | Dispatch | Mapping | T | The system shall be capable of creating standard address locators for use with transportation geometric networks. | |
| DAR-164 | Dispatch | Mapping | T | The system shall be capable of editing standard address locators for use with transportation geometric networks. | |
| DAR-165 | Dispatch | Mapping | T | The system shall be capable of creating and editing composite locators for customization for unique datasets address locators for use with transportation geometric networks. | |
| DAR-166 | Dispatch | Mapping | T | The system shall be capable of creating and editing associated data structure for deriving an address location relative to the street segment. | |
| DAR-167 | Dispatch | Mapping | T | The system shall import Geographic Information System (GIS) information from existing DoD geospatial datasets without loss of accuracy. | |
| DAR-168 | Dispatch | Mapping | T | The system shall allow road closures to be used in deriving vehicle route to incident location. | |
| DAR-169 | MDC | CAD | T | The system shall pass alerts to mobile devices. | |
| DAR-170 | Dispatch | Network Interface | T | The system shall be able to enter and be managed in PSNet. | |
| DAR-171 | Dispatch | Network Interface | T | The system shall be built on secure, open standards so that interoperability with PSNet is assured. | |
| DAR-172 | Dispatch | Physical Interface | T | The system shall be capable of printing all incidents. | |
| DAR-173 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the Electromagnetic Environment (EME) by complying with interference control requirements. | |
| DAR-174 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the EME environment by controlling Electrostatic Discharge (ESD) build-up caused by p-static. | |
| DAR-175 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the EME environment by bonding all electrically conductive items to control electrical current flow. | |
| DAR-176 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the EME environment by bonding all electrically conductive items to control static charge. | |
| DAR-177 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the EME environment by bonding all external ground provisions to control electrical current flow. | |
| DAR-178 | Dispatch | Physical Interface | T | The system shall be able to sustain operations in the EME environment by bonding all external ground provisions to control static charge. | |
| DAR-179 | Dispatch | Physical Interface | T | The system shall provide electrical bonding for electrical continuity across external mechanical interfaces between the equipment and other system elements for control of E3 to ensure system operational performance requirements are met. | |
| DAR-180 | Dispatch | Physical Interface | T | The system shall not exceed unintentional electromagnetic radiated emissions of -110 dBm/m2 at one nautical mile (-105 dBm/m2 at one kilometer) in any direction from the system over the frequency range of 500 kHz to 40 GHz. | |
| DAR-181 | Dispatch | Physical Interface | T | The system shall comply with NFPA 70, 2011 Edition installation standards. | |
| DAR-182 | Dispatch | Physical Interface | T | The system shall use modular plug-in electrical components. | |
| DAR-183 | Dispatch | Physical Interface | T | The system shall use modular plug-in communications components. | |
| DAR-184 | Dispatch | Physical Interface | T | The system shall mark or key electrical components to preclude insertion or installation in the wrong position or location. | |
| DAR-185 | Dispatch | Physical Interface | T | The system direct replacement components shall be physically interchangeable, requiring only resetting of exterior switches, connection of cables, or insertion of plug-in devices. | |
| DAR-186 | Dispatch | Physical Interface | T | The system shall provide Dispatch Workstations compliant with the ergonomic standards in ANSI/HFES 100-2007. | |
| DAR-187 | Dispatch | RMS | T | The system shall track call activity noting how many calls were received. | |
| DAR-188 | Dispatch | RMS | T | The system shall have the ability to search the databases for previous histories on vehicle license numbers and alert the dispatcher. | |
| DAR-189 | Dispatch | RMS | T | The system shall maintain an audit trail on each incident. | |
| DAR-190 | Dispatch | RMS | T | The system shall maintain an audit trail on subsequent updates. | |
| DAR-191 | Dispatch | RMS | T | The system shall provide an audit trail that includes user name. | |
| DAR-192 | Dispatch | RMS | T | The system shall provide an audit trail that includes user ID. | |
| DAR-193 | Dispatch | RMS | T | The system shall provide an audit trail that includes the date and time stamp. | |
| DAR-194 | Dispatch | RMS | T | The system shall provide an audit trail that includes the change type. | |
| DAR-195 | Dispatch | RMS | T | The system shall display the audit log on all open incidents for viewing by those with the correct access rights. | |
| DAR-196 | Dispatch | RMS | T | The system shall have the ability to combine duplicate incidents into a single incident. | |
| DAR-197 | Dispatch | RMS | T | The system shall be able to recall incidents for review. | |
| DAR-198 | Dispatch | RMS | T | The system shall be able to recall incidents to enter update information. | |
| DAR-199 | Dispatch | RMS | T | The system shall support incident recall using the command line. | |
| DAR-200 | Dispatch | RMS | T | The system shall support incident recall using a preformatted screen. | |
| DAR-201 | Dispatch | RMS | T | The system shall allow for incident searches. | |
| DAR-202 | Dispatch | RMS | T | The system shall have the ability to perform automatic queries on information entered into the proper fields of an incident. | |
| DAR-203 | Dispatch | RMS | T | The system shall be able to scan returned queries, highlighting certain key words for the dispatcher (e.g., "wanted person," "stolen vehicle") capable of being modified by authorized personnel. | |
| DAR-204 | Dispatch | RMS | T | The system shall maintain the unit ID(s) associated with the incident for audit purposes. | |
| DAR-205 | Dispatch | RMS | T | The system shall maintain the dispatcher ID(s) associated with the incident for audit purposes. | |
| DAR-206 | Dispatch | RMS | T | The system shall maintain the call-taker ID(s) associated with the incident for audit purposes. | |
| DAR-207 | Dispatch | RMS | T | The system shall provide a methodology for closed incidents to be archived. | |
| DAR-208 | Dispatch | RMS | T | The system shall provide a methodology for closed incidents to be recorded on a media device for evidentiary purposes. | |
| DAR-209 | Dispatch | RMS | T | The system shall provide a methodology for archived incidents incidents to be restored to the system for review. | |
| DAR-210 | Dispatch | RMS | T | The system shall respond to queries in no more than 2 seconds for normal activity excluding external response delays. | |
| DAR-211 | Dispatch | RMS | T | The system shall respond to queries in no more than 5 seconds for active incident queries excluding external response delays. | |
| DAR-212 | Dispatch | RMS | T | The system shall respond to queries in no more than 30 seconds for historical queries excluding external response delays. | |
| DAR-213 | Dispatch | RMS | T | The system shall archive data recording for tracking trends of various events, call processing, lessons learned, training, after action reports and for increased clarity during investigations in accordance with NFPA 1221. | |
| DAR-214 | Dispatch | RMS | T | The system shall provide a methodology for logged incidents and associated audio to be recorded on a media device for evidentiary purposes. | |
| DAR-215 | Dispatch | RMS | T | The system shall provide a methodology for archived logged incidents and associated audio to be restored to the system for review. | |
| DAR-216 | Dispatch | RMS | T | The system shall log and record dispatcher actions (enter a new incident, dispatch a unit, unit arrives on-scene, etc.). | |
| DAR-217 | Dispatch | RMS | T | The system shall include the ability to conduct Quality Assurance through playback. | |
| DAR-218 | Dispatch | RMS | T | The system shall include the ability to conduct Quality Assurance through printouts. | |
| DAR-219 | Dispatch | RMS | T | The system shall store 99.99 percent of incident data online for no less than 30 days for retrieval. | |
| DAR-220 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by incoming line information. | |
| DAR-221 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by outgoing line information. | |
| DAR-222 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on position information. | |
| DAR-223 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on dispatcher information. | |
| DAR-224 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on time of day information. | |
| DAR-225 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on day of week information. | |
| DAR-226 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on call volume information. | |
| DAR-227 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on name of caller information. | |
| DAR-228 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on subscriber type. | |
| DAR-229 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on address or coordinate (ALI). | |
| DAR-230 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed based on time of initiation. | |
| DAR-231 | Dispatch | RMS | T | The system shall generate custom reports based on data tracked for an incident. | |
| DAR-232 | Dispatch | RMS | T | The system shall provide users the ability to search the narrative of incidents for key words/phrases. | |
| DAR-233 | Dispatch | RMS | T | The system shall be capable of scheduling reports, either "canned" or user-designed, to run at specific intervals. | |
| DAR-234 | Dispatch | RMS | T | The system shall export reports into third-party applications such as word processing or spreadsheet applications. | |
| DAR-235 | Dispatch | RMS | T | The system shall clearly mark system output in accordance with DoD, USMC and local policy (e.g., Law Enforcement Sensitive, FOUF, PII). | |
| DAR-236 | Dispatch | RMS | T | The system shall have the ability to create an online log of items of note for each zone or Emergency Services department for review by subsequent shifts. | |
| DAR-237 | Dispatch | RMS | T | The system shall display calculated time for reports in the HH:MM:SS format. | |
| DAR-238 | Dispatch | RMS | T | The system shall allow for the distribution of the reports via inclusion in a message. | |
| DAR-239 | Dispatch | RMS | T | The system shall have the ability to save reports in an electronic format. | |
| DAR-240 | Dispatch | RMS | T | The system shall allow for calculations of call handling times (from the call-taking and dispatch perspective). | |
| DAR-241 | Dispatch | RMS | T | The system shall allow for calculations of response times (from the emergency responders perspective) | |
| DAR-242 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by time spent on incidents. | |
| DAR-243 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by incident types. | |
| DAR-244 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by incident priority. | |
| DAR-245 | Dispatch | RMS | T | The system shall allow for activity analysis reporting on any criteria captured by the system such (e.g. incident type, unit, day of week, time of day, geographic area or Emergency Services department). | |
| DAR-246 | Dispatch | RMS | T | The system shall allow reports to be published to an intranet or the Internet. | |
| DAR-247 | Dispatch | RMS | T | The system shall allow snapshot data reports to be published to an intranet or the Internet. | |
| DAR-248 | Dispatch | RMS | T | The system shall allow reports published to an intranet or the Internet to be labeled with appropriate security markings (e.g. PII, Law Enforcement Sensitive, FOUO). | |
| DAR-249 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by Emergency Services department. | |
| DAR-250 | Dispatch | RMS | T | The system shall have a reporting system that allows reports to be accessed by geographic area (response zone, city, etc., or user definable area). | |
| DAR-251 | Dispatch | RMS | T | The system shall have the ability to perform automatic queries on information from the command line. | |
| DAR-252 | Dispatch | Time Sync | T | The system shall provide a time synchronization signal. | |
| DAR-253 | Dispatch | Time Sync | T | The system shall synchronize date and time to MDCs. | |
| DAR-254 | Dispatch | Time Sync | T | The system shall synchronize date and time with CERS components. | |
| DAR-255 | Dispatch | User Access Control | T | The system shall utilize permissions-based access. | |
| DAR-256 | Dispatch | User Access Control | T | The system shall have security that controls individual user access to system reports. | |
| DAR-257 | Dispatch | User Access Control | T | The system shall provide access to audit trails for only the users with proper security role. | |
| DAR-258 | Dispatch | User Access Control | T | The system shall provide user security levels to determine system access to user classification (e.g., call taker, dispatcher). | |
| DAR-259 | Dispatch | User Access Control | T | The system shall produce an audit trail of all transactions. | |
| DAR-260 | Dispatch | User Access Control | T | The system shall provide user security levels to determine system access to areas of responsibility (Law, Fire, EMS). | |
| DAR-261 | Dispatch | User Access Control | T | The system shall provide user security levels to determine system access to production (live) or training mode. | |
| DAR-262 | Dispatch | User Access Control | T | The system shall afford system administrators the ability to identify the user who made the change to the system. | |
| DAR-263 | Dispatch | User Access Control | T | The system shall allow authorized users to print incident information or the incident audit trail upon demand. | |
| DAR-264 | Dispatch | User Access Control | T | The system shall provide user status functions to users if granted access to these functions by the administrator. | |
| DAR-265 | Dispatch | User Interface | T | The system shall have a single administration interface. | |
| DAR-266 | Dispatch | User Interface | T | The system shall include an audio headset that supports multiple independent audio sources simultaneously. | |
| DAR-267 | Dispatch | User Interface | T | The system shall provide the user access to CAD software. | |
| DAR-268 | Dispatch | User Interface | T | The system shall provide the user access to radio software interfaces. | |
| DAR-269 | Dispatch | User Interface | T | The system shall provide the user access to radio hardware interfaces. | |
| DAR-270 | Dispatch | User Interface | T | The system shall provide the user access to Fire Station & EMS Alerting interface. | |
| DAR-271 | Dispatch | User Interface | T | The system shall integrate all components and applications through the use of no more than 2 keyboards, mice and other man-machine interfaces on a multiple display console. | |
| DAR-272 | Dispatch | User Interface | T | The system shall provide standard graphical user interface items like drop-down menus to make selection easier for frequently used fields such as incident types, disposition codes and Emergency Services department IDs. | |
| DAR-273 | Dispatch | User Interface | T | The system shall provide quick-entry methods to minimize the keystrokes required to perform actions. | |
| DAR-274 | Dispatch | User Interface | T | The system shall provide users the ability to correct spelling errors without having to retype the entire field. | |
| DAR-275 | Dispatch | User Interface | T | The system shall have function keys available for frequently used functions. | |
| DAR-276 | Dispatch | User Interface | T | The system shall provide an application command line for user entry. | |
| DAR-277 | Dispatch | User Interface | T | The system shall provide a standard user interface items controlled by mouse or touch screen. | |
| DAR-278 | Dispatch | User Interface | T | The system shall support pre-fill fields in appropriate preformatted screens, eliminating redundant data entry. | |
| DAR-279 | Dispatch | User Interface | T | The system shall allow a user to move easily from one work area to the other via the mouse, keyboard or touch screen. | |
| DAR-280 | Dispatch | User Interface | T | The system shall interface with databases that provide emergency medical information. | |
| DAR-281 | Dispatch | User Interface | T | The system shall interface with databases that provide emergency medical protocols. | |
| DAR-282 | Dispatch | User Interface | T | The system shall interface with databases that provide criminal justice information. | |
| DAR-283 | Dispatch | User Interface | T | The system shall save user specific changes to the workstation screens for each authorized user. | |
| DAR-284 | Dispatch | User Interface | T | The system shall be capable of being reset to default settings configured by the system administrator. | |
| DAR-285 | Dispatch | User Interface | T | The system shall support combined call taker/ dispatcher functions at a single workstation. | |
| DAR-286 | Dispatch | User Interface | T | The system shall support separate call taker/ dispatcher functions at separate workstations. | |
| DAR-287 | Dispatch | User Interface | T | The system shall have customizable menus giving access to frequently used functions. | |
| DAR-288 | Dispatch | User Interface | T | The system shall allow incident type database to be changed/updated while the system is online. | |
| DAR-289 | Dispatch | User Interface | T | The system shall restrict access to the incident type database based on user roles. | |
| DAR-290 | Dispatch | User Interface | T | The system shall allow configuration of tones by authorized users. | |
| DAR-291 | Dispatch | User Interface | T | The system shall allow more than one call-taker, dispatcher and/or supervisor to monitor an incident at any time. | |
| DAR-292 | Dispatch | User Interface | T | The system shall provide electronic help for any form to describe fields as well as procedures from system documentation. | |
| DAR-293 | Dispatch | User Interface | T | The system shall allow for the online access to various indexes stored/maintained in the system (e.g. phone lists, offense codes, fire codes, community resources, government officials). | |
| DAR-294 | Dispatch | User Interface | T | The system shall be National Information Exchange Model (NIEM) compliant. | |
| DAR-295 | Dispatch | User Interface | T | The system shall be Global Justice XML Database Model (GJXDM) compliant. | |
| DAR-296 | Dispatch | User Interface | T | The system shall allow parameter changes to be done while the system is online. | |
| DAR-297 | Dispatch | User Interface | T | The system shall allow changes to take effect once the system is returned to the operational mode. | |
| DAR-298 | Dispatch | User Interface | T | The system shall allow the user to select Training Mode during the sign-on process. | |
| DAR-299 | Dispatch | User Interface | T | The system shall notify the dispatcher if an interface is down. | |
| DAR-300 | Dispatch | User Interface | T | The system shall provide a Computerized Radio Interface (CRI) capability for voice communications. | |
| DAR-301 | Dispatch | User Interface | T | The system shall allow a dispatcher to monitor multiple radio channels. | |
| DAR-302 | Dispatch | User Interface | T | The system shall allow a dispatcher to communicate via multiple radio channels. | |
| DAR-303 | Dispatch | User Interface | T | The system shall allow a dispatcher to patch channels for increased efficiency of first responder services and enhanced management of large scale incidents. | |
| DAR-304 | Dispatch | User Interface | T | The system shall allow a dispatcher to multi-select channels for increased efficiency of first responder services and enhanced management of large scale incidents. | |
| DAR-305 | Dispatch | User Interface | T | The system shall provide CRI priority emergency voice communications transmitted between the dispatcher and First Responder 99.99 percent of the time. | |
| DAR-306 | Dispatch | User Interface | T | The system shall support dropdown menu lists for fields that support a predefined set of user entries. | |
| DAR-307 | Dispatch | User Interface | T | The system shall comply with E3 DoD directives. | |
| DAR-308 | Dispatch | User Interface | T | The system shall comply with E3 DoD instructions. | |
| DAR-309 | Dispatch | User Interface | T | The system shall comply with Federal Communications Commission (FCC) Class A standards. | |
| DAR-310 | Dispatch | User Interface | T | The system shall comply with Military Standard (MIL-STD)-464. | |
| DAR-311 | Dispatch | User Interface | T | The system shall comply with international/host nation regulations. | |
| DAR-312 | Dispatch | User Interface | T | The system shall be compatible with IPv6 networking standards. | |
| DAR-313 | Dispatch | User Interface | T | The system shall allow for the addition or removal of components with minimal impact to the users. | |
| DAR-314 | Dispatch | User Interface | T | The system shall use open systems design to allow for future growth through planned insertion of advancements in technology. | |
| DAR-315 | Dispatch | User Interface | T | The system shall be built on secure, open standards so that interoperability with other NENA-Compliant systems is assured. | |
| DAR-316 | Dispatch | User Interface | T | The system shall allow the addition of government approved third-party hardware components through its open architecture. | |
| DAR-317 | Dispatch | User Interface | T | The system shall allow the addition of government approved third-party software components through its open architecture. | |
| DAR-318 | Dispatch | User Interface | T | The system shall support electronic data access to third-party systems for query/exchange (e.g., Web services, ODBC, data warehouse/flat file, API). | |
| DAR-319 | Dispatch | User Interface | T | The system shall meet the “design for maintenance” human engineering design criteria requirements of MIL-STD-1472G | |
| DAR-320 | Dispatch | User Interface | T | The system shall meet the Occupational Safety and Health Standards 29 CFR 1910. | |
| DAR-321 | Dispatch | User Interface | T | The system shall allow the user to page via keystrokes or use the mouse to scroll to subsequent status monitors screens to view more incidents or units in the event they do not fit in a single window. | |
| DAR-322 | Dispatch | User Interface | T | The system shall support the ability for system administrators to configure the layout of the workstation screen(s), depending on the number of monitors at the workstations so that workstation windows are not hard-coded. | |
| DAR-323 | Dispatch | User Interface | T | The system shall allow administrators to alter the configurations at any time. | |
| DAR-324 | Dispatch | User Interface | T | The system shall allow the system administrator to assign different audio files for low, medium and high priority incident. | |
| DAR-325 | Dispatch | User Interface | T | The system shall allow database changes to be done while the system is online. | |
| DAR-326 | MDC | CAD | T | The system shall support field-initiated incidents from a mobile data entry. | |
| DAR-327 | MDC | CAD | T | The system shall provide navigational features for vehicle operators including destination location. | |
| DAR-328 | MDC | CAD | T | The system shall provide navigational features for vehicle operators including vehicle heading. | |
| DAR-329 | MDC | CAD | T | The system shall provide navigational features for vehicle operators including remaining distance to destination. | |
| DAR-330 | MDC | CAD | T | The system shall provide navigational features for vehicle operators including direction to destination. | |
| DAR-331 | MDC | CAD | T | The system shall send secure message transfers between the CAD and MDC. | |
| DAR-332 | MDC | CAD | T | The system shall send messages to the MDC in no more than 2 minutes 95 percent of the time. | |
| DAR-333 | MDC | CAD | T | The system shall send messages from the MDC in no more than 2 minutes 95 percent of the time. | |
| DAR-334 | MDC | CAD | T | The system shall provide an audible indication upon message receipt to the MDC. | |
| DAR-335 | MDC | CAD | T | The system shall provide a visible indication upon message receipt to the MDC. | |
| DAR-336 | MDC | CAD | T | The system shall have ability to support automatic vehicle tracking via GPS technologies. | |
| DAR-337 | MDC | CAD | T | The system shall allow users to prepare/access incident reports from the MDC. | |
| DAR-338 | MDC | CAD | T | The system shall provide a time tracking form for mobile users. | |
| DAR-339 | MDC | CAD | T | The MDC shall pass the time tracking information to the CAD. | |
| DAR-340 | MDC | CAD | T | The system shall include a time tracking form to include a data field for validated activity code. | |
| DAR-341 | MDC | CAD | T | The system shall include a time tracking form to include narrative description of the activity. | |
| DAR-342 | MDC | CAD | T | The system shall include a time tracking form to include location/address of activity. | |
| DAR-343 | MDC | CAD | T | The system shall include a time tracking form to include narrative remarks. | |
| DAR-344 | MDC | CAD | T | The system shall include a time tracking form to include case/citation numbers associated with the activity. | |
| DAR-345 | MDC | Mapping | T | The system shall utilize a Mobile Mapping Capability w/vehicle information (e.g. speed, heading). | |
| DAR-346 | MDC | Mapping | T | The system shall provide an integrated map to display on the MDC. | |
| DAR-347 | MDC | Mapping | T | The system shall display associated capabilities of First Responder vehicles (such as tool tips with vehicle type, HAZMAT and status) with AVL track on the MDC GIS map display. | |
| DAR-348 | MDC | Mapping | T | The system shall have in-vehicle heading indication. | |
| DAR-349 | MDC | Mapping | T | The system shall have in-vehicle speed indication. | |
| DAR-350 | MDC | Mapping | T | The system shall provide predictive routing for known congested areas during predefined times throughout each day. | |
| DAR-351 | MDC | Network Interface | T | The system shall leverage existing RF to provide data transfer to MDCs. | |
| DAR-352 | MDC | Network Interface | T | The system shall leverage existing cellular infrastructure to provide data transfer to MDCs. | |
| DAR-353 | MDC | Physical Interface | T | The system shall provide secure two way communications with MDCs. | |
| DAR-354 | MDC | Physical Interface | T | The MDC shall provide for in-vehicle day viewing. | |
| DAR-355 | MDC | Physical Interface | T | The MDC shall provide for in-vehicle night viewing. | |
| DAR-356 | MDC | Physical Interface | T | The MDC shall be portable. | |
| DAR-357 | MDC | Physical Interface | T | The MDC shall be sealed against rain in compliance with MIL-STD 810F. | |
| DAR-358 | MDC | Physical Interface | T | The MDC shall be designed to survive a 3 foot drop without physical damage in compliance with MIL-STD 810F. | |
| DAR-359 | MDC | Physical Interface | T | The MDC shall be specified for temperatures of -20 degrees Celsius to 60 degrees Celsius in compliance with MIL-STD 810F. | |
| DAR-360 | MDC | Physical Interface | T | The MDC shall include a fixed in vehicle MDC docking station supporting a simple, easily-accessible, one-button/one-touch MDC release mechanism. | |
| DAR-361 | MDC | Physical Interface | T | The MDC shall include a touch pad mouse. | |
| DAR-362 | MDC | Physical Interface | T | The MDC mounting shall not block the passenger seat/area in the vehicle. | |
| DAR-363 | MDC | Physical Interface | T | The MDC mounting shall not block/inhibit the deployment of vehicle air bags. | |
| DAR-364 | MDC | Physical Interface | T | The MDC power shall be wired to a clean voltage source that is not within the starting loop. | |
| DAR-365 | MDC | Physical Interface | T | When installed in the vehicle, the MDC shall rely on the internal battery supply if the vehicle ignition is off. | |
| DAR-366 | MDC | Physical Interface | T | The MDC shall be sealed in compliance with MIL-STD 810F. | |
| DAR-367 | MDC | Physical Interface | T | The MDC shall be designed to survive a 3 foot drop without operational failure in compliance with MIL-STD 810F. | |
| DAR-368 | MDC | User Interface | T | The system shall provide an interface to the RMS that supports communication with field users for field report upload. | |
| DAR-369 | MDC | User Interface | T | The system shall provide an interface to support mobile user access to NCIC. | |
| DAR-370 | MDC | User Interface | T | The system shall provide an interface to support mobile user access to local/regional databases. | |
| DAR-371 | Security | Information Assurance | T | The system shall use FIPS 140-2 compliant interfaces to external databases. | |
| DAR-372 | Security | Information Assurance | T | The system shall utilize a minimum of 128 bit encryption. | |
| DAR-373 | Security | Information Assurance | T | The system shall include protection against security attacks on network interfaces connected to either a managed WAN or protected via a VPN through the public internet. | |
| DAR-374 | Security | Information Assurance | T | The system shall have virus protection software installed. | |
| DAR-375 | Security | Information Assurance | T | The system shall have Host Based Security Software (HBSS) installed. | |
| DAR-376 | Security | Information Assurance | T | The system shall have the BIOS protected in accordance with DoD BIOS Protection Guideline Memorandum Dtd 8 Sep 2011 and NIST SP 800-147 to the greatest extent possible. | |
| DAR-377 | Security | Information Assurance | T | The system shall satisfy USMC security requirements for data stored on mobile or removable devices (e.g., encryption of data at rest). | |
| DAR-378 | Security | Information Assurance | T | The system shall use encryption algorithms that meet current USMC requirements (e.g., FIPS 140-2 compliant, AES 128/256 where appropriate). | |
| DAR-379 | Security | Information Assurance | T | The system shall only use Ports, Protocols and Services (PPS) that are in accordance with authorized USMC PPS | |
| DAR-380 | Security | Information Assurance | T | The system shall ensure that communications/data transfers between external interfaces are conducted in a secure manner (e.g. SSH V 3.0) using FIPS 140-2 compliant encryption algorithms. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .