Outstanding Work Items
| Work Item | Owner | Status |
|---|---|---|
| Agree the Commitment Definition | Finance | Awaiting review. The definition and its questions are on the Project Commitment - Definition page. |
| Roll out the two worksheets | Matthew | All 17 division templates built and file-verified on 23 Sep via CVR_Rollout.ps1. Remaining: a live refresh test on the NG Bailey network, then release to the QSs. |
| Consolidate template copies | Matthew | Multiple copies of Template.xlsm exist (CVR\WorkingCVRs is the live master, fixed 23 Sep; CVR\Working and _context hold older copies). Keep one master, mark the rest clearly as history. |
| QS verification | Matthew with the QSs | Verify the new worksheets against live projects once the rollout completes. |
| Purchase Order status filter | Paul to decide, then Matthew | Investigated 25 Sep. Closed order lines are carrying £131.7M of dead commitment system wide (open lines carry £87.6M of genuine commitment). Two options for releasing it, decision needed from Paul.
Option 1, line status (recommended): release commitment when the line is closed in Focalpoint (POD_STATUS = 2, stamped by the Close Purchase Order Lines screen). Handles part closed orders correctly, for example a closed works line with an open retention line. Lines stay visible with a released flag, commitment shows zero. This is also the rule Focalpoint's own overnight committed cost engine uses (ARM_COMMITED_COST_CC filters pod_status <> 2), so it agrees with the committed cost figures already shown on Focalpoint screens. Option 2, header status: release when the whole order reaches Delivered or Complete (POH_STATUS 2 or 3), matching the existing FG ME commitment report. Simpler to explain, agrees with the numbers Finance already see, but all or nothing per order (£130.2M vs Option 1's £131.7M, the difference being part closed orders). Line status 5 (six lines, undocumented in Focalpoint) stays unreleased either way. The v3 view is drafted, deployed as a test copy ([BI].[Commitment_OrderLine_Base_3]) and certified on project 446459 on 25 Sep: all six reconciliation assertions pass, and the project's commitment moves by one penny (a closed hire line invoiced 1p short). Supporting evidence: the release removes a £118M keying error (order 675543, value entered 1000x actual) plus roughly £13.6M of genuine dead commitment on closed short lines. Live view untouched until Paul agrees. |
| Roll out the v3 commitment columns | Matthew, after Paul agrees the release rule | Once the release rule is signed off, deploy in order: the v3 view (drafted, adds ReleasedCommitment, OrderLineStatus Open/Closed for a slicer, LineShouldBeClosed), then the stored procedure to surface the new columns, then rebuild the Commitments sheet in the master template with the columns in the agreed positions and roll out to all 17 divisions, then update the Project Commitments RDL dataset and layout to match. |
| Front sheet commitment figures | Matthew | Later phase. Switch the CVR front sheet's committed cost figures from Focalpoint's own totals to the new commitment logic, once Finance agree the definition. |
| Commitments and Transactions together | Business, via Jamie Thompson | Request from the Scotland CVR meeting to see the two worksheets side by side. To be specified. |
| Arrange meeting | Matthew | Meeting with the contact Barry flagged. To be arranged. |
| GRN accruals in future divisions | Matthew, with Finance | Raised by Paul Richmond on 18 Sep. Some divisions may in time raise GRN accruals. The definition assumes GRNs post nothing to the ledger, so the treatment would need revisiting for those divisions. |
| Credit note explanation on the CVR template | Matthew | Raised by Paul Richmond on 18 Sep. Update the CVR template with an explanation of how credit notes are treated, including that unmatched credit notes are not picked up in commitment. |