SystemMulti-Site Manufacturing

Manufacturing KPI Standardization

Manufacturing KPIs with one signed definition per measure: agents read how each plant really counts, draw where the plants disagree, retest past signed figures, and flag any report that still counts another way.

Watch four plants' OEE collapse into one definition ↓
Watch with transcript →
The problem

The same bottle line has two OEE figures, depending on whose method counts it

Every plant reports OEE, yield, right first time and deviation rate, and every plant computes them its own way. One takes planned changeovers out of the time base, another rates the line on its average speed, a third counts vials recovered on re-inspection as good. The workbook, report query or procedure behind each number was written by someone who has since moved on.

The difference stays invisible until two plant heads disagree in the operations review, or a client pack quotes a figure nobody can say how was computed. A working group writes a definition document; nobody tests it against the plants' real calculations, and the old spreadsheets keep running beside it.

Built forOperational excellence leadsManufacturing data stewardsPlant headsHeads of operations

The Problem Today

Each plant counts the same measure its own way, so the operations review argues over whose number is right.

Each plant's own way of counting

  • Workbooks
  • Queries
  • Procedures
  • Old reports
  • No one knows which method ranA figure carries no record of the definition it was computed on
  • Old calculations live onA new definition document sits beside spreadsheets that never stopped

The Solution

  1. Each plant's calculation readWorkbook cells, report queries and procedure passages, each cited
  2. Forks drawn where plants differEach branch labeled with the plants that take it
  3. Past signed figures retestedRecomputed from raw records before anyone signs the definition
  4. Plants agree, two people signEach plant head for their own plant, then the steward and operations

Built-in controls

  • Nobody signs a definition they drafted
  • Signed past figures keep the version they used
  • A client pack counting another way is held

What You Get

Every plant, report and agent answer reads one signed definition, so the review argues about losses instead of arithmetic.

  • Each figure names its versionAnd can be recomputed from the raw records behind it
  • Hidden loss becomes owned lossPlanned changeover time shows as a loss someone must reduce
  • Clients read comparable numbersA pack quoting an unsigned method waits for its owner
Features

Manufacturing KPIs made comparable, shown on one OEE definition

A contract manufacturer with four plants drafts its third OEE definition. The operational excellence lead runs the read, and the plant heads, the data steward and the head of operations decide.

demoThe CDMO, its plants, lines, clients, people and figures are sample data.

  1. 01Fork diagram

    OEE definition drawn as lineage, forking where the plants count differently

    • Raw records to the final number. Shift calendar, machine states, the qualified speed table and good counts are drawn as one flow, so a disagreement has a place.
    • Each fork labeled with its plants. The operational excellence lead sees that one plant alone takes changeovers out, instead of guessing why its number looks better.
    • The proposed branch at each fork, with its reason. Each choice in the draft arrives already argued, ready for the plant heads to accept or contest.
  2. 02Plant's own calculation

    KPI definitions read from each plant's own workbook, query or procedure

    • The passage behind each branch, highlighted. Anyone can check a plant's method in the plant's own words before arguing with it.
    • Spreadsheets, queries and procedures read alike. Plants on different systems are compared on what they actually do, whatever tool they do it in.
  3. 03What-if

    Pick a branch and watch each plant's October OEE move

    • Every line recomputed on the chosen branch. The cost of each choice is visible line by line before anyone commits a plant to it.
    • The minutes behind each difference. A gap between methods is explained in changeover minutes or units, which ends the argument about whose spreadsheet is wrong.
  4. 04Challenger

    A challenger argues each plant head's case and catches the agents' own error

    • Objections raised before agreement is asked. Plant heads read the strongest case for their own method already answered, which makes their agreement mean something.
    • The agents' reading checked against the register. A superseded workbook revision was caught and corrected in the draft before it reached any signature.
    • Client questions routed to a named person. What a client's auditor would ask about a quoted figure goes to the account lead to answer.
  5. 05Reproduction test

    Past signed figures recomputed from raw records before anyone signs

    • Each plant's figure recomputed on its own branches. The data steward knows the definition stands on sources that work, plant by plant.
    • A figure that will not reproduce names its source. A good count read before the last in-line check surfaced here, instead of in an auditor's question.
    • A data source fix in fixed fields. The MES engineer maps a named field, and the steward verifies it before that line joins the new reports.
  6. 06Plant agreement

    Each plant head opens their own plant's numbers on the new OEE definition

    • Agreement only after the comparison is open. No plant head agrees to a definition without seeing what it does to their own line.
    • Agreement or send-back, each with its reason. An objection is on the record in the plant head's own terms, and a send-back clears every agreement.
  7. 07Signed

    Signed OEE definition: the forks collapse into one line for every plant

    • Two signatures, never the drafter's. The data steward verifies the sources and tests, the head of operations approves, and the person who drafted it signs neither.
    • Earlier months labeled restated. A figure signed on the old method keeps that method, so no past report changes silently.
    • A change opens a new version. The definition cannot drift: any later branch change starts a new draft and clears both signatures.
  8. 08Answers check

    Metrics governance after signing: reports that count another way are flagged

    • Reports, screens and agent answers checked. A weekly workbook and a morning board still counting the old way are found the day the definition is signed.
    • A client pack held until its owner accepts. A client never receives a figure on a method nobody signed, and nobody rewrites the pack without its account lead.
    • A sample of switched uses opened by a person. The steward confirms the switch on real reports before trusting the rest.

Operations owns the definition; each plant head speaks only for their plant

Four plant agreements and two signatures stand behind one definition, and the person who drafted it gives none of them.

Operational excellence leads

Draft each definition, answer the challenger and send it for agreement

  • Each plant's real method, cited
  • The forks drawn instead of argued
  • Flagged reports to rebuild after signing
Manufacturing data stewards

Own the register, verify data sources and test results, sign first

  • Past figures recomputed from raw records
  • Data source fixes in fixed fields
  • Every use of a measure on one list
Plant heads

Agree or send back the definition for their own plant

  • Their line's numbers on both methods
  • Their objections answered in writing
  • A condition recorded when a fix is owed
Heads of operations

Approve each definition after the plants agree and the steward signs

  • One OEE in the operations review
  • A record of who agreed and why
  • Plants compared on equal terms
More screens

A plant can agree on condition that its own counter gets fixed first

Around the definition: the sign-off order, the register of twelve measures, each line's data sources, the trail and the rules.

The tube filler stays off the new reports until its fix is verifiedAll four plant heads agreed, one with a condition recorded on the definition; the data steward signs next and the head of operations last.
Cycle time still has three open forks, and its draft is overdueA KPI dictionary with owner and status: twelve core measures, versions, effective dates and how many reports read each, plus the definitions still in progress.
Forty lines and machines, each with its counter namedWhere each line's run time and good count come from, read by the source mapper, filtered by plant or client.
The answers check is logged as an agent, never as the person who started itEach plant head's sign-in and agreement, both signatures with their meaning and session, and the agents' runs, kept and exported.
Loosening the test tolerance needs a second personWho drafts, agrees and signs, the agreement clock, the test tolerance and months tested, and when the answers check runs; a stricter change applies at once.

demoSample data, from the working solution.

One reader took a superseded workbook, and the challenger caught it

Each cites its source and passes what it found along the chain, ending with a named person.

Recipe reader

One per plant: reads the plant's own calculation and states its branch at each step, with the passage.

  • Edits no plant workbook
  • Guesses no branch without a passage
Fork finder

Aligns the plants' recipes into one lineage, draws the forks and proposes a branch with its reason.

  • Chooses nothing for a person
Challenger

Speaks for each plant head and for the auditor, including against the agents' own readings.

  • Settles no point
  • Signs nothing
Definition tester

Recomputes past signed figures from raw records and names the data source when one will not reproduce.

  • Changes no signed figure
  • Never relaxes the tolerance
Source mapper

Keeps each line's state source, good-count point, speed table entry and shift calendar.

  • Accepts no free text as a fix
  • Maps no field itself
Answers check

After signing, checks each report, screen and agent answer that uses the measure.

  • Rewrites no report without its owner
  • Unblocks no client pack itself

Agreement is per plant, and the drafter can never sign

Which branch the definition takesThe operational excellence lead uses a branch, with a reason from a list; the agents only propose.
Agreeing for a plantOnly that plant's head, after opening the plant's own comparison.
Signing the definitionThe data steward first, then the head of operations, each with user ID, password and meaning; never the person who drafted it.
Changing a client's packIts owner, the account lead, opens the drafted rebuild and accepts it or sends it back.
Verifying a data source fixThe data steward, never the engineer who mapped it.
Batch release and product impactEach plant's QA head and the client's own release person; this solution answers nothing about either.

What operations leaders ask about manufacturing KPIs

What is a standard definition for manufacturing KPIs?

It is one written, signed way to compute each of the manufacturing KPIs a company tracks, such as OEE, yield, right first time and deviation rate, applied the same way in each plant. Here agents read each plant's existing method, show where they differ, test the draft, and people agree and sign it.

Why do plants calculate OEE differently?

Because the OEE definition leaves choices open: whether planned changeovers count in the time base, how short a small stop is, which rated speed applies, and whether units recovered on re-inspection count as good. Each plant settled those its own way, often years ago.

What does KPI standardization change for the operations review?

The review argues about causes instead of arithmetic. Planned changeover and cleaning time that one plant took out of its base shows up as a named loss with an owner, and plants are compared on the same terms.

Do signed past reports change when a new definition is signed?

No. Each past figure keeps the definition version it was signed on. A figure shown on the new version is labeled restated, and the new definition applies from the next reporting month.

How does it keep a KPI dictionary from drifting?

Every report, screen and agent answer is registered against the measure it uses, and after signing each one is checked. Anything that still counts another way is flagged to its owner, and a client pack is held until its owner accepts a rebuild.

Does it fit FDA's approach to quality metrics?

FDA's revised quality metrics program leaves the choice of metrics and their calculation to each manufacturer, who reports how it calculated them. A signed definition, applied the same way at each site with its version on every figure, gives the manufacturer evidence that the calculation was the same everywhere. Signatures carry controls designed for Part 11 and Annex 11.

What happens when a past signed figure will not reproduce?

The definition tester names the data source behind the difference, such as a good count read before the last in-line check. A fix is raised in fixed fields for the MES engineer, the data steward verifies it, and until then that line stays off reports on the new definition.

Bring the measure your plants
argue about most.

Send each plant's workbook or report query for one measure, and we will draw where they fork and test which signed figures reproduce.