BrightCore
BrightCore is an open building automation software solution platform, not a closed “SCADA” system solution. BrightCore includes the tools for an easy integration, maintenance, supervision and development of new applications, as well object classes. (Prototypes of user-defined constructs, which govern how variable data is processed) The System opens space to ICT professionals by Shell API, who are not necessarily experts in the automation, to build connections to Enterprise class of applications, as well to build special corporate applications like the energy management dashboards. All products developed at the top of the Shell API could be offered to market as separate products. Its focus is the needs of corporations and not the technology. Besides, this technological solution primary helps by connecting devices from the different syntactic and semantic networks.
From the Lonworks point of view Lonworks BrightNode is just another node of the network seen from Management Tool as any other node. Solution could be used for development of: Streetlight. Monitoring solutions, Distributed Enterprise Solutions, Energy management solutions… By the opinion of independent experts this middle ware can fully meet the Sarbanes–Oxley Act - Corporate Auditing and Accountability and Responsibility Act (SOX).
The novelty of the solution is in complete “syntactic-semantic notion of network infrastructure,” making it expandable to hundreds of buildings and at the same time preserving the integrity of the local control network infrastructure. In principle, the model follows the way of connecting ICT infrastructure like LAN and Wide area network, with the difference that instead of routing of just information packets through communication it is handling the content by usage of a class/objects model.
BrightCore is designed as a service and, as such, belongs to the category of “Internet of Things” technology. By the first reactions, we see that it is taken seriously in the circles of Operators who advocates Energy net class of services generally considered as the following stage in the development of the Internet. (Internet of Things)
It is a solution, which could solve large campus integration problems, as well as to efficiently solve integration of large geographically distributed multi vendor building automation networks. BrightCore is built precisely with an idea to reduce the number of people engaged in passive maintenance and to help Outsourcing services control infrastructure and maintain corporate standards.
In the context of this service it is important to say that all companies that have ISO 9001 and ISO 14000 as of 2011 will have to access to certification for ISO 50001 - standard for energy management and without such infrastructure, it will be very expensive task to maintain this standard. It is assumed that this standard will have the influence to 60% of the world energy consumption, which will certainly become very important for global corporations, and therefore such services will become necessity at the market place.
BrightCore is designed with a service infrastructure in mind. Therefore combining the technical systems in buildings with expert’s knowledge is one of its natural tasks. It is suited for such maintenance of a subsystem segment in a corporate environment, so an expert could manage just one subsystem in all facilities but at the same time the Local Control Networks stay intact and act as entity. Consequently, every building could be managed by different automation contractor, and multiple experts could simultaneously monitor various subsystems.
BrightCore is a distributed software system with a primary goal to successfully mediate between control networks and their desired uses. Control networks are in essence structured collections of information and BrightCore acts as a two-way information conduit that connects control networks with client programs called Brightlets. The actual function and purpose of Brightlets is not predefined. BrightCore enables complete customization of Brightlets through the Shell, an API connecting a Brightlet to the rest of BrightCore. The information held in the control networks is structured in variables. This information is processed into values through “objects”, user-defined constructs, which govern how variable data is processed. The mapping of variables to objects, objects to objects, object definitions and all else vital to the functioning of BrightCore is configured in a single program called BrightCore Builder. The BrightCore Builder includes a vector graphics editor for creating interactive graphic representations of variable data. The graphics are handled in Brightlets by the Shell, which has a built-in vector graphic engine. The entire system has a well-defi ned encapsulated core and is completely expendable to be sufficiently versatile for today’s continuously changing market demands.
Structure and Operation
This visual depicts a line of communication from one control network to one client. It encompasses all the elements of the BrightCore system.
Adapters
The problem of polytypic networks is solved with the “adapters.” Each type of network has an adapter, a server which monitors wanted network traffic and converts it to the common protocol - BrightTalk. This selected traffic is then sent to an ObjectCore.
ObjectCore
The ObjectCore (could live in Windows or Linux environment) is a server, which uses the system’s configuration to convert the network variable data to the values through objects. Objects are user defined constructs that are mapped to network variables and other objects in the system’s configuration. Every object has an object class that defines the object’s inputs and how the inputs are processed. The object classes are completely configurable.
Shell
Client programs can connect to the ObjectCore and get the information on past object values as the ObjectCore stores all object value changes in an internal database. They can also be notified of object value changes as they happen. This traffi c also goes through BrightTalk. Client connectivity to the ObjectCore is handled by the BrightCore client API - the Shell. The Shell is simple to use and it enables third party vendors to create new BrightCore clients (called Brightlets) tailored to custom specifi cations. The Shell also supports client network actuation - setting the network variable values. The Shell solves the problem of changing user demands - client programs can be created and modified asusers wish, without compromising system structure and function. BrighCore Builder. The BrightCore Builder is a program used for creating and editing the main BrightCore configuration. Some of its features are highlighted here.
Mapping
The variable-to-object and object-to-object mapping is done through straightforward drag and drop. The program has an interactive error and warnings list to help keep track of empty or invalid mappings.
List of benefits
- Communication with Lonworks network at the M2M level
- Commission of Lonworks BrightNode in LonMaker as regular node
- Reusable vector graphics
- Reusable facility template (Graphics, process, variable behavior)
- Limitedness number of Lon nodes (interconnected Lonworks networks)
- Scalable system to talk to hundreds of buildings
- Open programming Client interface Shell API
- Confi gurable object classes directly in BrightCore Builder
- Heterogeneous system integration possibility of Lonworks infrastructure
- Network router functionally between different BrightNodes
- Fast installation
- Easy maintenance
- Full asynchronous event driven mechanism over INTERNET
- Precise user management (at the level of object)
- Easy connectivity to horizontal and vertical applications (Enterprise resource planning, Energy management, Facility management…)
List of unique and innovative features
- Event driven asynchronous BrightTalk for interconnection between BrightNodes, ObjectCore and BrightLet clients
- Constructed with an idea to manage an arbitrary number of control networks of multiple arbitrary types
- Could work as vertical service from the cloud!
- Easy integration with horizontal and vertical applications
- The Lonworks BrightNode act as peer in control network and the control network will see this node as any other controller node commissioned in Lonworks network.
- Virtual Lonworks node appears in LonMakerTM as one of control nodes of networks
- Works on a top of Windows XP TM, Windows 7 TM & Linux
- Works from DIN rail embedded devices to 19” rack servers
- Integrated web server for configuration (Service pin, reset button…)
- Real time clock
- Inter-operable with LonMaker®
- Compliant with existing Lonworks® routers
- No limitation on network input buffers
- Supports up to 4096 dynamic network variables
- Supports up to 65534 network variables
- Supports up to 4096 network variable aliases
- Supports up to 8192 LonWorks® devices per node
- Supports binding with LBN dynamic network variables
- Supports puling of 65534 network variables from Lonworks net
- Supports binding of 65534 network variables from Lonworks net
- Supports routing with other BrightNodes and control networks beneath
- Supports extended set of address table entries with up to 65535 address table entries!
- Works within Windows and Linux environment
- Affordable SHELL API with full functionally to build OverWatch class of clients
BrightNode
Multiple BrightNode adapters can run simultaneously allowing BrightTalk to interconnect many systems over IP. We can assume every building as one node of infrastructure. Therefore we could have hundreds of Lonworks building connected into the BrighCore and still each one is acting as separate Lonworks network, as well any other control networks (KNX, Modbus, BACnet, etc.. Furthermore, the built-in BrightNode routing service allows data to be transferred from one protocol to another, either on the same altitude system or between altitude systems, across the IP network.
Clearly, the system is constructed with an idea to manage an arbitrary number of control networks of multiple arbitrary types, as well as a system that could work as vertical service from the cloud.
LonBrightNode (LON)
The Lonworks Data Acquisition Server is the adapter that translates LON traffic to BrightTalk. The Node is based at VLD - VirtualLonDevice framework unique fully compliant EIA-852/EIA-709 node framework that provides connectivity of Lonworks networks in M2M style with BrightCore infrastructure. The Node acts as a peer in the control network and the control network recognizes this node as any other controller commissioned in Lonworks network. Furthermore, this virtual Lonworks node appears in LonMakerTM as one of control nodes!
Through the VLD framework Lonworks BrightNode follows EN 14908 family of standard, as well as ANSI/EIA/CEA-709 and EIA 852 tunneling mechanism over IP standards. The node currently runs on Windows XPTM, as well Linux OS. In the future, the node will be ported to XPe, CE, as well. This unique open Lonworks® infrastructure lives entirely in the IP world, and at the same time still keeps compatibility with regular Lonworks® infrastructure. VLD framework brings a possibility of high performance controller applications for EIA-852/EIA-709 networks fully used in Lonworks BrightNode.
Lonworkst BrightNode features:
• Works with Windows XP TM & Linux
• Works from DIN rail embedded devices to 19” rack servers
• Includes a real time clock
• Interoperates with LonMaker®
• Supports EIA-852 fully
• Provides no limitation on network input buffers
• Supports dynamic network variables
• Supports up to 65534 network variables
• Supports up to 4096 network variable aliases
• Supports up to 8192 LonWorks® devices per node
• Supports 65534 binding with LBN dynamic network variables
• Supports 65534 puling of network variables from Lonworks networks
• Supports bridging with other BN control networks
• Supports extended set of address table entries with up to 65535 address table entries.
• It is based on Nstack (Lon stack) and MStack
• It has integrated web server for configuration (service pin, reset button…)
• Developed in c++
• Compliant with existing Lonworks® routers
ModbusBrightNode (Modbus)
The Modbus Data Acquisition Server is the adapter which acts as Modbus Master Device and translates ModbusTCP or J-Bus traffi c to BrightTalk. The Modbus TCP/IP BrightNode creates a powerful connection between devices on a Modbus TCP/IP or J-Bus network as well with other devices on any control network. The node could be instilled on following OS platforms: Windows and Linux, from DIN-rail mounted Devices to big 19” rack servers.
Modbus BrightNode features: • work on a top of Windows XPTM, Linux • based on our MStack ( BrightTalk) • Modbus/TCP master (client) • developed in c++ • real time clock • support up to 1024 ModbusTCP/RTU gateways • support up to 255 ModbusRTU units connected to one ModbusTCP/RTU gateway • work with up to 8192 Modbus devices • individual control of 65534 Modbus registers or statuses
The Modbus TCP/IP BrightNode supports Client and Server connections. The MBN node contains an internal database that consists of areas for application data, status information, and configuration information. For access to Modbus registers or statuses (Coils &Input Discretes) function of conformance class are used: “0” (Read Multiple Registers, Write Multiple Registers) and “1” (Read Input Registers, Write Single Register, Read Coils, Read Input Discretes, Write Coil). For accessing certain register it is possible to determine read function which is supported by device. Registers and statuses could be read in groups for efficiency purposes. The node supports active data reading and writing with Modbus TCP/IP compatible devices.
Modbus Template Editor
Modbus devices are added to BrightCore Builder using templates, which are created by BrightCore Modbus Template Creator. Once created template could be used every time when particular device is needed.
OverWatch
OverWatch is a control-center-type Brightlet – HMI. It enables its user to monitor control networks in three main aspects: Alarms, Trends and Graphics. This is achieved through a modular GUI alongside a main window that only contains a tree of the user’s preferred window links, there are an arbitrary number of other windows the user can adjust to achieve his or her optimal confi guration. The windows and their configurations are automatically stored in the program’s settings so the user has to adjust the windows only once.
BrightCore Demo
Applications:
Multi Building Management Center