PCS Documentation

PCS Documents can be browsed and search in three different ways:

  • Document table
  • Search engine (above)
  • Topic Labels: hierarchical view (below)

pcs logo

The document table view provides a very refined way of finding specific documents. The table provides multiple ways of filtering and sorting the content. It is ideal to search for certain type of content or subjects. 

The search engine provides a quick and fast way to find content related to any subject. Results are wider than in the Document table.

The hierarchical view below provides a general overview of the general classification of documents based on labels. Each label includes a number with the amount of articles dedicated to each topic. Clicking on the label link the system offers all the documents that contain that label.

Last, but not less important: Regardless of the method used to find documents, some content takes part of a book as a chapter. If that is the case, the content will contain at its bottom a book navigation structure.

Area

Company Type

Language

Recent Activity

Filter 

November 17, 2017

  • 10:49am
    [PCS] [PCS Documentation] Máté Bak updated How to Carry forward dossiers 17-11-2017Máté Bak updated How to Carry forward dossiers   Changes to Body  Loco types Loco types    -With Major Release 2017 Loco types has become a list in PCS uploaded by the IMs instead of the former free text field. That is why during the carry forward from TT2018 to TT2019 RUs need to map the former free text entries with the existing valid loco types. In case PCS cannot resolve it automatically based on the last year entry and the new loco type number, the user will see the following dialog.+With Major Release 2017 Loco types has become a list in PCS uploaded by the IMs instead of the former free text field. During carry forward to TT2019 PCS tries to resolve the free text entry - defined loco type mapping in the background. Long-term the user will be able to map the locos, if there is an update in the loco type database from one year to another.  for dossiers that have *loco type number* system tries to find defined *loco type* for that loco type number for the target TTP. If matching is found loco type is replaced for dossiers that have *loco type number* system tries to find defined *loco type* for that loco type number for the target TTP. If matching is found loco type is replaced  for dossiers that have *loco types* there are 2 cases that are covered: for dossiers that have *loco types* there are 2 cases that are covered: Máté Bak updated How to Carry forward dossiers

    [PCS] [PCS Documentation] Máté Bak updated How to Carry forward dossiers

    17-11-2017

    Máté Bak updated How to Carry forward dossiers

     

    Changes to Body
     
    Loco types
     
    Loco types
     
     
    -
    With Major Release 2017 Loco types has become a list in PCS uploaded by the IMs instead of the former free text field. That is why during the carry forward from TT2018 to TT2019 RUs need to map the former free text entries with the existing valid loco types. In case PCS cannot resolve it automatically based on the last year entry and the new loco type number, the user will see the following dialog.
    +
    With Major Release 2017 Loco types has become a list in PCS uploaded by the IMs instead of the former free text field. During carry forward to TT2019 PCS tries to resolve the free text entry - defined loco type mapping in the background. Long-term the user will be able to map the locos, if there is an update in the loco type database from one year to another.
     
    for dossiers that have *loco type number* system tries to find defined *loco type* for that loco type number for the target TTP. If matching is found loco type is replaced
     
    for dossiers that have *loco type number* system tries to find defined *loco type* for that loco type number for the target TTP. If matching is found loco type is replaced
     ...
    Read more
  • 10:42am
    [PCS] [PCS Documentation] Máté Bak updated How to Carry forward dossiers 17-11-2017Máté Bak updated How to Carry forward dossiers  Too many differences to list. See Revisions for details.Máté Bak updated How to Carry forward dossiers

    [PCS] [PCS Documentation] Máté Bak updated How to Carry forward dossiers

    17-11-2017

    Máté Bak updated How to Carry forward dossiers

     

    Too many differences to list. See Revisions for details.

    Too many differences to list. See Revisions for details.
    Read more

November 16, 2017

  • 3:19pm
    [PCS] [PCS Documentation] Máté Bak updated Dossier Creation (Create New Dossier Wizard) 16-11-2017Máté Bak updated Dossier Creation (Create New Dossier Wizard)  Too many differences to list. See Revisions for details.Máté Bak updated Dossier Creation (Create New Dossier Wizard)

    [PCS] [PCS Documentation] Máté Bak updated Dossier Creation (Create New Dossier Wizard)

    16-11-2017

    Máté Bak updated Dossier Creation (Create New Dossier Wizard)

     

    Too many differences to list. See Revisions for details.

    Too many differences to list. See Revisions for details.
    Read more
  • 3:18pm
    [PCS] [PCS Documentation] Máté Bak created Dossier creation demo 16-11-2017Máté Bak created Dossier creation demo   Video of Dossier creation demo without PaP and train id Video TextIn this video, we will show the creation of a new dossier without PaPs and without Train ID. We will use Metrans (mtd) as the RU company. After login, we get into the dashboard and we look for a New dossier creation button.The first step is about the Basic Data. We enter first a dossier name. We will use in this case the name "Dossier creation demo without PaPs and without Train ID". Next field, International Train Number, is optional but we can define one here as an example. Train ID is also optional. Select the Timetable period: We choose today 2018 and change the Process type to Ad-hoc Pre Accepted. The rest of the fields are ok and we can jump to the next step "RU timetable". For further details on the different processes, please check the documentation.Next step is to build the RU timetable. We will add four operation points as an example. Then we add the timetable. We can use the Tab key to jump from one field to the next one. We enter here the origin and destination times and the border operation point times as well so it will be clearer for the IM. The timetable is ready but we may add the train number as well. Please notice the star in the first point corresponding to the Reference point of the timetable. We can also add our neighboring RU partner in the points corresponding to Hungary. We are ready with the timetable and we can go ahead to the calendar as the next step.In our example, we would like to run the train only from March until September instead of the entire Timetable year. Also, we would like to run this train only on Monday, Wednesday, and Friday. Now our calendar is ready and we go towards the new step "Dossier Level Data".At this point, we don't have to edit anything. The leading RU and the leading IM have been selected automatically. We can change these values at this point. Also, it is possible to change this values later on. For this case, please check the "Edit agent" documentation.In the last step, we can configure the train parameters. For example, for the Activity type, we can choose "Operational stop" for our first point. We select the Loco type number and the system automatically fulfills the fields of the train. The train will be probably heavier, so we can edit that data and its adjacent fields in accordance with its real characteristics. In our example, we will also include the container profile values and the Brake type and the Braking Ratio, and finally, we save the data. After getting our first point ready we can copy the parameters to other operation points. The loco parameters are only valid in Slovakia but the Common train parameters are valid across the rest of the other operation points. So we click on ¨Apply¨ and ¨Replace¨. Now we can check that the parameters are indeed copied to the other points but still we need to add the loco and the activity types. We continue the procedure with the other two points. In Hungary, since we are using the same loco type, we can copy also the values from its first operation point to the second one. Now for the last point, we only need to include the activity type of this operation point: For example "Terminal Service". The rest of the parameters are fine so we can finally save the parameters and create the dossier.The system takes us directly into the Basic Data of the new dossier with its first version in the Open phase.For further steps, please check the other videos.Máté Bak created Dossier creation demo

    [PCS] [PCS Documentation] Máté Bak created Dossier creation demo

    16-11-2017

    Máté Bak created Dossier creation demo

     

    Video Text

    In this video, we will show the creation of a new dossier without PaPs and without Train ID. We will use Metrans (mtd) as the RU company. After login, we get into the dashboard and we look for a New dossier creation button.

    The first step is about the Basic Data. We enter first a dossier name. We will use in this case the name "Dossier creation demo without PaPs and without Train ID". Next field, International Train Number, is optional but we can define one here as an example. Train ID is also optional. Select the Timetable period: We choose today 2018 and change the Process type to Ad-hoc Pre Accepted. The rest of the fields are ok and we can jump to the next step "RU timetable". For further details on the different processes, please check the documentation.

    Next step is to build the RU timetable. We will add four operation points as an example. Then we add the timetable. We can use the Tab key to jump from one field to the next one. We enter here the origin and destination times and the border operation point times as well so it will be clearer for the IM. The timetable is ready but we may add the train number as well. Please notice the star in the first point corresponding to the Reference point of the timetable. We can also add our neighboring RU partner in the points corresponding to Hungary. We are ready with the timetable and we can go ahead to the calendar as the next step.

    In our example, we would like to run the train only from March until September instead of the entire Timetable year. Also, we would like to run this train only on Monday, Wednesday, and Friday. Now our calendar is ready and we go towards the new step "Dossier Level Data".

    At this point, we don't have to edit anything. The leading RU and the leading IM have been selected automatically. We can change these values at this point. Also, it is possible to change this values later on. For this case, please check the "Edit agent" documentation.

    In the last step, we can configure the train parameters. For example, for the Activity type, we can choose "Operational stop" for our first point. We select the Loco type number and the system automatically fulfills the fields of the train. The train will be probably heavier, so we can edit that data and its adjacent fields in accordance with its real...

    Read more
  • 11:28am
    [PCS] [PCS Documentation] Máté Bak updated Phase Harmonization 16-11-2017Máté Bak updated Phase Harmonization   Changes to Body -[[{"fid":"509","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false},"type":"media","link_text":null,"attributes":{"alt":"Phase Harmonization","class":"panopoly-image-original media-element file-default"}}]]+[[{"fid":"509","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false},"type":"media","link_text":null,"field_deltas":{"1":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false}},"attributes":{"alt":"Phase Harmonization","class":"panopoly-image-original media-element file-default","data-delta":"1"}}]]  This is the second phase for each process. Leading agency shares the dossier with chosen RU partners and other involved agencies. All together should prepare consistent dossier for placing path request or for consultation with IMs via feasibility study to the IMs. This is the second phase for each process. Leading agency shares the dossier with chosen RU partners and other involved agencies. All together should prepare consistent dossier for placing path request or for consultation with IMs via feasibility study to the IMs.  *Rights*: RU agencies have read and write access. Each RU can read everything but write only into his assigned section. Leading agency is able to change read/write rights to read only for the other involved agencies. There is still no IM access. *Rights*: RU agencies have read and write access. Each RU can read everything but write only into his assigned section. Leading agency is able to change read/write rights to read only for the other involved agencies. There is still no IM access. Changes to Linked PCS Documents   +Harmonization without PaPs Máté Bak updated Phase Harmonization

    [PCS] [PCS Documentation] Máté Bak updated Phase Harmonization

    16-11-2017

    Máté Bak updated Phase Harmonization

     

    Changes to Body
    -
    [[{"fid":"509","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false},"type":"media","link_text":null,"attributes":{"alt":"Phase Harmonization","class":"panopoly-image-original media-element file-default"}}]]
    +
    [[{"fid":"509","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false},"type":"media","link_text":null,"field_deltas":{"1":{"format":"default","field_file_image_alt_text[und][0][value]":"Phase Harmonization","field_file_image_title_text[und][0][value]":false}},"attributes":{"alt":"Phase Harmonization","class":"panopoly-image-original media-element file-default","data-delta":"1"}}]]
     
    This is the second phase for each process. Leading agency shares the dossier with chosen RU partners and other involved agencies. All together should prepare consistent dossier for placing path request or for consultation with IMs via feasibility study to the IMs.
     
    This is the second phase for each process. Leading agency shares the dossier with chosen RU partners and other involved agencies. All together should prepare consistent dossier for placing path request or for consultation with IMs via feasibility study to the IMs.
     
    *Rights*: RU agencies have read and write access. Each RU can read everything but write only into his...
    Read more