The file's text, extracted by GovTribe without its formatting.
Attachment 6 - PWS Requirements Matrix
S-AQMMA-12-R-0413 A005 Department of State Personnel Tracking Locator
| PWS PARAGRAPH REFERENCE |
| PTL SYSTEM CAPABILITIES |
| MANDATORY |
(at time of delivery)
OPTIONAL
(to be incorporated after award)
PROPOSAL
COMPLIANCE
CHECKLIST
| C.5.1.1 |
| Facilitate the viewing of live track data, historical track data, emergency messages, track administration functions, user administrative functions, and data export functions through a unified, secured, and web interface. |
| X |
| C.5.1.2 |
| Display live/historical tracks with the following device information for all ingested devices: device ID, alias/call-sign, last reported latitude/longitude, last reported track receive time, and emergency status. If the device provides speed, direction or brevity code then the web interface shall display that information as well. |
| X |
| C.5.1.3 |
| Have the capability to export historical device data in CSV format to files. |
| X |
| C.5.1.4 |
| Be able to create, retrieve, update, or delete brevity codes in the web interface for each tracking device |
| X |
| C.5.1.5 |
| Record a “receive” timestamp with each received device update |
| X |
| C.5.1.6 |
| Provide secure two-way messaging capability to trackers capable of receiving messages. |
X
| C.5.1.7 |
| Provide users the capability to filter live/historical tracks individually or as part of a device group. Each user approved to do so shall be able to filter by device, device name/alias, date/time, or device group. |
| X |
| C.5.1.8 |
| Use role-based access control for all functions and commands available to the government. Users shall be granted only the minimum necessary permissions to perform functions for any given device group. User administration functions shall be granted only to authorized administrators. |
| X |
| C.5.1.9 |
| Provide a means to access all configuration settings through the same unified interface. These shall include all software and program settings except settings of the internal COTS products |
| X |
| C.5.1.10 |
| Provide the capability to authorized administrators to assign a user separate permissions for each nested device group. These permissions include but are not limited to the ability to view or modify devices within the device group. |
| X |
| C.5.1.11 |
| Provide system-wide notifications to all users upon software updates, maintenance cycles, or system-wide configuration changes. |
X
| C.5.1.12 |
| Allow users to create nested device groups and to assign or reassign devices under the user’s control to any of the device groups under that user’s control. |
| X |
| C.5.1.13 |
| Show only devices, functions, and configuration settings for which a user has authorization. |
| X |
| C.5.1.14 |
| Allow users to remotely configure all capable trackers for which a user has permissions to modify. This configuration shall include remotely changing the reporting rate of each tracking device. |
X
| C.5.1.15 |
| Display an audible/visual emergency warning to the user in the event that a user-viewable device sends an emergency message to the system. |
| X |
| C.5.1.16 |
| Provide an authorized user the ability to configure a Geofence for each user-viewable device. The user shall have the ability to configure whether the Geofence alarms when a device enters the Geofence, exits the Geofence, or both. If configured, when a tracking device enters or exits the Geofence , the PTL System's web interface shall provide an audio and visual warning to those users with the viewing permissions for that device. |
| X |
| C.5.1.17 |
| Allow an authorized user the ability to define and edit multiple Geofences or zones for each user-viewable device (at least 10). |
X
| C.5.1.18 |
| Be capable of importing a Geofence from file. |
X
| C.5.1.19 |
| In an emergency, allow an authorized user to remotely activate the microphone of audio-capable trackers. The administrator shall have the capability to globally enable or disable this function. Contractor will define safeguards over how this feature will be controlled to ensure access to this feature will be limited to a restricted group of authorized users only, and track implementation of this feature in the audit logs. |
X
| C.5.1.20 |
| Provide an authorized user the ability to edit a user-modifiable tracker’s association data, including each tracker’s alias or call-sign. |
| X |
| C.5.1.21 |
| Provide an authorized user the ability to edit emergency contact information for each user-viewable device. |
| X |
| C.5.1.22 |
| In the event of an emergency, the PTL Systems shall send an emergency notification via e-mail to the configured emergency contact(s) associated with that device in the system. |
| X |
| C.5.1.23 |
| Allow authorized users to manually deactivate an audible/visual emergency warning and geo-fence warnings. |
| X |
| C.5.1.24 |
| Provide an authorized user the capability to export live tracking data and emergency messages via unencrypted UDP, unencrypted TCP, and HTTPS protocols to any other IP address and port. An authorized user shall be able to switch between export protocols at any time. |
| X |
| C.5.1.25 |
| Provide a secure built-in web viewer that allows a user to see selected trackers as icons directly in the web application. Viewer shall allow the user to pan and zoom on the map. |
| X |
| C.5.1.26 |
| Provide the user with the capability to disable the built-in viewer when necessary, in order to save bandwidth, or so that the user can use an external viewing application |
| X |
| C.5.1.27 |
| Have the ability to zoom to a specified tracker, resolution less than or equal to 250m for geospatial imagery and street level for street maps. |
| X |
| C.5.1.28 |
| Differentiate trackers within the display so that a user may distinguish between closely-spaced trackers. |
X
| C.5.1.29 |
| Have the ability to zoom to a specified tracker, at street-level resolution, meaning streets must be distinctly identifiable, for both geospatial imagery and street maps. |
| X |
| C.5.1.30 |
| Provide an authorized user the ability to configure a Geofence for a user-viewable device by highlighting the area directly on a map. |
| X |
| C.5.1.31 |
| Display the following device information when an icon is selected : device ID, device model, alias/call-sign, last reported latitude/longitude, last reported MGRS, last reported time, and emergency status. If a device provides speed, direction or brevity code then the web interface shall display that information as well. |
| X |
| C.5.2 |
| Operator Display and Presentation |
| C.5.2.1 |
| Serve data to multiple external viewing applications. These applications include but are not limited to Google Earth, ESRI and FalconView. This data will include the following device information: device ID, device model, alias/call-sign, last reported latitude/longitude, last reported MGRS, last reported time, emergency status, and brevity code. |
| X |
| C.5.2.2 |
| If the external viewing application supports the ability to display speed and direction this data also shall be provided to the external viewing application. |
X
| C.5.2.3 |
| Provide the capability to integrate layers of geospatial data and overlay the data on a Google Earth Baseline. |
X
The PTL Systems shall provide security auditing and monitoring services, to include intrusion detection and firewall monitoring.
X
As deemed necessary by the government, the Contractor shall use network management software, another automated process, or a combination of the two to monitor the connection status and health of the externally-connected networks. These externally-connected networks include but are not limited to VPN's to other systems and incoming device transmission networks such as satellite ground stations.
X
| C.5.4 |
| Special Technical Requirements |
| C.5.4.1 |
| Ingest multiple device formats over varied transmission paths, including but not limited to PECOS, Iridium, Global Star, and various 2G/3G/4G cellular networks via Short Message Service (SMS) and data. |
| X |
| C.5.4.2 |
| Ingest, at a minimum, device ID, position, and elevation data from each tracker, and any brevity code. If the device provides it, the PTL Systems shall also ingest device send time, speed, and direction. |
| X |
| C.5.4.3 |
| Provide the ability to ingest encrypted device data using FIPS-approved encryption algorithms where encryption is supported by the device. |
| X |
| C.5.4.4 |
| Utilize an Application Programming Interface (API) for integration to third-party external viewing applications and systems. This API shall include at a minimum: retrieval of live or historical tracks by ID, Alias, Date, Device Group, or other filters, and retrieval of device metadata and geo-fences. |
· The API shall be exposed through secured and encrypted services, be it web services, remote method invocation, or complete exposure of proprietary format to the government.
· All API methods shall be exposed, documented, and provided to the government. All API methods and documentation shall be accessible without requiring proprietary software or a license.
X
| C.5.4.5 |
| Provide the ability to import and export real-time data in the JBFSA format (Versions 1.0, 1.0a, 2.3 and FFT 2.4). The contractor shall update this capability for forward compatibility as required. |
| X |
| C.5.4.6 |
| The production server shall consist of performance languages, either compiled or JIT-compiled, suitable to an enterprise environment. |
X
| C.5.4.7 |
| The PTL shall have the ability to store all tracking data for a minimum of two (2) years. |
| X |
| C.5.4.8 |
| (OPTIONAL) Provide the capability to export live track data and emergency messages in real-time through a one-way guard. |
X
