TCIP Moving Toward Implementation Eva Lerner-Lam President Palisades

TCIP: Moving Toward Implementation Eva Lerner-Lam, President Palisades Consulting Group, Inc. Presentation at the 1999 Annual Meeting of the American Public Transit Association Orlando, FL October 12, 1999

Why Are ITS Standards Important to Transit? • • • Reduce capital and operating costs (increase benefit/cost of technology) Increase flexibility (plug-and-play compatibility) Assist in meeting future funding eligibility requirements

What’s Happening to Help Make Transit ITS Standards a Reality? • • • National Architecture for ITS “Base” and “Critical” Standards National Transportation Communications for ITS Protocols – Center-To-Center • • Dedicated Short-Range Communications Location Referencing and Messaging Standard International ITS Standards Transit-specific standards: – – Bus Vehicle Area Network Transit Communications Interface Profiles Rail Transit Vehicle Interface Standards Smart Card Standards

TCIP is. . . • A “FRAMEWORK” AND A “SUITE OF BUSINESS AREA DATA OBJECTS”. The framework defines how TCIP fits into the ITS and other standards arenas, and the data objects can be specified in procurements by transit agencies to enable data exchange between transit departments and among transit and other traffic and transportation management agencies. • TRANSIT INDUSTRY-DRIVEN. Consensus-based standards developed by the transit industry, facilitated by technical support consultants with both transit and ITS expertise.

TCIP is. . . • MOVING QUICKLY. Recently approved for balloting as Recommended Standards by Standards Development Organizations (ITE, NEMA and AASHTO). • IMPETUS FOR A TRANSIT STANDARDS CONSORTIUM. User subgroups were a strong foundation for a permanent consortium.

Status of TCIP Standards

What does TCIP do? • Refines Advanced Public Transportation System (APTS) data flows • Defines a Transit Data (Interface) Dictionary (composed of relevant data objects) • Defines a Transit Message Set (composed of transit business objects or entities) • Allows flexibility by providing a mechanism for “marshaling” data flows

History • Funded by US DOT FTA and Joint Program Office for ITS in October 1996 • Developed as an ITS standard under auspices of the Institute of Transportation Engineers (ITE) • The Transit component of the National Transportation Communications for ITS Protocol (NTCIP)

Unanticipated Odyssey • Began as an “ITS standard”; now firmly rooted in the transit arena • Because of the “information engineering” focus on transit as a business enterprise, and acknowledgement of the different user groups within that enterprise, the project team had solid buy-in on the effort from the transit user community, vendors and agencies alike.

APTS ITS System Architecture PAIS Personal Information Access Parking Service Provider PMS RTS Parking Management Remote Traveler Support Intermodal Transportation Service Provider Transportation Planners PS PS Planning Subsystem Financial Institution ISP Information Service Provider TMS TRMS Traffic Management Government Administrators EM Transit Management RS Roadway Subsystem Multimodal Crossing Other TRM Recommended by Transit Industry. EMVS Emergency Vehicle Subsystem Emergency Management TRVS Transit Vehicle Subsystem (J 1708/J 1587) Tr GMS Transit Garage Management System Transit Vehicle

Transit’s Interface Problem APP APP APP

TCIP Solution APP APP TCIP Object Bus APP

TCIP Architecture Scheduling System GIS Spatial Analysis Network Analysis Display/Mapping Runcutting/ Planning CORE Business Data Bus Stop Time Pt. Route Architecture Blocking Rolling Stack VIP Work Rule Policies Procedure Map Database/ Network Roster Control Center On-Board Dispatch Annunciator Incident Management Fare Collection Unit RT Display Passenger Unit/ Radio Schedule Adherance APC VMS Comm. Center TCIP "Object" Bus

Business Area Subgroups • Passenger Information (PI) • Scheduling/Runcutting (SCH) • Incident Management (IM) • Vehicle On-Board (OB) • Transit Control Center (CC) • Fare Collection (FC) • Traffic Management (TM) • Spatial Representation (SP) • Common Public Transportation Objects (CPT) • Rail Transit Vehicle (RTV) • Paratransit [as yet unfunded] • Dynamic scheduling/transfer connection protection [as yet unfunded] • Transit garage management [as yet unfunded]

Integrating TCIP with the ITS National Architecture Transit ITS Data Flows and Deliverables A. Public Transit Vehicles B. PTV to/from Tr. MS and other transit facilities C. Tr. MS to/from Other ITS Centers (TMC, EMSC, ISP, selected transit facilities, financial organizations) D. Tr. MS to/from Kiosks

Integrating TCIP with the ITS National Architecture On-Board Fare Collection TCIP Subgroups/Object Transit Control Center Scheduling/Runcutting Passenger Information Incident Management Traffic Management Spatial Representation Common Public Transportation Objects Message Sets

Integrating TCIP with the ITS National Architecture TCIP Subgroups/Objects Transit ITS Data Flows and Deliverables A. Public Transit Vehicles On-Board Fare Collection Transit Control Center B. PTV to/from Tr. MS and other transit facilities Scheduling/Runcutting Passenger Information C. Tr. MS to/from Other ITS Centers (TMC, EMSC, ISP, selected transit facilities, financial organizations) Incident Management Traffic Management D. Tr. MS to/from Kiosks Spatial Representation Common Public Transportation Objects

TCIP Approach

Transit Communications Interface Profile Project Organization US Department of Transportation FTA/ITS Joint Program Office for ITS Standard Development Organization James Cheeks Institute of Transportation Engineers Project Director Eva Lerner-Lam Palisades Consulting Group, Inc. TCIP Steering Group James Cheeks, Eva Lerner-Lam, Polly Okunieff, Isaac Takyi NTCIP’s TCIP Technical Working Group Isaac Takyi NYC Transit Authority Working Subgroups Technical Project Manager Polly Okunieff ARINC, Inc.

Transit Communications Interface Profiles Within the ITS Standards Development Structure AASHTO, ITE, and NEMA Individual NTCIP Partner Balloting Groups NTCIP Joint Standards Committee Ed Seymour, Chair NTCIP Standards Review AASHTO, ITE and NEMA Committees Other NTCIP Working Groups Transit Standards Review Group Existing APTA, IEEE and ITE Committees TCIP Technical Working Group Isaac Takyi, Chair TCIP Working Subgroups

TCIP Current Status • Framework Standard and first 8 business area standards in final balloting stages (Traffic Management pending final TMDD ballot) • Series of 15 White Papers describing in detail specific approaches and issues • Participation by more than 800 volunteers on the TCIP TWG (transit staff, vendors, consultants, academics) • 6, 700 volunteer hours contributed at 53 face-to-face subgroup meetings • Original work plan included 4 regional workshops; completed 11, hosted by transit agencies • All documentation posted at the TCIP Website: www. tcip. org

Data Interface Standards, at last • Awakening, not to the problem (which was always present and acknowledged), but to the solution • Rapidly growing sense of empowerment and selfdetermination by the user community • Strengthened by coordination and cooperation with IEEE Rail Transit Vehicle Interface Standards Committee

The Future • How to fund testing of TCIP and development of more transit standards? • Transit Standards (TS) Consortium – A nationwide, grass-roots, transit industry initiative

TSC Mission “To provide a transit industry forum for comprehensive and integrated research, development, testing, training and maintenance of transit standards in order to improve cost effectiveness, customer service and employee satisfaction. ”

Organizational Structure • • • Independent, non-profit organization IRS-certified under Sec. 501 ( c ) 3 Twelve-member Board of Trustees Technical Council and Education/Outreach Council Technical Working Groups for Functional Areas (e. g. , data standards, hardware standards, reporting standards, etc. ) • Task Committees for specific standards-related activities

Member-Driven • Equal representation at all levels of TSC – Operators – Vendors – Other • • University Transportation Research Centers State and local DOT’s System Integrators Etc.

Funding • Three sources: – Member dues – Grants from governmental agencies – Stakeholder contributions to specific functional areas

Status of TSC Effort • White Paper published, December 1997 • First Board constituted and corporate entity legally established, March 1998 • Interim Technical Council constituted and Interim Executive Director appointed, March 1998 • First Annual Meeting, October 4, 1998 • FTA grant for start up activities: June 1999 • Charter Membership Drive until early October 1999 • Second Annual Meeting, October 25, 1999

Current Activities • Assisting FTA with planning and programming of all transit standards activities, including ITS standards • Facilitating coordinated transit ITS standards activities involving JPO, ITE, AASHTO, NEMA, SAE, IEEE, TRB and ITSA • TCIP, Other Recommended Practices (e. g. , Bus Stop Inventory, Y 2 K Aftermath, Transit Signal Priority, etc. ) • Transit ITS Outreach coordination • Newsletters, email subscriber updates, teleconferences, forums, etc.

Future Strategic Alliances • • APTA ITS America Object Management Group Open GIS Consortium

For more information. . . TCIP: www. tcip. org TSC: www. tsconsortium. org