Deployments

Built for real municipal operations

SCMS modules are designed around operations municipalities already run. This page states clearly what each module's status is and how modules are typically deployed.

Status definitions

What each status means

We use these terms consistently. A proposal is never described as a deployment.

Deployed

In operational use by an authority.

Pilot

Running with an authority for a defined period and scope.

Tested

Validated in field or controlled conditions.

Available

Offered for deployment today.

Beta

Functional and under active development. Scope agreed per project.

Module register

Current module status

Module	Domain	Deployment type	Status
WASTE	Waste collection operations	Street and vehicle	Available
MEASURE	Tank level monitoring	Buildings and tanks	Available
GUARDIAN	Elderly care support	Wearable	Available
ADOPT	Companion animal management	Collar tag and app	Available
CLINE	Citizen requests	Software and app	Available
PROTECT	Emergency alerting	Software, app and sensors	Available
PULSE	Public consultation polls	Software and app	Available
CULTURE	Events and culture	Software and app	Available
VOLUNPEER	Volunteer management	Software and app	Available
BUSINESS	Local business promotion	Software and app	Beta
justPARK	Paid parking	App and enforcement checks	Beta
SERVICES	Official documents	Software and app	Beta

Deployment scenarios

How modules are put to work

Typical scenarios, described so that authorities can see how a deployment is scoped. They are not case studies of specific clients.

Scenario

WASTEBRAINCity App

Documented waste collection across a municipal fleet

Challenge: Complaints about missed bins cannot be verified, and routes have not been reviewed for years.
SCMS solution: Sensors on bins and gateways in collection vehicles produce a Digital Proof of Collection. BRAIN is used to review routes.
Typical scope: Bins in one or more collection sectors and the vehicles serving them.

Scenario

MEASURENOTIFIER

Heating fuel in schools and public buildings

Challenge: Tanks are checked by hand. Low levels and abnormal consumption are noticed late.
SCMS solution: Tank sensors report levels to SCMS. Responsible staff receive alerts for low level and sudden changes.
Typical scope: Fuel and water tanks across the municipality's building estate.

Scenario

PROTECTCity App

Civil protection alerting for a flood-prone area

Challenge: General announcements do not reach the residents actually at risk, in time.
SCMS solution: Incidents are published as geofenced zones, with scenarios for push, SMS, email and voice calls, and instructions attached.
Typical scope: Defined risk zones, with optional connected sensors.

Scenario

CLINEVISION

Everyday requests handled in one workflow

Challenge: Requests arrive by phone, website and in person and are tracked in separate lists.
SCMS solution: All channels feed one queue. Requests are routed, grouped by location and reported on by department.
Typical scope: All municipal departments that respond to citizens.

Next step

Discuss a deployment

We can share details of deployments relevant to your municipality and scope a first phase with your teams.

Discuss a deployment