SunStore Program (Part of ATTAIN Program)

Project Description: SunStore is FDOT District 5's local data warehouse where users can search, browse, interact with, and download FDOT D5 ITS data. The SunStore is central data storage for all the transportation system management and operations information. SunStore includes Master Data Management, Data Fusion, and Sensor Fusion for increased data quality. SunStore connects and integrates many data sources, so FDOT can make the information available to planning, operations, universities, research institution, and businesses to encourage innovation. SunStore Program is a part of the ATTAIN Central Florida Program under an Advanced Transportation and Congestion Management Technologies Deployment (ATCMTD) grant award. Data in SunStore will be used to support the other parts – PedSafe, GreenWay, and SmartCommunity deployments of the ATTAIN Central Florida program.

Project Status: Planned

Project Stakeholders:

• Archived Data Users
• FDOT Central Office of Information Services
• FDOT CO
• FDOT District 5
• MetroPlan Orlando
• Private Sector ISPs
• Private Weather Information Providers
• SunRail
• Travelers

Project Service Packages:

• DM02: Performance Monitoring (SunStore Program (Part of ATTAIN Program))
• SU04: Map Management (SunStore Program (Part of ATTAIN Program))
• DM01: ITS Data Warehouse (SunStore Program (Part of ATTAIN Program))

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
archive coordination	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	SunStore	Planned
archive coordination	FDOT District 5 RTMC	SunStore	Existing
archive coordination	FDOT Statewide OIS Enterprise Databases	SunStore	Existing
archive coordination	MetroPlan Transportation Data Collection System	SunStore	Existing
archive coordination	SunStore	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	Planned
archive coordination	SunStore	FDOT District 5 RTMC	Existing
archive coordination	SunStore	FDOT Statewide OIS Enterprise Databases	Existing
archive coordination	SunStore	MetroPlan Transportation Data Collection System	Existing
archive status	SunStore	Central Florida Mobility Application	Planned
archive status	SunStore	FDOT Asset Management Systems	Existing
archive status	SunStore	FDOT District 5 AAM Dashboard	Existing
archive status	SunStore	FDOT District 5 Bridge Condition Monitoring Management System	Existing
archive status	SunStore	FDOT District 5 Construction and Maintenance	Existing
archive status	SunStore	FDOT District 5 Maintenance and Inventory Management System (MMIS)	Existing
archive status	SunStore	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	Planned
archive status	SunStore	FDOT District 5 RTMC	Existing
archive status	SunStore	FDOT Statewide OIS Enterprise Databases	Existing
archive status	SunStore	Private Sector Traveler Information Services	Existing
archive status	SunStore	Private Travelers Personal Computing Devices	Existing
archive status	SunStore	SunRail Operations Control Center	Existing
archive status	SunStore	Weather Information Providers	Existing
archived data product requests	Archived Data User Systems	SunStore	Planned
archived data product requests	FDOT District 5 AAM Dashboard	SunStore	Existing
archived data product requests	FDOT District 5 RTMC	SunStore	Existing
archived data product requests	FDOT Signal4	SunStore	Planned
archived data products	SunStore	Archived Data User Systems	Existing
archived data products	SunStore	FDOT District 5 AAM Dashboard	Existing
archived data products	SunStore	FDOT District 5 RTMC	Existing
archived data products	SunStore	FDOT Signal4	Existing
archived data products	SunStore	SunRail Operations Control Center	Existing
asset archive data	FDOT Asset Management Systems	SunStore	Existing
asset archive data	FDOT District 5 Maintenance and Inventory Management System (MMIS)	SunStore	Existing
asset archive data	FDOT Statewide OIS Enterprise Databases	SunStore	Existing
emergency archive data	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	SunStore	Planned
maint and constr archive data	FDOT District 5 Bridge Condition Monitoring Management System	SunStore	Existing
maint and constr archive data	FDOT District 5 Construction and Maintenance	SunStore	Existing
maint and constr archive data	FDOT District 5 RTMC	SunStore	Existing
map update notification	SunStore	CAV-ITS Map Update System	Existing
map updates	CAV-ITS Map Update System	SunStore	Existing
multimodal archive data	Central Florida Mobility Application	SunStore	Planned
traffic archive data	Central Florida Mobility Application	SunStore	Planned
traffic archive data	FDOT District 5 AAM Dashboard	SunStore	Existing
traffic archive data	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	SunStore	Planned
traffic archive data	FDOT District 5 RTMC	SunStore	Existing
transit archive data	FDOT District 5 Regional Integrated Corridor Management System (R-ICMS)	SunStore	Planned
transit archive data	SunRail Operations Control Center	SunStore	Existing
transportation weather information	Weather Information Providers	SunStore	Existing
traveler archive data	Central Florida Mobility Application	SunStore	Planned
traveler archive data	Private Sector Traveler Information Services	SunStore	Planned
traveler archive data	Private Travelers Personal Computing Devices	SunStore	Planned
weather archive data	Weather Information Providers	SunStore	Existing

Project Functional Requirements (Element - Functional Object):

• CAV-ITS Map Update System - Map Management
• 5: The Center shall provide basemap updates to other Centers.
• 8: The Center shall coordinate the contents of map data for distribution with other Centers.


• Central Florida Mobility Application - TIC Operations Data Collection
• 4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.


• Central Florida Mobility Application - TMC Data Collection
• 3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.


• FDOT District 5 AAM Dashboard - TMC Data Collection
• 1: The center shall collect traffic management data such as operational data, event logs, etc.
• 3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.


• FDOT District 5 Bridge Condition Monitoring Management System - Archive Data Repository
• 6: The center shall include capabilities for archive to archive coordination.


• FDOT District 5 Bridge Condition Monitoring Management System - Archive Situation Data Archival
• 1: The center shall collect data from roadside devices.
• 6: The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive.


• FDOT District 5 Construction and Maintenance - MCM Data Collection
• 1: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.
• 3: The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself.


• FDOT District 5 Regional Integrated Corridor Management System (R-ICMS) - Archive Data Repository
• 9: The center shall respond to requests from the administrator interface function to manage center-sourced data collection.


• FDOT District 5 Regional Integrated Corridor Management System (R-ICMS) - TIC Operations Data Collection
• 5: The transportation information center shall produce sample products of the data available.


• FDOT District 5 Regional Integrated Corridor Management System (R-ICMS) - Transit Center Data Collection
• 1: The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc.


• FDOT District 5 RTMC - Archive Data Repository
• 1: The center shall collect data from centers.
• 3: The center shall store collected data in an information repository.
• 6: The center shall include capabilities for archive to archive coordination.
• 8: The center shall collect data from data distribution systems and other data sources.


• FDOT District 5 RTMC - MCM Data Collection
• 3: The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself.


• FDOT District 5 RTMC - TIC Operations Data Collection
• 1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.


• FDOT DIVAS - TIC Operations Data Collection
• 4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.


• FDOT Signal4 - Archive Data Repository
• 3: The center shall store collected data in an information repository.
• 7: The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.


• FDOT Signal4 - Archive Situation Data Archival
• 6: The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive.


• FDOT Statewide OIS Enterprise Databases - Archive Data Repository
• 10: The center shall respond to requests from the administrator interface function to manage the archive data.
• 3: The center shall store collected data in an information repository.
• 4: The center shall perform quality checks on collected data.


• LYNX Transportation Center - TIC Operations Data Collection
• 4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.


• LYNX Transportation Center - TMC Data Collection
• 3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.


• LYNX Transportation Center - Transit Center Data Collection
• 3: The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself.


• MetroPlan Transportation Data Collection System - Archive Data Repository
• 1: The center shall collect data from centers.
• 10: The center shall respond to requests from the administrator interface function to manage the archive data.
• 6: The center shall include capabilities for archive to archive coordination.


• Orlando Intermodal Center - Traveler Interactive Information
• 1: The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request.


• Orlando Intermodal Center - Traveler Trip Planning
• 1: The public interface for travelers shall receive traffic information from a center and present it to the traveler to support trip planning.
• 8: The traveler support equipment shall provide a mechanism for its user to create/modify a trip plan including selection of mode, route and parking.


• Port Canaveral - Terminal Data Collection
• 1: The intermodal terminal shall collect intermodal shipping data including shipping schedules, container statistics, chassis usage, traffic into and out of the facility.
• 3: The intermodal terminal shall receive and respond to requests from ITS Archives for either a catalog of the parking management data or for the data itself.
• 4: The intermodal terminal shall produce sample products of the data available.


• Private Sector Traveler Information Services - TIC Operations Data Collection
• 1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.


• Private Sector Traveler Information Services - TMC Data Collection
• 3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
• 4: The traffic management center shall produce sample products of the data available.


• Private Travelers Personal Computing Devices - Personal Interactive Traveler Information
• 1: The personal traveler interface shall receive traffic information from a center and present it to the traveler upon request.


• SunRail Operations Control Center - MCM Data Collection
• 3: The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself.


• SunRail Operations Control Center - TIC Operations Data Collection
• 4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.


• SunRail Operations Control Center - Transit Center Data Collection
• 3: The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself.


• SunStore - Archive Data Repository
• 1: The center shall collect data from centers.
• 10: The center shall respond to requests from the administrator interface function to manage the archive data.
• 11: The center shall respond to requests for archive data from archive data users (centers, field devices).
• 4: The center shall perform quality checks on collected data.
• 6: The center shall include capabilities for archive to archive coordination.
• 8: The center shall collect data from data distribution systems and other data sources.


• SunStore - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .

Standards:

• (None-Data) - Secure Internet (ITS)
• US: ADMS - Guaranteed Secure Internet (ITS)
• US: ADMS - Secure Internet (ITS)
• US: TMDD - NTCIP Messaging

Project Operational Concepts:

Roles and Responsibilities

• Private Sector ISPs
• Provide crowd sourced traffic information for archiving in SunStore.


• Travelers
• Load transit application on mobile device.


• FDOT CO
• Provide Authroization, SCMS and Map services to Citties and Counties in the FDOT District 5 region.
• Provide transportation system inventory, condition and management information for archiving.


• Archived Data Users
• Access SunStore to recieve archived data for research and analysis.


• FDOT District 5
• Collect and archive multimodal data from multimodal transportation service providers.
• Collect and archive roadside information from FDOT District 5 traffic count stations (field equipment).
• Collect and archive traffic information from RTMCs.
• Collect and archive traffic information from the FDOT District 5 RTMC.
• Coordinate the archival of information with the central Florida data warehouse and the regional ITS data warehouse.
• Coordinate the archival of information with the SunStore Data Warehouse.


• MetroPlan Orlando
• Collect and archive multimodal data from multimodal transportation service providers.
• Collect and archive traffic and accident information from TMCs.


• Private Weather Information Providers
• Coordinate SunStore for archiving weather data relevant for FDOT District 5 transportation systems.


• FDOT Central Office of Information Services
• Coordinate SunStore for archiving crash reports and other safety-related transportation data.


• SunRail
• Coordinate SunStore for archiving SunRail transit system data.