Internet of Things: “Connected” Does Not Equal “Smart”
"Connected" and "smart" are not synonyms, and bridging the gap takes a lot of upfront work; but with work invested in identifying, understanding and supporting the key decisions, the more productive the data science will be.
The hype is huge around the Internet of Things (IoT) and the Internet of Everything (IoE), but the potential often gets lost in endless discussions about the technologies that underpin the IoT and IoE (sensors, beacons, telematics, fitness trackers, mobile apps, global positioning devices, etc.). Millions of different “connected” devices + massive amounts of data = lots of confusion, unless you first determine what you are trying to do with that wealth of data.
So how do we actually realize business value? How do we get to the “Make me more money” conversation (from the business perspective), or the “Make Life More Easy” conversation (from the ME perspective)?
“Connected” Does NOT Necessarily Mean “Smart”
Being able to capture, store and manage the data created by connected devices and humans creates amazing possibilities. I, like many people, wear a fitness band, which tracks my steps, workout time, sleep, heart rate, and more. But that data by itself isn’t useful unless I apply some analytics to understand what it’s telling me about my health. I want to see trends, outliers, patterns and any other imbalances to help extract the right insights and recommendations to make better decisions about my diet, exercise, sleep, and overall wellness.
Let’s extend this example to the “connected” city, comprised of a wide range of devices (traffic lights, parking meters, weather instruments, etc.) and video cameras (traffic, pedestrian and bike traffic flow) generating data about city operations. A citizen could combine these sensor and video-generated data with other data sources, such as social media (Facebook, Instagram, Yelp) + citizen comments (emails, phone calls) + city reports (police blotters, fire reports, emergency services, construction permits, work orders, building hours, etc.) + local events (concerts, sporting events, farmers markets, parades, festivals, etc.) to create a rich perspective on the city’s activities, problems and overall economic and social vitality.
However, having a “connected” city does not mean that you have a “smart” city. So how do we get smart?
How Do We Get Smart?
Getting smart starts by understanding the city’s key business initiative or business objective (i.e., “what” we want to accomplish). For example, let’s identify and understand the decisions that city management (our key business stakeholder in this example) needs to make to support the business initiative of “Improving traffic flow.” This could include:
- Traffic flow decisions: New roads? New lanes? New turn lanes? New bike lanes? Pedestrian crossings? Railroad crossings? Bus stops?
- Road repair and maintenance decisions: Fixing potholes? Repaving surfaces? Materials and equipment needed? When to fix potholes and repave streets?
- Construction permits decisions: Types of permits needed? Impact on traffic flow? Length of time to complete the work? Number of employees to consider?
- Events management decisions: Traffic (cars and pedestrians) attending proposed event? Impact on normal traffic flow? Date, time, location and duration of events?
- Parks decisions: Location of parks? Size of parks? Hours of operation? Park equipment maintenance?
- Schools decisions: Location and size of new schools? Hours of operations? Location of stoplights and stop signs?
Each grouping of decisions equates into a use case, or the “how” we will accomplish the “what” of the business initiative.
What Data Should I Consider?
Once you know the decisions, the next step is to brainstorm the questions stakeholders need to answer in support of key decisions. This process will help to identify variables and metrics that might be better predictors of the decisions we are trying to make. While most organizations have a good handle on the “descriptive” (What happened?) questions, the business stakeholders struggle with the “predictive” (what is likely to happen?) and the “prescriptive” (what should I do?) questions (see Figure 1).
Brainstorming predictive and prescriptive questions typically uncovers numerous new data sources that are worthy of consideration. And this is a key point: ALLdata sources are worthy of consideration! Do NOT filter the data sources at this point in the process.
Next, we assess the business value and implementation feasibility of each of the brainstormed data sources. This is where we determine 1) the business value and 2) the implementation feasibility (over the next 9 to 12 months) of each of the data sources vis-à-vis the use cases (see Figure 2).