1. Agenda  Introduction of Project – FPID 465348-1-82-01(New Project)  Agenda Review  Safety Briefing  Public Input  Introduction of FDOT Personnel  Instructions for exempt documents  Exempt document requirement (DL Required)  Process Requirements  Must be authorized to do business in Florida  Proposals Due Date  Questions to the Bid Q&A website  Project Scope

2. FDOT D5 Big Data Management Pilot Project Pre-Bid Mandatory Meeting FPID: 465348-1-82-01 October 13, 20153:00 PM

3. Agenda  Introduction of Project – FPID 465348-1-82-01(New Project)  Agenda Review  Safety Briefing  Public Input  Introduction of FDOT Personnel  Instructions for exempt documents  Sample data  Includes exempt documents  Exempt document requirement (DL Required)  Process Requirements  Must be authorized to do business in Florida  Proposals Due Date  Questions to the Bid Q&A website  Project Scope

4. Special Note Mandatory Pre-Proposal Conference  Per RFP Section 8) MANDATORY PRE-PROPOSAL CONFERENCE:  A MANDATORY pre-proposal conference will be held at the date, time, and location in the Timeline. The purpose of this meeting is to provide an open forum for the Department to review the Technical Requirements and respond to general questions from potential proposers regarding the Technical Requirements, RFP requirements, contractual requirements, and other conditions or requirements that may, in any manner, effect the work to be performed. Any changes and/or resulting addenda to the RFP will be the sole prerogative of the Department. All questions requiring a response must be posted to the Departments Bidders Q&A site as per Section 3 above.  Attendance at this pre-proposal conference is MANDATORY  Failure by a proposer to attend or be represented at this pre-proposal conference will constitute a nonresponsive determination of their proposal package. Proposals found to be non-responsive will not be considered.  LATE ARRIVALS TO MANDATORY PRE-PROPOSAL MEETINGS  All bidders must be present and signed in prior to the start of the mandatory pre-proposal meeting.  Anyone not signed in at the commencement of the meeting will be considered late and will not be allowed to bid on the project.

5. Project Scope  Project History  Purpose  Contract Terms  FDOT Responsibilities  Expectations of the Vendor  Project Deliverables  Use Cases and Tasks  Q & A’s  Sample Data

6. Project History  Integrated Corridor Management (ICM) Plan developed by MetroPlan Orlando  Relationship between FDOT and MetroPlan Orlando  Big Data Pilot resulting from ICM Project  FDOT seeks to find proper use for varies data sets

7. Purpose  Chief Aims  Seek to understand the potential benefits of Business Intelligence used for transportation related issues  Provide useful data to two groups:  Planning – To assist with building the right projects  Operations – To assist with making the most current investments

8. Contract Terms  2 year contract  1 year with a 1 year renewable (if necessary)  FDOT Fiscal Year (FY)  Begins July 1 and Ends June 30 th  This project is set for FY 15/16 and ends FY 17/18

9. FDOT Responsibilities  Provide Sample Data Sets  FDOT Owned data sets show in table A-1  Provided to give Vendors an understanding of the type of data owned  Mitigate Project Risks  Assist with Project Bidding  Length of Data (intend is to acquired as much as is needed)  Must sign release form to receive data sets  Data includes confidential and non confidential sensitive Data SetsData SourceData Type Length of Data in years Factors that play a role in Ped Fatalities Location of Pedestrian Fatalities Crash Data DB Structured5 Location of Street lighting near Ped Fatals Unknown 5 Locations of existing sidewalks near Ped Fatals Crash Data DBStructured5 Weather conditions during Ped Fatals Crash Data DBStructured5 Land Use near Ped Fatals DRIStructured5 Bus routes and amenities Unknown 5 New Development Starts DRIStructured5 Roadway Construction ActivityRCI, InfonetUnstructured5 Annual Average Daily TrafficFTICDStructured5 Travel TimesSunguideStructured5 Geometric Conditions (# of lanes, median width, etc.) Roadway DataStructured5 Vehicular crash data Crash Data DBStructured5 Incident Time of Day Crash Data DBStructured5

10. FDOT Responsibilities  Data Restrictions  Restriction for Use on this project  Not restricted to state or US  No live feeds or interfaces to FDOT data sources  “The Vendor shall not redistribute, reuse or resell the datasets provided by the Department to any third party without authorized written consent from the Department.”  Provide FDOT Liaison  Will be available to help guide Vendor to FDOT owned data sets

11. Expectations of the Vendor  Meet the RFP requirements  Read and Re-Read the RFP  Utilize expertise to determine BI needs  No Preliminary efforts conducted by FDOT  No solicitations by FDOT regarding hardware/software solutions  Hardware/software solutions at Vendor’s sole discretion  FDOT does not own any transferable hardware/software  FDOT does not employ BI experts  FDOT has no intention of procuring hardware or software  Vendor may use personnel in any state,  No remote access to FDOT resources will be granted

12. Expectations of the Vendor  Focus on RFP tasks  Seeking Descriptive Analytics for now  No Predictive Analytics at this time  Data Acquisition  Vendor responsible for acquiring and validating all data sets, even FDOT provided data sets  Determine any and all data sets needed to fulfill RFP requirements  Coordinate with agencies to acquire data sets (when necessary)  Vendor determine any other necessary data sets  Coordinates with third party (when necessary)

13. Expectations of the Vendor  Analyze Datasets  Help FDOT understand any data entry issues  Process & Clean  Clean real-time and historical data sets  ETL  Typically relational model developed  Non relational will be acceptable  Reports  FDOT seeks to understand the Vendor’s process & methods for deriving at the solutions for each Use Case

14. Expectations of the Vendor  Next Steps  You are our Big Data expert  We want your suggestion on how to move forwad following your work  Not vendor specific  Focused on our objective  If next steps are taken there will be a separate competitive procurement  Project Schedule  Develop CPM Schedule based on your method of fulfilling the RFP requirements  1 year contract w/ability for 1 year renewal

15. Expectations of the Vendor  Bidding & Award  Include all costs associated with the project  Hardware, Software, Time and Materials  All new accounts must be in Vendors name  No Cost shall be payed beyond the contract budget or expiration date  Project will be awarded to only one Vendor  No Vendor Participating in this pilot project will be precluded from work from any other contract  Vendors must bid on the entire project (all use cases)

16. Project Deliverables  Reports  FDOT requires Point-in-Time reports  Per Use Case  PDF Format  Data  Provide cleaned data  SQL Format  Do NOT provide hardware or software  Process  Discuss in report  Process taken to determine Use case solutions  Staff used and level of expertise  Man-Hours used to complete Project  Per Use Case  Total Project

17. Use Cases and Tasks  Use Case Priority  FDOT will disclose priority order to Awarded Vendor  Task requirements are expected to be fully met  All data, even historical must be cleaned  Targeted Road ways  Use Cases are targeted for all State and local roadways

18. Q & A’s  Post all questions to the Bid Q&A Website  FDOT official responses to all questions  Read the RFP prior to posting questions  Read the posted questions prior to posting a new question

19. Meeting Adjourned Thank you!

20. Data Disk  Data Disc will be at booth  Complete release form  Provide Driver’s License  The Vendor shall not redistribute, reuse or resell the datasets provided by the Department to any third party without authorized written consent from the Department.