The assets you can only check by driving to them
Lights, water, doors, gates and everything else
Floodlights, irrigation, amenity and toilet doors, change rooms, gates, bollards, pumps, metered power outlets, BBQs, HVAC, signage and scoreboards. If it can be switched, locked, dimmed, opened or metered, it can run to a schedule, report what it is doing and raise a work order when it needs attention.
Set and forgotten
A sports field is one of the few assets an organisation owns that nobody can see from the office. The lights come on at a time set into a controller years ago. The irrigation runs on a schedule written for a season that has since changed. Both keep running through rain, through a cancelled fixture, and through a fortnight when the ground was closed.
The maintenance is the same shape. A crew visits on a rota, which means they visit the court that has not been booked since March at the same interval as the one carrying four times its usual load. Nothing about that is anybody's fault. It is what happens when the only information available is the calendar.
One cause, and one cost: energy and water spent on an empty ground, crew hours spent on the wrong site, and a complaint as the first fault report. Once something on site can report what is happening, the schedule stops being a guess and the rota stops being a rota.
The lights are the obvious example because everybody can see them. The toilet block that somebody drives out to open at seven and lock at dusk is the same problem, and so is the change room that needs a key handover before every fixture.
Four things the controller does, whatever the asset happens to be. It does not care whether it is a light, a lock or a pump.
-
Switch and lock
Relays, contactors and access controllers put any powered or lockable asset under command.
-
Schedule
One-off or recurring schedules, tied to a booking or driven by a condition, with overrides from a phone.
-
Sense
Motion, light, moisture, temperature, occupancy, flow and door state, all reporting to one place.
-
Integrate
Documented APIs connect control to the systems you already run, so the booking creates the schedule and the fault creates the work order. Nothing is ripped out.
Lighting and irrigation are the start, not the limit
Eight kinds of asset, one controller. The ninth card covers the rest.
-
Amenity and toilet doors
Released at opening, locked at curfew, held open for an event, or released remotely for somebody standing outside on the phone. Every actuation is logged with a time and a user.
-
Change rooms and pavilions
Access granted to the club that holds the booking, for the hours of the booking. No key handovers and no after-hours call-outs.
-
Gates, bollards and barriers
Carpark and reserve gates on a calendar, retractable bollards for markets and road closures, all overridable from a phone.
-
Floodlights and public lighting
Programmable, dimmable and booking-aware, across fields, courts, paths, carparks and plazas.
-
Irrigation and water
Zone valves, pumps, tanks, bubblers, drinking fountains and water features, all weather and flow aware.
-
Power outlets and BBQs
Metered outlets for markets and food trucks, time-limited BBQ circuits, and event or EV power released against a booking.
-
HVAC, fans and heating
Halls, pavilions and community centres conditioned to the booking calendar instead of to habit.
-
Signage and scoreboards
Digital signage, wayfinding and scoreboards switched with the space they serve, and dark when it is closed.
-
Something not on this list
If it has power and a way to be triggered, it can be brought under control. Tell us the asset and we will scope it.
How it runs
Three things happen on every site, and the third is the one that pays for it.
-
Schedule, once
Staff set one-off and recurring schedules for any connected asset from a browser or a phone, tied to a booking where one exists, with overrides by SMS and email when the day does not go to plan.
-
Report, continuously
Sensors report occupancy, door state, soil moisture, light, temperature, flow and equipment status to one dashboard, and a controller that stops reporting is itself an alert.
-
Act on the data
A rules engine dims lights at dawn, releases amenity doors at opening, pauses irrigation when it is raining, and raises maintenance orders from usage and fault data instead of from the rota.
Three of the jobs it does today
Same controllers, same portal, same reporting. Only the asset changes.
-
Lighting
Lighting that follows the bookings
Fields lit dusk to dawn on a controller last opened years ago.
Training nights, seasonal hours, event overrides and curfews, set centrally and changed without a site visit. Switch, dim and diagnose from anywhere, so a failed lamp surfaces as an alert instead of a resident complaint.
Run-hour and consumption trends per asset, ready for capital planning and tariff conversations.
-
Irrigation
Irrigation that reads the weather
A schedule written for a season that has since changed, still watering through the rain.
Sensor-based control across sites, watering where turf and plantings need it and not where they do not. Rain skips a cycle and heat brings one forward, without anybody driving out to a controller.
Less waste, less runoff onto paths, and a defensible position during water restrictions.
-
Amenities and access
Doors that open for the hirer
A lock-up run every night, and a key handover before every fixture.
Amenity doors release at opening and lock at curfew across the whole area. Change rooms, halls and gates open for the hirer, for the hours booked, then close themselves.
Every release, override and fault logged with a time and a user, which is what a claim or a safety review asks for.
What sits behind it
Field hardware built for sites with poor power and worse connectivity, and an API layer that assumes you already own systems worth keeping.
Leads with
It keeps running when the network does not
CV6000 field controllers hold their schedules and keep logging through an outage, so lights, doors and pumps do what they were told regardless.
-
Several sensors, one picture
Motion, light, soil moisture, door state and occupancy read together, which is what makes a rule worth writing.
-
Rain stops the water
Weather feeds and flow-meter data pause and resume irrigation without anybody deciding to.
-
Occupancy you can put in a budget bid
People counts and door-strike inputs show which zones are in demand and which are not, which is evidence a capital case can be built on.
-
It talks to what you already run
Documented REST APIs connect it to booking, asset management and CRM platforms, so billing and reporting stay where they already are.
-
Hosted in Australia where that is required
Australian hosting is available for organisations with data residency obligations. Which arrangement applies to you is settled during scoping.
Where it goes
One platform, across assets with very different owners.
Sport and recreation 5
- Sports fields and courts
- Aquatic centres and pools
- Golf courses
- Fitness trails and areas
- Skate parks and BMX tracks
Parks and open space 5
- Parks and event spaces
- Gardens and green sites
- Botanical gardens
- Beaches and boardwalks
- Dog parks
Community and civic 3
- School grounds
- Community centres and squares
- Urban plazas and streetscapes
Councils, private clubs, schools and facility operators. Every scope starts with a site assessment.
Why it is noticed
These are the assets residents notice the moment they stop working.
A locked toilet block at nine in the morning, a dark field on a training night, a gate that will not open for the markets. None of it is complicated and all of it is visible, which is why it takes up more of a council meeting than anything expensive.
What we do and do not do
What it does
-
Assess, install and commission
Certified electricians and network engineers size the controllers and sensors against the power and connectivity each site already has, then install and prove them.
-
Run it afterwards
The platform is monitored and supported as a managed service, so a controller that stops reporting is noticed by us rather than by a groundskeeper standing in the dark.
-
Integrate with your systems
Your booking and asset systems connect over documented APIs, so the schedule and the work orders live where your team already works.
What it does not do
-
We are not your bookings system
We connect to the one you have. Replacing it is a different project and usually a worse idea than integrating with it.
-
We do not maintain the grounds
The system tells your crew or your contractor what needs doing and when. It does not mow, resurface or repair anything.
-
This is not a security system
Occupancy counting is not surveillance and the sensors produce no imagery. If you want cameras reading what happens on a site, that is video analytics and a different conversation.
-
We do not quote from a map
What is possible at a site is decided by its power and its connectivity, and neither is knowable from an aerial photograph. Every scope starts with a site assessment.
Common questions
Short answers first.
Can it control more than lighting and irrigation?
Yes, and that is the point of it. Anything with power and a way to be triggered runs on the same controllers and the same portal; the range above is what that covers today.
Does it work with what we already have?
That is the normal case. The controllers sit alongside assets already in the ground and put them under schedule and monitoring without a wholesale replacement. What each site can support is settled in the site assessment.
Is this only for councils?
No. Councils know it as CivicPlay, which is the local government edition of the same platform. It is also run by sporting clubs, schools, golf courses, aquatic centres and the contractors who maintain facilities for other people.
How does it reduce what we spend?
Three ways, and they compound. Lighting and conditioning run to actual use instead of to a fixed timer. Irrigation responds to weather and sensor data instead of watering through rain. And maintenance is dispatched from a fault alert or a usage trend instead of from a rota, so a crew visits the site that needs them.
Do we have to do the whole area at once?
No. Most start with one reserve, depot or precinct, prove it, and extend site by site. There is no minimum footprint and no multi-year programme before the first result.
Who installs and supports it?
Ericom does. Certified electricians and network engineers size the controllers, install and commission them, and the platform is monitored and supported afterwards as a managed service. Support hours are set in the agreement.
Where is the data held?
The data is yours. Australian hosting is available where residency obligations apply, and which arrangement suits you is settled during scoping.
The site you drive to most
The sites the crew visits on a rota, the lights that run to a timer and the doors that need a person with a key are where a scope starts. We assess those sites, check the power and connectivity you already have, and the proposal sets out the hardware, a phased rollout and where the return on energy, water and staff time actually is.
Book a scoping call