Allow Failure Codes and Failure Hierarchies to exist at System in addition to Organization level

Global Maximo clients have similar assets on many sites across multiple organizations. For example, a global terminal/port company has all the same asset types in many ports across many countries. They have multiple organizations because they are dealing with multiple business units working in different countries with different currencies. These Maximo clients want a Global Failure Hierarchy and instead of FAILURECODE and FAILURELIST objects operating at ORG level, it would be better if they worked at SYSTEMORG level, allowing a failure hierarchy to exist at either the System level or the Organization level. For those global clients using System level failure hierarchies they would then only have one set of codes/hierarchies to maintain instead of trying to keep each organization set synchronised with a common set of codes/hierarchies.

There could be an alternative approach a bit like Company Master and Companies where there is a separate application called Failure Codes Master with an Organization level flag to say whether the Failure Codes at the Organization level are maintained separately or from the Failure Codes Master. This would achieve the same purpose but it might be easier to implement as there would be no knock-on to other places where failure codes/hierarchies exist (Tickets for example, other work order classes, Maximo Mobile). The Failure Codes Master will keep the Organization level data synchronised. It would duplicate the data, but there is less impact on an already built Maximo system.

Reliability Strategies when it links with failure codes will probably benefit from being able to associate records at the System or Organization level.