MINUTES OF COMBINED WG9  & INTEROPERABILITY TASK FORCE MEETING 

May 1, 2000

 STV, Philadelphia, PA

-----

1.      Attendance & Welcome

Attendance is the combined Interoperability Task Force and the Working Group 9 as outlined in the attached Excel spreadsheet. Thanks to our host John Ewing for arranging the meeting room, equipment and food.

2.      Purpose of Meeting

This combined meeting was held to coordinate the efforts of the two groups and combine their collective talent

The main purpose of the meeting was 1) to review work performed since the last meeting towards assembling a set of minimum required data elements required for basic operating unit to basic operating unit interoperability and 2) to obtain agreement on a uniform format for presentation of that data.

3.      WMATA Status

Karl Berger reported that the final design review for the WMATA LonWorks based maintenance and diagnostic system would be May 9^th. Karl also said he would review again the WMATA program vis-à-vis our working group activities based on what he had learned at this meeting and provide an update at the next meeting.                      

4.      Dave Phelps - Compatibility of R142 Data Elements with IEEE 1475 Standard 

Dave compared the R142 data elements prepared by Jim Lyke with IEEE 1475. There were 7-8 items not called for in IEEE 1475 which were in the R142 data elements. There were also some IEEE 1475 data elements not in the R142 list. Most important were a small number of instances where the data elements in the R142 list were incompatible with IEEE 1475. There were not many of these cases so it is deemed feasible to move forward. Jim Lyke and Dave Phelps will go over these discrepancies with a view towards how to harmonize and rationalize the IEEE 1475 derived data elements with those derived from the R142 car. Since IEEE 1475 is a consensus standard while R142 is a single car order, the benefit of the doubt should lie with the IEEE 1475 version, but none-the-less a careful review is needed.  

5.      Standard Format 

Jeremy Roberts discussed a standard format example he had prepared and this was compared with the standard format developed from it by Jim Lyke. It was agreed that a field should be added to identify the source of the data (R-142 car, IEEE 1475, etc.) and that a definition  field was also needed.  Lyke, Roberts and the WG9/ITF members at the meeting then agreed upon a common set of headings for characterizing both LonWorks and TCN derived data elements in an Excel spreadsheet format. The standard headings agreed upon are: data_index; system; applicability; source document; long name; name; in/out; type; combined elements; combined elements type; priority; units; min send/receive time; max send time; size; range; invalid value; description; scale factor a; scale factor b; scale factor c; raw range; and comments. Recognizing that the final presentation will be a relational database, the Excel format must be importable to Access  

6.      Definitions 

The group has been using the term "data element" for the basic alphanumeric data being transmitted. This is not the same as a LonWorks SNVT (Standard Network Variable) , which can consist of one or a set of related data elements. Nor is it the same as a LonWorks "object" which is the  entities which interact with each other or the major subsystems doing the communicating. (Objects may be viewed as the major blocks in a functional block diagram of the system between which data flows). It was agreed the group will need to develop these standard definitions as part of the standard.  

Jeremy Roberts cited the example that data elements may be viewed as "pennies" being put into a sealed envelope to be mailed to someone who needs them. The sealed and addressed envelope may be viewed as a " packet"  which consists of a variable length data structure or payload containing the  related data elements or "pennies" and the address information on the envelope. In LonWorks, SNVTS are sent as packets.

7.      Scope of WG9 Effort 

The proper scope of the WG9 TCIP Standard was discussed with regard to basic operating unit interoperability. It was agreed that the group would need to identify data elements suitable for both ROSIN and LonWorks, harmonized as much as possible, and expressed in the standard Excel Format agreed upon at this meeting. For TCN, it would be necessary to go beyond this and identify the packaging of data elements. For LonWorks, the committee should recommend those data elements which should be packaged together, but the LonMark Interoperability Association should actually stipulate the particular SNVTS. It was agreed that we would derive data elements from UIC 556, R142, IEEE 1475 etc. While we would try to maintain the actual content, format, etc. of the data element with as little change as possible, it was agreed we could change the data element name, if it would make it easier to understand. Pierre Zuber noted that UIC 556 does not necessarily identify the data elements we will need here in the U.S. and we should not let it be limiting.  

8.      Non Propulsion and Braking Data Elements 

The non propulsion and braking data elements developed by Jim Lyke were discussed. It was agreed that Jim would refine his spreadsheet using the new agreed upon format and eliminating redundant data elements. There was also discussion about the use of descriptors for data elements which imply that they are limited to a single state (such as "Doors Closed and Locked") when in fact they are intended as questions    ("Doors Closed and Locked?")  which can possess affirmative, negative, or even other states. To eliminate confusion which might exist for persons not familiar with transit but expert in data communications, names such as "Door Status" are preferred since this name does not infer any specific state.  

9.      Locomotive Data Elements 

John Ewing presented a set of propulsion and braking data elements needed for locomotive applications. The list is based on the 27 point APTA MU Standard. It was agreed the next step would be for John to refine his elements and place them in the standard Excel format agreed upon at this meeting. It was also agreed that Dave Phelps would send John the latest version of the 27 point APTA MU standard.  

10.  Combined List of Propulsion/Braking Elements 

Fred Woolsey has started a uniform list of propulsion and braking elements. He will add the John Ewing and Dave Phelps material and put it into the agreed upon standard Excel format. 

11.  Combined List of  Data Elements 

Jim Lyke and Fred Woolsey will then prepare a combined list including Jim Lyke's non propulsion data elements and all of the combined propulsion and braking data elements into a single overall list using the agreed upon format. This list will be sent to all WG9 and ITF members and possibly to the RTVISC membership for review and comment. Written comments should be provided and only these written comments will be reviewed at the next meeting. It was also suggested that those data elements whose functions must also be hardwired be identified in the data base.  

12.  UIC Issues 

Pierre Zuber has identified contacts at UIC regarding copyright issues and provided them to Tom McGean. We will wait to contact these people until it is clearer which part of their standards we may want to use.  

13.              Rail TCIP Real Time Data Elements 

Since Jim Kemp was not at the meeting, and there was much to be done on car to car data elements, this area was deferred. Tom McGean is to contact Jim to discuss the status of Jim's work item to identify from the total family of potential rail TCIP data elements those which communicate outside of the rail system in real time and are thus priorities for WG9 standardization. If necessary Tom and Rob should see about getting Jim additional help in this area. 

14.              Off Vehicle Communications Protocol Standards 

The group showed interest in an IEEE standard protocol for off-vehicle communications and pointed out this activity is underway now with no standards available. McGean pointed out the CBTC Working Group had determined that signaling system standard protocols were not ready to be standardized and should be deferred while the NYCT Canarsie Line project moves forward. The group's view was that non-CBTC off vehicle communications protocol standards were needed now. Fred Woolsey offered to chair such a working group and prepare a title, purpose and scope for discussion at the next Rail Transit Vehicle Interface Standards Committee meeting. Tom McGean will discuss this proposal with Alan Rumsey, Chair of the CBTC Working Group to determine their views on this matter. 

15.              PASSWORDS & COPYRIGHT ISSUES

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.  The P1488 is on the TSD website: (http://www.tsd.org/wg9.htm).  It is security protected; contact Rob or Tom Sullivan for the password. Documents which may have copyright issues will also be identified.  

16.              Next Meeting 

It was agreed the next meeting of the ITF would be held jointly with WG9 in Washington DC at the offices of Booz Allen on Friday,  July 21, 2000. The meeting will start at 9:30AM and end at 4:30 PM. Karl Berger has made arrangements to meet at the BAH offices at the Columbia Square Bldg., 555 13th Street, N.W., Suite 480 East, Washington, DC 20004 

17.   Summary of Assignments 

For convenience assignments from the meeting are summarized below. Please refer back to the text of the minutes for full details on your assignments. 

Karl Berger

·        Report on WMATA maintenance & diagnostics LonWorks system at next meeting.  

John Ewing

·        Refine locomotive data elements and place them in the standard Excel format agreed upon at this meeting. Provide the refined data elements to Fred Woolsey by June 1st. 

Christian Girard

·        Obtain information on data elements being used on new N.E. Corridor trains and provide to Fred Woolsey by June 1st. 

Jim Lyke

·        Provide Rob McHugh list of agreed upon data element headings.

·        Refine list of non motor control data elements in key functional areas (Doors, Lighting, Current Collection, basic Passenger Information) Place them in the agreed upon format, and with Fred Woolsey integrate with the propulsion and braking data elements and provide the complete interoperability data base to Rob McHugh by June 15th.

·        With Fred Woolsey, assemble written comments received concerning data base and be prepared to discuss at next meeting.

Tom McGean

·        Provide Rob McHugh Interoperability Task Force email list.

·        Contact Jim Kemp to discuss the status of Jim's work item to identify from the total family of potential rail TCIP data elements those which communicate outside of the rail system in real time and are thus priorities for WG9 standardization. If necessary Tom and Rob McHugh should see about getting Jim additional help in this area.

·        Contact Alan Rumsey about his views concerning establishing an off-vehicle non-CBTC communications protocol standard.

·        Prepare Interoperability Task Force minutes and provide to Rob McHugh

·        Check status of FTA Gateway proposal and any ways to kick start effort.  

Rob McHugh

·        Add Interoperability Task Force members to WG9 membership list

·        Mail out ITF minutes as part of WG9 minutes

·        Receive the interoperability data elements from Fred Woolsey/Jim Lyke on June 15th and distribute by June 18th to all WG9 members, all Interoperability Task Force members, and possibly all Rail Transit Vehicle Interface Standards Committee members for written comments which are to be sent directly to Fred Woolsey. 

Dave Phelps

·        Go over with Jim Lyke discrepancies between R142 and IEEE 1475 data elements with a view towards how to harmonize and rationalize these differences.  Provide list of data elements Fred Woolsey by June 1st.

·        Provide John Ewing the latest version of the APTA 27 point MU standard.

·        See about getting someone from BART involved in the WG9 and ITF effort.  

Fred Woolsey

·        Refine his list of non-R142 propulsion and braking data elements and integrate with IEEE 1475/R142 list provided by Dave Phelps and Jim Lyke and locomotive data elements received from John Ewing..

·        With Jim Lyke, integrate "harmonized" and refined non motor control data elements with the propulsion and braking data elements and provide the complete interoperability data base to Rob McHugh by June 15th.

·        With Jim Lyke, assemble written comments received concerning data base and be prepared to discuss at next meeting. 

18.  Adjournment

 The meeting adjourned at 4 PM.