Recording sign-off and work completion details
This page allows you to sign-off the tasks / sub tasks in bulk. The sign-off details are retrieved based on the search item such as task number, task description, ATA number, work area, zone, skill and execution. Sign-off can be performed either by mechanic, inspector or mechanic and inspector, RII. RII sign-off is performed only at task level.
You can specify whether the task is completed on successful completion of the sign off, indicate the date and time at which the task is to be completed and update the sign-off and work completion details.
Click the icon in the “Work Information”
section of the “Record Aircraft Maintenance Execution Details”
page.
The “Record Sign-Off & Work Completion” page appears. The sign-off details are displayed at sub task level during the page launch.
Note: This page can be invoked only for tasks with the 'Execution Status' set as "Planned", "In-Progress", "In-Complete", "Completed" or "Deferred" and tasks whose Job Type is other than “Off-Wing”.
The system displays the following field:
Date & Time |
The compliance date and time of the aircraft. The date and time displayed in the “Record Aircraft Maintenance Execution Details” screen will be defaulted here. |
The system displays the following in the “Execution Document Details” group box:
Execution Ref # |
The system displays the Package Type of the Execution Ref # in this field. The Execution Ref # is displayed alongside and is hyperlinked to display the execution reference details. The Execution Ref # must be in status other than “Closed” or “Cancelled”. |
Click the hyperlinked Execution Ref # to view the execution reference details.
Status |
The status of the Execution Ref #, which could be “Planned”, “In-Progress” or “Completed”. |
Aircraft Reg # |
The aircraft registration number identified for the Execution Ref #. |
Work Center |
The primary work center of the Execution Ref #. |
The system displays the following in the “Flight Hours / Cycles” group box:
Flt. Hrs |
The flying hours of the aircraft, as displayed in the “Record Aircraft Maintenance Execution Details” screen. |
Flt. Cycles |
The flying cycles of the aircraft, as displayed in the “Record Aircraft Maintenance Execution Details” screen. |
Enter the following fields in the “Search Option” group box:
Note: This group box appears collapsed on launch of the page.
Search Item |
Use the drop-down list box and select one of the following values based on which the sign-off details of the tasks which are in status “Planned”, “In-progress", "Incomplete" and "Completed" in the Execution Ref # available in the header, are retrieved in the multiline. An input box is provided alongside in which the values corresponding to the item selected in the drop-down list box are entered. This value is entered in full or specified partially using the characters “,” (comma), “:” ( Colon) or “;” (Semi-colon).
If a value is selected in the drop-down list box and if no value is entered in the adjacent field, then system retrieves all the tasks which are having sign off details and which are in status “Planned”, “In-progress”, "Incomplete" and "Completed". The system displays “Task #” by default. |
Sign-Off Status |
Use the drop-down list to select the sign-off status of the task. The system lists the following values if the ‘Display Option’ is set as “Task level”:
If the ‘Display Option’ is set as “Subtask level”, the system lists all the above values except “Pending RII”. By default, the system displays “Not Required” if the sign-of requirements are identified as “Not Required” for all the tasks within the package. Else, the system displays “Pending Signoff”, by default. |
Display Option |
Use the drop-down list box and select the option for displaying the sign-off details. The system lists the following values:
The system displays “Subtask level”, by default. |
Click the “Search” pushbutton to retrieve the sign-off details.
For the task # available in the “Search Item” drop-down list box, the system retrieves the sub tasks based on the “Sign-Off Status” selected and the Package Type parameter “Allow sign-off entry by different employee” set in the “Set Process Parameters” page of the “Common Masters” business component, as shown in the table below:
Sign-Off Status |
Package Type parameter - ‘Allow sign-off entry by different employee’ |
Values retrieved in multiline |
Pending Sign-Off
|
Yes |
Retrieves all the sub tasks which are having 'Pending Mechanic', 'Pending Inspector' and "Pending Mechanic & Inspector' signoff statuses. |
No |
Checks the option set for the parameter “Permit Dual Sign-off by the employee?” in the “Commons Masters” business component and Retrieves the sub tasks matching the skill and resource group requirements of the employee mapped to the login user, accordingly.
Note: If the “Permit Dual Sign-Off by the employee” is set as "No", the system does not allow the same employee to sign-off as "Mechanic" as well as "Inspector" for a sub task even though the employee has Mechanic and Inspector resource group for the Skill. |
|
Pending Mechanic |
Yes |
Retrieves all the sub tasks which are having 'Pending Mechanic' sign-off status. |
No |
Retrieves the sub tasks matching the skill and resource group requirements of the employee mapped to the login user. |
|
Pending Inspector |
Yes |
Retrieves all the sub tasks which are having 'Pending Inspector' signoff status. |
No |
Retrieves the sub tasks matching the skill and resource group requirements of the employee mapped to the login user. |
|
Pending Mechanic & Inspector |
Yes |
Retrieves all the sub tasks which are having 'Pending Mechanic', ‘Pending Inspector’ and ‘Pending Mechanic & Inspector' signoff statuses. |
No |
Retrieves the sub tasks matching the skill and resource group requirements of the employee mapped to the login user. |
|
Signed-Off |
Yes |
Retrieves all the sub tasks which are having Sign-off status as “Signed Off" signoff status and which have at least one resource group signed and still in “Pending” status. |
No |
Not Applicable. |
|
Pending RII |
Yes |
Checks whether RII signoff is Pending. If yes, then system retrieves the task # into the multiline along with its consolidated sub task level signoff requirements. |
No |
Not Applicable. |
Select one of the radio buttons in the “Default Option” group box:
Action |
Select one of the following radio buttons to specify the sign-off action of the task / sub task.
By default, the button “Sign-Off” is selected. |
Enter the following in the “Default Option” group box:
Mechanic |
The code of the employee who performs mechanic sign-off. The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. Data entry in this field is mandatory, if the “Sign-Off Action” is selected as “Sign-Off” or “Void”, and if the “Mechanic” field in the multiline is left blank. The employee code entered here must have resource group “Mechanic” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
|
Inspector |
The code of the employee who performs inspector sign-off. The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. Data entry in this field is mandatory, if the “Sign-Off Action” is selected as “Sign-Off” or “Void”, and if the “Inspector” field in the multiline is left blank. The employee code entered here must have resource group “Inspector” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
|
Sign-Off Comments |
The sign-off comments recorded against the sub tasks. |
RII |
The code of the employee who performs RII sign-off. The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. Data entry in this field is mandatory, if the “Sign-Off Action” is selected as “Sign-Off” or “Void”, and if the “RII” field in the multiline is left blank. The employee code entered here must have resource group “Inspector” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
|
Addl. Sign-Off |
The code of the employee who performs additional sign-off. |
Note: The above two fields “RII” and “Addl. Sign-Off” are visible only if the “Display Option” is selected as “Task Level”.
The system displays the following fields in the “Task Sign-Off Details” multiline:
Note: The system retrieves only those tasks and corresponding sub-tasks whose associated ‘WBS Code’ has process parameter 'Execution Operations ?' set as "Yes" in the “Common Master” business component.
MPD Item # |
The MPD Item Ref. # of the subtask as defined in Maintenance Task. Note: This field displays value only if Display Option is selected as “Subtask Level”. |
Task Description |
The description of the task. |
Sub Task Description |
The description of the sub task. Note: This field is hidden if the "Display Option" is set as "Task Level". |
Ø Enter the following fields in the “Task Sign-Off Details” multiline:
Sign-Off Action |
Use the drop-down list box and select the sign-off action of the task. The system lists the following values:
By default, the system displays the value “--Select--“. |
Mechanic |
The code of the employee who performs mechanic sign-off. If the “Sign-Off Action” is selected as “Sign-Off” or “Void”, the employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. The employee code entered here must have resource group “Inspector” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
If Mechanic Signoff has to be reversed, ensure that this field is left blank and no value is specified in the “Sign-Off Action” drop down box.. |
Inspector |
The code of the employee who performs inspector sign-off. If the “Sign-Off Action” is selected as “Sign-Off” or “Void”, the employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. The employee code entered here must have resource group “Inspector” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
If Inspector Signoff has to be reversed, ensure that this field is left blank and no value is specified in the “Sign-Off Action” drop down box.. Note: A mechanic cannot reverse / revert the sign off action of an inspector. |
RII |
The code of the employee who performs RII sign-off. If the “Sign-Off Action” is selected as “Sign-Off” or “Void”, the employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. The employee code entered here must have resource group “Inspector” or “Mechanic & Inspector” mapped to at least one skill for the current date in the “Employee Personal Information” business component, if following conditions are satisfied:
Note the following: If RII Signoff has to be reversed, ensure that this field is left blank and no value is specified in the “Sign-Off Action” drop down box. This column is visible only when the display option is selected as Task Level. Note: A mechanic cannot reverse / revert the RII sign off action. |
Addl. Sign-Off |
The code of the employee who performs additional sign-off. |
Note: The above two fields “RII” and “Addl. Sign-Off” are visible only if the “Display Option” is selected as “Task Level”. |
|
Sign-Off Comments |
The sign-off comments recorded during execution of the task. Process parameter dependencies: This field becomes mandatory for
|
Dual Sign-Off permission check:
Ensure that the same employee # is not entered in the Mechanic and inspector fields in the “Default Option” group box and the multiline, if the following conditions are satisfied:
If the “Sign-Off Action” drop-down list box is set as “Sign Off” or “Void”.
If the Sign-Off status of the task is set as "Pending Mechanic & Inspector" or "Pending Inspector" or “Not Required”
If the parameter “Permit Dual Sign-off by the employee?" is set as "No" for the Package Type of the Execution Ref #, in the “Set Process Parameters” page of the “Common Masters” business component.
Different Employee Sign-Off permission check:
Ensure that the employee # available in the Mechanic / Inspector / RII fields is same as the employee mapped to the login user, if the following conditions are satisfied:
If the “Sign-Off Action” drop-down list box is set as “-Select-”.
If the “Action” radio button is selected as “Sign Off” or “Void”.
Relevant option is selected in the “Sign-Off Status” drop-down list box in the search criteria, along with the value “Not Required”
If the parameter “Allow sign-off entry by different employee?" is set as "No" for the Package Type of the Execution Ref #, in the “Set Process Parameters” page of the “Common Masters” business component.
The system displays the following fields in the “Task Sign-Off Details” multiline:
Skill |
The skill mapped to the employee, for sign-off requirement. Alternately, the skill required for the corrective action against the discrepancy. |
Sign-Off Status |
The sign-off status of the task, which could be Signed Off, Pending RII, Pending Mech&RII, Pending Insp&RII, Pending Mech,Insp&RII, Pending Insp (Mech Voided), Pending RII (Mech Voided), Pending RII (Insp Voided), Pending Insp&RII (Mech Voided), Pending RII (Mech&Insp Voided) or Signed Off (Voided). For more details, see How the system derives Sign-Off Status of tasks. |
Previous Sign-Off Comments |
The previous sign-off comments. |
Task # |
The code identifying the task. |
Task Seq # |
The order of execution of the task within the package. |
Sub Task Seq # |
The order of execution of the sub task within the task. Note: This field will be available only if the “Display Option” field is set as “Subtask Level”. |
Enter the following in the “Update Option” group box:
Change Status to Completed |
Use the drop-down list box and specify if the status of the task is changed to “Completed”. The system lists the options “Yes” and “No”. By default, the system displays “Yes”. |
Compliance Date & Time |
The date and time at which the task is completed. (Date & Time Format). By default, the system displays Execution Date and Time of the Execution Reference, if the page is launched from Record Aircraft Maintenance Execution Reference interface. Process Parameter dependency: The system does not save Compliance Date & Time when a discrepancy is deferred, if the process parameter "Compliance update required when Discrepancy is Deferred?" is set as '0' for 'Not Required' under the entity type Package Type and the entity “All User Defined Package Types including Log Cards” in the Define Process Entities activity of Common Master. As a result of this, the deferred discrepancy will not appear in the “Track Maintenance Compliance History” page as Compliance is not updated for the same. However, if "Compliance update required when Discrepancy is Deferred?" is set as 1 for Yes, compliance will be updated when a discrepancy is deferred and the deferral record will show in the compliance maintenance history of the discrepancy. |
Note: At least one row must be selected in the multiline.
Note: The sign-off details cannot be modified for signed of Tasks and sub tasks.
Click the “Record Sign-Off & Completion” pushbutton to record the sign-off and work completion details. Dual Authentication
The system performs the following:
Ensures that the Employee # entered in the Mechanic / Inspector / RII input boxes in “Task Sign-Off Details” / “Default Options” group box has a valid license / certificate to sign-off the task / Sub-Task based on the following conditions:
If a “Sub task-Skill” combination having the “Sign-Off ?” flag set as "Yes", also has the “Approval Reqd. ?” flag set as "Yes" in the “Edit Resource / Sign-Off Requirements” screen in the “Maintain Activated Tasks” activity of the “Maintenance Task” business component.
If for the row selected in the “Task Sign-Off Details” multiline, the value "Sign Off" or "Void" is selected in the “Sign-Off Action” drop-down list box.
Considers an Employee to have a valid License for Sign-Off based if the following conditions are true:
For sign-off at Task level: License requirements have to be satisfied for all applicable “Sub-Task-Skill” combinations, having ‘Sign-Off’ and ‘Approval Reqd. ?’ flags set as “Yes” in the “Edit Resource / Sign-Off Requirements” page in the “Maintain Activated Tasks” activity of the “Maintenance Task” business component.
For sign-off at Sub-Task level: License requirements have to be satisfied for all Skill Resources mapped to the Sign-Off Sub-Task, having ‘Sign-Off’ and ‘Approval Reqd.?’ flags set as “Yes”.
For sign-off of skill resource: License requirement have to be satisfied for the combination: Skill Code- Aircraft Model # - License #, in the interacting “Record Employee License Information” page in the ”Record Personal Information” activity of the “Employee Personal Information” business component.
Verifies if there is a valid Certificate for Sign-Off in the case of Employees without a valid License.
Considers an employee to have a valid certificate for sign-off if the following conditions are true:
Certificates having the following mapping will be deemed as valid for the Task Sign-Off : Certificate – Work Unit – Aircraft Model. Here, Work Unit could refer to either: Sign-Off Task / Parent Task of Sign-Off Task) / Root Task of Sign-Off Task. More.. The employee to Certificate mapping can be done in the “Edit Certificate Effectivity Information” in the “Maintain Certificate Information” activity of the “HR General Information” business component.‘
The employee has at least one Certificate as mentioned in point (i) above, in “Active” status for the given Sign-Off date. The Employee to Certificate mapping can be done in the “Record Employee Certificate Information” page in the “Record Personal Information” activity of the “Employee Personal Information” business component.
If the “Change status to Completed” drop-down list box is selected as "Yes", then for the tasks retrieved for sign-off, the system ensures the following:
There are no pending sign-off requirements at task / sub task level. (Sign-off status either ‘Signed Off’ or ‘Not Required’).
There are no mandatory parameter value updates pending at task / sub task level.
There are no excess parts are pending for return at the task level.
If the above conditions are satisfied, the “Compliance Date & Time” entered must be converted into server equivalent date and time, based on the conversion factor defined for the station of each task, in the “Common Masters” business component, The converted date and time must be lesser than or equal to the server date and time.
The system also updates the task status to “Completed”, on satisfying the conditions above.
The system does not allow the status of the task to be updated to “Completed” if one of the following conditions is true:
If the Customer Order #, Package #, Task # or Discrepancy # is on hold with a hold code which has the process parameter “Shop A/C Maint. Execution?” set as “Yes’ or “Till Estimation Confirmation” in the “Set Process Parameters” page of the “Define Process Entities” activity in the “Common Masters” business component.
If the Customer Order #, Package #, Task # or Discrepancy # is on hold with a hold code which has the process parameter, “Prevent Task Status Change?” set as “Yes” or “Till Estimation Confirmation” in the “Set Process Parameters” page of the “Define Process Entities” activity in the “Common Masters” business component.
If the sign-off for few of the subtasks of the task is pending.
Closure of Child Discrepancies for task closure:
If the process parameter "Mandate completion of related Discrepancies before closure of Inspection Tasks ?” associated to the 'Package Type' of the 'A/C Maint. Exe. Ref. Document' is set as "Yes", the system allows completion / closure of the task, only if all the child discrepancies associated to the Task are in terminating statuses i.e. "Closed", "Transferred", "Deferred" or "Cancelled".
If the process parameter mentioned above is set as "No", the system allows completion / closure of the task, irrespective of the status of the child discrepancies associated to the task.
Note: If a Discrepancy has a Task specified against it in the ‘Source Type & No’ control (Discrepancy section), the Discrepancy is considered as the Child Discrepancy of the specified Source Task.
The system does not allow you perform sign-off / void of Task or Sub-Task) / Discrepancy, if the process parameters:
'Stop A/C Maint. Execution ?' is set as "Yes" for the 'Hold Code' corresponding to the ‘Task’ / ‘Discrepancy’ / A/C Maint. Exe. Ref. Document’ / 'Customer Order'.
'Prevent new Tasks addition ?' is set as "Yes" for the 'Hold Code' corresponding to the ‘Task’ / ‘Discrepancy’ / ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.
On completion of the task, the system updates the compliance details of the task in the compliance history.
On completion of the task, if the Job Type of the task is "On-wing" or "Component Removal", based on their maintenance type, the system resets the following component parameter values:
If the maintenance type is overhaul, the system resets the “Since Overhaul”, “Since Repair” and “Since Inspection” parameter values to zero.
If the maintenance type is repair, the system resets the “Since Repair” and “Since Inspection” parameter values to zero.
If the maintenance type is inspection, the system resets the “Since Inspection” parameter value to zero.
Note: The system will not reset any value if the maintenance type of the task is “Others” or “Retire”.
If the task for which the status is updated as "Completed" is the last task in the current Execution Ref #, the system updates the status of the Execution Ref # as "Completed".
The sign-off details of the task and sub tasks cannot be modified, if the ‘Transient Status’ of the task is set as “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.
If the 'Execution Status' of a task is changed to “Completed” / “Closed', the system performs the following:
If the “Ref. Date for Compliance against Flight Ops” parameter is set as "Start Date" in the Common Masters” business component, the system converts the 'Act. Start Date & Time' of the Task into its 'Server Date & Time' equivalent by considering the conversion factor available for the Execution Station of the task, in the “Common Masters” component. Example.
If the Ref. Date for Compliance is set as "End date", the system converts the 'Act. End Date & Time' of the Task into its 'Server Date & Time' equivalent.
In either cases mentioned above, the converted value is updated as 'Compliance Date & Time' in the “Track Maintenance Compliance History” page of the “Compliance Tracking & Control” business component.
Note: The update explained above does not happen, if the status of the task is changed from “Completed” to “Closed”.
Auto Return of parts on package completion:
If the parts are pending for return for the tasks inside a package, the system creates a Material Return document on completion of the package, if the attribute “Auto Return of Parts” is set as “Required” for the Package Type in the “Set Process Parameters” page of the “Common Masters” business component.
Scenario 1: Pending Return - Core
If core return parts and the parts which are removed from aircraft are available for return, then for the work center mapped to the corresponding task, the system creates the Return Document against the ‘Return Warehouse # - Cores’ associated to the Work Center.
Scenario 2: Pending Return - Excess
If excess return parts are available for return, the system creates the Return Document against the ‘Return Warehouse #’ associated to the Work Center. Example.
Note: The Return Document creation happens only if the “Auto Return?” drop-down list box is set as “Required” for the Work Center in the “Associate Warehouses” page of the “Work Center” business component.
If the “Action” radio button or the “Sign-Off Status” drop-down list box is selected as “Sign-Off” or “Void”, and if the option “Approval Reqd.?” for the task is set as “Yes” in the “Edit Resource/Sign-Off Requirements” page of the “Maintenance Task” business component, the system considers that the employee possesses valid Certificate or License for the sign-off of the task, only if the following conditions are satisfied:
The Certificate # / License # must be mapped to the Employee # and Skill # available for the task / sub task, as defined in the “Employee Personal Information” business component.
Certificate # / License # must be valid for the current date.
The task # must be identified as Work Unit effectivity for the Certificate # / License #.
The Aircraft model # of the Aircraft Reg # identified for the Execution Ref # in the header must be mapped for the task # for the Certificate / License.
If an employee has signed-off at both task / level for an ‘On-wing’ or a ‘Component Removal’ job identified for an ETOP position code, the system does not allow the same employee to sign-off for a different ‘On-wing’ or ‘Component Removal job identified for the ETOP position code identified as reference to the previous ETOP position code. This is applicable if the “Action” radio button or the “Sign-Off Status” drop-down list box is selected as “Sign-Off” or “Void”.
Aircraft Condition Update:
On clicking the “Record Sign-Off & Completion” pushbutton, the system updates the condition of the aircraft to “Under Maintenance”, if the condition of the aircraft is saved as “Operational” and if the following conditions are satisfied:
If the parameter “Aircraft Condition Change” is set as “Required” for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.
If the status of the Execution Ref # is set as “In-Progress”.
The system updates the condition of the aircraft to “Operational”, if the condition of the aircraft is saved as “Under Resolution” and if the following conditions are satisfied:
If the parameter “Aircraft Condition Change” is set as “Required” for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.
If the status of the Execution Ref # is set as “Completed”.
If the parameter “CoM Required” is set as “Not Required” for the current Package #.
The "User Authentication Web Dialog" screen appears, on clicking the “Record Sign-Off & Completion” pushbutton.
Insert the smart card into the smart card reader and enter your Personal Identification Number (PIN) in the "User PIN” field. Follow the steps mentioned under the topic “Signing-off using Electronic Signature”, for user authentication while releasing aircraft.
Signing-off using Electronic Signature
Following are the prerequisites for using Electronic Signature in this activity:
The Smart Card Interface Client installation must have been completed and configured on this computer.
A Smart Card Reader must be connected to this computer and configured.
Electronic signature authentication must have been enabled for this business component or function in the “Smart Card Interface” business component.
The person who will be using the Electronic Signature feature, must have been enrolled as a smart card user and issued a card in the "Smart Card Interface” business component. The card must be active and valid for the current date.
Click the “OK” pushbutton.
The system authenticates the entered PIN value against the user's PIN value stored in the smart card.
On successful authentication, the system displays the message “Sign-Off Recorded successfully”.
If an invalid PIN is entered, the system displays the error message “Incorrect Secret Code Submission” and the Electronic signature cannot be completed.
Note: The smart card will get into "Locked" status, if the number of continuous invalid PIN entries exceeds the maximum number of invalid PIN entries defined in the “Smart Card Configuration” activity in the "Smart Card Interface” business component. Contact the administrator for unlocking the card and to use the smart card again for Electronic signature.
To proceed carry out the following:
Select the “Record Parameter Reading / Cond. Eval. Form” link to record the parameter values and conditional evaluation details of the parameters.
Select the “Create Maintenance Return” link at the bottom of the page to create a maintenance return document for the AME.
Refer to the “Stock Return” online help for more details.
Select the “View Sign-Off Comments” link to view the sign-off comments.
Refer to the “Flight Log” online help for more details.