Tag Archives: IoT community

4 reasons why Atmel is ready to ride the IoT wave


The IoT recipe comprises of three key technology components: Sensing, computing and communications.


In 2014, a Goldman Sachs’ report took many people by surprise when it picked Atmel Corporation as the company best positioned to take advantage of the rising Internet of Things (IoT) tsunami. At the same time, the report omitted tech industry giants like Apple and Google from the list of companies that could make a significant impact on the rapidly expanding IoT business. So what makes Atmel so special in the IoT arena?

The San Jose, California–based chipmaker has been proactively building its ‘SMART’ brand of 32-bit ARM-based microcontrollers that boasts an end-to-end design platform for connected devices in the IoT realm. The company with two decades of experience in the MCU business was among the first to license ARM’s low-power processors for IoT chips that target smart home, industrial automation, wearable electronics and more.

Atmel and IoT (Internet of Things)

Goldman Sachs named Atmel a leader in the Internet of Things (IoT) market.

Goldman Sachs named Atmel a leader in the Internet of Things (IoT) market

A closer look at the IoT ingredients and Atmel’s product portfolio shows why Goldman Sachs called Atmel a leader in the IoT space. For starters, Atmel is among the handful of chipmakers that cover all the bases in IoT hardware value chain: MCUs, sensors and wireless connectivity.

1. A Complete IoT Recipe

The IoT recipe comprises of three key technology components: Sensing, computing and communications. Atmel offers sensor products and is a market leader in MCU-centric sensor fusion solutions than encompass context awareness, embedded vision, biometric recognition, etc.

For computation—handling tasks related to signal processing, bit manipulation, encryption, etc.—the chipmaker from Silicon Valley has been offering a diverse array of ARM-based microcontrollers for connected devices in the IoT space.

Atmel-IoT-Low-Power-wearable

Atmel has reaffirmed its IoT commitment through a number of acquisitions.

Finally, for wireless connectivity, Atmel has cobbled a broad portfolio made up of low-power Wi-Fi, Bluetooth and Zigbee radio technologies. Atmel’s $140 million acquisition of Newport Media in 2014 was a bid to accelerate the development of low-power Wi-Fi and Bluetooth chips for IoT applications. Moreover, Atmel could use Newport’s product expertise in Wi-Fi communications for TV tuners to make TV an integral part of the smart home solutions.

Furthermore, communications across the Internet depends on the TCP/IP stack, which is a 32-bit protocol for transmitting packets on the Internet. Atmel’s microcontrollers are based on 32-bit ARM cores and are well suited for TCP/IP-centric Internet communications fabric.

2. Low Power Leadership

In February 2014, Atmel announced the entry-level ARM Cortex M0+-based microcontrollers for the IoT market. The SAM D series of low-power MCUs—comprising of D21, D10 and D11 versions—featured Atmel’s signature high-end features like peripheral touch controller, USB interface and SERCOM module. The connected peripherals work flawlessly with Cortex M0+ CPU through the Event System that allows system developers to chain events in software and use an event to trigger a peripheral without CPU involvement.

According to Andreas Eieland, Director of Product Marketing for Atmel’s MCU Business Unit, the IoT design is largely about three things: Battery life, cost and ease-of-use. The SAM D microcontrollers aim to bring the ease-of-use and price-to-performance ratio to the IoT products like smartwatches where energy efficiency is crucial. Atmel’s SAM D family of microcontrollers was steadily building a case for IoT market when the company’s SAM L21 microcontroller rocked the semiconductor industry in March 2015 by claiming the leadership in low-power Cortex-M IoT design.

Atmel’s SAM L21 became the lowest power ARM Cortex-M microcontroller when it topped the EEMBC benchmark measurements. It’s plausible that another MCU maker takes over the EEMBC benchmarks in the coming months. However, according to Atmel’s Eieland, what’s important is the range of power-saving options that an MCU can bring to product developers.

“There are many avenues to go down on the low path, but they are getting complex,” Eieland added. He quoted features like multiple clock domains, event management system and sleepwalking that provide additional levels of configurability for IoT product developers. Such a set of low-power technologies that evolves in successive MCU families can provide product developers with a common platform and a control on their initiatives to lower power consumption.

3. Coping with Digital Insecurity

In the IoT environment, multiple device types communicate with each other over a multitude of wireless interfaces like Wi-Fi and Bluetooth Low Energy. And IoT product developers are largely on their own when it comes to securing the system. The IoT security is a new domain with few standards and IoT product developers heavily rely on the security expertise of chip suppliers.

Atmel offers embedded security solutions for IoT designs.

Atmel, with many years of experience in crypto hardware and Trusted Platform Modules, is among the first to offer specialized security hardware for the IoT market. It has recently shipped a crypto authentication device that has integrated the Elliptic Curve Diffie-Hellman (ECDH) security protocol. Atmel’s ATECC508A chip provides confidentiality, data integrity and authentication in systems with MCUs or MPUs running encryption/decryption algorithms like AES in software.

4. Power of the Platform

The popularity of 8-bit AVR microcontrollers is a testament to the power of the platform; once you learn to work on one MCU, you can work on any of the AVR family microcontrollers. And same goes for Atmel’s Smart family of microcontrollers aimed for the IoT market. While ARM shows a similarity among its processors, Atmel exhibits the same trait in the use of its peripherals.

Low-power SAM L21 builds on features of SAM D MCUs.

A design engineer can conveniently work on Cortex-M3 and Cortex -M0+ processor after having learned the instruction set for Cortex-M4. Likewise, Atmel’s set of peripherals for low-power IoT applications complements the ARM core benefits. Atmel’s standard features like sleep modes, sleepwalking and event system are optimized for ultra-low-power use, and they can extend IoT battery lifetime from years to decades.

Atmel, a semiconductor outfit once focused on memory and standard products, began its transformation toward becoming an MCU company about eight years ago. That’s when it also started to build a broad portfolio of wireless connectivity solutions. In retrospect, those were all the right moves. Fast forward to 2015, Atmel seems ready to ride on the market wave created by the IoT technology juggernaut.

Interested? You may also want to read:

Atmel’s L21 MCU for IoT Tops Low Power Benchmark

Atmel’s New Car MCU Tips Imminent SoC Journey

Atmel’s Sensor Hub Ready to Wear


Majeed Ahmad is author of books Smartphone: Mobile Revolution at the Crossroads of Communications, Computing and Consumer Electronics and The Next Web of 50 Billion Devices: Mobile Internet’s Past, Present and Future.

IoT’s 7th layer will facilitate scaling and real-time

The spurring growth of the Internet of Things (IoT) has taken rise in business, with a number of startups stemming from the software alley, Maker Movement and crowdfunded space already contributing to the industry. Within idea making and product baking, various origins ferment the constant demand for transparency and community. This reveals strong elements of Conway’s law.

The Internet of Things cannot evolve into what everyone expects it should without the larger open source component. Let’s go back and take a look at Conway’s law.  In perspective of both systems of the individual and organization, we are trying to create and the organization also creates it. Interoperability, integrations and the ability to share across communities hold the vital keys in the system.

An organization looking to build into IoT will need to help mature an open development organization, where we all have the ability to participate in the decisions, code, wiring, funding, and the ramp up of the work. By removing the attachment of intellectual property and changing the dynamics of the development team helps to keep things engaged and promotes the resolve attained by larger communities in moving forward and solving problems.

Partnerships across the breadth of business and enterprise will eventually surface the need to have wider and more comprehensive APIs; these APIs are agile and act as the seamless building blocks for sharing of data and bridging the real-time events into the symphony of various different devices, which can integrate easily into enterprise solutions. The API is the building block and cementing agent for innovative uses of connected devices — the Internet of Things.

For example, partnerships between two companies can quickly enable the creation of smart energy service, opening up opportunities to integrate energy appliances combined with data analytics showing home heating and air conditioning as well as consumer usage. An output like this not only creates added value chain, but also helps unify the customer-centric view for businesses wanting to grow closer with their customers, allowing them choices in their activity and usage.

The connected home market ― even connected consumer devices to energy harvesting ― will all require partnerships between companies, enabling them to deliver a smart energy service that integrates energy devices and appliances with data analytics around air conditioning and home heating systems designed for a device-agnostic platform. The partnership allows pools of expertise (enterprises, startups, or newly-established IoT services) to draw upon energy efficiency algorithms to enhance customers’ home energy use and automation.

Partnerships have already been used to spark and create new services for U.S. households. A growing number of sensors are emerging into the marketplace as well as threading these aggregate sensor results to end-to-end to products/solutions.

PubNub-real-time-IoT

As previously seen on Bits & Pieces, we talk about PubNub. This is a service that is already widely used, distributing traffic to 200 million real-time IoT devices across 14 data centers worldwide, serving 3 millon messages a second all within a ¼ second in latency. That’s close to global real-time one can get with that many tenets/nodes on the cloud. In shear numbers, there are well over 1000s of apps leveraging this solution. In fact, this company has really got big plans for the Internet of Things, as it’s already powering thousands of real-time apps streaming 3 million messages per second to over 100 million devices each month. For example, just take some of their notable customers who are already using their services and technology to scale real-time applications and devices onto their own domain expertise solutions.

Coke_Mirage_Chase_IoT

Coke-Big-Game-VoteApp developers like CBS Outdoor and Coca-Cola are using these integrations with real-time data aggregation transmitted by the sensors to produce some really powerful results. CBS Outdoor integrates sensors on embedded controllers to sync content on real-life digital billboards with online web displays using PubNub. Another IoT integration is found with Coca-Cola enabling friends to chat and annotate live video in real-time on the red carpet at the American Music Awards. The beverage giant has also introduced live voting (“You Decide the Ending”) and IoT experience synchronization using PubNub during their Cokechase.com campaign.

As demonstrated by both Coca-Cola and CBS Outdoor, companies are using/scaling this real-time device connectivity across their services. With their availability of an SDK kits for both Arduino (AVR-based Microcontrollers) and Rasberry Pi, Pubnub is quickly on their way to establishing a hook into the Maker Movement; a class of hackers, crowdfunded makers, creative tinkers, and app coders who can wield the power of this API to help take their ideas from prototype to a product.

cbs-outdoor-iot

This is all done with open code and idea contribution, building a collective number of APIs.

APIs are core to the expansion of IoT. What an inventor needs are the following:

  1. A standard protocol (ie. Restful, CoApp, MQTT, etc)
  2. A set of variables with enough data points to create a sophisticated algorithm that maximizes efficiency or augments information or experience
  3. Arduino SDK (Development and Coding into AVR based Microcontrollers)

nodejs_pubnub_solutionPubnub is enabling their customers to rapidly develop, more importantly, scale real-time applications. Explore solutions to some of these examples they offer ranging from (1) challenges for IoT building, (2) building real-time dashboards to connected devices, (3) bridging devices across networks from lan to wan, (4) connecting the car, and (5) home automation.

Interested in learning more about the Arduino SDK kit? Please visit the PubNub Developer site and then get to IoT exploring. Get ready to jump start the rapid building and connecting of devices for the Internet of Things.

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-2-Maker-Faire-2013-SanMateo-Atmel-Maker-Movement

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-Maker-Faire-2013-SanMateo-Atmel-Maker-Movement

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.

IoT in Silos

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

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

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 CosmPachube, 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.