Connect IBM Maximo (CF) to KODE OS for work orders, asset data integration
Overview
Use this integration to connect IBM Maximo to KODE OS for work orders and asset data. You can discover devices and points, collect operational data with hybrid historical collection over REST, and use supported actions for maintenance and asset workflows.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
- Discover Assets
Prerequisites
- An active account with IBM Maximo (CF) and access to their API or developer portal
- API key or token from the IBM Maximo (CF) platform
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the IBM Maximo (CF) platform or admin console
- Navigate to the API settings, developer section, or account settings
- Generate a new API key or token
- Copy the key and store it securely — you will need it when configuring the connector in KODE OS
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for IBM Maximo (CF)
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
Discover Devices and Points
After configuring the connector, click Discover on the connector detail page. KODE OS will query the IBM Maximo (CF) system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.What Data You Get
Work Orders
Maintenance and service requests including title, description, status, priority, assignee, due dates, vendor response, resolution details, and cost estimates KODE OS maps IBM Maximo (CF) data to these standard fields:Polling Schedule
- WorkOrder — Default polling: 30 minutes (min: 30 minutes, max: 1 days)
- Asset — Default polling: 1 days (min: 1 days, max: 1 days)
Available Actions
This integration supports actions that allow you to send commands to the IBM Maximo (CF) system. Available actions are displayed on the device or entity detail page in KODE OS.Example Request
Expected Result
- KODE OS sends the action to the external API using the configured connector credentials
- The external system returns success (typically HTTP 2xx) and processes the requested operation
Use Cases
Once connected, this integration enables you to:- Centralize maintenance requests and work order status from facility management systems
- Create and update work orders directly from KODE OS when issues are detected
- Track maintenance KPIs including response time, completion rate, and cost
Troubleshooting
Authentication or connection error
Authentication or connection error
Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the API key or token is valid and has not been revoked or expired in the IBM Maximo (CF) platform.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the IBM Maximo (CF) system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
Data collection stops or gaps appear
Data collection stops or gaps appear
Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the IBM Maximo (CF) API.