
Agenda PCS Test Group Feb 2017
Features that are ready or will be ready for sure for test
- TEST:
- Loco types usage as RU in train parameters (1136) - RU/IM specific topic
- Search for Observation (1223) – IM/RFC specific topic
- General Terms and Conditions in PCS (1204) – freight RU/RFC specific topic
- SUMMARY/INTRODUCTION of the implemented “simple” features – RU/IM/RFC (usability issues)
- Improved usability when adding a location in a TT (1196)
- Path number copied to subsidiary (1231)
- Used terminology in creating and managing PaP (1186)
- Always show Dossier ID on PCS GUI (1178)
- Edit calendar (1172)
- Mandatory Traction details – Default (1152)
Features that could be ready for test
- TEST:
- PAMT in PCS (1008) – RFC specific topic
- Conflict solving view in PCS (1075) – RFC specific topic
Issue registration is also possible from here
Tasks during the meeting
Loco types usage as RU in train parameters (1136) - RU/IM specific topic
- IM: prepare locos via the GUI and import sheet
-- Use import with and w/o national id
- RU:
-- Look for old dossier (before loco types)
--- Try to edit
--- Change old text to loco type
-- Create new dossier
--- Select loco in train parameters
--- Define weight/length of carriages and use pre-calculation
--- Check the speed constraints
-- Check the loco portfolio in the administration area
Search for Observation (1223) – IM/RFC specific topic
- Place Observations in dossiers (as a preparation perhaps you need to create dossier)
-- Place full Observation (add value to each field)
-- Place "incomplete" Observation (miss some or almost every field)
- Dossier is in Observations/Post-Processing (feature is available only in these phases)
- Go to advanced search and filter for dossiers in Observations/Post-Processing phases
- Check Observations in the result
- Check reporting (Dossier Data Organizer) for the same phases and use show only (similar to the labels)
- Check bulk editing and use show only (similar to the labels)
General Terms and Conditions in PCS (1204) – freight RU/RFC specific topic
- Select PaP and try to submit path request
- Check the GTC side from Control and from Administration
- Try to withdraw path request after acceptance
PAMT in PCS (1008) – RFC specific topic
- Create PaPs for testing (if import fails due to the locos, for the time being create them manualy)
-- Fix PaPs
-- Flex PaPs
-- Define Network PaPs
-- Create PaPs with n.a. days
-- Be sure that every path section in the published PaPs has distance information
- Create path requests
-- Request types:
--- Fix PaP or Flex PaP w/o intermediate section or cut edge only on available days
--- Flex PaP with intermediate station
--- Shortened Fix or Flex PaP (cut the edge)
--- Request for n.a. days
--- Request with Network PaP
--- Always define F/O
-- Create also a conflict
-- Create once composite relation
- Generate PAMT report
-- Check report content in general
-- Check distance & running day information + K values
- Play conflict resolution (reservation, tailor-made) and generate new report
-- Check Request & Allocation status
-- Check alternative PaP ID