Re-forecasting component arising

In this page, the planner can re-forecast the maintenance arisings. Tell me more.

• Select the "Re-forecast Component Arising" link in the previous page. Alternatively click the hyperlinked forecast number in the multiline of the same page.

The "Re-forecast Component Arisings" page appears.

The system displays the following:

The system displays the following fields in the "Forecast Details" group box:

• Click the “Re-forecast” pushbutton to re-forecast the maintenance arisings.

Note: Forecast is generated for the appropriate parent based on the option specified in the “Parent Removal” field in the Component Maintenance pProgram. If the “Parent Removal” field is specified as “Specific part”, then the system generates forecast for the part number entered. If the “Parent Removal” field is specified as “NHA”, then the system generates forecast for the next higher assembly of the part number entered. If the “Parent Removal” field is specified as “NHA-LRU”, then the system generates forecast for the next higher assembly which of replacement type – Line replacement Unit (LRU),  of the part number entered. If the “Parent Removal” field is specified as “End Part”, then the system generates forecast for the part number at the highest level of configuration of the part number entered.

• If any work unit is available in the component pending jobs tray with job status as "Pending" against a component and if the same component is re-forecasted in “Aircraft Maintenance Forecast” or “Component Maintenance Forecast”, the system performs re-forecasting of the component and increments the re-forecast count. The system also updates the pending tray with the forecast number and reforecast count.

Note: The re-forecasting is performed for pending work units for which the schedule dates fall within the forecast horizon.

• For work units having job status as “Allocated”, the system increments the re-forecast count and updates the count in the re-forecast log.

• Removes all the pending work units for the component and its associated child components from the pending tray, if the condition of the component is updated as “Phased Out” in the “Aircraft” business component.

• If any of the forecasted work units of the component does not fall under the forecast horizon for the planner group and if the component is still mapped to the planner group, the system removes those pending work units from the pending tray.

• Copies the expense type of the work units as identified in the component maintenance program to the pending tray.

The system does not forecast the work units under the following circumstances:

• If the status of the component in “Component Maintenance Program” business component, is “Inactive”.

• If the work unit of the maintenance program is inactivated, during reforecast.

The system also removes the work units from the pending tray, when the above conditions are satisfied.

Re-forecast

The system performs the following on clicking the "Re-forecast" pushbutton:

Date -based forecasting

The list of components associated with the planner group is identified. Forecasting is performed on all the components of the planner group.

• If the schedule type is "Actual Interval", or if the schedule type is "Fixed Date" and there is no value in the "Last Performed Date" in the "Component Maintenance Program" business component, the system finds out the next scheduled date for all the maintenance type or work units associated with the component.

• If the next scheduled date is less than or equal to the forecast end date then the system retrieves the component number along with the work unit and maintenance type which is due for maintenance.

Note: If the “Next schedule date” exceeds the “Terminating Date”, then the system will not retrieve the maintenance requirement of the component for forecast.

• Calculates Earliest Scheduled Date as ESD = Scheduled Date - Negative Tolerance

• Calculates Latest Scheduled Date = Scheduled Date + Positive Tolerance

• Calculates Alert Date = Scheduled Date - Alert Value (If the tolerance/alert value is  given in months / year, then the system converts it into number of days and performs the calculation)

• Stores the forecasted output , that is the component ID/work unit details along with the scheduled dates with the job source as "CMP".

Usage based forecast

• If the component is attached to the aircraft, the system identifies the lead parameter and the usage value of the lead parameter for both the aircraft and the component from the "Aircraft" business component.

• If usage- based schedule details are available for the component in the component maintenance program and if the schedule type is "Recurring" or "One time", and there is no value in the "Last Performed Value", the system calculates the remaining usage parameter value. The remaining usage value is calculated for all the parameters of the component attached to the aircraft.

Note: If the “Next schedule date” exceeds the “Terminating Date”, then the system will not retrieve the maintenance requirement of the component for forecast.

• If any of the forecasted work units of the component falls under the forecast horizon for the planner group and If there is any change in the usage-based schedule of the component which is not associated to the planner group currently, the system retains the work units in the pending tray.

Scheduled date of maintenance arising calculation:

The system calculates the scheduled date of maintenance arising as follows:

Average usage value of parameter calculation

• The average value of the lead parameter of the aircraft to which the forecasting component is attached can be taken as the average usage value. This is possible only when the forecasting parameter and the lead parameter of the aircraft are same.

• If the lead parameter is different from the forecasting parameter, then the average value of the given parameter of the component is retrieved from the "Create Component Record" activity of the "Aircraft" business component.

• If any forecast factor is specified in the "Aircraft" business component for the forecasting component, then the forecast factor is converted into the average value.

Average value = Forecast factor * average value for the lead parameter.

Position- Based Forecasting

Position -based schedule forecasting has to be executed only if the component is attached to the aircraft and the position in which the component is attached has its schedule defined in the "Component Maintenance Program".

• If position- based schedules are available for a position to which the  component is fitted, then the system ascertains the scheduled date, latest/earliest/alert dates for the maintenance arising.

• If date- based schedule information is available for the attached  position, then "Next scheduled date" for all the maintenance type / Work Units associated with the component in the component maintenance program is ascertained.

Note: The next scheduled date and the alert date are calculated as done for usage-based forecasting.

Forecast-based on deferment log

• The scheduled date/alert date from the forecasted output for the given component is calculated. Also the deferral details from the deferment request in the"Authorized" status for all the component-maintenance type from the deferment log, like the number of days it is deferred and alert value in terms of days, are identified.

• If the sum of the scheduled date and the number of days it is deferred is less than the forecast end date, then the system stores the component –cum- maintenance type in the forecast log with the job status as "Pending" and the job source as "deferral"

• In the usage- based deferrals, if the scheduled date is less than the alert date, then the system stores the work unit /maintenance type and component into the forecast log with  the job source as "Deferral".

Shelf Life calculation

The remaining shelf life for the components which are not attached with the aircraft is calculated as follows:

Remaining Shelf Life = Design Shelf Life – (Difference between the date in which component came into the warehouse and the forecast end date)

• If the Remaining Shelf Life is less than or equal to zero, then the component and corresponding work unit identified in the CMP for shelf life expiry is updated with job source "Shelf life expiry"

• If the remaining shelf life is less than or equal to the alert value, then the schedule date and alert dates are calculated as follows:

a) Schedule date: The remaining shelf life (in terms of days) is calculated and subtracted from the forecast end date. This is done when difference between the remaining shelf life and alert value date  is positive, then it is added to the forecast end date and schedule date is obtained.

b) Alert date:-The difference between the alert value and the remaining shelf life is calculated. The value is converted into number of days and subtracted from the forecast end date.

• The work unit and the component – cum – maintenance type is updated with job source “Shelf Life Expiry”.

• If the expiry date of a component (as defined in the “Stock Maintenance” business component) is lesser than the forecast date, then the component and the corresponding work units added in the forecast log of the component, which are identified in CMP with job source as "Shelf life expiry".

Opportunity Maintenance Job forecasting

• If any opportunity work units are defined for the component and maintenance type combination in the “Visit Package” business component, those work units are identified.

• The work units are then added to the forecast.

• If the maintenance arising is of higher level maintenance type such as “Overhaul”, then the lower level opportunity checks of type “Inspection”,”Repair” or ”ShopVisit” can be attached to the work unit. The order of the work units will be [OVERHAUL - REPAIR - INSPECTION - SHOP VISIT].

• The system considers the minimum schedule date among the maintenance types as the schedule date for all the opportunity work units.

Status of forecast and work units

• The forecast status is updated as “Fresh”. If you have checked “Release Forecast” box, then the system sets the status to “Released”.

• If there are pending work units (defined in CMP as “shelf life expiry”) for a component (that is, the next schedule date is earlier than the forecast start date), the system stores the components and the correspondng work units in the forecast log with the job source as “CMP”.

• If a component has pending work units but the component is “issued out” prior to the forecast start date, then the system removes these work units from the forecast log.

• If the component is attached to the aircraft and has off-wing jobs, then the system sets the “Removal Status” as “Pending” for the work units of the parts that have to be removed.

Short Term Escalation Reference

• Generates the NSD for tasks with date-based schedule /NSV for tasks with usage based schedule in the following way,

 NSD  = Last Performed Date + Repeat Interval

 NSV  = Last Performed Value + Repeat Value

NSD for each parameter in the usage-based schedule = ((NSV - Present Value) / Utilization Value + Current Server Date)

• If the task compiled has a short term escalation reference, sets the NSD/NSV of a task on the basis of the Schedule Reset Basis specified in the short term escalation request.

1. If the Schedule Reset Basis is set to “Actual Schedule”, the system derives NSD/NSV for tasks on the basis of the last performed date, as explained previously.

2. If the Reset Schedule Basis is set to “Last Schedule”, the system derives the NSD/NSV in the following way,

For date-based schedule: NSD (New) = NSD + Repeat Interval

For usage-based schedule: NSV (New) = NSV + Repeat Value Example

Example

• Updates the NSD and NSV for a task in the aircraft/component maintenance program.

Component Arisings

The system displays the following in the "Component Arisings" multiline after clicking the “Re-forecast” pushbutton:

The system displays the following in the “Record Statistics” group box:    

To proceed, carry out the following:

• Select the "Edit Utilization Factor" link at the bottom of the page to edit the utilization factor details.

• Select the "View Forecast Details" link at the bottom of the page to view the forecast details.

Re-forecasting component arising - An overview

In this page, the planner can re-forecast the maintenance arisings. The forecast in the “Fresh” or “Released” status can be re-forecast in this page.

The system displays the re-forecast impact after analyzing the scheduled dates of the work units and the forecast. The number of affected component jobs is also displayed along with the impact.

The forecast is created according to the conditions specified for the component in the "Component Maintenance Program" business component. The forecasting can be one of the following types:

• Date-based forecasting - For more details refer to the section "Date-Based Forecasting".

• Usage-based forecasting - For more details refer to the section "Usage-Based Forecasting".

• Position-based forecasting - For more details refer to the section "Position-Based Forecasting".

• Deferment log - based forecasting - For more details refer to the section "Forecast based on deferment log".

• Shelf life based forecasting – For more details refer to the section “Shelf Life based Calculation”.

• Opportunity maintenance job forecasting - For more details refer to the section “Opportunity maintenance job forecasting”

The forecast is re-forecasted and the forecast details are entered into the Re-forecast log.