One connected screen for readings, thresholds, alerts and history.
Put the readings from your machines, meters and sensors on one screen. See the current value, the range it should sit in and the person who is told when it goes outside. Downtime and run hours are counted from the same readings, and every number keeps its history. The hardware is selected with you or your vendor. The screen, the rules and the record are what we build.
- Every reading checked against your own gauge before a screen is trusted
- Sensors and gateways selected with you or your vendor and bought in your name
- Continues recording at the site when the network drops and fills the gap later
Readings from machines, meters and sensors land on one screen, which GullySystem builds and sets up as an IoT monitoring dashboard. Operators, supervisors, maintenance and plant heads each see their own sites. It keeps live values, thresholds and alerts, downtime and run hours, and the history behind every reading. Sensors and gateways are chosen with your vendor.
What goes wrong before the software.
How the work flows through it, step by step.
- 1
Deciding what to measure
Walk the plant with your maintenance team to review panels, cable routes, power points and signal coverage. Points not worth instrumenting yet are identified at this stage.
- 2
Sensor selection
We do not make sensors or gateways. The probe, meter and gateway are selected with you or your vendor to suit site conditions, bought in your name and fitted by an electrician who works there.
- 3
Proving the reading
The new sensor runs beside your own gauge for several shifts and the two are compared. If they disagree, the sensor is moved or changed before a dashboard is built.
- 4
Setting thresholds
Your supervisors define what counts as abnormal, how long it must last and who is informed on each shift.
- 5
Working through a network outage
The gateway keeps reading and applying its rules, and sounds the hooter at the panel. Readings are held at the site and uploaded in order when the connection returns.
- 6
Review and export
Shift reviews open on run hours, stoppages with reasons and values outside range. Readings can be exported for quality heads, consultants or engineers.
What is inside.
Every module can be switched on, left out or changed to match how your team already works.
Live values on one screen
Show the current reading per device, grouped by line, plant or site, with the time it last reported.
Learn moreThresholds and duration rules
Set high and low limits, how long a condition must persist and how fast a value is moving.
Learn moreAlerts, acknowledgement and escalation
Send alerts by WhatsApp, SMS, email or panel hooter to the named person on shift. Unacknowledged alarms escalate, and who acknowledged what is kept.
Learn moreDowntime and run hours
Work out running, idle and stopped time from the readings. When a stop crosses the set duration, the operator picks a reason from a short list at the panel.
Learn moreHistory behind every reading
Show trends by hour, shift, day or month, compare two machines or months, and open the readings around any alert.
Learn moreDevice health
Alert when a sensor stops reporting, a battery is low, a gateway loses power or an impossible value arrives.
Learn moreEdge buffering and backfill
Store readings on the gateway when connectivity fails and upload them in order later, with the times they were taken.
Learn moreLocal rules and controlled outputs
Run local actions such as stopping a pump at a set level, a lamp and hooter at the panel or an interlock. Manual override stays at the panel, and every action is logged.
Learn moreEnergy, water and fuel
Read consumption from energy and water meters per machine, line or block, with generator run hours and fuel level.
Learn moreExport for analysis
Provide raw time-series readings for any period as a file or over an API. Retention is agreed before the first device is fitted.
Learn moreRoles, sites and access
Give operators, supervisors, maintenance, plant heads and owners their own machines and locations. Changing a threshold is recorded with a name.
Learn moreCalibration reminders
Schedule comparison against a reference instrument and remind when a sensor is due for verification or replacement.
Learn moreThe business modules it is built from.
Each one is also available on its own, or inside a system built for you.
- Dashboards and KPIs
Operators see the current reading per device, grouped by line, plant or site, along with the time it last reported.
- WhatsApp, SMS and Email Notifications
Alerts go by WhatsApp, SMS, email or panel hooter to the named person on shift, and unacknowledged alarms escalate.
- Roles and Permissions
Operators, supervisors, maintenance, plant heads and owners each see their own machines and locations, and a threshold change is recorded with a name.
- Service Reminders
Sensors are scheduled for comparison against a reference instrument, with a reminder when one is due for verification or replacement.
- Report Builder
Raw time-series readings for any period can be exported as a file or fetched over an API, with retention agreed before the first device is fitted.
- Workflow and Approvals
Each alarm is acknowledged by a named person, escalated if no one responds, and the record keeps who acknowledged what.
How we would put it in.
Setup, data migration, integrations and anything built on top.
Every part of the system, by area.
Take the modules you need. Each one works on its own or inside a larger system built for you.
- Applicant Tracking (5)
- CRM (8)
- Finance & Accounting (10)
- Helpdesk (4)
- Human Resources (13)
- Inventory Management (5)
- Project Management (7)
- Manufacturing (6)
- Procurement (4)
- Sales and Distribution (6)
- Field Service (5)
- Statutory and Compliance (4)
- Retail and POS (4)
- Bookings and Appointments (3)
- Subscriptions (2)
- Assets and Fleet (4)
- Platform (6)
- Analytics (2)
- Documents (1)
- All business solutions
Topics beyond the modules.
Each page covers one part of how the system is used, connected or controlled.
Views by role for plant and facility teams
Operators, shift supervisors, maintenance, plant heads and owners read the same readings, each through the view that suits their work.
Learn moreReports for plant and facility managers
Run hours, stoppage reasons, excursions outside range, energy, device gaps and raw readings are all counted from the same recorded readings.
Learn moreIntegrations for plant monitoring systems
The dashboard reads from PLCs, drives, chillers and meters, and sends alerts by WhatsApp, SMS, email and panel hooter.
Learn moreOne system, each person sees their part.
For shift supervisors
See the screen for your line, the alerts raised on your shift and the acknowledgements you are responsible for at handover.
For maintenance in-charge
See run hours and cycle counts per machine, devices that have gone quiet and the calibration due list.
For plant heads
See downtime by machine and reason, shift against shift, and energy per line.
For owners and facility managers
See every site on a phone, including what went outside range overnight.
For operators at the panel
Choose a stoppage reason when a machine has been down past the set minutes, and keep the manual override.
The numbers the owner asks for.
- Run hours and downtime per machine, by shift
- Stoppage reasons, counted for the month
- Every excursion outside range, with its duration and who acknowledged it
- Condition history against a batch, a consignment or a date
- Energy, water and fuel per machine, line or block
- Devices that stopped reporting, and the gap they left
- Raw readings exported for any period you name
Who this is built for.
- Manufacturers who want machine run hours and stoppage reasons instead of estimates
- Cold storage, dairy and pharma distributors who must show a condition record
- Facility and property teams running pumps, tanks, generators and meters across buildings
- Plants with equipment from several suppliers, each with its own separate app
- Sites where the internet drops often and the record still must not
- Automation firms wanting a monitoring layer above panels they already commissioned
When it is not the right choice.
- Sensors, gateways and panels are not made by us. They are selected with you or your vendor, bought in your name, and fitted on site by an electrician.
- One machine in one room that somebody walks past every hour. Look at it and write it down. That is cheaper than a sensor and a SIM card.
- No uptime or accuracy figure is promised on this page. What a device reads depends on where it is fitted and how it is calibrated, and that is settled on your site.
Adapted to your business before it goes live.
You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.
Works alongside
- Modbus and OPC UA devices
- PLCs, drives and chiller controllers
- Energy and water meters
- SMS and email
- ERP and maintenance software
- Panel hooters and indication lamps
Questions owners ask before a demo.
Does it keep working when the plant internet drops?
Yes, because the rules run on the gateway at the site rather than in the cloud. Readings are buffered locally, the hooter still sounds and an interlock still fires. When the link returns, stored readings upload in order and fill the history.
Do you supply the sensors and gateways?
No. We do not manufacture hardware. Devices are selected with you or your vendor for site conditions and bought in your name. If the portal your hardware supplier already gives you covers most of the readings, tell us what it shows and we will say so plainly.
Can it read our existing PLCs, drives and energy meters?
Usually yes. Modbus, OPC UA, BACnet, RS-485, 4-20 mA and pulse inputs cover most of what sits in a typical plant room. We read alongside the control system rather than into it.
How accurate will the readings be?
No figure is claimed here. Accuracy depends on the device, where it is mounted and when it was last calibrated. We run it beside your own gauge for several shifts, show both sets of numbers and set a calibration reminder afterwards.
Can we export the data for our own analysis?
Yes. Raw readings for any period download as a file, and an API serves them into your own tools. Retention is agreed before the first device goes up.
Can supervisors see it on a phone?
Yes. It opens in a browser on phones and tablets, with each role seeing its own machines and sites. Alerts arrive on WhatsApp or SMS, and acknowledging one from the phone stops the escalation.
Can we bring in the readings we already have?
Exports from an older logger or a spreadsheet load as history with their timestamps. Paper logbooks need a closer look first, since keying in old temperature rows only pays off when someone will chart them.
Does it connect to our accounting package or ERP?
Run hours, downtime and consumption figures can be pushed into your ERP or maintenance software. Accounting software keeps books rather than machine logs, so the usual link is a consumption or production figure agreed with your accountant.
Who owns the devices, SIMs and data?
You do. Devices are bought in your name, cloud accounts stay in your accounts and the readings are yours. Source code and device documentation are handed over at the end of the work.
What does it cost?
No price is published. The figure is set by the points measured, how often each is read, how long readings are kept and how much sits at the edge. Machines to be read over Modbus or OPC UA, and the alert routing to build, add work. Hardware is bought separately in your name. A quotation follows a site visit.
How long before the first screen shows live readings?
A first usable version covers the readings that matter most, with thresholds and alerts on those points, once the machines have been read and the values proved. Downtime, energy and history views follow. The proposal sets out what is included first and gives the dates. Proving the reading comes first.
What does the plant need to prepare ahead of a site visit?
List the machines and points you want measured, with the controllers, drives and meters behind them. Existing readings, panel layouts and the alert rules supervisors follow today help too. Nominate a maintenance in-charge and a shift supervisor to answer our questions. Network access at the site is required. Pain points guide the rest.
Wondering what it would cost? Share your requirements and an engineer will come back with a scope.
Every part, on its own page.
Each page covers one part of the system: what it records, who uses it and what it hands on.
- Live Sensor Values on One Plant Screen
- Threshold and Duration Rules for Plant Alarms
- Plant Alerts, Acknowledgement and Escalation
- Machine Downtime and Run Hours Recording
- Sensor Reading History, Trends and Export
- Sensor and Gateway Health Monitoring
- Edge Buffering When the Plant Link Drops
- Energy, Water and Fuel Monitoring per Machine
- Raw Reading Export and API for Analysis
- Local Rules and Controlled Outputs for Plant Panels
- Calibration Reminders for Plant Sensors
- Roles, Sites and Access for Plant Monitoring
- Views by Role for Plant and Facility Teams
- Reports for Plant and Facility Managers
- Integrations for Plant Monitoring Systems
Built for.
The trades this product is set up for. Pick yours to see how the work runs there.
Related products.
Selling these goods online as well?
These e-commerce pages describe the online side: the storefront, dealer ordering and the connections to a system like this one.
See IoT Monitoring Dashboard set up around your records.
Tell us how you run things today. An engineer reads it and writes back with what fits as it is, what would need changing, and what we would start with.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements