Menu
A+ A A-

How does BrightCore compare with the conventional and exiting solutions?

Currently, integration of multiprotocol structures varies. It may use integration of all existing devices as one silo proprietary structure through the use of gateways. Another approach is to establish one of the before mentioned standardized protocols as the master protocol and the rest of protocols are connected to master protocol by a gateway. There are systems that, at the first glance look as if they followed our approach, but upon closer inspection, it is noticeable that they are more complex and could no provide end-to-end information visibility. Therefore, they are not easy to use and they are mostly connected to native equipment protocol through gateways. In all cases, the existence of an open independent application development space is hardly imaginable. When compared to BrightCore, all these approaches are not covering all aspects of multi-facility and multiprotocol integration in full sense as BrightCore does. Other approaches and frameworks do not have simple and extendable Class/Object model as BrightCore does. Furthermore, other approaches require long training before one can use them, whereas BrightCore training is simple since usage of BrightCore commissioning tool “Builder” is mimic database management tools with Javascript engine for class creation. Essentially, most of today engineers who are involved in automation are familiar with this kind of tools.

Some vendors are representing established silo structures. Moreover, we were not able to locate a lot of offering of the free open development kit. Therefore, an independent developer who generally develops universal independent applications usable regardless of the protocol structure in the automation and IoT eco-system cold use BrightCore as one of the interfaces to the underlying networked devices regardless of application protocol used. Furthermore, we were not able to locate anyone with Multiprotocol Commissioning tool with simply open integration space to all of these application protocols, third-party applications, and multi-facility environment.

Gateway approach in talking remotely to the buildings obscures what is really happening at the level of facility network. The networks stay closed as if behind a curtain, and if any problem were at the communication layer, it would be seen when something definitely goes wrong. Therefore, it is not possible to address the root cause; rather the result of malfunction is addressed. However, this approach is always more expensive than treating the root cause. By contrast, BrightCore opens space for Dynamic Fault Detection at both levels, process as well as the network communication level. One of the BrightCore main properties is allowing the control managers to enter the system remotely, at the device level. As the need arises, the control managers can conduct the necessary distance diagnostics in all of the protocols regardless of the facility location... By contrast, other approaches are generally again locking mechanisms for vertical silos automation vendors, just in bigger scale. Any third party application is hardly available at the open market.

Login or Register