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.

A small bridge reads the control PC's own log every few minutes. Nobody types a tonne. The cumulative curve, warm-up, gross and net capacity, every stop window and every batch weighing arrive on their own — and the day is scored on six axes. Gross is the machine's own speed; the gap to net is the organisation's loss.

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 say how it was computed and what this plant's own normal is over the last 30 days.

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, same second

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.

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

04 / on the road

Progress measured in chainage, not in guesses.

Import the surveyor's coordinates once. Every paving section is marked between two kilometre points, on a side, in a 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.

05 / in the yard

Stock moves without a keyboard.

Every batch weighed at the plant takes its bitumen, aggregate and filler off the yard by recipe. Tack-coat emulsion comes off by the square metre marked on the map; diesel by haul kilometre and machine hour. The alarm fires the moment a level crosses its minimum — not every day it stays below — 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/70batch weighing

−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

06 / 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 from the alignment 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 itself is read straight from the scale software — 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

Layer × width × thickness from the alignment. Remaining work, material 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 is printed faint. Colour appears only when a month leaves the band — a crossing is news, staying below is not.

Financial USD · DZD

Material85.3%48.92 USD/t

Bitumen61.2%35.10 USD/t

Haul · from the map, not the ticket3.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²

07 / 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

Sent by the server, not by the tablet — a shift entered offline still notifies when the device reconnects, and the bot token never reaches a browser.

247

QUEUED · SYNCS ON RECONNECT

Nothing lost, nothing typed twice

08 / 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, with the plant's real log files as the acceptance test. The weighbridge bridge reads the scale software directly. No automation? The tablet flow needs nothing but a browser.

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