Part 1: Leasing Software
Earlier posts focused on the best practices followed by ValuD during IBM TRIRIGA application upgrades. In this blog series, we highlight the best practices that ValuD advocates for an IBM TRIRIGA 10.5.3 leasing software implementation…
Part 2: Data Readiness
Our earlier blog focused on the key learning from ValuD’s 10.5.3 implementations. In the next couple of blogs, we list our recommendations for each stage of the implementation life cycle. In this post, we focus on data readiness, data migration, and the design phases…
Part 3: Journal Entries Setup
Continuing with our recommendations for each stage of the implementation life cycle, today we focus on the build process and general ledger (journal entry) integration steps…
Part 4: Testing & Training
In our final blog of this series, we list our recommendations for the last two phases of the implementation life cycle: TRIRIGA testing and training…
[Admin: This post is related to the 01.10.18 post, 08.07.17 post, and 09.24.15 post about the best practices for configuring and upgrading TRIRIGA applications. To see other related posts, use the Best Practices tag or Implementation tag.]
Part 1: Introduction
With 150+ IBM TRIRIGA completed projects across the globe, ValuD has the largest and most experienced team focused exclusively on IBM TRIRIGA. ValuD offers a variety of delivery models to meet our clients’ needs to ensure customer success whether for a new implementation or an upgrade. In the first of a four-part series, we share our best practices for TRIRIGA application upgrades…
Part 2: Lease Accounting
In our earlier post, we shared best practices followed by ValuD during IBM TRIRIGA upgrades. In this post, we highlight the best practices for IBM TRIRIGA 10.5.3 upgrades especially related to FASB/IASB lease accounting standards…
Part 3: Modifications & Metadata
Our earlier posts focused on IBM TRIRIGA application upgrade steps adopted by ValuD. In this post, we share best practices following the actual upgrade process…
Part 4: Record Data
In our last and final post on this series, we talk about record data tips and IBM TRIRIGA application upgrade delivery best practices that ValuD recommends…
[Admin: This post is related to the 08.07.17 post and 09.24.15 post about the best practices for configuring and upgrading TRIRIGA applications. To see other related posts, use the Best Practices tag or Object Label tag.]
We have upgraded the TRIRIGA platform to 18.104.22.168 and started upgrading the application from 10.2 to 10.5.2 in incremental order (10.3, 10.3.1, until 10.5.2). To minimize the outage and complexity during production implementation, we have been suggested to take a final OM package after completing 10.5.2 deployment, and apply all the customizations which might have been impacted with the upgrade. This final OM package will contain all the changes from 10.2 to 10.5.2.
Our question is on the patch helpers: Can we run all the patch helpers (from 10.3 to 10.5.2 in order) after importing the final OM package?
Also, we are running the Varchar-to-Numeric script before importing the application upgrade packages. This script is taking a long time (almost a day in two test environments), but when we tried in another environment, it’s running for more than 2 days and still didn’t get executed. Is it normal for this script to run like that? Or will it be an issue? There are no differences between the environments.
I wouldn’t recommend doing the upgrade in one package. Usually, it ends up being quite large and it will cause issues. The IBM-recommended way is to perform each OM, then run the patch helpers. Once you have upgraded the OOB OM packages, you can have one OM which has your custom objects…
[Admin: This post is related to the 10.25.17 post and 04.28.17 post about running “SetVarcharColsToNumeric” scripts. To see other related posts, use the Scripts tag.]
Webinar: Thursday, September 14, 2017, 12:00 PM – 1:00 PM Eastern Time
Join ValuD’s Lease Accounting expert team in their Sept 14th webcast for “Best Practices of Implementing TRIRIGA for FASB Compliance” and get prepared to meet your FASB compliance deadline. Register here.
[Admin: The same announcement is also posted in the LinkedIn group. To see other related posts, use the ValuD tag or FASB tag.]
What is the best way to implement a mobile app that will record the time spent in maintenance? Is the OSLC integration the best way to do this connection?
[Admin: To see other related posts, use the Mobile tag or OSLC tag.]
There has been a running debate on how to define a “real” mobility solution for IBM TRIRIGA – do we depend on a UI/UX framework or on commercially available solutions?
A UI/UX solution is a good platform solution that serves as an extension of the desktop TRIRIGA solution, but definitely has its limitations particularly for offline capabilities and keeping development costs in check. Mobility solutions need to operate offline and to leverage the native capabilities of the mobile device and platform. Based on our interaction with a variety of customers, we found some key challenges in evaluating the IBM mobility technology options…
How can we help?
Having executed multiple IBM TRIRIGA implementations, ValuD knows and anticipated the issues faced by customers. Given our in-depth expertise, ValuD designed a mobility solution solely for IBM TRIRIGA.
ValuD’s IBM TRIRIGA mobility solution – MobilD – was developed on true MADP (Mobile Application Development Platform) called Xamarin, an open source platform for developing MobilD. Microsoft acquired Xamarin recently and they made the entire development toolkit free to increase the market penetration. Xamarin, a widely known MADP, has thousands of application developer networks that can help organizations acquire the necessary skills for future development or management.
Another key factor is the choice of middleware solution; most current vendors use a “proprietary” middleware solution that needs a footprint on one of the TRIRIGA servers. MobilD’s middleware choice is Microsoft Azure which is a hosted solution and does not need any footprint on TRIRIGA servers and can also work with your SaaS solution or on-premise solutions…
[Admin: To see other related posts, use the ValuD tag or UX Framework tag.]
Integrated Workplace Management Systems (IWMS) were developed in the ’90s to address the technical limitations of sharing data between multiple real estate and facility management teams. The benefit of IWMS was having a single system for managing the entire real estate portfolio lifecycle. Since these systems were designed for traditional office space, progressive companies are starting to doubt the ability of IWMS to support the transition to the modern workplace…
It is no secret that IWMS are cumbersome to use, which results in companies hiring high-priced consultants for implementations. Paired with its lack of features and flexibility, IWMS frequently exceed their original prices due to customization…
To combat these issues, progressive companies are leveraging (IWMS 2.0) best-of-breed space management technology to augment their existing investment in traditional IWMS to support their modern workplaces. Space management technology is able to address the new requirements of modern workplaces such as neighborhoods, seating ratios, real-time utilization, and highlighting the differences between actual usage of space and allocation of space.
To learn more about IWMS in the modern workplace, download our white paper: “Can Traditional IWMS Meet the Requirements of the Modern Workplace?”
[Admin: To see other related posts, use the Serraview tag or IWMS 2.0 tag.]