i-210 verification plan v1.0 final · i-210 pilot: verification plan iii primary authors jeny...

i

PARTNERS FOR ADVANCED TRANSPORTATION TECHNOLOGY INSTITUTE OF TRANSPORTATION STUDIES UNIVERSITY OF CALIFORNIA, BERKELEY

Connected Corridors: I-210 Pilot Verification Plan February 12, 2018 v1.0

Partners for Advanced Transportation Technology works with researchers, practitioners, and industry to implement transportation research and innovation, including products and services that improve the efficiency, safety, and security of the transportation system.

I-210Pilot:VerificationPlan

ii

Thispageleftblank

intentionally


iii

PrimaryAuthors

JenyGovindanQualityEngineerCaliforniaPATHUniversityofCalifornia,BerkeleyBrianPetersonDevelopmentManagerCaliforniaPATHUniversityofCalifornia,Berkeley

EditorialReview

MichelleHarringtonEditorCaliforniaPATHUniversityofCalifornia,Berkeley

REVISIONHISTORYVersion Author Reviewer1.0 JenyGovindan BrianPeterson


iv

Thispageleftblank

intentionally


v

TABLEOFCONTENTS

1. Introduction.................................................................................................................... 1

2. PurposeofDocument ..................................................................................................... 3

3. Scope.............................................................................................................................. 5 3.1 Scopeofthisdocument ..............................................................................................................5 3.2 Systemrequirementsscope........................................................................................................5

3.2.1 InScope ......................................................................................................................................... 6 3.2.2 OutofScope .................................................................................................................................. 6

4. Rolesandresponsibilities................................................................................................ 7

5. SystemHighlevelDescription ......................................................................................... 9

6. TechnologyStack .......................................................................................................... 13

7. PrimaryUseCase .......................................................................................................... 15

8. TestingDescriptionandCoverage ................................................................................. 19 8.1 TestSetup .................................................................................................................................19 8.2 Teststrategyandcoverage .......................................................................................................20

8.2.1 TestingStrategy,ScopeandApproach ........................................................................................ 20 8.2.1.1 Code/TestCoverage .................................................................................................................. 21 8.2.1.2 TestAutomationandAutomationCriteria ................................................................................ 21

8.2.1.2.1 ManualTesting ..................................................................................................................................... 21 8.2.1.2.2 AutomationTesting .............................................................................................................................. 21

8.2.1.3 TestingScope............................................................................................................................. 22 8.2.1.3.1 TypesofTesting .................................................................................................................................... 22 8.2.1.3.2 UnitTesting........................................................................................................................................... 23 8.2.1.3.3 FunctionalTesting................................................................................................................................. 23

8.2.1.3.3.1 DataHubDataPipelines................................................................................................................. 24 8.2.1.3.3.2 DSS(trafficestimation)................................................................................................................... 24 8.2.1.3.3.3 DSS(trafficprediction) ................................................................................................................... 24 8.2.1.3.3.4 DSS(responseplangeneration) ..................................................................................................... 24 8.2.1.3.3.5 DataHubOrchestrationandWorkflow.......................................................................................... 24

8.2.1.3.4 APITesting ............................................................................................................................................ 25 8.2.1.3.5 Integrationtesting ................................................................................................................................ 25 8.2.1.3.6 Securitytesting ..................................................................................................................................... 26 8.2.1.3.7 Performancetesting ............................................................................................................................. 26 8.2.1.3.8 Stabilitytesting ..................................................................................................................................... 27 8.2.1.3.9 Acceptancetest .................................................................................................................................... 27 8.2.1.3.10 Regressiontesting................................................................................................................................. 27

8.2.2 EntryandExitCriteria.................................................................................................................. 28 8.2.2.1 MinimumEntryandExitCriteria ............................................................................................... 28 8.2.2.2 TestExecution ........................................................................................................................... 28 8.2.2.3 ValidationandDefectManagement.......................................................................................... 29 8.2.2.4 TestMetrics ............................................................................................................................... 29 8.2.2.5 DefectTracking&Reporting...................................................................................................... 29

8.2.2.5.1 Openingadefect:.................................................................................................................................. 30 8.3 VerificationMatrix ....................................................................................................................30

8.3.1 TestMatrixforI-210pilotproject ............................................................................................... 31


vi

8.3.1.1 InstitutionalRequirements ........................................................................................................ 31 8.3.1.1.1 CorridorStrategicPlanning ................................................................................................................... 31 8.3.1.1.2 AssetExistence ..................................................................................................................................... 32 8.3.1.1.3 CorridorChampions.............................................................................................................................. 32 8.3.1.1.4 OrganizationalCompositionandStructure........................................................................................... 33 8.3.1.1.5 ManagementStructureandProcesses ................................................................................................. 33 8.3.1.1.6 InteragencyTrustandCommunication................................................................................................. 34 8.3.1.1.7 InteragencyAgreements....................................................................................................................... 34 8.3.1.1.8 FundingforICMSystem........................................................................................................................ 35 8.3.1.1.9 Trainingandeducation ......................................................................................................................... 35 8.3.1.1.10 PublicOutreachandCommunications.................................................................................................. 35 8.3.1.1.11 ManagementofThird-PartyRelationships ........................................................................................... 36

8.3.1.2 CorridorMonitoring .................................................................................................................. 36 8.3.1.2.1 StaticTransportationNetworkCharacteristics ..................................................................................... 36 8.3.1.2.2 AssetInventoryandHealthManagement ............................................................................................ 37 8.3.1.2.3 ControlAssetStateMonitoring ............................................................................................................ 39 8.3.1.2.4 TrafficMonitoring ................................................................................................................................. 40 8.3.1.2.5 TransitMonitoring ................................................................................................................................ 41 8.3.1.2.6 Park-and-RideMonitoring .................................................................................................................... 41 8.3.1.2.7 CorridorPerformanceMetrics .............................................................................................................. 41 8.3.1.2.8 TrafficStateDetermination .................................................................................................................. 46 8.3.1.2.9 HistoricalPatternDetermination.......................................................................................................... 50

8.3.1.3 StrategicIncident/EventResponsePlanning(CorridorPlanning).............................................. 53 8.3.1.3.1 StakeholderInvolvement...................................................................................................................... 53 8.3.1.3.2 ManagementofResponsePlanComponents....................................................................................... 53 8.3.1.3.3 IncidentResponseTestingCapabilities................................................................................................. 54 8.3.1.3.4 RuleCreationandManagement........................................................................................................... 55

8.3.1.3.4.1 DecisionSupportRules................................................................................................................... 55 8.3.1.3.5 RulesTestingandEvaluation ................................................................................................................ 57 8.3.1.3.6 RuleDocumentingandArchiving.......................................................................................................... 58 8.3.1.3.7 Post-Incident/EventAnalyses ............................................................................................................... 58 8.3.1.3.8 QuarterlyOperationalReviews............................................................................................................. 58

8.3.1.4 Real-TimeIncident/EventMonitoring ....................................................................................... 58 8.3.1.4.1 Incident/EventIdentification ................................................................................................................ 58 8.3.1.4.2 Incident/EventVerification................................................................................................................... 62 8.3.1.4.3 Incident/EventCharacterization ........................................................................................................... 62 8.3.1.4.4 Incident/EventInformationDissemination .......................................................................................... 64 8.3.1.4.5 Incident/EventTermination.................................................................................................................. 66 8.3.1.4.6 Incident/EventArchiving....................................................................................................................... 67

8.3.1.5 DeterminationofReferenceDataforResponseplanning......................................................... 68 8.3.1.5.1 Incident/EventImpactAssessment ...................................................................................................... 68 8.3.1.5.2 ResponsePlanGeneration.................................................................................................................... 69 8.3.1.5.3 IdentificationofAvailableFieldElements............................................................................................. 70 8.3.1.5.4 IdentificationofSuitableDetours ......................................................................................................... 72 8.3.1.5.5 IdentificationofSuitableControlActions(ResponsePlanDevelopment)............................................ 75 8.3.1.5.6 EvaluationofIndividualResponsePlans............................................................................................... 77 8.3.1.5.7 SelectionofRecommendedResponsePlan.......................................................................................... 82 8.3.1.5.8 ResponsePlanReviewandApproval .................................................................................................... 85 8.3.1.5.9 PeriodicResponsePlanUpdates........................................................................................................... 86 8.3.1.5.10 ResponseTermination .......................................................................................................................... 87 8.3.1.5.11 ResponsePlanningArchiving ................................................................................................................ 91 8.3.1.5.12 ResponsePlanningPerformanceAssessment ...................................................................................... 91

8.3.1.6 ResponsePlanImplementation................................................................................................. 91 8.3.1.6.1 ResponsePlanFieldImplementation ................................................................................................... 91 8.3.1.6.2 InformationDisseminationtoTravelers ............................................................................................... 98 8.3.1.6.3 ImplementationOverride ................................................................................................................... 101 8.3.1.6.4 ResponsePlanImplementationTracking............................................................................................ 102 8.3.1.6.5 ResponsePlanningArchiving .............................................................................................................. 103


vii

8.3.1.7 DataManagement................................................................................................................... 103 8.3.1.7.1 DataQuality ........................................................................................................................................ 103 8.3.1.7.2 DataManagementNeeds ................................................................................................................... 104

8.3.1.7.2.1 GeographicandInstitutionalData ............................................................................................... 104 8.3.1.7.2.2 AssetInventory............................................................................................................................. 104 8.3.1.7.2.3 AssetCapabilities(BackgroundOperationalData)....................................................................... 110 8.3.1.7.2.4 AssetStateData ........................................................................................................................... 111 8.3.1.7.2.5 AssetReal-TimeData.................................................................................................................... 114 8.3.1.7.2.6 ResponsePlanData ...................................................................................................................... 117 8.3.1.7.2.7 DataArchiving .............................................................................................................................. 123 8.3.1.7.2.8 MaintenanceLogs ........................................................................................................................ 124 8.3.1.7.2.9 AdministrativeLogs ...................................................................................................................... 124

8.3.1.7.3 DataCommunicationInterface........................................................................................................... 125 8.3.1.7.3.1 IncomingDataCommunicationChannel...................................................................................... 125 8.3.1.7.3.2 OutgoingDataCommunicationChannels .................................................................................... 128

8.3.1.7.4 DataFormats ...................................................................................................................................... 130 8.3.1.7.5 DataVerificationandValidation......................................................................................................... 130 8.3.1.7.6 DataStorageandWarehousing .......................................................................................................... 136 8.3.1.7.7 DataDocumentationandMaintenance ............................................................................................. 136

8.3.1.8 DecisionSupport...................................................................................................................... 138 8.3.1.8.1 CorridorRoadandAssetInformationAccess ..................................................................................... 138 8.3.1.8.2 CorridorTrafficStateEstimation ........................................................................................................ 140 8.3.1.8.3 CorridorTrafficStateForecasting ....................................................................................................... 143 8.3.1.8.4 RulesEngineCapabilities .................................................................................................................... 146

8.3.1.8.4.1 RuleApplication ........................................................................................................................... 146 8.3.1.8.4.2 Post-ResponseEvaluation ............................................................................................................ 148

8.3.1.9 CoreSystemUserInterfaces.................................................................................................... 148 8.3.1.9.1 UserInterfacesforManagingAssetInformation................................................................................ 148 8.3.1.9.2 UserInterfacesforManagingIncident/EventInformation................................................................. 154 8.3.1.9.3 UserInterfaceforManagingMockIncidents ..................................................................................... 155 8.3.1.9.4 UserInterfacesforManagingResponsePlans.................................................................................... 157

8.3.1.9.4.1 ResponsePlanViewing................................................................................................................. 157 8.3.1.9.4.2 ResponseRulesManagement ...................................................................................................... 158 8.3.1.9.4.3 ResponsePlanDevelopment........................................................................................................ 159 8.3.1.9.4.4 ResponsePlanSelection............................................................................................................... 160 8.3.1.9.4.5 ResponsePlanApproval ............................................................................................................... 160 8.3.1.9.4.6 ResponsePlanImplementation.................................................................................................... 162 8.3.1.9.4.7 UserInterfacesforManagingICMCoreSystemInformation ...................................................... 165 8.3.1.9.4.8 GeospatialVisualizationofData................................................................................................... 166 8.3.1.9.4.9 Reporting,Charting,andGraphingFunctions .............................................................................. 173

8.3.1.9.5 Post-Incident/EventAnalysisReport .................................................................................................. 177 8.3.1.9.6 InterfacetoCaltrans’ATMS ................................................................................................................ 179 8.3.1.9.7 InteragencyCommunication............................................................................................................... 179 8.3.1.9.8 IntegratedVisualizationandReporting .............................................................................................. 179 8.3.1.9.9 IntegratedControlFunctions.............................................................................................................. 180 8.3.1.9.10 IntegratedDataDefinition,Capture,andProcessing ......................................................................... 181 8.3.1.9.11 Ownershipofsoftware,hardware,data,andalgorithms................................................................... 182 8.3.1.9.12 SystemofRecord/LocationforData................................................................................................... 183

8.3.1.10 SystemManagement............................................................................................................... 183 8.3.1.10.1 SystemAccessandSecurity ................................................................................................................ 183 8.3.1.10.2 ICMSystemHealthMonitoring........................................................................................................... 186 8.3.1.10.3 SystemReliability ................................................................................................................................ 186 8.3.1.10.4 SystemMaintenance .......................................................................................................................... 187 8.3.1.10.5 SoftwareMaintenanceandUpdates .................................................................................................. 188 8.3.1.10.6 SystemUpgrades ................................................................................................................................ 188 8.3.1.10.7 SupportingDocumentationandTraining............................................................................................ 189

9. ReferenceDocuments..................................................................................................190


viii

10. DefinitionofTerms ......................................................................................................192

Thispageleftblank

intentionally


ix

LISTOFFIGURES

Figure1-1I-210PilotMap ............................................................................................................................................ 1

Figure5-1SystemHighLevelDesign ............................................................................................................................ 9

Figure7-1PrimaryUseCase ....................................................................................................................................... 15

Figure8-1SystemPrimaryTestHooks........................................................................................................................ 20

Figure8-2TestCaseLifeCycle .................................................................................................................................... 22

Figure8-3DefectTrackingProcess ............................................................................................................................. 30


x

LISTOFTABLES

Table4-1RolesandResponsibilitiesforQA/QC ........................................................................................................... 7

Table7-1PrimaryUseCaseDescription ..................................................................................................................... 17

Table8-1HighLevelTestScenario ............................................................................................................................. 26

Table8-2DefectCategories........................................................................................................................................ 29

Table8-3TestMatrix .................................................................................................................................................. 31

1

1. Introduction

The“I-210IntegratedCorridorManagement(ICM)SystemPilot”project,isbeingconductedaspartoftheConnectedCorridorsprogramadministeredbytheCaliforniaDepartmentofTransportation(Caltrans)andthePartnersforAdvancedTransportationTechnology(PATH)attheUniversityofCalifornia,Berkeley.ThisdocumentprovidesaverificationguidelinefortheI-210Pilotprojectsystemsdevelopment.

Figure1-1I-210PilotMap


2

Thispageleftblank

intentionally


3

2. PurposeofDocument

TheverificationplanspecifiesthemethodsofverificationtobeusedfortestingtheICMsystemoperations.Thisincludingteststrategies,definitionsofwhatwillbetested,thelevelstowhichdifferentsystemelementswillbetested,andatestmatrixwithdetailedmappingconnectingthetestingperformedtothesystemrequirements.ThisverificationplanensuresthatallrequirementsspecifiedintheSystemRequirementsdocumenthavebeenmetandreviewed.Theteststrategiespresentedensurethatthetestingdefinedforeachsystemcomponentandtheintegrationofthesecomponentsshallmeetthesystemrequirements.


4

Thispageleftblank

intentionally


5

3. Scope

3.1 Scopeofthisdocument

Thisistheverificationplanforthereleaseofthe“I-210Pilot.”Thisdocumentdefinesthescope,approach,resources,schedule,andrisks/mitigationsfortestingthisproject.ThetestcasesasoutlinedinSection8havebeenreviewedandapprovedtoensurecompletenessofthetesting,aswellasdeterminethetestingschedule.Thetestcasescanbemanagedusingthisdocumentorwithinatestcasemanagementsystem.Detailedtestcasesarenotincludedinthisdocument,butwillbemaintainedwithinatestcasemanagementsystem.Anymajorchangestotestingwillbedocumentedandapprovedthroughtheverificationplanandneworrevisedtestcasesshallalsobereviewedandapproved.

3.2 Systemrequirementsscope

ThepurposeoftheI-210PilotistoreducecongestionandimproveoverallcorridorperformancealongasectionofI-210corridorinLosAngelesCounty.TheimprovementswillbeachievedbydevelopinganddeployingtheICMsystem.AttheheartoftheproposedsystemwillbeaDecisionSupportSystem(DSS)designedtohelpcorridorsystemoperatorsmanageincidents,unscheduledevents,andplannedeventsmoreeffectively.Thissystemwilluseinformationgatheredfrommonitoringsystemsandprovidedbypredictiveanalyticaltoolstoestimatecurrentandnear-futureoperationalperformance.Theinformationwillbeusedtodeveloprecommendedcoursesofactiontoaddressproblemscausedbyidentifiedincidentsandevents.Morespecifically,thissystemisexpectedto:

• Improvereal-timemonitoringoftravelconditionswithinthecorridor• Enableoperatorstobettercharacterizetravelpatternswithinthecorridorandacross

systems• Providepredictivetrafficandsystemperformancecapabilities• Beabletoevaluatealternativesystemmanagementstrategiesandrecommenddesired

coursesofactioninresponsetoplannedevents,unscheduledevents,andincidents• Improvedecision-makingbytransportationsystemmanagers• Improvecollaborationamongagenciesoperatingtransportationsystemsinthecorridor• Improvetheutilizationofexistinginfrastructuresandsystems• Moreefficientlyusesparecapacitytoaddressnon-recurringcongestion• Reducedelaysandtraveltimesalongfreewaysandarterials• Improvetraveltimereliability• Helpreducethenumberofaccidentsoccurringalongthecorridor• Reducetheperiodduringwhichthecongestionresultingfromanincidentorevent

affectscorridoroperations


6

• Reducegreenhousegasemissions• Generatehighertravelersatisfactionrates• IncreasetheoveralllivabilityofcommunitiesinandaroundtheI-210corridor

Referto“I-210Pilot-High-LevelDesign“and“I-210Pilot-SystemRequirements”documentsforfurtherdetails.

3.2.1 InScope

Ingeneral,thescopeoftherequirementsistoimprovecorridor-widetrafficconditionsparticularlyduringanincident,unscheduledevent,orplannedevent.Thismeanstherequirementsarefocusedon:

• Providingbetterinformationtotransportationoperatorsandtravelersregardingincidentsandevents—Thisincludesthecreationanddeploymentof“incidentresponseplans.”Itisnotfocusedonmanagingtheincidentoreventitself,however,betterdatacouldpotentiallyenableafasterresponseandreducetheimpactanincidentoreventhasoncorridorconditions.

• Operationsatthecorridorlevel—Ratherthanfocusingonfreewaysalone,therequirementsdefineasystemthatusesfreeways,arterials,andalternativemodesoftravelinacoordinatedwaytoassistwithtraffic/travelermanagementaroundanincidentorevent.

• ImprovingcommunicationsanddataflowbetweenthetransportationoperatorswithintheI-210corridor.

3.2.2 OutofScope

Therequirementsarenotfocusedon:• Managingnormaldailytraffic—Thesystemshallnotbeusedtoimprovenormalday-to-

daytrafficonanongoingbasis.• Managingthesceneofanincident/event—Whilethesystemwilldiverttravelersaround

anincidentorevent,itisnotintendedtomanagewhathappensattheincident/eventitself.Thatremainsunderthecontrolofemergencyresponders.Forexample,theproposedsystem:

o Doesnotexpectfirstresponderstochangetheirprocessesorprioritiesattheincidentsceneoreventlocation.ItwillrequestcommunicationfromfirstrespondersaspartoftheICMprocess,butitwillnotalterresponders’internalmethodsalreadyinplaceforincident/eventmanagement.

o Doesnotsuggestroadorlaneclosures.Safetyofficersonthescenewilldeterminewhichlanestocloseandforhowlong.TheICMsystemonlyrequiresinputonwhichlanesareclosed,howlongtheclosureswilllast,andwhenthelanesareexpectedtobereopened.

o Doesnotsuggestorenableroutesforfirstresponderstoreachanincidentoreventlocation.


7

4. RolesandresponsibilitiesInthecontextoftheI-210Pilot,implementationoftheQualityManagementPlanwillrestprimarilywiththeQALead.SignificantoversightdutieswillalsobeassignedtotheCaltransProjectManagerandPATHProjectManager.Table4-1liststheRolesandResponsibilitiesrelatedforQA/QC.Thistablehasbeencopiedinitsentiretyfromthe“I-210Pilot-ProjectManagementPlan”-Table10-1.ProjectEntity ResponsibilitiesQA/QCLead • ResponsiblefortheimplementationandmonitoringoftheQualityManagementPlan

• DevelopanddirectQualityControlandQualityAssurancereviews • MonitorsselectedperformancemetricsrelativetoQualityAssuranceandQualityControl • Trackstheresolutionofidentifiedqualityissues • DevelopandsubmitQualityAssuranceStatusandImprovementReportstothePATH

ProjectManagerandCaltransProjectManager • Whenrequired,submitChangeRequeststotheChangeControlBoardaccordingtothe

processoutlineintheChangeManagementPlanandtracktheresultsofthereviewtobeconductedbytheChangeControlBoard

• InformprojectteammembersofanycorrectiveactionstobeimplementedbecauseoftheQualityControlandQualityAssurancereviews

PATHProjectManager

• ReviewresultsofqualityauditsperformedbytheQA/QCLead • ReviewtheQualityAssuranceStatusandImprovementReportssubmittedbytheQA/QC

Lead • Whennecessary,escalateQualityControlandQualityAssuranceissuestotheProject

ManagementTeam,TechnicalAdvisoryCommittee,orOversightManagementCommittee CaltransProjectManager

• ReviewresultsofqualityauditsperformedbytheQA/QCLead • ReviewtheQualityAssuranceStatusandImprovementReportssubmittedbytheQA/QC

Lead • Whennecessary,escalateQualityControlandQualityAssuranceissuestotheProject

ManagementTeam,TechnicalAdvisoryCommittee,orManagementOversightCommittee Table4-1RolesandResponsibilitiesforQA/QC


8

Thispageleftblank

intentionally


9

5. SystemHighlevelDescription

Figure5-1SystemHighLevelDesign

Figure5-1providesanillustrationoftheI-210systemdesign.Thesystemisdividedintothreemajorsubsystems–thedatahub,decisionsupportsystem(DSS),andtheCorridorManagementSystem(CMS).Thedatahubisillustratedinthediagraminred,theDSSinblue,andtheCMSinpurple.Dataflowisgenerallylefttorightinthediagram.

Datafromfielddevices(e.g.intersectionsignals,sensing,rampmeters,anddynamicmessagesigns)areprovidedtothesystembytrafficmanagementcenters(TMCs)(illustratedingreen).TheTMCsaremanagedbythelocalagenciesandCaltrans.TheleftsideofthediagramillustrateseachoftheTMCsprovidingdatafromtheirfielddevices.ItisacriticaldesignconstraintthattheICMsystemneverdirectlycommunicatewithorprovidecommandstoafielddevice.

Thedatahubhasfiveprimaryresponsibilities:receivedatafromeachTMC,verifydataqualityandprocessthedatafortheCMSandDSS,provideacommunicationsbusformanagingdatabetweentheDSS,CMS,anddatahub,providedatastorage(includingmovingdatatoPeMSforarchivalstorageandanalytics),andsecurethedata.ItdoesreceivedatabyfirstcommunicatingwitheachTMCsourceandcollectingdatafromthatsourceviaareader.Readersarespecificto


10

theirsourceandarethebeginningofthedatapipeline.Thepipelinesareusedtomoveandprocessdatathroughoutthesystem.

Fromeachreader,thedataistransferredeithertoamessagingsystemforstreamingdataorMongo.Mongowillbeusedforlargerdatasetsthatareupdatedlessfrequently.Nextthedataisprocessedusingadedicatedprocessorforeachtypeofdata,eitherajavaprocessorwithinApacheSpark(streamingcases).Processorstransformthedatatoastandardformat,performqualitychecks,processthedata,andinsomecases,providemachinelearningservicessuchaspredictionsforthedatareceived.Dataisthenpasseddownstreamineachpipelineonthemessagingsystem.

Dataispersistedusingpersistenceworkersthatlistentotheprocesseddatamessagingtopics,andthenstorethedataineitherCassandraorMongo.Persistenceworkersalsoprovideretrievalservicesforeachdatastore.

Processeddataisalsopassedtothedatahubdatagateway.ThedatagatewayprovidesanexternalinterfacefromthedatahubtotheCorridorManagementSystemandtheDecisionSupportSystem.ThedatahubdatagatewayprovidesroutingofinformationtoboththeDSSandtheCMS,andprovidesamethodofroutinginformationbetweentheDSSandCMSaswell,whileguaranteeingthestandardizationofinterfacesandcapturingofanycommunicationbetweentheDSSandCMS.

Thedatahubcontrolgatewayisadatahubcomponentthatprovidesorchestrationandworkflowmanagementofcontrolandstatusmessagesforthedatahub,aswellastheDSSandCMS.ItusesNetflixConductortoprovideworkflowmanagementandorchestrationservicestotheentiresystem.

TheDSSinterface’sprimaryrolesaretoprovideanestimateofcurrenttrafficstatefordisplaytotheoperator(intheCMSinterface)andprovideresponseplansandresponseplanevaluationservices.TheDSShasthreemaincomponents:responseplanmanagement,therulesengine,andmodeling.Theresponseplanmanagementcomponentreceivesincidentinformationandcoordinatesthedevelopmentandevaluationofresponseplans.Therulesengineprovideslogicandrulesto:decidewhenresponseplansshouldbegenerated,developresponseplansforevaluation,andevaluateandrankresponseplans.Themodelingcomponentprovidestrafficestimationandpredictioncapabilitiestosupportresponseplancreation,evaluation,andranking.CommunicationsbetweentheresponseplanmanagementandmodelingareenabledviaRESTandActiveMQmessaging.

TheCMSsystemprovidesaninterfacefortheICMoperator,isthesourceofincidentinformation,allowstheoperatorandstakeholderstoviewandapproveorrejectresponseplans,anduponresponseplanapproval,executesthecommandsrequiredtosendthe


11

approvedresponseplantotheTMCstoimplement.ThegreenboxesontherightsideofFigure5-1arethesameTMCsillustratedontheleftsideofthefigure,butthedataflowsdisplayedontheright,representthecommandssenttotheTMCstoimplementtheresponseplanselected.


12

Thispageleftblank

intentionally


13

6. TechnologyStackThetechnologystackincludesthefollowing:

• TheprimarycomponentsarebuiltusingJava7or8withtheSpringframework.HibernateisusedwithcomponentsrequiringPostgresaccess.

• PersistenceisbuiltwithJavabasedpersistenceworkers(bothforstoreandretrieveoperations)andPostgres,Mongo,orCassandraforpersistence.

• MessagingviaActiveMQandKafka

• ApacheTomcat

• LogManagementviaGraylog

• ApacheSpark

• ApacheCamel

• AmazonWebServices,includingthefollowingAWSservices:

o EC2

o RDS(Postgres)

o S3

o VPC

o IAM

o EMR

o Otherservicesforcoderepository,build,anddeploymentservices

• Platform/ApplicationServers/OS

o MostanyversionofLinuxOSisacceptable,Ubuntu14.04isthecurrentstandard

o Tomcatv8.5.1


14

Thispageleftblank

intentionally


15

7. PrimaryUseCase

Figure7-1PrimaryUseCase


16

Figure7-1providesanillustrationofthesystem’sprimaryusecase.Thisusecasecanbedescribedasfollows:

Name: FreewayIncident

Description: FreewayincidentoccursandisinitiatedatCaltransTMCusingATMS

Actors:

CaltransOperator/CTOperator

CaltransATMS

CorridorManagementSystem

DataHub

DecisionSupportSystem

BasicFlow

Actor Action

1 Freeway IncidentoccursandisreportedtoTMC

2 CTOperator Inputsincidentinformation,confirmsincident

3 CaltransATMS IncidentpassedtoCorridorManagementSystem

4 CMS CMSregistersconfirmedevent,passestoDataHub,informsusers

5 DataHub Datahubbeginsincidentworkflow,requestsresponseplanfromDSS

6 DSS Responseplandevelopmentrequests“donothing”predictionfrommodeling

7 DSS Donothingpredictioncompletedusingcurrentestimatedtrafficstate–resultsprovidedtoresponseplandevelopment

8 DSS Responseplandevelopmentusesthe“donothing”predictionandtherulesenginetodetermineifaresponseplanshouldbedeveloped

9 DSS (Assumingresponseplanisrequired)Theresponseplandevelopmentcomponentusestherulesengine,resultsofthe“do-nothing”prediction,currentcorridorstate,andasetoffixedresponseplancomponentstodevelopalimitednumberofresponseplansforevaluation.Itsubmitsthoseresponseplanstothepredictionengine.

10 DSS Thepredictionenginerunsapredictionforeachresponseplan,alongwithanother“donothing“prediction”basedoncurrentcorridorconditions.Itprovidestheresultsofthosepredictionstotheresponseplandevelopmentcomponent.

11 DSS Theresponseplandevelopmentcomponentusestheresultsofeachprediction,currentcorridorstate,andtherulesenginetoevaluate,rank,andselectarecommendedresponseplan.ItprovidestherecommendedresponseandtheotherresponseplansandtheirresultstotheDataHub.

12 DataHub TheDataHubstoresallresultsoftheresponseplanrequestreceivedfromtheDSSandforwardstherecommendedresponseplananditsresultstotheCMS.

13 CMS TheCMSprovidestheresultstotheATMS.

14 CMS TheCMSprovidestheresultstolocalagencies,whoapproveorrejectthe


17

responseplan.

15 ATMS TheATMSprovidestheresultstotheoperator.

16 Operator TheCaltransOperatorreviewsandapprovestheresponseplan.

17 ATMS TheATMSsendstheapprovalresultstotheCMS.

18 CMS TheCMSverifiesthatallrequiredjurisdictionshaveapprovedtheplan.

19 CMS TheCMSsendsthefullresultsofapprovaltotheATMSandtheDataHub.

20 CMS (Assumingalljurisdictionshaveapprovedtheplan)TheCMSsendstheexecutioncommandsrequiredtoimplementtheresponseplantoeachaffectedTMC.

21 TMCs TheTMCsexecutethecommandsrequiredtoimplementtheresponseplan.

22 TMCs TheTMCsreportassetstatuschangesastheassetsimplementtheresponseplancommands.

AlternativeFlow1

9A DSS Noresponseplanisrequired.DSSinformsDataHubworkflowthatnoresponseplanisrequiredorwillbedeveloped.

10A DataHub DataHubinformsCMSthatnoresponseplanisrequired.

11A CMS CMSinformsATMSthatnoresponseplanisrequired.Closesincidentandinformsusers.

AlternativeFlow2

20B CMS TheCMSdisplaysdisapprovaloftheplan.

21B DataHub TheDataHubendsresponseplanworkflow.

Table7-1PrimaryUseCaseDescription

Uponcompletionofthisprimaryworkflow,furtherprocessesinvolvedinresponseplanlifecyclemanagementwilloccur,suchasresponseplanevaluation,responseplangenerationtoadjusttocurrentconditions,responseplancancellation,andresponseplancloseout.

Othermajorusecasesforwhichtestingwillbedefinedincludethefollowing:

• PlannedEvent

• UnplannedEvent

• SecondIncidentorEventinOverlappingZonesofInfluence

• SecondIncidentorEventinNon-OverlappingZonesofInfluence

• CancelorEndResponsePlanImplementation

• Operationduringperiodofnoincidentsorevents

• ArchivetoPeMS

• ArchivetoGlacier

• OperationalReporting

• DataPipelineFailure


18

• DataPipelineResumeOperations

• EventorIncidentrequiringresponseplanwherenoresponseplanisavailable

• DSSonlyresponseplandevelopment


19

8. TestingDescriptionandCoverageThissectiondescribesthetestingandtestcoverageforthissystem,withadescriptionofthetestsetupandteststrategy,includingtypesoftesting.Ingeneral,thefollowingtypesoftestingwillbeincludedinsystemtesting,ineithermanualorautomatedtests:

• Unit• Functional• Performance• Integration• Security• Regression• API• Acceptance

Testingwillcoverprimarilythedatahubanddecisionsupportsystems.Testingofthecorridormanagementsystems(CMS)willbetheresponsibilityofeachCMSvendor.IntegrationtestingofeachCMSwillbepartofeachCMSintegrationeffortandevaluation.

8.1 TestSetup

Throughoutthedevelopmentprocess,aminimumoftwofullsystemenvironmentsaremaintained.Thedevelopmentenvironmentiswheredevelopmentoccursandunittestsarerun.Atestenvironmentisalsomaintainedidenticaltothedevelopmentenvironment(atthelastdevelopmentrelease)forthepurposeofsystemtestinginaccordancewiththisplan.Bothdevelopmentandtestenvironmentsshallbeversionsofthetargetproductionenvironment(uptothecurrentstateofdevelopment)sothatupondelivery,thesystemwillbetestedinanenvironmentidenticaltothetargetdevelopmentenvironment.

Thetestsetupwillincludesomeadditionstoallowfortestingincluding:

• Testautomationserver(s)

• Specifictestdatacomponentstoallowdatasourcesforloadingofspecificdatasetstodatahubdatapipelines,componentinterfaces,orsystemdatastores

• Testmonitoringcomponents


20

8.2 Teststrategyandcoverage

8.2.1 TestingStrategy,ScopeandApproach

Figure8-1SystemPrimaryTestHooks

Theteststrategyisdefinedbasedonthefollowingprinciplesandconstraints:

• Therearethreeindependentprimarysubsystemsthatoperatebasedondefinedcommunicationcontractsbetweenthesubsystemsandexternaldataprovidersandreceiversofcommands(TMCs).

• Eachprimarysubsystemshallbetestedindependentlyandasanintegratedsystem,primarilyattheprimarytesthooksdesignatedbythearrowsinFigure8-1.

• TherearethreeCorridorManagementSubsystems,eachprovidedbyaseparatevendorthatwilloperateinterchangeablywiththeothertwosubsystems.Testingforeachofthesesubsystemsistheresponsibilityofeachvendor.

• IntegrationtestingoftheDSSandDataHubaretheresponsibilityofPATH.IntegrationtestingoftheCMSwillbepartoftheevaluationofeachvendor’ssystemandisnotdescribedinthisplan.

• TestingoftheDataHubinterfacesprovidedfortheCMSisdescribedwithinthisplan.

• Therearelimitedresourcesavailablefordevelopmentandtestingofthesystem.Thisisacriticalconstraintthatmustbeconsideredindevelopmentoftesting.

• TheDataHubwillbetestedprimarilyusingtheexternalinterfacesprovidedbytheDataHub.


21

• TheDSSwillbetestedprimarilyusingtheexternalinterfacesprovidedbytheDSS.

• IntegrationtestingoftheDataHubandDSSwillbeaccomplishedusingamockupoftheCMS.

• Automatedtestingwillbethepreferredtestingmethod.

• IntegrationtestingwillbeacontinuousprocessaseachofthethreeCMSvendorsaretransitionedinandoutoftheproductionenvironment.

• Therewillbeasinglededicatedtestenvironmentthatwillbeamirroroftheintendedproductionenvironment.Thiswillincludeconnectionstoeachdatasource.ThiswillnotincludetheabilitytosendcommandstocorridorassetsviatheTMCs.

8.2.1.1 Code/TestCoverage

Duetolimitedresourcesandhighcomplexityofthesystem,therewillbealimitationontestcoverageandtestautomation.Thiswillbeaddressedonacase-by-casebasisdependinguponthepriorityandcriticalityofeachimplementedrequirementtobetested.Thegoalistohavesufficientcoveragetoensurethesystemcanbedeployedwithsufficientfunctionalityandsafety.Limitedresourcesareariskidentifiedforthisproject.Toaddtothecomplexity,therearethreeCMSvendorswhichneedtobeintegratedwiththesystem.Therewillbealimitationonregressiontestingwitheachnewvendorintegrationwithnoguaranteesoffullinterchangeability,buteachvendor’sproductintegrationwillbeverifiedtoensurebasicfunctionality.

8.2.1.2 TestAutomationandAutomationCriteria

Testingwillincludebothmanualandautomatedtests.Ingeneral,thefollowingcriteriawillbeusedtodetermineifatestistobeautomated:

8.2.1.2.1 ManualTesting

Highprioritytestcasesthatcannotbeautomatedwillbetestedmanually.Lowerprioritytests,suchastestingloggingshouldbeexecutedmanually.Anytestthatcannotbeautomatedwillbeexecutedmanually.RESTAPI&SOAPrequestsshouldbetestedmanuallybeforetheycanbeautomated.Initially,connectionstoAMQ,Cassandra,Kafka,Postgresaretestedmanually.

8.2.1.2.2 AutomationTesting

Acceptancetestandhighprioritytestswillbeautomated,unlessmanualinterventionisrequired.JMeterscriptingshallbeusedtoautomatetestingwhenconnectingtoAMQorKafka;fordatabaseverificationqueriestoCassandra,Postgres,orMongo;and,forRESTorSOAPwebservicerequests.Automationwillbeusedtoprocesstheresultsobtainedandcomparedwithexpectedresults.


22

Testcasestobeautomatedaredesignatedasautomationtestcandidatesinthetestmatrix.Notallautomationtestcandidatesshallbeautomated,butallautomationtestcandidatesshall,ataminimum,betestedmanually.

8.2.1.3 TestingScope

8.2.1.3.1 TypesofTesting

Thetypesoftestingwillinclude:

• UnitTests• FunctionalTests• APITests• IntegrationTests• SecurityTests• PerformanceandStabilityTests• AcceptanceTests• RegressionTests

Figure8-2TestCaseLifeCycle

Ingeneral,testingofthesoftwareshallflowasfollows:

Regression


23

Developersunittestcodeastheydevelopindividualcodeelements.Unittestsarerunateachcodebuildanddeploy.Continuousintegrationensuresthatthisoccursautomaticallywheneveradeveloperchangescode.FunctionaltestsdefinedandrunbytheQAengineerforeachdiscretesystemfunctiondeliveredbythedevelopmentteamupondeliverytothetestenvironment.APITestsaredefinedandrunbytheQAengineerforeachAPIinterfacedeliveredbythedevelopmentteamupondeliverytothetestenvironment.Integrationtestsareteststhatensurefunctionalityacrosstheboundariesofthethreeprimarysubsystems,thisincludesfunctionsthatcrossinternalsystemboundariesorfunctionsthatcrossthesystemboundarytoexternalsystems.Functionsaregroupedintofeaturesfordeliveryintoaproductionenvironment.TheQAengineerdevelopsandrunsacceptancetestsforeachreleasedfeatureupondeliverytothetestenvironment.Regressiontestsarecollectionsoffunctional,acceptance,orotherteststhat,uponsuccessfuldelivery(passingofthefunctionaloracceptancetestinthetestenvironment),arerunwitheverysubsequentdeliverytothetestenvironment.TheQAengineerensuresthatregressiontestsaredefined,maintained,andrunoneverysubsequentdeliverytothetestenvironment.Othertestingwillproceedonanad-hocbasisdependinguponthespecificsofthetests.Theseincludesecurity,performance,stability,anddocumentationtests.Securitytestsareruninaccordancewithspecifictestcasesdevelopedaccordingtotheirowntestschedule.PerformanceandStabilitytestsareruninaccordancewithspecifictestcasesdesignedtoensuresufficientsystemperformancecriteriaandsystemstabilitycriteriaaccordingtotheirowntestschedule.

8.2.1.3.2 UnitTesting

AllcodedevelopedbyPATHwillbeunittested.UnittestcoveragewilldependuponcriticalityofeachcomponentandwillbedeterminedjointlybytheQAteamandthedevelopmentteam.

8.2.1.3.3 FunctionalTesting

Functionaltestingensuresthefunctionsofthesystemworkasexpectedandareapartoftheexitacceptancecriteriaforeverysystemormodule.Automatedfunctionaltestsareexecutedeverysprintasaregressiontesttoensurethatnochangesintroducedwithinasprintintroducesnewfailuremodeswithinthesystem.Thefollowingitemsareaveryhighlevelrepresentationofwhatfunctionaltestsareinplaceformodules/components.Thefunctional


24

testsareelaboratedduringeachsprintasthemodulesandsystemsarecompletedbythedevelopmentteam.

8.2.1.3.3.1 DataHubDataPipelinesEachdatapipelinewillbetestedtoverifythefollowing:

• Dataintegrity• Dataqualityandcalculatedqualityindicators• Dataprocessing• Pipelinefailurehandling• Datapersistence• Deliverytocorrectdatagatewayendpoint(s)• Pipelinecontrol

8.2.1.3.3.2 DSS(trafficestimation)

Trafficestimationwillbetestedforcorrectestimation(arterialandfreeway)andprocessstatusreportingatDSSinterfaces.Trafficestimationsproducedwillbereviewedbyresearcherstoverifyestimationsarewithintargetaccuraciesforeachcriticalestimationresult(density,speed,flow).Regressiontestsmayrequiresetconditions(specifiedPeMSdataset,scenario,andparameterset).

8.2.1.3.3.3 DSS(trafficprediction)Trafficpredictionwillbetestedforcorrectprediction(arterialandfreeway)andprocessstatusreportingatDSSinterfaces.Trafficpredictionsproducedwillbereviewedbyresearcherstoverifypredictionsarewithintargetpredictionparameters.Researcherswillalsoreviewinitialtrafficstateprovidedbyestimationtoensureacorrectreproductionofinitialtrafficstate.Regressiontestswillrequiresetconditions(specifieddatasets,scenario,andparameters).

8.2.1.3.3.4 DSS(responseplangeneration)ResponseplangenerationwillbetestedattheDSSinterface.Responseplangenerationwillbetestedunderasetoffixedinitialconditionsincludingsensingandtrafficassetdataandafixedsetofrules.Researcherswillreviewthecreatedresponseplanstoensurethecorrectresponseplansaregenerated.Followingtestingwithafixedsetofinitialconditionsandrules,theinitialconditionsandrulesshallbevariedandtheresultsreviewedagaintoensureproperoperation.

8.2.1.3.3.5 DataHubOrchestrationandWorkflow

EachworkflowdefinedwithintheDataHub’sConductorwithintheCommandGatewayshallbeverified,includingprimaryandsub-workflows.Eachpossibleworkflowoutcomeandeachworkflowbranchoperationshallbeverifiedundervaryingconditions.


25

8.2.1.3.4 APITesting

Refertothedesigndiagram“ICMDesign-Full_2.pdf”.APItestingforthedesigndiagramlistedwillbeconductedforthedatahubandDSSinterfaceboundaries.TestingoftheCMSinterfacesistheresponsibilityofeachCMSvendorandshallbeverifiedduringCMSevaluations.Eachendpointshallbetestedforthefollowing:

• Endpointfunctionality

• ValidationofAPIcorrectnesswithAPIdesign(format,configuration,frequency,protocol)

• Failoverandrecoverycapabilitywhenrequired

Ingeneral,APItestingwillbepartoffunctional,workflow,oracceptancetesting,giventhelargenumberofinterfacesandlimitedresources.SpecificandcomprehensiveAPItestingwillbelimitedbasedonriskassessment,issuesidentifiedduringothertesting,andworkloadpriorities.

8.2.1.3.5 Integrationtesting

Eachoftheprimarysystemcomponents(Datahub,DSS,CMS)willbetestedindividually.Endtoendtestingofthesecomponentsforthevarioussystemprocessesistheobjectiveofintegrationtesting.AstherearethreedifferentCMSvendorproductsbeingintegrated,oneatatime,theinitialintegrationtestingwillbelimitedtotheDataHubandDSS,withamockoftheCMSinterfaces.Thistestingwillprimarilybedrivenbytheprimaryusecaseofincidentmanagement.AseachCMSproductisintegrated,integrationtestswillbedefinedincooperationwiththeCMSvendorbasedontheinitialDataHubandDSSintegration,aswellassecondaryusecasetestingsimilartothehigh-leveltestscenariosdefinedbelow.

Estimation:

Freewayandarterialestimation

Prediction:

Freewayandarterialprediction

Incident:

Endtoendfromincidentgenerationtoresponseplandevelopment

Failurecases–lossofinstances/AWSservices/systemservices

CMSintegrationandrecoveryafterAWSrecovery

ATMSandCMSrecovery

Pipelines:

40pipelinesprioritization

CMSintegrationchecks: Threevendorsystemintegrationandregressiontest


26

execution

CaltransATMSintegration:

IncidentgenerationnotificationfromATMStothreevendorsystemintegrationsandregressiontestexecution.

Multi-incident:

Handlingofmultiplesimultaneousincidents

Dataverificationacrosssystemboundarieschecks:

Dataintegrityismaintainedforthedatasourcescomingintothedatahub,goingoutofthedatahub,comingintotheDSS.

Outofsequencedatachecks/validation/latedata:

Dataintegrityismaintainedforthedatasourcescomingintothedatahub,goingoutofthedatahub,comingintotheDSS.

Lossofsourceresiliency–verifycorrectnesswhencomesbackonline:

Componentsgoingdown,attemptsofrecover.Howvariouscomponentscrashingornotavailableishandled.

Table8-1HighLevelTestScenario

8.2.1.3.6 Securitytesting

Securitytestingwillincludeanumberofcomponents,withteststhatinclude:

• InitialreviewofsecuritybestpracticesimplementationconductedjointlywithCaltransITandPATH.

• ReviewofAWSTrustedAdvisorresultsconductedbyCaltransITandPATH.

• TestsforcorrecthandlingofmalformedSOAPmessagesatDatahubexternalinterfaces.

• ScanningDataHubexternalinterfacesusinganopensourcescanningtoolsuchasOWASPZedAttackProxy.

8.2.1.3.7 Performancetesting

Performancetestswillincludeteststoensurethesystemperformsatalevelsufficientfor120daysofoperationinaccordancewiththeup-timerequirementslistedwithinthesystemrequirements.Thistimeperiodischosentosimulatethedatavolumesexpectedtobestoredatanytimeinthedatahub.Testingwillsimulate120daysofoperation.Thisperformancetestingwillinclude:


27

• Datapipelineperformance

• Responseplangenerationperformance

• Incidentmanagementlifecycleperformance

• Multipleincidenthandlingperformance

• Loggingsystemperformance

EachoftheseperformancetestareasshalluseasetofmockCMSendpoints.CMSperformancewillbeevaluatedaspartofeachCMSvendorevaluation.

8.2.1.3.8 Stabilitytesting

TeststodeterminetherobustnessofthecomponentsinvolvedinICMshallbecompleted.Thesetestswillincludethefollowing:

• Stabilityinlossofdatasourcesandpipelinecomponents

• Stabilityinlossofabilitytoimplementresponseplansduetonon-respondingassets(limitedtoDataHubandDSStesting)

Testingwillalsoincludemonitoringandreportingofsystemstabilityduringtestingandevaluationperiods.

8.2.1.3.9 Acceptancetest

Acceptancetestingshallincludetestingofasubsetoftherequirementslistedwithintheverificationmatrix.Eachmajorsystemfeatureshallbetestedastheyaredeliveredbythedevelopmentteamtothetestenvironment.Thefullmatrixoftestsdevelopedduringthisprocessshallconstitutethesuiteofacceptancetestsforthesystem.Acceptancetestsforeachsprintwillbeexecutedatleasteveryweekforreportingpurposes.

8.2.1.3.10 Regressiontesting

Regressiontestingisthetestingofexistingsoftwarefunctionalitythathasbeenpreviouslycompletedandtestedtoensurethatachangeoradditiontothesoftwarehasn’tbrokentheexistingfunctionality.Suchtestscanbeperformedmanuallyonsmallprojects,butinmostcases,manualtestingistootime-consumingandcomplicated.Eachsprintwillhavethefunctionaltestsforthatsprintautomatedforpurposesofregressiontesting.Regressiontestingwillberunonanongoing,regularlyscheduledbasistoidentifyanyissuesasearlyinthedevelopmentcycleaspossible,withaminimumofatleastoncepersprint.


28

8.2.2 EntryandExitCriteria

• Theentrycriteriarefertothedesirableconditionsnecessarytostarttestexecution.

• Theexitcriteriaarethedesirableconditionsthatneedtobemetfollowingthecompletionoftestinginordertoproceedwiththeimplementation.

• Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteamwillconsultwiththedevelopmentteamandprogrammanagementandassesstherisk,identifymitigationactions,andprovidearecommendation.

8.2.2.1 MinimumEntryandExitCriteria

Theminimumentrycriteriatostarteachtestcycleincludethefollowing:

• Developtestplanandguidelinestocreatetestconditions,testcases,expectedresultsandexecutionscripts.

• Provideguidelinesonhowtomanagedefects.

• Developerscommunicatetothetestteamanychangesthatneedtobemadetothetestdeliverablesorapplicationandwhentheywillbecompleted.

Theminimumexitcriteriatoproceedtodeploymentfollowingeachtestcycleincludethefollowing:

• 100%oftestscriptsareexecuted

• NoopenCriticalormajorseveritydefects

• Allremainingvaliddefectsaredocumentedforcorrectionwithinafuturerelease

• Allexpectedandactualresultsarecapturedanddocumentedwithinthetestscripts

• Alltestmetricscollected

• AlldefectsloggedinJira

8.2.2.2 TestExecution

• Therewillbefunctionaltestingexecutedeverysprint.Eachcyclewillexecutealloftherequiredtestscripts.

• Theobjectiveofeachexecutionistoidentifyanyblocking,criticaldefects,andmostofthemajordefects.Itisexpectedtousesomework-aroundsinordertocompleteallofthetestscripts.

• Theobjectiveofthefinalsprintexecutionistoidentifyremainingmajorandminordefects,removeanywork-aroundsfromtheprevioussprints,correctgapsinthescriptsandobtainperformanceresults.

• Acceptancetestswillbecompletedeverysprintderivedfromthecompletedfunctionaltests.


29

8.2.2.3 ValidationandDefectManagement

• Itisexpectedthatthetestersexecuteallofthescriptsineachofthecyclesdescribedabove,aswellasdefiningandcompletingadditionaltestingiftheyidentifygapsinthetestscripts.Ifagapisidentified,thescriptsandtraceabilitymatrixwillbeupdatedandthenadefectloggedagainstthescripts.

• ThedefectswillbetrackedthroughJiraonly.Thetechnicalteamwillworkonfixes.

• Itistheresponsibilityofthetestertoopenthedefects,linkthemtothecorrespondingscript,assignaninitialseverityandstatus,retestandclosethedefect.

• Itistheresponsibilityofthetestertoreviewtheseverityofdefectsandfacilitatewiththedevelopmentteamthefixanditsimplementation,determinewhenthetestcancontinueorshouldbehalted,retest,andmodifythestatusasthedefectprogressesthroughthecycle.

• ItistheresponsibilityofthedevelopmentteamtoreviewJiraonadailybasis,askfordetailsifnecessary,fixthedefect,communicatetothetesterwhenthefixiscomplete,andimplementthesolution.

DefectsfoundduringtheTestingwillbecategorizedaccordingtothebug-reportingtool“Jira”andthecategoriesare:

Severity Impact

1(Blocker) • Crashesthesystem • Causestheapplicationtohang • Stopstestingeffort

2(Critical) • Itcausesalackofvitalprogramfunctionalitywithworkaround. 3(Major) • Thisbugwilldegradethequalityofthesystem.Thereisaworkaroundfor

achievingthedesiredfunctionality. • Thisbugpreventsotherareasoftheproductfrombeingtested.However

otherareascanbeindependentlytested. 4(Minor) • Thereisaninsufficientorunclearerrormessage,whichhasminimum

impactonproductuse. 5(Trivial)

• Cosmetic/enhancement

Table8-2DefectCategories

8.2.2.4 TestMetrics

Testmetricstomeasuretheprogressandlevelofsuccessoftestingwillbedevelopedandsharedwiththeprojectmanagerforapproval.

8.2.2.5 DefectTracking&Reporting

ThefollowingdiagramoutlinesthetypicalbugtrackingorJiraticketworkflowtobeusedbythetestandengineeringteam.


30

Figure8-3DefectTrackingProcess

8.2.2.5.1 Openingadefect:

ThefollowingguidelinesshouldbefollowedwhilecreatingadefectloginJira:

• IssueType:Bug• Summary:Briefsummaryabouttheissue

• Priority:Blocker,Critical,Major,Minor,Trivial

• Assignee:BrianPetersonorJenyGovindan.Assigneeinturnassignstoadeveloper.

• Label:Systemcomponent,function,ortestdescription

• Description:Precondition,stepstoreproduce,observedandexpectedbehaviordescription

• Attachments:Relatedsnapshotoftheissue,Graylogattachments

• Sprint:Blockersshouldbeassignedtothesamesprint

• Environment:SpecifyiftestedagainstDevorTestenvironment

8.3 Verif icationMatrix

Todefinesuitable,qualityobjectives,theissuesandneedsassociatedwitheachidentifiedgroupofcustomerswillbecatalogedandusedtocreatetheRequirementsTraceabilityMatrix“Table10-2–RequirementsTraceabilityMatrix”listedintheI-210Pilot-ProjectManagementPlan.docx.Thematrixcoupleseachsystemrequirementwithoneormoreuserneedsand,whereapplicable,oneormoretestcases.Oncecompleted,thismatrixwillbeusedtosupportqualitycomplianceactivitiesduringallphasesoftheproject’slifecycle.Thehigh-levelverificationmatrixbelowisbasedontheI-210Pilot-SystemRequirementsdocument.Acceptancetestingisasubsetofthisverificationmatrix.Testingislimitedtodatamanagement,decisionsupport,andcorridormanagementsubsystemmatrixelementsthatarelistedwithacriticalityofHigh.Asresourcespermit,mediumandlow

Open

In ProgressResolve

Start progress

Resolved

Resolve

Open

Resolved

Reopened

Start Progress

Resolve

Re-open Closed

Resolve & Close

Resolve & Close

Close

Resolve & Close


31

criticalitytestswillbedefinedwhentherequirementisaddressed.InstitutionalJobTasksarenotconsideredpartofthistesting.Teststhatarepartofthevendorsuppliedcorridormanagementsystemaregenerallytestedaspartofthevendorsystemevaluationasidentifiedinthefollowingsection.

Table8-3TestMatrixTestREQID

Description Criticality RelatedSubsystem

TestCases/Description TestMethod Notesorcomments

8.3.1 TestMatrixforI-210pilotproject

8.3.1.1 InstitutionalRequirements

8.3.1.1.1 CorridorStrategicPlanning

IN-1.1

TheCorridorManager,incoordinationwithstakeholders,shalltrackanticipatedchangestotheICMcorridor’sroadwaynetwork.

M InstitutionalJobTasks

Notpartofsystemtesting.Willbeevaluatedduringpostimplementationreview.

IN-1.2

TheCorridorManager,incoordinationwithstakeholders,shalltrackanticipatedchangestotheICMcorridor’stransitnetworksofinterest.



IN-1.3

TheCorridorManager,incoordinationwithstakeholders,shalltrackanticipatedchangestothecorridor’strafficcontroldevices(trafficsignals,rampmeters,others).



IN-1.4

TheCorridorManager,incoordinationwithstakeholders,shalltrackanticipatedchangestothecorridor’stravelerinformationdevices(CMS,extinguishabletrailblazersigns,etc.).



IN-1.5

TheCorridorManager,incoordinationwithstakeholders,shalltrackrequiredchangestoexistingsensorsandsensorlocations.



IN-1.6

TheCorridorManager,incoordinationwithstakeholders,shalltrack




32

TestREQID



anticipatedchangestothemetricsthatmustbeprovidedbytheICMsystem.

IN-1.7

TheCorridorManager,incoordinationwithstakeholders,shalldeterminerequirementsfornewmetrics.



IN-1.8

TheCorridorManager,incoordinationwithstakeholders,shallmaintainastrategicplanforperformancemetriccalculation.

H InstitutionalJobTasks


IN-1.9

TheCorridorManager,incoordinationwithstakeholders,shallmaintainastrategicplanfordatacollection.



IN-1.10

TheCorridorManager,incoordinationwithstakeholders,shallmaintainastrategicplanforcorridorcontrol.



8.3.1.1.2 AssetExistence

IN-2.1

Stakeholdersshallensuresensingassetsrequiredbythecorridorstrategicplanareavailable.



IN-2.2

Stakeholdersshallensuretrafficcontrolassetsrequiredbythecorridorstrategicplanareavailable.



IN-2.3

Stakeholdersshallensuretravelerinformationassetsrequiredbythecorridorstrategicplanareavailable.



IN-2.4

Stakeholdersshallensuretransitassetsrequiredbythecorridorstrategicplanareavailable.



8.3.1.1.3 CorridorChampions

IN-3.1

CorridorChampionsshallbehigh-levelstaffpersonsorelectedofficialswithinterestintransportation/transitissues.




33

TestREQID



IN-3.2

CorridorChampionsshallhavelongevity(forexample,ifanelectedofficial,someonewhoisnottermedoutinthenextyearorso,ifpossible).

M

InstitutionalJobTasks


IN-3.3

AlistofcurrentCorridorChampionsfromeachstakeholderagencyshallbedevelopedandmaintainedbytheOutreachandCommunicationsManager.



IN-3.4

ThelistofcurrentCorridorChampionsshallbedistributedtoallprojectstakeholders.



IN-3.5

CorridorChampion(s)shallbereplacedifpreviouschampion(s)leave.



8.3.1.1.4 OrganizationalCompositionandStructure

IN-4.1

TheConnectedCorridorsSteeringCommitteeshalldefineroles,responsibilities,andreportingstructuresfortheICMsystem.



IN-4.2

JobdescriptionsshallbewrittenforsupportingICMroles.



IN-4.3

StakeholderagenciesshallensurethatICMstaffareinplaceandtrained.



IN-4.4

Oversightandadvisorycommitteesshallbesetupandmaintained.



8.3.1.1.5 ManagementStructureandProcesses

IN-5.1

ProcessesshallbeestablishedtomanagetheICMcorridor.



IN-5.2

ManagersshallbeidentifiedtomanagetheICMcorridor.



IN-5.3

StakeholdersshalldevelopnewproceduresandpracticessupportingICMcorridormanagementobjectives.



IN-5.4

Caltrans,inconsultationwithsystemstakeholders,shallmaintainaRiskRegister.




34

TestREQID



8.3.1.1.6 InteragencyTrustandCommunication

IN-6.1

AllagencieshavingapotentialinterestinICMcorridoroperationsshallbeengagedindevelopment,implementation,andoperationalICMactivities.



IN-6.2

Clear,consistentcommunicationmechanismsshallbeestablishedamongthecorridorstakeholders.



IN-6.3

QuarterlymeetingsshallbeheldtokeepICMsystemstakeholdersupdatedonsystemandcorridoractivities.



IN-6.4

Stakeholderagenciesshallestablishandmaintaincommunicationsmechanismswithotherstakeholderagencies.



IN-6.5

InformationrequestsabouttheICMsystemshallbeappropriatelyfollowedup.



8.3.1.1.7 InteragencyAgreements

IN-7.1

AProjectChartershallbedraftedtogetstakeholderagenciestoagreeoninitialrolesandresponsibilities.



IN-7.2

AMemorandumofUnderstanding(MOU)shallbesignedbyprojectstakeholderstogetformalagreementonexpectedrolesandresponsibilities.



IN-7.3

AnOperations&Maintenance(O&M)Planshallbesignedbycorridorstakeholders.



IN-7.4

TheOutreachandCommunicationsManager,withassistancefromcorridorstakeholders,shalldeterminewhetheradditionalagreementsmaybeneededtosupportsystemoperations.



IN-7.5

Managementofagreementsshallbetheresponsibilityof


Notpartofsystemtesting.Willbeevaluatedduringpost


35

TestREQID



theOutreachandCommunicationsManager.

implementationreview.

IN-7.6

Stakeholderagenciesshallsigninatimelymanneragreementssubmittedfortheirapproval.



IN-7.7

Developedagreementsshallbemaintained,updated,and/oramendedthroughoutthelifeoftheproject.



IN-7.8

StakeholderagenciesshallparticipateinthereviewandupdatingofdocumentsrelatedtotheoperationoftheICMsystem.



8.3.1.1.8 FundingforICMSystem

IN-8.1

Potentialfundingsourcesshallberesearchedonanongoingbasis.



IN-8.2

Adequatesupportshallbeprovidedforthedevelopmentandsubmissionoffundingapplications.



IN-8.3

Approvedfundingsourcesshallbemanaged,andnecessaryreportscompletedandsubmitted.



8.3.1.1.9 Trainingandeducation

IN-9.1

AdequatetrainingshallbeprovidedtoindividualsresponsibleforICMoperations.



8.3.1.1.10 PublicOutreachandCommunications

IN-10.1

AnOutreachandCommunicationsManagershallbeaCaltransroleresponsibleforhandlinggeneraloutreachandcommunicationactivitiespertainingtotheICMsystem.



IN-10.2

InformationonstakeholderagenciesshallbecollectedandupdatedonanongoingbasisbytheOutreachand




36

TestREQID



CommunicationsManager.

IN-10.3

Keycorridorstakeholdersshallreviewdocumentssubmittedtothembyagreed-upondeadlines.



IN-10.4

AgenciesparticipatingintheoperationoftheICMsystemshallidentifyaPIO(orPIOrole)whoshallbeactivelyinvolvedinICMoutreachandcommunicationsactivities,suchaspressevents,announcements,briefingsonincidents/events,etc.



IN-10.5

Ongoing,inclusivecommunicationshallbeestablishedamongcorridorPIOs.



IN-10.6

CorridorstakeholdersshallkeeptheCorridorManagerinformedofscheduledeventsanticipatedtohaveanoticeableimpactontravelconditionsalongcorridorarterialsthatmaybeusedasdetoursbytheICMsystem.



8.3.1.1.11 ManagementofThird-PartyRelationships

IN-11.1

TheCorridorManagerincoordinationwithstakeholdersshallmanagethird-partyrelationships.



IN-11.2

Third-partypurchasingchoicesandcontractsshallbereviewedperiodicallyunderthedirectionoftheCorridorManager.



8.3.1.2 CorridorMonitoring

8.3.1.2.1 StaticTransportationNetworkCharacteristics

CM-3.1

RoadwayoperatorsshallmaintainandcommunicatetotheCorridorManagerup-to-datedefinitionsofroadway




37

TestREQID



facilitiesconnectedtotheICMEnvironment.

CM-3.2

Parkingfacilityoperatorsshallmaintainup-to-datedefinitionsofpark-and-ridefacilitiesconnectedtotheICMEnvironment.

L InstitutionalJobTasks


CM-3.3

Transitoperatorsshallmaintainup-to-datedefinitionsoftransitelementsconnectedtotheICMEnvironment.



CM-3.4

TheCorridorManagershallensurethatnetworkdefinitionsareuptodateinalllocationswithintheICMCoresystem.



8.3.1.2.2 AssetInventoryandHealthManagement

CM-4.1

TheICMCoreSystemshallcontinuouslyassessthehealthstatusofdevicesusedtomonitortrafficconditions.

H DataHub/DSS 1. VerifytheICMCoreSystemshallmonitorforfaultanderrormessagesthatmaybesentbyindividualtrafficdetectiondevices.

2. VerifyvalidPEMSsensordatamonitoringtrafficconditions.

3. Verifyfaulty&erroneousdatafromsensorscanbedetectedinventorychecksonPEMSsensors.

4. VerifyflowchecksandflowbalancesarestoredinCassandra.

5. VerifytheICMCoreSystemshallmonitorforfaultanderrormessagesthatmaybesentbyindividualtrafficdetectiondevices.

6. Verifyerroneoustraveltimemeasurementfromsensorscanbedetected.

7. Verifyvalidarterialsensordataismonitoringtrafficconditions.

8. Verifyfaulty&erroneousdatafromarterialsensorscanbedetected.

9. VerifytheICMCoreSystemshallmonitorfor

Connecttodataendpoint,AMQendpointtoverifythedataiscorrect

CheckforvalidsensordataCheckthatthequalityindicatorispresent&correct,thesensorsaregivingrightinformationAutomationtestcandidate


38

TestREQID



faultyanderrormessagesthatmaybesentbyindividualtraveltimemeasurementdevices.Verifyerroneoustraveltimemeasurementfromarterialsensorscanbedetected.

CM-4.2

TheICMCoreSystemshallcontinuouslyassessthehealthstatusofdevicesusedtocontroltrafficwithinthecorridor.

H DataHub/DSS 10. VerifytheICMCoreSystemshallmonitorforfaultyanderrormessagesthatmaybesentbytrafficsignalcontrollers.

11. VerifytheICMCoreSystemshallmonitorforfaultyanderrormessagesthatmaybesentbyindividualrampmetercontrollers.

Connecttodataendpoint,AMQendpointtoverifythedataiscorrect

Automationtestcandidate

CM-4.3

TheICMCoreSystemshallcontinuouslyassessthehealthstatusofdevicesusedtoinformtravelers.

H DataHub/DSS 12. Verifytheerrormessageandstatusinformationfromchangeablemessagesigns(CMS),extinguishabletrailblazersigns(arterials).

13. VerifytheerrormessageandstatusinformationfromHAR.

14. Verifythehealthstatusispresentandcorrect.

ConnecttoCMS&HARSOAP&AMQendpoint.ConnecttoHARinventoryendpoint.


CM-4.4

TheICMCoreSystemshallcontinuouslyassessthehealthstatusofcommunicationnetworksusedbyparticipatingagenciestoexchangeinformation.

H DataHub/DSS 15. VerifyICMcanmonitorfaultyorerrormessagesthatmaybesentfromRIITScommunicationnetwork.

16. VerifytheRIITSprocessedstatusmessageiscorrect.

ConnecttoRIITScenteractiveverificationSOAPendpoint.

CM-4.5

TheICMCoreSystemshallreportonidentifiedoperationalproblemswithdevicesusedtomonitorandmanagetravelwithinthecorridor.

H CorridorManagement

17. Verifyforeachdevicewithanidentifiedorreportedproblem,theICMCoreSystemshallstorethefollowinginformation:Verifyallphysicaldevices(sensors,arterialsensors,intersectionsignals,rampmeter,environmentsensors)withknownproblemrecord:• Daterecordwas

createdorlastupdated

• Dateproblemwas

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria


39

TestREQID



firstidentified• Typeofdevice

affected• Locationofdevice• Agencyresponsible

fordeviceoperationandmaintenance

• Reportproblemwithdevice

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.18. VerifytheICMCore

SystemshallnotifydailythedesignatedTMCorTCSoperatorofeachstakeholderagencyofidentifiedproblemswithatrafficmonitoringdeviceoperatedbytheagency.VerifyTMCorTCSoperatornotifiesdailyofeachstakeholderagencyofidentifiedproblemswithatrafficmonitoringdeviceoperatedbytheagency.

8.3.1.2.3 ControlAssetStateMonitoring

CM-5.2

TheICMCoreSystemshallmonitorinrealtimetheoperationalstateoftrafficcontroldevicesusedalongroadwaysunderICMmanagement.

H DecisionSupport

19. Verifystatusmessagefromsignalintersectionalongcorridorarterial.Verifysignalstatemessagesarepresentandcorrect.

20. Verifystatusmessagefromeachon-rampsfreewaysectionrampmeter.Verifyon-rampmessagesarepresentandcorrect.

Connecttothedatahubintersectionsignalstateendpoint.Connecttothedatahubrampmeterstateendpoint

CM-5.3

TheICMCoreSystemshallmonitorinrealtimetheoperationalstateoftravelerinformationdevicesunderICMmanagement.

H DecisionSupport

21. VerifyHARstatusmessage.

22. VerifyCMSblazerstatusmessage.

23. VerifyTrailblazerstatusmessage.

ConnecttoCMS,HAR,Trailblazerendpoint.



40

TestREQID



8.3.1.2.4 TrafficMonitoring

CM-6.1

TheICMCoreSystemshallmonitorinrealtimetrafficconditionsonfreewaysegmentswithintheICMcorridorevery30seconds.

H DataHub 24. VerifylatencyofoneminuteorlessfortrafficvolumemeasurementsatSensorsontrafficlanes(livePEMSdata).

25. VerifylatencyofoneminuteorlessfortrafficvolumemeasurementsatSensorsonHOVlanes(livePEMSdata).

26. VerifylatencyofoneminuteorlessfortrafficvolumeatSensorsonfreewayon-ramps(freewayon-rampmeter).

27. VerifylatencyofoneminuteorlessfortrafficvolumeatSensorsonfreewayoff-ramps(freewayoff-rampmeter).

28. VerifylatencyofoneminuteorlessfortrafficvolumeatSensorsonfreeway-to-freewayconnectors(livePEMSdata).

29. Verifylatencyofoneminuteorlessforsensoroccupancyongeneralpurposetrafficlanes(livePEMSdata).

30. VerifylatencyofoneminuteorlessforsensoroccupancyonHOVlanes(livePEMSdata).

31. Verifylatencyofoneminuteorlessforspeedmeasurementongeneraltrafficlanes(livePEMSdata).

32. VerifylatencyofoneminuteorlessforspeedmeasurementonHOVlanes(livePEMSdata).

Connecttodatahubendpoint(SOAP&AMQ)andcheckthedataisthereandcorrect


CM-6.2

TheICMCoreSystemshallmonitorinrealtimetrafficconditionsonkeycorridorarterials.

H DataHub 33. VerifylatencyofoneminuteorlesstrafficflowmeasurementsfromsensorsoperatedbyCaltransalongkeycorridorarterials(allthe

ConnecttoIntersect-ionsignalsensorsdataendpointandverifythe


41

TestREQID



arterialsieLosAngelesCounty,CityofPasadena,CityofArcadia,CityofMonrovia,cityofDuarte).

34. Verifylatencyofoneminuteorlessdatacollectedbytraveltimemeasurementsystemsoperatedbylocalagenciesalongkeycorridorarterials(allthearterialsieLosAngelesCounty,CityofPasadena,CityofArcadia,CityofMonrovia,cityofDuarte).

dataisthereandcorrectConnecttotraveltimesensingdataendpoint

8.3.1.2.5 TransitMonitoring

CM-7.1

TheICMCoreSystemshallmonitorforsignificanttransitservicedisruptionsalongrelevanttransitrouteswithinthecorridor.

M DataHub Testingtobedefinedwhentherequirementisaddressed.

CM-7.2

TheICMCoreSystemshallmonitoraverageridershipalongtransitservicesofinterestwithinthecorridor

L DataHub Testingtobedefinedwhentherequirementisaddressed.

CM-7.3

TheICMCoreSystemshallreportonmonitoredtransitoperationswithintheICMcorridor.

M CorridorManagement

Testingtobedefinedwhentherequirementaddressed.

8.3.1.2.6 Park-and-RideMonitoring

CM-8.1

TheICMCoreSystemshallmonitorinrealtimepark-and-rideavailabilityatfacilitiesoperatedbyparticipatingagencieswithinthecorridor.

L DataHub Testingtobedefinedwhentherequirementaddressed.

CM-8.2

TheICMCoreSystemshallreportonparkingavailabilityatfacilitiesunderICMsurveillance.

L CorridorManagement

Testingtobedefinedwhentherequirementaddressed.

8.3.1.2.7 CorridorPerformanceMetrics

CM-9.1

TheICMCoreSystemshallcalculateandstoremetricssummarizingoverallcorridorperformance.

H DecisionSupport

35. VerifyProductivitymetricsfortheentirecorridor:• Vehicle-miles

Connecttoestimationmetricendpoint&

Corridorperformancetestforgeographic


42

TestREQID



traveled(VMT)• Vehicle-hours

traveled(VHT)• Vehiclehoursof

delay• Vehicleoccupancy

(personmilestraveled,personhourstraveled)

• Estimateaveragevehicleoccupancyfactor

AMQendpointandcheckthedataisthereandcorrect

area/timespansAutomationtestcandidate

CM-9.2

TheICMCoreSystemshallcalculateandstoremetricssummarizingtheperformanceofmainlinefreewayoperations.

H DecisionSupport

36. Verifyvehiclebasedmetricsonfreewaysegment(estimationengine,vehiclesensing):• Totalvehicleflow• Vehicle-miles


traveled(VHT)• Averagetraveltime

acrosssegment• Averagespeed

acrosssegment• Vehicle-hoursof

delay(VHD)• Averagedelayper

vehicle• VehicleOccupancy

Factor:Totalpersonflow

• VehicleOccupancyFactor:Person-milestraveled(PMT)

• VehicleOccupancyFactor:Person-hourstraveled(PHT)

• Reliabilitymetrics:Traveltimeindex

• Reliabilitymetrics:Bufferindex(extratimethattravelersmustaddtotheiraveragetraveltimewhenplanningtripstoensureon-timearrival)

• HOVlanedatafromsensors

Connecttoestimationmetricsendpoint&AMQandcheckthedataisthereandcorrect

CorridorperformancetestAutomationtestcandidate

CM-9.3

TheICMCoreSystemshallcalculateandstoremetricssummarizingtheperformanceoffreewayrampoperations.

H DecisionSupport

37. Verifyvehiclebasedmetricsonfreewayon-rampoff-ramp(estimation&sensing):• Totalvehicleflow

Connecttoestimationmetricsendpoint&AMQ

CorridorperformancetestAutomation


43

TestREQID



• Vehicle-milestraveled(VMT)

• Vehicle-hourstraveled(VHT)

• Vehicle-hoursofdelay(VHD)

• Averagedelaypervehicle

• Vehicleoccupancyfactors:Totalpersonflow

• Vehicleoccupancyfactors:Person-milestraveled(PMT)

• Vehicleoccupancyfactors:Person-hourstraveled(PHT)

endpointandcheckthedataforthefreewayrampsisthereandcorrect

testcandidate

CM-9.4

TheICMCoreSystemshallcalculateandstoremetricssummarizingtheperformanceofarterialtrafficoperations.

H DecisionSupport

38. VerifytheICMCoreSystemshallcalculateandstorethefollowingbasedmetricsonarterials:• Totalvehicleflow• Vehicle-miles


traveled(VHT)39. VerifytheICMCore

Systemshallestimateandstorethefollowingperson-basedproductivitymetricsbasedonavailableaverageregionalvehicleoccupancyfactors:• Totalpersonflow• Person-miles

traveled(PMT)• Person-hours

traveled(PHT)40. VerifytheICMCore

Systemshallestimateandstorethefollowingperson-basedmobilitymetricsbasedonavailableaverageregionalvehicleoccupancyfactors:• Person-hoursof

delay(PHD)• Averagedelayper

person41. VerifyICMCoreSystem

shallcalculateandstorethefollowingvehicle-

Connecttoestimationmetricsendpoint,AMQendpointandcheckthedataisthereandcorrect

ArterialcorridorperformancetestAutomationtestcandidate


44

TestREQID



basedproductivitymetrics:• Vehicleflow(each

approach)• Averagedelayper

vehicle(eachapproachandoverallintersection)

42. Verifythekeyintersectionsshallcalculateandstorethefollowingperson-basedproductivitymetrics:• Personflow(each

approach)• Averagedelayper

person(eachapproachandoverallintersection)

43. Verifythekeyintersectionsshallcalculateandstorethefollowingvehicle-basedproductivitymetrics:• Vehicleflow

capacity(eachapproachandoverallintersection)

• Volume-to-capacityratio(eachapproachandoverallintersection)

• Averagequeuelength(eachapproach)

44. Verifythekeyintersectionsshallcalculateandstorevehicle-basedmobilitymetrics:• Vehicle-hoursof

delay(eachapproachandoverallintersection)

• Averagedelaypervehicle(eachapproachandoverallintersection)

45. Verifythekeyintersectionsshallcalculateandaverageregionalvehicleoccupancyfactors.

CM-9.5

TheICMCoreSystemshallcalculateandstoremetrics

H DecisionSupport

46. Verifythevehicle-basedproductivitymeasures:

Connecttoestimation

Performancetest


45

TestREQID



summarizingtheperformancealonguser-definedroutes.

• Maximumvehicleflowalongeachsegmentoftheroute

• Vehicle-milestraveledalongtheroute(VMT)

• Vehicle-hourstraveledalongtheroute(VHT)

• Verifytheperson-basedproductivitymeasuresbasedonavailableaverageregionalvehicleoccupancyfactors:

• Maximumpersonflowalongeachsegmentoftheroute

• Person-milestraveledalongtheroute(PMT)

• Person-hourstraveledalongtheroute(PHT)

• Verifythefollowingmobilitymeasures:

• Overalltraveltimealongtheroute

• Speedcontourplot47. Verifythefollowing

reliabilitymeasures:• Observedtravel

timevariabilityalongtheroutewithinthedefinedtimeperiod

• Observedflowvariabilityalongtheroutewithinthedefinedtimeperiod

• Traveltimeindexfortheroute

• Bufferindexfortheroute(extratimethattravelersmustaddtotheiraveragetraveltimewhenplanningtripstoensureon-timearrival)

metricsendpoint&AMQendpointandcheckthedataisreportedcorrectly


CM-9.6

DecisionSupportshallcompileperformancemetricsforeachroadway

H DecisionSupport

48. Verifymetricscalculatedforfreewayelements(mainlinesections,on-

Connecttoestimationmetricsdata

Performancetest


46

TestREQID



managementagencyparticipatingintheoperationoftheICMsystem.

ramps,off-ramps,freeway-to-freewayconnectors).

49. VerifymetricscalculatedforarterialsegmentsmanagedbyLosAngelesCounty.

50. VerifymetricscalculatedforarterialsegmentsmanagedbyPasadena.

51. VerifymetricscalculatedforarterialsegmentsmanagedbyArcadia.

52. VerifymetricscalculatedforarterialsegmentsmanagedbyMonrovia.

53. VerifymetricscalculatedforarterialsegmentsmanagedbyDuarte.

hubendpoint(SOAP&AMQ)andcheckthedataisthereandcorrect


CM-9.7

TheICMCoreSystemshallcompilemetricssummarizingtheperformanceofmonitoredtransitservices.

M DecisionSupport

Testingtobedefinedwhentherequirementisaddressed.

CM-9.8

TheICMCoreSystemshallcompilemetricssummarizingtheperformanceofparkingfacilities.

L DecisionSupport


8.3.1.2.8 TrafficStateDetermination

CM-10.1

TheICMCoreSystemshalluseavailablesensordatatodeterminethestateoftrafficalongroadwaysofinterestwithintheICMcorridor.

H DecisionSupport

54. Verifythatthesensingalongtheroadwaysofinterestisproperlyassimilatedintoeachestimation.

55. Verifysensordatatoestimatetheaveragetrafficflow/trafficspeed/traveltimesonfreeway.

56. VerifytheICMCoreSystemshalluseavailablesensordatatoestimatetheprevailingaveragetrafficflowrateonsectionsofroadwaysofinteresttothesystem.

57. VerifytheICMCoreSystemshalluseavailablesensordatatoestimatetheprevailingaveragetrafficflowratebetweensuccessiveon-rampsalongthesections

Connecttoestimationendpoint,AMQendpointandcheckthedataisthereandcorrect



47

TestREQID



ofI-210,I-605,andSR-134withintheICMcorridor.

58. VerifytheICMCoreSystemshalluseSensordatatoestimatetheprevailingaveragetrafficflowrateonHOVlanesbetweensuccessiveon-rampsalongthesectionofI-210withintheICMcorridor.

59. Verifyavailablesensordatatoestimateprevailingaveragetrafficflowratesonon-rampsalongthesectionsofI-210,SR-134,andI-605withintheICMcorridor.

60. Verifyavailablesensordatatoestimateprevailingaveragetrafficflowratesonoff-rampsalongthesectionsofI-210,SR-134,andI-605withintheICMcorridor.

61. Verifyavailablesensordatatoestimateprevailingaveragetrafficflowratesonarterialsegmentsalongpotentialdetourroutes.

62. Verifyavailablesensordatatoestimateprevailingaveragetrafficflowratesonarterialsegmentsoutsidepotentialdetourroutesthatmayinfluencedecision-makingactivities.

63. Verifytheavailablesensordatatoestimateprevailingaveragetrafficspeedsonsectionsofroadwaysofinteresttothesystem.

64. Verifyavailablesensordatatoestimatetheprevailingaveragetrafficspeedonthegeneral-purposetrafficlanesbetweensuccessiveon-rampsalongthesectionsofI-210,SR-134,andI-


48

TestREQID



605withintheICMcorridor.

65. VerifyavailablesensordatatoestimatetheaveragetrafficspeedontheHOVlanesbetweensuccessiveon-rampsalongthesectionsofI-210andSR-134withintheICMcorridor.

66. Verifytheavailablesensordatatoestimateprevailingaveragetrafficspeedsonarterialsegmentsalongpotentialdetourroutes.

67. Verifytheavailablesensordatatoestimateprevailingaveragetrafficspeedsonarterialsegmentsoutsidepotentialdetourroutesthatmayinfluencedecision-makingactivities.

68. Verifytheavailablesensordatatoestimateprevailingaveragetraveltimesalongsectionsofroadwaysofinteresttothesystem.

69. Verifytheavailablesensordatatoestimateprevailingaveragetraveltimesongeneral-purposetrafficlanesbetweenkeyinterchangesalongthesectionofI-210withintheICMcorridor.

70. VerifytheavailablesensordatatoestimateprevailingaverageHOV-lanetraveltimesbetweenkeyinterchangesalongthesectionofI-210withintheICMcorridor.

71. Verifytheavailablesensordatatoestimateprevailingaveragetraveltimesalongarterialsegmentsthatmaybepartofadetourroute.

72. Verifytheavailablesensordatatoestimate,


49

TestREQID



wherepossible,averagequeuelengthsalongsectionsofroadwaysofinteresttothesystem.

73. Verifytheavailablesensordatatoestimateprevailingaveragequeuelengthonfreewayon-rampsalongthesectionofI-210withintheICMcorridor.

74. Verifytheavailablesensordatatoestimateprevailingaveragequeuelengthonapproachestosignalizedintersectionsalongpotentialdetourroutes.

75. Verifytheavailablesensordatatodeterminethelevelofcongestiononsectionsofroadwaysofinteresttothesystem.

76. Verifytheavailablesensordatatoestimatethelevelofcongestionbetweensuccessiveon-rampsalongthesectionsofI-210,SR-134,andI-605withintheICMcorridor.

77. VerifytheavailablesensordatatoestimatethelevelofcongestiononHOVlanesbetweensuccessiveon-rampsalongtheI-210,SR-134,andI-605freeways.

78. Verifytheavailablesensordatatoestimatethelevelofcongestionbetweenkeyintersectionsonarterialsegmentsalongpotentialdetourroutes.

CM-10.2

TheICMCoreSystemshallattempttouseavailablesensordatatoestimatetrafficconditionsonroadwaysectionsofinterestwithoutinstrumentation.

H DecisionSupport

79. Verifytheestimationisusingtheavailablesensordata.

80. Verifythatthetrafficonallroadways,withorwithoutinstrumentationareincludedinestimations.

Connecttoestimationendpoint&AMQendpointandthedataisthereandcorrect(withsensorsornot)



50

TestREQID



8.3.1.2.9 HistoricalPatternDetermination

CM-11.1

TheICMCoreSystemshalldeterminehistoricaltrafficpatternsfromavailabletrafficdata.

H DecisionSupport

81. Verifyforeachtrafficdetector,ICMcoreshalldetermineuponrequestthefollowingstatisticsoveraspecifiedperiod:• Averagemeasured

volumesforright-turn,thru,andleft-turnmovements

• Volumevarianceforeachmovement

• Averageflowmeasurement

• Averagesensoroccupancy

• Averagespeedmeasurement(ifavailable)

• Flowvariance• Sensoroccupancy

variance82. Verifyforeach

intersectionforwhichturnmovementsareavailable,theICMCoreSystemshalldetermineuponrequestthefollowingstatisticsoveraspecifiedperiod:• Averagemeasured

volumesforright-turn,thru,andleft-turnmovements

• Volumevarianceforeachmovement

• Foreachroadwaysegmentforwhichtraveltimemeasurementsareavailable,theICMCoreSystemshalldeterminethefollowingstatisticsoverauser-orsystem-specifiedperiod:

• Averagemeasuredtraveltime

• Traveltimevariance83. Verifythisistestedfor

eachdetector/intersection.

Connecttodatabasetocheckthedataisthereandcorrect



51

TestREQID



CM-11.2

TheICMCoreSystemshalldeterminehistoricalpatternsfromavailabletrafficcontroldata.

H DecisionSupport

84. Verifyforeachmeteredfreewayon-ramp,theICMCoreSystemshalldeterminethefollowingoperationalstatisticsoveraspecifiedperiod:• Averageperiod

duringwhichtherampmeterwasinoperation

• Averagestarttimeofmeteringoperation

• Averageendtimeofmeteringoperation

• Averagemeteringrateduringactiveperiod

• Proportionoftimethateachdefinedmeteringratewithinthecontrollerhasbeenused

85. Verifyforeachsignalizedintersection,theICMCoreSystemshalldeterminethefollowingoperationalstatisticsoveraspecifiedperiod:• Listofactivated

signaltimingplans• Totaltimeduring

whicheachactivatedtimingplanwasoperational

• Averageobservedcyclelength

• Minimumandmaximumobservedcyclelength

• Averagedurationofeachsignalphase

• Minimumandmaximumdurationofeachsignalphase

• Averagesignaloffset

Connecttodatabasetocheckthedataisthereandcorrect


CM-11.3

TheICMCoresystemshallcalculatevariabilitystatisticsassociatedwithreal-timetrafficdataoveragiveninterval.

H DecisionSupport

86. VerifytheDataManagementshallincludeafunctiontoobtainorcalculateacrossdays,weeks,months,oryearsthemeanvalueofflow,speed,andtravel

Connecttodatabaseandverifythedataisthereandcorrect



52

TestREQID



timedataprovidedtotheICMsystembyagivensensororsystemforagiveninterval.

87. VerifytheDataManagementshallincludeafunctiontoobtainorcalculateacrossdays,weeks,months,oryearsthestandarddeviationofflow,speed,andtraveltimedataprovidedtotheICMsystembyagivensensororsystemforagiveninterval.

88. Verifybothmeanandstandarddeviation.

CM-11.4

TheICMCoreSystemshallincludeafunctiontoanalyzehistoricaldataovertimeperiods.

H DecisionSupport

89. VerifyICMCoreSystemshallincludeafunctiontoanalyzehistoricaldataoverarangeofdates.

90. VerifyICMCoreSystemshallincludeafunctiontoanalyzehistoricaldatawithinonedayofthecollectionofthehistoricaldatabeingcollected.

91. VerifyICMCoreSystemshallincludeafunctiontoanalyzehistoricaldataoverspecificweekdayswithinagivendaterange.

92. VerifyICMCoreSystemshallincludeafunctiontoanalyzehistoricaldataoveraninterval(forinstance,every15minutes,1hour,day,month,etc.)

93. VerifydatahubcanbeconfiguredtoprovideHistoricaldataovertimeperiods.

Connecttodatabaseandverifythedataisthereandcorrect


CM-11.5

TheICMCoreSystemshallnotifysystemuserswhetherarequestedhistoricaldatacompilationisfeasibleforthespecifiedperiodandreportingintervalbasedonavailabledataandthecharacteristicsoftheavailabledata.

H DecisionSupport



53

TestREQID



8.3.1.3 StrategicIncident/EventResponsePlanning(CorridorPlanning)

8.3.1.3.1 StakeholderInvolvement

SP-1.1

Stakeholdersshallparticipateinincident/eventresponseplanningactivities.



8.3.1.3.2 ManagementofResponsePlanComponents

SP-2.1

Systemstakeholdersshalldetermineandmaintaindesiredroutestobeusedasdetoursforincidentsandevents.



SP-2.2

Systemstakeholdersshallbeabletoinfluencetheselectionofsuitabledetoursaroundincidentsorevents.



SP-2.3

Systemstakeholdersshalldeterminethesignalizedintersectionsintheirjurisdictionswhosetrafficsignaltimingplansmaybechangedduringanincidentorevent.



SP-2.4

Systemstakeholdersshalldeterminewhichfreewayrampsshallhavetheirmeteringratechangedduringanincidentorevent.



SP-2.5

Systemstakeholdersshallidentifyorcreate,maintain,anddistributesignaltimingplanstobeusedalongcorridorarterialsduringincidentsandevents.



SP-2.6

Systemstakeholdersshallidentifyorcreate,maintain,anddistributerampmeteringplanstobeusedduringincidentsandevents.



SP-2.7

Systemstakeholdersshalldeterminemessagingequipmentthatmaybeusedtosupporttheimplementationofresponseplans.



SP-2.8

Systemstakeholdersshalldetermineequipment(vehiclesandotherportables)




54

TestREQID



thatmaybeusedtosupporttheimplementationofresponseplans.

SP-2.9

Systemstakeholdersshalldeterminepersonnelavailablefordeploymentduringanincidentorevent.



SP-2.10

Systemstakeholdersshalldeterminetypicalinformationtobesenttoagencypersonnelwhenrespondingtoanincidentorevent.



SP-2.11

Systemstakeholdersshalldeterminemessagestobepostedonfixedand/orportableCMSdeviceswhenrespondingtoanincidentorevent.



SP-2.12

TheCorridorManager,inconsultationwithallrelevantstakeholders,shalldeterminetheinformationtobesentto511services.



SP-2.13

TheCorridorManager,inconsultationwithallrelevantstakeholders,shalldeterminetheinformationtobesenttoHARstationsusedaspartofresponseplans.



SP-2.14

TheCorridorManager,inconsultationwithallrelevantstakeholders,shalldeterminetheinformationtobesenttothird-partyproviders.



SP-2.15

TheICMCoreSystemshallincludeafunctionforstakeholderstospecifypredefinedresponseplans,i.e.,specificsetsofresponseactionsthatmaybeconsideredasresponsestoanincidentorevent.



8.3.1.3.3 IncidentResponseTestingCapabilities

SP-3.1

TheICMCoreSystemshallincludeafunctionfortrafficengineerstocreatemockincidents.



Systemshallincludeafunctionfortrafficengineerstocreatemockincidents.

Manualtest


55

TestREQID



SP-3.2

TheICMCoreSystemshallincludefunctionalitypermittingmockincidentstobeusedtotesttheeffectivenessofcreatedorproposedresponseplans.



Systemshallallowuser-createdmockincidentstobesubmittedasrealincidentsfortestingpurposes.

96. Verifyuponreceivingamockincident,theICMCoreSystemshallperformReal-TimeIncidentPlanningandgenerateresponseplansaddressingthemockincidentasifitwerearealincident.

97. Uponreceivingamockincident,theICMCoreSystemshallidentifyarecommendedresponseplanasifthemockincidentwerearealincident.

98. Uponreceivingamockincident,theImplementationfunctionshallrecognizethataresponseplanisbeinggeneratedforamockincidentandstopresponseactivitiesattheidentificationofrequiredfieldcontrolactions.Nofieldcommandsaretobeissued.

99. Upontheexecutionofamockincident,theICMCoreSystemshallstoreinformationpermittingtothegenerationofapost-incidentreport.

Manualtest

8.3.1.3.4 RuleCreationandManagement

8.3.1.3.4.1 DecisionSupportRules

SP-4.1

TheICMCoreSystemshallincludeafunctionforuserstodefinerulestobeusedinthedevelopment,evaluation,selection,andimplementationofresponse


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.


56

TestREQID



plans.SP-4.2

Rulesfordeterminingtheexistenceofanincidentshallbedefinedandmaintained.



SP-4.3

Rulesfordeterminingtheseverityofanincidentshallbedefinedandmaintained.



SP-4.4

Rulesfordeterminingthezoneofinfluenceofanincidentoreventshallbedefinedandmaintained.



SP-4.5

Rulesforassessingthelevelofimpactofanincidentoreventoncorridoroperationsshallbedefinedandmaintained.



SP-4.6

Rulesforbuildingresponseplansfromasetofpossibleindividualresponseactionsshallbedefinedandmaintained.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.100. Verifytherulesexistfor

creatingresponseplans.

Manualtest

SP-4.7

Rulesforhandlingspecialmanagementoroperationalsituationsshallbedefinedandmaintained.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.101. Verifyruleslimitingthe

useofspecificroadwayelementsbasedonspecificsituationsshallbedefinedandmaintained.

102. Ruleslimitingtheuseofspecificroadwayelementswithoutsufficientcapacityshallbedefinedandmaintained.

103. Ruleslimitingtheuseofspecificroadwayelementsbasedontheoperationalstatusoftrafficmanagementdevicesontheseelementsshallbedefinedandmaintained.

Manualtest

SP-4.8

Rulesforselectingarecommendedresponseplanamongasetofalternateplansshallbedefinedandmaintained.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.104. Verifyalternateplansare

defined.

Manualtest

SP-4.9

Rulesforsendingresponseplaninstructionstocorridorassetsshallbedefinedandmaintained.



Manualtest

SP-4.10

Rulesfordeterminingagencypersonnelwhoshouldbe


105. Verifyrulesfordeterminingagency

Manualtest


57

TestREQID



notifiedofaresponseplanningactionshallbedefinedandmaintained.

personnelwhoshouldbenotifiedofaresponseplanningactionshallbedefinedbytrafficengineersfromstakeholderagencies.

106. Verifyrulesexistfordefiningresponseplannotification.

SP-4.11

TheICMCoreSystemshallincludeafunctionforTrafficEngineerstospecifytheconditionsunderwhichtheimplementationofanapprovedresponseplancanbecanceled.



SP-4.12

Systemusersshallspecifythelevelofautomationrequiredfortheapprovalofsubmittedmodificationstoactiveresponseplans.



SP-4.13

DecisionSupportshallprovideameansforuserstogroupandcategorizerules.



8.3.1.3.5 RulesTestingandEvaluation

SP-4.11

Proposedmodificationtoexistingrulesshallbevalidatedoverauser-definedperiodpriortobeingintroducedintotheproductionsystem.



SP-4.12

TheICMCoreSystemshallprovideanenvironmentallowingproposednewrulesorrulemodificationstobetestedandvalidatedpriortotheirimplementation.



SP-4.13

TheICMCoreSystemshallconductarulestest,exercisingtherulesusingtestdataonaregularbasisandprovidingapass/failcheckfortheresultsofeachruleexecution.



SP-4.14

TheCorridorTechnicalManagershallconductweeklyandquarterlyevaluationsoftherulesandtheirexecution.




58

TestREQID



8.3.1.3.6 RuleDocumentingandArchiving

SP-4.15

TheICMCoreSystemshallprovideameansforuserstoarchiveruleswithinthesystem.



SP-4.16

AlldevelopedrulesshallbestoredinaformatusablebytheDSSrulesengine.

H DataHub Testingtobedefinedwhentherequirementisaddressed.

SP-4.17

TheICMCoreSystemshallutilizeaconfigurationmanagementsystemtomanagerules.



8.3.1.3.7 Post-Incident/EventAnalyses

SP-5.1

TheCorridorManagershallconductapost-incidentanalysisreviewwithallaffectedagencieswithinoneweekofeachsignificantevent.



8.3.1.3.8 QuarterlyOperationalReviews

SP-6.1

TheCorridorManagershallconductaquarterlyreviewoftheoperationaleffectivenessoftheICMEnvironment.



SP-6.2

Aspartofthequarterlyeffectivenessevaluation,theCorridorManagershallassignascoretotheobservedeffectivenessofresponseplanningactivities.



SP-6.3

TheCorridorManagershalluseresultsfromquarterlyoperationalassessmentsofdecisionsupportoperationstoinfluencecorridorplanningdecisions.



8.3.1.4 Real-TimeIncident/EventMonitoring

8.3.1.4.1 Incident/EventIdentification

IM-1.1.5

TheICMCoreSystemshallmaintainalistofactiveincidentsandeventsaffecting

H DataHub/DSS 107. Verifydatahubmaintainsalistofactiveincidentsandevents.

Connecttotheconductor



59

TestREQID



corridoroperations. andseethetaskstatusandseeiftheinformationispersisted

IM-1.1

TheICMCoreSystemshallbeawareofwhentrafficincidentsoccuroncorridorroadwaysofinterest.

H DataHub/DSS WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.108. Verifylawenforcement

agenciesshallinformtheICMCoreSystemaboutnewactiveincidentsassoonastheincidentshavebeenverified.Note:Thesystemshallbeabletooperatewithoutthisrequirementbeingmet.

109. VerifytheICMCoreSystemshallreceivefromfirstrespondingagenciesinformationaboutactiveincidentsoreventsaffectingcorridoroperationsbeingmanagedbytheseagencies.Note:Thesystemshallbeabletooperatewithouttheserequirementsbeingmet.

110. VerifytheICMCoreSystemshallreceivefromtheCaliforniaHighwayPatrolinformationaboutmajoractiveincidentsontheICMcorridorbeingmanagedbytheagency.

111. VerifytheICMCoreSystemshallreceivefromtheLosAngelesCountySheriff’sDepartmentinformationaboutmajoractiveincidentsonmaincorridorarterialsinDuarte.

112. VerifytheICMCoreSystemshallreceivefromthePasadenaPoliceDepartmentinformationaboutmajoractiveincidentsonmaincorridorarterialsbeingmanagedbytheagency.

113. VerifytheICMCoreSystemshallreceivefromtheArcadiaPolice

Connecttotheendpointtocapturethelistofactiveincidentsandeventsforcorridorroadways



60

TestREQID



Departmentinformationaboutmajoractiveincidentsonmaincorridorarterialsbeingmanagedbytheagency.

114. VerifytheICMCoreSystemshallreceivefromtheMonroviaPoliceDepartmentinformationaboutmajoractiveincidentsonmaincorridorarterialsbeingmanagedbytheagency.

115. VerifytheVerdugoFireCommunicationsdispatchsystemshallsendtotheICMCoreSysteminformationaboutfireincidentsexpectedtosignificantlyaffectroadwayoperationswithintheICMcorridorbeingmanagedbytheagency.

116. VerifytheICMCoreSystemshallreceivefromLASAFEinformationaboutincidentsbeingrespondedtobytheagency.

117. VerifyICMCoreSystemshallretrieveincidentsreportedbytravelersonsocialmediaapplications.

118. VerifyICMCoreSystemshallincludeafunctionforsystemuserstomanuallydefinenewtrafficincidentsthatshouldbeconsideredbytheresponseplanningactivities.(Thiscanonlybeaddressedinthisreleaseandwillbeaddressedbycorridormanagementsystem)

IM-1.2

TheICMCoreSystemshallbeawareofmajortransitincidentsoccurringwithinthecorridor.

M DataHub/DSS Testingtobedefinedwhentherequirementisaddressed.

IM-1.3

TheICMCoreSystemshallbeawareofwhenscheduledeventsmayaffectcorridoroperations.

H DataHub/DSS WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.119. Verifythelistofmajor

scheduledevents

Connectto


61

TestREQID



expectedtohaveasignificantimpactoncorridoroperations.Verifytheinformationaboutscheduledeventsfrominformationsystemsusedbystakeholderagencies(theCaltransLaneClosureSystem(LCS)informationaboutplannedroadwayclosuresthatmayaffectcorridoroperations,LosAngelesCountyLaneClosureWebsiteinformationaboutplannedroadwayclosuresthatmayaffectcorridoroperations)

120. Verifyincidentinformationgetsupdatedaboutplannedlane/roadwayclosureswhenmanuallyenteredintothesystembysystemusers.WhenwegettheCMSsystemwecanverifythedataiscorrect.

121. VerifyincidentinformationgetsupdatedafunctionforusersieStakeholdersshallenterintotheICMCoreSysteminformationaboutscheduledeventsorplannedlaneorroadwayclosure,tomanuallydefineneweventsthatshouldbeconsideredbytheresponseplanningactivities.WhenwegettheCMSsystemwecanverifythedataiscorrect.

theendpointtocapturethelistofactiveincidentsandeventsforcorridorroadways

IM-1.4

TheICMCoreSystemshallbeawareofwhenmajorweathereventsmayaffecttravelconditionswithinthecorridor.

L DataHub/DSS Testingtobedefinedwhentherequirementisaddressed.

IM-1.5

TheICMCoreSystemshalldeterminewhenunusualtrafficconditionsexistwithinthecorridor.

H DataHub/DSS Testingtobedefinedwhentherequirementisaddressed.

IM-1.6

TheICMCoreSystemshallalertrelevantTMCorTCS




62

TestREQID



operatorswhenunusualtrafficvolumesorspeedsaredetected.

IM-1.7

TheICMCoreSystemshallhaverulesandparametersforincidentdetectionthatcanbeadjusted("fine-tuned")tominimizefalsealertsandeffectivelydeliverusefulwarningstotheoperator.



IM-1.8

TheICMCoreSystemshallensurethatduplicateincidentsoreventsarenotcreatedwhenprocessingdatafromvarioussources.

M DSS/DataHub Testingtobedefinedwhentherequirementisaddressed.

8.3.1.4.2 Incident/EventVerification

IM-2.1

Allincidentsshallbeverifiedbeforeinitiatingresponseplanning.

H DecisionSupport

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.122. Verifyiftheincidents

thathavebeenverifiedtoexistbeforedevelopingresponseplans.

123. Verifyiftheeventsthathavebeenverifiedtooccurbeforedevelopingresponseplansforscheduled.


IM-2.3

TheICMCoreSystemshallremovefromconsiderationanyidentifiedincidentoreventthathasnotbeenverifiedwithinareasonableamountoftime.

H DecisionSupport

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.124. Verifyifanyidentified

faultyincidentoreventreportedisremovedfromconsideration.Keeplogforfuture.Reviewallunverifiedincidentsandeventshavebeenremovedfromconsideration.

8.3.1.4.3 Incident/EventCharacterization

IM-3.1

TheICMCoreSystemshallobtainorbeprovidedwithinformationallowingittoassesstheimpactofanincidentoreventoncorridoroperations.

H DecisionSupport

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.IncidentinformationwillbepartoftheCMS.125. Verifytheimpactofthe

incident.

Manualtest


63

TestREQID



• Typeofincident• Timeincident

occurred• Expectedduration

ofincident• Roadwaysegment

onwhichincidentislocated

• Locationofincidentalongroadwaysegment

• Lane(s)affectedbytheincident

• Agencyresponsibleformanagingtheincident

126. Verifytheimpactoftheevent.• Typeofevent• Locationofevent• Timeeventstarted• Expectedduration

ofevent• Roadwaysegment(s)

affectedbytheevent

• Trafficlanesaffectedbytheeventoneachaffectedroadwaysegment

• Agencyresponseformanagingtrafficevent

• Gather,storeincidentoreventcharacteristicsinadvancefromavailabledatafeeds.

IM-3.4

TheICMCoreSystemshallnotdevelopresponseplansforincidentsoreventsforwhichcriticalinformationismissing.

H DecisionSupport

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.127. Verifynoresponseplan

willbegeneratedforanincidentoreventthathasnotbeenlocatedonaspecificroadwaysegment.

128. Verifynoresponseplanwillbegeneratedifnoinformationaboutthenumberoflanesclosedontheaffectedroadway.

129. Verifynoresponseplanwillbegeneratedforan


64

TestREQID



incidentoreventifanexpecteddurationhasnotbeenprovided.

IM-3.5

TheICMCoreSystemshalllogforfuturereviewanynon-verifiedincidentoreventthathasbeenremovedfromconsideration.

M DecisionSupport


8.3.1.4.4 Incident/EventInformationDissemination

IM-4.1

TheICMCoreSystemshallnotifythesystem’sReal-TimeResponsePlanningfunctionofanynewactiveincident,unscheduledevent,orplannedeventoccurringwithintheICMcorridor.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.130. Verifywhenanincident

isinputted,itgetssentintothedecisionsupportsystem.UntilCMSisavailableforcethisatthedatahubendpointfortheCMS.

IM-4.2

TheICMCoreSystemshallincludefunctionalitytoinformstakeholders,travelers,andindustrypartnersofincidentsandevents.



IM-4.3

TheICMCoreSystemshallnotifyTMC/TCSoperatorsofactiveincidentsandeventsaffectingtravelconditionswiththeICMcorridor.



IM-4.4

TheICMCoreSystemshallinformfirstrespondersofactiveincidentsandeventsaffectingtravelconditionswiththecorridor.



SystemshallinformTrafficManagementTeamoffreewayincidentsandcorridoreventsthatmayrequireitsdeployment.

132. VerifytheICMCoreSystemshallinformLASAFEofidentifiedfreewayincidents.

133. VerifytheICMCoreSystemshallinformtheCHPofidentifiedfreewayincidentsandmajorarterialincidentsthatmayaffectfreewayoperations.

134. VerifytheICMCore


65

TestREQID



Systemshallinformlocalfirstrespondingagenciesofincidentsandeventsthatmayaffecttravelconditionswithintheirjurisdiction.• InformtheLos

AngelesCountySheriff’sDepartmentofincidentsandeventsexpectedtoaffectroadwaysmanagedbytheCityofDuarte.

• InformthePasadenaPoliceDepartmentofincidentsandeventsexpectedtoaffectroadwaysmanagedbytheCityofPasadena

• InformtheArcadiaPoliceDepartmentofincidentsandincidentsexpectedtoaffectroadwaysmanagedbytheCityofArcadia.

• InformtheCityofMonroviaPublicSafetyManagerofincidentsandeventsexpectedtoaffectroadwaysmanagedbythecity.

• InformtheCityofDuartePublicSafetyOfficerofincidentsandeventsexpectedtoaffectroadwaysmanagedbythecity.

• InformVerdugoFireCommunicationdispatchersofincidentsandeventsexpectedtoaffectroadwayswithintheICMcorridor.

• TheCorridorManagementSubsystemshallinformtheLosAngelesCounty


66

TestREQID



Sheriff’sDepartmentofcorridorincidentsandeventsexpectedtoaffectroadwaysmanagedbyLosAngelesCounty.

IM-4.5

TheICMCoreSystemshallinformtransitfieldsupervisorsofactiveincidentsandeventsaffectingtravelconditionswiththecorridor.



IM-4.6

TheICMCoreSystemshallinformcorridortravelers,bymultiplechannels,ofactiveincidentsandeventsaffectingtravelconditionswiththecorridor.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.Testingtobedefinedwhentherequirementisaddressed.135. TheICMCoreSystem

shallsendincident/eventalertstotheregional511System,Nixlecommunicationsystem,tothird-partynavigationapplicationproviders,andsocialmediaapplicationssupportingICMoperations.

IM-4.7

TheICMCoreSystemshallincludeafunctionforsendingincidentinformationdirectlytofirstrespondersoragencystaffinthefield(i.e.,viasmartphone,tablet,oronboardvehicledevice).


Testingtobedefinedwhentherequirementisaddressed.WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.

IM-4.8

TheICMCoreSystemshalldisseminateinformationaboutincidentsandeventsthatenablestheinformationrecipientstoassesshowtheincidentoreventmayimpacttheiractivities.



IM-4.9

TheICMCoreSystemshalldisseminateinformationabouthowidentifiedincidentsandeventsareexpectedtoimpactcorridortravelconditions.



8.3.1.4.5 Incident/EventTermination

IM-5.1

TheICMCoreSystemshallattempttodeterminewhen




67

TestREQID



anactiveincidentoreventhasterminated.

/DSS

IM-5.2

TheICMCoreSystemshallpermitevent/incidenttermination.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.136. Onlypersonnelfromthe

agencyassociatedwithanincidentoreventshallbeauthorizedtoterminateanevent.

137. Wheninformedthatanincidentoreventhasterminated,theICMCoreSystemshalllabeltheincidentoreventashavingterminated.

138. TheICMCoreSystemshallnotterminateanincidentoreventwithoutstakeholderapproval.

139. Beforemarkinganactiveincidentoreventashavingterminated,theICMCoreSystemshallseekconfirmationfromrelevantTMC/TCSoperatorsthattheincidentoreventhaseffectivelybeenterminated.

140. TMC/TCSoperatorsshallconfirmthattheincidentoreventhaseffectivelybeenterminatedbeforetheICMCoreSystemidentifiesitassuch.

141. TheICMCoreSystemshallnotifystakeholdersifanincidentoreventhasnotbeenterminatedwithinauser-definedtimepasttheexpectedduration.

8.3.1.4.6 Incident/EventArchiving

IM-6.1

TheICMCoreSystemshalllogallidentifiedincidents/events.

M CorridorManagement/DSS/DataHub

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.CMSwillhavelogofallincidents.142. Verifydatahublogofall

verifiedincidents.Automatethedatahub



68

TestREQID



part

8.3.1.5 DeterminationofReferenceDataforResponseplanning

RP-1.1

Attheonsetofaresponseplanningactivity,theICMCoreSystemshallidentifythesetofdatathatwillbeusedtoassistintheevaluationofcurrentcorridoroperationsandthedevelopmentoftrafficforecasts.

H DecisionSupport

143. Verifytherulesexistwhereveritisstored.Thisisamanualprocess.

144. Verifytheresponseplanpersistencecontainscurrentstateinformation(Assetdata,routedata,responsestate).

8.3.1.5.1 Incident/EventImpactAssessment

RP-2.1

Priortodevelopingaresponseplan,theICMCoreSystemshallassessthenear-futureimpactsofidentifiedincidentsoncorridoroperations.

H DecisionSupport

145. Verifyfollowingtheidentificationofanactiveincidentorevent(Predictionisrunforminimumofanhour),theICMCoreSystemshallassessthepotentialimpactoftheincidentoreventonoverallcorridoroperationsoverthenexthour.

146. Whenevaluatingtheimpactofanewactiveincidentorevent,theICMCoreSystemshalldeterminetheextentofthezoneofinfluenceoftheincidentorevent(Calculateszoneofinfluence).

147. Whenevaluatingtheimpactofanewactiveincidentorevent,theICMCoreSystemshallconsiderthecumulativeeffectofallotheractiveincidentsandeventswithinthecorridor,aswellasfutureeventsscheduledtostartduringtheevaluationperiod.

148. Verifythemodelithasrun,hasthecorrectstateinfoandtheinfofromotherincidents.

149. Verifythepredictionsthatarerunincludeallotherincidentinfoandthecurrentestimation.

Connecttotheendpointforprediction

AutomationtestcandidateManualtest


69

TestREQID



RP-2.2

TheICMCoreSystemshallonlyconductoperationalassessmentsofincidentsandeventsthathavebeenconfirmedtoexist.

H DecisionSupport

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.150. VerifyCMSonlysends

confirmedincidents.

RP-2.3

Basedontheresultsoftheincidentimpactassessment,activeincidentsoreventsshallbecategorizedusingrulesspecifiedinresponseplanningashavingaminor,medium,ormajorimpactoncorridoroperations.

H DecisionSupport

151. Verifyranking(1-10)ofresponseplanisreceived.

ConnecttodatahubendpointthatsendstheinformationtotheCMS.


8.3.1.5.2 ResponsePlanGeneration

RP-3.1

TheICMCoreSystemshallassembleresponseplansforallincidents,unscheduledevents,andplannedeventsexpectedtogenerateaveragedelaysof5minutesorgreatertotravelers.

H DecisionSupport

152. VerifytheICMCoreSystemshallassembleresponseplansforfreewayincidentsexpectedtolastlonger(setalimitintherulesengine10min/20mins,beyondthelimitandbelowthelimit)thanthenumberofminutesdefinedintheresponseplantriggerrulesandexpectedtogenerateaveragedelaysof5minutesorgreatertotravelers.

153. VerifytheICMCoreSystemshallassembleresponseplansforarterialincidentsexpectedtolastlongerthanthenumberofminutesdefinedintheresponseplantriggerrulesandexpectedtogenerateaveragedelaysof5minutesorgreatertotravelers.

154. VerifytheICMCoreSystemshallassembleresponseplansforplannedroadclosuresanticipatedtolastlongerthanthenumberofminutesdefinedintheresponseplantriggerrulesandexpectedto

Feedabunchofincidentsandseethecorrectresponseforvariouslimitsthatareputin

AutomationtestcandidateManualtest


70

TestREQID



generateaveragedelaysof5minutesorgreatertotravelers.

155. VerifytheICMCoreSystemshallassembleresponseplansforplannedeventsaffectingroadwayoperationsexpectedtolastlongerthanthenumberofminutesdefinedintheresponseplantriggerrulesandexpectedtogenerateaveragedelaysof5minutesorgreatertotravelers.

156. VerifytheICMCoreSystemshallassembleresponseplansforunexpectedeventsanticipatedtolastlongerthanthenumberofminutesdefinedintheresponseplantriggerrulesandexpectedtogeneratedelaysof5minutesorgreater.

157. Manualverificationiftherulesexist.

8.3.1.5.3 IdentificationofAvailableFieldElements

RP-3.2

Whenassemblingaresponseplan,theICMCoreSystemshallonlyconsidermodifyingavailable,workingassets.

H DecisionSupport

158. VerifytheICMCoreSystemshallusestatusdatacollectedfromindividualtrafficsignalcontrollerstodeterminewhetherchangestotheoperationofspecificsignalizedintersectionswouldbeauthorized.

159. VerifytheICMCoreSystemshallusestatusdatacollectedfromindividualrampcontrollerstodeterminewhethermeteringchangescanbeimplementedatspecificfreewayon-rampsorfreeway-to-freewayconnectors.

160. VerifytheICMCoreSystemshallusestatusdatacollectedfromfixed

Createadummymessageforarampmeterthatdoesn’texistNegativetestforvariousassetsthataren’tavailable



71

TestREQID



CMSstodeterminewhetherdesiredinformationmessagescanbedisplayedonspecificdevices.

161. VerifytheICMCoreSystemshallusestatusdatacollectedfromextinguishabletrailblazersignstodeterminewhetherthesignscanbeusedtoproviderouteguidance.

162. VerifytheICMCoreSystemshallchecktheavailabilityofportableCMSstodeterminewhethersuchdevicescanbedeployed.

163. VerifytheICMCoreSystemshallusestatusdatacollectedfromindividualHighwayAdvisoryRadios(HARs)todeterminewhetherthestationscouldbeusedtobroadcastincident/event-relatedmessages.

164. VerifytheICMCoreSystemshallremovefromconsiderationanycontrolelementdeterminedtobecurrentlyunavailable.

165. VerifytheICMCoreSystemshallremovefromconsiderationanycontrolelementprojectedtobecomeunavailablewithintheanticipatedperiodofapplicationoftheresponseplantobedeveloped.

RP-3.3

Whenassemblingaresponseplan,theICMCoreSystemshallonlyconsidermanagementresourcesavailablewithineachagencyatthetimeofdayaresponseplanisdeveloped.

H DecisionSupport

166. Verifytheresponseplanmanagementeliminatesresourcesthatarenotavailable.

Statusmessagewithassetnotavailableshouldn’tbeintheresponseplangenerated.Putinarule


72

TestREQID



withtheassetnotavailable.

RP-3.4

TheICMCoreSystemshallincludethecapabilitytoincludeorexcludeaparticularcontrolassetfrommodificationbyresponseplans.

L DecisionSupport


8.3.1.5.4 IdentificationofSuitableDetours

RP-3.5

Whenrespondingtoanincidentorevent,theICMCoreSystemshallfirstassesstheusabilityofuser-definedpredefineddetoursbeforeattemptingtoassemblenewdetourroutes.

L DecisionSupport


RP-3.6

Ifnopredefineddetourrouteisavailable,theICMCoreSystemshallconductnetworksearchestotrytoidentifypotentialdetoursaroundincidentsandeventswithinasetofallowableroadwaysegments.

L DecisionSupport


RP-3.7

TheICMCoreSystemshallbeabletoidentifysuitabledetoursforvarioustypesofvehicles.

M DecisionSupport


RP-3.8

TheICMCoreSystemshallconsiderallapplicableroadwaygeometricalrestrictionswhensearchingforsuitabledetoursaroundanincidentorevent.

H DecisionSupport

167. VerifytheICMCoreSystemshallrefrainfromsendingtrucksalongroadwaysegmentsforwhichtheremaybeinsufficientheightclearanceunderbridgesorstructures.

168. VerifytheICMCoreSystemshallrefrainfromsendingtrucksalongroadwaysegmentswherethereisinsufficientturningradiustoallowthevehiclestomakeintendedrightorleftturns.

169. VerifytheICMCoreSystemshallrefrainfromsendingbusesalongroadwaysegmentswherethereisinsufficientturningradius


73

TestREQID



toallowthevehiclestomakeintendedrightorleftturns.

170. Verifywithtrafficengineersthattheyroutevehiclestoroutessufficientforallvehicles.

RP-3.9

TheICMCoreSystemshallconsiderallapplicableactivetrafficrestrictionswhensearchingforsuitabledetoursaroundanincidentorevent.

H DecisionSupport

171. VerifytheICMCoreSystemshallnotsendtrafficintoschoolzoneswhenchildrenarewalkingtoandfromschools.

172. VerifytheICMCoreSystemshallnotsendheavyvehiclesonlocalarterialswithactivetruckrestrictions.

173. Verifytotheextentpossible,theICMCoreSystemshallrefrainfromsendingtrafficalongarterialsegmentsheavilytraveledbybuses(e.g.,ColoradoBlvdinPasadena).

174. Verifyrulesareinplacethatthisdoesn’toccur.

RP-3.10

TheICMCoreSystemshallconsidertheavailabilityoftrafficmanagementdevicesalongindividualdetours.

H DecisionSupport

175. VerifytheICMCoreSystemshallexcludefromconsiderationidentifieddetourswheretheproportionoftrafficcontrolsignalsthatcanbemodifiedbytheICMCoreSystemisbelowauser-definedthreshold.

176. VerifytheICMCoreSystemshallexcludefromconsiderationidentifieddetourswheretheproportionofdevicesthatcanbeusedtoprovideguidancealongtheidentifiedroute(suchasCMSsandextinguishabletrailblazersigns)isbelowauser-definedthreshold.

177. Verifyrulesareinplacethatthisworks.

RP-3.11

Unlessnecessary,theICMCoreSystemshallavoidsendingtraffictowardsstop-controlledintersections.

H DecisionSupport

178. Verifyrulesareinplacethatthisworks/noreroutesusestopcontrolledintersections.


74

TestREQID



RP-3.12

TheICMCoreSystemshallconsiderthecongestiondevelopingupstreamandaroundanincidentoreventwhensearchingforsuitabledetoursaroundanincidentorevent.

H DecisionSupport

179. Whereverpossible,theICMCoreSystemshallselectordevelopdetoursstartingfromapointupstreamofthecongestiondevelopingontheapproachtoanincident.

180. Whereverpossible,theICMCoreSystemshallselectordevelopdetourroutesavoidingheavilycongestedroadwaysegments.

181. Verifypredictionsaregettingacurrentestimation.

182. Verifyrulesareinplacetomakesureitworks.

RP-3.13

TheICMCoreSystemshallberobustenoughtoincorporateprojectedtrafficconditionsonthefreewaysandarterials,ifavailable,indeterminingthebestdetour(s)aroundincidentsandevents.

H DecisionSupport

183. Verifypredictionsareusedinevaluation.

Checkmultipleresponseplans(1-10plans)aredeveloped.

RP-3.14

TheICMCoreSystemshallincludeafunctiontoidentifyandaccommodatemorethanonedetourbeingimplementedsimultaneouslyasaresponsetoagivenincident/event.

H DecisionSupport

184. Verifyresponseplans(1-10plans)allowmorethanonesimultaneousdetour.

RP-3.15

TheICMCoreSystemshallrankpotentialdetourroutesaroundanincidentoreventbasedontheirattractivenessrelativetotheincidentorevent.(Note:Thisrequirementisrankedlow,astheinitialrequirementsstatethatresponseplanrouteswillbeselectedinadvance.Thisrequirementisinanticipationthatatsomepointinthefuturethesystemwillgenerateroutesinrealtime.)

L DecisionSupport


RP-3.16

TheICMCoreSystemshallincludeafunctiontoremoveroutesfromconsiderationbasedoncontrolassetavailability.

H DecisionSupport

185. TheICMCoreSystemshalleliminatefromconsiderationroadwaysegmentsorroutesalongwhichthenumberofunavailablecontrolassetsexceedsauser-definedthreshold.


75

TestREQID



186. TheICMCoreSystemshalleliminatefromconsiderationroadwaysegmentsorrouteswherecontrolassetscriticaltotheimplementationofaresponseplan(suchasatrafficsignalatakeyintersection)areunavailable.


RP-3.17

TheICMCoreSystemshallincludeafunctiontoreturna“noexistingdetour”solutionasasuitablesolutiontothesearchofdetourroutesaroundanincidentorevent.

H DecisionSupport

188. Verifythatthe“donothing”responseplanisselectedwhennobetterresponseplanisavailable.

8.3.1.5.5 IdentificationofSuitableControlActions(ResponsePlanDevelopment)

RP-3.18

TheICMCoreSystemshalldevelopresponseplansseekingtominimizetheanticipatedimpactsofidentifiedactiveincidents/eventsonnear-futurecorridoroperations.

H DecisionSupport

189. Whendevelopingaresponseplan,theICMCoreSystemshallpromoteactionsseekingtominimizeoveralltraveltimes/delayswithinthezoneofinfluenceoftherelatedincident/event.

190. Whendevelopingaresponseplan,theICMCoreSystemshallconsidertheeffectsoncorridoroperationsofallidentifiedactiveincidents/eventswithinthecorridor.

191. Whendevelopingaresponseplan,theICMCoreSystemshallconsidertheeffectsofallfutureroad/laneclosuresandeventsscheduledtooccurwithinthezoneofinfluenceoftherelatedincident/eventduringtheincident’sprojectedduration.


193. Verifythatfutureandcurrentincidentsandevents&laneclosures


76

TestREQID



areusedinpredictions.RP-3.19

Developedresponseplansshallbecomprisedofpre-approvedcontrolandmanagementactions.

H DecisionSupport

194. Verifyeveryresponseplanfrom1ormoreisinplace.Allofthemgetusedinsomeresponseplan.Thattheelementsofageneratedresponseplanhavebeenapproved.

195. Verifydevelopedresponseplansshallbecomprised,ataminimum,ofoneormoreofthefollowingcontrolactions:• Individualstobe

contactedateachagencyabouttheincidentbeingrespondedto.

• Recommendedalternateroutesaroundanincidentorevent:

• Recommendedroute(s)forpassengercars

• Recommendedroute(s)fortrucks

• Recommendedroute(s)forbuses

• Rampmeteringcontrolactions:

• Turningrampmeterstogreen(“Green-ball”operation)

• Activationofaspecificmeteringrate(0to15)

• Intersectioncontrol:• Changeintraffic

signalcontrolplaninoperation

196. VerifyPersonneldeploymentrequests:• Fullrampclosure• Locationswhere

portableCMSsaretobedeployed

• Informationdissemination:

• MessagestopostonfixedCMSs

• Messagestoposton


77

TestREQID



portableCMSstobedeployedalongthecorridor

• Extinguishabletrailblazersignstobeactivated

• MessagestobroadcastonHARs

197. Informationtodisseminateto511systems,third-partyinformationproviders,andmobiletravelapplicationdevelopers.

RP-3.20

Whendevelopingaresponseplan,theICMCoreSystemshallfavortheimplementationofpre-approvedresponseactions.

H DecisionSupport


RP-3.21

Whendevelopingresponseplans,theICMCoreSystemshallconsider,ifpossible,thehistoricalperformanceofpreviouslydevelopedcombinationsofresponseactionsforpastincidentsoreventsofsimilarmagnitudeoccurringatsimilarlocations.

L DecisionSupport


RP-3.22

TheICMCoreSystemshallonlydevelopresponseplansthatcanbeimplementedifrecommended.

M DecisionSupport


RP-3.23

TheICMCoreSystemshallincludeafunctiontodevelopmultiplepotentialresponseplansinresponsetoagivenincidentorevent.

H DecisionSupport

198. VerifytheICMCoreSystemshallbeabletodevelopmultipleresponseplansasaresponsetoanincidentorevent.

RP-3.25

TheICMEnvironmentshallinformtransitfieldsupervisorsassoonaspossibleoftheresponseactionsbeingconsideredtohelpthemmakedecisionsregardingpotentialtransitserviceadjustments.



8.3.1.5.6 EvaluationofIndividualResponsePlans

RP-3.26

TheICMCoreSystemshallevaluatealldevelopedvalidresponseplans.

H DecisionSupport

199. Verifythereisa“donothing”andeveryresponseplanisevaluated.

200. TheICMCoreSystem


78

TestREQID



shallalwaysconsidera“donothing”scenario(scenarioinwhichnoactionistaken)asoneofthepotentialresponseplanstobeevaluated.

201. TheICMCoreSystemshallevaluateallresponseplansdevelopedbyDecisionSupport.

RP-3.27

TheICMCoreSystemshallproduceatrafficforecastforeachresponseplanbeingevaluated.

H DecisionSupport

202. Verifypredictionisrunforeveryresponseplan.

203. Verifyeverypredictionusesestimationastheinitialstate.

204. Verifythatfutureandcurrentincidentsandevents,laneclosures&corridorassetstateareusedinpredictions.

205. Verifythatresponseplanimplementalltheplanelementssuchasintersectionsignalplanchanges,rampmeterchanges,road/lanechanges,communicationelements,manualinterventions.

206. Thetrafficforecastforeachresponseplanshallusethecorridor’scurrenttrafficstateasitsinitialstate.

207. Thetrafficforecastforeachresponseplanshalltakeintoaccountexpectedchangesintrafficpatternsfromknownroadclosures,otherincidentsorevents,etc.

208. Thetrafficforecastforeachresponseplanshallimplementalltheplanelements(intersectionsignalplanchanges,rampmeterchanges,road/lanechanges,communicationelements,manualinterventions)associatedwiththeresponseplanbeingevaluated.



79

TestREQID



RP-3.28

TheICMCoreSystemshallevaluatetheextenttowhicheachdevelopedresponseplanwouldimprove/deterioratecorridoroperationsovera“donothing”scenario.

H DecisionSupport

209. Verifystartingfrom“donothing“scenariowitheachresponseplanoverone-hourforecastsofcorridoroperations.

210. Verifyeachcomparisonisusingcurrenttimeascomparisonstartingpoint.

211. Verifypredictionswithvehicle-delay.

212. Verifyeachpredictiongeneratesamapforcongestion.

213. Verifycomparisonsofresponseplanpredictionsofvehicle-delaywithdonothingpredictionsofvehicle-delay.

214. Evaluationofthepotentialimpactsofindividualresponseplansoncorridoroperationsshallbeconductedoverone-hourforecastsofcorridoroperationsusingthecurrenttimeasastartingpoint.

215. Foreachevaluatedresponseplan,theICMCoreSystemshallprovidetheforecastedincrease/decreaseinvehicle-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.• Foreachevaluated

responseplan,theICMCoreSystemshallprovidetheforecastednominalincrease/decreaseinvehicle-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.


80

TestREQID



• Foreachevaluatedresponseplan,theICMCoreSystemshallprovidetheforecastedpercentincreaseinvehicle-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.

216. Foreachevaluatedresponseplan,theICMCoreSystemshallprovidetheforecastedincrease/decreaseinperson-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.• Foreachevaluated

responseplan,theICMCoreSystemshallprovidetheforecastednominalincrease/decreaseinperson-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.

• Foreachevaluatedresponseplan,theICMCoreSystemshallprovidetheforecastedpercentincreaseinperson-delayincurredwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.

217. Foreachevaluated


81

TestREQID



responseplan,theICMCoreSystemshallprovidetheforecastedincrease/decreaseintraveldemandresultingfromtheimplementationoftheresponseplan.• Foreachevaluated

responseplan,theICMCoreSystemshallprovidetheforecastedpercentincrease/decreaseinvehicle-milestraveledwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.

• Foreachevaluatedresponseplan,theICMCoreSystemshallprovidetheforecastedpercentincrease/decreaseinperson-milestraveledwithinthezoneofinfluenceoftheassociatedincidentoreventwhencomparedtothe“donothing”scenario.

• Foreachdevelopedresponseplan,theICMCoreSystemshallprovideamapshowingthelocationofcongestedroadwaysegmentsassociatedwiththeresponseplan.

RP-3.29

Foreachevaluatedresponseplan,theICMCoreSystemshallproduceaconfidenceindexreflectingthepotentialabilityoftheproposedactionstopositivelyaffectcorridoroperations.

M DecisionSupport



82

TestREQID



8.3.1.5.7 SelectionofRecommendedResponsePlan

RP-3.32

TheICMCoreSystemshallalwaysconsidera“donothing”scenarioasapotentialrecommendation.

H DecisionSupport

218. Verifyeveryincidentgeneratesa“donothing“responseplan.

Automationcandidate

RP-3.33

TheICMCoreSystemshallrankalldevelopedresponseplansbasedontheirabilitytoimprovecorridoroperationswithintheidentifiedzoneofinfluenceoftheincidentoreventthattriggeredtheresponseplanning.

H DecisionSupport

219. Responseplanrankingshallbemadeagainstthe“donothing”scenario

220. TheICMCoreSystemshallassignahigherrankingtoresponseplansreducingincurreddelayswithinthezoneofinfluenceoftheincidentorevent.

221. TheICMCoreSystemshallassignahigherrankingtoresponseplansincreasingthenumberofvehiclesortravelersabletotravelthroughthezoneofinfluenceoftheincidentorevent.

222. TheICMCoreSystemshallassignahigherrankingtoresponseplanswhereallinvolvedcorridorassetsareavailableandingoodoperatingcondition.

223. TheICMCoreSystemshallassignahigherrankingtoresponseplanshavingahigherconfidenceindex.

224. TheICMCoreSystemshallrankaresponseplanas“Unacceptable–JurisdictionalRestricted”ifimplementationoftheplanwouldviolateamandatoryjurisdictionalrestriction(suchasaschoolzonerestriction,atruckrestriction,etc.).

225. TheICMCoreSystemrankingshallrankaresponseplanas“Unacceptable”ifitsimplementationwouldresultinaworseoutcomethanthe“do


83

TestREQID



nothing”scenario.226. Verifyeachresponse

planiscomparedtothe“donothing”responseplan.

227. Verifytherulesexistforusingincurreddelayinresponseplanranking.

228. Verifytherulesexistforusingnumberofvehiclesortravelersabletotravelthroughthezoneofinfluenceinresponseplanranking.

229. Verifytherulesexistforusingcorridorassetsareavailableandingoodoperatingconditioninresponseplanranking.

230. Verifytherulesexistforusinghigherconfidenceindexinresponseplanranking.

231. Verifytherulesexistforusingmandatoryjurisdictionalrestriction(suchasaschoolzonerestriction,atruckrestriction,etc.inresponseplanranking.

232. Verifytherulesexistforrankingaresponseplanas“Unacceptable”forthoseworsethan“donothing”

233. Verifyalltherulesareimplementedcorrectly.

RP-3.34

TheICMCoreSystemshallonlyrecommendforimplementationresponseplanswithforecastedbenefitsexceedinggivenuser-definedthresholds.

H DecisionSupport

234. Verifyeachresponseplanforwhichtheforecastedtotalvehicle-delay/person-delayreductionoverthe“donothing”scenarioexceedsagivenuser-definedthreshold.

235. TheICMCoreSystemshallonlyrecommendforimplementationresponseplansforwhichtheforecastedtotaldelayreductionoverthe“donothing”scenarioexceedsagivenuser-definedthreshold.• TheICMCore


84

TestREQID



Systemshallonlyrecommendforimplementationresponseplansforwhichtheforecastedtotalvehicle-delayreductionoverthe“donothing”scenarioexceedsagivenuser-definedthreshold.

• TheICMCoreSystemshallonlyrecommendforimplementationresponseplansforwhichtheforecastedtotalperson-delayreductionoverthe“donothing”scenarioexceedsagivenuser-definedthreshold.

236. TheICMCoreSystemshallonlyrecommendforimplementationresponseplansforwhichthecorridorthroughputincreaseoverthe“donothing”scenarioexceedsagivenuser-definedthreshold.

RP-3.35

TheICMCoreSystemshallrecommendforimplementationtheresponseplanwiththehighestpositiveranking.

H DecisionSupport

237. Verify“donothing”scenariocomparisonwithotherresponseplansandresponseplanrecommendediswiththehighestpositiveranking.TheICMCoreSystemshallrecommendthe“donothing”scenarioshouldnoalternativeresponseplanwithapositiverankingremain.

RP-3.36

TheICMCoreSystemshallpermitmanualselectionofaresponseplanfromalistofrecommendedresponseplans.


238. Verifytheresponseplandeterminedtobebestsuitedcanbeselectedmanually.

239. TheICMCoreSystemshallpermitmanualselectionofresponseplans.

240. TheTMC/TCSoperator


85

TestREQID



shallbeabletomanuallyselectaresponseplanfromalistofrecommendedresponseplans.

241. TheICMCoreSystemshallnotallowselectionofaplanestimatedtohaveanegativeimpactoncorridoroperations.

242. TheICMCoreSystemshallnotallowselectionofaplanhavingalowconfidenceindex.

8.3.1.5.8 ResponsePlanReviewandApproval

RP-4.1

TheICMCoreSystemshallsubmitforapprovalalltheresponseplansthatarerecommendedforimplementationbytheDecisionSupportmodule.


243. Verifyresponseplanbestsuitedwillbeapprovedonacasetocasebasisbeforebeingdeployed.

244. Approvalofrecommendedresponseplansshallberequiredfromallagencieshavingaroletoplayintheimplementationoftheplanorbeingaffectedbyitsimplementation.

245. Foreachrecommendedresponseplan,theICMCoreSystemshallidentifytheindividualswithineachagencyresponsibleforreviewingandapprovingtheplan.

246. TheICMCoreSystemshallnotifyallindividualsresponsibleforreviewing/approvingresponseplanswhenanagencyhasapprovedorrejectedarecommendedplanthathasbeensubmittedforreview.

247. TheICMCoreSystemshallonlyconsiderasapprovedarecommendedplanthathasreceivedapprovalforitsimplementationfromallagenciesaffectedbyitsimplementation.

RP- Individualstaskedwith H Corridor 248. Verifyresponseplanbest


86

TestREQID



4.2 reviewingrecommendedresponseplansshallprovideareviewdecisionwithinaprescribedinterval.

Management suitedwillbeapproved/rejectedwithinaprescribedinterval.TheICMCoreSystemshallinformagencyrepresentativesoftheintervalallowedtomakeadecisionontheapproval/rejectionofasubmittedresponseplanwheneverthisintervalischanged.

RP-4.3

TheICMCoreSystemshallpermitminormodificationstorecommendedplanssubmittedforstakeholderapprovalbeforefinalplanapprovalisobtained.



RP-4.4

Followingapprovalofaresponseplan,theICMCoreSystemshallimmediatelynotifytheresponseplanimplementationfunctionsoftheneedtoimplementanewresponseplan.



8.3.1.5.9 PeriodicResponsePlanUpdates

RP-5.1

TheICMCoreSystemshallcontinuetomonitor,evaluate,andupdatetherecommendedresponseplan(e.g.,suggestchangestomessages,timingplans,meterrates,etc.)asanincident/eventunfolds.

H DecisionSupport

249. Verifyresponseplanbestsuitedwillbeupdated/approvedwithinaprescribedinterval.

RP-5.2

TheICMCoreSystemshallautomaticallyreassessevery5-15minutes(dependingonuserconfiguration)theadequacyofthepreviouslyrecommendedplanandpropose,ifnecessary,modificationstotheexistingplan.

H DecisionSupport

250. Verifyresponseplanbestsuitedwillbeupdated/approvedevery5-15minuteswithinaprescribedinterval.

RP-5.3

TheICMCoreSystemshallautomaticallyreassesstheadequacyofthepreviouslyrecommendedresponseplaniftherearechangestoimportantcharacteristicsoftheincidentoreventbeingrespondedto.

H DecisionSupport

251. Verifyresponseplanisreassessediftheincidentdurationismorethan15minutes.TheICMCoreSystemshallautomaticallyreassesstheadequacyofthepreviouslyrecommendedresponseplanifthereisa


87

TestREQID



changeinthenumberoflanesaffected.

252. TheICMCoreSystemshallautomaticallyreassesstheadequacyofthepreviouslyrecommendedresponseplaniftheexpecteddurationoftheincidentoreventbeingrespondedtochangesbymorethan15minutes.

RP-5.4

TheICMCoreSystemshallincludeafunctionforTMCandTCSoperatorstoproposechangestoanimplementedresponseplan.



RP-5.5

TheICMCoreSystemshallsubmitforreviewandapprovalallproposedmodificationstoanactiveresponseplan.



8.3.1.5.10 ResponseTermination

RP-6.1

Followingtheterminationofanincidentorevent,theICMCoreSystemshallcontinuetomonitor,evaluate,andupdatetheactiveresponseplanuntiltravelconditionswithinthecorridorhavereturnedtoanhistoricalaverage.

H DecisionSupport

253. Verifytrafficconditionsareassessedevery5minutesafterresponseplantermination.Followingtheclosureofanincidentorevent,theICMCoreSystemshallcontinueassessingtravelconditionswithinthecorridorevery5minutestodeterminewhethertravelconditionshavereturnedtohistoricalaverage.

254. Trafficconditionsshallbeassumedtohavereturnedtohistoricalaveragewhenobservedconditionsarewithintherangeofconditionstypicallyobservedforthegiventimeofweekandtimeofdayintheabsenceofincidentsorevents.

RP-6.2

Followingtheterminationofanincidentorevent,activeresponseplanningshallcontinueuntiltravel

H DecisionSupport

255. VerifyPostIncidentresponseplanisinplacepasttheterminationofresponseplan.Following


88

TestREQID



conditionswithinthecorridorhavereturnedtoahistoricalaverage.

theclosureofanincidentorevent,normalassetoperationsshallonlyberesumedoncetravelconditionswithinthecorridorhavereturnedtoanormalstateforthegiventimeofdayanddayofweek.

256. Followingtheidentificationofaneedtocontinueresponseplanningactivitiespasttheterminationanincidentorevent,theICMCoreSystemshallassignthe“Post-Incident/EventResponse”labeltotheactiveresponseplanuntilresponseactivitiescanformallybeterminated.

RP-6.3

TheICMCoreSystemshallreturncorridorassetstonormaloperationswhencorridoroperationshavereturnedtonormal.


257. Verifyonceclosureofanincidentallcontroldevicereturntonormaloperation.Upondeterminingthatcorridoroperationshavereturnedtonormalaftertheclosureofanincidentorevent,theICMCoreSystemshallinstructallcontroldevicesforwhichoperationhasbeenalteredduringtheincident/eventresponsetoreturntotheirdefinednormaloperationsforthetimeofdayanddayofweek.

258. Priortoterminatingresponseplanningactivities,theICMCoreSystemshallcheckthatallcontroldevicesforwhichoperationhasbeenalteredduringtheincident/eventresponsehaveeffectivelyreturnedtonormaloperation.

RP-6.4

Beforeterminatingaresponseactivity,theICMCoreSystemshallseekappropriateapprovalfromTMC/TCSoperatorsthatthe


259. Verifyapprovalisrequiredbeforeterminatinganyresponseplan.TMC/TCSoperatorsshallapprove


89

TestREQID



responseplanningactivitycanbeterminated.

terminationofresponseplans.

RP-6.6

TheICMCorridorManagershallhavetheauthoritytocommandtheICMCoreSystemtoterminatearesponseplanningactivity.



RP-6.7

TheICMCoreSystemshallinformrelevantsystemoperatorswhentrafficconditionswithinthecorridoraredeemedtohavereturnedtonormal.


260. Verifyrelevantoperatorsareinformedwhentrafficreturnstonormal.TheICMCoreSystemshallnotifytheCorridorManagerwhentrafficconditionswithinthecorridorhavereturnedtonormalstate.

261. TheICMCoreSystemshallnotifytheTMC/TCSoperatorsofallagenciesinvolvedintheimplementationofaresponseplanwhentrafficconditionswithinthecorridorhavereturnedtonormalandthatregularcorridoroperationsaretoresume.

262. TheICMCoreSystemshallnotifyfirstrespondersinvolvedintheimplementationofaresponseplanthattrafficconditionswithinthecorridorhavereturnedtonormalandthatregularcorridoroperationsaretoresume.

263. TheICMCoreSystemshallnotifytransitagenciesinvolvedintheimplementationofaresponseplanthattrafficconditionswithinthecorridorhavereturnedtonormalandthatregularcorridoroperationsaretoresume.

264. TheICMCoreSystemshallnotifyparkingoperatorsinvolvedintheimplementationofaresponseplanthattrafficconditionswithinthecorridorhavereturnedto


90

TestREQID



normalandthatregularcorridoroperationsaretoresume.

265. TheICMCoreSystemshallnotifyinformationprovidersinvolvedintheimplementationofaresponseplanthattrafficconditionswithinthecorridorhavereturnedtonormalandthatregularcorridoroperationsaretoresume.

RP-6.8

TheICMCoreSystemshallinformrelevantsystemoperatorswhenaresponseplanningactivityhasbeenterminated.


266. Verifyrelevantoperatorsareinformedwhenresponseplanisterminated.TheICMCoreSystemshallinformaffectedTMC/TCSoperatorswhenadecisionhasbeenmadetoterminatearesponseplanningactivity.

267. TheICMCoreSystemshallinformtheownerofeachfielddevice(e.g.,trafficsignalcontrollers,fixedCMS,etc.)usedintheimplementationofaresponseplanwhenadecisionhasbeenmadetoreturnthedevicetonormaloperation.

268. TheICMCoreSystemshallinformfieldsupervisorsofaffectedtransitagencieswhenadecisionhasbeenmadetoterminatearesponseplan.

269. TheICMCoreSystemshallinformaffectedfirstresponderswhenadecisionhasbeenmadetoterminatearesponseplanningactivity.

270. TheICMCoreSystemshallinformaffectedparkingoperatorswhenadecisionhasbeenmadetoterminatearesponseplanningactivity.

271. TheICMCoreSystemshallinformaffectedinformationproviders


91

TestREQID



whenadecisionhasbeenmadetoterminatearesponseplanningactivity.

272. TheICMCoreSystemshallinformallsystemstakeholderswhenallresponseplanningactivitieshaveofficiallyconcluded.

8.3.1.5.11 ResponsePlanningArchiving

RP-7.1

TheICMCoreSystemshalllogallresponseplanningactivities.

M Testingtobedefinedwhentherequirementisaddressed.

RP-7.2

TheICMCoreSystemshallarchivedevelopedresponseplans.


8.3.1.5.12 ResponsePlanningPerformanceAssessment

RP-8.1

TheICMCoreSystemshallgeneratearesponseplanwithin5minutesoftheverificationofanactiveincidentorevent.

H 273. Verifyresponseplanrankingbetween1to10isgeneratedwithin5minutesofverificationofanactiveincident.

RP-8.2

Thesimulationsoftwareshallbeabletoevaluatewithina5-minuteintervaltheimpactsofatleastthreecandidateresponseplansoveratleastthenextprojectedhourofoperation.

H 274. Verifyatleastthreeresponseplancomparisonswithprojectionforthenexthourisgeneratedwithin5minutesofverificationofanactiveincident.

8.3.1.6 ResponsePlanImplementation

8.3.1.6.1 ResponsePlanFieldImplementation

PI-2.1 Uponreceivinganewapprovedresponseplan,theICMCoreSystemshalldeterminetheorderandpropertimeatwhichcontrolactionsshouldbesenttoindividualcontrolelements.

H DecisionSupport

275. VerifytheICMCoreSystemshalldeterminetheorderandtimeatwhichcontrolactionswouldbesenttoindividualcontrolelements.

PI-2.2 TheICMCoreSystemshallsendresponseplaninstructionstoindividualcorridorassets.


276. Verifytheinstructionsaresenttotheindividualtrafficcontroldevicesinvolvedintheimplementationofthe


92

TestREQID



plansuchas• Individualtraffic

signalcontrollersspecifyingwhichtimingplantouseatthecorrespondingintersection.

• Individualrampmetercontrollersspecifyingwhichmeteringalgorithm/ratetouseatthecorrespondingon-ramporfreeway-to-freewayconnector.

277. Verifytheinstructions/commandsaresenttothetravelerinformationdevicesinvolvedintheimplementationofaresponseplansuchas:• IndividualfixedCMS

devicesspecifyingwhatmessageistobepostedonthedevice.

• IndividualportableCMSdeviceswithremotecommunicationcapabilityspecifyingwhatmessageistobepostedonthedevice.

• Individualextinguishabletrailblazersignsalongtheselecteddetour(s).

278. VerifytheICMCoreSystemshallsendinstructionstoindividualtrafficcontroldevicesinvolvedintheimplementationoftheplan.• TheICMCore

Systemshallsendcommandstoindividualtrafficsignalcontrollersspecifyingwhichtimingplantouseatthecorresponding


93

TestREQID



intersection.• TheICMCore

Systemshallsendcommandstoindividualrampmetercontrollersspecifyingwhichmeteringalgorithm/ratetouseatthecorrespondingon-ramporfreeway-to-freewayconnector.

279. VerifytheICMCoreSystemshallsendinstructionstotravelerinformationdevicesinvolvedintheimplementationofaresponseplan.• TheICMCore

SystemshallsendcommandstoindividualfixedCMSdevicesspecifyingwhatmessageistobepostedonthedevice.

• TheICMCoreSystemshallsendcommandstoindividualportableCMSdeviceswithremotecommunicationcapabilityspecifyingwhatmessageistobepostedonthedevice.

• TheICMCoreSystemshallsendactivationcommandstoindividualextinguishabletrailblazersignsalongtheselecteddetour(s).

280. TheICMCoreSystemshallsenddeploymentrequeststoagencypersonnelhavingaroletoplayinimplementingtheplan.• Stakeholdersshall


94

TestREQID



permittheCoreICMSystemtocontactdesignatedagencypersonnelwithrequestsforperformingpreapprovedactions.

• TheICMCoreSystemshallsendtaskrequeststoagencystaffresponsibleforthedeploymentofportableCMSs,specifyinghowmanysignsaretobedeployedandwhere.

• TheICMCoreSystemshallsenddeploymentrequeststofieldoperationstafffromeachparticipatingagencyspecifyingwheretheyshoulddeployandwhattaskistobeaccomplished.

• TheICMCoreSystemshallsendtrafficmanagementrequeststofirstrespondersfromeachparticipatingagency.

PI-2.3 TheICMCoreSystemshallverify,totheextentpossible,thatfieldassetshavethecorrectplancomponents.


281. VerifythetrafficcontroldevicesinvolvedintheimplementationofaresponseplanshallacknowledgereceivinginstructionssentbytheICMCoreSystem.• Trafficsignal

controllersshallacknowledgereceivinginstructionsonwhentostartaspecificsignalplan.

• Rampcontrollersshallacknowledgereceivinginstructionson


95

TestREQID



whentostartaparticularrampmeteringplan.

282. VerifythetravelerinformationdevicesinvolvedintheimplementationofaresponseplanshallacknowledgereceivinginstructionssentbytheICMCoreSystem.• FixedCMSdevices

shallacknowledgereceivinginstructionsonwhentodisplayaparticularmessage.

• PortableCMSdeviceswithremotecommunicationcapabilityshallacknowledgereceivinginstructionsonwhentodisplayaparticularmessage.

• Extinguishabletrailblazersignsshallacknowledgereceivingactivationinstructions.

• HARsystemsshallacknowledgereceivinginstructionsonwhentobroadcastaparticularmessage.

PI-2.4 AssetsfailingtoacknowledgeinatimelymannerreceiptofinstructionsfromtheICMCoreSystemshall,totheextentpossible,becheckedtodeterminewhethertheyhavereceivedtheinformation.


283. VerifytravelerinformationdevicesinvolvedintheimplementationofaresponseplanfailingtoacknowledgeshallbecheckediftheyreceivedinstructionssentbytheICMCoresystem.

284. Trafficcontroldevicesfailingtoacknowledgewithinoneminutethereceiptofresponseplanimplementationinstructionsshallbecheckedtoseeiftheyhavereceivedtheinstructions.


96

TestREQID



• Intheabsenceoftimelyacknowledgment,rampcontrollersshallbecheckedtoensurethatthemeteringchangeinformationsentbytheICMCoreSystemhasbeenreceivedbythedevice.

• Intheabsenceoftimelyacknowledgment,trafficsignalcontrollersshallbecheckedtoensurethatthetimingplanchangeinformationsentbytheICMCoreSystemhasbeenreceivedbythedevice.

285. Travelerinformationdevicesfailingtoacknowledgewithinoneminutereceiptofmessaginginstructionsshallbecheckedtoseeiftheyhavereceivedtheinstructions.• Intheabsenceof

timelyacknowledgment,fixedCMSsignsshallbecheckedtoensurethatthemessaginginformationsentbytheICMCoreSystemhasbeenreceived.

• Intheabsenceoftimelyacknowledgment,portableCMSsignsshallbecheckedtoensurethatthemessaginginformationsentbytheICMCoreSystemhasbeenreceived.

• Intheabsenceof


97

TestREQID



timelyacknowledgment,extinguishabletrailblazersignsshallbecheckedtoensurethattheactivationinformationsentbytheICMCoreSystemhasbeenreceived.

• Intheabsenceoftimelyacknowledgment,HARsystemsshallbecheckedtoensurethatthemessaginginformationsentbytheICMCoreSystemhasbeenreceived.

PI-2.5 TheICMCoreSystemshallberesponsibleforperforminginitialchecksoninstructionreceiptacknowledgmentsfromcorridorassets.


286. Totheextentpossible,theICMCoreSystemshallprovideanautomatedwaytocheckwhetherinstructionreceiptacknowledgmentshavebeenreceivedfromcorridorassets.

287. Humanassetsshallonlybeinvolvedinverifyinginstructionreceiptwhereautomationisnotpossibleorafterautomationverificationhasfailed.

288. Assetacknowledgmentsandlackofacknowledgmentsshallbetrackedinelectronicformat.

289. Assetchecksandresultsshallbetrackedinelectronicformat.

290. Verifyinstructionreceiptacknowledgmentshavebeenreceivedfromcorridorassets.

291. Verifyhumanassetsshallonlybeinvolvedinverifyinginstructionreceiptwhereautomationisnot


98

TestREQID



possible.292. Verifyasset

acknowledgmentsandlackofacknowledgmentsaretrackedinelectronicformat.

293. Verifyassetchecksandresultsaretrackedinelectronicformat.

8.3.1.6.2 InformationDisseminationtoTravelers

PI-3.1 TheICMCoreSystemshallinformcorridortravelersofincidents,unscheduledevents,andplannedeventsoccurringwithinthecorridor.


294. TheICMCoreSystemshallinformtravelersandfleetoperatorsofroadwayincidents,unscheduledevents,andplannedeventsoccurringalongcorridorfreewaysandarterialsthatmaybeusedasdetours.

295. TheICMCoreSystemshallinformtravelersandfleetoperatorsofplannedroadwayclosuresoccurringalongcorridorfreewaysandarterialsthatmaybeusedasdetours.

296. TheICMCoreSystemshallinformtravelersandfleetoperatorsofunscheduledroadwayclosuresduetomaintenanceorotherreasonsoccurringalongcorridorfreewaysandarterialsthatmaybeusedasdetours.

297. Foreachincidentorevent,theICMCoreSystemshallprovidetravelersandfleetoperatorswithanassessmentoftravelconditionswithinthecorridor.• Foreachincidentor

event,theICMCoreSystemshallprovidetravelersandfleetoperatorswithestimatesofcurrenttraveltimesortraveldelayswithin


99

TestREQID



thecorridor.• Foreachincidentor

event,theICMCoreSystemshallprovidetravelersandfleetoperatorswithestimatesofprojectedtraveltimesortraveldelayswithinthecorridorat15-minuteintervals.

298. VerifyICMCoreSysteminformstravelersandfleetoperatorsofroadwayincidents,unscheduledevents,andplannedeventsoccurringalongcorridorfreewaysandarterialsthatmaybeusedasdetours.

299. VerifyICMCoreSysteminformstravelersandfleetoperatorsofplannedroadwayclosuresoccurringalongcorridorfreewaysandarterialsthatmaybeusedasdetours.

300. VerifyICMCoreSysteminformstravelersandfleetoperatorsofunscheduledroadwayclosures.

301. VerifyforeachincidentICMCoreSystemprovidestravelersandfleetoperatorswithanassessmentoftravelconditions.• Estimatesofcurrent

traveltimesortraveldelayswithinthecorridor.

• ICMCoreSystemshallprovidetravelersandfleetoperatorswithestimatesofprojectedtraveltimesortraveldelayswithinthecorridorat15-minuteintervals.

PI-3.2 TheICMCoreSystemshall H Corridor 302. VerifyICMCoreSystem


100

TestREQID



informcorridortravelers,bymultiplechannels,ofrecommendeddetoursaroundincidents.

Management willdisplaydetourinformationonrelevantCMS:TheICMCoreSystemshalldisplayinformationaboutrecommendeddetour(s)onrelevantCMSswithinandaroundthecorridor.

303. TheICMCoreSystemshalldisplay,whenneeded,detourinformationonfixedCMSsoperatedbyCaltransalongtheI-210freeway.

304. TheICMCoreSystemshalldisplay,whenneeded,detourinformationonfixedCMSsoperatedbyCaltransonrelevantregionalfreeways.

305. TheICMCoreSystemshalldisplay,whenneeded,relevantdetourinformationonfixedCMSsoperatedalongcorridorarterialsbylocalagencies.

306. TheICMCoreSystemshalldisplay,whenneeded,relevantdetourinformationonmobileCMSsoperatedbylocalagencies.

307. TheICMCoreSystemshalldisplay,whenneeded,relevantdetourinformationonextinguishabletrailblazersignsoperatedalongcorridorarterialsbylocalagencies.

308. TheICMCoreSystemshallsendinformationaboutrecommendeddetour(s)totheregional511System.

309. TheICMCoreSystemshallsendinformationaboutrecommendeddetour(s)toparticipatingthird-partyinformationproviders.


101

TestREQID



310. TheICMCoreSystemshallmakedetourinformationavailabletonavigationapplicationproviders(Waze,Google,etc.).

PI-3.3 TheICMCoreSystemshallsendmode-specificdetourinformationtocorridortravelers.


311. VerifyICMCoreSystemwillsendmode-specificdetourinformationtocorridortravelers.

312. TheICMCoreSystemshallsendsuitabledetoursaroundincidentsandeventstopassengercars.

313. TheICMCoreSystemshallsendsuitabledetoursaroundincidentsandeventstotruckfleetdispatchersand/ortruckoperators.

314. TheICMCoreSystemshallsendsuitabledetoursaroundincidentsandeventstotransitbusfieldsupervisorsand/orbusdrivers.

PI-3.4 TheICMCoreSystemshallguidevehicleoperatorsalongrecommendeddetours.


315. VerifyICMCoreSystemwillguidedetouringtrafficalongrecommendeddetours,usingvariouschannelsthatmayincludefixedCMSs,mobileCMSs,fixedextinguishabletrailblazersigns,fixedstaticsigns,hands-freemobileapplications,and/orradiobroadcasts.

PI-3.5 TheICMEnvironmentshallsendcorridortravelersinformationonalternatetransportationmodes.



PI-3.6 TheICMEnvironmentshallprovidetravelersinformationaboutincidentsandeventsoccurringwithinthecorridorinaconsistentformat.


316. VerifyICMenvironmentwillprovidetravelersinformationaboutincidentsandeventsoccurringwithinthecorridor.

8.3.1.6.3 ImplementationOverride

PI-4.1 Priortoinitiatingtheimplementationofan

M DecisionSupport



102

TestREQID



approvedresponseplan,theICMCoreSystemshallcheckwhetherchangesincorridoroperationsmaywarrantthedevelopmentofanewresponseplan.

PI-4.2 TheICMCoreSystemshallinitiatethedevelopmentofanewresponseplanifchangesincorridoroperationsrenderthecurrentlyapprovedresponseplanobsoletebeforeitsimplementation.

L DecisionSupport


8.3.1.6.4 ResponsePlanImplementationTracking

PI-6.1 TheICMCoreSystemshalltracktheimplementationprogressofapprovedresponseplans.


317. Verifyimplementationprogressofapprovedresponseplansistracked.

318. Verifyeachrecommendedactionimplementationislogged.

319. Verifyanyfailuretoimplementachangerequestislogged.

PI-6.2 Uponterminationofanincidentoreventresponseplan,theICMCoreSystemshallensurethatallassetsarereturnedtothestateofoperationthatwouldhavebeenineffecthadanincidentoreventnotoccurred.


320. Verifyuponterminationofanincidentoreventresponseplanallassetsarereturnedtostateofoperation.

PI-6.3 TheICMCoreSystemshallinformallTMC/TCSoperatorsandtransitfieldsupervisorswhetherarecommendedresponsehasbeensuccessfullyimplemented.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.321. VerifyICMcoreshall

informallTMC/TCSoperatorsandtransitfieldsupervisorswhetherarecommendedresponsehasbeenimplemented,ICMCoreSystemshallinformTMC/TCSoperatorsandtransitfieldsupervisorswhenaresponseplanhasbeensuccessfullyimplementedinitsentirety.



103

TestREQID



shallinformindividualTMC/TCSoperatorsandtransitfieldsupervisorsofallimplementedchangeswithintheirjurisdiction.

323. TheICMCoreSystemshallinformtheCorridorManagerandrelevantTMCoperatorsandtransitfieldsupervisorsifarecommendedresponseplancannotbeimplemented.

324. Inthecaseofimplementationfailure,theICMCoreSystemshallindicatewhyarecommendedresponseplancouldnotbeimplemented.

PI-6.4 TheICMCoreSystemshallinformallTMC/TCSoperatorsandtransitfieldsupervisorswhenallcorridorassetshavebeenreturnedtonormaloperations.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.325. VerifyICMCoreSystem

informsallTMC/TCSoperatorsandtransitfieldsupervisorswhenallcorridorassetshavebeenreturnedtonormaloperations.

8.3.1.6.5 ResponsePlanningArchiving

PI-7.1 TheICMCoreSystemshalllogallcontrolactivitiesrelatedtotheimplementationofanapprovedresponseplan.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.326. Verifyloggingofall

controlactivitiesrelatedtoimplementationofanapprovedresponseplan.

PI-7.2 TheICMCoreSystemshallarchiveimplementedresponseplans.

H DataHub 327. DataisarchivedtoAWSglacierafter90days.

8.3.1.7 DataManagement

8.3.1.7.1 DataQuality

DM-1.1

TheCorridorTechnicalManagerandCorridorDataAnalystshalldevelopadata




104

TestREQID



qualitymanagementprogramfortheICMEnvironment.

DM-1.2

FortheICMEnvironment,dataqualityrequirementsshallbespecifiedforalldatasourcesandsystemdataelements.



DM-1.3

Dataqualityshallbemaintained.



8.3.1.7.2 DataManagementNeeds

8.3.1.7.2.1 GeographicandInstitutionalData

DM-2.1

DataManagementshallstoreandprovideaccesstoinformationcharacterizingthecorridor’sinstitutionalenvironment.


8.3.1.7.2.2 AssetInventory

DM-2.2

DataManagementshallstoreorprovideaccesstoinformationcharacterizingfreewaysegments.

H DataHub 328. Foreachfreewaysegment,DataManagementshallstoreorprovideaccesstothefollowinginformation:

Generalcharacteristics:• Numberofgeneral-

purposetrafficlanes• Postedspeedlimit• Upstreammainline

freewaysegments,on-ramps,andconnectorsfeedingtraffictothesegment

• Downstreammainlinefreewaysegments,off-ramps,andconnectorsreceivingtrafficfromthesegment

• Leftandrightshoulderwidths

• Medianbarrierheight,ifany

• HOVtreatment• NumberofHOV

lanes• TypeofHOV

ConnecttoRoadNetworkInformationserviceendpoint


105

TestREQID



restriction(2+or3+occupants)

• PeriodsduringwhichHOVrestrictionisineffect

• Restrictions:o Vehicleheight

clearanceunderbridgesorstructures

o Truckuserestrictions

329. Foreachon-ramporfreeway-to-freewayconnector,DataManagementshallstoreorprovideaccesstothefollowinginformation:Generalcharacteristics:• Numberofgeneral-

purposetrafficlanes• Postedspeedlimit• Roadwaylink(s)

feedingtraffictotheramp

• Mainlinefreewaysegment(s)receivingtrafficfromtheramp

• HOVtreatment:• NumberofHOV

lanes• TypeofHOV

restriction(2+or3+occupants)

• PeriodsduringwhichHOVrestrictionisineffect

• Rampmetering:• Rampmeterpresent• Typeoframp

metering(fixed,adaptive,etc.)

• HOVvehiclesallowedbypassingtherampmeter



o Truckuserestriction


106

TestREQID



330. Foreachoff-ramp,DataManagementshallstoreorprovideaccesstothefollowinginformation:Generalcharacteristics:• Numberofgeneral-

purposetrafficlanes• Postedspeedlimit• Freewaysegment(s)

feedingtraffictotheoff-ramp

• Roadwaysegment(s)receivingleft-turning,thru,andright-turningtrafficfromtheoff-ramp



o Truckuserestriction

DM-2.3

DataManagementshallstoreorprovideaccesstoinformationcharacterizingarterialsegments.

H DataHub 331. Foreacharterialsegment,DataManagementshallstoreorprovideaccesstothefollowinginformation:Generalcharacteristics:• Numberofthrough

trafficlanes• Postedspeedlimit• Roadwaysegment(s)

feedingtraffictothearterialsegment

• Roadwaysegmentsreceivingleft-turning,thruandright-turningtrafficfromthearterialsegment

• Presenceofhardmedianbarrier

• Restrictions:o Left-turn

restrictionso Vehicleheight


o Truckuserestrictions

o Parkingrestrictions

ConnecttoRoadNetworkInformationserviceendpoint

DM- DataManagementshallstore M DataHub Testingtobedefinedwhen Connectto


107

TestREQID



2.4 orprovideaccesstoinformationcharacterizingrelevanttransitservicesoperatedwithinthecorridor(raillines,transitroutes,etc.).

therequirementisaddressed.

TransitRoutesandTransitStateendpoint

DM-2.5

DataManagementshallstoreorprovideaccesstoinformationcharacterizingpark-and-ridefacilitiesoperatedwithinthecorridor.


DM-2.6

DataManagementshallstoreorprovideaccesstoinformationcharacterizingdevicesusedtomonitortraffic.

H DataHub 332. DataManagementshallmaintainaninventoryofdevicesusedtocollecttrafficflowdata.

333. DataManagementshallstoreorprovideaccesstothefollowinginformationforeachdeviceusedtocollecttrafficflowdata:• Sensorlocation• Sensortype• Deviceowner• Sensoridentification

number• Reportingsystemto

whichthesensorisconnected

• Movementscoveredbythesensor(through,left-turn,right-turn,combinations)

• DataManagementshallmaintainaninventoryofdevicesusedtomonitortraveltimes

334. DataManagementshallstoreorprovideaccesstothefollowinginformationforeachdeviceusedtocollecttraveltimes:• Sensorlocation• Sensortype• Deviceowner• Sensoridentification

number• Reportingsystemto

whichthesensorisconnected

ConnecttoTravelTimeDetectorInventory/maintenance&TraveltimeDetectorInventory

DM-2.7

DataManagementshallstoreorprovideaccesstoinformationcharacterizingdevicesusedtomonitorweatherconditions.



108

TestREQID



DM-2.8

DataManagementshallstoreorprovideaccesstoinformationcharacterizingsignalizedintersections.

H DataHub 335. DataManagementshallmaintainaninventoryofsignalizedintersectionsunderICMmanagement.

336. ForeachsignalizedintersectionunderICMmanagement,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Agency/Agencies

owningtheintersection

• Agency/Agenciesresponsibleforoperationandmaintenanceofintersection

• Typeofsignalcontrollerused

• Controllerfirmware• Numberof

approachestotheintersection

337. ForeachapproachtoasignalizedintersectionunderICMmanagement,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Laneassignments

(numberofleft,thru,rightlanes)

• Distancetoupstreamintersection

• Postedspeedlimit• Lengthofleft-turn

bay,ifany• Lengthofright-turn

bay,ifany

Connecttointersectionsignalinventoryendpoint

DM-2.9

DataManagementshallstoreorprovideaccesstoinformationcharacterizingrampmeteringoperationswithinthecorridor.

H DataHub 338. DataManagementshallmaintainaninventoryoffreewayrampsandfreeway-to-freewayconnectorsequippedwithrampmetersunderICMmanagement.

339. Foreachmeteredon-ramporfreeway-to-freewayconnectorunderICMmanagement,DataManagementshallstoreorprovideaccesstothe

ConnecttoRampmeterinventory


109

TestREQID



followinginformation:• Locationoframp

meteralongtheon-ramporconnector


• Rampmeteringprograminstalledincontroller

• Distanceofqueuesensorsfromrampmeteringstopline

DM-2.10

DataManagementshallstoreorprovideaccesstoinformationcharacterizingdevicesthatmaybeusedtodisseminateinformationtotravelers.

H DataHub 340. DataManagementshallmaintainaninventoryoffixedCMSdeviceswithinandoutsidetheICMcorridorthatmaybeusedtodisseminateinformationtotravelers.

341. DataManagementshallmaintainaninventoryofportableCMSdevicesthatmaybeusedtodisseminateinformationtotravelers.

342. DataManagementshallmaintainaninventoryofextinguishabletrailblazersignsthatmaybeusedtodisseminateinformationtotravelers.

343. ForeachfixedCMSthatmaybeusedbytheICMEnvironment,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Locationofdevice• Deviceoperator• Numberofdisplay

lines• Totalnumberof

charactersthatcanbedisplayedperline

344. ForeachportableCMSthatmaybeusedbytheICMEnvironment,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Deviceoperator• Locationwhere

deviceisnormallystoredwhennotused

ConnecttoCMSInventory(trailblazerinventorycanbeverifiedatthisendpoint),HARinventory


110

TestREQID



• Numberofdisplaylines

• Totalnumberofcharactersthatcanbedisplayedperline

345. ForeachextinguishabletrailblazersignthatmaybeusedbytheICMEnvironment,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Locationofdevice• Deviceoperator• Message(s)

displayedbydevicewhenlit

346. ForeachHARthatmaybeusedbytheICMEnvironment,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Stationlocation• Broadcastfrequency• Stationoperator

8.3.1.7.2.3 AssetCapabilities(BackgroundOperationalData)

DM-2.11

DataManagementshallstoreorprovideaccesstoinformationcharacterizingtypicaltrafficsignaloperationsatrelevantintersectionswithintheICMcorridor.

H DataHub 347. ForeachsignalizedintersectionunderICMmanagement,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Agencyresponsible

fortheoperationoftheintersection

• Agencyresponsibleformaintenance

• Trafficcontrolsystemmanagingtheintersection


• Numberofdefinedtimingplansavailable

348. Foreachsignaltimingplan,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Typicaltimesof

operation

Connecttointersectionsignalcontrolscheduleendpoint


111

TestREQID



• Cyclelength• Signaloffset• Offsetreference

pointwithincycle• Phasesequence• Phasedurations

349. Foreachapproachtoasignalizedintersection,DataManagementshallstoreorprovideaccesstothefollowinginformation:Prohibitedrightturnonredmovements

DM-2.12

DataManagementshallstoreorprovideaccesstoinformationcharacterizingtypicalrampmeteringoperationswithintheICMcorridor.

H DataHub 350. Foreachmeteredon-ramporfreeway-to-freewayconnector,DataManagementshallstoreorprovideaccesstothefollowinginformation:• Minimumand

maximumrampmeteringratesallowed

• Meteringratetable• Meteringalgorithm

used

ConnecttoRampmeterinventoryendpointandPlans

DM-2.13

DataManagementshallstoreorprovideaccesstoinformationidentifyingtypicaldetourroutesthatshouldbeconsideredwhenrespondingtoincidents.

H DataHub 351. DataManagementshallstoreorprovideaccesstoinformationidentifyingtypicalpreferreddetourroutesthatshouldbeconsideredforpassengercars.

352. DataManagementshallstoreorprovideaccesstoinformationidentifyingtypicalpreferreddetourroutesthatshouldbeconsideredforbuses.

ConnecttoRouteinventoryendpointTestingtobedefinedwhentherequirementisaddressed


8.3.1.7.2.4 AssetStateData

DM-2.14

DataManagementshallreceivereal-timedatacharacterizingtheoperationalstatusofdevicessupportingICMoperations.

H DataHub 353. Foreachtrafficsensor,DataManagementshallreceiveevery5minutesorlessthefollowingdevicestatusdata:• Whetherthedevice

isoperatingnormally

• Anyerrormessagesproducedbythedeviceoritsassociated

ConnecttotheFreewayDetectorstateendpoint


112

TestREQID



managementsystem

Testingtobedefinedwhentherequirementisaddressed:354. Foreachtraveltime

measurementdevice,DataManagementshallreceiveevery5minutesorlessthefollowingstatusdata:• Whetherthedevice

isoperatingnormally

• Anyerrormessagesproducedbythedeviceoritsassociatedmanagementsystem

355. Foreachsignalizedintersection,DataManagementshallreceiveevery5minutesorlessthefollowingdevicestatusdata:• Whetherthesignal

isoperatingnormally

• Timingplaninoperation

• Anyerrormessagesproducedbythedeviceoritsassociatedmanagementsystem

356. Foreachrampmeter,DataManagementshallreceiveevery5minutesorlessthefollowingdevicestatusdata:• Whethertheramp

meterisoperating• Anyerrormessages

producedbythedeviceorassociatedmanagementsystem

• Meteringratecurrentlyinoperation

357. ForeachfixedCMS,DataManagementshall

ConnecttotheTravelTimeDetectorInventoryendpointConnecttotheIntersectionDetectorState/IntersectionsignalStateendpointtocheckthedevicestatusConnecttotheRampmeterstateendpointConnecttotheCMSstateendpoint


113

TestREQID



receiveevery5minutesorlessthefollowingdevicestatusdata:• Whetherthesignis

active• Whetherthesignis

operatingnormally• Anyerrormessages

producedbythedeviceoritsassociatedmanagementsystem

358. Foreachextinguishabletrailblazersign,DataManagementshallreceiveevery5minutesorlessthefollowingdevicestatusdata:• Whetherthesignis

active• Whetherthesignis

operatingnormally• Anyerrormessages

producedbythedeviceoritsassociatedmanagementsystem

Testingtobedefinedwhentherequirementisaddressed:359. Foreachweather

monitoringstationprovidingdatatotheICMEnvironment,DataManagementshallreceiveevery15minutesorlessthefollowingstatusdata:• Whetherthe

weatherstationisoperational

• Whetherthemonitoringstationisoperatingnormally

• Anyerrormessagesproducedbythedeviceoritsassociateddatacollectionsystem

360. DataManagementshallreceiveevery5minutesthedataindicating

ConnecttotheCMSstateendpointConnecttotheEnvironment-alDetectorInventoryendpointevery15mins


114

TestREQID



whetherICMEnvironmentcomponentsareoperatingnormallyornot.

ConnecttotheDatahub,DSS,CMS,centerverification(cities/counties)endpoint

8.3.1.7.2.5 AssetReal-TimeData

DM-2.15

DataManagementshallreceivereal-timetrafficdatafromindividualtrafficsensorsoperatingwithinthecorridor.

H DataHub 361. DataManagementshallreceiveevery1minuteorlessthefollowingdatafromeachtrafficsensorlocatedongeneral-purposeorHOVfreewaylanes:• Recordedvehicle

counts• Measuredsensor

occupancy• Estimated/measur-

edspeed362. DataManagementshall

receiveevery1minuteorlessthefollowingreal-timedatafromeachtrafficsensorlocatedonfreewayon-ramps,off-ramps,andfreeway-to-freewayconnectors:• Recordedvehicle

counts• Measuredsensor

occupancy363. DataManagementshall

receiveevery5-15minutesorless(detailstobedeterminedatdesign)thefollowingreal-timedatafromindividualtrafficsensorslocatedalongarterialsegments:• Recordedvehicle

counts364. Basedondatareceived

fromtrafficsensorslocatedonmainlinegeneral-purposeorHOVlanes,DataManagementshallcalculate,if

ConnecttotheFreewayDetectorDataendpoint&Rampdetectordataendpointevery30secsConnecttotheIntersectiondetectordataendpointConnecttotheIntersectiondetectordataendpointConnecttotheFreewaydetectordataendpoint


115

TestREQID



necessary,thefollowingtrafficstatisticsforeachsuccessive5-minuteintervalforeachsensor:• Averageobserved

vehicleflow(invehiclesperhour)

• Averageestimatedflowdensity(invehiclespermile)

• Averageobservedtrafficspeed(inmilesperhour)

365. Basedondatareceivedfromtrafficsensorslocatedonfreewayon-rampsandoff-ramps,aswellasfreeway-to-freewayconnectors,DataManagementshallcalculateifnecessarythefollowingtrafficstatisticsforeachsuccessive5-minuteintervalforeachsensor:• Averageobserved




366. Basedondatareceivedfromtrafficsensorslocatedoncorridorarterials,DataManagementshallcalculateifnecessarythefollowingtrafficstatisticsforeachsuccessive5-minuteintervalforeachsensor:• Averageobserved




ConnecttotheRampdetectordataendpointConnecttotheIntersectiondetectordataendpoint

DM-2.16

DataManagementshallreceivereal-timedatafrom

M DataHub 367. DataManagementshallreceiveevery5minutes

Connecttothetravel


116

TestREQID



traveltimemeasurementsystemswithinthecorridor.

orlesstraveltimemeasurementsfromBluetoothtraveltimemeasurementsystemsinoperationwithinthecorridor.

368. DataManagementshallreceiveevery5minutesorlesstraveltimemeasurementsfromPasadena’sSMARTsysteminoperationalongOrangeGroveBoulevard.

timedetectorinventoryendpointevery5mins

DM-2.17

DataManagementshallreceivereal-timedatafromparticipatingprobevehiclemonitoringsystemscoveringtheICMcorridor.


DM-2.18

DataManagementshallreceivereal-timedatacharacterizingincidentsandeventsoccurringwithinthecorridor.

H DataHub WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.369. DataManagementshall

receiveevery5minutesorlessinformationupdatesabouttrafficincidentsthathavebeenidentifiedtohaveoccurred.

370. DataManagementshallreceiveevery5minutesorlessinformationupdatesaboutactiveeventsaffectingcorridoroperations.

371. DataManagementshallreceiveevery5minutesorlessinformationupdatesaboutunusualtrafficcongestionpatternsthatmayhavebeendetectedbytheICMEnvironmentandCoreSystem.

WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.Testingtobedefinedwhentherequirementisaddressed.372. DataManagementshall

receiveevery5minutesorlessinformationupdatesaboutplannedlaneclosuresscheduled

ConnecttotheLCSschedule


117

TestREQID



tooccurduringthecurrentoperationday.

endpointfortheincidentsandevents

DM-2.19

DataManagementshallreceivereal-timedatacharacterizingtheoperationalperformanceofrelevanttransitserviceswithinthecorridor.


DM-2.21

DataManagementshallreceivereal-timedatacharacterizingobservedrampmeteringoperationswithinthecorridor.

H DataHub 373. Foreachrampmeter,DataManagementshallreceivethefollowinginformationeachtimeachangeinmeteringrateisimplementedwithinoneminuteofthetimeofthechange:• Timerampmetering

ratewaschanged• Meteringratethat

wasactivated

ConnecttotheRampMeterStateendpointforverifyingtherelevantdata

DM-2.22

DataManagementshallreceivereal-timedatacharacterizingthecurrentoperationalstatusoftrafficsignalsinoperationwithinthecorridor.

H DataHub 374. ForeachsignalizedintersectionunderICMsurveillance,DataManagementshallreceiveattheendofeachsignalcyclethefollowingoperationalinformation:• Signaltimingplanin

effect• Starttimeofsignal

cycle• Signalcyclelength• Signalcoordination

status• Signaloffset• Offsetreference

phase

ConnecttotheIntersectionSignalStateendpoint

DM-2.23

DataManagementshallstoreinformationcharacterizingthetypicalrangeofvaluesassociatedwiththedatareceived.


8.3.1.7.2.6 ResponsePlanData


118

TestREQID



DM-2.24

DataManagementshallmaintainanupdatedlistofactiveincidentsandeventsaffectingcorridoroperations.

H DataHub 375. Verifyatanygiventime,DataManagementshallmaintainthefollowinglistsofactiveincidentsandeventsaffectingcorridoroperations:• Activetraffic

incidents• Activeunusual

congestioneventsreportedbytheICMEnvironmentorCoreSystem

• Activetransitincidents

• Activeplannedroad/laneclosures

• Activeplannedevents

• Activeweathereventshavingthepotentialtoaffecttravelconditionswiththecorridor

376. Verifyforeachidentifiedincidentandevent,DataManagementshallcollectandperiodicallyupdatethefollowinginformationcharacterizingtheincidentorevent:• Identification

numberassignedtotheincidentorevent

• Locationofincidentorevent

• Timeincidentoccurredoreventstarted

• Timealllaneswereclearedoropened

• Timetrafficconditionsreturnedtonormal

• Roadwaysegment(s)affectedbyincidentorevent

• Numberoflanesclosedoneachaffectedroadwaysegment

• Locationofclosedlanesoneachaffectedroadway

QuerytheDBtogetthelistofcreatedmockincidents(createviewonCMSaspartofCMSevaluationandseethelistofincidents)


119

TestREQID



segment• Agencyresponsible

formanagingtheincident/eventtraffic

DM-2.25

DataManagementshallmaintainalogofresponseplanningactivitiesconductedasaresultofanactiveincidentorevent.

H DataHub 377. Verifyfollowingtheidentificationofanactiveincidentorevent,DataManagementshallcollectandperiodicallyupdatethefollowinginformationdescribingtheresultingresponseplanningactivities:• Identification

numberassignedtotheincidentorevent

• Timewhenresponseplanningactivitieswereinitiated

• Informationaboutrecommendedresponseplans,ifany:

o Timearecommendedresponseplanwasproposed

o Identificationnumberofrecommendedresponseplan

o Responseplanevaluationscore

o Timeresponseplanwasapproved

o Timeresponseplanwasimplemented

o Timeresponseplanwasreplacedbyanotherplanorterminated

o Responseplanelementimplementationschedule

o Responseplan

ConnecttotheResponsePlanServiceendpointtoverifytherelevantinformation


120

TestREQID



elementimplementationsuccessorfailureandtimeofimplementation

o Timewhenresponseplanningactivitieswereterminated

DM-2.26

DataManagementshallcollectandstoreinformationdescribingeachdevelopedresponseplan.

H DataHub 378. Verifyforeachdevelopedresponseplan,DataManagementshallstoreorprovideaccesstoinformationdescribingtherecommendedcontrolactionsassociatedwiththeplan.Thisincludes:• Agenciesinvolvedin

theimplementationoftheresponseplan

• Recommendedalternateroute(s)aroundincident/eventforwhichtheresponseplanwasdevelopedo Recommended

route(s)forpassengercars

o Recommendedroute(s)forbuses

• Recommendedmeteringactionsatfreewayon-ramp:o Rampswith

recommendedfullclosure

o Rampswithrecommendedgreenballoperation

o Rampswithrecommendedmeteringchange

o Recommendedmeteringrateateachramp

• Recommendedtrafficsignalcontrolactions:o Intersections

forwhichsignaltimingplans

ConnecttotheResponsePlanServiceendpointtoverifytherelevantinformationStoringwillbeverifiedatthedatabase


121

TestREQID



aretobechanged

o Signaltimingplantoactivateateachidentifiedintersection

• Informationdisseminationstrategy:o Messagesto

postonfixedCMSs

o WheretodeployportableCMSsandwhatmessagetopostateachlocation

o Extinguishabletrailblazersignstoactivate

o WhichHARstoactivateandwhatmessagetobroadcastonthem

o Informationtodisseminatetotheregional511System

o Informationtomakeavailabletothird-partyinformationprovidersandmobiletravelapplicationdevelopers

• Requestedpersonneldeploymentstospecificcorridorlocations:o Implementatio

nscheduleDM-2.27

DataManagementshallcollectandstoreinformationdescribingeachimplementedresponseplan.

H DataHub 379. Verifyforeachimplementedresponseplan,DataManagementshallstoreorprovideaccesstoinformationdescribingthecontrolactionstaken.Thisincludes:• Timeplanwas

ConnecttotheResponsePlanServiceendpointtoverifytherelevantinformation


122

TestREQID



activated• Timeplanwas

terminated(updatedwithanotherplanorclosed)

• Agenciesinvolvedintheimplementationoftheplano Requested

personneldeploymentstospecificcorridorlocations

o Responseplanelementimplementationtimes

• Recommendedalternateroute(s)aroundtheincident/event:o Recommended

route(s)forpassengercars

o Recommendedroute(s)forbuses

• Recommendedmeteringactionsatfreewayon-ramp:o Rampswith

recommendedfullclosure

o Rampswithrecommendedgreenballoperation

o Rampswithrecommendedmeteringchange

o Recommendedmeteringrateateachramp

• Recommendedtrafficsignalcontrolactions:o Intersections

forwhichsignaltimingplansaretobechanged

o Signaltiming


123

TestREQID



plantoactivateateachidentifiedintersection

• Informationdisseminationstrategy:o Messages

postedonfixedCMSs

o LocationswhereportableCMSsweredeployed

o MessagepostedoneachdeployedportableCMS

o Extinguishabletrailblazersignsactivated

o ActivatedHARs,withwhatmessagebroadcasted

o Informationdisseminatedtotheregional511System

o Informationmadeavailabletothird-partyinformationprovidersandmobiletravelapplicationdevelopers

• Requestedpersonneldeploymentstospecificcorridorlocations

• Responseplanelementimplementationtimes

8.3.1.7.2.7 DataArchiving

DM-2.28

DataManagementshallarchiveICMCoreSystemconfigurationelements.

H DataHub VerifythebackuptoAWSglacier.DataManagementshallarchiveroadnetworkinformation.380. DataManagementshall


124

TestREQID



archiveICMCoreSystemconfiguration,security,error/fault,andstatusinformation.

381. DataManagementshallarchiveICMCoreSystemrulesinformation.

382. DataManagementshallarchiveallassetcapabilitydataprovidedtotheICMCoresystem.

DM-2.29

DataManagementshallarchivedatacollectedaspartofICMCoreSystemoperations.

H DataHub VerifythebackuptoAWSglacier.383. DataManagementshall

archiveinformationdetailingtheresponseplansthatweredevelopedandimplementedinresponsetospecificincidentsorevents.

384. DataManagementshallarchivetrafficestimationandpredictioninformation.

DM-2.31

DataManagementshallprovideameansforuserstoconfigurearchivingfunctions.


DM-2.32

DataManagementshallarchiveselecteddatasetsforaperiodof5years.


Glacierwillkeepitfor5years.

8.3.1.7.2.8 MaintenanceLogs

DM-2.33

DataManagementshallcollectandarchiveallmaintenancealertsandnotificationsgeneratedbytheICMEnvironmentandCoreSystem.


DM-2.34

DataManagementshallcollectandarchiveallmaintenanceactivitylogsenteredbyparticipatingagencies.


8.3.1.7.2.9 AdministrativeLogs

DM-2.35

DataManagementshalllogwhenusersaccessthesystem.



DM-2.36

DataManagementshalllogICMCoreSystemandsubsystemactivities.



DM- DataManagementshalllog M Corridor Testingtobedefinedwhen


125

TestREQID



2.37 allsystemchangesmadebysystemusers.

Management therequirementisaddressed.

8.3.1.7.3 DataCommunicationInterface

8.3.1.7.3.1 IncomingDataCommunicationChannel

DM-3.1

DataManagementshallincludeafunctiontoretrievedatadisseminatedthroughregionalcommunicationnetworks.

H DataHub DataManagementcomponentsshallincludeafunctiontoretrievedatadisseminatedthroughtheIEN.(NotvalidREQ)385. DataManagement

componentsshallincludeafunctiontoretrievedatadisseminatedthroughRIITS.VerifyeachpipelineconnectedtoRIITS.

386. VerifyDataManagementcomponentsshallincludeafunctiontoretrievedatadisseminatedthroughCaltrans’FreewayPerformanceMeasurementSystem(PeMS).VerifyeachpipelineconnectedtoFreewaydetector.

IENisnotthesourceofinformationforthesystem

DM-3.2

DataManagementshallreceivetrafficdetectiondatafromtrafficmanagementsystemsoperatedbylocalagencies.

H DataHub 387. DataManagementshallreceivetrafficsensordatafromCaltrans’freewaytrafficsurveillancesystem.

388. DataManagementshallreceivetrafficsensordatafromCaltrans’TSMSSsystem.

389. DataManagementshallreceivetrafficsensordatafromPasadena’sQuicNetsystem.

390. DataManagementshallreceivetrafficsensordatafromPasadena’sSCATSsystem.

391. DataManagementshallreceivetrafficsensordatafromArcadia’sTransSuitesystem.

392. DataManagementshallreceivetrafficsensordatafromLosAngeles


126

TestREQID



County’sKITSsystem.393. DataManagementshall

receivetrafficsensordatafromMonrovia’sKITSsystemhostedontheLosAngelesCountyKITSserver.

394. DataManagementshallreceivetrafficsensordatafromDuarte’sKITSsystemhostedontheLosAngelesCountyKITSserver.

DM-3.3

DataManagementshallreceivedatafromtraveltimemonitoringsystemsinstalledwithinthecorridor.

H DataHub 395. DataManagementshallreceivetraveltimedatacollectedbyPasadena’sDigiwestBlueMACsystem.

396. DataManagementshallreceivetraveltimedatacollectedbyPasadena’sSMARTSignalSystemdeployedalongOrangeGrove.

397. DataManagementshallreceivetraveltimedatacollectedbyArcadia’sIterisVantagesystem.

398. DataManagementshallreceivetraveltimedatafromthetraveltimemonitoringsystemusedbytheLosAngelesCountyDepartmentofPublicWorks.

399. DataManagementshallreceivetraveltimedatafromthesystemusedbytheCityofMonroviatomonitortraveltimesoncityarterials.

400. DataManagementshallreceivetraveltimedatafromthesystemusedbytheCityofDuartetomonitortraveltimesoncityarterials,ifdifferentfromLosAngelesCounty’ssystem.

401. DataManagementshallreceivetraveltimedatafromthesystemusedbyCaltranstomonitortraveltimesalongthesectionsofI-210,SR-134,

Connecttotraveltimedetectordataendpoint


127

TestREQID



andI-605freewaysunderICMmanagement.

DM-3.4

DataManagementshallreceivedatafromparticipatingprobedataproviders.

L Testingtobedefinedwhentherequirementisaddressed.

DM-3.5

DataManagementshallreceiveoperationaldatafromtransitmanagementsystems.


DM-3.6

DataManagementshallreceivetrafficsignaloperationaldatafromtrafficmanagementsystemsoperatedbylocalagencies.


DM-3.7

DataManagementshallreceiveoperationaldatafromelectronictravelerinformationmessagesignsoperatedalongcorridorroadwaysofinterest.


DM-3.8

DataManagementshallreceiveoperationaldatafromHARstationswithinandaroundthecorridorusedtodisseminateinformationtotravelers.


DM-3.9

DataManagementshallreceiveincidentinformationfromdispatchsystemsusedbyfirstresponders.


DM-3.10

DataManagementshallreceiveplannedlaneclosuresfromsystemsmaintainedbyroadwaymanagementagencies.


DM-3.11

DataManagementshallreceivealertsfromregionalnotificationsystems.


DM-3.12

DataManagementshallreceiveincidentdatafromcrowd-sourcingapplications.


DM-3.13

DataManagementshallusecommunicationprotocolsandmethodsforincomingdataappropriatetothedesignneedsofthesystem.

H DataHub Verifythestoreddataisintherightformat.Incomingdataeg:TMDDmessagesarecorrect.

DM-3.14

DataManagementshallusedatatransformationmethodsforallincomingdataappropriatetothespecificdataformatsandcommunicationprotocolsanditsintendedusewithinthesystem.Possibletransformationmethodsmay

H DataHub Designreviewisnotasystemtest.


128

TestREQID



includeETL,streaming,servicelayers,orothers.Specificmethodsshallbedefinedduringsystemdesign.

DM-3.15

DataManagementshallusethesystemofrecord,asdefinedintheSystemIntegrationrequirements,astheinitialsourceorfinaldestinationfordata.

H DataHub Designreviewisnotasystemtest.

8.3.1.7.3.2 OutgoingDataCommunicationChannels

DM-3.16

TheICMCoreSystemshallincludeafunctiontodisseminatedatausingregionalcommunicationnetworks.


TheICMCoreSystemcomponentsshallincludeafunctiontosenddatathroughtheIEN.(NotvalidREQ)WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.402. TheICMCoreSystem

componentsshallincludeafunctiontosenddatathroughRIITS.

IENisnotthecurrentsourceofdata

DM-3.17

TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststotrafficmanagementsystemsoperatedbylocalagencies.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.403. TheICMCoreSystem

shallincludeafunctiontosendtrafficsignalchangerequeststoCaltrans’TSMSSsystem.

404. TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststoPasadena’sTransparitysystem.

405. TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststoPasadena’sSCATSsystem.

406. TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststoArcadia’sTransSuitesystem.

407. TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststoLosAngelesCounty’sKITSsystem.

408. TheICMCoreSystemshallincludeafunctionto


129

TestREQID



sendtrafficsignalchangerequeststoMonrovia’sKITSsystemhostedontheLosAngelesCountyKITSserver.

409. TheICMCoreSystemshallincludeafunctiontosendtrafficsignalchangerequeststoDuarte’sKITSsystemhostedontheLosAngelesCountyKITSserver.

DM-3.18

TheICMCoreSystemshallincludeafunctiontochangemeteringratesinoperationatfreewayon-rampsandfreeway-to-freewayconnectors.



shallincludeafunctiontosendmeteringraterequeststotheATMSmoduleusedbyCaltranstomanageramp-meteringoperations.

DM-3.19

TheICMCoreSystemshallincludeafunctiontosendmessagepostingrequeststoelectronicmessagesignsusedtodisseminateinformationtotravelerswithinthecorridor.



DM-3.20

TheICMCoreSystemshallincludeafunctiontosendmessagebroadcastrequeststoHARstationsusedtodisseminateinformationtotravelersinandaroundthecorridor.



DM-3.21

TheICMCoreSystemshallincludeafunctiontosendrelevantinformationtoparticipatingfirstrespondingagencies.



DM-3.22

TheICMCoreSystemshallincludeafunctiontosendrelevantinformationtoparticipatingtransitagencies.



DM-3.23

TheICMCoreSystemshallincludeafunctiontosendalertstoparticipatingagencies.



DM-3.24

TheICMCoreSystemshallincludeafunctiontosendinformationtoregionaltravelerinformationsystems.



DM-3.25

TheICMCoreSystemshallincludeafunctiontosendinformationtotraveler




130

TestREQID



informationsystemsusedbytruckfleetdispatchersandtruckoperators.

8.3.1.7.4 DataFormats

DM-4.1

TheICMEnvironmentshallstoreorprovideaccesstodataincommonlyusedformats.

H DataHub 411. Verifytotheextentpossible,theICMEnvironmentshalltransmitdataintheTransportationManagementDataDictionary(TMDD)orNationalTransportationCommunicationsforIntelligentTransportationSystemProtocol(NTCIP)format.

412. Verifytotheextentpossible,theICMEnvironmentshallstoreorprovideaccesstocollectedtransitroutedataintheGeneralTransitFeedSpecification(GTFS)format.

DM-4.2

Collectedtrafficdatashallbeaggregatedinintervalsnolongerthan15minutes.Alldataaggregationsshallbeappropriatetotheintendeduseoftheinformation.


DM-4.3

AlldatausedbytheICMEnvironmentshallbestoredinelectronicformat.


8.3.1.7.5 DataVerificationandValidation

DM-5.1

DataManagementshallvalidateallfieldmeasurements.

H DataHub 413. DataManagementshall

validateunverifiedtrafficdataobtainedfromtrafficsensordata,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata• DataManagement

shallvalidateunverifiedtrafficvolumedataobtainedfromtrafficsensordata,usingvalidated

ConnecttoFreewaydetectordata&intersectiondetectorendpoint,andverifythequalityindicatorsarethereandcorrect



131

TestREQID



historicaldataandexpectedvaluesfortheperiodassociatedwiththedata.

• DataManagementshallvalidateunverifiedsensoroccupancydataobtainedfromtrafficsensordata,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata


414. DataManagementshallvalidateunverifiedtrafficspeedestimatesobtainedfromtrafficsensordata,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

415. DataManagementshallvalidatereceivedincident/eventdata,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

416. DataManagementshallvalidateunverifiedtransitdatareceivedfromparticipatingtransitagencies,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

417. DataManagementshallvalidateunverifiedparkingoccupancydataobtainedfromparkingmanagementsystems,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.


132

TestREQID



418. DataManagementshallvalidatereceivedweatherdata,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

DM-5.2

DataManagementshallvalidateallreceivedcontroldevicedatathathavenotbeenpreviouslyvalidatedbythesystemsupplyingtheinformation.

H DataHub 419. VerifyDataManagementshallvalidateunverifiedoperationaldatareceivedfromcontroldevicesconnectedtotheICMsystem,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.• DataManagement

shallvalidateunverifiedsignaltimingdatareceived,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

• DataManagementshallvalidateunverifiedrampmeteringdatareceived,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

• DataManagementshallvalidateunverifiedfixedCMSoperationaldatareceived,usingvalidatedhistoricaldataandexpectedvaluesfortheperiodassociatedwiththedata.

ConnecttoCMS,Rampmeter,intersectionsignalstateendpoint,andvalidatethedataiscorrect

DM-5.4

DataManagementshallmarkas“potentiallyinvalid”receivedfieldmeasurementsdatafailingaverificationorvalidationtest.

H DataHub 420. VerifyDataManagementshallmarkas“potentiallyinvalid”unverifiedflowmeasurementsreceivedfromfielddevicesorsystemsdeviatingbymorethantwostandarddeviationsfromthe

ConnecttoFreewaydetector&Intersectiondetector&traveltimedetectorendpointand


133

TestREQID



historicalaverageorfallingoutsideauser-definedacceptedrangeforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

421. VerifyDataManagementshallmarkas“potentiallyinvalid”unverifiedintersectionturningcountsreceivedfromfielddevicesorsystemsdeviatingbymorethantwostandarddeviationsfromthehistoricalaverageorfallingoutsideauser-definedacceptedrangeforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

422. VerifyDataManagementshallmarkas“potentiallyinvalid”unverifiedspeedmeasurementsorestimatesreceivedfromfielddevicesorsystemsdeviatingbymorethantwostandarddeviationsfromthehistoricalaverageorfallingoutsideauser-definedacceptedrangeforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

423. DataManagementshallmarkas“potentiallyinvalid”unverifiedtraveltimemeasurementsreceivedfromfielddevicesorsystemsdeviatingbymorethantwostandarddeviationsfromthehistoricalaverageorfallingoutsideauser-definedacceptedrangeforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

checkthequalityofdata


134

TestREQID



Testingtobedefinedwhentherequirementisaddressed:424. DataManagementshall

markas“potentiallyinvalid”unverifiedparkingoccupancydatareceivedfromparkingmanagementsystemsdeviatingbymorethantwostandarddeviationsfromthehistoricalaverageorfallingoutsideauser-definedacceptedrangeforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

425. DataManagementshallmarkas“potentiallyinvalid”unverifieddatareceivedfromtransitagenciesdeviatingbymorethantwostandarddeviationsorfallingoutsideauser-definedacceptedrangefromthehistoricalaverageforthecorrespondingtimeperiodintheabsenceofactivemajorincidents/events.

426. DataManagementshallmarkas“potentiallyinvalid”anyweatherdatareceivedfromweatherstationsfallingoutsideauser-definedacceptedrange.

DM-5.5

DataManagementshallincludeafunctiontodeterminearangeoftypicalvaluesforthedatathatmaybesuppliedbytrafficmanagementdevices.


DM-5.6

DataManagementshallmarkas“invalid”datareceivedfromtrafficmanagementdevicesfallingoutsidethenormalrangeofvaluesassociatedwiththedeviceoperations.


DM-5.7

TheICMCoreSystemshallnotuseinvalidorerroneous

H DataHub 427. VerifytheICMCoreSystemshallignoreany

Lookatthedownstream


135

TestREQID



datainitscorridoroperationalassessmentsanddecision-makingprocesses.

datamarkedashavingfailedavaliditytest.

428. VerifytheICMCoreSystemshallignoreredundantdata.

processandinjectdataismarkedasinvalidanddoesn’tusethisdata.Datahubwillmarkthisasinvaliddataanddownstreamdoesn’tuseitIndividualsforeachconsumingtestwillberunonanindividualbasis(thisisnotadatahubtestbutthisdataisnotconsumed)

DM-5.8

TheICMEnvironmentshallinformrelevantTMCandTCSoperatorswhendataanomaliesorabnormalitiesareidentified.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria:429. VerifytheICM

Environmentshallinformthedesignatedmaintenancemanageroftheagencyoperatingadevicewhenanomaliesorabnormalitiesareidentifiedinthedatareceivedfromthedevice.

430. VerifytheICMEnvironmentshallinformtheTrafficEngineeroftheagencyoperatingadevicewhenanomaliesorabnormalitiesareidentifiedinthedatareceivedfromthedevice.

431. VerifytheICMEnvironmentshallinformICMEnvironmentuserswhenanomaliesorabnormalitiesareidentifiedinthedatareceivedfromadeviceconnectedtotheICMsystem.

DM-5.9

TheICMEnvironmentshallsubmitforreviewfield


WillbepartofvendorsuppliedCMSevaluationand

Manualtest


136

TestREQID



measurementdatathathavebeenflaggedas“potentiallyinvalid.”

acceptancecriteria.

8.3.1.7.6 DataStorageandWarehousing

DM-6.1

DataManagementshallstoreinacentralrepositoryalldatautilizedorcreatedbythesystemnotbeingstoredelsewhere.

H DataHub Designreviewtest,notasystemtest.

DM-6.2

DataManagementshallstoreinacentralrepositoryalldatacharacterizingtheoperationoftheICMCoreSystemnotstoredelsewhere.


DM-6.4

Datashallbestoredusingstate-of-the-arttechnologybymethodsthatareextensibleandscalable.


DM-6.5

Datashallbestoredusingtechnologiesappropriatetothedesignneedsofthesystem(performance,cost,size,etc.).TechnologiesshallincludebothSQLandNon-SQLtechnologiesasdictatedbydesignneedsandconstraints.


8.3.1.7.7 DataDocumentationandMaintenance

DM-7.1

TheICMEnvironmentshallhaveanICMdatadictionary.

H DataHub 432. VerifySysteminterfacedesignspecdoc.

433. TheDataDictionaryshallcontainalistingofallDataHubdataelements,theirdefinition,dataformat,andsize.

434. TheDataDictionaryshallcontainalistingofalldatasourcesandtheirdataelements,theirdefinition,dataformat,andsize.

435. TheDataDictionaryshallcontainalistingofallexternallyavailabledataprovidedbythesystem,includingtheirdataelements,theirdefinition,dataformat,andsize.

436. TheDataDictionaryshall


137

TestREQID



containalistingofallavailablesystem-produced,externallyavailableinterfacesandmessages,documentingthedataavailable,transmissionprotocols,andformats.

437. TheDataDictionaryshalldescribesystemstandardsforcapturingandmanagingdata,includingissuesofthetimevalueofdata,dataprovenance,datatypes,datastandarduseandselection,anddatasecurity.

438. TheDataDictionaryshalldescribedataqualitystandardsforalldataelements.Dataqualitystandardsshallincludestandardsfor:• Dataaccuracy• Methodsto

measureandverifydataquality

• Requiredlevelsofdataquality(suchasdegradedperformancevs.unabletoperformfunctionresults)

• Requiredresponsesfordatathatdoesnotmeetdataqualitystandards

• Requiredtimelinessstandardsforeachdatasource

• Requiredcompletenessforeachdatasource

439. Dataqualityshallbeuniquelyspecifiedforeachdatasourceandinternallyprocesseddataelement.

440. 90%ofalldataelementsmustincludeadataqualitystandard.

441. TheDataDictionaryshalldescribesystem


138

TestREQID



standardsandvalidation.Includedwillbespecificdatavalidationspecificationsforallincomingandprocesseddataelements.

442. Maintenanceincludingupdates,reviews,andaccuracyoftheDataDictionaryshallbetheresponsibilityoftheCorridorDataAnalyst,alongwithassigneddataanalystsanddatabaseadministrators.

DM-7.2

TheCorridorDataAnalystshallensurethatalldatahasadataqualityspecificationandthatdataismeetingthosespecificationsatalltimes.



DM-7.3

Stakeholdersshallbeabletocommunicateneedsfordataadditions,removals,orformatchangestothesystemdataprocessesanddesign.

H Willbeaddressedafterthepilotrelease.Notpartofsystemtesting.Willbeevaluatedduringpostimplementationreview.

8.3.1.8 DecisionSupport

8.3.1.8.1 CorridorRoadandAssetInformationAccess

DS-1.1

DecisionSupportshallreceivefromDataManagementthestatusoftheroadnetwork,includingcurrentincidentinformation,roadwaymaintenanceactions,andclosures.

H DecisionSupport

443. VerifyallpipelinesareavailableatthedatahubgatewayforDecisionSupport.

444. Verifyeachendpointfordecisionsupportisavailable.

445. VerifyDecisionSupportshallreceiveallroadstatusinformationfromDataManagement/DataHubatafrequencyof30secondsorless.

446. VerifyallroadstatusinformationreceivedfromDataManagementshallbeprocessedandavailabletoDecisionSupportwithin1minuteofthedata’stimeofmeasurement.

ConnecttoappropriateAMQtopicandchecktheinformationiscorrect



139

TestREQID



DS-1.2

DecisionSupportshallreceivefromDataManagementcurrentsensordata.

H DecisionSupport

447. VerifyPEMSpipelinesensordata.

448. VerifydecisionsupportshallreceivesensordatafromDataManagementatafrequencyofevery30secondsorless.

449. VerifyallsensordatareceivedfromDataManagementshallbeprocessedandavailabletoDecisionSupportwithin1minuteofthedata’stimeofmeasurement.

450. Verifyintersectionsignalsensordata.

451. VerifyDecisionSupportshallreceivesensordatafromDataManagementatafrequencyofevery30secondsorless.

452. VerifyallsensordatareceivedfromDataManagementshallbeprocessedandavailabletoDecisionSupportwithin1minuteofthedata’stimeofmeasurement.



DS-1.3

DecisionSupportshallreceivefromDataManagementtheoperationalstatusofthetrafficcontrolassets,includingtrafficsensors,environmentalsensors,intersectionsignals,rampmeters,andCMSdevices.

H DecisionSupport

453. VerifydecisionsupportshallreceivealloperationalstatusinformationfromDataManagementatafrequencyof30secondsorless.

454. VerifyalloperationalstatusinformationreceivedfromDataManagementshallbeprocessedandavailabletoDecisionSupportwithin1minuteofthedata’stimeofmeasurement.



DS-1.4

DecisionSupportshallreceivefromDataManagementtheoperationalstatusoftransitassets.

M DecisionSupport


DS-1.5

DecisionSupportshallusereliabledatafromcorridorassets.

H DecisionSupport

455. Verifyallsensorinformationreceivedshallbeevaluatedfordataquality.Methodsforevaluatingqualityshall

ConnecttoappropriateAMQtopicandcheckthe



140

TestREQID



bedeterminedaccordingtothespecificsensortype.Thesemethodsandthespecificthresholdsrequiredbythesystemshallbedefinedduringthesystemdesignphase.

456. Datafromasensorthatfailsdataqualitychecksshallcausethesensortobeconsideredfailedforthepurposesoftheuptimerequirement.

457. Longevityinventorycheckshallbeperformedoveraperiodoftime(day,week,month),whenthesoftwareisstableandrunning.

informationiscorrect

DS-1.6

DecisionSupportshallreceivefromDataManagementtheoperationalstatusandavailabilityofallorganizationalassets.


8.3.1.8.2 CorridorTrafficStateEstimation

DS-2.1

DecisionSupportshallestimateonacontinuousbasisthecurrentstateofvehicletrafficonroadwaylinksunderICMconsideration.

H DecisionSupport

458. Verifyestimationprovidescurrentstateofvehicletrafficforeverylink.

459. DecisionSupportshallmaintainacharacterizationofthecurrentvehicletrafficconditionsonthelinkforeachfreewaysegmentunderICMconsideration.• Foreachfreeway

segmentunderICMconsideration,DecisionSupportshallestimatethecurrentaveragetrafficdensityacrossthesegment.

• ForeachfreewaysegmentunderICMconsideration,DecisionSupportshallestimatethecurrentaveragetrafficflowacrossthesegment.

Connecttofreewayestimationendpoint&AMQcheckifthedataisthereandcorrect



141

TestREQID



460. VerifyDecisionSupportshallmaintainacharacterizationofthecurrentvehicletrafficconditionsoneacharterialsegmentunderICMconsideration.• Foreacharterial

segmentunderICMconsideration,Decisionsupportshallestimatetheaveragetrafficflowabletotravelacrossthelink.

• Foreachuser-definedarterialroute,Decisionsupportshallestimatethecurrentaveragetraveltimealongtheroute.

• ForeacharterialsegmentunderICMconsideration,Decisionsupportshallestimatewhetherthesegmentis:

• Notcongested• Experiencinglow-

levelcongestion• Experiencinghigh-

levelcongestion• Oversaturated

461. VerifyDecisionSupportshallmaintainacharacterizationofcurrentvehicletrafficconditionsateachintersectionunderICMconsideration.ForeachmajorapproachtoanintersectionunderICMconsideration,DecisionSupportshalldeterminewhethertheapproachis:• Undersaturated• Oversaturated• Spillingbackacross

theupstreamintersection

ForeachintersectionunderICMconsideration,

Connecttoarterialestimationendpoint&activecheckifthedataisthereandcorrect


142

TestREQID



DecisionSupportshalldeterminewhethertheoverallintersectionis:• Undersaturated• Oversaturated• Spillingbackacross

upstreamintersectionsonatleastoneapproach

462. Currenttrafficstateshallbeestimatedonanongoingbasis,delayednomorethan5minutesbehindactualtime.

463. Trafficstateestimationsnapshotshallbeprovidedevery5minutes.

464. Currenttrafficstateestimatesshallbebasedonthelatestinformationavailablefromthedatahub.

DS-2.3

DecisionSupportshallincludeinitscurrenttrafficstateestimationeffectsassociatedwithactiveincidentsandevents.

H DecisionSupport

465. Verifycurrenttrafficstateestimationeffectsassociatedwithactiveincidentsandevents.

466. DecisionSupportshallidentifyinitscurrenttrafficstateestimationlaneblockagesand/orcapacityconstraintscausedbyactiveincidentsthathavebeenverified.

467. DecisionSupportshallidentifyinitscurrenttrafficstateestimationlaneblockagesand/orcapacityconstraintscausedbyplannedlaneorroadwayclosures.



DS-2.4

DecisionSupportshallincludeinitscurrenttrafficstateestimationtheeffectofthecurrentworkingstateofalltrafficsensorssettosupplyinformationtotheICMCoreSystem.

H DecisionSupport

468. Verifytheeffectofthecurrentworkingstateofalltrafficsensors.DecisionSupportshallassesstheeffectofthequalityofincominginformationonthequalityofitscurrenttrafficstateestimates.

469. VerifyDecisionSupportshallassesstheeffectofmissinginformationonthequalityofitscurrent




143

TestREQID



trafficstateestimates.470. VerifyDecisionSupport

shallprovideanoverallconfidencelevelforallcurrenttrafficestimates.

DS-2.5

DecisionSupportshallincludeinitscurrenttrafficstateestimationeffectsassociatedwiththeoperationalstatusoftrafficcontroldevices.

H DecisionSupport

471. VerifyDecisionSupportshallincludeinitscurrenttrafficstateestimationtheeffectsofthetrafficsignalcontrolplancurrentlyinuseatindividualsignalizedintersections.

472. VerifyDecisionSupportshallincludeinitscurrenttrafficstateestimationtheeffectsofcurrentrampmeteringoperationsonfreewayon-rampsandfreeway-to-freewayconnectors.

Connecttoarterialestimationendpoint&AMQcheckifthedataisthereandcorrect


DS-2.6

DecisionSupportshallprovidereliableestimatesofcurrenttrafficconditionswithinthecorridor.

H DecisionSupport


DS-2.7

DecisionSupportshallcomparethecurrentcorridortrafficstatetohistoricaltrafficpatternsandprovideameasureofvariabilityfromthenormalhistoricaltrafficpattern.

DecisionSupport


8.3.1.8.3 CorridorTrafficStateForecasting

DS-3.1

DecisionSupportshallincludeafunctiontoproduceforecastsoffuturestatesofvehicletrafficonroadwaylinksunderICMconsideration.

H DecisionSupport

473. VerifyDecisionSupportforecastsshallcomputeanddisplaythefollowingbasictrafficcharacteristicsforeachroadwaylinkunderICMconsiderationattheendofeachforecastinterval:• Forecastedaverage

trafficflowrateacrossthelink

• Forecastedaveragetrafficspeedacrossthelink

• Forecastedaveragetrafficdensityalongthelink

474. VerifyDecisionSupportforecastsshallcompute

Connecttopredictionendpoint&activeMQandthedataisthereandcorrect



144

TestREQID



anddisplaythefollowingvehicle-basedproductivitymetricsforeachforecastreportingintervalforeachroadwaylinkunderICMconsideration:• Vehicle-miles


traveled(VHT)475. VerifyDecisionSupport

forecastsshallcomputeanddisplaythefollowingvehicle-basedmobilitymetricsforeachforecastreportingintervalforeachroadwaylinkunderICMconsideration:• Averagetraveltime

acrosslink• Averagedelayper

vehicletraversingthelink

• Vehicle-hoursofdelay(VHD)incurredonthelinksincestartofforecastinterval

476. VerifyDecisionSupportforecastsshallcomputeanddisplaythefollowingperson-basedproductivitymetricsforeachforecastreportingintervalforeachroadwaylinkunderICMconsideration:• Person-miles

traveled(PMT)• Person-hours

traveled(PHT)477. VerifyDecisionSupport

forecastsshallcomputeanddisplaythefollowingperson-basedmobilitymetricsforeachforecastreportingintervalforeachroadwaylinkunderICMconsideration:• Averagedelayper

persontraversingthelink

• Person-hoursofdelay(PHD)incurred


145

TestREQID



onthelinksincestartofforecastinterval

DS-3.2

Trafficforecastsshallbebasedonthelatesttrafficanddemandinformationavailableforthecorridoratthetimetheforecastisrequested.

H DecisionSupport

478. VerifyDecisionSupportshallconducttrafficforecastsusingthelatestfieldandestimateddataavailableatthetimetheforecastisrequested.

479. VerifyDecisionSupportshallnotattempttoreplacethesetoffieldandestimateddatausedtoconductaforecastinthemiddleofaforecastingprocess.



DS-3.3

DecisionSupportshallincludeinitstrafficforecaststheeffectofthecurrentworkingstateofalltrafficsensorssettosupplyinformationtotheICMCoreSystem.

H DecisionSupport

480. VerifyDecisionSupportshallevaluatetheeffectofthequalityofincominginformationonthequalityofitstrafficforecasts.

481. VerifyDecisionSupportshallevaluatetheeffectofmissinginformationonthequalityofitstrafficforecasts.

482. VerifyDecisionSupportshallcalculateanddisplayanoverallconfidencelevelforalltrafficforecasts.



DS-3.4

DecisionSupportshallcompleteatrafficforecastforeachresponseplandeveloped(knownasaresponseplanforecast).

H DecisionSupport

483. Verifyresponseplanisinplaceasperpredictionresults.

DS-3.5

DecisionSupportshallincludeafunctionforICMCoreSystemuserstospecifyunderwhichcircumstancestrafficforecastsofexistingcontrolstrategies(“nochangescenario”)aretobeexecuted.



DS-3.6

DecisionSupportshallincludeafunctionforICMCoreSystemuserstospecifythetimehorizontowhichtrafficforecastsaretobeexecuted(forecastoverthenext30minutes,1hour,2hours,etc.).



DS-3.7

DecisionSupportshallincludeafunctionforICMCore




146

TestREQID



Systemuserstospecifythedatareportingintervalwithinatrafficforecast(e.g.,forecastdatareportedevery5minutes,15minutes,1hour,etc.)

DS-3.8

DecisionSupportshallincludeafunctionforICMCoreSystemuserstospecifytheintervalatwhichDecisionSupportistoexecutetrafficforecasts(e.g.,newforecastevery15minutes).



DS-3.9

DecisionSupportshallbeabletocompleteforecastsofcorridoroperationsinatimelymanner.

H DecisionSupport

484. Verifypredictionsarecompletedwithin5minutes.DecisionSupportshallbeabletocompleteatrafficforecastwithin5minutesofreceivingaforecastrequest.

DS-3.10

TheCorridorManagershallperiodicallyensuretheaccuracyofthetrafficforecastsproducedbyDecisionSupport.



DS-3.11

DecisionSupportshallarchivetheresultsoftrafficforecastingactivitiesforfutureanalyses.

H DecisionSupport

485. VerifydatahubstoresthepredictionsandPEMSsavesthisinformation.

486. DecisionSupportshallarchiveallforecastedtrafficstatesforuseinpost-incident/eventanalysis.

487. VerifyDecisionSupportshallarchivetheresultsofallforecastcomparisonstofielddataforfutureanalyses.

8.3.1.8.4 RulesEngineCapabilities

8.3.1.8.4.1 RuleApplication

DS-4.1

Therulesengineshallhavestate-of-the-artrulesenginecapabilities.

H DecisionSupport

488. Verifytherulesengineselectedhasallthementionedcapabilities:DecisionSupport,rules,evaluation.Performanceshallnotdegradelinearlywithincreasesinthenumberofrules.


147

TestREQID



489. VerifyDecisionSupportrulesengineshallimplementaReteorsimilaralgorithmwithinitsinferenceengine.

490. VerifyDecisionSupportrulesengineshallimplementahybrid-chaining(forwardandbackwardchaining)rulesexecution(NOTE:Likelyusesforbackwardchaining–constantlyevaluatingcurrenttrafficstatelookingforincident,lookingformultiplepossibleroutes).

491. DecisionSupportrulesengineshallincludeafunctionforrecursiverulesdefinitionandprocessing.

492. DecisionSupportrulesengineshallincludeafunctionforgeospatial-basedrulesexecution.Geospatialresultsmaybeimplementedasanexternalqueryprocess.

493. DecisionSupportrulesengineshallallowfordeterministicresults.

494. DecisionSupportrulesengineshallallowfornon-deterministicresults(NOTE:Likelyusagefindingroutes,incidents)

495. DecisionSupportrulesengineshallincludeafunctiontoreacttoeventsinthecorridor,ineffectlisteningforeventsandexecutingrulesasaresult(NOTE:Inamanner,similartoareactivetransitivequery).

496. DecisionSupportrulesengineshallallowforexternalclass/method,procedure,andserviceexecutioninrulesestimations.

DS-4.2

DecisionSupportshallbeabletoimplementtherulesdefinedinSection9.3.4.

H DecisionSupport

497. Verifyiftherulecanbeimplementtocreateappropriateresponse


148

TestREQID



Section9.3.4=>RuleCreationandManagement

plans.

DS-4.3

DecisionSupportshallincludeafunctionforTrafficEngineerstomanagetherulestobeappliedtoincident/eventresponse.


498. Verifythespreadsheetcanbeuploadedandrulesbechanged.DecisionSupportshallprovideameansforTrafficEngineerstoactivate/deactivaterulestobeused.

DS-4.4

DecisionSupportshallexecuterulesautomaticallyorondemand.

H DecisionSupport


8.3.1.8.4.2 Post-ResponseEvaluation

DS-4.5

DecisionSupportshallmaintainalogofruleexecutionforpost-incident/eventevaluation.

H DSS/CorridorManagement


DS-4.6

DecisionSupportshallprovideapost-incident/eventrulesevaluationandanalysis.



DS-4.7

DecisionSupportshallgenerateadailyoperationalevaluationreportattheendofeachdayprovidingasummaryoftherulesexecutionanddetailsofthespecificrulesoperation,tobereviewedbytheCorridorTechnicalManager.



8.3.1.9 CoreSystemUserInterfaces

8.3.1.9.1 UserInterfacesforManagingAssetInformation

UI-1.1 TheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteassetinventorydata.



Systemshallincludeauserinterfacetocreate,view,update,anddeletetheinventoryofroadwaylinksandintersections(networkinventory)definingtheICMcorridor.

500. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddelete


149

TestREQID



traveltimemeasurementdeviceinventory.

501. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteweathermeasurementdeviceinventory.

502. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeletesignalinventory.

503. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleterampmeterinventory.

504. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeletetransitassetinventory.

505. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeletetrafficsensorinventory.

506. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeletefixedCMSinventory.

507. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteportableCMSinventory.

508. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteextinguishabletrailblazersigninventory.

509. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteHARinventory.

510. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteorganizationalassetinventory.


150

TestREQID



511. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeleteparkingassetinventory.

512. VerifytheICMCoreSystemshallincludeauserinterfacetocreate,view,update,anddeletevideocamerainventory.

UI-1.2 TheICMCoreSystemshallincludeauserinterfacetoviewandupdateassethealthinformation.



shallincludeauserinterfacetoviewandupdatetrafficsignalhealthinformation.

514. TheICMCoreSystemshallincludeauserinterfacetoviewandupdaterampmeterhealthinformation.

515. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateparkingassethealthinformation.

516. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetransitassethealthinformation.

517. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatefixedCMShealthinformation.

518. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateportableCMSinventoryandstateinformation.

519. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateextinguishabletrailblazersignhealthinformation.

520. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateHARhealthinformation.


151

TestREQID



521. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateorganizationalassethealthinformation.

522. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateCCTVcamerahealthinformation.

523. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetrafficsensorhealthinformation.

524. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetraveltimemeasurementdevicehealthinformation.

525. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateweathermeasurementdevicehealthinformation.

UI-1.3 TheICMCoreSystemshallincludeauserinterfacetoviewandupdateassetavailability.



shallincludeauserinterfacetoviewandupdatetrafficsignalavailability.

527. TheICMCoreSystemshallincludeauserinterfacetoviewandupdaterampmeteravailability.

528. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateparkingassetavailability.

529. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetransitassetavailability.

530. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatefixedCMSavailability.


152

TestREQID



531. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateportableCMSavailability.

532. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateextinguishabletrailblazersignavailability.

533. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateHARavailability.

534. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateorganizationalassetavailability.

535. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateroadnetworksegmentavailability.

536. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateCCTVcameraavailability.

537. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetrafficsensoravailability.

538. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetraveltimemeasurementdeviceavailability.

539. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateweathermeasurementdeviceavailability.

UI-1.4 TheICMCoreSystemshallincludeauserinterfacetoviewandupdateassetstate.



shallincludeauserinterfacetoviewandupdatescheduledlane/roadclosures.


153

TestREQID



541. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetrafficsignalstate.

542. TheICMCoreSystemshallincludeauserinterfacetoviewandupdaterampmeterstate.

543. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateparkingassetstate.

544. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetransitassetstate.

545. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatefixedCMSstate.

546. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateportableCMSstate.

547. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateextinguishabletrailblazersignstate.

548. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateHARstate.

549. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateorganizationalassetstate.

550. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateroadnetworkstate.

551. TheICMCoreSystemshallincludeauserinterfacetoviewandupdatetrafficsensorstate.

552. TheICMCoreSystemshallincludeauser


154

TestREQID



interfacetoviewandupdatetraveltimemeasurementdevicestate.

553. TheICMCoreSystemshallincludeauserinterfacetoviewliveCCTVcameravideostreams.

554. TheICMCoreSystemshallincludeauserinterfacetopanandtiltCCTVcameras.

555. TheICMCoreSystemshallincludeauserinterfacetoviewandupdateweathermeasurementdevicestate.

UI-1.5 TheICMcorridorassetmanagementuserinterfaceshallbecapableofcontinuousoperationsintheeventofanyindividualsystemfailure.



8.3.1.9.2 UserInterfacesforManagingIncident/EventInformation

UI-2.1 TheICMCoreSystemshall

includeauserinterfacetocreate,view,update,anddeleteincident/eventinformation.



shallincludeauserinterfacetocreate,view,update,anddeletethefollowinginformationforanincident:• Typeofincident• Timeincident

occurred• Expectedduration

ofincident• Roadway/transit

segmentonwhichincidentislocated

• Locationofincidentalongroadway/transitsegment


• Agencyresponsibleformanagingthe


155

TestREQID



incident• Verificationstatusof

incident557. TheICMCoreSystem

shallincludeauserinterfacetocreate,view,update,anddeletethefollowinginformationforanevent:• Typeofevent• Timeeventoccurred• Expectedduration

ofevent• Roadway/transit

segment(s)onwhicheventislocated

• Location(s)ofeventalongroadway/transitsegment(s)


• Agencyresponsibleformanagingtheincident

• Verificationstatusofevent

558. TheICMCoreSystemshallprovideafunctionpermittinguserstoconfirmthatanincidentoreventhasbeenverifiedtoexist.

559. TheICMCoreSystemshallincludeafunctiontosetintervalthresholdswithinwhichnewlyidentifiedincidentsoreventsshallbeverified.

8.3.1.9.3 UserInterfaceforManagingMockIncidents


includeauserinterfacepermittinguserstocreatemockincidents.



shallincludeauserinterfacepermittinguserstocreate,view,update,anddeletemockincidents.

561. TheICMCoreSystemshallincludeamap-


156

TestREQID



basedinterfaceenablinguserstochoosethelocationforthemockincidentstobetested.

562. TheICMCoreSystemshallincludeauserinterfaceforsettingthestarttimeformockincidents.

563. TheICMCoreSystemshallincludeauserinterfaceforspecifyingthedurationofmockincidents.

564. TheICMCoreSystemshallincludeauserinterfaceforspecifyinglanes,busroutes,ortracksaffectedbymockincidents.

565. TheICMCoreSystemshallincludeauserinterfaceforspecifyinganendtimeformockincidents.

566. TheICMCoreSystemshallincludeauserinterfaceforspecifyingwhetheraspecialresponseplanisrequiredasaresponsetomockincidents.

567. TheICMCoreSystemshallincludeauserinterfacepermittinguserstoassignanametoamockincident.

UI-3.2 TheICMCoreSystemshallincludeauserinterfacepermittingthetestingofmockincidents.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.568. Verifymockincidentscan

beidentifiedasmockincidentsinthedatahub.

569. TheICMCoreSystemshallincludeaninterfacepermittingthesubmissionofmockincidentstotheDecisionSupportmodulefortestingpurposes.

570. TheICMCoreSystemshallincludeaninterfacepermittingthegenerationofapost-incidentreportbasedon


157

TestREQID



asubmittedmockincident.

571. TheICMCoreSystemshallincludeaninterfacepermittingthedisplayingonamapoftheresponseplanelementsthathavebeenrecommendedforsubmittedmockincidents.

8.3.1.9.4 UserInterfacesforManagingResponsePlans

8.3.1.9.4.1 ResponsePlanViewing


includeauserinterfaceforviewingresponseplans.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.572. Foreachresponseplan,

theICMCoreSystemshalldisplaysummaryinformationabouttheincidentoreventthattriggeredthedevelopmentoftheplan.

573. Foreachresponseplan,theICMCoreSystemshalldisplayalistofalltheagenciesinvolvedintheimplementationoftheplan.

574. Foreachresponseplan,theICMCoreSystemshalldisplaytherecommendeddetourroute(s)forpassengercars,trucks,andbuses.

575. Foreachresponseplan,theICMCoreSystemshalldisplayalistoframpmetersthataretobemodifiedandinformationaboutthemeteringstrategy/ratetobeusedateachlocation.

576. Foreachresponseplan,theICMCoreSystemshalldisplayalistofintersectionswheretrafficsignaloperationsaretobealteredandinformationaboutthetimingplantobe


158

TestREQID



activatedateachintersection.

577. Foreachresponseplan,theICMCoreSystemshalldisplayalistoffixedfreeway/arterialCMSswhereincident/detourmessagesaretobepostedandwhatmessageistobepostedateachlocation.

578. Foreachresponseplan,theICMCoreSystemshalldisplaythelocationswhereextinguishabletrailblazersignsaretobeactivated.

579. Foreachresponseplan,theICMCoreSystemshalldisplaythelocationswhereportableCMSsaretobedeployedandwhatmessageistobepostedateachlocation.

580. Foreachresponseplan,theICMCoreSystemshalldisplaytheHARstationsthataretobeactivatedandwhatmessageistobebroadcastedateachlocation.

581. Foreachresponseplan,theICMCoreSystemshalldisplayasummaryofpersonnelrequiredtoimplementtheresponseplan.

582. Foreachresponseplan,theICMCoreSystemshalldisplayalistofconstraintsthatmayhaveaffectedthedevelopmentoftheresponseplan.

UI-4.2 TheICMCoreSystemshallallowsystemuserstoaccessinformationaboutactiveresponseplanswhileinthefield.



8.3.1.9.4.2 ResponseRulesManagement

UI-4.3 TheICMCoreSystemshallprovideauser-friendly




159

TestREQID



interfaceformanagingrulesusedbytheDecisionSupportmoduletoidentify,evaluate,andrespondtoincidentsandevents.

UI-4.4 TheICMCoreSystemshallprovideameansforuserstodocumenttherequirementsforspecificrulesanddependentruleswithinthesystemfordisplaywiththerule.



8.3.1.9.4.3 ResponsePlanDevelopment

UI-4.5 TheICMCoreSystemshallprovideauserinterfaceallowinguserstosubmitrequestsforspecificactionstobeincludedinaresponseplan.



UI-4.6 TheICMCoreSystemshallincludeafunctionforuserstomanuallyspecifywhetherspecificcontrolassetscanbeusedforthegenerationofaresponseplan.



UI-4.7 TheICMCoreSystemshallprovideauserinterfacepermittingmodificationtopreferencesaffectinghowresponseplansareevaluated.



shallincludeauserinterfacepermittingthesettingofweightingfunctionsforthecalculationofprediction-basedperformancemetricsusedintheevaluationofresponseplans.• TheICMCore

Systemshallincludeaninterfacepermittinguserstosetdifferentweightfactorstobeappliedtometricsassociatedwithspecificpredictionintervals(e.g.,0-15minutes,15-30minutes,etc.).

• TheICMCoreSystemshallincludeaninterface


160

TestREQID



permittinguserstosetdifferentweightfactorstobeappliedtovariousvehicletypes(e.g.,higherweightsforbuses).

584. TheICMCoreSystemshallincludeauserinterfacepermittingtheselectionofperson-basedorvehicle-basedmetricsintheevaluationofresponseplans.

UI-4.8 Foreachdevelopedresponseplan,theICMCoreSystemshalldisplayalistofsystemelementsthatwerenotselectedbecauseofoperationalproblems,ifany.



8.3.1.9.4.4 ResponsePlanSelection

UI-4.9 TheICMCoreSystemshallprovideaninterfacesummarizingthevariousresponseplansdeveloped,theresultoftheirevaluation,andtheplanrecommendedforimplementation.



UI-4.10

TheICMCoreSystemshallprovideaninterfaceallowinguserstoselecttheapproachtobeusedfortheevaluationofcorridorimpactsofeachdevelopedresponseplanswheremultiplealternativesexist(suchasselectionbetweenuseofuser-definedrules,orspecificevaluationtoolsormodels).



UI-4.11

TheICMCoreSystemshallprovideaninterfaceallowinguserstomanuallyselecttheresponseplantoimplementamongtheproposedplansdevelopedbythesystem.



8.3.1.9.4.5 ResponsePlanApproval

UI-4.12

TheICMCoreSystemshallincludeauserinterfacepermittingeachstakeholderagencytospecifythelevelofautomationdesiredfortheapprovalofsubmitted




161

TestREQID



recommendedresponseplans.

UI-4.13

TheICMCoreSystemshallincludeaninterfacepermittingthesettingofthelevelofautomationrequiredfortheapprovalofsubmittedmodificationstoanactiveresponseplan.



UI-4.14

TheICMCoreSystemshallprovideaninterfaceallowingindividualsresponsibleforapprovingresponseplanstoreviewplanssubmittedfortheirapproval.



shallprovideindividualstaskedwithapprovingaresponseplananinterfacedetailingtheplansubmittedforapproval.• Theresponseplan

approvalinterfaceshalldisplayamapshowingtherecommendeddetour(s)foreachvehicletype.

• Theresponseplanapprovalinterfaceshalldisplayamapshowingthelocationofallcontrolelementsassociatedwitharesponseplan.

• Theresponseplanapprovalinterfaceshalldisplayamapshowingthecontrolactionsassociatedwitheachcontrolelement.

• Theresponseplanapprovalinterfaceshallprovideacomparativeperformancesummaryoftheproposedresponseplanagainstthe“donothing”scenario(currentsituation).

586. TheICMCoreSystemshallprovideindividualstaskedwithapprovingaresponseplanan


162

TestREQID



interfaceallowingthemtocomparealternateresponseplansthatmayhavebeenproducedbytheDecisionSupportmodule.

587. TheICMCoreSystemshallprovideindividualstaskedwithapprovingaresponseplananinterfaceallowingthemtoentertheirapprovaldecision.

588. TheICMCoreSystemshallprovideindividualstaskedwithapprovingaresponseplanasummaryoftheapprovalstatusoftheplanbyotheragencies/individualsfromwhichapprovalissought.

8.3.1.9.4.6 ResponsePlanImplementation

UI-4.15

TheICMCoreSystemshallincludeauserinterfacefordirectingtheimplementationofanapprovedresponseplan.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.589. VerifytheICMcorewill

haveauserinterfacefordirectingtheimplementationofanapprovedresponseplan.

590. TheICMCoreSystemshallincludeafunctionfordirectingtheimplementationofroadnetworkchanges(rampclosures,etc.).

591. TheICMCoreSystemshallincludeafunctionfordirectingtheimplementationoftrafficsignalchanges.

592. TheICMCoreSystemshallincludeafunctionfordirectingtheimplementationoframpmeterchanges.

593. TheICMCoreSystemshallincludeafunctionfordirectingtheimplementationoforganizationalassetrequiredactions.



163

TestREQID



shallincludeafunctionfordirectingtheimplementationoftransitassetrequiredchanges.

595. TheICMCoreSystemshallincludeafunctionfordirectingtheimplementationofmessagesonfixedCMSsigns.

596. TheICMCoreSystemshallincludeafunctionfordirectingthedeploymentofportableCMSsigns.

597. TheICMCoreSystemshallincludeafunctionfordirectingtheactivationofextinguishabletrailblazersigns.

598. TheICMCoreSystemshallincludeafunctionfordirectingtheactivationofHARbroadcasts.

599. TheICMCoreSystemshallincludeafunctionfordirectingthedisseminationofinformationto511services,media,andotherinformationoutlets.

UI-4.16

TheICMCoresystemshallincludeaninterfacepermittingstakeholderstospecifywhethertheyrequiretheICMCoreSystemtoseekconfirmationfromthemthatanincidentoreventhasbeenterminatedbeforeallowingtheICMCoreSystemtoterminatetheevent.



UI-4.17

TheICMCoreSystemshallincludeaninterfaceforsystemuserstomanuallyindicatethatanincidentoreventhasterminated.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.600. Verifythatdatahubcan

processaterminationrequestwhenanincidentoreventisterminated.

601. TheICMCoreSystemshallincludeaninterfaceforTMCandTCS


164

TestREQID



operatorstomanuallyinformtheICMCoreSystemthatanincidentoreventhasterminated.

602. OnlyTMC/TCSoperatorsfromtheagencyassociatedwithanincidentoreventshallbeauthorizedtoinformtheICMsystemthataspecificincidentoreventhasterminated.

UI-4.18

TheICMCoreSystemshallincludeaninterfaceindicatingwhetherarecommendedresponseplanhasbeensuccessfullyimplementedinthefield.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.603. Verifyinformationabout

aresponseplanisdisplayedontheinterface.

604. TheICMCoreSystemshallincludeaninterfaceindicatingwhenandifaresponseplanhasbeensuccessfullyimplementedinitsentirety.

605. TheICMCoreSystemshallincludeaninterfacelistingallimplementedresponseplancomponentswithinaselectedjurisdiction.

606. TheICMCoreSystemshallincludeaninterfaceindicatingifarecommendedresponseplancannotbeimplemented.

607. Inthecaseofimplementationfailure,theICMCoreSystemshallindicatewhyarecommendedresponseplancouldnotbeimplemented.

UI-4.19

TheICMCoreSystemshallinformstakeholdersofsystemelementsthatwerenotselectedbecauseofoperationalproblemsbutthatwouldotherwisehavebeenpartoftheresponseplan.



UI-4.20

TheICMCoreSystemshallprovideresponseplan


608. Verifyapprovedresponseplaninformationis


165

TestREQID



informationtostakeholders. providedtorelevantoperators/supervisors.

609. TheICMCoreSystemshallinformTMC/TCSoperatorsofapprovedresponseplansthataretobeimplementedwithinthecorridor.

610. TheICMCoreSystemshallinformtransitfieldsupervisorsofresponseplanelementsthatmayaffectbusserviceoperations.

611. TheICMCoreSystemshallprovidedetailedinformationtofirstrespondersaboutapprovedresponseplans.

612. TheICMCoreSystemshallincludeafunctionforsystemuserstoaccessinformationaboutactiveresponseplanswhileinthefield.

8.3.1.9.4.7 UserInterfacesforManagingICMCoreSystemInformation

UI-5.1 TheICMCoreSystemshallincludeafunctionforviewingallICMlogactivity.



UI-5.2 TheICMCoreSystemshallprovideameansforuserstocustomizeICMEnvironmentoperations.



Systemshallprovideinputscreensformanualinputoreditofsystemconfigurationinformation.

614. VerifytheICMCoreSystemshalldisplayinputscreensformanualinputoreditofuseradministrationinformation.

615. VerifytheICMCoreSystemshalldisplayinputscreensformanualinputoreditofuserpreferences.

UI-5.3 TheICMCoreSystemshallallowoperationalparameterstobechangedwithoutrequiringasystemrestart.




166

TestREQID



UI-5.4 TheICMCoreSystemshallprovideauserinterfacetopermitstartandshut-downofCoreSystemcomponents.



8.3.1.9.4.8 GeospatialVisualizationofData

UI-6.1 TheICMCoreSystemshalldisplayonamapthedevicesthatmaybeusedtomanagetrafficwithintheICMcorridor.



shalldisplayonmapsroadwaysegmentsunderICMmanagement.

617. TheICMCoreSystemshalldisplayonmapsthesignalizedintersectionsconnectedtotheICMsystem.

618. TheICMCoreSystemshalldisplayonmapstherampmetercontrollersconnectedtotheICMsystem.

619. TheICMCoreSystemshalldisplayonmapsthefixedCMSdevicesconnectedtotheICMsystem.

620. TheICMCoreSystemshalldisplayonmapstheextinguishabletrailblazersignsconnectedtotheICMsystem.

621. TheICMCoreSystemshalldisplayonmapstheHARstationsconnectedtotheICMsystem.

622. TheICMCoreSystemshalldisplayonmapsthepark-and-ridefacilitiesconnectedtotheICMsystem.

UI-6.2 TheICMCoreSystemshalldisplayonamapinformationabouttransitservicesofinteresttoICMoperations.



UI-6.3 TheICMCoreSystemshalldisplayonamapinformationaboutthedevicesusedtomonitorcorridoroperations.



UI-6.4 TheICMCoreSystemshallincludeafunctionforuserstoaccessfrommapskeygeometriccharacteristics




167

TestREQID



aboutindividualroadwaylinksunderICMmanagement.

UI-6.5 SystemusersshallbeabletoaccessfrommapdisplaysinformationaboutthetrafficmanagementdevicesintheICMinventory.



UI-6.6 TheICMCoreSystemshallincludeafunctionforuserstoaccessfrommapdisplaysavailablevideofeedsfromnearbyCCTVcameras.



UI-6.7 TheICMCoreSystemshallincludeafunctionforuserstoviewonamapthecurrentoperationalstatusofroadwaysegmentsunderICMmanagement.



shallincludeafunctionforuserstoview,ifavailable,thelatestmeasurementsfromtrafficdetectiondevicesdisplayedonmap.

624. Mapsshallbeabletocolorroadwaylinksbasedonthelevelofcongestiononthelink.

625. Mapsshallbeabletodisplayuponrequestthecurrenttrafficstateofalinkdisplayedonthemapforwhichtheinformationisavailable:• Forroadwaylinks

forwhichfielddataisavailable,mapsshallbeabletodisplaytrafficstatesdeterminedfromthefielddata.

• Forlinksforwhichfielddataisnotprovided,mapsshallbeabletodisplayestimatedtrafficstatesproducedbytheICMSystem,ifsuchinformationisavailable.

• TheICMCoreSystemshallincludeafunctionforuserstodeterminewhatcurrenttrafficstateinformation(density,speed,flow


168

TestREQID



rate,etc.)istobedisplayed.

• Mapsshallindicatewhetherthedisplayedtrafficstatesarederivedfromfielddataoranestimationprocess.

UI-6.8 TheICMCoreSystemshallincludeafunctionforuserstoviewonamaptheprojectedoperationalstatusofroadwaysegmentsunderICMmanagement.



shallbeabletodisplayonmapsforecastedstatesforroadwaylinksforwhichaforecastexists.

627. TheICMCoreSystemshallincludeafunctionforuserstodeterminewhichavailableforecastedtrafficstates(density,speed,flowrate,etc.)aretobedisplayed.

UI-6.9 TheICMCoreSystemshallincludeafunctionforuserstoviewonamaphistoricalstatusdataforroadwaysegmentsunderICMmanagement.



UI-6.10

TheICMCoreSystemshallincludeafunctionforuserstoviewonamaptheoperationalstatusoftrafficmanagementdevicesintheICMinventory.



UI-6.11

TheICMCoreSystemshallincludeafunctionforuserstoviewonamaptheoperationalstatusoftransitservicesofinteresttotheICMSystem.



UI-6.12

TheICMCoreSystemshallincludeafunctionforuserstoviewonamaptheoperationalstatusofmonitoredpark-and-ridefacilities.



UI-6.13

TheICMCoreSystemshallincludeafunctiontoplotonamapthelocationofincidentsandeventsbeingtracked.



shallincludeafunctiontoplotonamapthe


169

TestREQID



locationofallactiveverifiedincidentsandevents.

629. TheICMCoreSystemshallincludeafunctiontoplotonamapthelocationofschedulednear-futureevents.

630. TheICMCoreSystemshallincludeafunctiontoplotonamapthelocationofactiveandnear-futurescheduledroadclosures.

631. TheICMCoreSystemshallincludeafunctiontoplotonamapthelocationofincidentsandeventsawaitingverification.

632. TheICMCoreSystemshallincludeafunctiontoplotonamapthelocationofclosedincidentsoreventsthatarestillsubjecttoresponseplanning(untilcorridorconditionsreturntonormal).

UI-6.14

TheICMCoreSystemshallincludeafunctionforuserstoaccessdetailedincidentoreventinformationfrommapdisplays.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.633. Foreachdisplayed

incident,theICMCoreSystemshallincludeafunctionforuserstoaccessthefollowinginformation:• Incidentstatus(e.g.,

pendingverification,active,closed,etc.)

• Incidenttype• Roadwaysegment

onwhichtheincidentislocated

• Numberoflanesaffected

• Anticipatedzoneofinfluence

• Expectedduration(ifnotclosed)

• Responsibleagency634. Foreachdisplayedevent,

theICMCoreSystemshallincludeafunction


170

TestREQID



foruserstoaccessthefollowinginformationdescribingtheevent:• Typeofevent(lane

closure,specialevent,etc.)

• Eventstatus(scheduled,active,recentlyterminated)

• Roadwaysegment(s)affected

• Numberoflanesaffected

• Anticipatedzoneofinfluence

• Expectedstarttime• Expectedduration

(ifnotclosed)• Responsibleagency

635. TheICMCoreSystemshallprovidethemeanstoaccessfromamapincident/eventinformationbasedontheactivestatusoftheincidentorevent.• TheICMCore

Systemshalldisplayalistofactiveincidentsandeventsthathavebeenverified.

• TheICMCoreSystemshalldisplayalistofactiveincidentsandeventswithanactiveresponseplan.

• TheICMCoreSystemshalldisplayalistofactiveincidentsandeventsthatarependingverification.

• TheICMCoreSystemshalldisplayalistofscheduledeventsexpectedtostartwithinthecurrentday.

UI-6.15

TheICMCoreSystemshallincludeafunctionforuserstoviewonamaptheavailabilityoftrafficmanagementdevicesconnectedtotheICM




171

TestREQID



Environmentforthedevelopmentofresponseplans.

UI-6.16

TheICMCoreSystemshallincludeafunctionforuserstoviewresponseplanelementsonamap.



shalldisplayonamaptherecommendeddetour(s)foreachvehicletype.

637. TheICMCoreSystemshalldisplayonamapthelocationofallfielddevicesassociatedwitharesponseplan.• TheICMCore

Systemshalldisplayonamapthelocationofalltrafficsignalsassociatedwitharesponseplan

• TheICMCoreSystemshalldisplayonamapthelocationofallrampmetersassociatedwitharesponseplan.

• TheICMCoreSystemshalldisplayonamapthelocationofallfixedCMSdevicesassociatedwitharesponseplan.

• TheICMCoreSystemshalldisplayonamapthelocationswhereportableCMSdevicesarerecommendedtobedeployed.

• TheICMCoreSystemshalldisplayonamapthelocationsofallextinguishabletrailblazersignsthataretobeactivated.

• TheICMCoreSystemshalldisplayonamapthelocationsofallHAR


172

TestREQID



stationsthataretobeactivated.

638. TheICMCoreSystemshalldisplayonamapthecontrolactionsassociatedwitheachresponseplanelement.• TheICMCore

Systemshalldisplayonamapthetimingplanthatistobeactivatedateachaffectedsignalizedintersection.

• TheICMCoreSystemshalldisplayonamapthemeteringstrategythatistobeactivatedateachaffectedfreewayon-ramp.

• TheICMCoreSystemshalldisplayonamapthemessagethatistobedisplayedateachaffectedfixedCMSdevice.

• TheICMCoreSystemshalldisplayonamapthemessagesthataretobepostedateachlocationwhereaportableCMSdeviceistobedeployed.

• TheICMCoreSystemshalldisplayonamapthemessageprovidedbyeachactivatedextinguishabletrailblazersigns.

UI-6.17

TheICMCoreSystemshallusealayeredapproachtodisplayinformationonmaps.



UI-6.18

TheICMCoreSystemshallprovideameansforuserstocreateandcustomizevisualizations.



UI-6.19

TheICMCoreSystemshallprovideageospatialapproachtomanagecorridorinformation.




173

TestREQID



shallprovideameansforuserstomodifyassetusageandstate(withintheparametersallowedbytheowningagency)fromgeospatialdisplays.

640. TheICMCoreSystemshallprovideameanstoinitiateincidentconfirmation,responseplandevelopment,responseplanselection,andresponseplanimplementationfromtheprimarygeospatialdisplays.

UI-6.20

Geospatialdisplaysshallincludeafunctionforanimationwheretime-baseddataanalysisisavailable.



8.3.1.9.4.9 Reporting,Charting,andGraphingFunctions

UI-7.1 TheICMCoreSystemshallprovidestandardandcustomizedreportingcapabilities.



shallprovideameanstocreateandsavereportsforuserstoruneitherscheduledorondemand.

642. TheICMCoreSystemshallprovideameanstodisplayreportsonthescreen.

643. TheICMCoreSystemshallprovideameanstoprintreports.

644. TheICMCoreSystemshallprovideameanstosavereportoutputinstandardizedformats,includingpdfandimage-basedformats.

UI-7.2 TheICMCoreSystemshallincludeafunctiontoproducetrafficsummaryreportsforspecificroadwayelements.



UI-7.3 TheICMCoreSystemshallincludeafunctiontoproduceoperationalsummaryreportsforindividualdevicesinoperationwithintheICMcorridor.



UI-7.4 TheICMCoreSystemshall M Corridor Testingtobedefinedwhen


174

TestREQID



includeafunctiontoproducesummaryreportsofsystemactivities.

Management therequirementisaddressed.

UI-7.5 TheICMCoreSystemshalldisplayplot-based(2d,3d,heatmap)visualizationsofcorridorinformation.



shallprovideplot-baseddisplaysofcorridortrafficdensityandvelocityvaluesfromtrafficstatedeterminationsalonguser-selectedroutesin2d(spatialpointintime)andheatmap(spatialandtimevariant).

646. TheICMCoreSystemshallprovideplot-baseddisplaysofcorridortrafficdensityandvelocityforecastsalonguser-selectedroutesin2d(spatialpointintime)andheatmap(spatialandtimevariant).

647. TheICMCoreSystemshallprovideplot-baseddisplaysofcorridorassetavailability(%ofassetsbytypeorgeographicareaoutofserviceordegraded).

648. TheICMCoreSystemshallprovideplot-baseddisplaysofcorridorassetreliability,quality,andaccuracy(assetqualitymetrics,assetreliabilitymetricsvs.timebytypeorgeographicarea).

649. TheICMCoreSystemshallprovideplot-baseddisplaysofcorridorsensordataalonguser-selectedroutesin2d(spatialpointintime)andheatmap(spatialandtimevariant).

650. TheICMCoreSystemshallprovideplot-baseddisplaysofcorridorroadwaycapacity.

651. Plotdisplaysshallincludeafunctionforanimationwheretime-based


175

TestREQID



analysisisavailable.652. Plotdisplaysshallinclude

drill-downcapabilitiestodisplayadditionaldetailwhenavailable.

UI-7.6 TheICMCoreSystemshallprovidemultipletypesofgraphingdisplays.



shalldisplayorganizationinformationinorganizationalcharts.

654. TheICMCoreSystemshalldisplayrulesindecisiontreecharts.

655. TheICMCoreSystemshalldisplayrulesinflowcharts.Plotsshallincludepie,line,bar,andhistogramcharts.

UI-7.7 TheICMCoreSystemshallincludeafunctiontodisplayinformationintables.



shallincludeafunctiontodisplaycorridorassetinventoriesintables.

657. TheICMCoreSystemshallincludeafunctiontodisplayuser-definedroutesintables.

658. TheICMCoreSystemshallincludeafunctiontodisplaycorridortransitroutesandinventoryintables.

659. TheICMCoreSystemshallincludeafunctiontodisplaycorridortransitassetstateintables.

660. TheICMCoreSystemshallincludeafunctiontodisplaycorridormaintenanceactivityandschedulesintables.

661. TheICMCoreSystemshallincludeafunctiontodisplayappropriaterules-basedinformation(i.e.,locationandhoursofschools,eventinformation,facilitylocationandhoursofoperationinformation,


176

TestREQID



etc.)intables.UI-7.8 TheICMCoresystemshall

providevisualizationsshowingdifferencesbetweenplots.



shallprovidedisplaysofcorridortrafficdensityandvelocityvaluesidentifyingdifferencesbetweenthestateofthecorridortrafficatthetimeforecastswereinitiatedandthecurrentestimatedtrafficstate.

UI-7.9 TheICMCoreSystemshallcalculateuponrequesttraveltimesortraveldelaysbetweenselectedpointswithinthecorridor.



UI-7.8 TheICMCoreSystemshallreportonobservedtrafficoperationswithinthecorridor.



UI-7.9 TheICMCoreSystemshallreportonobservedversusestimated/predictedvalues.



UI-7.10

TheICMCoreSystemshallincludeafunctionforsystemuserstorunqueriesontheperformanceofmonitoredroadways.



UI-7.11

TheICMCoreSystemshallincludeafunctionforsystemuserstospecifytheperiodoverwhichhistoricaldataistobeanalyzed.



shallincludeafunctionforsystemuserstospecifytherangeofdatesforwhichhistoricaldataistobeanalyzed.

664. TheICMCoreSystemshallincludeafunctionforsystemuserstospecifythespecifictimeperiodwithinadayforwhichhistoricaldataistobeanalyzed.

665. TheICMCoreSystemshallincludeafunctionforsystemuserstospecifythespecificweekdayswithinagivendaterangeforwhichhistoricaldataistobeanalyzed.


177

TestREQID



666. TheICMCoreSystemshallincludeafunctionforsystemuserstospecifytheintervalwithinagiventimeperiodwithwhichhistoricalstatisticsaretobecalculated(forinstance,every15minutes,1hour,day,month,etc.).

8.3.1.9.5 Post-Incident/EventAnalysisReport

UI-8.1 TheICMCoreSystemshallcreatepost-incident/eventanalysisreportsforincidentsandeventsforwhichresponseplansweregenerated.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.667. Thepost-incident/event

analysisreportshallincludeadetaileddescriptionoftheincidentoreventforwhichapotentialresponsewasevaluated.Minimalinformationtobepresentedincludes:• Typeof

incident/event• Locationwhere

incident/eventoccurred

• Timeincidentoccurredoreventstarted

• Formaldurationofincident/event(uptoincidentclearanceoreventclosure)

• Timewhentravelconditionswerereportedtohavereturnedtonormalfollowingterminationoftheincidentorevent

• Roadwaysegment(s)affectedbytheincident

• Reportedlaneclosuresoneachaffectedroadwaysegment

• Agencyresponsibleformanagingthe


178

TestREQID



incidentorevent668. Foreachresponseplan

evaluated,thepost-incident/eventanalysisreportshallidentifyallelementsincludedintheresponseplan.

669. Thepost-incident/eventanalysisreportshallincludetheresultsoftherulesanalysis,includingsourcedatausedintheanalysis,rulesevaluated,dataqualityevaluation,andfinalrecommendationsoftherulesanalysis.

670. Thepost-incident/eventanalysisreportshallidentifyresponseplanelementsautomaticallyselectedbytheICMCoreSystemandplanelementsthatweremanuallyinputbyagencystaff.

671. Foreachrecommendedresponseplan,thepost-incident/eventanalysisreportshallidentifyanyplanmodificationsthatweremadebyagencystaffaftertheinitialplandevelopment.

672. Foreachrecommendedresponseplan,thepost-incident/eventanalysisreportshalldetailtheresultsofanyrequiredapprovalactionsbyagenciesinvolvedintheimplementationoftheplan.

673. Foreachrecommendedresponseplan,thepost-incident/eventanalysisreportshallidentifywhichplanelementsweresuccessfullyimplemented,whichelementswerenotfullysuccessfullyimplemented,andatimelineoftheresponseplanimplementationand


179

TestREQID



de-escalation.674. Thepost-incident/event

analysisreportshallincludeananalysisoftheaccuracyofthetrafficforecastatthebaseoftheresponserecommendation(“noaction”or“responseplanrecommendation”).

675. Thepost-incidentanalysisreportshallreferenceanyadditionaleventsthatoccurredduringthesameimpactperiodanywhereonthecorridor.

8.3.1.9.6 InterfacetoCaltrans’ATMS

UI-9.1 TheICMEnvironmentshallincludeUIfunctionalitywithintheCaltransATMSforusebyCaltrans’operators.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.676. TheICMEnvironment

shallprovideATMSoperatorswithanATMSinterfaceprovidingtheabilitytocreate,edit,andreviewincident/eventinformation.

677. TheICMEnvironmentshallprovideATMSoperatorswithanATMSinterfaceprovidingtheabilitytoreviewresponseplans.

678. TheICMEnvironmentshallprovideATMSoperatorswithanATMSinterfaceprovidingtheabilitytorejectorapproveresponseplans.

8.3.1.9.7 InteragencyCommunication

UI-9.1 TheICMEnvironmentshallfacilitatecommunicationbetweenstafffromdifferentagencies.



8.3.1.9.8 IntegratedVisualizationandReporting

SI-2.1 TheICMCoreSystemshall H Corridor Willbepartofvendor


180

TestREQID



provideasinglevisualizationandreportinguserinterfaceforallICMCoreSystemOperations.

Management suppliedCMSevaluationandacceptancecriteria.679. TheICMCoreSystem

shallprovideasinglevisualizationandreportinguserinterfaceforcorridortrafficstate.

680. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfacefortrafficforecasts.

681. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceforcorridorassetinventories.

682. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceforcorridorassetinformation.

683. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceforcorridorsensingdata.

684. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceforcorridoranalyticdataandmetrics.

685. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceforresponseplaninformation.

686. TheICMCoreSystemshallprovideasinglevisualizationandreportinguserinterfaceformanagement,maintenance,andoperationsfunctions.

8.3.1.9.9 IntegratedControlFunctions

SI-3.1 TheICMCoreSystemshallprovideintegratedfunctionsformajorfunctionalareas.




181

TestREQID



shallprovideanintegratedsetoffunctionsforcorridormonitoring.

688. TheICMCoreSystemshallprovideanintegratedsetoffunctionsforincident/eventmanagement.

689. TheICMCoreSystemshallprovideanintegratedsetoffunctionsforresponseplanmanagement.

690. TheICMCoreSystemshallprovideanintegratedsetoffunctionsfordatamanagement.

691. TheICMCoreSystemshallprovideanintegratedsetoffunctionsfordecisionsupportcapabilities.

692. TheICMCoreSystemshallprovideanintegratedsetoffunctionsforsystemmanagement.

693. AlltrafficstateassessmentandtrafficforecastingshallbeaccomplishedwithinDecisionSupport.

694. AllICMrulesevaluationshallbeaccomplishedwithinacommonrulesengine.

695. ICMcontrolfunctionsshallbecapableofcontinuousoperationsintheeventofanyindividualsystemfailure.

8.3.1.9.10 IntegratedDataDefinition,Capture,andProcessing

SI-4.1 TheICMCoreSystemshallhaveanintegratedpointofaccesswithconsistentdatadefinitionsandformattingforinternalsystemdataaccessanddataprocessing.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.696. Alldatacollectedbythe

ICMCoreSystemshallbeavailablethroughthecommonICMdataaccessinterfaces.


182

TestREQID



697. AlldatacollectedbytheICMCoreSystemshallbemanagedthroughthecommonICMuserinterfaces.

698. AlldatacollectedbytheICMCoreSystemshallbedefinedandusedinacommonmannerandformatcrossallICMsystemcomponents.

SI-4.2 AlldatacollectedbytheICMCoreSystemshallbemanagedwithintheappropriatesecuritycontext.



SI-4.3 AllICMdatashallbeprocessedinaconsistentmanner,usingdesigntechniquesthatensurethateachdataelementisconsistentlydefined,processed,andcalculatedtoensuretheintegrityandaccuracyofthedataelement.

H DataHub Notpartofsystemtesting.Willbeevaluatedduringpostimplementationreview.

SI-4.4 TheICMEnvironmentcorridordataprocessingandaccessshallbecapableofcontinuousoperationsintheeventofanyindividualsystemcomponentfailure.



8.3.1.9.11 Ownershipofsoftware,hardware,data,andalgorithms

SI-5.1 TheICMEnvironmentshallmaintainownershipofeachdataelementanddatarecord.



SI-5.2 TheICMEnvironmentshallmaintainownershipofrules.



SI-5.3 TheICMEnvironmentshallmaintainownershipofalgorithmsandworkflows.



SI-5.4 TheICMEnvironmentshallmaintainownershipofhardware.



SI-5.5 TheICMEnvironmentshallmaintainownershipofsoftware.




183

TestREQID



8.3.1.9.12 SystemofRecord/LocationforData

SI-6.1 TheICMEnvironmentshalldefineasinglesystemofrecordforeachdataelement.



8.3.1.10 SystemManagement

8.3.1.10.1 SystemAccessandSecurity

SM-1.1

TheICMEnvironmentshallgrantaccessforsystemfunctionalitiestoauthorizedusersonly.



shallallowonlyauthorizeduserstoaccessitsfunctionalities.

700. TheICMEnvironmentshallreportallunauthorizedaccessattempts.

SM-1.2

TheICMEnvironmentshallallowmultipleuserstosimultaneouslyaccesssystemfunctionalitiesfromvariouslocations.



SM-1.3

TheICMEnvironmentshallprovidesecureaccesstoitsfunctionalities.



shallprovideameansforsystemuserstologintoaccesssystemfunctionalities.

702. TheICMEnvironmentshallimplementencryptedmulti-factorauthenticationforsystemaccess.

SM-1.4

TheICMEnvironmentshallprovideasecuremeansofinformationtransmission.



shallimplementencryptedmulti-factorauthenticationforsystemaccess.

704. TheICMEnvironmentshallprovideameanstomaintainsecure


184

TestREQID



connectionsbetweeninternalandexternalsystemcomponents.

705. TheICMEnvironmentshallimplementindustry-standardpoint-to-pointencryptionforallinformationtransmission.

SM-1.5

TheICMEnvironmentshallprovideasecuremeansforstoringinformation.



shallimplement,atanystoragepoint,encryptionofinformationdeemedsensitive.

SM-1.6

TheICMEnvironmentshalltracksystemaccessandusage.



shalltracksystemaccesshistory.

708. TheICMEnvironmentshalltrackauthorizeduseractionhistory.

SM-1.7

TheICMEnvironmentshallallowICMEnvironmentuserstomanageaccesstoICMEnvironmentcomponents.



shallprovideameansforICMEnvironmentuserstocreate/editauthorizeduseraccounts.

710. TheICMEnvironmentshallprovideameansforICMEnvironmentuserstocreate/editauthorizedusergroups.

711. TheICMEnvironmentshallprovideameansforICMEnvironmentuserstoeditauthorizeduserprivileges.

SM-1.8

TheICMEnvironmentshallprovideavalidatedsecureenvironment.



shallimplementcommercialoropen-sourceoff-the-shelfsecuritycomponentsolutionsapprovedbythestakeholders.

713. TheICMEnvironment


185

TestREQID



shallimplementpenetrationtestingfordevelopedsoftware,certificationofpenetrationtestingforpurchasedsoftwaresolutions.

714. TheICMEnvironmentshallimplementsecurityreviewsoftheintegratedsolutionandeachprimarycomponent.

SM-1.9

TheICMEnvironmentshallprotectthesystemenvironmentfromunauthorizedintentionalmodificationorunintentionalmodifications.


WillbepartofvendorsuppliedCMSevaluationandacceptancecriteria.715. TheCorridorTechnical

Manager,followingindustry-standardsecurityprocesses,shalldevelopsecurityprocedures.

716. TheCorridorTechnicalManagershalldesignateanITSecurityOfficerfortheICMEnvironmentwhoshallhaveresponsibilityforthesecurityoftheICMEnvironmentanditsoperations.

717. TheITSecurityOfficershallimplementsecurityprotocolsandprocessesfortheICMEnvironment.

718. TheITSecurityOfficershallconductformalreviewsofICMEnvironmentsecurityprocessesataregularfrequencyinaccordancewiththesecurityprotocolsandprocesses,withaminimumfrequencyofquarterly.

719. TheITSecurityOfficershalldirectaformalreviewofICMEnvironmentsecurity,ledbystakeholdersandconsultants,ataregularfrequencyinaccordancewiththesecurityprotocolsandprocesses,withaminimumfrequencyofannually.


186

TestREQID



SM-1.10

TheCorridorTechnicalManagershalldevelopandimplementsecurityprotocolsandprocessestoensuresecureoperationsoftheICMEnvironment.



8.3.1.10.2 ICMSystemHealthMonitoring

SM-3.1

TheICMEnvironmentshallmonitorthehealthstatusofitscorecomponents.



shallincludeafunctiontoperformself-checkswithoutoperatorassistance.

721. TheICMEnvironmentshallreportanyidentifiedoperationalissuewithitscorecomponents.

8.3.1.10.3 SystemReliability

SM-2.8

TheICMEnvironmentshallhaveaservicelevelagreement.



SM-2.9

TheICMSystemshallprovideasystemuptimemetricsreportfortheICMEnvironment.



SM-2.10

TheICMEnvironmentshallallowfordegradedsystemperformanceintheeventofcomponentfailure.



SM-2.11

TheICMCoreSystemshallhaveaSystemRecoveryPlan.



SM-2.12

TheICMEnvironmentshallimplementredundantcriticalsystemcomponentdesign.



SM-4.1

TheICMEnvironmentshallbeavailable24hoursaday,7daysaweek.

H CorridorManagement/DSS/DataHub

722. LongevitytestfordatahubandDecisionSupportcanworkforaweekorlonger.

Longevitytest

SM-4.2

TheICMEnvironmentshallbeavailable85%ofthetimeduringnormaloperation,notincludingroutinemaintenanceandoutagesduetofactorsbeyondthe




187

TestREQID



controlofsystemusers.SM-4.3

AlltrafficmonitoringdevicesconnectedtotheICMEnvironmentshallbemaintainedingoodoperationalcondition.



SM-4.4

AlltravelerinformationdevicesthatmaybeusedbytheICMEnvironmentshallbemaintainedingoodoperationalcondition.



8.3.1.10.4 SystemMaintenance

SM-5.1

TheICMEnvironmentshallmaintainabackupofitscoreoperatingparameters.


723. Verifythereisabackupandfrequencyofbackupscanbeconfigured.

724. TheICMEnvironmentshallstoreabackupofthesysteminventoryandconfigurationparametersonceperday.

725. TheCorridorTechnicalManagershallhavetheabilitytospecifythefrequencyofsystembackups.

SM-5.2

TheICMEnvironmentshallnotberequiredtoruncontinuouslywithoutmaintenance.



SM-5.3

MaintenanceofICMEnvironmentelementsshallbetheresponsibilityoftheagencyowning/operatingeachelement.



SM-5.4

AlltrafficsensorsprovidinginformationtotheICMEnvironmentshallbemaintainedandcalibratedaccordingtothemanufacturers’specifications.



SM-5.5

AllcorridorassetsprovidingautomateddatafeedstoDecisionSupportshallbemaintainedinaccordancewiththemanufacturers’specificationsfortheassets.



SM-5.7

ICMEnvironmentoperatorsshalldevelopandmaintainalistofcriticalelementsthatshouldreceivemaintenancepriorityshouldtheyfail.




188

TestREQID



SM-5.9

TheICMEnvironmentshalllogallreceivedalertsandnotificationsregardingsystemsoperations.


726. Verifylogsofallreceivedalertsandnotification/errors.

SM-5.10

TheICMEnvironmentshalllogallmaintenance-relatedactivitiesconductedondevicesconnectedtothesystem.



8.3.1.10.5 SoftwareMaintenanceandUpdates

SM-6.1

TheICMEnvironmentsoftwareshallreceiveregularupdates.



SM-6.2

TheCorridorTechnicalManagershallproduceanannualreportofsystemsoftwaremaintenance,providingayearinreviewofthepreviousyear,andaplanforthecomingyearofsoftwaremaintenanceandbugfixactivities,schedule,andbudget.



SM-6.3

TheICMEnvironmentshallmaintainamanagedrepositoryofsoftwareconfigurationchangesandactivities.



8.3.1.10.6 SystemUpgrades

SM-7.1

TheICMEnvironmentshallhavea5-yearsystemupgradeplan.



SM-7.2

TheICMEnvironmentshallhaveanannualupgradeplanthatidentifiesthesystemupgradesfromthe5-yearplanthatwillbeimplementedwithinthenextyear.



SM-7.3

TheCorridorTechnicalManagershalldevelopasystemofgovernancetoensureeachproposedsystemupgradereceivestheappropriatepriorityandreflectstheneedsofallcorridorstakeholders.



SM-7.4

TheCorridorTechnicalManagershallensuresystem


Notpartofsystemtesting.Willbeevaluatedduringpost


189

TestREQID



upgradesaredeveloped,delivered,andimplementedaccordingtothebudgetandplanningidentifiedintheannualupgradeplan.

implementationreview.

SM-7.5

TheCorridorTechnicalManagershallprovideupdatestothe5-yearandannualupgradeplanswhenchangesareidentifiedandapprovedaccordingtothegovernancesystemofthecorridor.



SM-7.6

Allsystemupgradesshallbemanagedandimplementedinaccordancewiththeindustrystandardsappropriatetothespecificupgradeelements.



8.3.1.10.7 SupportingDocumentationandTraining

SM-7.7

TheICMEnvironmentshallhavedocumentationofitsoperationsandmaintenance.



SM-7.8

TheICMEnvironmentshallprovideameansforsystemuserstoaccessrelevantsystemdocumentationwhenloggedintothesystem.



SM-7.9

TheCorridorManagerandCorridorTechnicalManagershalldevelopatrainingprogramfortheICMEnvironmentandICMCoreSystem.



Thispageleftblank

intentionally


190

9. ReferenceDocumentsCommonLinks-CC.htmI-210Pilot-ProjectManagementPlanI-210Pilot-SystemRequirementsI-210PilotHigh-LevelDesignhttps://connected-corridors.berkeley.edu/resources/document-library


191

Thispageleftblank

intentionally


192

10. DefinitionofTermsTerm Definition

Alert NotificationsentbytheICMsystemtoindividualsorunits.Alertsmaybedisplayedonscreen,sentbyemail,textmessage,radiomessage,ortelephone.

Archive Datathathasbeenstoredforhistoricalpurposesandcanberetrieveduponrequest,usuallytoalocationandusingastoragemethodthathaslargecapacityandslowerretrievaltimes.

AreaofImpact(areaofinfluence)

Theroadnetworkelementsimpactedbyanincidentorevent.

Asset SeeCorridorAsset.

AssetInventory Aninventoryofcorridorassetstakenatanypointintime.Assetinventoryincludeslocationsoffixedpositionassets,andtypesofcorridorassets.Canbespecifiedforatypeofassets,suchasintersectionsignalassetinventory.Alsoincludestheattributesofeachindividualasset,suchasintersectionorrampmetersignalcapabilitiesandcurrentlyavailablesignal/rampmeterplans.

AssetState Theconditionofacorridorassetatapointintime.Thisconditionincludesworkingstate(usuallyoperational,failed,orsomedegradedoperationalstate),locationofmobileassets,signalorrampmeterplanthatisinoperationatthatpointintime,andallmostrecentdatareceivedbytheassetatthatpointintime.

Authentication Verifyingauser'sidentity.

Authorization Verifyingauser'spermissionstoviewspecificdataelementsorperformspecificfunctions.

Availability Adescriptionofwhetheranassetisavailableforuseinaresponseplanornot.

BackwardChainingRules

Rulesthataredefinedsothataspecificgoalisspecified,andthepossiblealternativesthatwillachievethatgoalareidentifiedbyexecutionoftherule.ApotentialICM-relatedexamplewouldberulesthataredefinedtocreatealistofalternativeroutesbetweentwodefinedpointsandsetlimitationsonwhatroadlinkscanbeusedatvarioustimesfortheroutecreation.Inthisexample,thegoalisaroutebetweenthetwopoints.Therulesareexecutedtofindallthepossiblealternatives,essentiallyworkingbackwardstofindsolutionsthatfittherulesgiventoachievethegoal.

CaltransATMS AdvancedTrafficManagementSystem(ATMS)softwaretool,whichprovidesreal-timeinformationonhighwayconditionstodetecttrafficincidents,managetheflowoftraffic,anddisseminatetravelerinformation.ATMShelpsCaltransreducecommutingtimes,maximizeroadwaycapacity,andgenerallyprovidesafertravelingroutes.Italsoprovidesoperatorswithunifiedaccessandcontroltomultipletypesofroadwaydevicesratherthanhavingtooperatedisparatesystems.

CMS Changeablemessagesign.Includesbothfixedandmobiledevices.

CMS CorridorManagementSystem

ConfigurationManagement

Maintainingatimelineofchangestoanentity,ensuringtraceabilityofchangesintime,content,andauthorofthechange.

ContactDetails Informationforaspecificindividualororganizationalunit,includingnames,phonenumbers,emailaddresses,physicaladdress,specifictothetypeofcontactmethodsavailablefortheindividualorunit.


193

Term Definition

CorridorAsset AnycorridorelementavailableforusewithinaresponseplanorthatprovidesinformationtotheICMSystem.Assetsincludethefollowingtypesofelements:

• Intersectiontrafficsignals• Rampmeters• Organizationalunitsorindividuals(peopleresources)• Equipment• MobileorstationaryCMSelements• Trafficsensorsandothermeasurementdevices• Communicationelements(511,HAR,thirdpartyinformationproviders)• Parkingfacilities• Transitelements

CorridorState Informationdescribingthestateofthecorridorataspecificpointintime.Stateinformationincludes:• Corridorroadnetworkclosures• Corridorroadnetworklaneblockages• Incidentinformation• Eventinformation• Assetinventory• Assetstate• Sensorinformation• Transitinformation• Transitstate• Trafficconditions(density,flow,velocity)ontheroadnetwork• Responseplanscurrentlyimplementedorintheprocessofbeingimplemented

CurrentTrafficState

Determiningavalueoftrafficdensity,flow,andvelocityforeachlinkintheroadnetworkatthecurrenttimeandwiththedataavailableatthecurrenttime.Alsoincludesvaluesforcurrentturnvolumesandratiosateachturnmovementwithintheroadnetwork.

DataHub AcorecomponentoftheICMsystemwhichhasprimaryresponsibilityforreceiving,processing,storing,andprovidingdataforallICMsystemcomponents.

DataQuality AmeasureofthequalityofdatabeingreceivedbytheICMSystem.Factorsconsideredindataqualityofaspecificassetortypeofassetsinclude:

• Percentofworkingassets• Individualassetstate,includinglevelofassetdegradation• Percentoftimereliabledataisprovidedbytheasset• Specificfilteringoralgorithmicverificationofincomingdataspecifictotheassetorassettype

DataRestoration Restorationofdatatoserviceintheeventofsystemorcomponentfailure.

DecisionSupport AcorecomponentoftheICMSystem,providingtrafficconditions,incidentandeventinformation,forecastsoftraffic,proposedresponseplansandassociatedtrafficforecasts,assetinventoriesandassetavailability,maintenanceinformation,organizationalinformation,roadnetworkconditions,andpreviouscorridorplanningandstudyinformationtouserstosupportcorridoroperationsanddecisionmaking.

Delay Ameasureofthetypicaltimeatravelerwouldexperiencealongarouteoverandabovethetimethetravelerwouldexperienceatfree-flowtrafficconditions.

Demand Ameasureoftrafficdemand(flow)atanentrancetotheroadnetworkorbetweenspecifyentryandexitpoints.

Deterministic Asolutiontoanalgorithmorruleexecutionforwhichtheexecutionofthealgorithmorrule,giventhesameinputdata,willalwaysprovidethesameansweratanypointintime.

DeviceState SeeAssetState.

SystemRecoveryPlan

Aplandevelopedthatprovidesprocedures,operations,andactionsthataretakenintheeventofsystemfailureorlossofcapabilities,includinganyrequiredsystemshutdownprocedures,dataprotectionactions,systemanddatarecoveryactions,proceduresforrestorationofthesystemtooperationalstate,andpost-eventactionstobetaken.

Trailblazer Localstreetsigns(“Trailblazer”signs)willactivatetohelpyounavigatearoundanincidentifyouexitthefreewaytodetouraroundtraffic


194


195

Thispageleftblank

intentionally