Our client’s tabular metric reports, which are set to show the tasks of service requests, seem to have some issues. Although the tasks are found by the report, they don’t always show up or aren’t displayed on the list.
Here are two examples below: (1) In the first case, 6 tasks are found, but only 2 of them show up. (2) In the second case, 3 tasks are found, but none is displayed. Any ideas on what could be happening?
It seems that the user’s language (set in his profile) and the existence of a contract for the tasks affect their visibility one way or another on the tabular report. Here’s an example below: (1) When the user’s language is set to EN (English), all of the tasks show up fine. (2) When the user’s language is set to FR (French), only tasks which have a contract show up (in this case, only 1) even though all 8 are found…
Are you new to using TRIRIGA? Do you wonder how to ever get started with your Preventive Maintenance (PM) schedules?
I know that when I came over to TRIRIGA, I had some trouble. So I am going to go through creating a work plan that includes a service plan and what that means for your task creation. Most PM schedules have some kind of job plan – a list of tasks that need to get done and will occur on a schedule, whether weekly, monthly, quarterly, yearly, or longer.
The first step is to create your job plan, which is called Plan Work in TRIRIGA. This is found under Maintenance > Preventive Maintenance > Plan Work. Your job plan is based on assets, locations, or systems. What is a system? A system is a collection of assets or locations. After you have identified whether your job plan is for assets or locations, you can go create your PM schedule. This is where it really gets “fun”…
NGKF VISION Real Estate is powered by IBM TRIRIGA. This solution is not out-of-the-box TRIRIGA but rather a pre-configured solution incorporating NGKF best practices in service delivery. VISION Real Estate is a cost-effective, low-risk and schedule-friendly replacement for the myriad point solutions, spreadsheets and reporting applications utilized at most organizations. This tool supports the NGKF Integrator Model and NGKF Account Management services.
There’s a stigma in the industry about Integrated Workplace Management Systems (IWMS). Statistically speaking, many IWMS projects fail. Moreover, even when an IWMS project is successful only one or two modules are effectively utilized creating an expensive and ultimately wasteful technology point solution. Until now.
NGKF has reinvented how IWMS is delivered; providing clients a pre-configured solution built on a mature, commercial platform. NGKF VISION Real Estate is part of an integrated technology platform utilizing IBM TRIRIGA with NGKF best practices as well as features not available in IWMS; a supplier registration portal, a business intelligence solution and a suite of benchmarking and analytics tools.
NGKF has made the complex IBM TRIRIGA solution user-friendly, efficient, fast, and affordable. NGKF VISION Real Estate is even leveraged within NGKF’s own brokerage, project management, facilities management and lease administration user community. VISION Real Estate is implemented by CRE consultants with expertise in CRE service delivery, data management, and industry best practices…
[Admin: This post is related to the 06.01.16 post about NGKF GCS and the acquired CFI team.]
Suppose you have a service agreement from which you generated your existing service assignment matrix (SAM) records. Everything is fine until you want to add a new request class to the service agreement. If you modify the agreement, based on the documentation, you apparently need to regenerate all of the SAM records again.
If you go to Maintenance > Set Up > General > Service Matrix and navigate to the Create Service Matrix tab, what is the best way to add the new request class? Here are the steps I think should work, but seems to seriously take a very long time to generate a single SAM record, let alone all of the needed SAM records.
- 1. Click the radio button next to Contract for the Manage By.
- 2. Select the Service Contract that will have the new request class.
- 3. Click on the check box for Use Request Class Defaults for the Default Matrix SLA Values section.
- 4. Find and select the new request class.
- 5. Find the highest level service geography. (World?)
- 6. Find the highest level service location. (Property?)
- 7. Click on the Generate Service Matrix action in the Manage By section.
As I mentioned, following this process will generate the SAM records, but it takes so long that it ends up messing up the whole system. It is much easier just to modify the service agreement directly and reissuing because it can regenerate ALL of the SAM records in considerably less time. If need be, I can open a support ticket, but thought this should be the first place to start if this is a problem with understanding the best way to add SAM records in support of an existing service agreement.
[Admin: This post is related to the 09.02.16 post about clarifying how service matrix records are generated. To see other related posts, use the SAM tag.]
Reading the documentation on how to generate service matrix records raises some questions with regards to what the Generate Service Matrix action on the Create Service Matrix tab will actually generate from a record perspective. By this, I mean the number of records I would expect to get generated is not the number of records that are actually generated. Here’s a step-by-step example of what I did…
- 1. Navigate to Contracts > Service Agreements and create a new Service Agreement as follows…
- 2. Navigate to Maintenance > Set Up > General > Service Matrix and click on the Create Service Matrix tab…
- 3. Go back to the Service Agreement you created earlier and click on the Terms and Conditions tab.
- 4. Scroll to the bottom of the screen. Notice that the Service Matrix records are being created based on the request classes defined in the Service Agreement and not based on the single request class you selected during the Create Service Matrix process.
So, the question is whether this is expected behavior? Or should we have expected only one service matrix record to be created based on the only request class record we selected in the Create Service Matrix process outlined above?
I have an issue with populating related request classes in the Service Request section of a Service Request form. I copied a Service Request form. In the Classification hierarchy, I added a Service Assignment class with the name “Quality Assurance and Quality Control”, added the request classes, and updated the workflow “… Populate Service Request triRequestClassPathTX …”.
Yet the request classes aren’t displayed in the Service Request section. What am I missing? Or where am I wrong? Can you guys help me? All of the workflow instances and workflow traces are similar to that of other available service requests.
[Admin: The same question is also posted in the IBM TRIRIGA forum.]