openetcs / ssrs Goto Github PK

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Description:

When the brake percentage is captured as Train Data and the conversion model is applicable, A_brake_emergency(V), T_brake_emergency and A_brake_service(V) shall not be influenced by the status of a special brake. However, the conversion model offers the possibility that T_brake_service can be affected by the status of the regenerative brake, eddy current brake or Ep brake (see A.3.9).

Comment:

The calculation of the full service brake equivalent time described in 3.A.3.9 does not specify the possibility to create different values of T_brake_service for the different combinations of special brakes; it only indicates that the parameters used to calculate T_brake_service may change if it is justified by the specific brake system of the train (Paragraph 3.A.3.9.6). However, only one value of T_brake_service will be calculated, that is inconsistent with this paragraph.

Description:

In case a message has to be sent during the loss of the safe radio connection, this message shall be considered as sent.

Comment:

what does it mean? what are the implications of the message being considered as sent?

Description:

Together with start and end of reversing area, the following supervision information shall be sent.

Comment:

If this information is not sent together with start and end of reversing area, what the on-board shall do?

Dear SSRS working group.

For verification reasons we need the SSRS data consisting of:

1. data dictionary
2. variables
3. ranges of variables
4. source or destination of varible (function/API)
5. Source of information regarding 1.- 4. concerning: where did the information come from (e.g. subset, operational rules, API, ...)

for Subset-026-3.5: Management of radio communication.

Concerning the SSRS there are concepts for the following questions missing:

Defining the funcitons and data dictionary how are the functionalities combined?
How do the functions play together in the architecture?

Description:

If the driver selects NL (E10) then the ERTMS/ETCS on-board equipment shall immediately switch to Non Leading mode (refer to SRS chapter 4, transition between modes: transition [46]). The mission starts in NL mode.

Comment:

According to the Condition 46 of the Table 4.6 describing the conditions to pass from the mode SB to the mode NL, three following conditions have to be satisfied:

1. Driver selects Non Leading.
2. Train is at standstill.
3. The "non leading" input signal is received.
   But what happens if Start of Mission is in the state S10, the driver selects Non Leading, but no "non leading" input signal is received?

without description is a picture useless.
Please provide a small description for the following pictures: 1, 2, 3 and 4

Workshop 2013-03-24-Paris will be in April
Workshop 2013-04-28-Charleroi was in March

In this chapter you have identify 4 Tasks. in my opinion, i think it could better to define for each task the expected inputs and outputs.

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Description:

In level 2/3: Train trip shall be initiated if the on-board equipment detects that the minimum safe front end has passed the EOA/LOA location.

Comment:

We suppose that the train must have an MA available on-board to be able to apply this rule (otherwise it cannot run until the first balise group).

Need volunteers for reviev of the SSRS interface document

The chapter is to generic.
A small description could be necessary, in order to understand what really the focus of this chapter is.

Description:

In case the LX is not protected, ERTMS/ETCS on-board equipment shall be informed:

Comment :

What happens for the case of not protected level crossing? EBD has to cross EBI supervision limit or 0km/h?

Description:

t1; Vest <= Vtarget; Not relevant; -; Normal Status

Comment:

What is Vtarget?

Description:

In case the calculation of the GUI curve is inhibited, for display purpose only, the P speed related to EBD, shall be calculated for the max safe front end of the train as follows (see Figure 49):
V_P_EBD_Target (d_maxsafefront) = V_EBD ( d_maxsafefront + Vest * ( T_driver + T_bs2 ) + Dbec ) - ( Vbec - Vest )
V_P_EBD_Target (d_maxsafefront) = Vtarget if d_maxsafefront + Vest * ( T_driver + T_bs2 )+ Dbec >= d_EBD (Vtarget)
With D_bec and V_bec calculated according to 3.13.9.3.2.10

Comment:

d_EBD is undefined for Vtarget (will always return Infinity), because for each EBD based target (except SvL or SR distance) the EBD curve crosses the ceiling speed EBI supervision limit at the target location (see 3.13.8.3.1).
EBI = P + dV_EBI (see 3.13.9.2.2), so d_EBD is undefined for Vtarget (= P).

Comments on the MoM SSRS Kick off UIC Paris 24th of april

Page 7
Point 6.2
Nota: SNCF was chosen as Review leader and not as “Requirements and criteria” (please cancel this wording that was not expressed in this meeting).

The SSRS writing is performed by a group of ERTMS system experts led by a manufacturer.
The logic is to take as basis the experience of the manufacturers that has already done this kind of job for their own previous developments and completed by an operator view through the review process.

Gilles Dalmas (SNCF) was chosen as leader for the review working group.

Please cancel the drawing never discussed in this meeting.

Nota: this acceptance of leadership of the review working group is intended in the context of the conclusions of the meeting of Charleroi summarized in the power point presented on point 3.

Page 8
Point 6.3
Last phrase:
SNCF: Focus is on the subset 26 and the other relevant subsets and will be defined by the SSRS itself (functional scope).

Point 6.4
Replace second bullet by: “the review group will start together with the SSRS writing group”

Page 9
Point 7.1
The comment from ERA is not clear.

Point 7.2
It shall be noted that the position of Lloyds on rewriting with structured language is not compliant with the conclusions of Charleroi.

Point 8
Question 7: the SSRS is the first step of design and therefore not part of the WP2, it is no more a question for WP2.

Point 9
Delete last point: it is question of review working group and not “requirement and criteria” and no date engagement has been taken.

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Description:

In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to SBD shall be calculated for the estimated train front end as follows:
V_P_EOA (d_estfront) = min { V_SBD ( d_estfront + Vest * ( T_driver + T_bs1 ) ),
V_GUI_EOA ( d_estfront ) }
V_P_EOA (d_estfront) = 0 if d_estfront + Vest * ( T_driver + T_bs1 ) >= d_EOA

Comment:

V_GUI_EOA ( d_estfront ) = ?

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Question:

1. shall the SSRS only focus on the ERTMS/ETCS OBU KERNEL? and why?
2. Considering the SSRS will only focus on the ERTMS/ETCS OBU KERNEL, will the interface between the KERNEL and TUI, BTM, MMI, ODO, EUROBALISE and LTM be defined and recorded in the SSRS?

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Description:

The maximum EB deceleration A_ebmax shall be the maximum of A_brake_emergency between 0 km/h and the maximum speed of the train.

Comment:

We assume that the A_brake_emergency used here is the one calculated by the conversion model.

Description

If the driver has manually changed the level to 2 or 3

Comment

[email protected]: seems a spec issue. Indeed, 3.5.3.4.a) covers start of mission case.
Actually, 3.5.3.4.d) seems to be included inside 3.5.3.4.a), as manual level selection can only
happen during SoM procedure.
Answer: --> the following paragraph makes it possible at virtually any time when there is a
driver present (and the train is at stand-still):
3.18.4.2.4 For operational fallback situations: at standstill, the onboard equipment shall allow the
driver to change the ERTMS/ETCS level: The selection shall be limited to those contained in the
table of priority, if available

Description:

b) If an error condition requiring the termination of the communication session is detected onboard
(e.g., not compatible system versions between on-board and trackside).

Comment:

Any other errors requiring this?

Description:

When the supervision status is Overspeed, Warning or Intervention, the on-board equipment shall display the SBI speed (i.e. the FLOI speed).

Comment:

There is no interface on DMI allowing to display the FLOI speed, we suppose that this
information is displayed instead the permitted speed.

Currently there is no effort planned for SSRS task, nor task leader, nor task participants.

Also, it is not clear to which WP belongs SSRS

This should be defined in project planning.

Description:

It shall be possible to define individual speed dependent deceleration models of
A_brake_emergency(V) and A_brake_service(V) for each combination of use of regenerative brake, eddy current brake and magnetic shoe brake.

Comment.

The paragraph 3.13.2.2.6.2 indicates that the selection of brake parameter for A_brake_service(V) is done according to status of regenerative brake and eddy current brake (but not magnetic brake), while the paragraph 3.13.2.2.3.1.7 states that it shall be possible to define individual speed dependent deceleration models of A_brake_service(V) for each combination of use of regenerative brake, eddy current brake AND magnetic shoe brake.

Description:

In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to EBD, shall be calculated for the max safe front end of the train as follows:
V_P_EBD_Target (d_maxsafefront) = min { ( V_EBD ( d_maxsafefront + Vest * ( T_driver + T_bs2 ) + Dbec ) - ( Vbec - Vest ) ), V_GUI_EBD_Target ( d_maxsafefront) }
V_P_EBD_Target ( d_maxsafefront ) = Vtarget if d_maxsafefront + Vest * ( T_driver + T_bs2 ) + Dbec >= d_EBD ( Vtarget ) or if d_maxsafefront >= d_GUI ( Vtarget )
With Dbec and Vbec calculated according to 3.13.9.3.2.10

Comment:

V_GUI_EBD_Target ( d_maxsafefront ) = ?

Description:

The information Termination of Communication Session and corresponding Acknowledgement shall be the same in every system version.

Comment:

-> how can this requirement be applied on Onboard?

Description:

t3; Vtarget < Vest <= V_MRSP; d_maxsafefront > d_I(Vest) if FLOI(Vest)=SBI2(Vest)
OR d_estfront > d_I(Vest) if FLOI(Vest)=SBI1(Vest); -; Indication Status

Comment:

For which distance is computed V_MRSP?

Description:

Nominally, accidental loss of an already open session (that can occur at any step) has not been taken into account for the design of the SoM flowchart. However, should such a fault occur above D11 the nominal procedure applies (refer to D11 in flowchart). On the other hand, if it occurs in any step further than D11, the process shall go to S10.

Comment:

These procedures are applied iff the level is 2 or 3 (otherwise there will be no open session with Euroradio).

issue 1:
you write about the modeling of the SRS, but within the scope of the openETCS, we will NOT modeling the SRS but the SSRS

Issue 2:
The chapter only focus on the modeling, but omit to mention how the SSRS will be created.

Issue 3:
The sentences are not clearly formulated.
you write for example: "The modeling of the SRS would be require the following steps: to define the scope of the model"
--> The sentence not make a sense for me

issue 4:
you write: "The first outcome of this Task force will an overview of all necessary documents from the
operator, the industry and all the European Railway Authorities to manage this kind of a
documents."
--> I don't understand the meaning

you write: "The SSRS will be composed of two parts: 1/ the functional decomposition and the API (architecture) and 2/ the requirements."

--> For me little bit difficult to understand. you want to start with the architecture definition and then the requirement specification?
In general you start with the requirement specification and after that define the architecture.

Description:

The ERTMS/ETCS on-board equipment shall be in On Sight mode before the train reaches the beginning of the On Sight area or, at the latest, when the train reaches the beginning of the On Sight area.

Comment:

According to the Condition 73 of the Chapter 4.6, needed to pass from LS mode to OS mode, the transition can be performed only if (1) the max safe front end of the train is inside the On Sight area AND (2) the estimated front end of the train is not inside an LS acknowledgement area. So, in this particular case, if the condition (2) is satisfied, the train shall not pass in On Sight when it reaches the beginning of the On Sight area. Also, if the level is 0 or NTC, the train will not pass in On Sight (see Paragraph 5.9.4.1).

Description:

When the supervision status is Overspeed, Warning or Intervention, the on-board equipment shall display the FLOI speed, according to the following formulas:
V_FLOI_DMI = min { max { V_SBI_MRDT, Vtarget_MRDT + dV_SBI_MRDT (Vtarget) },
V_MRSP + dV_SBI (V_MRSP) } in case of MRSP target or LOA
V_FLOI_DMI = min { max { V_SBI_MRDT, Vrelease }, V_MRSP + dV_SBI (V_MRSP) } in case of EOA or SvL

Comment:

There is no interface on DMI allowing to display the FLOI speed, we suppose that this
information is displayed instead the permitted speed.
For which location is computed the release speed in case of EOA or SvL?

Dear Baseliyos,
your start of the wiki inclding information about weekly meetings is pretty much what we need. Thanks.
I have a small request for reorganisation: please seperate the weekly update + SCRUM agenda + MoM into an own file "Project Management".
This is our target configuration and is already used by other projects as well (toolchain, WP1).

Need resources for this issue!!
Description of how to create a SSRS artifact will be find Here.

Description:

If none of its supported system versions is compatible with the one sent by trackside, it shall send a version independent message indicating "No compatible version supported". It shall inform the driver and shall terminate the communication session.

Comment:

[[email protected]] SpecIssue: how should the driver be informed?

Description:

After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data), and if no reply is received within the fixed waiting time from the last sending of the mode change report, the ERTMS/ETCS onboard equipment shall terminate the session.

Comment:

The Paragraph 5.6.4.3 describes a degraded situation where no order to terminate the communication session was received from the RBC after a given number of position report sendings. It states that in that case the ERTMS/ETCS onboard equipment shall terminate the session. But there is no information about the state change after this action => should be process end? or remain in the same state?

Description:

The on-board equipment shall display the Permitted speed, according to following formula:V_P_DMI = min { max { V_P_MRDT, V_Target_MRDT }, V_MRSP }

Comment:

What is V_target_MRDT?
For which distance is computed the value of MRSP?

Description:

t2; Vtarget < Vest <= V_MRSP; d_maxsafefront <= d_I(Vest) if FLOI(Vest)=SBI2(Vest)
OR d_estfront <= d_I(Vest) if FLOI(Vest)=SBI1(Vest); -; Normal Status

Comment:

For which distance is computed V_MRSP?

A formalization of Subset-026, Chapt. 7 is available, that could be used for working on the SSRS.
It is unclear, where to store this contribution on github.

Description:

In Level 1: Train Trip shall be initiated if the on-board equipment detects that the minimum safe antenna position (calculated by subtracting distance between active Eurobalise antenna and the front end of the train from the min safe front end position) has passed the EOA/LOA location.

Comment:

We suppose that the train must have an MA available on-board to be able to apply this rule (otherwise it cannot run until the first balise group).

Description:

In case the calculation of the Guidance curve is enabled, the on-board shall calculate the location of the Permitted speed supervision limit valid for the estimated speed, as follows: d_P (Vest) = min { d_FLOI (Vest) - Vest * T_driver), d_GUI_FLOI (V_est) }

Comment:

d_GUI_FLOI (Vest) = ?

Dear all,

Backlog for the 1st Sprint in the backlog is ready.
To all volunteers - please pick up a requirement from the list of the backlog
Manual will be described here
[email protected]

Description:

All current MA and track description data, except track conditions, shall be deleted and new ones shall not be accepted
The process shall go to S050.;
1,2,3

Comment:

How long MA and track description data shall not be accepted? Until the state S150?

A common flace to collect the namespace (starting) during the SSRS work is needed. This namespace collection should be usable by all modelling activities and has to be documented properly.

How can the namespace list for the model be managed.
Maybe a simple xml file can be used as basis which is then transferred into glossary documents to create links in every model.
The Latex document can then be generated based on the XML file.

Please feel free to bring more ideas

Description:

t4; Vtarget < Vest <= V_MRSP; d_maxsafefront > d_P(Vest) if FLOI(Vest)=SBI2(Vest)
OR d_estfront > d_P(Vest) if FLOI(Vest)=SBI1(Vest); -; Overspeed Status

Comment:

For which distance is computed V_MRSP?