Description:
|
Collection and storage of information related to Emergency Management. For use by operations personnel or data archives in the region.
|
Included in:
|
DPS Administration
|
Functional Requirements:
|
| 1 | The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data. |
| 2 | The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data. |
| 3 | The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself. |
| 4 | The center shall be able to produce sample products of the data available. |
| | |
|
User Service Requirements (fully or partially addressed):
|
| 7.0 | INFORMATION MANAGEMENT |
| 7.1 | ARCHIVED DATA FUNCTION |
| 7.1.3 | The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function. |
| 7.1.3.1 | DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories. |
| 7.1.3.1.5 | DIV shall be capable of importing ITS Incident Management data to include: |
| 7.1.3.1.5(a) | Incident characteristics. |
| 7.1.3.1.5(b) | Train arrivals at highway rail intersections. |
| 7.1.3.1.5(c) | Emergency vehicle dispatch data. |
| 7.1.3.1.5(d) | Emergency vehicle location data. |
| 7.1.3.1.5(f) | Emergency request data |
| 7.1.3.1.5(h) | Emergency response |
| | |
|
|
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture.
Consult the National
ITS Architecture web site for more information.
|
Web Spinner Technology.