New Jersey Statewide ITS Architecture


Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: Collect Traffic Surveillance

Description: This equipment package collects, stores, and provides electronic access to the traffic surveillance data.
Included In: Atlantic City Area Joint Operations Center
DRBA TMC
DRJTBC Facility Operations Center
NJDOT TOC Central
NJDOT TOC North
NJDOT TOC South
NJTA Parkway Division TOC
NJTA Turnpike TOC
PANYNJ Port Commerce Operations Centers
PANYNJ TB/T Bus Terminals/Stations Communications Desk/Operations Center
SJTA TOC
Processes: 1.1.2.2 - Process Traffic Data
1.1.2.3 - Update Data Source Static Data
1.1.4.1 - Retrieve Traffic Data
1.1.4.2 - Provide Traffic Operations Personnel Traffic Data Interface
1.1.4.4 - Update Traffic Display Map Data
1.3.4.2 - Provide Traffic Operations Personnel Incident Data Interface
User Service Requirements: 1.0 - TRAVEL AND TRAFFIC MANAGEMENT
1.6 - TRAFFIC CONTROL
1.6.0 - ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
1.6.1 - TC shall include a Traffic Flow Optimization function to provide the capability to optimize traffic flow.
1.6.1.7 - Implementation of the Control function shall include strategies that account for at least the following:
1.6.1.7(a) - Human factors.
1.6.2 - TC shall include a Traffic Surveillance function.
1.6.2.2 - Traffic Surveillance shall include a data collect function to provide the capability to collect data for determining traffic flow and prediction.
1.6.2.2.1 - The data collect function shall provide the capability to quickly feedback traffic data to the control processes.
1.6.2.3 - Traffic Surveillance shall include a wide-area surveillance capability to include several jurisdictions.
1.6.2.3.2 - The wide-area surveillance shall cover a large number of roadway segments.
1.6.2.4 - TC shall provide the capability to acquire detailed traffic measurements at specific locations.
1.6.2.4.1 - Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.3 - TC shall include a Device Control function.
1.6.3.4 - Device Control shall communicate control data to the following devices.
1.6.3.4(e) - Human operator support.
1.6.3.4.1 - Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.4 - Device Control shall provide traffic control information to other elements of the ITS, including but not limited to the following:
1.6.4(a) - In-vehicle navigation.
1.6.4(b) - Trip planning.
1.6.4(c) - Routing systems.
1.6.4(d) - Fleet management systems.
1.7 - INCIDENT MANAGEMENT
1.7.0 - ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) Predict Hazardous Conditions.
1.7.1 - Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1 - The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1 - The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(a) - Traffic flow sensors.
1.7.1.1.1(b) - Environmental sensors.
1.7.2 - IM shall provide a Response Formulation function to formulate appropriate response actions to each identified incident and revise those actions when necessary.
1.7.2.1 - The Response Formulation function shall propose and facilitate the appropriate scheduling of those predicted incidents that can be scheduled to minimize incident potential, incident impacts, and/or the resources required for incident management.
1.7.3 - IM shall include a Response Implementation function to provide the services to implement a response coordinated with all appropriate agencies.
1.7.3.2 - The Response Implementation function shall provide a link between Incident Management and all other user services necessary to implement incident response actions.
1.7.4 - IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident.
1.8 - TRAVEL DEMAND MANAGEMENT
1.8.1 - TDM shall include a communications function.
1.8.1.4 - The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(a) - Sensor data.
1.8.2 - TDM shall include a processing function.
1.8.2.3 - Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(a) - Monitor traffic.
1.8.2.3(d) - Detect traffic.
1.10 - HIGHWAY RAIL INTERSECTION
1.10.0 - ITS shall include a Highway-Rail Intersection (HRI) function to control highway and rail traffic in at-grade HRIs. Two sub-services are supported: Standard Speed Rail Subservice which is applicable to light rail transit, commuter rail and heavy rail trains with operational speeds up to 79 miles per hour (MPH); and High Speed Rail Subservice which is applicable to all passenger and freight trains with operational speeds from 80 to 125 MPH.
5.0 - EMERGENCY MANAGEMENT
5.1 - EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3 - ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4 - RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3 - MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.3.5 - RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.2 - PSS shall allow system operators to monitor and control operation of the physical security system devices, including operator override.
5.1.3.5.3 - PSS shall provide current status of the system including readiness and activation to operators.
5.1.5 - ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1 - PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2 - The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3 - PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4 - PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.
5.3 - DISASTER RESPONSE AND EVACUATION
5.3.0 - ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.2 - Disaster Response shall provide a Monitor Alert Levels (MAL) function.
5.3.2.2 - MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.2.2(c) - Review and update resource inventories
7.0 - INFORMATION MANAGEMENT
7.1 - ARCHIVED DATA FUNCTION
7.1.0 - ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.3.1 - DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.9 - DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include:
7.1.3.1.9(e) - GIS map of network.
8.0 - MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1 - MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.1 - Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.6 - MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1 - MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a) - Congestion
8.1.1.6.1(b) - Incidents

Last updated: 02-11-05