Novus Metrics
Demand and supply, where the work waits, how the machines run, what comes out right and how the routes run — read from the exports the business already keeps, week by week or year by year. Ask for a page in plain words, build it yourself, or open the method underneath; try a change beside how things run now; and trace every figure to the rows and the rule it came from.
Free for 30 days during the beta. Nothing is charged.
The whole operation
Five areas — Demand & Supply, Bottleneck, Equipment, Quality, Route & Location — each a question and the page that answers it, made from the sales exports, delivery sheets, job logs and machine readings a business already keeps.
Where does the time go, and what holds the flow?
The data it reads
Work events — a step, a start, an end, and the case it belongs to
✓ already in the Library
The page
Every step, the time each takes, and where cases wait
Proof holds the line
2.1 h average wait, 61% of lead time
And the what-ifs that read it
Process — add a prover, or split the step
Starting the reviews
Say what you want to see each week, month, quarter or year. Novus proposes the pages, a question for each, and drafts the review on synthetic sales or a simulated floor from what you tell it, so everyone can agree what to track. As the real files come in, the same pages fill with real numbers, each set beside its preview. Or start from a layout for your kind of work, and build it yourself.
Start with three questions — a page for each, then the assumptions:
Their files aren’t in yet, so I’ll draft it from what you tell me. What’s the business like?
✓ Made three months of sales and deliveries from that — Synthetic
✓ The floor’s runs are in Log — Simulation
✓ Built “Cebu — monthly review”. Every page says what it stands on.
Cebu — monthly review
for the operations director · 3 sections, then the assumptions
Needs its data
Needs its data
Needs its data
Assumptions
4 markets · about 1,200 loaves a day · paydays +20% · delivered Mon, Wed, Fri
Synthetic sales and deliveries, made by Novus from this; Studio’s simulated runs. When the real files arrive, each page sets its preview beside them.
Every number says where it came from
A made-up number is only safe to show if it can never pass for a real one. Novus keeps three kinds of data apart everywhere it shows them, and every result says which it was projected from.
A page built partly on real data and partly on a preview says that too — “partly synthetic or simulated” — so the moment the real numbers take over is visible, not assumed.
Your files, as they are
Sales exports, delivery sheets, a log of when each job started and finished — as they come, including the report-style sheets people fill in by hand, with the date above the table and headers in two rows. Novus works out what each file holds and shows you exactly how it read it, column by column.
The preparation is yours, without a data team or a script. As it reads, Novus finds the table under the header block, joins the sheets that belong together, sorts out dates, returns and currencies, and matches each column to what it holds — and shows every step, so you can point a column somewhere else.
Correct a reading once and it’s kept for that layout: next week’s file reads the same way, with nothing asked. The file stays in the Library as you gave it.
Three, from what this board already records:
Returns at Cebu · 9.1%
against a usual 4.8% — ₱18,400 at cost last month.
See it in Log › Analyze › Monarch
Pandesal selling out · 1 day in 4
Fri and Sat clear everything delivered, so next week's forecast is understated until that's read in.
See it in Review › Demand & Supply › Forecast
Mixer 2 downtime · 6.5 h
most of it waiting on a part, not repair.
See it in Review › Equipment
Monitor will raise a signal if any of them move — but only on readings you actually measure, never on a simulated one.
Every figure in a check-up comes out of code reading your rows — the same engines the rest of Metrics runs on. Novus words them and cites each one’s id, so you can check a finding instead of trusting it.
A file it can’t place is kept and named as not read, never quietly forced into shape. When a copy would drop lines, it says how many and why.
Drop a whole folder if that’s how it comes. Each file is listed with whether it was read in, and removing one never takes back what it already read.
What it reads
Where each kind goes, in full: the User Guide.
Studio
Lay out the line, counter, clinic or office the work runs through and run it as a flow. The runs become Simulation data, so Review has pages to show from the first afternoon — and once the real floor is recorded, the simulation is held against what it actually did.
Here it is on a small firm’s tax returns: the steps land, the run starts, and the returns pile up in front of the one reviewer.
Intake
15m
Prepare
80m · 3
Review
41m · 1
Sign-off
1 day
File
10m
Review holds the line. One reviewer for three preparers, busy 85% of the day — returns queue in front of it.
Try a second reviewer in What-ifs before hiring one.
Monitor · Studio vs actual
Within 10% counts as a match. Waiting is off — returns sit longer before Review than the model thinks.
What if
Eight levers — demand, capacity, process time, quality, reliability, supply, policy and money — each moved by a percentage, a shift or a set value, on everything or only the places, items or steps you choose. The staff, process, stock and warehouse engines run the change and set it beside how things run now: as a table, as a chart of what moved, measure by measure.
Lever
Move
Amount
On
A second reviewer on Review
Simulated| Now | With it | ||
|---|---|---|---|
| Returns done a week | 60 | 64 | +7% |
| Intake to filed | 2.3 days | 1.8 days | −22% |
| Waiting before Review | 66 min | 3 min | −95% |
| Reviewers · busy | 85% | 47% | −38 pts |
| Prepare · busy | 55% | 61% | +6 pts |
What moved
Sign-off is the longest wait now — a day a return. The second reviewer sits idle half the day; try shortening sign-off before hiring.
For when you want the controls: draw the floor Schematic, Standard or Illustrative, place the teams, set the layout, the calendar and how each step behaves. This is the real Studio, on the same tax-returns floor, running in your browser — open Review, give it a second reviewer, and press Run.
A sample floor, kept in this browser. Item extensions need a Project Board.
Underneath
Every page can be asked for in plain words — and every page can be opened to the rule that made it, changed, and checked. The engines are tested against the published worked answers of university operations-research courses, so a figure you defend upward is one you can work out by hand.
Start a Metrics project, describe the business or lay out its floor, and present the first review this afternoon. Bring the real files when you have them — the review will check its own preview.