All learning series · Industry solution · Part 1
Maximo Aviation
Model an aircraft once, then let the build data interpreter (BDI) check every installed part against it.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Maximo Aviation? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Maximo Aviation?
Aviation is the industry solution for aircraft and component maintenance. Asset Configuration Manager can share a build idea and is still a different add-on with a shorter module list.
Before configuration
Aviation is Premium or Limited. The 9.2 install table does not list an Aviation install quantity. Have a model and a serialised assembly before the first build discrepancy.
Before the first successful journey
One aircraft model, positions, one serialised assembly, and the validation behaviour your build uses for a discrepancy.
Before production use
Model rules, airworthiness roles and the discrepancy process have owners. ACM flight logs are not this product’s entitlement.
Licensing, entitlement and AppPoints
Aviation is a Maximo Manage industry solution. The MAS 9.2 licensing guidance prices it at Premium, or at Limited when the three modules include Aviation’s modules. The modules page lists Aircraft and Equipment Configuration Management, Consists, Data Import, Flight Log Exchange, Orders, Motor Pool, Operations, Safety and Quality Management, and Warranties. There is no Aviation install quantity on the install table. ACM is a separate add-on whose modules are Asset Configuration Manager and Flight Logs. Entitle each product you actually grant.
Keep four facts separate for Maximo Aviation. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Confirm the Aviation applications open and the component version matches the build you will follow for discrepancy behaviour. ACM, if it is also installed, stays a separate menu. Installed means Aviation opens. Configured means a model has positions and allowed parts. Usable means a serialised assembly shows a build you can validate.
Foundation configuration
You need the site, the aircraft or assembly model, positions, the items a position accepts, and one serialised parent. Variants matter when two standards share a model. Meters and life sit on the components. People and security groups split engineering from the line. A hangar location is useful and is not the model.
Product configuration
Create the model, positions, allowed items and any variant. Create the serialised assembly from the model. Set the validation options the installed build uses before you raise a discrepancy. Grant engineering a group that edits the model and maintenance a group that fits parts. Review defaults that accept any part in a position.
Infrastructure and integration
Aviation runs in Manage. A flight-log feed or an OEM load is an external system with its own format, credentials and licence. No optimization service is required for the first build. Optimizer can consider aviation zones later, and that is the Optimizer course.
Data and operational readiness
The first journey needs one model, one serialised assembly and one build position with a known allowed part. Fit the part and read the build back. A discrepancy journey needs the validation option turned on for that model. A missing model is configuration. A missing serial is data. An ACM-only menu is the wrong product.
Setup order for an aircraft build
- 1. Aviation entitlement Premium or Limited. Not the ACM add-on row.
- 2. Model, positions, allowed parts, variants The rules.
- 3. Serialised assembly The parent the guidance treats as the asset.
- 4. Fit a part and read the build Then a discrepancy only if validation is configured.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Aviation industry-solution entitlement | Aviation users are Premium or Limited. The install table has no Aviation quantity. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | An engineer on Premium, or Limited with Aviation modules inside the three. | Read the dashboard tier after the Aviation groups are applied. | The user is Base, or only ACM is entitled. | Grant Aviation on its own. Keep ACM as a separate decision. | Licensing in Maximo Application Suite 9.2 |
| Aviation applications, not only ACM | The module lists differ. Flight Logs under ACM is not Flight Log Exchange under Aviation. | Mandatory | Suite administration → Catalog, Manage workspace | An Aviation configuration or build application opens. | Record the Aviation version and open a model. | Only ACM menus exist. | Deploy Aviation for this workspace before this course’s journey. | Modules and applications in Maximo Application Suite 9.2 |
| A model with positions and allowed parts | The build is checked against the model. | Mandatory | Aviation model, positions, allowed items. | Model AC-1, one position, one allowed part. | Save and read the position back. | A serial accepts a part the model does not list. | Set the allowed parts before the assembly is created. | Modules and applications in Maximo Application Suite 9.2 |
| One serialised assembly | The journey is about a specific tail or assembly, not the model alone. | Mandatory | Assets or the Aviation assembly application, in the site. | Assembly TAIL-1 built from AC-1. | The assembly lists the model’s positions. | The model exists and there is no serial to fit. | Create the assembly from the model. | Modules and applications in Maximo Application Suite 9.2 |
| Validation options for a discrepancy | Discrepancy behaviour follows the options on the model and the build you run. | Conditional | The model’s validation settings for your Aviation build. | Validation on for the training model, one known bad part. | Attempt the bad part and read the message the installed build returns. | A bad part saves because validation was left off. | Set the option before you teach the discrepancy path. | Modules and applications in Maximo Application Suite 9.2 |
| Separate groups for model editors and fitters | Line staff should fit allowed parts without rewriting the model. | Mandatory | Manage → Security → Security Groups, and the suite user type | AVI-ENG edits the model. AVI-LINE fits parts. | Sign in as the line user and confirm the model rules are read only. | A fitter changes an allowed-part rule. | Remove model save from the line group. | User access and entitlements in MAS 9.1 and later |
A. Ready to configure
- Aviation is on the entitlement at Premium or Limited.
- The Aviation applications open and the version is recorded.
- A site and a part exist.
- ACM access, if any, is recognised as a different product.
B. Ready for the first end-to-end journey
- The model and the serialised assembly save.
- An allowed part fits and reads back on the position.
- A disallowed part follows the validation setting you configured.
- The line user cannot edit the model.
C. Ready for production operation
- Models, variants and life limits have an engineering owner.
- External flight or OEM feeds have their own access and an agreed owner.
- Aviation zones used by Optimizer are configured only when that model will run.
- ACM and Aviation security are reviewed as two grants.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Aircraft maintenance journeys and worked examples
Before you start
MAS learning path for Maximo Aviation. BDI behaviour and codes changed across releases (7.6.8 added BDI enhancements), so follow the IBM pages for the build you run.
- Maximo Manage with the Aviation component enabled.
- The BDI service installed and configured for your environment, with validation options set on the training model.
- A training aircraft model and one fictional serialised assembly to work on.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Maximo Aviation keeps two sets of data. Engineering reference data says what may be installed and where: the as-designed configuration. Operational data records what is installed, on which serial number, with what history: the as-built and as-maintained configuration.
The build data interpreter (BDI) sits between the two. It compares the operational data with the model's reference data and rules, then reports a configuration status and any findings.
Models, variants and sub models keep the reference data small. One model covers several aircraft standards through variants. A sub model marked Installable defines a major assembly, such as an engine, once for reuse in several positions or asset types.
BDI configuration rules handle anything conditional. A position, a part, a Master PM or a meter formula can apply only to a variant, an end-item serial range, a path in the structure, or when another part is fitted elsewhere.
A closed work order shows the maintenance was done. A valid BDI status shows the resulting configuration matches the model. Check both.
Aviation accepts some transactions out of chronological sequence, such as a late-recorded installation, removal or meter reading. A backdated entry changes history, so validate again afterwards.
The product has four functional areas: Configuration & Master Data, Core Operations, Quality Management and Customer Management. This lesson covers the first, plus the configuration side of Core Operations.
| Component | What it does | Typical output |
|---|---|---|
| Model | Defines the allowable (as-designed) structure of an aircraft or major assembly. | Build positions and the parts each one accepts. |
| Variant | A version of a model. Rules switch positions, parts and maintenance on or off per variant. | One model covering several aircraft standards. |
| Installable sub model | Defines a major sub-assembly once, such as an engine or landing gear. | Reuse across positions and asset types. |
| Build position | A slot in the model's structure where a part may be fitted. | A position with its path in the structure. |
| CM item | A configuration-managed part that can be fitted in a build position. | The part numbers allowed per position. |
| End item | The top-level asset, such as the aircraft, that a sub-assembly is fitted to. | The serial number that serial-range rules test. |
| Build data interpreter (BDI) | Compares operational data with the model's reference data and rules. | A configuration status and a list of findings. |
| BDI configuration rules | Make a position, part, Master PM or meter formula apply only under a condition. | Conditional applicability without extra models. |
Topics in this series
- Reference data versus operational data
- Models, variants and installable sub models
- Build positions and CM items
- BDI configuration rules
- Configuration status and findings
- Component installation history
- Configuration-driven maintenance
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Define the training model: create its build positions and record the CM items each position accepts.
- Add variants for the aircraft standards you need to tell apart, for example Standard and Long-range. Set up shared assemblies, such as the engine, as Installable sub models.
- Add BDI configuration rules for anything conditional. Ask "this applies only when…?". A position only on some variants (XF), end-item serials (XE) or paths (X1). A part only on some variants (HO) or end-item serials (HN). A part only when another part is fitted elsewhere (H2, or H3 with a serial range). Master PMs (C1–C3) and meter formulas (C4–C6) by path, variant or serial range.
- Configure the model's validation options so BDI checks operational changes against the model's reference data and rules.
- Build the as-built structure for one training aircraft against the model, with a serial number on every installed component.
- Run BDI and record the baseline status. Clear every finding before the next step, so new findings are clearly yours.
- Remove one component and install a replacement through the supported process.
- Run BDI again. Compare the structure, the component histories and the status before and after the change.
03 · Practical example
Fictional teaching example
Training model TA-100. A service bulletin allows fuel pump P/N 2000 in position FUEL-1 only on aircraft serials 001–050; later aircraft take P/N 2001. That is one CM item to end-item serial range rule (HN) on FUEL-1. Aircraft S/N 049 has its pump swapped for another P/N 2000: the serial number changes, the position stays, and BDI passes. Aircraft S/N 051 gets a P/N 2000 by mistake: the work order closes normally, and BDI flags FUEL-1 as not applicable. That second case is the reason to run BDI.
04 · Practice and verify
Build a before/after sheet for each change: end-item serial, model and variant, build position, CM item part number, component serial number, the rule codes that apply, the work order reference and the BDI status with its findings.
Expected result
The removed component keeps its own history under its serial number. The new component is traceable to the work order. BDI reports a valid configuration for the selected model and variant.
Common mistakes
- Losing removed-component history: history follows the serial number, not the position.
- Treating a closed work order as a valid configuration. Check the BDI status as well.
- Putting the rule on the wrong object. Use a position rule when the position itself is conditional, and a CM item rule when only the part choice is.
- Starting without a clean baseline, so old findings look like new ones.
- Backdating an installation or meter reading without running BDI again.
05 · Advanced concepts
Make maintenance follow the actual build with Master PM and meter formula rules (C1–C6), which IBM calls dynamic maintenance plans. Then plan the work with Operator Maintenance Programs, Master Task Cards, the Maintenance Task Library and Work Packages that bundle different work-order types for one hangar visit. Record service bulletins as technical publications, assess them through Engineering Assessment Orders and turn them into configuration rules. Outside aviation, the Complex Assets accelerator runs the same applications under industry-neutral names for rail, marine and space. It needs Manage 9.0.x or later with the Aviation component enabled; check the Manage compatibility matrix before you install it.
IBM references
- IBM Maximo Aviation — Configuration-management design concept
- IBM Maximo Aviation — BDI configuration rule matrix
- IBM Maximo Aviation — Application schematic
- IBM Maximo Aviation — Complex Assets accelerator
- IBM documentation — Configuring validation options for models
- IBM support — Maximo Aviation and ACM build data interpreter on MAS
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench