Understanding the IoT/M2M IT ecosphere

IDC analyst Scott Tiazkun confirms that the Internet of Things (IoT) is beginning to coalesce – both in terms of abstract concept and concrete solutions. As such, Tiazkun recommends vendors take the next step by analyzing IoT’s huge IT opportunity in a “more realistic and valuable” framework.

“As exciting as the overall opportunity for the IoT market currently exists, understanding the vertical ramifications is paramount,” he explained.

“All of the greatest IoT IT opportunities – from the connected home, smart meters, the connected car, and smart grid to personal wellness and connected health – are driven from a vertical market perspective.”

According to Tiazkun, the IoT market must be understood in terms of vertical markets, as the value of IoT is based on individual use cases across all markets.

“Successful sales and marketing efforts by vendors will be based on understanding the most lucrative verticals that offer current growth and future potential and then creating solutions for specific use cases that address industry-specific business processes,” said the analyst. 

|

“IoT already impacts our everyday life down to the smallest processes. The vertical opportunity that arises from IoT is already in play, but only if the need for vertical expertise is recognized and offered. Realizing the existence of vertical opportunity is the first step to understanding the impact – and therefore market opportunity that exists – for IT vendors.”

More specifically, IDC expects IoT technology and services revenue to expand from $4.8 trillion in 2012 to $7.3 trillion by 2017 at an 8.8% CAGR, with the greatest opportunity initially in the consumer, discrete manufacturing and government vertical industries.

Similarly, the IoT/M2M market is growing quickly, although the development of this market is not expected to be consistent across all vertical markets. 

For example, industries that already “understand” IoT will experience the most immediate growth, such as industrial production/automotive, transportation and energy/utilities. However, all verticals will reflect great opportunity.

“IoT is a derivative market containing many elements, including horizontal IT components as well as vertical and industry-specific IT elements. It is these vertical components where IT vendors will have to distinguish themselves to address industry-specific IoT needs,” Tiazkun continued.

“IoT opens up many IT vendors to the consumer market, providing B2B2C services to connect and run homes and automobiles — all the places that electronic devices will have a networking capability.

The first step to understanding how vendors can position themselves will be to analyze the components of the IoT/M2M IT ecosphere. Because this is a derivative market, there are many opportunities for vendors to offer parts or product suites that cover the needed IoT IT set. 

Vendors, Tiazkun confirmed, will have incentive to do so due to rapid growth which will occur as industries see the convenience, productivity and efficiency that IoT brings to business processes.

“While horizontal-focused IT vendors will look to offer IoT solutions that appeal to many industries, there will also be impetus to offer vertical-focused solutions that make IoT tangible for both industries applications (M2M) and consumer needs (B2B2C),” he added.

“The IoT market will greatly impact and offer the potential for vertical-aligned businesses to improve both performance and profitability. The IoT solutions space will expand exponentially and offer every business endless IoT-focused solutions. The initial strategy of businesses should be to avoid choosing IoT-based solutions that will solve only immediate concerns and lack ‘staying power.'”

IoT: Connecting 80 billion “things” by 2020

The Internet of Things (IoT) refers to a future world where all types of electronic devices link to each other via the Internet. According to lead IDATE analyst Samuel Ropert, the scope of the IoT is currently quite broad, as it includes communicating devices and M2M.

“[The IoT actually] aims to go beyond M2M by enabling any object to connect and leverage the Internet (Internet of Objects – IoO) even if it does not contain the electronics required to connect directly to the Internet; it connects to the internet with the use of an intermediate device,” Ropert explained.

“[Based on] this definition, 15 billion things (machines, connected devices and objects) were connected to the Internet in 2012, up from 4 billion in 2010. In 2020, there will be 80 billion where IoO will represent 85% of the total IoT, ahead of communicating devices with 11% and M2M with only 4%.”

Indeed, says Ropert, the IoT encompasses multiple and heterogeneous building blocks.

“Underlying M2M and IoO run over different hardware and communication technologies. While RFID and 2D barcodes are used to interact with objects in the IoO concept, M2M application will rely on several different networking technologies that allow the machine to communicate and transmit the data it has generated (or is meant to receive, depending on the application and the machine),” he continued.

“Nevertheless, implementing an open Internet of Things requires a new kind of architecture with scalable naming and addressing (ONS) technologies and new sustainable tools to access the data, as the Internet of Things is designed to browse vast (M2M and IoO) databases.”

Ropert also noted that M2M and IoO are being driven by vertical markets, with the leading verticals in terms of connected objects (IoO) expected to be the pharmaceutical and textile industries by 2020.

Atmel MCUs: High performance for the IoT

Atmel microcontrollers (MCUs) are designed to deliver maximum performance and meet the requirements of advanced applications. That is why our MCUs offer highly integrated architecture optimized for high-speed connectivity, optimal data bandwidth and rich interface support – making them ideal for powering the smart, connected products at the heart of The Internet of Things (IoT).

Essentially, the Internet of Things (IoT) refers to a future world where all types of electronic devices link to each other via the Internet. Today, it’s estimated that there are nearly 10 billion devices in the world connected to the Internet, a figure expected to triple to nearly 30 billion by 2020.

“As applications become more interconnected and user interfaces become richer, microcontrollers must handle and transfer ever-growing levels of data,” an Atmel engineering rep told Bits & Pieces. “To boost performance for these smart, connected applications, Atmel’s 8-bit Flash MCUs integrate a wide range of classic communication peripherals, such as UART, SPI and I2C. Plus, our higher-performance 32-bit MCUs and embedded MPUs (eMPUs) feature Ethernet and full-speed and high-speed USB, while also providing extension ports for external communication modules such as WiFi or cellular modems.”

More specifically, Atmel’s ARM-based SAM9G45 eMPU  boasts high-speed 480 Mbps USB Host and Device Ports with on-chip transceivers, Ethernet MAC and SDIO/SD Card/MMC interfaces – offering developers an easy way to manage large amounts of data and interconnection both between systems and printed circuit boards (PCBs) inside a system. Indeed, the SAM9G45 eMPU is fully compliant with both EHCI and OHCI standards, enabling easy porting of USB host drivers to the SAM9G45.

Similarly, Atmel’s 32-bit AVR and AT91SAM devices are also well-suited for a wide range of standards-based high-speed USB applications. To be sure, the peripheral DMA controller found in the AVR XMEGA and AVR UC3 facilitates efficient data transfers between peripherals and memories with minimal CPU intervention. This eliminates CPU bottlenecks, allowing AVR microcontrollers to achieve transfer rates of up to 33 MBit/s per SPI and USART port with only a 15 percent load on the CPU.

“In addition, Atmel offers a complete line of IEEE 802.15.4-compliant, IPv6/6LoWPAN based, ZigBee certified wireless solutions,” the engineering rep continued. “They are based on our extensive family of RF transceivers, 8-bit and 32-bit AVR, and ARM microcontrollers. As expected, to ease development and speed time to market, Atmel offers a variety of free software stacks, reference designs, wireless modules and development kits.”

In terms of ensuring sufficient data bandwidth, Atmel’s 32-bit MCUs and eMPUs contains a set of parallel data buses where each bus master controls its own dedicated bus connected to all the slaves. This lets the devices support tremendous data bandwidth and removes processing bottlenecks. Atmel 400 MHz eMPUs also feature a high data speedway architecture based on a peripheral DMA (direct memory access) and distributed memory architecture that, together with a multi-layer bus matrix, enables multiple simultaneous data transfers between memories, peripherals and external interfaces without consuming CPU clock cycles.

Meanwhile, select models of Atmel’s 32-bit microcontrollers feature additional SRAM blocks connected to the multi-layer databus or tightly-coupled with the CPU, enabling devices with multiple high-speed communication interfaces to transfer more data by allowing each peripheral to use all of the available bandwidth of any one of the SRAMs. Combined with the peripheral DMA controller, this allows large blocks of data to be transferred with minimal load on the CPU.

It should also be noted that Atmel’s versatile and expansive MCU portfolio can be used to power a wide range of sophisticated interfaces. Examples include industrial applications, such as home and commercial building automation, data loggers, point-of-sale terminals and cash registers, in-house displays for energy metering, alarm systems and medical equipment – all are joining the “smart” revolution currently enjoyed by portable media player and smartphone markets.

So in addition to ubiquitous Internet connectivity, a central aspect of The Internet of Things, the way in which individuals interface and interact with equipment is fundamentally changing. This is prompting hardware designers to increase the processor performance to several 100 MIPS, the peripheral data rates to tens of Mbps and on and off-chip bandwidth to Gbps. As such, the memory size scales with the software to several Mbytes in cases of an RTOS-based implementation or tens of Mbytes for Linux or Microsoft Embedded CE.

Last, but certainly not least, videos are replacing static images. To address this demand, the Atmel SAM9M10 eMPU embeds a high-performance hardware video decoder and 2D accelerator, delivering a high-quality user experience, all while preserving the full processing power of the central processing unit for the application.

“Simply put, we are continuing to build on its legacy of innovation and highly integrated designs, to deliver a solid combination of performance, flexibility and efficiency to support the machine-to-machine (M2M) communications and evolution of the ‘industrial Internet,'” the engineering rep added.

1:1 interview with Michael Koster

Series 3 – Why IoT Matters?

---

By Tom Vu, Digital Manifesto and Michael Koster, Internet of Things Council Member

---

Three-part Interview Series (Part 3)

---

Tom Vu (TV):  Describe how Internet of Things matters? Why should anyone care? Should futurist, technologist, data hounds, product extraordinaires, executives, and  common consumer need to understand what’s to come?

Michael Koster (MK):

There are two main effects we see in the Internet of Things. First, things are connected to a service that manages them. We can now monitor things, predict when they break, know when they are being used or not, and in general begin to exploit things as managed resources.

The second, bigger effect comes from the Metcalfe effect, or simply the network effect, of connecting things together. Bob Metcalfe once stated that the value of a communications network is proportional to the square of the number of connected compatible communicating devices. Since then it’s used to refer to users, but maybe Bob was thinking way ahead. Notice the word compatible. In this context, it means to be able to meaningfully exchange data.

When we connect physical objects to the network, and connect them together in such a way as to manage them as a larger system, we can exploit the Metcalfe effect applied to the resources. We are converting capital assets into managed resources and then applying network management.

Because Internet of Things will be built as a physical graph, it’s socialization of everything, from simple everyday devices to industrial devices. Metcalfe states that 10X connections is 100 times the value.  Cisco is projecting that the Internet of Everything has the potential to grow global corporate profits by 21 percent in aggregate by 2022. I believe these represent a case for pure information on one end, and an average efficiency gain over all of industry on the other.

This has the potential to change things from a scarcity model, where the value is in restricting access to resources, thus driving up price, to a distribution centered model, where value is in the greater use of the resource.  Connecting things to the network is going to reverse the model, from a model of “excluding access” to “inclusion access”, a model where you push toward better experience for consumer/customer/co-business.

Crowdsourcing of things is an example, where models are inverted.  The power arrow is going in the opposite direction, a direction equalizing toward the benefit of the massive body consumers and people.  This in turn, helps shift the business model from a customer relationship managed by vendors, also called advertising, to vendor relationship managed by customers. This is called Vendor Relationship Management, or VRM, pioneered by Doc Searls. This reverses the power arrow to point from customer needs toward business capability to meet needs, and needs are met now that the vendor is listening.  A lot of this is not just IoT but also open source nature, and the big changes happening in people, where sharing being held more valuable than the exclusion of access.

Inverting the value model, breaking down artificially bloated value chains, creating a more efficient economy, I believe it important to create a layer of connectivity that will act as the necessary catalyst to the next Internet of Everything, Internet of Things, Industrial Internet.  Break down the scarcity-based models, exclusion of access, turn it around. Instead of excluding access and driving prices up for limited resources, we will yield higher more efficient utilization of resources.

Michael Koster describing Internet of Things and the Maker Movement and Open Source Importance of this Development with Booth attendees at Maker Faire 2013 in San Mateo

It matters on a Global Scale, by giving us better resource utilization. SMART Grid alone has resulted in up to 19.5% efficiency improvement, with an average of 3.8% improvement over all deployments already. We do not have enough energy storage or transmission capacity to deal with the major shift to solar energy sources now in progress worldwide. We are going to have to adapt, learn, monitor, manage, and control our usage in ways only possible with large scale sensing and control.

For the spirit of IoT, it’s not only in making peoples/consumers lives more convenient, solving their first world problems, but its more in the ability to manage resources together as a larger system, from the individual out to a global scale. Especially, this holds true with the effects of globalization, balancing, localization, connectivity, and ubiquity.  It’s for the people.  Social Media had it’s transformation across many things, Internet of Things will also have an efficiency and business transformation.

Companies like Atmel play an important role in creating the building blocks for embedded control and connectivity by means of progressing the ARM / AVR / Wireless / Touch portfolio of products, all of which are the necessary thinking and connecting glue of the Internet of Things. Internet of Things has a large appetite for ultra low power connectivity using wireless standards.  Wireless Sensor Networks are key technology for the IoT, so much that WSN was probably the number one issue in the early deployment. There are many competing standards: Zigbee, SA100.11, Bluetooth, Body Area Network, Wi-Fi Direct, NFC, Z-Wave, EnOcean, KNX, XRF, WiFi, RFID, RFM12B, IEEE 802.15.4 (supporting WPAN such as ZigBee, ISA100.11a, WirelessHART, IrDA, Wireless USB, Bluetooth, Z-wave, Body Area Network, and MiWi).

Michael Koster Exhibiting with Atmel Booth at Maker Faire 2013 San Mateo

Tom Vu (TV):  What would be the most important design decision that supersedes the eventual success of an open source Internet of Things compliance?

Michael Koster (MK):

The first most important decisions are to do open source design based on needs and use cases. I don’t think we can build an IoT if its not open source, or if it’s not connected to the real world use cases.

Just like the Internet, built on open source and open standards, the starting data models are important for building on and building out. HTML and http and URLs allowed many platforms to be built for the web and supersede each other over time, for example Server Pages, SOAP, Javascript, and AJAX. A browser can understand all of the current platforms because they are all based on common abstractions. We believe that the Semantic Web provides a solid basis of standard web technology on which to base the data models.

Tom Vu (TV):  Describe the importance of Internet of Things silos and other M2M standards currently at large in the development community? What are the differences?

Michael Koster (MK):

The IoT has started off fueled by crowdfunding, VC money and other sources that have to some extent built on a business model based on vertical integration. Vertical integration has a big advantage; you need to have a self-contained development to get things done quickly for proof of concept and demonstration.

Vertical integration is also a big driver of the current machine-to-machine, or M2M, communication market. This is the paradigm supporting the initial deployment of connecting things to services for management on an individual thing basis.

The downside of vertical integration is that it leads to silos, where the code developed for a system, the data collected, and even the user interfaces are all unique to the system and not reusable in other systems. Moreover, the vertical integration is often seen as a proprietary advantage and protected through patents and copyrights that are relatively weak because they apply to commonly known patterns and methods.

It’s not always this way, though. As an example, the Eclipse foundation is open source, allowing their M2M system to be used for vertical application development as well as integrated with IoT Toolkit data models and APIs to enable interoperability with other platforms.

The European Telecommunications Standardization Institute, or ETSI, also has an M2M gateway that is a combination of open source and paid license code. New features are enabled through Global Enablers or GEs that implement a particular function using an OSGi bundle consisting of Java code. The Smart Object API can be built into ETSI through a GE bundle, which will enable an ETSI M2M instance to inter-operate with other IoT Toolkit instances. This is the power of the approach we’re taking for interoperability, which is obtained by adding a Smart Object API layer to the system.

Tom Vu (TV):  Explain horizontal and service interoperability for Internet of Things, why is it so important?

Michael Koster (MK):

Connected things connect through WSN gateways and routers to Internet services that fulfill the application logic for the user. Today, for the most part, each vendor provides a cloud service for the devices they sell, e.g. Twine, Smart Things, or the Nest thermostat. There are also some cloud services that allow any connection, providing an API for anyone to connect, for the purpose of integrating multiple devices. But the dedicated devices mentioned earlier don’t work with the generic cloud services.

Many IoT services today are based on providing easy access to the devices and gateway, with open source client code and reference hardware designs, selling hardware on thin margins, and Kickstarter campaigns. There is typically a proprietary cloud service with a proprietary or ad-hoc API from the device or gateway to the service, and a structured API to the service offering “cooked” data.

These systems contain a highly visible open source component, but much of the functionality comes from the cloud service. If a user wishes to use the open source part of the system with another service, the APIs will need to be adapted on either the device/gateway end or service end, or both. It’s not exactly a lock-in, but there is a fairly steep barrier to user choice.

Internet of Things (IoT) in Silos

There is the beginning of an ecosystem here, where some devices are being built to use existing services, e.g. Good Night Lamp uses Cosm as their cloud service. Other services that allow open API connectivity include Thingworx and Digi Device Cloud. These services all use very similar RESTful APIs to JSON and XML objects, but have different underlying data models. As a result, sensors and gateways must be programmed for each service they need to interact with.

The current system also leaves users vulnerable to outages of a single provider. Even if there was a programmable cloud service that all could connect to that ran user applications, there would be a vulnerability to provider outages. Much better and more robust would be an ability to configure more than one service provider in parallel in an application graph, for a measure of robustness in the face of service outages. Even more, it should be possible to run user application code in IoT gateways, local user-owned servers, or user-managed personal cloud services. Today’s infrastructure and business models are at odds with this level of robustness for users.

In terms of business and business models, a lot of the connection and network infrastructure today was built on a “value chain” model. These are businesses that are built on a model of vertical integration. In these models, value is added by integrating services together to serve one function, hence vertical.  With the Internet of Things, traditional value chains are collapsing down and flattening. There is a bit of a disruption in the business model (services, etc), but also new opportunities emerge to create new Internet of Things services, which is good for business and consumers.

Companies will continue to build out vertical models to specialize in their services. IoT can potentially augment service models with the customer even further and offer creative possibilities of cost savings and experience and deploy more customer centric business fabrics, which will result in better service for consumers.

If companies build their vertically based infrastructure of applications integrating into the IoT Toolkit platform, the basic enablement for horizontal connections will already exist, making it easy to create horizontal, integrative applications based on automatic resource discovery and linkage.

Access to the knowledge can enhance the customer experience and ROI for businesses.  We are at the brink of the new era, where companies and products can arise from the information economy; only now motivation via implicit or explicit engagement is tied to things, assets, information, sensors, education, and augmentation; and everything is more intertwined and involved.

Tom Vu (TV):  Please assume the role of a futurist or even contemporary pragmatist. How does the landscape of Internet of Things fit into that picture for an individual?

Michael Koster (MK):

It goes back to the idea that your life is going to change in ways that we are no longer be driven by the scarcity pressures we experienced as hunter gatherers. IoT will trigger the overall shift from the resource accumulative, to the interaction driven and resource sharing-enjoying model due to the ubiquitous connectivity and the right kind of applications we can use to bring this experience to maturity.

We expect the Internet of Things to be where the interaction moves away from screens and becomes more like everyday life, only more convenient, comfortable, and easy to manage. We’re still looking for the valet, the system that simply helps us manage things to enable us to become more as people.

Tom Vu (TV):  Do you have any insights into how industries like Semi-Conductor can help share the responsibility of making Internet of Things for the People and by the People?

Michael Koster (MK):

Yes, of course, everyone has a part in the build up and build out of Internet of Things.  From business to academia, in the home and across the planet, the march to Internet of Things is inevitable.  Again and again, the familiar signs of disruption are being seen.  We see that happening today with the very first initial releases of connected products.  There is a movement in Makers, with substantial global activity. Which is quite harmonious to open source and open hardware.  This will be even wider spread once critical mass takes effect with products more and more becoming connected and smart via Internet.  The power of the sensor proliferation is akin to Twitter having 10 people registered and using their Social Fabric versus 100s of millions.  The more everyday devices and things are connected, the more the power of IoT will overwhelmingly surface.

It’s only how well we integrate and collaborate together across industry to propel this next phase of Internet to the next level.  Every potential disruptive technology has a turning point.  We are at that point and we are all part of this movement. In turn, the Internet of Things will make better products, a better user experience, and optimized efficiency across all resources. How we decide to apply this technology will make all the difference.

This very notion forces industries to be more aware, efficient, and productive. Sensors and connected devices will help supply chain, manufacturing, research, product roadmaps, experience, and ultimately drive an economy of growth. The enterprise begins to have a visibility, transparency to customers, people.   Ultimate, it’s a true nervous system, connected via an enterprise level to a personal consumer level.

SMART, AWARE, and SENSORY are new enhancements to business to include customer habits and patterns of use, threaded right into the production routine and product design. Internet of Things will help sculpt a more consumer oriented and customer centric world of products. Customers will have direct influence in the manufacturing of individual products and instances of products.  Companies can help by being part of the community, albeit in the field of electrical engineering, design, data, to software development on the cloud.  Internet of Things will have touch points between customers and business as much as the electrical power grids have influence across all business today.

The new ecosystem will have micro scale and agile manufacturing at a level of customization unimaginable today. It’s the next driver for brilliant machines, maybe artisan-machines that work for individuals but still live on the factory floor.

You can work with the developers and work toward expanding businesses that can embrace the development world.  Help build the $50 cell phone or connected devices that bridge fiscal and energy compliance for a better world.

Ride the long tail wave… and the inverted business models…  Make more accessibility to all products and be responsible in accessibility… From crowdfunding or crowdsourcing, like Kickstarter or Makers, someone is going to figure out how a sensor can do more, in a very impactful and human experience paradigm. The new innovations will come from everywhere; from the 14 year old in Uganda who takes apart her cellphone to repurpose it into a medical monitoring device, from the basements and garages of millions of makers and DIY’ers worldwide who have sure genius among them.

It is super important to get the very latest hardware out to the open community so that innovation can be leveraged, taken to new levels of creativity and crowdsource ideation for collaboration and massive cross-contribution. Accessibility, documentation, development, ecosystem for software support for the MCUs are all too important.  Atmel holds building blocks to many of these pieces, combined with their development tools and evaluation ecosystem (Atmel Studio 6, Atmel Spaces, Atmel Gallery) and involvement with Makers and Arduino.

Open Hardware / Open Source will come to be de-facto standards.  Bundle open source along with the open hardware to make it even more accessible and embed rapid guide start for newcomers. Right now a key piece is the Wireless Sensor Net. If there were a good open source WSN available and supported by manufacturers, it could enable a groundswell of connected devices.

Build open source and open hardware educational IoT developer’s kits for ages 8 and up, for high school and college, to hit all levels of involvement and expertise. Support community hackspaces and places (ie Noisebridge) where everyone can learn about the digital world and programming.

We are seeing the leveling out of the development happening in all parts of the world. Radical innovation is happening everywhere. Open Source is helping shape this curvature.  This is the broader whole tide that we are seeing. Pinocchio is one great innovation emerging from Makers and Open Source, then we have IoT hubs such as SmartThings, Thingworx, or Xively (formerly Cosm).  There is a lot of crowdfunding, ideation, blooming of disruptive products looking to change the scene of things to come….
Support open source and open collaboration in everything, to create a culture of sharing and innovation, a culture of synergy in building the Internet of Things together. Involve customers as participants and makers of their own experiences. Make sure everyone has access to the information and support they need to build, maintain, hack, and repurpose their devices over time to promote a healthy ecosystem.

This time innovation is going global. The ideation is happening everywhere. There are many global Silicon Valley type hubs, other metros in the world, as well as global accessibility to the same information. We see startup mentality blossoming across all geo-locations.  Again, Semi-Conductors is contributing, helping pave the back-plane for innovation & connectivity for the development layers on top.  Global village of innovation is coming of age… Now.

 

Also read Part 1 and Part 2 of the Interview Series.

1:1 Interview with Michael Koster

---

Three-part Interview Series (Part 2)

---

Series 2 – IoT Toolkit and Roadmap

Tom Vu (TV):  What is in the roadmap for IoT Toolkit?

Michael Koster (MK):

The IoT Toolkit is an Open Source project to develop a set of tools for building multi-protocol Internet of Things Gateways and Service gateways that enable horizontal co-operation between multiple different protocols and cloud services. The project consists of the Smart Object API, gateway service, and related tools.

IoT Smart Object Structure

The foundation of the platform is purely bottom up, based on applying best practices and standards in modern web architecture to the problem of interoperability of IoT data models. I believe that the practice of rough consensus and running code results in better solutions than a top-down standard, once you know the basic architecture of the system you’re building.

To that end, I created a public github and started building the framework of the data model encapsulations and service layer, and mapped out some resourceful access methods via a REST interface. The idea was to make a small server that could run in a gateway or cloud instance so I could start playing with the code and build some demos.

The next step is to start building a community consensus around, and participation in, the data models and the platform. The IoT Toolkit is a platform to connect applications and a mixture of devices using various connected protocols.  It’s real power lies in its broader use, where it can span across all of our connected resources in industry, ranging from commerce, education, transportation, environment, and us. It’s a horizontal platform intended to drive Internet of Things more widely as an eventual de facto standard, built for the people who are interested in building out Internet of Things products and services based on broad interoperability.

IoT Applications Run on Cloud or On Gateway

We intend to create a Request For Comment (RFC), initiate a formal process for the wider Internet of Things platform and standards.  An community agreed upon process similar to the world wide web that we use today, based on rough consensus and running code, with RFCs serving as working documents and de facto standards that people can obtain reference code, run in their system to test against their needs, and improve and modify if necessary, feeding back into the RFC for community review and possible incorporation of the modifications.

The Internet of Things interoperability platform stands as an ideal candidate, leveraging the power of the open source community’s development process.  In turn, community involvement is taken to a new level, across many fields of discipline, and in many directions. Here is where we can get the most benefit of an agile community.  Crowdsource the development process based on principles of open communication and free of the need for participants to protect interests toward proprietary intellectual property.

We need to build the platform together meshed around the community of Makers, DIY, Designers, Entrepreneurs, Futurist, Hackers, and Architects to enable prototyping in an open ecosystem.  Proliferation then occurs; a diverse background of developers, designers, architects, and entrepreneurs have many avenues of participation. They can create a new landscape of IoT systems and products.

This broad participation extends to industry, academia and the public sector.  We are aiming for broad participation from these folks, build a global platform based on common needs. As a member of the steering committee, when I participated in the IoT World Forum, I heard from the technical leaders of enterprise companies (Cisco and others), research departments, and IoT service providers. They believe an open horizontal platform would be needed to enable applications that span across their existing vertical markets and M2M platforms.

Instead of a top-down approach, where people from corporations and institutions get together in a big meeting and put all their wish lists together to make a standard, we’re taking an overall bottom-up approach, bringing together a diverse community ranging from makers to open source developers, and entrepreneurs. Together with corporations, academia, and public sector, we all will participate in a very broad open source project to develop a platform that can be ubiquitous that everyone can use.

In many ways, this is modeled after the Internet and World Wide Web itself.  As we need to create a more formal standard, it will likely engage with the IETF and W3C. A good example is the semantic sensor network incubator project, which is an SSN ontology that describes everything about sensors and sensing. This enables broad interoperability between different sensor systems and platforms, based on common data models and descriptions. What we want to do is something similar to that, only on a more comprehensive scale and intended for the Internet of Things.

Tom Vu (TV):  Can you take us through a tour of the Data Object model importance and how it yields significance for simple and sophisticated connected devices?

Michael Koster (MK):

The Internet of Things today consists of many different sensor networks and protocols, connected to dedicated cloud services, providing access through smartphone and browser apps. It is rare for these separate “silos” to cooperate or interact with each other.

We abstract the complexity of sensor nets connecting devices and hardware by adding a layer of semantic discovery and linkage. This enables the sensors and actuators on disparate sensor nets to be easily combined to build integrated applications.

The way this works is using a few techniques. First, the different sensor nets are integrated through a common abstraction layer. This works a lot like device drivers in an operating system, adapting different devices and protocols to a common system interface. Only in this case, they are adapted to a common data model.

The common data model for sensor nets is based on the new IETF CoRE application protocol and sensor descriptions. This provides standard ways for common types of sensors to be discovered by their attributes, and standard ways for the data to be linked into applications, by providing descriptions of the JSON or BSON data structure the sensor provides as it’s output.

We use the W3C Linked Data standard to provide web representations of data models for sensor data and other IoT data streams. Linked data representations of IETF CoRE sensor descriptions are web-facing equivalents of CoRE sensor net resources. Linked data provides capabilities beyond what CoRE provides, so we can add functions like graph-based access control, database-like queries, and big data analysis.

Internet Smart Object

Internet of Things Applications are essentially graph-structured applications. By using Linked data descriptions of JSON structures and the meaning of the data behind the representation, we can create applications that link together data from different disparate sources into single application graphs.

Then we enable the platform with an event-action programming model and distributed software components. The common semantic language enables the data sources and software components to easily be assembled and make data flow connections. The result is an event-driven architecture of self-describing granular scale software objects. The objects represent sensors, actuators, software components, and user interaction endpoints.

Interent of Things with FOAT Control Graph

Tom Vu (TV):  Who and what companies should be involved?

Michael Koster (MK):

Whoever wants to participate in the building out of the Internet of Things. The people that use the infrastructure should build it out; the people who want to provide products and services based on interoperability, along with those who provide the backplane of thinking low power microcontrollers / microprocessors, connected sensors, and importantly the network infrastructure.

We want to enable all avenues of participation to allow corporations, academia, policy and standards makers, entrepreneurs and platform developers, makers, and DIY hackers all to be involved in building the platform as a community.

For corporations, we will provide an important role, to build a vendor-neutral platform for data sharing and exchange, an open horizontal platform that will allow the integration of what were traditionally vertical markets into new horizontal markets.

Anyone participating or expecting to participate in the emerging Internet of Things, Internet of Everything, Industrial Internet, Connected World, or similar IoT ecosystems initiatives, could benefit by participating in creating this platform. Companies that provide network infrastructure and want to build in value add can adopt this standard platform and provide it as infrastructure. Companies that want to provide new services and new connected devices that can use the IoT Toolkit to easily deploy and connect with existing resources could benefit.

All companies, organizations, and people that can benefit from an open Internet of Things are welcome to participate in the creation of a platform that everyone can use.

Tom Vu (TV):  How important is Open Source to Internet of Things evolution?

Michael Koster (MK):

I don’t see how the Internet of Things can evolve into what everyone expects it to without a large open source component. We need to go back to Conway’s law and look at it from both the system we’re trying to create and the organization that creates it. Interoperability and sharing are key in the system we want to create. It’s only natural that we create an open development organization where we all participate in both the decisions and the work.

Removing the attachment of intellectual property, changes the dynamics of the development team, keeps things engaged and moving forward solving problems. It’s important for software infrastructure projects like this to remove the barrier to cooperation that arises from the self-protection instinct around proprietary Intellectual Property, or even egoism associated with soft intellectual property, “my” code.

Instead, we turn the whole project into a merit-based system as opposed to being ego driven.  Rather than worry about guarding our property, we are motivated to solve the problems and contribute more to the deliverable. The limits to participation are removed and there is a more rapid exposure of intentions and goals. Engagement and innovation can rule in this environment of deep collaboration.

Tim Berners-Lee said that he was able to achieve the creation of the World Wide Web system because he didn’t have to ask permission or worry about violating someone’s copyright. We are creating the same environment for people who want to build our platform, and even for those who want to build their services and applications on top of the platform.

We are going to create the service enabled layer as open source as well so that any one of the companies can help proliferate the idea and everyone has influence and access to the development of the underlying IoT platform.  If it’s open source infrastructure and platform software, you can make a service on top of that software that can contain proprietary code. With our license, you can even customize and extend the platform for your own needs as a separate project.

Tom Vu (TV):  Describe your work with the EU IoT organization and how you are involved as a voice for the Internet of Things?

Michael Koster (MK):

I work with the IoT Architecture group within the overall EU Internet of Things project. The IoT-A group is closely related to the Future Internet project. They have an Architecture Reference Model describing different features one might build in an IoT platform, a sort of Architecture for Architectures. Since their process mirrors my own design process to a large extent, I found their reference model to be compatible with my own architecture modeling process.

They are conducting a Top-Down activity, stewarding the participation in the architecture and standardization model.  One of the ways I work with IoT-A is to use the Smart Object API as a validation case for the Architecture Reference Model. They are building the reference model top down, and we’re building the architecture bottom-up, based on a common expression of architecture relationships and descriptions.

I am also involved in advocating open source of IoT and building of local IoT demonstrator projects, educating around IoT, open data, etc. as well as user controlled resource access and privacy.  I am providing a voice for open source and open standards, into the standards movement going forward.

Here in the USA, there is not anything like what they have in Europe. Here the process will be to engage corporations and institutions and create a participatory structure that enables fair and open opportunity for influence and access to both the development process and the final products.

Tom Vu (TV):  How important is an open standard – building of an RFC in which all industries can agree upon ultimately serving to a wider scale factors of adoption and proliferation?

Michael Koster (MK):

To simply put it, the construction of a formal RFC is something that describes part of system.  A Request for Comments (RFC) is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.  It is a process or evolution in achieving a more widely adopted standard.  The founders of the Internet created this process, and http, etc are all built using original RFC process from many years ago.

Through the Internet Engineering Task Force, engineers and computer scientists may publish discourse in the form of an RFC, either for peer review or simply to convey new concepts, information, or (occasionally) engineering humor. The IETF adopts some of the proposals published as RFCs as Internet standards.

If the IoT Toolkit platform becomes adopted, it may eventually be as many as 10-12 different RFCs, but it’s important to get people to agree on common first set.  This is the initial phase into a more pervasively used universal standard.  In fact, it’s sort of like a strawman platform.  It’s intent is to describe and collaborate, but also invoke and seek out broader participation…  We are at the stage of putting proposals together over the next few weeks and setting up meetings to talk to many people around collaboration and participation in building an Internet of Things platform.

We believe that an open standard platform for horizontal interoperability is key to achieving the promise of the Internet of Things. Everyone needs to be able to present and process machine information in machine understandable formats on the IoT, just as we humans enjoy commonly understandable web data formats and standardized browsers on today’s WWW. It’s important that developers be able to focus on solving problems for their clients and not waste resources on communication and translation.

Read Part Three to Learn More about Why IoT (Internet of Things) Matters?

Here are Part 1 and Part 2 of the Interview Series.

1:1 interview with Michael Koster

A candid conversation of Internet of Things
By Tom Vu, Digital Manifesto and Michael Koster, Internet of Things Council Member

---

Three-part Interview Series

---

Series 1 – Inspiration and requirements for Internet of Things

Tom Vu (TV):  What inspired you to build the IoT Toolkit and educate the IoT community about data models for the Internet of Things?

Michael Koster (MK):

Michael Koster, System Architect, Open Source Internet of Things, Member of Internet of Things Council

A little over a year ago my partner and I started researching the Internet of Things (IoT), with the idea of creating a system as a sort of “valet” to help manage things in our lives. At the time we lived off the grid, and generated our own energy, maintained our own water system, and spent significant time away from home. We looked at what was available, and there was nothing available in ready-to-use systems that would not require at least a layer of programming to work together in the ways we imagined.

Interoperability between multiple devices is quickly becoming a common feature as people try to build their own ‘Internet of Things’—getting all their smart, devices to be connected to the ‘cloud.’ Once they buy the device on Kickstarter, they can easily enjoy the remote control ability and automation afforded for a while. We found a lot of vendors selling devices that connected to services—services such as the Internet.  Some vendors offered open source clients but still tied the devices to their service. We wanted to pull together devices with multiple services, such as combining the home environmental control, energy management, and water, garden, and livestock automation. This requires multiple devices connected together by algorithms, controlling valves, doors, fans, lights, blinds, batteries, etc.  Very often, the vertically integrated devices and services didn’t allow all the devices to be connected because they weren’t built on a standard that was interoperable.

Soon they started to think about ideas on how they could create new relationships and interactions between devices and humans by integrating devices from two or three of these systems together. They quickly found out connecting the systems were quite complex.

This is becoming more common as people try to build their own Internet of Things. Once they buy the device on Kickstarter, they enjoy the remote control ability and automation afforded for a while. Soon they start to think up ideas about how they could create new relationships and interactions between things and between themselves and things by integrating devices from 2 or 3 of these systems together. They quickly find out that it’s not straightforward.

There is a service, IFTTT (IF This Then That) which has software connectors that hook up to the APIs of some popular IoT services and provides a rule engine to apply simple logic predicates to conditions and generate actions, if this, then that. All well and a good proof of the need, but not sufficient for the general use case.

We then decided to investigate the DIY approach, and started from the bottom, through online resources like Sparkfun and Evil Mad Science. We also used components like Arduino, many of which are driven by megaAVR (ATmega) or ARM Cortex-M3, both are AVR and ARM microcontrollers with a strong open hardware, IDE and ecosystem tied to it. We put together a few networkable connected sensors, like a weather station, environmental sensors, ambient LED displays, and power monitoring. We found it relatively easy to connect these to Xively formerly Cosm, Pachube, for monitoring and recording, and quickly discovered a number of limitations to what we wanted to accomplish.

We discovered the same situation with the vertically integrated systems, that there was no open, standard way to connect many different devices together and build a larger application to manage things together. Some Platform-As-A-Service vendors run rules engines, similar to IFTTT, and other application logic inside their platform, but we were looking for a way that enabled us to choose where we wanted to run the software, particularly in both the cloud service and in a local hardware gateway. This allowed more embedded devices and connected sensors to potentially grow into a larger system without a central hub, where IoT is being driven.

This is important because our network connection was often impacted by weather and other variables. We realized that everyone would be impacted to some degree, even with DSL or cable service. Our experience with frequent service interruptions taught us the importance of being able to tolerate interruptions in the network connection. Even if the network connection could be made reliable enough, the services are subject to outages and “latency events”, which make them unsuitable for critical services without backup.

After a few months of inquiry and investigation, we decided a robust, common way of interacting between all devices and things was a requirement. It felt like the early days of the Internet. Before the web, before the invention of hyperlinking, HTML and the http protocol, there were no common ways for people to interact within a document, such as creating hyperlinks.

The Internet of Things is at a similar stage of development. IoT needs a standard to interact with other machines; the standard enabling software for easier interaction is essential.

A platform that provides a base set of common tools and services, similar to an operating system, is also a requirement for IoT users. This platform would enable them to get started quickly with their IoT ideas.

Accessibility and interoperability were key to enable a user to start building smart, connected devices in the era of the Internet of Things.

It became clear that if we could find a standard way to do what everyone expects the Internet of Things to do, and make it as easily accessible and usable as the web is today, that we could help enable the Internet of Things to scale and evolve into what conceivably is the next stage of the internet.

We studied a number of IoT use cases, collaborated with the IoT community, and began to map out what was needed in a common set of tools everyone could use, share, contribute, distribute, and enhance. We wanted to take what already existed in standards, infrastructure, and system components, and build an open source platform that we, and others, could use to create our own end-to-end IoT systems and products.

In the platform, we wanted to provide machine to machine (M2M) connections from sensors and devices, along with application software, and re-use common data models that can easily span across devices and other IoT data streams to build out a common language for descriptions and connections.

We started this process with Social Media, reaching out to like-minded people on LinkedIn. During our investigation, we learned that the issues we discovered weren’t widely known and discussed. Many people there were using no common tools for IoT.

We realized community learning was required to an already steep learning curve on some technologies like RDF and Linked Data. This was one of the reasons we started this IoT blog series to educate people about semantic data modeling and Linked Data driven APIs. Around the same time, we started the Open Source Internet of Things Meet Up in Silicon Valley to meet other like-minded people and build the community.

The founding principle is to create a community around Open Source and Internet of Things.  The gravitating principles follow two successful fundamentals: community and interoperability.  In fact, the very nature of Internet of Things resonates well with Open Source and Conway’s Law. We want to build a system. Create the structure we envision, based on community and sharing.

 

You can also read Part 2  and Part 3 to learn more about Michael and IoT.

New ARM Cortex-M4 Flash MCU: Advanced Connectivity, Floating Point Unit

Industrial applications–from home and building control to machine-to-machine (M2M) communications to energy management–call for underlying technology with abundant connectivity peripherals, processing power and analog capabilities. Atmel’s newest ARM Cortex-M4 processor-based Flash microcontroller, the SAM4E, delivers on all of these fronts.

• 10/100Mbps Ethernet MAC supporting IEEE 1588, full-speed USB 2.0 device and dual CAN
• More processing power with a maximum operating frequency of 120MHz
• Floating point unit
• Two independent 16-bit ADCs with dual sample and hold, offset and gain error correction, programmable gain amplifier

As with Atmel’s other ARM Cortex-M as well as AVR microcontrollers, the SAM4E devices are supported by the Atmel Studio 6 integrated development platform. A free download, Atmel Studio 6 comes with more than 1,600 project examples that minimize much of the low-level coding for designs. With its integrated Atmel Gallery apps store, you can access a variety of Atmel and third-party embedded software, tools and extensions to support your design process.

Learn how SAM4E microcontrollers can support your next design.

Open Sauce

By Steve Castellotti

CTO, Puzzlebox

North Beach, San Francisco’s Italian neighborhood, is famous for the quality and wide variety of its many restaurants. From colorful marquees scattered up and down Columbus to the hushed, more dimly lit grottos hidden down side streets and back alleys, there is no lack of choice for the curious patron.

Imagine then, having chosen from all these options, you sit down and order your favorite dish. When the plate arrives the waiter places next to it a finely embossed card printed on thick stock. A closer examination reveals the complete recipe for your meal, including hand-written notations made by the chef. Tips for preparation and the rationale for selecting certain ingredients over others are cheerfully included.

Flipping the card over reveals a simple message:

“Thank you for dining with us this evening. Please accept this recipe with our regards. You may use it when cooking for friends and family, or just to practice your own culinary skills. You may even open your own restaurant and offer this very same dish. We only ask that you  include this card with each meal served, and include any changes or improvements you make.”

Sharing the “Secret” Sauce

Having been raised in an Italian family myself, I can assure you that there is no more closely guarded secret than the recipe for our pasta gravy (the sauce). But I can’t help but wonder how such an open sharing might affect the landscape of a place such as North Beach. If every chef was obliged to share their techniques and methods, surely each would learn from the other? Customers would benefit from this atmosphere of collaboration in terms of the taste and quality of their dinners.

These many restaurants, packed so tightly together as they are, would still be forced to compete on terms of the dining experience. The service of their wait-staff, the ambience, and cost would count for everything.

For the majority of customers, knowledge of the recipe would simply be a novelty. In most cases they would still seek a professional chef to prepare it for them. But to the aspiring amateur, this information would contribute to their education. A new dish could be added to their repertoire.

An experienced restaurateur could no doubt correct me on any number of points as to why such a scenario would be a poor business model and never could or should be attempted. But just across town, throughout Silicon Valley and indeed across the globe, in the realm of technology, this exact model has been thriving for decades.

Open Source in the Software World

In the software world, developers have been sharing their source code (the recipe for the programs they write) under licenses similar to the one outlined above on a grand scale and to great success. The Internet itself was largely constructed using open platforms and tools. Mobile phones running Google’s Android operating system are now the most popular in the world, with complete source material available online. And in 2012 Red Hat became the first open source company to achieve a billion dollars in revenue, with customers from IBM to Disney and Pixar among their roster.

The benefits are many. Developers can leverage each others’ work for knowledge and time saving. If you want to build a new web site, there’s no need to write the web server or common routines such as user management from scratch. You can take open versions and start from there. Even better, if you have questions or run into trouble, more likely than not someone else has, too, and the answer is only a search away. Most importantly, if the problem you found indicates a flaw in the software (a bug), then a capable coder is empowered to examine the source and fix it himself or herself. And the result can be shared with the entire community.

There are parallels here to several fields. Similar principles form the basis of the scientific method. Without the sharing of procedures and data, independent verification of results would be impossible. And many discoveries result from iterating on proven techniques. A burgeoning do-it-yourself community, a veritable Maker Movement, has grown around magazines like Make and websites such as Instructables.com. New inventions and modifications to popular products are often documented in meticulous detail, permitting even casual hardware hackers to follow along. Electronics kits and prototyping boards from companies like Arduino are based on Atmel microcontrollers  plus open circuit designs, and are often used to power such projects.

Brain-Controlled Helicopter

Recently, our company, Puzzlebox, released the Orbit, a brain-controlled helicopter. The user begins by setting a display panel to the desired level of concentration and/or mental relaxation they wish to achieve.  A mobile device or our custom Pyramid peripheral processes data collected by a NeuroSky EEG headset. When that target is detected in the user’s brainwaves, flight commands are issued to the Orbit using infrared light. One can practice maintaining focus or a clarity of thought using visual and physical feedback.

Puzzlebox Brain-Controlled Helicopter with Atmel AVR

Beyond novelty, however, lies the true purpose of the Puzzlebox Orbit. All source code, hardware designs, schematics, and 3D models are published freely online. Step-by-step guides for hacking the software and electronics are included. Methods for decoding infrared signals and extending mechanisms to operate additional toys and devices are shared. Creative modification is encouraged.  The goal is to promote the product as a teaching aid for middle and high school sciences classes and in university-level programming and electrical engineering courses.

This business model is itself a bit of an experiment, much like the restaurant described above. There is little preventing a competitor from producing a knock-off and leveraging our own recipes to do it. They might even open their doors just across the street from ours. We’ll need to work hard to keep our customers coming back for seconds. But so long as everyone abides by the rules, openly publishing any modifications of improvements made on our recipe, we’re not afraid to share the secrets of our sauce. We only ask that they include the original material with each dish they serve, and include any changes or improvements made along the way. We’re willing to compete on cost and dining experience. In this way we hope to improve the quality and flavor for everyone.

Puzzlebox with Arduino and Atmel AVR

Openness and The Internet of Things

Today, communities such as Kickstarter and others tapping into the power of openness and crowd-sourcing are fueling a lot of technological innovation.  The next era for enterprise is revolving around The Internet of Things (#IoT), machine-to-machine (#M2M) communications and even the Industrial Internet (#IndustrialInternet).

One strong proponent of innovation and thought, Chris Anderson, is renowned for having his fingerprints and vision on trends as they bloom into movements.  Anderson is committed and energized in this Make-infused world. His latest book, “Makers: The New Industrial Revolution”, eloquently outlines the “right now” moment with makers. “Hardware is the new software”, opening up the brink of the next age of the Internet, where devices and machines become connected. Cloud, agile apps, and embedded design hardware (systems on chips, microcontrollers, or smart devices) are converging and  paving the next generation of integrated products across the fabric of devices.

“The real revolution here is not in the creation of the technology, but the democratization of the technology. It’s when you basically give it to a huge expanded group of people who come up with new applications, and you harness the ideas and the creativity and the energy of everybody. That’s what really makes a revolution.

…What we’re seeing here with the third industrial revolution is the combination of the two [technology and manufacturing]. It’s the computer meets manufacturing, and it’s at everybody’s desktop.”

Excerpt credited from Chris’s Anderson’s “Maker: The New Industrial Revolution”

With that said, we enter the next age, where hardware is the new software.

Smartphones Powering the Internet of Things

Good piece today from Peter Yared, CTO of CBS Interactive, in Venture Beat. Yared’s key point is that smartphones are controlling a greater amount of devices inside–and outside–of the home. He writes, “It is likely that every room of a home will have a 4” or 7” smart device mounted as a control panel for lights, music, and more. Soon, “flipping a light switch” will sound as archaic as “dialing a telephone”.”

Part of what’s making this possible, says Yared, is the underlying technology. From embedded controllers–and we’d count Atmel maXTouch touchscreen controllers in this mix–to easy-to-use, low-cost platforms like Arduino, based on Atmel megaAVR microcontrollers, and Raspberry Pi, these technologies are making it easier and faster to create feature-rich smartphones as well as other touch-based and web-enabled devices. With these robust technologies and a lot of engineering ingenuity, consumers can now bring into their homes unique, smartphone-controlled products, from door locks to home theater systems. The same transformation is happening with today’s vehicles, where manufacturers now have the technology to bring the smartphone experience to drivers.

And this is why so many are calling this the era of The Internet of Things. Before long, according to The Internet of Things proponents, web-enabled devices and products will outnumber people on our planet. More and more of these “machines” will be able to take in data, apply smart analytics and algorithms, and take action, without our intervention.

Have you brought the smartphone experience into your car or home? What types of web-enabled products are most prominent in your life today?

Internet of Things — How Do You Feel About the Role of Machines in Our World?

The “machines” are, indeed, taking over. How do you feel about this?

We’re getting deeper into the era of The Internet of Things (IoT). What we’re seeing–and using–is no longer sci-fi fantasy. In healthcare, the combination of IoT and genomic research is moving us toward more personalized medicine.  On production lines, machine-to-machine (M2M) communications is getting product out the door, quickly and efficiently. In our homes, we can remotely activate a variety of systems–lighting, security and entertainment, just to name a few. And Google, as you’ve probably heard, is testing its self-driving car.

According to Forbes, there are about two Internet-enabled devices for every person in the world today. Analysts expect that by 2025, there will be nearly 50 billion Internet-enabled devices.

Just yesterday, Atmel announced that it is acquiring Ozmo, Inc., a leading developer of ultra-low power Wi-Fi solutions. With this move, Atmel strengthens its product line up to enable the design of smart, connected devices, including those targeted to IoT.

As a design engineer, how do you feel about the opportunities available to use your engineering ingenuity to create Internet-enabled products that are changing the world? And as a consumer, how do you feel about the power that these products now have?