Skip to main content

Part Number Master

Overview​

The Part Number Master application is a foundational component of Maximo for Aviation that provides comprehensive management of part numbers, including Configuration-Managed (CM) part numbers. This application serves as the central repository for all part number definitions that are essential for aircraft configuration management, maintenance planning, and inventory control. The application is a modified version of the core Manage Item Master application with additional fields, tabs and related attributes to manage configuration-managed part numbers. Configuration-Managed Part Numbers represent the components that make up an aircraft or complex asset.

CM Part Numbers are used in Models and form part of the engineering reference data used to define an as-designed configuration. They establish the baseline for what components should be installed on an aircraft and provide the framework for tracking actual vs. designed configurations.

The Part Number Master is tightly integrated with the Model application, Master Task Cards, Operators Maintenance Program (OMP) and the Build Data Interpreter (BDI) to ensure configuration compliance and automated maintenance program management.

Key Capabilities:

  • Define and manage part numbers with comprehensive attributes
  • Establish configuration-managed part numbers for aircraft components
  • Define serial number formats and ranges for traceability
  • Create serial range usable-on codes (UOCs) for effectivity management
  • Display Master Task Cards for CM Parts (used for automated Task Card generation)
  • Support interchangeable parts and alternates
  • Manage part specifications, vendors, and storeroom locations
  • Track part assembly structures and relationships
  • Define ATA chapter codes for system organization
  • Support both hardware and software part number management
Part Number Master Main Screen

Field Information​

The Part Number Master application contains numerous fields that define the characteristics, attributes, and relationships of each part number. Understanding these fields is essential for consultants implementing the system and ensuring data quality.

Core Identification Fields​

Field NameDescriptionExample ValueRequired
Part NumberThe unique identifier of the PartAPU-7766Yes
Part SetThe Part Set to which the Part BelongsAVINPNSETYes
DescriptionA detailed description of the partAuxillary Power UnitYes

The Part Number in combination with the Part Set field forms its unique identifier in the system and once saved, it cannot be changed. Plan your part numbering scheme carefully before implementation.

Classification and Categorization​

Field NameDescriptionExample ValueNotes
CategoryThe type of part (HARDWARE, SOFTWARE, etc.)HARDWAREUsed to classify parts by type
Software TypeThe type of software if categorized as SOFTWAREFLS (Field Loadable Software)Only applicable for software parts
ATA CodeAir Transport Association chapter code49-00 (APU)Organizes parts by aircraft system
Commodity GroupHigh-level commodity classificationAVIONICSFor procurement and inventory grouping
Commodity CodeDetailed commodity classificationNAVIGATION_EQUIPMENTMore specific than commodity group

Common Part Categories:

  • HARDWARE - Physical components and assemblies
  • SOFTWARE - Software loads, firmware, and applications
  • ENGINE - Aicraft Engine
  • APU - Auxilliary Power Unit

Configuration Management Fields​

Field NameDescriptionExample ValueImpact
Configuration-Managed?Indicates if this is a CM part number☑ (checked)Enables use in Models and BDI validation
Aircraft Part?Indicates if this part is used on aircraft☑ (checked)Determines if part appears in aircraft BOMs
Rotable?Indicates if part is repairable/rotable☑ (checked)Affects inventory and maintenance processes
Serial FormatFormat of serial numbers for this partAANNNDefines expected serial number pattern
Position Code Required?Whether position code is mandatory☐ (unchecked)Controls position tracking requirements
Hazardous?Indicates if part contains hazardous materials☐ (unchecked)Triggers special handling requirements

Configuration-Managed parts are the foundation of the Model application. Only CM parts can be used to define aircraft build hierarchies and configuration rules.

Serial Format Patterns:

  • A - Alphabetic character
  • N - Numeric digit
  • X - Alphanumeric character (letter or number)
  • AANNN - Two letters followed by three numbers (e.g., AB123)
  • NNNNN - Five numeric digits (e.g., 12345)
  • AANNNN - Two letters followed by four numbers (e.g., XY1234)

Inventory and Procurement Fields​

Field NameDescriptionExample ValuePurpose
Shelf Life?Indicates if part has a shelf life☐ (unchecked)Triggers expiration tracking
Preferred?Indicates if this is a preferred part☐ (unchecked)Guides procurement decisions
Kit?Indicates if part is a kit of components☐ (unchecked)Affects issue and inventory processes
Replenishment?Indicates if part should be auto-replenished☐ (unchecked)Triggers automatic reorder
Add as Consumable Part?Add to consumable parts list☐ (unchecked)Makes part available for consumption

Monitoring and Tracking​

Field NameDescriptionExample ValueUsage
Monitoring TypeType of condition monitoring appliedHT (Hard Time)Defines monitoring approach
Meter GroupGroup of meters associated with partENGINE_METERSLinks to meter definitions
MeterSpecific meter for tracking usageFLIGHT_HOURSPrimary usage meter
MSDSMaterial Safety Data Sheet referenceMSDS-12345Safety information reference

Monitoring Type Examples:

  • CM - Condition Monitoring
  • HT - Hard Time
  • LLP - Life Limited Part
  • OC - On Condition
  • ST - Soft Time

Serial Ranges for Part Number​

The Serial Ranges functionality allows for the definition of one or more Serial Range Usable on Codes (UOC) for each configuration-managed part number. Serial Range UOCs are a powerful feature that enables precise control over which serial numbers of a part are applicable to specific aircraft or configurations.

Purpose of Serial Range UOCs:

  • Define effectivity for specific serial number ranges
  • Support engineering changes that affect only certain serial numbers
  • Enable configuration rules based on component serial numbers
  • Track which part serial numbers are valid for specific aircraft

The Serial Range UOC is a unique value within the context of the CM Part Number that is used to identify a range of serial numbers. These UOCs are then referenced within specific configuration rules in the Model application to specify which positions or part numbers are valid for specific ranges of end item serial numbers.

Serial Ranges for Part Number

Serial Range UOC Structure​

Each Serial Range UOC consists of two key components:

ComponentDescriptionExample
Serial Range Usable on CodeUnique identifier for the serial rangeUOC1, UOC2, EARLY_BUILD, LATE_BUILD
Serial Range ExpressionDefines the actual serial numbers included10001..19999, 20000..99999

Serial Range Expression Formats:

The Serial Range Expression can be defined using three different formats:

  1. Comma-Separated List of Serial Numbers

    • Format: Individual serial numbers separated by commas
    • Example: AA001, AA004, AA009
    • Use Case: When only specific, non-consecutive serial numbers are affected
    • Result: Only the explicitly listed serial numbers are included
  2. Range Notation Using Double Dots

    • Format: Start serial number, double dots (..), end serial number
    • Example: A001..A100
    • Use Case: When a continuous range of serial numbers is affected
    • Result: Includes A001, A002, A003, ... all the way to A100 inclusive
    • Note: The system automatically includes all serial numbers between start and end
  3. Combination of Both Formats

    • Format: Mix of individual serial numbers and ranges
    • Example: A001, A003, A006..A009
    • Use Case: When you need both specific serial numbers and ranges
    • Result: Includes A001, A003, A006, A007, A008, A009
    • Note: Provides maximum flexibility for complex effectivity scenarios

Serial Range Expression Examples:

ScenarioUOC CodeSerial Range ExpressionInterpretation
Early production unitsEARLY_PROD10001..19999All serial numbers from 10001 through 19999
Late production unitsLATE_PROD20000..99999All serial numbers from 20000 through 99999
Specific test unitsTEST_UNITST001, T002, T005, T010Only these four test serial numbers
Mixed effectivityMIXED_EFF1001..1050, 1075, 1100..1150Range 1001-1050, plus 1075, plus range 1100-1150
Pre-modificationPRE_MOD5001..5500, 5550..5600Two separate ranges before modification
Post-modificationPOST_MOD5601..9999All units after modification cutoff

Creating Serial Range UOCs​

Step-by-Step Process:

  1. Navigate to the Serial Ranges tab in the Part Number Master
  2. Click Add Row to create a new serial range UOC
  3. Enter a unique Serial Range Usable on Code (e.g., UOC1, EARLY_BUILD)
  4. Define the Serial Range Expression using one of the three formats
  5. Validate the expression syntax
  6. Save the serial range UOC

Serial Range UOC codes must be unique within the context of a single part number. However, the same UOC code can be used across different part numbers with different serial range expressions.


Master Task Cards for Part Number​

The Master Task Cards for Part Number section displays all Master Task Cards that are related to the current configuration-managed part number. This relationship is fundamental to Maximo for Aviation's automated preventive maintenance generation capability and ensures that the correct maintenance tasks are created for each installed component.

Relationship Overview:

  • Master Task Cards are linked to part numbers in the Master Task Card application
  • The relationship is typically established when creating or editing Master Task Cards
  • Multiple Master Task Cards can be associated with a single part number
  • Each task card defines specific maintenance requirements for the component
  • The relationship drives automated PM generation through BDI validation
Master Task Cards for Part Number

Master Task Card Information Display​

The Master Task Cards table shows key information about each related task card:

ColumnDescriptionExample Value
Master Task CardUnique identifier for the task card1013, 1014, 1015, 1016
Task CodeShort code identifying the task typeRS, DS, GVI, DVI
ATA CodeATA chapter code for the task49-00 (APU)
Master Task Card TypeCategory of maintenance taskCOMPONENT, AIRCRAFT, SYSTEM
DescriptionBrief description of the taskAPU Overhaul, APU Life Limit, APU Inspection
OMPOperators Maintenance Program referenceXJET-001

Additional Tabs and Functionality​

The Part Number Master application includes several additional tabs that provide extended functionality for managing part numbers, their relationships, and associated data.

Applicability Tab​

Defines where and how the part number can be used:

  • Aircraft models and variants
  • System applicability
  • Configuration restrictions
  • Interchangeability rules

Interchangeable Parts Tab​

Manages alternate and interchangeable part numbers:

  • Define substitute part numbers
  • Specify interchangeability conditions