PLATE P.6.2 — DATA WAREHOUSE

A data warehouse your figures all read from, built in Adelaide

A data warehouse is one store that holds a reconciled copy of the figures from every system you run — sales, jobs, stock, accounts — matched, kept with their history, and read by every report, dashboard and spreadsheet in the business. It is for businesses whose systems each tell a different story. Ozwebnet builds data warehouses from scratch in Adelaide, South Australia, for businesses across Australia: one fixed quote staged against milestones, and the source code handed over with the IP assigned to you.

DETAIL OF SHEET 06 — DATA PLATFORMS →

FIG. P.6.2 — THE PLOTTER: EVERY CHART IT DRAWS AND EVERY SHEET BESIDE IT IS PLOTTED FROM THE ONE DATA FILE · HOVER TO POUR
GENERAL NOTES 02 / 07

What is a data warehouse and what does it hold?

A data warehouse is a database of your own that holds a copy of the figures from every system you run, pulled on a schedule and kept in one shape. Reconciled means the copies have been matched — the customer in Xero is the same customer as the one in simPRO and on the till — and the differences resolved by a rule you agreed, once, in writing. The store keeps every figure with its date, so last month's numbers still read the same next year. Dashboards, reports, Excel and your accountant all read from this one copy.

SECTION A–A 03 / 07

Who needs a data warehouse, rather than dashboards that read each system directly?

BUILT FOR
Businesses running two or more systems that each hold a version of the same customer, job or sale — accounts, job management, point of sale, stock — and whose totals disagree depending on which one you ask.
REPLACES
The master spreadsheet that joins the exports by hand each month; the reporting tool pointed at three systems that each define a customer differently; the argument over whose figure is right.
NOT FOR
A business on one system whose reports already agree — dashboards can read it directly — or one whose only need is an existing report sent on a schedule, which is automated reporting; we will say so.
SCHEDULE OF WORKS 04 / 07

What is included in a data warehouse build?

01

A written map of every source, and which one is the authority

Each system you run is listed with what it holds — customers, products, jobs, invoices, stock — and for each kind of record, which system's version wins when two disagree. This is agreed before any figure is copied.

02

Copies pulled from your systems on a schedule, read-only

Figures are read from Xero, MYOB, simPRO, ServiceM8, Cin7, your point of sale or your own database on the schedule you set — nightly, hourly, whatever each figure needs. The warehouse only reads; nothing in the source is changed and nothing is re-entered.

03

One customer, one product, one job, however many systems name them

The same customer is spelt one way in accounts, another on the job board, and is a number at the till. The rules that join them into one record are written down, applied the same way on every load, and anything that will not match is listed for a person to decide.

04

Every figure kept with its history, not just its latest value

The store holds each figure as it stood on each date. An invoice edited in June still reads as it did in the May report, and a price changed today does not rewrite last year's sales.

05

Where each figure came from, recorded beside it

Every row carries the system it was read from, the record it came from and the time it landed, so any number on any report can be traced to its source in one step.

06

Checks that run on every load, and a named person told when they fail

Row counts and totals are compared with the source system each time figures land. A load that fails, a gap in the schedule or a total that has drifted is reported to someone straight away, rather than left for a wrong report to find.

07

A standard database you own, open to any tool that reads one

The warehouse is a standard database, not a locked product. Your dashboards read from it, and so can Excel, Power BI, a scheduled report or your accountant's own query; you receive the source code with the IP assigned to you.

TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.

Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.

STAGES 05 / 07

How is a data warehouse built and priced?

One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.

SEE THE FIVE STAGES ANIMATED 
  1. 01 SURVEY

    Discovery

    We list every system that holds a figure, what each one calls a customer, a job and a sale, and where the totals disagree today.

  2. 02 BLUEPRINT

    Specification

    Which system is the authority for each customer, job and sale, the rules that match them and the schedule each load runs on are written into the specification; the fixed quote is set here, staged against milestones.

  3. 03 FORGE

    Build

    Each source is loaded and matched in turn, so at every milestone there is a store you can query and figures you can check, not only at the end.

  4. 04 TEMPER

    Testing

    Every total in the store is reconciled back to the system it was read from, and the loads are run on the live schedule before launch.

  5. 05 DEPLOY

    Launch

    The scheduled loads are switched on, your reports and spreadsheets are pointed at the store, and you receive the source code with the IP assigned to you.

REQUESTS FOR INFORMATION 06 / 07

Questions before you call

RFI-01Do we need a data warehouse if we only run one system?

Usually not. If one system holds your figures and its reports agree, dashboards can read it directly. A warehouse earns its place when two or more systems each hold a version of the same customer, job or sale and the totals disagree — and we will say so either way.

RFI-02Does a data warehouse change anything in Xero, MYOB or simPRO?

No. The warehouse only reads from your systems, on a schedule you set; nothing in the source is changed and nothing is re-entered.

RFI-03How much does a data warehouse cost?

One fixed quote, set in writing before the build and staged against milestones.

RFI-04Do we own the data warehouse?

Yes — source code delivered, IP assigned to you. It is a standard database, so Excel, Power BI or any reporting tool can read it as well as the dashboards we build.

RFI-05Do you build data warehouses for businesses outside Adelaide?

Yes — Adelaide first, Australia-wide. The warehouse is written in Adelaide and reads from your systems wherever your office is.

RFQ — REQUEST FOR QUOTE 07 / 07

Get a fixed quote for a data warehouse.

Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.

CALL 1300 699 321 Mon–Fri 9–5 ACST · REPLY WITHIN ONE BUSINESS DAY