LCS ObjectivesLCS Objectives Provide a standard interface for lane closure operations, Provide a standard interface for lane closure operations,

closure tracking, and data retrieval for WisDOT regional closure tracking, and data retrieval for WisDOT regional offices statewideoffices statewide

Facilitate data sharing with WisDOT applications that Facilitate data sharing with WisDOT applications that require lane closure data such as 511 Traveler require lane closure data such as 511 Traveler Information, the STOC Incident Management System Information, the STOC Incident Management System (IMS), Inconvenience Map production, and (IMS), Inconvenience Map production, and Oversize/Overweight (OSOW) permittingOversize/Overweight (OSOW) permitting

Improve the completeness, reliability, and timeliness of Improve the completeness, reliability, and timeliness of lane closure data on state highwayslane closure data on state highways

Archive LCS data in the WisTransPortal system for Archive LCS data in the WisTransPortal system for future analysis and integration with other WisDOT / future analysis and integration with other WisDOT / TOPS Lab traffic engineering applications and researchTOPS Lab traffic engineering applications and research

Integrate historical traffic flow data and capacity Integrate historical traffic flow data and capacity information to calculate available closure thresholdsinformation to calculate available closure thresholds

LCS BenefitsLCS Benefits Coordinates activities to reduce back-ups Coordinates activities to reduce back-ups

and potential conflictsand potential conflicts Multiple activities can utilize the same closure Multiple activities can utilize the same closure Avoid lane closures during a special eventAvoid lane closures during a special event Avoid right lane closure near a left lane closure Avoid right lane closure near a left lane closure

on the same roadwayon the same roadway

Eliminates duplications and inefficiencies by Eliminates duplications and inefficiencies by streamlining information into one systemstreamlining information into one system

Provides link to historical data that can be Provides link to historical data that can be used to make informed decisions used to make informed decisions

LCS Data FlowsLCS 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

System UseSystem UseWhat closures should be tracked?What closures should be tracked?

All let projects (information formerly entered All let projects (information formerly entered into Traffic Impediment Module)into Traffic Impediment Module)

Any planned closure or restriction on Any planned closure or restriction on Corridors 2030 roadwaysCorridors 2030 roadways

All major special eventsAll major special events

When should closures be entered? When should closures be entered? 14 days - Project start or full roadway closure14 days - Project start or full roadway closure 7 days - System ramp closure7 days - System ramp closure 3 days - Lane and service ramp closure3 days - Lane and service ramp closure

System UseSystem Use Closure / Restriction Types Closure / Restriction Types

Construction Construction – Let projects– Let projects

MaintenanceMaintenance Permit Permit – Utility work– Utility work

Special Event Special Event – Summerfest – Summerfest Fireworks, Harley Parade, Farm Fireworks, Harley Parade, Farm Progress DaysProgress Days

Emergency Emergency

Closure InformationClosure Information General Section – includes attributes that General Section – includes attributes that

pertain to the entire closure and once pertain to the entire closure and once entered cannot be changed (with limited entered cannot be changed (with limited exception)exception)

Facility Section – used to group closure Facility Section – used to group closure specific attributes within the same closure. specific attributes within the same closure. Facilities come in four types:Facilities come in four types: MainlineMainline RampRamp BridgesBridges System Interchanges System Interchanges

Closure Duration TypesClosure Duration Types Daily/NightlyDaily/Nightly – Closures that will occur once – Closures that will occur once

on the day(s) or night(s) definedon the day(s) or night(s) defined

WeeklyWeekly – Closures that will occur on the – Closures that will occur on the same days of the week for a number of weekssame days of the week for a number of weeks

ContinuousContinuous – Closures that will last for – Closures that will last for longer than 24 hours, but less than two longer than 24 hours, but less than two weeksweeks

Long TermLong Term – Closures that will last for more – Closures that will last for more than two weeks than two weeks

System UsersSystem Users

System can be accessed via the Internet – System can be accessed via the Internet – therefore people outside of WisDOT can therefore people outside of WisDOT can log on with a username and passwordlog 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)

Acceptance ProcessAcceptance Process Closures that will typically be automatically Closures that will typically be automatically

accepted include: accepted include: Let project information that was formally entered Let project information that was formally entered

into the Traffic Impediment Module of FITinto the Traffic Impediment Module of FIT Closures that meet requirements outlined in the Closures that meet requirements outlined in the

TMPTMP

Closures that should follow the approval Closures that should follow the approval process include: process include: Maintenance workMaintenance work Short-term project closures – i.e. overnight workShort-term project closures – i.e. overnight work

LCS Work FlowLCS Work Flow

ACCEPT

REQUEST

FORWARD

Complete

Closure

Ret

urn

/ Res

ched

ule

Acceptance ProcessAcceptance Process Special events will typically be entered by a Special events will typically be entered by a

Traffic Engineer who has already approved Traffic Engineer who has already approved the closure and the closure will not go the closure and the closure will not go through the acceptance processthrough the acceptance process

Acceptance authority can be delegated to Acceptance authority can be delegated to anyone by their supervisor anyone by their supervisor

Users with acceptance authority are allowed Users with acceptance authority are allowed to, but not required to, immediately accept a to, but not required to, immediately accept a closure they have entered into the system closure they have entered into the system

System InterfacesSystem Interfaces

Request – Enter a closure into the systemRequest – Enter a closure into the system Accept – Edit, advance or accept a closureAccept – Edit, advance or accept a closure Modify – Modify or reschedule accepted closuresModify – Modify or reschedule accepted closures Search – Search for closuresSearch – Search for closures Reports – Run closure reportsReports – Run closure reports Capacity – Evaluate lane closureCapacity – Evaluate lane closure Calendar – View calendar of events (i.e. Packer Calendar – View calendar of events (i.e. Packer

Games)Games) E-mail – Add, edit or delete e-mail preferencesE-mail – Add, edit or delete e-mail preferences Preferences – Update user information Preferences – Update user information

LCS Key PointsLCS Key Points April 1, 2008 - LCS go live dateApril 1, 2008 - LCS go live date

Does Does notnot replace person to person replace person to person communicationscommunications

Can be run from almost any web browser using any internet connection

Flexible, statewide system developed to accommodate a variety of business needs

http://transportal.cee.wisc.edu/clohttp://transportal.cee.wisc.edu/closuressures