Octave Attune EAM (formerly HxGN EAM)

Our main customer in the healthcare sector is Aga Khan Hospital, the largest hospital in Pakistan. The hospital manages a large facility, covering between 50 and 60 acres. All aspects of the facility, such as taps, doorknobs, and incubators, are managed through Hexagon EAM , ensuring monitoring, maintenance, depreciation, and phasing out of the system. For any maintenance tasks or accidents, work orders are generated and managed via Hexagon EAM .

Additionally, we manage inventory equipment and conduct scheduled maintenance, such as monthly, quarterly, or weekly maintenance checks based on the cycle. The system helps verify the completion and thoroughness of these tasks, ensuring the maintenance was done correctly.

Hexagon EAM's traceability is impressive, making it easy to maintain historical data, perform root cause analysis, and complete fishbone diagram reporting. If there are recurring issues, this system helps identify persistence in problems. For example, if an HVAC issue arises due to mice affecting wiring, root cause analysis allows identifying and documenting the problem, potentially highlighting shortcomings in complementary departments like fumigation.

The mobile app also plays a significant role for large facilities, such as hospitals, where maintenance staff need to travel for tasks. Real-time data entry and feedback provided by the mobile app are crucial for efficiency. For organizations aiming for ISO 9001 or other certifications, Hexagon EAM facilitates proper documentation and task execution, aiding in standardization and certification efforts.

Some Hexagon EAM modules are detailed and challenging for new users, suggesting simplification to enhance user understanding and implementation. Encouraging customers to adopt new features can be achieved through workshops and seminars, as organizations may resist changes. Additionally, the pricing in this region can be prohibitive, affecting the adoption rate. The annual recurring license cost impacts ROI, making it challenging for some organizations.

Customers have noted that engaging with the Hexagon technical support team can be a lengthy process, especially with the on-premises version, where sharing logs and receiving resolutions is time-consuming. Improved response times and streamlined communication could benefit customers.

I have been using Hexagon EAM for more than three years.

I have never faced any downtime with the cloud version, so I find it stable.

Scalability is not an issue with Hexagon EAM. If we want to add more licenses, we can easily do that, and if we want to add any new module or integrate it with anything, we can do that easily as well.

We have worked with the Hexagon technical support team. The issue that we find with them is that getting to the resolution takes time. If we are working with the on-premises version, they ask for logs, check the logs, and then ask for logs again. These processes take time and can be frustrating for customers because they do not receive immediate answers, and sharing logs and discussing the issue takes weeks or even months to reach a resolution.

I would rate the technical support a seven on a scale of one to ten.

I am familiar with SAP and its maintenance module, and I am familiar with Maximo  as well. However, I have not used them.

Clients choose Hexagon EAM because it is a more detailed product than SAP. In terms of Maximo , while pricing is a bit high, Hexagon EAM offers a detailed module for each aspect, including every detail and options for maintenance in every possible way. This detailed offering helps it achieve better market penetration.

If we get the data in the right format, there are not many challenges in the initial setup process. Implementing Hexagon EAM depends on the scope of implementation, and if it is a simple implementation, then it is not a big challenge. However, if there are many modules involved, it gets challenging.

We are resellers of Hexagon EAM, and we work directly with Hexagon and provide it to the customers in the region.

The ROI on Hexagon EAM depends from organization to organization. Most organizations find it hard to achieve ROI because the product they are producing is not of that value that they could achieve ROI in a year or two. Additionally, there is a recurring cost of the license each year, and that cost actually affects the business.

The pricing for this region is a bit high, and this is the main reason that organizations take time to adopt Hexagon EAM. Only organizations that are big and earning substantial revenue adopt Hexagon EAM; most organizations in this region are not adopting it due to the high costs they have to bear.

Although the customer is not using the analytics in quite detail, we do use IBM Cognos  for reporting purposes. We use IBM Cognos  to create and deploy reports. The reports are not that difficult but are not very detailed; however, they fulfill the requirement. For KPI management and the dashboard we have when we start the application, that is also helpful in highlighting the number of open work orders, closed work orders, or in-process work orders. Thus, management gets a high-level overview of which jobs are done and which are still pending.

I would overall rate Hexagon EAM as a product or solution a 9 or 9.5. The product is good, and it is easy to find that many of your tasks are resolved very easily regarding maintenance once you implement it. My overall review rating for Hexagon EAM is 9.

My main use case for Hexagon EAM  is for maintenance, and it helps with predictive maintenance. I use Hexagon EAM  for predictive maintenance in a solar farm and for heavy machines in the oil and gas and electric energy utility business.

The best features Hexagon EAM offers are for inventory management, works management, and the correct data of the asset. Inventory management and work management help my organization by allowing for specific work orders, closing jobs, and registering assets and inventory in the company.

The features can be used on mobile devices and for real-time tracking of open work orders and registering assets by QR code. Hexagon EAM has positively impacted my organization by helping and solving problems in the work order workflow and approval in real-time.

Real-time workflow and approval have improved my team's efficiency by allowing us to input all data outside in low signal areas without duplicate work.

Hexagon EAM can be improved by rebranding from HxGN EAM to APM , Asset Performance Management. I would like to add that AI should improve data learning or the knowledge base by AI.

I have been using Hexagon EAM for over five years.

My advice for others looking into using Hexagon EAM is to consider the AI plug-in and its integration with other platforms. Learn  from data and pursue real predictive maintenance. I would rate Hexagon EAM a nine on a scale of one to ten.

My main use case for Hexagon EAM  is as the Systems Administrator, so I make sure that the system is up and running, dealing with end user problems and submitting support tickets to the cloud since ours is a cloud implementation. I work closely with the Hexagon EAM  cloud architect, and when we want to add a new feature, I work with him to get the best way to do it. I do enhancements to the system by creating Flex SQL statements to customize usability, and I maintain the mobile environment because we use both the Digital Work and Mobile Offline applications. I perform data analytics on the data from EAM, sometimes using Cognos , which is built into EAM, and we also have a data lake where we have Microsoft Power BI  attached, allowing me to create dashboards in Power BI. I sometimes set up the API connections that feed these dashboards if the information is not in the data lake, so overall, that is basically what I do.

Regarding my main use case for Hexagon EAM, it is a great system, but it is difficult because it upgrades twice a year in May and November for feature updates, so I have to stay on top of the release notes and perform proper regression testing before each release to ensure any existing processes do not break. Those are the main things I deal with.

The best features Hexagon EAM offers include its robustness and a lot of customization options that depend on the skill level of your staff. You can use the desktop version of EAM, and there are both online and offline mobile applications that focus on work order execution for field staff, which is very helpful. Hexagon EAM has a comprehensive PM schedule module for all PM-based equipment, many options for corrective work, and the ability to create detailed task plans for staff, enabling everyone to know what to do. You can attach pictures and any necessary documentation, and the alerting system contains many cool features. They are also slowly starting to implement artificial intelligence built into the application, which helps new end users with many questions, such as how to create a work order. That is going to continue to expand as AI evolves with more updates.

Hexagon EAM has positively impacted our organization by significantly lowering costs. Previously, we needed ruggedized laptops for our field staff, which were expensive and bulky. With Hexagon EAM, we can run everything on iPads, making equipment lighter and cheaper to maintain. When we migrated to EAM, we applied universal standards across all departments using it, forcing us to align our SOPs to work within the same environment while maintaining department security to prevent overlap. The reporting has also improved due to robust API web services that allow me to connect to Power BI or Excel and send data to our data lake.

A specific metric worth sharing is our condition assessment, where we utilize closing codes and condition scores on assets to run reports prioritizing capital improvement spending. This has evolved dramatically since our previous system did not collect that kind of information, meaning the assets being replaced were not always the highest priority. Now that we can collect that data accurately, it has a huge impact on both time saved and money spent on replacing the correct assets.

One thing I believe could be improved in Hexagon EAM is the scheduling function. Although it works, it can seem daunting at first to those who are not comfortable on a computer, compared to our previous asset management system, which had a better and easier-to-use scheduling module.

Hexagon EAM's AI capabilities are just getting started. The AI currently accesses the Hexagon knowledge base but does not access personal data in your tenant or gather information from the web, so it is still in its infancy. One of the next features on their roadmap is to connect the AI to your internal data, which is where governance and security come into play, though this is not yet available.

The accuracy and reliability of outputs from Hexagon EAM's AI capabilities are also in their infancy stage. It is good at answering questions about how to use EAM by accessing the Hexagon knowledge base. Issues may arise if there are customizations to a screen being asked about since it does not have access to your database to know about these changes. However, I believe the responses are really good, provided the prompt is clear, something EAM cannot control.

I have been using Hexagon EAM for four years, as we went live with EAM in August of 2022.

Hexagon EAM is very stable; in the cloud, we have yet to experience any outages.

Hexagon EAM's scalability is very good. We started with two departments and have scaled up to four, with the possibility of adding six more. It is essential to configure the system properly during the implementation phase to ensure scalability with any asset management system.

The customer support for Hexagon EAM is good. When I have an issue, I submit a ticket through the Hexagon cloud, and based on its severity, a technical support person usually responds within 10 to 15 minutes. Their accounting team meets with us monthly to ensure everything is progressing well and to measure our use of the system.

Prior to Hexagon EAM, we used Oracle Work and Asset Management, or Oracle WAM, for approximately 20 years. It had reached the end of its life cycle, and upgrading to the next version would have required a complete re-implementation. We conducted due diligence to evaluate all systems due to this, prompted by a directive from the city manager's office to unify the application across departments. Since one department was already using Hexagon EAM, we assessed its capabilities against the newer version of Oracle WAM and IBM Maximo , concluding that EAM provided the necessary functionality and would streamline procurement and upgrade processes due to its public cloud tenant.

We evaluated Oracle WAM version 2, IBM Maximo , and City Works along with Hexagon EAM before making our decision.

My advice for others looking into using Hexagon EAM is that it is a robust application. You can customize it to meet your needs, but it is crucial to have a good plan during the implementation phase and rework your workflows for efficiency. Understanding Hexagon EAM's licensing is also important since we transitioned from enterprise licensing in our previous system to needing to maintain a strict user count now. One pain point is not having direct access to the database in the cloud environment, as access is limited to the reporting tool, which can be a bit frustrating, but it is not a showstopper.

Overall, I think Hexagon EAM is a really good application. It is very robust and customizable, with both desktop and mobile components that should meet anyone's needs. If you are considering using it, I believe you cannot go wrong, as long as you implement the system correctly and have the technical staff to make necessary customizations. I have given this review a rating of 9 out of 10.