Skip to main content

Master Task Cards

Overview​

The Master Task Cards application is a foundational component of Maximo for Aviation that enables the creation and management of master maintenance task definitions.

Master Task Cards serve as templates that define maintenance requirements, frequencies, and procedures for configuration-managed (CM) components and aircraft systems.

Purpose and Function:

Master Task Cards act as the authoritative source for maintenance task definitions that are:

  • Linked to one or more configuration-managed (CM) Part Numbers
  • Used to automatically generate Task Cards for applicable assets (Aircraft or Equipment)
  • Integrated with Operators Maintenance Programs (OMPs)
  • Maintained with full revision control and change tracking
  • Organized by ATA chapters and maintenance phases

Master Task Cards are the bridge between manufacturer maintenance requirements (imported via MTL) and operational maintenance execution (Task Cards on assets). They ensure consistency and compliance across the fleet.

Key Capabilities:

  • Define maintenance tasks with comprehensive frequency criteria
  • Link tasks to configuration-managed part numbers
  • Support multiple frequency types (calendar, meter-based, iterations)
  • Configure task actions that affect related tasks
  • Manage task revisions with full change tracking
  • Generate Task Cards automatically for applicable assets
  • Support check-based maintenance organization
  • Enable task extensions and deferrals
  • Integrate with OMP and BDI for automated Task Card generation
Master Task Card Main Screen

Integration Points:

  • Part Number Master - Links tasks to CM part numbers
  • MTL Application - Source for manufacturer task requirements
  • OMP Application - Organizes tasks into maintenance programs
  • Aicraft and Equipment Application - Displays generated active Task Cards on the Maintenance Plan tab
  • BDI (Build Data Interpreter) - Automates Task Card generation
  • Work Orders - Execution of maintenance tasks
  • Job Cards - Detailed work instructions and resource requirements

Master Task Card Structure​

Understanding the structure and fields of a Master Task Card is essential for consultants implementing the system.

Header Information​

Core Identification Fields:

FieldDescriptionExampleRequired
Task NumberUnique identifier for the Master Task CardXJET-APU-OVHYes
DescriptionDescriptive name of the taskAPU OverhaulYes
StatusCurrent status of the Master Task CardACTIVE, DRAFT, PNDREV, INACTIVEYes
RevisionRevision number for change tracking0, 1, 2Yes
OperatorOperating organizationIBMYes
ATA CodeATA chapter code49-00 (APU)Yes
Master Task Card TypeCategory of taskCOMPONENT, AIRFRAME, CHECK, EVENTYes
Task CodeShort code for task typeRS, OPC, DET, GVIYes

Master Task Card Type Values:

The Master Task Card Type field categorizes tasks by their nature and purpose:

TypeDescriptionUsage
AIRFRAMEAirframe TaskTasks performed on the aircraft structure, systems, or zones. Not specific to a removable component. Examples: fuselage inspections, wing structural checks, system functional tests.
CHECKMaintenance CheckUsed to group tasks with similar frequencies into larger maintenance events (A-Check, C-Check, etc.). Checks organize multiple tasks for efficient planning and execution.
COMPONENTComponent TaskTasks performed on specific removable components or assemblies. Linked to part numbers and follow the component through its lifecycle (on-wing, in-shop, in-storage). Examples: engine overhaul, landing gear inspection, APU service.
EVENTEvent-Based TaskMaintenance tasks triggered by specific events rather than time or usage intervals. Examples: post-lightning strike inspection, after hard landing check, following bird strike.

Selecting the correct Master Task Card Type is critical as it determines how the task behaves, how Task Cards are generated, and how the task integrates with asset configuration management.

Task Code Examples:

CodeDescriptionTypical Usage
RSRestorationOverhaul, major repair, rebuild
OPCOperational CheckFunctional verification, system operation test
DETDetailed InspectionThorough visual inspection with specific criteria
GVIGeneral Visual InspectionBasic visual check for obvious defects
DISDiscardTime-change item, life-limited part replacement
SVCServiceLubrication, replenishment, routine servicing
FNCFunctional CheckSystem functional test, operational verification

Special Instructions​

The Special Instructions section contains flags that are used for information purposes only. They highlight specific requirements or nature of the task to be performed.

FieldDescriptionImpact
ALI?Airworthiness Limitation Item.Indicates that failure to perform the task could result in the aicraft being unfit to fly
One Star CMR?One Star Critical Maintenance RequirementRegulatory critical task
Two Star CMR?Two Star Critical Maintenance RequirementHigher level regulatory critical task
ETOPS?Extended Range Twin-engine OperationsRequired for ETOPS certification
CDCCL?Critical design configuration controlIndicates whether critical design configuration control limitations apply to this master task card.
EWIS?Electrical Wiring Interconnection SystemIndicates whether an electrical wiring interconnection system is associated with this master task card.
CPCP?Corrosion Prevention and Control ProgramCorrosion-related task
RVSM?Reduced Vertical Separation MinimumRequired for RVSM operations

Task Information​

Operational Fields:

FieldDescriptionExample
Work StationWhere task is performedHANGAR, LINE, SHOP
Task SourceOrigin of task requirementCMM, MPD, SB
Deferral?Whether task can be deferredChecked/Unchecked
TPSTemporary Protection SystemReference to standard
Weight and Balance?Affects weight and balanceChecked/Unchecked
ApplicabilityApplicability statementFree text
CraftPrimary maintenance trade that is required to perform the taskAF (Airframe), AV (Avionics)
PhaseMaintenance phaseA, B, C, D
Out of phase?Can be done out of phaseChecked/Unchecked
TCI?Tool Calibration ItemChecked/Unchecked
SDR?Service Difficulty Report requiredChecked/Unchecked
CommentsAdditional notesFree text
Off-Wing?Task performed off-wingChecked/Unchecked
Include in Flight Schedule?Include in flight planningChecked/Unchecked

Relationship with Part Numbers​

The relationship between Master Task Cards and Part Numbers is fundamental to Maximo for Aviation's automated maintenance generation and statusing capability.

Part Number Linkage​

Master Task Cards are linked to configuration-managed (CM) part numbers through the Part Numbers tab. This relationship enables:

  • Automatic Task Card Generation - When an asset with a linked part number is validated by BDI, Task Cards are automatically created
  • Component Tracking - Tasks follow components through their lifecycle (installation, removal, shop visit)
  • Configuration Control - Ensures correct tasks are applied based on installed components
  • Maintenance Planning - Links maintenance requirements to specific components
Master Task Card Part Numbers

Part Number Table Fields:

FieldDescription
Part NumberCM part number from Part Number Master
DescriptionPart description
VendorPart manufacturer or vendor
DescriptionAdditional description or notes

The Part Number relationship is what enables "configuration-aware" maintenance

  • the system automatically knows what maintenance is required based on what components are installed on each aircraft.

Multiple Part Numbers:

  • A single Master Task Card can be linked to multiple part numbers
  • Useful for tasks that apply to different variants or alternates
  • All linked part numbers will trigger Task Card generation
  • Enables fleet commonality and standardization

Frequency Configuration​

Frequency configuration is one of the most critical aspects of Master Task Cards, defining when maintenance tasks become due. Maximo for Aviation supports multiple frequency definition methods to accommodate various maintenance philosophies.

Frequency Definition Methods​

Master Task Cards support three primary methods for defining when tasks are due:

  1. Intervals and Thresholds - Traditional fixed-interval maintenance
  2. Time-Based Iterations - Sequential calendar-based task progression
  3. Meter-Based Iterations - Sequential usage-based task progression
Frequency Tab Overview

Special Frequency Information​

Refer to the Maintenance Task Library topic for an explanation of the fields within this section.

Life Span:

  • Start Date - When task becomes active
  • Stop Date - When task is no longer required. The BDI will automatically de-activate the associated Task Cards once the date is exceeded.

Alert and Warning Interval State:

Defines when alert and warnings are issued before task becomes due:

OptionDescriptionExample
Absolute from ActiveFixed time from task activation / last completion30 days after activation
Percent of Frequency from ActivePercentage of interval from activation80% of interval after activation
Absolute prior to DueFixed time before due date / count500 FH before due

Work Order Generation Information:

FieldDescription
Use Last Work Order's Start Information to Calculate Next Due Frequency?Determines if the task is treated as a Fixed or Floating.
Fixed tasks are next due based on the prior work orders target start date.
Floating Tasks are based on when the previous work order was completed (Actual Finish Date).
Extended DateDate to which task can be extended
Update Existing Task Cards?Update all existing Task Cards when Master Task Card changes
Adjust Next Due Date?Adjust next due date for existing Task Cards

Intervals and Thresholds​

The Intervals and Thresholds method defines fixed-interval maintenance where tasks become due at regular intervals based on calendar time or meter readings.

Intervals and Thresholds Configuration

Standard Intervals​

Standard Intervals define when the task becomes due:

Interval Definition:

FieldDescriptionExample
Frequency TypeCALENDAR or METERCALENDAR, METER
FrequencyNumeric interval value5.00, 5000.00
Frequency UnitsUnit of measureYEARS, OHAPU (APU Hours)
Apply Adjustment Factor?Apply adjustment calculationChecked/Unchecked

Interval Details:

When you expand an interval, additional configuration options appear:

FieldDescription
Alert and Warning Frequency UnitsUnit for alert/warning calculations
Alert IntervalHow far in advance to alert ("EBA" BDI Problem Code is reported as part of the aircraft configuration status)
Warning IntervalHow far in advance to warn ("EBW" BDI Problem Code is reported as part of the aircraft configuration status)
Tolerance UnitsUnit for tolerance
Higher ToleranceAllowable extension beyond due
Lower ToleranceAllowable early completion

The Alert Interval in combination with the Alert and Warning Interval State determines when the BDI will automatically generate a Work Order from the related Task Card.

Calendar Frequency Examples:

FrequencyUnitsDescription
5.00YEARSEvery 5 years
24.00MONTHSEvery 24 months (2 years)
90.00DAYSEvery 90 days
1.00DAYSDaily

Meter Frequency Examples:

FrequencyUnitsDescription
5,000.00OHAPUEvery 5,000 APU operating hours
12,000.00FHEvery 12,000 flight hours
10,000.00FCEvery 10,000 flight cycles
20,000.00EHEvery 20,000 engine hours

Example Configuration:

Task: APU Overhaul
Frequency Type: CALENDAR
Frequency: 5.00 YEARS
Alert Interval: 14.00 DAYS (alert 14 days before due)
Warning Interval: 7.00 DAYS (warn 7 days before due)
Higher Tolerance: (no extension allowed)
Lower Tolerance: (no early completion allowed)

Standard Thresholds​

Standard Thresholds define when the first or initial instance of the maintenance task is due. This is distinct from Standard Intervals, which determine the frequency of all subsequent occurrences after the initial task is completed.

Threshold vs. Interval:

ComponentPurposeExample
ThresholdDefines when the FIRST occurrence is dueFirst inspection due at 1,000 FH after installation
IntervalDefines when SUBSEQUENT occurrences are dueRepeat every 5,000 FH after first inspection

Threshold Configuration:

Thresholds use the same structure as intervals but represent the initial due point:

FieldDescription
Frequency TypeCALENDAR or METER
FrequencyInitial threshold value
Frequency UnitsUnit of measure
Apply Adjustment Factor?Apply adjustment calculation

Threshold Examples:

FrequencyUnitsPurpose
1,000.00FHFirst inspection due at 1,000 flight hours
90.00DAYSFirst check due 90 days after installation
500.00FCFirst inspection due at 500 cycles

How Thresholds and Intervals Work Together:

Example: Engine Borescope Inspection

Threshold: 1,000.00 FH (First inspection)
Interval: 5,000.00 FH (Recurring inspections)

Timeline:
0 FH: Engine installed
1,000 FH: First borescope inspection due (THRESHOLD)
6,000 FH: Second borescope inspection due (1,000 + 5,000 INTERVAL)
11,000 FH: Third borescope inspection due (6,000 + 5,000 INTERVAL)
16,000 FH: Fourth borescope inspection due (11,000 + 5,000 INTERVAL)

Thresholds are particularly useful for break-in inspections, initial service checks, or any maintenance that has a different first-time interval compared to recurring intervals.

Multiple Intervals and Thresholds:

A Master Task Card can have multiple intervals and thresholds:

  • Multiple Intervals - Task becomes due when ANY interval is reached (whichever occurs first)
  • Multiple Thresholds - Multiple warning points for different planning horizons
  • Combined - Mix of calendar and meter-based intervals

Example: Combined Frequency

Task: C-Check Inspection
Interval 1: 12,000.00 FH (flight hours)
Interval 2: 72.00 MONTHS (calendar)
Threshold 1: 500.00 FH (warn at 11,500 FH)
Threshold 2: 14.00 DAYS (warn 14 days before calendar due)

Result: Task becomes due at 12,000 FH OR 72 months, whichever occurs first
Warnings issued at appropriate thresholds for each frequency type

Time-Based Frequency Iterations​

Time-Based Iterations provide a sequential, calendar-based approach to maintenance where tasks progress through a defined sequence of intervals. This method is ideal for progressive inspections, calibrations, or maintenance programs that require different actions at different intervals.

Time-Based Frequency Iterations

Time-Based Iteration Concept​

Instead of a single repeating interval, Time-Based Iterations define a sequence of calendar-based frequencies. Each iteration can have:

  • Different interval lengths
  • Different job cards
  • Different alert and warning intervals
  • Sequential progression through the iteration cycle

Key Features:

  • Sequential Progression - Task moves from iteration 1 to 2 to 3, etc.
  • Variable Intervals - Each iteration can have a different frequency
  • Iteration-Specific Job Cards - Different work instructions for each iteration
  • Loop Capability - Option to return to first iteration after completing the sequence

Configuring Time-Based Iterations​

Iteration Table Fields:

FieldDescription
FrequencyCalendar interval value
Frequency unitsMONTHS, DAYS, YEARS
Alert and Warning Frequency UnitsUnit for alerts/warnings
Alert intervalAdvance alert time
Warning intervalAdvance warning time
Iterations of this frequencyNumber of times this iteration occurs
Iteration sequence numberPosition in the sequence
Job CardSpecific job card for this iteration

Time-Based Iteration Examples​

Example 1: Progressive Calibration Program

Equipment: Precision Test Equipment
Requirement: Calibration intervals that increase with equipment maturity

Iteration 1:
- Frequency: 6 MONTHS
- Iterations: 2 (occurs twice)
- Sequence: 1
- Job Card: JPCAL101 (Initial Calibration)

Iteration 2:
- Frequency: 12 MONTHS
- Iterations: 2 (occurs twice)
- Sequence: 2
- Job Card: JPCAL102 (Standard Calibration)

Iteration 3:
- Frequency: 24 MONTHS
- Iterations: 1 (occurs once)
- Sequence: 3
- Job Card: JPCAL103 (Extended Calibration)

Progression:
Month 0: Equipment becomes operational
Month 6: Iteration 1, Occurrence 1 (JPCAL101)
Month 12: Iteration 1, Occurrence 2 (JPCAL101)
Month 24: Iteration 2, Occurrence 1 (JPCAL102)
Month 36: Iteration 2, Occurrence 2 (JPCAL102)
Month 60: Iteration 3, Occurrence 1 (JPCAL103)
Month 84: [Depends on Loop Iterations setting]

Example 2: Phased Inspection Program

Task: Structural Inspection Program
Requirement: Different inspection depths at different intervals

Iteration 1:
- Frequency: 24 MONTHS
- Iterations: 1
- Sequence: 1
- Job Card: JPBI001 (Basic Inspection)

Iteration 2:
- Frequency: 12 MONTHS
- Iterations: 1
- Sequence: 2
- Job Card: JPDI001 ( Detailed Inspection)

Progression:
Month 0: New component installed
Month 24: Iteration 1 (Basic Inspection)
Month 36: Iteration 2 (Detailed Inspection)
Month 48: [Depends on Loop Iterations setting]

Loop Iterations Checkbox​

The Loop Iterations checkbox controls what happens after the final iteration in the sequence is completed:

Loop Iterations = Checked (Enabled):

  • After completing the final iteration, the task returns to Iteration 1
  • The cycle repeats indefinitely
  • Useful for ongoing maintenance programs
  • Example: Calibration program that cycles through inspection depths

Loop Iterations = Unchecked (Disabled):

  • After completing the final iteration, the task stops and the Task Card is made inactive
  • No further work orders are generated
  • Useful for one-time progressive programs
  • Example: Break-in inspection program for new equipment

The Loop Iterations setting is critical for determining whether your maintenance program is cyclical (repeating) or finite (one-time). Choose based on your maintenance philosophy and regulatory requirements.

If the "Iterations of this Frequency" field is left empty for the last iteration in the sequence then the associated task card will continue indefinitely at the last iteration frequency.


Meter-Based Frequency Iterations​

Meter-Based Iterations provide a sequential, usage-based approach to maintenance where tasks progress through a defined sequence of meter intervals. It operates in an almost identical manner to the time based iterations.

This method is ideal for progressive inspections based on operating hours, cycles, or other usage metrics.

Meter-Based Frequency Iterations

Meter-Based Iteration Concept​

Similar to Time-Based Iterations, but driven by meter readings rather than calendar time. Each iteration can have:

  • Different meter interval lengths
  • Different job cards
  • Different alert and warning thresholds
  • Sequential progression through the iteration cycle
  • Variable iterations (different number of occurrences per iteration)

Configuring Meter-Based Iterations​

Step 1: Select Meter

First, define which meter drives the iterations:

FieldDescription
MeterMeter code (FH, FC, EH, etc.)
DescriptionMeter description

Step 2: Configure Iteration Flags

FieldDescription
Variable Iterations?Allow different iteration counts per frequency
Loop Iterations?Return to first iteration after completing sequence

Step 3: Define Frequency Iterations

For each iteration in the sequence:

FieldDescription
FrequencyMeter interval value
Alert intervalAdvance alert threshold
Warning intervalAdvance warning threshold
Iterations of this frequencyHow many times this iteration occurs
Iteration sequence numberPosition in the sequence
Job cardSpecific job card for this iteration

Meter-Based Iteration Examples​

Example 1: Engine Borescope Inspection Program

Component: Turbine Engine
Meter: EH (Engine Hours)
Requirement: Progressive borescope inspections with increasing intervals

Variable Iterations: Checked
Loop Iterations: Checked

Iteration 1:
- Frequency: 600.00 EH
- Alert interval: 50.00 EH
- Warning interval: 25.00 EH
- Iterations: 1
- Sequence: 2
- Job Card: JPBORO001 (Initial Borescope)

Iteration 2:
- Frequency: 1,200.00 EH
- Alert interval: 50.00 EH
- Warning interval: 25.00 EH
- Iterations: 1
- Sequence: 1
- Job Card: JPBORO002 (Standard Borescope)

Progression:
0 EH: Engine installed
600 EH: Iteration 2, Occurrence 1 (Initial Borescope - JPBORO001)
1,800 EH: Iteration 1, Occurrence 1 (Standard Borescope - JPBORO002)
3,000 EH: Iteration 2, Occurrence 1 (Initial Borescope - JPBORO001) [Loop back]
3,600 EH: Iteration 1, Occurrence 1 (Standard Borescope - JPBORO002)
...continues cycling

Meter-Based Iterations with Variable Iterations and Loop Iterations provide maximum flexibility for complex maintenance programs that need to adapt to component usage patterns and maturity.


Master Task Card Actions​

Master Task Card Actions provide powerful automation capabilities that allow one task (the "primary" task) to trigger actions on other related tasks (the "secondary" tasks). This feature enables sophisticated maintenance logic and workflow automation.

Master Task Card Actions Configuration

Actions Concept and Purpose​

What Are Master Task Card Actions?

Master Task Card Actions define automated responses that occur when specific events happen with a primary task. These actions affect secondary tasks on the same asset, enabling:

  • Coordinated Maintenance - Link related tasks so they work together
  • Workflow Automation - Automatically activate, deactivate, or complete related tasks
  • Maintenance Logic - Implement complex maintenance rules and dependencies
  • Event-Driven Maintenance - Trigger tasks based on component installation/removal

Master Task Card Actions are limited to primary and secondary Task Cards for the same CM Item or configuration-managed asset. Actions cannot affect Task Cards on different assets.

Action Configuration​

Action Table Fields:

FieldDescription
Action TypeType of action to perform
Secondary Master Task CardTarget Master Task Card for the action
DescriptionDescription of the secondary task
Reset Job Card Sequence?Whether to reset job card sequence
ScenarioWhen the action is triggered

Action Details:

When you expand an action:

FieldDescription
Action TypeType of action to perform
DescriptionScenario description
Secondary Master Task CardTarget Master Task Card
Reset Job Card Sequence?Reset job card sequence flag
Activation Delay UnitUnit for activation delay
Activation Delay PeriodDelay period value

Action Types and Triggers​

Master Task Card Actions support multiple action types, each triggered by specific events:

Work Order Completion Actions:

These actions are triggered when a work order generated from the primary Task Card is completed:

Action TypeEffectUse Case
ACTIVATEChanges secondary Task Card status to ACTIVEEnable a task after another task is completed. Example: Activate operational checks after installation task is complete.
COMPLETEMarks secondary Task Card as complete and resets next due dateClaim completion of a related task when primary task is done. Example: Complete follow-up inspection when main inspection is complete.
CREATE WOGenerates a work order from the secondary Task CardAutomatically create work for a related task. Example: Generate calibration work order after equipment installation.
DEACTIVATEChanges secondary Task Card status to INACTIVEDisable a task after another task is completed. Example: Deactivate temporary inspection after permanent fix is complete.

Component Installation Actions:

These actions are triggered when the asset associated with the primary Task Card is installed into a parent assembly:

Action TypeEffectUse Case
ON-ACTIVATEChanges secondary Task Card status to ACTIVE when component is installedEnable tasks when component is installed. Example: Activate operational checks when engine is installed on aircraft.
ON-DEACTIVATEChanges secondary Task Card status to INACTIVE when component is installedDisable tasks when component is installed. Example: Deactivate storeroom maintenance tasks when component goes on-wing.

Component Removal Actions:

These actions are triggered when the asset associated with the primary Task Card is removed from a parent assembly:

Action TypeEffectUse Case
OFF-ACTIVATEChanges secondary Task Card status to ACTIVE when component is removedEnable tasks when component is removed. Example: Activate shop inspection when engine is removed from aircraft.
OFF-DEACTIVATEChanges secondary Task Card status to INACTIVE when component is removedDisable tasks when component is removed. Example: Deactivate on-wing tasks when component is removed.

Reset Job Card Sequence​

The Reset Job Card Sequence checkbox controls whether the job card sequence for the secondary Task Card is reset when the action is triggered:

Reset Job Card Sequence = Checked:

  • Job card sequence is reset to the beginning
  • Useful when you want to restart a job card progression
  • Example: After overhaul, reset calibration job card sequence to start from first calibration

Reset Job Card Sequence = Unchecked:

  • Job card sequence continues from current position
  • Useful when you want to maintain progression
  • Example: Continue with next job card in sequence after completing related task

Activation Delay​

Actions can be configured with a delay before they take effect:

FieldDescription
Activation Delay UnitUnit for delay (DAYS, HOURS, etc.)
Activation Delay PeriodNumeric delay value

Use Cases for Activation Delay:

  • Allow time for post-maintenance stabilization
  • Coordinate with operational schedules
  • Implement mandatory waiting periods
  • Stagger related maintenance activities

Master Task Card Actions provide powerful automation but should be carefully designed and tested. Incorrect action configuration can lead to unexpected Task Card status changes or maintenance gaps.


Status and Revisions​

Maximo for Aviation introduces enhanced status management and revision control for Master Task Cards, providing better change tracking and configuration control.

Status Management​

Status Field:

Master Task Cards have a status field (MASTERPM.PLUSASTATUS) that controls their lifecycle:

StatusDescriptionTask Card Generation
DRAFTMaster Task Card is being developedNo Task Cards generated
ACTIVEMaster Task Card is approved and operationalTask Cards generated automatically
INACTIVEMaster Task Card is no longer in useNo new Task Cards generated. Existing Task Cards are deactivated
PNDREVPending revision (revision in progress)Changes are not put into effect into the new revision is activated
REVISEDPrevious revision (superseded)Historical reference only

Status Workflow:

  1. Create - New Master Task Card created with DRAFT status
  2. Configure - Set up frequencies, part numbers, actions, etc.
  3. Activate - Change status to ACTIVE when ready for use
  4. Revise - Create revision (status becomes PNDREV for new revision)
  5. Supersede - Previous revision changes to REVISED status

Task Cards cannot be created from Master Task Cards unless they are in ACTIVE status. This ensures only approved, validated tasks are used for maintenance generation.

Revision Control​

Revision Benefits:

  • Full change tracking (what changed, when, by whom)
  • Audit trail for regulatory compliance
  • Controlled change management process
  • Prevents accidental modifications to active tasks
  • Maintains historical record of all revisions

Updating Associated Task Cards:

Revising Master Task Cards in OMPs​

Master Task Cards that are part of an Operators Maintenance Program (OMP) have special revision requirements. The revision creation process and activation of the new revision must be performed within the OMP application itself, not directly in the Master Task Cards application.

OMP-Based Revision Process:

When a Master Task Card is included in an OMP:

  1. Navigate to OMP Application - Open the OMP that contains the Master Task Card
  2. Locate Task - Find the Master Task Card in the OMP Tasks list
  3. Initiate Revision - Use the OMP's revision action for the task
  4. Make Changes - Applink to the Master Task Card to make modificiations to it and save. Return to the OMP once changes are made
  5. Activate Revision - Activate the new master task card revision using the change status icon on the OMP Task row within the OMP
  6. Propagate Changes - The system automatically triggers the update to the associated Task Cards by triggering BDI validation for the affected Aircraft.

Be aware that the update of associated Task Cards is not immediate. The time taken for changes to be propagated depends on a numnber of factors including: number of aircraft and how the BDI and asynchronous job crontasks are configured.

When a Master Task Card revision is activated:

  • Automatic Update - BDI updates Task Cards during next asset validation
  • Manual Update - Use "Update Associated Task Cards?" action for immediate update

Extendable Task Cards​

The Extendable checkbox on a Master Task Card indicates that associated Task Cards can have their due dates or due counts extended through a controlled process.

Extendable Checkbox:

  • When checked, Task Cards generated from this Master Task Card can be extended
  • Extensions are created through Task Card Extension records
  • Extensions can be subject to approval workflow
  • Provides controlled flexibility for operational needs

Task Card Extension Process:

  1. Identify Need - Task Card approaching due date but cannot be completed
  2. Create Extension - Create Task Card Extension record
  3. Justify Extension - Document reason and new due date/count
  4. Approval - Submit for approval (if workflow configured)
  5. Apply Extension - Extension updates Task Card due date/count
  6. Track Extension - Extension history maintained for audit

Use Cases for Extensions:

  • Aircraft grounded for unrelated issues
  • Parts availability delays
  • Operational schedule conflicts
  • Weather or facility constraints
  • Regulatory approval for extension

Task Card extensions must comply with regulatory requirements and manufacturer limitations. Some tasks (especially CMR tasks) may not be extendable or may require regulatory approval.


Additional Tabs​

The Master Task Card application includes several additional tabs for comprehensive task documentation:

Planning Tab​

Contains Master Task Card Actions (covered in detail above) and planning information:

  • Master Task Card Actions configuration
  • Planning notes and considerations
  • Resource requirements
  • Scheduling preferences

Job Cards Tab​

Links detailed work instructions to the Master Task Card:

  • Associates Job Cards with the task
  • Job Cards define detailed work procedures and steps and resources required to peform the task (see separate guide on Job Card usage)

OMP Tab​

Shows which Operators Maintenance Program includes this Master Task Card:

  • Lists OMPs that reference this task
  • Shows task applicability within each OMP
OMP Tab

Checks Tab​

Defines which maintenance checks include this task:

  • Associates task with check-based maintenance
  • Supports A-Check, C-Check, etc. organization
  • Enables check-based work packaging

Links supporting documentation to the Master Task Card:

  • Technical manuals
  • Service bulletins
  • Engineering orders
  • Illustrated parts catalogs
  • Training materials
  • Safety documentation

Related Documentation:

  • Maintenance Task Library (MTL)
  • Operators Maintenance Program (OMP)
  • Part Number Master
  • Task Cards Application
  • Build Data Interpreter (BDI)