Federal facility teams running IA-FMS on Maximo sit on top of years of Building Investment Analysis and Building Investment Evaluation asset and work order history — and most of that history stays locked inside a system that front-line technicians rarely open on a mobile device in the field. The gap between the BIA/BIE data model and a modern, mobile-first CMMS layer is the reason integration projects keep stalling: teams either rebuild years of asset history from scratch in a new system, or they keep two disconnected systems running in parallel indefinitely. Neither approach is necessary once the integration is scoped correctly around the specific data objects IA-FMS and Maximo already share. Book a demo to see how OxMaint layers onto existing Maximo data without a rebuild.
Guide · Federal Facilities · System Integration
Government IA-FMS Maximo Integration Software Guide
A phase-by-phase approach to bringing BIA and BIE asset, work order, and inspection data out of IA-FMS on Maximo and into a modern, mobile CMMS layer that field technicians will actually use — without discarding the historical record.
Why IA-FMS on Maximo Needs a Modern Layer, Not a Replacement
IA-FMS was built on Maximo to standardize facility condition assessment and capital planning data across federal agencies, and for that purpose the underlying data model is thorough. The problem most site teams report is not the data itself — it is access to that data at the point of maintenance work. A technician standing at an asset in a mechanical room rarely has an efficient way to view BIA condition history or log a corrective action against it without returning to a desktop terminal.
Source System
IA-FMS on Maximo
Holds BIA condition assessments, BIE evaluation scores, asset hierarchy, and historical work order records built up over multiple assessment cycles.
connects to
Integration Layer
OxMaint Sync Layer
Reads and writes asset, work order, and condition data on a scheduled or event-driven basis, keeping both systems aligned without duplicate manual entry.
delivers to
Field Layer
Mobile CMMS App
Gives technicians asset history, PM schedules, and corrective work order creation from a phone or tablet, on-site, without a Maximo terminal.
What Each System Is Built For — and Where Integration Adds Value
The table below separates what IA-FMS on Maximo does well from what a mobile CMMS layer adds, so the integration is scoped to close the actual gap rather than duplicating functionality that already works.
| Capability |
IA-FMS on Maximo |
Mobile CMMS Layer |
Integration Behavior |
| Condition assessment scoring |
System of record — BIA/BIE methodology, multi-cycle history |
Displays current score, does not replace scoring methodology |
Read from Maximo, displayed in mobile asset record |
| Mobile work order creation |
Limited mobile access, typically desktop-first workflow |
Native mobile creation, photo attachment, offline capable |
Created in CMMS, synced back to Maximo as source record |
| PM scheduling and dispatch |
Scheduling exists but technician-facing dispatch is desktop-centric |
Push notifications, route optimization, technician assignment |
PM schedule pulled from Maximo, dispatch managed in CMMS |
| Asset hierarchy and history |
Authoritative multi-year asset and capital record |
Reflects current hierarchy for field reference |
One-way sync from Maximo as system of record |
| Photo and condition evidence |
Limited native photo capture from the field |
Photo capture attached directly to work order at point of service |
Captured in CMMS, attached to Maximo work order record |
INTEGRATION · OXMAINT · FEDERAL FACILITIES
Your Maximo Data Does Not Need to Move to Become Mobile
OxMaint reads and writes to your existing IA-FMS Maximo environment, giving field technicians a mobile layer for work orders, PM, and inspections while BIA and BIE records stay exactly where they are.
Scoping the Integration: Four Phases That Avoid a Data Rebuild
1
Map the Shared Data Objects
Identify which asset, work order, and condition fields exist in both systems and which fields are unique to IA-FMS. Only the shared objects need a sync mapping — asset-specific BIA methodology fields typically stay in Maximo as the authoritative source.
2
Define the Direction of Truth for Each Object
Asset hierarchy and condition scores typically flow one direction, from Maximo to the mobile layer. Work orders created in the field typically flow the other direction, from the mobile layer into Maximo as the system of record. Defining this per object prevents sync conflicts later.
3
Pilot on One Facility or Building Before Full Rollout
Running the sync on a single facility for a defined pilot period surfaces mapping issues, field-level mismatches, and technician workflow gaps while the impact of a correction is limited to one site rather than the full portfolio.
4
Roll Out With a Defined Sync Schedule
Once the pilot validates the mapping, extend the sync across the full asset portfolio on a defined schedule — near-real-time for work order status, and a daily or scheduled batch for condition and asset hierarchy updates that change less frequently.
Expert Review
The recurring mistake in federal facility integration projects is treating it as a data migration rather than an integration. Migration means picking a winner and moving everything, which discards years of BIA assessment history that took multiple cycles to build. Integration means defining, object by object, which system is the source of truth and building a sync layer that respects that boundary. The projects that succeed scope this narrowly at the start — often just work orders and PM dispatch in the first phase — and expand the sync mapping only after the first phase has run cleanly for a full assessment cycle.
Priya Nathan, PMP
Project Management Professional · 12 years federal facility systems integration and IA-FMS/Maximo implementation support
Frequently Asked Questions
Does integrating a mobile CMMS require replacing our Maximo environment?
No. The sync layer reads and writes to your existing Maximo environment as the system of record for BIA and BIE data, while the mobile layer handles field-facing work order creation and dispatch.
How long does an IA-FMS Maximo integration pilot typically take?
A single-facility pilot scoped to work orders and PM dispatch typically runs 4 to 8 weeks, including mapping validation and technician onboarding.
Start free to see the mapping template used for pilot scoping.
What happens to BIA condition assessment history during integration?
Condition assessment history stays in Maximo as the authoritative record. The mobile layer displays current scores for field reference but does not alter or duplicate the BIA/BIE methodology itself.
Can technicians work offline if field connectivity is unreliable?
Yes, work orders and inspection data captured offline queue locally on the device and sync to Maximo once connectivity is restored, so field work is not blocked by intermittent signal at remote facilities.
Who should be involved in defining the data mapping before a pilot starts?
Facility engineering leads who understand the BIA/BIE data structure and the IT team managing the Maximo environment should jointly define the mapping.
Book a demo to review a sample mapping session.
INTEGRATION · FEDERAL FACILITIES · OXMAINT
Give Your Maximo Data a Mobile Front End Without a Rebuild
OxMaint integrates with existing IA-FMS Maximo environments to give field technicians mobile work orders, PM dispatch, and condition reference — while BIA and BIE records remain exactly where your assessment cycle expects them.
