Brewing Operations Reliability Assessment (BORA)

Overview

Brewing Operations Reliability Assessment (BORA) is a collection of operational metrics used to evaluate the health, effectiveness, and reliability of a brewing operation.

While Service Level Indicators (SLIs) and Service Level Objectives (SLOs) focus on the performance of individual batches, BORA focuses on the performance of the brewing process itself.

SLIs answer questions such as:

Did this beer perform as expected?

BORA answers questions such as:

Is this brewery improving over time?

The purpose of BORA is to provide visibility into brewing operations and establish measurable indicators for continuous improvement.

⸻

Why BORA Exists

A brewery can consistently produce great beer while operating inefficiently.

Likewise, a brewery can operate efficiently while producing inconsistent beer.

Both outcomes matter.

BevOps views brewing as a system.

Recipes, processes, equipment, documentation, and feedback all contribute to the success of that system.

BORA provides a way to evaluate the effectiveness of those operational practices.

⸻

What Makes a Good BORA Metric?

A useful BORA metric should:

  • Be measurable
  • Encourage improvement
  • Support decision-making
  • Provide operational insight
  • Remain simple enough to maintain

Not every metric needs to be tracked.

The objective is to identify the metrics that best reflect the health of the brewing operation.

⸻

Core BORA Metrics

The following metrics form the foundation of Brewing Operations Reliability Assessment.

⸻

Deployment Frequency

Purpose

Measure how often beer is brewed.

Frequent brewing creates more opportunities for learning, experimentation, and improvement.

Example

3 batches/month

Questions Answered

  • Are we actively brewing?
  • Are ideas becoming beer?
  • Are we generating opportunities to learn?

⸻

Lead Time for Changes

Purpose

Measure how long it takes for an idea to become a finished beer.

Lead Time begins when an idea is identified and ends when the resulting beer is ready for evaluation.

Example

Idea: May 1 First Taste: June 1 Lead Time = 31 Days

Questions Answered

  • How quickly can we test new ideas?
  • How long does experimentation take?
  • Are we reducing delays in the brewing process?

⸻

Change Failure Rate

Purpose

Measure the percentage of recipe or process changes that fail to achieve their intended outcome.

Not every experiment will succeed.

That is expected.

The objective is to understand how effectively changes translate into improvements.

Example

Recipe Changes Introduced: 10 Successful Changes: 8 Failed Changes: 2 Change Failure Rate = 20%

Questions Answered

  • Are experiments producing meaningful improvements?
  • Are changes helping or hurting?
  • Are we learning from failures?

⸻

Mean Time To Recovery (MTTR)

Purpose

Measure how quickly the brewery recovers from incidents.

Examples include:

  • Stalled fermentation
  • Equipment failures
  • Contamination
  • Packaging issues
  • Process failures

Example

Failed Batch: June 1 Replacement Batch Brewed: June 8 MTTR = 7 Days

Questions Answered

  • How resilient is the brewing operation?
  • How quickly can issues be corrected?
  • How disruptive are failures?

⸻

Recipe Health Metrics

These metrics help evaluate the maturity and stability of recipes.

⸻

Recipe Stability Index (RSI)

Purpose

Measure how frequently a recipe changes.

Some recipes are still evolving.

Others have reached a mature and stable state.

RSI helps identify which recipes are still under active development.

Example

Trailhead Wit v1.0.0 v1.1.0 v1.2.0 v1.2.1 4 Changes in 12 Months

Questions Answered

  • Is this recipe stable?
  • Is this recipe still evolving?
  • Should future changes be introduced carefully?

⸻

Rebrew Rate

Purpose

Measure how frequently a recipe is brewed again.

A recipe that is repeatedly brewed often indicates a successful release.

Example

El Pescador Brewed: 6 Times Rebrew Rate: High

Questions Answered

  • Which recipes are most successful?
  • Which recipes justify continued investment?
  • Which recipes have become brewery staples?

⸻

Operational Metrics

These metrics evaluate the consistency of brewing operations.

⸻

Operational Consistency Score

Purpose

Measure how consistently brewing targets are achieved.

Consistency is one of the primary goals of operational excellence.

Example

Target Metrics: 10 Met Metrics: 9 Operational Consistency Score = 90%

Example metrics may include:

  • Original Gravity
  • Final Gravity
  • Fermentation Temperature
  • Carbonation
  • Yield

Questions Answered

  • Are processes repeatable?
  • Are targets consistently achieved?
  • Is operational reliability improving?

⸻

Documentation Coverage

Purpose

Measure how completely brewing activities are documented.

Undocumented processes create operational risk and make future troubleshooting more difficult.

Example

Batches Brewed: 20 Fully Documented: 18 Documentation Coverage = 90%

Required documentation may include:

  • Recipe
  • Brew Log
  • Release Notes
  • Batch Review
  • Incident Reports

Questions Answered

  • Can batches be reproduced?
  • Is operational knowledge being preserved?
  • Is documentation becoming technical debt?

⸻

Human Metrics

Not everything important can be measured by gravity readings and fermentation curves.

Some of the most valuable indicators are subjective.

⸻

Beer Satisfaction Score (BSS)

Purpose

Measure overall satisfaction with a beer.

A beer may achieve every target and still fail to inspire a brewer to make it again.

Example Scale

1 = Never Again 2 = Needs Significant Improvement 3 = Worth Revisiting 4 = Strong Candidate for Rebrew 5 = Immediate Rebrew

Questions Answered

  • Was the beer enjoyable?
  • Did the beer meet expectations?
  • Would it be brewed again?

⸻

Enjoyment Rate

Purpose

Measure how frequently beer is shared and enjoyed with others.

Beer exists to be consumed and enjoyed.

No amount of documentation, telemetry, or dashboards should distract from that purpose.

Example

Batches Brewed: 10 Shared Batches: 8 Enjoyment Rate = 80%

Questions Answered

  • Are beers being shared?
  • Are people enjoying the results?
  • Is the brewery fulfilling its purpose?

⸻

Choosing BORA Metrics

Not every brewery will track every metric.

A commercial brewery may focus heavily on consistency, throughput, and yield.

A homebrewer may focus on experimentation, learning, and enjoyment.

BevOps encourages brewers to select metrics that align with their goals while maintaining enough visibility to support continuous improvement.

⸻

The Goal of BORA

The purpose of BORA is not to create more dashboards.

The purpose of BORA is to understand whether a brewing operation is improving over time.

A healthy brewery should:

  • Learn from mistakes
  • Repeat successes
  • Preserve knowledge
  • Encourage experimentation
  • Deliver enjoyable beer

SLIs measure the health of a batch.

BORA measures the health of the brewery.

Together they provide a complete picture of operational performance.

Brew → Measure → Learn → Improve