where applicable, one or more test cases. Once completed, this matrix will be used to support quality compliance activities during all phases of the project’s life cycle. The high-level verification matrix below is based on the I-210 Pilot - System Requirements document. Acceptance testing is a subset of this verification matrix. Testing is limited to data management, decision support, and corridor management subsystem matrix elements that are listed with a criticality of High. As resources permit, medium and low criticality tests will be defined when the requirement is addressed. Institutional Job Tasks are not considered part of this testing. Tests that are part of the vendor supplied corridor management system are generally tested as part of the vendor system evaluation as identified in the following section. Table 83 Test Matrix Test REQ ID Description Criticality Related Subsystem Test Cases/Description Test Method Notes or comments Test Matrix for I-210 pilot project Institutional Requirements Corridor Strategic Planning The Corridor Manager, in coordination with stakeholders, shall track anticipated changes to the ICM corridor’s roadway network. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in coordination with stakeholders, shall track anticipated changes to the ICM corridor’s transit networks of interest. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in coordination with stakeholders, shall track anticipated changes to the corridor’s traffic control devices (traffic signals, ramp meters, others). M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in coordination with stakeholders, shall track anticipated changes to the corridor’s traveler information devices (CMS, extinguishable trailblazer signs, etc.). M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
Corridor Champions Corridor Champions shall be high-level staff persons or elected officials with interest in transportation/transit issues. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Corridor Champions shall have longevity (for example, if an elected official, someone who is not termed out in the next year or so, if possible). M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. A list of current Corridor Champions from each stakeholder agency shall be developed and maintained by the Outreach and Communications Manager. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The list of current Corridor Champions shall be distributed to all project stakeholders. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Corridor Champion(s) shall be replaced if previous champion(s) leave. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Organizational Composition and Structure The Connected Corridors Steering Committee shall define roles, responsibilities, and reporting structures for the ICM system. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Job descriptions shall be written for supporting ICM roles. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Stakeholder agencies shall ensure that ICM staff are in place and trained. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Oversight and advisory committees shall be set up and maintained. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Management Structure and Processes Processes shall be established to manage the ICM corridor. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
Managers shall be identified to manage the ICM corridor. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Stakeholders shall develop new procedures and practices supporting ICM corridor management objectives. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Caltrans, in consultation with system stakeholders, shall maintain a Risk Register. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Interagency Trust and Communication All agencies having a potential interest in ICM corridor operations shall be engaged in development, implementation, and operational ICM activities. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Clear, consistent communication mechanisms shall be established among the corridor stakeholders. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Quarterly meetings shall be held to keep ICM system stakeholders updated on system and corridor activities. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Stakeholder agencies shall establish and maintain communications mechanisms with other stakeholder agencies. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Information requests about the ICM system shall be appropriately followed up. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Interagency Agreements A Project Charter shall be drafted to get stakeholder agencies to agree on initial roles and responsibilities. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. A Memorandum of Understanding (MOU) shall be signed by project stakeholders to get formal agreement on expected roles and responsibilities. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. An Operations & Maintenance (O&M) Plan shall be signed by corridor H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
stakeholders. The Outreach and Communications Manager, with assistance from corridor stakeholders, shall determine whether additional agreements may be needed to support system operations. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Management of agreements shall be the responsibility of the Outreach and Communications Manager. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Stakeholder agencies shall sign in a timely manner agreements submitted for their approval. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Developed agreements shall be maintained, updated, and/or amended throughout the life of the project. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Stakeholder agencies shall participate in the review and updating of documents related to the operation of the ICM system. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Funding for ICM System Potential funding sources shall be researched on an ongoing basis. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Adequate support shall be provided for the development and submission of funding applications. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Approved funding sources shall be managed, and necessary reports completed and submitted. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Training and education Adequate training shall be provided to individuals responsible for ICM operations. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
Manager. Corridor Monitoring Static Transportation Network Characteristics Roadway operators shall maintain and communicate to the Corridor Manager definitions of roadway facilities connected to the ICM Environment. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Parking facility operators shall maintain up-to-date definitions of park-and-ride facilities connected to the ICM Environment. L Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Transit operators shall maintain up-to-date definitions of transit elements connected to the ICM Environment. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager shall ensure that network definitions are up to date in all locations within the ICM Core system. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Asset Inventory and Health Management The ICM Core System shall continuously assess the health status of devices used to monitor traffic conditions. H Data Hub/DSS Verify the ICM Core System shall monitor for fault and error messages that may be sent by individual traffic detection devices. Verify valid PEMS sensor data monitoring traffic conditions. Verify faulty & erroneous data from sensors can be detected inventory checks on PEMS sensors. Verify flow checks and flow balances are stored in Cassandra. Verify the ICM Core Connect to data endpoint, AMQ endpoint to verify the data is correct Check for valid sensor data Check that the quality indicator is present & correct, the sensors are giving right information Automation test candidate
measurement on general traffic lanes (live PEMS data). Verify latency of one minute or less for speed measurement on HOV lanes (live PEMS data). The ICM Core System shall monitor in real time traffic conditions on key corridor arterials. H Data Hub Verify latency of one minute or less traffic flow measurements from sensors operated by Caltrans along key corridor arterials (all the arterials ie Los Angeles County, City of Pasadena, City of Arcadia, City of Monrovia, city of Duarte). Verify latency of one minute or less data collected by travel time measurement systems operated by local agencies along key corridor arterials (all the arterials ie Los Angeles County, City of Pasadena, City of Arcadia, City of Monrovia, city of Duarte). Connect to Intersect-ion signal sensors data endpoint and verify the data is there and correct Connect to travel time sensing data endpoint Transit Monitoring The ICM Core System shall monitor for significant transit service disruptions along relevant transit routes within the corridor. M Data Hub Testing to be defined when the requirement is addressed. The ICM Core System shall monitor average ridership along transit services of interest within the corridor L Data Hub Testing to be defined when the requirement is addressed. The ICM Core System shall report on monitored transit operations within the ICM corridor. M Corridor Management Testing to be defined when the requirement addressed. Park-and-Ride Monitoring The ICM Core System shall monitor in real time availability at facilities operated by participating agencies within L Data Hub Testing to be defined when the requirement addressed.
the corridor. The ICM Core System shall report on parking availability at facilities under ICM surveillance. L Corridor Management Testing to be defined when the requirement addressed. Corridor Performance Metrics The ICM Core System shall calculate and store metrics summarizing overall corridor performance. H Decision Support Verify Productivity metrics for the entire corridor: Vehicle-miles traveled (VMT) Vehicle-hours traveled (VHT) Vehicle hours of delay Vehicle occupancy (person miles traveled, person hours traveled) Estimate average vehicle occupancy factor Connect to estimation metric endpoint & AMQ endpoint and check the data is there and correct Corridor performance test for geographic area/time spans Automation test candidate The ICM Core System shall calculate and store metrics summarizing the performance of mainline freeway operations. H Decision Support Verify vehicle based metrics on freeway segment (estimation engine, vehicle sensing): Total vehicle flow Vehicle-miles traveled (VMT) Vehicle-hours traveled (VHT) Average travel time across segment Average speed across segment Vehicle-hours of delay (VHD) Average delay per vehicle Vehicle Occupancy Factor: Total person flow Vehicle Occupancy Factor: Person-miles traveled (PMT) Vehicle Occupancy Factor: traveled (PHT) Reliability metrics: Travel time index Reliability metrics: Connect to estimation metrics endpoint & AMQ and check the data is there and correct Corridor performance test Automation test candidate
Buffer index (extra time that travelers must add to their average travel time when planning trips to ensure on-time arrival) HOV lane data from sensors The ICM Core System shall calculate and store metrics summarizing the performance of freeway ramp operations. H Decision Support Verify vehicle based metrics on freeway off-ramp (estimation & sensing): Total vehicle flow Vehicle-miles traveled (VMT) Vehicle-hours traveled (VHT) Vehicle-hours of delay (VHD) Average delay per vehicle Vehicle occupancy factors: Total person flow Vehicle occupancy factors: traveled (PMT) Vehicle occupancy factors: traveled (PHT) Connect to estimation metrics endpoint & AMQ endpoint and check the data for the freeway ramps is there and correct Corridor performance test Automation test candidate The ICM Core System shall calculate and store metrics summarizing the performance of arterial traffic operations. H Decision Support Verify the ICM Core System shall calculate and store the following based metrics on arterials: Total vehicle flow Vehicle-miles traveled (VMT) Vehicle-hours traveled (VHT) Verify the ICM Core System shall estimate and store the following person-based productivity metrics based on available average regional vehicle occupancy factors: Total person flow Person-miles traveled (PMT) Person-hours traveled (PHT) Verify the ICM Core Connect to estimation metrics endpoint, AMQ endpoint and check the data is there and correct Arterial corridor performance test Automation test candidate miles
between key intersections on arterial segments along potential detour routes. The ICM Core System shall attempt to use available sensor data to estimate traffic conditions on roadway sections of interest without instrumentation. H Decision Support Verify the estimation is using the available sensor data. Verify that the traffic on all roadways, with or without instrumentation are included in estimations. Connect to estimation endpoint & AMQ endpoint and the data is there and correct (with sensors or not) Automation test candidate Historical Pattern Determination The ICM Core System shall determine historical traffic patterns from available traffic data. H Decision Support Verify for each traffic detector, ICM core shall determine upon request the following statistics over a specified period: Average measured volumes for thru, and movements Volume variance for each movement Average flow measurement Average sensor occupancy Average speed measurement (if available) Flow variance Sensor occupancy variance Verify for each intersection for which turn movements are available, the ICM Core System shall determine upon request the following statistics over a specified period: Average measured volumes for thru, and movements Volume variance for each movement For each roadway segment for which Connect to database to check the data is there and correct Automation test candidate
incidents and events. System stakeholders shall identify or create, maintain, and distribute ramp metering plans to be used during incidents and events. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. System stakeholders shall determine messaging equipment that may be used to support the implementation of response plans. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. System stakeholders shall determine equipment (vehicles and other portables) that may be used to support the implementation of response plans. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. System stakeholders shall determine personnel available for deployment during an incident or event. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. System stakeholders shall determine typical information to be sent to agency personnel when responding to an incident or event. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. System stakeholders shall determine messages to be posted on fixed and/or portable CMS devices when responding to an incident or event. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in consultation with all relevant stakeholders, shall determine the information to be sent to 511 services. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in consultation with all relevant stakeholders, shall determine the information to be sent to HAR stations used as part of response plans. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager, in consultation with all relevant stakeholders, shall determine the information to be sent to third-party providers. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The ICM Core System shall include a function for stakeholders to specify predefined response plans, i.e., specific sets of response actions that may be H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
information permitting to the generation of a report. Rule Creation and Management Decision Support Rules The ICM Core System shall include a function for users to define rules to be used in the development, evaluation, selection, and implementation of response plans. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Rules for determining the existence of an incident shall be defined and maintained. M Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Rules for determining the severity of an incident shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Rules for determining the zone of influence of an incident or event shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Rules for assessing the level of impact of an incident or event on corridor operations shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Rules for building response plans from a set of possible individual response actions shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Verify the rules exist for creating response plans. Manual test Rules for handling special management or operational situations shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Verify rules limiting the use of specific roadway elements based on specific situations shall be defined and maintained. Rules limiting the use of specific roadway elements without sufficient capacity shall be defined and maintained. Rules limiting the use of specific roadway elements based on the Manual test
operational status of traffic management devices on these elements shall be defined and maintained. Rules for selecting a recommended response plan among a set of alternate plans shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Verify alternate plans are defined. Manual test Rules for sending response plan instructions to corridor assets shall be defined and maintained. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Manual test Rules for determining agency personnel who should be notified of a response planning action shall be defined and maintained. H Corridor Management Verify rules for determining agency personnel who should be notified of a response planning action shall be defined by traffic engineers from stakeholder agencies. Verify rules exist for defining response plan notification. Manual test The ICM Core System shall include a function for Traffic Engineers to specify the conditions under which the implementation of an approved response plan can be canceled. L Corridor Management Testing to be defined when the requirement is addressed. System users shall specify the level of automation required for the approval of submitted modifications to active response plans. L Corridor Management Testing to be defined when the requirement is addressed. Decision Support shall provide a means for users to group and categorize rules. M Corridor Management Testing to be defined when the requirement is addressed. Rules Testing and Evaluation Proposed modification to existing rules shall be validated over a user-defined period prior to being introduced into the production system. M Corridor Management Testing to be defined when the requirement is addressed. The ICM Core System shall provide an environment allowing proposed new rules or rule modifications to be tested and validated prior to H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria.
their implementation. The ICM Core System shall conduct a rules test, exercising the rules using test data on a regular basis and providing a pass/fail check for the results of each rule execution. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. The Corridor Technical Manager shall conduct weekly and quarterly evaluations of the rules and their execution. M Corridor Management Not part of system testing. Will be evaluated during post implementation review. Rule Documenting and Archiving The ICM Core System shall provide a means for users to archive rules within the system. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. All developed rules shall be stored in a format usable by the DSS rules engine. H Data Hub Testing to be defined when the requirement is addressed. The ICM Core System shall utilize a configuration management system to manage rules. M Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Post-Incident/Event Analyses The Corridor Manager shall conduct a post-incident analysis review with all affected agencies within one week of each significant event. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Quarterly Operational Reviews The Corridor Manager shall conduct a quarterly review of the operational effectiveness of the ICM Environment. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. As part of the quarterly effectiveness evaluation, the Corridor Manager shall assign a score to the observed effectiveness of response planning activities. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager shall use results from quarterly operational assessments of decision support operations H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
incidents and events within the corridor, as well as future events scheduled to start during the evaluation period. Verify the model it has run, has the correct state info and the info from other incidents. Verify the predictions that are run include all other incident info and the current estimation. The ICM Core System shall only conduct operational assessments of incidents and events that have been confirmed to exist. H Decision Support Will be part of vendor supplied CMS evaluation and acceptance criteria. Verify CMS only sends confirmed incidents. Based on the results of the incident impact assessment, active incidents or events shall be categorized using rules specified in response planning as having a minor, medium, or major impact on corridor operations. H Decision Support Verify ranking (1- 10) of response plan is received. Connect to data hub endpoint that sends the information to the CMS. Automation test candidate Response Plan Generation The ICM Core System shall assemble response plans for all incidents, unscheduled events, and planned events expected to generate average delays of 5 minutes or greater to travelers. H Decision Support Verify the ICM Core System shall assemble response plans for freeway incidents expected to last longer (set a limit in the rules engine 10min/20 mins, beyond the limit and below the limit) than the number of minutes defined in the response plan trigger rules and expected to generate average delays of 5 minutes or greater to travelers. Verify the ICM Core System shall assemble response plans for arterial incidents expected to last longer than the number of minutes defined in the response plan trigger rules and expected to Feed a bunch of incidents and see the correct response for various limits that are put in Automation test candidate Manual test
with the response plan. For each evaluated response plan, the ICM Core System shall produce a confidence index reflecting the potential ability of the proposed actions to positively affect corridor operations. M Decision Support Testing to be defined when the requirement is addressed. Selection of Recommended Response Plan The ICM Core System shall always consider a “do nothing” scenario as a potential recommendation. H Decision Support Verify every incident generates a “do nothing “response plan. Automation candidate The ICM Core System shall rank all developed response plans based on their ability to improve corridor operations within the identified zone of influence of the incident or event that triggered the response planning. H Decision Support Response plan ranking shall be made against the “do nothing” scenario The ICM Core System shall assign a higher ranking to response plans reducing incurred delays within the zone of influence of the incident or event. The ICM Core System shall assign a higher ranking to response plans increasing the number of vehicles or travelers able to travel through the zone of influence of the incident or event. The ICM Core System shall assign a higher ranking to response plans where all involved corridor assets are available and in good operating condition. The ICM Core System shall assign a higher ranking to response plans having a higher confidence index. The ICM Core System shall rank a response plan as “Unacceptable – Jurisdictional Restricted” if implementation of the plan would violate a mandatory jurisdictional restriction (such as a
automatically reassess the adequacy of the previously recommended response plan if there are changes to important characteristics of the incident or event being responded to. Support reassessed if the incident duration is more than 15 minutes. The ICM Core System shall automatically reassess the adequacy of the previously recommended response plan if there is a change in the number of lanes affected. The ICM Core System shall automatically reassess the adequacy of the previously recommended response plan if the expected duration of the incident or event being responded to changes by more than 15 minutes. The ICM Core System shall include a function for TMC and TCS operators to propose changes to an implemented response plan. L Corridor Management Testing to be defined when the requirement is addressed. The ICM Core System shall submit for review and approval all proposed modifications to an active response plan. L Corridor Management Testing to be defined when the requirement is addressed. Response Termination Following the termination of an incident or event, the ICM Core System shall continue to monitor, evaluate, and update the active response plan until travel conditions within the corridor have returned to an historical average. H Decision Support Verify traffic conditions are assessed every 5 minutes after response plan termination. Following the closure of an incident or event, the ICM Core System shall continue assessing travel conditions within the corridor every 5 minutes to determine whether travel conditions have returned to historical average. Traffic conditions shall be assumed to have returned to historical average when observed conditions are within the range of conditions typically observed for the
given time of week and time of day in the absence of incidents or events. Following the termination of an incident or event, active response planning shall continue until travel conditions within the corridor have returned to a historical average. H Decision Support Verify Post Incident response plan is in place past the termination of response plan. Following the closure of an incident or event, normal asset operations shall only be resumed once travel conditions within the corridor have returned to a normal state for the given time of day and day of week. Following the identification of a need to continue response planning activities past the termination an incident or event, the ICM Core System shall assign the Response” label to the active response plan until response activities can formally be terminated. The ICM Core System shall return corridor assets to normal operations when corridor operations have returned to normal. H Corridor Management Verify once closure of an incident all control device return to normal operation. Upon determining that corridor operations have returned to normal after the closure of an incident or event, the ICM Core System shall instruct all control devices for which operation has been altered during the incident/event response to return to their defined normal operations for the time of day and day of week. Prior to terminating response planning activities, the ICM Core System shall check that all control devices for which operation has been altered during the
in a consistent format. occurring within the corridor. Implementation Override PI-4.1 Prior to initiating the implementation of an approved response plan, the ICM Core System shall check whether changes in corridor operations may warrant the development of a new response plan. M Decision Support Testing to be defined when the requirement is addressed. PI-4.2 The ICM Core System shall initiate the development of a new response plan if changes in corridor operations render the currently approved response plan obsolete before its implementation. L Decision Support Testing to be defined when the requirement is addressed. Response Plan Implementation Tracking PI-6.1 The ICM Core System shall track the implementation progress of approved response plans. H Corridor Management Verify implementation progress of approved response plans is tracked. Verify each recommended action implementation is logged. Verify any failure to implement a change request is logged. PI-6.2 Upon termination of an incident or event response plan, the ICM Core System shall ensure that all assets are returned to the state of operation that would have been in effect had an incident or event not occurred. H Corridor Management Verify upon termination of an incident or event response plan all assets are returned to state of operation. PI-6.3 The ICM Core System shall inform all TMC/TCS operators and transit field supervisors whether a recommended response has been successfully implemented. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Verify ICM core shall inform all TMC/TCS operators and transit field supervisors whether a recommended response has been implemented, ICM Core System shall inform TMC/TCS
Data Management Data Quality The Corridor Technical Manager and Corridor Data Analyst shall develop a data quality management program for the ICM Environment. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. For the ICM Environment, data quality requirements shall be specified for all data sources and system data elements. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Data quality shall be maintained. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Data Management Needs Geographic and Institutional Data Data Management shall store and provide access to information characterizing the corridor’s institutional environment. M Data Hub Testing to be defined when the requirement is addressed. Asset Inventory Data Management shall store or provide access to information characterizing freeway segments. H Data Hub For each freeway segment, Data Management shall store or provide access to the following information: General characteristics: Number of traffic lanes Posted speed limit Upstream mainline freeway segments, on-ramps, and connectors feeding traffic to the segment Downstream mainline freeway segments, and Connect to Road Network Information service endpoint
adaptive, etc.) HOV vehicles allowed bypassing the ramp meter Restrictions: Vehicle height clearance under bridges or structures Truck use restriction For each off-ramp, Data Management shall store or provide access to the following information: General characteristics: Number of traffic lanes Posted speed limit Freeway segment(s) feeding traffic to the off-ramp Roadway segment(s) receiving thru, and right-turning traffic from the off-ramp Restrictions: Vehicle height clearance under bridges or structures Truck use restriction Data Management shall store or provide access to information characterizing arterial segments. H Data Hub For each arterial segment, Data Management shall store or provide access to the following information: General characteristics: Number of through traffic lanes Posted speed limit Roadway segment(s) feeding traffic to the arterial segment Roadway segments receiving thru and right-turning traffic from the arterial segment Presence of hard median barrier Restrictions: Connect to Road Network Information service endpoint
Will be part of vendor supplied CMS evaluation and acceptance criteria. Testing to be defined when the requirement is addressed. Data Management shall receive every 5 minutes or less information updates about planned lane closures scheduled to occur during the current operation day. Connect to the LCS schedule endpoint for the incidents and events Data Management shall receive real-time data characterizing the operational performance of relevant transit services within the corridor. M Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive real-time data characterizing observed ramp metering operations within the corridor. H Data Hub For each ramp meter, Data Management shall receive the following information each time a change in metering rate is implemented within one minute of the time of the change: Time ramp metering rate was changed Metering rate that was activated Connect to the Ramp Meter State endpoint for verifying the relevant data Data Management shall receive real-time data characterizing the current operational status of traffic signals in operation within the corridor. H Data Hub For each signalized intersection under ICM surveillance, Data Management shall receive at the end of each signal cycle the following operational information: Signal timing plan in effect Start time of signal cycle Signal cycle length Signal coordination status Signal offset Offset reference phase Connect to the Intersection Signal State endpoint Data Management shall store information characterizing the typical range of values associated with the data M Data Hub Testing to be defined when the requirement is addressed.
archive ICM Core System configuration, security, error/fault, and status information. Data Management shall archive ICM Core System rules information. Data Management shall archive all asset capability data provided to the ICM Core system. Data Management shall archive data collected as part of ICM Core System operations. H Data Hub Verify the back up to AWS glacier. Data Management shall archive information detailing the response plans that were developed and implemented in response to specific incidents or events. Data Management shall archive traffic estimation and prediction information. Data Management shall provide a means for users to configure archiving functions. M Data Hub Testing to be defined when the requirement is addressed. Data Management shall archive selected data sets for a period of 5 years. M Data Hub Testing to be defined when the requirement is addressed. Glacier will keep it for 5 years. Maintenance Logs Data Management shall collect and archive all maintenance alerts and notifications generated by the ICM Environment and Core System. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall collect and archive all maintenance activity logs entered by participating agencies. L Data Hub Testing to be defined when the requirement is addressed. Administrative Logs Data Management shall log when users access the system. M Corridor Management Testing to be defined when the requirement is addressed. Data Management shall log ICM Core System and subsystem activities. M Corridor Management Testing to be defined when the requirement is addressed. Data Management shall log M Corridor Testing to be defined when
and I-605 freeways under ICM management. Data Management shall receive data from participating probe data providers. L Testing to be defined when the requirement is addressed. Data Management shall receive operational data from transit management systems. M Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive traffic signal operational data from traffic management systems operated by local agencies. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive operational data from electronic traveler information message signs operated along corridor roadways of interest. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive operational data from HAR stations within and around the corridor used to disseminate information to travelers. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive incident information from dispatch systems used by first responders. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive planned lane closures from systems maintained by roadway management agencies. M Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive alerts from regional notification systems. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall receive incident data from crowd-sourcing applications. L Data Hub Testing to be defined when the requirement is addressed. Data Management shall use communication protocols and methods for incoming data appropriate to the design needs of the system. H Data Hub Verify the stored data is in the right format. Incoming data eg: TMDD messages are correct. Data Management shall use data transformation methods for all incoming data appropriate to the specific data formats and communication protocols and its intended use within the system. Possible transformation methods may H Data Hub Design review is not a system test.
information systems used by truck fleet dispatchers and truck operators. Data Formats The ICM Environment shall store or provide access to data in commonly used formats. H Data Hub Verify to the extent possible, the ICM Environment shall transmit data in the Transportation Management Data Dictionary (TMDD) or National Transportation Communications for Intelligent Transportation System Protocol (NTCIP) format. Verify to the extent possible, the ICM Environment shall store or provide access to collected transit route data in the General Transit Feed Specification (GTFS) format. Collected traffic data shall be aggregated in intervals no longer than 15 minutes. All data aggregations shall be appropriate to the intended use of the information. M Data Hub Testing to be defined when the requirement is addressed. All data used by the ICM Environment shall be stored in electronic format. M Data Hub Testing to be defined when the requirement is addressed. Data Verification and Validation Data Management shall validate all field measurements. H Data Hub Data Management shall validate unverified traffic data obtained from traffic sensor data, using validated historical data and expected values for the period associated with the data Data Management shall validate unverified traffic volume data obtained from traffic sensor data, using validated Connect to Freeway detector data & intersection detector endpoint, and verify the quality indicators are there and correct Automation test candidate
Data Management shall validate received weather data, using validated historical data and expected values for the period associated with the data. Data Management shall validate all received control device data that have not been previously validated by the system supplying the information. H Data Hub Verify Data Management shall validate unverified operational data received from control devices connected to the ICM system, using validated historical data and expected values for the period associated with the data. Data Management shall validate unverified signal timing data received, using validated historical data and expected values for the period associated with the data. Data Management shall validate unverified ramp metering data received, using validated historical data and expected values for the period associated with the data. Data Management shall validate unverified fixed CMS operational data received, using validated historical data and expected values for the period associated with the data. Connect to CMS, Ramp meter, intersection signal state endpoint, and validate the data is correct Data Management shall mark as “potentially invalid” received field measurements data failing a verification or validation test. H Data Hub Verify Data Management shall mark as “potentially invalid” unverified flow measurements received from field devices or systems deviating by more than two standard deviations from the Connect to Freeway detector & Intersection detector & travel time detector endpoint and
measurement data that have been flagged as “potentially invalid.” acceptance criteria. Data Storage and Warehousing Data Management shall store in a central repository all data utilized or created by the system not being stored elsewhere. H Data Hub Design review test, not a system test. Data Management shall store in a central repository all data characterizing the operation of the ICM Core System not stored elsewhere. H Data Hub Design review test, not a system test. Data shall be stored using state-of-the-art technology by methods that are extensible and scalable. H Data Hub Design review test, not a system test. Data shall be stored using technologies appropriate to the design needs of the system (performance, cost, size, etc.). Technologies shall include both SQL and technologies as dictated by design needs and constraints. H Data Hub Design review test, not a system test. Data Documentation and Maintenance The ICM Environment shall have an ICM data dictionary. H Data Hub Verify System interface design spec doc. The Data Dictionary shall contain a listing of all Data Hub data elements, their definition, data format, and size. The Data Dictionary shall contain a listing of all data sources and their data elements, their definition, data format, and size. The Data Dictionary shall contain a listing of all externally available data provided by the system, including their data elements, their definition, data format, and size. The Data Dictionary shall
traffic state estimates. Verify Decision Support shall provide an overall confidence level for all current traffic estimates. Decision Support shall include in its current traffic state estimation effects associated with the operational status of traffic control devices. H Decision Support Verify Decision Support shall include in its current traffic state estimation the effects of the traffic signal control plan currently in use at individual signalized intersections. Verify Decision Support shall include in its current traffic state estimation the effects of current ramp metering operations on freeway on-ramps and connectors. Connect to arterial estimation endpoint & AMQ check if the data is there and correct Automation test candidate Decision Support shall provide reliable estimates of current traffic conditions within the corridor. H Decision Support Testing to be defined when the requirement is addressed. Decision Support shall compare the current corridor traffic state to historical traffic patterns and provide a measure of variability from the normal historical traffic pattern. Decision Support Testing to be defined when the requirement is addressed. Corridor Traffic State Forecasting Decision Support shall include a function to produce forecasts of future states of vehicle traffic on roadway links under ICM consideration. H Decision Support Verify Decision Support forecasts shall compute and display the following basic traffic characteristics for each roadway link under ICM consideration at the end of each forecast interval: Forecasted average traffic flow rate across the link Forecasted average traffic speed across the link Forecasted average traffic density along the link Verify Decision Support forecasts shall compute Connect to prediction endpoint & active MQ and the data is there and correct Automation test candidate
on the link since start of forecast interval Traffic forecasts shall be based on the latest traffic and demand information available for the corridor at the time the forecast is requested. H Decision Support Verify Decision Support shall conduct traffic forecasts using the latest field and estimated data available at the time the forecast is requested. Verify Decision Support shall not attempt to replace the set of field and estimated data used to conduct a forecast in the middle of a forecasting process. Connect to prediction endpoint & active MQ and the data is there and correct Automation test candidate Decision Support shall include in its traffic forecasts the effect of the current working state of all traffic sensors set to supply information to the ICM Core System. H Decision Support Verify Decision Support shall evaluate the effect of the quality of incoming information on the quality of its traffic forecasts. Verify Decision Support shall evaluate the effect of missing information on the quality of its traffic forecasts. Verify Decision Support shall calculate and display an overall confidence level for all traffic forecasts. Connect to prediction endpoint & active MQ and the data is there and correct Automation test candidate Decision Support shall complete a traffic forecast for each response plan developed (known as a response plan forecast). H Decision Support Verify response plan is in place as per prediction results. Decision Support shall include a function for ICM Core System users to specify under which circumstances traffic forecasts of existing control strategies (“no change scenario”) are to be executed. H Corridor Management Testing to be defined when the requirement is addressed. Decision Support shall include a function for ICM Core System users to specify the time horizon to which traffic forecasts are to be executed (forecast over the next 30 minutes, 1 hour, 2 hours, etc.). H Corridor Management Testing to be defined when the requirement is addressed. Decision Support shall include a function for ICM Core H Corridor Management Testing to be defined when the requirement is addressed.
System users to specify the data reporting interval within a traffic forecast (e.g., forecast data reported every 5 minutes, 15 minutes, 1 hour, etc.) Decision Support shall include a function for ICM Core System users to specify the interval at which Decision Support is to execute traffic forecasts (e.g., new forecast every 15 minutes). H Corridor Management Testing to be defined when the requirement is addressed. Decision Support shall be able to complete forecasts of corridor operations in a timely manner. H Decision Support Verify predictions are completed within 5 minutes. Decision Support shall be able to complete a traffic forecast within 5 minutes of receiving a forecast request. The Corridor Manager shall periodically ensure the accuracy of the traffic forecasts produced by Decision Support. H Institutional Job Tasks Testing to be defined when the requirement is addressed. Decision Support shall archive the results of traffic forecasting activities for future analyses. H Decision Support Verify data hub stores the predictions and PEMS saves this information. Decision Support shall archive all forecasted traffic states for use in post-incident/event analysis. Verify Decision Support shall archive the results of all forecast comparisons to field data for future analyses. Rules Engine Capabilities Rule Application The rules engine shall have state-of-the-art rules engine capabilities. H Decision Support Verify the rules engine selected has all the mentioned capabilities: Decision Support, rules, evaluation. Performance shall not degrade linearly with increases in the number of rules.
plan implementation and de-escalation. The post-incident/event analysis report shall include an analysis of the accuracy of the traffic forecast at the base of the response recommendation (“no action” or “response plan recommendation”). The post-incident analysis report shall reference any additional events that occurred during the same impact period anywhere on the corridor. Interface to Caltrans’ ATMS UI-9.1 The ICM Environment shall include UI functionality within the Caltrans ATMS for use by Caltrans’ operators. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. The ICM Environment shall provide ATMS operators with an ATMS interface providing the ability to create, edit, and review incident /event information. The ICM Environment shall provide ATMS operators with an ATMS interface providing the ability to review response plans. The ICM Environment shall provide ATMS operators with an ATMS interface providing the ability to reject or approve response plans. Interagency Communication UI-9.1 The ICM Environment shall facilitate communication between staff from different agencies. M Corridor Management Testing to be defined when the requirement is addressed.
Integrated Data Definition, Capture, and Processing SI-4.1 The ICM Core System shall have an integrated point of access with consistent data definitions and formatting for internal system data access and data processing. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. All data collected by the ICM Core System shall be available through the common ICM data access interfaces. All data collected by the ICM Core System shall be managed through the common ICM user interfaces. All data collected by the ICM Core System shall be defined and used in a common manner and format cross all ICM system components. SI-4.2 All data collected by the ICM Core System shall be managed within the appropriate security context. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. SI-4.3 All ICM data shall be processed in a consistent manner, using design techniques that ensure that each data element is consistently defined, processed, and calculated to ensure the integrity and accuracy of the data element. H Data Hub Not part of system testing. Will be evaluated during post implementation review. SI-4.4 The ICM Environment corridor data processing and access shall be capable of continuous operations in the event of any individual system component failure. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Ownership of software, hardware, data, and algorithms SI-5.1 The ICM Environment shall maintain ownership of each data element and data record. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. SI-5.2 The ICM Environment shall maintain ownership of rules. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. SI-5.3 The ICM Environment shall H Institutional Not part of system testing.
All corridor assets providing automated data feeds to Decision Support shall be maintained in accordance with the manufacturers’ specifications for the assets. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. ICM Environment operators shall develop and maintain a list of critical elements that should receive maintenance priority should they fail. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The ICM Environment shall log all received alerts and notifications regarding systems operations. H Corridor Management Verify logs of all received alerts and notification/errors. The ICM Environment shall log all maintenance-related activities conducted on devices connected to the system. L Corridor Management Not part of system testing. Will be evaluated during post implementation review. Software Maintenance and Updates The ICM Environment software shall receive regular updates. H Corridor DSS/Data Hub Not part of system testing. Will be evaluated during post implementation review. The Corridor Technical Manager shall produce an annual report of system software maintenance, providing a year in review of the previous year, and a plan for the coming year of software maintenance and bug fix activities, schedule, and budget. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The ICM Environment shall maintain a managed repository of software configuration changes and activities. H Corridor Management Not part of system testing. Will be evaluated during post implementation review. System Upgrades The ICM Environment shall have a 5-year system upgrade plan. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The ICM Environment shall have an annual upgrade plan that identifies the system upgrades from the 5-year plan that will be implemented H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.