Skip to content
BI & reporting

Sites, trucks, plants: dashboards built on reconciled figures

For managing, finance and operations directors in construction, transport, asphalt plants and industry. We start from your Excel exports, your software and your activity reports, and reconcile the figures. Then we build Power BI dashboards, or a custom web reporting app, where everyone reads the same numbers.

  • Power BI or a web app
  • Phone layouts
  • Figures reconciled before publication
  • Indicators defined with you

Dashboards

What we build

Reports organised around what drives the margin in your trade: sites and projects in construction, trucks and trips in transport, tonnes produced in a plant, jobs and purchasing in industry. The figures come from your files, your software or Rivena’s own products. We start from the indicators that matter to you; here is what we can build.

Management dashboard

A home page for management: the month’s production, margin, cash position and alerts, with direct access to the detail. Every total breaks down from group or company level to a single site, truck or production plant.

One report, organised in spaces

  • Management
  • Budget
  • Weekly report
  • Sites & projects
  • Production
  • Fleet & fuel
  • Purchasing
  • Administration
  • Cash
  • Finance
  • Budget vs actual, variance analysis

    The month’s actuals and the cumulative total compared with budget, by site, business line, production plant or company. Variances are explained by cost type and compiled in a monthly pack in Excel, PowerPoint or PDF. For projects run in Rivena Projects, the execution budget, the time entered and the margin per project form the basis of the dashboard.

  • Cost price and margin

    Production, costs by type (labour, equipment, fuel, materials, subcontracting), share of overheads and margin, by project, plant or company, with documented allocation keys. For a plant: conversion cost per tonne, excluding materials, and full cost per tonne.

  • Profitability per truck

    Revenue and costs for each truck, period by period: leasing, insurance, vehicle tax, hire, fuel, maintenance, labour and indirect costs, whether the truck works by the trip, by the tonne or by the day. The costs come from Rivena Equipment or from your own files.

  • Automated weekly activity report

    Week and month-to-date production against the monthly budget, fuel, equipment and headcount by role, a month-end projection at the current pace, and a list of sites or depots that have not sent in their report.

  • Cash and scenarios

    Cash position and cash plan by project, company, client and supplier, with actuals compared with forecast. The low point is spotted in advance and several collection scenarios are compared before the management meeting.

  • Machines, trucks and fuel

    Utilisation of machines and trucks, long breakdowns and replacement hire, profitability per machine, fuel consumption against standards, and the gap between fuel bought and fuel allocated to sites or vehicles. The data can come from Rivena Equipment, Rivena Fleet or your own files.

  • Purchasing and material control

    Supplier Pareto, price trends, lead times from purchase request to order to receipt. Material control: theoretical consumption, from mix formulas or planned quantities, compared with quantities delivered or issued from stock, with the gap valued in MAD.

  • Contracts, earned value and price revision

    For contractors: contract portfolio (value, service orders, deadlines, progress, work remaining), earned value (CPI and SPI, estimate at completion) and price revision, with K coefficients per contract and month and the gap between revision due and revision billed.

  • Overheads and headcount

    Overheads tracked by type. Headcount, attendance from time recording, absences and leave, by site, plant or role, whether the data comes from Rivena HR or from your own files. Everything is shown as totals: groups that are too small are merged so that no individual data appears.

Two ways to deliver

Power BI, or a custom web reporting app

Power BI covers most needs. When licence costs, the number of readers or highly specific calculation rules make it a poor fit, we can build a dedicated web reporting application instead.

  • Microsoft platform

    Power BI dashboards

    Reports built in Power BI Desktop on a documented data model, organised in spaces, with a phone layout for every page. Online sharing goes through the Power BI service and your Microsoft licences, in your own environment.

    Data flow

    1. Your Excel exports
    2. Python preparation
    3. Power BI model
    4. Reports and mobile

    What it includes

    • Documented data model and DAX measures
    • Management, business-line and cash spaces…
    • A phone layout for every page
    • Versioned, backed-up Power BI project (PBIP)

    When to choose it

    Your teams already work with Microsoft 365 and the number of readers keeps Power BI licence costs reasonable.

  • Custom-built

    Web reporting app

    A web application of your own: your files are read with Python, stored in a database, served through an API and displayed in a web interface. When it replaces an existing report, its figures are reconciled cell by cell with the old one before the changeover.

    Data flow

    1. Your Excel exports
    2. Python ingestion
    3. Database
    4. API
    5. Web interface

    What it includes

    • Your files read with Python, never modified
    • Dedicated database and API
    • Screens by subject: purchasing, material consumption, equipment fleet, margins, checks
    • Versioned calculation rules, one-click refresh, load log

    When to choose it

    You have many readers, your calculation rules are specific to your trade, or you want a tool of your own, with no Power BI licence per reader. Hosting and maintenance need to be planned: we cost them with you at the scoping stage.

Either way, data preparation, reconciliation and the indicator dictionary are the same: starting with Power BI and moving to a web app later does not mean starting again.

Reliability

Reliable figures, reconciled before they are published

A dashboard is only useful if management can trust it. So the work starts well before any chart is drawn: data preparation, reconciliation and a controlled refresh.

  • Python data pipelines built on your exports

    Time sheets, fuel, trips, production, purchasing, sales: your Excel exports are read from copies, cleaned and consolidated into tables ready for Power BI or for a database. Your source files are never modified.

  • Reconciliation before publication

    Fuel bought and fuel allocated, cash and the finance department, production and invoicing, theoretical and actual material consumption, revision due and revision billed: each pair is reconciled. A gap that cannot be explained is flagged, not hidden.

  • Scripted refresh

    Extracts are rebuilt only when their sources have changed, and only the affected tables are reloaded. An update runs in a single step, with no manual file handling, and every load is logged, anomalies included.

  • Versioned, backed-up changes

    A Power BI report is kept in project format (PBIP), whose text files can be compared from one version to the next; a web app’s calculation rules are versioned in the same way. Every change is preceded by a dated backup and recorded in a change log.

  • Phone layouts

    Every Power BI page has its own phone layout, with title, filters, indicators and charts at full width. A custom web app is designed for the phone from the start, so figures can be checked from the site, the depot or the plant.

Method

From your files to the dashboard

Each step ends with your sign-off before we move on. The scope then widens, one space at a time.

  1. Understand

    Audit of current reporting

    We start from your current files and reports: sources, how figures come in from sites, depots or plants, indicators already tracked, and numbers that differ from one department to another.

    • Inventory of sources and reports
    • Gaps and duplicates identified
    • Priorities agreed with management
  2. Structure

    Data model and indicators

    Each indicator is defined with you: formula, source, frequency and owner. The data model, in Power BI or in the web app’s database, is built on those definitions, not the other way round.

    • Indicator dictionary
    • Documented data model
    • Reconciliation rules
  3. Build

    Dashboards

    Pages are built space by space on your real figures, reconciled with your sources, then reviewed with the people who will use them before anything is shared.

    • Management, business-line and cash pages…
    • Phone layouts
    • User acceptance testing
  4. Hand over

    Automation and handover

    Data preparation and refresh are scripted and documented. Your team takes over, or we stay on hand for future changes.

    • Preparation and refresh scripts
    • Documentation and change log
    • Handover to your team

FAQ

Before you start

For Power BI dashboards, yes. Reports are built in Power BI Desktop; sharing them online goes through the Power BI service and depends on your company’s Microsoft licences, whose type and number set the cost. We help you estimate what you need, and publishing takes place in your own Microsoft environment, with your IT team. A web reporting app does not need them.

When you have many readers and licences become costly, when your calculation rules are too specific for a Power BI model, or when you want a tool of your own. The app reads your files with Python, stores the data in a database, serves it through an API and displays it in a web interface. It does, however, need hosting and maintenance, which we cost with you before we start.

From what you already use: Excel exports from your ERP or other business software, time-sheet, fuel, trip and production files, and site or operations reports. We work on copies and never modify your source files. If a source is missing or unreliable, we say so rather than filling the gap.

No. A first dashboard can start from your current Excel files, as they are kept today. The preparation and reconciliation rules set along the way remain useful the day you change software.

We only access the files we need, read-only and on copies. Sensitive data (bank accounts, employees’ personal data, passwords) stays out of the reports, and headcount is shown as totals. A confidentiality agreement can be signed before any files are exchanged.

You decide. We hand everything over to your team (scripts, documentation, change log), or we look after maintenance and changes as part of an ongoing engagement. Either way, every change is preceded by a dated backup.

Yes, like any other source: from the Excel exports of Rivena ERP, Rivena Projects, Rivena HR or Rivena Equipment, or from the Rivena Fleet API. Connecting them to Power BI or to a web reporting app is part of the project, and the same checks apply: every figure is reconciled with its source before publication.

Let’s talk about how you work.

Tell us about your business, how your organisation runs and what you want to improve. We’ll then suggest a concrete next step — a demo, a call or a scoping session — with no obligation.

Based in Rabat · Demo on request

E-mail — E-mail us at contact@rivena.maRequest a demo