Tririga Review from a recent certified developer
Overall Satisfaction with Tririga
The entire organization of Department of Management Services of Florida is implementing TRIRIGA. They are using it for leasing, operations and maintenance, capital projects, paid parking, reservation manager and strategic planning. It addresses an issue with legacy software not being able to provide ample reporting and tracking of the above items. The budget on projects alone allows users to now track budget and contracts separately along with now tracking invoicing within TRIRIGA itself instead of on paper.
Pros
- TRIRIGA breaks down things into separate objects and items and can track things to a very granular level. Project budgets have original amounts, change amounts, transfer amounts, current amounts, and then it also breaks down committed amounts and invoice amounts in similar fashion.
- TRIRIGA also relates data easily and provides a relatively good format to look at records and data.
- TRIRIGA does a good job of keeping data integrity by having a main ‘Portfolio’ module that stores and tracks data that relates to organizations, people, locations, geography, assets, and specifications. This model provides a level of security for data so that everyone must pick from the same ‘core’ data. For instance if there is a client running TRIRIGA for leasing, Operations & Maintenance and Projects then they all must use the same people, buildings, assets, and organizations. This means that you can’t have two organizations with similar names that are both the same organization, just used by different people. For example if the projects team needs a ‘Division of Administration’ they have to pick the one that is listed in TRIRIGA Portfolio, they can’t choose a ‘Div of Admin’ name so that way when a leasing person goes in to create a lease for that organization they choose the same one. This allows management to see all information for the organization is one place and not have to worry about looking at a report that includes two names for one organization. TRIRIGA allows this data to be set up and updated by specific security groups so only admins and specific security groups can update or edit this data making the system very secure for the core data that all teams will utilize.
Cons
- Less clicks. TRIRIGA is very click happy. As a user, when we have data we want to type it is easier to use 'Tab' and 'Enter' keys to navigate forms and TRIRIGA doesn't always allow for that functionality in a logical manner.
- TRIRIGA menus can be misleading or repetitive. As an admin there are two Requests menus and you can then have things under a menu item that might not make sense. Invoices go under Contracts (because the invoice should be paying a contract) but not every beginning user will know this so it takes some getting used to.
- Some action buttons/links have a poor contrast in colors so it can be hard to see these buttons and links on certain forms. This has gotten better in some places and worse in others.
- TRIRIGA has provided the client with the capability to correct deficiencies in the legacy software and to provide excellent reporting to give management the tools needed to make better informed decisions regarding their company.
- Negatively it has been a very big draw on resources to implement because the client is trying to implement 5 modules in a 15 month period.
- Another positive thing TRIRIGA has provided is it has broken objects into separate items that can each be audited. For example the legacy software only tracked one budget amount and if that was changed the system didn't say who or what was changed. TRIRIGA gives a break down of what line item is changed, who did it, and when. Properties can be changed to track what the pre-change and post-change data was. This is a great feature for auditing purposes.
I haven't used any similar products but the legacy software that was in use was very limited in auditing capabilities and was not very user friendly or easy to learn. TRIRIGA was mostly selected because it allowed the client a large amount of possible growth. They could implement their current processes and then start using different parts of the system along with finding bottlenecks in their current process.
Evaluating Tririga and Competitors
Yes - Legacy software that was proprietary to the client. It was old and very limited in auditing purposes and reporting capabilities. There were a lot of work arounds that were in the business process that really were bad for growth and limited the client with their capabilities in budgeting and contract work. TRIRIGA allowed the client to have massive room for growth within their process. They can now track so many more items and really see where bottlenecks are occurring and report on the data to see how to fix them.
- Product Features
- Product Reputation
- Vendor Reputation
- Analyst Reports
- Third-party Reviews
Single most important factor was the fact that the vendor for TRIRIGA was confident they could meet the deadline to implement in 15 months from start to finish. The client was given strict restrictions to implement in 15 months or less and with a strict budget along with limited resources. Even with these limitations the plan was good and has been implemented well.
Would not change the evaluation or selection but would change the order the modules were implemented. Basically the order the modules were implemented was the order of how 'messed up' they were in the legacy system. This turned out to be a bad idea but has still ended up working. The better idea would have been to implement them in order of complexity of the business processes.
Tririga Implementation
- Vendor implemented
BRG, which is now JLL did the implementation of TRIRIGA for the client
Yes - The phases were Portfolio, Leasing, Operations & Maintenance, Capital projects, Paid Parking, Reservations, Strategic Facility Planning, and then support.
Change management was a major issue with the implementation - There were a lot of 'old school' people who did not want to change systems because they knew the legacy software and knew how to use the work arounds in it and did not want to learn a new system and new methods of their business processes.
- Long term employees who did not want to give up the old software and thought there was nothing wrong with the old system. This was a classic 'If it's not broken, don't fix it' mentality event though it was broken.
- The client was a government agency and there were certain statutes that had to be taken into account because state law required certain things like custom forms and custom reports.
Tririga Support
Pros | Cons |
---|---|
Quick Resolution Knowledgeable team Problems get solved Kept well informed Support understands my problem Support cares about my success Quick Initial Response | Escalation required |
Not Sure - The vendor provides initial support for TRIRIGA and any implementation issues.
Yes - It has been noted that it is a glitch and has be logged with IBM to be fixed in a future release but we don't know which release that will be.
We had some performance issues that IBM took seriously and we got the top level support on the phone very quickly which helped even though the issue ended with the problem being BIRT reports and the way they were written.
Using Tririga
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Navigating through the system is easy as there are multiple ways to get to everything and you can get there using different menus and portals.
- The look of the system is very easy to see and to find things. The system places a max amount of data fields on the forms/windows which is great for users to see all the available fields to use.
- Creating reports can be hard and take some time if the user doesn't know how to navigate or read the relationships TRIRIGA has.
- Going through the developer tools can be hard also if the time isn't taken to learn what each does and how it should be used.
Not Sure - This depends on the version of TRIRIGA.
Comments
Please log in to join the conversation