HEPO adds software for examining people and culture, coordinating business processes, and exploring work through Simulation & Gamification. Your ERP, HRIS and CRM can remain responsible for the records and transactions they already hold. Implementation connects the information and actions needed for a defined purpose.
The practical question is ownership: which system maintains each record, which information HEPO needs, what HEPO produces and where an authorised change must take effect.
Start with a piece of work
Consider a quotation that needs customer information, pricing, a review and a response. The existing systems may already own customer and price records. HEPO can bring agreed information into a defined process, route the review, present the relevant context and record the result. If the workflow needs to deliver an approved change to another system, that is a separately scoped integration operation.
A later review can examine waiting, rework or missed information. A P&C application may ask a related question about how commitments were handled, using definitions and evidence agreed for that purpose. A simulation can help participants rehearse an alternative path. These are connected uses of the work, with different responsibilities.
Agree the ownership function by function
| Area | Existing system responsibility to preserve | HEPO's contribution to establish |
|---|---|---|
| HR | Employment, payroll, benefits and the organisation's established HR processes | Working context, authored cultural definitions, development activity and permitted evidence for review |
| Sales and procurement | Customer/vendor records, prices, orders and transactions | Defined decision paths, human gates, supporting information and process-performance review |
| Operations | Production, inventory and other established operational records | Connected work, events, communication and coordination across the chosen workflow |
| Reporting | Existing reporting definitions and their source authority | Reports and interpretations needed for the HEPO application, with explicit measures and context |
| Learning | Existing learning content and administration where retained | Development journeys and participatory exploration or rehearsal, using suitable platform capabilities |
These boundaries depend on the systems you actually operate. A product category alone does not determine what an existing system can do.
Separate intake, HEPO records and outbound delivery
A connector obtains agreed external information. Mappings establish what fields and identifiers mean; schedules or supported triggers establish when it is obtained. The organisation should know which source remains authoritative and how corrections are reconciled.
HEPO also holds its own records: work, evidence, readings, recommendations, decisions and execution context. Creating one of these records in HEPO is not automatically writing it into the ERP.
Outbound delivery requires a supported writable adapter, appropriate credentials and an authorised process. Define exactly which external operation is permitted. An attempt, a confirmed delivery and a failed or retrying operation are different states. Test duplication and reconciliation behaviour for the selected path.
The Data Integration reference explains connectors, mappings, schedules and delivery. The Process example follows their role in a business decision.
Keep infrastructure decisions visible
HEPO's local inference runs inside the agreed deployment. Exchanging business information with an authorised external system is a separate connection. Together, the organisation and implementer define service locations, permitted data, credentials, support access and operating responsibilities.
Existing investments remain part of that discussion: current interfaces, data quality, update cycles and the people maintaining them. A shared platform can reduce repeated implementation work, but actual cost and complexity must be evaluated for the integration being proposed.
Begin with one boundary you can inspect
Bring one workflow and identify its records, owners, inputs, decisions and outputs. Follow a normal case, a denied action, a missing input and a failed delivery. Agree what remains in the source systems and what HEPO is responsible for carrying.