5 requests that go beyond temperature control.
Temperature control is still the main job. But customers now expect more information they can use to decide or act faster.
Customers now expect more from a temperature controller than the temperature value. They want information they can use to decide or act faster. A next generation temperature controller may receive five requests: remote visibility, useful alarms, a short history, integration with other systems and more operating information. Not every request fits every product. Before you add any of them, define who will use the information and what action it should lead to, because information that does not lead to an action adds cost without adding value.
The job the controller already does.
Five requests for your next generation temperature controller
“Can I see the status without going to the unit?”
The controller needs a way to send data. You also need to decide which data to share and who can see it.
“What happened, and what needs attention now?”
A general error message is often not enough. Useful alarms separate urgent problems from problems that can wait. Then the team knows what to do first.
“What happened before the problem appeared?”
Keeping a short history can help service understand what happened before a problem appeared.
“Can the product share useful data with another system?”
Define what information is worth sharing, and check what the other system needs to use it.
“Can the product tell me more than the temperature?”
Temperature may not be the only information the customer needs. Depending on the application, other values or operating information can help the user understand what the product is doing.
Decide what information is really useful
Information only has value if someone understands it and uses it. Before you add information to the controller, check how it will be used.
What happened?
High temperature
What does it mean?
Above limit
What should I do?
Cooling needs attention
Do it now.
Check the unit
If the information does not lead to an action, it may add cost without adding value for the user.
Who uses the information, and what it changes
| Who uses it | What they need | Useful output | Possible impact on the controller |
|---|---|---|---|
| User | Current status and a clear warning | Simple value, status or alarm | Display, alarm logic, local access |
| Service | The reason for the problem and what happened before it | Alarm detail, recent events, selected past values | Event memory, diagnostics, service access |
| Other system | Selected data it can use | Defined data points and status | Communication, integration tests |
The KTS Series is KELD’s new generation of temperature controllers, with an enhanced display, connectivity options and programmable logic for more advanced applications.
Questions about the next controller
What should a next generation temperature controller include?
It depends on who will use the information. Customers now expect more than the temperature value: remote visibility, useful alarms, a short history, integration with other systems and more operating information. Include what the user, service and other systems really need, and what leads to an action. Each addition has an impact on the controller: display, alarm logic, event memory, communication and integration tests.
What does remote monitoring need?
The controller needs a way to send data. You also need to decide which data to share and who can see it. Remote access only adds value if the information that arrives is useful for the person who receives it.
What makes an alarm useful?
A useful alarm separates urgent problems from problems that can wait, so the team knows what to do first. A general error message is often not enough.
Why keep a history in the controller?
A short history, or data logging, helps service understand what happened before a problem appeared. Without it, service only sees the moment of the alarm, not the conditions that led to it.
If you recognise one of these requests in your market
Your next controller does not need every possible function. KELD can help you define what your customer really needs and which functions, information and communications make sense for the application.
See how KELD designs and manufactures custom HVAC and temperature controllers.
