Skip to content
Business Intelligence SimulatorGodEngine

SIMULATION LAYER 01 / 09

Seven sections. Section depth follows data availability, not ambition.

Finance is safe: a trial balance gives it. Supply chain needs a purchase-order register and a goods-receipt log. Compliance needs a filing calendar. Below is every section, with what it computes on an accounting export alone and what each other panel is waiting for.

SIMULATION LAYER 02 / 09

Group · Company

Overview

The figures checked first, and the signals ranked against them. A signal is not a generated observation — it carries a severity, a window, the metrics it refers to and its evidence rows, each with the source behind it.

Severities are deliberately three: needs action, watch, working. Anything finer would imply a precision the underlying reading does not have.

  • 1

    Needs action

    4 qtrs

    Ranked first, with evidence rows keyed to the documents they were read from.

  • 2

    Watch

    projected

    A signal on a projected window says so, so it is never mistaken for something recorded.

  • 3

    Working

    2 qtrs

    What is going right is reported too. A list of only problems is a biased reading.

SIMULATION LAYER 03 / 09

Group · Core

Finance

The section a trial balance alone makes real. Revenue, margin, cost and working capital derive from measures a general ledger genuinely states, which is why this is where a first upload is judged.

real on one export

  • Formula, visible

    Each panel states its formula as a tree over named measures, not as prose. Substituting the measures reproduces the figure exactly.

  • Drivers, with residual

    A movement is decomposed into drivers, and whatever the drivers do not explain is labelled unattributed instead of being distributed across them.

  • Line items, with "other"

    Breakdowns carry an explicit other bucket rather than quietly dropping the tail.

SIMULATION LAYER 04 / 09

Group · Core

Sales

Sales invoiced is in the ledger. Sales as a pipeline — stages, conversion, cycle length, win rate — is in a CRM, and no accounting export contains it.

Send a pipeline export and the section fills. Until then it shows what the ledger supports and names the rest.

Revenue by period
computes
Pipeline coverageneeds a CRM stage export
locked
Win rateneeds won and lost outcomes per opportunity
locked
Sales cycle lengthneeds created and closed dates
locked

SIMULATION LAYER 05 / 09

Group · Core

Marketing & Growth

Marketing spend sits in the ledger and computes. What that spend caused does not, and attribution invented from a ledger is the clearest example of a number that looks real and is not.

Cost per acquisition needs acquisitions counted somewhere other than the accounts. That is a source, not a model.

The temptation this section exists to refuse

Every analytics product can produce a customer acquisition cost from a spend line and a customer count guessed from invoice frequency. It renders beautifully and it is not a measurement.

A locked panel with a named requirement is worth more, because it tells you exactly which export makes it real.

SIMULATION LAYER 06 / 09

Group · Delivery

Operations

Operations panels and what unlocks them.

  • Utilisation

    locked

    Output against available capacity. Capacity is an operational fact about plant and shifts; no accounting export states it.

    Unlocked by a stated line or shift capacity. Note: rising utilisation is treated as bad here — past a point it means no headroom, which is where delivery failures start.

  • Rework rate

    locked

    Needs a quality outcome per unit produced. A ledger may carry a rework cost, but not the denominator.

    Unlocked by a quality or inspection log.

SIMULATION LAYER 07 / 09

Group · Delivery

Supply chain

One panel computes today. The other three name what they need, and one of them is the closest locked panel in the whole product.

  • Inventory cover

    computes

    Closing inventory over cost of goods sold, in days of the period. The one supply-chain panel a trial balance genuinely supports.

  • Vendor concentration

    closest

    The share of purchases going to the largest vendors, so it needs purchases by vendor. Mapping every creditor account individually would give this.

  • Lead time

    locked

    Order date to receipt date. Neither is in a ledger. Unlocked by a purchase-order register with receipts.

  • Cost variance to plan

    locked

    A variance needs a plan. The ledger records what was spent, never what was budgeted. Unlocked by a budget or standard-cost schedule.

SIMULATION LAYER 08 / 09

Group · Governance

Compliance

Entirely document arithmetic. Filings on time is a comparison of due dates against filed dates; findings and their ageing come from an audit observation register; renewal exposure needs contract end dates and values.

None of it can be derived from a ledger, and all of it is straightforward once the register exists.

Filings on timefiling calendar, or GST acknowledgements
locked
Open findingsaudit observation register
locked
Days to close a findingregister with opened and closed dates
locked
Contract renewal exposurecontract register with values and end dates
locked

SIMULATION LAYER 09 / 09

Which sections do you actually have data for?

That question decides where we build first. Tell us what exports exist and we will say plainly which sections would be real for you and which would stay locked.

Start that conversation