> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IBM Maximo (FDH)

> Connect IBM Maximo (FDH) to KODE OS for work orders data

> Connect IBM Maximo (FDH) to KODE OS for work orders data integration

## Overview

Use this integration to connect IBM Maximo (FDH) to KODE OS. You can pull work order and related operational data over REST with snapshot collection into your building Data Sources.

| Property            | Value       |
| ------------------- | ----------- |
| **System Type**     | Work Orders |
| **Communication**   | REST        |
| **Collection**      | Pull        |
| **Collection Mode** | SNAPSHOT    |

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

* An active account with IBM Maximo (FDH) and access to their API or developer portal
* API key or token from the IBM Maximo (FDH) platform
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the IBM Maximo (FDH) platform or admin console
2. Navigate to the API settings, developer section, or account settings
3. Generate a new API key or token
4. Copy the key and store it securely -- you will need it when configuring the connector in KODE OS

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **IBM Maximo (FDH)**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field            | Required | Type     | Description                                              |
| ---------------- | -------- | -------- | -------------------------------------------------------- |
| **URL**          | Yes      | text     | The base URL or IP address of the external system        |
| **Auth URL**     | Yes      | text     | The OAuth authorization URL for token exchange           |
| **External URL** | Yes      | text     | An additional external URL for the integration           |
| **Username**     | Yes      | password | The username for authenticating with the external system |
| **Password**     | Yes      | password | The password for authenticating with the external system |
| **API Key**      | Yes      | password | The API key for authenticating with the external system  |

## 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 (FDH) data to these standard fields:

| KODE Field      | Source Field        | Notes       |
| --------------- | ------------------- | ----------- |
| **id**          | `wonum`             | --          |
| **title**       | `wodesc`            | --          |
| **description** | `description(`      | --          |
| **status**      | `status`            | --          |
| **priority**    | `priority`          | --          |
| **category**    | `prioritydesc`      | --          |
| **subCategory** | `classficationdesc` | --          |
| **location**    | `(formatted)`       | --          |
| **floor**       | `floorname`         | --          |
| **assignedTo**  | `wo_assigned_to`    | --          |
| **createdAt**   | `wocreatedate`      | transformed |
| **updatedAt**   | `changedate`        | transformed |
| **dueDate**     | `schedfinish`       | transformed |
| **startedAt**   | `actstart`          | transformed |
| **completedAt** | `actfinish`         | transformed |
| **assetId**     | `equipmentid`       | --          |
| **assetName**   | `equipmentdesc`     | --          |

### Polling Schedule

* **WorkOrder** -- Default polling: 3 minutes (min: 3 minutes, max: 1 days)

For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection).

## 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

<AccordionGroup>
  <Accordion title="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 (FDH) platform.
  </Accordion>

  <Accordion title="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 (FDH) API.
  </Accordion>
</AccordionGroup>