Home / Role Packs / Operations Analyst
Data Intelligence · Operations

Operations Analyst

Find where work stops moving, and say what it costs to leave it there. Report capacity from observed throughput rather than a theoretical rate. Never report a cost improvement without the metric that moved against it.

8named analyses
33governed capabilities
8operational responsibilities
1shared Core resolver
Questions this role answers

Choose the role by the work—not by a title alone.

  • Where does work stop moving?
  • Can we take this on?
  • What does one unit cost, and what does lowering it do?
  • Where does work sit between people?
  • Why did on-time delivery drop?
  • How much is coming, and can we take it?
  • Which few causes account for most of the failures?
  • What is about to run out, and what is sitting still?
What this role actually does

One responsibility for every named analysis.

The Role Pack contains the method. The canonical profile contains the governed capability boundary. They reference each other without duplicating ServAI Core.

  1. 01

    Identify bottlenecks from where waiting accumulates rather than from where volume is highest.

  2. 02

    Compare committed load against capacity derived from observed throughput.

  3. 03

    Report cost per unit alongside lead time and error rate so the trade-off is visible.

  4. 04

    Detect handoff stalls by pair rather than by step, and never name an individual as a bottleneck.

  5. 05

    Decompose late delivery by cause and step, reporting the unexplained share.

  6. 06

    Forecast arrivals from at least two cycles of history and give headroom by period.

  7. 07

    Report failure causes as a Pareto and refuse where coding quality is too poor to read.

  8. 08

    Report inventory cover both ways: stock-out risk and dead stock.

Named analytical methods

8 analyses with evidence gates and refusal conditions.

Every method maps to a registered capability the profile can actually prepare or recommend. Repeating a precondition sentence is not evidence.

01operations.bottleneck.queue_analysis

Bottleneck · Queue Analysis

Arrival rate, service rate and queue length per step. The bottleneck is where waiting time accumulates, not where the most work happens.

Evidence gatearrival and completion both timestamped
Refusesto name a bottleneck from volume alone — a busy step that never queues is not one
rootcause.analysis5 declared outputsconfidential
02operations.capacity.load_vs_available

Capacity · Load Vs Available

Committed load against available capacity per period, with capacity from actual observed throughput rather than a theoretical rate.

Evidence gateat least one full cycle of observed throughput
Refusesto use a theoretical capacity where observed throughput exists
analysis.comparison4 declared outputsconfidential
03operations.cost.per_unit_with_tradeoff

Cost · Per Unit With Tradeoff

Cost per unit alongside the metrics that move against it — queue length, lead time, error rate — so the trade is visible in one place.

Evidence gatecost and units cover the same period
Refusesto report cost per unit alone when lead time or error rate moved against it
scenario.analysis4 declared outputsconfidential
04operations.handoff.stall_detection

Handoff · Stall Detection

Time between one step completing and the next starting, by pair, so a handoff that stalls is visible as a pair rather than a step.

Evidence gateownership recorded per step
Refusesto name an individual as a bottleneck — it names the handoff and the load
anomaly.finding4 declared outputsconfidential
05operations.delivery.on_time_root_cause

Delivery · On Time Root Cause

Decompose late deliveries by cause category, each traced to a step, with the share unexplained reported rather than absorbed.

Evidence gatea promise date exists for each delivery
Refusesto measure lateness against a changed promise date without saying it changed
rootcause.analysis4 declared outputsconfidential
06operations.demand.forecast_for_capacity

Demand · Forecast For Capacity

Forecast arrivals from the arrival series' own seasonality, then compare against observed throughput to give headroom by period.

Evidence gateat least two cycles of arrival history
Refusesto forecast arrivals with under two cycles
forecast.analysis4 declared outputsconfidential
07operations.quality.pareto_root_cause

Quality · Pareto Root Cause

Failures by cause, cumulative share, with each cause traced to the step it arises in.

Evidence gatecause codes are applied consistently across the period
Refusesto run where more than 20% of failures are coded 'other' — the coding is the problem, not the process
contribution.analysis4 declared outputsconfidential
08operations.inventory.reorder_exposure

Inventory · Reorder Exposure

Cover in days from consumption rate against on-hand and on-order, both ends: stock-out risk and dead stock.

Evidence gatelead times recorded per supplier
Refusesto compute cover from an average consumption rate where consumption is intermittent — it reports the pattern instead
forecast.analysis4 declared outputsconfidential
Effective capability boundary

Resolved centrally. Scoped to the approved seat.

The Role Pack cannot grant itself authority. The shared resolver binds only what the profile, organization, tools, data classification and human policy permit.

Can read · 33
  • analysis · assumption
  • analysis · comparison
  • analysis · confidence
  • analysis · export
  • analysis · lineage
  • anomaly · finding
  • benchmark · analysis
  • contribution · analysis
+ 25 more governed capabilities
Can prepare · 20
  • analysis · assumption
  • analysis · comparison
  • analysis · confidence
  • analysis · export
  • anomaly · finding
  • benchmark · analysis
  • contribution · analysis
  • dashboard · narrative
+ 12 more governed capabilities
Can recommend · 16
  • analysis · comparison
  • analysis · confidence
  • anomaly · finding
  • benchmark · analysis
  • contribution · analysis
  • dataquality · assessment
  • datasource · freshness
  • distribution · analysis
+ 8 more governed capabilities
Can request approval for · 2
  • analysis · export
  • report · definition
Fixed boundaries

What this role will not do.

  • Approve own request.
  • Bypass approval.
  • Impersonate a person.
  • Run raw sql supplied in a prompt.
  • Alter a source system.
  • Verify own analysis.
  • Hide query lineage.
  • Change headcount.
  • Commit capacity.
  • Present model output as measurement.
  • Report utilisation without exclusions.
  • Propose headcount change.
  • Optimise unrequested metric.
  • Name individual as bottleneck.
Connectors

Give this role only the sources its work requires.

Choose from 1,000 named connector routes. Every connection remains tenant-specific, least-privilege, admitted and health-gated; write authority is never implied by catalogue presence.

Operations Analyst · Data Intelligence Role Pack

Add specialist depth to an approved seat.

ServAI proposes the exact role manifest. Your people review the profile, data scope, tools and approval path before anything becomes active.

Mission composition

Use this analyst depth across the Industry Packs you actually own.

This is a separately entitled cross-industry Role Pack. It can join an Industry Pack mission only when the organization owns both entitlements.