Testing "As a PBV I want to run LPA to create WP's automatically for every groundslot in AMS"

8-3-2017, Roy ten Have

Testing "As a PBV I want to run LPA to create WP's automatically for every groundslot in AMS"

8-3-2017, Roy ten Have

Zoom out

For the Narrow Body fleet, PBV's would like to use the LPA (Line Planning Automation) functionality in Maintenix to be able to schedule Turn Checks for every groundslot in AMS.

Using LPA for an a/c type is limited to either using it only for outstations, or using it only for 'home base'. Therefore, LPA will not be used to create TC Work Packages on Outstations for the Narrow Body fleet.

Scenario's

Prerequisites
Set up flights that result in 4 ground slots in AMS and Narrow Body tail and a Wide Body tail:

Flight 1: Outstation -> AMS
Flight 2: AMS -> Outstation
Flight 3: Outstation -> AMS
Flight 4: AMS -> Outstation
Flight 5: Outstation -> AMS
Flight 6: AMS -> Outstation
Flight 7: Oustation -> AMS
Flight 8: AMS -> Outstation

Primary Flow

Cancelling Flights / ground slots

✅ S03 - Groundslots for a committed TC WP with manually added tasks/faults is cancelled, and .......LPA determines how many WP's are needed for the entire day,reschedules the first WP's it needs (in order) and cancels the rest while leaving WP's in "COMMIT" status untouched

Risks

Bugs

Advice

Test Goals

✅ T01 - LPA can be used to create TC's in AMS and outstations for Narrow Body

✅ T02 - LPA for Wide Body does not create TC's in AMS

R02 - LPA prefers the 'Number of the WP's needed' above 'scheduled time of a WP' when it comes to re-scheduling due to changes of the number of ground slots. (i.e. adding a groundslot shifts current WP's to the left, while a cancelled ground slot results in cancelling of the last WP).

R01 - As LPA reschedules TC Work Packages, any Tasks/Faults which are manually assigned to these Work Packages are also at risk of being re-scheduled.

R03 - Work Packages in 'COMMIT' state are unaffected by all LPA functionality (rescheduling, cancelling). When not actively verifying the status of a WP, this might result in unexpected results for the PBV.

✅ T03 - TC Workpackages created by LPA can be used to assign other open faults and tasks to.

✅ S02 - Groundslots for a scheduled TC WP with manually added tasks/faults are cancelled, and .....LPA determines how many WP's are needed for the entire day,reschedules the first WP's it needs (in order) and cancels the rest

Adding or updating flights / ground slots

✅ S04 Adding a ground slot and running LPA..... results in LPA creating a TC in that ground slot

✅ S05 Changing the planned flights so that any/all ground slots are planned earlier / later ..... results in LPA rescheduling all WP's which are not yet in status "COMMIT"

✅ S01 - Running LPA for 737 creates a TC Workpackage in every AMS ground slot

✅ S02 Running LPA for a Wide Body results in TC Work Packages for every Outstation ground slot

============================================================================================