Nothing today is isolated. Our data are shared across users and systems, where they can be measured and manipulated by other users and systems.
The challenges inherent in designing for interconnected systems is nowhere more apparent than with the Internet of Things. The data path begins and ends with our behavior; the objects in between need to perform and predict according to our expectations. For example, combining our home-to-work schedule and our desire to save time and money are the boundary conditions needed for our thermostats, locks, and maps, as well as the dog walker and delivery services. Each app and item outputs what the next needs for inputs.
Oh, and by the way, often each link in the chain has a completely different owner. After all, your job, car, garage, thermostat, and energy provider are otherwise unrelated. Compatibility is NOT a given.
IoT systems, like DAM and WCM and MDM and CRM, must be constructed for a domain larger than system itself. You need use cases that extend into the entire ecosystem, the entire journey. You need to intelligently design a “data API” that can be leveraged by devices you can’t know much about. Like adapter plugs, data fields are integration fundamentals.
If your system could talk, who would it want to talk to most? Share your thoughts with me at firstname.lastname@example.org.
Originally published at http://www.earley.com/blog/things-modeled#sthash.jX2gKlje.dpuf