April 25, 2017
AMQP, Analytics, Azure, Azure IoT Suite, Cloud Computing, Cloud Services, Cloud to Device, Communication Protocols, Connected, Connectivity, Device to Cloud, Emerging Technologies, HTTP 1.1, Identity of Things (IDoT), Intelligent Cloud, Intelligent Edge, Internet of Things, IoT, IoT Central, IoT Devices, IoT Edge, IoT Hub, IoT Privacy, IoT Security, Machines, MQTT, PaaS, SaaS, Stream Analytics
Microsoft has today released their IoT SaaS offering for customers and partners called as “Microsoft IoT Central”. IoT Central enables powerful IoT scenarios without requiring cloud solution expertise and also simplifies the development process and makes customers to make quick time to market solutions, making digital transformation more accessible to everyone without overhead of implement solutions end to end.
As per Microsoft :
“IoT Central provides an easier way to create connected products that propel digital business. Take the complexity out of the Internet of Things (IoT) with a true, end-to-end IoT software as a service (SaaS) solution in the cloud that helps you build, use, and maintain smart products.”
Benefits of IoT Central:
- Proven platform and technology with enterprise grade security.
- Reduced complexities of setting up and maintaining IoT infrastructure and solutions.
- Building smart connected products with lesser cost and lesser overhead would ensure higher customer satisfaction.
- Quickly adapt to changing environments.
For those would need control on implementing end to end can still choose the PaaS solution Azure IoT Suite.
Below is a picture from @JanakiramMSV’s article from forbes.com, to help you have a high level look at all the IoT offerings from Microsoft.
January 7, 2017
Analytics, Azure, Azure SDK, Cloud Computing, Communication Protocols, Contrained Networks/Devices, Data Collection, Data Integration, Emerging Technologies, Identity of Things (IDoT), Internet of Things, Interoperability, IoT, PaaS, Performance, Predictive Analytics, Predictive Maintenance, Realtime Analytics, Reliability, Scalability, Self Driven Cars, Solutions, Stream Analytics, Tech-Trends, Windowz Azure
Microsoft Azure IoT Suite Provisioned solutions will help you create your own fully integrated solutions tailored for your specific needs in the following 3 sections. Using these ready to consume solutions will accelerate your time to market IoT(Internet of Things) requirements.
- Remote Monitoring – Connect and monitor your devices to analyze untapped data and improve business outcomes by automating processes. For ex: As a car manufacturing company, provide an option to customer to remotely monitor their car condition, and suggest if they need a re-fuel or oil change.
- Connected Factory – Anticipate maintenance needs and avoid unscheduled downtime by connecting and monitoring your devices. For ex: As a car manufacturing factory and spare parts are essential for car manufacturing. Automated solutions can ensure timely availability of necessary spare parts inventory to meet daily, weekly or monthly manufacturing needs.
- Predictive Maintenance – Connect and monitor your factory industrial devices for insights using OPC UA to drive operational productivity. For ex: As a car service support, you can get near real-time performance data from the cars manufactured by your company, predict the health of each components in a car and offer timely maintenance to their cars. Send real-time reminders and notifications to customers. Their by ensuring higher satisfaction levels for customers and more business value to the organization as it attracts more sales and good customer feedback.
These solutions will help you to:
Connect and scale quickly – Use preconfigured solutions, and accelerate the development of your Internet of Things (IoT) solution.
Analyze and process data – Collect previously untapped data from devices and sensors, and use built-in capabilities to visualize—and act on—that data.
Integration and Digital Transformation – Easily integrate with your systems and applications, including Salesforce, SAP, Oracle Database, and Microsoft Dynamics, making it simple to access your data and keep your disparate systems up to date.
Enhanced security – Set up individual identities and credentials for each of your connected devices—and help retain the confidentiality of both cloud-to-device and device-to-cloud messages.
December 9, 2016
.NET, AMQP, Analytics, Azure, C#.NET, Cloud to Device, Communication Protocols, Connected, Connectivity, Contrained Networks/Devices, Device to Cloud, Device Twin, Emerging Technologies, Geolocation, HTTP 1.1, Identity of Things (IDoT), Internet Appliance, IoT, IoT Hub, IoT Privacy, IoT Security, KnowledgeBase, machine-to-machine (M2M), Machines, Microsoft, MQTT, Stream Analytics, Visual Studio 2015, Visual Studio 2017, Visual Studio Code, VisualStudio, VS2015, VS2017, Windows, Windows 10, Windowz Azure
IoT Hub is a fully managed service from Microsoft Azure as part of Azure IoT Suite that enables reliable and secure bi-directional communications between millions of IoT devices and your solution back end.
Azure IoT Hub are designed to provide following capabilities:
- Multiple device-to-cloud and cloud-to-device communication options, including one-way messaging, file transfer, and request-reply methods.
- Built-in declarative message routing to other Azure services.
- A queryable store for device metadata and synchronized state information.
- Secure communications and access control using per-device security keys or X.509 certificates.
- Extensive monitoring for device connectivity and device identity management events.
- Provides device libraries for the most popular languages and platforms.
IoT Hub and the device libraries help you to meet the challenges of how to reliably and securely connect devices to the solution back end.
Real-world IoT devices mostly have the following constaints:
- Embedded systems.with minimal or no user interaction.
- Remotely available, with less physical access. .
- Reachable through the solution back end.
- Limited power and processing capabilities
- Intermittent, slow, or expensive network connectivity.
- Use proprietary, custom, or industry-specific application protocols.
- Created using a large set of popular hardware and software platforms.
IoT Hub provide solutions to meet all the above constraints of a connected device. In addition it also provides scale, scalability and reliability. It also addresses most of the connectivity challenges through following capabilities.
- Device Twin: With Device twins, you can store, synchronize, and query device metadata and state information, and these are stored in JSON format. IoT Hub persists a device twin for each device that you connect to IoT Hub. This feature was introduced in Novemeber’16 with General availability of Iot Hub.
- Per-device authentication and secure connectivity. You can provision each device with its own security key to enable it to connect to IoT Hub.There by enabling you to manage or block devices as desired.
- Route device-to-cloud messages to Azure services based on declarative rules. IoT Hub enables you to define message routes based on routing rules to control where your hub sends device-to-cloud messages.
- Monitoring of device connectivity operations. You can receive detailed operation logs about device identity management operations and device connectivity events.
- Support for latest and widely used IoT protocols and provides extensibility: Protocols such as AMQP 1.1 or HTTP 1.1 and MQTT 3.1 are supported. We could also provide additional protocol translation using Azure IoT Gateway SDK at Device/Field/Protocol Gateway layer.
Azure IoT Hub can bring more value to organizations to bring in their field devices to cloud with real-time data capture and bi-directional communication. It solves the problem of lack of proper communication infrastructure for devices to communicate or operate on real-time basis. Pay per use, less investment infrastructure that would let you scale as you grow.
Do you feel some similarities between IoT Hub and Event Hubs service already exists as part of Azure Platform? In my later articles I would be covering some of the major differences.