TTM FOR JS PILOT: USERS MANUAL. Table Of Contents. Test Setup. Test Execution. Published on CMS RNE (

Transcription

1 Published on CMS RNE ( Home > TTM FOR JS PILOT: USERS MANUAL TTM FOR JS PILOT: USERS MANUAL Submitted by CMS on 25 June, :02 Content Table Of Contents Test Setup TTM - Setup TTM - Create and Deploy Test Scenario Workflows CI - Setup Test Execution Assumptions Process Overview 1.Process for RU 1 to RU 2 2.Process for RU 2 RU 1 3.Process for RU 1 to IM 1 4.Process for RU 2 to IM 2 5.Process for IM 1 to IM 2 6.Process for IM 2 to IM 1 7.Process for IM 1 to RU 1 1

2 8.Process for IM 2 to RU 2 Test Setup TTM - Setup This task is mainly done by the Support Team Setup Partners In the TAF Train ID Pilot, the scenarios include at least one RU and one IM and can be extended to two RUs / two IMs. The communication pathes between the partners look as follows. Each path has to be configured and tested. For each partner, basic information has to be provided, for the particular test case 2

3 Partner Name Contact Communication Role RU 1 SBB Cargo AG Mister abc Phone: Mail abc@sbb.ch [1] Skype: yes xxx RU 2 DB Cargo RU Lead RU IM 1 SBB Infrastruktur Coordinating IM IM 2 DB Netz IM Setup Route Delivery Type With XLS-File Add. Info Filename*: route_xxx.xlsx X Through PCS PCS Dossier ID**: xxxxxx In the Joint Sector Pilot we agreed to use maximal 2 RU 2 IM cases. However, for the explanatory reasons of usage of TTM tool, the 3 RUs are given here. 3

4 Partner From ref via to RU 1 A A C G RU 2 A C E G RU 3 A E G G The example above is provided to explain the logic of the construction of the Path Request in TTM. In the JS Pilot, we use maximal 2 RU 2 IM cases. We have here the example of 3 Rus just for the explanation purposes. TTM automatically constructs the Path Request related messages upon the given route. The approach is the simplified train planning and path request construction which helps understanding the basic logic of the path request related messages in TAF TSI. For each RU participating in the Path request process, the whole trip of the train must be known. Therefore, the from to (A - G) relation is always given. The ref means Reference point for the train planning of the particular RU. For the first RU, the reference point is the departure point. For the second RU (and other participating RUs), the reference point is the interchange point with the previous RU, and via is the interchange point to deliver the train to the third (i.e. to the next) RU. For the simplicity reasons, for the construction of the routes in TTM, we place the interchange and handover (change of IMs) points to the same location in all cases. In the practice, the interchange and handover points may not always match. Setup Locations ID Full location name Abbreviation PLC (TAF CRD ID) A CH_BSRB B CH_MU C CH_PR D... K IT_MIL PLC = Primary Location Code of the TAF / TAP CRD (Common Reference Data) It is important that all the locations used on the route are registered in CRD, otherwise, the TAF/TAP messaging will fail. TTM - Create and Deploy Test Scenario Workflows Done by Support Team 4

5 Partner Flow Type With Interface No Interface XML Workflow Name* RU 1 2 IM 1 2 X X RU Scenario <LeadRU>- <From>- <To> IM Scenario <LeadIM>- <From>-<To> * Scenarios are generic: When the workflow starts, the tester will be asked to provide thecompany codes of the participating companies. Example: IM Scenario OBB-I GR-SP-M-LJ or RU Scenario CD-P DEC-PRA Explanation: For the IM scenario in the example, the location names can be found in the previous table with locations on the route (location name, abbreviation). Currently, in the names of the workflows, the abbreviations are used: Gr for Graz SP for Spielfeld M for Maribor LJ for Ljubljana Please note that the whole route is given in the name, including the locations located on the territory of the second partner. CI - Setup Setup Communication Channels Check Company Codes Setup Web Service Connectors This has to be done for each message type of each partner oft the test. Partner Message Type Version Adapter Address RU 1 PCM CI RU 1 PR LL Adapter RU 1 PD CI

6 RU 2 PCM CI RU 2 PD LL Adapter Adding for an address of a message means, that the message is looped back to the originating computer. Test Execution Assumptions The test execution described in this document is based on a real example with the following partners involved on the selected route. Involved Partners Role Real Partner ID RU 1 CD Cargo 2154 RU 2 Rail Cargo Austria RCA 2181 IM 1 SZDC 0054 IM 2 ÖBB Infrastruktur/Netz 0081 Selected Route The selected route goes from Tyniste (TYN) to Spielfeld (SPI) Process Overview Throughout the document the process is described with the following sketch (RU-IM Quadrant) 6

7 Each of the communication paths between the partners has to be built up consecutively in the sequence as described in this manual and the process steps for each RU and IM have to be executed as described below. The process steps for an RU look as follows (as displayed in the TTM): 7

8 The process steps for an IM look as follows (as displayed in the TTM): 8

9 9

10 The sequence in the RU-IM quadrant is as follows. The numbers 1. to 8. correspond with the chapter numbers. 1.Process for RU 1 to RU 2 10

11 The first step is to build up the communication between the initiating RU 1 and the partner RU 2. There are the following possibilities to create a dossier for the Lead RU: a) Go to PCS and create dossier b) Go to PCS and copy an existing dossier (containing the agreed route and calendar for the particular test case) c) Use TTM to create the dossier d) Use SoapUI testing tool to create dossier (separately documented) PCS - Create Dossier for RU 1 (a) Login to PCS as RU 1 partner (in this example CD Cargo). Create the dossier for RU 1 in PCS 11

12 Dossier name: it is recommended to use a structured name for your dossier e.g. NNxxxxxxTyyy where NN = Abbreviation of responsible Test Manager xxxxxx = Date T = Test yyy = number of instance of test (related to (b)): One may use the features of PCS to copy an already existing dossier and continue to process the new copy it saves time. Please refer to PCS documentation regarding all the tricks for dossier processing. For example, do not forget to mark the calendar, RU timetable (with locations and times and train characteristics) for the copy. After saving the dossier, PCS indicates the success The status of the dossier changes to «Open» and the signal for RU 1 changes to yellow. 12

13 TTM - Start Test Process for RU 1 After the dossier for RU 1 is successfully initiated in PCS, you have to start the test process for RU 1 in TTM. 1) Start the process and 2) select «Deployed process definitions» 3) Search for the related test scenario, which corresponds to RU 1, in this case «RU Scenario CD TYN_SPI» 4) Start the process by pressing the button «Start process» The following process steps in the RU scenario are possible: 13

14 - Step 1: create dossier (related to ( c) dossier creation method): PathCoordination message with Type of Information 30 (create dossier) - Step 2: create a subsidiary timetable with PathCoordination message, Type Of information 1 harmonization in progress). (One can add here the company specific PathRequest-ID, to follow up the subsidiary in the path request process). - Step 3: acceptance indicator in PCS set to green (with PathCoordinationMessage and Type Of Information 2 harmonization accepted) - Step 4: initialization of the Path Request message. IMPORTANT NOTE: in the setup with PCS, this step makes only sense when executed by LeadRU. In PCS, the involved RU cannot execute this step in the harmonized timetabling process. The precondition for this step is that all acceptance indicators of both RUs are set to green. Otherwise, PCS will treat the dossier as not harmonized and will not promote the dossier from Harmonization to Path Elaboration. If the user tries to execute the step 4 without fulfilled preconditions, PCS will generate the corresponding Error Message, which will be shown in the message archive of the TTM server. - Step 5 / step 6: initialization of the PathConfirmed message. This message has an effect in TAF/TAP TSI to symbolize that the RU has accepted the IMs offer. Additionally, it will have an effect to PCS that the dossier will be promoted to Active Timetable. For more details about PCS phases and their meaning, please refer to the PCS documentation. Enter the necessary parameters as follows: 14

15 Start the process and wait until the progress indicator shows, that the process was sucessfully started. 15

16 CCS - CI Check Message Status As soon as the above described process started successfully, it starts to communicate with PCS through the Common Interface (CI) of the CCS (Common Components System). Login to CCS, go to the «Dashboard» and select «Outbound Online Status» Look for the relevant Message that indicates the transmission of the necessary Path Coordination Message from originating RU 1 (in this case 2154, CD Cargo) to the partner RU 2 (in this case 2181, RCA). The signals indicate the status of the transmission. As soon as the «RTD» signal is green, the message was sucessfully transmitted from TTM through CI to PCS. TTM - Check Message Log Now you have to check if TTM received the necessary messages from PCS through CI. In TTM go to the message archive und select the corresponding message, open it and check the XML-File. 16

17 PCS Check Dossier Status After communication between TTM, CI and PCS has taken place you have to finally check the status of the dossier in PCS. 1) In PCS you are still logged in as RU 1. Go to «Control» and check if the signal of RU 1 became green. Now the communication from lead RU 1 to partner RU 2 is set up. 17

18 2.Process for RU 2 RU 1 Now the communication from partner RU 2 to initiating RU 1 has to be established. PCS - Prepare Dossier for RU 2 Log in to PCS as RU 2, in this case as RCA 18

19 Go to the corresponding dossier (here ). In the dossier you see the status of the leading RU in green. Open the dossier by selecting «Control» 19

20 The status of the dossier is now in status «Harmonization», the signal for RU 1 is green and the signal for RU 2 in the dossier is in the processing mode. TTM - Start Test Process for RU 2 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to RU 2, in this case «RU Scenario CD TYN_SPI». Start the process by pressing the button «Start process» 20

21 Enter the necessary parameters as follows: 21

22 With this single step in TTM two steps in PCS are triggered: switch lights in PCS dossier to green for this RU close harmonization phase Start the process and wait until the progress indicator shows, that the process was successfully completed. 22

23 CCS - CI Check Message Status Login to CCS, go to the «Dashboard», select «Outbound Online Status» and check the message and CI-routing status. Again the «RTD» signal has to be green. TTM Check Process Status and Message Log Back in TTM, first you can check how far the process has already worked. Follow the red lines to see how far did the process get. 23

24 In this case, the TTM has successfully sent an PCM (Path Coordination Message). In the message log/archive you find the corresponding messages as in the previous process. 24

25 PCS Check Dossier Status Go back to PCS, where you are still logged in as RU 2. You see, that a dossier got an update indication. Press «Update Dossier» 25

26 After the update, the dossier in PCS shows, that now the signal for RU 2 is also green and the overall status of the dossier is still in harmonization. Now the communication from lead RU 1 to partner RU 2 is set up. 3.Process for RU 1 to IM 1 26

27 Now the communication between the RU1 and its partner IM 1 has to be established. PCS Prepare Dossier for IM 1 Login to PCS as RU 1, in this case as CD Cargo. After login, go to «All 2018» and you get a lot of dossiers, where you see the status of the involved partners. Select the dossier you want to work with. 27

28 On the screen you see, that the dossier is in the phase «Harmonization» and the two RUs have green signals. TTM - Start Test Process for RU 1 / IM 1 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to RU 1, in this case «RU Scenario CD TYN_SPI» Start the process by pressing the button «Start process» 28

29 Enter the necessary parameters as follows: 29

30 Start process and wait until it is completed. CCS - CI Check Message Status 30

31 Login to CCS, go to the «Dashboard», select «Outbound Online Status» and check the message status. Under «Remote Li», you can see that a message has been sent to SZDC, which in our case is IM 1. Again the «RTD» signal has to be green. TTM Check Process Status and Message Log Back in TTM, first you can check how far the process has already worked. Follow the red lines to see where the process actually stands. 31

32 In this case, the process has successfully sent an PR (Path Request). In the message log/archive you find the corresponding messages as in the previous process. 32

33 PCS Check Dossier Status Go back to PCS, where you are still logged in as RU 1. The dossier now looks as follows The dossier successfully passed the status «Path Request» and is now in the status of «Path Elaboration». Now the communication from lead RU 1 to its partner IM 1 is set up. 33

34 4.Process for RU 2 to IM 2 Now the communication between the RU2 and its partner IM 2 has to be established. PCS Prepare Dossier for IM 2 Login to PCS as RU 2, in this case as RCA. 34

35 Selecting «Control» you see, that the dossier is now in the status of «Path Elaboration». TTM - Start Test Process for RU 2 / IM 2 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to RU 2, in this case «RU Scenario CD TYN_SPI» Start the process by pressing the button «Start process» 35

36 Enter the necessary parameters as follows: 36

37 Hint: The PathRequest messages must be sent by each RU to his IM to follow the TAF process steps. In PCS this information is already visible to the IMs. But as we test here the TAF processes the message must be sent nevertheless. Start process and wait until it is completed. 37

38 CCS - CI Check Message Status Login to CCS, go to the «Dashboard», select «Outbound Online Status» and check the message status. Under «Remote Li», you can see that a message has been sent to OEBB I, which in our case is IM 2. Again the «RTD» signal has to be green. TTM Check Process Status and Message Log Back in TTM, first you can check how far the process has already worked. Follow the red lines to see where the process actually stands. 38

39 In this case, the process has successfully sent an PR (Path Request). In the message log/archive you find the corresponding messages as in the previous process. 39

40 Now the communication from RU 2 to its partner IM 2 is set up. 5.Process for IM 1 to IM 2 Now the communication between the two involved IM partner IM 1 and IM 2 has to be established. PCS Prepare Dossier for IM 1 Login to PCS as IM 1, in this case as SZDC. 40

41 Select the corresponding dossier Select «Basic Data» 41

42 And then «Control» You see that the dossier is in the status of «Path Elaboration» and the indicator shows that the dossier «is waiting for all IMs to accept the dossier so you can submit Ad-Hoc Request Offers» TTM - Start Test Process for IM 1 -> IM 2 42

43 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to IM 1, in this case «IM Scenario SZDC TYN_SPI» Start the process by pressing the button «Start process» Enter the necessary parameters as follows: 43

44 Start process and wait until it is completed. 44

45 CCS - CI Check Message Status Login to CCS, go to the «Dashboard», select «Outbound Online Status» and check the message status. Under «Remote Li», you can see that a «Path Coordination Message» has been sent to OEBB I, which in our case is IM 2. Again the «RTD» signal has to be green. TTM Check Process Status and Message Log Back in TTM, first you can check how far the process has already worked. Follow the red lines to see where the process actually stands. 45

46 In this case, the process has successfully sent an PCM (Path Coordination Message). In the message log/archive you find the corresponding messages as in the previous process. PCS Check Dossier Status Go back to PCS, where you are still logged in as IM 1. After you have updated the dossier, it now looks as follows 46

47 The signal for IM 1 is now in status green. Now the communication from IM 1 to IM 2 is set up. 6.Process for IM 2 to IM 1 Now the communication between the responding IM 2 and the lead IM 1 has to be established. 47

48 PCS Prepare Dossier for IM 2 Login to PCS as IM 2, in this case as ÖBB Infrastruktur. Select the corresponding dossier 48

49 And then «Control» You see that the dossier is in the status of «Path Elaboration» and the indicator for ÖBB Infrastructure shows that the dossier can be modified. TTM - Start Test Process for IM 2 -> IM 1 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to IM 1, in this case «IM Scenario SZDC TYN_SPI» 49

50 Start the process by pressing the button «Start process» Enter the necessary parameters as follows: 50

51 Start process and wait until it is completed. 51

52 TTM Check Process Status and Message Log In TTM, first you can check how far the process has already worked. Follow the red lines to see where the process actually stands. In this case, the process has successfully sent an PCM (Path Coordination Message). In the message log/archive you find the corresponding messages as in the previous process. 52

53 PCS Check Dossier Status Go back to PCS, where you are still logged in as IM 2. After you have updated the dossier, it now looks as follows 53

54 The signal for IM 2 is now in status green. Now the communication from IM 2 to IM 1 is set up. 7.Process for IM 1 to RU 1 Now the communication between IM 1 and its corresponding RU 1 has to be established. PCS Update Dossier for IM 1 Login to PCS as IM 1, in this case as SZDC. 54

55 Select «Control» You see that the dossier is in the status of «Path Elaboration» and the indicator for SZDC shows that the dossier can be modified. TTM - Start Test Process for IM 1 -> RU 1 Go to the «Process» screen and select «Deployed process definitions». Search for the test scenario, which corresponds to IM 1, in this case «IM Scenario SZDC TYN_SPI» Start the process by pressing the button «Start process» 55

56 Enter the necessary parameters as follows: 56

57 With these settings, TTM will send an answer to the original «Path Request» from IM 1 to RU 1. Start process and wait until it is completed. 57

58 CCS - CI Check Message Status Login to CCS, go to the «Dashboard», select «Outbound Online Status» and check the message status as done in previous cases. TTM Check Process Status and Message Log In TTM, first you can check how far the process has already worked. Follow the red lines to see where the process actually stands. 58

59 In this case, the process has successfully sent an PD (Path Details Message). In the message log/archive you find the corresponding messages as in previous cases. PCS Check Dossier Status Go back to PCS, where you are still logged in as IM 1. After you have updated the dossier, it now looks as follows 59

60 The dossier is now in the status of «Acceptance». Now RU 1 has to confirm the Path Details to IM 1 in order to finish the whole negotiation process. PCS Update Dossier for RU 1 If you log in PCS as RU 1 (in this case CD Cargo) 60

61 You see, that the dossier has changed: It is now in status «Acceptance» and the indicator shows, that the RUs now have to process the dossier in order to achieve the status «Active Timetable». By clicking on the indicator of RU1 (CD Cargo), you see the status in details: 61

62 Change the status to «Accepted» and the indicator for RU1 goes to green Now the communication from IM 1 to RU 1 is set up. 8.Process for IM2 to RU 2 Now IM 2 has to provide the Path Details to RU 2 and RU 2 has to confirm the Path Details to IM 2 in order to finish the whole negotiation process. 62

63 PCS Update Dossier for RU 2 Login to PCS as RU 2, in this case as Rail Cargo Austria. Select «All 2018» 63

64 You see that the lead RU 1 and IM 1 are green, meaning that the coordination has taken place. Also IM 2 (ÖBB-I) is green, meaning that the coordination with IM 1 took place. Changing to «Control» Shows, that RU2 (RCA) has not yet accepted the Path Details. Change the status to «Accepted». 64

65 The signal changes to green. PCS Check Dossier for RU 1 If you now login to PCS as RU 1 (CD Cargo) and go to «All 2018» 65

66 You see, that coordination between all partners took place, all status are in green. If you change to «Control» you see, that all indicators are set to green and the status of the dossier is in «Active Timetable» At this stage, the whole process is finished, all partners have built up their relations. 66

67 Source URL: Links [1] 67