dmmckinn 1200006SCS Visits (3542)
This year’s TRIRIGA user group conference spans all aspects of the facilities, real estate, and building lifecycles – delivered by clients, partners and the IBM product and business teams. See partner and IBM demonstrations, and speak with product experts to deepen your understanding of the capabilities available to achieve greater ROI for your business.
Here are 6 key Reasons to attend TRIRIGA University:
Register now: http
dmmckinn 1200006SCS Visits (4671)
Companies are instrumenting and connecting their industrial equipment, buildings and facilities, and vehicles with billions of sensors to create what is known as the Industrial Internet of Things (IIoT).
To learn more, read Industrial “Things” Produce “Industrial-Sized” Outcomes, by Kareem Yusuf, General Manager for IBM Watson IoT.
jendobo 50V7SQF9N1 Visits (6217)
Have you ever wondered how to import a new fiscal calendar into TRIRIGA? I have wondered and recently went through the exercise of loading a new calendar. So I will share my thoughts with you. Keep in mind, Classifications are hierarchical,
First, you need to go into TRIRIGA, to Classifications and add a new Fiscal Period. You can do this manually. Once that is entered, you then work with your import files to get them in the correct format to then use Data Integrator to load into TRIRIGA. When working with your import files, they need to be in a .txt format. However, in order to make sure the formatting is correct, you need to edit them in Excel and save it as a .txt file. If you don’t, it could cause problems when you load the import files. Before loading, you should create the Fiscal Period manually. This will be used in the path when loading fiscal years, quarters and months.
Note: before loading your data, it is always a good idea to load a couple of records to make sure it loads correctly and in the right spot before loading everything.
Starting with Fiscal Years, your import file would look something like this:
It has the column names in the header. Then you enter your data. You need to be sure that the path name is correct. Then in Excel, you would save it as a .txt file. Once you have your import file, you can go to TRIRIGA Data Integrator to load your file. When importing the file, it is important to make sure you have the correct settings. You want to have the Module set to Classifications. The Business object to Fiscal Periods and the Form set to Fiscal Years.
After you loaded your sample file, you should go to Clas
If there is an error, generally it could be something like the header was not correct. Or the path name of the Fiscal Period is not correct.
Once you have successfully loaded the fiscal years, you can then load the Fiscal Quarters followed by Fiscal months using the same steps above. Just be sure you get the correct path name and when you use Data Integrator be sure to use the appropriate form. And I recommend that you import a few records at each level to be sure that it will load successfully. If it loads under the wrong category incorrectly, then you need to manually delete those records which could be time consuming.
AcdntlPoet 2700019V2G Visits (7967)
Recommended better practices when using Lease Accounting Payments in TRIRIGA - Edgar Mengelberg discusses some simple steps you can consider that are seen as recommended best practices where it concerns your Lease Accounting Payment Schedule run. [Read more...]
More posts from Edgar:
See even more posts on the IBM Real Estate and Facilities Management blog
JeffLong 270005B0Q4 Visits (9792)
IBM TRIRIGA Support works on addressing problems through a problem ticketing system where each issue is logged as an IBM Service Request (SR) or Problem Management Report (PMR). IBM TRIRIGA Support manages problems reported via this process.
This page has a Support Resources Home section that provides numerous links to some great resources, including a link to our IBM Service Request system where you can open a Service Request (SR). For convenience, the link for creating a Service Request (SR) is here: http
Alternatively, on the IBM TRIRIGA Information and Support Resources page there are also IBM Support phone numbers that can be used to call for support.
Once an SR/PMR is opened, it can be tracked for updates via the SR tool. You may also request an update at any time and this will notify the Support team to follow up with you as soon as possible.
For the most efficient IBM TRIRIGA support experience, a few guidelines should be followed:
Also, it is important to have one problem per SR/PMR because if the problem reported is determined to be a defect, we will create an APAR for it and an APAR also can only cover one distinct problem and we can only create on APAR per SR/PMR. More information about SRs, PMRs, and APARs can be found here: http
Please keep in mind that if all issues are logged as severity 1 issues, this is a misrepresentation, and IBM will be unable to provide adequate timely resolution for truly critical issues for all customers.
Keep in mind that any inside knowledge about your particular problem or environment is good to provide as well because Support deals with a wide variety of issues and test cases and might not be aware of how a particular customer has customized their envi
Finally, try to be prompt and clear in your responses as we communicate during the resolution process. Especially with high priority issues. The quicker you can reply that you have received any updates and let us know your response, the better. Again, due to the large volume of issues coming in, by quickly responding it can ensure that your issue remains at the forefront of the minds of those involved.
For additional guidance on the IBM TRIRIGA Support process, please see the following link for our IBM Support Handbook: http
doboski 310000SJR4 Visits (10171)
In this day in age, security is a very hot topic and as soon as one vulnerability pops up, it is addressed and mitigated, another one is found. It is a vicious circle of identifying and addressing that does not seem to let up. In our fixpack release notes, information regarding mitigation of vulnerabilities that were addressed without an APAR is listed. And sometimes, a vulnerability could be addressed as an APAR.
The reason I am mentioning security vulnerabilities is that sometimes, when they are resolved, there is an effect that impacts existing functionality and it may not always be clear. Sometimes, the result of fixing these vulnerabilities can “change” functionality.
As an example, in the 3.5.2 release, there is mention of an APAR related to external URL navigation items will now open in a new window to avoid cross origin scripting vulnerabilities. Prior to the 3.5.2 release, if you used an external URL in the navigation, it just opened in the same window. We have seen some issues where clients wanted the original design, but that is no longer possible since the change was made as a result of fixing a security vulnerability. The current behavior is correct and cannot revert to the old design. So in this case, there was an APAR referenced. But in others, there may not be. You can look at the 188.8.131.52 release notes (found here http
As the product develops and security vulnerabilities are found and addressed, it could mean a change in how something works. Reading the release notes can be a source of information but it may not always be clear why something changed. We all know change is hard, especially when we are so used to it working a certain way. I don’t know about you, but if the change was made to address a security vulnerability, I can live with that and accept the change.
doboski 310000SJR4 Visits (9780)
If you are an administrator for TRIRIGA, chances are you have access to Security Manager, which is responsible for granting access to the TRIRIGA applications through the security groups. Prior to 3.5.2, the only way to view security access was to go to the Access tab and then select the Access Configuration sub-tab. That is where you would grant (or remove) access. However, it is not very user friendly in terms of finding something and looking what the overall picture of the access of the selected security group. So in 3.5.2, a new sub-tab was access to the Access tab called Access Summary.
The Access Summary tab will show you in a column format, the permissions of the module/business object, form, tab and section. You are able to filter by each of those fields. But only the module/business object and form filters will have a drop down list. The rest of the filters are free form text so be careful when entering data into them.
It is worth noting that when you go to the Access Summary, it will take a little bit for the data to come up. This is because of the query used to extract all that data. Once you have the data up, you can start using the filters to look at the access. what modules/business objects it has. Or if there is a specific form you want to look at. The permissions field will show the specific permission, if it's Read, No Access or the name of the action, like Asse
This tab should now make it much easier to identify what a security group has access to. If you find yourself limited with what you want to do within the tab, there is an Export button, that will export the data into a tab delimited .txt file. When you click on the Export button, you will get a message letting you know that it will run in the background and you will receive a notification when it is complete. You will want to monitor your Notification notices. It should also be noted that the file is exported to the application server, not your local server. The path of where the file can be found will be in your notification. If you don't have access to the servers, you will need to reach out to your system administrators to get the file for you. Here is what the file will look like when it is imported into Excel.
So there you have it - an easier way to view the access of a security group.
doboski 310000SJR4 Visits (7657)
In TRIRIGA's Data Modeler, there are 2 methods to add a field to your business object: Add and Find. How do I know when to use them and what really is the difference?
Add is when you are creating a new field that has never existed before. It should only be used for creating brand new fields that do not exist. This not only adds the field to TRIRIGA but it will add t to the database. For example, you want to add the field cstNewField1TX to the business object triContract and it does not exist on any other business object. So you would use Add to add the field.
Find is used when you want to add a field whose name already exists. For example you want to add cstNewField1TX to the business object cstMyObject. We know from above that cstNewField1TX was already added (and we will assume published). You would use Find to search for the field and it would add it to your business object, with all the same information. Then, it can be modified for this particular business object, except for the field name and data type.
If you are looking for a specific type of data - say a Start Date, you would use the Find action to look to see if a Start Date exists and re-use on your business object.
Why does this matter? Because, if you added cstNewField1TX to your business object, you could get errors because that field name already exists on a different object. It could cause confusion seeing the same name more than once in the database. Even if you remove the field, you are removing the field from TRIRIGA, not necessarily from the platform.
doboski 310000SJR4 Visits (9736)
Are you new to using TRIRIGA and wonder how do you ever get started with your Preventive Maintenance 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 preventive maintenance schedules have some kind of job plan - a list of tasks that need to get done and will occur on a schedule, be it weekly, monthly, quarterly, yearly, etc.
The first step is to create your job plan, which is called Plan Work inside of TRIRIGA. This is found under Maintenance -> Preventive Maintenance -> Plan Work. Your job plan is then based on assets, locations or systems. What is a system? A system is a collection of assets or locations. After you have identified if your job plan is for assets or locations, you can go create your Preventive Maintenance (PM) schedule. That's where it really gets "fun"!
So create a new Work Plan that will have the Resource type set to All Resources in Selected Systems. And add 2 Assets to it. Then go to the PM Schedules tab and let's add a schedule for those Assets.
You are going to need to define a Request Class. This request class defines the type of work, like if it's for HVAC , Electrical, Plumbing, etc. Associated with this Request class is what is called a service plan. This service plan identifies information about task creation, SLA's, priority, etc. Knowing the service plan you are using is really important to know but I will get into more on that later.
Now you need to create the pattern or frequency of the schedule. How often will this be needed - daily, weekly, monthly, quarterly, yearly, etc. You can also choose to do shadowing PM's but for this we will not be including that. Once you have identified all that, your tasks are now created. This could take a little bit of time depending on the length of your schedule and how many assets/locations are on it.
Now about those service plans. Here are some examples of how they work.
You have a work plan with 2 assets on it. Create the Preventive Maintenance schedule so that it occurs daily for 5 days. And the service plan is set to create tasks for single tasks. The end result is that it will create 10 tasks in total. 5 tasks for each asset. If you go back and add another asset to the work plan, then another 5 tasks will be added. So each asset will get their own set of tasks. If you are using a system, the functionality will work the same way. The key is the service plan is set to create tasks for single tasks.
Now in another scenario that will also have 2 assets on it but the service plan is going to be set to create single task for all assets. So you have a work plan with 2 assets on it. Create the Preventive Maintenance schedule so that it occurs daily for 5 days. Set the service plan to create a single task for all assets. The end result will be that it will only show 5 tasks because the same task will be applied to all the assets on the work plan. You would have to go look at the association of the task to see all the assets lists. See the screen shot below for an example.
And if you add a new asset to this scenario, it will not add a new task. It will just add another association to the new asset from the task.
So now that you know this, go on and create your work plan for your maintenance schedules!
For additional information on this, you might want to go check out the documentation found here
dmmckinn 1200006SCS Visits (9817)
As we approach the end of the first quarter we thought we'd send a reminder about some of our Watson IoT product versions and supported platforms that are coming up for End of support.
The following product versions are currently scheduled for end of support in April 2017:
Refer to this previous blog post for general information about Watson IoT Support Lifecycle Resources:
doboski 310000SJR4 Visits (10278)
Towards the end of last year, I had the opportunity to sit in on a Maximo Anywhere class. While I am a TRIRIGA Support Engineer, both Maximo and TRIRIGA use the Anywhere platform for their mobile solutions. So for me, there was benefit in sitting in on the class since the process of configuring is the same for either product though the code base will be different! So these tips could apply to either Maximo or TRIRIGA, depending on what you are using. It is worth noting that Maximo has more mobile applications than TRIRIGA. So I would like to share with you some basic tips that I learned in this class.
As shown in the screen above, there is a section called Outline that will, like the UI, view sections of the code. When you click on something in the outline, it will bring you to that section of the code. Which will save you from having to search the code for the correction section. Believe me, I am wishing I used that to help me find the Work Detail View as I ended up putting the new field I was trying to add in the wrong place! But I learned my lesson!
So those are some basic tips when getting started with configuring your Anywhere files. I hope this will help you get around easier when configuring your Mobile solution, be it on Maximo or TRIRIGA. And remember tip #1 and #2 - ALWAYS back up your files! Save early and save often!
GiuCS 270003E2P0 Visits (10316)
It is often asked if there is a panel or administration console available in IBM TRIRIGA for showing active users and the licenses they are consuming.
Unfortunately there is not, but to circumvent this you can use some helpful SQL queries.
The SQL queries are documented in
The queries provide a snapshot of current user and licenses being used, in a few different outputs:
JeffLong 270005B0Q4 Visits (8171)
If you have installed IBM Tririga with WebSphere Liberty Profile, you may find a need in the future to update the JAVA version you are running in WebSphere Liberty Profile. If you need guidance on how to do so, please refer to the following documentation:
If you need additional assistance please contact support.
doboski 310000SJR4 Visits (6957)
Have you have ever had performance issues with loading data into your location hierarchies? Or making large changes to hierarchical data? Are you reorganizing your company, adding new departments, moving or combining others? Is it taking a long time to process these changes?
When an update is made to the hierarchy, the entire tree is rebuilt. So if you have multiple updates you are making, it is rebuilding the entire tree. If you have a rather large tree with many layers or branches, this could be quite time consuming and frustrating while you wait for it to update. Do not fear! There are some things that can be done to make it less time consuming!
One of the things to look at is in your Admin Console. You would go to Cache Manager and look for System Cache Processing Mode. By default this is set to Normal.
You would want to set this to Data Load Mode and then click on Change Cache Processing. It is worth noting that when using Data Load Mode, it will not update the tree but it will be faster to process because it is not updating the tree after every single update. Once the process is done, the tree can be rebuilt once and not after every update.
You don’t have to necessarily go into the Console to set that every time you are adding something into a hierarchy or making an update. If you have a workflow that is currently used to process your hierarchy inserts and/or updates, you can add a custom task to turn on Data Load Mode and then turn it back to Normal after your processing is complete.
To set it to Data Load Mode, in the custom task, you would set the class name to com.
To set it back to normal, in the custom task, you would set the class name to com.
For additional information regarding custom tasks, you can reference the following wiki:
Many times, a client may hear a support engineer say that they should upgrade to the latest version. Why do I keep hearing that - especially if upgrading will take time, money, and resources? TRIRIGA, like all other software, evolves. We continuously fix defects and add new functionality. For instance, if you are on version 3.3.2, some of the features you cannot take advantage of include improved logging capabilities, which makes it easier for us to help you troubleshoot an issue. Also included is improved security and, more recently workflow versioning. Since complex software can sometimes have defects you never know when a defect might impact your business. But why wait for it to impact you? Upgrade so that it won’t happen. New functionality is also added into the software and you may want to take advantage of it.
Another reason to upgrade is that software uses various technologies, which changes faster than New England weather! Technology is constantly changing and TRIRIGA must keep up in order to keep it running. That technology can be in operating system updates, browser versions, application servers and Java to name a few. Support may often recommend staying current with product releases but it is always good to review the release notes for the current release. The release notes for each version show what has been fixed and functionality that has been added. You can find the release notes for TRIRIGA here:
Before upgrading, it is important to understand the structure of TRIRIGA because there are 2 very different procedures to upgrade. Those 2 structures are Platform and Application. The TRIRIGA Platform is the java code that IBM writes and is installed on a server. The TRIRIGA Applications are developed using the TRIRIGA Platform. Applications are not “written” but are developed using the Platform as a development tool. Applications are stored in the database as metadata and are not found in the TRIRIGA directory structure. Both the Platform and the Application have their own version number. How do I tell what number is for what? Platform versions are the lower of the 2 numbers associated with a TRIRIGA install. So the Platform version would be something like 3.5.1 or 3.4.2. Applications are the larger numbers associated with a TRIRIGA install. So the Application version would be something like 10.5.1 or 10.4.2. TRIRIGA 3.5.1/10.5.1 is Platform 3.5.1 and Application 10.5.1. But this can change. If IBM releases a 4.1.0/11.1.0 release, a client can upgrade to Platform 4.1.0 and leave the application at 10.5.1. But you can never upgrade the Application beyond the platform it was built on. So using the example of 4.1.0/11.1.0, you could not upgrade the application to 11.1.0 and still be on platform 3.5.1 because the functionality required to support the new Application exists in the new Platform.
The TRIRIGA Platform will always be there as it is required for the database to be run. The Platform never deprecates functionality. So if an application is developed on one release of the Platform, it will continue to function in future releases of the Platform. Ever since the 3.2 release, you can easily upgrade the Platform in under 2 hours. You simply stop the servers, install the new platform code, start one server to perform the database updates and when it is complete, stop the server, apply the latest fixpack, start one server and then start the rest. That’s it! The Platform will be upgraded. Security vulnerabilities, new technology, performance enhancements, new properties and more are ready to use. You should plan to perform a Platform upgrade at least once a year.
Applications can be substantially more complex. If you have never done one, I would strongly recommend that you consider engaging our IBM Global Business Service (GBS) or one of the IBM TRIRIGA certified business partners to help you through an application upgrade. Since the applications are actually data in the database, an upgrade involves updating data, which is always a tricky task. On top of that, clients have the ability to configure and modify functionality associated with an application. A wrong step could overwrite data and damage functionality. To add to it, application upgrades must be done one version at a time. If you on 10.3.1 and are going to 10.5.1, then you will need to upgrade to 10.3.2. Then 10.4.0, 10.4.1, 10.4.2, 10.5.0 and finally 10.5.1. We strongly recommend that you plan for an Application upgrade at least once every two years to minimize the number of versions between platform and application. In addition, audited functionality may require Application upgrades. Customers who use the Lease functionality in TRIRIGA will know that government rules around leases are called FASB. Clients who need to be compliant with FASB rules will need to be on the latest Application release.
Fixpacks are important too! If a defect is found in a release, we will identify the defect as an APAR and develop a fix that can be applied to the installed software. It is recommended that customers set aside time and resources once a quarter to apply any fixpacks.
When a support engineer recommends that the user should upgrade to the latest version, the first thing that should be done is plan! Just because the platform may not take a lot of time to do, you should put in the proper planning. Here are somethings to ask yourself when planning your upgrade: