The catalogue EngineeringSecurity EngineeringTransactional

Service EN10A

Vulnerability Remediation

Runs transactional. Starts when a request lands in the queue. It runs 3,326 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, 4 of them on the shared spine.

Runs a week

3,326

86 in flight right now.

Stations

1 person · 2 agent · 4 spine

Agent share of steps

86%

Autonomy on this service is set at 72% against a ceiling of 82%.

Decisions a person makes

Held by Director, Security Engineering.

Touchless

81%

Share of runs that complete without anybody opening them.

Timetable against actual

1.0h

Actual 0.9h, 0.1h under the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 42% of the dwellAgent2 stations and 24% of the dwellShared spine4 stations and 34% of the dwell4 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Materials and Inventory

Configuration Management Database

Group ERP — Materials and Inventory

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Scan	GBS	Vulnerability Scanning Agent	gbs	1h 14m	2h 37m	44	Group ERP — Materials and Inventory
2	Score severity	GBS	Vulnerability Scanning Agent	gbs	18m	36m	4	Group ERP — Materials and Inventory
3	Auto-patch low risk	GBS	Vulnerability Scanning Agent	gbs	15m	25m	18	Group ERP — Materials and Inventory
4	Assign owner	Agent	Threat Modeling Agent	workflow	51m	1h 2m	15	Configuration Management Database
5	Escalate critical Held for a named human when the unit exceeds the finding decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Director, Security Engineering	policy	3h 47m	5h 27m	0	Group ERP — Materials and Inventory
6	Verify	GBS	Vulnerability Scanning Agent	gbs	1h 20m	2h 29m	3	Group ERP — Materials and Inventory
7	Close	Agent	Security Engineering Orchestrator	workflow	1h 19m	3h 7m	2	Group ERP — Materials and Inventory

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. more

Move something

Demand100%

3,326 a week is what the estate records. more

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 gates360 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. more

Person time a week

12,583.4h

3,326 items at 227 minutes of decision each.

Agent time a week

17,572.4h

317 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 16.6h of headroom.

Stations without a person

86%

1 gate left on 7 stations.

Where an item spends its time

42% waiting on a person

58% in the agent lane

An item now takes 544 minutes of worked time end to end against 544 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 Vulnerability Remediation

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

How it runs

Run it again, going wrong

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

7 stations, walked twice

Once clean, once with the categories the estate counts

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

No break below was chosen. more

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

7 stations, nothing waiting, nothing sent back

0 min of 9.1 hrs

now Scan · Vulnerability Scanning Agent · 1.2 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 23 hrs

now Scan · Vulnerability Scanning Agent · 1.2 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

5 counted categories land on this procedure. more

What this run cannot claim

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

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

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

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Materials and Inventory

SAP S/4HANA MM · supply · bidirectional · high

modeled

6 of 7 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 7 stations attributed here · read only

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Security Engineering Orchestrator
That orchestrator’s remit: Owns finding work end to end inside Engineering. Runs 3 lines across 19 stations, drains the repeatable share into the IT tower, and holds 4 human gates.
Accountable person: Director, Security Engineering
Sub-function: Security Engineering
Shared spine tower: it
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Secret Exposure ResponseEN10B Threat Model ReviewEN10C

What this page is and is not

This is a catalogue of the modeled estate. more