ApexIQ Companion | Readiness
What a PoC pack looks like
An excerpt of the customer charter from a PoC Readiness Pack. The seller, its customer, and the evaluation are fictional, so the charter can be shown as it was written.
Fictional companies and evaluationNo customer material usedAn excerpt of 1 of the 3 files
What was sent
A proof of concept with its start date close and its owners unclear
Halden Systems is preparing a proof of concept for Marlowe Freight, which is evaluating real-time exception detection for its dispatch operation. Halden's account team sent the brief with the discovery notes and the success measures raised on the first call.
- Known: the decision Marlowe Freight wants to make, the person who makes it, and 1 confirmed limit on false alerts
- Not known: who at Marlowe grants access to the telematics feed, and who at the depot runs the evaluation
The customer charter
The excerpt, as it is delivered
The charter is set in the white sheets. Our notes on why it is written the way it is sit between them, on the orange rule, and are not part of what you receive.
Readiness | Customer PoC charter
Real-time exception detection evaluation
Pack details
| Field | Entry |
|---|---|
| Customer | Marlowe Freight |
| Prepared for | Halden Systems account team |
| Pack | PoC Readiness Pack |
| This file | Customer PoC Charter |
| Status | Proposal for review |
Readiness
Where this evaluation stands against the 5 checkpoints, and what would move each one. The level follows from the checkpoints and is not set by hand.
| Checkpoint | State | What would move it |
|---|---|---|
| The question | Proposed | Helen Marsh, Marlowe Freight's operations director, confirms that the decision is whether to proceed to a paid pilot at the Leeds depot, taken at the steering meeting on 20 October. Priya Nair at Halden to secure the confirmation by 16 September. |
| The measures | Proposed | Tom Hale, Marlowe Freight's dispatch lead, confirms the targets below and the July dispatch log as their baseline, by 23 September. |
| The evidence | Proposed | Both teams agree the alert log export and the dispatcher review sheet as the evidence for each criterion. Priya Nair to settle it by 23 September. |
| The people | Missing | Nobody is named to run the evaluation at the Leeds depot, so no result has anyone to accept it. Helen Marsh to name the depot lead by 23 September. |
| The start | Missing | Access to the telematics feed has no owner and no date, and the evaluation cannot take in a single event without it. Marlowe Freight's IT service owner to be named, and read access granted, by 30 September. |
| Level | Why |
|---|---|
| Not ready | The people and the start are Missing. Until the depot lead is named and access to the feed has an owner, the evaluation cannot run, and nobody could accept a result if it did. |
Reading this. Not ready means the evaluation is not yet able to produce a decision anyone can act on. It names what has to happen first, before your time is spent on it.
What we are proposing
A 4-week proof of concept at the Leeds depot, running Halden's exception detection against Marlowe Freight's own telematics feed alongside the current dispatch process. It establishes whether delayed and at-risk shipments are flagged early enough, and accurately enough, for dispatchers to act on them. Nothing changes in how Leeds dispatches while it runs.
Success criteria
Each criterion names what is measured, how, against what, and who accepts the result. The measure is written before the target: a target with no measure is a wish.
| Criterion | Measure | Target and its basis | State |
|---|---|---|---|
| Exceptions are flagged in time to act | Minutes from the vehicle event to the dispatcher's alert, at the 90th percentile | 15 minutes or less. Basis: the latest point at which a re-route still makes the delivery slot, from the discovery notes. | Proposed |
| Real exceptions are caught | Share of the exceptions in the dispatch log that were also flagged | At least 85% over the 4 weeks. Basis: put forward by Halden. Marlowe Freight to confirm the level it would act on. | Proposed |
| Dispatchers are not flooded | False alerts per 100 shipments, as judged in the dispatcher review | No more than 3. Basis: the limit Tom Hale set on the first call. | Agreed: confirmed by Tom Hale in the call notes of 28 August |
The baseline, measurement and representative conditions, and milestones are not shown in this example.
Evidence
| Criterion | Evidence captured | By whom | Sufficient when |
|---|---|---|---|
| Exceptions are flagged in time to act | Alert log export, with the event time and the alert time for every alert | Sam Okafor, Halden solutions engineer | Every alert raised in the 4 weeks is present, with both times |
| Real exceptions are caught | Dispatch exception log, each entry marked flagged or not flagged | Tom Hale, Marlowe Freight dispatch lead | Every logged exception carries a mark |
Prerequisites
| Prerequisite | Owner | Due date or trigger | Blocks |
|---|---|---|---|
| Read access to the telematics feed | Missing: nobody named at Marlowe Freight IT | 30 September | The whole evaluation |
| A named depot lead at Leeds | Helen Marsh | 23 September | Acceptance of every result |
| The dispatcher review sheet | Priya Nair | 23 September | The false alert measure |
Stop conditions
| If this happens | Who calls it | What happens then |
|---|---|---|
| The feed cannot be reached by 30 September | Priya Nair and Helen Marsh, jointly | Pause, and restart the 4 weeks from the day access is granted |
| Alerts disrupt live dispatch | The Leeds depot lead | Stop alerts reaching dispatchers, keep logging, and review within 2 working days |
What is not covered
Alerts to Marlowe Freight's own customers, and any depot other than Leeds. Both follow from the decision this evaluation supports, and neither is part of it.
What we are asking you to do
| We are asking you to | Checkpoint it moves | By when |
|---|---|---|
| Confirm the decision, who makes it, and that it is taken on 20 October | The question | 16 September |
| Confirm the targets, and the July dispatch log as their baseline | The measures | 23 September |
| Name the Leeds depot lead who accepts each result | The people | 23 September |
| Name the owner of access to the telematics feed, and grant read access | The start | 30 September |
The full pack
What this excerpt leaves out
The pack you receive carries 3 files, built from 1 record so they agree:
- The whole customer charter, including the problem, the baseline, measurement, and milestones
- The internal charter, for your team alone: the reasoning behind the proposal, and what to resolve before the customer charter goes out
- The working workbook, with the criteria, milestones, register, and results record, and the same readiness view with an owner and a date against each checkpoint. It is locked except for the cells your team fills in
Your brief is deleted when the pack is sent, and nothing you send is ever used as an example. This one was written from scratch.
Price
£1,550 standard, £1,750 same day
Flat price per pack, excluding VAT, whichever pack you choose. The same-day rules are on the pricing page.