.png)
Hexagon HxGN EAM Integration Guide
Integrate HxGN EAM with enterprise applications through deployment-specific REST APIs, legacy SOAP services, scheduled synchronization, and controlled workflow orchestration.
Hexagon HxGN EAM integration options at a glance
HxGN EAM provides REST-oriented integration capabilities for retrieving, creating, updating, and processing business objects such as Work Orders, Equipment, Parts, Employees, and Purchase Orders. Deployment-specific SOAP services remain relevant for legacy or compatibility scenarios. Webhooks are not generally confirmed, so near-real-time requirements may depend on outbound services or event rules available in the customer environment; otherwise, Martini can poll incrementally using timestamps or status filters. Batch, attachment, and file capabilities vary by release and configuration. Martini workflows can authenticate through the enabled deployment method, transform JSON or XML, apply validation, and coordinate reliable synchronization.
| Integration point | Supported by Hexagon HxGN EAM? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Retrieve, create, update, and process HxGN EAM objects such as Work Orders, Equipment, Parts, Employees, and Purchase Orders. Exact resources, methods, fields, and pagination depend on the deployment and release. | Martini can consume HxGN EAM REST endpoints from workflows, transform JSON payloads, apply business rules, and expose APIs for surrounding applications. |
| SOAP APIs | Limited | Support legacy or deployment-specific web-service integrations where current HxGN EAM environments expose SOAP operations and a WSDL. | Martini can consume SOAP services when the WSDL, endpoint, and authentication details are available, while preserving XML mapping and error handling in workflows. |
| Webhooks / outbound callbacks | Not confirmed | Selected deployments may provide outbound web services, event rules, callbacks, or middleware notifications, but no generally applicable public webhook model was confirmed. | Martini can receive an outbound notification if the customer configuration supports a compatible endpoint; otherwise it can use scheduled polling rather than assuming webhook delivery. |
| Bulk / asynchronous / batch APIs | Limited | Batch processing may be available through selected services, imports, scheduled jobs, or integration capabilities. A universal bulk REST API was not confirmed. | Martini can process bounded batches, paginate requests, checkpoint progress, apply backoff, and retry selected transient failures. |
| File / attachment APIs | Limited | Document and attachment processes may be available for Work Orders or Equipment, but the current binary API surface, repository model, and limits require deployment confirmation. | Martini can orchestrate confirmed metadata and file operations and apply MIME-type, size, retention, and error policies when endpoints are available. |
| Database / analytics access | Legacy | Authorized customer-managed installations may permit database reads for reporting or extraction, but direct database writes are not the preferred integration boundary and should not be assumed for cloud deployments. | Martini can use JDBC for an explicitly approved extraction scenario, while application APIs remain preferable for validation, security, business rules, and audit behavior. |
| Authentication | Limited | Depending on deployment and identity configuration, HxGN EAM may use Basic Authentication, session or token authentication, or OAuth and external identity-provider mechanisms. | Martini stores credentials and tokens in environment-specific secrets and configures the workflow for the authentication method confirmed by the HxGN EAM administrator. |
| Scheduled synchronization | Yes | Scheduled polling can support incremental synchronization when webhook or outbound event delivery is unavailable, using update timestamps, status changes, or other supported filters. | Martini scheduler-triggered workflows retrieve pages, maintain watermarks and overlap windows, deduplicate results, and route failures for retry or review. |
How Hexagon HxGN EAM exposes data and business events
HxGN EAM REST APIs
HxGN EAM provides REST-oriented integration capabilities for accessing application data and business processes. Depending on the release, enabled modules, and configuration, REST resources can support objects including Work Orders, Equipment, Parts, Employees, and Purchase Orders.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the deployment-specific REST endpoint, retrieves or receives the required resource, maps the HxGN EAM JSON model to a canonical model, applies validation and business rules, and writes to the target system or back to HxGN EAM.
Implementation sequence
HxGN EAM SOAP services
HxGN EAM has a history of SOAP and web-service integrations, particularly in legacy or deployment-specific environments. SOAP coverage and current recommendations vary by release and should be confirmed with the target WSDL and documentation.
Martini implementation pattern
Martini implementation pattern: Martini consumes the confirmed SOAP operation, handles XML serialization and authentication, maps the response into a reusable internal model, and routes business or transport errors according to the workflow policy.
Implementation sequence
Scheduled HxGN EAM synchronization
Because a generally applicable public webhook model was not confirmed, scheduled polling is a practical option for incremental synchronization. The workflow can use supported last-updated timestamps, status filters, pagination, and an overlap interval.
Martini implementation pattern
Martini implementation pattern: a scheduler-triggered workflow loads a durable watermark, retrieves bounded pages from HxGN EAM, deduplicates by stable identifiers, maps changed objects, writes downstream results, and advances the checkpoint only after successful processing.
Implementation sequence
HxGN EAM batch and attachment processing
Batch jobs, imports, and document or attachment operations may be available in selected HxGN EAM configurations, but a universal bulk or attachment API was not confirmed. The target deployment must establish the supported operation and limits.
Martini implementation pattern
Martini implementation pattern: Martini processes bounded groups or confirmed document operations, records progress and file metadata, validates sizes and MIME types, and uses checkpoints so a failed batch can resume without replaying completed work.
Implementation sequence
Common Hexagon HxGN EAM integration patterns
Pattern 1: Synchronize ServiceNow maintenance requests
When to use this pattern
Use this pattern when ServiceNow manages incidents, requests, or approvals while HxGN EAM manages maintenance execution. It supports request intake, Work Order creation, status updates, completion notes, and cost feedback across the two systems.
Integration direction
Example Mapping
| Hexagon HxGN EAM Field | Canonical Field | Target Field |
|---|---|---|
| number | sourceRequestId | externalReference |
| short_description | maintenanceDescription | description |
| priority | priorityCode | priority |
| cmdb_ci | equipmentReference | Equipment |
Martini implementation pattern
Martini receives a ServiceNow request, resolves Equipment, Location, Department, and priority references through HxGN EAM lookups, creates or updates a Work Order, and stores both identifiers. A reverse workflow sends status and completion information to ServiceNow. Validation errors are quarantined, while timeouts, rate limits, and transient server failures use bounded retries.
Martini capabilities used
- workflows
- API consumption
- API exposure
- data mapping
- business rules
- error handling
Pattern 2: Synchronize assets and maintenance data with SAP
When to use this pattern
Use this pattern when SAP owns financial, organizational, supplier, or material information and HxGN EAM owns asset maintenance, Work Orders, inspections, or technician execution. Object ownership should be explicitly defined before enabling bidirectional updates.
Integration direction
Example Mapping
| Hexagon HxGN EAM Field | Canonical Field | Target Field |
|---|---|---|
| materialNumber | partCode | Parts.code |
| plant | organizationCode | organization |
| equipmentNumber | equipmentId | Equipment.code |
| maintenanceOrder | workOrderId | Work Orders.externalReference |
Martini implementation pattern
Martini consumes approved SAP changes, maps organization and material identifiers, validates HxGN EAM references, and performs supported upserts. It can extract HxGN EAM Work Orders and Equipment incrementally for SAP reporting or maintenance processes. Watermarks, overlap windows, reconciliation, and cross-reference storage reduce missed or duplicated updates.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- transformations
- validation
- checkpointing
- error handling
Pattern 3: Integrate HxGN EAM procurement with Oracle
When to use this pattern
Use this pattern when HxGN EAM identifies material requirements and Oracle manages procurement, suppliers, receipts, or costs. It is appropriate for Parts, Purchase Requisitions, Purchase Orders, and related inventory reconciliation.
Integration direction
Example Mapping
| Hexagon HxGN EAM Field | Canonical Field | Target Field |
|---|---|---|
| PartCode | itemIdentifier | itemNumber |
| PurchaseRequisition | procurementRequestId | requisitionNumber |
| PurchaseOrder | purchaseOrderId | orderNumber |
| supplier | supplierIdentifier | supplierNumber |
Martini implementation pattern
A Martini workflow validates HxGN EAM procurement references, transforms approved requirements into the Oracle model, and records returned supplier and document identifiers. Receipt, cost, and availability data can be reconciled back to HxGN EAM. Lookup-before-create logic and idempotency keys prevent duplicate purchasing documents; business-rule failures are not blindly retried.
Martini capabilities used
- workflow orchestration
- API consumption
- data mapping
- business rules
- idempotency
- retry handling
Pattern 4: Poll HxGN EAM changes for reporting
When to use this pattern
Use this pattern when the customer environment does not provide a confirmed webhook or outbound callback mechanism and downstream reporting requires reliable incremental delivery of Work Orders, Equipment, Parts, or maintenance metrics.
Integration direction
Example Mapping
| Hexagon HxGN EAM Field | Canonical Field | Target Field |
|---|---|---|
| WorkOrderNumber | workOrderId | work_order_id |
| EquipmentCode | equipmentId | equipment_id |
| lastUpdated | changedAt | updated_at |
| status | workOrderStatus | status |
Martini implementation pattern
A scheduled Martini workflow retrieves filtered HxGN EAM pages using supported update fields, applies an overlap interval, normalizes dates and identifiers, and writes curated data to the approved reporting layer used by Power BI. It advances the watermark only after successful delivery and records page, request, and execution identifiers for replay and reconciliation.
Martini capabilities used
- scheduler triggers
- API consumption
- pagination handling
- data mapping
- checkpointing
- monitoring
- error handling
Applications commonly integrated with Hexagon HxGN EAM
HxGN EAM commonly participates in enterprise architectures alongside service management, ERP, procurement, workforce, field-service, EAM, and analytics products. The exact ownership of each object should be agreed before implementation, because the integration relationship does not imply a native connector or jointly documented integration.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| ServiceNow | Exchange maintenance requests, approvals, incidents, and Work Order status between service management and enterprise maintenance operations. | ServiceNow → Martini → Hexagon HxGN EAM | Martini receives a ServiceNow request, resolves Equipment, Location, Department, and priority references, creates or updates an HxGN EAM Work Order, stores cross-system identifiers, and returns execution status and completion details. Validation failures and transient API errors are routed for diagnosis or retry. |
| SAP | Synchronize asset, material, supplier, purchasing, financial, and maintenance data while assigning clear system-of-record ownership. | SAP → Martini → Hexagon HxGN EAM | Martini consumes approved SAP master-data or procurement messages, maps organizational and material identifiers to HxGN EAM fields, validates references, and writes supported objects through HxGN EAM APIs. Reverse flows publish Work Order and maintenance outcomes back to SAP with durable cross-references. |
| Oracle | Exchange procurement, inventory, supplier, receipt, and cost information between Oracle applications and HxGN EAM. | Oracle → Martini → Hexagon HxGN EAM | A Martini workflow transforms HxGN EAM Parts, Purchase Requisitions, and Purchase Orders into the Oracle model, applies approval and duplicate-prevention rules, and reconciles supplier, receipt, and cost data back to HxGN EAM. Idempotency keys and retry policies protect document creation. |
| Microsoft Dynamics 365 | Coordinate Equipment, customer, site, workforce, field-service, and maintenance information across operational teams. | Microsoft Dynamics 365 → Martini → Hexagon HxGN EAM | Martini orchestrates bidirectional API exchanges, normalizes asset and site identifiers, enriches service requests with HxGN EAM references, and sends completed Work Order information to Dynamics 365. Business rules control ownership, status transitions, and handling of unmapped assets. |
| Salesforce | Synchronize customer, site, service request, maintenance completion, and cost information. | Salesforce → Martini → Hexagon HxGN EAM | Martini exposes or consumes controlled APIs for Salesforce, maps service requests to HxGN EAM Work Orders, and publishes status, completion notes, and costs back to Salesforce. The workflow uses correlation identifiers, reference validation, and retry handling for transient failures. |
| IBM Maximo | Support EAM migration, coexistence, consolidation, divestiture, or phased replacement programs. | IBM Maximo → Martini → Hexagon HxGN EAM | Martini performs staged extraction and transformation of Equipment, Work Orders, Parts, and maintenance history, using mapping tables for status and organization codes. During coexistence, workflows synchronize only agreed objects and use checkpoints, reconciliation reports, and duplicate controls. |
| Workday | Exchange employee, organization, and cost-center information used for workforce and maintenance administration. | Workday → Martini → Hexagon HxGN EAM | Martini retrieves approved workforce and organizational changes, maps Employees and Departments to HxGN EAM identifiers, validates effective dates and organization context, and applies updates through the available HxGN EAM API. Failed reference mappings are isolated for correction rather than retried blindly. |
| Microsoft Power BI | Publish Work Orders, Equipment, Parts, inventory, and maintenance metrics for reporting and operational analysis. | Hexagon HxGN EAM → Martini → Microsoft Power BI | Martini extracts incrementally through HxGN EAM APIs, creates a curated reporting model, normalizes dates and identifiers, and delivers data through the customer’s approved reporting layer. Watermarks, pagination, and reconciliation checks prevent incomplete reporting loads. |
How to build a Hexagon HxGN EAM integration in Martini
Objective
Establish the HxGN EAM endpoint, API version, organization context, and authentication method for the specific deployment without embedding credentials in workflows.
Instructions in Martini
- Confirm the base URL, API version, enabled resources, and required headers with the HxGN EAM administrator.
- Confirm whether Basic, session or token-based, OAuth, or external identity-provider authentication is enabled.
- Store credentials and tokens in Martini environment-specific secrets.
- Test authorization against a non-destructive resource before enabling writes.
Objective
Select an event, inbound API, or scheduled trigger based on what the target HxGN EAM deployment actually exposes.
Instructions in Martini
- Use an inbound API or outbound notification only when the customer configuration supports it.
- Use a scheduler for incremental polling when webhook or callback delivery is unavailable.
- Define the polling interval, update filter, overlap window, and expected volume.
- Capture a correlation identifier for every workflow execution.
Objective
Retrieve or receive HxGN EAM objects using deployment-specific operations, pagination, filters, and bounded request sizes.
Instructions in Martini
- Confirm resource paths, required fields, pagination behavior, and ordering from the environment API definition.
- Retrieve Work Orders, Equipment, Parts, Employees, Departments, or procurement objects as required.
- Persist page, cursor, or watermark state after successful processing.
- Avoid unrestricted concurrency and respect deployment-specific limits.
Objective
Coordinate lookups, transformations, target writes, status handling, and compensating actions in a maintainable Martini workflow.
Instructions in Martini
- Resolve related Equipment, Location, Department, Organization, supplier, and employee references before transactional writes.
- Separate lookup, validation, transformation, write, and notification stages.
- Use reusable workflow logic for common authentication, mapping, and error handling.
- Route permanent business failures to an operational review path.
Objective
Convert HxGN EAM JSON or XML payloads into canonical and target-specific models while preserving identifiers and business context.
Instructions in Martini
- Map vendor fields to canonical names before applying target-specific transformations.
- Normalize timestamps, time zones, status values, codes, and organization identifiers.
- Preserve source identifiers, request identifiers, and HxGN EAM response details.
- Handle configured custom fields only after comparing the target schema with the deployment definition.
Objective
Apply validation, ownership, status-transition, duplicate-prevention, and authorization rules before writing data.
Instructions in Martini
- Validate required references and controlled lifecycle values.
- Use lookup-before-create or external-reference logic for Work Orders and Purchase Orders.
- Do not treat a status field update as a valid business transition without confirming the required operation.
- Reject or quarantine invalid records rather than repeatedly submitting them.
Common Hexagon HxGN EAM data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Work Orders | Represent maintenance requests, preventive maintenance activities, corrective work, assignments, status, completion notes, and costs. | ServiceNow, SAP, Microsoft Dynamics 365, Salesforce, IBM Maximo, Microsoft Power BI | Martini validates Equipment, Location, Department, priority, employee, and status references; maps fields; applies transition rules; stores cross-system identifiers; and uses idempotent create or update logic. |
| Equipment | Represent maintainable assets and equipment records used in maintenance execution and asset hierarchy processes. | SAP, Microsoft Dynamics 365, IBM Maximo, Salesforce, Microsoft Power BI | Martini synchronizes stable asset identifiers and attributes, resolves organizational context, transforms hierarchy data, and uses incremental extraction with reconciliation checks. |
| Parts | Represent spare parts, materials, stock items, and inventory-related information required for maintenance and procurement. | SAP, Oracle, IBM Maximo, Microsoft Power BI | Martini maps material and inventory identifiers, validates Stores and organizational references, handles bounded batches, and prevents duplicate material or stock updates. |
| Purchase Orders | Represent procurement documents for parts, services, and other maintenance requirements. | Oracle, SAP, Microsoft Power BI | Martini validates supplier, organization, line, and status data; coordinates document creation and updates; records external identifiers; and distinguishes business-rule errors from retryable transport failures. |
| Employees | Represent technicians, supervisors, planners, and other workforce members involved in maintenance operations. | Workday, SAP, Microsoft Dynamics 365, ServiceNow | Martini maps employee and organization identifiers, applies effective-date rules, protects sensitive data, and isolates unmapped or unauthorized updates for review. |
| Departments | Represent organizational or operational ownership structures used for maintenance responsibility and cost allocation. | SAP, Workday, ServiceNow, Oracle | Martini synchronizes department codes and ownership relationships, validates references before transactional writes, and maintains mapping tables for differing organizational models. |
Authentication and security considerations
Deployment-specific authentication
HxGN EAM authentication varies by release, deployment, and identity configuration. Confirm whether the environment uses Basic Authentication, session or token-based authentication, OAuth 2.0, or an external identity provider.
Least-privilege access
API users should have only the organization, role, and object permissions required for the integration. Validate access to each resource and business operation before enabling production writes.
Secret protection
- Store credentials, tokens, and client secrets in Martini environment-specific secrets.
- Do not embed authentication values in workflow definitions or logs.
- Protect request and response data that may contain sensitive workforce, asset, procurement, or maintenance information.
Operational considerations for Hexagon HxGN EAM integrations
Schema and deployment differences
Confirm the HxGN EAM version, base URL, enabled modules, custom fields, required headers, organization context, and supported operations. Do not assume that a generic HxGN EAM schema applies to every tenant or installation.
Pagination and incremental extraction
Use the documented pagination model, deterministic ordering, update filters, durable watermarks, and a small overlap window. Checkpoint only after downstream processing succeeds.
Reliability and duplicate prevention
- Use bounded concurrency and exponential backoff for rate limits, timeouts, and transient 5xx responses.
- Use source identifiers, external references, correlation IDs, and idempotent upserts for Work Orders and procurement objects.
- Preserve HxGN EAM responses and Martini execution identifiers for diagnosis and reconciliation.
Business validation
Validate Equipment, Location, Department, Organization, employee, supplier, priority, and status references. Confirm lifecycle operations because changing a status field may not perform the required business transition.
Testing and change management
Test custom fields, time zones, attachments, file limits, pagination behavior, and authorization in a representative environment. Revalidate mappings after HxGN EAM upgrades or configuration changes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini coordinates HxGN EAM with service management, ERP, procurement, workforce, field-service, EAM, and reporting applications in a single workflow model. This avoids duplicating business logic across isolated scripts.
Reusable integration assets
Teams can centralize authentication, pagination, mapping, validation, error handling, retries, and cross-reference logic while exposing controlled APIs for other systems.
Operational reliability
- Support scheduled, API-led, and deployment-specific event-driven patterns.
- Apply canonical mappings and business rules consistently across HxGN EAM objects.
- Use checkpoints, retries, monitoring, and durable identifiers for maintainable synchronization.
- Extend workflows with custom logic when deployment-specific behavior requires it.
Frequently asked questions
HxGN EAM can be integrated primarily through its deployment-specific REST APIs. Legacy or compatibility scenarios may use SOAP services, while scheduled polling can support incremental synchronization when outbound events or callbacks are unavailable. Batch, attachment, database, and authentication options depend on the HxGN EAM release and deployment configuration.
Yes. Martini can consume HxGN EAM REST APIs, consume SOAP services where a supported WSDL is available, orchestrate scheduled polling, transform JSON or XML, apply validation and business rules, and expose controlled APIs for surrounding applications. A dedicated native Martini connector was not confirmed.
No. A dedicated HxGN EAM connector is not required. Martini can integrate using the HxGN EAM REST APIs, deployment-specific SOAP services, supported outbound notifications, scheduled retrieval, authentication methods, and other confirmed endpoints in the target environment.
Lonti does not charge an additional per-connector or per-vendor fee to integrate HxGN EAM. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Hexagon, infrastructure providers, or other third-party systems based on subscription, usage, and deployment model.
REST APIs should generally be the primary integration boundary because they support application-level data and business-process interactions. SOAP can be used when required by a legacy or deployment-specific environment. Batch, attachment, database, and outbound integration capabilities should be confirmed against the target release rather than assumed.
No generally applicable public HxGN EAM webhook catalog was confirmed. Some deployments may support outbound web services, event rules, callbacks, or middleware notifications. If those options are unavailable, Martini can use scheduled polling with update timestamps, status filters, pagination, overlap windows, and durable checkpoints.
Use the supported REST or SOAP operations, define system-of-record ownership for each object, and map HxGN EAM objects such as Work Orders, Equipment, Parts, Employees, Departments, and Purchase Orders to a canonical model. Martini can normalize dates, codes, statuses, and identifiers, validate references, and maintain cross-system identifiers and watermarks.
Retry timeouts, rate-limit responses, and selected transient server failures with exponential backoff and bounded concurrency. Do not blindly retry validation, authorization, or business-rule errors. Use source identifiers, external references, lookup-before-create logic, correlation IDs, and durable cross-reference storage to prevent duplicate Work Orders, Purchase Orders, or inventory transactions.
Related Martini documentation
Plan your Hexagon HxGN EAM integration
Define the HxGN EAM resources, authentication method, synchronization triggers, ownership rules, and operational controls required for a reliable Martini integration.