Creating journey log

This page allows you to create a journey log.  Tell me more

• Select the “Create Journey Log” link under the “Flight Log” business component.

The “Create Journey Log” page appears.

The system displays the following field:

The system displays the following fields in the “Log Details” group box:

• Enter the following:

Note: You can leave this field blank, only if the numbering type or the default numbering type is set for the journey log transaction, in the “Create Numbering Type” activity of the “Document Numbering Class” business component.

The system displays the following:

•  Enter the following:

•   Enter the following in the “Aircraft Details” group box:

• Click the “Get Details” pushbutton to retrieve the leg details and summary parameter details pertaining to the aircraft registration number.

On clicking the “Get Details” pushbutton, the system retrieves parameter values for which the source is ‘Flight Log’, from the “Aircraft” business component, into the “Leg Details” and "Summary Parameter Details" multiline. This retrieval of Summary Parameter Details fetching  is based on the latest leg’s  “Arrival Date”, and “Arrival Time”, if leg information is entered or the “Flight Date", if leg information is not entered.

On clicking the “Get Details” pushbutton, the system ensures that at least one the following conditions in the table given below, is satisfied for the Aircraft Reg # entered:

Usage Mode: ‘Usage Mode’ is a process parameter defined in the "Configurator” business component to indicate whether the system is being operated from the main base or remote base to record OFMS transactions.

Mode of Usage: ‘Mode of Usage’ is defined in the “Aircraft” business component to indicate the location of the aircraft. Mode of Usage is said to be “Online” if the aircraft is located in the main base and “Offline” if the aircraft is in a remote base.

The system displays the following in the “Log Reference Details” group box:

Note: On clicking the “Create Log” pushbutton, the system displays the total flight hours as the sum of the time spent on each leg of the journey. The total take-offs is calculated as the sum of take-offs of each leg of the journey.

To proceed carry out the following:

• Select the “Leg Details” tab to enter the  leg details for the journey log.

• Select the “Summary Parameter Details” tab to enter the parameter details of journey log

• Enter the following in the “Operational Details” group box:

The system displays the following in the “Computed Flight Parameters” group box:

The system checks for the parameters definition in the ‘Maintain Journey Log Parameter Information’ activity of the “Aircraft” business component, of the “Aircraft Model #” and “Configuration Class combination, for the “Aircraft Reg #” on which the journey log is created.

If parameter definition is not available for the “Aircraft Model #” and “Configuration Class” combination, the system checks for the leg-wise parameter definition for the “Model #” alone, of the “Aircraft Reg #” on which the journey log is created.

If parameter definition is not available for the “Aircraft Model #”, then the system checks for the leg-wise parameter definition at the generic level , that is , when the “Aircraft Model #” and “Configuration Class”  combination is left blank in the ‘Maintain Journey Log Parameter Information’ activity of the “Aircraft” business component.

Note: For the defined parameters, if position code is not available, then the system considers the parameter applicable for the aircraft. If position code is available, and component is attached at that position, then the system considers the parameter applicable for component level. If component is not attached, then the system considers the parameter is applicable for part level.

If the leg-wise parameter in ‘Maintain Journey Log Parameter Information’ activity of the "Aircraft" business component, is not applicable for the aircraft registration number or attached component or part of the aircraft on which the journey log is created, then the system displays the following:

• Not Set - The parameter has not been set. For example, if the definition is available for “Parameter1” and “Parameter2”  and no definition is available for “Parameter3” to “Parameter6” , then system displays “Not Set” .

• Not Defined – The system displays “Not Defined” when the defined parameters in the ‘Maintain Journey Log Parameter information’ activity of the aircraft business component, is not applicable as aircraft or part or component level parameters.

For example, if the defined parameter in the “Maintain Journey log Parameter Information” activity of the aircraft business component, is identified as aircraft parameter, and if its not applicable for the “Aircraft Reg#” on which the journey log is created or the defined parameter in the “Maintain Journey log Parameter” activity of the “Aircraft” business component is identified as component or part level parameter, and if its not applicable for the attached component number or part number of the aircraft registration number on which the Journey log is created, then the system displays the following:

• Not Updateable – The system displays this, when the defined parameters in the ‘Maintain Journey Log Parameter information’ activity of the "Aircraft" business component, refers a source as other than ‘Flight Log’.

For example, if the parameter ‘Param1’ is defined in the “Maintain Journey Log parameter Information’”activity of the “Aircraft” business component, and is applicable to aircraft, but the source defined is not ‘Flight log’, then system displays “Not Updateable”.

• Position Not Available – The system displays this when the defined position in the “Maintain Journey Log Parameter information” activity of the “Aircraft“business component, is not available in the configuration for the aircraft on which the journey log is created.

For example, If the position ‘Pos1’ is defined in the “Maintain Journey Log parameter Information” activity of the “Aircraft” business component, and this position is not identified as first level position in the aircraft configuration for the aircraft on which journey log is created.

• Position Inactive – The system displays this when the defined position in the ‘Maintain Journey Log Parameter information” activity of the “Aircraft” business component, is available in the configuration for the aircraft  on which the journey log is created, but the position code status is set as ‘Inactive’.

For example, If the position ‘Pos1’ is defined in the “Maintain Journey Log parameter Information” activity of the “Aircraft” business component, and this position is also identified as first level position in the aircraft configuration for the aircraft on which journey log is created, but if the position code status is set as ‘Inactive’, then system displays ’Position Active’.

• Not available - The system displays this, if no parameter definition is available in the “Maintain Journey Log Parameter” activity of the “Aircraft “ business component, for the aircraft on which Journey log is created for all the leg-wise parameters.

Note: The system displays ‘Not Available’ for all the leg-wise parameters, when no parameter is defined at the generic level.

Note: If the parameter values in the “Computed Flight Parameters” group box is "Not Set", "Not Defined", "Not Updateable", "Position Not Available", "Position Inactive", "Not Available" or "Definition not Available", then the corresponding fields in the “Summary Parameter Details” multiline must be left blank.

Note: Ensure that the “Arrival Station” is entered, if the “Departure Time” and “Departure Time” fields are entered.

On clicking the “Create Log” or “Approve log” pushbutton, the system displays “1”, if the “Flight Duration” field is left blank or if “Flight Duration” is equal to the difference between “From Date & Time” and “ To Date & Time”.

Note: Ensure that the “Flight Duration” is zero when the “Take Offs” is zero.

Ensure that the journey leg timings do not overlap with each other within the same journey log as well as across the journey logs, for the same aircraft registration number, if “FH Log Mode” is set as “Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component.

For example, for Journey Log ‘JL001’, if a leg has been reported between ‘11:00’ hours and ‘13:00’ hours on 17 August, 2004, then, in the same journey log, another leg cannot be reported between ‘12:30’ hours and ‘14:15’ hours, for the same date. If a leg has been reported between ‘11:00’ hours and ‘13:00’ hours on 17 August 2004, then, in a different journey log  ‘JL002’, a leg cannot be reported between ‘12:30’ hours and ‘14:15’ hours for the same aircraft registration number on the same date (17 August, 2004).

•  Enter the following in the “Document Attachment Details” group box:

•   Click the “View File” link to view the contents of the attached file.

To create journey log

• Click the “Create Log” pushbutton to create the journey log.

Transferred aircraft: You cannot create a journey log for an aircraft that has been transferred to another operating unit for maintenance. The system allows for log creation upon return of the aircraft.

The system ensures that no other journey log is entered for the same period for the aircraft registration number. The system creates the journey log number based on the numbering type, and sets the status of the created journey log as “Fresh”.

The system updates the “Departure Date”, “Departure Time”, “Arrival Date” and “Arrival Time” for the flight, leg and flight date combination.

Note: The system considers the arrival date of the preceding leg as the departure date for the next leg of the aircraft, if the Flight Status of the previous flight (leg) is other than “Cancelled” or “Substituted”.

If the “Flight Status” for a flight and leg combination is set to “On-Schedule” and if “Departure time” is not entered, the system considers the “Sch. Departure Time” as the “Departure Time”. If the “Departure Date” is not entered, the system updates the departure date as the “Flight Date”.

Note: If the “Departure Time” is not entered, the system considers the “Sch. Arrival Time” as the “Arrival Time”. If “Arrival Date” is not specified, the system calculates the arrival date as the sum of departure date and block hours.

If the “Flight Status” for a flight and leg combination is “On-Schedule” or “Delayed” and if the “Arrival Station” is not entered, the system stores the arrival station defined for the flight and leg combination in the “Flight Assignment” business component as the “Arrival Station”, if the “Flight Details Validation Basis” is set as "Required" in the Set Options activity of the current business component.

If the “Update Mode” is “Delta”, the system sums up the parameter values for all legs of the journey and displays the total for the corresponding parameter in the “Computed Flight Parameters” group box. For example, if a journey has three legs and the values for “Parameter 1” field of the first, second and third leg of the journey is ‘2’, ’5’ and ‘4’ respectively, the “Parameter 1” field in the “Computed Flight Parameters” group box will display ‘11’ as the parameter value. 

If the “Update Mode” is “New”, the system displays the parameter of the last leg in the corresponding parameter field of the “Computed Flight Parameters” group box. For example, if a journey has three legs and the value for “Parameter 1” field for the first, second and third leg of the journey is ‘2’, ‘5’ and ‘4’ respectively, the “Parameter 1” field in the “Computed Flight Parameters” group box will display ‘4’ as the parameter value.

Note: Once the journey log is created, you can record discrepancies in the “Record Pilot reported discrepancies” page. These discrepancies will also be recorded in the “Discrepancy Processing” business component and the record status of these discrepancies is set to “Fresh”.

Note: If delay details are not recorded for the journey log, then the system updates the “Flight Status” as “On Schedule”.

Note: The parameters must be mapped to the “Hobbs Meter Reading” base parameter as defined in the “Aircraft” business component, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg #.

If the "FH Log Mode" is set as "Actual Flight Times" for the Aircraft Reg #, then the system calculates the following for each row in the Leg Details multiline with reference to UTC:

a. Arrival Time = Departure Time + Flight Hours. If the value of “Arrival Time” is greater than 24:00 hrs, then the “Landing Time” as difference of Departure Time and Flight Hours.                                                                                                                     

b. Arrival Date = Departure Date + Flight Hours. If the “Arrival Time” is later than the “Departure Time” and less than 24:00 hrs, then the “Arrival Date” is the same as “Departure Date”. If the “Arrival Time” is earlier than the “Departure Time”, then the “Arrival Date” is one day later than the “Departure Date”.

c. If the “Flight Hours” is more than 24 hours, then the “Arrival Date” is the addition or subtraction of quotient  of the Flight Hours by 24 to the “Departure Date”.  For ex: If Departure Date is 15/11/2006, FH = 23:00 hrs, then Landing Time = Arrival Time.

Note: If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg # as defined in the “Aircraft” business component, and if there is a manual new mode re-initialized entry for the Parameter which is mapped to “Hobbs Meter Reading” base parameter, later to the Arrival Date and Arrival Time of the Latest Journey Log # in “Confirmed” status  for the Aircraft Reg #, the system allows the creation of a Journey Log with the Hobbs-In value less that or equal to re-initialized value. E.g. If there is a Journey Log with Hobbs-Out as 100 and Hobbs-In as 120 in “Confirmed” status with Arrival Date as 15/11/2006 and Arrival Time 10:00 hrs and if user updates the Parameter mapped to Hobbs Meter Reading base parameter with a value 110 with As On Date as 15/11/2006 and As On Time as 11:00 hrs, then a system allows creation of Journey Log  with Hobbs-Out/In value greater than or equal to 110.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, and if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component, then the system ensures one preceding record is entered in the “Flight Hours” column for each row in the Leg Details multiline.

Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and if the departure date and departure time are entered, the system calculates the Arrival Time and Arrival Date as given below:

a) Arrival Time = Departure Time + Flight Hours. If the value for Arrival time is greater than 24:00 hrs, then the Arrival time is 02.00 hrs for the Departure Time = 23:00 hrs and FH = 3:00.

b) Arrival Date = Departure Date +Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Arrival Date is the same as Departure Date.

c)  If Arrival Time is earlier than the Take-Off Time, then the Arrival Date is one day later than the Departure Date.

Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and if the arrival time and arrival date are entered, the system calculates the Departure Time  and Departure date  as given below:

a) Departure Time = Arrival Time - Flight Hours. For E.g. If the value for Arrival Time is negative, the Arrival Time = 06:00 hrs, FH = 8:00, then the Departure Time = (06:00-08:00)+24 = 22:00 hrs.

b) Departure Date = Departure Date - Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Departure Date is the same as Arrival Date

c)  If Arrival Time is earlier than the Departure Time, then the Departure Date is one day earlier  than the Departure Date.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if no value is entered in the Departure Date, Departure Time, Arrival Date and Arrival Time, then the system copies the Arrival Date and Arrival Time of the preceeding leg as the Departure Date and Departure Time for current record.

The system performs the following on clicking the “Create Log” pushbutton:

• If the flight status is set as “On Schedule”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b)The  difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the set limit for Delay Duration.

• If the flight status reported for the journey log is “Delayed”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the set limit for Delay Duration.

Note: The system considers the “Reportable Delay (In Minutes)” as the Delay Duration, if defined in the “Reliability Analysis” business component. Otherwise, the system considers the “Delay Duration (In Minutes)” defined in the “Aircraft Reliability” business component as the Delay Duration.

• Computation of NSD / NSV based on ‘Change Type’:

1. If the ‘Change Type’ is set as “Correction”, on modification of interval or correction of complied value from ‘Compliance History’ or modification of journey Log, NSV is recomputed based on:

1. • Threshold value or Repeat Interval if task is not complied at least once.

   • ‘Update Basis’ (Time Window, Schedule or Actual Completion) set in the last instance of compliance.

2. If the ‘Change Type’ is set as “Correction”, on modification of interval or correction of Complied Date and Time from ‘Compliance History’, NSD is recomputed based on:

1. 3. "Reference Basis" (Induction or Operational date) if task is not complied at least once.

   4. ‘Update Basis’ (Time Window, Schedule or Actual Completion) set in the last instance of compliance.

3. If the ‘Change Type’ is set as “Re-baseline”, on modification of interval:

• On re-baseline of LPD / LPV, NSD / NSV, on change of Journey log, NSD / NSV must not be recomputed.

Note: If any open escalation exists for tasks in aircraft program, on modification of Journey Log, the system recomputes the Next Due Value, and the new due value is updated in escalation records.

3. Update of computation basis controls - Post Compliance

To approve journey log

•  Click the “Approve Log” pushbutton to approve the journey log.

Transferred aircraft: You cannot approve a journey log for an aircraft that has been transferred to another operating unit for maintenance. The system allows for log approval on upon return of the aircraft.

The system sets the status of the journey log to “Approved”.

Once a journey log is approved, the respective aircraft details are updated with the parameter values entered in this page. If a component is attached to the aircraft, then the parameter values are updated to the component as well.

Note: The system allows approval of the journey log only if the user login ID is granted the necessary access rights for ‘approval’. Once the journey log is approved, the record status of the discrepancies is set to “Pending” in the “Discrepancy Processing” business component.

On approval of the journey log, the system updates the Flight Details, Interruption Details and Delay Summary Details in the “Regularize Operational Interruption Details” page.

The system re-computes the Last Performed Value of work units by adding the recorded journey log parameter or flying hours, whichever applicable, along with the history details, if those work units of the 'Aircraft Maintenance Program' or ' Component Maintenance Program' have been complied with, provided the last leg's date and time of the journey log is earlier than the last compliance date and time of the work unit. If the work unit is repetitive, the 'Next Schedule Value' is also recomputed based on the updated last performed value.

For example, if there is a work unit with a floating interval of flying hours, which has a periodicity of 50 hours, and the compliance date of the work unit is on 15th Dec 2004, the last complied value is 110 and the Next Schedule Value is 160. When a back-dated journey log is created on 14th Dec 2004 with a flying hours update of 5 hours, the ‘Last Performed Value’ will be recomputed as 115 and the ‘Next Schedule Value’ will be updated as 165.

If the aircraft has any discrepancies (Maintenance Reports) in "Deferred" status with usage based limits set, when a back-dated journey log is approved before the deferral date and time of that discrepancy, the system re-computes the threshold value for the discrepancy deferral by adding the updated parameter values to it.

The system performs the following on clicking the “Approve Log” pushbutton.

• Ensures that Journey Log is not available in “Fresh” status for the Aircraft Reg # in header level, If the “Enforce Sequential Reporting of Journey Log” is set as "Allowed" in the “Set options” activity of the current business component.  

• Ensures that the positive numeric values are entered in the “Parameter Value” column for each row of the Summary Parameter Details multiline, if the “Parameter Type” is “Range” or “Consumption”.

• Creates a Journey Log with the Hobbs-In value less that or equal to re-initialized value, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg # as defined in the “Aircraft” business component, and if there is a manual new mode re-initialized entry for the Parameter which is mapped to “Hobbs Meter Reading” base parameter, later to the Arrival Date and Arrival Time of the Latest Journey Log # in “Confirmed” status  for the Aircraft Reg #. E.g. If there is a Journey Log with Hobbs-Out as 100 and Hobbs-In as 120 in “Confirmed” status with Arrival Date as 15/11/2006 and Arrival Time 10:00 hrs and if user updates the Parameter mapped to Hobbs Meter Reading base parameter with a value 110 with As On Date as 15/11/2006 and As On Time as 11:00 hrs, then a Journey Log is created with Hobbs-Out/In value greater than or equal to 110.

• Ensures that the journey leg timings do not overlap with each other within the same journey log as well as across the journey logs, for the same aircraft registration number, only if “FH Log Mode” is set as “Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component.

If the "FH Log Mode" is set as "Actual Flight Times" for the Aircraft Reg #, then the system calculates the following for each row in the Leg Details multiline with reference to UTC:

a) Arrival Time = Departure Time + Flight Hours. If the value of “Arrival Time” is greater than 24:00 hrs, then the “Landing Time” as difference of Departure Time and Flight Hours.                                                                                                    

b) Arrival Date = Departure Date + Flight Hours. If the “Arrival Time” is later than the “Departure Time” and less than 24:00 hrs, then the “Arrival Date” is the same as “Departure Date”. If the “Arrival Time” is earlier than the “Departure Time”, then the “Arrival Date” is one day later than the “Departure Date”.

c) if the “Flight Hours” is more than 24 hours, then the “Arrival Date” is the addition or subtraction of quotient  of the Flight Hours by 24 to the “Departure Date”.  For ex: If Departure Date is 15/11/2006, FH = 23:00 hrs, then Landing Time = Arrival Time.

Note: The parameters must be mapped to the “Hobbs Meter Reading” base parameter as defined in the “Aircraft” business component, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg #.

Note: If the “FH Log Mode” is set as “Hobbs Meter Reading” for the Aircraft Reg #, then ensure that the “Hobbs-In” field is not blank for each row in the Leg Details multiline.

Note: If the “FH Log Mode” is set as "Actual Flight Hours" and the “Enforce Sequential Reporting of Journey Log” is set as "Allowed" in the current business component, then ensure that the “Departure Date” and “Departure Time” of each record is not earlier than the “Arrival Date” and “Arrival Time” of the last leg of the latest preceding journey log for the Aircraft Reg #.  

Note: The system consolidates the Flight Hours calculated for each of the preceding leg # (including the current leg record) till the preceding leg for which “Maint. Execution” is set as "Yes" if the “Maint. Execution” is set as “Yes”, consolidates the Flight Hours recorded for the preceding legs # (including the last leg) till the preceding leg for which “Maint. Execution” is set as “Yes” if the “Maint. Execution” is set as “No”, and consolidates and updates the FH for all the legs with the last leg reference in the “Aircraft Parameter Master” business component if none of the leg is identified with “Main. Execution” as  “Yes”.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, and if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component, then the system ensures one preceding record is entered in the “Flight Hours” column for each row in the Leg Details multiline.

 Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if the departure date and departure time are entered, the system calculates the Arrival Time and Arrival Date as given below:

a) Arrival Time = Departure Time + Flight Hours. If the value for Arrival time is greater than 24:00 hrs, then the Arrival time is 02.00 hrs for the Departure Time = 23:00 hrs and FH = 3:00.

b) Arrival Date = Departure Date +Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Arrival Date is the same as Departure Date.

c)  If Arrival Time is earlier than the Take-Off Time, then the Arrival Date is one day later than the Departure Date.

Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if the arrival time and arrival date are entered, the system calculates the Arrival Time and Arrival Date as given below:

a) Departure Time = Arrival Time - Flight Hours. For E.g. If the value for Arrival Time is negative, the Arrival Time = 06:00 hrs, FH = 8:00, then the Departure Time = (06:00-08:00)+24 = 22:00 hrs.

b) Departure Date = Departure Date - Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Departure Date is the same as Arrival Date

c)  If Arrival Time is earlier than the Departure Time, then the Departure Date is one day earlier  than the Departure Date.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline If no value is entered in the Departure Date, Departure Time, Arrival Date and Arrival Time, then the system copies the Arrival Date and Arrival Time of the preceeding leg as the Departure Date and Departure Time for current record.

Note: The system considers the arrival date of the preceding leg as the departure date for the next leg of the aircraft, if the status of the previous flight is other than “Cancelled” or “Substituted”.

The system performs the following on clicking the “Approve Log” pushbutton:

• If the flight status is set as “On Schedule”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b)The  difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the Delay Duration.

• If the flight status reported for the journey log is “Delayed”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the Delay Duration.

Note: The system considers the “Reportable Delay (In Minutes)” as the Delay Duration, if defined in the “Reliability Analysis” business component. Otherwise, the system considers the “Delay Duration (In Minutes)” defined in the “Aircraft Reliability” business component as the Delay Duration.

On approval of journey log, if the Parameter mapped to ‘Flight Days’ base parameter is mapped to the Aircraft Reg #, then system update the Flight Days parameter value based on the following:

1. Date option provided for ‘Date for Flight Day update’ option in the Set option activity of Flight log business component is ascertained. Date options may be ‘Flight Date’ or ‘Departure Date’ or ‘Arrival Date’ or ‘Take off date’.

2. Flight Status to be considered for Flight Day parameter update are ascertained from the Flight Day Computation options in Flight log business component

3. Flight Operation Types to be considered for Flight Day parameter update are ascertained from the Flight Day computation options in Flight log business component.

4. For the Date value provided in the Date option ascertained as mentioned above, as mentioned

a. If the ‘Flight Status’ of the Journey Log – Leg is considered for Flight Day update and

b. If the ‘Flight Operations Type’ of the Journey Log is considered for Flight Day update and

c. If the Journey Log getting approved is the first Journey log document (i.e no other Journey log exists in Approved status for that Date), then system updates the Flight Day parameter value as 1 for that Date.

Example: For Aircraft Reg # VT-JAN, let there be a new journey log JL1 created with Flight Date as ‘01/01/2009’. The Journey log – leg details be as follows:

Let following be the options set for ‘Flight Day Computation options’ in the Flight log business component

Based on the above given options settings, assuming that JL1 is the first Journey Log created on 02/01/2009,(02/01/2009 is considered since Departure Date is set as ‘Date for Flight Date update) on approval, system will update the Flight Day parameter value as “1” for the date 02/01/2009

Note:

1. The date for which the “Flight Days” parameter to be updated should be identified from the set options “Flight Day computation basis” in the current business component.

2. Journey Log – legs for which the Flight Operations Type and Flight Status identified as “Include” in the set options “Flight Day computation basis” in the current business component will only be  considered for Flight Day update

3. If the “Flight Days” parameter is incremented already for the considered date as per the set option by the any other journey log, then it will not be incremented by 1 in the Parameter history for the Aircraft reg # on approval of  the current Journey log.

Automatic Approval based on Workflow configuration

• The journey log is automatically routed to the next level of approval, if CIM interaction exists between Workflow Management and Flight Log.

• For the above to occur, the login user must have the requisite permission to approve the journey log or must be a first-level approver for the journey log. If the login user is a first-level approver, the journey log moves to the second–level of approval and the status changes to “Pending Approval”. If the next level of approval is the last in the approval workflow, the status becomes Approved on approval.

• The approval workflow gets terminated on cancellation of journey log.

To proceed, carry out the following

• Select the “Edit Journey Log” link to modify the journey log details.

• Select  the “Report Operational Interruption Details” link to update delay details.

Note: You can launch this page only if the journey log is not “Approved’ or “Cancelled”.

• Click the “Record Pilot Reported Discrepancies” link to update pilot reported discrepancies.

Note: The above links cannot be launched if the journey log is “Approved”.

• Select the “Report Inflight Shut Down Hours” link to report the engine shut down and restart details

• Select the “Report Cabin Crew Details” link to report the details of the cabin crew.

• Select the “Record Aircraft Maintenance Execution Details” link to record the aircraft maintenance execution details for an aircraft.

Note: The “Record Aircraft Maintenance Execution Details” link is not displayed for Offline Usage. (i.e. ‘Usage Mode’ set as “Offline” in the “Configurator” business component.)

Creating journey log – An overview

In this page, you can enter the journey log information. A unique journey log number will be generated by the system, based on the numbering type that you select in this page. You can enter the flight date, the time zone for the journey and the station where the journey log begins.

You can record the aircraft registration number for which the journey log details are entered.

You must enter the station where the leg of the journey begins and the station where it concludes. Parameter details for each leg of the journey, the number of passengers and take offs can be specified. The parameter value for the position code and the position type can be entered.

The system creates the journey log details and assigns a “Fresh” status to the created journey log.

What you can do in this page

Choose a numbering pattern to generate the journey log number

Specifying the aircraft registration number

Specifying the parameter value

Choose a numbering pattern to generate the journey log number

You can select a numbering type for the journey log. A unique journey log number will be generated by the system based on the numbering type you select in this page.

•   Select the numbering type in the “Numbering Type” drop-down list box.

•   Enter all other journey log details.

On clicking the “Create Log” pushbutton, the system generates the journey log number using the selected numbering type.

Specifying the aircraft registration number

You can specify the registration number of the aircraft for which journey log details are to be recorded, in the “Aircraft Reg# field”.Specifying the parameter value

You can enter the parameter value for a part number based on its position code.

• Enter the “Parameter Value” field in the “Summary Parameter Details” multiline.

Specifying the parameter value

You can enter the parameter value for a part number based on it’s its position code. In

Enter the “Parameter Value’” field in the “Summary Parameter Details” multiline.