IEEE Rail Transit Vehicle Interface Standards Committee

 

MEETING OF WORKING GROUP #2

COMMUNICATION BASED TRAIN CONTROL

 

Date:            November 2, 2000 - 9:00 am

 

Place: GE Harris Harmon Corporate Headquarters, Blue Springs, Missouri

 

Attendees:

 

Name

Representing

Email

Fred Childs

PATH

fchilds@panynj.gov

Nicholas Estivals

RATP

nicolas.estivals@ratp.fr

Victor Grappone

LIRR

vfgrapp@lirr.org

Seyed Hosseini

Metro North

hosseini@mnr.org

John LaForce

SEPTA

jlaforce@septa.org

Martin Lukes

WMATA

mlukes@wmata.com

Bob MacDonald

T.K. Dyer

RmacDonald@HNTB.com

Rob McHugh

SkyTrain

rob_mchigh@bcrtc.bc.ca

Bob Miller

BART

rmille1@bart.gov

Bill Petit

Safetran

bill.petit@ieee.org

Alan Rumsey

Parsons Transportation Group

alan.rumsey@parsons.com

Lou Sanders

APTA

lsanders@apta.com

Carl Schwellnus

Alcatel

cschwell@torsel.alcatel.com

Jeffrey Smith

GE Harris Harmon

jpsmith@harmonind.com

John Vogler

NJT

jvogler@njtransit.com

Naor Wallach

Alstom Signaling

naor.wallach@transport.alstom.com

Robert Walsh

Adtranz

robert.e.walsh@us.adtranz.com

 

 

Minutes of Meeting:

 

1.0  HOUSEKEEPING ITEMS

 

1.1  Introductions

 

Alan Rumsey thanked Bob Anderson and GE Harris Harmon for hosting this meeting of Working Group #2 (WG2) of the Rail Transit Vehicle Interface Standards Committee (RTVISC).

 

1.2  Review of Previous WG2 Meeting Minutes

 

The minutes of the previous WG2 meeting held on July 27, 2000 were reviewed and accepted as written.

 


1.3  Status of Other CBTC-Related Standards Initiatives

 

1.3.1  Environmental Standards for CBTC Wayside Equipment

 

Harold Gillen will be chairing a new Working Group to develop environmental standards for wayside electronic equipment, including wayside CBTC equipment.

 

Draft Scope and Purpose for this proposed standard has been prepared. 

 

Anyone interested in participating in this Working Group should contact Harold directly.

 

1.3.2  Future Updates to 1474.1

 

The existing IEEE Std. 1474.1-1999 will be updated in the future to include an expansion of the functional requirements in paragraph 6.1.15: "Highway grade crossing warning". This update will be undertaken by a subgroup of WG2, chaired by Vic Grappone.

 

Proposed updates to paragraph 6.1.15 were distributed at the last WG2 meeting. Meeting participants were again encouraged to review and provide comments to Alan Rumsey and Vic Grappone.  (ACTION: All)

 

The existing IEEE Std. 1474.1-1999 will also be updated in the future to include CBTC performance and functional requirements for train operations without crews.  WG2 members who are interested in this topic were invited to identify those sections of the existing IEEE Std. 1474.1-1999 that would need to be updated to support train operations without crews, and provide inputs to the WG2 Chair.  (ACTION: All)

 

1.4  Date/Location of Next WG2 Meeting

 

The next WG2 meeting was tentatively scheduled for Thursday, February 22, 2001 at APTA’s new headquarters in Washington, DC.  Lou Sanders to confirm availability of conference room.  (ACTION)

 

2.0  REVIEW OF DRAFT D2.0 OF PROPOSED STANDARD 1474.2

 

2.1  General

 

Draft 2.0 of the proposed Standard was distributed on October 5, 2000 and reflected comments/agreed changes on the previous draft. 

 

The meeting participants approved the new organizational structure of the proposed Standard.

 

Written comments on draft D2.0 had been received from Dave Male prior to the meeting and were reviewed with the meeting participants during the course of the meeting.

 

As agreed at the previous WG2 meeting, the objective of this meeting was to focus primarily on the trainborne CBTC user interfaces, with detailed discussions on the central and maintenance CBTC user interfaces deferred to future WG2 meetings.

 

2.2  Review of Section 4 (General User Interface Requirements)

 

Section 4 of the proposed Standard was reviewed in detail.  Specific agreements/ comments were as noted below:

 

·        the first paragraph of section 4.1 will be moved into the “Introduction” section to the standard

 

·        the second paragraph will remain in a renamed section 4.1 “Categorization of CBTC systems” with a note added that the specific CBTC configuration will impact the user interface details

 

·        the third (final) paragraph will be moved into a new section (4.2) “Range of applications”

 

·        current section 4.2  will be re-written to reflect intent of the standard, rather than subjective requirements that cannot be measured

 

·        section 4.2.1/2 will be re-written to define parameters that must be specified by the authority having jurisdiction, and to remove reference to “the general population”

 

·        section 4.3 will be updated to note that authority having jurisdiction may define alternative colors, for compatibility with existing non-CBTC systems; it was also proposed to reduce number of shades of gray from four to two;  Lou Sanders undertook to review potential applicability of ATCS standards to this section (ACTION); a note will also be added to this section that displays shall not be used to perform “vital” functions

 

·        note will be added to section 4.4 that ambient noise sensors may be utilized; central example to be added for “operational or malfunction noises”

 

·        editorial changes will be incorporated to sections 4.5 and 4.6; reference to four distinct audible alarms will be moved to section 4.4

 

2.3  Review of Section 5 (Trainborne CBTC User Interface Requirements)

 

Section 5 of the proposed Standard was reviewed in detail. 

 

It was agreed to restructure the information contained in this section into mandatory ATP data and optional ATO/ATS data.  The proposed Standard will also reflect the fact that the information displayed will be dependent on the train operating mode (e.g. certain display information may be suppressed in ATO mode).

 

It was agreed that mandatory data should include:

 

·        train operating mode

·        current train speed

·        current maximum authorized CBCT speed (i.e. speed that will trigger an automatic brake application if exceeded)

·        an approaching movement authority limit (zero speed target)

·        an approaching speed reduction (permanent or temporary)

·        an approaching work zone

·        distance to an approaching movement authority limit, speed reduction or work zone

·        overspeed alarm

 

Optional data should include:

 

·        territory-related data (such as location of stations, interlockings, highway grade crossings, etc.)

·        train location

·        train identity

·        reason for movement authority limit (e.g. train ahead)

·        speed profile to an approaching movement authority limit, speed reduction or work zone

·        required brake rate to an approaching movement authority limit, speed reduction or work zone

·        “time to penalty” when approaching a movement authority limit, speed reduction or work zone

·        route through interlocking

·        train regulation information

·        information related to unscheduled train stops between stations

·        station management related information (including indication of on which side of the train door opening is authorized)

·        grade crossing related information

 

A new section will be added for user information inputs (e.g. mode selection and ATO Start inputs).

 

The WG2 participants agreed that sections 5.3 and 6.3 (user interface presentation requirements) should remain separate for trainborne and central user interfaces as the presentation requirements were considered significantly different for the two locations.

 

Seyed Hosseini agreed to prepare an initial draft for section 5.3.1, display layout (ACTION).

 

2.4  Review of Section 6 (Central CBTC User Interface Requirements)

 

Section 6 of the proposed Standard was briefly reviewed in the limited time available and a number of updates were identified for inclusion in the next draft.

 

2.5  Review of Section 7 (Maintenance-Related User Interface Requirements)

 

It was agreed that data logging, archival and retrieval would be addressed in this section.

 

2.6  Summary

 

All comments raised by the meeting participants will be addressed by the WG2 Chair in draft 3.0  (ACTION: Alan Rumsey).

 

Any additional comments on draft 2.0, together with suggested wording changes/additions, are to be forwarded to the WG Chair no later than the end of November 2000. (ACTION: All)

 

The WG Chair will incorporate all additional comments received, and issue draft 3.0 of the proposed standard in January 2001.  (ACTION: Alan Rumsey).

 

3.0  EXAMPLES OF CBTC CENTRAL GRAPHICAL USER INTERFACE

 

3.1  Presentation by RATP

 

Nicholas Estivals (RATP) described the design approach adopted by RATP for the central control for the Meteor Line and gave examples of basic screen layouts.

 

3.2  Presentation by Alcatel

 

Carl Schwellnus (Alcatel) described the Alcatel SMC product for the automated central control of rail mass transit systems and gave examples of screen layouts.

 

4.0  ANY OTHER BUSINESS

 

Lou Sanders advised that TRB funding for RTVISC activities had been secured for an additional year, but this could be the last year that TRB would be able to fund the standards activities.  Other funding sources may need to be secured for the future.

 

 

Minutes prepared by:

 

Dr. Alan F. Rumsey

WG2 Chair