FAX TRANSMITTAL

IEEE Rail Transit Vehicle Interface Standards Committee

MEETING OF WORKING GROUP #2

COMMUNICATION BASED TRAIN CONTROL

Date: December 10, 2001 - 9:00 am

Place: TRB Headquarters, Washington, DC

Attendees:

Name	Representing	Email
Ramesh Dhingra	VTA	Ramesh.Dhingra@vta.org
Jeff Eilenberg	US&S	jeeilenberg@switch.com
Harvey Glickensstein	PB Transit & Rail Systems Inc.	h.glickenstein@ieee.org
Geoff Hubbs	NYCT	gehubbs2@nyct.com
John LaForce	SEPTA	jlaforce@septa.org
Dave Male	Systra Engineering	Dmale@systrausa.com
Bob Miller	BART	Rmille1@bart.org
Tom McGean	TJMPE	t.j.mcgean@ieee.org
Ed Mortlock	Parsons Transportation Group	Edwin.Mortlock@parsons.com
Bill Petit	Safetran	Bill.Petit@ieee.com
Venkat Pindiprolu	FTA	Venkat.pindiprolu@fta.dot.gov
Alan Rumsey	Parsons Transportation Group	Alan.Rumsey@parsons.com
John Vogler	NJ Transit	jvogler@njtransit.com
Naor Wallach	Alstom	Naor.Wallach@transport.alstom.com
Firth Witwam	Alcatel	Firth.Whitwam@tas.alcatel.ca

Minutes of Meeting:

1. HOUSEKEEPING ITEMS

1.1. Introductions

Alan Rumsey thanked Chris Jenks and the TRB for hosting this meeting of Working Group #2 (WG2) of the Rail Transit Vehicle Interface Standards Committee (RTVISC).

Chris Jenks distributed a Research Results Digest, Number 44, dated November 2001 prepared by the Transit Cooperative Research Program (TCRP). This digest had been written by Tom McGean and was entitled: “Consensus Standards for the Rail Transit Industry”.

Chris Jenks and Tom McGean explained that for the past five years, the IEEE rail transit standards effort, including the work of WG2, has been supported by the Transit Cooperative Research Program as an experiment to see if a consensus based rail transit standards program could be established. Based on the success of this effort, the APTA Rail Transit Standards Policy and Planning Steering Committee, meeting at the APTA annual Rail Transit Conference in Boston this past June, committed to joint FTA/transit industry funding which will permit the project to move from its research status to an ongoing standards activity within the overall APTA industry standards initiatives. The transition will occur effective March 1, 2002. Although the funding source will be new, the program will continue essentially unchanged with the standards activities themselves remaining under IEEE and ASME auspices.

1.2. Review of Previous WG2 Meeting Minutes

The minutes of the previous WG2 meeting held on September 25, 2001 were reviewed and accepted as written, with the note that the correct email address for Carl Schwellnus should be Carl.Schwellnus@tas.alcatel.ca.

1.3. Liaison with IEC TC9 "Urban Guided Transport Management and Command/ Control Systems" project (UGTMS)

Working Group 40 of the IEC TC9 Railway Committee intends to develop standards for Urban Guided Transport Management and Command/Control Systems.

Alan Rumsey will be attending the first working group meetings on this proposed new standard in Paris on January 30/31, 2002. At this meeting he will provide a status report on the work of IEEE WG2 and the CBTC standard IEEE 1474.1. The draft agenda for this initial WG40 meeting is included as Attachment A for information.

Naor Wallach also briefed the working group on his understanding of the UGTMS program.

1.4. Date/Location of Next WG2 Meeting

The next WG2 meeting was scheduled for Tuesday/Wednesday, February 26/27, 2002 at New York City Transit’s offices in New York, NY. The first day of this meeting will focus on proposed updates to the existing IEEE Std. 1474.1-1999. The second day of this meeting will be a line-by-line review of the draft standard 1474.2.

A CBTC Peer Group meeting was also scheduled for Monday, February 25, also at New York City Transit. The CBTC Peer Group meetings are open to transit agency representatives only, and all transit agencies with an interest in CBTC technology are encouraged to attend.

2. UPDATES TO IEEE STD. 1474.1 “CBTC PERFORMANCE AND FUNCTIONAL REQUIREMENTS”

2.1. Project Authorization Request (PAR)

A PAR will need to be raised once agreement has been reached on the proposed scope of the updates to 1474.1.

2.2. Driverless Operations and Compatibility with ASCE APM standards

Tom McGean presented a draft proposal for expanding the IEEE Rail Transit Vehicle Interface Standards Committee Working Group #2 with additional members drawn from the Automated People Mover community to develop an overall train control performance standard (see Attachment B).

This proposal was discussed at length by WG2 with approximately 50% of the meeting participants favoring the development of a single integrated standard, and approximately 50% favoring separate (but coordinated) IEEE and ASCE standard developments.

In general, the supplier representatives favored a single unified standard, in particular for CBTC technology. The agency representatives, while supporting a desire to move to a single standard, were not convinced that there was a need for performance standards for non-CBTC technology, and suggested that WG2 continue to limit its activities to CBTC technology only.

The WG2 participants agreed that there was a need for harmonious standards, and that there should be continued liaison between the IEEE and ASCE working groups. Based on the meeting discussions, therefore, an alternative draft proposal was developed for expanding the IEEE RTVISC WG#2 with additional members drawn from the Automated People Mover community to develop a revised CBTC performance and functional requirements standard that is applicable to driverless/APM applications.

The primary advantage of this alternative proposal is that suppliers of CBTC systems would only need to refer to a single standard (the revised IEEE 1474.1 standard), and could develop a standard CBTC product, or range of CBTC products applicable to commuter rail, heavy rail, light rail and APM applications, including both driverless operations and operations with drivers.

This alternative proposal is included in Attachment C. The WG2 meeting participants, with the exception of Tom McGean who deferred offering an opinion pending further discussion with the ASCE APM committee, unanimously supported this alternative proposal.

If this alternative proposal is acceptable to the ASCE APM committee and the full RTVISC, the PAR referenced in 2.1 above will be developed accordingly.

2.3. Expanded Grade Crossing Functional Requirements for CBTC Systems

It was agreed that the proposed update to 1474.1 should also include expanded grade crossing functional requirements for CBTC Systems.

2.4. Other Updates

In the proposed update to 1474.1, it was suggested that consideration be given to developing performance and functional requirements related to security aspects of CBTC technology (e.g. protection against “hacking”).

3. REVIEW OF DRAFT D6.0 OF PROPOSED STANDARD 1474.2

Draft 6.0 of the proposed Standard had been distributed on November 19, 2001 and reflected comments and agreed changes on the previous draft.

WG2 completed a general review of draft 6.0, prior to a detailed line-by-line review that will be scheduled at the next WG2 meeting. The following comments were noted:

3.1. Introduction

The Introduction section (which does not form part of the standard) will be completed in draft 7.0 (Action: Alan Rumsey).

3.2. Section 1: Overview

No changes identified in Section 1.

3.3. Section 2: References

The sentence related to applicability of revisions to referenced standards will be deleted or modified.

Version F of MIL-STD 1472 had been reviewed by Dave Male, Geoff Hubbs and Alan Rumsey since the last WG2 meeting to ensure the referenced sections and subsections were applicable to 1474.2. An independent review will also be conducted prior to the next meeting. (Action: Jeff Eilenberg).

3.4. Section 3: Abbreviations, Acronyms and Definitions

Consideration will be given the including additional definitions such as: “CBTC user”, “Overspeed condition”, “Soft key” and “Line replaceable unit”.

3.5. Section 4: General User Interface Requirements

In section 4.2, the definition of “CBTC user” will be moved to section 3. The discussion on user profiles will also be expanded to recognize that different user profiles may be required for train operators and control center operational staff.

In section 4.4, it will be clarified that hazard analyses are “required” not “anticipated”.

In section 4.5, the statement that “white” is typically used to display established routes on track diagrams will be deleted.

3.6. Section 5: CBTC Trainborne User Interface Requirements

In section 5.2, the issue of “overspeed alarm conditions” will be clarified. It was the consensus of the WG that warning of a potential penalty brake condition should be a mandatory alarm, while an alarm of an actual penalty brake application should be optional. Consideration will be given to including a definition of “overspeed condition” in section 3.

In section 5.2.3, the phrase “ATP related” will be deleted.

CBTC user login parameters will be added to section 5.2.4.

A new section 5.2.6 will be added for optional audible alarms.

In section 5.3.1, consideration will be given to deleting explicit reference to ANSI/HFS 100-1988.

3.7. Section 6: CBTC ATS User Interface Requirements

The phrase “in an emergency” will be deleted from the last paragraph in section 6.1.

The ability to display status of AWS elements will be added to section 6.2.1

In section 6.2.1 c), “current traffic direction” will be changed to “currently authorized travel direction”.

In section 6.2.1 f), reference to train operator errors will be deleted.

Section 6.2.2 will be reviewed for completeness.

Section 6.3.2 will be reviewed to ensure that control action confirmation function is clearly defined.

User help facilities, section (section 6.3.4), still to be completed.

3.8. Section 7: CBTC Maintenance-Related User Interface Requirements

Section 7.1 will be revised to include both local and remote diagnostic capabilities, to clarify that scope of this section is limited to first-level maintenance only, and that the failure types listed are intended to be examples only.

With respect to currently available CBTC systems, suppliers were encouraged to provide specific details of maintenance-related display data and user inputs supported. (Action: Suppliers).

4.0 SUMMARY

The WG2 Chair, in draft 7.0 of the proposed standard, will address all comments raised by the meeting participants. (ACTION: Alan Rumsey). Any additional comments/inputs should be provided to the WG2 Chair no later than January 31, 2002. (Action: All).

Minutes prepared by:

Dr. Alan F. Rumsey

WG2 Chair

DRAFT PROPOSAL FOR EXPANDING THE IEEE RAIL TRANSIT VEHICLE INTERFACE STANDARDS COMMITTEE WORKING GROUP 2 WITH ADDITIONAL MEMBERS DRAWN FROM THE AUTOMATED PEOPLE MOVER COMMUNITY TO DEVELOP AN OVERALL TRAIN CONTROL PERFORMANCE STANDARD

Introduction:

At present the only internationally used standard related to driverless automatic train operation is ASCE 21-96, Automated People Mover Standard. In addition, IEEE 1474.1, IEEE Standard Method for Communications Based Train Control (CBTC) Performance and Functional Requirements, provides standards for CBTC systems with operators.

However, there are a number of Train Control standards efforts underway requiring coordination including 1)Plans for IEEE 1474 to extend its Communication Based Train Control Performance Standard to cover driverless systems 2) The IEC WG39 work on Railway Applications - Urban Automated Guided Transit, and 3) Proposed IEC WG40 work on Urban Guided Transit Train Control Standards.

The purpose of this draft proposal is to provide the basis for cooperation between current individual members of the IEEE Rail Transit Vehicle Interface Standards Committee's WG2 and the ASCE Automated People Mover Standards Committee in harmonized development of train control standards. This proposal does not involve any joint action between the IEEE and ASCE as corporate or professional organizations.

Approach

At present, it is planned to update and revise both the IEEE and ASCE standards in essentially the same time frame. It is proposed that instead, a single Train Control Performance Standard be developed under the auspices of an expanded IEEE RTVISC WG2. A four part train control standard is envisioned. The Parts would be as follows: Part 1 General Train Control Requirements; Part 2 Special Requirements for Driverless Systems; Part 3 Special Requirements for Automated People Movers; and Part 4 Special Requirements for CBTC Technologies.

It is further proposed that current members of the ASCE Automated People Mover Standards Committee be permitted to participate in the IEEE RTVISC WG2 and that the balloting group for the new IEEE standard be composed of a balanced group drawn from WG2, the parent RTVISC and the ASCE APM Standards Committee, to equitably represent all interests.

Development of Parts 1 and 2 of the new standard would be jointly undertaken by the expanded full working group acting together (chair of expanded working group TBD); Part 3 would be solely developed by WG2's new APM members under Charles Martin, and Part 4 solely developed by the original WG2 members under Alan Rumsey.

It is intended that at the end of the day there would be a single IEEE Train Control standard applicable to all train control technologies and all rapid transit and APM applications. When the ASCE reaffirms Part 1 of its ASCE standard it will cite the IEEE standard's applicable portions. If necessary to dovetail with release of the IEEE standard, ASCE could temporarily reaffirm its current Part 1 as is, and then do the reaffirmation when the new IEEE standard is available. Further, if necessary to obtain consensus within the ASCE APM Standards Committee, that group would reserve the right to take certain specific exceptions to the IEEE standard.

Coordinated Meetings

To facilitate this cooperative effort, it is proposed that IEEE RTVISC WG2 meetings will be held in conjunction with ASCE APM Standards Committee meetings to the maximum extent practical.

Make-up of New WG2 and Balloting Group

The new WG2 would be open to all interested parties as is the case at present. However,
it is expected that a number of ASCE APM Standards Committee members would join the RTVISC working group.

Invitation to join the balloting group would be extended to 1)RTVISC WG2 members 2) APM Standards Committee Members and 3)RTVISC members. In the event the balloting group becomes unbalanced or unwieldy, decisions on the balloting group will be jointly made by Tom McGean and the chair of the expanded working group subject to review and appeal to the ASCE APM Standards Committee full membership and the IEEE RTVISC full membership.

Name

Representing

1. Opening of the meeting

2. Roll call of the delegates

3. Approval of the agenda

4. Resolution of the 41^st meeting of IEC/TC9 in Florence

5. IEC or national standards existing or in progress on related subjects

6. Presentation of the scope of WG39 "Automated Urban Guideway Transit - Safety Requirements" (Anselme COTE)

7. Presentation of CBTC standard IEEE 1474 (Alan F. RUMSEY)

8. Presentation of the ERTMS/ETCS (European Rail Traffic Management System/European Train Control System) standard (André KROL)

9. Presentation of the UGTMS project (Jean-Paul RICHARD)

10. Discussion of the NCs' comments and response of the WG40 (see document 9/632/RVN Result of Voting, as completed with the proposals of the WG40 convenor)

11. Scope of work of the WG40 standard

12. Date and place of the next meeting