ASPHORA — Smart Asphalt Operations Platform

01 / the problem

Production is in the plant's printer. Quantities in a notebook. Cost arrives at month end.

Every road project keeps the same three records, and none of them agree with each other.

The plant knows tonnes

The control PC prints a log nobody reads until something breaks — and the shift total still gets typed up by hand.

The site knows metres

Which chainage got which layer is tracked separately, by hand, and rarely matches the plant.

The office knows money

Cost per tonne shows up weeks later, when nothing can be done about it any more.

02 / at the plant

The plant reports itself.

The plant's control system feeds ASPHORA on its own, every few minutes. Nobody types a tonne. The cumulative curve, warm-up, every stop window and every batch weighing arrive by themselves — and the day is scored on six axes. Two paces stand side by side: the machine's and the day's.

No automation on your plant? A tablet with two buttons — add a truck, pick the stop reason — does the same job.

Live plant 13:51 · UTC+1

8:05Plant on

1:09Warm-up

5:48Net run

0:48Stops

Day score 84/100

Capacity92

Utilisation78

Temperature96

Stops71

Warm-up64

Manual mode95

Six axes, one score — and each axis opens to show this plant's own normal, not a figure from a catalogue.

03 / when it stops

Twenty-three alarms in one second are one event, not twenty-three.

A plant's fault log is a chain: a fieldbus drops, twenty drives and scales fault behind it, the watchdog fires. ASPHORA reads the chain, names the root and puts the cause on the chart and in the Pareto. Ask for more and the assistant reads the day, gives a diagnosis with its evidence — and you grade it. The plant learns its own normal; every verdict becomes case memory.

Stop diagnosis · 12:47 – 13:171 event · 23 records

12:47:40Fieldbus fault

12:47:4022 drive and scale faults behind it

12:47:41Watchdog

Root: fieldbus

The bus dropped first; the drive faults are consequences, not causes. The team's note points at the coupler in cabinet 3 — a statement, not a measurement. evidence: plant log · this plant's history: 3rd time in 30 days

CorrectPartlyWrong

Your verdict feeds the case memory. The next diagnosis starts from what this plant has already taught it.

Assistant

Why did the plant stop on 2 September?

Two windows. 13:13 – 13:38: sixty-two "lack on sort — bitumen 1" warnings, the plant waited for binder. 14:16 – 14:41: a gap after the tank change. No fault of the S class on either; production resumed on its own both times.

read: plant day · incident history · stock

Verify against the plant log before you act on it.

It fetches the numbers with read-only tools and says so when it is inferring. It advises; it does not decide.

Machine groups · one dayevery record read

Burner4 Cold feed17 Mixer2 Scales23 Filter6 Binder line62

Records that never stopped production are counted too, group by group. Sixty-two “insufficient supply” entries on the binder line inside half an hour are not a breakdown yet — they are the one about to happen.

04 / under the mixer

The mix is checked before the truck leaves.

Every batch carries its own weighing: what the mix design asked for, what the scales actually put in, and the deviation on each component. Aggregate and binder temperatures run alongside it, minute by minute, against the band the design allows. A day that drifted is visible the same day — not when the cores come back from the laboratory.

Batch 412 · 13:04within tolerance

Component	Design	Weighed	Deviation
Aggregate 0/4	31.0%	31.2%	+0.2
Aggregate 4/10	24.0%	23.8%	−0.2
Aggregate 10/20	34.5%	34.6%	+0.1
Filler	5.8%	5.8%	0.0
Binder 50/70	4.70%	4.62%	−0.08

Every batch of the day is read the same way, and the day carries the share that stayed inside tolerance.

Temperature · through the daybinder cooling 14:20

Aggregate 164° Binder 151°

A binder tank that cooled at twenty past two shows up here as a line — before it shows up as a complaint from the paving crew.

1,568t/day capacitymeasured 149 t/h net

17,720 tremaining2 sides · 3 layers

11.3days at plan14.9 at measured pace

★Priority programme · 16+000 – 19+170 · 8,400 t · 5.4 days

12+408 – 15+6903,282 m5,668.8 t

16+100 – 19+1703,070 m5,302.7 t

19+680 – 19+74060 m103.6 t

Material requirementsShortfall 340 t

40/50 Bitumen 1.6 days

0/4 6.5 days

8/16 all of it · +2,536 t excess

05 / on the road

Progress measured in chainage, not in guesses.

Import the surveyor's alignment once. Mark what was paved, where and in which layer — viaduct decks counted on their own. What is left comes out in tonnes and in days, twice: at plan capacity and at the plant's measured pace. Materials show days of cover, not a percentage. Save a filter as a priority programme and the Overview reports on it every morning.

06 / in the yard

Stock moves without a keyboard.

Bitumen, aggregate and filler leave the yard as the plant uses them. Tack-coat emulsion and fuel come off with the work that consumed them — nobody opens a spreadsheet. The alarm fires the moment a level crosses its minimum, and every material shows how many days of the remaining programme it covers.

Stock · now days of cover

Bitumen 50/7065.2 t1.6 days

ECR-65 emulsion12.4 t9 days

Diesel8,900 L6 days

8/166,013 tcovered

Today's movements

−47.9 tBitumen 50/70plant consumption

−1.9 tECR-6515,840 m² tack coat

−612 LDiesel96 haul trips

Bitumen 50/70 crossed the 40 t minimum · 14:02 · sent to Telegram

07 / in the office

Three tonnages. Three questions. Never added together.

The weighbridge ticket is the money. The plant tonnage is the performance — and the bitumen it actually burned. The theoretical tonnage is what is left and what to order. ASPHORA keeps them apart and shows the gap in one place, by day, month and year. The weighbridge tickets arrive on their own — no Excel, no retyping.

Weighbridge

Progress payment and every financial figure. The official one — it leads wherever a single tonnage is shown.

Plant

Performance, planning projections and bitumen consumption — 65 to 70 percent of the cost.

Theoretical

Taken from the alignment itself. What is left to pave, what to order, and the money still to earn.

Reconciliation · September

	Weighbridge	Plant	Gap
Day	1,231.9 t	1,206.5 t	−2.1%
Month	9,412 t	9,180 t	−2.5%
Year	61,340 t	59,905 t	−2.3%

Inside the normal band the gap stays quiet. Colour appears only when a month leaves it.

Financial USD · DZD

Material85.3%48.92 USD/t

Bitumen61.2%35.10 USD/t

Haul · measured, not estimated3.7%2.14 USD/t

Cost per tonne57.21 USD/t

Progress payment2026

GC-12Base course18,420 t

GC-14Binder course9,860 t

GC-31Tack coat96,400 m²

Where the cost actually sitsthis month

Plant58%

Haulage21%

Paving15%

Coats6%

Waste recorded where it happened, not discovered at the year end Remaining work carries its own cost and its own margin

Machines, crews, fuel and materials are costed per section and per month, in the project’s own currency.

08 / at a distance

The plant has no signal. The manager is not on site.

The bridge tells the team's group what the plant is doing while it does it: opened, asphalt started, stopped for thirty minutes and why, resumed. At the end of the day the report comes with an AI read, and at seven in the evening the site diary is saved as a PDF — written by the data, not by a person. Trucks entered with no connection queue on the device and reconcile when the bar returns.

07:58Plant opened

08:13Asphalt production started · EME 0/20 · 16+200 left lane

13:17Production stopped for 30 min · fieldbus fault

13:26Production resumed

19:00 · Day-end report

Plant 1,206.5 t · weighbridge 1,231.9 t · 84 trucks

Paved 653 m · EME 0/20 · 16+200 → 16+853

Stops 48 min · 1 event · fieldbus

Bitumen 50/70 — 1.6 days left

AI read

Net rate held at 149 t/h; the only material loss is the 12:47 fieldbus stop, the third of its kind this month.

Order bitumen today, not this week.

Site diary · PDF · 19:00

You choose what arrives, and when

Plant opened Asphalt started Production stopped Resumed Status at the hours you pick Stock alarm Shift ended Day-end report Site diary PDF AI read

Every one of them has a switch, and the status hours are yours to set. One button connects your own group; the notifications speak four languages.

Notifications come from the server, so a shift entered with no connection still reaches the group once the device is back.

247

QUEUED · SYNCS ON RECONNECT

Nothing lost, nothing typed twice

09 / anywhere

Written for any road project, not for one country.

Time zone, locale, currency, materials and mix designs all come from the project itself. Nothing about a site is baked into the software. The interface speaks three languages, the notifications four, and a sixteen-step checklist walks a new project from empty to running — with each step saying which page stays dark until it is done.

EN · TR · FRinterface languages

4notification languages

∞recipes and materials

16setup steps, checked for you

Plant automation is connected per make — Ammann today, other makes per project. The weighbridge is connected the same way. No automation? The tablet flow needs nothing but a browser.

Who sees what

Four roles. Money stays with management — an operator never opens it. Settings sit behind a PIN. You add your own people, and you cut their access yourself.

What is on site

Machines, the hours they ran and the crews that ran them, against a working calendar that already knows the country’s holidays.

Where your data lives

Each project in its own space, backed up every day and recoverable to a point in time. It is your data, and it stays that way.

Every tonne, every kilometre, every stop, on one screen.