Departments have different figures
We agree on common definitions. The reason is simple: the same metric is calculated by different formulas.
Three items follow strictly in order: first the rules, then the warehouse, and only after that automatic processing of incoming documents.
Single lists of partners, products and organisational units, the rules for adding to them and the catching of duplicates. Skip this stage and you get a system that simply processes rubbish faster.
Metrics from the accounting system, the online store and third-party services flow into a shared warehouse, from which datasets on sales, stock, money and production are built. The result no longer changes depending on who prepared the report.
We read scanned source documents: delivery notes, invoices, certificates of completion. Numbers, dates and amounts land in the database by themselves while the employee only checks and approves.
The request usually sounds like «build us a nice dashboard». Almost always one of the problems below is behind it, and that is what needs treating.
We agree on common definitions. The reason is simple: the same metric is calculated by different formulas.
We clean the reference data and set the rules. Duplicates appear where nobody checks at the moment a record is created.
We build the warehouse with scheduled refreshes. Assembling it by hand from exports eats whole days of an analyst's time.
We set up scheduled loading. A manual export once a month cannot keep up with the decisions.
We switch on automatic document reading. Details and amounts are typed from paper by hand, line by line.
A pretty dashboard on top of dirty data is more dangerous than no dashboard at all. While a report is assembled by hand, a mistake gets noticed along the way. A finished chart is persuasive by its very look, and people act on it without bothering to check the underlying numbers.
We start with one department and a narrow set of figures. Trying to cover the whole organisation at once drags on for months and usually ends in nothing.
We agree what counts as revenue, as a shipment and as an active customer. The dullest and the most important step.
We establish what is stored in which system and how usable it is. We estimate how much cleaning up is needed first.
We start the scheduled data pipeline and build the first dataset around the questions the director actually asks.
We add further systems and departments. Each new connection is cheaper than the last because the foundation is already built.
When all the information sits in a single system and nobody disputes its figures, no extra layer is needed. The need arises with several data sources: the accounting system, the online store, the warehouse system, advertising accounts. Pulling all of that into the live database is awkward, and large queries against it slow down everyday work.
With tidy data, about a month including agreeing the list of metrics. When the reference data has been neglected, the bulk of the time goes on sorting it out and the estimate shifts. That is why we study the contents of the databases first and only then quote a timeline.
On standard printed forms the accuracy is high; on handwritten notes and murky scans it is lower. That is why there is always human confirmation in the scheme: the software fills the fields, the accountant checks and posts. The time saving remains even with spot checks.
Both are possible. Under a support contract we do it: we watch the data pipelines, adapt to changes in the source systems and add metrics at your request. Or we hand everything over to your own specialists with the documentation. The choice is fixed at the start of the project.
Напишите, какие сводки готовятся вручную и в каких показателях возникают расхождения. Изучим системы-источники и предложим, с какого набора данных начать.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.