Nuclear Asset Management Integration
Our founder's prior work with IBM Canada
Challenge
Canada's largest nuclear facility needed bi-directional integration between IBM Maximo and Oracle Primavera P6 for nuclear-grade asset and schedule management, one of the most complex Maximo integrations on record.
Solution
Our founder worked on this alongside IBM Canada. The integration was built on IBM MQ for guaranteed-delivery messaging and IBM Integration Bus message flows for transformation and routing, connecting 26+ data points across third-party systems. On the Oracle side he designed PL/SQL transformation pipelines that ran within strict SLA windows, and resolved 100,000+ malformed BLOB records through data remediation.
Results
- ✓ 26+ system integration points
- ✓ Guaranteed-delivery messaging on IBM MQ
- ✓ Transformation and routing in IBM Integration Bus message flows
- ✓ 100,000+ malformed BLOB records fixed
- ✓ Bi-directional Maximo ↔ Primavera P6
This is our founder’s prior experience with IBM Canada, not a DB Realm Inc. engagement. We include it as background for our integration work. The work was for Bruce Power, a nuclear facility that operates under strict regulation: every data transformation has to be auditable, integration points have to be reliable, and SLA windows do not move.
The project connected IBM Maximo’s asset management system with Oracle Primavera P6’s project scheduling, with data flowing both ways for maintenance planning, work order management and schedule optimization.
The integration layer
In a regulated setting a message that goes missing is a problem, not an inconvenience, so the integration was built on IBM’s messaging stack:
- IBM MQ carried the messages between the asset-management system and the systems around it. Its guaranteed-delivery model means a message is held until the receiving side has taken it, so a slow or unavailable system does not cause a silent loss.
- IBM Integration Bus (IIB) message flows did the transformation and routing: reshaping each message into the format its destination expected and sending it to the right place.
Where the Oracle database work fits
The Oracle database work sat alongside the messaging layer. PL/SQL transformation pipelines ran within the strict SLA windows.
A separate remediation effort fixed 100,000+ malformed BLOB records that were corrupting integration payloads. Previous teams had not found the root cause.