🩺 Support and Monitor Your Systems

Ongoing operational support is where a TM1 implementation either earns its keep or starts costing more than it returns. Arc+ gives administrators the historical visibility they need to investigate issues quickly and the usage data they need to keep the model lean over time.

What you'll find in this section

Chore / Process History

A historical record of every chore and process execution — start time, duration, status, and any errors encountered.

Why it matters: patterns become visible over time. A nightly process that's been slowly creeping up in runtime is spotted before it breaks an SLA; a process that failed silently can be investigated weeks later because the history is still there.

Object Usage Tracking

See which TM1 objects are actually being used, how often, and by whom — across cubes, views, dimensions, and processes.

Why it matters: the model stays lean. Unused cubes and views can be identified and retired, licence decisions can be backed by real usage data, and optimisation effort can be focused on the objects that actually matter to users.

Summary

Long-running support comes down to having the right data at the right moment. With execution history and object-level usage tracking, administrators can investigate what already happened, see what's being used, and prove the value of the platform to the people paying for it.