What is your primary use case for Hexagon EAM?

My main use cases for Hexagon EAM are asset maintenance and inventory management, which are primarily used in automotive manufacturing and the pharmaceuticals industry. I can provide a specific example of how I used Hexagon EAM for asset maintenance in an automotive manufacturing industry. For one of my customers in this industry, we use a multi-organization setup in Hexagon EAM. They have a lot of equipment that creates spare parts for different automotive companies, such as Mercedes and Maserati, and they need to perform regular maintenance on the machines that produce those parts. Those machines can be any type, including a simple motor, pump, or sewing machine that stitches car seats. We create work schedules in Hexagon EAM for those equipments and the PM schedule, and based on the type and details of that PM schedule, we release work orders that are carried out by technicians who perform the work and close those work orders, ensuring a record is kept for the maintenance of all equipment. Regarding inventory management, it was used for keeping a record of spare parts but was limited to the usage of spare parts for maintenance; the purchasing side was not utilized much. We kept a record of all the spares present in the organization, tracking what kind of spare is needed and what kind of spare is issued during maintenance.

The main use case I have for Hexagon EAM is managing the company's assets for the development of its activities related to preventive and corrective maintenance.A concrete example of how I use Hexagon EAM in a specific maintenance activity is in maintenance planning.Traceability of the equipment is an important aspect of how I use Hexagon EAM in my day-to-day work.

My main use case for Hexagon EAM is as a work order management system. My specific example of how I use Hexagon EAM for work order management at a client site involves a call center at a hospital where people call in to raise complaints. The call center staff raises a work order through Hexagon EAM, following the standard work order management system process, which includes creating a work request, accepting it, shifting to work in progress, completing the work, fulfilling all necessary tasks, and closing it.

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.

Hexagon EAM is the main software my consulting firm uses to enable the management of fixed assets and to trace the entire life cycle of fixed assets. From the moment an asset is purchased in a company, business, or industry, until that asset is retired, the system is based on analysis regarding failures and the value that asset may have within the corporation or company. Concrete examples of projects or clients where I implemented Hexagon EAM to manage the life cycle of fixed assets include many organizations. In Chile, there are large clients such as Cencosud, which is a company at a continental level dedicated to retail, and for them I implemented Hexagon for the maintenance of the buildings and infrastructure they have. I have also implemented Hexagon in the mining sector, in the Santiago Metro, and in many other organizations. I would like to add that I was working on the implementation and support for a company here that is in charge of Chile's ports and also has ports in other South American countries, and with them I conducted an assessment to handle maintenance and support for everything related to Hexagon EAM. I also did this with a multinational company in Peru, Inkia Corporate, which was dedicated to power generation. With them I worked on implementations in Peru, Nicaragua, Jamaica, and several countries in the Southern Cone.

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.