COOL AI · Presight | Working brief
DAS delivery plan
Product core, responsibilities and proposed milestones.
Solution architecture
A shared core supports each customer’s business workflow and delivery outputs.
Presight coordination
Customer, environment, access and delivery coordination.
COOL AI common product core
Workflow design, business tools, shared controls and outputs.
Customer Use Case Packs
Specification, field mappings, rules, checks, reports and operating guide.
Supporting services
Customer applications & data; AI models, document & speech processing; cloud/on-prem infrastructure, storage & security; …
COOL AI common product core · logical design
Business workspace
Use Case design
Execution
Enterprise brain
Data intake
Models & infrastructure
Create and maintain Use Cases
- 01
Understand the work
Confirm inputs, rules, owners and the useful result.
- 02
Configure / generate
Map fields and assemble the workflow and report.
- 03
Test & approve
Check normal and exception samples with reviewers.
- 04
Release & maintain
Release the approved version with an operating guide.
Business goal + sample documents + rules + reviewers
Workflow + data mappings + checks + report + operating guide
Delivery timeline
Rolling preparation and releases; Day 45 acceptance target, Day 60 contractual limit.
Delivery targets; scope, access and team allocation agreed at kick-off. Day 0 = contract effectiveness; RFP implementation/SAT limit = 60 calendar days.
Business/data preparation
Procurement workflow
Next 2 Use Cases
Next 3 Use Cases
Final 4 Use Cases
Testing & acceptance
Contingency
Day 0
D7 · Pass logic
Named owners approve sources, rules and the release plan.
Delivery team & business-unit engagement
Proposed roles and parallel workstreams; allocation agreed at kick-off.
| Role | Work & output | When / engagement |
|---|---|---|
| RoleDelivery lead | Work & outputScope, release plan, issues and decisions. | When / engagementThroughout. |
| RoleBusiness/data implementation | Work & outputBusiness-unit interviews; workflow, source and rule mapping; sample confirmation. | When / engagementBefore each release; on-site workshops + remote preparation. |
| RoleUse Case engineering & integration | Work & outputConfigure/build tools and interfaces; batch development and corrections. | When / engagementEach delivery batch. |
| RoleQuality, deployment & handover | Work & outputNormal/exception tests, permission/recovery checks, training and runbooks. | When / engagementEvery release and final acceptance. |
| RoleDAS / Presight coordination | Work & outputDAS appoints business, data and review owners per business unit; Presight coordinates environment, access and delivery. | When / engagementKick-off and each release. |
- Workflow walkthrough
- Authorised samples / data access
- Review working case
- User trial & sign-off
Review all 10 Use Cases in week one to expose source-access blockers. Share one source/rule/decision register; the prior batch operates while the next business unit is prepared.
Release gates
D7 · Scope & batch plan
Named owners approve sources, rules and the release plan.
D21 · First department using procurement workflow
Normal and exception samples pass; usable output and reviewer sign-off.
D28 · 3 Use Cases
Each case passes its samples and reviewer sign-off.
D35 · 6 Use Cases
Changed mappings and rules pass normal and exception tests.
D42 · All 10 ready for acceptance
Full scope has usable outputs and owner sign-off.
D45 · Target signed acceptance & handover
Final scope, permissions, recovery and operating handover approved.
D60 · Contingency to contractual limit
Implementation and SAT complete within the contractual limit.
Reuse & cooperation
Engineering procurement → automotive parts: keep the useful flow, validate local differences.
| Deliverable | Retain | Confirm for the next business unit |
|---|---|---|
| DeliverableUse Case Pack | RetainSpecification, tools and workflow. | Confirm for the next business unitFields, units, business rules and owners. |
| DeliverableChecks & report | RetainTest method, evidence and report structure. | Confirm for the next business unitLocal samples, review decisions and useful outputs. |
| DeliverableOperating handover | RetainGuide and controlled change record. | Confirm for the next business unitAnother operator can run and maintain the agreed case. |
Review one agreed adaptation before scaling.
Next business unit
Review the specification, mappings, checks, report and operating guide together; record each approved change.
Procurement workflow
Screens captured 11 Oct
Illustrative procurement case · prepared sample data
- User input — add the invoice and supporting materials.
- Evidence + person — trace findings to sources, then confirm corrections in human review.
- Export + overview — hand over the report and retain history with the updated overview.
Earlier UI recording
AP handover is a finance handoff, not payment.
Download earlier recording