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

# AssetOps

> Connect AssetOps to KODE OS for work orders data

> Connect AssetOps to KODE OS for work orders data integration

## Overview

Use this integration to connect AssetOps to KODE OS. You can collect work order and related operational data over REST with hybrid historical collection, sync sensor and non-sensor readings, and use supported connector actions from Data Sources.

| Property            | Value                |
| ------------------- | -------------------- |
| **System Type**     | Work Orders          |
| **Communication**   | REST                 |
| **Collection**      | Hybrid (Pull + Push) |
| **Collection Mode** | HISTORICAL           |
| **Actions**         | Supported            |

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

* An active account with AssetOps and access to their API or developer portal
* KODE OS environment with access to Data Sources

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **AssetOps**
3. Click **+ Add Datasource**
4. Complete the three-page setup flow using the credential prerequisites for this integration

<Note>
  Connector field metadata is not exposed in code for this integration. Configure the connector using your standard credentials and endpoint details shown in the prerequisites and vendor onboarding references.
</Note>

## Devices and Points

| Point         | Display Name |
| ------------- | ------------ |
| `dueDate`     | dueDate      |
| `title`       | title        |
| `description` | description  |
| `assignees`   | assignees    |
| `category`    | category     |
| `issueType`   | issueType    |
| `team`        | team         |
| `vendor`      | vendor       |

## 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 AssetOps data to these standard fields:

| KODE Field          | Source Field                                                                                                            | Notes                |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------------------- |
| **id**              | `id`                                                                                                                    | --                   |
| **woNumber**        | `number`                                                                                                                | --                   |
| **title**           | `title`                                                                                                                 | --                   |
| **description**     | `description`                                                                                                           | --                   |
| **status**          | `status`                                                                                                                | --                   |
| **startedAt**       | `Utils.getSafe( startDate, startDate -> DateUtils.buildingTzDateMillis(startDate, DATE_FORMATTER, timezone`             | transformed          |
| **dueDate**         | `Utils.getSafe( dueDate, dueDate -> DateUtils.buildingTzDateMillis(dueDate, DATE_FORMATTER, timezone`                   | transformed          |
| **createdAt**       | `Utils.getSafe( createdAt, createdAt -> DateUtils.buildingTzDateMillis(createdAt, DATE_FORMATTER, timezone`             | transformed          |
| **updatedAt**       | `Utils.getSafe( updatedAt, updatedAt -> DateUtils.buildingTzDateMillis(updatedAt, DATE_FORMATTER, timezone`             | transformed          |
| **completedAt**     | `Utils.getSafe( completedDate, completedDate -> DateUtils.buildingTzDateMillis(completedDate, DATE_FORMATTER, timezone` | transformed          |
| **assignedTo**      | `Utils.getSafe( assignees, assignees -> assignees.get(0`                                                                | transformed          |
| **createdBy**       | `createdBy.firstName`                                                                                                   | transformed          |
| **location**        | `area.name`                                                                                                             | transformed          |
| **serviceProvider** | `vendor.name`                                                                                                           | transformed          |
| **customFields**    | `(custom fields)`                                                                                                       | custom fields object |
| **assetId**         | `asset.id`                                                                                                              | --                   |
| **assetName**       | `asset.name`                                                                                                            | --                   |
| **assetId**         | `asset.id`                                                                                                              | conditional          |

### Polling Schedule

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

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

## Available Actions

### Create Work Order

**Type:** Write

Creates a new work order in AssetOps

| Field           | Type   | Required | Input     | Options / Default                      |
| --------------- | ------ | -------- | --------- | -------------------------------------- |
| **Title**       | STRING | Yes      | Text Box  | --                                     |
| **Description** | STRING | No       | Text Area | --                                     |
| **Assignees**   | STRING | No       | Drop Down | Dynamic: fetched from AssetOps API     |
| **Category**    | STRING | Yes      | Drop Down | Dynamic: fetched from AssetOps API     |
| **Issue Type**  | STRING | Yes      | Drop Down | Dynamic: filtered by selected category |
| **Team**        | STRING | No       | Drop Down | Dynamic: fetched from AssetOps API     |
| **Vendor**      | STRING | No       | Drop Down | Dynamic: fetched from AssetOps API     |

#### Example Request

```json theme={null}
{
  "title": "example-value",
  "category": "example-value",
  "issueType": "example-value",
  "description": "example-value",
  "assignees": "example-value"
}
```

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

For more details on how actions work, see the [Actions guide](/products/integrations/capabilities/actions).

## 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. Double-check all credential fields match the values from the AssetOps 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 AssetOps API.
  </Accordion>
</AccordionGroup>