Fill your Control Room with your own numbers.

Twenty-five questions in seven steps, about 10 minutes. Rough numbers from memory are fine. Each answer lands in a live Control Room as you type. You finish with a control score out of 39, the dollars at stake, the models that would fix it, and a PDF report to keep. It all runs in your browser. Nothing is sent to us.

Just looking? Load a sample:

Step 1 of 7: Your business

Q1

What kind of operation do you run?

Sets the language, the loss categories and who owns what in your Control Room.

Feeds: Header, loss categories, owners
Q2

How big is the business?

Size decides which install fits: one model, or the whole Control Room.

Employees
Sites
Feeds: Install scope, licence
Q3

Roughly what is your annual revenue, and the company name?

Optional. Revenue lets you test the dollars at stake against the 1–3% leakage band we use on every diagnostic.

Feeds: $ at stake, Operational Health Score
Q4

What is your role?

The report is written for the person who will read it.

Feeds: Report framing
Q5

What runs the business today, and how many spreadsheets does a weekly number pass through?

Tells us what we map from on day one, and how fragile the current path is.

Main system
Spreadsheets in the chain
Feeds: Data refresh, Governance

Step 2 of 7: Output & capacity

Q6

Last week, how many units did you plan to produce, and how many did you actually get out?

The single number every Control Room opens on.

units
units
Feeds: Output vs plan (A01 Production Tracker, E01)
Q7

How many hours a week is the operation scheduled to run, and what could it put out in that time at full rated speed?

If you are not sure of the rated number, leave it blank and we will estimate it. Not knowing true capacity is itself a finding.

h
units
Feeds: OEE availability and performance (A02 OEE Calculator)
Q8

Of those hours, roughly how many were lost to unplanned stoppages last week?

Your best guess. In an install this comes from the downtime log, not memory. The gap between the two is usually a finding in itself.

h
Feeds: OEE availability (A03 Downtime Register)
Q9

Where did your answer to the output question come from?

If someone had to go and pull it together, there is no daily truth yet.

Feeds: Daily truth (E01 Daily Operations)

Step 3 of 7: Where it’s lost

Q10

What share of output has to be redone or written off?

Quality loss is capacity you paid for twice: the third term in OEE.

%
Is that loss tracked in dollars?
Feeds: OEE quality (A04 Quality & Defect Log)
Q11

Where do the lost hours go? Tap the causes in order, biggest first. Then, how is downtime recorded?

Most teams can name the top cause. Very few can say what it costs.

Causes, biggest first
How is it recorded?
Feeds: Downtime Pareto (A03, C02 Pareto)
Q12

Right now, what limits you from doing more, and is that measured or a feeling?

If the constraint is assumed, improvement money usually lands on the loudest problem, not the largest.

Feeds: Bottleneck clarity (B06 Throughput & Bottleneck)

Step 4 of 7: Economics

Q13

What did you budget this year: selling price and cost per unit?

The opening bar of your margin bridge. Planned volume does the rest.

Feeds: Margin bridge, budget GM (E02 GM Control Room)
Q14

And what are you actually getting, and paying, per unit right now? How sure are you of that cost?

If the cost is an informed estimate rather than measured, that is the cost-to-produce conversation.

That cost is…
Feeds: GM % and the price, volume, cost bridge (B02, E02)
Q15

What margin should nothing fall below, and how many products or services do you sell?

Your floor. Anything under it turns red and gets an owner. Most businesses set 25–35%.

%
Products / SKUs
Feeds: Below-floor flag (E02)
Q16

Do you know your margin by customer?

Revenue by customer is easy. Profit by customer is where the surprises are.

Feeds: Customer economics (B07 Pricing & Margin)

Step 5 of 7: Customers & planning

Q17

Out of your last 100 customer orders or jobs, how many were delivered on time and in full?

If the honest answer is “we’d hear about it if it didn’t”, that is the answer.

of 100
How do you know?
Feeds: OTIF (A06 OTIF Order Fulfilment Tracker)
Q18

How do you forecast the next three months?

A static budget is out of date by the first month-end.

Feeds: Forecast discipline (B03 Demand Forecast)

Step 6 of 7: How you run it

Q19

How does leadership see these numbers today, and how many hours a week go into building the report?

Cadence decides whether a number arrives in time to act on.

h
Feeds: Refresh cadence (E01, E03, E05)
Q20

When a number goes red, what usually happens next?

The difference between a dashboard and a control system is this answer.

Feeds: Issue register owners (E03 Weekly Ops Review)
Q21

Does everyone agree how your KPIs are calculated?

Two reports, two answers, one meeting lost arguing about definitions.

Feeds: KPI definitions, data dictionary
Q22

How does the report get built, and is it clear which file is the latest?

Copy-paste pipelines break quietly. Governance is what makes a number safe to act on.

The report is…
The latest file is…
Feeds: Data refresh, governance pack
Q23

When you fix something, do you track what it saved in dollars?

Improvements that are not monetised do not get funded twice.

Feeds: ROI tracking (C06 Cost Savings Tracker)

Step 7 of 7: What you want

Q24

What would make the biggest difference in the next 90 days? Pick up to two.

This decides which model goes first in your report.

Feeds: Recommended starting point
Q25

When would you want this fixed, and how would you rather do it?

Your answers only shape the recommendation. Nothing is sent to us.

Timing
Approach
Feeds: Recommended option
Your Control Room Industry — Control —/39 0 / 25 answered

vs Plan

—

awaiting Q6

OEE

—

awaiting Q6–8

GM %

—

awaiting Q14

OTIF

—

awaiting Q17

At stake

—

builds as you go

Gross margin bridge: budget to actual, last week

Awaiting Q6, Q13, Q14

Price, volume and cost reconcile to actual

Downtime Pareto: lost hours by cause

Awaiting Q8, Q11
PendingThe issue register writes itself from your answers, ranked by status then dollars, with an owner on every line.—
LA-OPS-E-E02, built from your answers, not yet reconciled Next action: answer Q1

Same governed layout as every install: header, KPI band, primary and secondary panels, issue register, then the stamp, owner and next action. Figures are indicative and built only from what you type.

A Control Room is only worth the decisions it triggers.

Your answers, turned into a score, a dollar figure and three ways to act: from one AU$500 model you install yourself, to the full Control Room installed on your data.

Indicative $ at stake / year

—

Conservative: one-third of each loss recovered.

Control score

—

Thirteen control dimensions, scored from your answers.

Start with

—

The model aimed at your largest dollar line.

Your 13 control dimensions

Answer the questions to score each dimension.

Three ways to act on it.

Prices exclude GST. Buy a model or a profile online, or talk any option through with us first.

Individual model

AU$500 each, ex GST

Fix one gap yourself

  • Governed workbook on the nine-tab spine
  • How-to guide, data dictionary and QA sheet
  • 30 days of email support
Choose a modelSecure checkout, GST added

Reporting profile

AU$500 each, ex GST

One report, configured to your answers

  • Your KPIs, targets and RAG bands from this page, pre-loaded
  • Your loss categories and owners set up
  • Delivered in five business days, one revision
Buy a profile, AU$500Secure checkout, GST added

Control Room

AU$7,500 ex GST, single site

Installed on your data. Target: 14 days from data access

  • Data mapping and a refresh pipeline from your exports
  • Weekly cadence, owners and two training sessions
  • Governance pack, signed QA, 14-day hypercare

Anything you spend on AU$500 models or profiles in the 90 days before you book is credited in full against a Control Room.

Where the money is

How we sized it

Answer the output, loss and economics questions to size the gap.

E03 Weekly Ops Review

Your Monday, fifteen minutes

The install

What gets switched on

Days 1–2Data mapping
Days 3–7Build
Days 8–10Test
Days 11–14Train and go-live

Target: 14 days from data access.

Take it with you.

A PDF of everything above: your Control Room, the margin bridge, the downtime Pareto, all 13 control scores with a priority action against each, the dollars at stake with the working shown, and a suggested next step. Ready to forward to your team or your board.

  • A4, print-ready, about seven pages
  • Your answers included as an appendix
  • Built in this browser: nothing is sent to us

Put a name on the cover

All fields are optional. They only appear on your PDF.

Lodestone Analytics does not collect anything on this form. The report is generated in your browser and saved to your device. See our collection notice and privacy policy.

Illustrative only. Every figure on this page is calculated from the rough numbers you entered, using stated assumptions: 50 operating weeks; one-third of unplanned downtime, scrap and adverse cost variance recovered; the downtime split follows a typical Pareto shape until your log replaces it; report time valued at AU$85 an hour with 80% saved. It is a sizing prompt, not a forecast, a measurement or a guarantee, and not financial advice. Actual value depends on your data and the actions you take. Prices exclude GST.