New York Sub-Regional ITS Architecture

Element Expanded Functional Requirements: MTA Bridges/Tunnels OCCC Special Operations Vehicles

Functional Area: ITS Data Repository
  1. The center shall collect data to be archived from one or more data sources.
  2. The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
  3. The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.
  4. The center shall include capabilities for performing quality checks on the incoming archived data.
  5. The center shall include capabilities for error notification on the incoming archived data.
  6. The center shall include capabilities for archive to archive coordination.
  7. The center shall support a broad range of archived data management implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.
  8. The center shall perform quality checks on received data.
  9. The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
  10. The center shall respond to requests from the administrator interface function to maintain the archive data.
  11. When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.
  12. For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.
Functional Area: On-board EV En Route Support
  1. The emergency vehicle, including roadway service patrols, shall track its current location.
  2. The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the center for emergency management and dispatch.
  3. The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene.
  4. The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates.
  5. The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.
  6. The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.
  7. The emergency vehicle shall send patient status information to the care facility along with a request for further information.
  8. The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of hospitals or emergency care providers.
  9. The emergency vehicle shall send the vehicle’s location, speed and direction to other vehicles in the area.
Functional Area: Government Reporting Systems Support
  1. The center shall provide data from an ITS archive to federal, state, or local government reporting systems.
  2. The center shall provide the capability to select data from an ITS archive for use in government reports.
  3. The center shall provide the capability to format data from an ITS archive suitable for input into government reports.
  4. The center shall support requests for ITS archived data from Government Reporting Systems.
  5. The center shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
Functional Area: Traffic and Roadside Data Archival
  1. The center shall manage the collection of archive data directly from collection equipment located at the roadside.
  2. The center shall collect traffic sensor information from roadside devices.
  3. The center shall collect environmental sensor information that from roadside devices.
  4. The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection process.
  5. The center shall send the request for data and control parameters to the field equipment where the information is collected and returned.
  6. The center shall record the status about the imported traffic and roadside data.
  7. The center shall use the status information to adjust the collection of traffic and roadside data.