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: TMC Multimodal Crossing Management

Description: This equipment package monitors and manages multimodal crossings and disseminates associated traveler information. Equipment controlled includes warning lights, gates, dynamic message signs, and other systems that provide driver information and control traffic at multimodal crossings. This equipment package manages draw bridges and miscellaneous other interference crossings between highway traffic and other modes. Railroad grade crossings are covered by the HRI Traffic Management equipment package.
Included In: NJDOT TOC Central
NJDOT TOC North
NJDOT TOC South
TRANSCOM Communications Center Servers
Processes: 1.1.2.2 - Process Traffic Data
1.1.4.1 - Retrieve Traffic Data
1.2.4.1 - Output Control Data for Roads
1.2.4.4 - Output Roadway Information Data
1.3.2.2 - Review and Classify Possible Incidents
User Service Requirements: 1.0 - TRAVEL AND TRAFFIC MANAGEMENT
1.5 - TRAVELER SERVICES INFORMATION
1.5.2 - TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.5 - Information Access shall provide the capability for travelers to access the TSI information via any of, but not limited to, the following methods:
1.5.2.5(a) - Highway advisory radio.
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.2.1 - Wide area optimization shall integrate the control of network signal systems with the control of freeways.
1.6.1.4 - Traffic Flow Optimization shall include a Control function that is responsive to both the current demand as well as the expected demand.
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.3 - The Device Control function shall provide the capability to exercise control over those devices utilized for traffic control.
1.6.3.3.1 - Device Control shall include the capability to control traffic signalization, including rapid modification of signalization parameters to respond to traffic requirements.
1.6.3.3.2 - Device Control shall include the capability to dynamically control traffic signing.
1.6.3.3.3 - Device Control shall include the capability to control freeway ramp metering.
1.6.3.3.4 - Device Control shall include the capability to exercise dynamic control over the infrastructure (such as reversible-lanes, turning restrictions, etc.).
1.6.3.4 - Device Control shall communicate control data to the following devices.
1.6.3.4(a) - Traffic signals.
1.6.3.4(c) - Information signs.
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.1.1.1(c) - Public safety sources.
1.7.1.1.1(d) - Media sources.
1.7.1.1.1(e) - Weather information sources.
1.7.1.1.1(f) - Transportation providers.
1.7.1.1.1(g) - Sponsors of special events.
1.7.1.1.1(h) - Hazardous condition prediction algorithms.
1.7.1.2 - The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents.
1.7.1.2.1 - The Incident Identification function shall use information from the following types of sources, where available, to identify existing incidents:
1.7.1.2.1(a) - Traffic flow sensors.
1.7.1.2.1(b) - Environmental sensors.
1.7.1.2.1(c) - Public safety sources.
1.7.1.2.1(d) - Media sources.
1.7.1.2.1(e) - Weather information sources.
1.7.1.2.1(f) - Transportation providers.
1.7.1.2.1(g) - Travelers.
1.7.1.2.2 - The Incident Identification function shall determine and continuously monitor at least the following characteristics of each existing incident:
1.7.1.2.2(a) - Type (including Terrain Hazards).
1.7.1.2.2(b) - Extent.
1.7.1.2.2(c) - Severity.
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.
1.10.3 - At all HRIs with active railroad warning systems, HRI shall manage the traffic in the intersection.
1.10.3.3 - HRI shall provide an Intelligent Intersection Controller (IIC) function to manage highway and rail traffic in the intersection.
1.10.3.3.5 - IIC function shall report real-time HRI traffic status as advisories or alerts.
1.10.5 - HRI shall provide a High Speed Rail (HSR) Subservice for HRIs on rail lines with operational speeds between 80 and 125 MPH.
1.10.5.2 - HSR shall provide special safety features to enhance safety.
1.10.5.2.6 - HSR shall provide HRI status to highway vehicles as either a "STOP FOR TRAIN" or a "PROCEED" indication.
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.5 - RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.4 - PSS shall warn travelers of impending security system deployment via local information systems.
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
5.3.11 - Evacuation Coordination shall provide an Evacuation Transportation Management (ETM) function to assist evacuation coordination personnel as they manage evacuation operations.
5.3.11.10 - ETM shall have a lane reversal management function.
8.0 - MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1 - MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.0 - ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities.
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
8.1.4 - Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers.
8.1.4.1 - RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished.
8.1.4.3 - RMCWPD shall coordinate information with other transportation agencies, including but not limited to:
8.1.4.3(d) - Traffic Management

Last updated: 02-11-05