CoCoS Device Management and Configuration

Introduction

CoCoS began as an interconnection platform, bringing together devices that lacked built-in communication capabilities. While this remains a core function today, CoCoS has evolved into much more. Devices are seamlessly integrated through Connectors, all operating uniformly within the CoCoS environment. This means intelligence can be added using scripts and standardized “things”, without requiring any hardware-specific knowledge.

Connecting everything

The goal of CoCoS is simple: to communicate with everything.
To achieve this, we develop so-called Connectors (also known as interfaces). These Connectors speak the native language of devices outside CoCoS, while inside CoCoS they translate everything into standardized, static or event-driven information.

Even with this powerful standardization, CoCoS remains flexible. It can still process device-specific protocols whenever customers prefer to work with protocol-dependent methods.

No matter the choice—as long as the equipment has documented protocols, CoCoS can connect to it, communicate with it, and automate its tasks.

Changing hardware without configuration and programming changes.

For system integrators, CoCoS offers the freedom to work with well-documented, open technologies such as PHP, JavaScript, and Python to build powerful applications. Even better: a script or application that runs on a Siemens PLC and SIP server will also work on Commend VirtuoSIS and Moxa I/O modules—with no changes required.

Scripts stay the same. Hardware can differ per client. And best of all, the complete CoCoS application remains unchanged—only the Connector (interface) adapts to the hardware.