Workflow customization has streamlined maintenance tracking but still needs deeper flexibility
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Hexagon EAM for two years.
What do I think about the stability of the solution?
In my experience, Hexagon EAM is quite stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
Which other solutions did I evaluate?
We have not evaluated other options since the client specifically asked for Hexagon EAM, so we chose Hexagon EAM.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Hxgn EAM
What do you like best about the product?
ability to link all things together from WOs to procurement.
What do you dislike about the product?
the organizational setup that is kind of forced upon you. organizations must conform to a certain degree to the software, and this can be a big change
What problems is the product solving and how is that benefiting you?
The ability to track WOs, labour's hours, and parts used. Historical data and being able to compile information is a huge benefit.
Powerful app, but poorly set up and fragmented
What do you like best about the product?
It does a good job with tracking information throughout the steps of our WO process
What do you dislike about the product?
Too many separate products to buy for successful implementation, with difficulty transitioning between solutions and getting the most out of the system.
What problems is the product solving and how is that benefiting you?
Managing work order tracking and tractor/trailer repair & lifecycle.
Strong Community with HxGN EAM
What do you like best about the product?
I appreciate the large community available through HxGN EAM. I consult with them to understand how they have approached problems similar to ours. This has helped us with project management too. I can levy their experience to improve my cost estimates, schedules, and scope.
What do you dislike about the product?
There’s nothing in particular that I dislike, but I do find the HxGN EAM UI a bit dated. I hope to see improvements in the future.
What problems is the product solving and how is that benefiting you?
HxGN EAM does a lot for us, and that includes managing assets, preventative maintenance, and corrective maintenance.
Asset management and maintenance solution
What do you like best about the product?
Preventive Planning capabilities along with inspection management. it has enabled an user to to do inspection based monitoring and condition based monitoring. Follow up procedure defines in the activity checklist are great. Work flow management is provided an added advantage over who is responsible for Preventive management of an asset. Integration with various machine has enabled us to provide organization to real time ticket generation system and automate its work flow.
What do you dislike about the product?
Deffered maintenance elements are not clear and concise. Budget management capabilities should be defined more as they should be integrates with Capex budget of company.It should have budget control features in order to have control over budgeting.Contract management is not available in the EAM. We need to use still other solution for this purpose.
What problems is the product solving and how is that benefiting you?
Timely management of resources including tools, employee qualification.
KPI management
Delegation of task
Check list management
Equipment update report.
Equipment Profile template
Management reporting
helps in capex budget preparations.
calculation of total life cost of the asset.
Maintenance inventory management.
Recommendations to others considering the product:
Integration with other ERP software should be based on API based rather than integration using third party application. AI based recommendation should be for next failure should be part of the solution.Direct inventory cost should be saved in part information as it is saved for inventory part. Most importantly, is south Asian countries, budget controlling is required. it should be there. Asset number and Finance tag number integration has to be there. actually during my implementation, it difficult for us to maintain this relation as asset management defies asset different that are define is Fixed asset register in financial ledger.
satisfactory
What do you like best about the product?
Working with digital thinker in EAM how simple they make training
What do you dislike about the product?
Infor's support is terrible. I have to allow on Digital Thinker to help us they do a terrific job
What problems is the product solving and how is that benefiting you?
Purchasing and inventory control
Utility using EAM
What do you like best about the product?
You can write code to help fix most problems. Lots of 3rd party companies to help.
What do you dislike about the product?
The user is in charge of watching their own user licenses usage. The system needs lots of hand holding to work efficiently. Not sure if any of my enhancements every get acknowledged like other companies.
What problems is the product solving and how is that benefiting you?
Work order management and warehouse inventory. Going paperless to be able to find problems and improvement areas.
Recommendations to others considering the product:
Product does lots of the basic problems. But it does have room to grow compared to other ones.
