Ohio Department of Transportation West Broad St., Columbus, OH Request for Qualifications. for

Transcription

1 Ohio Department of Transportation 1980 West Broad St., Columbus, OH Request for Qualifications for Transportation Asset Management Decision Support Tool Office of Technical Services 07/21/2015

2 Contents: I. Introduction II. General Purpose and Scope of the Application III. RFQ Procedure and Further Expectations IV. RFQ Responses

3 I. Introduction This is a Request for Qualifications (RFQ), and does not constitute a commitment, implied or otherwise, that the Ohio Department of Transportation (ODOT) will take procurement action in this matter. This RFQ is being used to gather information for ODOT to make decisions regarding the development/purchase of a Transportation Asset Management Decision Support Tool. This RFQ is designed to provide Respondents with the information necessary for the preparation of an appropriate response. It is not intended to be comprehensive, and each Respondent is responsible for determining all factors necessary for submission of a comprehensive response. Responses should be based on the material contained in this RFQ or any other relevant information the Respondent thinks is appropriate. By submitting a response, each Respondent agrees that it will not bring any claim or have any cause of action against the ODOT, the State of Ohio, or any employee of ODOT or the State, based on any misunderstanding concerning the ODOT s failure, negligent or otherwise, to provide the Respondent with pertinent information as intended by this RFQ. Information submitted in response to this RFQ will become property of the State of Ohio. The State of Ohio will not pay for any information herein requested nor is it liable for any cost incurred by the vendor. II. General Purpose and Scope of the Application The Office of Technical Services has been charged with recommending a framework that will allow for the establishment of a transportation asset decision-making application which will interact with transportation data and inventory applications within ODOT. This is a business process referred to as Transportation Asset Management. The role of the Transportation Asset Management process is to identify, manage, and leverage all related assets. Through the use of management systems, engineering, economic analyses, and other tools, ODOT can comprehensively view the state of assets, and evaluate data before determining how specific resources should be deployed. Another key outcome of the process is to support investment decisions and demonstrate the return on those investments both quantitatively and qualitatively. In order to support these processes, it is necessary to have an application to facilitate the decision making processes within ODOT. ODOT will consider products currently available or yet to be developed which will facilitate decision-making processes across a variety of transportation data. The data will include (but is not limited to) core datasets such as pavement and bridge data. This data is held in multiple other databases and applications resting on various platforms. The expectation is that a user will be able to utilize the application to extract relevant information for assisting transportation asset management decisions. Basic components and processes will include: 1. Effective data integration and data sharing, with the ability to access data from various databases and applications 2. Geo-spatial storage of data 3. Ability to use transportation linear data within the datasets being analyzed 4. Ability to summarize many datasets into one result

4 5. Application and supporting framework to use efficient data processing processes 6. Ability to analyze data from a transportation/engineering point of view 7. Asset information to be easily available to various levels of ODOT decision makers. 8. If the application uses a dashboard or similar front-end, there must be functionality available to drill down to the data needed. The user should be able to see the root of any deficiencies they are investigating. 9. Ability to view multiple datasets at once, and their relationship to an area or location 10. Ability to handle cross-asset planning, with outputs including (but not limited to): age, location, future conditions, value of assets, trends, and degradation over time 11. Provide data (results) to support work plans 12. Provide an option to store summary tables capturing the user s analyzed data 13. Ability to add weighting factors on each of the assets a user is analyzing in order to obtain a composite index 14. Reporting capabilities, with ability to export reports in multiple formats 15. Application must be able to work in a distributed fashion 16. Where possible, the application must leverage the asset information within ODOT s TIMS (Transportation Information Mapping System) 17. Leverage current technology where possible 18. Generate mapping results and map output scenarios 19. Application must reference and integrate with ODOT s LRS (Linear Referencing System) 20. Provide analytical tool and graphical presentation to evaluate: asset performance, design & maintenance policies, and funding level vs. performance III. RFQ Procedure and Further Expectations In order to proceed, ODOT is requesting information relating to vendor details and experience in order to evaluate the experience levels of potential vendors that will move forward to the Request for Proposal (RFP) process. RFQ Responses are due August 12 th, (RFQ Response information is detailed in the next section, IV.) ODOT will score the responses based on: Transportation experience (applicable to the components and processes listed in Section II), as well as DOT-specific transportation experience Experience integrating with a customer s existing technology Transportation asset management experience Transportation cross-asset analysis experience Business intelligence experience Transportation experience of project team members

5 PROCEDURE: The Vendors with the highest scoring responses will then be notified by ODOT that their RFQ Response qualifies them to continue in the process. ODOT will then send the Request for Proposal (RFP) to only the Vendors that qualified to continue on in the RFQ and RFP procedure. Additionally, a meeting will be held, at a date to be determined, to demonstrate the existing prototype. During this meeting, Vendors may ask questions, as well as hear the other Vendor questions that are being asked. Vendors may then provide a response according to the procedure which will be outlined in the RFP. After the deadline for RFP responses has passed, ODOT will score the RFPs, then schedule on-site meetings at ODOT s Central Office with Vendors that submit a feasible proposal. This meeting will also be a time for ODOT to ask questions about the submitted RFP responses from the Vendors and for further explanations to be given by the Vendors as appropriate. Once the above steps are completed, ODOT will make a Vendor selection. IV. RFQ Responses Please include the below information when responding to this RFQ. All responses must have pages numbered and be ed as PDF or Word documents to: Dean Tran, ODOT Project Manager Dean.Tran@dot.ohio.gov Responses are due by 5pm EST on Wednesday, August 12 th, Respondent Information Organization Point of Contact Phone Number Address 2. Vendor (Company) Experience Vendors must have a demonstrated track record of successfully implementing Transportation based solutions.

6 For each completed project relevant to the TAMDST, and demonstrates Transportation experience by the Vendor that is applicable to the components and processes listed in Section II, provide the following: Company/DOT Name Company/DOT Address Contact Name Contact Title Contact Phone Number Contact Date Project Sold (Month/Year) Project Start Date (Month/Year) Project End Date (Month/Year) Date Solution in Production (Month/Year) Duration to Configure (Provide in Months or Years as applicable) Duration in Production (Provide in Months or Years as applicable) Provide a brief description of how the solution is operating in Production with Company/DOT named above. If the solution required integrating with existing technology, provide a brief description of how this was done. If the solution included transportation asset management and/or cross-asset analysis, provide a brief description of this. 3. Vendor (Resource) Experience For specific resources which would be involved with the TAMDST, should Vendor be selected after the RFP process, provide the following: Name Title Resume, including detailed transportation experience