Friday, May 20, 2016

Will this become THE platform for IoT-based business processes

This week at Knowledge16 in Las Vegas, ServiceNow made some pretty cool announcements, a few of which are extremely relevant to the IoT space and to my last few blog posts.  The Day 2 keynote from Dan McGee is the best place to see the full details, but I'll give you  may take on it here...

ServiceNow introduced what they call The "Connected Experience".  It's a way for any enterprise to build business processes and workflows on top of the Internet of Things without a custom application for every business process.

The biggest problem with IoT today is that it's often thought of as a big dumping ground for all kinds of data that will be analyzed to find the great insight.  The reality of IoT is that it will be devices that publish specific events and data, which feed a specific business process (or workflow).  Tightly coupled devices & processes.

Today, that business process requires a custom application to be written for the consumption and use of that information, to drive the business process.  Even with the most "agile" and "extreme" development processes, that's a lot of custom apps, interfaces and code to manage which will be slow to develop and expensive to maintain.

The ServiceNow "Connected Experience" provides is a way to build structured workflows and business processes based on subscribing to the events and analyzing that data.  At it's core is a workflow engine, with an application interface for end users to see their tasks, to collaborate and conduct work. This has a modern web app and a mobile interface. Lastly there is an analytics engine to provide more predictive notifications and workflows.  A screen shot from the keynote shows the concepts and workflow in detail...

To make this easier to understand, let's use a couple of examples...  The first one is pretty close to the current ServiceNow business.  There's a server that fails in a branch office for a global bank.  The notification is sent, starting a workflow to repair the server.  The workflow rules notice this server is required for a mission critical app and the bank cannot operate without the application running, which causes and automated escalation process.

This escalation process is driven through notifications and visual task boards in the Connected Experience.  Those applications allow participants to collaborate in the application, including adding new participants and sharing context and knowledge in a structured way.  This is very new and it speeds the process and management oversight by replacing phone calls, emails and chaos with a simple web-mobile interface.

The second thing you can do, by looking into the CMDB is identify other branch offices that are susceptible to this same failure due to similar hardware, firmware and software configurations and trigger a series of workflow tasks to preventatively maintain those servers.  That's the predictive analytics component.

OK, so that's the traditional data center view and it's pretty close to the current world.  What about something a little more in the future of IoT.  A vending machine publishes it's low inventory status, which triggers a restocking action item.  But, the workflow checks the inventory of other machines in the area and cost optimizes the other stocking actions based on a myriad of variables including the driving routes, current inventories, inventory consumption rates, cost of fuel, etc...  The restocking item is updated with the precise inventories needed at each location and a driving map of the precise route the driver should take.

Sure, you could write a custom app for both of these situations, but it's faster to build in a platform fit-for-purpose.  It's also easier for end users to consume many different business processes in a single integrated interface vs. having to use 5-10 different applications.

I see a tremendous and groundbreaking opportunity for this Connected Experience to become THE platform for building business processes on top of any IoT platform and data set.  Time will tell, but it's a compelling vision from a market leader.

Wednesday, May 11, 2016

Disrupting SCADA and Beyond

SCADA or Supervisory Control and Data Acquisition is a system for monitoring and control of industrial processes and complexes from power generation, to heating and ventilation, to manufacturing and beyond.

Today, there are a host of vendors providing these systems and most of them have evolved from massive scale-up systems to smaller collections of networked sub-systems.  But, most of them are large proprietary systems and that are expensive and complicated to deploy.

This means SCADA vendors and the industrial telemetry and automation market is ripe for disruption.  Established vendors are clearly rushing to evolve their portfolios and build a more modern, Cloud and IoT based solution.  But, there is also a startup that has the potential to eat their lunch - Samsara.

What I love about Samsara is the how clean, clear and focused the company is.   Their products are "apple-like" in their elegance and simplicity.  And, they have four very clear initial use cases - Fleet Management, Industrial Monitoring,  Cold Chain Monitoring and Power Monitoring.

They provide a plug-and-play cellular gateway to stream sensor data from the site / vehicle to the Samsara cloud.  This gateway has proprietary software for added security and reliability.  They have applications that run on their cloud and provide visibility to devices and analytics of the data.

They also provide a range of sensors that can send data to the gateway.  These sensors can measure temperature, humidity and shock.  They have power monitors for measuring power consumption and efficiency. Lastly, Samsara can interface with third party sensors to monitor additional devices and data.

It's still early days for Samsara, but they raised $25M from Andreessen Horowitz last year and Marc Andreessen is on their board.  The founding team was behind Meraki, purchased by Cisco for $1.2B in 2012.  They clearly have the people, resources and experience to win.

Their aspiration is to make it so simple to deploy and analyze sensors that they can be broadly deployed for all kinds of use cases.  That is an exciting and big vision.  It's far bigger than disrupting the SCADA space, but that's probably one of the first steps.

Tuesday, May 3, 2016

From Consumer IoT To The Enterprise

Many of the most useful applications and interesting disruptions of the last several years have to do with a combination of the Internet of Things and new cloud-mobile applications.  The initial targets were primarily consumer-based and creators of these new devices and applications were building a new business to go after this space.

Consider four of best known disruptions in the last several years...

In the case of Fitbit and Nest, it's easy to see how they built a new smart device and an application that allows the consumer to control the device and analyze the data.  There is a lot more data being created by these devices than they are exposing to the end user, but a key reason these companies have been successful is that they surface all that data through a consumer-friendly cloud-mobile application that makes sense of the data and solves a customer need.

In the case of Waze and Uber, it's a little harder to see the IoT play because their smart device is not available yet - a car that drives itself or a car that senses traffic, obstacles and police cars.  So, for now, these companies have built applications on both sides.  One to create the data and the other to analyze and surface that data in a useful way.

The things that all four companies have in common is that they built the platform required to run these IoT and cloud-mobile apps, for their specific purpose.  They are building a business around these devices/apps and competing in the war for technology talent capable of building that platform.

As this IoT and cloud-mobile apps disruption is embraced by enterprises, there will need to be a core platform that supports IoT.  We need a new picture that reflects the enterprise and industrial IoT, different from the consumer IoT.

At the core of it is an IoT Data Platform.  This platform would likely cover four areas: Data Capture, Data Management, Data Security and Data Consumption.  Data Capture is a set of interfaces to pull/receive data from the things and send it to the infrastructure to be stored.  Data Consumption is a similar set of interfaces that will allow applications to get access to the data stored and managed by the platform.  Both of these functionality areas need to support broad access and the maximum possible compatibility with devices and application use cases. For Data Capture and Consumption, accessibility and compatibility trump proprietary value-add, so this is an area ripe for open source software and community-driven development.

The Data Management and Data Security layers are to, well, secure and manage this data.  Different data will have different value and different requirements for performance, retention, security, etc...  Data Management and Data Security is an area where technology vendors are likely to build "special sauce" that they want to monetize, so it will be interesting to see if these layers are as readily open-sourced.

Lastly, there needs to be a highly elastic, low cost, high performance infrastructure to power this platform and the data.  That is what people today call "cloud infrastructure", but that doesn't necessarily mean public cloud.  As the traditional infrastructure players build new technologies for this digital world, expect enterprises to choose to mix on-premise cloud infrastructure with off-premise cloud infrastructure to power their IoT deployments.

Some vendors will try to deliver this entire stack from IoT platform to infrastructure.  IBM seems to be headed this way.  Other vendors can offer a compelling solution for one part or the other.  Splunk seems to have a great opportunity in the IoT platform space and GE Predix has launched into this space.  Companies like EMC and Cisco are moving into the Cloud Infrastructure for IoT space.

As IoT grows more mainstream and digital transformation moves to the classic enterprise and industrial companies, this IoT platform space will quickly evolve.