JL Usage Info.

The number of revisions made for the Journey Log after generating the Flight Sheet but before confirmation.

Parameter Info.

Indicates the number of modifications made.

Billing Parameter

The usage related billing parameter based on the billing head that is available in the Contract / Revision #.

Time Ref.

The UOM of the Billing Parameter, which could be any of the following:

• Engine Time if the “Per Block Hour” is the Billing Parameter.

• Flight Time if “Per Flight Hour” is the Billing Parameter.

No. of Trips

The number of trips the flight has flown.

Note: The system displays value in this field based on the option setting in the “Edit Pricing & Invoicing Info” link page in the Manage Flight Contract activity of the “Flight Contract” business component. More…

I.

Indicates amendments made to the Journey Leg # in the Flight Sheet #, which could be M – Modification, D – Deletion.

Dir.?

Indicates that the record is a direct flight sheet i.e. whether journey information has been received directly. Data selection in this field is mandatory for direct flight sheet.

Leave this field blank if the Flight Sheet is Journey based.

Journey Log #

The number identifying the journey log.  Mandatory.

Amd. #

The code identifying the latest amendment number of the flight sheet.

Journey Leg #

The code identifying the journey leg applicable for the Journey Log # and Amendment #.

Start Time Ref.

The start time reference of the journey.

·         Eng. Start Time - Indicates either of the following:

1.     That the ‘Operating Charges  Usage’ combination is based on Block Hours and “No” is set for the parameter 'Exclude Engine Start to Taxi Out Time from Block Hours for billing” the “Parameters” tab page of the “Edit Pricing  & Invoicing Info.” activity under the “Flight Contract” business component..

2.     Taxi Out Time is not available in the “JL Usage” tab page in the “Manage Flight Sheet” activity.

·         Taxi Out Time - Indicates either of the following:

1.     That the ‘Operating Charges – Usage’ is based on Block Hours and “Yes” is set for the parameter 'Exclude Engine Start to Taxi Out Time from Block Hours for billing” the “Parameters” tab page of the “Edit Pricing  & Invoicing Info.” activity under the “Flight Contract” business component..

3.     Taxi Out Time is available in the JL Usage tab page in the “Manage Flight Sheet” activity.

·         Take Off Time – Indicates that the ‘Operating Charges - Usage is based on Flight Hours and “Not Applicable” is set for the parameter 'Exclude Engine Start to Taxi Out Time from Block Hours for billing” in the “Parameters” tab page of the “Edit Pricing & Invoicing Info.” activity under the “Flight Contract” business component.

From Date - UTC

The date on which the journey leg begins. Mandatory.

Ensure that the date entered in this field is equal to or later than the flight date From Date and earlier than or equal to the flight date To Date.

Note that the system allows modifications to this field if the Flight Sheet is journey based.

From Time - UTC

The time at which the journey leg begins. Mandatory.  Data entry in this field is mandatory if “To Time” is specified.

End Time Ref.

The edn time reference_of the journey.

• Eng. Stop Time - Indicates that the ‘Operating Charges – Usage’ combination  is based on Block Hours and “Yes” or “No” is set for the parameter 'Exclude Engine Start to Taxi Out Time from Block Hours for billing” in the “Parameters” tab page of the “Edit Pricing & Invoicing Info.” activity under the “Flight Contract” business component.

• Landing Time - Indicates that the ‘Operating Charges – Usage’ combination is based on Flight Hours and “Not Applicable” is set for the parameter 'Exclude Engine Start to Taxi Out Time from Block Hours for billing” in the “Parameters” tab page of the “Edit Pricing & Invoicing Info.” activity under the “Flight Contract” business component. stop:���u�,

To Date - UTC

The date on which the journey leg ends. Mandatory.

Ensure the following:

• The date entered in this field is later than the From date – UTC

• The date entered in this field is equal to the From date – UTC in the multiline and equal to or earlier than the flight date To Date.

The system allows modifications to this field if the flight sheet is “Journey” based

To Time - UTC

The time at which the journey leg ends. Mandatory. Data entry in this field is mandatory if “From Time” is specified.

Ensure that the value entered in this field is later than the From Time - UTC

Value(In Hours)

The total number of hours spent on the journey applicable for the Journey Log #.

Value(In Decimals)

The total number of hours in decimals spent on the journey applicable for the Journey Log #.

Mod. Value(In Hrs)

The modifications made to the journey details. Data entry in this field is mandatory if both From Time and To Time is not specified.

Ensure that the value entered in this field is equal to or greater than “0”.

Mod. Value(In Decimals)

The modified value (Hrs) converted in decimals before applying the rounding off policies.

Example: The system displays the value as 2.50 in this field if the journey time is two and a half hours for the given date and time ranges.

Data entry in this field is mandatory if both “From Time” and “To Time” is specified.

R. off Value (In Hrs)

Round off value in hours spent on the journey in hours.

R. off Value (Decimals)

Round off value of hours spent on the journey in decimals.

Note that the system applies rounding off policies based on the contract that is evaluated.

Flight Ops. Type

The flight operation type which could be any of the following:

• Regular - Indicates that the flight is used for regular flight operations.

• Test Flight - Indicates that the flight is used for test flight operations.

• Training - Indicates that the flight is used for training flight operations.

• Ferry - Indicates that the flight is used for ferrying flight operations.

• Positioning – Indicates that the flight is used for positioning flight operations.

• Others – Indicates that the flight is used for operations, other than the above flight operation types.

Flight Category

The category to which the flight belongs.

Sys. Billable?

Indicates if the billing head is included in the Contract / Revision which could “Yes” or “No”.

Billable?

Indicates whether the journey information is billable to the customer, which could be “Yes” or “No”. Mandatory.

By default the system leaves this field blank.

Remarks

Any comments pertaining to the journey log. Mandatory.

Modification Comments

Indicates that the user wishes to modify data that is received from EFB. Data entry in this field is mandatory if EFB / JL data has been modified.

Flight Status

The status of the flight, which could be ”On Schedule”, ”Delayed”, “Cancelled”, “Substituted”, “Air Turned Back”, “Ground Turned Back” “Diverted” or “Deleted”.

Journey Log Category

The category to which the journey log belongs.

JL Rep. Time Zone

Indicates the time zone to which the journey belongs.

Departure Station

The station from which the journey begins.

From Date

The date on which the leg of the journey starts. Mandatory.

Ensure that the date entered in this field is the same or later than the flight From Date and earlier than the same as the flight To Date

From Time

The time at which the leg of the journey starts. Mandatory.

Arrival Station

The destination station of the flight.

To Date

The date on which the leg of the journey ends. Mandatory.

Ensure that the date entered in this field is later than the From Date.

Ensure that the date entered in this field is the same as the From Date in the multiline or earlier than or the same as the flight To Date

To Time

The time at which the leg of the journey ends. Mandatory.

Ensure the following:

• The time entered in this field is later than the “From Date”.

• The time entered in this field cannot be modified if the flight sheet is Journey Based.

Apply JL Revisions

Check this checkbox to apply all the revisions or modifications made to the flight log after generation of the Flight Sheet.