The work sits between an idea and a product decision
A connected energy feature often involves more than the device that performs it. A meter supplies readings, a gateway moves messages, a control rule proposes an action, and an application explains what happened. A fault or misunderstanding can begin at any of those points.
Our proposed engagements examine those relationships. The work might prepare a meter dataset, connect an agreed device interface, simulate a scheduling rule, or prototype the screen a household will use. The scope identifies the question, the material available, and the evidence needed to decide what comes next.
A useful starting point is specific
A manufacturer may need to know whether an application can reliably distinguish a connected device from one that has stopped reporting. A software team may need a consistent daily picture across two different data sources. A pilot organizer may need to know what an operator should do when a household opts out.
Those questions lead to different outputs. We agree the deliverable and its purpose before extending the work. A prototype can support a development decision without being presented as a production service or proof that every home will behave the same way.
Clear responsibilities make the research usable
The client provides the product context, the necessary rights to supplied information, and access to agreed development material. An engagement defines equipment availability, technical access, review responsibilities, and any specialist work needed outside the research scope.
We keep measured observations separate from assumptions and modeled behavior. Installation, certification, utility enrollment, and production operation are separate activities unless expressly included in a written agreement. Company correspondence is based at the Columbus, Ohio address shown below.