HxGN EAM (US and Canada) - Enterprise Asset Management

My main use case for Hexagon EAM  is that I was a developer at Hexagon, and I perform customizations as part of client requirements.

A specific example of a customization I have worked on using Hexagon EAM  involved creating Flexes to bypass the standard workflow. Instead of changing a work order directly from open to in-progress status, I added customizations such as waiting for materials and waiting for budget statuses. When an original technician gets assigned to it, the status changes to in-progress. If a technician is removed from the activity, it changes to a waiting for assign status. When a technician gets attached again, it changes to assign status, and then once the technician approves it, it changes to in-progress.

I have created several reports and worked on EAFs regarding my main use case and other customizations I have performed.

The best features Hexagon EAM offers, in my experience, are the status customizations, which are easier from an end-user perspective. Users can simply go to status authorization to make changes.

The status custom license feature makes things easier for end users in that if a supervisor needs access to change a work order into cancel status, they can simply go to status auth, give the status auth user role, and then select the entity they want to do it for, such as purchase order. They select purchase order and fill in the from status to status and then save it. Once they log in to Hexagon EAM, these new statuses are reflected.

Hexagon EAM has positively impacted our organization. It was our first project, and after go-live, it resulted in huge success. The client was satisfied and thrilled, and we received positive feedback.

Specific outcomes from that success include cost reductions around 30%, labor utilization increased by 20%, and new users are adopting the systems and appreciate the product and are eager to work in those systems.

Hexagon EAM can be improved, especially in workflows. If I observe other applications, I can customize the workflow as part of not only the out-of-box features, allowing for proper customization of the flow. However, in Hexagon EAM, I noticed I cannot customize the flow and can only use status auth, which I think is a limitation.

That is the main thing I thought of regarding needed improvements at the moment, and I can send an email if I find or recollect something else.

I have been using Hexagon EAM for two years.

In my experience, Hexagon EAM is quite stable.

Regarding scalability, I feel that we need an extra column, but we need to raise a ticket to Hexagon every time. Since it is very difficult for us, I think we need to find a way to manipulate these things. Adding more columns to existing objects is very hard, and I need to create custom tables and link them to the existing tables, which makes coding very challenging.

The customer support is quite acceptable. I cannot say it is excellent; it is more of an average rating. I would rate the customer support of Hexagon EAM a seven out of ten.

Positive

I had been working on Maximo  solutions as well, and then the client specifically asked for Hexagon EAM, so we switched from Maximo  to Hexagon EAM. Since both are in the same background, it was quite easier for us to pick up.

We have seen a return on investment as we learned several things while using Hexagon EAM, and then we implemented those to the client, resulting in their satisfaction.

We have not evaluated other options since the client specifically asked for Hexagon EAM, so we chose Hexagon EAM.

The advice I would give to others looking into using Hexagon EAM is to be careful while writing Flexes. Since Flexes are based on PL/SQL, if I mess up with any PL/SQL, I cannot save any records, so I need to write proper, optimized, and user-friendly code and add comments so if someone else works on it, they can easily understand and make changes. The same applies to EAFs. As EAF works dynamically, I need to cover all aspects such as before saving, after save, before render, and after render, writing each function carefully to avoid breaking the system. I would rate this product a six out of ten overall.

Public Cloud

Amazon Web Services  (AWS )

What do you like best about the product?

What I like best about HxGN EAM is how it keeps all asset and maintenance information in one place. It makes it easy to see what work needs to be done, track progress, and know the status of equipment. It really helps me stay organized and avoid surprises with maintenance or downtime.

What do you dislike about the product?

The main thing I find a bit frustrating about HxGN EAM is that some of the menus and navigation can be a little confusing at first. It takes some time to get used to where everything is, especially when managing multiple assets at once. Once you get familiar with it, though, it works well.

What problems is the product solving and how is that benefiting you?

HxGN EAM helps solve the problem of keeping track of all our assets and maintenance activities in one place. Before using it, monitoring equipment status and scheduling work orders involved a lot of manual tracking. Now, it’s much easier to stay organized, reduce downtime, and make sure maintenance is done on time, which saves both time and effort.

What do you like best about the product?

Easy to use. Regular updates and addition of features

What do you dislike about the product?

diffcult to identify technical issues, specially in on premise environment

What problems is the product solving and how is that benefiting you?

managing maintencence operations.

What do you like best about the product?

Cloud based and very tailorable to meet business needs. Scalable and able to insert dynamic business rules to automate user experience within the software. The new DataBridge Pro integrations allow much needed interaction with native data and better monitoring. Expansive native quality reporting through Cognos allows near real time reporting to support processes that rely on it.

What do you dislike about the product?

The ability to inject business rules, while a transformative feature, at times can be difficult to debug and can impact system performance requiring vendor support when cloud based. This aspect needs to be used cautiously when implementing and can lead to production issues with users that are not favorable, such as api time outs and long running database procedures.

What problems is the product solving and how is that benefiting you?

Hxgn has allowed us to bring three operating companies together onto a standard EAM and Work Management platform. Allowing us to standardize business processes and deploy best in class enhancements quickly to all three. It also has allowed for variances in operating companies due to regulations to be adopted and compartmentalized within just that company with no impact to our other companies.

What do you like best about the product?

It makes getting the data I need easy. It integrates with our system very well and the user experience is not over complicated. I learned it in a matter of hours.

What do you dislike about the product?

Nothing comes to mind that I can think of at this time.

What problems is the product solving and how is that benefiting you?

Helping me find the usages of key materials used in production.