Service LG9C
Breach Response
Runs transactional. Starts when an upstream system posts an event. It runs 1,669 times a week across 7 stations. 3 of those stations stop for a person and 4 are done by an agent, none of them on the shared spine.
Runs a week
1,669
117 in flight right now.
Stations
7
3 person · 4 agent · 0 spine
Agent share of steps
57%
Autonomy on this service is set at 61% against a ceiling of 70%.
Decisions a person makes
3
Held by Data Protection Officer.
Touchless
65%
Share of runs that complete without anybody opening them.
Timetable against actual
9.5h
Actual 7.5h, 2.0h under the timetable.
Operations
The lane diagram
Read it left to right. more
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 | Detect Hands over at information-technology | Agent | Data Subject Request Agent | workflow | 2h 17m | 4h 17m | 20 | Contract Lifecycle Management |
| 2 | Triage severity | Agent | Processing Register Agent | workflow | 1h 58m | 4h 2m | 11 | Document and Matter Management |
| 3 | Contain | Agent | Impact Assessment Agent | workflow | 1h 15m | 1h 43m | 28 | Contract Lifecycle Management |
| 4 | Assess notifiability Held for a named human when the unit exceeds the privacy case decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Data Protection Officer | policy | 2h 18m | 5h 9m | 7 | Contract Lifecycle Management |
| 5 | Regulator notify Held for a named human when the unit exceeds the privacy case decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Data Protection Officer | policy | 2h 30m | 5h 41m | 3 | Contract Lifecycle Management |
| 6 | Subject notify Held for a named human when the unit exceeds the privacy case decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Data Protection Officer | policy | 4h 38m | 6h 5m | 6 | Contract Lifecycle Management |
| 7 | Post-mortem | Agent | Privacy Policy Agent | workflow | 1h 56m | 2h 43m | 42 | Document and Matter 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. more
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 17 hrs
now Detect · Data Subject Request Agent · 2.3 hrs
As the ledger has it
the same stations, plus 4 categories the estate already counts
0 min of 34 hrs
now Detect · Data Subject Request Agent · 2.3 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
4 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
Attestations on this estate are written against intake items, not against procedures, so a step done off the platform cannot be matched to the attestation that covers it. 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
Contract Lifecycle Management
Icertis · legal · bidirectional · high
5 of 7 stations attributed here · would write back
Document and Matter Management
iManage · legal · inbound · medium
2 of 7 stations attributed here · read only
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Privacy Orchestrator
- That orchestrator’s remit
- Owns privacy case work end to end inside Legal. Runs 3 lines across 21 stations, drains the repeatable share into the LEGAL tower, and holds 6 human gates.
- Accountable person
- Data Protection Officer
- Sub-function
- Privacy & Data Protection
- Shared spine tower
- Not on the shared spine
- Hand-over points
- information-technology
Other services in this sub-function
2 alongside this one
What this page is and is not
This is a catalogue of the modeled estate. more