To the Sense Team:
First I’d like to commend the company on an innovative concept. Compared to peers I think you have something innovative compared to other products that monitor circuits without any intelligence. The magic to Sense is the vision that through analytics you’ll be able to break out the the components through electric signature and thus enable a much higher degree of insight than would otherwise be accomplished. In my humble opinion… it simple, innovative and differentiated.
As a brand new Sense owner, I’m going through the same excitement and anxiety as new devices are discovered and then identified by me. It’s been a couple days since install and two devices have been discovered thus far. One I think is accurate and one I think is flagging an impartial load due to its specific almost always on characteristic. In both cases I’ll evaluate, tag and then provide feedback as revelant.
But the process I am going through got me wondering if Sense and the Data Scientists were missing the broader crowd sourcing opportunity. I have seen a lot of topics one training, but haven’t seen anything on our ability to teach. It’s a subtle difference but in the crowd sourcing world it can be huge. I think Sense has an opportunity to make the user community a broad source for information, by giving us rules to provide inputs. I have used this model in the past in corporate America and have never been disappointed with the results when properly structured.
So the opportunity as I see it is as follows: Sense has a engaged community that like me is probably a bit OCD in that we will want to identify and track every single device possible. Heck if I had my way, every non Always On device would be identified and the Always On would be broken out the the 9 or so devices that took 80% of that always on load. But I don’t think I am alone in that desire which is why I believe you have a community that wants to provide the Sense team inputs. You started that with allowing us to identify manufacturer and model information after a device has been discovered, but the real opportunity is for all of us to proved you inputs prior to discovery.
Every one of us has walked around turning devices on and off after installing our first Sense device. We love gaining the insight which is why we bought Sense in the first place. I believe if you provided us rules and the application (web based, app based, email, or other) we would give you far more infomation than you could mine independently, For example if you asked for a clean power signature of a device for five times with manufacturer and model a lot of us would comply in the hopes it would help our personal device discovery as well as others. We could segment the device separately by turning off other circuits and then after running the device the required times, provide Sense the Manufacturer, Model, Sense ID, Start and Stop Times for each run and any additional inputs needed.
Maybe Sense would want more… Maybe less. But the opportunity is lost if you take none. It is not a commitment for identifying those devices, but it does enhance your data scientist abilities to learn and model patterns by providing them an additional input source. Now of course conceptually I have not thought all the components through, but hopefully this will spur some thinking on how to leverage your community a little differently. Crowd sourcing problems can be extremely impactful and that opportunity doesn’t last forever. The window for success is now.