Running on a live highway project · plant connected

From the plant to the road. Every decision connected.

Is the mix right? Is the fleet enough? Will the work finish on time, and at what cost? ASPHORA connects live production, paving quality, stock, planning and finance in one operation.

See the demo Request a quote

Read-only demo — sign in with demo@asphora.app · Asphora-Demo-2026

Illustrative product view

PRODUCING · SINCE 08:13
1,206.5TON
EME 0/20 · 16+200 → 16+853 · LEFT LANE
165GROSS T/H
149NET T/H
0:48STOPS
1,410DAY-END FORECAST
Plant on 8 h 05 · net run 5 h 48 · stops 48 min
DAY SCORE
84 six axes · one score
STOP 12:47 · 30 MIN
Fieldbus dropped
23 alarms in one second → one event, one root

One working day. The whole operation.

Right now

  • Is the plant running? Why did it stop?
  • Too few trucks, or too many? Cycle and queue times.
  • Mix conformity and temperature, while loading.
  • How many hours of bitumen, how many days of stock?

Through the day

  • Produced versus dispatched. Every load in view.
  • Out-of-spec load → estimated paving location.
  • Incoming materials and consumption, booked automatically.
  • Opening, closing, manual batch count and day score.

The whole project

  • Remaining work, finish forecast and priority targets.
  • Cost per tonne, profit or loss, payments outstanding.
  • Theoretical, plant and weighbridge tonnage compared.
  • What was paved, where and when — and at what thickness?

Everywhere

  • Phone, tablet and offline operator records.
  • Telegram events and a daily AI work summary.
  • Mark paving on the route map. See progress in place.
  • Automatic PDF at 19:00. English, Turkish and French UI.
Live production, dispatch and operation alarms.

Based on an actual application screen, with anonymised identities and illustrative data edits.

Open full-size image
Operation alarms · 15:00 (3 pm) · 40% chance of rain

Example weather warning, alongside production and quality alarms.

Route Map
The surveyor's alignment on satellite imagery, marked where it was paved
MARK
Progress Km Structures Sections
Tiles © Esri — Source: Esri, Vantor, Earthstar Geographics, and the GIS User Community
Route EME 0/20 1 EME 0/20 2 BBME 0/14 Viaduct / Tunnel Section
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 connected plant automation? Record trucks and stop reasons from a tablet. Automatic batch and temperature analysis requires a compatible plant connection.

Live plant 13:51 · UTC+1
8:05Plant on
1:09Warm-up
5:48Net run
0:48Stops
Day score 84/100
Capacity92
Utilisation78
Temperature96
Continuity71
Recipe64
Intervention95

12 batches with manual intervention

Capacity, utilisation, continuity, recipe, temperature and intervention. Open a score card to inspect the evidence; manual intervention is also shown as a batch count.

The plant is ready. Is the fleet?

See the trucks needed beside the trucks running. Follow measured cycle time, expected cycle time and estimated queue time; inspect the detail from the Live View cards. Spot a fleet shortage or excess before it becomes a lost shift.

Illustrative product view

6Trucks needed
5Trucks running
Measured cycle54 min
Expected cycle46 min
Estimated queue8 min

Fleet requirement responds to the operation. Cycle and queue values are estimates to support dispatch decisions.

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.

under the mixer

Know the mix is out of spec while it is loading.

Open the Live View cards to follow individual batches: recipe targets, actual weighing and deviations. The alarm panel flags out-of-spec mixtures while the truck is being loaded. Follow aggregate, bitumen and calculated asphalt temperatures against their specification bands.

Recipe conformity, day score and hourly weather.

Based on an actual application screen, with anonymised identities and illustrative data edits.

Open full-size image

From an affected load to the road section to inspect.

Repeated out-of-tolerance batches are associated with loads and an estimated chainage range. The lab sees where to start looking. Compare target thickness with estimated achieved thickness, plus over- or under-consumption.

Illustrative product view

Alarm panel · mix outside specificationLoad 18 · repeated recipe deviation
Estimated location≈16+420–16+445
Target thickness8.0 cm
Estimated achieved7.8 cm

Estimated location and thickness guide inspection; they do not replace field measurements or laboratory checks.

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
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.

Turn a deadline into a daily production target.

Save a priority area and its target date. Compare planned and completed work, the daily tonnage needed, and finish forecasts at planned and recent pace. The work calendar keeps holidays, production days and lost days visible.

Illustrative product view

Priority area · remaining8,400 t
Working days to target7
Daily production needed1,200 t

Material requirements show stock available and quantities to procure for the remaining programme.

in the yard

The weighbridge books it in. Production takes it out.

Incoming materials recognised by the weighbridge enter stock automatically. A bitumen tanker arrives; the receipt appears without retyping. Production consumption reduces stock in the same flow. See bitumen cover in hours, material cover in days, and which ingredient limits each asphalt recipe.

Weighbridge receipt → stock

Bitumen, aggregate and other configured incoming products. No duplicate entry.

Production consumption → stock deduction

Check today’s receipts, consumption and balance; calculate material needs by tonnes or kilometres.

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
in the office

Know the cost, the margin and what is still unpaid.

Break costs down into plant, haulage, paving and coats. Follow cost per tonne, earned value, profit or loss, cash flow and progress payments versus amounts paid. At day end, compare theoretical, plant and weighbridge tonnages side by side: three different measures, never added together.

Weighbridge

Measured dispatch tonnage. Compare it with plant production and theoretical quantities.

Plant

Production performance and actual material consumption.

Theoretical

The project quantity: compare the work done, plan the work remaining.

Day-end check · three separate tonnages

Illustrative product view

Theoretical · project1,260.0 t
Plant · produced1,206.5 t
Weighbridge · dispatched1,231.9 t

Compare the gaps. Never add the three measures. Review the work done, production and dispatch on their own terms.

Reconciliation · September
WeighbridgePlantGap
Day1,231.9 t1,206.5 t−2.1%
Month9,412 t9,180 t−2.5%
Year61,340 t59,905 t−2.3%

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

FinancialUSD
AsphaltDepreciation included
Cost per tonne54.12 USD/t
Material87.4%47.29 USD/t
of which bitumen35.11 USD/t
Labour6.0%3.23 USD/t
Maintenance0.3%0.17 USD/t
Depreciation6.3%3.43 USD/t

Asphalt cost breakdown from the application. Bitumen is included in material; it is not added again. Coats are tracked separately per m².

The records should tell the same story.

Compare work quantities with plant output, actual consumption with recipes, and stock counts with book balances. See crew productivity and labour cost per tonne alongside the operation.

at a distance

Your site reports to you. Wherever you are.

Telegram carries the events that matter: plant opened, asphalt started, production stopped, tanker arrived. The daily AI summary explains output, interruptions and points needing attention. At 19:00 the site diary is generated automatically as a PDF. On phone and tablet, the installed app opens offline; queued operator entries sync when the connection returns.

07:58Plant opened
08:13Asphalt production started · EME 0/20 · 16+200 left lane
11:05Bitumen tanker arrived · +25.0 t booked into stock
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
Theoretical 1,260.0 t · three tonnages compared
Paved 653 m · EME 0/20 · 16+200 → 16+853
Stops 48 min · 1 event · fieldbus
Bitumen 50/70 — 1.6 days left
Daily AI work summary

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 Tanker arrived 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
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.

Look at a real day before you decide.

The demo is a full project with sample data — production, chainage, stock. Read-only, nothing to install.

Open the demo Request a quote

demo@asphora.app · Asphora-Demo-2026