CMiC

How the CMiC integration works

Clue connects directly to your CMiC instance through the CMiC REST API and synchronises every hour. There are no CSV exports, no scheduled file drops and no middleware to maintain. Once your CMiC credentials are in place, your equipment list, your jobs and your job phases stay continuously aligned between the two systems without anyone re-keying them.

Because Clue reads CMiC as the system of record for job structure, the equipment data Clue collects from telematics, inspections and work orders lands against the same job and phase codes your finance team already uses. That is what makes the equipment cost and utilisation reporting in Clue reconcilable with what CMiC shows.

What syncs today

• Equipment — your full CMiC equipment master flows into Clue, including equipment code, make, model and status. Clue keys each asset on its CMiC identifier, so renaming an asset in CMiC never creates a duplicate in Clue.

• Jobs — CMiC jobs become Clue projects, carrying job name, job code, status and address. Archived jobs are automatically excluded, so Clue only ever shows work that is actually live.

• Job Phases — phase structure comes across with the job, so equipment time and cost can be attributed at the phase level rather than lumped against the job.

‍

Available as optional add-ons

The following are built and available. They are switched on per customer during onboarding rather than enabled by default, so you only take what you need:

• Departments → Sub-organisations — mirror your CMiC department structure in Clue, and optionally auto-assign equipment and jobs to the right division or region.

• Employees → Users — provision Clue users from your CMiC employee records instead of maintaining a separate list.

• Cost codes and financial data — bring CMiC cost codes into Clue so equipment charges line up with your existing cost structure.

• Custom fields and endpoints — if your CMiC instance exposes data specific to how you operate, it can be mapped into Clue.

‍

CMiC x Clue Capabilities

‍

What this changes day to day

Your equipment list stops drifting. Most contractors running CMiC maintain a second equipment list somewhere else — a spreadsheet, a telematics portal, a maintenance system. Every one of those drifts from CMiC within months. With the integration live, CMiC stays the master and Clue follows it hourly.

Job costing gets the usage data it was missing. CMiC knows what a job should cost. Clue knows how many hours the excavator actually ran, when it was serviced and what the repair cost. Connecting them means equipment cost per job stops being an estimate.

Nobody re-keys a job number again. When jobs and phases flow automatically, field crews pick from a list that is already correct, instead of typing a code from memory into a form.