i-210 pilot system requirements: job descriptions and duties… · 2019. 12. 17. · i-210 pilot:...

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

I-210 Pilot System Requirements: Job Descriptions and Duties/TasksDecember 23, 2016

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.

SystemRequirements:JobDescriptionsandDuties/Tasks

ii

Thispageleftblankintentionally


iii


iv

TABLEOFCONTENTS

TableofContents ................................................................................................................................ iv

1. Requirements:JobDescriptionsandDuties/Tasks ..........................................................................1

2. CorridorChampion(s) .....................................................................................................................2

2.1. InstitutionalSupport ............................................................................................................... 2

2.2. StrategicIncident/EventResponsePlanning........................................................................... 2

3. CorridorManager ...........................................................................................................................3

3.1. InstitutionalSupport ............................................................................................................... 3

3.2. CorridorMonitoring ................................................................................................................ 5

3.3. StrategicIncident/EventResponsePlanning........................................................................... 6

3.4. Real-TimeIncident/EventMonitoring..................................................................................... 7

3.5. Real-TimeResponsePlanning ................................................................................................. 8

3.6. ResponsePlanImplementation .............................................................................................. 8

3.7. DataManagement ................................................................................................................ 10

3.8. DecisionSupport ................................................................................................................... 10

3.9. CoreSystemUserInterface................................................................................................... 10

3.10. SystemIntegration ................................................................................................................ 11

3.11. SystemManagement ............................................................................................................ 11

4. CorridorTechnicalManager .........................................................................................................12

4.1. InstitutionalSupport ............................................................................................................. 12

4.2. corridorMonitoring .............................................................................................................. 12

4.3. StrategicIncident/EventResponsePlanning......................................................................... 13

4.4. Real-TimeIncident/EventMonitoring................................................................................... 13

4.5. DataManagement ................................................................................................................ 13





5. CorridorDataAnalyst ...................................................................................................................17


5.2. corridorMonitoring .............................................................................................................. 17

5.3. DataManagement ................................................................................................................ 18


v


6. TrafficEngineers...........................................................................................................................20

6.1. CorridorMonitoring .............................................................................................................. 20



6.4. Real-TimeResponsePlanning ............................................................................................... 23

6.5. ResponsePlanImplementation ............................................................................................ 23


7. DataAnalysts ...............................................................................................................................25




7.4. DataManagement ................................................................................................................ 26


8. SoftwareEngineers.......................................................................................................................28






8.6. DataManagement ................................................................................................................ 30





9. ElectricalEngineers.......................................................................................................................35


10.DatabaseAdministrators ..............................................................................................................36




10.4. DataManagement ................................................................................................................ 37



vi



11.Stakeholders ................................................................................................................................39







11.7. DataManagement ................................................................................................................ 43



11.10. SystemIntegration............................................................................................................. 44

11.11. SystemManagement ......................................................................................................... 44

12.MaintenanceStaff ........................................................................................................................46



13. ITSupport.....................................................................................................................................47

14. ITSecurity ....................................................................................................................................48


15.TransportationManagementCenter(TMC)andLocalTrafficControlSystem(TCS)Operators ......49



16.TransitFieldSupervisors(Rail,Bus) ..............................................................................................50



17.PublicInformationOfficers(PIO) ..................................................................................................51



18.FirstResponders...........................................................................................................................52




vii


19.OutreachandCommunicationsManager......................................................................................53


I-210Pilot:JobDescriptions

1

1. REQUIREMENTS:JOBDESCRIPTIONSANDDUTIES/TASKS

ThisdocumentliststheresponsibilitiesofeachjobroleidentifiedintheSystemRequirementsfortheI-210Pilot.Thejobrolesare:

• CorridorChampions • MaintenanceStaff

• CorridorManager • ITSupport

• CorridorTechnicalManager • ITSecurity

• CorridorDataAnalyst • TrafficManagementCenter(TMC)Operators

• TrafficEngineers • TrafficControlSystem(TCS)Operators

• DataAnalysts • TransitFieldSupervisors

• SoftwareEngineers • PublicInformationOfficers

• ElectricalEngineers • FirstResponders

• DatabaseAdministrators • OutreachandCommunicationsManager

• Stakeholders

For each role, the responsibilities are grouped by requirement type (Institutional Support, StrategicResponse Planning, Data Management, etc.). The intent is to provide a way to understand theKnowledge,Skills,andAbilities(KSAs)neededforeachjobandtotracethejobfunctionsdirectlytotheSystemRequirements.

Stakeholdersdecidehowtheseroleswillbefilledattheirparticularagencies.Noteveryagencywillhaveeveryrole,andspecificjobtitlesmayvaryfromagencytoagency.


2

2. CORRIDORCHAMPION(S)

TheCorridorChampion is the individual inanorganizationwho leadsandadvocates for theprogram,secures thesupportandparticipationof thestakeholdersandotheragencies throughout theprocess,and acquires resources within the major organizations participating in the Integrated CorridorManagement(ICM)process.

2.1. INSTITUTIONALSUPPORT

InstitutionalSupportfocusesonstrategicplanningandonhoworganizationsandpeoplearestructured,funded,motivated,andinformedinordertoexecutestrategicplans.

Responsibility

1. Resolveproblemsinmanagementstructureandprocesses.Assistasneededwithongoingmanagementfunctions.

2. Resolvecommunicationbreakdownissues.

3. Ensureagreementsaresignedandfollowed.

4. Resolveoutreachandcommunicationsissues.

2.2. STRATEGICINCIDENT/EVENTRESPONSEPLANNING

StrategicResponsePlanningmeansensuringthatresponseplansforincidents/eventscanbedesigned,developed,reviewedandtested.

Responsibility

1. WithstakeholdersandtheCorridorManager,determinewhyquarterlyresponseplananalysismeetingsarenotbeingheldorattendanceislow,andremedythecauses.


3

3. CORRIDORMANAGER

TheCorridorManagerensuresthattheIntegratedCorridorManagement(ICM)processandprojectaresuccessful. This is the most important role described in this document and requires organizational,managerial,andtechnicalskillsandawareness.TheCorridorManageristheprimarypointofcontactforcorridorplanning,operations,data,maintenance,andoversightandwillmakedecisionsforthegoodofthecorridorthatmayormaynotbepartofthejobdescription/tasks.ThisroletouchesallareasoftheSystemRequirements,including:

• InstitutionalSupport• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeIncident/EventMonitoring• Real-TimeResponsePlanning• ResponsePlanImplementation• DataManagement• DecisionSupport• CoreSystemUserInterface• SystemIntegration• SystemManagement


InstitutionalSupportfocusesonstrategicplanningandonhoworganizationsandpeoplearestructured,funded,motivated,andinformedinordertoexecutestrategicplans.Therequirementsdocumentoftenstatesthatthefollowingjobresponsibilitieswillbecarriedout“inconsultationwithstakeholders.”Wehavenotincludedthosewordsinthisdocument.

Responsibility

1. Post-LaunchCorridorStrategicPlan

a. Overseethedrafting,review,approval,andmaintenanceoftheCorridorStrategicPlanfordatacollection,corridorcontrol,andperformancemetriccalculation.

b. DetermineiftheCorridorStrategicPlaniscompleteandhaveitapprovedbythestakeholders.

c. Reviewchangestothecorridornetwork,newtechnologies,andnewgovernmentalrequirementsinordertodetermineanyappropriatechangestotheStrategicPlan.

d. ResolveStrategicPlandeficiencies(withappropriateassistance).

e. EnsuretheexistenceofassetsanddatadefinedintheStrategicPlan.Thismayinvolvepurchasingorupgradingofassetsand/ordata.

2. CorridorAssets

a. TrackanticipatedchangestotheICMcorridor’sroadwaynetwork,includingfreewayramps,arteriallanes,intersections,origin-destinationcenters.

b. TrackanticipatedchangestotheICMcorridor’stransitnetworks,includingrail,express/commuterbuslines,localbuslines.


4

Responsibility

c. TrackanticipatedchangestotheICMcorridor’strafficcontroldevices(trafficsignals,rampmeters,others).

d. Trackrequiredmaintenancefortrafficmanagementdevices.

e. DeterminewhenandwheretrafficmanagementdeviceswouldbeneededtoadequatelysupportICMsystemoperations.

f. Trackanticipatedchangestothecorridor’stravelerinformationdevices(CMS,extinguishabletrailblazersigns,etc.).

g. Trackrequiredmaintenancefortravelerinformationdevices.

h. DeterminewhenandwheretravelerinformationdeviceswouldbeneededtoadequatelysupportICMsystemoperations.

i. Trackrequiredchangestoexistingsensorsandsensorlocations.

j. Trackrequiredmaintenanceforsensors.

k. DeterminewhenandwherenewsensorsareneededtoadequatelysupportICMsystemoperations.

3. ResponsePlans

a. Trackproposedresponseplancomponentadditionsanddeterminewhethernewormodifiedtrafficmanagementdevicesareneededtofulfilltheseadditions.

b. Trackproposedresponseplancomponentadditionsanddeterminewhethernewtravelerinformationdevicesareneededtofulfilltheseadditions.

c. Trackproposedresponseplancomponentadditionsanddeterminesensinganddatarequirementsneededtofulfilltheseadditions.

4. Metrics

a. TrackanticipatedchangestothemetricsthatmustbeprovidedbytheICMsystem.

b. Trackanticipatedgovernmentalrequirementsforcollectingperformancemetrics.

c. Reviewtheacceptabilityandusefulnessofexistingmetricsanddeterminechangesneededtothemetricsproduced.

5. Requirements

a. Determinerequirementsfornewmetrics,includingtheneedforneworexistingdata,sensing,andalgorithms.

b. TrackproposedneworupdateduserrequirementsfortheICMsystem.

6. OrganizationsandPersonnel

a. WiththeOutreachandCommunicationsManager,setupandmaintainaConnectedCorridorsSteeringCommittee,TechnicalandOperationalAdvisoryCommittee,andothercommitteesasneeded.

b. Createandmaintainamanagement-levelorganizationchartofallprojectstakeholders.

c. Reviewcurrentstaffversusneededstaffandworkwithstakeholderstoresolvediscrepancies.

d. Keepanup-to-dateinventoryofjobdescriptionsrelatedtotheICMoperations.

e. DeterminewhetherpersonnelinothercorridoragenciesshallbeaddedtothelistofICMsupportpersonnel.

f. WiththeOutreachandCommunicationsManager,developanorganizationalchartidentifyingcommunicationcontacts.

g. IncoordinationwiththeOutreachandCommunicationsManager,surveypersonnelandtheirmanagerstodetermineifpersonnelunderstandICMandtheculturalchangesitrequires.


5

Responsibility

h. Incoordinationwithinvolvedagencies,determinewhetherICMsupportpersonnelatotheragenciesshallreceivetrainingonICMoperations.

7. MaintainaRiskRegister,managetherisksdefinedinit,ensureitisdiscussedinthemonthlymeetingsand/orconferencecalls,keepituptodate.

8. Establishquarterlymeetingstokeepallstakeholdersupdatedonsystemandcorridoractivities.

9. Lead(ordelegatearepresentativetolead)updatemeetingsorteleconferences.

10. WiththeOutreachandCommunicationsManager,followuponinformationrequestsabouttheICMsystem.Forwardrequeststootherstakeholdersforcommentorresponsewhenneeded.

11. WiththeOutreachandCommunicationsManager,overseethedevelopmentofapplicationsforfunding,tracktheprogressofsubmittedfundingapplications,anddevelopatrackingsystemtomanageapprovedfundingsources.

12. Determinewhichparticipatingagenciesneedtoreviewprojectdocumentsandprovidecommentsonthem.Determineifotheragenciesneedtoreviewandcomment.

13. Third-PartyRelationships

a. Incoordinationwithstakeholders,managethird-partyrelationships.

b. Incoordinationwithstakeholders,developastrategyforacquiringreal-timeand/orhistoricaldatafromthird-partyprobedataproviders(INRIX,HERE,orothers).

c. Incoordinationwithstakeholders,developastrategytosharedatawithWazeandothertravelinformationproviders.

d. Incoordinationwithstakeholders,purchaseordevelopcontractsrelatedtothird-partydata.

e. Incoordinationwithstakeholders,determinewhichfunctionsshallbeoutsourcedtocontractors.

f. Incoordinationwithstakeholders,developandmaintaincontractswithcontractors.

g. Incoordinationwithstakeholders,draftcontractsforprovidingdatageneratedbytheICMEnvironmenttothird-partyentities.

h. Incoordinationwithstakeholders,maintainpositiverelationshipswithvendorsandcontractors.

i. Periodicallyreviewthird-partypurchasingchoicesandcontracts.

3.2. CORRIDORMONITORING

This function is tasked with determining the state of the corridor and using this state to accuratelycalculateandreportcorridorperformancemeasures.

Responsibility

1. WorkwithTrafficEngineerstoensurethatthedefinitionofthetransportationnetworkisaccurateanduptodateinalllocationswithintheICMCoreSystem,includingtheestimationandpredictionfunctions,allrulesreferencingnetworkconfiguration,userinterfacemaps,networkanomalyfunctions,metricsthatmayhaveconstantsbasedonnetworkconfiguration.

2. Ensureanychangestodesignatedreroutesaroundincidentsoreventsarecommunicatedtoallsystemstakeholders.


6


StrategicResponsePlanningmeansensuringthatresponseplansforincidents/eventscanbedesigned,developed,reviewedandtested.

Responsibility

1. Leadincident/eventresponseplanning.

2. DeterminethepercentageoftimethatappropriateTrafficEngineersarepresentforresponseplanningsessions;workwithstakeholderstoresolveattendanceissues.

3. Determineandensurerulesexist.

a. Determineandensurerulesexistforincidentdetection.

b. Determineandensurerulesexistforincidentseverity.

c. Determineandensurerulesexistforzoneofinfluence.

d. Determineandensurerulesexistforspecialsituations.

e. Determineandensurerulesexistforbuildingresponseplansfromcomponents.

f. Determineandensurerulesexistforselectingaresponseplanforimplementation.

g. Determineandensurerulesexistforsendingresponseplaninstructionstocorridorassets.

4. Ensurethatstakeholdershaveidentifiedanddefinedallresponseplancomponentsneededtomanageincidentsandevents;determine,withTrafficEngineers,thepercentageofrequiredresponseplancomponentsthataredefinedandlisted.

5. Inconsultationwithallrelevantstakeholders,determinetheinformationtobesentto511services,HARstations,andthird-partyprovidersaspartofresponseplans.

6. Post-Incident/EventReview

a. Ensurethatreportssummarizingtheresultsoftheincidentresponseplananditseffectsoncorridorperformancearegeneratedaftereachincidentoreventinthecorridorforwhicharesponseplanwasgenerated.

b. Conductapost-incidentanalysisreviewwithallaffectedagencieswithinoneweekofeachsignificantevent.

c. Aftereachincident,unscheduledevent,orplannedevent,incoordinationwithTrafficEngineersandotherstakeholders,reviewtheselectedresponseplancomponents,includingtimingplans,anddetermineifanyaremissing,inappropriate,orneedtobechanged;updatethecomponentlistasnecessary.

d. Asthetransportationnetworkchanges,workwithTrafficEngineerstoupdatethelistofresponseplancomponents.

7. MockIncidents

a. WithTrafficEngineers,determinetheproperamountoftestingneededformockincidentsandresponseplans,andensurethetestingtakesplace.

b. EnsurethatTrafficEngineerscreateandrunthemockincidents.

8. QuarterlyReview

a. ConductaquarterlyreviewoftheoperationaleffectivenessoftheICMEnvironment.

b. Aspartofthequarterlyeffectivenessevaluation,assignascoretotheobservedeffectivenessofresponseplanningactivities.Scorecorridorperformancebasedontheabilityofimplementedresponseplanstoreducedelayincurredbytravelerswithinthecorridoronaquarter-to-quarterandayear-to-yearbasis.ScoretheperformanceoftheDecisionSupportmodulebasedonitsabilitytoselectplansthatimprovecorridorresponse


7

Responsibility

toincidentsandevents.Supporteachpublishedscoreevaluationwithadequatefielddata.

c. Ensurequarterlystakeholdermeetingsoccurtoreview/analyzeresponseplanresultsinthecorridor.Keepanupdatedlistofwhowillattend.Ifmeetingsarenotheldorattendanceislow,workwithstakeholdersandCorridorChampion(s)todetermineandremedythecause.

d. Usetheresultsofthequarterlyresponseplananalysestoinfluencecorridorplanningdecisions.

3.4. REAL-TIMEINCIDENT/EVENTMONITORING

Real-timeMonitoringinvolvesensuringthatincidents/eventscanbeaccuratelydetected,identified,andcharacterized,andthatallproperpersonnelarenotified.

Responsibility

1. Incident/EventInformation

a. Determinethepercentageoftimestakeholdersprovidesufficientincident/eventinformation(location,starttime,type,severity,etc.)fortheICMCoreSystemtofullycharacterizetheincident/event.

b. Reviewallincidentsandeventsanddeterminewhendatawasnotprovided.Stakeholders,FirstResponders,andPublicInformationOfficersmustworktogethertoresolvetheissues.

2. WithTrafficEngineers,reviewincident/eventdetectionanddetermineifthesystemisworkingcorrectly.

3. Incident/EventValidation

a. Reportthepercentageofincidentsandeventsthatarevalidated(verifiedasactuallyexisting)bystakeholders.

b. Ensurethevalidationprocessisworkingproperly.Ifanincidentoreventischaracterizedbutnotvalidated,determinewhyandworkwithstakeholderstodeterminearemedy.

4. Incident/EventCharacterization

a. Trackthepercentageofincidentsoreventsthatarenotfullycharacterizedbutstillresultinthegenerationofaresponseplan.

b. ReviewsuchcasesandworkwithSoftwareEngineerstodiagnoseandfixtheproblem.

5. StakeholderNotification

a. Determinethepercentageofproperpersonnelnotifiedthatanincidentoreventhasoccurred.

b. Workwithstakeholderstoensurethe“whotocontact”rulesetisupdatedorthatcontactdetailsarecorrect.

6. UpdatedIncident/EventInformation

a. Determinewhenstakeholdersdidnotprovideupdatedinformation(suchasend-of-incidentnetworkchanges)totheICMCoreSystemduringanincident/event.

b. Workwithstakeholderstoresolveissues;updateprocessesasneeded.

7. WithTrafficEngineers,reviewallterminationrecommendationsprovidedbytheICMsystemforerrors;diagnoseandresolveissuesasneeded.


8

3.5. REAL-TIMERESPONSEPLANNING

Real-timeResponsePlanning requires ensuring that responseplans generatedby the ICM systemarereasonable,accurate,andproperlyapprovedbyappropriatepersonnel.

Responsibility

1. ResponsePlanGeneration

a. WithTrafficEngineers,determinethepercentageofresponseplansthatarecorrectlygenerated.

b. WithTrafficEngineers,determinewhenresponseplansarenotreasonableandwhy.

c. WithTrafficEngineers,determinewhenpredictionresultsarenotcorrect.

d. Reviewtheresponseplanthesystemrecommendsandseeifthechoicewasaccurateandbasedcorrectlyonpredefinedrules.Ifnot,reviewtherulesandrulesenginewithTrafficEngineers.

2. PlanReviewandApproval

a. Determinethepercentageofappropriatestakeholderswhoreviewedandmodifiedresponseplans.Determinewhenplansarenotbeingreviewedandworkwithstakeholderstoidentifyandresolveissueswiththereviewprocess.

b. Alongwithstakeholders,notewhenapprovalrulesarenotfollowedanddeterminewhethertheproblemiswiththerulesorthesoftware;coordinatewithSoftwareEngineerstofixtheproblem.

c. Notethepercentageofstakeholderswhofulfilltheirroleasapproversoftheresponseplan.Ifproblemsexistwithapprovals,contactstakeholderstodetermineiftheproblemisoneofhumanprocess,software,orrules.Dependingontheproblem,stakeholders,SoftwareEngineers,ortheCorridorManagerresolvestheproblems.

3. PlanImplementation

a. Notethepercentageoftimeresponseplanimplementationiscorrectlyinitiated.

b. Determinethepercentageoftimesnewresponseplansaregeneratedduringanincidentorevent;notewhennewresponseplansarenotbeinggenerated.

c. Asneeded,commandtheICMCoreSystemtoterminatearesponseplanningactivity.

4. Off-lineAnalysis

a. Determinethepercentageofincident/eventresponseplansthatwereabletobereviewedbystakeholdersinoff-lineanalysis.

b. WorkwiththeSoftwareEngineers,DataAnalysts,andDatabaseAdministratortoidentifyandresolvepossibleissues.

3.6. RESPONSEPLANIMPLEMENTATION

Implementingaresponseplanrequiresensuringthat instructionsaresentcorrectlytocorridorassets,keeping instructions current as assets change, notifying proper personnel, and tracking and resolvingissues.

Responsibility

1. InstructionOrderandSchedule


9

Responsibility

a. WithTrafficEngineers,determinethepercentageoftimethattheICMCoreSystemcorrectlyidentifiestheassetstoreceiveinstructionsandtheproperorderandtimestheyshouldbesent.

b. WiththeTrafficEngineers,determineinpost-incident/eventanalysiswhereissuesarosewiththeassetstatusorinstructionsand/orresponseplaninstructions;resolveissues.

c. Asassetsandequipmentchangeovertime,workwithTrafficEngineerstomodifytheorderandtimeassetsreceiveinstructions.

2. StakeholderNotification

a. Determinethepercentageoftimeproperpersonnelarenotifiedofresponseplandeployment.

b. Workwithstakeholderstoensurethe“whotocontact”rulesetisupdated.

3. ImplementationOverride

a. Determinepercentageoftimethattheresponseplaniscorrectlycanceled(duetochangedcircumstancesinthecorridorpriortoimplementation).

b. WithTrafficEngineers,determineinpost-incident/eventanalysiswhereplanswereinappropriatelyimplemented.

4. SendingResponsePlanInstructions

a. Determinethepercentageoftimeinstructionsaresenttoassets(bothITSandhumanelementsintheresponseplan).

b. WithTrafficEngineers,determineinpost-incident/eventanalysiswhereissuesarosewithsendinginstructions.

5. InstructionVerification

a. Determinepercentageoftimethatthesystemverifiesthatassetshavereceivedinstructions.

b. WithTrafficEngineers,determineinpost-incident/eventanalysiswhereissuesarose.

6. ChangesinAssetStatus

a. Determinethepercentageoftimethatchangesinassetstatushaveoccurredwhilearesponseplanisinplace,andstakeholdershavebeennotified.

b. WithTrafficEngineers,determineinpost-incident/eventanalysiswherestatuschangesoccurredandtheproperprocesseswerenotfollowed.

7. ReturntoNormalStatus

a. Determinepercentageoftimethatassetsreturntonormalstatuswhenanincidentoreventends.

b. WithTrafficEngineers,determineinpost-incident/eventanalysiswhereassetsdidnotreturntonormalstatus.

8. HistoricalRecords

a. Determinethepercentageoftimethatproperhistoricalrecordsofincidents/eventsandresponseplanimplementationaresavedandavailableforreview.

b. WithTrafficEngineers,noteissuesinpost-incident/eventanalysisanddeterminewhytherewasdifficulty.


10

3.7. DATAMANAGEMENT

Dataanddataqualityisattheheartofdata-drivenperformancemanagement.Datamustbeaccurate,complete,timely,reliablyavailable,storedsafely,andcommunicatedandpresentedconsistently.

Responsibility

1. Aspartofthecontinuousimprovementprocess,usedataqualitystatisticsandtrendstoimprovesystemperformance.

2. Ensureadequatefundingforthedataqualitymanagementprogramandforfundingandexecutionofanycorrectiveactionsrequiredfromdataqualitymanagementactions.

3. WiththeCorridorDataAnalyst,conductquarterlyandannualreviewsofthesystemdata.

4. WiththeCorridorDataAnalyst,ensurethatthequarterlyandannualdatareviewrecommendationsarefundedandexecuted.

3.8. DECISIONSUPPORT

DecisionSupportinvolvesensuringthattheappropriaterulesarecapturedbytherulesengine.

Responsibility

1. WiththeCorridorTechnicalManager,determinethepercentageofdesiredrulesthathavebeencapturedbytherulesengine.

2. Reviewrulesduringpost-incidentresponseplananalysis.

3. Duringpost-incidentresponseplanreview,determineifruleswerenotevaluatedcorrectlybytherulesengine.

4. PeriodicallyreviewtheaccuracyofthetrafficstateestimatesandforecastsproducedbytheDecisionSupportSystem.AtthestartofICMSystemoperations,conductareviewevery2weeks.Overtime,asaccuracyincreases,reviewfrequencycanbespacedtonofewerthanonceevery3months.

5. Initiatecomparisonsbetweenforecastedandfielddataforspecifictrafficforecastsasneeded(forinstance,trafficforecastsproducedonagivendayandtime,orforecastsassociatedwithaspecificincidentorevent).

3.9. CORESYSTEMUSERINTERFACE

Stakeholders interactwith the ICMCoreSystemthroughsoftware-baseduser interfaces.This includesprovidingstakeholdersand,inparticular,firstresponderswithmethodstoeasilyexchangeinformationduringincidents.

Responsibility

1. Determine,throughinterviews,easeofinformationexchange.

2. Observecommunicationduringincidentsanddetermineifcommunicationissuesexist.Ifso,workwithstakeholderstoresolveissues.


11

3.10. SYSTEMINTEGRATION

SystemIntegrationrequiresmonitoringsystemfunctionality,datacontrol,andassetownership.

Responsibility

1. WiththeCorridorTechnicalManager,trackownershipofallcorridorassets—includingdatadefinitions,algorithms,andworkflows,aswellashardwareandsoftwaresystems—anddeterminethepercentageofitemsthathaveowners(anindividualororganization).

2. Ifownershipofanassetisunclear,determinewhowillworkwithstakeholderstoidentifytheowner.

3. Asassetschange,ensure,withtheCorridorTechnicalManager,thateachassethasanowner.

3.11. SYSTEMMANAGEMENT

SystemManagementinvolvesensuringthatthesystemisreliablyoperatedandmaintained.

Responsibility

1. Trackthepercentageofmaintenanceactivities(bothrepairandpreventative)thatareproperlyreportedbystakeholders.

2. Aspartofmaintainingsystemreliability,ensurethatallsensing,measurement,andcontroldevicesusedbytheICMEnvironmentoperatecorrectlyatanygiventime,atthelevelspecifiedintheservicelevelagreement.

3. WiththeCorridorTechnicalManager,developatrainingprogramfortheICMEnvironmentandICMCoreSystem.

4. WiththeCorridorTechnicalManager,conductquarterlyandannualtrainingprogramreviewsandmakeanynecessarychangesinthetrainingprogram.

5. WiththeCorridorTechnicalManager,reviewtheinitialICMtrainingplanandsubmitanewICMtrainingplanonanannualbasis.


12

4. CORRIDORTECHNICALMANAGER

TheCorridorTechnicalManagerensuresthesoftwareandhardwarecomponentsoftheICMsystemaremaintained,upgraded,andfunctioning.ThisroleislinkedprimarilytothefollowingareasoftheSystemRequirements:

• InstitutionalSupport• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeIncident/EventMonitoring• DataManagement• DecisionSupport• CoreSystemUserInterface• SystemIntegration• SystemManagement



Responsibility

1. WiththeCorridorManagerandCorridorDataAnalyst,determineifthestrategicplaniscompleted.

2. WiththeCorridorDataAnalyst,determinethepercentageofrequiredsensingassets,datasources,andperformancemetrics,asdefinedintheStrategicPlan,thatareinplace.

3. WiththeCorridorDataAnalyst,determinethemostimportantmissingassetsordataandworkwithstakeholderstoprovidethemissingitems.



Responsibility

1. Toensurethatthereal-timestatusofcorridorassets(theirhealthandavailability)isavailabletoallstakeholders,reviewanddeterminewhetherthestatusisavailableforallcorridorassets(includingthetransportationnetwork,ITShardwareelements,personnel,vehiclesandsignage,softwareandsupportingservers,andcommunications).

2. WorkwithElectricalEngineersandSoftwareEngineerstodeterminethereasonassetstatusesarenotavailable,andworktobringthembackonline.

3. Toensurethatthereal-timestateofcorridorassets(thecurrentconfigurationofinformationondevices,includingsignalplans,rampmeteringplans,CMSmessages)isavailabletoallstakeholders,determinethepercentageavailabilityofassetstate.


13

Responsibility

4. WorkwithSoftwareEngineersandElectricalEngineerstodeterminethereasonassetstateisnotavailableandresolvetheissues.


StrategicResponsePlanningmeansensuringthatresponseplansforincidents/eventscanbedesigned,developed,reviewed,tested,andreported.

Responsibility

1. WiththeCorridorManager,determinethepercentageofrequiredtimingplansdevelopedanddeployed.

2. Conductweeklyandquarterlyevaluationsoftherulesandtheirexecution.

3. DeterminethepercentageoftimethattheICMCoreSystemisabletocorrectlybuildmockincidentsandevents.



Responsibility

1. Determinethepercentageoftimethatthereal-timeresponseplanningfunctioniscorrectlyinitiated.

4.5. DATAMANAGEMENT


Responsibility

1. DataQuality

a. WiththeCorridorDataAnalyst,developadataqualitymanagementprogramfortheICMEnvironmenttospecifyprocesses,procedures,responsibilities,metrics,andbestpracticesformeasuring,monitoring,andcorrectingdataissues.

b. WiththeCorridorDataAnalyst,developaDataQualityManagementGuideforthedataqualitymanagementprogram.

2. DataOversight

a. WiththeCorridorDataAnalystandrepresentativesfromstakeholdersanddataproviders,serveontheDataGovernanceBoard.

b. Aspartofthequarterlyorannualdatareviews,conductareviewwiththeCorridorData


14

Responsibility

Analystofdatastoredbothinelectronicandnon-electronicformats,anditsavailabilitytousersofthesystem.

3. DataFormats

a. WithDataAnalysts,determinethepercentageofdatastoredinelectronicformat.

b. Toensurethatalldata,wherepossible,willbetransmittedusingTMDD/NTCIP/GTFSformats,workwithDatabaseAdministratorsandSoftwareEngineerstoidentifywhenotherdataformatsarebeingusedandworktoreplacethem.

4. WithDatabaseAdministrators,determinethepercentageoftimeETL(Extract,Transform,Load)functionality—requiredforinterfacingwithexternalsystems—canbeused.

5. Determinethepercentageoftimerequestsfromstakeholdersfordataadditions,removals,orformatchangesarerespondedtopromptly.

6. DataPolicies

a. Developandfollowstandardsfordataarchiving,warehousing,anddeletion.

b. WithDatabaseAdministrators,determinethecompletenessofdatamanagementpoliciesandthepercentageoftimepoliciesarebeingfollowed.

c. Updatethedatamanagementpoliciesandmethodsasdatachangesandvolumesgrow.



Responsibility

1. WiththeCorridorManager,determinethepercentageofdesiredrulesthathavebeencapturedbytherulesengine.

2. WithTrafficEngineers,determinethepercentageofthetimerulesareevaluatedcorrectlybytherulesengine.

3. ReviewthedailyoperationalevaluationreportgeneratedbyDecisionSupportattheendofeachdayprovidingasummaryoftherulesexecutionanddetailsofthespecificrulesoperation.


TheICMCoreSystemincludessoftware-baseduserinterfacesforcreating,viewing,updating,deleting,andreportingondata,aswellasinterfacesformanagingtheprocessofincidentidentification,responseplangeneration,responseplanimplementation,andCoreSystemmanagement.

Responsibility

1. TrackUIfunctionality.

2. Notewheninterfacesarenotworking,displayinginsufficientdata,orpresentingitincorrectly.

3. Determinewheninterfacesneedtobechangedorupdated.

4. WorkwithSoftwareEngineersandDatabaseAdministratorstodiagnoseandresolveissues.


15



Responsibility

1. Monitorthepercentageoffunctions,includingvisualizationandreportingfunctions,accessiblethroughoneintegratedsystem.

2. Trackfunctionality,noteissues,andworkwithSoftwareEngineersandotherpersonnelasneededtodiagnoseandresolveissues.

3. WiththeCorridorManager,trackownershipofallcorridorassets—includingdatadefinitions,algorithms,andworkflows,aswellashardwareandsoftwaresystems—anddeterminethepercentageofitemsthathaveowners(anindividualororganization).

4. Asassetschange,ensure,withtheCorridorManager,thateachassethasanowner.


System Management involves ensuring that the system is reliably operated and maintained. Thisincludes the areas of security, service level agreements,maintenance, training, system recovery, andupgrades.

Responsibility

1. Security

a. Followingindustrystandards,developandimplementsecurityprotocolsandprocessestoensuresecureoperationsoftheICMEnvironment.

b. Ensureonlyauthorizedpersonnelcanaccesssystemassets.

c. DesignateanITSecurityOfficerfortheICMEnvironmentwhoshallhaveresponsibilityforthesecurityoftheICMEnvironmentanditsoperations.

2. ServiceLevel

a. Developandmaintainaservicelevelagreement,incoordinationwithstakeholders.

b. Toensurethesystemisavailableandfunctioninganagreed-uponpercentageofthetime,reviewsystemlogsandup-timereportstodetermineproblemsandhelpresolveissues.

c. Determinethepercentageofsystemactivitylogsthatareproperlymaintained.WithSoftwareEngineers,ensurethatanynewfunctionalityisattachedtoviewablelogs.

3. SystemMaintenance

a. Specifythefrequencyofsystembackups.

b. Monitorthepercentageoftimethatrequestsformaintenance,improvements,andbugfixesareproperlyenteredintothetrackingsystem.WithSoftwareEngineers,performnormalmaintenanceonthetrackingsystem.

c. Developandmaintainalistofcriticalelementsthatshouldreceivemaintenancepriorityshouldtheyfail.

d. Trackassetsundergoingmaintenance(bothrepairandpreventative)bystakeholders;helpresolveissues.

e. Notewhenmaintenancereportingisnotoccurringandworkwithstakeholderstoresolve


16

Responsibility

anyproblems.

f. Validatenon-catastrophicsoftwarebugsreportedbystakeholders;ensureSoftwareEngineersareavailabletofixbugs.

4. Training

a. WiththeCorridorManager,developatrainingprogramfortheICMEnvironmentandICMCoreSystem.

b. WiththeCorridorManager,conductquarterlyandannualtrainingprogramreviewsandmakeanynecessarychangesinthetrainingprogram.

c. WiththeCorridorManager,reviewtheinitialICMtrainingplanandsubmitanewICMtrainingplanonanannualbasis.

d. Noteifindividualsdonotknowhowtoperformtheirfunctions,operatesoftware/hardwaresystems,orarenotawareofproperproceduresduetolackoforinadequatetrainingordocumentation.Workwithstakeholderstoaddressissues.

5. SystemRecovery

a. EnsuretheICMCoreSystemcanrecoverfromcriticalfailuresordisasters.

b. DevelopaSystemRecoveryPlan,incoordinationwithstakeholders;reviewitquarterlyandtestitannually.

c. Workwithstakeholderstoresolvedisasterpreparednessissues.

6. SoftwareUpdates

a. Designateasoftwaredevelopmentandupdateprocess,basedonindustrystandards,forsoftwareupdatesandbugfixes.

b. Developascheduleforsoftwaredevelopmentupdatesandbugfixes,andmaintaintheschedule,providingupdatestothescheduleonamonthlybasis.

c. Developanannualbudgetforsoftwareupdatesandbugfixes,withquarterlyupdates.

d. Produceanannualreportofsystemsoftwaremaintenance,providingayearinreviewofthepreviousyearandaplanforthecomingyearofsoftwaremaintenanceandbugfixactivities,schedule,andbudget.

7. SystemUpgrades

a. Inconcertwithcorridorstakeholders,developandmaintaina5-yearsystemupgradeplan.

b. Ensuretheplanisadequateandapprovedbystakeholders.

c. Createanannualupgradeplanthatidentifiesthesystemupgradesfromthe5-yearplanthatwillbeimplementedwithinthenextyear.Delivertheannualupgradeplanaminimumofsixmonthspriortothefiscalyearstart.

d. Developasystemofgovernancetoensureeachproposedsystemupgradereceivestheappropriatepriorityandreflectstheneedsofallcorridorstakeholders.

e. Ensuresystemupgradesaredeveloped,delivered,andimplementedaccordingtothebudgetandplanningidentifiedintheannualupgradeplan.

f. Provideupdatestothe5-yearandannualupgradeplanswhenchangesareidentifiedandapprovedaccordingtothegovernancesystemofthecorridor.

g. Manageandimplementsystemupgradesinaccordancewiththeindustrystandardsappropriatetothespecificupgradeelements.


17

5. CORRIDORDATAANALYST

Corridor Data Analyst is an extremely important role. It has responsibility for ensuring data qualitywithintheICMenvironmentbyanalyzingcorridordata,settingqualitystandards,ensuringdatameetsthosestandards,identifyingwhenitdoesnot,andworkingwithstakeholderstomeettheirdataanalysisneeds. Overall, Connected Corridors and ICM in general are about using data to manage corridorperformance. ICM requires quality data, well-defined performance measures, and correct metriccalculations—allareasthattheCorridorDataAnalystisresponsiblefor.

DataManagementrequiresbothapurelytechnicalcomponent(i.e.,doesthedatabasework,doesthecommunicationfromthesensorswork,etc.)andadefinitionalandanalysiscomponent.ThedefinitionalandanalysiscomponentistheresponsibilityoftheCorridorDataAnalyst.Thetechnicalcomponentsareshared with the Corridor Technical Manager, database administrators, and software and hardwareengineers. The managerial requirements are shared with the Corridor Manager. A number of thefollowing requirements are shared with those other roles, but the Corridor Data Analyst is primarilyresponsible for overall data management. Thus, those other roles are not listed in the followingresponsibilitiesunlessofparticularimportance.

ThisroleislinkedprimarilytothefollowingareasoftheSystemRequirements:

• InstitutionalSupport• CorridorMonitoring• DataManagement• SystemIntegration



Responsibility

1. Determinethepercentageofrequiredsensingassets,datasources,andperformancemetrics,asdefinedintheCorridorStrategicPlan,thatareinplace.

2. Determinethemostimportantmissingassetsordataandworkwithstakeholderstoprovidethemissingitems.



Responsibility

1. Determinethepercentageoftimethesystemmakeshigh-qualitytrafficmonitoringdataavailabletoallstakeholders(e.g.,freewaycounts/flows,arterialthrough/turningcounts,


18

bus/trainlocations,videodata,etc.).

2. Determinewhentrafficmonitoringdataqualityhasdegradedandwhendataisnotavailable.

5.3. DATAMANAGEMENT


Responsibility

1. Governance

a. DevelopadataqualitymanagementprogramfortheICMEnvironment.

b. DevelopaDataQualityManagementGuideforthedataqualitymanagementprogram.

c. WiththeCorridorTechnicalManagerandrepresentativesfromstakeholdersanddataproviders,serveontheDataGovernanceBoard.

2. Definition

a. Ensurethatthedatadictionaryiscomplete,accurate,anduptodate.

b. Defineandmaintaindataqualityrequirementsandthemethodsforcalculatingthequality.

3. ApplicationofStandards

a. Determinethepercentageofdatathathasappropriatequalitymetrics.

b. Ensurethatalldatahasadataqualityspecification.

c. Determineifdataqualityisbeingmaintained.

d. Ensurethatdataismeetingdataqualityspecificationsatalltimes.

e. Ensurethatprocesses(bothautomatedandhuman)areinplaceandinuseforensuringandmeasuringthequalityofdataandforaddressingdataqualityissueswhentheyarise.

f. Ensurethatthefollowingmetricsareestablished,measured,andmetforalldata:

• maximumtimetodetecterrorsorproblemswithdataquality

• maximumtimetocorrecterrorsorproblems

• meantimetodetecterrorsorproblems

• meantimetocorrecterrorsorproblems

g. Updatespecificationsandcalculationmethodsasdatasourcesandformatschange.

h. Asdataandpersonnelchange,ensurethatdataqualitymeasurementproceduresareinplaceandthatDataAnalystsareavailableandtrained.

4. Reviews

a. Conductaweeklycorridordatareview,usingdataqualitymetricsspecifiedintheDataDictionary.

b. ConductaquarterlydataqualityassessmentforallICMEnvironmentdataelementsandsources.


19

Responsibility

c. Conductquarterlyandannualreviewsofsystemdata,including:

• Measuresofthedataqualityforthequarterandyear

• Statusofthedatadictionary• Achangemanagementreviewofthesystemdatasources,dataprocesses,datahub,andexternallyavailabledataelements

• Datamanagementsystemperformance

• Recommendedactionstoimprovedata,dataprocesses,anddataquality

d. Conductanannualreviewofdataqualitymetricsdefinitionandcalculationmethod.

e. WiththeCorridorManager,ensurethatthequarterlyandannualdataassessmentandreviewrecommendationsarefundedandexecuted.

f. Aspartofthequarterlyorannualdatareviews,conductareviewofdatastoredbothinelectronicandnon-electronicformats,anditsavailabilitytousersofthesystem.

5. DaytoDay

a. Measureandreportonmeantimebetweenfailureforalldataqualitymetrics.

b. PromptlyreportallidentifieddataqualityfailurestotheCorridorManagerandstakeholders.

c. Reportonthestatusofcorrectionsbeingexecutedtoaddressdataqualityfailures.Thisincludesreportingonthetimeneededtoperformthecorrection.

d. Initiateanyactionsrequiredtoaddressissuesidentified,eitherduringsystemoperationorasaresultoftheweeklyreview.

e. Identifyproblemsandworkwithstakeholdersandthird-partyproviderstorefineandupdatethedataqualityrequirementsandcalculationmethods.

f. Analyzestakeholderrequestsfordataadditions,removals,orformatchangesanddeterminewhethertherequestcanbeaccommodatedbyresourcesandwillenhancetheICMfunction.Ifrequestsareappropriate,ensurethemaintenanceisperformed.



Responsibility

1. Determinethepercentageofappropriatedatathatuseacommonsetofdatadefinitions,areprocessedandmanagedconsistentlyacrossallICMcomponents,andarepresentedtousersconsistentlyacrossallICMCoreSystemcomponents.

2. Notewhenintegration/consistencystandardsarenotbeingfollowedandresolvetheproblems.

3. Determinethepercentageofdatathathaveoneandonlyonesystem/accessprotocolofrecord.Identifyandresolveissues.


20

6. TRAFFICENGINEERS

Traffic Engineers fill an essential role in the ICM process. They provide the knowledge required forcreating andmaintaining the response plans, rules, networks, andmodels contained in the DecisionSupportSystem.Theyarealsoresponsibleforreviewingtheresultsoftheapplicationofresponseplanstoincidentsanddeterminingiftheresponseplansworkedasexpected.

Anumberofthefollowingrequirementsaresharedwithotherroles,butifthetaskswillbeperformedprimarilybyTrafficEngineers,thoseotherrolesarenotlistedunlessofparticularimportanceincarryingouttheresponsibilities.


• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeIncident/EventMonitoring• Real-TimeResponsePlanning• ResponsePlanImplementation• DecisionSupport



Responsibility

1. NetworkDefinition

a. WorkwiththeCorridorManagertoensurethatthetransportationnetworkiswelldefinedintheICMsystemanduptodate.

b. Checkforissueswiththeaccuracyofresponseplanpredictions.Ifdiscrepanciesarefound,correctthenetworkdefinitionsasneeded.

2. PerformanceMetrics

a. WithDataAnalysts,determinethepercentageoftimemetricsarecalculatedcorrectly.

b. WorkwithDataAnalystsandSoftwareEngineerstouncoveranyissueswithperformancemetriccalculations.

c. Asnewdatasources/sensorsbecomeavailable,workwithDataAnalystsandSoftwareEngineerstoupdatethemetriccalculationalgorithms.

3. CorridorStateDetermination

a. DeterminetheaccuracyoftheresultsoftheDSSCorridorStateDeterminationfunction.Useobservation,statisticalanalysis,andperiodicexternalevaluationstoidentifyinaccuracies.

b. Asthenetworkanddatasourceschange,workwithSoftwareEngineerstoadjustthealgorithmsandrulesthatperformthecorridorstatedetermination.

4. HistoricalData


21

Responsibility

a. WithDataAnalysts,determinetheaccuracyofhistoricaltrafficpatterns,usingobservationandstatisticalanalysis.WorkwithSoftwareEngineerstoresolveissues.

b. Asnewdatasources/sensorsandnewalgorithmsbecomeavailable,workwithDataAnalystsandSoftwareEngineerstomaintainandupgradethealgorithmsusedtocreatehistoricaldata.



Responsibility

1. Participateindevelopingresponseplans.

2. ResponsePlanComponents

a. Determinedesiredroutestobeusedasdetoursforincidentsandevents.

b. Asneeded,definethepreferreddetourstobeconsideredasfirstpotentialsolutionsinbuildingresponseplans.

c. Asneeded,definetemporaryrestrictionsontheuseofspecificroadwaysegmentsinresponseplans.

d. Determinethesignalizedintersectionswhosetrafficsignaltimingplansmaybechangedduringanincidentorevent.

e. Determinewhichfreewayrampsshallhavetheirmeteringratechangedduringanincidentorevent.

f. Create,maintain,andtesttrafficsignaltimingplans,anddistributethemtothedevicesintheresponseplancomponentlist.

g. Astrafficconditionschange,updateandreverifythesignaltimingplans.

h. Create,maintain,andtestrampmeteringplans,anddistributethemtothedevicesintheresponseplancomponentlist.

i. Determinemessagingequipmentavailableforuseduringanincidentorevent(HAR,fixedCMSs,portableCMSs,extinguishabletrailblazersigns,others).

j. Defineaminimalpercentageofcontroldevices(trafficsignals,rampmeters,changeablemessagesigns)thatshouldbeavailablealongadetourroutesfortheroutetobeconsideredviable.

k. Determinewhatvehiclesareavailableforusetoimplementaresponsetoanincidentorevent.

l. Determinepersonnelavailablefordeploymentduringanincidentorevent.

m. Determinetypicalinformationtobesenttoagencypersonnelrespondingtoanincidentorevent.

n. Determinemessagestobepostedonfixedand/orportableCMSdeviceswhenrespondingtoanincidentorevent.

o. WiththeCorridorManager,determinethepercentageofrequiredresponseplancomponentsthathavebeendefinedandlisted.

3. ResponsePlanRuleCreation


22

Responsibility

a. Definetherules(metricsandthevalueofthosemetrics)tobeusedindeterminingtheexistenceofanincident.

b. Definetherulestobeusedindeterminingtheseverityofanincidentoreventanditszoneofinfluence.

c. Definetherulesforassessingthelevelofimpactofanincidentoreventoncorridoroperations.

d. Definetherulesforbuildingresponseplansfromasetofpossibleresponseactions.

e. Definetherulesforhandlingspecialsituations.

f. Definetherulesforselectingarecommendedresponseplanamongasetofalternateplans.

g. Definetherulesforsendingresponseplaninstructionstocorridorassets.

h. Definetherulesfordeterminingagencypersonnelwhoshouldbenotifiedofaresponseplanningaction.

i. Specifytheconditionsunderwhichtheimplementationofanapprovedresponseplancanbecanceled.

4. RuleandComponentEvaluation

a. Reviewtheincidentdetectionrulestodetermineiftheapplicationoftherulesresultedinthecorrectidentificationofanincidentand,ifnot,determinewheretheerrorlies.Correctanyinaccuraterules.

b. Reviewtherulestodetermineiftheapplicationoftherulesresultedinthecorrectseverityandzoneofinfluencedeterminationand,ifnot,determinewheretheerrorlies.Correctanyinaccuraterules.

c. Reviewthespecialsituationrulesappliedduringincidentsoreventstodetermineiftheirapplicationresultedinthecorrectresponseplancomponentselection.Ifinaccurate,updatetherules.

d. Duringincidentsorevents,reviewtherulesforbuildingresponseplansfromcomponentstodetermineiftheapplicationoftherulesresultedinthegenerationofappropriateresponseplans.Correctanyinaccuraterules.

e. Reviewtheresponseplansselectedduringincidentsoreventstodetermineiftherulesforselectingaplanresultedinthecorrectselections.Correctanyinaccuraterules.

f. Reviewtheexecutionorderofinstructionssenttocorridorassetstodetermineiftherulesforchoosingtheorder/scheduleresultedinthecorrectordering.Correctanyinaccuraterules.

g. Asthecorridorchanges,reviewandupdatetherules.

h. Aftereachincident,unscheduledevent,orplannedevent,incoordinationwiththeCorridorManagerandotherstakeholders,reviewtheselectedresponseplancomponentsanddetermineifanyaremissingorinappropriate;updatethecomponentlistasnecessary.

i. Asthetransportationnetworkchanges,workwiththeCorridorManagertoupdatethelistofresponseplancomponents.

j. Aftereachincident,unscheduledevent,orplannedevent,workwiththeCorridorManagertoreviewthetimingplanstodetermineanychangesneeded.Makethechanges.

5. Testing

a. Createmockincidentsandeventsandreviewtheresultingresponseplans;runtheresponseplansthroughthepredictionsystem;analyzetheresultstodeterminethelikelyeffectivenessoftheplans.


23

Responsibility

b. WiththeCorridorManager,determinetheproperamountoftestingneededforthemockincidentsandresponseplans,andensurethetestingtakesplace.

c. WithSoftwareEngineers,DataAnalysts,andDatabaseAdministrators,identifyproblemsandresolveissuesrelatedtothemockincidentsandevents.



Responsibility

1. DeterminethepercentageoftimetheICMsoftwareproperlyidentifiesincidents.

2. WiththeCorridorManager,reviewincident/eventdetectionanddetermineifthesystemisworkingcorrectly.

3. WithSoftwareEngineers,tuneincidentdetectionalgorithmsandrules.

4. WiththeCorridorManager,reviewthesystem’sincident/eventterminationrecommendationsforerrors;resolveissues.



Responsibility

1. WiththeCorridorManager,determinethroughobservationandanalysisthepercentageofresponseplansthatarecorrectlygenerated.

2. WiththeCorridorManager,determinewhenresponseplansarenotreasonableandwhy.

3. WiththeCorridorManager,determinewhenpredictionresultsarenotcorrect.

4. Ifthesystemchoosesaninaccurateresponseplan,workwiththeCorridorManagertoreviewtherulesandrulesengine.



Responsibility

1. Determinethepercentageoftimethatinstructionsforresponseplanimplementationaresentin


24

Responsibility

thecorrectorderandschedule.

2. Determineinpost-incident/eventanalysiswhereissuesrelatedtoorderandtimearose;resolveissues.

3. Asassetsandequipmentchange,workwiththeCorridorManagertomodifytheorderandtimetheyreceiveinstructions,asneeded.

4. Determineinpost-incident/eventanalysiswhereresponseplanswereinappropriatelyimplemented;updaterulestoresolveissues.

5. Ascorridorassetschange,updatetherulesasneeded.

6. Determineinpost-incident/eventanalysiswhereissuesarosewithsendinginstructionstocorridorassets(bothITSandhumanelementsintheresponseplan)andverifyingthatinstructionswerereceived.

7. Determineinpost-incident/eventanalysiswhereissuesarosewiththesystemmonitoring,andassetscommunicating,anychangesinstatusandnotifyingstakeholdersofthechangeswhilearesponseplanisinplace.

8. Determineinpost-incident/eventanalysiswhereassetsdidnotreturntonormalstatuswhenanincidentoreventends.

9. Noteinpost-incident/eventanalysiswheretheICMsystemdidnotsaveallinformationrelevanttoresponseplanimplementation;determinewhy.



Responsibility

1. WithCorridorTechnicalManager,determinethepercentageoftimetherulesareevaluatedcorrectly.

2. Usingobservation,measurement,andstatisticalanalysis,assesswhetherthecorridorstatedeterminationresultsarecorrect.

3. WithSoftwareEngineers,updateandmaintainthealgorithmsanddatausedtodeterminecorridorstatebasedonchangesinthecorridor.

4. Usingobservation,measurement,andstatisticalanalysis,assesswhetherthefuturecorridorstatepredictionresultsarecorrect.

5. WithSoftwareEngineers,usemodelingskillstoupdateandmaintainthealgorithmsanddatausedtopredictcorridorstatebasedonchangesinthecorridor.

6. Usingobservation,measurement,andstatisticalanalysis,assesswhetherthesystemiscorrectlydeterminingiftrafficiswithinnormalvariabilityforagivendateandtime.


25

7. DATAANALYSTS

Data Analysts are responsible for day-to-day implementation of the data quality standards, ongoingreviewofICMenvironmentdataquality,andinitiationofcorrectiveactions.


• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeResponsePlanning• DataManagement• SystemIntegration



Responsibility

1. PerformanceMetrics

a. WithTrafficEngineers,determinethepercentageoftimeperformancemetricsarecalculatedcorrectly.

b. WatchforunusualmetricsandworkwithTrafficEngineersandSoftwareEngineerstouncoveranyissues.

c. Asnewdatasourcesandsensortypesbecomeavailable,workwithTrafficEngineersandSoftwareEngineerstoupdatethemetriccalculationalgorithms.

2. HistoricalData

a. WithTrafficEngineers,useobservationandstatisticalanalysistodeterminetheaccuracyofhistoricalpatterns.

b. Asnewdatasources/sensorsandnewalgorithmsbecomeavailable,workwithTrafficEngineersandSoftwareEngineerstomaintainandupgradethealgorithmsusedtocreatehistoricaldata.



Responsibility

1. Diagnoseandresolveissueswithexecutingresponseplanrulesforincidentdetection,severity,zoneofinfluence,specialsituations,buildingresponseplans,choosingaplantoimplement,andsendingplaninstructionstocorridorassets.

2. WithTrafficEngineers,SoftwareEngineers,andDatabaseAdministrators,identifyandresolve


26

Responsibility

issuesrelatedtocreatingandexecutingmockincidentsandevents.

3. WithSoftwareEngineersandDatabaseAdministrators,resolveproblemsinthegenerationofafter-incident/eventreports.



Responsibility

1. WorkwithCorridorManager,SoftwareEngineers,andDatabaseAdministratorstoidentifyandresolveissueswithincident/eventresponseplansbeingabletobereviewedandanalyzedbystakeholdersoff-line.

7.4. DATAMANAGEMENT


Responsibility

1. WithDatabaseAdministrators,assisttheCorridorDataAnalystinmaintainingtheDataDictionary,ensuringthatitisaccurateanduptodate.

2. WithDatabaseAdministrators,noteanydiscrepanciesbetweentheDataDictionaryandtheactualdataandresolvethem.

3. Reviewthequalityofdataanddeterminethereasonsforanydeviationsfromdataqualityrequirements.

4. AssisttheCorridorTechnicalManagerwithdeterminingthepercentageofdatastoredinelectronicformat.

5. Notewhendataisnotbeingstoredinelectronicformatandworkwithstakeholders,SoftwareEngineers,andDatabaseAdministratorstostorethedata.

6. Asdatatypesandformatschangeovertime,workwithstakeholders,SoftwareEngineers,andDatabaseAdministratorstoensurethatstoragemethodsareuptodate.

7. WithDatabaseAdministrators,ensureETL(Extract,Transform,andLoad)operationscontinuetoworkwhenexternaldataformatschange.

8. Reviewrequestsfromstakeholdersfordataadditions,removals,orformatchanges;determinetheappropriatenessofthechanges.


27



Responsibility

1. Continuallywatchforcopiesofdatathatarebeingerroneouslyusedassystemsofrecord.WorkwiththeCorridorDataAnalyst,SoftwareEngineers,andDatabaseAdministratorstoidentifyandresolveissues.


28

8. SOFTWAREENGINEERS

SoftwareEngineersinvestigateandremedysoftware-relatedproblems(“bugs”)andprovideupgradesasrequired. A significant and essential percentage of the requirements for the ICM Core System areimplemented using software. It is impossible to maintain a nimble system capable of responding tochangesinthecorridor,newdata,newrequirements,andthegeneralneedsofthecoresystemwithoututilizingsoftwareengineeringexpertise.Inaddition,allsoftwarehasbugs,andthesebugsmustbefixedinatimelyway.


• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeIncident/EventMonitoring• Real-TimeResponsePlanning• ResponsePlanImplementation• DataManagement• DecisionSupport• CoreSystemUserInterface• SystemIntegration• SystemManagement



Responsibility

1. WiththeCorridorTechnicalManagerandElectricalEngineers,determinethereasonassetstatusesarenotavailableandworktobringthembackonline.

2. Whereassetstatusisprovidedthroughautomation,workwithElectricalEngineerstoensurestatusisavailable.

3. WithElectricalEngineers,determinethereasonassetstate(thecurrentconfigurationofinformationondevices,includingsignalplans,rampmeteringplans,CMSmessages)isnotavailableandresolvetheissue.

4. WithElectricalEngineers,maintainsoftwareandhardware.

5. WorkwithDataAnalystsandTrafficEngineerstouncoveranyissueswithperformancemetriccalculations.

6. Asnewdatasources/sensorsbecomeavailable,workwithDataAnalystsandTrafficEngineerstoupdatethemetriccalculationalgorithms.

7. Asthenetworkanddatasourceschange,workwithTrafficEngineerstoadjustthealgorithmsandrulesthatperformthecorridorstatedetermination.

8. WorkwithTrafficEngineerstoresolveissueswiththeaccuracyofhistoricalpatterns.

9. Asnewdatasources/sensorsandnewalgorithmsbecomeavailable,workwithDataAnalystsandTrafficEngineerstomaintainandupgradethealgorithmsusedtocreatehistoricaldata.


29



Responsibility

1. Diagnoseandresolveissueswithexecutingresponseplanrulesforincidentdetection,severity,zoneofinfluence,specialsituations,buildingresponseplans,choosingaplantoimplement,andsendingplaninstructionstocorridorassets.

2. Diagnoseandfixtheproblemswiththebuildingofmockincidentsoreventsusedintestingresponseplans.

3. WithTrafficEngineers,DataAnalysts,andDatabaseAdministrators,identifyandresolveissuesrelatedtocreatingandexecutingmockincidentsandevents.

4. WithDataAnalystsandDatabaseAdministrators,resolveproblemsinthegenerationofafter-incidentorafter-eventreports.

5. Upgradeandmaintainafter-incident/eventreports.



Responsibility

1. WithTrafficEngineers,tunethealgorithmsandrulesusedtoidentifypotentialincidents.

2. WorkwiththeCorridorManagertodiagnoseandresolveproblemswheretheICMsystemgeneratedaresponseplanwithoutafullycharacterizedincidentorevent.

3. Determinewhytheresponseplanningfunctionwasnotinitiatedonceanincident/eventwascharacterized;resolvetheproblem.



Responsibility

1. Ensurechangesinrulesanddataareproperlyhandledbytheresponseplanbuildingfunction.

2. Resolvesoftwareissueswiththegeneration,evaluation,andrecommendationofresponseplans.

3. ResolveproblemswheretheresponseplanapprovalprocessisnotfollowedbytheICMsystemorstakeholdersbecauseofsoftwareissues.

4. Determinewhyresponseplanimplementationwasnotproperlyinitiatedandresolvetheissues.

5. Trackdownandresolveissueswiththesystemnotperiodicallygeneratingnewresponseplanswhiletrafficconditionswarrant.


30

Responsibility

6. WorkwiththeCorridorManager,DataAnalysts,andDatabaseAdministratorstoidentifyandresolveissueswhereincident/eventresponseplansareunabletobereviewedandanalyzedbystakeholdersoff-line.



Responsibility

1. Asassetsandequipmentchange,modifythewayinstructionsaresenttohardwareandsoftwareassets,asneeded.

2. Asassetsandequipmentchange,updatethesoftwaretoensureandverifythatassetshavereceivedinstructions.

3. Ascorridorassetsandpolicieschange,updatesoftwareasneededtoensureassetsreturntonormalstatuswhenanincidentoreventends.

4. WithDatabaseAdministrators,resolveissueswheretheICMsystemdidnotsaveinformationrelevanttoresponseplanimplementation.

5. Asnewdataisused,workwithDatabaseAdministratorstoupdatetheICMCoreSystemsoftwareasneeded.

8.6. DATAMANAGEMENT


Responsibility

1. Workwithstakeholders,DataAnalysts,andDatabaseAdministratorstostoredatainelectronicformat.

2. Asdatatypesanddataformatschangeovertime,workwithstakeholders,DataAnalysts,andDatabaseAdministratorstoensurethatthedataisstoredcorrectly.

3. WithDatabaseAdministrators,determinethepercentageoftimethatdataistransmittedusingTMDD/NTIP/GTFS(data)format,thepreferredstandardfortheICMsystem.WithDatabaseAdministratorsandtheCorridorTechnicalManager,identifywhenotherdataformatsarebeingusedandworktoreplacethemwiththepreferredformat.

4. AstheTMDD/NTCIP/GTFS(data)specificationisupdated,workwithDatabaseAdministratorstomodifythesystemtostayincompliance.

5. WithDatabaseAdministrators,fulfillstakeholderrequestsfordataadditions,removals,orformatchanges.


31



Responsibility

1. WithDatabaseAdministrators,performnormalmaintenanceoftherulessystem,takingnoteofanddiscussingtheexistenceofrulesthathavenotbeenusedforalongperiodoftime.

2. Fixproblemswiththerulesenginenotevaluatingrulescorrectly.

3. Asnewdataandnewrulesarerequired,updatetherulesengineasneeded.

4. Asthecorridorchanges,workwithTrafficEngineersasneededtoupdateandmaintainthealgorithmsanddatausedtodetermineandpredictcorridorstate.

5. WithDatabaseAdministrators,performongoingmaintenancetoensurethesystemaccuratelydeterminesiftrafficiswithinnormalvariabilityforagivendateandtime.



Responsibility

1. AssetInformation

a. WithDatabaseAdministrators,resolveissueswithuserinterfacesformanagingassetinformation,including:

• Assetinventory• Assethealth• Assetavailability• Assetstate

b. Maintaintheinterfaces.


a. WithDatabaseAdministrators,resolveissueswithuserinterfacesformanagingincident/eventinformation,including:

• Typeofincident/event• Timeofoccurrence

• Expectedduration• Roadway/transitsegmentwhereoccurred

• Locationalongroadway/transitsegment

• Lane(s)affected• Agencyresponsibleformanagingincident/event

• Verificationstatusofincident/event• Userconfirmationinterface

b. Maintaintheinterfaces.

3. MockIncidents


32

Responsibility

a. Asneeded,modifytheuserinterfacesforcreatingmockincidents,including:

• Creating,viewing,updating,anddeletingmockincidents

• Map-basedinterfaceforchoosingincidentlocation

• Settingthestart/endtimes,duration,lanes/routes/tracksaffected

b. Asneeded,modifytheuserinterfacesfortestingmockincidents,including:

• SubmissionofmockincidentstotheDecisionSupportmodulefortesting

• Mapdisplayoftheresponseplanelementsrecommendedforamockincident

• Generationofapost-incidentreportforamockincident

4. ResponsePlans

a. Asneeded,modifytheuserinterfacesformanagingresponseplans,including:

• Viewingresponseplans(triggeringevent,agenciesinvolved,reroutes,controlassets,messaging,personnel,constraints)

• ManagingDecisionSupportrules(creating,testing,visualizing)

• Settingpreferences• Selecting/approvingaplan• Implementingaplan

• Confirmingincident/eventtermination

• Notifyingstakeholders

b. Updatetheinterfacesasnewfeaturesareadded.

5. ICMCoreSystem

a. Asneeded,modifytheuserinterfacesformanagingtheICMCoreSystem,including:

• Viewingalllogactivity• CustomizingICMEnvironmentoperations(systemconfiguration,useradminstration,userpreferences)

• StartingandshuttingdownCoreSystemcomponents

b. Updatetheinterfacesasnewfeaturesareadded.

6. Geospatialvisualization

a. WithDatabaseAdministrators,resolveproblemswithmap-basedvisualizationofdata,including:

• Viewing(corridorcharacteristics,roadwaygeometry,sensing/controlassets,operationalstatus,incidents/events,responseplanelements)

• Accessinginformationfrommapdisplays(roadwaydetails,deviceconfiguration,videofeeds,trafficstate,incident/eventdetails)

• Layeringofdisplayelements

• Customizing(userselection/customizationofdisplayandcontent,saveduserpreferences)

• Managing(userinteractionwithICMsystemfrommapdisplaystomodifyofassetusageandstate,verifyincidents,select/approveresponseplans)

b. Updatetheuserinterfacesasdataanddatapresentationneedschangeandbugsarefound.

7. Reporting,Charting,andGraphing

a. WithDatabaseAdministrators,resolveproblemswithreporting,charting,andgraphingfunctions,including:

• Standardandcustomizedreporting(creating/saving,scheduled/on-demand,printed/on-screen)


33

Responsibility

• Summaryreports(roadwayelements,sensing/controldevices,responseplanning,systemperformance)

• Plot-basedvisualizations(2d,3d,heatmap)

• Graphingdisplays(orgcharts,decisiontrees,flowcharts,pie/line/bar/histogramcharts)

• Tables• Userqueries

b. Updatetheuserinterfacesasdataanddatapresentationneedschangeandbugsarefound.

8. Post-incident/eventreports

a. WiththeCorridorTechnicalManager,diagnoseandresolveissueswhenpost-incident/eventanalysisreportsarenotgenerated.

b. Updatethereportsasnewfeaturesareadded.

9. SoftwareSystem

a. Asthesystemundergoesplannedmodifications,workwithDatabaseAdministratorstomaintainthecentralinterfaceformanagingsoftwaresystemparameters.



Responsibility

1. EnsurethesystemprovidesasingleuserinterfaceforvisualizationandreportingandforCoreSystemcontrolfunctions.Keepthesystemincompliancewiththesestandardsasnewfeaturesareadded,bugsarefixed,etc.

2. WiththeCorridorDataAnalystandDatabaseAdministrators,resolveproblemswhenstandardsarenotfollowedforintegrateddatadefinition,capture,processing,andpresentation.

3. Asdataneedschangeandbugsarefound,workwithDatabaseAdministratorstoupdatetheuserandprogramminginterfaces.

4. WorkwiththeCorridorDataAnalyst,DataAnalysts,andDatabaseAdministratorstoidentifyandresolveissueswherecopiesofdataarebeingerroneouslyusedassystemsofrecord.



Responsibility

1. Resolveissueswithinaccurateormissingloggingactivity.Ensurenewfunctionalityisattachedtoviewablelogs.

2. Resolveissueswiththetrackingsystemusedformaintenancerequests,improvementrequests,


34

Responsibility

andbugfixrequests.WiththeCorridorTechnicalManager,performnormalsystemmaintenance.

3. Fixsoftwarebugsasneeded.


35

9. ELECTRICALENGINEERS

Electrical Engineers are responsible for investigating and remedying hardware- and communication-relatedproblemsandforinstallingupgradesasrequired.



Responsibility

1. WiththeCorridorTechnicalManagerandSoftwareEngineers,determinethereasonassetstatusesarenotavailableandworktobringthembackonline.

2. Whereassetstatusisprovidedthroughautomation,workwithSoftwareEngineerstoensurestatusisavailable.

3. WithSoftwareEngineers,determinethereasonassetstate(thecurrentconfigurationofinformationondevices,includingsignalplans,rampmeteringplans,CMSmessages)isnotavailableandresolvetheissue.

4. WithSoftwareEngineers,maintainsoftwareandhardware.


36

10. DATABASEADMINISTRATORS

DatabaseAdministratorsensureaccesstoandproperstorageofallcorridordata.


• StrategicIncident/EventResponsePlanning• Real-TimeResponsePlanning• ResponsePlanImplementation• DataManagement• DecisionSupport• CoreSystemUserInterface• SystemIntegration



Responsibility

1. WithTrafficEngineers,SoftwareEngineers,andDataAnalysts,identifyandresolveissuesrelatedtocreatingandexecutingmockincidentsandevents.

2. WithSoftwareEngineersandDataAnalysts,resolveproblemsinthegenerationofafter-incident/eventreports.

3. WithSoftwareEngineers,upgradeandmaintainafter-incidentorafter-eventreportsastheirformatandcontentchangeovertime.



Responsibility

1. WorkwithCorridorManager,SoftwareEngineers,andDataAnalyststoidentifyandresolvepossibleissueswithincident/eventresponseplansbeingabletobereviewedandanalyzedbystakeholdersoff-line.


37



Responsibility

1. WithSoftwareEngineers,resolveissueswheretheICMsystemdidnotsaveinformationrelevanttoresponseplanimplementation.

2. Asnewdataisused,workwithSoftwareEngineerstoupdatetheICMCoreSystemasneededtoensureallrelevantdataissavedforpost-incidentanalysis.

10.4. DATAMANAGEMENT


Responsibility

1. DataDictionary

a. WithDataAnalysts,assisttheCorridorDataAnalystinmaintainingtheDataDictionary,ensuringthatitisaccurateanduptodate.

b. WithDataAnalysts,noteanydiscrepanciesbetweentheDataDictionaryandtheactualdataandresolvethem.

2. DataStorage

a. Workwithstakeholders,SoftwareEngineers,andDataAnalyststostoredatainelectronicformat.

b. Asdatatypesandformatschangeovertime,workwithstakeholders,SoftwareEngineers,andDataAnalyststoensurethatstoragemethodsareuptodate.

3. DataFormats

a. WithSoftwareEngineers,determinethepercentageoftimethatdataistransmittedusingTMDD/NTIP/GTFS(data)format.

b. WithSoftwareEngineersandtheCorridorTechnicalManager,identifywhenotherdataformatsarebeingusedandworktoreplacethem.

c. WithSoftwareEngineers,astheTMDD/NTCIP/GTFS(data)specificationisupdated,modifythesystemtostayincompliance.

4. ETL(Extract,Transform,andLoad)

a. AssistwithusingETL(Extract,Transform,andLoad)forinterfacingwithexternalsystems.

b. WiththeCorridorTechnicalManager,determinethepercentageoftimeETL-providedfunctionscanbeused.

c. WithDataAnalysts,ensureETLoperationscontinuetoworkwhenexternaldataformatschange.Performcontinualmaintenance,asexternalandinternalformatsmaychangeatanytime.

5. WithSoftwareEngineers,fulfillstakeholderrequestsfordataadditions,removals,orformat


38

Responsibility

changes.

6. Reviewanddeterminethepercentageoftimethatstate-of-the-arttechnologiesareusedtostore,access,andselectdata,andqueriesexecutedwithappropriateresponsetimes.

7. Reviewquerylogstodeterminewhenperformanceisnotmeetingrequirements;resolveissues.

8. WiththeCorridorTechnicalManager,determinethecompletenessofdatamanagementpoliciesandthepercentageoftimepoliciesarebeingfollowed.



Responsibility

1. WithSoftwareEngineers,performnormalmaintenanceoftherulessystem,takingnoteofanddiscussingtheexistenceofrulesthathavenotbeenusedforalongperiodoftime.

2. WithSoftwareEngineers,performongoingmaintenancetoensurethesystemaccuratelydeterminesiftrafficiswithinnormalvariabilityforagivendateandtime.



Responsibility

1. WithSoftwareEngineers,resolveissueswithuserinterfacesformanagingassetandincident/eventinformation;maintaintheinterfaces.

2. WithSoftwareEngineers,resolveproblemswithgeospatialvisualizationofdataandreporting,charting,andgraphingfunctions;updatetheuserinterfaceasdataanddatapresentationneedschangeandbugsarefound.



Responsibility

1. WiththeCorridorDataAnalystandSoftwareEngineers,resolveproblemswhenstandardsarenotfollowedforintegrateddatadefinition,capture,processing,andpresentation.WithSoftwareEngineers,updatetheuserandprogramminginterfacesasdataneedschangeandbugsarefound.

2. WorkwiththeCorridorDataAnalyst,DataAnalysts,andSoftwareEngineerstoidentifyandresolveissueswherecopiesofdataarebeingerroneouslyusedassystemsofrecord.


39

11. STAKEHOLDERS

StakeholdersarethekeyrepresentativesfromthecorridoragencieswhoparticipateintheICMproject.Manystakeholderresponsibilitiesarecarriedoutbyspecificpersonnelwithinanagency,suchasTrafficEngineers,DataAnalysts,andsoon,and,wherepossible, thoseresponsibilitiesare listedunder thoseparticular job titles in this document. Tasks not associated with a specific job title, or that are theresponsibilityofthestakeholderagencygenerally,arelistedinthis“Stakeholders”section.

StakeholdersareinvolvedinallareasoftheSystemRequirements,including:

• InstitutionalSupport• CorridorMonitoring• StrategicIncident/EventResponsePlanning• Real-TimeIncident/EventMonitoring• Real-TimeResponsePlanning• ResponsePlanImplementation• DataManagement• DecisionSupport• CoreSystemUserInterface• SystemIntegration• SystemManagement



Responsibility

1. StrategicPlanning

a. InconsultationwiththeCorridorManager,overseethedrafting,review,approval,andmaintenanceoftheCorridorStrategicPlanfordatacollection,control,andperformancemetriccalculationprocesses.

b. Withconsultantswhoarenotdirectstakeholders,reviewtheCorridorStrategicPlan.

c. ApprovetheCorridorStrategicPlan.

d. EnsurethattheassetsanddatadefinedintheStrategicPlanareavailableandproperlymaintained.WorkwiththeCorridorTechnicalManagerandCorridorDataAnalysttoprovideanymissingitems.Thismayinvolvepurchasingorupgradingassetsand/ordata.

2. PersonnelandManagement

a. NameandidentifyCorridorChampions.ReplaceChampionsnolongerwiththeprojectoragency.

b. IncoordinationwiththeCorridorManager,writejobdescriptionsforICMroleswithineachorganizationandidentifytheindividualswhowillfilltheroles.

c. EnsurethatICMsupportpersonnelareinplaceandtrained.

d. WorkwithCorridorManagertoresolvediscrepanciesbetweencurrentstaffversusneededstaff.


40

Responsibility

e. DevelopnewproceduresandpracticessupportingICMcorridormanagementobjectives.

f. ContinuouslyengageinICMcorridoractivities.

g. Providefeedback,whensurveyed,onthemanagementteam,structure,andprocessesoftheICMeffort.

3. InteragencyCooperation

a. Participateindevelopingacultureofcooperationandcommunicationwithagencies,organizations,otherstakeholders,andallotherpersonnelintheICMenvironment(electedofficials,travelers,thepress,etc.).

b. ProvidefeedbackonwhetheragencypersonnelunderstandICMandtheculturalchangesrequired.

c. Providefeedback,throughsurveysandafter-incident/eventreviews,oncommunicationeffectivenessand/orbreakdowns.

d. AnalyzewhycommunicationisnotworkingorwherethebreakdownoccurredandinvolveseniormanagementandChampionsinresolvingtheissues.

e. Attendregularcorridorupdatemeetingsorteleconferences.

f. Assistasneededwiththedrafting,review,approval,andmaintenanceofinteragencyagreements,suchastheProjectCharter,MemorandumofUnderstanding,andOperationsandMaintenancePlan.

g. Signagreementssubmittedforapprovalinatimelymanner.

h. Analyzewhyandhowinteragencyagreementsarenotsignedandfollowed;workwithproperChampionstoresolveissuesandensureallconditionswithinthedocumentsareadheredto.

i. Determineneedsforongoingcommunicationtraining,includingitemssuchasconflictresolution,customerservice,facilitation,speakingskills,etc.

4. Funding

a. Continuallyreviewbudgetsandidentifyexistingfundinggapsandneedsfornewfunds.

b. WorkwithCaltranstoidentifyfederal,state,regional,andlocalfundingsources.

c. Identifyagencypersonneltohelpwiththedevelopment,submission,andtrackingoffundingapplications.

d. Whenneeded,writeLettersofSupportforfundingapplications.

5. OutreachandCommunications

a. Provideanorganizationalchart,namesofBoardmembersandofficedirectors,keycontactpersons,andotherrelevantinstitutionalinformationtotheOutreachandCommunicationsManager.

b. Designateanindividualintheagencywhoshallberesponsibleforoutreachandcommunications.

c. Providefeedbackonoutreachandcommunicationeffortsandtheeffectivehandlingofinquiries.WithCorridorChampion(s),helpresolveissues.

d. Reviewprojectdocumentsandprovidecommentsbyagreed-upondeadlines.

e. KeeptheCorridorManagerinformedofscheduledeventsandassociatedstreetclosuresandrecommendeddetoursalongcorridorarterials.

f. IncoordinationwiththeCorridorManager,developcontractsandpositiverelationshipswiththirdparties.Periodicallyreviewandrenewpurchasingchoicesandcontracts.


41



Responsibility

1. EnsurethatthestatusofcorridorassetsiscommunicatedtotheICMsystem,whenstatusinformationisnotprovidedthroughautomationbutthroughhumanprocesses.

2. Createandeditdeviceproblemreports,wherereportsarenotgeneratedautomaticallybytheICMCoreSystem.

3. Incoordinationwithexternalconsultants,reviewperformancemetricsonceperyear.



Responsibility

1. WorkwiththeCorridorManagertoresolveattendanceissuesforresponseplanningmeetings.

2. SpecifywhetheractiveresponseplansinvolvingagencyassetscanbeautomaticallyterminatedbytheICMCoreSystem.

3. Defineperiodsduringwhichmanualapprovalisrequiredandperiodsduringwhichautomatedapprovalispossible.

4. Aftereachincident,unscheduledevent,orplannedevent,incoordinationwiththeCorridorManagerandTrafficEngineers,reviewtheselectedresponseplancomponentsanddetermineifanyaremissingorinappropriate.

5. Noteanyproblemsbuildingmockincidents.

6. Eachquarter,aswellasfollowingeachmajorincident,meettodiscussandreviewtheresultsoftheapplicationofresponseplanstothecorridor.Ifmeetingsarenotbeingheldorattendanceislow,workwiththeCorridorManagerandCorridorChampion(s)todetermineandremedythecauses.



Responsibility


a. Provideinformationcharacterizinganincident/eventtotheICMCoreSystem(e.g.,location,starttime,type,severity,etc.).IftheCorridorManagerdeterminesthatinformationwasnotprovided,workwithFirstRespondersandPublicInformationOfficers


42

Responsibility

toresolvetheissues.

b. Reviewallincident/eventinformationcommunicationprocessesperiodicallyandensurethatpersonnelareawareofandfollowtheseprocesses.

c. Manuallyenterinformationaboutplannedlane/roadwayclosuresorscheduledeventsintotheICMCoreSystemifnotautomaticallyretrievedbythesystem.

2. Incident/EventValidation

a. Validatethatanincidentoreventexistsbeforearesponseplanisapplied.

b. Ifanincidentoreventischaracterizedbutnotvalidated,workwiththeCorridorManagertodetermineandremedythecause.

3. Incident/EventNotification

a. InformtheCorridorManagerifnotificationisnotreceivedfromtheICMsystemwhenanincidentoreventoccurs.

b. WorkwiththeCorridorManagertoensurethe“whotocontact”rulesetisupdated.

c. Maintainthe“whotocontact”list.

4. UpdatedIncident/EventInformation

a. Provideupdatedeventinformation(forexample,end-of-incidentnetworkchanges)totheICMCoreSystem.

b. WorkwithCorridorManagertodeterminewhenincidentinformationwasnotproperlyupdatedandresolveissues.



Responsibility

1. Reviewresponseplansthesystemrecommendsforimplementation.Whenreviewsarenottakingplace,workwiththeCorridorManagertoidentifyandresolveissueswiththereviewprocess.

2. Ifpartoftheplanapprovalprocess,approve,ordisapprove,theresponseplan.Ifapprovalisnotoccurring,workwiththeCorridorManagertodeterminethecauseandresolvetheproblems.

3. WiththeCorridorManager,notewhenapprovalrulesarenotfollowedanddeterminewhethertheproblemiswiththerulesorthesoftware.

4. Asneeded,reviewandanalyzeoff-lineeachstepintheresponseplanningworkflow,tounderstandhowpredictionswereperformed,recommendationsmade,andplanschosen.




43

Responsibility

1. Assistwhereneededinresolvingissuesrelatedtotheorderandscheduleofassetinstructions.

2. InformtheCorridorManagerifnotappropriatelynotifiedthataresponseplanisbeingdeployed.WorkwiththeCorridorManagertoensurethe“whotocontact”rulesetisupdatedandmaintained.

3. PermittheICMCoreSystemtocontactdesignatedagencypersonnelwithrequestsforperformingpreapprovedactions.

4. AssistwhereneededinresolvingissuesrelatedtosendingassetinstructionstobothITSandhumanelementsintheresponseplan.

5. Aspersonnelchange,modifyasneededthemannerinwhichinstructionsaresent.

6. Asassetsandequipmentchange,modifyasneededthesystemcomponentsandpoliciesforverifyingthatassetinstructionshavebeenreceived.

7. Assistasneededinresolvingissueswherestatuschangesduringaresponsewerenotcommunicatedtostakeholders.

8. Assistasneededinresolvingissueswhereassetsdidnotreturntonormalstatuswhenanincidentoreventended.

11.7. DATAMANAGEMENT


Responsibility

1. Designatearepresentativetoserveonthedatagovernanceboard.

2. Withconsultants,annuallyreviewdataqualityrequirementsandcalculationmethods.Asneeded,workwiththeCorridorDataAnalystandthird-partyproviderstorefineandupdatethedataqualityspecifications.

3. WorkwiththeSoftwareEngineers,DataAnalysts,andDatabaseAdministratorstostoredatainelectronicformat.

4. Asdatatypesandformatschange,workwiththeSoftwareEngineers,DataAnalysts,andDatabaseAdministratorstoensurethatstoragemethodsareuptodate.

5. Asneeded,submitrequestsfordataadditions,removals,orformatchangestoDataAnalysts.

6. NotifytheCorridorDataAnalystofanychangestodatasourcesfromsystemsownedbytheagency.

7. Determinewhypoliciesfordataarchiving,warehousing,anddeletionarenotbeingfollowedandensureproperdatamanagementoccurs.


44



Responsibility

1. Createsimplerulesfortherulesenginetouseindevelopingresponseplans.(Morecomplexrulesrequireprogrammingskills.)

2. Updaterulesasdatachanges.(Morecomplexrulesmustbecreated/updatedbySoftwareEngineers.)



Responsibility

1. InformCorridorTechnicalManagerwhenuserinterfacesarenotfunctioning.

2. WorkwiththeCorridorManagertoresolveanyinteragencycommunicationissuesobservedduringincidents.



Responsibility

1. WorkwiththeCorridorManagerasneededtoclarifywhoownsagivencorridorasset.



Responsibility

1. Security

a. Resolveissuesrelatedtounauthorizedaccesstosystemassets.

2. ServiceLevelAgreement

a. Reviewandapprovetheservicelevelagreement.

b. Eachyear,incoordinationwiththeCorridorTechnicalManager,determinethedesired


45

Responsibility

servicelevelagreementmetricsandprovideresourcestoensuretheycanbemet.

3. LoggingandTracking

a. Reportinaccurateormissingloggingactivityinsystemhealth,status,andotherlogs.

b. Useasystemfortrackingmaintenancerequests,improvementrequests,andbugfixrequests.Reportanyproblemswithusingthesystem.

c. Reportsoftwarebugs.

4. Maintenance

a. Beresponsibleformaintenance(bothrepairandpreventative)ofallsystemcomponents(ITScomponents,vehicles,people,software,hardware,useapprovals,etc.).WorkwiththeCorridorTechnicalManagertoresolveissues.

b. Reportmaintenanceactivities(bothrepairandpreventative).WorkwiththeCorridorTechnicalManagertoresolveanyreportingproblems.

5. Training

a. EnsurethatappropriatetrainingandtrainingmaterialsareprovidedforallaspectsoftheICMsystem.

b. Ensurethatappropriatedocumentation,bothusermanualsandworkflowdescriptions,isavailableforallfunctions.WorkwiththeCorridorTechnicalManagertoimprovedocumentationasneeded.

6. SystemRecovery

a. Workwithconsultantstoperiodicallyreviewdisasterpreparedness;workwiththeCorridorTechnicalManagertoresolveissues.

7. SystemUpgrades

a. Approvethe5-yearsystemupgradeplan.WorkwiththeCorridorManagertoresolveissuesrelatedtotheplanandtomaintainit.


46

12. MAINTENANCESTAFF

Maintenance Staff ensure all ICM hardware and communication components are maintained and inworkingorder.



Responsibility

1. Ensurethathardwareandcommunicationsystemsareworking.



Responsibility

1. Performmaintenance(bothrepairandpreventative)forsystemcomponents(ITScomponents,vehicles,hardware,etc.).

2. Open/close/editmaintenanceticketitemsasneeded.

3. Reportmaintenanceactivities(bothrepairandpreventative).


47

13. ITSUPPORT

IT Support ensures the day-to-day operation and maintenance of workstations, security patchmanagement,internetaccess,andpropersoftwareinstallationandconfiguration.

Responsibility

1. Troubleshootandresolvetechnicalissuesassociatedwithnetworkconnectivity,identityaccess,computerdesktops,andperipheraldevices.

2. Participateindisasterpreparednessexercisesandassiststakeholdersinresolvingtechnicalissues.

3. Provideconsultationasneeded.


48

14. ITSECURITY

ITSecurityensuresthatallICMcomponents(software,hardwareandpersonnel)aresafeandsecure.



Responsibility

1. BeresponsibleforthesecurityoftheICMEnvironmentanditsoperations.

2. DevelopandimplementsecurityprotocolsandprocessesfortheICMEnvironmentandensuretheyaremaintained.

3. Maintainandreviewalogofaccessforevidenceofunauthorizeduseofthesystem.

4. ConductformalreviewsoftheICMEnvironmentsecurityprocessesataregularfrequencyinaccordancewiththesecurityprotocolsandprocesses,withaminimumfrequencyofquarterly.

5. DirectaformalreviewofICMEnvironmentsecurity,ledbyexternalsecurityexperts,ataregularfrequencyinaccordancewiththesecurityprotocolsandprocesses,withaminimumfrequencyofannually.


49

15. TRANSPORTATION MANAGEMENT CENTER (TMC) AND LOCALTRAFFICCONTROLSYSTEM(TCS)OPERATORS

TMC/TCS Operators are responsible for day-to-day interaction with the ICM system, documentingincidentinformation,andapprovingresponseplans.TMCOperatorsmaybeatCaltransorlocalagenciessuchasacityorcounty.LocalTCSOperatorsareatthelocallevel,suchasacityorcounty.



Responsibility

1. SpecifywhetheractiveresponseplansinvolvingagencyassetscanbeautomaticallyterminatedbytheICMCoreSystem.

2. Defineperiodsduringwhichmanualapprovalisrequiredandperiodsduringwhichautomatedapprovalispossible.



Responsibility

1. ConfirmthatanincidentoreventhasbeeneffectivelyterminatedbeforetheICMCoreSystemidentifiesitassuch.



Responsibility

1. Asneeded,manuallyselectaresponseplanfromalistofrecommendedresponseplans.

2. Asneeded,proposeminormodificationstoarecommendedresponseplan.

3. Reviewandapproveapplicationofresponseplans.

4. Asneeded,proposechangestoanimplementedresponseplan.

5. Reviewandapproveterminationofresponseplans.

6. Asneeded,manuallyinformtheICMCoreSystemthatanincidentoreventhasterminated


50

16. TRANSITFIELDSUPERVISORS(RAIL,BUS)

Transit Field Supervisors are responsible for day-to-day interaction with the ICM system, providingincidentinformationtothesystemandrelayingresponseplanrecommendationstooperators.



Responsibility

1. Participateinresponseplanningactivities.

2. Determine,ifneeded,detourroutesthatmaybeusedduringincidentsandeventsimpactingtransitoperations.

3. Determine,ifneeded,informationtobesenttotransitpersonnelduringanincidentorevent.

4. Participateindefiningorvalidatingrulesforbuildingresponseplans.

5. Participateindefiningorvalidatingrulesforhandlingspecialsituations.



Responsibility

1. EnterintotheICMCoreSysteminformationabouttransitincidentsorservicedisruptions.



Responsibility

1. UseinformationfromtheICMCoreSystem’sresponseactionsunderconsiderationtomakepotentialtransitserviceadjustments.


51

17. PUBLICINFORMATIONOFFICERS(PIO)

PIOsat stakeholderagenciesare responsible forpublic andmedia relationsduringmajor incidentsormajorchangestotheICMsystem.



Responsibility

1. ActivelyparticipateinICMoutreachandcommunicationsactivities,suchaspressevents,announcements,briefingsonincidents/events,etc.

2. AssisttheOutreachandCommunicationsManagerwithsurveystodeterminestakeholders’satisfactionwithinteragencycommunication.

3. MaintainongoingcommunicationwithPIOsatotherstakeholderagencies.



Responsibility

1. WorkwithstakeholdersandFirstResponderstoresolveissueswheninformationcharacterizinganincident/eventwasnotprovidedtotheICMCoreSystembystakeholders.


52

18. FIRSTRESPONDERS

FirstRespondersareemergencyresponsepersonnelwhoareatthesceneofanincidentorevent,taketheleadinsecuringthescene,anddirectothers.



Responsibility

1. EnsurethatICMsupportpersonnelareinplaceandtrained.

2. AttendquarterlyICMcorridorupdatemeetingswherefirstresponseproceduresareontheagenda.

3. Provideorganizationalcharts,namesofkeycontactpersons,andotherrelevantinstitutionalinformationtotheOutreachandCommunicationsManager.



Responsibility

1. Participateinincident/eventresponseplanning.

2. Determinedesiredroutestobeusedasdetoursforincidentsandevents.

3. Determinepersonneltobeavailablefordeploymentduringanincidentorevent.

4. Determinetypicalinformationtobesenttoagencypersonnelwhenrespondingtoanincidentorevent.

5. Participateindefiningrulesforhandlingspecialsituations.



Responsibility

1. WorkwithstakeholdersandPIOstoresolveissueswheninformationcharacterizinganincident/eventwasnotprovidedtotheICMCoreSystembystakeholders.


53

19. OUTREACHANDCOMMUNICATIONSMANAGER

TheOutreachandCommunicationsManagerisresponsibleforensuringanongoingflowofinformationbetween all ICM stakeholders both during incidents and as part of planning, implementation, andgeneralPRefforts.



Responsibility

1. OrganizationComposition

a. Maintaininformationonstakeholderagencies(orgchart,boardmembersandofficers,contacts,etc.).

b. DevelopandmaintainalistofcurrentCorridorChampionsfromeachstakeholderagency.

c. WiththeCorridorManager,setupandmaintainaConnectedCorridorsSteeringCommittee,TechnicalandOperationalAdvisoryCommittee,andothercommitteesasneeded.

2. CommunicationsStrategy

a. Developacommunicationsstrategy.

b. Cultivateandmaintainongoingpositiverelationshipswithstakeholders,partners,andotheragencies.

c. Responsiblefororganizingregularmeetingswithstakeholders,PIOs,andfirstresponders.

d. Createandmaintainoutreachmaterialsinmultipleformats,includingnewsletters,factsheets,website,socialmedia,etc.

e. Followuponinformationrequests;forwardrequeststootherstakeholdersforcommentasneeded.

f. Monitorelections,fundingopportunities,andthepoliticalenvironmentwhichmayaffecttheICMeffort.

g. ConductoutreachandcommunicationseffortstoensurethatICMisunderstoodandacceptedbyallstakeholders(particularlywhenthereisstafforelectedofficialturnover).

h. IncoordinationwiththeCorridorManager,surveypersonnelandtheirmanagerstodetermineifpersonnelunderstandICMandtheculturalchangesrequired.

i. Responsibleforstakeholdersurveysandafter-incident/eventreviewsfocusingoncommunicationand/orcommunicationbreakdowns.

3. Funding

a. AlongwiththeCorridorManager,researchandtrackfundingopportunities;prepareandsubmitfundingapplications.

4. InteragencyAgreements

a. DraftaProjectCharterandmanagetheprocessleadingtoitsadoptionbystakeholders.

b. Ensureinteragencyagreementsaredrafted,approved,andcurrent.

c. Trackwhencurrentstakeholderagreementsaresettoexpireandwhethertheyneed


54

Responsibility

updatingoramending.Informstakeholdersofagreementstatusandleaddiscussionsontherenewal,updating,oramendingofexistingagreements.

i-210 pilot system requirements: job descriptions and duties… · 2019. 12. 17. · i-210 pilot:...

Documents