Installations, Moves, Additions and Changes (IMACS)
The IMAC report tracks all infrastructure changes since a baseline inventory date, categorised into four types: Installations, Moves, Additions, and Changes. This structured view is essential for IT governance, audit compliance, and understanding how your environment evolves over time.
Accessing the IMAC Report
Navigate to the Additions and Changes menu or dashboard to access the IMAC report:
TODO Screenshot:
ClickMenu "Asset Inventory Dashboard" | PrintScreen "itam-change-reporting-installations-moves-additions-and-changes-imacs"
Scope
The IMAC report covers Configuration Items (CIs) only -- assets with a Network Discovery code other than "SW" in their category. This means it focuses on physical and virtual infrastructure (computers, servers, network devices) rather than software licence records.
IMAC Categories
The default IMAC categories track the following changes:
| Category | Changes Tracked |
|---|---|
| Installations | New asset records created during the reporting period |
| Moves | Location changes, Cost Centre changes, Department changes |
| Additions | Memory changes, CPU slot changes, CPU speed changes, disk additions, disk size changes, device manager entries |
| Changes | Operating system changes, domain name changes, custodian changes, disposals, software additions, software removals |
Customisation
The types of changes tracked in each IMAC category are configurable. If your organisation needs to track additional change types (e.g., IP address changes, warranty updates), these can be added through the Configuration Guide.
Using IMAC Reports
| Use Case | How |
|---|---|
| Audit preparation | Generate an IMAC report for the audit period to demonstrate what changed and when |
| Change verification | After a planned project (e.g., memory upgrades across a department), run the IMAC report to confirm the changes were applied |
| Trend analysis | Compare IMAC reports across periods to identify patterns (e.g., increasing rate of hardware additions may indicate growth) |
| Security review | Look for unexpected changes that may indicate unauthorised modifications |
Tips
- Set a meaningful baseline date that aligns with your reporting cycle (e.g., the start of the financial year)
- Run IMAC reports monthly and archive them for audit purposes
- If the report is very long, filter by category (Installations only, Moves only, etc.) to focus on specific change types
- Compare IMAC data with change requests to verify that all recorded changes were authorised
Related Articles
- Additions and Changes — the broader change reporting dashboard
- Asset History — viewing change history for a specific asset
- Email Notifications — automated alerts for specific change types