Edge Computing Implementation

Edge computing implementation covers gateway selection, local rule logic, power and mounting, remote updates and a commissioning test. The gateway sits in a panel, polls devices and keeps working when the network is down.

Share your requirements

Choosing and placing the gateway

Hardware is chosen for the conditions in that room and not from a catalogue page. Standard parts that can be bought again locally are preferred.

The environment

Panel temperature, dust, vibration and whether anything is washed down decide the enclosure and the mounting, and each is checked on the site visit. Nothing is assumed.

Ports and load

The number of devices, the protocols and the polling interval are counted first, because a gateway polling a hundred registers carries real load.

Power

A DIN rail supply sits on a circuit that stays up. Where cuts are routine, a small UPS is added.

Rules that run on the gateway

Local logic is written so that whoever inherits it can read it. The person maintaining it later may not be from GullySystem.

Node-RED or code

Flows handle straightforward rules, and written services handle heavier logic. Both are documented and kept under version control.

Store and forward

A local queue survives restarts, and uploads keep their order. Duplicates are removed on arrival, so the record holds each reading once. Nothing is counted twice.

Remote configuration

Thresholds and intervals are changed from the application without a site visit, and every change is logged.

Commissioning tests

A deployment is accepted on evidence, and the tests below are run in front of you before operations depend on the gateway. Each has a pass or fail result.

Pull the cable

The link is disconnected deliberately, and the gateway is shown still firing alarms and still keeping readings.

Cut the power

The gateway is restarted mid run to show that nothing buffered is lost.

Parallel log

Gateway readings from several shifts are compared against your manual register before the register is retired.

FAQ

Frequently asked questions

How long does an edge computing implementation take on one site?

It depends on panel access and the number of points involved. The parallel run adds a few shifts by design. A plan is given after the site visit.

Can gateway software be updated remotely afterwards?

Yes, over a secure tunnel or VPN, with a record of what changed and when. Sites with no route in tend to go stale, so remote access is set up at commissioning.

Who owns the gateway and the SIM?

You do. Hardware is bought in your name, SIMs are on your account, and the configuration and source code are handed over with the wiring documents.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

No obligation
A reply within one business day
Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements