How Stockland tracks changes and resolves performance issues across a large TM1 implementation

About Stockland

Stockland is the largest diversified property group in Australia. With a large TM1 implementation and multiple internal and external developers working in parallel across different release cycles, managing change control and performance in production is a significant operational challenge.

Challenge 1: Change Tracking in Production

Any changes to production systems must be tested, signed off, and approved before deployment. With multiple developers working in parallel and different release cycles, tracking what had changed in production — and by whom — was extremely difficult. When production issues arose after deployment, identifying the root cause was a time-consuming manual process.

Challenge 2: Performance Issues

When TM1 users reported system slowness, identifying the root cause was complex — issues could stem from model design, user behaviour, recent deployments, or concurrency locks. Native TM1 administration tools lacked the granularity needed to diagnose recurring performance issues efficiently.

The Solution

Pulse's change tracking logs every change made to TM1 objects — by administrators, users, or automated processes — recording who made the change, when, and which specific lines of rules or TurboIntegrator scripts were modified. Combined with rollback functionality, this gives the Stockland team the ability to restore any previous version quickly.

Pulse's user analytics feature allows the team to analyse system behaviour from a performance perspective, identifying long-running operations, concurrent activities, and the users involved — enabling targeted resolution rather than guesswork.

Real-World Examples

Production Deployment Error

After a series of releases, Pulse alerts indicated users couldn't log into a TM1 instance. Using change tracking, the admin team discovered that an external contractor had incorrectly updated a process in production — the wrong version of a TurboIntegrator script had been deployed due to human error. The team could see exactly which lines were changed, rolled back to the correct version, and resolved the issue quickly with minimal user impact.

Recurring Performance Issue

Using Pulse's user analytics, the admin team identified a recurring long-running thread that was causing wait times for users. They identified concurrent activities occurring simultaneously and worked with users to resolve the contention — eliminating a performance bottleneck that had been difficult to pinpoint with standard TM1 tools.

The Results

• Full audit trail of all changes across development and production environments
• Rapid identification and rollback of incorrect production deployments with minimal user impact
• Recurring performance bottlenecks identified and resolved using user analytics
• Confidence that correct versions have been deployed to production at all times
• Ability to manage multiple parallel development streams without losing track of production state