Intelligent Transportation Systems Data Dictionaries and Data Registry Thomas M. Kurihara
July 11, 2018 | Author: Anonymous | Category: N/A
Short Description
Download Intelligent Transportation Systems Data Dictionaries and Data Registry Thomas M. Kurihara...
Description
Intelligent Transportation Systems Data Dictionaries and Data Registry
Thomas M. Kurihara IEEE ITS Program Manager Standards Activities 17 February 1999
A Growing Demand for Integrated Transportation Systems Increasing Demands: • 30% increase in traffic • 50% increase in vehicles • 6 million crashes per year; 41,000 fatalities • Changing demographics
Limited Resources: • Limited space to build new capacity • Financial constraints • Environmental impacts / land use concerns Extracted from Lockheed Martin ITS National Architecture Team Outreach Session Presentation, 1998
ITS User Services are the Basis for National ITS Architecture
National Architecture Describes Integration of ITS Infrastructure Components
Traffic Signal Control Electronic Toll
RR Grade Crossing Safety
National ITS Architecture
Transit Management
Multi-Modal Traveler Information Emergency Response Management
Freeway Management Electronic Fare Payment Incident Management
Architecture Subsystems Centers
Travelers Traffic Traffic Management Management
Remote Traveler Support
Information Service Provider
Personal Information Access
Vehicle
Emergency Management
Emissions Management
Toll Administration
Transit Transit Management Management
Commercial Vehicle Administration
Fleet and Freight Management
Planning
Roadway Transit Vehicle
Toll Collection
Commercial Vehicle
Vehicles
Parking Management
Emergency Vehicle
Roadside
Commercial Vehicle Check
Architecture Subsystems & Interconnects Centers
Travelers Traffic Management
Remote Traveler Support
Information Service Provider
Personal Information Access
Emergency Management
Emissions Management
Vehicle
Transit Vehicle Commercial Vehicle
Vehicles
Emergency Vehicle
Transit Management
Commercial Vehicle Administration
Fleet and Freight Management
Planning
Wireline Communications
Dedicated Short Range Communications
Vehicle to Vehicle Communications
Wide Area Wireless Communications
Toll Administration
Roadway
Toll Collection
Parking Management
Roadside
Commercial Vehicle Check
Your Proposed Architecture: Stakeholders Traveler Subsystems
Center Subsystems Information Service Provider
Remote Traveler Support
- Metro Traffic - Fastline - RBDS Systems
- Metropolitan Transit Kiosks Personal Information Access
Traffic Management
- FMC -Metro TOC -Suburban TOC -Small-town TOC*
Emergency Management
- Metro Fire - Metro PD - Suburban Fire - Suburban Police - Small-town Fire - Metro E-911
Vehicle
Transit Vehicle
- Metro Transit AVL - Suburban Transit AVL* Emergency Vehicle
Vehicle Subsystems
-Metro Transit -Suburban Transit
Planning -Metro RTA -Metro University
Wireline Communications
Dedicated Short Range Communications
Wide Area Wireless Communications
Transit Management
Roadway Roadway
- CCTV - Loops - Ramp Meters - VMS - Signals - Signal Priority System* Parking Management
Roadside Subsystems
* Indicates future (proposed) system components
- City Lots - Parking4Cheap Inc.
Next Level of Detail request for traffic information
Traffic Management Subsystem
traffic information transit system data request for signal priority signal priority status
Transit Management Subsystem
High-level subsystem information exchange Considerations for integration
Architecture and Standards request for traffic information
ITS Architecture
Traffic Management Subsystem
traffic information transit system data request for signal priority signal priority status
Transit Management Subsystem
Transit Communications Interface Profiles
ITS Standards
Traffic Management Data Dictionary NTCIP Center to Center
Proposed Architecture-Next Level of Detail
Transit Management
request for transit signal priority signal priority status
Traffic Management
(Metro Transit)
transit system data
(Metro TOC)
transit vehicle conditions
vehicle probe data
vehicle probe data
signal control status
local signal priority request
Transit Vehicle
vehicle probe data
Roadway
request for right of way
AVL Project
Transit Management
request for transit signal priority signal priority status
Traffic Management
(Metro Transit)
transit system data
(Metro TOC)
transit vehicle conditions
vehicle probe data
vehicle probe data
signal control status
local signal priority request
Transit Vehicle
vehicle probe data
Roadway
request for right of way
Standard for Data Dictionaries for Intelligent Transportation Systems (IEEE P1489) • • • •
IEEE Standards Coordinating Committee 32, ITS Data Dictionary / Message Set Template Working Group Sponsor: ITS Joint Program Office, Federal Highway Administration Facilitator: Intelligent Transportation Society of America ITS functional area data/message set standards development » Traffic Management Data Dictionary (TMDD) [Institute of Transportation Engineers (ITE), American Association of State Highway and Transportation Officials (AASHTO)] » Transit Communications Interface Protocol (TCIP) [IEEE, ITE, AASHTO, National Electrical Manufacturers Association (NEMA)] » Advanced Traveler Information Systems (ATIS) Data Dictionary [Society of Automotive Engineers (SAE), AASHTO] » Incident Management / Emergency Service [IEEE, ITE, AASHTO, National Nine-One-One Number Association (NENA)] » Dedicated Short Range Communications (IEEE, American Society for Testing and Materials (ASTM)
ITS DATA DICTIONARIES • Mechanism for storing formally described data elements and data concepts, and associated documenting information (“meta data”) • Three types: » Application: Implementation-specific application developer’s database of data elements (not in scope for IEEE P1489) » Functional: ITS National Architecture described data flows, e.g., Information Service Provider (ISP) databases of data elements and related concepts (Advanced Traveler Information Systems (ATIS)) » Registry: ITS level database of fully described data elements and related data concepts (All ITS data dictionary contents), ITS message sets, and ITS Data Registry metadata • Goal: Interoperable, reusable data; unambiguous data interchange
IEEE P1489 DESIGN CONCEPTS • Based upon ISO/IEC 11179, Specification and Standardization of Data Elements • Some tailoring to ITS needs, e.g., meta attribute name changes and definition clarifications, specific conventions • Extensions based upon ANSI X3.285, Metamodel for the Management of Sharable Data » Entity types (i.e., ISO/IEC 11179 ‘object class’) » Properties » Value Domains » Data Element Concepts » ‘Generic Property Domains’ (i.e., ISO/IEC 11179 ‘generic data element’)
• Additional “administrative” meta attributes, e.g., “user”, “view” • Includes ITS message sets (ITS Data Registry only) • Includes ITS meta attributes (ITS Data Registry only)
Eight Data Concepts Adopted by ITS Data Element Components Data Element Constructs Entity Type Bus route
Data Element Concept
Property
node/stop
Data Element
Generic Property Domain
Value Domain
lat/long (degrees/minutes/seconds)
Plus, message sets and meta attributes
Meta Attribution Requirements • Mandatory (M), same as ISO 11179
• Optional (O), same as ISO 11179 • Conditional (C), same as ISO 11179 • Indicative (I), Dependent upon an “if” condition, of some type; if the “if” condition is true then meta attribute is required
A Little More Detail... Data Data Generic Entity Property Value CLAUSE Element Element Property Type Domain Concept Domain META ATTRIBUTES CONCEPTUAL SCHEMA Descriptive Name
NOTE M
O
O
O
O
O
M
C
C
C
C
C
M
C
C
C
C
C
O
O
O
O
O
O
C
C
C
C
C
C
‘C’ = Required when clause 5.1.1.4 optioned.
I
N/A
I
N/A
N/A
I
‘I’ = Required if it exists.
O
O
O
O
O
O
M
O
O
O
O
O
M
C
C
C
C
C
M
C
C
C
C
C
I
I
I
I
I
I
5.1.1.1 Descriptive Name Context
5.1.1.2 Definition 5.1.1.3 Synonymous Descriptive Name Synonymous Descriptive Name Context Formula
‘C’ = Required when clause 5.1.1.1 optioned. ‘C’ = Required when clause 5.1.1.1 optioned.
5.1.1.4 5.1.1.5 5.1.1.6
Source 5.1.1.7 Class Name 5.1.1.8 Classification Scheme Name 5.1.1.9 Classification Scheme Vers. 5.1.1.10 Data Concept Type 5.1.1.11
At least one annex E class name is required for data elements. ‘C’ = Required when clause 5.1.1.8 optioned. ‘C’ = Required when clause 5.1.1.8 optioned. ‘I’ = Mandatory if non data element data concepts are contained in data dictionary.
What Does the P1489 Cover? • How to describe and document ITS data concepts in ITS data dictionaries (Part 1): » Identifiers (sequential, non-significant, numeric identifier are specified) » Definitions » Relationships, etc. » Specific naming convention » Specific suggested value domains » Specific required representation class terms » Specific ITS classification scheme • How to register and improve documentation of data concepts, including message sets and metadata (Part 2)
Naming Convention • Entity Type Term, with modifiers (entity): CONSTRUCTION.ROAD • Property Term, with modifiers (information of interest): TargetCompletion • Representation Class Term: (format & syntax for instance values): date • CONSTRUCTION.ROAD_TargetCompletion_date » Proposed design provides for a list of recommended Representation Class Terms and Value Domains; Value Domains includes class word and legal value list (or a rule for creating a legal value list, e.g., from ANSI X3.30)
ITS Data Dictionaries in Pictures ITS Data Registry
Foreign Data Registry
ITS Functional Area Data Dictionary
Foreign Data Dictionary
ITS Implementation Data Dictionary
•ITS Registration Roles
• Registrar » ISO/IEC 11179 “Registration Authority”
• Steward » ISO/IEC 11179 “Responsible Organization”
• Submitter » ISO/IEC 11179 “Submitting Organization”
ITS Registry Roles Relationships
•
•
•
EPA Data Registrar
ITS Registrar
••
ITS Enterprise Data Registry •
••
• Traffic Management Steward
ITS Stewards Relevant Data Dictionaries/ Registries
• Submitter
• •
Traffic Management Registry View
Data Registry Views
•ITS Registration Status Levels
• Preferred » ISO/IEC 11179 “Standardized”
• Qualified
» ISO/IEC 11179 “Certified”
• Recorded
» ISO/IEC 11179 “Recorded”
• Working Draft
» ISO/IEC 11179 “Incomplete”
• Deleted
» ISO/IEC 11179 “Retired”
• Intermediate administrative status levels
ITS Registration Process Submitter
Steward
Registrar 8
6
Proposes data concept for preferred status
4 Checks quality of candidate & reviews appropriate external registries
Confirms concurrence of ITS Stewards as Preferred
7 Acknowledges status and submits for review by ITS Stewards
5 Confirms/resolves quality of data registration proposal
Submits data concept to registry
Preferred
Provisionally Preferred
Qualified
Recorded Request Recorded
1 Identifies & documents data concept
Stewardship Area “A” View
Provisionally Qualified 3 Confirms/resolves completeness of registration proposal
2
ITS Data Registry
Working Draft
Identifies path of lead responsibility
ITS IEEE P1489 Status
•
•
IEEE DD/DR IEEE P1489, Part 1
» Balloted, comment resolution in progress » Submit to IEEE Standards Board for endorsement, June 1999 IEEE DD/DR IEEE P1489, Part 2
» Sponsor SCC 32, ITS DD/MST WG Chair position recently filled » Plan to subcontract to a consultant to create draft Part 2, based upon
•
»
preliminary notes from P1489 Part 1 development, the ITS Data Registry Functional Design Document, and the ITS Data Registry Functional Operating Procedures ITS DD/MST (P1489/P1488) WG to be reactivated this summer
ITS Data Registry Development
» ITS Data Registry Functional Design Document completed » ITS Data Registry Functional Operating Procedures completed » April 1999 start date for development anticipated
ITS Data Registry Development
• • • •
Re-activate ITS Interim Data Registrar Function Develop ITS Data Registry Establish a working prototype of ITS Data Registry Activate ITS Data Registry governance groups
» ITS Data Registry Configuration Control Committee - Provide technical direction - Resolve technical issues - Progressing data concepts through registration status levels - Approving Data Registry structures, procedures, and formats - Identify authorized users and types of users » ITS Data Registry Board of Directors - Establishes policy - Provides overall direction - Resolves strategic issues - Maintains and manages the Data Registry Business Plan
View more...
Comments