IEEE Rail Transit Vehicle Interface Standards Committee
WG9 STANDARD P1544
TRANSIT COMMUNICATIONS INTERFACE PROFILES FOR RAIL APPLICATIONS
Sixth Meeting, Apr. 30, 1999
MTA-NYC Transit
the conference/lecture room on the first floor
130 Livingston St., Brooklyn
Meeting called to order at 8:10 a.m.
Rob McHugh introduced himself and asked individuals their experience with MS Access; also their interest in transit systems beyond the vehicle. Introductions continued around the table with those questions in mind. A list of attendees is attached (Attachment 1).
Thanks to our gracious hosts Gene Sansone and Lorraine Brillante, Kenny and Debby for a great job with meeting arrangements, including arranging for refreshments, for meeting rooms and equipment, and for arranging a tour of the new NYCT simulator.
.
2.0 Agenda
The agenda was reviewed and accepted as attached (Attachment 2)
3.0 Database Format
The support and familiarity with Microsoft Access was adequate to continue to use it as the database program ( Office 97 or its predecessors ). Rob McHugh agreed to distribute the latest On-board database form to facilitate the entry of working groups’ data elements. Only data to and from the vehicle is a candidate for TCIP conversion. WG9 need only consider the non-SAE 1587 onboard variables of which there are about 64. It also needs to consider the non-Onboard TCIP variables which are relevant (Primarily the Common Data Elements and the Spatial Representation, but possibly also some business areas such as Passenger Information, Fare Collection etc.)
Paula Okunieff agreed to update the data entry application to make the Rosin/Lonworks translation easier; a copy of the latest Access database is attached.
4.0 P1544 Standard Document Structure
Wording for the scope and purpose was reviewed. The data dictionary will follow the guidelines of IEEE standard 1489; a pre-ballot copy is available on request. ROSIN will be used for the WG9 message sets. An attempt will be made to coordinate with LONMARK and TCN to have as much commonality as possible. The LonMark Interoperability Association will provide much of the support required for immediate applications; WG9 will build on this. The consensus of the group was that LonWorks is advanced enough to be self-supporting.
Tom Sullivan will check with IEEE about posting the P1489 version on the TSD website.
The website: http://www.tsd.org
is maintained by Tom Sullivan. Tom's site is directly linked to the IEEE site where draft standards are password protected. The user name and password for accessing draft standards are "transit" and "railway". Posted Email attachments may be in either Word 6.0/95 or Word 97.6.0 IEEE–SDO Co-ordination
Tom McGean updated the group on standards activities. The chair presented a block diagram showing how our work was related to numerous other transit standards activities, and also a sheet explaining the acronyms used on the chart.
The chart is preliminary and help is needed to properly relate all activities and identify those that may have been missed. Persons are asked to email the chair at
t.j.mcgean@ieee.org with corrections or additions so we can improve the chart.Coordination between the IEEE–RTVISC WG9 and the Transit Standards Consortium (ITE–TCIP) will be enhanced by The Consortium for Communications Protocol Implementation (CCPI). This Consortium proposal represents the critical missing element in a complex set of institutional activities which can assure full communications interoperability for rail based microprocessor systems. IEEE 1473 provides the communications protocol standard; IEEE P1544 provides the TCIP approved profiles to make sure that the information carried by the protocol is in a standard format; and the LonMark Interoperability Association assures internal compatibility of EIA 709 based elements . The Consortium proposal completes this multifaceted approach by providing a reference implementation of the IEC protocol and the critical gateway between the European developed IEC protocol and the EIA protocol widely used in the U.S. It offers the industry the advantages of both protocols; the train specific engineering designed into the IEC protocol, and the economies of the wide user base of the EIA protocol.
7.0 Data Object Modeling
The LonMark Interoperability Association has formed a new transportation group. Tom Sullivan serves as the interim chair. One of the group's tasks will be to help make the IEEE1473 L protocol standard a reality. The group met in New York on April 28th. Subsequent meetings are planned October 13-15 in Amsterdam. Contact Tom Sullivan at
tjs@pacbell.net for details. The LonMark website is www.lonmark.org.Alex Chervet of Echelon gave an excellent example of how to profile a data element so that it would be reusable between business entities. WG9 needs to consider how to use as many Common Public Transit Database data objects as possible. The
LonMark Interoperability Association will provide much of the support required for immediate applications; WG9 will build on this.Rob to obtain Alex’ PowerPoint presentation .
8.0 TCIP Overview and Report
The IEEE-RTVISC WG9 are to fill the rail object set placeholders. Eva Lerner- Lam noted that it is necessary to follow the ITS Database Registry and that if necessary, TCIP will change their data objects to correspond with NTCIPTCIP is compliant with IEEE 1489 ITS Data Dictionary and IEEE P1488 ITS Message Set Template, and that the IEEE ITS Database Registry requires both. Polly Okunieff confirmed that dData types not supported by TCIP can be represented by type reference and can be added to an ASN.1 compiler. ASN.1 does support floating point representation.
9.0 Next Meeting
It was proposed that the next meeting be held the week of June 7,1999 in Seattle.
Rob will contact King County Metro to arrange a venue and finalize a date; exact date and location will be posted on
http://www.tsd.org/(Action items are printed in italicized bold font.)
Prepared by:
R.E. McHugh, P.Eng.
Chair, WG9
Attachment 1:Participants List
Sixth Meeting, Apr. 30, 1999
MTA-NYC Transit
the conference/lecture room on the first floor
130 Livingston St., Brooklyn
Meeting message center contact person at NYCT is Laureen Brillante; phone number 718 694 4411
8:00 -8:10 AM
Introductions, Meeting Purpose
8:10-9:00 AM
Database format
Internet issues
Input from Working Groups
9:00 - 11:00 AM
P1544 Document structure review
Rosin Data Base review
LonWorks Rail Transit functional profiles
11:00 - Noon
Driver Simulator tour
Noon - 1:00 PM
Lunch
1:00 - 2:40 PM
Review of TCIP common data on-board objects
Identify Rail specific objects
TSC liaison; related standards & publications
TCIP Camp & Abstract Syntax Notation (ASN.1) seminars
2:40-3:30 PM
Review of Action Items
Meeting Time and Place, next meeting
Adjourn