PennDOT Traffic Signal Unified Command and Control Integration Guidelines April 8, 2020

Introduction The Bureau of Maintenance and Operations (BOMO) procured Intelight Maxview ATMS software as the statewide platform for unified command and control of traffic signals in 2018. Maxview is a web-based software which allows traffic signal controller databases to be managed and allows for real-time monitoring and operation of connected traffic signals. Maxview is integrated with OpenRoads ATMS software, which will allow TMC operators to implement predefined action sets along signal corridors for special events, work zones, and during incidents. Action sets could also be used to mitigate recurring congestion which impacts signalized corridors differently depending how much traffic diverts from a freeway to the arterial. This document is intended to provide PennDOT-specific configuration information for consistency in Maxview. For general information, refer to the Maxiew user manual in the Help menu. Logging into Maxview/Users and Groups Maxview can be accessed from the following URL using Internet Explorer: https://pdprsigmax01.penndot.lcl/MaxView/ (note: Maxview does not currently work with Google Chrome). This URL is only available when connected to the PennDOT network. Municipalities and contractors will need to have CWOPA credentials and VPN access to use Maxview, but the Maxview username and password are different than CWOPA credentials. Users may run Maxview directly through Internet Explorer or may install Maxview onto their computer from the login screen. Most functionality is available through Internet Explorer, with the exception of PennDOT TSAMS basemaps (only Bing Maps are available in Internet Explorer). The Bing Maps traffic layer may not work through Internet Explorer due to firewall restrictions, but will work in the locally installed version. The username and password to login are specific to Maxview. An administrator will be assigned for each District who can create new user accounts. District administrators will be responsible to maintain user lists, including deleting accounts in cases where a period of performance (such as for vendors or consultants) has expired. Administrators shall maintain records of user accounts in the following spreadsheet: P:\PENNDOT SHARED\Traffic Signals\Unified Command and Control\Maxview User Accounts.xlsx User Groups User permissions are determined by the group of which a user is assigned. A user may belong to multiple groups. The permission area include: • Acknowledge alarms: Permission to acknowledge/unacknowledged alarms • Database editing: Permission to view, edit, and download device database data. • Device Configuration and Graphics: Permission to modify existing device configuration and detailed layout. • Device Control: Permission to set, edit, and delete TOD, Action Set, and Manual Control commands • Device Control Plans: Permission to create, modify, and delete traffic responsive and action set plans. • DMS Messages: Permission to create, modify, and delete DMS messages (not used – OpenRoads will continue to be used for DMS) • Sync Time – Permission to manually sync and set device time • Viewers – Permission to view only – unless this is checked, users will have the ability to add intersections by default

The following user groups will be established in Maxview:

Group Scope of Access

Device Device Device Device

editing

Alarms

Control

Viewers

Database

Sync Time

Acknowledge

and Graphics

Control Plans Configuration PennDOT Central Office User All Districts X X X X X X PennDOT District User District X X X X X X Municipal User Municipality X X X X X X Maintenance Contractor Municipality X X X X X X Vendor Supplier District(s) X X X X X X View Only All Districts X District roles should be assigned to the district in which an individual is responsible. RTMC district signal staff may be assigned to all of the districts in the region. Municipal roles should be assigned to the group containing signals in their municipality. Vendor roles may be assigned on a municipal basis for maintenance contractors. Suppliers who are supporting signals in a larger area may be assigned to one or more districts. New user accounts may be created by a system administrator. Each district shall designate one or more system administrators who will be responsible for adding user accounts within their district. Central Office will also have System Administrators. Usernames should generally be the same as CWOPA user IDs to simplify management. Administrators will assign a default password when creating new accounts and share with the user. Users should change their password upon first login. This can be done by choosing System→Edit User Profile. External Access Whenever the first traffic signals within a municipality are added to Maxview, the Department will coordinate with the municipality in order for the municipality to obtain VPN access to Maxview. A traffic signal supervisor in the district where the municipality is located will send the following documents to the municipality: • Cover letter explaining Maxview, the process for gaining access, and available training opportunities • PennDOT Network Access Request form • PennDOT VPN Access Request form • PennDOT Maxview Access Request form The municipality (and associated vendors and/or consultants) will follow the procedures outlined in these documents to request PennDOT Network and VPN access. Device Tree Maxview operates with devices in a nested tree structure. An example of the Maxview device tree is shown below. Each group or section of the tree must have a unique ID number. Following is the numbering scheme: • Districts: district number X 100 (e.g. 100 for District 1, 1200 for District 12) • Counties: use PennDOT county number (1-67, alphabetical except Philadelphia is 67). • Municipality: use PennDOT municipality code (5 digits, first two digits are county code, last 3 digits are municipal code) • Systems: use TSAMS System ID (the unique ID in TSAMS doesn’t display on the main screen, but is in the URL bar as shown below. The above numbering scheme for groups will ensure each group has a unique number. Each signal device must have a unique ID. The last 6 digits of the TSAMS ID should be used, since this is a unique number.

Note, Maxview doesn’t show leading zeros on ID numbers.

Device Configuration New devices can be added by choosing System→Configuration→Devices. Then select Add Devices or Add Group. When adding a signal in a county and/or municipality that hasn’t already had a group set up, first set up the group with type “Section.” The group should be assigned to the appropriate parent to appear correctly in the tree. Counties should have the group assigned to a District. Municipalities should have the group assigned to a county. Smaller groups should correspond to signals that are usually coordinated together. This allows the time of day patterns to be set for the group and applied to all the signals in that group. These have the type “Group” and the Group assigned to the municipality. Following are key tips when configuration signal controller devices: • Name should be a short abbreviation for the intersection, in the following format: [Main Street] at [Minor Street] [Permit Number] [(System Permit Number)] • Main Street and Side Street names may include SR numbers • Note field can be used for other information, including firmware version, system permit number, permit number, etc. The note field is also viewable in ATMS. The following must be included in the notes field when applicable: o If the intersection has adaptive control, indicate the adaptive product being used (such as Rhythm InSync, Centracs, etc.) o If the firmware version of the controller doesn’t exactly match one of the available options in Maxview, indicate the actual firmware version • Ensure the proper group is selected (either a system group or a municipality) • Ensure “Enable Dynamic Objects” is selected, which speeds up polling • For Econolite Controllers, be sure to set the Send Port to “501” • The Host/IP Address is the IP address of the controller • Polling rate should be set to use system polling, or disable if the signal is still active in another signal software Controller time zone should be set to GMT -05 and Deselect “Disable Time Autocorrect” to ensure time synchronization commands from Maxview are correctly interpreted by the controller. Intersection Graphics Intersection graphics are defined in the configuration for the device under the Location & View tab. There are two sets of graphics: 1) Location & Directions, and 2) Detail View. Click Edit Location & Directions to locate the intersection. Pan the map to the intersection location, then right click at the center of the intersection and choose “Set Center Here.” The intersection can also be dragged on the map. The angle can be adjusted at the top of the window to align the approaches. Click on each approach in the drawing and then set the Direction Type (Main Street, Side Street, Other) and the Phase Number in the top panel. Click Edit Detail View to define the detailed graphics for the intersection. There are templates which can be used for typical configurations. Click on individual lanes for additional configuration options, including the icon type (lane configuration), angle, phase number, and size. Separate arrows shall be provided for each lane. Click the Add New button in the button right to add additional lanes. An example completed intersection is shown below:

External Links External links provide access to third-party vendor systems, such as detection systems. Following are examples for systems currently in use: System Name External Link Name Type URL InSync Adaptive InSync – Intersection Name Browser Link http://xx.xx.xx.xx/cameraViewMulti.php Processor Autoscope Autoscope – Intersection Application “C:\Program Files (x86)\VideoLAN\VLC\vlc.exe” Name Detector rtsp://xx.xx.xx.xx/video Gridsmart Gridsmart – Intersection Browser Link Copy and paste Camera API (Quadview)* Name Wavetronix Wavetronix – Intersection Application “C:\Program Files\Wavetronix\SmartSensor Name Detector Manager Matrix v2.0.0\Bin\SSM Matrix.exe” http://xx.xx.xx.xx Rhythm Hawkeye Hawkeye – Intersection Application “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” http://xx.xx.xx.xx:5001/login *To obtain Gridsmart Camera API Quadview URL: 1. Select Info 2. Select Show GRIDSMART API 3. Copy QUADVIEW link

ATMS Integration PennDOT’s Traffic Management Centers (TMCs) use OpenTMS as the Advanced Transportation Management System (ATMS). OpenTMS is used to manage various types of ITS devices. PennDOT has built a module in OpenTMS to allow TMC operators to implement Maxview action sets, such as in response to a freeway incident, planned event, or work zone that will divert traffic to a signalized corridor. Action Sets To create Action Sets in Maxview, choose Device Configuration→Action Set Control. Then click on “Action Set Configuration.” When creating an Action Set, the following parameters should be set: • Number – pick a unique number. It is recommended to use the route number as the beginning of the number. • Name – name should reflect the problem that is being addressed, such as the name of the freeway, direction, and the location of the detour (Exit to Exit). The naming should be consistent with the names of established detours in RCRS. • Operational Impact – choose from High, Medium, Low. o High – events which result in the highest amount of traffic on the signalized corridor. This could be the result of a high volume diversion or could be a lower volume diversion during peak hours. These plans would be expected to cause more delays on side streets intersecting the corridor. o Medium – events which will increase the volume on the signalized corridor, but the volume is not high enough to justify severe delays for intersecting side street traffic. These types of events could be a freeway with a lane closure where not all traffic is diverted. o Low – events where the traffic volume increase on the arterial should be prioritized with offsets in the direction of the diversion, but the cycle length is kept lower to continue serving intersecting side street traffic with minimal delay. • Notes – notes should indicate more specific details about what the plan will do, including the name of the signalized corridor where the traffic detoured. Include information about what the operational impact means specific to the corridor. Examples of types of incidents for which the action set should be utilized may also be included (e.g. full closure during peak times, road work X during off peak times). Alarms should be set in the controller to turn on Alarm 10 whenever a diversion plan is activated. This can normally be done through the logic processor in the controller. The alarm can be used to trigger email notifications in Maxview, such as notifying a municipality whenever a diversion plan is implemented. It is recommended to use consistent plan numbering for incident management coordination plans in signal controllers for ease of establishing action sets, although this is not required. The following are suggested: • Eastbound diversion – Plans 50-59 • Westbound diversion – Plan 60-69 • Northbound diversion – Plan 70-79 • Southbound diversion – Plan 80-89 Plans should start with the first available number for the applicable direction. All of the diversion plans can be set to the same alarm number for the purpose of notifications. System Detectors System detectors can be added through System → Configuration → System Detectors. Then click the “Add” button at the bottom left of the window to create a new system detector. System detector numbers should be assigned using the number for the system and then the detector number within the system. For example, detector 4 in system 1234 would have system detector number 12344. System detector are associated to detector channel(s) at a particular intersection in the “Source Det/Lane Number(s)” box. Multiple detector channels may be entered as a comma-separated list if there are separate detection zones by lane, and the data will be averaged across the lanes. Signal Connections to Maxview Districts should seek to connect any signals which are on the Commonwealth network to Maxview to minimize the need to maintain multiple software platforms and ensure ATMS functionality at the maximum number of locations. Existing central systems with IP communications on the Commonwealth network can be migrated relatively easy to Maxview. Older legacy systems with serial communications and/or dial-up connections should be reviewed to determine if the communication and/or controllers can be upgraded as part of a project to integrate with Maxview. For projects where signals controllers will be replaced, the specifications should indicate the new controller must be compatible with Maxview. The controller manufacturer may provide their MIBs to PennDOT for integration of new controller types, or they may provide controller software which provides support for Intelight Maxtime controller objects. Generally, multiple central systems cannot simultaneous poll a signal controller. Although the intent is to provide full functionality for controllers through MIB integration, there may be cases where a vendor- specific central system is needed for operation, such as adaptive control. In those cases, the signals should be set up and configured in Maxview, but polling should be disabled. The primary control will be from the other vendor’s software. This scenario would allow the signal to be deactivated in the other software to run an action set through ATMS if the need arises. Maxview Help The Help menu contains a link to the Maxview User Manual, which can be consulted for more specific details about commands.