LensReading which lens this session carries.

Standard operating procedure · RD8A · Research & Development

Regulatory Submission

Transactional procedure owned by Regulatory Science in Research & Development. 8 numbered steps, 3 of them a person deciding and 5 of them agent work …

Procedure code

RD8A

Transactional

Rule versions in force

v3.3 · v1.4

2 governing rules stacked over it

In force since

2024-09-29

Earliest effective date across those rules

Last reviewed

2026-07-19

Latest review date across those rules

Rules approved by

1

VP Regulatory Science

Rule health

2/2

0 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run regulatory submission to one repeatable standard inside Regulatory Science, part of Research & Development.

Entry condition

Runs transactional. Starts when a scheduled window opens.

Exit condition

The unit clears track.

In scope

  • Every unit of regulatory submission raised inside Regulatory Science, from the trigger below through to the final step.
  • 5 of the 8 steps, which run without a person present.
  • 3 decisions that stop the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line hands off to legal and does not follow the unit there.
  • The 2 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Regulatory Science Orchestrator

Accountable person

VP Regulatory Science

The end of the escalation path. Above them sits R&D Chief of Staff for the function.

That team’s remit

Owns submission work end to end inside Research & Development.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

63% now · ceiling 66%

Requirement mapping and evidence assembly are agentic at scale.

The procedure, step by step

8 numbered steps · 3 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Map requirements

GBSgbs

Requirement Mapping Agent

Requirement Mapping Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management21 minstandard 41 min5
02

Assemble evidence

GBSgbs

Requirement Mapping Agent

Requirement Mapping Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.8 hrsstandard 4.3 hrs38
03

Draft dossier

Agentworkflow

Submission Drafting Agent

Submission Drafting Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management15 minstandard 36 min1
04

Scientist review

HumanpolicyDecision

VP Regulatory Science

Releases: VP Regulatory Science

Work stops. VP Regulatory Science reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: 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.Product Lifecycle Management5.9 hrsstandard 8.1 hrs2
05

Counsel review

HumanpolicyDecision

VP Regulatory Science

Releases: VP Regulatory Science

Work stops. VP Regulatory Science reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: 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.Hands off to legalProduct Lifecycle Management3.7 hrsstandard 8.7 hrs5
06

Officer sign

HumanpolicyDecision

VP Regulatory Science

Releases: VP Regulatory Science

Work stops. VP Regulatory Science reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: 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.Product Lifecycle Management1.8 hrsstandard 3.5 hrs5
07

Submit

Agentworkflow

Regulatory Science Orchestrator

Regulatory Science Orchestrator performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Research Notebook and Experiment Data14 minstandard 27 min27
08

Track

Agentworkflow

Requirement Mapping Agent

Requirement Mapping Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.1 hrsstandard 4.8 hrs24

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person3 stations and 66% of the dwellAgent3 stations and 15% of the dwellShared spine2 stations and 18% 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
Product Lifecycle Management
Research Notebook and Experiment Data
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.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/8
the happy path, worked time0 min of 17 hrs
the same run against its allowance0 min of 31 hrs
Human
decides · 3
Agent
does the work · 3
GBS
shared spine · 2
run log

Nothing has happened yet.

where the worked time goes17 hrs a unit
Person11 hrs · 66%Agent2.6 hrs · 15%Shared spine3.1 hrs · 18%3 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 3 of the 8 stations stop for a person and every one of them still does on this run.
  • Every one of the 3 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 66% autonomy ceiling and this run sits at 34% unattended, inside it.
  • 2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

1 of the 3 decisions can be handed over inside the 66% ceiling.

could move to the agent lane
  • 05 Counsel review — held by VP Regulatory Science, 3.7 hrs a unit
stays with a person
  • 04 Scientist review — Handing this over would put 100% of the worked time in the unattended lane, past the 66% ceiling this team is held to.
  • 06 Officer sign — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

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

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

8 stations, nothing waiting, nothing sent back

0 min of 17 hrs

now Map requirements · Requirement Mapping Agent · 21 min

As the ledger has it

the same stations, plus 7 categories the estate already counts

0 min of 47 hrs

now Map requirements · Requirement Mapping Agent · 21 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

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

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.

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

Roles and responsibilities

5 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Regulatory Science Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to VP Regulatory Science when a unit falls outside the envelope or confidence drops below the floor.

Requirement Mapping Agent

agent

A2% autonomy · ceiling A2%

91% clean · 2% overridden

Responsible3Runs the repeatable portion of regulatory science inside the shared transaction spine at spine cost and spine controls.Escalates to VP Regulatory Science when the unit falls outside the decision envelope or confidence drops below the floor.

Submission Drafting Agent

agent

A2% autonomy · ceiling A2%

90% clean · 4% overridden

Responsible1Executes the regulatory science step it owns, posts its evidence, and hands the unit to the next stage.Escalates to VP Regulatory Science when the unit falls outside the decision envelope or confidence drops below the floor.

VP Regulatory Science

person

Accountable and responsible3Holds 3 decisions on this line. Accountable to VP Regulatory Science for the decisions held here.

Regulatory Science Orchestrator

agent

A2% autonomy · ceiling A2%

90% clean · 9% overridden

Responsible1Owns the regulatory science lane end to end. Escalates to VP Regulatory Science when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

3 places this procedure stops

04 · Scientist review

5.9 hrs

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.

VP Regulatory Science

05 · Counsel review

3.7 hrs

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.

VP Regulatory Science

06 · Officer sign

1.8 hrs

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.

VP Regulatory Science

Handoffs out of this procedure

Step 05 Counsel review passes the work to legal.

The rules this procedure runs inside

2 governing rules

Regulatory Science Decision Envelope

active

RD8-POL-200 · envelope · vv3.3

Agents in this lane may act without a human when the submission sits inside the stated value, risk and confidence envelope.

Approved by VP Regulatory Science · in force 2024-09-29 · reviewed 2026-05-19

Binds Requirement Mapping Agent, Evidence Assembly Agent, Submission Drafting Agent, Testing Coordination Agent

APAC

Regulatory Science Evidence Standard

active

RD8-POL-201 · evidence · vv1.4

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by VP Regulatory Science · in force 2025-07-16 · reviewed 2026-07-19

Binds Requirement Mapping Agent, Evidence Assembly Agent, Submission Drafting Agent, Testing Coordination Agent

LATAM · US

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Product Lifecycle ManagementSiemens Teamcenterengineeringhigh7modeled
Research Notebook and Experiment DataBenchlingengineeringmedium1not-connected

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 0 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

17.1 hrs

Summed from the time each step sits, standard 31.1 hrs — running at 55% of the standard.

Touchless

64%

Agent share

63%

A week

7,459

In flight

107

Effort a week

680 human minutes · 343 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Physical experiment authorization

approval

Any laboratory experiment involving materials, equipment or subjectsPrincipal investigator and safety officer2 business daysNo

External data acquisition

approval

Any new external dataset, license or third-party evidence sourceResearch governance and Legal3 business daysNo

Publication or external disclosure

approval

Any material leaving the research boundary, including conference abstractsCSO and General Counsel5 business daysNo

Reproduction sampling

oversight

Independent re-derivation of 15% of reported internal resultsReproducibility boardMonthlyNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.