REQUEST FOR INFORMATION

(1)

STATE OF NEVADA

DEPARTMENT OF TRANSPORTATION

REQUEST FOR INFORMATION

Specifications and Instructions for Submitting Information for

Business Intelligence Implementation Project

Release Date:

February 4, 2013

Rudy Malfabon, P.E., Director Department of Transportation

(2)

1. General Information

1.1 Introduction

The Nevada Department of Transportation (NDOT) is seeking information from Business Intelligence implementers who are capable of and interested in providing implementation services for the NDOT Oracle Business Intelligence Enterprise Edition (OBIEE) solution. This Request for Information (RFI) is intended to educate NDOT, to obtain information about various Business Intelligence (BI) implementations, to identify various implementers and to obtain cost estimates for the phased implementation.

NDOT has implemented many systems over the years (over 50 applications/source systems currently). Each of these systems was designed for a specific function, but not necessarily with the global needs of the agency in mind. This proliferation of applications has left NDOT with data stored in multiple disparate databases and no obvious way to link them together. Cross system analysis that requires integration and analysis of data from multiple systems is a manual labor intensive process generally done by functional staff.

In addition, NDOT has multiple Linear Referencing Systems (LRS) and Linear Referencing Methods/Measures (LRM) used by different divisions. In addition, multiple Geographic Information Systems (GIS) systems from different vendors exist and each has a different repository: ESRI, Bentley and Intergraph. NDOT understands that much of its data has a geographical component and analysis of spatial data is necessary. GIS is beginning to have a larger role in the transportation planning process. GIS serves as the cornerstone of many operational and analytical functions at NDOT including the Highway Performance Monitoring System maintained by Roadway Systems (HPMS) and the Nevada Citation and Accident Tracking System maintained by Safety Engineering (NCATS). Major challenges exist with this type of data architecture. A Data Governance Team has been formed to address this challenge. The Data Governance Team is working to define processes and procedures to handle information so it can be utilized by all of NDOT, and not just users of that particular source system. NDOT understands that Data Governance is critical for staff to perform information-related processes. NDOT also understands it is critical to be able to analyze data across its tabular and GIS databases.

NDOT currently uses Oracle Discoverer as its primary data query and reporting tool. Discoverer works well with the siloed databases/sources systems but this tool is becoming outdated and has no capabilities for geographically displaying queried data. The Department has over 2000 reports written using Oracle Discoverer. It is anticipated the Discoverer tool used today throughout the Department will be replaced by OBIEE as part of this implementation. Excel is often utilized to combine data extracted from multiple systems.

In November 2011, a team of Oracle solution architects recommended a Business Strategy that included following initial source systems:

• Pavement Management System (PMS) • Maintenance Management System (MMS) • Integrated Financial System (IFS)

(4)

• Highway Performance Monitoring System (HPMS) • Safety Engineering Management System (SMS) • Project Scheduling and Management System (PSAMS)

• Project Submittal –Statewide Transportation Improvement Program (PTS/STIP) • Bridge Management System (BMS)

• Location Information System (LoIS) • Integrated Right of Way Network (IRWIN)

The Oracle team recommended a modern Business Intelligence solution to supplement to the capabilities of the existing data marts and reporting environments. The Business Intelligence solution should provide for the following capabilities.

Web-Based, Self-Service Environment: The implementer will create an environment that allows user groups to access information they need to make informed decisions in a timely manner. Capabilities include simple reporting, interactive dashboards, cross system complex reporting, predictive analysis models and future mobile access to information.

Data Integration: The implementer will assist the department in the task of integrating data across key systems. Queries of operational data will need to be discussed and a determination made as to what queries are created. NDOT wants to show immediate return on their BI investment. Knowledge transfer in this area is critical to the success of the project.

Integrated Security: The implementer will teach staff about granular row and column level access within the data integration layer of the BI architecture so a common point of security is enforced and report development is not negatively impacted.

Data Quality Products: The implementer should be familiar with various data quality products and provide a data quality strategy based on the data sources identified in the phased implementation.

NDOT has licensed Oracle’s Business Intelligence Enterprise Edition (OBIEE) and Oracle Data Integrator (ODI) as the primary tools to be used in this Business Intelligence project. These tools will be used along with our existing ESRI GIS tools, Bentley CADD tools, Mandli Roadview tools, EMC AX5 document management tools, and other data sources such as spreadsheets, etc. NDOT expects the BI implementer to have experience in the OBIEE capabilities noted above.

In addition, NDOT would like to display documents from our document management system, display information from our Bentley ProjectWise CADD system, and display videos of our roads from our Roadview system, all coinciding with the data displayed on the map as a result of any query.

(5)

NDOT has developed a comprehensive Strategic Data Plan (see diagram below) that identifies requirements and challenges of the BI Implementation: Data Integration, Data Sources, Analysis and Information Delivery. In addition, NDOT envisions an Information Center as an integral part of the BI implementation. The Information Center, when complete, would be used by the staff to find data in a variety of ways such as:

1. By Division

2. By Application by Location 3. Projects and Programs 4. BI Platform

NDOT understands the Strategic Data Plan is closely related to the BI Implementation. Both the Strategic Data Plan and the BI Implementation are based on the NDOT vision and key business goals. The business objectives of this project are:

1. Provide a better transportation system for Nevada by integrating siloed data with business intelligence. This would produce actionable data for staff, partners, legislators and citizens.

2. Improve customer satisfaction and transparency by enhancing the Information Technology Division’s ability to support emerging transportation initiatives. Business

(6)

intelligence would allow the department to work with external entities such as a Metropolitan Planning Organization (MPO) in the transportation planning process. 3. Increase efficiency by providing access to integrated, relevant and complete information.

Employees using the siloed data could access the integrated data in one place allowing more time for additional analysis.

4. Utilizing predictive analysis models to make better informed decisions. 5. Reduce costs by improving end-user self service.

The specific project objectives are:

1. Integrate NDOT data so queries, analysis and reporting can be done across database/application boundaries.

2. Integrate GIS data into query, analysis and reporting functions.

3. Implement Oracle Business Intelligence Enterprise Edition Suite (OBIEE) across database/application boundaries including the following components:

o Business Intelligence Server o Interactive Dashboards o Self Service Analysis o Report Publishing

o Office Suite Productivity Plug-in o Alert Engine

o Scorecard and Strategy Management

4. Migrate high priority Discoverer reports to OBIEE and provide a migration path for remaining reports for NDOT staff to convert.

5. Configure and teach NDOT staff to launch internal applications using query results as parameters including CADD and GIS documents.

6. BI Platform should support information delivery to mobile platforms. This should include notifications, reports, interactive dashboards and self service analysis.

7. Development of the NDOT Information Center Prototype to be used as an effective business tool. This should include interactive proof of concept sessions used to orient project and implementer staff about the goals of the Information Center.

8. Reports should be able to be provided in multiple platforms such as (PDF, HTML, XML, CVS, RTF, XLS, etc.).

NDOT is analyzing Business Intelligence implementation options to determine how to deliver the best value to the state and to taxpayers, with minimum cost and risk. This Request for Information will provide NDOT with the data necessary to plan effectively for this implementation. This Request for Information (RFI) and any future vendor presentations do not imply any form of an agreement with candidate suppliers. Responses to the RFI will be used to build and fine tune any future Request for Proposal (RFP).

While this RFI will not result in an award, we believe it is in the vendor community’s best interest to assist in providing cost estimates (per phase and per milestone). At the same time, we understand that vendors will not eagerly pursue extremely detailed and time consuming requests. We have constructed this RFI, and the accompanying response section to make it as easy as possible for vendors to respond.

(7)

NDOT management has expressed the need for a project budget to help vendors define the scope of the project. It is anticipated that implementation could cost between $5-$6 million for all phases of the project with each phase not to exceed $2M. This is not the amount considered potentially available for the implementation services, as it includes state infrastructure costs, state technical resources and project management.

If this level of funding is unrealistic, vendors are encouraged to provide substantiating information to assist NDOT with ongoing budget discussions.

1.2 Submission of Questions

If you have questions about this RFI, please submit them to the NDOT Administrative Services Division in writing via electronic mail. All responses to questions will be posted on the NDOT’s RFP/RFQ/RFI website. No vendor names will be included in the questions and answers posted to the website. The deadline for submission of questions is 3:00 PM Pacific Standard Time (PST), February 19, 2013. Answers to questions submitted will be posted on or before 5:00

PM PST, February 26, 2013. Questions should be submitted to [email protected]

and should be titled as follows:

Business Intelligence Implementation Project Questions 1.3 Vendor Submissions

Vendor responses are due by 3:00 PM PST, March 4, 2013. Please include sixteen (16) copies of the RFI response and one (1) electronic copy submitted on a CD. If a vendor has multiple solutions, separate responses are to be submitted. Response should be submitted addressed exactly as follows:

Agreement Services Nevada Department of Transportation Attn: RFI Business Intelligence Implementation Project

1263 South Stewart Street, Room 101 Carson City, NV 89712

Responses containing confidential information shall have each page marked as confidential to include the front cover of the response.

1.4 RFI Schedule

Description Timeline

Release of RFI February 4, 2013

Submission of Questions February 19, 2013

Responses to Submitted Questions February 26, 2013

(8)

The NDOT reserves the right to revise the above timeline.

1.5 RFI Coordinator

Vendor communications concerning this RFI should be directed to the RFI Coordinator listed below.

RFI Coordinator Procurement Person

Address Nevada Department of Transportation

Administrative Services Division 1263 S. Stewart Street, # 101 Carson City, NV 89410

Phone (775) 888-7070

E-mail [email protected]

1.6 Response Format

The responses shall be submitted in the following format (see Section 3): Section 1 – Executive Summary

Section 2 – Implementation Approach Section 3 – Proposed Solution Section 4 – Concept of Operations Section 5 – Scope of Work Section 6 – Cost

Section 7 – Past Performance

1.7 Vendor Presentation

Vendors may be invited to give a presentation at a time and date to be determined after review of the responses.

1.8 Cost of Preparing Response

The NDOT is not responsible for any cost incurred by the vendor in the RFI response preparation or presentation.

(9)

1.9 General Terms and Conditions

The State of Nevada is not obligated to any course of action as the result of this RFI. Issuance of this RFI does not constitute a commitment by the NDOT to issue an RFP or to award any contract.

Information submitted in response to this RFI will become the property of NDOT. NDOT will not pay for any information herein requested, nor will it be liable for any other costs incurred by any respondent related to the preparation or delivery of the response to this RFI or any subsequent presentation.

NDOT reserves the right to modify the RFI at any time. By submitting a response, the vendor agrees that NDOT may copy the response information for purposes of facilitating review or to respond to requests for public records. The vendor consents to such copy by submitting a response and warrants that such copying will not violate the rights of any third party. The NDOT will have the right to use ideas or adaptations presented in the responses.

NDOT reserves the right to reject any and all responses to the RFI, in whole and in part, at any time. This RFI is designed to provide vendors with the information necessary for the preparation of informative response proposals and demonstrations of product. This RFI process is for NDOT’s benefit and is intended to provide future selection of goods and services. The RFI is not intended to be comprehensive and each vendor is responsible for determining all factors necessary for submission of comprehensive response and complete product capability demonstration. The RFI response and demonstration will not be subject to an RFP type evaluation but only to a review of suggested product performance, cost of processes offered, and abilities to perform services that may be of use to NDOT. Cost shall be estimated by the vendor. When the estimated cost is submitted, the vendor shall state that it is an estimated or approximate cost.

1.10 Request for Confidential Treatment

The State of Nevada will treat all information submitted by a vendor as public information unless the vendor properly requests that the information be treated as confidential at the time of submitting the response. Any requests for confidential treatment of information must be included in a cover letter with the vendor’s RFI response. The request must also include the name, address, and telephone number of the person authorized by the vendor to respond to any inquiries concerning the confidential status of the materials.

A single confidential page in the document will classify the whole document as being confidential. Each page shall be marked as containing confidential information. The confidential information must be clearly identifiable to the reader on the outside of the document, cover letter, and on each page of the document.

(10)

2. Background

2.1 Project Background

This section provides general information regarding NDOT and is provided to assist proposers in better understanding the current environment and system difficulties. The information will help proposers become more familiar with the NDOT’s organizational structure and current computing environment.

This project is a joint effort between the Administrative, Engineering, Operations, Planning Divisions, and District Offices. Project leadership comes from the Location Division and project management duties are being supplied by the Information Technology section Division.

The project will be implemented in a phased approach, with each successive phase designed to incorporate the data and functionality that provides the most benefit to NDOT as a whole. The initial phase of the project will complement the current initiative at NDOT to streamline transportation planning process by identifying transportation needs early in the process. By providing access to integrated data and analytical capabilities across key planning data, staff will be able to conduct project planning based on needs. The table below identifies the key sources of planning data anticipated for Phase 1:

Key Source System Proposed Phase

Pavement Management System (PMS) Phase 1

Bridge Management System Phase 1

Nevada Citation and Accident Tracking System (NCATS) Phase 1

Event Geo Locator (EGL) Phase 1

Road Network Phase 1

Route Master Phase 1

Milepost Index Phase 1

Guardrail Phase 1

Traffic Information System (TIS) Phase 1

It is anticipated that Phase 1 will focus on deploying the BI foundation and providing access to the first set of data sources through the Common Enterprise Information Model. Manageable scope and immediate benefits are crucial to the success of Phase 1. The Data Governance team will be engaged to assist users with all phases of the project. Phase 1 will also include a

(11)

proof of concept/pilot to determine if there is a need for a planning data warehouse in subsequent phases.

The initial goal for the BI Implementation project at NDOT is to be able to enhance/improve the transportation planning process based on statewide transportation needs using key data sources. The flow chart on the following page shows the milestone events in the Project Development Life Cycle (Core Data View). The diagram identifies the 4 key source systems (Pavement, Traffic, Bridge, and Safety) used in the beginning of the planning process to determine statewide transportation needs.

NDOT expects these core data sources to be utilized in the data integration function in Phase 1 and be part of the Common Enterprise Information Model.

(12)

Project Development Life Cycle – Core Data View

Initially, travel forecasts for each highway are used along with data from the Pavement Management System to predict future pavement and capacity deficiencies. These deficiencies are used in the planning process to select alternative improvements (projects) to satisfy performance objectives. The next step is to perform additional analysis using safety and bridge

(13)

information. The most economically attractive improvement is noted. These projects are then re-prioritized and the best projects for system-wide implementation are selected.

Each of the milestone events (1-9) of the Project Development Life Cycle are explained further in Exhibit 1 of this document. NDOT expects the first 2 milestones: Initial Project Generation and Second Project Screening will benefit from the use of a BI tool and this is the area NDOT wants to use as a Proof of Concept. NDOT expects the implementer to look at Phase 1 data and demonstrate how NDOT can perform the initial project generation process more efficiently.

1) Initial Project Generation

It is anticipated the BI tool will enable NDOT staff to examine travel forecasts for each highway along with our pavement management system to predict future pavement and capacity deficiencies. This information is combined with a graphical component to identify the specific locations on a map allowing decision makers to see where the statewide needs are.

2) Second Project Screening

The BI tool will also be utilized at this step for further analysis using data from our safety management system and bridge management system. This analysis allows for the most economical improvement to be selected. Proposed projects are then prioritized according to relative merit and the best set of projects is selected for system-wide implementation.

NDOT’s business problems are similar to other DOTs with silos of data across the organization. NDOT wants Phase 1 to focus on integrating transportation planning data so analysis and comprehensive reporting can be done based on Statewide transportation needs. By starting early in the planning process, NDOT can make better transportation planning decisions because key planning data is in one centralized location. In addition, adding the geographical component would allow decision makers to identify project overlaps or planning inconsistencies very early in the process.

In addition, Phase 1 will look at the existing financial data warehouse, as shown in the table below. A migration strategy will be prepared for the existing Phase 1 Discoverer reports to be generated using the BI tool.

Financial Data Warehouse (FDOTDW) Phase 1

Phase 2 will include the second set of source systems. NDOT expects these systems will also be added to the Common Enterprise Information Model. During this phase, a decision will be made about the enterprise data warehouse development. The table below identifies the key sources of planning data anticipated for Phase 2:

(14)

Equipment Management System (EMS) Phase 2

Maintenance Management System (MMS) Phase 2 Project Scheduling & Management System (PSAMS) Phase 2

Project Submittal (PS) Phase 2

Statewide Transportation Improvement Program (STIP)

Phase 2

Annual Work Program (AWP) Phase 2

Phase 3 will include the remaining systems plus additional data sources identified in earlier phases. The table below identifies the key sources of planning data anticipated for Phase 3:

Integrated Right of Way Information Network (IRWIN) Phase 3 Highway Performance Monitoring System (HPMS) Phase 3

Location Information System (LOIS) Phase 3

Historical GIS data Phase 3

Railroad Systems Phase 3

Road Weather Information System (RWIS) Phase 3 DMV Data (Fuel Tax and Car Registrations) Phase 3

It should be noted, NDOT has identified functional and system requirements for the BI Implementation in Section 2.5. As part of that effort, the Department has prepared a BI Implementation Strategy document as shown as Exhibit 3. This represents a suggested strategy for transitioning NDOT from its current “siloed” structure. This document is provided as a guideline only. NDOT is open to other strategies.

As noted previously, NDOT is currently using Oracle Discoverer as its primary reporting tool. This tool allows NDOT to report on a wide variety of data, but primarily focuses on tabular data. Discoverer does not support GIS information and has no method for displaying or using GIS type data. Discoverer allows users to generate reports in separate systems but when data needs to come from 2 or more sources (applications), the Discoverer tool cannot be utilized unless key table joins have been done. Very few of the silos of information have been joined.

(15)

NDOT’s computing environment is driven by the automated applications and products used by the various divisions within NDOT. In general, the NDOT uses Microsoft Windows based desktop and server products for in-house application, design and development.

1. Windows 7 and Windows XP Desktop Operating Systems 2. Web Servers running IIS Versions 6 and 7.5

3. .NET Development Framework 4. MS Office (Word, Excel, Access)

5. MS Exchange and Outlook used for email and document communication

The Information Technology Division within NDOT develops, supports and maintains various applications, databases and spreadsheets. NDOT is currently using the following development and operational software:

1. Oracle 10g and 11g databases with separate development, test and production environments

2. Microsoft SQL Server databases

3. Visual Source Safe code management software 4. MS Visual Studio 2010

2.2 Acronyms/Definitions

Acronym/Term Definition

Bentley Software solution for infrastructure, NDOT uses Bentley products for designing roads.

BMS Bridge Management System – used to record bridge inventory and condition data, Bridge Inspect application records this information now.

EGL Event Geo Locator – application used to locate crashes, uses NCATSDW as input and creates the Statewide Located Crashes database

ESRI Software company that builds solutions to help scientists and planners visualize and analyze data on maps.

GIS Geographic Information System – allows users to visualize, query and analyze data through spatial analysis.

HPMS The Highway Performance Monitoring System (HPMS) is a federally mandated inventory system and planning tool, designed to assess the nation’s highway system.

IFS Integrated Financial System – used to account for NDOT financial data as well as the rest of the state.

Intergraph Software provider of engineering and geospatial software that enables customers to visualize complex data.

IRWIN Integrated Right of Way Information Network – developed to assist NDOT with Right of Way data

LOIS Survey Monument Location Information System - developed to assist NDOT with distributing survey monument information

LRM Linear Referencing Method/Measure, NDOT has multiple LRM’s: State Cumulative Miles, County Cumulative Miles, Mile Post Calibrated and Engineering Station

(16)

Acronym/Term Definition

LRS Linear Referencing System – the association of attributes or events along linear features defined by one or more measures such as the measurement of a special point or section of road. At NDOT there are at least two linear referencing methods/measures: Route cumulative and County cumulative MAP-21 Moving ahead for Progress in the 21st Century – authorizes Federal-Aid

Highway programs while maintaining current spending levels

MMS Maintenance Management System used for tracking information related to maintenance crew time and tasks, also used for ad-hoc reporting. MPO Metropolitan Planning Organization - Federally mandated and federally

funded transportation policy-making organization in the United States that is made up of representatives from local governments and governmental transportation authorities. In Nevada, there are 4 MPO’s: Carson Area Metropolitan Planning Organization (CAMPO), Tahoe Area Metropolitan Planning Organization (TMPO), Regional Transportation Commission of Southern Nevada (RTCSNV) and Regional Transportation Commission of Washoe County (RTC).

NCATSDW Nevada Citation and Accident Tracking System Data Warehouse – stores data received from the Department of Public Safety

OBIEE Oracle’s Business Intelligence Enterprise Edition 11g – one of the primary tools to be used in the Business Intelligence project.

ODI Oracle’s Data Integrator – tool to be used in the Business Intelligence project.

PMS Pavement Management System - used to maintain data on the condition of the state network as well as prioritize state network needs. A data

warehouse has been set up by IT to assist with reporting and analysis of their roadway system.

ProjectWise Suite of engineering project collaboration software from Bentley Systems designed for the architecture, engineering, construction (AEC) industries. It helps project teams manage, share and distribute engineering project content and review in a single platform. NDOT uses this product in our Road Design process.

PSAMS Project Scheduling and Management System - NDOT application designed to be an integrated Scheduling and Work Flow management tool covering the Planning and Design Phases of a Project, with some support for the Construction phase.

SMS Safety Management System that supplies traffic crash data to governments, non-governmental entities and the public.

STIP Statewide Transportation Improvement Program that identifies all capital and non-capital transportation projects proposed for funding under Title 23 of the Federal-Aid Highway Act or the Federal Transit Act. This document is required to receive federal funding for transportation projects. NDOT collects this data in the Project Submittal (PS) and Annual Work Program (AWP) applications after most of the research and decisions have been made.

(17)

2.3 NDOT Organizational Chart

NDOT Director

Administration Operations Engineering Planning Deputy Director North Deputy Director South Flight Opts Financial Management Accounting District Engineer District 2 District Engineer District 3 District Engineer District 1 Information Technology Administrative Services Traffic Operations Maintenance Asset Management Materials Construction Equipment Design Structures Environmental Right of Way Project Management Safety Engineering Traffic Information Multimodal Research Federal Program Manager Performance Analysis Roadway Systems Crews Construction Maintenance Traffic Tonopah Maintenance Safety Administrative Services Crews.Maint District Support Communications Training Traffic Traffic State of Nevada Department of Transportation Information Technology Functional Organization Chart Date BI Implementation REV 01/08/2013 1

SCALE N/A SHEET 1 OF 1 Location

(18)

2.4 Current Process

NDOT is responsible for planning, construction, operation and maintenance of approximately 5,400 miles of highways and over 1000 bridges. Excel is the primary tool used to compile the data from each of the systems. There is limited GIS capability with the current process. This process is a collaborative effort between federal, state, local governments, Regional

Transportation Commissions (RTC) and Metropolitan Planning Organizations (MPO’s) is shown on the diagram below.

1) Data is collected from the MPO’s, engineering studies and rural/local agencies. Applications are accepted from federal and state agencies, county, city, local governments, local public agencies and Indian Tribal governments.

2) NDOT Divisions that are an integral part of the planning process begin compiling project data based on their divisional knowledge.

1

Project Development Life Cycle Organizational View

2

3

4

(19)

• Betterment and 3R (Resurfacing, Restoration and Rehabilitation) priority list is provided to the Districts based on data compiled by the Pavement Analysis team. Districts review and recommend projects, eventually a final version of the prioritized list and repair strategy is forwarded to NDOT management for approval.

• Traffic Operations provides type and volume data for projects being considered for future improvement. They also ensure each project meets the minimal traffic capacity and is included in the 5 year plan.

• The Structures division compiles data and recommends projects based on bridge condition ratings, seismic risk, scour critical risks and other critical maintenance needs.

• Safety Engineering compiles crash data to develop systematic projects based on specific crash types and to identify high crash locations. These are projects that are typically discussed for inclusion into the 3R projects.

• Hydraulics and Landscape Architecture provide input as necessary based on data collected earlier in the process. Additional information from various asset management systems is provided such as drainage features and elements inventory.

3) NDOT Divisions that are an integral part of the planning process begin the verification process by refining scope, identifying risks, project schedules and costs estimates. Statewide needs are identified and projects are bundled based on issues, location, etc.

• Betterment and 3R data is reviewed, estimated and prioritized by the 3R Review Team.

• Traffic Operations reviews projects being considered and develops proposals for each project.

• The Structures division reviews lists for Betterment and 3R projects and provides recommendations for bridge related work to be included.

• Safety Engineering reviews project list and prioritizes projects with potential safety needs and also identifies counter-measures.

• Hydraulics and Landscape Architecture provide input as necessary based on data collected earlier in the process.

4) The Project Development Committee (PDC) meets quarterly to make decisions and based on project prioritization, ranking and funding availability determines which 3R projects continue to the programming and scheduling phase.

5) The Planning and Funding Phase of project development is accomplished by the Program Development and Financial Development divisions. The Program

Development division ensures each project approved by the PDC is part of the Annual Work Program (AWP), Statewide Transportation Improvement Program (STIP/TIP) or the Long Range Element (LRE).

(20)

The Financial Management Division programs funding for individual projects, which must meet specific federal requirements if federally funded. These requirements can be considerable but there is some flexibility in shifting of funds from one category to another. Generally they must be federally eligible projects within each of the federal project categories.

6) The National Environmental Protection Act (NEPA) is another approval process. All reasonable and feasible alternatives are studied equally. This process requires close coordination between Roadway Design and Environmental Services. When NEPA approvals are re-evaluated, formal notification of the project occurs in the form of a public meeting.

7) The Preliminary Engineering involves the development of contract documents for the “preferred alternative” that includes alignments and geometric design. This Preliminary Design is typically completed up to 60% level prior to establishing right of way impacts. As noted previously, the data used by each of these divisions resides in “silos” and is very difficult to combine for additional analysis. The geographical component of this data is available but limited causing incomplete and potentially inaccurate analysis.

NDOT is in the process of implementing a new transportation planning process. This new methodology identifies the most deficient portions of the highway system to ensure public dollars are directed to the areas with the most need. It is anticipated that several NDOT divisions such as traffic, structures, safety engineering, hydraulics and architecture as well as the district offices will be part of this new planning process.

While NDOT has taken steps to improve the transportation planning process, the methodology to determine the projects most in need require analysis of data from multiple systems and is a currently a very manual, labor intensive process. It is expected that the NDOT BI

Implementation project will greatly enhance this process.

NDOT is also in the process of implementing Moving Ahead for Progress in the 21st Century legislation (MAP-21) which consolidates 87 funding programs under SAFETEA-LU to less than 30 programs. The activities for which dedicated funding has been removed have been consolidated into very broad programs, leaving the State of Nevada with the flexibility to fund various road project as they see fit.

MAP-21 focuses the highway program on key performances measures, such as reducing fatalities, improving bridges, fixing roads, reducing congestion, in order to ensure taxpayers are receiving the most for their money. NDOT sets its own targets for improving safety, road and bridge condition, congestion and freight movement.

(21)

2.5 Functional and System Requirements

Requirement

Number Area Requirement

Priority (Mandatory or Optional) Response 1 BI Functionality

The vendor shall implement built-in interactive mapping and location-analysis within the Oracle BI tool and teach NDOT

staff how this is done. Mandatory

2

BI

Functionality

Vendor shall provide a single and consistent metadata layer and work with NDOT staff to map the data for mutually agreed upon applications (up to 4) for

each phase. Mandatory

3

BI

Functionality

The vendor will document the steps to analyze and design the mappings between the source data and the

business intelligence tool (OBIEE). Mandatory

4

BI

Functionality

The vendor shall demonstrate and document how to link common datasets

across multiple systems. Mandatory

5

BI

Functionality

The vendor shall define mutually agreed upon metrics to monitor the initial and

ongoing performance of the BI function. Optional

6

BI

Functionality

The vendor shall work with NDOT staff to optimize data for analytics and reporting

purposes. Mandatory

7

BI

Functionality

The system shall be designed with search parameters to prevent an intensive search from bringing down the server

performance. Mandatory

8

Dashboard Functionality

Sample dashboards will be created for 5 functional areas per phase to include simple and complex reporting and

predictive analysis. Mandatory

9

Dashboard home pages must be created for 5 divisions and be able to be

customized by individual users. Optional

10

The business intelligence dashboards in each phase shall contain the following elements: Graphs, Charts, Predictive Analysis, Ad-hoc reporting, drill-down functionality, associate project documents

and diagrams and map integration. Mandatory

11

The vendor shall design an NDOT Information Center where all interactive dashboards can be accessed by NDOT

(22)

Requirement

Priority (Mandatory or Optional) Response 12 Dashboard Functionality

The vendor shall design an NDOT Information Center where interactive dashboards can be accessed on the

NDOT external website. Optional

13

The vendor shall provide the ability to drill down into reports to get more information (e.g., Project ID drills to project details

such as name, costs, scope, etc.). Mandatory

14

The solution shall provide the ability to view dashboards via a mobile handset.

Optional

15

The vendor shall work with state staff to develop predictive analysis reports for 5

functional areas. Mandatory

16 Data Quality

The vendor shall work with NDOT staff to

identify and analyze duplicate data sets. Mandatory

17

Discoverer Report Migration

Implementation shall include the conversion/migration of 10 Oracle Discoverer reports (2 very easy complexity, 2 easy complexity, 2 moderate complexity, 2 complex and 2 very complex) per phase as determined by NDOT project team and knowledge

transfer with NDOT staff Mandatory

18

Query Functionality

Solution needs to accept GIS data for querying and mapping from ESRI and

SDE (spatial database engine). Mandatory

19

Query Functionality

Solution must be able to launch 4 NDOT written applications per phase using data

returned from queries. Optional

20

Query Functionality

Solution must be able to launch NDOT’s Mandli RoadView system using location

data returned from queries. Mandatory

21

Query Functionality

Solution must be able to display documents from NDOT’s AX5 document imaging system and ProjectWise system

using data returned from queries. Mandatory

22

Data Purification

Vendor should be familiar with Data Quality Products and provide a strategy as to how data cleansing/purification can

be done in an efficient manner. Mandatory

23

BI

Functionality

Vendor shall demonstrate and document how to incorporate NDOT data security

into analytics and reporting. Mandatory

(23)

Requirement

Priority (Mandatory or Optional) Response 24 BI Functionality

BI shall support information delivery to mobile platforms. This includes notifications, alerts, reports, dashboards

and other self service analysis. Mandatory

3. Vendor Responses

Responses should consist of the following sections. Each section is described below.

3.1 Section 1 - Executive Summary

Vendors shall provide an executive summary written in non-technical language to summarize the overall capability and approaches for a phased Business Intelligence Implementation using OBIEE.

3.2 Section 2 - Implementation Approach

This section should describe the implementation strategy for the Business Intelligence Project. This section should include a rollout strategy and project plan for the OBIEE implementation. In addition, an organizational structure should be included with defined roles for all project participants. Required skill sets should be noted for each project participant especially for the data modeling group.

3.3 Section 3 - Proposed Solution

Vendors shall provide their proposed solution. The proposal should make high-level recommendations specific to the NDOT implementation.

The solution should be presented in the following order: 1. Project management

a. Project plan b. Training plan

c. Roles and responsibility matrix 2. High Level Requirements Task

a. Vendor should validate and prioritize BI implementation requirements b. Vendor should determine data summarization and frequency requirements c. Identify reporting needs

d. Develop a gap analysis 3. Strategy Task

a. BI Reporting strategy b. Data Quality strategy c. Data Mapping strategy

(24)

d. Support 4. Training Task

a. Training strategy b. Documentation strategy c. Help desk strategy 5. Estimate of resources required 6. Projected timeframe for implementation

7. Total cost (estimated range); approach to pricing

3.4 Section 4 – Concept of Operations

Describe how your implementation would satisfy NDOT’s Business Intelligence needs based on project background information, requirements, current processes and the suggested implementation strategy.

The following topics should be considered in the solution:

1. Integration – The solution should be able to join key source data for each phase and all data should be joined at the end of Phase III

2. Flexibility – The solution should be flexible enough to accommodate changes mandated by state statutes, Federal Highway Administration (FHWA) and other regulatory bodies

3. Scalability – The solution must be scalable to support growth in data volume. It should have the ability to accommodate additional data and users.

3.5 Section 5 – Scope of Work

Please describe your recommended approach to the following milestone tasks. Include the estimated timeframe to accomplish each task plus the roles and skill sets required of state personnel. Assume that the state will provide overall project management and independent quality assurance. Please specify any additional tasks you envision to be required. Assuming this will be a multi-year phased implementation, indicate what functionality would be included in each phase. If your implementation strategy does not require any of these tasks please indicate why not.

Project Planning

Objective: Develop a phased implementation strategy and including deliverables based upon the source systems and specific functionality as prioritized in system requirements as well as the implementation strategy (Exhibit 2).

Validate Functional and System Requirements

Objective: This task involves confirming and expanding functional requirements and developing a conceptual approach document to support the defined functionality.

(25)

Proof of Concept

Objective: Illustrate/demonstrate BI functionality using source systems from each phase and gain input and acceptance from the user community prior to detailed system design.

System Configuration

Objective: Configure and tune Oracle OBIEE software on NDOT servers. Other tasks of this milestone include, but are not limited to:

• Security setup for OBIEE administrators and developers; • Set up of the end user environment

• Determine the performance monitor to be used; Data Modeling

Objective: Develop the methodology to determine the quality of the data and usability when mapping source data to the BI tool. This effort includes but is not limited to:

• Creating conformed dimensions

• Identifying data quality tool and/or strategy so NDOT will understand what is involved in this task

Verification and Testing

Objective: Verify that the BI solution operates in accordance with stated objectives in both test and NDOT production environments.

Documentation &Training

Objective: Provide system and user documentation. Train end-users, trainers and technical staff on how to use the BI tool to extract data from different source systems.

System Acceptance

Objective: Ensure independent testing and verification of BI system functionality prior to going live with a release of the application.

Rollout

Objective: Ensure system availability to all system users in accordance with a predefined rollout schedule.

3.6 Section 6 – Cost

While this RFI will not result in an award, we believe it is in the vendor community’s best interest to assist in providing cost estimates. At the same time, we understand that vendors will not eagerly pursue extremely detailed and time consuming requests. We have constructed this RFI, and the response section to make it as easy as possible for vendors to respond.

Please provide a cost estimate for each of the following areas. Assuming a multi-year phased implementation, indicate the year in which the costs would be incurred. Also, please identify any additional on-going costs such as software licenses, system maintenance, etc.

(26)

1. Equipment and Software

Include all hardware, application software licenses, third party licenses, etc. for the development, testing and production environment. NDOT has already purchased the software and will be using existing servers. Additional software would include any Data Quality products or products to be used during the BI Implementation.

2. Project Costs

This would include vendor costs to accomplish the following milestones:

• Project Planning

• Validate High Level Functional Requirements • Validate Functional and System Requirements • Proof of Concept

• System Installation and Configuration • Data Modeling

• Verification and Testing • Documentation and Training • System Acceptance

• Rollout

Each of the milestones noted above represents major levels of effort in the scope of work. NDOT would like to see a cost estimate assigned to each of these major tasks with a total for each phase.

3. Opportunities to share risk or otherwise reduce cost

Use this section to describe any suggestions on how the state could reduce costs for this project.

(27)

3.7 Section 7 – Past Performance

Using the categories listed below provide a complete description of projects of similar scope. The descriptions should include current references in the user organizations and sufficient information for NDOT to understand the proposer’s capabilities and experience in designing, configuring and implementing a business intelligence solution.

Client Name:

Project Name:

Primary Contact Information:

Name:

Street Address: City: State: Zip:

Phone, including area code: Facsimile, including area code: Email address:

Alternate Contact Information:

Name:

Street Address: City: State: Zip:

Phone, including area code: Facsimile, including area code: Email address:

Description of client:

Brief description of the project/contract:

Project/contract start date:

Project/contract end date:

Length of project/contract:

Project/contract value:

Proposer's management personnel/key personnel on the project/contract:

Size and complexity of the project/contract:

Application Software (i.e., Java, Cobol, etc.):

Operating System Software (i.e., Unix):

Hardware Platform (i.e., IBM RISC 6000):

(28)

4 Additional Vendor Comments

As part of your response to this RFI, please feel free to include any additional comments or suggestions that your company believes would be helpful to the NDOT.

Vendors may submit comments and questions to the RFI Coordinator prior to responding to the RFI by the date indicated in the RFI schedule in Section 1.3. Responses to vendor questions will be considered addendums to the RFI. Modifications to the RFI that may result from Vendor comments will be sent to all Vendors (or posted to the procurement website). Where there appears to be a conflict between the RFI and any amendment or addenda issued, the last amendment or addendum issued will prevail.

(29)

5 Exhibits

Exhibit 1 – Project Development Life Cycle – Core Data View

(30)

Milestone Events Definition

1) Initial Project Generation: Travel forecast for each highway facility from our traffic information system are used along with our pavement management system to predict future pavement and capacity deficiencies. These deficiencies are used to select a set of alternative improvements to satisfy analyst-specified performance objectives. 2) Second Project Screening: This list of needs is generated using data from our safety

management system and bridge management system. Safety and Bridge projects can be combined with 3R projects. Those projects that still have a high need from the safety management system or bridge system that do not make it into the system-wide

implementation as 3R projects go onto the list as point projects. Structures that need to be rehabilitated or replaced based on the sufficiency rating and conditional data are scheduled.

3) Planning Reports: The projects are now further subjectively ranked based on Land use/Corridor Studies, County Master Plans, and the Planning and Environmental Linkages (PEL).

4) Additional Project Needs: All other costs are included into the projects. This cost is derived from the asset management systems. During this stage, initial information is placed onto a project initiation form, this includes the approximate cost, location and the need generated from the previous steps. This additional project list will enable the information to be seen and searched on a map. This list is now sent out to the MPO’s and Rural and Local Agencies. This will assist the agencies in making their project selections. The MPO’s and Rural and Local Agencies will also be able to do their own analysis with our tools.

5) Decision Making Resource Allocation: Projects are further scoped. Issues such as utilities, right of way and preliminary environmental issues/concerns are identified. 3R team makes its final recommendations. The project initiation forms are again updated with current information.

6) Political Decisions: NDOT, MPO’s and Rural and Local Agencies now review the list of projects and preliminary costs with benefit/cost included and make their initial selections. This is part of the county tour process. At this time other projects can make the list, such as a point project for flooding. In addition, projects can be added to address Risk Management and Performance Management. This becomes the draft of the Annual Work Program, Long and Short Range elements of the STIP TIP. When additional projects are selected, initial information is placed onto a project initiation form. 7) Budgets: Budgets are now reviewed for the projects and preliminary funding sources

are applied. Projects that did not make the funding cutoffs will stay on a non-funded list until the next project development cycle.

(31)

8) Project Funding: Final selection of the projects is made. The director approves the STIP/TIP. FHWA approves STIP/TIP.

9) NEPA: Information from the planning phases is carried forward into the Planning and Environmental Linkages process. Environmental impacts and mitigation measures are identified and documented. Preferred Alternative is identified and approved by FHWA. A project manager is assigned to the project. Programming papers are submitted

electronically. Electronic tracing and signatures are used. Project information is downloaded into the PSAMS application.

(32)

Exhibit 2 – Business Intelligence Implementation Project Charter

Project Charter

Business Intelligence Implementation Project

(33)

1. Executive Summary

The Business Intelligence Implementation project will move the Department of Transportation to a more structured data and strategic decision support system. This effort is part of a larger effort by NDOT called the Strategic Data Plan (SDP) to address long term system/data integration issues. The Strategic Data Plan is composed of 2 key objectives: Data Governance and Core Data Integration. A diagram of the components is shown below:

Strategic Data Plan

Goals 1. Optimize the integration of NDOT business systems. 2. Streamline data Storage and man hours by identifying duplicate data sets.

3. Develop necessary organizational changes and systems to support a GIS centered organization.

4. Provide a method to query NDOT data in both tabular and GIS enabled formats.

5. Establish appropriate data security and documentation control. 6. Become more transparent and responsive to internal, external interests.

Data Governance

To establish and maintain policies, standards, procedures and processes that support the timely delivery of reliable transportation-related

data in and across NDOT divisions, other governments, external partners and the public

at large

Core Data Integration

Empower staff with data to improve operations, control costs, increase transparency and improve performance of projects through NDOT

technology initiatives.

Oracle BI Implementation

1. To provide a better transportation system by integrating siloed data with business intelligence. 2. Improve customer satisfaction and transparency by enhancing IS’s ability to support emerging transportation

initiatives.

3. Increase efficiency by providing access to integrated, relevant and complete information.

Needs Repository

1. To provide a better transportation planning process to enable NDOT staff to plan the transportation infrastructure

based on needs.

2. Comprehensive system to store needs coming in from all of NDOT and the outside project agencies that provides for

early staff involvement/research and make recommendations based on statewide transportation needs.

GIS Core Integration Implementation

1. Streamline the maintenance of the GIS road network and associated linear referencing system. 2. Easily synchronize NDOT division data with changes

made to the road network 3. Esri Road and Highway Implementation

The mission of the Data Governance effort is to establish and maintain policies, standards, procedures and processes that support the effective and timely delivery of reliable transportation-related data in and across NDOT divisions, other government agencies, external partners and the public at large. The success of this effort will affect how the Core Data Integration effort is executed.

The Oracle Business Intelligence (BI) Implementation project is one part of the Core Data Integration effort. NDOT expects this project will address the proliferation of applications with data stored in multiple disparate databases. In the past, applications were designed for a specific function, but not necessarily with the global needs of the agency in mind. This project will require collaboration and multiple inputs across the department. It is anticipated the BI Implementation project will be a phased implementation. This approach will allow NDOT to manage scope and provide ability to move quickly and show business value. This approach

(35)

also reduces risk and provides an opportunity to fine tune the road map to meet changing business requirements and implement lessons learned.

The initial key source systems will be implemented over a phased period of time utilizing resources from several divisions. The organization of the project will reflect the need to not only extract data in usable ways but correlate the data across multiple applications/dimensions. NDOT’s key source systems are shown below:

• Pavement Management System (PMS) • Bridge Management System (BMS)

• Nevada Citation and Accident Tracking System (NCATS) • Event Geo Locator (EGL)

• Roadwork Network • Route Master

• Milepost Index (MPINDEX) • Guardrail

• Financial Data Warehouse (FDOTDW) • Equipment Management System (EMS) • Maintenance Management System (MMS) • Project Scheduling and Management (PSAMS) • Annual Work Program (AWP)

• Project Submittal (PS)

• Statewide Transportation Improvement Program (STIP) • Integrated Right of Way Information Network (IRWIN) • Highway Performance Monitoring System (HPMS) • Location Information System (LOIS)

• Historical GIS data (LRSDW) • Railroad Systems

• Road Weather Information System (RWIS) • DMV Data

The primary risks to the project relate to the size and scope of the endeavor. Based on research from other departments of transportation (DOTs), the biggest risk factor is attempting to do too much too fast. There are multiple applications and data marts and many opportunities to create dashboards and reports. NDOT is aware of this and the project will be managed such that reasonable goals are agreed upon and communicated effectively. It is also critical that quick wins are achieved early. NDOT understands if there is not a clear project focus, the efforts will be diluted and very little value accomplished.

(36)

2. Business Objectives

For the BI Implementation at NDOT to be achievable, it must address specific project objectives. These project objectives are shown below:

1. Integrate NDOT data so queries, analysis and reporting can be done across database/application boundaries.

2. Integrate GIS data into query, analysis and reporting functions.

3. Implement Oracle Business Intelligence Enterprise Edition Suite (OBIEE) across database/application boundaries including the following components:

a. Business Intelligence Server b. Interactive Dashboards c. Self Service Analysis d. Report Publishing

e. Office Suite Productivity Plug-in f. Alert Engine

g. Scorecard and Strategy Management

4. Migrate high priority Discoverer reports to OBIEE and provide a migration path for remaining reports for NDOT staff to convert.

5. Configure and teach NDOT staff to launch internal applications such as Roadviewer, using query results as parameters including CADD documents.

6. BI Platform should support information delivery to mobile platforms. This should include notifications, reports, interactive dashboards and self service analysis.

7. Development of the NDOT Information Center Prototype to be used as an effective business tool. This should include interactive proof of concept sessions used to orient project and implementer staff about the goals of the Information Center.

8. Reports should be able to be provided in multiple platforms (PDF, HTML, XML, CVS, RTF, XLS, etc.).

All of these project objectives together will help NDOT achieve the following business objectives:

1. Provide a better transportation system for Nevada 2. Improve customer satisfaction and transparency 3. Increase NDOT staff efficiency

(37)

3. Scope

The scope of this project can be defined by 5 major milestones:

1. Install the Business Intelligence Server (OBIEE) optimized and aggregated for each data source. The data sources for each phase are shown below.

Key Data Source Proposed Phase

Pavement Management System (PMS) Phase 1

Bridge Management System (BMS) Phase 1

Nevada Citation and Accident Tracking System (NCATS) Phase 1

Event Geo Locator (EGL) Phase 1

Road Network Phase 1

Route Master Phase 1

Milepost Index Phase 1

Guardrail Phase 1

Traffic Information System (TIS) Phase 1

Financial Data Warehouse (FDOTDW) Phase 1

Equipment Management System (EMS) Phase 2

Maintenance Management System (MMS) Phase 2

Project Scheduling and Management (PSAMS) Phase 2

Annual Work Program (AWP) Phase 2

Project Submittal (PS) Phase 2

Statewide Transportation Improvement Program (STIP) Phase 2 Integrated Right of Way Information Network (IRWIN) Phase 2

Highway Performance Monitoring System (HPMS) Phase 3

Location Information System (LOIS) Phase 3

Historical GIS Data (LRSDW) Phase 3

Railroad Systems Phase 3

Road Weather Information Systems (RWIS) Phase 3

(38)

2. Extract data from each data source using the Oracle Data Integrator Enterprise Edition’s Extract, Load and Transform (E-LT) architecture. NDOT staff should be an integral part of this effort to gain the necessary knowledge to maintain the data in the future.

3. Using the source systems identified above, create a proof of concept document that demonstrates the effectiveness of the business intelligence tool and identifies constraints to the process (technical, functional or staff).

4. Using the source systems identified above, demonstrate the predictive analysis ability with key staff including knowledge transfer to perform this analysis in the future.

5. Using the source systems identified above, demonstrate research reporting and dashboards for each source system and phase.

(39)

4. Project Deliverables

Key project deliverables are shown in the table below:

Deliverable Objective Dependencies

Technical/Functional Components

Planning and Administration

Ensures adequate planning and project

management are dedicated to the

project

Data Governance team needs to be formed with members

across NDOT to help start shaping how the

data will be organized, deployed

and maintained

Secure executive and business sponsorship

Lay the foundation for governance and program

management Creation of the initial project

plan

Initiate technical training

Validate Functional and

System Requirements

Collect, validate and define requirements

to illustrate the system is working as

NDOT expects

Project team needs to be formed and available to review and validate findings

Requirement definition document will need to be developed that captured the project teams feedback and

recommendations

Proof of Concept

Ensures the proposed solution provides the

desired functionality

High value BI Initiatives need to have manageable scope and benefit several groups

Deploy the Business Intelligence (BI) foundation

Phase 1 data sources are identified

Provide access to the first phase of data sources through

the Common Enterprise Information Model Initial project plan and refined

and completed for Phase 1 data sources Initial list of priority Discoverer

reports (for Phase 1 data sources) are developed

Lesson learned are documented to help improve

the success of subsequent phases

(40)

Deliverable Objective Dependencies Technical/Functional Components System Configuration Ensures NDOT technical staff understands system parameters, processes and how

configuration decisions are made

NDOT staff (technical and functional) are identified and capable

Knowledge transfer document prepared that identifies decisions made and decisions

to be made in subsequent phases

Data Modeling

Develop methodology to determine the quality of the data and

usability when mapping source data

to the BI tool

Project team needs to be formed and

available to participate in the data

modeling tasks

Conformed dimensions are created, data quality tools are

identified so NDOT understands the level of effort

involved in this task

Integration of ESRI GIS data

Develop the methodology to use ESRI GIS data in the

Oracle BI tool

Project team needs to be formed and

available to participate in the GIS data integration tasks

Provide access to the first phase of GIS data sources

through the Common Enterprise Information Model.

System Integration

Testing

Ensures Phase 1 data sources work together

Phase 1 data sources are identified

Integration testing schedule prepared that includes all

Phase 1 data sources Integrated test scripts are developed and reviewed with

staff

Initial list of priority Discoverer reports (for Phase 1 data

sources) are tested

Documentation and Training

Ensures end-users, subject matter experts and technical staff are proficient with the BI tool and the Phase 1

data sets

NDOT staff (technical and functional) are identified and capable

System set-up steps along with utilities (such as backup and

restore procedures) are documented, online and user

manuals, training materials

Acceptance Testing

Ensures end-users and technical staff believe the system is

working as desired

NDOT staff (technical and functional) perform the required

testing

Acceptance test plan developed, Acceptance test scripts executed and results

(41)

Deliverable Objective Dependencies Technical/Functional Components Rollout - Production System Implementation

Ensures Phase 1 data sources are "production ready"

Production servers have been identified

and usable

Cutover meetings held so technical and functional staff understand what is expected Cutover technical task list

created

Confirm help desk support approach Post Implementation Evaluation and Review (PIER) Ensure lessons learned from Phase 1

implementation are applied to subsequent phases Issues need to be documented so references can be made when PIER

document is developed

PIER document developed by both implementation vendor and NDOT in a collaborative

approach

REQUEST FOR INFORMATION

STATE OF NEVADA

DEPARTMENT OF TRANSPORTATION