The examples below are at the very-basic end of IWAS's range.

It has a much larger advantage over proprietary-SCADA in hybrid systems that require a sizeable amount and variety of interaction with operators.

We've created Indo / IWAS implementations of production processing encountered earlier elsewhere, and created simulated physical environments for them to operate in. Details here.

As water flows a flow meter generates pulses, and for each pulse the computer it's connected to adds the corresponding volume to the total volume.

Every 60 seconds that meter-computer sends the total volume and the local sensor values to the Base Unit, which then sends them to the server.

On the server the received data is saved and also sent to the graphing module. An alert is generated if data stops arriving.

A few hours after midnight the server can automatically generate a summary of a site's previous-day water use and upload it to a local-government server. That summary and the associated upload transaction log are saved, for audit and diagnosis purposes.

The system can optionally control the water pump(s). For horticulture and agriculture sites, adding one or more soil moisture sensors makes automatic operation possible.

All of the collected data is also saved locally by the Base Unit, and after an Internet outage the data collected during the outage is sent to the server.

Every 60 seconds the Base Unit gets the milk vat temperature and several other sensor values and sends them to the server.

On the server the received data is saved and also sent to the graphing module, and in the graphing module alerting rules are set up. Including ones to generate an alert if the vat temperature is too high for too long, or if data has stopped arriving, or for other abnormalities.

The Base Unit also detects the vat being emptied and adapts accordingly.

All of the collected data is also saved locally by the Base Unit, and after an Internet outage the data collected during the outage is sent to the server.

Therefore support personnel have the best chance of fixing a fault before the vat contents spoil. And the collected data will show whether or not they succeed. So the system may well deliver full payback upon the first such occurrence.

Start by working out your requirements - i.e. What steps need to happen. The above examples should help.

Then send the information to us : Send New System Enquiry

Typically we'll need clarification and more detail, so some to-and-fro is to be expected.

Once your requirements are firm we can assemble a detailed design and generate a quote.

Any information you send us will be handled in confidence. In support of that, our email server always offers to use TLS (transport layer security), and it's authenticated. We also provide key and certificate files to allow you to encrypt your email content. Details here.