1 / 46

TCIP TWG Kickoff Meetings

TCIP TWG Kickoff Meetings. Passenger Information TWG December 8, 2003. Welcome & Introductions. Lou Sanders APTA Mark Nawrath Passenger Information TWG Chair. Agenda. TCIP Task Force Structure John Fayos TCIP Status & Review Plans John Fayos TCIP 2.4 Rob Ayers

brennan-mayo
Download Presentation

TCIP TWG Kickoff Meetings

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCIP TWG Kickoff Meetings Passenger Information TWG December 8, 2003

  2. Welcome & Introductions Lou Sanders APTA Mark Nawrath Passenger Information TWG Chair

  3. Agenda • TCIP Task Force Structure John Fayos • TCIP Status & Review Plans John Fayos • TCIP 2.4 Rob Ayers • Passenger Information Rob Ayers • TCIP Web Site Diane O’Neill • Review Comment Submissions Diane O’Neill • Q&A

  4. TCIP Task Force Structure John Fayos Critical Link

  5. TCIP Task Force • Task Force Co-Chairs • Isaac Tayki & Jerry Lutin • TWG Chairs Committee • TWG Chairs • Chair Coordinating Forum (CCF) • Task Force Co-Chairs • APTA Technical Team • Program Manager • Lou Sanders

  6. Technical Working Groups • TWG 1: Scheduling / Runcutting (Dan Overgaard) • TWG 2: Passenger Information (Mark Nawrath) • TWG 3: Incident Management (Edward Mark) • TWG 4: Software Tools & Test (Bill Hiller) • TWG 5: On Board (TBA) • TWG 6: Control Center (Marc Gordon) • TWG 7: Fare Collection (H Rosen & CC Tam) • TWG 8: Spatial Representation (Bibiana Kamler) • TWG 9: CPT & TCIP Framework (Polly Okunieff) • TWG 10: Signal Control & Prioritization (TBA)

  7. TCIP Task Force BUS & PARATRANSIT CEOs COMMITTEE TWG 2: PASSENGER INFORMATION TCIP OVERSIGHT PANEL PROGRAM MANAGER TCIP TASK FORCE TWG CHAIRS COMMITTEE TCIP CONTRACTORS TWG 4: SW TOOLS & TEST TWG 1: SCHEDULING/ RUNCUTTING TWG 3: INCIDENT MANAGEMENT TWG 5: ON-BOARD TWG 9: FRAMEWORK & PRIORITIZATION TWG 6: CONTROL CENTER TWG 7: FARE COLLECTION TWG 8 SPATIAL REPRSENTATION TWG 10: SIGNAL CONTR & PRIORITIZATION

  8. Task Force Co-Chair Responsibilities • Coordinate, in conjunction with APTA, the overall TWG review activities of the TCIP 2.4 standard • Members of the Chair Coordinating Forum (CCF) • Disposition of major and trans-TWG review comments / changes to the standard • Provide overall direction of TSC technical assistance effort • Point of Contact for TWG chairs • Support ongoing TCIP Strategic Planning activities

  9. TWG Chair Responsibilities • Coordinate review activities within their TWG • Encourage participation of all group members • Direct TSC technical assistance within their TWG • Act as the primary point of contact between their TWG and the APTA technical team • Review ongoing TCIP Strategic Planning activities

  10. TWG Member Responsibilities • Review and comment on applicable areas of the TCIP 2.4 standard • Work with APTA technical team on resolution of review comments • Primary Technical Review Focus: • Concept of Operations: do the functional requirements embodied in the Concept of Operations sufficiently address the operational needs of a transit agency? • Dialogs: will the dialogs successfully implement the functions outlined in the Concept of Operations?

  11. TSC Technical Assistance • TSC will be providing technical consultants to support each TWG • TSC TA’s may receive additional tasking direction from the CCF • Responsibilities: • Facilitate discussion within the TWG • Read narrative section of TCIP 2.4 document • Sections 1 thru 9 (pages 1-88) • Review and comment on applicable Narrative sections • Review and comment on applicable Annex sections • Dialogs • Data messages, frames, and elements

  12. TCIP Status & Review Plans John Fayos Critical Link

  13. Current Status of TCIP • TCIP 2.4 released on Nov 1 • Includes: • TCIP 1 Data Elements and Messages (now called Data Frames) • Concepts of Operation • Dialogs • Includes all business areas except Spatial Representation • Scheduling • Passenger Information • Incident Management • Onboard • Control Center • Signal Priority • Fare Collection • Common Objects

  14. TWG Review Process Phase 1: Initial Document Production NTP Authorization TCIP Oversight Panel Authorization Contractor Resolve Comments and Revise Draft Distribute Draft Standards to TWGs TWGs Review, Comments, & Recommenda-tions Contractors Develop Draft Standards (v2.4) Phase 2: Intermediate Review and Approval Task Force Approval For Public Posting (v2.6) TWGs Review and Approval Contractor Resolve Comments and Revise Draft TWGs Review and Comment Corrected Draft/Spatial Business Area to TWGs (v2.5) Phase 3: Public Review & Comment Phase 4: Final Review and Approval Distribute Final Draft Standard to TWGs Contractor Incorporate Modifications TWGs Final Draft Balloting (v2.7) NTCIP Joint Committee / Public Review & Comment Resolve Comments and Prepare Final Draft Release Authorization TCIP Oversight Panel Approval for Release Release Standards (v3.0)

  15. TCIP 2.4 Review Schedule • Passenger Information TWG Kickoff Meeting • Dec 8, 1:00-2:30 PM EST • TWG Review Meetings • Group meetings to discuss initial review progress • Jan 21-23, 2004 in Annapolis, Maryland • TCIP 2.4 review cycle complete • Feb 29, 2004

  16. Overall Review Schedule • TCIP 2.4 • Review cycle complete by end of February • TCIP 2.5 • Includes Spatial Representation business area • Incorporates TCIP 2.4 review comments • Release in April, 2004 • TWG Review complete in May, 2004 • TCIP 2.6 • Public review version • Release in June, 2004 • TCIP 2.7 • Incorporates public review cycle comments • Final version prior to balloting • TCIP 3.0 • Balloted release version of TCIP

  17. Other TWG Activities • Software Tools & Test TWG • TCIP Support Tool Requirements Specifications • RFP Specification Tool • Example TCIP “mini-applications” • Conformance tools • TCIP Simulator • TCIP Framework TWG • Includes Common Objects (CPT) business area • Coordination with other standards efforts • Possible future additional TWG’s (beyond TCIP 3.0) • Safety & Security TWG • Decision Support TWG • Procurement Support TWG • Strategic Planning • TCIP Task Force Co-Chairs and TWG Chairs

  18. TCIP 2.x Rob Ayers ARINC

  19. Discussion Topics • What TCIP 2.x contains • Incorporates TCIP 1 • Addition of Data Frames • Concept of Operations • Dialogs • XML

  20. Building the New Standard TCIP 2.X Dialogs Dialog Patterns Messages Data Frames New Frames TCIP 1 Msgs Data Elements New Elements TCIP 1 Elements

  21. New TCIP Standard • TCIP 3.0 • Plan to publish a new TCIP standard that incorporates the prior work, as well as XML Schema, and Dialogs • Single Standard instead of 9 documents

  22. TCIP 2.X Standard Outline • Overview • Definitions • Conformance • Understanding TCIP • Concept of Operations (For each Business Area) • Dialogs (Meaning of Patterns, Instantiations, Batch) • Dialog Patterns (Patterns are specified here)

  23. TCIP 2.X Standard Outline (continued) • Annex A-Data Elements(By Business Area) • Annex B-Data Frames (By Business Area) • Annex C-Messages (By Business Area) • Annex D-Dialogs (By Business Area) • Annex E-XML Schema • Annex F-Sample RFP Wording • Annex G-Traceability Matrix

  24. What is a Dialog? • A dialog specifies how and when a group of messages are used. • Dialogs are based on patterns. A pattern specifies a particular type of transaction which can then be used to implement many dialogs. • Patterns and Dialogs provide the context information necessary to effectively use TCIP messages.

  25. Pattern Example - Query Client Client Server Server AaaXxxSub AaaXxxSub Calculation Calculation AaaXxx CptSubErrorNotice Complete Complete Complete Complete Normal Execution of Query Error Response to Query

  26. Pattern Example-Periodic Client Server AaaXxxSub Calculation AaaXxx Timeout AaaXxx Timeout AaaXxx Timeout AaaXxx Subscription Expires Complete Complete Normal Execution

  27. Dialog Components • Name • Pattern • Business Area • Purpose • Narrative • Sequence Diagram • Assumptions • Notes • Message Identification

  28. eXtended Markup Language (XML) • TCIP I Standards are written in ASN.1 • TCIP 2.X uses XML as the implementation language, & include XML Schemas with the new Standards. • Advantages: Better known, more tools, more rapid supplier acceptance, take advantage of ubiquity of web-based products

  29. Data Element Example NameCPT-SubscriptionType Identifiercptdd 100 PurposeProvide the type of a requested subscription. The types allow the subscriber to ask for a one-shot provision of the information (query), a periodic update of the information, an update whenever the information changes (event), or cancellation of an existing subscription, or all existing subscriptions. Usage DefinitionENUMERATED { Query (1), Periodic (2), Event (3), Cancel (99), CancelAll (100), -- 4-98 reserved -- 101-255 reserved } (0..255)

  30. Data Element XML Schema XML-TAGCPT-SubscriptionType XML-SCHEMA <xsd:simpleType name="CPT-SubscriptionType" > <xsd:annotation> <xsd:appinfo> Query (1) Periodic (2) Event (3) Cancel (99) CancelAll (100) -- 4-98 reserved -- 101-255 reserved </xsd:appinfo> <xsd:documentation> </xsd:documentation> </xsd:annotation> <xsd:union> <xsd:simpleType> <xsd:restriction base="xsd:unsignedInt"> <xsd:minInclusive value="0"/> <xsd:maxInclusive value="255"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xs:enumeration value="Query"/> <xs:enumeration value="Periodic"/> <xs:enumeration value="Event"/> <xs:enumeration value="Cancel"/> <xs:enumeration value="CancelAll"/> </xsd:restriction> </xsd:simpleType > </xsd:union> </xsd:simpleType>

  31. Data Frame Example NameCptSubscriptionHeader Identifiercpt 1000 PurposeProvide a standardized header structure for subscription requests, cancellations, and responses. UsageThe expiration date and time must be specified. Report Interval is required if the requestedType is periodic, and not allowed otherwise. When the header is included in a subscription request, the information reflects the parameters desired by the subscriber. When the header is included in a response to a subscription request, the information reflects the parameters of the subscription actually provided. Subscriber and host identifiers are agency-assigned unique numbers to identify systems/applications. Request Identifier is a unique identifier that provided by the subscriber. The number is carried forward from the original request to all responses to the request by the server, and any cancellations must carry the same subscription number as the original request. DefinitionSEQUENCE { requestedType CPT-SubscriptionType, expirationDate CPT-DeactivationDate, expirationTime CPT-DeactivationTime, reportInterval CPT-TimeInterval OPTIONAL, requestIdentifier CPT-RequestIdentifier, subscriberIdentifier CPT-ApplicationID, hostIdentifier CPT-ApplicationID }

  32. Data Frame Example XML XML-TAGCptSubscriptionHeader XML-SCHEMA <xsd:complexType name="CptSubscriptionHeader" > <xsd:annotation> <xsd:documentation> </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="requestedType" type="CPT-SubscriptionType" > </xsd:element> <xsd:element name="expirationDate" type="CPT-DeactivationDate" > </xsd:element> <xsd:element name="expirationTime" type="CPT-DeactivationTime" > </xsd:element> <xsd:element name="reportInterval" type="CPT-TimeInterval"minOccurs="0"> </xsd:element> <xsd:element name="requestIdentifier" type="CPT-RequestIdentifier" > </xsd:element> <xsd:element name="subscriberIdentifier" type="CPT-ApplicationID" > </xsd:element> <xsd:element name="hostIdentifier" type="CPT-ApplicationID" > </xsd:element> </xsd:sequence> </xsd:complexType>

  33. Message Example NameCptStoppointListSub Identifiercpt 2001 PurposeRequest a specified version of stoppoint information UsageSubscription type should be query. If the information changes, then a new version number should be created by the scheduling system or schedule repository (server). The subscriber can become aware of such updates using the Subscribe Master Schedule Version dialog. The subscriber is able to determine the appropriate version of the stoppoints to request using the Subscribe Master Schedule Version dialog, thus the query does not need to be qualified with dates or other information. The include-details field indicates whether the response message should include additional details in the response message. These details provide optional information about a stoppoint (such as whether it is ADA-accessible). This detail is not required for all applications using the stop point list. An agency may decide to include all stoppoints for the agency within a stop point version, or to limit aversion to the stoppoints included on a route or group of routes, however all stoppoints referenced in a pattern list (SchPatternList message) must be included in the version of the stoppoints referenced by that pattern list. DefinitionSEQUENCE { subscriptionInfo CptSubscriptionHeader, stoppointVersion CPT-StoppointVersion, include-details CPT-Boolean }

  34. Message XML Schema XML-TAGCptStoppointListSub XML-SCHEMA<xsd:complexType name="CptStoppointListSub" > <xsd:annotation> <xsd:documentation> </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="subscriptionInfo" type="CptSubscriptionHeader" > </xsd:element> <xsd:element name="stoppointVersion" type="CPT-StoppointVersion" > </xsd:element> <xsd:element name="include-details" type="CPT-Boolean" > </xsd:element> </xsd:sequence> </xsd:complexType>

  35. Populated Message Example =================== ====XML Message =================== <SCH-MasterScheduleVersionSub> <subscriptionInfo> <requestedType>1</requestedType> <expirationDate>20091225</expirationDate> <expirationTime>0</expirationTime> <requestIdentifier>88</requestIdentifier> </subscriptionInfo> <beginDate>20020121</beginDate> <endDate>20020121</endDate> <routes> <SCH-RouteID>1</SCH-RouteID> <SCH-RouteID>5</SCH-RouteID> </routes> </SCH-MasterScheduleVersionSub>

  36. TCIP 2.X Standard Summary • Concept of Operations • each business area • Traceability • Incorporates TCIP 1 data elements and messages • Addition of dialogs • Conformance Strategy • TCIP usage in RFP’s

  37. TCIP PI Rob Ayers ARINC

  38. What PI Contains • 5.4 Passenger Information • 5.4.1 Locating Transit Service • 5.4.2 Determining the Status of Transit Service • 5.4.2.1 Status of Service • 5.4.2.2 Service Bulletins • 5.4.2.3 Stop Point ETAs (omitted) • 5.4.3 Parking Availability • 5.4.4 Transit Itineraries and Maps • 5.4.5 Text Timetables • 5.4.6 Passenger Information Displays (PID) • 5.4.7 Printed Mailings • 5.4.8 Locating Landmarks

  39. Passenger Information Displays 5.4.6.1 PID Capability Groups 5.4.6.2 Schedule Capabilities 5.4.6.3 PID Text Capabilities 5.4.6.4 PID Audio Capabilities 5.4.6.5 PID Graphics Capabilities 5.4.6.6 PID Animation Capabilities 5.4.6.7 PID Video 5.4.6.8 PID Logging 5.4.6.9 PID Health

  40. PI Dialogs

  41. PID Dialogs

  42. PI Questions

  43. TCIP Website Diane O’Neill ARINC

  44. TCIP Web Site • URL: • http://www.arincxchange.com/exchange/login.cfm • Web site is central distribution center for program information • Web site is account controlled • General public access is provided under APTA Guest accounts • Participant Account Information • User ID: your name as it appears on the Task Force or Technical Working Group Participant Lists • Password: initial password is the same as the user ID.

  45. Web Site Content • Content • The TF and each TWG has an area on the site to post information • General Program Information • New Member area • Historical Information • Documents in Review • Documents in Review • Current documents under review • Guidelines for TWG comments and comment form

  46. Document Configuration Management • Document Configuration Management • Comments are documented on standard forms • Comment forms are the basis of tracking what and why changes were made • Comments are logged into APTA system • Resolution of comments are proposed • TWG approves proposed resolution • Changes are incorporated in subsequent releases of the standard

More Related