LensReading which lens this session carries.
The catalogueResearch & DevelopmentRegulatory ScienceTransactional

Service RD8C

Compliance Testing

Runs transactional. Starts when a scheduled window opens. It runs 7,479 times a week across 5 stations. 2 of those stations stop for a person and 3 are done by an agent, 2 of them on the shared spine.

Runs a week

7,479

105 in flight right now.

Stations

5

2 person · 1 agent · 2 spine

Agent share of steps

60%

Autonomy on this service is set at 63% against a ceiling of 66%.

Decisions a person makes

2

Held by VP Regulatory Science.

Touchless

64%

Share of runs that complete without anybody opening them.

Timetable against actual

11.0h

Actual 10.6h, 0.4h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 58% of the dwellAgent1 station and 14% of the dwellShared spine2 stations and 27% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Product Lifecycle Management
Product Lifecycle Management
Product Lifecycle Management
Product Lifecycle Management
Product Lifecycle 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

Schedule

GBSRequirement Mapping Agentgbs5m6m45Product Lifecycle Management
2

Execute

AgentEvidence Assembly Agentworkflow1h 30m3h 22m19Product Lifecycle Management
3

Record

GBSRequirement Mapping Agentgbs2h 49m4h 33m29Product Lifecycle Management
4

Non-conformance escalate

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

HumanVP Regulatory Sciencepolicy1h 24m2h 50m3Product Lifecycle Management
5

Certify

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

HumanVP Regulatory Sciencepolicy4h 47m5h 49m9Product Lifecycle 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%
7,479 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates1322 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
46,245.2h
7,479 items at 371 minutes of decision each.
Agent time a week
32,907.6h
264 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 24.9h of headroom.
Stations without a person
60%
2 gates left on 5 stations.
Where an item spends its time
58% waiting on a person
42% in the agent lane
An item now takes 635 minutes of worked time end to end against 635 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 Compliance Testing

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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 11 hrs

now Schedule · Requirement Mapping Agent · 5 min

As the ledger has it

the same stations, plus 6 categories the estate already counts

0 min of 40 hrs

now Schedule · Requirement Mapping Agent · 5 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

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

1 systems attributed

0 of 1 returning records

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

5 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Regulatory Science Orchestrator
That orchestrator’s remit
Owns submission work end to end inside Research & Development. Runs 3 lines across 19 stations, drains the repeatable share into the C2L tower, and holds 6 human gates.
Accountable person
VP Regulatory Science
Sub-function
Regulatory Science
Shared spine tower
c2l
Hand-over points
None — this service stays inside its function

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.