TABLE OF CONTENTS

• New critical path
• Critical path identification
• Tasks
  • Start and end descriptions
  • Additional information
• Proof-read and save

If this is not the first critical path you are creating, we recommend duplicating an existing one and making the appropriate modifications. This way is usually much more efficient!

See How to duplicate a critical path in the Backoffice?

New critical path

Once logged into the Backoffice (https://backoffice.tarmactechnologies.com) and having selected an airport, click on the Add a critical path button. 

Critical path identification

Fill in the details in the first section in the page that just loaded, except Airport which should be filled in.

• Aircraft
• Airline
• Minimum Turnaround Time (MTT)
• Adjustment time (the airline-defined delay between blocks-in and the opening of the first door (ADO))
• Default (see What is a default critical path?)

Known bug: if your browser is set up to display times in 24 hours format, the MTT display may be wring (e.g. 00:50 will be displayed as 10:50 AM).

Tasks

Tasks are split in two categories: above the wing and below the wing.

For each category and for as many tasks as necessary (you can add tasks by clicking on the green plus sign):

• Select the appropriate task name in the list. (The task list is different between those above the wing and those below the wing.)
• If the task is instantaneous (without duration), toggle the End only? column.
• Enter the start and end references (or the end reference only for an end-only task).

  •  The references should have the format A+hh:mm or D-hh:mm, respectively for tasks related to the arrival and to the departure of the aircraft.

  • References A-hh:mm and D+hh:mm are also possible, for pre-arrival and post-departure tasks, although this is less common.

  • The start and the end of a task should either both refer to the arrival or both refer to the departure. Combinations like a A+ start and a D- end are disallowed.

    One exception: because plugging in the GPU is arrival-related and unplugging it is departure-related, we created two different tasks — GPU Plug and GPU Unplug — meant to be used as end-only, the former planned after the arrival and the latter before departure. In the analytics, we will easily be able to calculate the duration between both tasks.

  • See How to know if a task is arrival-related or departure-related?

We recommend that you set up the list of tasks to represent what actually happens during a turnaround in your station.

Keep in mind that you do not need to record each and every one of the tasks, but that you should include any and all critical and time-sensitive tasks. You may also want to include tasks whose timings you want to track.

Start and end descriptions

For each task, you have the possibility to define a trigger for the start and the end of the task. This may help agents understand when they should tap on the Start and End button for each task, and will most likely reduce misunderstandings and make the data more reliable.

• For a given task, click on the three dots in the More column.
• Fill in the Start description and End description (or just the latter for end-only tasks).
• Click on Close to come back to the previous screen.

In the AGOA app, these descriptions will be visible by clicking on the icon of a task, while on the page of this task.

Additional information

For each task, you have the possibility to record additional information (e.g. “Number of pax boarded” for the Boarding task).

Each item of additional information will be linked to a given task and accessible in the AGOA app through the page of this task.

• Click on the three dots in the More column of a task (the same ones than for adding start/end descriptions).
• For as many items of additional information as you want (you can add one by clicking on the green plus sign):

  • Choose what you would like to track in the dropdown list.

  • Optionally, define a custom label. This is the label that will be displayed in the AGOA app, so do not hesitate to rephrase using your airline’s lingo.

    • You may want to use custom labels to shorten the text displayed in the app, especially for agents using a smartphone, with a relatively small screen. For example, the first item in the screenshot below was relabeled “Jetbridges/stairs”.

    • Make sure the custom label and the item of additional information correspond. It will be near impossible for us to provide you with decent analytics if you do not…
      

  • Choose the type of information you want to track (checkbox, number, text or datetime).

    • The number information type only works with integers. If you want to track decimal quantities, choose the text information type.
      

• Click Close to return to the previous screen.

Proof-read and save

DO NOT FORGET TO SAVE! Otherwise, you way lose all of your work.