Linear Referencing System (LRS) System Development Plan

Print
General Information
Solicitation Number: 1388
Status: Solicitation withdrawn
Date Posted: Nov 21, 2014
Last Updated: Nov 25, 2014
Solicitation Expires: Nov 21, 2015
Lead Organization: California Department of Transportation
Financial Summary
Suggested Contribution:
Commitment Start Year: 2014
Commitment End Year: 2016
100% SP&R Approval: Not Requested
Commitments Required: $300,000.00
Commitments Received:
Contact Information
Lead Study Contact(s): Robert Buendia
robert.buendia@dot.ca.gov
Organization Year Commitments Technical Contact Name Funding Contact Name Contact Number Email Address

Background

State Departments of Transportation commonly use an LRS for identifying the locations of features, events, and activities along a transportation network. Caltrans maintains an LRS for the State Highway System (SHS) and is developing an LRS for all functionally classified roads that are not part of the SHS. The Plan will take into account all current LRS activities or projects within the Division of Research, Innovation and System Information (DRISI), including but not limited to, On-system (State Highway System) LRS, Off-system (All Local Roads) LRS project, meeting federal reporting mandates, and other LRS activities/projects that may have an impact. It will also consider all LRS-related business needs (beyond DRISI) for Caltrans. The System Development Plan will be the foundation to meet the business demands for Caltrans’ future LRS development.

Objectives

The primary purpose of this project is to develop a “Linear Referencing System (LRS) System Development Plan” (Plan) to document Caltrans’ LRS-related business requirements and prioritize future LRS system improvements. In order to meet this purpose, the Plan must be comprehensive in scope, must enable the LRS to meet current and future department-wide LRS-related business needs, must take into account any requirements related to interoperability between existing or planned Caltrans applications and the LRS, must consider spatial data collaboration and sharing between Caltrans and its partners, and must address meeting current federal/state/Caltrans reporting requirements all while still allowing for agile LRS development in the face of changing transportation legislation or other new mandates. The secondary purpose of this project is to complete an assessment of the State of California’s anticipated LRS requirements (on a high level) and ensure that what gets incorporated under Caltrans’ business requirements does not prevent the implementation of these statewide requirements at a future date.

Scope of Work

SUMARY OF ACTIVITIES AND DELIVERABLES BY TASK Task 1 – Project Management • Project Setup - Coordination and Communication with Caltrans and FHWA • Schedule Kickoff Meeting • Create draft communication plan, risk management plan, Change Management Plan and project work plan • Create project website (eRoom) for project management, communication, document sharing • Conduct project kickoff • Deliver final communication plan, risk management plan, Change Management Plan and project work plan. • Develop project status PowerPoint presentation and update monthly • Conduct bi-weekly internal project management calls • Conduct bi-weekly Project Team calls with Caltrans and FHWA • Maintain communication, risk management and project work plans • Provide monthly progress reports to Caltrans Contract Manager Task 2 – Assess Caltrans’ LRS-Related Business Needs and California’s LRS Requirements • On-site interviews with selected Caltrans Divisions and Districts to identify LRS business needs (CDM Smith has budgeted 2 people for two weeks on-site) • Conduct analysis of Caltrans’ LRS requirements, data structures, maintenance, data sharing and federal requirements regarding geospatial data • On-Site interviews with representative sample of stakeholders to identify LRS requirements at statewide level (CDM Smith has budgeted 2 people for one week on-site) • Develop a document summarizing and prioritizing Caltrans’ LRS business needs and technical requirements • Develop a document summarizing Statewide LRS requirements Task 3 – Analysis of Alternatives for Caltrans’ LRS-Related Business Needs • Conduct a best practices review and develop whitepaper • Conduct a comparative analysis of industry standard LRS solutions to meet Caltrans requirements • Develop and deliver business case analyses documentation • Develop document which contains results of solution comparative analyses Task 4 – System Development Plan for Caltrans • On-Site Meetings with Caltrans project management and technical staff (CDM Smith has budgeted 2 people for two days on-site) • Development and delivery of a draft System Development Plan • Development and delivery of a final System Development Plan Task 5 – Final Report and Presentation • Develop draft Final Report with Executive Summary • Develop Project Summary PowerPoint Presentation • Develop and deliver Final Report with Executive Summary

No document attached.

Linear Referencing System (LRS) System Development Plan

General Information
Solicitation Number: 1388
Status: Solicitation withdrawn
Date Posted: Nov 21, 2014
Last Updated: Nov 25, 2014
Solicitation Expires: Nov 21, 2015
Lead Organization: California Department of Transportation
Financial Summary
Suggested Contribution:
Commitment Start Year: 2014
Commitment End Year: 2016
100% SP&R Approval: Not Requested
Commitments Required: $300,000.00
Commitments Received:
Contact Information
Lead Study Contact(s): Robert Buendia
robert.buendia@dot.ca.gov
Commitments by Organizations
No data available.

Background

State Departments of Transportation commonly use an LRS for identifying the locations of features, events, and activities along a transportation network. Caltrans maintains an LRS for the State Highway System (SHS) and is developing an LRS for all functionally classified roads that are not part of the SHS. The Plan will take into account all current LRS activities or projects within the Division of Research, Innovation and System Information (DRISI), including but not limited to, On-system (State Highway System) LRS, Off-system (All Local Roads) LRS project, meeting federal reporting mandates, and other LRS activities/projects that may have an impact. It will also consider all LRS-related business needs (beyond DRISI) for Caltrans. The System Development Plan will be the foundation to meet the business demands for Caltrans’ future LRS development.

Objectives

The primary purpose of this project is to develop a “Linear Referencing System (LRS) System Development Plan” (Plan) to document Caltrans’ LRS-related business requirements and prioritize future LRS system improvements. In order to meet this purpose, the Plan must be comprehensive in scope, must enable the LRS to meet current and future department-wide LRS-related business needs, must take into account any requirements related to interoperability between existing or planned Caltrans applications and the LRS, must consider spatial data collaboration and sharing between Caltrans and its partners, and must address meeting current federal/state/Caltrans reporting requirements all while still allowing for agile LRS development in the face of changing transportation legislation or other new mandates. The secondary purpose of this project is to complete an assessment of the State of California’s anticipated LRS requirements (on a high level) and ensure that what gets incorporated under Caltrans’ business requirements does not prevent the implementation of these statewide requirements at a future date.

Scope of Work

SUMARY OF ACTIVITIES AND DELIVERABLES BY TASK Task 1 – Project Management • Project Setup - Coordination and Communication with Caltrans and FHWA • Schedule Kickoff Meeting • Create draft communication plan, risk management plan, Change Management Plan and project work plan • Create project website (eRoom) for project management, communication, document sharing • Conduct project kickoff • Deliver final communication plan, risk management plan, Change Management Plan and project work plan. • Develop project status PowerPoint presentation and update monthly • Conduct bi-weekly internal project management calls • Conduct bi-weekly Project Team calls with Caltrans and FHWA • Maintain communication, risk management and project work plans • Provide monthly progress reports to Caltrans Contract Manager Task 2 – Assess Caltrans’ LRS-Related Business Needs and California’s LRS Requirements • On-site interviews with selected Caltrans Divisions and Districts to identify LRS business needs (CDM Smith has budgeted 2 people for two weeks on-site) • Conduct analysis of Caltrans’ LRS requirements, data structures, maintenance, data sharing and federal requirements regarding geospatial data • On-Site interviews with representative sample of stakeholders to identify LRS requirements at statewide level (CDM Smith has budgeted 2 people for one week on-site) • Develop a document summarizing and prioritizing Caltrans’ LRS business needs and technical requirements • Develop a document summarizing Statewide LRS requirements Task 3 – Analysis of Alternatives for Caltrans’ LRS-Related Business Needs • Conduct a best practices review and develop whitepaper • Conduct a comparative analysis of industry standard LRS solutions to meet Caltrans requirements • Develop and deliver business case analyses documentation • Develop document which contains results of solution comparative analyses Task 4 – System Development Plan for Caltrans • On-Site Meetings with Caltrans project management and technical staff (CDM Smith has budgeted 2 people for two days on-site) • Development and delivery of a draft System Development Plan • Development and delivery of a final System Development Plan Task 5 – Final Report and Presentation • Develop draft Final Report with Executive Summary • Develop Project Summary PowerPoint Presentation • Develop and deliver Final Report with Executive Summary

No document attached.

Currently, Transportation Pooled Fund is not supported on mobile devices, please access this Web portal using a desktop or laptop computer.