Seventh Meeting, June. 8&9, 1999

KING County Metro

821 – 2^nd Avenue, Seattle WA.

Rob McHugh introduced himself and introductions continued around the table. A list of attendees is attached (Attachment 1).

Thanks to our host Ron Atherley for arranging the meeting room and equipment, and for arranging a tour of the King County Metro control center and the traffic priority demonstration .

The minutes of meeting six were reviewed with requested changes in section 8.0 from Polly Okunieff. The agenda was reviewed and accepted as attached (Attachment 2

Mike Barnett presented the consolidated Microsoft Access database program. Rob McHugh agreed to distribute this latest On-board database form to facilitate the entry of working groups’ data elements. Mike also included some Vending Equipment Variables for consideration. WG9 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.)

The opportunity to interact with Ron Atherley , the co-chair of the TSC priority signaling WG was appreciated. Ron informed the group of a communications protocol guide published by Network Associates showing ISO 7-layer breakdowns. The chart is available on request.

Coordination between the IEEE–RTVISC WG9 and the Transit Standards Consortium 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.

Damian Inglin of Echelon pointed out that highly packed information of infrequently changing data could best be represented by SCPTs (Standard Configuration Parameter Types). WG9 needs to consider how to use as many Common Public Transit Database data objects as possible

The IEEE-RTVISC WG9 are to fill the rail object set placeholders. Eva Lerner Lam noted TCIP is compliant with IEEE 1489 ITS Data Dictionary and IEEE P1488 ITS Message Set Template, and that the IEEE ITS Data Registry requires both. ASN.1 does support some ROSIN data types; however, Polly Okunieff confirmed that data types not supported by TCIP ASN.1, can be defined and represented by a type reference and thus supported at runtime by the ASN.1 compiler.

It was proposed that the next meeting be announced at a later date.

(Action items are printed in italicized bold font.)

R.E. McHugh, P.Eng.

Chair, WG9

Seventh Meeting, June. 8&9, 1999

KING County Metro

821 – 2^nd Avenue, Seattle WA.

Database format

Internet issues

Input from Working Groups

P1544 Document structure review

Rosin Data Base review

LonWorks Rail Transit functional profiles

tour

Lunch

Review of TCIP common data on-board objects

Identify Rail specific objects

TSC liaison; related standards & publications

Database Input

Meeting Time and Place, next meeting

Adjourn for the day

Assemble to go to train station

Amtrak to Vancouver to continue meeting and tour SkyTrain

Review of Action Items

Adjourn

Assemble to go to train station