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.]
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, and the 06.14.17 post by ValuD about space as an asset. 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.]
Out-of-memory errors can occur as a result of a report running, but we cannot identify which report. So we need a way to identify the report that is running, who ran it, and how long it is running, so analysis can be provided.
In the TRIRIGA 3.5.1 release, a new flag was added to reports to enable them to be tracked over time. This tracking includes who ran the report, when it was run, and the total duration the report took to complete. By default, this is disabled. However, it may be a good idea to enable full tracking across all reports in the system to help trace performance issues, and usage over time…
[Admin: This post is related to the 04.19.17 post about tracking the report runtime history, and the 10.31.16 post about using the report run history to track performance.]