LensReading which lens this session carries.
Every coverage statement

Function coverage

Supply Chain

The platform observes 65.0% of the 9,620 items a week in scope here, reconstructs 25.0%, and estimates that 962 happen where it cannot read them.

The method behind this statement

Source system count · owned by Chief Supply Chain Officer · Function head

Observed is the count the source systems return.

Observed comes straight from what the connected systems return. The remainder is split between what the platform can reconstruct and what it is told exists.

What is happening in the unseen share

Carrier and 3PL exception handling conducted on the carrier’s portal.

Who has signed for it

Nobody. This figure rests on its method alone.

An attestation would not turn an estimate into a measurement.

Work filed here that the platform could not see

2 items have been filed by somebody who did the work off-platform.

Carrier exception cleared on their portalDeclared · accepted
IN-0003 · Gathoni Mwangi · Supply Chain · logistics exceptions
Planning override agreed in a stand-upDeclared · rejected
IN-0020 · Ryo Nakamura · Supply Chain · demand planning

Gaps raised against this function

1 gap in a chain that something must have filled.

Shipment held → Shipment releasedConfirmed by a filing · strong

Exceptions are being cleared on the carrier’s own portal.

SP-0007 · 74 instances · median gap 11.0 hours

What this statement is, and what it is not

Coverage can only ever be estimated from the outside.

A coverage statement is disputable by design.

Compare against every other statement