Kernel platform · Client overview
Understand the platform and choose your journey
Kernel connects administration, access, governed screens, documents, communication, reporting and scheduled work. Each module owns a clear part of the journey and passes its approved record references to the next module.
Choose the right document
| Document | Use it for | What it contains |
|---|---|---|
| User Guides | Learning and carrying out daily work. | Detailed steps, field meanings, permissions, review decisions, recovery and next actions. |
| Demo Walkthroughs | Presenting a complete module journey. | Preparation, example inputs, screens to open, actions to perform, expected outcomes and evidence to show. |
| UAT Handover | Testing and recording acceptance of the agreed scope. | Test cases, prerequisites, actual-result fields, defects, regression evidence, deployment/gateway runbooks and sign-off. |
What each Kernel module does
| Module | Business purpose | Outcome to explain |
|---|---|---|
| Kernel Core | Maintain shared people, organizations, contacts, addresses and reference information. | A consistent business identity used across the platform. |
| Tenant Engine | Set up a subscribing organization and govern its tenant configuration. | A tenant with reviewed setup and clear activation prerequisites. |
| Tenant Control Plane | Control environments, module availability and tenant lifecycle. | An environment and entitlement decision linked to the approved tenant setup. |
| Identity and Access Management | Create accounts and define who can do what through domains, profiles, roles and permissions. | Reviewed access assignments and traceable access decisions. |
| Axis | Maintain screen definitions, screen help, control labels and their permission references. | A screen and its own fields/controls, with reviewed presentation changes. |
| TimeVault | Manage when governed record versions become effective. | A version history that distinguishes effective dates from review status. |
| Regulix | Define rules and workflows, assign work and inspect service-level exceptions. | Controlled decisions and work items linked to their approved definitions. |
| Custodia | Capture documents, maintain metadata and control access, retention and export. | Documents with custody, version and lifecycle evidence. |
| MEDES | Connect member/case evidence, review and correspondence journeys. | A case-to-evidence-to-communication trail; target activation is required before a live business demo. |
| Nexora | Maintain learning content, assignments and completion records. | A traceable learning and competency journey. |
| Pulse | Design reusable email and letter content, preview it, review it and publish it. | Published communication content and separate generation/delivery evidence. |
| Vista | Define sources and datasets, then build and publish reports and dashboards. | A governed data-to-report or data-to-dashboard journey. |
| Enterprise Scheduler | Define and schedule registered work, inspect runs and recover failures. | A governed job, trigger, execution result and recovery history. |
| Kernel Atlas | Maintain linked platform knowledge and controlled documentation. | Knowledge records with relationships and publication context. |
Demonstration 1 · Administration to user access
- Confirm tenant setup and the intended environment in Tenant Engine and Tenant Control Plane.
- In IAM create the domain, profile and role definitions using the approved setup sequence. A newly approved domain has no profile links until they are explicitly mapped.
- Map the intended domain/profile and profile/role relationships. Grant the exact permissions needed by the role.
- In Axis open the owning screen and its Fields / Controls. Explain the difference between a screen label, a permission reference and an effective user grant.
- Create or enroll the example account, review its access assignment and sign in with the selected functional profile.
- Show an allowed action, a denied action and the originating record’s decision/audit history. Explain any explicitly assigned administrator exception separately.
Demonstration 2 · Source to content to scheduled result
- Define or select an approved data source. Build or select the dataset belonging to the selected source.
- Enter the report, dashboard or template name and business details, then open the relevant Studio.
- In Vista build the report/dashboard; in Pulse design the email or letter and bind its data fields.
- Preview the exact saved version with authorized data. Submit it for review, inspect the decision on the originating artifact, and publish the approved version.
- In Scheduler choose the registered operation and published artifact. Inspect execution ownership and inputs, preview the job and use the permitted run or schedule action.
- Inspect the result, output and audit trail. Demonstrate a permitted retry or rerun using its recorded failure/recovery rules. Content publication, output generation and external delivery are separate outcomes.
Demonstration 3 · Document and case evidence
- Use Custodia to capture and inspect an example document, its metadata and controlled access.
- After MEDES activation is verified, open the member/case context, connect the evidence and follow its review and case-work actions.
- Use the approved communication template and inspect correspondence generation, delivery status and returned responses where configured.
- Follow the document, case, workflow, content and run references to explain the cross-module handoff. Confirm provider setup before demonstrating external delivery.
Demonstration readiness: use prepared example data and the correct authorized profiles. MEDES activation and provider-dependent delivery must be confirmed in the target environment. Documentation coverage explains the implemented scope; a completed demonstration and signed UAT decision require their own evidence.
How to present and hand over
- Start with the business outcome and the module that owns the record. Open its dedicated demonstration rather than mixing operational guidance with test results.
- State the required profiles and setup. Follow the screen steps and compare the actual result with the documented expected result.
- Show approval on the originating record, the published/effective version and its audit history. Use the cross-module guide when the journey passes to another owner.
- Hand over the separate user guide for daily operation. Use the UAT workbook to record actual results, evidence, defects and the final acceptance decision.