Mistake on this page?
Report an issue in GitHub or email us

From evaluation to production for IoT devices

Beginning an IoT project can be daunting. There are many engineering disciplines to consider: embedded software, cloud software, hardware, radios and so on. You have an idea of what you want to make, including its features and connectivity. Whether it’s a completely new IoT device or a legacy product that you want to securely connect to the cloud, this guide aims to help you through the process.

This guide introduces a proven IoT system, Mbed OS, and several industry best practices, advice and recommendations for optimal performance and security for Mbed OS devices integrated with Pelion Device Management. It follows a chronological design route, and we recommend reading through the guide before starting work, so you can design and build for later stage requiremnts at an early stage.

You don’t have to do it all yourself. If you want help, there are many resources available such as forums, email, workshops, webinars, and our support team. Arm also has a network of approved design partners, who can help at any stage of the journey, from design assistance to managing the entire life cycle including production and supply. They can also help train your team in preparation for your next project.

We look forward to adding your IoT products to the Built with Mbed program.

This content is regularly updated and expanded.

Who this guide is for

This guide is for you if:

  • You want to connect Mbed OS devices to Pelion Device Management.
  • Your devices use the latest versions of Mbed OS and Device Management Client.
  • You plan to go into large-scale production.

Mbed development model

The following model shows the guide's terms and their order:

IoT device development life cycle


This is the first stage of development. You are discovering what's possible, evaluating hardware, software and tools, and beginning the implementation of a working prototype.

Proof of concept

You have a demo-quality product to help you convince your stakeholders of the product's value. You can build your proof of concept using IoT starter kits with minor modifications to help minimize delays.


You are comfortable with the Mbed tools and concepts. You have selected hardware that meets your functionality, connectivity and security requirements, and begun developing a custom hardware form factor based on your findings in the proof-of-concept stage. By the end of this stage, you have a minimum viable product and may have deployed the first devices for field trials.


You are now focusing on securely scaling the product, defining and refining your production processes. You begin to optimize your factory line to program devices and securely inject the required certificates and device parameters. Finally, you test your solution at scale, and use your test results to iteratively improve.


You now have a large scale deployment in place. You focus on maintenance, securely updating the devices in the field and further optimizing the operational production process.

Postproduction (content coming soon)

Depending on your technological choices, you might need to consider what happens to your devices after they have reached the end of their useful life. You may also want to consider transfer of control or ownership.

Quick starts

The first step is to use our quick start guides to:

  1. Connect a device to Pelion Device Management.
  2. Perform remote firmware updates.
Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.