Crew Rotation : TBA (To Be Announced)

1 - Introduction

The term TBA (To Be Announced) refers to a functionality developed to book seats on scheduled flights( ) or flights of type “Date” (without scheduled flights) to Operational Units. When it is not defined yet which worker will attend a job, the seats can be saved for an undefined worker. After including the TBA, DRAKE will attribute the seats to the quantity of workers assigned to embark or disembark. These bookings can be done on the page or through Crew Rotation -where workers who will be part of the planning can also be monitored, as will be displayed below.

Supplementary article of:

Learn how to create recurring TBA schedules on:


2 - Access

2.1 Go to the Crew Rotation page. Apply the filter by operational unit and, since there is any activity linked, new lines will be available with the name TBA).

The quantity of lines displayed is according to the number of TBAs added.

2.2 When clicking with the right button of the cursor over any TBA cell, DRAKE will notify that there is “No action available“. This happens because (as mentioned on this tutorial’s introduction) the Crew Rotation will be available only for monitoring the TBA, but all changes must be made through the pages and .


3 - TBA Details on Crew Rotation

3.1 To add TBA through the Crew Rotation, click on the “Add” button.

3.2 Done this, the window “Add Appointment“ will be opened over the page. Initially, will suggest to add a worker with the options “To Be Announced“ or “Worker“. Select the option TBA, and inform the quantity of workers that will be needed in this category (in this example will be 5 workers). When finishing, click on “Next”.

 

3.3 In this demonstration the Crew Rotation is not filtered by Operational Unit, therefore the next step will be to select the OU that this TBA will perform the job. In case it is already filtered, this step will not be necessary, once that DRAKE will assume that the TBA will be for the filtered Unit.

3.4 Select the company (Records - entities) and the task( ) of the TBA.

3.5 On this step, the embark information needs to be included. Pay attention to the “Logistic schedule type“, this is where can be defined if is “Date” or “Flight”. Fill in as needed.

 

Field

Description

Field

Description

Logistic schedule type

Inform if the worker logistics will be the type “Date“ of “Flight”. When selecting “Flight”, the system will request the scheduled flight to the unit ( ).

Date*

Date of the embark/disembark (check if correct)

TR time

Transport time

Origin

Transport origin operational unit

Destination

Transport destination operational unit

Embark Address

Embark/Disembark Address

Operational Job

Job the worker will perform on board

Contract

Contract linket do the appointment

Transport type

Airplane/Helicopter/Maritime/Land

Passenger type

Schedule type( )

Cost Center

Cost Center linked to the appointment (Records - Cost Center).

Bank Accounts

Worker’s Bank Account

Comments

Free Text

3.6 - Now the Crew Rotation will display the TBA as below:

3.7 With the TBA created, the Flight booking is ensured for these participants. When the workers finally be allocated for the demand, will necessary to inform the system DRAKE through the system. To do so, click with the right button of the cursor on the TBA entry and choose the option “Set Worker”.

3.8 The window “Set Worker” pops-up over the page requesting to select the worker that will perform the job replacing the TBA .

3.9 Done this, DRAKE will replace the TBA register with the selected worker.

 

4 - TBA on Logistic Schedule

4.1 When registering a TBA, it is generated as well a Logistic Schedule with embark and disembark days to the OU selected.

4.2 It is possible to view the TBA participants on Logistic Schedules, but it is not possible to include which participant will perform the job through the Logistic Schedule. For this, will be necessary to use the Crew Rotation as mentioned above.

4.3 After including the work through Crew Rotation, the TBA is replaced and the Schedule flow proceeds normally.

 

5 - TBA on Task Planning

5.1 This functionality is necessary for seat booking on flights. When saying that a certain flight will have a maximum number of passengers, the quantity of workers that can board the same flight is restricted. To ensure that many teams work simultaneously, it is possible to view the number of seats available per flight on crew rotation.

5.2 To have this information, it is necessary to set the parameter that displays the seat number per flight and set a daily round trip Flight Template with the maximum of 5 seats as seen on

5.3 And in the page ,a TBA has been created with activity from 30/09/2021 to 14/10/2021.

5.4 Done this, automatically all 5 seats are filled on flight, to embark on 30/09/2021 and disembark on 14/10/2021.

This information is displayed on

5.5 Now the Crew Rotation will indicate 0 available seats for both flights on embark and disembark dates. By that, the seats are booked on the flight and the overbooking is avoided.

 

5.6 To define which workers will be denominated on the TBA, go back to the page (Task Planner) , click with the cursor right button and select “View the involved workers” and set the workers by clicking on “Set worker”.

 


6 - Add worker on TBA

6.1 To add a worker through “Crew Rotation” is necessary to find the TBA, click with the cursor’s right button above the embark period and a menu will be displayed.

 

6.2 Click on the option “Set Worker“, select the worker and click on “Save”.

 


7 - Removing TBA appointment

7.1 Click with the cursor’s right button above the TBA appointment and choose the option “Remove appointment“.

 

.

7.2 The option “Remove appointment” will display the information. Confirm if this is the correct TBA to be removed and click on “Confirm”.

7.3 The page will be updated with the information “Logistic Schedule removed successfully”.

 

7.4 By this, the both Crew Rotation and Logistic Schedule will be updated. as seen below, the TBA quantity is now reduced.

 

7.5 In case the user tries to remove a TBA through the Logistic Schedule page, the system will not allow this command. The TBA is registered as embark and disembark while the Logistic Schedule registers only embark or disembark . To avoid conflicts, the Crew Rotation will be used to define which TBA will be removed.

 

 

Caso surja alguma dĂșvida, entre em contato com nosso suporte atravĂ©s do E-mail: suporte@sapiensia.com / ou Telefone em: +55 (21) 2391-4726