Block changing occurrence in schedule

According to the calculation rule, DRAKE automatically sets an occurrence to embark or disembark the employee. E.g.: Rodrigo embarked before enjoying his 14-day off period; DRAKE will generate an extra time for each day off not taken on his time sheet. This occurrence may or may not be changed manually. It is recommended to keep it blocked, since DRAKE will calculate the occurrences correctly .

Create logistical schedules independent of end of contract

Allows to generate logistic schedules even after contracts expiring dates.

Request Type:  Change or Schedule. 

This is the standard type of request that DRAKE inserts when automatically generates crew change logistic schedules. However, this can be changed when the Crew Change responsible enters the Logistic Schedule on DRAKE

Transport Type: Airplane, Helicopter or Maritime

Is the default type of transports for crew change DRAKE automatically inserts when generating crew change schedules. This can be also changed when the crew change responsible performs changes on DRAKE schedules.

Blocking Color

This color will be displayed on crew change's logistic schedule if there is any obstacle for the worker embark or disembark.

Warning color

This color will be displayed on crew change's logistic schedule if there is an alert for the worker embark or disembark.

Substitution Color

 This color will be displayed within the crew change's logistic schedule if the worker  has been replaced.

To be announced color

 This color will be displayed within the crew change's logistic schedule if the worker  is undefined and set as TBA (To be Announced)

Crew Change Schedule Type

 It defines what is the default schedule type for crew change. The default crew change is recommended.

Standard Schedule Type

 Set the general default schedule type for all schedules. The default crew change is recommended

Use Base default when not informed

When checked, this parameter defines that if the day-off Operational Unit  is not defined, it will set as default the rest OU.

Base

 Sets the default rest OU.

Allow embark on base OUs for work and overtime occurences.

 If there is a postponement, participants will earn an embark or extra time event depending on their work schedules, but they will remain on land. This parameter defines whether it is possible to embark employees with these occurrences while on land. It is recommended this option to be checked so that there are no problems embarking postponement participants.

Copy TR's on postponed flight

 In cases of postponement, this parameter will define if the Transport Request (TR) will be copied to the postponed schedule.

Includes employee on vacation on automatic schedules.

 Defines whether DRAKE will include vacation workers in schedules that are automatically generated. The shift operator will see a lock if the employee is actually on vacation.

Includes sick employee on automatic schedules.

 Defines whether DRAKE will include workers in schedules that are automatically generated.

Remove empty logistic schedules by scale changes

 If there are changes in class scale, DRAKE will reallocate class participants to new schedules on new dates, leaving the old schedules empty. This parameter will define if DRAKE will be able to erase them or not. We recommend that you leave this option checked.

Justify absence during finalization

 If this parameter is checked, DRAKE will ask for an excuse for absence whenever an employee does not embark on his/her class change date.

Filling absence justification

Defines if any information will be automatically filled to the absence reason.

Default reason absence justification

 Defines if any information will be automatically filled in for the absence reason and what will be filled out.

Type of Logistics Schedule that can create.

If the Logistic Schedule will be Date, Flight or Date and Flight.

Require contract

 If marked, contract will be required to do some programming

It requires specific permission to include participant with block in programming

 If checked, a permission to include participant with blocking will be required. The permission will be "include participant with block in schedule"

It requires specific permission to include participant with alert in programming

 If checked, a permission will be required to include participant with alert. The permission will be  "Include participant with alert in schedule"

Use rest operational unit address for logistic schedules

If checked, the rest operational unit recorded on Units will be used to generate schedule disembark address.

Demand extra time reason

If checked, DRAKE will request a justification when finishing the logistic schedule to each worker that exceeds the shift.

Filling extra justification

Defines if the Extra Time Reason will be automatic and what will be filled.

Notify extra for expats

Defines if expatriates extra time will be also sent by e-mail with locals extra time notification

Period for notification of extra time

Defines a period to sent extra time notification.

Acronym

The Operational Unit acronym that will be displayed on many options from DRAKE.

Description

Operational Unit's name

Type

Defines if the unit  is onshore, offshore or extra

Color

Color for report identification

Base

Place where the disembark occurs. It is recommended to use the nearest headquarter or the city where the crew change happens.

Airport

Airport acronym where crew change occurs

Cost center

Defines if the operational unit has a default cost center, in case it utilizes more than one cost center, it is recommended to leave this option empty.