With BrightCore @OSTM Network Operating System you can connect to, manage and process data from any remote system which is able to communicate by any of standardized open protocols in an economic way. In few easy steps and with possibility to avoid mayor upfront investment, we can help you and your contractor to build your individual IOT or machine-to-machine (M2M) application on top of @OS with our toolkit, or through eventdriwen SQL database, allowing you to receive benefits of IOT integrated system in less then a month.
What is BrightCore @OS?
BrightCore @OS is a IOT OS with a primary goal to successfully mediate between IOT/M2M and facility automation control networks and their desired uses. BrightCore @OS acts as a two-way information conduit that connects control networks with servers and client programs called Brightlets and Corelets. The actual function and purpose of Brightlets and CoreLetes is not predefined. Generally Brightlets are clients and Corelets are servers. The Shell, an modular software SDK is a gate for 3rd pary appliations into the direct connectio to the rest of BrightCore infrastrucutre. Other way of building application on top of @OS is through connected event driven database.
Thus, your individual IOT/M2M application can be tailor made or purchased from our BookShelf from stock of already available applications and services. The cost effician scalabilty could be accheaved trough our cloud – based approach or through accomodation of your own close infrastrucutre. This is economicaly sustainable regardles do you have few larege sites or lot of small ones with just a few machines geographicaly distributed over large teritory.
Whom does BrightCore @OS address?
The B.@OS is designed for:
- Companies who desire an remote management solution but they can not find one at the market
- Companies who have need for deep IOT/M2M integration into their business process for affordable price
- Companies who have a lot of geographically distributed sites delivered from various contractors
- Companies who have strong development possibilities and are interested in offering Cloud based service to Consumers
B.@OS through its model makes it easy to monetize your ideas:
- Your systems and machines are operated on the site by service personal
- You have few contractors building your site infrastructure and you would like to keep them but put them under same umbrella
- Your current solution is not open and you have big problem to exceed the functionality outside Automation boundaries
- You would like to put your maintenance under control
- You would like to combine data from various internet services into your M2M business model
- You would like to monetize your special knowledge and offer it to the market as a product or service
B.@OS opens possibilities which are currently available just from big vendors as part of their closed systems.
What every industry you are in, Utilities, Trade, Building Management, agriculture, Manufacturing, Transport - BrigtCore could help you to find the right, affordable and extendable solution.
If you can imagine we can make it real.
Example of use
Company deploys elevators globally. With the aim to increase the availability and serviceability of elevators uses customized remote management with direct link to their in-house applications and data.
The elevators now send vital data in real-time with information about functionality and general operating conditions of the elevators.
Service employees can remotely access the systems at any time using graphical interface. Customized reports are created for technical and business use. The systems could be automatically updated with actual software and firmware.
BrightCore @OS Shell SDK
Throughout our business practice we learned that applications share similar requirements. The difference happened with integration to various RDBMS systems.
We developed very unique SDK which aloud to general ICT programmer to use Rapid development toolkit and create new applications and services over M2M NOS. Developed applications could be offered to the market as finished connectable product to @OS or as frameworks. All development could be done in general programming languages like C++, C#, Java, Payton at both platforms Windows and Linux.
Currently available components:
The BrightCore @OS Builder is a program for commissioning, mapping, creating and editing the main BrightCore @OS configuration and object interaction business logic.
The mapping of variables to objects, objects to objects, object definitions and everything vital to the functioning of BrightCore @OS is configured in BrightCore OS @Builder.
The BrightCore @OS 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-defined encapsulated core and it is completely extendable to be sufficiently versatile for today’s continuously changing market demands.
OverWatch - BrightLet
@OS OverWatch is a control-center-type Brightlet – HMI. It enables its user to monitor control networks in four main aspects: Alarms, Trends, Graphics and Time Schedule. 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 configuration. The windows and their configurations are automatically stored in the program’s settings so the user has to adjust the windows only once. It could run at Window, Linux and Android platform.
CoreLets are server applications who could but not have to run at the same machine as @OS.microCore or they could be any ware on internet. The fields’ devices are communicating with CoreLets at the same level. CoreLets are generally not exchanging data with users, they are representing servers who are operate complex Business logic too demanding for regular control device defined behaviors, or are used as event driven real time SQL RDBMS connectivity points for field data.
Alarm CoreLet – Alarm Editor
Alarm CoreLet is server centric application connected to the @OS microCore, accompanied with graphical user interface for Alarm functional distribution. Supports, E-mail sending, SMS notification and as well cascading higher rank officer in case that the alarm is not noticed.
Permition CoreLet – Permition Editor
Permition Editor is Application for user right management it could be extend through Radius and LDAP to corporate Identity management solutions like IBM Tivoli.
Integration with company ICT
Shell SDK ( C++, Java; Windows, Linux)
Client programs can connect to the M2M.NOS.Core and get the information on past object values as the Core stores all object value changes in an internal database. They can also be notified of object value changes as they happen. This traffic also goes through UnifiedControlNetworkProtocol. Client connectivity to the M2M.NOS.Core is handled by the BrightCore client API and SDK - the Shell. The Shell is simple to use, it enables third party vendors to create new BrightCore clients (called BrightLets and CoreLets) tailored to custom specifications. 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 assures wish, without compromising system structure and function. Shell opens window to ICT application to communicate with field devices at the same M2M level.
SQL Database CoreLet
The SQL Database CoreLet is designed for intercommunication between and real time data systems and SQL RDBMS.
It is designed to support full access to data produced by the BrightCore @OS ( alarms, trends, values, system events...), and to transfer data from 3rd party applications and databases back to the BrightCore @OS in real time.
It is constructed as a event driven direct two-way interaction street between BrightCore @OS and different standard RDBMS systems.
It allows the automatic data transfer in real time between the database and the @OS objects and properties, and thus the data transfer between nodes from control networks and the database.
Data from the database input table immediately after their input are passed to the BrightCore @OS, while the data from the BrightCore @OS are instantly being written back to the appropriate output tables in the database.
Linking of tables with the BrightCore @OS is done via Connector feature, which by its flexibility in configuring allows connection of multiple appliance instances to the same database table, both input and / or output.
A number of different database types and the number of instances of the database at the same time connected to the Database CoreLet are not limited, as well the amount of input, output or passive table within each database.
There is built-in mechanism for automatic database as well the required tables with triggers creation directly from Builder Tool database-system-configuration-plug-in.
There is a possibility of additional initialization of tables and settings of additional triggers in the database through database-system-configuration-plug-in.
Currently, there are MySQL and SQLite DAO for connection to the eponymous database.
- Business requirements analyze
- Solution design
- Business modeling
- Business case development
- Business process analysis
- Device and Network integration design
- Operational model selection
Designs and deployment
- Network commissioning
- Business logic creation
- Custom development if needed
- Graphical UI design
- ICT DB design
- ICT integration
- Acceptance tests
- Hosting in-house or data center
- System monitoring
- SLA – based support
- System back up
- Scalable according load
- Add on development or 3rd party support for development of custom applications
Solution consulting and application design Complete consulting from concept to implementation Rapid creation of individual applications Open interface to Open protocols (LonWorks, BACnet, Modbus, SNMP, REST, MQTT) Applications for tablets and Smartphone’s Optimized event driven IOT/M2M traffic (very low bandwidth) Strong encrypted communication - AES 256 real time data Scalable to any size of network and any number of devices Interaction with existing IOT/ICT solutions via open interfaces Simple pricing model through connected devices both as a service and as NOS appliance sales.
1. @OS Appliance purchases
The System could be purchased as appliance in that case customer could purchase appliance with 100.000 MicroUnits base. Appliance has all EdgeDevices include in the price. If there are remote sites the edge device has to be purchased separately
With the appliance comes essential BrightLets and CoreLets, the customer could purchase additional licenses for 3rd party applications both BrightLets and CoreLets
MicroUnit represents multiplication of Object and weight - quantifier
We have following object types:
To get a sense 100.000 MicroUnits represent network of 30 to 50 devices network
It is one time purchase and the consumer could sign maintenance agreement
There are following MicroUnit lots:
- 100.000 MicroUnits
- 50.000 MicroUnits
- 10.000 MicroUnits
- 5.000 MicroUnits
- 1.000 MicroUnits
- 500 MicorUnits
Partner channels are getting discount on MicroUnit list price.
2. Service Model
In case customer do not need @OS and would rather have service model. We are offering hosting under following conditions:
- Service Monthly Fee
- One time Charge for Edge device
- Number of devices connected unlimited
- One tenant
- Users Unlimited o Storage 1GB
- 20.000 events
- Support included 8x5
- Additional tenant
- Additional Edge device
- Additional 1GB of disk space o Additional 1000 events