Operational views
Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Defence support & sustainment
Administer non-combat support training, prerequisites, authorised assessments, credential expiry and refresher enrolment.
12 workspace menus · 5 role profiles · Connected records
Designed for Defence support training schools and qualification administrators

Operational workspace and record review. Select a screen to inspect it in full.


Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Administer non-combat support training, prerequisites, authorised assessments, credential expiry and refresher enrolment. A training attendance record does not establish that a person has met the prerequisites and current assessment requirements for a support role. The system connects enrolment and qualified assessment to credential validity, making expired or incomplete qualifications visible for administrative action.
From intake to authorised completion, with evidence at each decision.
Enrol support personnel.
Verify training prerequisites.
Record qualified assessment.
Manage credential expiry and refresher enrolment.
Permissions are configured and tested for the agreed responsibilities.
Interface scope, data mapping and testing are agreed for each engagement.
Access schedules and qualification status, and record permitted assessment evidence on approved devices.
Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.
Core workflows and approval rules are defined with your business owners. Operational AI can be assessed separately against a specific business outcome and review requirements.
AI extensions are scoped around the required data, business outcome and review controls.
Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.
Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.
Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.
An example operating scenario
A support trainee enrols with a missing prerequisite. The administrator resolves the requirement before scheduling, an authorised assessor records the result and the qualification receives an expiry date. A subsequent refresher requirement appears in the renewal queue.
Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.
Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.
Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.
Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.