At the decision's level of detail
A report stays clear at the level the decision needs, with simple graphs or maps and a path to the underlying record.
Reporting
That is the kind of question reporting should answer. Collection, processing, a data warehouse and presentation, with every figure drillable to the record that produced it, because it came from the same operational data.
A code-native six-site bar view of sample margin per car. The bars compare Praha, Brno, Ostrava, Plzeň, Bratislava and Wien; the concept calls out Ostrava at 52 400, Wien at 22 100 and an average of 38 900, then explains the Wien outlier. Sample data, not dealer performance.
The problem
How much does the business earn? What causes the losses? Will there be enough money for next year's development? Is another mechanic worth hiring? These source questions usually trigger several exports that disagree; Reporting answers from records that already exist.
A report stays clear at the level the decision needs, with simple graphs or maps and a path to the underlying record.
Data is transmitted securely to the configured warehouse, processed and displayed across operating systems, browsers and devices with set access rights.
Reporting connects to source systems and can deliver tailored views; XLS and CSV remain available when data must move elsewhere.
Six standard views
Every standard view the source publishes, and the answer, evidence and drill-down it provides. Select one.
Cars in the business, average age of warehouse stock and commission, alongside open cases, tasks and images, a daily state of play.
This is the view a site manager opens first, not the controller's month-end view.
Cars sold, total sales and margins, average margin per car and the composition of that margin explain a good or poor month.
Composition distinguishes healthy retail from one unusually profitable trade deal.
Margin by sales price, mileage, production year and days on offer, plus leading brands and models, turns buying policy into an evidenced decision.
The result can shape what Sourcing looks for next month.
Count, total value, averages for price, mileage and age, plus how many cars are sitting at each stage of work.
Cars waiting on a task are cars not yet for sale, which is why both appear together.
Cars against capacity, value against budget, age and turnaround, and stock-age structure are the four comparisons a floorplan conversation needs.
Against capacity and budget, not in isolation: full within budget is different from empty and over it.
Count, value and average price split by price band and production year turn too much stock into a segment a buyer can act on.
The view makes capital concentration a specific decision rather than a general worry.
Capabilities
The full reporting process the source describes, grouped across the delivery pipeline.
From Omnetic modules and your own source systems.
Secure transmission, processing and storage in a data warehouse.
Reporting connects to systems outside Omnetic too.
Delivered as a service with no customer-hosted reporting server.
Simple graphs and maps at the detail the decision needs.
A figure openable down to the record behind it.
Overview, margins, margin profile, car profile, stock overview and structure.
Geographic visualisation where location is the question.
Views tailored to the content and visualisation in scope.
Data downloadable for further use.
A site sees its scope while a group can see across it.
Independent of operating system, browser or device.
By role
Gets one place to answer the operating questions that shape hiring, capital and development.
Compares sites on identical definitions and opens an outlier down to the deal.
Sees the same figures the group sees, turning the review into a discussion of causes.
Learns which vehicle profiles earned rather than which felt like good purchases.
Platform & data connections
Views read the events modules wrote rather than a separately interpreted export.
The ledger under the management view, so a KPI can reconcile with the books.
Ageing, capacity and stock value feed the stock views.
Your systems as additional sources, or the governed warehouse output feeding your BI.
System relationship
The views read the same operational events, ledger and stock records that the modules already use; Open Platform adds or exports sources at the governed boundary.
Outcome & proof
Group and site teams read the same metrics over the same operational records.
Every aggregate can open to the vehicle, order, task or document that produced it.
Six standard views are the starting set; custom views are scoped around the decision and its sources.
The reporting warehouse refreshes on a configured cadence documented for the deployment.
Delivery & cadence
Secondary product demonstration
One sample question connects a group figure to the site and vehicles that caused the outlier.
Review Reporting52,400 · 24 cars
41,200 · 31 cars
31,700 · 18 cars
22,100 · 19 cars
Average
38,900Outlier
−16,800Bring the number you cannot currently get without several people exporting spreadsheets. We will map it to the standard or scoped custom view that should answer it.
See the dashboardsThe operating decision the figure must support.
The modules and external systems that hold the input records.
The deal, vehicle, task or document a reader must be able to reach.