What Are IMAC Services? Install, Move, Add, Change Explained

IMAC services cover the daily churn of hardware work every organisation generates: Installs, Moves, Adds and Changes. No single IMAC task is difficult. The difficulty is volume, geography and consistency, a hundred small jobs a month, spread across forty sites, each needing to happen on time and to standard.

The four letters, unpacked

Install. New equipment into service: a starter's workstation, a new printer in the back office, a replacement terminal at a counter. Configured to the standard build, connected, tested, recorded.

Move. Equipment relocated: desk moves, office restacks, a device shifted between branches. Disconnect, transport where needed, reconnect, retest, and update the asset register so the estate's records survive the shuffle.

Add. Capacity added to what exists: a second monitor, more memory, a peripheral, an access point extending coverage. Small jobs with a talent for queue-jumping when executives request them.

Change. Configuration and hardware changes: swaps, upgrades, reconfigurations. The category where undocumented work does its damage, one unrecorded change at a time, until the estate and its records diverge.

Why multi-site organisations outsource IMAC

A single office can absorb IMAC with local IT. Forty sites across three states cannot, not economically. The travelling costs dwarf the tasks, volume spikes (a restack, a refit season) swamp fixed headcount, and every site develops its own informal standard. An outsourced IMAC service with national field coverage flips each problem: local hands within SLA, elastic capacity, one written method everywhere, and every job closed against the asset register with evidence. How our IMAC service runs.

What good IMAC looks like

Four tells separate a real IMAC operation from a body-hire arrangement:

1. Work orders, not favours. Every task enters a queue with an SLA, gets scheduled, and closes with evidence. Nothing happens because someone knew someone.
2. The asset register stays true. Serial-level updates with every install, move and change. Six months of sloppy IMAC is how a CMDB dies.
3. Standards travel. The Cairns install matches the Melbourne install because the method is written, not remembered.
4. Reporting reads like operations. Volumes, SLA performance and trends by site, monthly, the data that quietly informs refresh planning too.

Where IMAC fits in the lifecycle

Deployment builds the estate; IMAC keeps it true between refreshes; break/fix catches what fails. Organisations that bundle the three under one partner get compounding returns: the crew that installed the fleet moves it and mends it, and one dataset describes the whole estate's life.

Drowning in small jobs? Speak to an expert.