Reference · built on requestConnectorField service & CMMS

Fiix

Assets, work orders, scheduled maintenance, meter readings, parts, and purchase orders from Fiix by Rockwell Automation.

Request accessPricing ↗

About

Fiix is a cloud CMMS from Rockwell Automation. Its API answers at https://{subdomain}.macmms.com/api/ and works as signed JSON requests over HTTP POST: FindRequest, AddRequest, ChangeRequest, RemoveRequest, BatchRequest, and RpcRequest, each naming a business object class such as WorkOrder, Asset, MeterReading, ScheduledMaintenance, or PurchaseOrder. Java and JavaScript SDKs wrap the same calls.

An operator on Fibric reads work orders, meter readings, and part stock, then proposes a new work order, a meter reading, or a purchase order for your approval. Every write is one request, and each proposal carries a receipt you can undo.

This is a reference listing. It documents what Fibric would read from Fiix and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • WorkOrder records with intWorkOrderStatusID, intPriorityID, intSiteID, assigned users, and linked WorkOrderTask, WorkOrderAsset, and WorkOrderPart rows
  • Asset records, AssetCategory, AssetEvent, and AssetOfflineTracker entries
  • MeterReading rows with dblMeterReading, intMeterReadingUnitsID, intAssetID, and dtmDateSubmitted
  • ScheduledMaintenance jobs with STATUS_PAUSED or STATUS_PLAYING state and their triggers, assets, parts, and users
  • PurchaseOrder, PurchaseOrderLineItem, Receipt, RFQ, Stock, and InventoryTransaction records
  • FindRequest filters written in Fiix's ql query language with parameters, ordering, startIndex, and maxObjects

Proposed actions

  • Target capability: propose a WorkOrder through an AddRequest, with priority, status, site, and requesting user set
  • Target capability: propose a MeterReading against an asset, optionally tied to the work order it was taken on
  • Target capability: propose a status or assignment change on a WorkOrder through a ChangeRequest naming changeFields
  • Target capability: propose a PurchaseOrder with line items, grouped with related writes in one transactional BatchRequest
  • Target capability: propose attaching a file to a work order, asset, or purchase order through the upload endpoint

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Open a work order when a meter crosses its line

    Read MeterReading values by asset, compare against the operator's threshold, and propose a WorkOrder with the reading attached.

    With Predictive Maintenance

  • Reorder spares before the bin empties

    Read Stock and InventoryTransaction rows for critical parts and propose a PurchaseOrder to the linked vendor when quantity drops below par.

    With Spares Reorder, Parts Reorder

  • Surface work orders nobody has touched

    Find open work orders past their suggested completion window and propose a priority change or reassignment.

    With Work Order Aging

  • Catch overdue inspections

    Read ScheduledMaintenance jobs and their generated work orders; flag inspection rounds that stayed paused or never completed.

    With Inspection Due

Requirements

  • A Fiix CMMS instance with a subdomain on macmms.com
  • An administrator to register an API Application and copy the secret, which Fiix shows once
  • A user account the keys run as, with permissions trimmed to what the operator needs
  • An Enterprise plan subscription if you want a developer sandbox before touching production
Authentication
An Application Key, Access Key, and Secret Key from Settings > Connect Management > MA Connect API Application Settings; each request URL is signed with HMAC-SHA256 using the secret.

Limits

  • Errors come back with HTTP 200; success is judged by the absence of an error object in the response
  • A work order created through the API does not get a default task; tasks are added separately
  • The API documentation describes no webhooks; changes are found by polling FindRequests
  • A batch is transactional: if one request in it fails, every request in it is rolled back

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fiix ↗

Questions and answers

How is a Fiix API request authenticated?
Three keys identify the app: appKey and accessKey travel as query parameters with signatureMethod=HmacSHA256, signatureVersion=1, and a timestamp. The URL without its protocol is signed with the Secret Key, and the hex signature goes in the Authorization header. Keys act as the user account that created them.
Which request types does the API accept?
FindRequest, AddRequest, ChangeRequest, RemoveRequest, BatchRequest, and RpcRequest, sent as JSON with Content-Type text/plain. RPC objects are limited to Calendar, DashboardWidget, GetAccessibleSites, GetTimezone, and Ping. Files upload through /api/upload?action=uploadFile.
Does Fiix provide a sandbox?
Active subscribers on Enterprise plans can request a sandbox CMMS from their Fiix representative. It is a working instance for testing calls such as creating assets and work orders before pointing an integration at production.
Ask about Fiix

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Fiix through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy