Hello Smart Connector Developers,
We have an opportunity here in APAC to include Smart Connector as part of the BMS software specification and then spec it into tender specification. I have tried looking for Smart Connector's specification in the Exchange and in this Community but to no avail.
Our aim is to extract a short summary description (half a page) from Smart Connector's specification, make it sound vendor neutral but still favors/sways to our side and include this extraction as part of the features of our BMS.
Looking forward to replies!
Is this what you are looking for?
Jeff that link doesn't work for me.
@Kevin - You need to watch this video to understand Smart Connector is a framework for building middleware to connect System to Systems together. So for IT you might want to send some data to do with Data Centers from the BMS to the cloud and have some analytics done in the cloud and then some adjustment to set points returned to the BMS to adjust the environment in the Data Center. For this you would use the Smart Connector framework to build a Smart Connector Extension to connect the BMS to the cloud. This Smart Connector Extension would run as a Windows service.
When developing solutions there is frequently a need for software that can bridge the gap between Schneider Electric Building Management Systems (BMS) and third party systems and data sources. This software goes by varying names: protocol shims, glue logic or more generally, middleware. As different projects are analyzed, patterns begin to emerge where this middleware performs similar actions with only minor variations from solution to solution. Smart Connector was conceived to be this middleware framework.
How SmartConnector Works
SmartConnector is an extensible and configurable application framework. At its simplest, SmartConnector is a multi-threaded Windows service. Threads are configured to execute custom Processor code written by solution providers and integrators.
SmartConnector also provides the infrastructure to provision HTTP endpoints. These endpoints can either serve data to Schneider Electric BMSs and third party clients via Schneider Electric’s EcoStruxure Web Services (EWS) SOAP protocol or generic RESTful services.
Watch our short explainer video for more information.
Hope this helps.
First of all, thanks for the link to the PA.
What we are looking for is a generic/vendor neutral description of Smart Connector that we can insert into EBO's specification and spec the whole thing into a tender spec through a consultant. I thought there would be standard specification for Smart Connector that we can extract from.
Maybe something like below, but a couple more paragraphs...
A multi-thread Windows Service that has an extensible and configurable application framework for building middleware for the purpose of 3rd party system integration. It can provision HTTP endpoints and serve data via Web Services SOAP protocol or generic RESTful services.
Bradley Stradtmann do you know of anything existing that we have ready like this?