220 likes | 350 Views
Traveler Information & Related Standards Past, Present, & Future. Information Forum Showcase ITS America Annual Meeting May 3, 2005 Joel Markowitz, Chair, SAE ATIS Committee Metropolitan Transportation Commission Oakland, CA. WARNING!. ACRONYM. SDO C2C TCIP XML SOAP ITE AASHTO
E N D
Traveler Information & Related Standards Past, Present, & Future Information Forum Showcase ITS America Annual Meeting May 3, 2005 Joel Markowitz, Chair, SAE ATIS Committee Metropolitan Transportation Commission Oakland, CA ITSA Phoenix
WARNING! ACRONYM SDO C2C TCIP XML SOAP ITE AASHTO NEMA ATIS ITS IM TMDD NTCIP APTA ITIS LRMS ZONE IEEE ASTM DSRC ADUS RDS ISO ITSA Phoenix
US National ITS Architecture ITSA Phoenix
US National ITS Architecture ITSA Phoenix
Each SDO Assigned a Functional Area • Traffic Devices (NTCIP) [NEMA, ASSHTO, ITE] • Traveler Data (ATIS) [SAE] • Transit Data (TCIP) [APTA] • Traffic Management (TMDD) [ITE] • Incident Management (IM) [IEEE] • Archived Data (ADUS) [ASTM] • DSRC [ASTM, IEEE, SAE] ITSA Phoenix
Milestones of the Past Year • Completed Revision 2 of J2354, including XML schema (published) • Complete update of original 1999 standard • Superseded J2353 • Completed Revision 2 of J2540-2, ITIS codes and phrases, including XML schema (published) • Added >100 codes needed by deployments • Completed J2266 LRMS (published) • Superseded J1746 and J2374 ITSA Phoenix
Traveler information Weather & pollution Roads & links Events & incidents Routes & itineraries Flights & schedules Preference settings Directory services Trip guidance Parking Mayday Reduced bandwidth The SAE J2354 ATIS Messages ITSA Phoenix
Group: Network Conditions 1 Traffic Conditions 2 Accidents & Incidents 3 Closures (Road and Lane) 4 Roadwork 5 Obstructions 6 Delays, Status, And Cancellations 7 Unusual Driving 8 Mobile Situation 9 Device And Equipment Status 10 Restrictions 11 Incident Response Status Group: Events Affecting Travel 12 Disasters 13 Disturbances 14 Sporting Events 15 Special Events 16 Parking Information 17 Information System Group: Travel Environment 18 Weather Conditions 19 Precipitation 20 Winds 21 Visibility & Air Quality 22 Temperature 23 Pavement Conditions 24 Winter Driving Restrictions & Recommendations 25 Winter Driving Index Group: Advice 26 Suggestion Advice 27 Warning Advice 28 Instructions (Recommendations) 29 Instructions (Mandatory) Group: Qualifiers 31 Generic Locations 32 Lane / Roadway Descriptions 33 Alternate Route Group: Groups Affected / Involved 35 Transit Mode 36 Vehicle Groups Affected 37 Traveler Group Affected 38 Responder Group Affected 39 Incident Response Equipment ITIS Main Groups
“ITIS picker” screen shot • One of several small utilities have been created as part of the training and outreach effort ITSA Phoenix
ITIS Is Everywhere • ITIS codes are central to how ITS messages work in ATIS, IM, TMDD and TCIP • ITIS codes can be freely mixed with text • ITIS sub-groupings form the top level taxonomy for all message filtering and grouping • ITIS code list is growing, with new codes being added, but allows local codes to be easily created and used in a structured way ITSA Phoenix
The Next 6 Months • All major development work accomplished maintenance mode • XML • Develop Web services XML files • Integrate with completed XML Schema file efforts • Close cooperation with C2C XML working group • Revise and re-ballot standards as needed based on above (J2354 and J2540/2 rev3) • Continue coordination with TMDD, TCIP, and Incident Management standards • Ensure cross-use of messages and data elements ITSA Phoenix
Training/Outreach User Guides (draft) Part of ITE standards training program 511 Implementation Guidelines Conferences World Congress demo Tools and Utilities “Mini-Edit” “ITIS Picker” On-line web support resources, discussion board Deployment Support ITSA Phoenix
The Importance of Coordinating Standards • Technical reasons • Ease of development, modification, revision • Practical/functional reasons • “No system is an island,” complex systems require multiple standards that have to ‘plug and play” • Focus on common data elements & code lists, naming & coding conventions ITSA Phoenix
Center to Center Message Sets Cross Integration ATIS TMDD IM TCIP ITSA Phoenix
An Example of Cross SDO Integration The IM message “road work” uses the ATIS message “event” which in turn uses the IM “lane description” which in turn uses several TMDD codes, some of which come from ITIS codes. IEEE IM Standards SAE ATIS Standards Road Work Message which uses... EventMessage which uses... LaneDescription ITIS Codes which uses... which uses... TMDD Items ITSA Phoenix
Facilitate Center Coordination City Traffic State DOT Emergency Dispatch ITSA Phoenix
What’s the Real Value of these ITS Standards ? • Provides the means for consistent information exchange among information centers, public and private • Preserves integrity of information from the sources • Increases credibility and reliability of information • Allows service providers to focus on value-added services • Facilitates national interoperability ITSA Phoenix
For further Information… • General: www.sae.org • The ITS Standards Discussion Board: • For postings & on-going technical discussions of all things ATIS (as well as other key standards)http://serv4.itsware.net/bb/index.php • Register on-line to receive current information and join in the deployment discussions. • The tools and links mentioned in this briefing can all be obtained at the above. ITSA Phoenix
For further Information… • SAE Advanced Traveler Information Systems Standards Committee • New members are always welcome! • Chairman: Joel Markowitz jmarkowitz@mtc.ca.gov • Consultant: David Kelley davidkelley@itsware.net • Standards Forum: • http://serv4.itsware.net/bb/index.php ITSA Phoenix