The Connected Effect

M2M in the wild: Real World Examples – Part 4 – (The Ecosystem)

Posted by Ian Lee

Jul 12, 2013 2:41:00 PM

Putting together a connected product strategy is not as plug-and-play yet as maybe it should be, but I think there are some strides being taken towards making it a lot simpler for those who wish to build connected machines. For a manufacturer wishing to go it alone, and not rely on the emerging ecosystem of companies who are partnering to provide solutions can be a daunting task. Not only is complexity increasing with the choices you have for devices, the networks and protocols, and the security implications, but there can also be an increase in costs with more applications needed to be developed, more integrations to your ERP or CRM systems, or purely the amount of data that you may be pumping from the devices back to the databases.

hardware picSo why would you build this all by yourself and not take advantage of people who specialize in these areas, and can work together to get your products all chatting on the Internet of Things (or the Machine Cloud as we call it). I worked for a company a few years ago that had a legacy system to do inventory management, and due to rapid acquisition and growth, had to scale that system up. But it was running on older hardware and operating systems, as well as the actual development platform, and it mean that the company effectively had to become their own software house to support that vital product. Going off and building your own is effectively turning you into a software house when that may not be your core capability.

 

Some of the unique things you need to know about when building M2M apps over more traditional enterprise-type software are:

  • Do I need short-haul or long-haul drivers?
  • How do I create embedded agents, message translators of raw data to business information?
  • How do I efficiently organize my data in an M2M data model?
  • How do I cope with queuing, throttling and caching compression of a constant stream of real-time data?

After all, you should really be focused on your business and its future. Improving your product experience, increasing your agility and empowering not only your service and support staff, but as we saw in my last blog, your customers as well.

That’s where the Collaborative Ecosystem comes in. where the 5 main areas of an M2M deployment come together to get your products to market faster than you can do it by yourself. So whether you are building connected products for mHealth, for transportation, for Usage-Based-Insurance (UBI) or for utilities, partnering up with people who have the most knowledge in their area makes the most sense.. after all, would you build your own email system nowadays, do you have software engineers building a credit-card processing application?

The 5 areas are of course;

  • The Network and Connectivity Providers
  • The Hardware and Component Providers
  • The Application Service Providers
  • The Business Systems Providers
  • The Cloud Application and Platform Providers

At Axeda, that ecosystem looks something like this:M2M Partner Ecosystem

And that doesn’t even include all of the device manufacturers in the Axeda Ready Program that is a technical approval program for hardware and module manufacturers in the M2M industry to ensure device compatibility with the Axeda Platform. Programs like this speed time-to-market for multiple devices that can communicate with a platform, and ensures accurate and secure data communication, as well as setting technical support expectations based on their certification. And when those devices are used with an ecosystem network provider, and the applications are written by an ecosystem application provider, the whole process can go a lot faster than trying to do it yourself.

Recently at Axeda’s user conference, Connexion ’13, we had members from each area of this ecosystem, as well as analysts and customers; speak in keynote sessions giving their vision on where the market was going, and how the ecosystem was a strong driver to get there. So I put together a video with highlights from their presentations, to view it, click here:

Axeda Connexion Video

Some of the benefits, as I see it, to joining the ecosystem rather than going it alone are not only that you free up resources to drive innovation, but you also get:

  • Fast time-to-market with new solutions and initiatives
  • Approved security protocols
  • Efficient data communication and machine data processing
  • Built-In business and administration tools
  • Less code to write yourself
  • The flexibility to extend and customize
  • Benefits of input from multiple customers

But that’s just my view; and as I said in my first post, I’m a newbie at all this, so I’m sure some of you will have comments. So add them below and share them with the rest of us. And if in the meantime you want to see someone else's view, check out this recent post on VentureBeat talking about the very same dilemma.

Topics: Internet of Things, M2M Ecosystem

Subscribe to Email Updates