intelligent transportation systems data dictionaries and data registry thomas m. kurihara ieee its...
TRANSCRIPT
Intelligent Transportation SystemsData Dictionaries and Data
Registry
Thomas M. KuriharaIEEE 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 theBasis for National ITS Architecture
National Architecture Describes Integration of ITS Infrastructure Components
Multi-ModalTraveler
Information
ElectronicFare
Payment
FreewayManagement
TransitManagement
TrafficSignal
Control
ElectronicToll
RR GradeCrossing Safety
EmergencyResponse
ManagementIncident
Management
Multi-Modal
Traveler
Information
FreewayManagement
Transit
Management
TrafficSignalControl
Ele
ctro
nic
To
ll
RR Grade
Crossing Safety
Emergency
Response
Managem
ent
Inci
dent
Man
agem
ent
Electronic
Fare
Payment
National ITS Architecture
Architecture Subsystems
Travelers
Vehicles Roadside
Centers
CommercialVehicle
Administration
Planning
Vehicle
TransitVehicle
CommercialVehicle
EmergencyVehicle
RemoteTravelerSupport
PersonalInformation
Access
TollAdministration
EmergencyManagement
TrafficManagement
Fleet andFreight
Management
TransitManagement
EmissionsManagement
InformationServiceProvider
Roadway
Toll Collection
ParkingManagement
CommercialVehicleCheck
TrafficManagement
TransitManagement
Architecture Subsystems & Interconnects
Travelers
Vehicles Roadside
Centers
Wide Area Wireless Communications
Veh
icle
to
Veh
icle
Co
mm
un
icat
ion
s
CommercialVehicle
Administration
Planning
Ded
icat
ed S
ho
rt R
ang
e C
om
mu
nic
atio
ns
Vehicle
TransitVehicle
CommercialVehicle
EmergencyVehicle
RemoteTravelerSupport
PersonalInformation
Access
TollAdministration
EmergencyManagement
TrafficManagement
Fleet andFreight
Management
TransitManagement
EmissionsManagement
InformationServiceProvider
Roadway
Toll Collection
ParkingManagement
CommercialVehicleCheck
Wireline Communications
Wireline Communications
Roadside SubsystemsVehicle Subsystems
Center Subsystems
Wide Area Wireless Communications
Traveler Subsystems
Remote Traveler Support
Personal Information
Access
Information Service Provider
Emergency Management
Transit Management
Planning
Vehicle
Transit Vehicle
Emergency Vehicle D
edic
ated
Sho
rt
Ran
ge C
omm
unic
atio
ns
Parking Management
Traffic Management
Roadway
- FMC-Metro TOC-Suburban TOC-Small-town TOC*
- Metro Fire- Metro PD- Suburban Fire- Suburban Police- Small-town Fire- Metro E-911
- CCTV- Loops- Ramp Meters- VMS- Signals- Signal Priority System*
-Metro Transit-Suburban Transit
- Metropolitan Transit Kiosks
- Metro Transit AVL- Suburban Transit AVL*
- Metro Traffic- Fastline- RBDS Systems
-Metro RTA-Metro University
- City Lots- Parking4Cheap Inc.
* Indicates future (proposed) system components
Wireline Communications
Roadway
Your Proposed Architecture: Stakeholders
Next Level of Detail
TrafficManagementSubsystem
Transit ManagementSubsystem
traffic information
request fortraffic information
transit system data
signal priority statusrequest for signal priority
High-level subsystem information exchange
Considerations for integration
Architecture and Standards
TrafficManagementSubsystem
Transit ManagementSubsystem
traffic information
request fortraffic information
transit system data
signal priority status
NTCIP Center to Center
Traffic Management Data Dictionary
Transit Communications Interface Profiles
ITSArchitecture
ITSStandards
request for signal priority
Proposed Architecture-Next Level of Detail
TrafficManagement
(Metro TOC)
TransitManagement
(Metro Transit)
RoadwayTransitVehicle
transit system data
signal priority status
request for transit signal priority
transitvehicle
conditions
vehicleprobe data
local signal priority request
vehicle probe data
vehicleprobe data
signalcontrolstatus
requestfor
right ofway
AVL Project
TrafficManagement
(Metro TOC)
TransitManagement
(Metro Transit)
RoadwayTransitVehicle
transit system data
signal priority status
request for transit signal priority
transitvehicle
conditions
vehicleprobe data
local signal priority request
vehicle probe data
vehicleprobe data
signalcontrolstatus
requestfor
right ofway
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, Functional: ITS National Architecture described data flows,
e.g., Information Service Provider (ISP) databases of data e.g., Information Service Provider (ISP) databases of data elements and related concepts (Advanced Traveler elements and related concepts (Advanced Traveler Information Systems (ATIS))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
Value Domain
Property
EntityType
Data Element Constructs
Data ElementConcept
GenericProperty Domain
Data Data ElementElement
Data Element Components
Bus route
node/stop
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...
META ATTRIBUTES
CLAUSEData
ElementData
ElementConcept
GenericPropertyDomain
EntityType
Property ValueDomain
NOTECONCEPTUAL SCHEMADescriptive Name
5.1.1.1M O O O O O
Descriptive Name Context5.1.1.2
M C C C C C ‘C’ = Required whenclause 5.1.1.1 optioned.
Definition5.1.1.3
M C C C C C ‘C’ = Required whenclause 5.1.1.1 optioned.
Synonymous DescriptiveName 5.1.1.4
O O O O O O
Synonymous DescriptiveName Context 5.1.1.5
C C C C C C ‘C’ = Required whenclause 5.1.1.4 optioned.
Formula5.1.1.6
I N/A I N/A N/A I‘I’ = Required if itexists.
Source5.1.1.7
O O O O O O
Class Name5.1.1.8
M O O O O O At least one annex Eclass name is requiredfor data elements.
Classification Scheme Name5.1.1.9
M C C C C C ‘C’ = Required whenclause 5.1.1.8 optioned.
Classification Scheme Vers.5.1.1.10
M C C C C C ‘C’ = Required whenclause 5.1.1.8 optioned.
Data Concept Type5.1.1.11
I I I I I I ‘I’ = Mandatory ifnon data element dataconcepts arecontained in datadictionary.
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
ITS Functional Area Data Dictionary
ITS Implementation Data Dictionary
Foreign Data Registry
Foreign DataDictionary
• Registrar» ISO/IEC 11179 “Registration Authority”
• Steward» ISO/IEC 11179 “Responsible Organization”
• Submitter» ISO/IEC 11179 “Submitting Organization”
•ITS Registration Roles
DataRegistry Views
•••
ITSRegistrar•
••
Relevant DataDictionaries/Registries
EPAData
Registrar
TrafficManagement
Steward
ITS Stewards
• • •
•••
TrafficManagement
RegistryView
ITS Enterprise Data
Registry
Submitter
ITS Registry Roles Relationships
• 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 Status Levels
ITS Registration Process
RegistrarSubmitter Steward
Stewardship Area “A”
View
ITS DataRegistry
Request Recorded
ProvisionallyQualified
Qualified
Working Draft
Recorded
ProvisionallyPreferred
Preferred
Identifies path of lead responsibility
Checks qualityof candidate & reviews
appropriate externalregistries
Identifies &documents
data concept
Confirms/resolvescompleteness of
registration proposal
Confirms/resolvesquality of data
registration proposal
Confirms concurrence of ITS
Stewards as Preferred
Proposes data concept for
preferred status
Acknowledges
review byITS Stewards
status and submits for
Submits data concept to registry
1
2
3
4
5
67
8
• 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 IEEE P1489 Status
• 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
ITS Data Registry Development