Accounts: identities inside and outside the organisation
Connect internal participants, external people, companies, and their personnel to work while keeping identity records and access decisions distinct.
Manage the people, work, events, communication, knowledge, and relationships that support HEPO's three offerings alongside existing business systems.
The Operational Core is HEPO's set of shared modules for managing people, work, events, communication, knowledge, and their relationships. Teams use these modules to maintain the records of everyday activity: who owns a task, which project it belongs to, what a meeting decided, and where the supporting document can be found.
These records support People & Culture Orchestration, Process Orchestration, and Simulation & Gamification. Core is their operating foundation. It gives the offerings information to work with and a place to record activity, alongside the systems your organisation already uses.
A team prepares a customer delivery. The project brings together the responsible people and work items. A review is scheduled at a venue, and its communication records capture the follow-up. A work item becomes blocked; the owner records the dependency and links the relevant document. The next reviewer can inspect the work with its context.
Process Orchestration can coordinate the next action and examine execution evidence. People & Culture Orchestration can evaluate relevant, permitted evidence against a defined practice such as reliable handoffs. Simulation & Gamification can use selected records or prepared scenarios for exploration and learning. Each use has its own definitions, access, and interpretation; recording an event does not automatically make every use of it appropriate.
| Module | What someone maintains or examines |
|---|---|
| Employees | Employee profiles, classifications, characteristics, and connections to work |
| Accounts | Internal and external identities, companies and their personnel, and the access arrangements for participants |
| Organization | Units, positions, assignments, reporting relationships, and movement through the structure |
These responsibilities remain distinct. The employee record identifies a person in the working organisation. Account administration handles participation and identity lifecycle. Organisation records describe where people sit and the responsibilities attached to positions.
| Module | What someone maintains or examines |
|---|---|
| Calendar Events | Meetings, reviews, deadlines, and other dated occurrences with their participants and context |
| Presence | Attendance and working-style records, submissions, approvals, and corrections |
| Works | Tasks and deliverables, including progress, blockage, rework, and completion |
| Projects & Collaboration | The shared effort that connects work, people, events, and reusable templates |
| Communication Hub | Typed exchanges, feedback, recognition, and follow-ups connected to what they concern |
| HR Time Management | Holidays, breaks, schedules, absence and attendance types, quotas, and schedule assignments |
| Module | What someone maintains or examines |
|---|---|
| Content | Policies, knowledge articles, programme briefs, and other structured content |
| Media & Storage | Documents, images, video, and their assignments to relevant records |
| Address & Geography | Postal and electronic addresses with geographic context |
| Venues | Physical and virtual places, ownership, status, and related activity |
| Relationships | Named connections among records that make their context navigable |
| Reports & Analytics | Report definitions, configured measures, and the process that produces a result |
A shared record can be referenced by several modules. The project, the meeting, and the work item can point to the same employee or venue. Typed relationships explain what a connection means: a person is assigned to a unit, a meeting concerns a work item, or a document supports a decision.
That structure reduces repeated entry within HEPO and helps reviewers follow a result back to its context. It also supplies relationships that configured evaluation, retrieval, and the assistant can use. The value depends on keeping those records and connections accurate; a common model does not repair missing or mistaken information by itself.
The System Layer provides the shared interface, security, storage, integration, and execution services beneath these modules. Technical services and operating records serve different purposes, even when they work together on the same request.
An organisation can retain its ERP and HRIS for the transactions they already own, including payroll, financial records, contracts, and inventory. Implementation establishes which information HEPO holds, which external system remains authoritative, and how updates are reconciled.
The integration layer connects agreed sources through configured mappings and delivery records. Intake for analysis and supported outbound delivery are separate decisions. Keeping an ERP in place still requires careful choices about identifiers, update ownership, and the work each system performs.
The organisation and its consultants define the real units, responsibilities, working practices, and terms. Implementers configure the records, relationships, imports, and permissions. The delivery partner helps the team walk a representative piece of work and examine whether the resulting information answers the questions that matter.
Start with the activity you need to understand. The module directory then shows which records and services support it.
People & Culture Orchestration · Process Orchestration · Simulation & Gamification · Platform overview