Sub-function
Engineering Analytics
Owns analysis work end to end inside Engineering. Runs 3 lines across 15 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 3 human gates.
Estate rating
BBB
74 / 100
Metric assembly and trend detection are fully agentic. Team-level metrics are deliberately never used for individual performance without a human interpreting context.
Agents
8
Lines
3
Units / wk
139
Timetable vs actual
7.1d → 7.6d
Cost / unit
$441
was $2K
Run-rate saving
$7.7M
annualized at this volume
The 8 agents running this sub-function
Grouped by what they are for, not by where they sit. The agent org is process-shaped.
Engineering Analytics Orchestrator
Owns the engineering analytics lane end to end. Sequences the other agents, holds the timetable, and decides what surfaces to a human.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Delivery Metrics Agent
Runs the repeatable portion of engineering analytics inside the shared transaction spine at spine cost and spine controls.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Reliability Trend Agent
Runs the repeatable portion of engineering analytics inside the shared transaction spine at spine cost and spine controls.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Cycle Time Agent
Executes the engineering analytics step it owns, posts its evidence, and hands the unit to the next stage.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Cost per Service Agent
Executes the engineering analytics step it owns, posts its evidence, and hands the unit to the next stage.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Team Health Agent
Watches engineering analytics continuously. Detects drift, quantifies it, and routes what matters without waiting for a reporting cycle.
ceiling A4 · escalates to Escalates to Director, Engineering Analytics when the unit falls outside the decision envelope or confidence drops below the floor.
Measurement Doctrine Agent
Authors positions on engineering analytics. Frames the question, models the options, and writes a recommendation a human can ratify or reject.
ceiling A4 · escalates to Escalates when two options sit inside the confidence band and the evidence cannot separate them.
Engineering Analytics Challenger Agent
Adversarial reviewer for engineering analytics. Argues the opposite case on every position and flags where the evidence does not carry the claim.
ceiling A4 · escalates to Escalates when a ratified position is still running against a break condition it flagged.
Estate rating breakdown
Seven control dimensions. Judgment readiness runs against autonomy on purpose.
People
What the humans stopped doing, and what they do now.
Redeployed into customer-facing escalation ownership.
Lines running in this sub-function
Each line is a workflow. Click a line to walk it station by station.
Strategy positions this sub-function holds
An agent that only executes is a robot. These are the calls it made, the argument against each one, and what would prove it wrong.
Measurement Doctrine Position
Ratifiedv3Is the current cost per analysis defensible against external comparators once inference spend is counted in full?
Hold the ceiling at A4 for engineering analytics. Metric assembly and trend detection are fully agentic. Team-level metrics are deliberately never used for individual performance without a human interpreting context. Raise it only after two consecutive quarters where the override rate stays under five percent and every override has a written cause.
confidence
86%
The challenge — Engineering Analytics Challenger Agent
Engineering Analytics Challenger Agent argues the recommendation leans on 2 quarters of data from a period with no volume shock. The confidence band overlaps the alternative, and the position does not say what it would take to be wrong. Recorded as a dissent, not a block.
Break conditions
- ·Override rate rises above 15 percent for two consecutive months
- ·Cost per analysis stops falling while volume keeps rising
- ·A control failure in this lane reaches a customer or a regulator
Evidence gaps
- ·No external comparator on a like-for-like unit definition
- ·Exception cases under $19k are sampled, not fully measured
| Alternative considered | Cost | Risk | Verdict |
|---|---|---|---|
| Hold the current position | $663k run rate | Known and priced. Cedes ground if comparators move faster. | not selected |
| Raise the ceiling one level now | $794k to build controls | Override rate is 4 percent; raising the ceiling before that settles imports the error into production. | rejected on evidence |
| Move the exception tail to the spine | $126k transition | Loses local context. Rework risk on the cases that are hardest to recover. | selected |
Ratified 3 months ago. Measured since: cost per analysis rose 3 percent against a forecast that it would fall 9 percent.
Engineering Analytics Operating Position
In challengev3Which parts of engineering analytics should deliberately stay human, and how do we defend that against a cost argument?
Keep the repeatable analysis volume in the spine and pull the exception tail back into the function. The spine is cheaper per unit; the tail is where the context that prevents rework actually sits.
confidence
65%
The challenge — Engineering Analytics Challenger Agent
Engineering Analytics Challenger Agent argues the recommendation leans on 3 quarters of data from a period with no volume shock. The confidence band overlaps the alternative, and the position does not say what it would take to be wrong. Recorded as a dissent, not a block.
Break conditions
- ·Override rate rises above 6 percent for two consecutive months
- ·Cost per analysis stops falling while volume keeps rising
- ·A comparator publishes a materially lower unit cost on a like-for-like basis
Evidence gaps
- ·No external comparator on a like-for-like unit definition
- ·Exception cases under $28k are sampled, not fully measured
| Alternative considered | Cost | Risk | Verdict |
|---|---|---|---|
| Hold the current position | $312k run rate | Known and priced. Cedes ground if comparators move faster. | live |
| Raise the ceiling one level now | $917k to build controls | Override rate is 8 percent; raising the ceiling before that settles imports the error into production. | rejected on evidence |
| Move the exception tail to the spine | $520k transition | Loses local context. Rework risk on the cases that are hardest to recover. | under review |
Policy register
The rules the agents above are bound by. Version, owner, approver, and the agents each rule constrains.
| Ref | Rule | Scope | Owner agent | Approved by | Version | Status |
|---|---|---|---|---|---|---|
| EN11-POL-200 | Engineering Analytics Decision Envelope Agents in this lane may act without a human when the analysis sits inside the stated value, risk and confidence envelope. Outside it, the unit holds at a gate with a named approver and a running clock. binds 4 agents · Global | envelope | Engineering Analytics Orchestrator | Director, Engineering Analytics | v1.4 | Active |
| EN11-POL-201 | Engineering Analytics Evidence Standard Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. An action with no evidence record is treated as a control failure, not a fast decision. binds 4 agents · US · Canada | evidence | Engineering Analytics Orchestrator | Director, Engineering Analytics | v3.4 | under review |
| EN11-POL-202 | Engineering Analytics Escalation Rule Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires. Director, Engineering Analytics owns the response clock. binds 4 agents · APAC | escalation | Engineering Analytics Orchestrator | Director, Engineering Analytics | v4.3 | Active |
| EN11-POL-203 | Engineering Analytics Autonomy Ceiling The ceiling for this lane is 88 on the platform scale. Metric assembly and trend detection are fully agentic. Team-level metrics are deliberately never used for individual performance without a human interpreting context. The ceiling is a governance decision, not a technical limit, and only Director, Engineering Analytics can propose moving it. binds 4 agents · Global | ceiling | Engineering Analytics Orchestrator | Director, Engineering Analytics | v5.6 | Active |