LensReading which lens this session carries.
The catalogueInformation TechnologyData & Integration PlatformTransactional

Service IT8B

Data Product Release

Runs transactional. Starts when a threshold is crossed. It runs 4,118 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

4,118

112 in flight right now.

Stations

6

1 person · 2 agent · 3 spine

Agent share of steps

83%

Autonomy on this service is set at 77% against a ceiling of 87%.

Decisions a person makes

1

Held by Director, Data Platform.

Touchless

84%

Share of runs that complete without anybody opening them.

Timetable against actual

1.9h

Actual 2.1h, 0.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 18% of the dwellAgent2 stations and 28% of the dwellShared spine3 stations and 55% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Configuration Management Database
IT Service Management
IT Service Management
IT Service Management
IT Service Management
IT Service Management
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Request

AgentPipeline Health Agentworkflow35m50m8Configuration Management Database
2

Model schema

AgentSchema Evolution Agentworkflow2h 10m5h 3m19IT Service Management
3

Quality gate

GBSLineage Agentgbs1h 6m2h 21m16IT Service Management
4

Lineage register

GBSLineage Agentgbs1h 40m3h 26m35IT Service Management
5

Owner approve

Held for a named human when the unit exceeds the pipeline run decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

HumanDirector, Data Platformpolicy1h 47m3h 27m2IT Service Management
6

Publish

GBSLineage Agentgbs2h 42m5h 22m32IT Service Management

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through.

Move something
Demand100%
4,118 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates210 people
Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.
Agent speed100%
100% is the dwell the estate records today.
Person time a week
7,343.8h
4,118 items at 107 minutes of decision each.
Agent time a week
33,836.2h
493 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 6.2h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
18% waiting on a person
82% in the agent lane
An item now takes 600 minutes of worked time end to end against 600 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.
What this model is, on Data Product Release

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking.

6 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

6 stations, nothing waiting, nothing sent back

0 min of 10 hrs

now Request · Pipeline Health Agent · 35 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 27 hrs

now Request · Pipeline Health Agent · 35 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

5 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

The system register

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

5 of 6 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Data Platform Orchestrator
That orchestrator’s remit
Owns pipeline run work end to end inside Information Technology. Runs 3 lines across 17 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 3 human gates.
Accountable person
Director, Data Platform
Sub-function
Data & Integration Platform
Shared spine tower
data-analytics
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Pipeline IncidentIT8AData Access GrantIT8C

What this page is and is not

This is a catalogue of the modeled estate.