Why do duplicate opportunity rows show in the Assessment tab?


We have an issue with duplicate opportunity rows in the building’s Assessment tab. The issue seems tied to the building system class smart section and the underlying table reporting against it, T_TR_DEF_LI_IT_TR_BUI_SY_CL, while in a building record, Assessment tab, when we create a new opportunity, fill in the building system class smart section (not the building system item one), and create draft.

If a user then tries to change the building system class, but then decides to not save and instead just closes the form, the row that is entered into the table T_TR_DEF_LI_IT_TR_BUI_SY_CL for the temp data, is not removed when the record is closed without saving. Which results in the opportunity query on buildings displaying the opportunity twice. This seems to be a general issue with the use of these tables, since it also happens when you do the same steps on a work task and a facility project; an extra row remains in T_TR_WO_TA_TR_FACILIT_PROJ.

Has anyone else encountered this issue and found a way to correct it? Using the steps below, can anyone confirm that the issue happens for them as well?

This issue is being addressed through PMR 12839,082,000 / APAR [IJ00504].

[Admin: To see other related posts, use the Assessment tag.]

Continue reading

Does anyone know about the IBM TRIRIGA Connector for RSMeans?


Has anyone used the IBM TRIRIGA Connector for RSMeans? If so, is the connector something that is already built into the base TRIRIGA? Or is it something that is purchased separately and then installed?

It is not a direct integration. We have a utility object for services to import RSMeans data into the TRIRIGA system. You need to buy RSMeans data which basically comes with text format, you need to format it into CSV files, then using Data Integrator to import into the utility object, you can finally start the process to create. The process of converting text file data into CSV format is a little tedious, so I would suggest engaging IBM Services to import the RSMeans data. The imported RSMeans data will be used in the Opportunity estimation process.

[Updated 11.13.17]

Gordian now offers an API which supports more seamless integration of RSMeans data with both TRIRIGA and Maximo.

[Admin: To see other related posts, use the Integration tag.]

Continue reading