IBM TRIRIGA Application Suite Migration FAQ

What is TRIRIGA Application Suite?

TRIRIGA Application Suite (TAS) is an is an integrated workplace management system (IWMS) that enables access to a full set of real estate and facilities applications, along with flexibility to expand into other areas.

TAS offers substantive improvements over classic TRIRIGA thanks to major changes in the application’s infrastructure. Based on Red Hat’s OpenShift containerized deployment architecture, it is possible to run multiple instances of TRIRIGA at once.

As a result, users can now deploy multiple TRIRIGA applications with a single license. Using a points-based subscription model, users can deploy different modules in TAS as necessary to support their real estate and facilities applications goals.

Why is IBM making this change?

Responding to feedback from TRIRIGA customers, IBM’s pivot toward TAS revolves around helping TRIRIGA users to better accomplish their goals with less friction and uncertainty.

One of the top priorities was to simplify licensing. Going forward, the points-based subscription model offered through TAS allows users to incorporate as many modules as they want with a single license, and only when they need them.

Another priority prompting the shift was to provide TRIRIGA users with more control around how they manage their enterprise assets. The ability to leverage the full functionality offered by TAS (when necessary) gives users the flexibility they need to respond to economic headwinds and global instability.

Finally, unifying TRIRIGA features and modules into a single platform helps users eliminate data silos in their organization and makes it easier to see how information from each module contributes to the big picture.

Is there a deadline for the transition to TAS?

As of the first half of 2023, there are no planned dates to sunset Classic TRIRIGA for SaaS or legacy licenses.

What are my options for implementing TAS?

TRIRIGA users have multiple options for implementing TAS, and the path forward will be dictated by what infrastructure is already in place.

For users that desire to continue running their TRIRIGA operations largely in-house, the ability to build and maintain the Red Hat software architecture underpinning TAS will be necessary both to implement the platform and for long-term success.

For users already operating their IWMS in the cloud, TAS is currently deployable on these and other supported cloud services:

Additionally, TAS can be deployed and maintained as a service by a strategic technology partner. Depending on the needs of the organization, this approach could mean setting up Red Hat and cloud infrastructure, acquiring TRIRIGA licenses, ongoing maintenance, or any combination of these services.

What does the transition to TAS to look like?

It’s best to start this process after understanding what the transition to TAS from TRIRIGA Classic will look like from beginning to end. The transition can be summarized by these four major goal posts:

1. Evaluate the existing system – Before an organization rebuilds their deployment of TRIRIGA, it makes sense to determine if that deployment is delivering its full value. The transition may be an ideal opportunity to move on from a configuration that isn’t working.

2. Establish the new environment – Whether TAS is being run on in-house servers or on the cloud, the next step in the transition is to configure the Red Hat OpenShift environment that will support the Application Suite.

3. “Lift and shift” from Classic to TAS – During this step, an organization’s existing features and functionality in Classic are ported into or recreated in the Application Suite.

4. Test and roll out – Finally, user testing and feedback will determine the success of the transition and whether additional configurations or modules are necessary before the project is complete.

How soon should the organization transition to TAS?

Several factors will determine how soon an organization should begin their transition from TRIRIGA Classic to TAS. The more complex the transition, the longer the process will take, and the sooner an organization will need to begin to meet their respective goals.

Data quality and governance play a large role in determining how complex the transition will be. Likewise, the presence of industry specific modules and user customizations can add extra steps to the process.

In cases where an organization is already prepared for a transition and just needs to execute the final stages of the transition, the process can take as little as 90 days. If an organization is starting the process from the beginning, their timeline could look closer to 9 months.

How can organizations get the most out of the transition to TAS?

The transition to TAS is a unique opportunity for TRIRIGA users to significantly increase the value they receive from their IWMS solution.

The new subscription model gives users more leeway to explore how TRIRIGA’s modules can improve their operations. And by partnering with an IWMS expert like JLLT, there’s no trial and error to determine which modules will have the biggest immediate impact.

Connect with us today to find out how easy we can make the transition to TAS for your team.