Assetize

All learning series · Industry solution · Part 1

Maximo Civil Infrastructure

Trace an inspection finding to a specific structure and a managed defect.

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.

  1. Are you ready to use Maximo Civil Infrastructure? Licensing and AppPoints, the records that must exist, and three checklists.
  2. Basics
  3. Configuration
  4. Practical example
  5. Practice and verify
  6. Advanced concepts

Are you ready to use Maximo Civil Infrastructure?

Civil Infrastructure inspects structures, records defects and turns them into work. The 9.2 guidance adds a 50-AppPoint install on top of the Premium or Limited user tier.

Before configuration

Both the user tier and the 50-point install need to be on the entitlement. Have a structure and its components before the first inspection.

Before the first successful journey

One structure, a component, an inspection criterion and a result you can score.

Before production use

Criteria, scoring and the path from a defect to work have owners. BIM, stitching or inference services are in scope only when those services are deployed.

Licensing, entitlement and AppPoints

Civil Infrastructure is a Maximo Manage industry solution priced at Premium, or at Limited when the three modules include it. The same guidance says the application also requires per-install licences, and the install table allocates 50 AppPoints. Those 50 points are reserved for the life of the environment. They are not a per-user charge, and they are not Spatial’s 20 or Optimizer’s 220. Users still consume their Premium or Limited ratio.

Keep four facts separate for Maximo Civil Infrastructure. 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 Civil applications are deployed and an inspection opens. The 50-point install should appear on AppPoints Usage. Installed means the applications and the install line are present. Configured means a structure has components and criteria. Usable means an inspector can store a result against a component.

Foundation configuration

You need the site, the structure as an asset or location hierarchy, and the components you will inspect. Classifications separate bridge, culvert or building elements. Photos belong to the inspection result. A map is optional and is Spatial. A linear measure is optional and is Linear. BIM models and automated defect services are extra systems.

Product configuration

Model the structure and the component. Set the inspection criteria and the score. Grant inspectors a group that records results and engineers a group that changes criteria. Review default scores before they drive work orders.

Infrastructure and integration

Inspections run in Manage. A BIM host, a photo store or an inference service needs its own route, credentials and licence. Include it only when that service is part of this workspace. The first manual inspection does not need it.

Data and operational readiness

The first journey needs one structure, one component, one criterion and one result, then a work order from a defect that fails the criterion. A missing component is data. A missing criterion is configuration. A refused save is security or object-structure authorisation. A missing install line is entitlement.

Setup order for an inspection

  1. 1. User tier and the 50-point install Both. The install is not implied by the user tier.
  2. 2. Structure and components The thing and the element.
  3. 3. Criteria and score What a defect means.
  4. 4. A result and, if it fails, work The inspection creates the follow-up.
Readiness for Maximo Civil Infrastructure
RequirementWhy neededMandatory/Conditional/OptionalWhere to configure or verifyMinimum working exampleVerification procedureConsequence if missingRemediationSource
Premium or Limited user entitlementIndustry-solution users are Premium or Limited, not Base.MandatorySuite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type.An inspector on Limited with Civil inside the three modules, or a Premium user.Read the tier after the Civil group is granted.The inspector remains Base and cannot open the applications.Change the tier. Do not rely on the install points to grant the user.Licensing in Maximo Application Suite 9.2
Install entitlement of 50 AppPointsThe guidance allocates 50 AppPoints per Civil Infrastructure install.MandatorySuite administration → Suite → Administration → AppPoints Usage, install line. Proof of entitlement.One install. Non-production draws no install points when production already has Civil.Match the dashboard to 50.The applications were copied onto the workspace and the install line is absent.Apply the 50-point install. Do not reuse another product’s install quantity.Licensing in Maximo Application Suite 9.2
Civil applications deployedThe component has its own version.MandatorySuite administration → Catalog, Manage workspaceThe structure and inspection applications open.Record the version and open one structure.The menu has no Civil inspection.Deploy the component that matches the Manage version.Modules and applications in Maximo Application Suite 9.2
A structure and a componentThe result has to name the element, not only the bridge.MandatoryThe structure hierarchy.Bridge BR-1, component Pier 2.Create the component under the structure and read the parent back.An inspection is filed against the whole structure with no element.Model the component before the inspection.Modules and applications in Maximo Application Suite 9.2
A criterion and a scoreThe defect needs a scale.MandatoryInspection criteria for the installed Civil build.Crack width, scored above a limit you set.Record one result and read the score back.Inspectors type comments and no score is stored.Enter the criterion before the first production inspection.Modules and applications in Maximo Application Suite 9.2
Object-structure and application access for the inspectorA deployed component can still refuse the user who writes the result.MandatorySecurity groups and object-structure authorisation for the Civil objects the inspector saves.Group CIVIL-INSP can save a result and cannot edit the criterion library.Save a result as the inspector. Confirm a refusal for the library.The application opens and the save is refused.Grant the application and the object structure. Keep library edits on the engineer group.User access and entitlements in MAS 9.1 and later
BIM, stitching or inferenceThose services are a different dependency from a manual inspection.OptionalThe external service’s deployment, licence and route, only when you use it.Leave them out of the first inspection.Complete a manual result with those services stopped.The first journey waits on a service the site does not have.Run the manual path. Add the service when it is deployed and licensed.Modules and applications in Maximo Application Suite 9.2

A. Ready to configure

  • The entitlement includes the user tier and the 50-point install, and the dashboard shows both.
  • Civil applications open.
  • A site exists and you can name one structure and one component.
  • Inspectors and engineers are different groups.

B. Ready for the first end-to-end journey

  • The structure and component save.
  • One inspection result scores the component.
  • A failing result can create or link work.
  • The inspector cannot change the criterion library.

C. Ready for production operation

  • Criteria and scores have an engineering owner.
  • The 50-point install is on every environment that the guidance says must carry it. Non-production is covered by the non-production install rule only when production already has the component.
  • Photo or BIM storage has capacity and an owner.
  • A refused save is checked as authorisation before anyone rebuilds the structure data.

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.

Before you start

MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.

  • Civil Infrastructure installed with a training structure.
  • A fictional component hierarchy, inspection criteria and sample photographs.

IBM sources + Assetize exercise

01 · Basics — Understand the building blocks

Civil Infrastructure connects structural assets, inspections, defects and maintenance. The structure and its components provide the context for finding and revisiting a defect.

An observation records what was seen. A defect needs location, evidence and a disposition so subsequent inspections and repairs can refer to the same issue.

Topics in this series

  • Structure hierarchy
  • Inspection design
  • Defect identity
  • Maintenance follow-up
  • History and visual context

02 · Configuration — Work through the setup

Use a training environment and match the actions to the IBM guide for your installed build.

  1. Model a training bridge and identify the exact component being inspected.
  2. Prepare the relevant inspection using your configured criteria and installed applications.
  3. Record an observation and create the corresponding defect using the supported flow.
  4. Attach a location reference and evidence, then assign a maintenance or monitoring disposition.
  5. Revisit the defect after a training repair and compare the inspection and work history.

03 · Practical example

Fictional teaching example

On fictional Bridge RB-B01, a defect belongs to bearing B2 rather than the bridge in general. A subsequent inspector must be able to find the same bearing and distinguish a repaired issue from a new one.

04 · Practice and verify

Create two nearby defects and demonstrate how each retains its own component, location, photographs and follow-up.

Expected result

A reviewer can navigate from structure to defect to follow-up work without relying on ambiguous descriptions.

Common mistakes

  • Creating a new duplicate defect on every inspection.
  • Closing defects without evidence of the chosen disposition.

05 · Advanced concepts

Explore linear/spatial views and visual inspection integration where available. Preserve engineering assessment separately from automated image detections.

IBM references

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