The B.@OSTM combines unique open source model for edge servers (CoreLets) & clients (BrightLets) with Secure-Close-Source-Communication-Network-Infrastructure (BrightNodes & microCores).
The B.@OSTM uses the ontology concept in integration of dissimilar networks through the abstract object-based control network model. The biggest benefit of such a system is avoidance of gateways (protocol translators). The system does not need rules on how to do mappings between dissimilar protocols any more, since every protocol is mapped just once to abstract representation within a generic control network model.
Having such a common base for all protocols opens up a one-to-one data relationship between dissimilar protocols, as well as one-to-many relationship too. We have single mapping defined, therefore we have moved mapping from technology to ontology (from the variable to the objects) and still we maintain visibility of every networked node from any attitude to all eligible participants.
The extension of the B.@OSTM additional protocols is very simple. Clearly, all integration models that are in use within one protocol fieldbus network could be now extend to the multi protocol domain. Simply one need to bind the data encapsulated into the object from "filedbus1" to "fieldbus2" or from "fieldbus1" to "fieldbusw3". Within B.@OSTM, all that is accomplished through a BrightCore @OS BuilderTM, which is a commissioning, integration, administration and business process management tool aiming to assist in the integration of the M2M, M2S, S2S, and S2C infrastructure, and at the same time it provides a plug-in possibility for 3rd party add-ons developments.
The B.@OSTM brings in a complete “syntactic-semantic notion of network infrastructure,” making it expandable to hundreds of facilities/objects and at the same time preserves the integrity of the local control network infrastructure. In general, the model follows the way of today’s IOT/ICT infrastructure connectivity like LAN, MAN and WAN, incorporating typical Telecom operator philosophy in the automation ECO system.
The main difference is that instead of just routing the information packets (data) through communication links it handles the routing of the content (information) by usage of a common class/objects model.
It is a solution, which can solve large campus integration problems, smart city issues, as well as solving the efficient integration of large geographically distributed multi-vendor automation networks and their secure connectivity to Cloud services by closing all data into the real-time AES 256 envelope.
It works from small embedded devices to 19” servers, from ARM to Intel processor and the user could communicate with the building from Windows, Linux and Android devices.
Within B.@OSTM we can distinguish Technical Users, Consumers, and different sort of Service Providers and Application developers. The technical users are people who manage buildings. The Consumers are people who work in the building (they could just manage the spaces where they are working in for example).
The B.@OSTM is based on the idea of opening facility & M2M automation to IOT/ICT developers, and putting in the same attitude automation devices with specialized IOT/ICT services which could be located anywhere on Internet.
Since, it is designed as an operating system it could be added to any deployed automation network or IOT/M2M automation structure without compromising the delivered solution regardless of the origin (Siemens, Honeywell, Schneider Electric or multivendor network based at any of the standardized automation protocols). This entire automation network space by B.@OSTM will be treated as a separate but combined network and the exchange of data will be possible between these networks at the IOT/M2M level.
The @OSTM currently supports Modbus, BACnet, LonWorks, IEC 60870-5-101, IEC60870-5-104, LoraWan, REST, SNMP and MQTT. It has available following SDKs (C++. Java; both Linux, Windows) accompanied by sample open source applications.
The B.@OSTM opens the possibility to make simple and affordable integration between automation infrastructure
and IOT/ICT applications and services. It is specially suited for management of small facilities (less than 1000m2) or
automated objects, movable or stationer.
The creation of this technology where the devices and networks comply, even if they are produced by different vendors and speak different languages, represents a major move to really open cloud-enabled IOT/M2M systems. And that is exactly what B.@OSTM is able to offer!