Improvements in IBM TRIRIGA Performance
By Rick Rhea & Jay Manaloto
What has the IBM TRIRIGA performance team been up to? Over the last few years and last few releases, our performance team has focused on areas that aren’t normally covered by our standard benchmark tests, and on tools that can help customers to resolve performance issues on their own. If you’re interested, here are a few of our recent improvements in lease and platform performance.
- Lease Benchmark Testing: Not only are database server and process server resources especially important, but using multiple process servers improves performance.
- New Recommended Indexes: Several additional indexes were identified and added to the best practices to obtain the best response times and resource utilization of the database server.
- Lease Journal Entries: By redesigning journal entry processing with parallel and batch processing, and multiple process servers, our test results took only about 2.5 hours instead of over 90 hours.
- Platform Enhancements: Dynamic workflows can now pass and return parameters, the Query task can now return the number of records instead of the actual records, and the Trigger Action task can now run the asynchronous event that occurs after the transition by a user other than the currently logged-in user.
- BIRT Reporting & Lease Disclosure Reports: In Version 3.6.1, the reporting was modified to improve running on a separate BIRT server, and to avoid the problematic “params.displayText”.
- Performance Analyzer Tool: In Version 3.5.3, this tool was introduced to allow a customer to run specific logging types without using the Admin Console, and to view easy-to-read reports.
- Module Level Associations, Early Adopter Feature: In Version 3.7.0, the platform was enhanced to support Module Level Associations (MLA) tables where the records in the IBS_SPEC_ASSIGNMENTS table are distributed into smaller tables that are created by module type.
By applying the above finding and tools, our recent IBM TRIRIGA 10.7.0 / 3.7.0 release has demonstrated a significant improvement in performance over previous releases. But we’re not done yet! Our performance team will continue to dig deeper into weaker areas or potential opportunities to make our products stronger or faster. So stay tuned for any upcoming developments!
Note: For future releases, “Module Level Assignments” will be renamed “Module Level Associations”.
[Admin: This post is related to the 07.27.17 post about the Performance Analyzer. To see other related posts, use the Performance tag.]
In the IBM TRIRIGA Administrator Console, under Performance Monitor > Monitor a Single Value, several monitors are no longer listed.
The following changes were made in the Administrator Console, under Performance Monitor > Monitor a Single Value:
- CRYSTAL_QUEUE_AGENT_RUNNING is renamed to REPORT_QUEUE_AGENT.
- CLEANUP_AGENT_RUNNING is renamed to PLATFORM_MAINTENANCE_SCHEDULER.
- KEYWORD_PARSER_AGENT_RUNNING and WAREHOUSE_AGENT_RUNNING were deprecated in a previous release and are now removed from the Performance Monitor.
Since the CRYSTAL_QUEUE_AGENT_RUNNING and CLEANUP_AGENT_RUNNING monitors are used for integration, only the performance monitor names are changed, not the values or URLs.
[Admin: This post is related to the 07.14.15 post about renaming CleanupAgent (Cleanup Agent) to PlatformMaintenanceScheduler (Platform Maintenance Scheduler). To see other related posts, use the Monitoring tag.]
In the IBM TRIRIGA 3.5.3 and 10.5.3 release, the Group object was redesigned to leverage query sections, instead of a single large smart section. The query sections improve the performance and usability of the Members tab by paginating the results, and providing filtering capabilities. These application changes are a part of the IBM TRIRIGA 10.5.3 application upgrade object migration (OM) package, but can be applied to systems running older application versions.
To help anyone who would like to apply the Group enhancements to an environment not running 10.5.3, the Group_Query_Enhancement_10.5.3.zip can be downloaded from this wiki. This is an unsupported object migration (OM) package that includes the Group form, queries, and workflows that were created to enhance the application. This OM package can be imported into an environment running on the 3.5.3 platform release.
Note: This enhancement requires the 3.5.3 platform release for the “Add” and “Delete” functions to work within the query section. There are new custom tasks that are called by workflows that handle the adding and removing of group member records, when users or groups are selected. Before applying this OM to a production system, the OM package should be tested in a test or development environment first.
[Admin: This post is related to the 03.07.16 post about best practices for managing your security groups. To see other related posts, use the Security tag.]
Starting in version 3.5.3, IBM TRIRIGA Application Platform includes a Performance Analyzer. The Performance Analyzer is a system tool that helps you to diagnose system performance issues.
Performance Analyzer overview
- The Performance Analyzer provides a more streamlined approach to troubleshooting performance issues than the traditional IBM TRIRIGA performance log analysis.
- The Performance Analyzer helps you to better isolate and analyze the causes of performance issues by generating a log that is more targeted at the problem area. When you contact IBM to report a TRIRIGA performance issue, you might be asked to run the Performance Analyzer and provide the resulting data.
- When you select the performance timing categories that you want and start a performance run, the analyzer rolls the performance log and captures data while you do the process or actions that cause the slowness.
- When you stop the performance run, the analyzer automatically loads the performance data and does a high-level analysis that shows the longest running item in each category in the performance run. A result summary of the performance run shows the top events that took the longest time to run. You can further analyze the data by reviewing the result details where all the selected category data is displayed.
- You can also upload an existing performance log to the analyzer and the analyzer does the same high-level analysis of the data.
The Performance Analyzer has the same base requirements and restrictions as the traditional TRIRIGA performance logging, which includes nightly rolling, space consumption, and logs for all users. Details include…
[Admin: This post is related to the 02.10.17 post about finding the performance best practices. To see other related posts, use the Performance tag.]
The Performance Problem Decision Tree helps you to troubleshoot system performance issues in IBM TRIRIGA. The decision tree progressively narrows the focus of your issue and provides targeted information for troubleshooting the issue.
IBM TRIRIGA Application Platform 3.5.3 introduced the Performance Analyzer. The Performance Analyzer is a platform tool that helps you analyze and diagnose issues in system performance. You are encouraged to use both the Performance Analyzer and this decision tree to help you troubleshoot system performance issues.
[Admin: This post is related to the 07.27.17 post about the Performance Analyzer, and the 02.10.17 post about finding the performance best practices. To see other related posts, use the Performance tag.]
Without a proper contract management repository, you and your organisation are at high risk and not in control of supplier obligations, associated costs, and contract terminations or regulatory compliance. A structured contract registration allows you to proactively manage suppliers, validate contract-related cost and performance, ensures timely contract cancellation or change, and delivers valuable information to improve contracting policies.
Setting up your contract management repository starts with an inventory of contract categories such as activity-based contracts, performance contracts or framework agreements and the contract applications such as maintenance, services, procurement, lease or any other. For any contract, you have to collect, register and maintain a set of basic data, such as:
- Internal information such as contract owner, department and cost centre.
- Supplier information such as company details, address and contact person.
- Contract status information such as active, in negotiation, for approval, or terminated.
- Date information such as start date, notice, end date or cancellation options.
- Asset reference, linking the contract to one or multiple assets in your asset repository.
On top of the basic data, the contract category determines the next level of contract data and information. For an activity-based maintenance contract, you have to register information about:
- The individual activities that are contracted.
- The timing and eventual frequency of the activities.
- The associated budget for the contract or fixed cost per activity.
As performance contracting is a completely different concept for outsourcing maintenance, the performance contract includes different types of data and information, such as:
- Performance definition in terms of availability and quality of assets.
- Detailed service levels, times to start and times to complete.
- Performance measurement methods, supplier bonus or penalty agreements, and billing parameters…
[Admin: To see other related posts, use the Planon tag or Contracts tag.]
Applying condition-based maintenance with IBM TRIRIGA helps to assess a facility’s or an asset’s performance, capture its lifecycle costs, and to identify necessary repairs and replacements. An integrated set of performance metrics of a facility’s condition is needed to predict when to repurpose, or renovate structures.
Building operations and maintenance managers are primarily responsible for assessing the condition of building components like roofs, air conditioning, walls, electrical, and communications. Forecasting facility conditions and predicting repairs before failure occurs, results in cost reduction. IBM TRIRIGA automates demand and preventive maintenance services to reduce the cost of maintenance operations.
TRIRIGA’s facilities and operations manager is an intense CMMS that enables organizations to manage their building assets and facilities over their lifecycle in order to reduce maintenance expenses. It provides condition-based facility assessments that help you to prioritize the areas for capital improvement and assists you in extending the life of your facilities and facility assets.
Condition-based maintenance features of IBM TRIRIGA
- Improves the value and environmental performance of facility assets through the capture and classification of facility, building system and asset deficiencies…
- Evaluates the required investment, energy and operating cost savings, and return on investment of each opportunity…
- Automates the generation of work requests and capital projects to manage the remediation of deficiencies or implementation of environmental opportunities…
[Admin: This post is related to the 03.30.15 post about facility condition assessments (FCA). To see other related posts, use the ValuD tag.]
Did you know the following?
- Store leases comprise 10% of total business costs in the retail industry.
- The number of online shoppers will increase from 1.5 billion in 2016 to 2 billion by 2019.
- At least 100 million customers are expected to shop in augmented reality by 2020.
IBM TRIRIGA provides a robust platform to manage the entire store lifecycle process and takes your real estate operational processes and workflow to the next level. It provides financial analysis and evaluation of your real estate transactions by evaluating and comparing site locations across geographies.
IBM TRIRIGA is a single technology platform and database repository with automated process workflows, pre-built performance metrics, and environmental and energy management functionality. The solution drives a three-fold value proposition to improve financial, operational, and environmental performance.
You can use IBM TRIRIGA for:
- Consolidating historical RE databases and spreadsheets into one integrated system.
- Improving lease accounting and administration.
- Capital program planning.
- Retail site selection.
- Performance analysis.
- Business Intelligence…
[Admin: This post is related to the 06.07.17 post by ValuD about IWMS in higher education, the 06.14.17 post by ValuD about space as an asset, and the 07.12.17 post by ValuD about building a business case on IWMS. To see other related posts, use the ValuD tag or Retail tag.]
Go to Tasks > Manage Work Tasks > Work Task. Click Add for a new work task. Create the draft. Go to the Resources tab, and click Find Organization. Select Organization and click OK. The Resources page takes 6-8 seconds for it to refresh and be available to the user for further action.
This process is a synchronous process. The time it can take to perform the action can vary based on the number of records being selected.
[Admin: A similar article is posted in the IBM Support Portal about slow performance when selecting an organizational resource for a work task. This post is related to the 02.01.17 post about a long-running workflow that hangs the form, and the 02.06.17 post about the TRIRIGA Workflow Analysis Utility. To see other related posts, use the Synchronous tag or Performance tag.]
In the Admin Console, Performance Monitor, when monitoring a single value, it returns bad results. Returns wrong agent’s status. Returns “false” for an agent status even if the agent is running. Returns “0” for the number of agents running even if multiple agents are running.
We needed to update the calls to various platform status APIs. Moving forward, we updated the Admin Console, Performance Monitor, Single Value to correctly obtain the status of the active agents. This means the AGENTS_RUNNING_COUNT, OBJECT_PUBLISH_AGENT_RUNNING, SCHEDULER_AGENT_RUNNING, and all other agent-related monitors will now correctly report the agent status and count. We also removed the calls to KEYWORD_PARSER_AGENT_RUNNING and WAREHOUSE_AGENT_RUNNING as these no longer exist.
[Admin: This post is related to the 04.08.15 post about performance monitoring tools, and the 02.10.17 post about performance best practices.]