Showing 0 products
Frequently Asked Questions
Where does the saving actually come from?
Mostly from stopping units fighting each other.
One unit cools while its neighbour dehumidifies.
Both report themselves as working correctly.
The hall holds temperature and energy is wasted.
Nothing alarms, so nobody notices.
Co-ordination removes it immediately.
What does runtime sequencing achieve?
It spreads wear across the plant.
Without it one unit leads and ages fastest.
Standby units sit unused and seize.
Rotation keeps every unit exercised.
It also evens out maintenance intervals.
Ask how rotation is configured.
Why is the protocol question asked first?
Integration outlives the hardware.
The site already has a management system.
Unreadable equipment becomes an island of data.
That means its own screen and its own login.
Gateways add cost and a failure point.
Confirm compatibility before comparing features.
What should happen if the controller fails?
Plant should revert to local control and continue.
A hall must not stop cooling for a supervisor.
Power loss and network loss differ.
Establish both behaviours separately.
Prove them at commissioning, not on paper.
Specify it rather than discovering it.
Does a small site need one?
Less than a large one, but not never.
One or two units need little sequencing.
Value rises sharply with unit count.
Twenty units is where it repays several times.
Even small sites benefit from central visibility.
Scale the ambition, not the principle.
Can it control liquid and air plant together?
Increasingly it has to.
Halls now run both at once.
Loop temperature and air setpoints interact.
Separate controllers optimise against each other.
Ask whether liquid plant is supported natively.
Retrofitting that later is awkward.
What is worth logging?
Trends, not just current values.
A slow drift is invisible in a live reading.
Trend data diagnoses a failing sensor early.
Export format matters for long term records.
Retention period should be agreed.
Baseline at commissioning for later comparison.