IEEE RAIL TRANSIT VEHICLE INTERFACE STANDARDS COMMITTEE
WORKING GROUP 2
Communications Based Trains Control Performance/Functional Requirements
Minutes of Meeting
|
Date: |
December 1, 1998 |
|
Location: |
SEPTA, Philadelphia |
Attendees:
|
Name |
Company |
Phone |
Fax |
|
Bob Anderson |
Harmon |
(816) 650 6171 |
(816) 650 3570 |
|
Fred Childs |
PATH |
(201) 216 6648 |
(201) 216 6576 |
|
Jeff Eilenberg |
LSTS |
(609) 716 9790 |
(609) 716 9798 |
|
Ales Filip |
Czech Railways |
+420 405645122 |
|
|
Bill Gallagher |
Alcatel |
(416) 742 3900 |
(416) 742 9088 |
|
Sofia Georgiadis |
NYCT |
(212) 492 8208 |
(212) 492 8390 |
|
Harvey Glickenstein |
PB Transit & Rail Syst. |
(973) 565 4820 |
(973) 824 3140 |
|
Adrian Hellman |
Volpe Center |
(617) 494 2171 |
(617) 494 2318 |
|
Geoff Hubbs |
NYCT |
(212) 492 8495 |
(212) 492 8145 |
|
Ken Karg |
Adtranz |
(412) 655 5225 |
(412) 655 5108 |
|
John LaForce |
SEPTA |
(215) 580 8228 |
(215) 580 8282 |
|
John Lewis |
MBTA |
(617) 222 5540 |
(617) 222 3918 |
|
Martin Lukes |
WMATA |
(202) 962 1111 |
(202) 962 2437 |
|
Bob MacDonald |
Dyer |
(781) 862 2075 |
(781) 861 7766 |
|
Dave Male |
RTS |
(212) 986 9866 |
(212) 986 9855 |
|
Rob McHugh |
SkyTrain |
(604) 520 3641 |
(604) 520 3273 |
|
Ed Mortlock |
Booz Allen & Hamilton |
(703) 917 2959 |
(703) 902 3617 |
|
Lang Nguyen |
FRA/R&D |
(202) 493 6349 |
(202) 493 6111 |
|
Bill Petit |
Safetran |
(716) 349 2305 |
(716) 349 2306 |
|
Omar Rezzoug |
Matra |
(33) 149657898 |
(33) 149657279 |
|
Alan Rumsey |
PTG - De Leuw, Cather |
(212) 266 8527 |
(212) 266 8536 |
|
David Rutherford |
RSE |
(716) 292 1440 |
(716) 292 1446 |
|
Warren Sims |
LSTS |
(609) 716 9790 |
(609) 716 9798 |
|
Jeffrey Smith |
Harmon Industries |
(816) 650 3112 |
(816) 650 3570 |
|
John Vogler |
NJT |
(973) 491 8117 |
(973) 491 8479 |
|
Ken Vought |
RT&T Inc. |
(914) 271 5223 |
(914) 271 5247 |
|
Robert Walsh |
Adtranz |
(412) 655 5230 |
(412) 655 5108 |
1.0 HOUSEKEEPING ITEMS
1.1 Introductions
Alan Rumsey welcomed participants to this meeting of the IEEE Rail Transit Vehicle Interface Standards Committee (RTVISC) Working Group #2 (WG2), developing performance and functional requirements standards for Communications-Based Train Control (CBTC) systems. This meeting was hosted by SEPTA, and Alan Rumsey thanked John LaForce for all of the meeting arrangements.
John LaForce summarized the status of SEPTA’s plans to install an Adtranz-supplied CBTC system on 115 4-axle cars operating on 5 miles of track within SEPTA’s Light Rail tunnel. The CBTC system will support 60-70 cars per hour in peak periods, with 30+ cars normally operating in the tunnel during the peak. In the event of a delay, the number of cars in the tunnel could be much greater than 30 cars and hence the CBTC system needs to be able to handle bunching of cars, as well as multiple berthing of cars in the terminal station. The CBTC system will provide safe train separation assurance and continuous overspeed protection only, with no ATO or ATS functionality, except for a simple mimic display at the Control Center. There will be no track circuits, except at the one interlocking on the line. A 30 month implementation schedule is envisaged, with car equipment installation being on the critical path as no more than 2 cars per week can be taken out of service.
1.2 Overview of WG2 Status
Alan Rumsey provide a summary of WG2 status, and highlighted the key changes that had been introduced in the latest draft of the WG2 standard since the last WG2 meeting.
Alan Rumsey reiterated that is was the group’s target to be in a position to ballot the CBTC performance and functional requirements standard early in 1999, and as such it was important for the group to reach closure on the various open issues.
Alan Rumsey advised that the current WG2 mailing list consists of over 100 active members and friends. The current mailing list was circulated, reviewed and updated by the meeting participants.
1.3 WG2 Comments Database
Alan Rumsey advised that all written comments received on draft versions of the proposed CBTC standard were being entered into the WG2 Comments Database (with the exception of minor typographical comments). A printout of the database was tabled and reviewed by the meeting participants. The printout identified all comments that had been open at the last meeting as well as new comments that had been added to the database since the last meeting. (Comments that had been closed prior to the last meeting have been archived, and were not included in the current printout. All comments are being retained, however, to provide an historical record of the workings of the group).
In summary, Alan Rumsey advised that 332 written comments had been received to date of which 320 had been addressed and were considered closed.
2.0 PREVIOUS WG2 MEETING HELD ON SEPTEMBER 30, 1998
2.1 Approval of Meeting Minutes
The minutes of the previous WG2 meeting, held at the Volpe Center on September 30, 1998 were reviewed and accepted as written.
2.2 Review of Meeting Action Items
Action items from the previous WG2 meeting were reviewed as follows:
2.2.1 WG2 Ballot Group
The full Rail Transit Vehicle Interface Standards Committee has approved that WG2 form a ballot group from within the WG2 membership, with interested members of the RTVISC, who are not currently members of WG2, also invited to be included within the ballot group.
The WG2 membership consist of "Producers" (suppliers, and consultants who receive the bulk of their income from suppliers), "Consumers" (transit agencies, and consultants who receive the bulk of their income from transit agencies), and "General Industry" (e.g. government and university representatives). No more than 50% of the Ballot Group can be drawn from any one of these three groups. In addition, there can be no more than two members from any one organization. Finally, participation on the WG2 Ballot Group, requires membership of the IEEE, as well as membership of the IEEE Standards Association (IEEE-SA).
Alan Rumsey will be working with Tom McGean to finalize the make-up of the Ballot Group. WG2 members who wished to be part of this Group were encouraged to take out membership of the IEEE Standards Association as soon as possible, if they had not already done so. Action item remains open.
2.2.2 Specific Values for CBTC Parameters
Alan Rumsey advised that no further inputs had been received from Suppliers with respect to Annex C, and as such this action item would now be considered closed.
See also item 3 below.
2.2.3 Definitions
Alan Rumsey advised that Section 3.2 of draft D5.0 of the proposed standard ("Definitions") reflects all agreements reached at the last WG2 meeting. Action item closed.
Definitions that had originated from Working Group #5 (WG5) will be reviewed to ensure that WG2 is using the latest revisions to these definitions. In addition, it was agreed that the latest WG5 definition for "light rail transit" should be used instead of the TRB definition.
It was also agreed that the "note" under the definition of automatic train supervision be revised to read:
"Note: the ATS subsystem also typically includes manual and automatic routing functions.]
2.2.4 General Requirements
Section 4 of the draft standard is now considered "ballot ready" and had been revised in draft D5.0 to incorporate minor changes suggested at the last WG2 meeting. Action item closed.
2.2.5 System Safety Requirements
Alan Rumsey advised that Section 5.3 of draft D5.0 of the proposed standard ("System safety requirements") had been revised and reorganized to reflect agreements reached at the last WG2 meeting. This section was now considered "ballot ready". Action item closed.
See also item 6 below.
2.2.6 Grade Crossing Protection
No inputs had been received on section 6.1.15 ("Grade crossing warning") prior to release of draft D5.0 of the proposed standard. Subsequent to release of draft D5.0, inputs had been received from Geoff Hubbs (NYCT) that will be incorporated into the next draft. This specific action item considered closed.
2.2.7 System Availability Requirements
Alan Rumsey advised that Section 5.4 of draft D5.0 of the proposed standard ("System assurance requirements") had been revised and reorganized to reflect agreements reached at the last WG2 meeting. This section was now also considered close to being "ballot ready". Action item closed.
See also item 7 below.
2.2.8 Measuring Passenger Service Delays
George Anagnostopoulos (Volpe Center) action item to provide a worked example of how the CBTC system contribution to passenger service delays could be measured in practice had not been completed in time for this meeting and remains open.
2.2.9 Environmental Requirements
Jeff Eilenberg (LSTS) tabled a proposed update to section 5.5, defining environmental requirements for CBTC wayside equipment based on the AAR Signal Manual and ATCS specifications. Action item closed.
See also item 8 below.
2.2.10 ATP Functional Requirements
Alan Rumsey advised that a number of revisions had been made to Section 6.1 of draft D5.0 ("ATP functional requirements") based on agreements at the last WG2 meeting. Action item closed.
See also item 3 below.
2.2.11 Interlocking Requirements
Errol Taylor (BART) had provided a re-write of section 6.1.11 (route interlocking protection) that had been incorporated in draft D5.0 of the proposed standard. Action item closed.
See also item 3 below.
2.2.12 Draft D5.0 of Proposed Standard
Alan Rumsey advised that the remaining sections of draft D5.0 of the proposed standard had attempted to respond to all other comments received at the last WG2 meeting. Action item closed.
3.0 REVIEW OF SECTION 6.1 ("ATP FUNCTIONS")
Section 6.1 of draft D5.0 of the proposed standard was reviewed on a subsection-by-subsection basis, and the following comments were noted:
a) In the last paragraph of section 6, incorporate the following changes: "… The RF datalink shall include a protocol structure to support safe ….. In addition, the RF datalink shall not cause any adverse electromagnetic …"
b) Rewrite the third paragraph of section 6.1.1.1 to read: "… shall automatically detect and establish the location of each CBTC equipped train as it enters CBTC territory …"
c) In section 6.1.1.2, modify as follows: "… by one or more trains, including trains not equipped …"
d) Change heading for section 6.1.2 to "Safe train separation" and rewrite section to clarify intent both for applications with and without an auxiliary wayside system; also clarify definition of "section of track".
e) In section 6.1.2.1, delete reference to assumed service brake rate, and add reference to train length; also clarify that safe braking model applies to all obstructions ahead, not only trains ahead; last paragraph should also be deleted. In addition, provide clearer definition of "ATP profile".
f) In section 6.1.3, change "actual train speed" to "actual train movement profile"; also expand discussion of brake assurance function to include the case when the CBTC system "pulls back" a movement authority limit such that a train’s actual speed profile now exceeds the new ATP profile.
g) In section 6.1.4, delete last paragraph (note).
h) In section 6.1.6, revise wording to clarify intent.
i) In section 6.1.8, add requirement for means to override these door interlocks.
j) In section 6.1.9, change "i.e." to "e.g."
k) There was considerable discussion on the revised section 6.1.11 (route interlocking protection) with a general consensus that this section should focus more on functional requirements. Ed Mortlock (BAH) and Geoff Hubbs (NYCT) undertook to update this section for further consideration by WG2 at its next meeting.
l) In section 6.1.11.5, correct format error (insert 6.1.12 Traffic direction reversal interlock), and renumber following sections.
m) In (renumbered) section 6.1.13, clarify that establishing work zones is a (non-vital) ATS function, while enforcing work zones is a (vital) ATP function; also move the last paragraph into section 6.3 (ATS functions).
n) In (renumbered) section 6.1.15, change heading to "Highway grade crossing warning" and note that these requirements are "where specified by the authority having jurisdiction".
o) In (renumbered) section 6.1.16, clarify that this section also covers, for example, intrusion detection and other detectable hazards that impact route integrity.
With the above comments, it was the consensus of the meeting participants that section 6.1 was now "ballot ready", subject to a further review of an updated section 6.1.11 (item k) above).
Section 6.1 will be updated in draft D6.0 to incorporate the above agreements, and other meeting comments.
There was insufficient time to review Annex C of draft D5.0 of the proposed standard. WG2 participants were therefore actioned to provide any written comments on this Annex no later than January 15, 1999.
4.0 REVIEW OF SECTION 6.2 ("ATO FUNCTIONS")
Section 6.2 of draft D5.0 of the proposed standard was reviewed on a subsection-by-subsection basis, and the following comments were noted:
a) Incorporate requirements of section 6.2.3 (programmed station stop) into section 6.2.1 (automatic speed regulation), and delete existing section 6.2.3.
b) Add item d) to section 6.2.2 to include requirement for multiple stopping positions for the case where train length is less than platform length.
c) Move section 6.2.7 (communication of train health data) to section 6.3 (ATS functions).
d) Move section 6.2.8 (trainborne passenger information system interfaces) to section 6.3 (ATS functions).
e) Move section 6.2.9 (trainborne system user interfaces) to section 4.5 (train operating modes).
Section 6.2 will be updated in draft D6.0 to incorporate the above agreements, and other meeting comments.
5.0 REVIEW OF SECTION 6.3 ("ATS FUNCTIONS")
Section 6.3 of draft D5.0 of the proposed standard was reviewed on a subsection-by-subsection basis, and the following comments were noted:
a) In section 6.3.1, clarify those ATS functions that are not covered by this standard.
b) In section 6.3.2, add references to: status of auxiliary wayside system devices, movement authority limits, and train door status.
c) In section 6.3.3.1, add reference to unequipped trains; also note that train identifications may not be unique in certain applications.
d) In section 6.3.3.3, add cross reference to section 6.2.1 (automatic speed regulation); also change "each station" to "defined stations" in item a).
e) Rewrite section 6.3.3.6 (energy optimization).
f) In section 6.3.3.7, note that an automatic system reaction may be required to certain alarms.
g) In section 6.3.3.8, change "store" to "archive"
h) In section 6.3.4.4, change "emergency brake" to "brake"
i) In section 6.3.4.6, add additional requirement for train door open inhibit.
Section 6.3 will be updated in draft D6.0 to incorporate the above agreements, and other meeting comments.
6.0 REVIEW OF SECTION 5.3 ("SYSTEM SAFETY")
There was insufficient time to review the revised section 5.3 of draft D5.0 of the proposed standard. WG2 participants were therefore actioned to provide any written comments on this section no later than January 15, 1999.
The following specific agreements were noted at the meeting:
a) Add a paragraph in section 5.3 referencing the need for configuration management of software and hardware.
b) Delete item f) from section 5.3.3.
7.0 REVIEW OF SECTION 5.4 ("SYSTEM AVAILABILITY")
There was insufficient time to review the revised section 5.4 of draft D5.0 of the proposed standard. WG2 participants were therefore actioned to provide any written comments on this section no later than January 15, 1999.
8.0 COMMENTS ON SECTION 5.5 ("ENVIRONMENTAL")
There was insufficient time to review the proposed new section 5.5 of draft D5.0 of the proposed standard. WG2 participants were therefore actioned to provide any written comments on this section no later than January 15, 1999.
9.0 SUMMARY OF MEETING ACTION ITEMS AND OBJECTIVES FOR NEXT MEETING
9.1 Assignment of Actions
The following specific action items were recorded:
|
Item |
Action |
Responsibility |
|
1. |
Alan Rumsey to work with Tom McGean and the WG2 membership to establish WG2 ballot group. |
Alan Rumsey |
|
2. |
Update Section 3.2 (Definitions) in draft D6.0 to reflect the latest WG5 definitions. |
Alan Rumsey |
|
3. |
Provide a worked example of how the CBTC system contribution to passenger service delays could be measured in practice. |
George Anagnostopoulos |
|
4. |
Update section 6.1.11 (route interlocking protection) for further consideration by WG2 at its next meeting. |
Ed Mortlock Geoff Hubbs |
|
5. |
Update section 6.1 (ATP requirements) in draft D6.0 to reflect meeting agreements. |
Alan Rumsey |
|
6. |
Provide any written comments on Annex C no later than January 15, 1999. |
All |
|
7. |
Update section 6.2 (ATO requirements) in draft D6.0 to reflect meeting agreements. |
Alan Rumsey |
|
8. |
Update section 6.3 (ATS requirements) in draft D6.0 to reflect meeting agreements. |
Alan Rumsey |
|
9. |
Update section 5.3 (System safety requirements) in draft D6.0 to reflect meeting agreements. |
Alan Rumsey |
|
10. |
Provide any additional written comments on revised section 5.3 (System safety requirements) no later than January 15, 1999. |
All |
|
11. |
Provide any written comments on revised section 5.4 (System assurance requirements) no later than January 15, 1999. |
All |
|
12. |
Provide any written comments on revised section 5.5 (Environmental requirements) no later than January 15, 1999. |
All |
|
13. |
Provide any other written comments on draft D5.0 of the proposed standard no later than January 15, 1999. |
All |
|
14. |
Re-issue draft D6.0 of the proposed standard by January 30, 1999. |
Alan Rumsey |
9.2 Objectives for Next Meeting
The objective of the next meeting will be to resolve any open issues, address any written comments that have not been previously addressed, and finalize all sections such that the complete standard can be submitted to the IEEE to formally commence the ballot process.
It was the consensus of the meeting participants that based on the current status of the draft standard, this was an achievable objective for the next WG2 meeting.
To ensure sufficient time to address all issues, the next WG2 meeting will be a two-day meeting.
Draft D6.0 of the proposed standard will be issued at least two weeks prior to the next WG2 meeting.
9.3 Date/Location of Next WG2 Meeting
The next WG2 meeting will be held on February 22/23 and will be hosted by Safetran in Louisville.
10.0 ANY OTHER BUSINESS
Alan Rumsey closed the meeting thanking the working group participants for their attendance and active involvement in the various discussions, and again thanking the SEPTA for hosting the meeting.
Minutes prepared by: Dr. Alan F. Rumsey, Chair, WG2