Solution Family – Building Energy Systems

FramTack LLC and Net Zero Analysis & Design have developed a revolutionary Learning Energy Control System, (LECS), an energy focused building control system offering typical 25% energy savings to existing buildings with minimal operational impact, and is installed by existing building systems integrators.

The LECS moves all energy control decisions within a building out of traditional devices like timers, thermostats and switches, into an intelligent gateway.  The LECS running on the gateway uses machine learning and external systems, such as facility performance history, current and predictive weather models, and ASHRAE compliant building models, to maximize operational and energy efficiency.

LECS-BuildingOverview

Products

The Solution Family team and Net Zero Analysis & Design have partnered to provided two total energy solutions that together address all major building types.

LECS_256

LECS – Learning Energy Control System – Targeting Buildings 40K sqft and above allowing for control and monitoring of all building systems in a single building solution that optimizes both energy and operations.

LECS_40K_256

LECS-40K – Learning Energy Control System – Targeting Building 40K sqft and below. A focused solution that allows for energy optimization of HVAC, Boiler, domestic hot water(DWH) and lighting systems in a single low cost solution.

Partnership

NetZero_Black

The Solution Family, a leader in advanced learning energy controls and Net Zero Analysis & Design, a national leader in building energy modeling have partnered to provided the Learning Energy Control System, a total energy solution that combines, learning, advanced controls and building models to minimize energy consumption, guarantee operations and provide advanced maintenance diagnostics at price points that eliminate any barriers to installation.

  • Smart Devices are not IoT

    Today I read an article on re/code describing a talk at TED that was supposedly about the Internet of Things.  The primary example given was that of an air conditioner that "learns" in order to provide you with lower costs and more accurate environm...

    0 comment(s).

  • Sensors to Severs: Meeting 3 Presentation

    I just completed my presentation of Meeting #3 of the Sensor to Servers initiative.  If you missed it, were unable to get Lync to cooperate, or if you simple want to view the slide deck, it is available directly here or over on the Downloads page....

    0 comment(s).

  • SDK Code Updates

    I've made a significant number of changes to the C# Hosting SDK.  The previous version had the JSON and XML hosts interned in a Hosting assembly.After thinking about it more, I decided that wasn't the best idea I've ever had - it would be nice t...

    0 comment(s).

  • Help Wanted

    Since implementing a new Protocol is a lot of work, and since we want IoTCM to reflect a wide array of vertical markets and use cases, we'd love to get some volunteers to help build things out.The first stop is to take a look at the Implementatio...

    0 comment(s).

  • Codeplex Project is Live

    The source code for the IoTCM SDKs and reference implementations will be housed in a Git repository on Codeplex.  The IoTCM Codeplex project is now live and there is actually some code already in it.Bear in mind that the code is very much at a p...

    0 comment(s).

  • Sensors to Servers: Meeting 2 Presentation

    We started presenting the status of this project last month in an online webcast through Microsoft as part of a "Sensors to Servers" initiative.  Today I gave the second presentation, which provides a lot more detail on what IoTCM is all about, the ...

    0 comment(s).

  • Welcome

    Welcome to the Internet of Things Connection Model (or IoTCM) Web Site.  In the coming weeks and months we will be pushing forward a protocol definition for how Internet of Things devices should communicate with one another in order to simplify buil...

    2 comment(s).

  • Smart Devices are not IoT

    Today I read an article on re/code describing a talk at TED that was supposedly about the Internet of Things.  The primary example given was that of an air conditioner that "learns" in order to provide you with lower costs and more accurate environm...

    0 comment(s).

  • Sensors to Severs: Meeting 3 Presentation

    I just completed my presentation of Meeting #3 of the Sensor to Servers initiative.  If you missed it, were unable to get Lync to cooperate, or if you simple want to view the slide deck, it is available directly here or over on the Downloads page....

    0 comment(s).

  • SDK Code Updates

    I've made a significant number of changes to the C# Hosting SDK.  The previous version had the JSON and XML hosts interned in a Hosting assembly.After thinking about it more, I decided that wasn't the best idea I've ever had - it would be nice t...

    0 comment(s).

  • Help Wanted

    Since implementing a new Protocol is a lot of work, and since we want IoTCM to reflect a wide array of vertical markets and use cases, we'd love to get some volunteers to help build things out.The first stop is to take a look at the Implementatio...

    0 comment(s).

  • Codeplex Project is Live

    The source code for the IoTCM SDKs and reference implementations will be housed in a Git repository on Codeplex.  The IoTCM Codeplex project is now live and there is actually some code already in it.Bear in mind that the code is very much at a p...

    0 comment(s).

  • Sensors to Servers: Meeting 2 Presentation

    We started presenting the status of this project last month in an online webcast through Microsoft as part of a "Sensors to Servers" initiative.  Today I gave the second presentation, which provides a lot more detail on what IoTCM is all about, the ...

    0 comment(s).

  • Welcome

    Welcome to the Internet of Things Connection Model (or IoTCM) Web Site.  In the coming weeks and months we will be pushing forward a protocol definition for how Internet of Things devices should communicate with one another in order to simplify buil...

    2 comment(s).

Putting Device Intelligence Where it is Needed