Recording parameter details and conditional evaluation details for the task

Prerequisite

Unified Glossary

Basics of using a typical web page

Using Online Help

This activity allows you to record the parameter values and conditional evaluation details of each parameter, at the time of compliance of the task. Tell me more.

The “Record Parameter Reading / Conditional Evaluation Form” page appears.

The system displays the following field:

Date & Time Format

The format in which the date and time fields must be entered. This format is displayed from the "User Preferences" business component based on the login user ID.

In case the format is not defined, the system displays the date and time format from the “Enterprise Modeling” business component by default.

The system displays the following details in the “Execution Details” group box:

Exe. Doc. Type / Ref #

The execution document type / execution document reference number. The system displays the following:

  • Package Type / document number, if the Execution Document Type is Aircraft Maintenance Execution Document (AME) or Shop Work Order (SWO).

  • “Hangar Work Order” / document number, if the Execution Document Type is Hangar Work Order (HWO).

Work Center #

The work center associated to the package or work order. The Work Center is defined at package level for AME / SWO and at Task level for HWO.

Tree Interface

The system displays a tree structure in the left pane. The tree will have the ‘Execution Doc. #’ as the parent node (level).  All the nodes of the tree are displayed in an exploded form. The various nodes displayed in the tree are as follows:

First (Parent) node: Execution Doc. #: The package, shop work order or the hangar work order against which the tasks are performed on an aircraft / engine.

Second node: Task # which have parameter requirements defined at task and / or at sub-task levels..

Third node:

Fourth Node: Parameter mapped at each of the sub task level (Parameters are listed in the same order as defined for the task in the “Edit Parameter Reading / Eval. Form” page of the “Maintenance Task” business component).

For the parameter with and without conditional evaluation requirements, the nodes are represented with different symbols as shown below:

- Indicates that the parameter has evaluation details defined for the task or sub tasks in the “Maintenance Task” business component.

- Indicates that the parameter does not have evaluation details defined for the task or sub tasks in the “Maintenance Task” business component.

Parameter Node with and without Value / Eval. Response:

When the parameter information is displayed in the tree interface, if the 'Value/ Eval. Response' is already defined for that parameter, the saved 'Value / Eval. Response' value is displayed along with the parameter, concatenated by "::", in ‘Bold Blue’ font. If the 'Value/ Eval. Response' is not defined for the parameter, the parameter node is displayed in ‘Bold Red’ font.

Example:

If the ‘Exec. Doc #’ is HVY-003482-2010, ‘Task #’ is 53A0051-HFEC, ‘Sub Task Desc.’ is “Inspection of Crack Length” and ‘Parameter’ is “Length”. The tree structure is displayed as follows:

Without Value / Eval. Response:

HVY-003482-2010

|

   53A0051-HFEC

    |

      Inspection of Crack Length

      |

         Length

With Value / Eval. Response:

HVY-003482-2010

|

  53A0051-HFEC

   |

     Inspection of Crack Length

      |

        Length :: 5mm

Parameter reading / conditional evaluation details:

On clicking the “Task #” and “Sub Task #” nodes in the tree interface, the system displays the details in the Parameter Reading / Evaluation Form” group box and in the “Conditional Maintenance Evaluation” multiline, in the right pane.

The system displays the following in the “Parameter Reading / Evaluation Form” group box:

Task #

The code identifying the task corresponding to the parameter selected in the tree interface.

Task Desc.

The textual description of the task.

Sub Task Desc.

The textual description of the sub task corresponding to the parameter selected. The sub task description is displayed only if the parameter is selected at the sub task level.

Sub Task Seq #

The sequence number of the sub task as defined for the corresponding task # in the “Maintenance Task” business component.

Aircraft Reg #

The registration number of the aircraft on which the package or the work order is raised.

Part # / Serial #

The code identifying the part / serial number of the part. The following values are displayed:

  • The part # / serial # corresponding to the on-wing 'Task #' in the package/ Hangar Work Order, if the execution document is AME or HWO.

  • The part # / serial # saved for each SWO-Task #. For the SWO-Task #, if serial number is not saved, the system does not display any value.

Parameter

The parameter defined for the 'Task # - Sub Task Seq # - Parameter' combination.

Parameter Desc.

The textual description of the parameter.

Value / Eval. Response

The actual value / response observed against the parameter as part of the compliance of the task. (Alphanumeric, 32).

The value entered in this field must satisfy the following conditions:

  • It must be lesser than or equal to the “Current Value” This is applicable only for “Consumption & Range Parameters”.

  • It must be a valid 'Permitted Value' defined for the 'Task # - Sub task Seq # - Parameter' combination. This is true only if permitted values are available for the parameter.

Exe. Remarks

Any additional remarks on the execution of the task. (Alphanumeric, 2000).

The system displays the following fields:

Permitted Values

The permitted values defined for the 'Task # - Sub Task Seq # - Parameter' combination in the “Maintenance Task” business component.

Current Value

The current value of the parameter. The value is displayed only for standard parameter. For non-standard parameter, the system does not display any value.

Mandatory?

Indicates whether the Value / Eval. Response recording is mandatory or not for the parameter. The system displays one of the following values:

 “Yes” - This value is displayed if the “Parameter Recording?” drop-down is set as "Mandatory" for the 'Task # - Sub Task Seq # - Parameter' combination in the “Edit Parameter Reading / Conditional Maint. Eval. Form” page of the “Maintenance Task” business component.

“No” - This value is displayed if the above option is set as “Non-Mandatory”.

Update Mode

The update mode of the parameter mapped to the maintenance object type as defined in the "Edit Consumption & Range Parameters" and "Edit Technical & Attribute Parameters" pages of the aircraft or part / serial. The system displays one of the following values:

  • “Delta” - This is a cumulative value indicating that the new parameter value must be added with the existing parameter value.

  • “New” - This is an absolute value indicating that the old parameter value must be overwritten with the new parameter value.

If the parameter is a non-standard parameter, the system displays the value as “New”.

Update Date & Time

The date and time at which the parameter details are updated. (Date & Time format).

The system displays the previously saved value, if exists, for 'Exec. Doc # - Task # - Sub Task Seq # - Parameter' combination. Else, the system defaults the following values:

  • Server date and time, when launched from WMC and HWO.

  • Date & Time as defined in the “Record Aircraft Maintenance Execution Details” page, when launched from ”Aircraft Maintenance Execution” business component.

  • Date & Time as defined in the “Record Shop Execution Details” page, when launched from “Shop Work Order” business component.

The date and time entered here must be earlier than equal to the server date and time.

Data entry in this field is mandatory if the “Value / Eval. Response” is specified.

Updated by

The employee code of the login user who updated the parameter details. (Alphanumeric, 30)

The system displays the previously saved value, if exists, for 'Exec. Doc # - Task # - Sub Task Seq # - Parameter' combination. Else, the system defaults the ‘Employee Code’ of the login user.

Data entry in this field is mandatory if the “Value / Eval. Response” is specified.

Help facility available.

The system displays the following fields in the “Conditional Maintenance Evaluation” multiline:

Processed?

Indicates whether the tasks are added to the package for immediate execution based on the ‘Value / Eval. Response’ defined by the user. The system displays the values “Yes” or “No”.

Trigger Value

The absolute value of the parameter, at which the follow-up action must be executed.

Trigger Value (Min)

The minimum value of the parameter, at which the follow-up action must be executed.

Trigger Value (Max)

The maximum value of the parameter at which the follow-up action must be executed.

Follow-up Action

The follow-up action for the task, as defined for the task. The system displays one of the following values: “None”, “Initiate Schedule”, “Terminate Schedule”, “Initiate Immediate Exec.”, and “Initiate Records Follow-up”.

Follow-up Task #

The task that must be executed as part of the follow-up action.

Records Follow-up Instructions

A set of actions, tasks or procedures that must be carried out as part of the “Initiate Records Follow-up" follow-up action.

Evaluation Remarks

Any additional information on evaluation of the follow-up action.

Note: Ensure that the 'Exec. Doc # - Task # - Sub Task Seq # - Parameter' combination is not updated by a concurrent user.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Recording parameter details and conditional evaluation details for the task - An overview

Record Parameter Reading / Conditional Evaluation Form - A summary of the activity

Engineering Change Management is a very critical and essential part of Aircraft Maintenance. Most of the engineering changes are very complex in nature and often needs lot of evaluation and follow-up. Consequentially, it is vital that the information systems employed, guide other related functions viz., Maintenance Planning & Production control, through various steps they need to take for effective completion of engineering change initiated, thus ensuring seamless information flow for effective decision making.

A task can have multiple types of relationships established with other tasks, to address maintenance planning, maintenance execution and compliance management requirements. This interface would guide the planner or mechanic through various next steps that they need to take, based on pre-configured follow-up actions.

While reporting work actual; mechanic will be able to review the parameter conditions identified by accessing the link ‘Record Parameter Reading / Conditional Eval. Form’. Also mechanic will be able enter the actual reading. On completion of primary task, the system will execute as per ‘Follow-Up action’ set if the parameter updated value matches with the standard value provided while authoring the task. Moreover while authoring task, if the parameter recording option is as mandatory, the system will enforce the mechanic to visit this page and update the value.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Prerequisite