2. LCS Objectives Provide a standard interface for lane closure operations, closure tracking, and data retrieval for WisDOT regional offices statewide Provide a standard interface for lane closure operations, closure tracking, and data retrieval for WisDOT regional offices statewide Facilitate data sharing with WisDOT applications that require lane closure data such as 511 Traveler Information, the STOC Incident Management System (IMS), Inconvenience Map production, and Oversize/Overweight (OSOW) permitting Facilitate data sharing with WisDOT applications that require lane closure data such as 511 Traveler Information, the STOC Incident Management System (IMS), Inconvenience Map production, and Oversize/Overweight (OSOW) permitting Improve the completeness, reliability, and timeliness of lane closure data on state highways Improve the completeness, reliability, and timeliness of lane closure data on state highways Archive LCS data in the WisTransPortal system for future analysis and integration with other WisDOT / TOPS Lab traffic engineering applications and research Archive LCS data in the WisTransPortal system for future analysis and integration with other WisDOT / TOPS Lab traffic engineering applications and research Integrate historical traffic flow data and capacity information to calculate available closure thresholds Integrate historical traffic flow data and capacity information to calculate available closure thresholds

3. LCS Benefits Coordinates activities to reduce back-ups and potential conflicts Coordinates activities to reduce back-ups and potential conflicts Multiple activities can utilize the same closure Multiple activities can utilize the same closure Avoid lane closures during a special event Avoid lane closures during a special event Avoid right lane closure near a left lane closure on the same roadway Avoid right lane closure near a left lane closure on the same roadway Eliminates duplications and inefficiencies by streamlining information into one system Eliminates duplications and inefficiencies by streamlining information into one system Provides link to historical data that can be used to make informed decisions Provides link to historical data that can be used to make informed decisions

4. LCS Data Flows LCS WisTransPortal Data Archive Construction Map OSOW STOC ATMS 511 Travel Info Email List LCS Users Request / Accept WisDOT Contracts, STN, Traffic Data WisDOT Website Special Project Websites

6. System Use What closures should be tracked? All let projects (information formerly entered into Traffic Impediment Module) All let projects (information formerly entered into Traffic Impediment Module) Any planned closure or restriction on Corridors 2030 roadways Any planned closure or restriction on Corridors 2030 roadways All major special events All major special events When should closures be entered? 14 days - Project start or full roadway closure 14 days - Project start or full roadway closure 7 days - System ramp closure 7 days - System ramp closure 3 days - Lane and service ramp closure 3 days - Lane and service ramp closure

8. System Use Closure / Restriction Types Closure / Restriction Types Construction – Let projects Construction – Let projects Maintenance Maintenance Permit – Utility work Permit – Utility work Special Event – Summerfest Fireworks, Harley Parade, Farm Progress Days Special Event – Summerfest Fireworks, Harley Parade, Farm Progress Days Emergency Emergency

9. Closure Information General Section – includes attributes that pertain to the entire closure and once entered cannot be changed (with limited exception) General Section – includes attributes that pertain to the entire closure and once entered cannot be changed (with limited exception) Facility Section – used to group closure specific attributes within the same closure. Facilities come in four types: Facility Section – used to group closure specific attributes within the same closure. Facilities come in four types: Mainline Mainline Ramp Ramp Bridges Bridges System Interchanges System Interchanges

11. Closure Duration Types Daily/Nightly – Closures that will occur once on the day(s) or night(s) defined Daily/Nightly – Closures that will occur once on the day(s) or night(s) defined Weekly – Closures that will occur on the same days of the week for a number of weeks Weekly – Closures that will occur on the same days of the week for a number of weeks Continuous – Closures that will last for longer than 24 hours, but less than two weeks Continuous – Closures that will last for longer than 24 hours, but less than two weeks Long Term – Closures that will last for more than two weeks Long Term – Closures that will last for more than two weeks

13. System Users System can be accessed via the Internet – therefore people outside of WisDOT can log on with a username and password System can be accessed via the Internet – therefore people outside of WisDOT can log on with a username and password LCS User Roles Supervisor Regional Traffic Engineer (RTE) - Regional Coordinator Statewide Traffic Operations Center (STOC) Project Manager (PM) Permit Coordinator (PC) Maintenance Coordinator (MC) Project Leader (PL) Public Information (PUBLIC) Inspector (INSP) Requestor (REQ) Viewer (VIEWER)

14. Acceptance Process Closures that will typically be automatically accepted include: Closures that will typically be automatically accepted include: Let project information that was formally entered into the Traffic Impediment Module of FIT Let project information that was formally entered into the Traffic Impediment Module of FIT Closures that meet requirements outlined in the TMP Closures that meet requirements outlined in the TMP Closures that should follow the approval process include: Closures that should follow the approval process include: Maintenance work Maintenance work Short-term project closures – i.e. overnight work Short-term project closures – i.e. overnight work

15. LCS Work Flow ACCEPT REQUEST FORWARD Complete Closure Return / Reschedule

16. Acceptance Process Special events will typically be entered by a Traffic Engineer who has already approved the closure and the closure will not go through the acceptance process Special events will typically be entered by a Traffic Engineer who has already approved the closure and the closure will not go through the acceptance process Acceptance authority can be delegated to anyone by their supervisor Acceptance authority can be delegated to anyone by their supervisor Users with acceptance authority are allowed to, but not required to, immediately accept a closure they have entered into the system Users with acceptance authority are allowed to, but not required to, immediately accept a closure they have entered into the system

17. System Interfaces Request – Enter a closure into the system Request – Enter a closure into the system Accept – Edit, advance or accept a closure Accept – Edit, advance or accept a closure Modify – Modify or reschedule accepted closures Modify – Modify or reschedule accepted closures Search – Search for closures Search – Search for closures Reports – Run closure reports Reports – Run closure reports Capacity – Evaluate lane closure Capacity – Evaluate lane closure Calendar – View calendar of events (i.e. Packer Games) Calendar – View calendar of events (i.e. Packer Games) E-mail – Add, edit or delete e-mail preferences E-mail – Add, edit or delete e-mail preferences Preferences – Update user information Preferences – Update user information

18. LCS Key Points April 1, 2008 - LCS go live date April 1, 2008 - LCS go live date Does not replace person to person communications Does not replace person to person communications Can be run from almost any web browser using any internet connection Flexible, statewide system developed to accommodate a variety of business needs

19. http://transportal.cee.wisc.edu/closures