architecture

sensors in. ai in the middle.
people on everything that counts.

scoop is not a black box and not a rip-and-replace. it's a layer that sits on top of your existing sensors, systems and teams, and ties them together more intelligently.

01
sensors
data comes in
mqtt, rest, nb-iot. scoop reads from everything you already have, and can add new sources via an open api.
02
the model
ai computes
a dedicated forecast model per container. weather, seasonal patterns, behaviour. retrained daily, always accountable.
03
people
you decide
planner on desktop, driver on ipad. scoop proposes, you click approve. never the other way around.
what goes in
inbound integrations
fill-level sensors
sidconbammensenevomic-o-dataams-iot
existing waste systems
new wastexlwasteecube
external data
knmi weathercalendar apismunicipal agenda
what goes out
outbound integrations
erp & bi
ms dynamicsafassappower bi
reporting
pdfdocxcsvwebhooks
driver & planner apps
ipad · desktop · open api
one platform · three surfaces

for the planner. for the driver.
for the data.

planner dashboard
planners.scoop.systems
scoop
today
routes
containers
anomalies
reports
routes today
18 april · 3 drivers active
47 emptyings-28% km
kerkplein 1292%
westwijk-a78%
havenstraat64%
dorpsweg 841%
stationsweg28%
the overview planners are missing.
dynamic routes, anomalies, reporting, desktop-first, multilingual, connects with existing wms and erp.
driver app
trip · 08:42
3 / 12
next stop
kerkplein 12
underground · residual · 92% full
620m3 min
container lid reported broken, 2 days ago
big buttons.
short trips.
designed for the ipad on a dashboard, operable with gloves. next stop, always in view.
rollout · 4–6 weeks

who installs it.
how long it takes. what do i need to do?

the question procurement always asks, and always gets answered too late. here's the short version: we do it ourselves, in three phases, alongside your existing operation.

01
week 0–1
on-site assessment
we walk the route with you, inventory existing bins and sensors, and decide which containers do and don't count for the pilot.
what you get
inventory listcompatibility scansensor plan
02
week 1–4
installation, parallel, not disruptive
sensors are mounted during regular pickups. your existing fixed routes keep running until scoop is live. no stop-the-planning month.
what you get
sensors livesync with your wmsdrivers trained (30 min)
03
week 4–6
go-live with a safety net
scoop first runs in 'advisory mode' alongside your fixed route. only when the numbers add up do we switch to dynamic. you decide when.
what you get
dynamic routes activefirst monthly reportpost-live check-in
security & privacy

for procurement, legal and cio.
not as an appendix, as a foundation.

the public sector can't carry saas experiments. that's why scoop is built with gdpr, eu-hosting, data ownership and a serious sla as starting points, not as checkboxes.

gdpr-compliant
gdpr-ready from day one
data processing agreement as standard. dpia support per municipality. data minimisation as a design principle, we only collect what we need for the route.
iso 27001 in progress
hosted in the netherlands
all data on eu servers (rotterdam + amsterdam). no data transfer outside the eu. audit logs per user, per endpoint, searchable indefinitely.
no vendor lock-in
you own your data
the municipality is owner of all measurements, reports and models trained on your data. export whenever you want, csv, parquet, or a direct database dump.
99.95% sla
uptime with an sla
99.95% uptime, plus a contractually guaranteed back-up operations plan. if scoop goes down, you get a fixed route as a safety net. never a planning blackout.
frequently asked questions

everything you want to know,
before the demo.

the average rollout takes 4–6 weeks, depending on sensor installation. until then we run in parallel with existing fixed routes so nothing breaks.
plan a demo

let us show you the kilometres
you'll save.

a 30-minute live demo on your own district data. we bring a planner and a driver back-seat.

rotterdam · nl