LensReading which lens this session carries.

COO · Chief Operating Officer

Is the work moving?

366 units of work on this desk right now — 201 moving, 30 stopped on a person, 134 past their service clock. 3 escalations open or acknowledged, 6 decisions overdue, 23 gaps still on the register. Scope: Admin, AI GBS.

Health

The four counts this chair opens on

Each one is the same figure its page shows. Where it is red, the chair opens on a problem.

Operations

How the work is running on this desk

Counted across 76 workflows in 2 of 14 functions. A unit past its service clock is counted as late whether or not anybody has noticed it.

Function by function

Units on the desk, what is stuck, and the duty conflicts sitting under it

FunctionUnitsHeldLateRedEscSoDAutonomy
Admin163146714325
73%
AI GBS20316671629
81%

Live observability

366 units, as the record has them this moment

Cleared without a person48
Evidence posted, not closed87
In flight with an agent201
Stopped on a person30

AI GBS is carrying the most stopped work on this desk: 16 units on a person and 16 showing red. None of this has been written back to a system of record.

What these numbers rest on

7 source systems feed this desk, 0 of them live

0 of 7 are already past the freshness their own contract commits to, and 0 have never delivered a sync at all. Every figure above this line was read through them.

7

feeds behind this desk

of 26 on the registry; 0 connected live, 0 not connected at all

0

feeds past their own commitment

every feed in scope is inside the freshness it committed to

0

feeds not healthy

7 healthy; health here is the state the registry records, not a check run this moment

5

business terms in scope

3 contested, 1 with no book of record, 9 open disagreements

Feed by feed, and how stale each one is

7 in scope, ordered by how far past commitment they are

Source systemConnectionHealthPromisedActualWhere that leaves it
Core HR and Payroll
hcm · owner People Systems · 3 terms bound
Modeled feedInside commitment4.0 hr3.4 hrinside its own commitment
Enterprise Data Warehouse
analytics · owner Data Platform · 1 term bound
Modeled feedInside commitment4.0 hr2.9 hrinside its own commitment
Group ERP — Financials
ledger · owner Finance Systems · 3 terms bound
Modeled feedInside commitment60 min38 mininside its own commitment
Invoice Capture and AP Automation
procurement · owner Shared Services Technology · no term in this register points at it
Modeled feedInside commitment30 min27 mininside its own commitment
IT Service Management
itsm · owner IT Operations · 2 terms bound
Modeled feedInside commitment15 min9 mininside its own commitment
Planning and Consolidation
ledger · owner FP&A Systems · 3 terms bound
Modeled feedInside commitment24.0 hr22.6 hrinside its own commitment
Source-to-Pay Suite
procurement · owner Procurement Technology · no term in this register points at it
Modeled feedInside commitment60 min52 mininside its own commitment

None of these 7 feeds is connected live. Every number on this page was read from a modeled copy of them, and the ages above are the ages of that copy. 2 of them carry no term that the register has defined, so nothing on this desk states what their fields mean.

9 unsettled disagreements about what a word means on this desk

Every one is listed; none is summarized away

TD-01Revenuetiming disagreement · open 160d · owned by the CFO chair

Group ERP — Financials says Revenue arises when the performance obligation is satisfied and the entry posts. Customer Relationship Management says Revenue arises when the opportunity is marked closed won.

Commercial reporting and statutory reporting move the same money into different periods, and the commentary written on the gap treats it as performance rather than timing. Not sized. Nobody has run the two populations side by side for a period.

TD-02Customergrain disagreement · open 180d · owned by the CRO chair

Customer Relationship Management says A customer is a buying organization rolled to its ultimate parent. Group ERP — Financials says A customer is a payer, and a payer exists once per company code.

Customer counts, concentration analysis and credit exposure all depend on which one is asked, and no reconciliation exists between them. Not sized.

TD-04Supplierscope disagreement · open 208d · owned by the CPO chair

Source-to-Pay Suite says A supplier is the legal entity contracted to supply. Invoice Capture and AP Automation says A supplier is whoever the money is sent to.

Where receivables are factored the two diverge, which is precisely where payment risk concentrates. Spend by supplier and payments by supplier cannot be reconciled today. Not sized. The factored population has never been counted.

TD-05Full-time equivalentunit disagreement · open 141d · owned by the CHRO chair

Core HR and Payroll says Contracted hours over the country standard for full time. Workforce Management says Scheduled hours over a fixed forty-hour week.

The same person is worth a different fraction in each system. The 2,219 figure carried on the transaction towers is a third thing again, because it includes contractors who appear in neither definition. Not sized. Three populations, no reconciliation between any pair of them.

TD-06Incidentscope disagreement · open 96d · owned by the CIO chair

IT Service Management says An incident is a service interruption raised as a ticket by a person. This platform says An incident is one of the sixteen agentic failure records this platform keeps.

Two non-overlapping populations share one word. A reader told there are sixteen incidents and a reader told there are several thousand are both being told the truth, and neither is told which population they are looking at. Not sized. The two have never been placed on the same page until this one.

TD-07Transactioninclusion disagreement · open 172d · owned by the COO chair

Enterprise Data Warehouse says A transaction is a completed unit landed from a tower into the warehouse. This platform says A transaction is whatever each tower declares it processed.

This is the estate disagreement already published on the throughput pages: 200,240 items a week declared against 1,463,698 summed. The gap is a definition problem, not an arithmetic one, and nothing on either page resolves it. Sized and published. 1,263,458 a week between the two, which is 86.3 percent of the summed figure.

TD-08Service levelscope disagreement · open 119d · owned by the COO chair

IT Service Management says The target is the resolution time held against the priority band. Contract Lifecycle Management says The target is the number written into the service schedule of the contract.

Where the two differ the group reports itself against the softer of them without saying so. Twelve of the twenty-eight service levels this platform carries have no function attached at all, so nobody owns the comparison. Not sized. No extract of contractual thresholds exists to compare against.

TD-13Tower operating costinclusion disagreement · open 70d · owned by the CFO chair

Group ERP — Financials says Direct cost only, mapped to towers by a spreadsheet held outside every system. Planning and Consolidation says Cost at the tower node inclusive of allocated corporate overhead.

Unit cost per transaction, which is one of the most quoted figures on this platform, changes materially depending on which of the two was used, and the source is not stated where it is quoted. Not sized. The hand-kept mapping has never been reviewed by anybody outside the team that maintains it.

TD-14Reported measuregrain disagreement · open 106d · owned by the CFO chair

Reporting Semantic Layer says A measure is one governed object holding formula, population and period together. Enterprise Data Warehouse says A measure is whatever the view computes, and several views compute the same one.

The same named measure is calculated in two places with no test that the two agree. Which report a reader opened decides which answer they were given. Not sized. No comparison of the duplicated calculations has been run.

Governance

58 things in this chair's scope are open, late or breached

Counted from the registers that name a function. Nothing here has been closed in a source system, because nothing writes back to one.

Controls, whole register
14of 24 controls cannot be shown working — 7 tested and found ineffective, 7 never tested at all. An untested control is counted with the failed ones, because neither can be shown working.
controls

The control register names no function on any of its entries, so it cannot be cut to this chair. These are the enterprise figures, shown here because these controls gate work on this desk. 12 of the service levels on the register name no function either, and are not in the count above.

Escalated

3 escalations are open or acknowledged in scope

Ordered by whether the clock has already run out, then by how much work sits behind it. The agent's recommendation is shown as written.

all escalations

Is policy and strategy coming to fruition

2 of 12 checked positions held

Strategy positions and policy items written inside the functions this chair carries, read against their own outcome checks.

Not holding on the record

32

positions written

12

ratified

9

still in challenge

20

never outcome-checked

2

held

5

partially held

5

did not hold

55

policy items active

20 of the 32 positions on this desk carry no outcome check at all, so most of what this chair set out cannot be said to have worked or failed. 4 policy items are under review against 55 active ones. Every check here was written by the same platform that wrote the position.

Go deeper

The pages this chair works from

Grouped the way this chair reads them. Each opens the page that produced the numbers above.

What this chair cannot say

Nothing on this floor writes back to a system of record. Work shown as moving is moving inside this platform only, and 292 units are sitting on a person.