Assetize

Maximo guided tours · MXTOUR format

ACM and Aviation Tours

Step-by-step tours of Asset Configuration Manager and Maximo for Aviation, played on a Maximo screen. Every step is built from IBM’s published ACM and Aviation documentation, the add-on DBC scripts and the 9.2 application list, and ships in Maximo’s own MXTOUR format.

12 tours, 78 steps, 112 IBM citations, played on a Maximo screen with the records in play named on every step. Sample fleet: one operator, one site, one aircraft model and two aircraft built from it.

Put it in your Maximo

  1. Export the rows: each tour is one MXTOUR row (TOURID, APPNAME, TOUR JSON) with the aszacmaviation label bundle.
  2. Load them into MXTOUR and your label bundle. The 9.2 system serves tours through the mxtour API route.
  3. Open the application named in APPNAME. The tour offers itself the first time a user opens it.

Start here

From the manufacturer's MPD to an aircraft in service

The end-to-end ACM and Aviation flow in nine stops: load the manufacturer's tasks, build the maintenance programme, model the aircraft, create it, fly it and keep it compliant. Application PLUSACM, 10 steps.

  1. One aircraft, nine applications This tour follows a single aircraft type through ACM and Maximo for Aviation, from the manufacturer's maintenance data to daily flying. Each stop names the application that owns the step. PLUSACM
  2. 1. Maintenance Task Library Import the manufacturer's Maintenance Planning Document. The MTL is a staging area: tasks are reviewed and validated here before they become Master Task Cards. PLUSAMPD · PLUSAMPDSTATUS: DRAFT, VALID, INACTIVE
  3. 2. Master Task Cards Master Task Cards turn validated tasks into rules that generate Task Cards for every applicable aircraft or piece of equipment. PLUSMMTCAR
  4. 3. Operator's Maintenance Program The OMP is your approved maintenance programme. It holds every required task, its frequency and the aircraft it applies to. PLUSAOMP · PLUSAOMPSTATUS: DRAFT, INACTIVE, ACTIVE, PNDREV, REVISED, CANCEL, SUBMITTED, EXPIRED
  5. 4. Models The Model is the engineering reference: which positions an aircraft has and which parts may go in them. PLUSACM
  6. 5. New Aircraft and Equipment Create the aircraft's whole asset hierarchy from the Model in one step, instead of asset by asset. PLUSANEWAS
  7. 6. Assets (CM) Day to day, Assets (CM) shows each aircraft's configuration status and is where installs and removals happen. PLUSAASSET
  8. 7. Build Data Interpreter Every install, removal, meter reading or status change is checked by the BDI against the Model, in the background. PLUSABDIQ
  9. 8. Flight Log Book Flights, crew, fuel and discrepancies are recorded in the Flight Log Book. Discrepancies flow straight into work management. PLUSAFLB · PLUSAFLBACSTATUS: GROUNDED, UNKNOWN, LRTS, DRTS, RTS
  10. 9. Technical Records When an engineering change lands, a Technical Record tracks it as a campaign across every affected aircraft until it is embodied. PLUSATR

Asset Configuration Manager

Models: define what an aircraft is allowed to be

Build positions, configuration rules and the identity attributes the BDI checks every asset against. Application PLUSACM, 8 steps.

  1. What a Model is A Model is the engineering reference for one type of complex asset. Everything ACM does later is checked against it. PLUSACM
  2. A CM item comes free Saving a new Model creates its default configuration-managed item for you. PLUSACM
  3. Build Hierarchy and Position Rules This tab is the aircraft's physical structure. Right-click a node to add a child or sibling position. Standard positions are sub assembly positions, indicator S. PLUSACM · PLUSACMPOSIDNAME: PHYSICAL, ATA, UIN
  4. Model, Variant, Revision These three attributes decide an asset's current configuration. Get them right before you create aircraft. PLUSACM
  5. Minimum Equipment List Flag the Model if it carries a Minimum Equipment List. The BDI then raises a MEL code and work order when a MEL rule is not met. PLUSACM
  6. Related Aircraft and Equipment See every end-item asset built from this Model. Once assets exist, moving build positions is restricted, so settle the structure first. PLUSACM
  7. Let the BDI act on Technical Records Validate Technical Records controls whether the BDI interprets and acts on Technical Records for this Model and its assets. PLUSACM
  8. Load rules in bulk Configuration rules and flag rules have their own object structures, so a whole Model can be loaded through MIF. PLUSACM

New Aircraft and Equipment: create a whole aircraft from its Model

Complete or partial assemblies, numbering, meters and bulk loading. Application PLUSANEWAS, 7 steps.

  1. The Model is the template This application generates the full configuration-managed asset hierarchy from a Model definition. PLUSANEWAS
  2. Complete or partial Build the complete assembly, or only part of it when the rest already exists. PLUSANEWAS
  3. Bring existing assets under CM Convert assets you already have into configuration-managed assets, or create new ones straight into a storeroom. PLUSANEWAS
  4. Asset numbering Use Maximo autokey, or a scheme with prefixes and suffixes. PLUSANEWAS
  5. Meters cascade A meter added here is added to every child asset in the assembly. PLUSANEWAS
  6. The BDI checks the result Creating the assets queues them for background BDI validation. PLUSANEWAS
  7. Load a fleet Use the PLUSAMXNEWASSET object structure, or the MXLoader template, to bring in many aircraft at once. PLUSANEWAS

Assets (CM): configuration status, installs and removals

Read an aircraft's configuration status, ask the BDI to validate, install and remove parts, and track modifications. Application PLUSAASSET, 8 steps.

  1. Assets, with configuration control Assets (CM) adds the fields, tabs and actions you need to see and change the as-maintained configuration. PLUSAASSET
  2. Current Configuration tab Configuration Status, Status Date, Last Updated, Revision and Hold Revision, in one place. PLUSAASSET
  3. Ask the BDI Configuration Actions sends a validation request to the BDI. The BDI Status dialog shows the answer. PLUSAASSET
  4. Install and remove Every install and removal is kept as position history, and each one triggers BDI validation. PLUSAASSET
  5. Installs and removals by API Integrations use the dedicated PLUSAMXAPISAONOFF object structure, not a generic asset update. PLUSAASSET
  6. Modification Status tab See which Technical Records are active against this asset and how far each is embodied. PLUSAASSET
  7. BDI Actions tab The recent jobs the BDI created for this asset, so you can see what it did and why. PLUSAASSET
  8. PMs are owned by the rules Once enabled, Master PM and PM records for configuration-managed assets become read-only. Change the rule, not the PM. PLUSAASSET

Technical Records: run an engineering change across the fleet

Applicability, maintenance plan, asset status and embodiment tracking. Application PLUSATR, 8 steps.

  1. Engineering change, tracked A Technical Record models a design change that affects configuration-managed assets, and runs it as a campaign. PLUSATR
  2. Four sections Header Information, Applicability, Maintenance Plan and Asset Status. PLUSATR
  3. Applicability Which positions, parts, Models and variants the change applies to. PLUSATR
  4. Maintenance Plan What the work is and when it must be done by. This section creates the PM for each affected asset. PLUSATR
  5. Asset Status Progress of the required work, asset by asset. PLUSATR
  6. Activate Activating the record makes the BDI re-validate every affected asset in the background. PLUSATR
  7. Embodiment filters Filter the asset view by fully embodied, partially embodied, active or not applicable. PLUSATR
  8. Load records and embodiment PLUSAMXTR loads Technical Records. PLUSAMXTRASSET records embodiment against assets. PLUSATR

BDI Queue: how ACM keeps every aircraft honest

What the Build Data Interpreter checks, what triggers it, and how to keep its queue moving. Application PLUSABDIQ, 6 steps.

  1. Position by position The BDI checks configuration-managed assets against their Model, one position at a time. Assets that are not configuration-managed are not checked. PLUSABDIQ
  2. The queue Each validation request becomes a queue record in PLUSAANTRAN. PLUSABDIQ
  3. What triggers validation Aircraft status changes, serial number changes and maintenance event changes all queue a validation. PLUSABDIQ
  4. Problem codes A quantity outside a position's minimum or maximum raises a BDI problem code on that position. PLUSABDIQ · PLUSABDICOND: AOG, BMR, SIR, XDP, SSR, ISR, SMM, SEI, ENR, EBD, EBW, NAD, EBA, SED, EMC, EID, BMD, SMO, SEO, OK, INACTIVE, INVALID, ALERT, CONVERSIONS PENDING, NONSERIALIZED OK, EIR, EMR
  5. MEL work orders When a MEL rule is not met, the BDI raises a MEL code and a MEL work order. PLUSABDIQ
  6. Keep the queue short If the validation backlog grows, add monitor threads or more BDI instances. PLUSABDIQ

Maximo for Aviation

Maintenance Task Library: import the manufacturer's MPD

Import, review and validate MPD tasks before they become Master Task Cards. Application PLUSAMPD, 6 steps.

  1. Start from the MPD The MTL imports maintenance task data from the manufacturer's Maintenance Planning Document. PLUSAMPD
  2. One record per aircraft type and revision Import each MPD revision as a new MTL record or revision. PLUSAMPD
  3. Import File Load tasks from an Excel file whose columns match the MTL file format. PLUSAMPD
  4. Regulatory flags NR? marks tasks a civil aviation authority requires. Soft Task? marks flexible ones. PLUSAMPD
  5. Frequencies A task can carry more than one frequency definition. PLUSAMPD
  6. VALID unlocks Master Task Cards Only VALID MTL records can create Master Task Cards. PLUSAMPD · PLUSAMPDSTATUS: DRAFT, VALID, INACTIVE

Master Task Cards: rules that generate the work

Part numbers, due rules, actions, revisions and how cards join the OMP. Application PLUSMMTCAR, 7 steps.

  1. Cards that make cards A Master Task Card generates Task Cards automatically for every applicable aircraft or piece of equipment. PLUSMMTCAR
  2. Linked to part numbers Link the card to one or more CM part numbers. That link drives PM generation through BDI validation. PLUSMMTCAR
  3. When is it due? Three ways: intervals and thresholds, time-based iterations, or meter-based iterations. PLUSMMTCAR
  4. Planning tab and actions Master Task Card Actions set what happens automatically when something happens to the primary task. PLUSMMTCAR
  5. Job Cards and OMP tabs Job Cards link the work instructions. The OMP tab shows which programme uses this card. PLUSMMTCAR
  6. Revision control Every change is revised and tracked. MASTERPM.PLUSASTATUS controls the card's lifecycle. PLUSMMTCAR
  7. Joining an OMP To add a card to an OMP it must relate to the Model through a part number and share the OMP's Operator. PLUSMMTCAR

Operator's Maintenance Program: your approved programme in Maximo

Effectivity, checks, modifications and activation into per-aircraft Task Cards. Application PLUSAOMP, 7 steps.

  1. The approved programme The OMP holds every required task, its frequency and the aircraft it applies to. PLUSAOMP
  2. List page Every OMP with its revision and status. REVISED and INACTIVE are hidden by default. PLUSAOMP · PLUSAOMPSTATUS: DRAFT, INACTIVE, ACTIVE, PNDREV, REVISED, CANCEL, SUBMITTED, EXPIRED
  3. Effectivity Decide which aircraft each task applies to, with expressions such as PREMOD, POSTMOD, MODEL, VARIANT or SERIALRANGE. PLUSAOMP
  4. Checks and intervals Group tasks into checks, on calendar or meter intervals. PLUSAOMP
  5. Before and after modification A task can apply only before, or only after, a modification. PLUSAOMP
  6. Activate Activation creates the individual Task Cards for each aircraft the OMP covers. PLUSAOMP
  7. Watch for expiry Switch on the OMP BDI option to monitor expired programmes. PLUSAOMP

Flight Log Book Setup: one template, many aircraft

Meters, fuel tanks, automation rules and which aircraft use the setup. Application PLUSAFLBSU, 3 steps.

  1. The template The setup defines operational parameters, meters, fuel tanks and automation rules for the Flight Log Books of the aircraft it covers. PLUSAFLBSU · PLUSAFLBSTATUS: DRAFT, INACTIVE, ACTIVE, LOCK
  2. Applies To Pick the aircraft models and configurations that use this setup. PLUSAFLBSU
  3. Options worth setting Munitions Required? tracks munitions. Status Symbol Required? shows an icon driven by the most severe open discrepancy. PLUSAFLBSU

Flight Log Book: from flight to fix

Flight data, aircraft status, discrepancies into work management, and BDI validation. Application PLUSAFLB, 5 steps.

  1. Everything about the flight Crew, fuel, munitions and flight data for each aircraft, in one record. PLUSAFLB
  2. Fed by the flight schedule Completed scheduled flights create flight records automatically. PLUSAFLB
  3. Aircraft status The aircraft's status runs from GROUNDED to RTS. A status change also queues BDI validation. PLUSAFLB · PLUSAFLBACSTATUS: GROUNDED, UNKNOWN, LRTS, DRTS, RTS
  4. Discrepancies become work A discrepancy entered here goes straight into work management for tracking and resolution. PLUSAFLB
  5. Validate the log The FLB BDI option turns on Flight Log Book validation. PLUSAFLB

Engineering Assessment Orders: the approval path

The EAO status path as IBM's DBC scripts define it: applicability approval, then compliance approval. Application PLUSMEAO, 3 steps.

  1. Two approvals An EAO moves through applicability approval first, then compliance. These are the statuses IBM's scripts define for it. PLUSMEAO · PLUSMEAOSTATUS: DRAFT, WAPPR_APPLICABILITY, APPR_APPLICABILITY, INPRG_COMPLIANCE, WAPPR_COMPLIANCE, APPR, REJECTED, CLOSED, CANCEL
  2. Applicability DRAFT, then WAPPR_APPLICABILITY and APPR_APPLICABILITY. PLUSMEAO · PLUSMEAOSTATUS: DRAFT, WAPPR_APPLICABILITY, APPR_APPLICABILITY, INPRG_COMPLIANCE, WAPPR_COMPLIANCE, APPR, REJECTED, CLOSED, CANCEL
  3. Compliance INPRG_COMPLIANCE and WAPPR_COMPLIANCE, then APPR. REJECTED, CLOSED and CANCEL end the order. PLUSMEAO · PLUSMEAOSTATUS: DRAFT, WAPPR_APPLICABILITY, APPR_APPLICABILITY, INPRG_COMPLIANCE, WAPPR_COMPLIANCE, APPR, REJECTED, CLOSED, CANCEL

The ACM lesson · The Aviation lesson · UI Playground