Post-Game Analysis (PGA)

Dashboards show you the end score, “what happened?” But not the “Why”.

Introducing o9’s Innovation — Post-Game Analysis (PGA).

A Chief Supply Chain Officer story

Elite Sports Teams watch tape to learn Why?
Now your business can too.

PGA solutions

Post-Game Analysis for Every KPI

  • Forecast Accuracy PGA

    Analyze the root cause of poor forecast accuracy and bias.

  • Inventory PGA

    Answer why there is excess inventory build up or stockout.

  • Service Level PGA

    Understand root cause of the misses in Service Level performance.

We had a sense of the problem. Now we have facts at scale, clear enough to align and act fast.

Director, Supply Chain

National Premier Wine & Spirits Retailer

This is exciting. One click and we know where excess inventory sits, why it’s there, and what to do next.

Director, Supply Chain Business Process

Global Industrial Technology & Lighting Manufacturer

Inventory PGA is powerful. How quickly can we extend it across all KPIs?

VP, Supply Chain

Global Diversified Food & Beverage Enterprise

Core Capabilities

How o9 PGA Stands Apart

  • System of Record for Plans and Decisions

  • AI-Powered Root Cause Analysis

  • Enterprise-Scale Computation

  • Amazing Storytelling

  • Tribal Knowledge Capture & Digitization

  • First value delivery & Improvement in Weeks

Get PGA going in your company. It is simple. 

Sign up for an o9 Specialist to contact you.

Questions.
Clear Answers.

Getting started with your first Post Game Analysis (PGA) doesn't require perfect data; a few core files are sufficient.

While the specific inputs depend on the analysis type, they generally include your item master, historical actuals, and plan snapshots covering demand, production, or procurement. For a more in-depth Root Cause Analysis (RCA), include multiple historical plan versions to accurately trace outcome evolution.

For a complete breakdown of mandatory and optional data inputs that unlock deeper insights—organized by analysis type—please refer to the Data Requirements documentation.