Unpruning of message elements with CR-0612 for future T2S-CRs. CRG, 25 January 2018 Frankfurt am Main

Transcription

1 Unpruning of message elements with CR-0612 for future T2S-CRs CRG, 25 January 2018 Frankfurt am Main

2 CRG Outcome Outcome of last CRG meeting on 15 th December 2017 CRG members expressed a preference to not prune new message fields that have been included in an ISO Maintenance Release due to an approved ISO CR raised by T2S. This would avoid a double market adaptation of the relevant message schemas. CRG members have been invited to provide the list of fields that they consider to be unpruned in line with ISO Maintenance Releases and the relevant T2S CRs for upcoming releases. Based on the CRG member s feedback, the 4CB will provide the CRG for the meeting in January 2018, with an assessment on the approach (pros/cons/risks) and the concrete elements that can be unpruned. 2

3 4CB assessment of new approach Pro s: In case the ISO Maintenance Release CR and functional CRs are implemented in different releases, reduced frequency referring to the creation of different schema versions which will reduce slightly the effort stemming from this implementation area. Less changes to automated testing tools required. Risks: In case a "likely functional T2S CR is not implemented for several T2S- Releases or even cancelled, it needs to be evaluated if the unpruned elements should be pruned again. As it is up to the PMG/RMSG to define the scope of a release, the CRG has no guarantee which CRs can be taken into account. As there are no rules which changes, ISO CR from T2S versus ISO CR from different source, should be taken into account and which not, we will end up in long-lasting discussions and cherry picking. 3

4 4CB assessment of new approach Con s: CR-0612 followed the same approach as the last Maintenance Release CR-0342 (which was initiated to implement MR 2012) Changing the initial approach in the direction of a cherry picking approach prevents the clear separation between standard compliance and functional enhancement (CR categories). In the end, this will prolong the drafting and assessment process of the CR, make the DA and the subsequent implementation overall more complex, error prone and costly Newly added elements cannot be fully tested, in case the functionality will be introduced with a later functional T2S CR. Nevertheless, new schemas will have to be tested twice at 4CB level, to first guarantee the schema is correctly implemented and the new elements are not used and second to test the correct usage of the elements after the implementation of the functional CRs Unpruning of elements in T2S messages without implementing new functionalities is not in line with the customizing principles followed by T2S In case messages are sent to T2S with new elements or codes, it has to be evaluated if an interim solution before the functional T2S CR functionality will be implemented is needed or BR's like additional technical validation have to be changed In addition, this approach requires two updates of MyStandards. Firstly to indicate that these fields, even if present, are not used in T2S and secondly once the functional T2S CR is implemented, to document its usage in MyStandards All in all, changing the current approach will (i) cause higher implementation efforts on 4CB side; and (ii) create additional risks. 4

5 4CB proposal According to the 4CB feedback on the written procedure and the previous slides, the 4CB disagree on changing the approach of CR We recommend, to only migrate the messages to a later Maintenance Release from a purely technical point of view If the CRG still wants to unprune some elements already within release 3.0, the CRG members shall raise a dedicated CR for to allow the 4CB to assess the impact and potential risks (see Annex and WP). For future ISO Maintenance Release CR the CRG can also request the inclusion of message changes caused by future T2S-CRs. But this approach might (i) requires longer discussions in the CRG, (ii) prolong the DA (iii) increases the costs of the CR 5

6 Annex T2S-CR (ISO-CR) Status 4CB assessment CR-519 (ISO-CR-512) CR-520 (CR-510 and CR- 511) PA completed (part of ranking exercise) Do not update the schemas as the CR is on hold candidate; DA ongoing Ok for 4CB to update CR-587 (ISO-CR-610) candidate; DA ongoing Ok for 4CB to update CR-600 (ISO-CR-608) candidate; DA ongoing Ok for 4CB to update CR-607 (ISO-CR-609) On hold; DA completed Ok for 4CB to update 6