HxGN EAM Technical Architecture

For years, enterprise IT leaders and maintenance executives relied on Infor EAM to manage their most critical physical assets. But as the industrial landscape evolved, so did the software. Following its acquisition by Hexagon, the platform was reborn as HxGN EAM, bringing with it a renewed focus on cloud-native scalability, advanced analytics, and seamless interoperability.

For IT Directors and System Architects in the US market, this transition represents more than just a rebranding. It marks a fundamental shift in how enterprise asset management systems are deployed, managed, and scaled. Today’s asset-intensive industries cannot afford the rigid, monolithic architectures of the past.

Downtime is not just an inconvenience; it is a massive hit to your bottom line. To maximize ROI and align with global standards like ISO 55000 for asset management, organizations need an agile, resilient, and highly available infrastructure. HxGN EAM delivers this through a modernized technology stack designed for the realities of modern manufacturing, fleet management, and public infrastructure.

In this comprehensive guide, we will tear down the HxGN EAM technical architecture. We will explore its cloud foundation, database tier, extensibility frameworks, and security models. Whether you are planning a migration from an on-premise legacy system or looking to optimize your current cloud deployment, understanding this architecture is the key to unlocking its full potential.

The Core Foundation: Cloud-Native Architecture on AWS

The backbone of HxGN EAM’s modern deployment strategy is its deep integration with Amazon Web Services (AWS). While on-premise deployments are still technically supported for highly regulated offline environments, the platform is undeniably engineered for a cloud-first world.

Hexagon leverages AWS to provide both multi-tenant Software-as-a-Service (SaaS) and single-tenant hosted environments. This architectural choice is crucial for US enterprises looking to balance cost-efficiency with stringent data isolation requirements.

Elastic Scalability and High Availability

In a traditional on-premise setup, scaling up for peak loads meant provisioning expensive hardware that sat idle 90% of the time. The HxGN EAM architecture on AWS eliminates this through elastic scalability.

By utilizing auto-scaling groups and containerized workloads, the application can dynamically allocate compute resources based on real-time user demand. If a massive batch of preventive maintenance (PM) work orders is generated at midnight, the system spins up additional resources to process the queue without degrading performance for shift workers logging in.

Furthermore, HxGN relies on AWS Multi-AZ (Availability Zone) deployments to ensure high availability. By mirroring data and application instances across distinct physical data centers within an AWS Region, the platform achieves industry-leading uptime.

Disaster Recovery and Resilience

Disaster recovery is baked into the architecture, not bolted on as an afterthought. HxGN EAM utilizes continuous data replication and automated snapshotting via AWS native services.

This infrastructure ensures an incredibly low Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Even in the event of a catastrophic regional failure, traffic can be rerouted, ensuring your maintenance operations never miss a beat.

Database and Application Tier

Beneath the sleek user interface lies a robust and battle-tested database and application tier. HxGN EAM is designed to handle massive volumes of transactional data, from high-frequency meter readings to complex, multi-tiered asset hierarchies.

The RDBMS Backbone

At its core, HxGN EAM relies on a powerful Relational Database Management System (RDBMS). Historically rooted in enterprise-grade databases like Oracle and Microsoft SQL Server, the cloud-native iterations heavily utilize highly available cloud relational databases.

This relational structure is vital for EAM. Asset hierarchies, warranty data, purchasing workflows, and labor tracking require strict data integrity and complex relational mapping. The database schema is highly normalized to ensure fast read/write operations, which is critical when hundreds of technicians are updating work orders simultaneously.

Transitioning to a Microservices Architecture

Legacy EAM systems were often monolithic, meaning a bug in the inventory module could crash the entire work order system. HxGN EAM has steadily transitioned toward a microservices-oriented architecture.

This approach decouples core business logic into independent services. The application tier, largely built on robust Java enterprise frameworks, allows specific modules to be updated, scaled, and maintained independently.

This agility is why Hexagon is consistently recognized in the Gartner Magic Quadrant for EAM. The architecture allows them to push updates and new features faster than competitors burdened by monolithic technical debt.

Core Modules and Technology Stack

Here is a high-level overview of the architectural tiers and their primary functions within the HxGN EAM ecosystem:

The Extensibility Framework and Integration Capabilities

No EAM exists in a vacuum. To realize actual digital transformation, your asset management system must talk to your ERP, your shop floor sensors, and your financial software. This is where HxGN EAM’s extensibility framework shines.

Bridging the Gap: Infor OS and HxGN Interoperability

Organizations migrating from older versions will remember Infor OS (specifically Infor ION) as the primary integration engine. Hexagon has retained and expanded upon these robust interoperability capabilities.

The architecture utilizes a sophisticated message broker system to facilitate asynchronous communication between HxGN EAM and external enterprise applications like SAP, Oracle EBS, or Microsoft Dynamics. This ensures that purchasing data, inventory levels, and financial ledgers remain in perfect sync.

Modern RESTful APIs and Webhooks

For custom integrations, the platform offers a comprehensive RESTful API suite. These APIs use lightweight JSON payloads, making it incredibly easy for modern developers to interact with the system.

Whether you are building a custom dashboard or integrating a third-party logistics tool, the REST APIs provide secure, authenticated access to virtually every data point in the EAM. Furthermore, the architecture is beginning to adopt GraphQL paradigms for highly specific, bandwidth-efficient data querying.

For real-time event triggers, HxGN EAM supports Webhooks. Instead of your custom app constantly polling the server to see if a work order status changed, the EAM instantly pushes a payload to your endpoint the second the event occurs.

IoT, SCADA, and Custom Middleware

The future of maintenance is predictive, and that requires machine data. HxGN EAM’s architecture integrates seamlessly with IoT gateways and SCADA systems using industrial protocols like OPC UA.

High-velocity telemetry data (like vibration or temperature readings) is typically routed through distributed event streaming platforms like Apache Kafka or MQTT brokers before triggering automated workflows in the EAM.

For organizations that need highly specialized portal integrations, custom middleware, or unique middle-layer applications, out-of-the-box tools might not be enough. In these scenarios, partnering with experts in custom software architecture services can bridge the gap, ensuring your specific business rules are mapped flawlessly into the EAM’s API framework.

Advanced Modules: GIS, BIM, and Mobile Tech Stack

Managing a fleet of trucks or a sprawling municipal water system requires more than just tabular data. The HxGN EAM architecture integrates spatial and 3D data natively, alongside a robust mobile framework.

Spatial Integration: Esri GIS and PostGIS

For linear assets (like pipelines, railways, and power lines) and distributed geographic assets, spatial context is everything. HxGN EAM features a deep, native integration with Esri ArcGIS.

This is not just a visual map overlay; it is a true architectural integration. Asset records in the EAM database are dynamically linked to feature classes in the GIS geodatabase. When a field technician updates the condition of a pump in the EAM, the map immediately reflects that status change.

Under the hood, the system leverages spatial database extensions (like PostGIS or Oracle Spatial) to handle complex geographic queries, enabling routing optimization and proximity-based work assignments.

Building Information Modeling (BIM)

Modern facilities are designed using BIM (Building Information Modeling). HxGN EAM embraces this by integrating 3D models (from software like Autodesk Revit) directly into the asset registry.

This creates a foundational Digital Twin. Maintenance planners can navigate a 3D rendering of an HVAC system, click on a specific compressor, and instantly view its work order history, O&M manuals, and real-time IoT sensor data.

The Mobile Architecture

Field technicians need access to the EAM while deep inside a concrete basement or miles out in a rural area without cellular service. HxGN EAM’s mobile app architecture is built to handle this reality.

The mobile applications (available on iOS and Android) are built using modern cross-platform frameworks (such as Ionic/Capacitor). They utilize local on-device databases (like SQLite) to store work orders, asset data, and inspection checklists locally.

When the device loses connectivity, the technician can continue working uninterrupted. The app utilizes a sophisticated offline sync engine that queues transactions and automatically resolves conflicts with the central server once a connection is re-established.

Security, Compliance, and Governance

In today’s threat landscape, an enterprise system holding the blueprints and operational data of your critical infrastructure is a prime target for cyberattacks. Hexagon has engineered a multi-layered security architecture to protect your data.

Authentication and Access Control

Identity management is seamlessly handled through integration with corporate Identity Providers (IdPs) like Microsoft Entra ID (formerly Azure AD) or Okta. The system utilizes modern authentication protocols like SAML 2.0 and OAuth 2.0 / OIDC for secure Single Sign-On (SSO).

Once authenticated, users are governed by a strict Role-Based Access Control (RBAC) model. System administrators can define granular permissions, ensuring a junior mechanic can only view work orders assigned to them, while a regional manager has access to cross-facility financial dashboards.

Data Encryption and Compliance

Data security is enforced both at rest and in transit. The database tier utilizes AES-256 encryption for all stored data, protecting sensitive asset information and employee records. All network traffic between the client browser, mobile apps, and the servers is secured using TLS 1.3.

For US enterprises, compliance is non-negotiable. HxGN EAM’s cloud environments undergo rigorous auditing to maintain compliance with SOC 2 Type II standards, proving their commitment to security, availability, and processing integrity.

Furthermore, the architecture supports data localization and privacy controls necessary for GDPR, HIPAA (for healthcare facilities managing medical equipment), and alignment with strict environmental regulations like ISO 14001.

Frequently Asked Questions (FAQs)

Is HxGN EAM the same as Infor EAM?

Yes and no. HxGN EAM is the direct evolution of Infor EAM. Hexagon AB acquired the EAM business unit from Infor in 2021. While the core DNA, user interface familiarity, and foundational architecture remain intact, Hexagon has heavily invested in modernizing the platform, focusing on cloud scalability, AI integrations, and spatial context.

What database does HxGN EAM use?

Historically, on-premise deployments of Infor EAM heavily utilized Oracle or Microsoft SQL Server. Today, while those are still supported, the modern cloud-hosted HxGN EAM environments leverage highly scalable, managed cloud relational databases (such as Amazon RDS for Oracle or SQL Server) to ensure high availability and automated backups.

Can HxGN EAM be hosted on-premise, or is it strictly cloud-based?

While Hexagon strongly pushes the SaaS cloud-native model (due to easier upgrades, better security, and lower Total Cost of Ownership), HxGN EAM can still be deployed on-premise. This is vital for US defense contractors, nuclear facilities, or hyper-secure manufacturing plants that operate on isolated “air-gapped” networks.

How does the HxGN EAM REST API work for custom integrations?

The REST API provides a secure, token-based (OAuth) gateway to interact with EAM data. Developers can use standard HTTP methods (GET, POST, PUT, DELETE) to query asset registries, generate work orders, or update inventory counts using JSON payloads. It is highly structured, well-documented, and designed for seamless integration with modern web applications and enterprise middleware.

Conclusion: Empowering the Future of Enterprise IT

Understanding the HxGN EAM technical architecture is about much more than knowing what database it uses or where it is hosted. It is about understanding how to leverage a modern, cloud-native platform to drive true operational excellence.

As the industry moves aggressively toward the industrial metaverse, the convergence of IT (Information Technology) and OT (Operational Technology) will rely heavily on robust EAM architectures. The seamless flow of data from edge sensors to predictive AI algorithms requires a foundation that is secure, scalable, and relentlessly reliable.

For US enterprises, embracing the architectural strengths of HxGN EAM—its elastic AWS foundation, its microservices agility, and its deep API extensibility—means moving away from reactive firefighting. It empowers IT and Maintenance teams to build proactive, predictive, and highly automated environments, ultimately extending the lifecycle of critical assets and driving unprecedented ROI.