| 7.0 | INFORMATION MANAGEMENT |
| 7.1 | ARCHIVED DATA FUNCTION |
| 7.1.0 | ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas. |
| 7.1.1 | The Archived Data Function shall provide a Historical Data Archive (HDA) system for ITS data. |
| 7.1.1.1 | HDA shall include repositories of operational data received from field equipment or data collection devices. |
| 7.1.1.2 | HDA shall provide permanent historical data repositories. |
| 7.1.1.3 | HDA repositories shall include meta data and meta-attributes repositories. |
| 7.1.1.4 | HDA shall provide ITS data system security. |
| 7.1.1.4.1 | HDA shall be capable of employing security solutions. |
| 7.1.1.4.2 | HDA shall be capable of preventing data loss. |
| 7.1.1.4.3 | HDA shall be capable of preventing unauthorized access to ITS data repositories |
| 7.1.1.4.4 | HDA shall be capable of providing a secure interface for online support of the ITS user interface. |
| 7.1.2 | The Archived Data Function shall include an Operational Data Control (ODC) function to ensure integrity of operational data as received from field equipment or data collection devices. |
| 7.1.2.1 | ODC shall be capable of receiving and storing all ITS operational data, as received from the source. |
| 7.1.2.1.1 | ODC shall ensure ITS operational data are in proper format. |
| 7.1.2.1.2 | ODC shall maintain the meta data schema for all ITS data entering the system. |
| 7.1.2.1.3 | ODC shall be capable of assigning the following meta attributes, when available, to ITS operational data during the archive process. |
| 7.1.2.1.3(a) | The equipment used to collect the data. |
| 7.1.2.1.3(b) | The conditions under which the data were collected. |
| 7.1.2.1.3(c) | The status of the equipment at the time of collection. |
| 7.1.2.1.4 | ODC shall be capable of applying user-defined quality control verification on ITS data and annotating results in the appropriate meta files. |
| 7.1.2.1.5 | ODC shall be capable of assigning meta-attributes to the data indicating the methods used to perform: |
| 7.1.2.1.5(a) | summarization and aggregation |
| 7.1.2.1.5(b) | transformations (i.e., reconstructing original data or constructing new data elements) |
| 7.1.2.2 | ODC shall be capable of collecting user-selected data. |
| 7.1.2.3 | ODC shall be capable of archiving, in data repositories, ITS operational data as received from field equipment or data collection devices. |
| 7.1.2.4 | ODC shall be capable of maintaining the integrity of all received operational data. |
| 7.1.2.5 | ODC shall be capable of disseminating data replicates to ITS operational users in real-time. |
| 7.1.3 | The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function. |
| 7.1.3.1 | DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories. |
| 7.1.3.1.1 | DIV shall be capable of importing ITS Freeway Operations data to include: |
| 7.1.3.1.1(a) | Freeway traffic flow surveillance data. |
| 7.1.3.1.1(b) | Ramp meter preemptions. |
| 7.1.3.1.1(c) | Ramp meter operational data. |
| 7.1.3.1.1(d) | Freeway visual and video surveillance data. |
| 7.1.3.1.1(e) | Traffic Management Center generated freeway flow metrics. |
| 7.1.3.1.2 | DIV shall be capable of importing ITS Electronic Toll Collection data. |
| 7.1.3.1.3 | DIV shall be capable of importing ITS Arterial data to include: |
| 7.1.3.1.3(a) | Traffic signal preemptions. |
| 7.1.3.1.3(b) | Traffic signal operational data. |
| 7.1.3.1.3(c) | Arterial visual and video surveillance data. |
| 7.1.3.1.3(d) | Traffic Management Center generated arterial flow metrics. |
| 7.1.3.1.3(e) | Arterial traffic flow surveillance data. |
| 7.1.3.1.4 | DIV shall be capable of importing ITS Transit and Ridesharing data to include: |
| 7.1.3.1.4(a) | Transit usage data. |
| 7.1.3.1.4(b) | Transit route data including schedule deviations. |
| 7.1.3.1.4(c) | Rideshare requests. |
| 7.1.3.1.4(d) | Multimodal Origin/Destination. |
| 7.1.3.1.4(e) | Fares |
| 7.1.3.1.4(f) | Vehicle maintenance |
| 7.1.3.1.4(g) | Personnel management data |
| 7.1.3.1.5 | DIV shall be capable of importing ITS Incident Management data to include: |
| 7.1.3.1.5(a) | Incident characteristics. |
| 7.1.3.1.5(b) | Train arrivals at highway rail intersections. |
| 7.1.3.1.5(c) | Emergency vehicle dispatch data. |
| 7.1.3.1.5(d) | Emergency vehicle location data. |
| 7.1.3.1.5(e) | Construction and work zone identification. |
| 7.1.3.1.5(f) | Emergency request data |
| 7.1.3.1.5(g) | Video surveillance data |
| 7.1.3.1.5(h) | Emergency response |
| 7.1.3.1.6 | DIV shall be capable of importing ITS Commercial Vehicle Operations data to include: |
| 7.1.3.1.6(a) | Cargo identification data. |
| 7.1.3.1.6(b) | Fleet activity data. |
| 7.1.3.1.6(c) | Hazardous material packaging data. |
| 7.1.3.1.6(d) | Border crossing data. |
| 7.1.3.1.6(e) | Commercial vehicle on-board safety data. |
| 7.1.3.1.6(f) | Truck Origin/Destination and Classification data |
| 7.1.3.1.7 | DIV shall be capable of importing ITS Environmental data to include: |
| 7.1.3.1.7(a) | Emission data. |
| 7.1.3.1.7(b) | Weather data. |
| 7.1.3.1.8 | DIV shall be capable of importing ITS Vehicle and Traveler data to include: |
| 7.1.3.1.8(a) | Commercial and non-commercial vehicle probe data. |
| 7.1.3.1.8(b) | VMS message set data. |
| 7.1.3.1.8(c) | Vehicle trajectories. |
| 7.1.3.1.8(d) | Route guidance data. |
| 7.1.3.1.8(e) | Parking and roadway pricing change data. |
| 7.1.3.1.8(f) | Origin/destination trip data. |
| 7.1.3.1.8(g) | Service requests |
| 7.1.3.1.8(h) | Information utilization |
| 7.1.3.1.9 | DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include: |
| 7.1.3.1.9(a) | Roadway network attributes. |
| 7.1.3.1.9(b) | Transit network attributes. |
| 7.1.3.1.9(c) | Equipment maintenance status |
| 7.1.3.1.9(d) | Transportation facilities. |
| 7.1.3.1.9(e) | GIS map of network. |
| 7.1.3.1.9(f) | Infrastructure maintenance data |
| 7.1.3.1.10 | DIV shall be capable of importing ITS Parking Management data. |
| 7.1.3.1.11 | DIV shall be capable of importing Intermodal Operational data. |
| 7.1.3.2 | DIV shall be capable of accepting pre-defined data inputs from transportation or other sources. |
| 7.1.3.3 | DIV shall be capable of applying pre-defined quality control verification on the imported ITS data and annotating results in the appropriate meta files. |
| 7.1.3.4 | DIV shall be capable of formatting the data to conform to the archive schema. |
| 7.1.3.5 | DIV shall be capable of cleansing imported data |
| 7.1.3.5.1 | Cleansing shall include the removal of source privacy attributes. |
| 7.1.3.5.2 | Cleansing shall be capable of assigning unique system-developed anonymous identifiers to data during archiving. |
| 7.1.3.6 | DIV shall be capable of performing pre-defined data mining functions to import data. |
| 7.1.3.7 | DIV shall be capable of performing pre-defined data fusion on imported data near real-time. |
| 7.1.3.8 | DIV shall be capable of assigning meta attributes to ITS operational data if data modification is required during the historical archive process. |
| 7.1.3.9 | DIV shall be capable of notifying source system owners of potential data or equipment errors. |
| 7.1.4 | The Archived Data function shall provide the Automatic Data Historical Archive (ADHA) function for permanently archiving the data. |
| 7.1.4.1 | ADHA shall provide an archive schema for all ITS data entering the archives. |
| 7.1.4.1.1 | The archive schema shall preclude the possibility of identifying or tracking either individual citizens or private firms. |
| 7.1.4.1.2 | ADHA shall strip all identifiers of individual citizens or private firms from all data before archiving. |
| 7.1.4.1.3 | ADHA shall be capable of assigning unique system-developed anonymous identifiers to data during archiving. |
| 7.1.4.2 | ADHA shall manage the ITS historical data archiving processes for all functional areas as follows: |
| 7.1.4.2(a) | Format data to archive schema conformance. |
| 7.1.4.2(b) | Maintain a centralized meta schema to specify how data is archived. |
| 7.1.4.2(c) | Maintain data quality meta attributes. |
| 7.1.4.2(d) | Schedule archiving of data. |
| 7.1.4.3 | ADHA shall permanently store historical archives and only provide data replicates to users. |
| 7.1.4.4 | ADHA shall be capable of supporting user-specified data archiving procedures as follows: |
| 7.1.4.4(a) | When specified by a user, archive operational data as received in the user's storage files. |
| 7.1.4.4(b) | When specified by a user, archive edited data in the User's storage files. |
| 7.1.4.4(c) | When specified by a user, perform pre-defined data fusion before archiving in User's storage files. |
| 7.1.4.5 | ADHA shall be capable of assigning meta attributes to ITS operational data if data modification is required during the historical archive process. |
| 7.1.5 | The Archived Data Function shall provide a Data Warehouse Distribution (DWD) function as the ITS data source to support the ITS community user functions. |
| 7.1.5.1 | DWD shall be capable of supporting the generation of data products for the following transportation agencies: |
| 7.1.5.1(a) | Planning |
| 7.1.5.1(b) | Operations |
| 7.1.5.1(c) | Safety |
| 7.1.5.1(d) | Research |
| 7.1.5.2 | DWD shall include a User Data Products (UDP) function. |
| 7.1.5.2.2 | UDP shall be capable of recreating ITS operational data formats from the historical archives. |
| 7.1.5.2.3 | UDP shall be capable of providing user defined data mining functions on ITS data sources. |
| 7.1.5.2.4 | UDP shall be capable of performing user defined data fusion functions on data extracted from ITS Archives. |
| 7.1.5.3 | DWD shall have the single point of administration for the archived data system. |
| 7.1.6 | The Archived Data Function shall provide users with an ITS Community Interface (ICI) including all ITS users for the specification and retrieval of data products. |
| 7.1.6.1 | ICI shall be the common data interface for all ITS users to access the ITS Data Archives. |
| 7.1.6.1.1 | ICI shall provide users' systems with the data interface functionality. |
| 7.1.6.2 | ICI shall manage user access and security across the interface. |
| 7.1.6.2.1 | ICI shall be capable of cleansing data to remove source privacy attributes before archiving data. |
| 7.1.6.2.2 | ICI shall be capable of cleansing data to remove source privacy attributes before exporting data to users. |
| 7.1.6.3 | ICI shall provide a user-interface functionality to existing data warehouse data schema for users to define their data products. |
| 7.1.6.3.1 | The user-interface shall permit users to define access to multiple databases as data sources for their data products. |
| 7.1.6.3.2 | The user-interface shall permit users to select online analytical functions to produce their data products. |
| 7.1.6.3.3 | The user-interface shall permit the user to view sample data products. |
| 7.1.6.4 | ICI shall provide the user interface for ITS Transportation Agencies. |
| 7.1.6.4.1 | Transportation agencies shall include the following planning functions: |
| 7.1.6.4.1(a) | Metropolitan Planning Organizations (MPO) and State Transportation Planning |
| 7.1.6.4.1(b) | Transportation System Monitoring |
| 7.1.6.4.1(c) | Air Quality Analysis |
| 7.1.6.4.1(d) | MPO/State Freight and Intermodal Planning |
| 7.1.6.4.1(e) | Land Use Regulation and Growth Management |
| 7.1.6.4.1(f) | Transportation Administration and Policy Analysis. |
| 7.1.6.4.1(g) | Transit Planning |
| 7.1.6.4.2 | Transportation agencies shall include the following ITS Operations functions: |
| 7.1.6.4.2(a) | Traffic Management. |
| 7.1.6.4.2(b) | Transit Management. |
| 7.1.6.4.2(c) | Construction and Maintenance. |
| 7.1.6.4.2(d) | The Private Sector. |
| 7.1.6.4.3 | Transportation functions shall include the following safety agencies: |
| 7.1.6.4.3(a) | Safety Planning and Administration. |
| 7.1.6.4.3(b) | Commercial Vehicle Operations. |
| 7.1.6.4.3(c) | Emergency Management. |
| 7.1.6.4.4 | Transportation agencies shall include research agencies. |
| 8.0 | MAINTENANCE AND CONSTRUCTION MANAGEMENT |
| 8.1 | MAINTENANCE AND CONSTRUCTION OPERATIONS |
| 8.1.1 | Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers. |
| 8.1.1.6 | MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems. |
| 8.1.1.6.7 | MVFM shall support transmission of fleet operations data to archives. |
| 8.1.2 | Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations. |
| 8.1.2.10 | RWM shall archive data for use in performance monitoring activities. |
| 8.1.3 | Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers. |
| 8.1.3.1 | WZMS shall monitor, control, and direct activity in the vicinity of work zones. |
| 8.1.3.1.3 | WZMS shall be able to divert vehicles around work zones via automated lane changing techniques. |
| 8.1.3.1.3.2 | WZMS shall support archiving of field data. |
| | |
