FLORIDA DEPARTMENT OF TRANSPORTATION Procurement Office

605 Suwannee Street, MS 20 Tallahassee, Florida 32399-0450

Phone: (850) 414-4381

ADDENDUM NO. 1 DATE: March 26, 2019

BID No.: DOT-RFP-19-9070-SJ

BID Title: Integrated Roadway Asset Identification System (IRAIS)

OPENING DATE: Thursday, April 4, 2019 @ 3:00PM LOCAL TIME

Notice is hereby given of the following changes to the above-referenced SOLICITATION:

Questions and Answers are found below

Updated Scope of Services attached below – updates made for clarity of certain qualifications

All Items Report Inventory attached below – contains a list of all reports generated by the RCI and its related systems

RCI Integrated Applications attached below – contains a list of all the applications related to the RCI data.

Updated Section 22 Proposal Format Instructions added below

Bidders/Proposers must acknowledge receipt of this Addendum by completing and returning to the

Procurement Office, by no later than the time and date of the bid/proposal opening. Failure to do so

may subject the bidder/proposer to disqualification.

Sherill Johnson, Procurement Agent

_____________________________________ Bidder/Proposer

_____________________________________ Address

_____________________________________

_____________________________________ Submitted by (Signature)

Failure to file a protest within the time prescribed in Section 120.57(3), Florida Statutes, or failure to post the bond or other security required by law within the time allowed for filing a bond shall constitute a waiver of proceedings under Chapter 120, Florida Statutes.

Question 1 Whether companies from Outside USA can apply for this? (like, from India or Canada)

Answer 1 Yes, companies outside the US may apply for this project.

Question 2 Whether we need to come over there for meetings?

Answer 2 On-site meetings will be required of the project. WebMeetings, teleconferences may be used as necessary.

Question 3 Can we perform the tasks (related to RFP) outside USA? (like, from India or Canada)

Answer 3 No.

Question 4 Can we submit the proposals via email?

Answer 4 Please see Special Condition 27 of the solicitation document

Question 5 Section 22.2 of the RFP mentions both a 25-page limit and a 30-page limit for the Technical Proposal. Can you confirm that there is a 30-page limit?

Answer 5 There is indeed a 30-page limit

Question 6 Do covers, tabs, cover letter, and table of contents count toward the page limit for the Technical Proposal? Do required forms count toward the page limit?

Answer 6

Yes, the covers, tabs, cover letter and table of contents do count toward the page limit for the Technical Proposal; The required forms (i.e. Drug Free Workplace, Bid Opportunity List, Anticipated DBE Participation, Vendor Scrutinized Companies) will not count toward that page limit.

Question 7

Should all of the required forms (Drug Free Workplace Program Certification, Bid Opportunity List, Anticipated DBE Certification Statement, and Vendor Certification Regarding Scrutinized Companies Lists) be included in the Part II. Price Proposal volume?

Answer 7 Yes, all forms should be included in Part II – Price Proposal

Question 8

If we propose completing the implementation of Roads and Highways for FDOT in less than three years, would it be acceptable to use the entire $1,000,000.00 maximum budget to accomplish this, even if this means that the budget is completely exhausted with significant time left on the overall contract?

Answer 8 No

Question 9 Is the intent of the $1,000,000.00 maximum budget to cover all activities performed over the three-year duration of the contract?

Answer 9 Yes

Question 10 Can the State, at its discretion, choose to add funding over and above the $1,000,000.00 in order to complete possible future task orders related to activities overlaying functionality onto the completed Roads and Highways implementation?

Answer 10 No

Question 11 May we propose additional project resources/resource categories in additional to the seven resource categories listed in the RFP?

Answer 11 No

Question 12 Will the State be responsible for repairing/mitigating all RCI data issues identified by our Project Team?

Answer 12

The FDOT will provide resources to repair and mitigate source data (RCI) issues that may need to be changed before migration into the R&H. The FDOT understands RCI data and workflows migrated to R&H may change or impact the legacy data. The priority of data migration of RCI data to R&H has not been fully identified. However, in these situations, the vendor will be required to support the analysis, coordinating, and facilitation of the changes of RCI data and support the workflow development for knowledge transfer to the Department.

Question 13 Will FDOT retain its existing 8-character route identifier structure?

Answer 13 The FDOT will have to retain the ROADWAY ID structure for Department legacy systems. A new Unique ID structure for roadway sections has been part of the design considerations for movement into R&H.

Question 14 Is FDOT open to modifying the existing RCI/LRS reconciliation process (package correction form) with a guided workflow process to help reduce any potential timeliness issues with correcting discrepancies in the data?

Answer 14 The RCI/LRS reconciliation process may provide guidance to future undetermined process to how FDOT manages timely up to date information of RCI and the LRS. The current process would be a baseline to support future processes.

Question 15 Does FDOT wish to maintain its existing spatial projection for the centerlines, calibration points, route network, and event data as NAD 1983 UTM Zone 17N?

Answer 15 The current projects will be retained until further notice.

Question 16 Does FDOT wish to maintain the 3-decimal precision of the begin/end post of the routes and events in Roads and Highways?

Answer 16 Yes

Question 17 Will the existing centerline, route, and measure data maintenance process continue with the RCI/LRS Coordinator working with District editors? Approximately how many centerline editors will be involved?

Answer 17

We expect to have a core user group receive training from the selected vendor and be capable of using the Roads and Highways environment to train other Department users. The official design, user base, and workflows of a future system has not been decided so the specific roles have not been identified yet.

Question 18

Will the existing six “owning offices” of RCI data each have editor staff who will be creating and maintaining the RCI data as events within Event Editor in Roads and Highways? Approximately how many event editors will be involved? Will the event editors be centrally located, or located in the District offices?

Answer 18 It is expected the responsibility and governance of the data collection requirements under the six Central Office owning offices will continue until further notice. District users have not been identified yet.

Question 19 What is the approximate number of individual data items that FDOT wishes to migrate as part of this project? Will data items deemed “obsolete” be included in the migration?

Answer 19

The Project team SMEs have normalized the RCI database and created an FDOT prototype to meet the R&H environment in the Azure Cloud. ESRI is also supporting the Department by providing assistance to understand and utilize the R&H prototype under the ESRI Enterprise Advantage Program where the Department selected a couple dozen RCI features to test in the prototype. The Department has not prioritized what features or characteristics will be managed in R&H.

Question 20 What is the approximate number of reports that FDOT wishes to produce from the LRS and RCI data as a result of this project? Can a listing of existing reports and sample reports be provided?

Answer 20

The Project team has not identified all the reports to be developed under the R&H environment. A copy of the reports generated by RCI and its related systems is attached below. Critical reporting functions will be developed under the legacy system until the Department has completed the end to end system design.

Question 21 What is the approximate number of systems that FDOT wishes to integrate LRS and RCI data with as a part of this project? Can a listing, description, and what LRS and RCI data is usd by those integrating systems be provided?

Answer 21 The number of systems and their functions has not been prioritized for integration into R&H. A listing of systems associated with RCI data can be provided.

Question 22 Does FDOT have any additional plug-ins or extensions that will be used alongside Roads and Highways in creating and maintaining centerlines, routes, and measures that need to be considerations of this project?

Answer 22 Additional required components have not been identified.

Question 23

Under the “Design and Data Architecture Services” section of the RFP, a solution for the management of vector and raster datasets within an enterprise Data Warehouse is requested (#9, p 30 of PDF, p 7 of Exhibit A; #3 p 31 of PDF, p 8 of Exhibit A). Besides the datasets involved with the LRS and RCI migration, what other vector datasets and what raster datasets might be included?

Answer 23 The Department has not decided what data may be provided in the Data Warehouse or the GeoDataWarehouse at this time.

Question 24

FDOT has maintained legacy documentation over the years for the RCI data and the various LRS/RCI update processes. Will content of this documentation, and perhaps other legacy documentation need to be updated as part of this project, in addition to any new documentation supporting the new Roads and Highways solution? Will FDOT be updating these documents?

Answer 24

Documentation of the work performed, delivered and accepted by the Department’s project team will be expected. Recommendations, changes, and updates for legacy documentation changes would be desired from the vendor as new business workflows are developed.

Question 25 What is FDOT's current enterprise reporting software(s)? Are there any plans to update the existing reporting software(s) or migrate to a different reporting platform(s)?

Answer 25

RCI web application reports are generated through WebFocus. Certified Public Mileage reports are generated through Oracle housed RCI extracts that combine RCI mileage data with other local mileage application data accessible through a customized MS Frontpage web tool to provide access. The exports are customized in PDF for public dissemination. The Department is developing a SAS Business Intelligence Data Warehouse with a Tableau data analytics dashboard to work with system of record data from R&H for reporting purposes.

Question 26

Does FDOT currently have adequate licensing levels for an enterprise implementation of Esri Roads and Highways, inclusive of ArcGIS Server and Desktop licenses? Does FDOT have a specific version of Esri Roads and Highways that will need to be implemented based on existing GIS infrastructure?

Answer 26 The Department currently licenses 3 Roads & Highways for Server (4 cores), 2 Roads & Highway for Server-Staging (4 core) and 6 concurrent Roads & Highways Desktop licenses. All current installations are 10.6.1.

Question 27

Does FDOT have an existing and dedicated server environment for Esri Roads and Highways, or does this environment need to be procured as part of this project by FDOT? What are the existing infrastructure environment tiers that FDOT requires (e.g., Development / Production, Development / User Acceptance Testing / Production, etc.)?

Answer 27 FDOT currently has a shared server environment in development. A dedicated environment procurement will not be part of this project. The Departments Roads and Highway licenses support at a minimum development and production environments.

Question 28 Will FDOT support the use of the ArcGIS Data Interoperability Extension for use in the data migration process? Does FDOT have current licensing for the Data Interoperability Extension (not required)?

Answer 28 ArcGIS Data Interoperability is available for use by Department Employees and in-house Contractors

Question 29 In the RFP (p 3 of pdf), the maximum amount allowed for travel expenses is stated at $35,000. Should the travel expenses be included as part of the budget, or should the travel expenses be considered separate and apart from the budget of this project?

Answer 29 The maximum amount of travel expenses is part of the budget of this project.

Question 30

The RFP (Section 22.2) states “The Technical Proposal is limited to a maximum of 25 pages, including resumes. Any proposal exceeding the 30-page limit will be considered Non-Responsive and will not be evaluated. “. Does FDOT consider the Executive Summary (5 pages) separate from the Technical Proposal which would include Proposers Business and Management Plan (10 pages) and the Proposers Project Plan (15 pages)?

Answer 30

No, the 25 pages was a typographical error. The Technical Proposal is limited to a maximum of 30 pages as defined within the solicitation document. Executive Summary – Maximum of 5 pages

Proposer’s Business and Management Plan – Maximum of 10 pages Proposer’s Project Plan – Maximum of 15 pages (including resumes)

Question 31 The RFP specifically identifies staffing classifications in (Exhibit A, page 10). Are vendors limited to listed classifications or may additional ones (i.e. Business Analyst, Deputy Project Manager, Administrator) be included in the response?

Answer 31 Please see Answer 11

Question 32

Data Integration Services (Exhibit A – Page 8) – The RFP mentions “1. Conduct integration evaluations and solutions of RCI and the RCI related systems”. Has FDOT identified the RCI related systems and if so, is a list of these systems available?

Answer 32

The FDOT has not identified all integration requirements of RCI and the related RCI systems. The FDOT can provide a list of the systems RCI interfaces with. It should be noted a main focus on integration would occur with TDA office applications that are involved with performing system of record functions. Other systems outside the TDA Office will primarily require obtaining access to the data from RCI

Question 33

Data Development and Implementation Services (Exhibit A, page 8) – The RFP mentions “4. Perform creation, coding, and editing of points, lines and polygons.” and “7. Perform data entry and updating of data attributes.” Can FDOT elaborate on any specific known systematic issues or gaps where the Vendor would be required to create new data or update erroneous data?

Answer 33

The bullets referenced are intended to cover any type of data editing that may be required to develop RCI data into the R&H environment. FDOT expects RCI data business rules may be changed as workflows are migrated into the R&H environment. It has not been determined what RCI workflows may be prioritized.

Question 34

Pdf pg. 28 Exhibit A pg. 5 Project Task Work Orders – Does FDOT plan to release one task work order per each of the 6 items listed A through F? Will task work orders be released in the order listed in the RFP? Does FDOT envision issuing task work orders concurrently?

Answer 34

The RFP lists activities required of the vendor are not in a particular order. Task Work Orders will be issued in consensus of the FDOT and the vendor. Task Work Orders will be in line with the FDOT project management team and may run concurrent. Depending on the progress of the FDOT's efforts to define the future state model and its related processes, the FDOT may require support from multiple areas from the RFP at one time.

Question 35

Pdf pg. 29 Exhibit A pg. 6 Task work order example B, bullet 2 references providing “solutions and guidance for systems integration and implementation testing” – does FDOT consider it in-scope of this effort to see systems integrations (such as with TDMS or safety) through to implementation, or for the vendor to make recommendations for how FDOT may execute system integrations in the future? If FDOT intends the vendor to execute systems integrations, what systems are desired to be integrated?

Answer 35

The prioritization of integration has not been identified yet. FDOT is currently reviewing how they may handle the numerous impacts of RCI systems and how to prioritize them. The vendor may be asked to review the needs and requirements and provide feedback and recommendations.

Question 36

Pdf pg. 29 Exhibit A pg. 6 Task work order example B, bullet 6 references historical transportation data record tracking. Does FDOT intend to migrate multiple historical representations of the same roads or road network into the R&H database, or is this portion of this task intended to maintain history of the road network moving forward?

Answer 36 FDOT recognizes the need to maintain historical transportation data record tracking as part of the Work Program and state public data records requests. It has not been determined how FDOT may handle historical tracking of spatial and tabular data.

Question 37

Pdf pg. 31 Exhibit A pg. 8 Task work order example C, bullets 4, 7, and 9 (as examples) reference the vendor performing edits. Are these examples of editing intended to correct existing data quality issues, or add data to complete otherwise incomplete datasets using new data?

Answer 37

The bullets referenced are intended to cover any type of data editing that may be required to develop RCI data into the R&H environment. FDOT expects RCI data business rules may be changed as workflows are migrated into the R&H environment. It has not been determined what RCI workflows may be prioritized.

Question 38

Pdf pg. 31 Exhibit A pg. 8 Task work order example C, bullet 6 references calibration of data; does FDOT’s legacy LRS have routes calibrated in multiple methods, and does FDOT envision maintaining any manual (forced, DMI, etc.) route calibration in Roads and Highways?

Answer 38 FDOT has not determined the business rules on how calibration may be handled by moving data into the R&H environment. FDOT currently performs calibration of routes through DMI, GPS, and field surveys in agreeance with aerial imagery.

Question 39

Pdf pg. 32 Exhibit A pg. 9 Task work order example E; can FDOT provide an estimate of the number of DOT divisions and users that are anticipated to be R&H users at the completion of the project?

Answer 39

An estimate of over 300 RCI users have been identified through RACFIDs of FDOT RCI users on the mainframe. The business workflows for these users in their respective office functions have not been identified on how they may be migrated into the R&H environment.

Question 40 Does FDOT already have Esri R&H extension licenses and necessary hardware procured to support the R&H implementation?

Answer 40 The Department currently licenses 3 Roads & Highways for Server (4 cores), 2 Roads & Highway for Server-Staging (4 core) and 6 concurrent Roads & Highways Desktop licenses.

Question 41 Does FDOT have a desired version of ArcGIS software at which to implement Roads and Highways? I.e. ArcGIS 10.5.1, ArcGIS 10.6.1, etc.

Answer 41 All current Roads & Highways installations are 10.6.1.

Question 42 Can the proposal include a single title page and cover letter? (not included in the page count as detailed in the proposal)

Answer 42 A title page and cover page will be part of the page count. These should be included in the executive summary.

Question 43 Pdf pg. 2 Exhibit C Can the vendor provide multiple staff per labor category or just one?

Answer 43 Yes. Multiple staff may be provided for the single job category.

Question 44

Pdf pg. 2 Exhibit C Can the vendor provide multiple levels and rates for Personnel Classifications? For example, can we show separate rates for a “Data Architect Jr” and “Data Architect Sr”?

Answer 44 No, but the Technical Product Support Analyst and the Technical Product Support Specialist may be an area to propose senior and junior staff. Please see the revised Exhibit A – Scope of Services attached below.

Question 45

Pdf pg. 2 Exhibit C Can the vendor list individual staff members for multiple categories?

Answer 45 Yes, if the staff can meet the requirements of multiple job classifications requirements.

Question 46

Pdf pg. 17 Section 22.2 3.a bullet 2 Proposer’s Project Plan requests: “Identify each individual and the percent of time (percent should be based on the hours allocated in the Price Proposal Form) that each person would be assigned to each major task in the Scope of Program Services. For example, if the Proposer has an individual assigned to marketing 50% of the time, that equals 1,040 hours.” Hours are mentioned in reference to the Price Proposal Form and in the example. Where are hours requested on the Price Proposal Form?

Answer 46 The vendor must be able to fill out at Price Proposal with the estimated % of work effort. Please refer to RFP changes.

Question 47

Pdf pg. 2 and Pdf pg. 17 Exhibit C and Section 22.2 3.a bullet 2 And Section 22.2 3.c Exhibit C requests: “The Estimated Percentage of Work column must total to 100% Proposer’s Project Plan requests: “Identify each individual and the percent of time (percent should be based on the hours allocated in the Price Proposal Form) that each person would be assigned to each major task in the Scope of Program Services. For example, if the Proposer has an individual assigned to marketing 50% of the time, that equals 1,040 hours.” Work Plan requests: “Proposer shall provide a Work plan which outlines the estimated staff-hours for each skill classification that will be utilized …" Can FDOT provide more detail/explanation for these three sections as to how they are to relate to one another?

Answer 47 The vendor must be able to fill out at Price Proposal with the estimated % of work effort. Please refer to RFP changes.

Question 48

Pdf pg. 34-Exhibit pg. 11 Exhibit A:Contractor Project Staffing Can FDOT clarify and explain the need for this requirement “The project manager should be familiar with roadway and asset data management business practices of Departments of Transportation and have recent (minimum of five years) and relevant project experience implementing R&H.”?

Answer 48

This detail refers to the familiarity of the project manager being able to understand the need of Departments of Transportation to manage roadway and asset data business practices to be implemented into R&H. Please refer to the scope of service changes removing the minimum requirement

Question 49

Pdf pg. 34-Exhibit pg. 11 Exhibit A: Contractor Project Staffing Would FDOT consider removing this requirement from project manager and adding it to Technical Product Support Analyst? “The project manager should be familiar with roadway and asset data management business practices of Departments of Transportation and have recent (minimum of five years) and relevant project experience implementing R&H. Additional experience should include integrating business functions and configuring the R&H and providing solutions or recommendations where R&H is unable to meeting the business functions of the Department.”

Answer 49

The technical lead under the Technical Product Support Analyst will be required to have at least five years of experience implementing R&H. Please refer to the scope of services changes removing the requirement from the Project Manager and changing the existing two years of experience under the Technical Product Support Analyst to five years of experience.

Question 50

Pdf pg. 34-Exhibit pg. 11 Exhibit A: Contractor Project Staffing Would FDOT consider removing requirement for PMP if the Project Manager has the following qualifications? “The project manager should be familiar with roadway and asset data management business practices of Departments of Transportation and have recent (minimum of five years) and relevant project experience implementing R&H. Additional experience should include integrating business functions and configuring the R&H and providing solutions or recommendations where R&H is unable to meeting the business functions of the Department.”

Answer 50 No, the PMP requirements are a requirement of Department and State project standards.

Question 51

Pdf pg. 33-Exhibit pg. 10 Exhibit A: Contractor Project Staffing The section includes a statement that, “Experience must be verifiable in resume and via references.” Are we to include references with our proposal or only if requested as follow-up? If we are to include references in our proposals, please provide direction on how many references, what info you want for each, and where this information should be provided.

Answer 51 Yes, three references should be provided

Question 52

Pdf pg. 17 Proposer’s Project Plan The proposal is requesting within 15 pages for vendors to provide/detail their Technical Approach, Work Plan, Facility Capabilities, and Personnel Qualifications for seven (7) positions providing “names of key personnel on the Proposer’s team, as well as well as resume for each individual proposed...” Can we request the resumes to be provided as a separate appendix?

Answer 52

The technical approach is limited to the pages listed. FDOT expects the remaining 8 pages will be sufficient space to detail the proposers project plan to meet the FDOT's desired task work order based activities due to the amount of internal resources has allocated to the IRAIS project. Based on this project strategy approach at this time, FDOT requires an experienced and proven vendor to help the Department implement a successful foundation of Roads and Highways for Department staff to acquire the knowledge transfer to continue implementation with internal resources.

22) PROPOSAL FORMAT INSTRUCTIONS

22.1 General Information

This section contains instructions that describe the required format for the proposal. All proposals submitted shall contain two parts and be marked as follows:

PART I TECHNICAL PROPOSAL NUMBER DOT-RFP-19-9070-SJ: (One Separately Sealed Package for Technical)

PART II PRICE PROPOSAL NUMBER DOT-RFP-19-9070-SJ: (One Separately Sealed Package for Prices)

THE SEPARATELY SEALED PACKAGES MAY BE MAILED TOGETHER IN ONE ENVELOPE OR BOX.

22.2 Technical Proposal (Part I) ( 4 copies) (Maximum of 30 pages, including Resumes) (Do not include price information in Part I)

The Proposer must submit one ( 1 ) original and three ( 3 ) copies of the technical proposal which are to be divided into the sections described below. The Technical Proposal is limited to a maximum of 30 pages, including resumes. Any proposal exceeding the 30-page limit will be considered Non-Responsive and will not be evaluated. Since the Department will expect all technical proposals to be in this format, failure of the Proposer to follow this outline will result in the rejection of the proposal. The technical proposal must be submitted in a separate sealed package marked "TECHNICAL PROPOSAL NUMBER DOT-RFP-19-9070-SJ: ".

1. EXECUTIVE SUMMARY (maximum five pages)

The Proposer shall provide an Executive Summary to be written in nontechnical languageto summarize the Proposer's overall capabilities and approaches for accomplishing theservices specified herein. The Proposer is encouraged to limit the summary to no morethan five (5) pages.

2. BUSINESS AND MANAGEMENT PLAN (maximum 10 pages)

The Proposer shall provide a management plan which describes administration,management and key personnel.

a. Business QualificationsThe Proposer should include a description of the organizational structure andmanagement style established and the methodology to be used to control costs,services reliability and to maintain schedules; as well as the means of coordinationand communication between the organization and the Department.

The Proposer must possess a minimum of five (5) years’ experience providingimplementation services for roadway data and asset management systems forDepartment of Transportation agencies using the ESRI Roads and Highwaysextension. This section must include, but is not limited to the following:

• Company Work History - supports the Proposer’s years of experiencethat would include a listing of current and past types of work/contracts, theyears worked on each contract, the length and scope of each contract, thename and phone number for each client’s project manager.

• The number of years of experience and the types of experienceassociated with the providing implementation activities of the

Revised Section 22 - Proposal Format Instructions (Revised 03-22-2019)

1

Environmental Research Science Institute Roads and Highways extension into a transportation agency business, providing roadway and asset data solutions, supporting the Highway Performance Monitoring System submission process, and performing knowledge transfer to clients.

• Work Capacity - the number, types, and scope of other projects currently worked on by the Proposer, to determine the Proposer’s capacity to complete this project. Include projects by principals and major staff and the amount of time each individual is devoted to each ongoing project.

b. Management Structure

The Proposer must describe how their business is currently managed (NOT how you would manage this contract, but how you currently manage your business), including but not limited to the following basic functions of management:

• Planning (the vision, mission and values; strategic plans; long and short term business plans; goals and objectives and how they will be accomplished; an explanation of your planning process)

• Organizing/Staffing (the allocation of resources to accomplish the goals and objectives established during the planning process; the organization’s structure showing an organizational chart, reporting relationships, responsibilities, and coordination required; the process to recruiting, selecting, hiring and training of employees)

• Directing/Leading (communicating the goals and objectives; establishing direction and influencing staff to follow that direction; problem solving; establishing individual performance goals; coaching and counseling; delegating; supervising actions of staff; developing positive interpersonal relationships)

• Controlling (monitoring and adjusting resources and processes to achieve goals and objectives; monitoring and evaluating the business success; monitoring and evaluating employees; measures used and evaluated to determine success; holding staff accountable; monitoring compliance with contractual requirements including the timely submittal of invoices and activity reports; management controlling strategies; cost control strategies; monitoring service provided)

3. PROJECT PLAN (Maximum 15 pages)

The Proposer shall provide a technical plan which explains their technical approach to the

project, facility capabilities, and prior relevant experience.

a. Personnel Qualifications The Proposer should provide the names of key personnel on the Proposer's team, as well as a resume for everyone proposed and a description of the functions and responsibilities of each key person relative to the task to be performed. The approximate percent of time to be devoted exclusively for this project and to the assigned tasks should also be indicated. The Proposer should provide a summary, with description, date, and location of the prior relevant experience they have acquired in providing/performing this work. The Proposer must submit a proposed organizational chart and provide the names and resumes of each individual (by personnel classification as listed on the price proposal form, Exhibit X – refer to the “Contractor Project Staffing” section of the Scope of Program Services) that will be working on this contract.

Revised Section 22 - Proposal Format Instructions (Revised 03-22-2019)

2

• Each resume must identify each employer with the years of service, the duties and responsibilities for that employer, and a phone number for a contact person.

• Identify the individuals the estimated percentage of work and if the staff will be working on-site. This number should match the information on the Price Proposal sheet.

• Include recent and relevant experience related to implementing the ESRI Roads and Highways to support state transportation agencies roadway data and asset management activities.

b. Technical Approach The Proposer should explain the approach, capabilities, suggested tasks, and means to be used in accomplishing the tasks in the Scope of Services, and where significant implementation difficulties may be anticipated and resolved. Any specific techniques to be used should also be addressed.

c. Work Plan

The Proposer shall provide a proposed Work Plan which outlines the necessary project staffing for implementation activities of the ESRI Roads and Highways extension.

d. Facility Capabilities

The Proposer should provide a description and location of the Proposer's facilities as they currently exist and as they will be employed for this work

22.3 Price Proposal (Part II) ( 2 copies)

The price proposal information is to be submitted in a separate sealed package marked "PRICE PROPOSAL NUMBER DOT-RFP-19-9070-SJ ". The Price Proposal information shall be submitted on the forms provided in the Request for Proposal.

22.4 Presenting the Proposal

The proposal shall be limited to a page size of eight and one-half by eleven inches (8½" x 11"). Foldout pages may be used, where appropriate, but should not exceed five (5) percent of the total number of pages comprising the proposal. Type size shall not be less than 10 point font. The proposals should be indexed and all pages sequentially numbered. Bindings and covers will be at the Proposer's discretion.

Unnecessarily elaborate special brochures, art work, expensive paper and expensive visual and other presentation aids are neither necessary nor desired.

It is recognized that existing financial reports, documents, or brochures, such as those that delineate the Proposer's general capabilities and experience, may not comply with the prescribed format. It is not the intent to have these documents reformatted and they will be acceptable in their existing form.

Revised Section 22 - Proposal Format Instructions (Revised 03-22-2019)

3

1 | P a g e

Florida Department of Transportation

IRAIS Scope of Services

Integrated Roadway Asset Identification System

(IRAIS) Project

2 | P a g e

Table of Contents

1. Integrated Roadway Asset Identification System (IRAIS) Project Background ......................................... 3

Summary ................................................................................................................................................... 3

Problem Statement ................................................................................................................................... 4

2. Project Task Work Orders ......................................................................................................................... 5

A. Project Planning Support Services ................................................................................................ 5

B. Design and Data Architecture Services ......................................................................................... 6

C. Data Development and Implementation Services ........................................................................ 7

D. Data Integration Services .............................................................................................................. 8

E. Training Support Services ............................................................................................................. 9

F. Report Development Support ....................................................................................................... 9

3. Contractor Project Staffing ..................................................................................................................... 10

A. Staffing Classifications ....................................................................................................................... 10

Project Manager.................................................................................................................................. 10

Technical Product Support Analyst ..................................................................................................... 11

Technical Product Support Specialist .................................................................................................. 11

Enterprise Application Integration Engineer ...................................................................................... 12

Data Architect ..................................................................................................................................... 12

Data Modeler ...................................................................................................................................... 13

Technical Trainer ................................................................................................................................. 13

B. Staffing Experience ............................................................................................................................ 13

C. Staffing Changes ................................................................................................................................. 14

D. Subcontractors ................................................................................................................................... 15

E. Mandatory Reporting Requirements ................................................................................................. 15

1. Monthly Reports ............................................................................................................................ 16

F. FDOT Contract Management ............................................................................................................. 16

4. Services/Materials Provided by the Department ................................................................................... 17

3 | P a g e

1. Integrated Roadway Asset Identification System (IRAIS) Project

Background

Summary

The implementation services for the Integrated Roadway Asset Identification System (IRAIS)

project are anticipated to support project phases that require the planning, design, migration,

conversion, configuration, and integration of the Department legacy roadway and asset data.

These services will be developed for implementation or configuration of the data management

system functions into the Environmental Systems Research Institute’s (ESRI) Roads and

Highways software suite (R&H).

FDOT desires to improve business functions, increase processing efficiency, enable GIS data

management workflows and provide reliable, accurate and consistent delivery of information

to support data driven decision-making of FDOT’s roadway data and assets. The Contractor

shall be experienced and familiar with the transportation roadway and asset data business

practices of the Department which includes providing data for transportation planning,

operational, and financial business needs. Other experience desired includes familiarity with

providing visualization options and representations to transportation data users and can

provide solutions to support the Department’s responsibility of meeting state and federal data

reporting requirements. FDOT expects the Contractor to be familiar with transportation

roadway and asset data architectures, Geographical Information Systems (GIS) data

management, Linear Referencing Systems, Straight Line Diagrams, the Federal Highway

Administration Highway Performance Monitoring System (HPMS) and related transportation

data collection systems, Video/Photo Log tools, and Business Intelligence/Data Warehouse

reporting platforms.

These services will be Task Work Order based and it is anticipated the term of the contract with

the Contractor will be three (3) years upon the date of award.

4 | P a g e

Problem Statement

FDOT has the responsibility of coordinating the planning of a safe, viable, and balanced state

transportation system serving all regions of the state, and to assure the compatibility of all

components, including multimodal facilities. To remain capable of meeting state and federal

data reporting requirements, Transportation Technology prioritizes that advancement of

enterprise systems that are technologically capable, scalable, functionally efficient. FDOT has

prioritized replacement of the Roadway Characteristics Inventory (RCI) and its related systems

whose functions are to manage statewide roadway and asset data. Originally developed in

1978, RCI is considered an enterprise business system, a core platform and is a Department

legacy system that has been customized to fit the complex business functions of FDOT.

The current business problems related to this project include the following:

• The legacy enterprise system platform technology is mainframe based and will no longer

be supported by the Department.

• Scalability and expandability for future growth of Department business data is not

available with the current technology and system.

• Data processing activities such as extracting, transferring and loading of data between

the RCI and related RCI systems require physical movement of data for additional

processing and validation and is inefficient.

• Customization of the RCI and its related systems is costly to maintain and

unmanageable.

• Advanced geospatial data collection types cannot integrate RCI system data directly;

• Time spent performing data business functions cannot be tracked and managed due to

the disparate systems.

• Performing data analysis, validation and quality control in the legacy system design is

difficult to learn and maintain and promotes data accuracy issues;

• Current system of record business rules and workflow data management create

locational data quality issues and cannot qualify as a single source of truth;

5 | P a g e

• System components and support report development will no longer be supported by

the Department.

• The sharing of RCI data to the userbase through Straight Line Diagrams and Video/Photo

Log programs are not maintained effectively in the current system.

• State and Federal data reporting require tracking roadway asset location, performance,

condition, extent, and financial information is at risk if unable to managed on time.

2. Project Task Work Orders

The Department intends to execute a Task Work Order(s) for the provision of technical and

contractual services necessary for the fulfillment of this contract providing services for all tasks

as defined in individual Task Work Orders. Overall the Contractor is expected to build the

implementation solution using R&H that would support the FDOT architecture and

environment. The Contractor will be expected to fulfill these tasks as directed by the

Department Contract Manager or the Task Work Order Manager. Such services may include:

A. Project Planning Support Services

The following activities are to provide project planning services that will support IRAIS project

coordination related to implementation of R&H:

1. Establishing and maintaining project communication within the Contractor team and the

Department and attending all project-related meetings as directed by the Department

Project Manager or Task Work Order Manager;

2. Providing project updates, in various formats, on project activities and deliverables in

various meeting formats;

3. Providing quality control and assurance for all task work order deliverables and work

activities;

4. Preparing and transmitting progress reports as required by the Department Project

Manager;

5. The Consultant Project Manager will conduct a Contractor Introductory Kickoff Meeting

at the start of the project, coordinating with the FDOT Project Manager;

6 | P a g e

6. Develop Department strategic/business plans related to Transportation data and

workflows to support FDOT transportation data conversion and migration into the

Roads and Highways data model;

7. Develop migration, implementation, and integration plans and test cases;

8. Analyze the Department’s project needs, functional, and user requirements as they

relate to the legacy system and support collection of new requirements as necessary;

9. Develop GIS data implementation plans for business workflows;

10. Develop GIS feasibility studies;

11. Develop data and application cost/benefit analysis;

12. Research project-level Operations and Maintenance (O&M) and assess status of

multiple projects and the projects’ O&M needs;

13. Assist in planning/facilitating project-level related meetings and events to support O&M

needs and Implement O&M strategies where needed.

B. Design and Data Architecture Services

The following activities support building the data design and architecture FDOT is initializing by

preparing the Department’s roadway and asset data for migration and configuration into R&H.

1. Provide transportation engineering knowledge to develop data management and

architecture solutions for roadway and asset data management systems;

2. Perform analysis on Department legacy system functions and components and their

related documentation to refine requirements and provide solutions and guidance

for systems integration and implementation testing;

3. Support development of a geospatial enterprise data architecture that allows for

visualization, analysis, archiving and reporting of Department data;

4. Perform maintenance, troubleshooting, and data management of the Department’s

enterprise GIS warehouses by developing feature services, publishing, monitoring,

and management to ensure desktop, web, cloud, and mobile users have secure

access to enterprise data;

7 | P a g e

5. Develop data, GIS and Linear Referencing System (LRS) workflows to support

Department transportation data business and maintenance which meets state and

federal reporting;

6. Develop business workflows and business rules to support Department current and

historical transportation data record tracking needs to meet public data records

requests;

7. Design and model spatial databases and develop document entity-relationship

diagram for the design of these databases that meet the transportation data

business needs;

8. Develop extract, transfer, load conversion scripts between legacy systems and the

Department IRAIS platform;

9. Provide solutions for data and GIS management of large vector and raster datasets

within the enterprise GIS warehouses environment;

10. Develop test plans for implementation activities;

11. Develop GIS web applications to interface with the enterprise GIS warehouses;

12. Develop metadata per Department standards and guidance;

13. The Contractor must comply with Open Geospatial Consortium (OGC) standards

and/or Federal Geographic Data Committee (FGDC) standards when required by

project specifications.

These standards are found at:

http://www.opengeospatial.org/standards

http://www.fgdc.gov/standards

C. Data Development and Implementation Services

The following activities outline the development and implementation services that would be

inclusive to migrating and converting data into the Department’s Roads and Highways

environment:

1. Provide assistance for short-term tasks where assistance is needed for IRAIS

development or implementation;

8 | P a g e

2. Perform the migration of data into the R&H environments;

3. Project and transform geospatial raster and vector data;

4. Perform creation, coding and editing of points, lines and polygons;

5. Support maintenance of Department linear referencing systems to enable

geolocating Department roadway and asset data;

6. Perform calibration of data to meet Department accuracy standards;

7. Perform data entry and updating of data attributes;

8. Perform quality assurance and quality control activities to validate geospatial data;

9. Perform topological and data validation edits as prescribed by the Department;

10. Develop business data workflows and configure solutions to maintain Department

data standards;

11. Develop and recommend topological and data validation functions necessary to

meet Department standards and expectations;

12. Test and validate data quality between the Department legacy system and R&H

environment;

13. Document and mitigate data quality issues and differences between data in the

legacy system and the R&H environment;

D. Data Integration Services

The following activities outline data integration services for R&H to meet functionality of the

legacy system and identify solutions and opportunities for FDOT:

1. Conduct integration evaluations and solutions of RCI and the RCI related systems;

2. Implement and configure R&H and identify feasibility measures to meet legacy

system functions;

3. Identify business functions of the legacy system that may be retired or retained and

provide recommendations to FDOT;

4. Perform acceptance testing activities in the R&H that are related to legacy system

workflows and functions;

5. Perform backwards compatibility conversion of data for extraction, transfer, or load

into legacy system environments;

9 | P a g e

6. Perform data integration activities to support the FDOT’s HPMS data submission

process;

7. Provide full documentation to the Department inclusive of source codes in standard

formats appropriate for Department platforms utilized in the project;

8. Provide documentation of implementation and functional issues;

9. Research and analyze related IRAIS issues the Department needs to further develop

based on the continuously changing technology environment and R&H

implementation.

E. Training Support Services

The following activities outline the training support services that may be required to perform

knowledge transfer of the implementation activities of Roads and Highways to Department

staff. Statewide travel may be required to provide training to Central Office and District

personnel. The following support services include:

1. Develop training plans that support the knowledge transfer of implementation of

Roads and Highways to FDOT;

2. Create training materials to support knowledge transfer workshops;

3. Develop in-person and hands-on training workshops for users;

4. Create workflow documentation for handoff and knowledge transfer to Department

personnel. Support the Organizational Change Management Office incorporate

process and workflow changes;

5. Travel expenses incurred by the Contractor will be in accordance with Section

112.061 of Florida Statutes.

F. Report Development Support

The following activities outline the report development support activities for the Department’s

state and federal reporting requirements:

1. Review current legacy system reporting workflows and develop Report Generation

Recommendation Plan for the R&H and IRAIS environment;

2. Coordinate data and business needs with Department reporting platform projects;

10 | P a g e

3. Generate reports for Department business needs and users;

4. Provide full documentation of report development to the Department inclusive of

source codes in standard formats appropriate for Department platforms utilized in

the project.

3. Contractor Project Staffing

The Contractor shall be experienced in working with state transportation department’s

roadway and asset data management systems. This experience must include implementation

of R&H to support the roadway and asset data management functions and requirements of

Departments of Transportation. The Contractor must have recent and relevant experience

implementing the R&H to support the HPMS data submission process as well as the planning,

operations, and financial data needs of a Transportation agency.

The Contractor will maintain staffing levels sufficient to complete the services and meet the

requirements specified in this Scope of Services and the resulting contract. All work must be

performed in the United States of America by individuals authorized to work in the United

States of America. Experience must be verifiable in resume and via references.

A. Staffing Classifications

The awarded IRAIS Contractor shall meet minimum qualifications and have the required listed

experience. Contractors may propose personnel to work on-site with FDOT to perform

activities if agreed upon in Task Work Orders.

The Contractor will provide personnel classifications that consist of the following:

Project Manager

Responsible for administering and promoting the IRAIS project which includes managing task

work orders, coordinating stakeholders, validating implementation activities, performing

quality control of deliverables, and project development. The individual will be a liaison

between the Contractor and subconsultants and the FDOT project management team.

The project manager will be responsible for overall coordination, project status reporting,

scheduling and maintaining stability of project-oriented work efforts. The project manager may

11 | P a g e

work on-site with FDOT if agreed upon. Establishes and implements project management

processes and methodologies to ensure projects are delivered on time, within budget, adhere

to high quality standards and meet customer expectations. Responsible for assembling project

plans and teamwork assignments, directing and monitoring work efforts on a daily basis,

identifying resource needs, performing quality review; and escalating functional, quality,

timeline issues appropriately. Responsible for tracking key project milestones and adjusting

project plans and/or resources to meet the needs of customers. Coordinates communication

with all areas of the enterprise that are impacted by the scope, budget, risk and resources of

the work effort being managed. Must possess extensive knowledge and expertise in the use of

project management methodologies and tools, resource management practices and change

management techniques to meet the Department’s project management business needs. The

project manager should be familiar with roadway and asset data management business

practices of Departments of Transportation. Additional experience should include integrating

business functions and configuring the R&H and providing solutions or recommendations where

R&H is unable to meeting the business functions of the Department. The Contractor must

provide a project manager with a current and active Project Management Professional®

certification.

Technical Product Support Analyst

Responsible for providing technical product support of Department’s business needs and

provide data support of the R&H software. This staff would be a technical lead for R&H and

have knowledge of transportation roadway and asset data management systems. This staff will

analyze and support the development and validation of customer technical requirements,

performing implementation activities, integration activities, performing quality control and

quality assurance of data, identify and coordinate business workflows and workflow changes,

provide vendor recommendations for project solutions and documenting the work performed.

This staff must have five years of experience implementing R&H with transportation agencies.

Technical Product Support Specialist

Responsible for technical product support of the R&H. This includes coordinating transportation

data extract, transfer, loads into geodatabases, developing spatial data, configuring R&H

12 | P a g e

functions, and performing day-to-day implementation needs of the project. This staff must

have knowledge and experience utilizing ESRI ArcGIS products, analyzing enterprise data and

imagery, performing data entry, and creating geospatial datasets that include transportation

networks and event data. This staff must have two years of experience implementing R&H with

transportation agencies.

Enterprise Application Integration Engineer

Responsible for developing and deploying integrated solutions aimed at modernizing,

consolidating and coordinating the independently designed applications within and across the

enterprises. Determines how existing applications, legacy systems, databases, GIS platforms,

Web interfaces and/or hardware logic, which may be currently operating on multiple platforms,

work together to meet the new and emerging enterprise requirements that is inclusive of

incorporating R&H. Develops methods to efficiently reuse existing components. Works with

users to gather business data requirements, performs database analysis, codes and tests

middleware routines to ensure successful and seamless communication among the various IT

systems and applications components. Participates in data architecture design, geospatial data

development and management, implementation of R&H workflows, integration activities,

software product evaluation and buy vs. build recommendations. Possesses skills and

knowledge of Enterprise Application Integration (EAI) methodologies and processes such as

object-oriented programming, distributed, cross-platform program communication using

message brokers with Common Object Request Broker Architecture, enterprise-wide content

and data distribution using common databases and data standards implemented with the

Extensible Markup Language (XML), middleware applications and message queuing approaches.

Data Architect

Responsible for developing the Department transportation data model, balancing optimization

of data access with batch loading and resource utilization factors. Knowledgeable in most

aspects of designing and constructing transportation data table architectures, operational data

stores, and data marts that are compatible with the R&H data models. Focuses on the

enterprise transportation data modeling and database design. Defines data architecture

standards, policies and procedures for the organization, structure, attributes and nomenclature

13 | P a g e

of data elements, and applies accepted data content standards to technology projects.

Responsible for business analysis, data acquisition and access analysis and design, database

management systems optimization, recovery strategy and load strategy design and

implementation. This staff is considered a junior position and must have two years of

experience implementing R&H with transportation agencies.

Data Modeler

Accountable for analyzing and developing complex logical database designs, logical data

models, providing mapping data schemas and creating relational data definitions in support of

FDOT business data requirements. Understands the methodologies and technologies that

depict the flow of data within and between technology systems and business

functions/operations. Responsible for the identification and resolution of information flow,

content issues and the transformation of business requirements into logical data models. This

position will identify opportunities to reduce data redundancy of the RCI system and related

systems, analyze trends in data uses and identify single sources of data. This staff must have

two years of experience implementing R&H with transportation agencies.

Technical Trainer

Responsible for the creation, and delivery of training and development programs. Involved in

gathering training needs and developing a training plan for FDOT to incorporate the

contractor’s work performed on transportation data business data. This staff will work closely

with both IT and the business to understand system and training needs for any supported

applications or packages supported or developed. Develops documentation for configuration

of applications, using a variety of mediums as needed. Designs training programs, classes,

workshops, and Computer Based Training (CBT) and on-line help as defined in the Task Work

Order. It is anticipated training will be delivered to a variety of audiences, understanding and

applying adult learning principles. This staff must have two years of experience implementing

R&H with transportation agencies.

B. Staffing Experience

The Contractor team must have experience in the following activities:

14 | P a g e

• Transportation data management for engineering, financial and planning practices;

• Enterprise resource planning;

• Data workflow productivity enhancement;

• Roadway data management;

• Transportation data modeling;

• Asset maintenance location tracking;

• Financial data management of transportation assets;

• Transportation data reporting through the Highway Performance Monitoring System;

• Data migration and conversion;

• Geographic Information Systems geodatabase management and processing;

• Geospatial data development;

• Linear referencing systems development and maintenance

• ESRI Roads and Highways Implementation;

• Obtaining data from computer-aided design and drafting;

• Data systems architecture;

• Master data management;

• Business intelligence and data analytics;

• Business data warehousing;

• Enterprise content management of transportation data;

• Visualizing, analyzing, and distributing transportation data through straight line diagrams,

video/photo Log;

• Azure Cloud technical expertise relevant to industry standards and best practices in cloud

computing;

C. Staffing Changes

The Contractor will not remove any key staff from their assigned roles on the Contract without

two (2) weeks prior notification and approval from the Project Manager and designated FDOT

team members, as appropriate or necessary. Before assigning any new individual to any

position on the project, the Contractor will provide the Project Manager with a resume and any

other information about the individual requested by FDOT within 48 hours of providing the

15 | P a g e

notification of a staffing change. Replacement personnel must be able to perform the core

functional responsibilities as identified in the Scope of Services. The replacement personnel

must have equal or superior experience and qualifications as the personnel being replaced. The

Contractor is responsible for conducting knowledge transfer and training any replacement

personnel.

All proposed personnel must be presented by role and estimated allocation in the Task Work

Order. FDOT reserves the right to reject proposed replacement personnel resumes based on

FDOT’s examination and determination of qualifications. All Contractor staff who work on the

project must successfully complete the FDOT Security Awareness computer based training prior

to starting work on the project.

If FDOT determines that the IRAIS consultant’s personnel/staff are unable to assist satisfactorily

in their area of expertise or to communicate effectively, FDOT will request the immediate

removal of that person(s) from the contract. Substitution of approved personnel may be made,

but requires approval of the FDOT project manager before beginning work if references or past

work performance is questionable or unfavorable. FDOT permits the IRAIS consultant to

subcontract services if needed to address staffing needs in the more technical areas and to

assist with staff deficiencies because of turnover. FDOT reserves the right to remove

Contractor personnel from the project at any time if deemed unacceptable by FDOT without

prior notification to the Contractor. There will be no increase in cost or change in deliverable

due dates because of replacement personnel.

D. Subcontractors

The use of subcontractors for work under this contract is allowable. The prime consultant will

be responsible for handling all contractual obligations with their subconsultants. All

subconsultants must be identified along with the submitted proposal to the Department.

E. Mandatory Reporting Requirements

The IRAIS contractor must demonstrate the capacity to provide services detailed in the scope

and implement the contract’s requirements, as directed by FDOT. The IRAIS contractor must

16 | P a g e

submit a flowchart of program processes, a project plan, an annual calendar of all proposed and

agreed upon activities and provide the FDOT project manager with any changes.

1. Monthly Reports

Submit an electronic copy via SharePoint (preferred method), e-mail, or FTP, in the

manner prescribed by FDOT, of the monthly activity/performance progress reports and

invoices to FDOT by the 15th of each month. Mail original hard copies of receipts and

other hard to read backup documentation. The IRAIS contractor will meet monthly with

the FDOT project management team as directed via teleconference or in person and

also quarterly with FDOT and the other FDOT consultants as directed by the FDOT. The

monthly meeting will include discussion on the project activities associated with the

program’s requirements, coordinate on schedules and timelines and outline

performance measures included in the scope of services. Meetings will be an

opportunity for the contractor and FDOT to report on any project concerns,

suggestions, or coordinate and plan on areas for improvement.

F. FDOT Contract Management

The FDOT Contract Manager may be responsible for the performance of the following

functions, some of which may be delegated to other FDOT staff:

1. Resolve any contractual problems.

2. Manage budget and contract performance.

3. Process, submit and track invoice payments.

4. Coordinate, develop and maintain task work orders associated with the

contract.

The designated Contract Managing Authority for this engagement will be addressed to:

Florida Department of Transportation Strategic Development Financial & Administrative Services Team 605 Suwannee Street. MS 27 Tallahassee, FL 32399

17 | P a g e

4. Services/Materials Provided by the Department

The Department will assign a Project Manager responsible for coordination with the Contractor.

The Department Project Manager will assist the Contractor with coordination of activities with

other stakeholders and work performed on behalf of the Department under this scope of

services. The Department will provide access to Department facilities and resources in

accordance with Department policies and procedures. All derived information, data and

reports is the property of the Department. Upon the conclusion of the contract, all data and

related materials revert to the Department.

Date Added Application Report Report Descriptoin Reporting‐Software Reporting‐Features Business‐Information Frequency Descriptive‐UM App‐or‐Report‐Gap‐Desc Standard‐Name Standards‐Category Primary‐SME Secondary‐SME Additional‐SME EDS Owner‐Office Functional‐Areas

Ad Hoc State Highway Systems Additions/Deletions

Consists of State Highway System edits governed by Florida Statute 335.08 ‐ Numbering Public Roads and the Transportation System Jurisdiction and Numbering Procedure, Topic No. 525‐020‐010.

Access and SharePoint PDF

Consists of State Highway System edits governed by Florida Statute 335.08 ‐ Numbering Public Roads and the Transportation System Jurisdiction and Numbering Procedure, Topic No. 525‐020‐010.

Annually Begin/End Mile Points

This is a manual process to input the various additions/deletions to then have a report generated.

N/A N/A Jerry Scott Lauren LeJeune Walter Liddell Paul O'Rourke CO CIM‐TDA

Ad Hoc Lane Mile Projections ‐ SHS and Turnpike projections for additional lane miles Excel formulas, graphs projections for additional lane miles Annual Lane Miles manual N/A N/A Tina Hatcher Eric Brickner Paul O'Rourke CO CIM‐TDA

Ad Hoc Logo AADT Report ‐ Interstate Interstate AADT FOCUS spreadsheet Interstate AADT Annual Centerline Miles Need to add to DART N/A N/A Tina Hatcher Paul O'Rourke CO CIM‐TDA

Ad Hoc Logo AADT Report ‐ Limited Access without Interstate Limited Access without Interstate AADT FOCUS spreadsheet Limited Access without Interstate AADT Annual Centerline Miles Need to add to DART N/A N/A Tina Hatcher Paul O'Rourke CO CIM‐TDA

10/31/2017 DART Error Message Report List of all data validations in DART Oracle spreadsheet RCI Data On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE01‐Sample Sections HPMS Sample validations Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE02‐Universe Sections HPMS Road validations Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE04‐Sample Breaks (By F330) HPMS Sample break validations Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE05‐Incongruent Lengths HPMS data with mismatch begin or end points Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE06‐Curves/Grades by Class Lengths Identify Curves or Grades incorrect lengths Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPE10‐HPMS Sample Number HPMS Sample Number validation Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART HPR04‐HPMS Sample Listing HPMS Sample List Oracle PDF, spreadsheet RCI/HPMS On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

10/31/2017 DART M01‐Preliminary RCI/HPMS Edit RCI Main Edit to validate administrative data Oracle PDF, spreadsheet RCI Data On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

3/2/2018 DART M02‐Gaps and Overlaps RCI Missing or Overlapping data Oracle PDF, spreadsheet RCI Data On Demand N/A N/A N/A Tina Hatcher Eric Brickner Bob Hendershot, Joel Worrell Paul O'Rourke CO CIM‐TDA

3/2/2018 DART PAV01‐Off System SIS Roads Off System SIS Roads Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

3/2/2018 DART PAV02‐SHS HPMS Samples SHS HPMS Sample Roads Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

3/2/2018 DART PAV03‐SHS Non‐HPMS Samples SHS Non‐HPMS Sample Roads Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

3/2/2018 DART PAV04‐Off System HPMS Samples Off System HPMS Samples Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR01‐RCI/HPMS Segment and Field Review List QAR RCI/HPMS Segments Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR02‐QAFIELD QAR Field Data  Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR03‐QAOFFICE QAR Office Data  Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR04‐QAHPMS QAR HPMS Data  Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR05‐QAPOINTS QAR HPMS Intersections Oracle PDF, spreadsheet RCI Data On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART QAR06‐QA Bike/Ped QAR Bike/Ped Data Oracle PDF, spreadsheet RCI Data On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE01‐Characteristics RCI validations Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE02‐RDWYSIDE RCI side validations Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE03‐TYPEROAD RCI Type road validations Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE04‐Invalid Offsets RCI invalid offsets Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE05‐Active Exclusive Roads RCI Active/Exclusive validations Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE06‐Bridge Edit Bridge Edit Oracle PDF, spreadsheet RCI Data On Demand centerline miles

Needs to also to against BRM for Bridge number accuracy/especially for new bridges.

N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCE07‐On‐System MAXSPEED On system Speed limit missing Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCR04‐Off System Roadway Listing Off System Road Listing Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

3/2/2018 DART RCR06‐State Highway System Listing On System Road Listing Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Jerry Scott Paul O'Rourke CO CIM‐TDA

3/2/2018 DART TE01‐Current AADT Required Traffic Edit ‐ missing Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Joey Gordon Paul O'Rourke CO CIM‐TDA

3/13/2018 DART TE03‐AADT Edit Traffic Edit ‐ AADT Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Joey Gordon Paul O'Rourke CO CIM‐TDA

3/13/2018 DART TE04‐Traffic Breaks Traffic Edit ‐ breaks Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Joey Gordon Paul O'Rourke CO CIM‐TDA

DART TE05‐Traffic Flow Breaks Traffic Edit ‐ flow breaks Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Joey Gordon Paul O'Rourke CO CIM‐TDA

DART TOE01‐Traffic Ops Traffic Signal edit Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

DART TOP01‐TOP 30 RCI RCI data Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Paul O'Rourke CO CIM‐TDA

DART TOP02‐TOP 30 Traffic RCI data with traffic Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Joey Gordon Paul O'Rourke CO CIM‐TDA

DART VR01‐Formatted Data for Download (Video Log) RCI data for Video log Oracle PDF, spreadsheet RCI Data On Demand centerline miles N/A N/A Tina Hatcher Bob Hendershot Andrea Hodge Paul O'Rourke CO CIM‐TDA

All Items Report Inventory

1

DART Truck VMT Report Truck VMT Report Oracle spreadsheet Truck VMT Report Annual Vehicle Miles Travel by Trucks Needs more automation N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

3/13/2018 DART RCR05‐Federal Aid Mileage ReportFederal Aid Mileage Report used during emergencies

Oracle PDF, spreadsheetFederal Aid Mileage Report used during emergencies

Annual, On Demand

Centerline Miles manually reformat N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

DQE DQE District Quality Evaluation ReportOracle, Access, and Excel 

PDF District Quality Evaluation Report Biannual N/A N/A N/A Andrea Hodge Ryan Rittenhouse Eric Hanson Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Coded Sample Values from FHWA v8 for QAR QAR HPMS Data  HPMS v8 PDF QAR HPMS Data  On Demand N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Consistency HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 ApplicationHPMS Extent and Travel Report (Urban‐Rural Summary)

HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Extent and Travel on the Interstate HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Extrent and Travel on the NHS HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS IRI on the Federal Aid Highway System HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS IRI on the NHS HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Length of Missing Pavement Data HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Overview HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Ownership HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Pavement Data Report Card HPMS Pavement Data Report Card HPMS v8 PDF, spreadsheet HPMS Pavement Data Report Card Annual Centerline Miles N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Sample Adaqacy HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Sample and TOPS Review Report HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Sample VMT Comparison HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Validation Summery HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FHWA HPMS v8 Application HPMS Vehicle Summary Changes HPMS Submittal HPMS v8 PDF, spreadsheet HPMS Submittal Annual N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

10/31/2017FL HPMS Reporting Application

FMIS5.0 HPMS List of Roadways with GIS RCI Arcs FMIS5.0 HPMS List of Roadways with GIS RCI Arcs Oracle spreadsheet FMIS5.0 HPMS List of Roadways with GIS RCI Arcs Annual Centerline Miles N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

HPMS Full View Export HPMS Data review Oracle access table HPMS Data review On Demand N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

HPMS List of Coded Values for QAR QAR HPMS Data  Access PDF QAR HPMS Data  On Demand N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

HPMS Pavement QAR Segment list QAR HPMS Data  Oracle spreadsheet QAR HPMS Data  On Demand N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

HPMS Pavement View Export Sample Details QAR HPMS Data  Oracle spreadsheet QAR HPMS Data  On Demand N/A N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

HPMS Submittal HPMS Submittal Oracle csv with pipes HPMS Submittal AnnualCenterline Miles and varies UM by characteristic

N/A N/A Eric Brickner Tina Hatcher Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Contact‐Report Contacts List of contacts SQL Server PDF, spreadsheet List of contacts On Demand N/A N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Contact‐Report Entities with no Contacts List of entities without contacts SQL Server PDF, spreadsheet List of entities without contacts On Demand N/A N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Data Submitted Confirmation Report Details to Entity Mileage Report ‐ current SQL Server PDF, spreadsheet Mileage Report ‐ current On Submit Mileage Report N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

End of Year Reports ‐ Draft and Final Mileage Draft/Final Mileage SQL Server PDF, spreadsheet Draft/Final Mileage On Demand Centerline Miles N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

End of Year Reports ‐ End of Year End of Year report SQL Server PDF, spreadsheet End of Year report On Demand Centerline Miles N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Entity‐Report Entity Historical Range Mileage change by entity SQL Server PDF, spreadsheet Mileage change by entity On Demand Centerline Miles N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Entity‐Report Percent Change Percent change by entity SQL Server PDF, spreadsheet Percent change by entity On DemandPercentage of Centerline Mileage Change

N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Entity‐Report Unreported Current Year Entities unreported for current cycle SQL Server PDF, spreadsheet Entities unreported for current cycle On Demand Quantity of entities  N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

Entity‐Report Variable Year Data to date SQL Server PDF, spreadsheet Data to date On Demand Quantity of entities  N/A N/A Tina Hatcher Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

Florida On‐Line Road Mileage

City/County Mileage Report City/County Mileage Report SQL Server PDF, spreadsheet City/County Mileage Report Annual Centerline Miles manually reformat N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

Certified Public Road Mileage Report Certified Public Road Mileage Report Oracle PDF, spreadsheet Certified Public Road Mileage Report Annual Centerline Miles manually reformat N/A N/A Eric Brickner Bob Hendershot Tina Hatcher Paul O'Rourke CO CIM‐TDA

FL HPMS Reporting Application

Public Road Mileage and Travel (DVMT) Report Public Road Mileage and Travel (DVMT) Report Oracle PDF, spreadsheet Public Road Mileage and Travel (DVMT) Report AnnualCenterline Miles and Daily Vehicle Miles Traveled

manually reformat N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

N/A QAR Quality Assurance Review Report Access and Excel PDF Quality Assurance Review Report 4X Annual N/A N/A N/A Andrea Hodge Ryan Rittenhouse Eric Hanson Paul O'Rourke CO CIM‐TDA

N/A Bike/Ped Report Bike/Ped Report Access PDF, spreadsheet Bike/Ped Report Annual Miles

Need to be expanded to include NHS and SIS data and automated on a better processing platform

N/A N/A Eric Brickner Eric Hanson Paul O'Rourke CO CIM‐TDA

N/A Interchange Mileage Report Interchange Mileage Report FOCUS PDF Interchange Mileage Report Annual Centerline Miles manual N/A N/A Tina Hatcher Eric Brickner Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Consistency Edits RCI input errors SQL PDF, spreadsheet RCI input errors On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Edits Performed RCI Edits Performed SQL PDF, spreadsheet RCI Edits Performed On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Feature ChangeList of Data changed from one point in time to the next

SQL PDF, spreadsheetList of Data changed from one point in time to the next

On DemandQuantity of records changed in RCI

N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

All Items Report Inventory

2

Roadway Characteristics Inventory

Feature/Characteristic Sort List of data for a roadway SQL PDF, spreadsheet List of data for a roadway On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Feature/Characteristic Summary Summary of data for a given area SQL PDF, spreadsheet Summary of data for a given area On DemandVaries by characteristic summed

N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Features Tied to an AnchorList of characteristics tied to an intersection for a roadway

SQL PDF, spreadsheetList of characteristics tied to an intersection for a roadway

On DemandQuantity of records tied on a roadway to an anchor

N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

FM Projects by Roadway ID All FM Projects by Roadway SQL PDF, spreadsheet All FM Projects by Roadway On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Propose New Roadway Section Boundaries List of data outside selected mile points  SQL PDF, spreadsheet List of data outside selected mile points  On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

RCI Breaks (Ad Hoc) Selected data related in a table output form SQL PDF, spreadsheet Selected data related in a table output form On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

RCI Breaks Historical (Ad Hoc)Historical elected data related in a table output form

SQL PDF, spreadsheetHistorical elected data related in a table output form

On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

RCI Data Export/Extract Data extracted from RCI in 224 byte flat file SQL PDF, spreadsheet Data extracted from RCI in 224 byte flat file On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

RCI Statistics RCI Statistics SQL PDF, spreadsheet RCI Statistics On Demand Varies by items on report N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Roadway ID SQL PDF, spreadsheet On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Route Detail SQL PDF, spreadsheet On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

Roadway Characteristics Inventory

Route ID SQL PDF, spreadsheet On Demand N/A N/A N/A Tina Hatcher Kirk Hutchison OIT Paul O'Rourke CO CIM‐TDA

RCIMENU HPMS Ad Hoc Report Generator SAS Flat File On Demand N/A N/A N/A Tina Hatcher Paul O'Rourke CO CIM‐TDA

RCIMENU RCI Ad Hoc Report Generator SAS Flat File On Demand N/A N/A N/A Tina Hatcher Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS Annual Mileage and Travel (DVMT) Report SHS Annual Mileage and Travel (DVMT) Report Oracle PDF SHS Annual Mileage and Travel (DVMT) Report AnnualCenterline Miles and Daily Vehicle Miles Traveled

manually reformat N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS Biannual Mileage and Travel (DVMT) Report SHS Biannual Mileage and Travel (DVMT) Report Oracle PDF SHS Biannual Mileage and Travel (DVMT) Report BiannualCenterline Miles and Daily Vehicle Miles Traveled

manually reformat N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Major Arterials

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Principal Arterials

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Rural Major Collectors

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Rural Minor Collectors

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Total Collectors

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Federal Classification‐Urban Total Collectors

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Interstate, Turnpike, Toll, Other

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Interstate, Turnpike, Toll, Other‐Rural Roads

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐Interstate, Turnpike, Toll, Other‐Urban Roads

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Comparison‐Reports Centerline‐State Summary SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Centerline‐State Summary‐Detailed

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Centerline Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Comparison‐Reports DVMT‐State Summary SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Daily Vehicle Miles Traveled N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports DVMT‐State Summary‐Detailed

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Daily Vehicle Miles Traveled N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Comparison‐Reports Lanemiles‐State Summary SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Lane Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Comparison‐Reports Lanemiles‐State Summary‐Detailed

SHS Comparison Report Oracle spreadsheet SHS Comparison Report On Demand Lane Miles N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Form 534 Reports‐NHS SHS Form 534 report Oracle spreadsheet SHS Form 534 report On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Form 534 Reports‐Not NHS SHS Form 534 report Oracle spreadsheet SHS Form 534 report On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Form 534 Reports‐State SHS Form 534 report Oracle spreadsheet SHS Form 534 report On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State Functional Class SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State Interstate SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State NHS Functional Class SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State NHS Interstate SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State NHS Summary SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State NHS Turnpike SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSHS‐Mileage‐Reports State SIS Connectors Functional Class

SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Connectors Interstate SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Connectors Summary SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

All Items Report Inventory

3

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Connectors Turnpike SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Functional Class SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Interstate SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Summary SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State SIS Turnpike SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State Summary SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage SHS‐Mileage‐Reports State Turnpike SHS Mileage Reports Oracle spreadsheet SHS Mileage Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Comparison Reports‐Federal System Changes

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On DemandCenterline Mileages, Lane Miles, and DVMT

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Comparison Reports‐Functional Classification Changes

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Comparison Reports‐Outdoor Advertising Changes

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage System Tracking Comparison Reports‐SIS Changes System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Comparison Reports‐Status Exception Changes

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage System Tracking Reports‐Federal Systems System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage System Tracking Reports‐Functional Class System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage System Tracking Reports‐Missing STATEXPT Values System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Reports‐NHS (with selection by [State, Managing or Geographic District], NHS Facility Type and Segment Status)

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage System Tracking Reports‐SIS System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Reports‐SIS (with selection by [State, Managing or Geographic District], SIS Facility Type and Segment Status)

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageSystem Tracking Reports‐STATEXPT gaps for Combo roads

System Tracking Comparison Reports Oracle spreadsheet System Tracking Comparison Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐County/SiteSpecific‐COSITE Cummulative

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐County/SiteSpecific‐COSITE Daily

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐County/SiteSpecific‐COSITE Hourly

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage TTMS Tracking Reports‐Statewide‐Annual Summaries TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐Statewide‐Comparisons‐Annual Comparisons

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐Statewide‐Comparisons‐Monthly Comparisons

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐Statewide‐Comparisons‐Quarterly Comparisons

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐Statewide‐DateRangeComparisons

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage TTMS Tracking Reports‐Statewide‐Monthly Summaries TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time Mileage TTMS Tracking Reports‐Statewide‐Monthly Trends TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Real‐Time MileageTTMS Tracking Reports‐Statewide‐Quarterly Summaries

TTMS Tracking Reports Oracle spreadsheet TTMS Tracking Reports On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Kendall Lindsay Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Construction Re‐Inventory Report Construction Re‐Inventory Report Oracle spreadsheet Construction Re‐Inventory Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Error‐Report Construction Error‐Report Construction Oracle spreadsheet Error‐Report Construction On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Error‐Report HPMS 3‐Year Error‐Report HPMS 3‐Year Oracle spreadsheet Error‐Report HPMS 3‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Error‐Report RCI 5‐Year Error‐Report RCI 5‐Year Oracle spreadsheet Error‐Report RCI 5‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Hit List Reports (by time) Hit List Reports (by time) Oracle spreadsheet Hit List Reports (by time) On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Inventory‐Report Construction Re‐Inventory Inventory‐Report Construction Re‐Inventory Oracle spreadsheet Inventory‐Report Construction Re‐Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Inventory‐Report HPMS 3‐Year Inventory Inventory‐Report HPMS 3‐Year Inventory Oracle spreadsheet Inventory‐Report HPMS 3‐Year Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Inventory‐Report RCI 5‐Year Inventory Inventory‐Report RCI 5‐Year Inventory Oracle spreadsheet Inventory‐Report RCI 5‐Year Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Inventory‐Report Statewide  Construction Re‐Inventory

Inventory‐Report Statewide  Construction Re‐Inventory

Oracle spreadsheetInventory‐Report Statewide  Construction Re‐Inventory

On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Inventory‐Report Statewide RCI 5‐Year Inventory Inventory‐Report Statewide RCI 5‐Year Inventory Oracle spreadsheet Inventory‐Report Statewide RCI 5‐Year Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Percent Complete‐Report HPMS 3‐Year Inventory Percent Complete‐Report HPMS 3‐Year Inventory Oracle spreadsheet Percent Complete‐Report HPMS 3‐Year Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Percent Complete‐Report Incomplete HPMS 3‐Year Roadway Inventory

Percent Complete‐Report Incomplete HPMS 3‐Year Roadway Inventory

Oracle spreadsheetPercent Complete‐Report Incomplete HPMS 3‐Year Roadway Inventory

On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Percent Complete‐Report Incomplete RCI 5‐Year Roadway Inventory

Percent Complete‐Report Incomplete RCI 5‐Year Roadway Inventory

Oracle spreadsheetPercent Complete‐Report Incomplete RCI 5‐Year Roadway Inventory

On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

All Items Report Inventory

4

Roadway Inventory Tracking Application

Percent Complete‐Report RCI 5‐Year Inventory Percent Complete‐Report RCI 5‐Year Inventory Oracle spreadsheet Percent Complete‐Report RCI 5‐Year Inventory On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Schedule HPMS 3‐Year Schedule HPMS 3‐Year Oracle spreadsheet Schedule HPMS 3‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Schedule RCI 5‐Year Schedule RCI 5‐Year Oracle spreadsheet Schedule RCI 5‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Statewide Construction Re‐Inventory Report Statewide Construction Re‐Inventory Report Oracle spreadsheet Statewide Construction Re‐Inventory Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Statewide RCI 5‐Year Schedule Report Statewide RCI 5‐Year Schedule Report Oracle spreadsheet Statewide RCI 5‐Year Schedule Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Timeliness Construction Re‐Inventory Report Timeliness Construction Re‐Inventory Report Oracle spreadsheet Timeliness Construction Re‐Inventory Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Timeliness HPMS 3‐Year Schedule Report Timeliness HPMS 3‐Year Schedule Report Oracle spreadsheet Timeliness HPMS 3‐Year Schedule Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Timeliness RCI 5‐Year Schedule Report Timeliness RCI 5‐Year Schedule Report Oracle spreadsheet Timeliness RCI 5‐Year Schedule Report On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Warning‐Report Construction Warning‐Report Construction Oracle spreadsheet Warning‐Report Construction On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Warning‐Report HPMS 3‐Year Warning‐Report HPMS 3‐Year Oracle spreadsheet Warning‐Report HPMS 3‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Roadway Inventory Tracking Application

Warning‐Report RCI 5‐Year Warning‐Report RCI 5‐Year Oracle spreadsheet Warning‐Report RCI 5‐Year On Demand N/A N/A N/A Tina Hatcher Bob Hendershot Eric Hanson Paul O'Rourke CO CIM‐TDA

Straight‐Line Diagrammer Straight‐Line Diagram  Straight‐Line Diagram  Oracle DXF, PDF Straight‐Line Diagram  On DemandCenterline Miles and varies UM by characteristic

N/A N/A Tina Hatcher Bob Hendershot Eric Brickner Paul O'Rourke CO CIM‐TDA

All Items Report Inventory

5

System Name Abbreviation System DescriptionInterface Direction (from the 

perspective of RCI)

 Enterprise GIS GISEnterprise GIS maintains the official FDOT basemap of all roads in RCI/LRS.

Outgoing

Bridge Management System (BMS) BMSBMS is a purchased application with department add‐ons. It is used to store bridge inspection information and schedule bridge inspections.  Outgoing

City to City Mileage FDOT's Official Highway Mileage Viewer provides official highway mileage between cities in Florida. Outgoing

Crash Analysis Reporting  CAR

The CAR system provides a framework against which the safety office collects, maintains, locates, analyzes, and reports crash accident data. The primary purpose is to identify highway safety improvement construction projects.     

Outgoing

Crash Locating System  CLS

Safety Office updates CLS with law enforcement data. Then CLS data is processed, based on crash location. CLS provides user functionality to enter geolocation data for off‐system crashes. All crash records originate at DHSMV. On‐System crashes are processed by the CAR system. CLS records are extracted and manually processed for location.

Outgoing

Data Analysis  and Reporting for Transportation

DART

The Data Analysis and Reporting Application (DART) is a web application that contains data validations and reports for data that comes from RCI. DART pulls information from the RCI and pushes that information in more efficient methods, dramatically reducing the effort and time to execute edits and receive the results as Adobe or Excel (among other options) directly. 

Incoming and Outgoing

District Quality Evaluation DQEThe DQE Web Application provides a visual overview of all District scores  based on specific goals and objectives outlined in the DQE Handbook.   Outgoing

Electronic Document Management System

EDMS

EDMS is FDOT’s enterprise document repository and enables the upload, storage, management, and access to digital versions of documents for the Department.  Note that EDMS does not currently interface with RCI. It is included here since there is an explicit requirement for the new system to utilize EDMS.

Incoming and Outgoing

Federal Authorization Management System

FAMS

FAMS transmits federal project information to the federal highway administration (FHWA) for subsequent authorization of federal funding for transportation projects.

Outgoing

RCI Integrated Applications

RCI Integrated Applications

1

Financial Management (WPA, FPM, PCM and FAMS)

FM

Financial Management is a “logical” application. Its subsystems include WPA, FPM, PCM and FAMS. This instance of an FM ‘application’ was created solely to document focus master ownership.

Outgoing

Financial Project Search  FPSA crosswalk for highway operations, construction, materials, maintenance, design, and right of way to search for project numbers and project information. Outgoing

Florida Traffic OnlineA web‐based mapping application that provides traffic count site locations, annual average daily traffic, and historical traffic count data. Outgoing

Highway Performance Management System 

HPMSHPMS shows the condition, performance, use, and operation conditions of the Florida Highway System. Incoming and Outgoing

iView

The IView is an ArcIMS intranet web application . IView is used to serve TDA's RCI/LRS data to Department users for analysis and planning purposes and to obtain estimated mileage information.  The Iview uses aerial photography to the Department’s users who do not have ready access to ArcGIS.  

Incoming and Outgoing

Maintenance Rating Program MRP

Maintenance office system used to record and report on the visual and mechanical evaluation of routine highway maintenance conditions.  The MRP utilizes RCI roadway data, features and characteristics to develop information to provide condition reporting.

Outgoing

ODA.Net

Outdoor Advertising Database, which contains an inventory of outdoor advertising structures, permits, accounts, and other related information maintained by the Department. In addition, standard reports are provided as well as a monthly data extract.

Outgoing

Pavement Condition Survey( Data Collection and Data Processing)

PCSPavement Condition Survey system is used to determine the present condition of State roads, predict future deterioration rates, and estimate funding needs. Outgoing

Pavement Management and Reporting PM

Maintenance office system used to record and report on visual and mechanical evaluation of routine highway maintenance conditions, like pavement failure, and resurfacing needs. 

Outgoing

Pavement Marking Management System PMM

Pavement Marking Management system is a new system that will be in production in the near future. PMMS records and reports on the retro‐reflectivity of the pavement markings on the State Highway System.

Outgoing

RCI Integrated Applications

2

Permit Information Tracking System PITS

Permit Tracking System records and tracks maintenance project permit requests submitted by the public to FDOT throughout the lifecycle of those requests: receipts by FDOT, review, approval (or denial), expiration, &/or extension, including correspondence dates. 

Outgoing

Project Cost Management  PCM

Used to monitor project cost transactions and facilitate corrective action as needed. Ensures the proper identification and recording of the direct costs of the Department to the proper transportation project and is essential for the accurate billing to the Federal Highway Administration of over $1.8 billion each year.

Outgoing

Project Suite Enterprise Edition PSEE

Provides project managers and administrators additional information about underway work program projects to ensure those projects stay on time and within budget.

Outgoing

Real Time Traffic

A web‐based mapping application that provides real‐time traffic count information ( NOTE: This data is only activated during emergencies such as hurricane, wildfire, etc.).

Outgoing

Real‐Time Mileage

The Real‐Time Mileage Reporting Application produces the official State Highway System (SHS) Mileage on the Fiscal and Calendar Year Ends and other comparison reports used for analysis by the Comptroller’s Office, SHS Coordinator, Functional Classification Coordinator, National Highway System (NHS) Coordinator, Strategic Intermodal System (SIS) Coordinator and the Highway Performance Monitoring System (HPMS) Coordinator.  

Outgoing

Right of Way Management System  RWM

Establishment, management, and reporting of Right of Way Projects, and their progress through appraisal, acquisition, litigation, relocation, business damages, transmittal submittals to financial services.

Outgoing

Roadway Inventory Tracking System RITA

Custom application used by District Offices to manage their highway data collection efforts.  RITA uses the RCI extract tables to track Roadway Inventory cycles for the Districts to manage timeliness information for RCI and SLDs.  The application also allows Districts to manage when RCI roadways are under construction.  Also used by Transtat to assist in performing District Quality Evaluations. Helps Transtat know when data is coming to time to report (5 yrs.). This serves as a form of quality assurance.

Incoming and Outgoing

Site Manager System  SM

Site manager is an AASHTO supported application used for managing projects during the construction phase and generating pay estimates for construction and maintenanceprojects. This is a part of the TRNS*PORT system.

Outgoing

RCI Integrated Applications

3

Skid Hazard Reporting SHR

System provides for data collection of skid tests taken by the state materials OFC on state maintained roadways. The results will be analyzed to determine if problem areas exist which should be addressed to lessen potential crash problems. Outgoing

Straight Line Diagrammer SLDSystem that creates straight line diagram documents. It is a custom application that was written by Center for Urban Transportation Research (CUTR) at USF. Outgoing

Traffic Characteristics Inventory TCI

Archives and reports traffic volumes, vehicle classifications, and related traffic data. Data is collected, stored, and distributed across the state highway system through traffic count stations and traffic breaks.

Incoming and Outgoing

Video Log VLG

Provides video documentation of the road segment for review. A vehicle with two cameras drives the length of roadway segments taking images every .005 miles (similar to Google cars).

Outgoing

Web Transport (Preconstruction) WTP

WTP is an AASHTO web application for managing different phases of a construction project including project item design, bid letting activities of advertisement, processing bids, evaluating bids, and project award. 

Outgoing

Work Program Application WPA

The Work Program Administration system is used to develop and monitor the department’s multi‐year work program. Projects are identified and programmed by phase cost and fund, against their programs and allocations.

Outgoing

RCI Integrated Applications

4