slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
LCS Objectives PowerPoint Presentation
Download Presentation
LCS Objectives

Loading in 2 Seconds...

play fullscreen
1 / 19

LCS Objectives - PowerPoint PPT Presentation

  • Uploaded on

LCS Objectives. Provide a standard interface for lane closure operations, closure tracking, and data retrieval for WisDOT regional offices statewide

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'LCS Objectives' - garry

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
lcs objectives
LCS Objectives
  • 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
  • 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
  • Integrate historical traffic flow data and capacity information to calculate available closure thresholds
lcs benefits
LCS Benefits
  • Coordinates activities to reduce back-ups and potential conflicts
    • Multiple activities can utilize the same closure
    • Avoid lane closures during a special event
    • Avoid right lane closure near a left lane closure on the same roadway
  • Eliminates duplications and inefficiencies by streamlining information into one system
  • Provides link to historical data that can be used to make informed decisions
lcs data flows
LCS Data Flows

LCS Users

Request / Accept

511 Travel Info


Email List


Contracts, STN,

Traffic Data


Data Archive



Construction Map

WisDOT Website

Special Project


system use
System Use

What closures should be tracked?

  • All let projects (information formerly entered into Traffic Impediment Module)
  • Any planned closure or restriction on Corridors 2030 roadways
  • All major special events

When should closures be entered?

  • 14 days - Project start or full roadway closure
  • 7 days - System ramp closure
  • 3 days - Lane and service ramp closure
system use1
System Use
  • Closure / Restriction Types
    • Construction – Let projects
    • Maintenance
    • Permit – Utility work
    • Special Event – Summerfest Fireworks, Harley Parade, Farm Progress Days
    • Emergency
closure information
Closure Information
  • 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:
    • Mainline
    • Ramp
    • Bridges
    • System Interchanges
closure duration types
Closure Duration Types
  • 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
  • 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
system users
System Users
  • 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)
acceptance process
Acceptance Process
  • Closures that will typically be automatically accepted include:
    • Let project information that was formally entered into the Traffic Impediment Module of FIT
    • Closures that meet requirements outlined in the TMP
  • Closures that should follow the approval process include:
    • Maintenance work
    • Short-term project closures – i.e. overnight work
lcs work flow
LCS Work Flow



Return / Reschedule




acceptance process1
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
  • Users with acceptance authority are allowed to, but not required to, immediately accept a closure they have entered into the system
system interfaces
System Interfaces
  • Request – Enter a closure into the system
  • Accept – Edit, advance or accept a closure
  • Modify – Modify or reschedule accepted closures
  • Search – Search for closures
  • Reports – Run closure reports
  • Capacity – Evaluate lane closure
  • Calendar – View calendar of events (i.e. Packer Games)
  • E-mail – Add, edit or delete e-mail preferences
  • Preferences – Update user information
lcs key points
LCS Key Points
  • April 1, 2008 - LCS go live date
  • 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