DAY11-Introduction To Microsoft Azure
DAY11-Introduction To Microsoft Azure
of
Things
Master Class
Day 11
M.K.Jeevarajan
www.pantechsolutions.net
What you will learn This week
Vision
To help 10 Million students around
the globe to learn technology in a
easy way
www.pantechsolutions.net
About me
My Primary Expertise
Microcontroller Architecture: 8051,PIC,AVR,ARM,MSP430,PSOC3
DSP Architecture: Blackfin,C2000,C6000,21065L Sharc
FPGA: Spartan,Virtex,Cyclone
Image Processing Algorithms: Image/Scene Recognition, Machine Learning, Computer Vision, Deep Learning,
Pattern Recognition, Object Classification ,Image Retrieval, Image enhancement and denoising.
Neural Networks : SVM,RBF,BPN
Cryptography :RSA,DES,3DES,Ellipti curve,Blowfish,Diffe Hellman
Compilers: Keil,Visual DSP++,CCS, Xilinx Platform studio,ISE, Matlab, Open CV
https://www.linkedin.com/in/jeevarajan/ www.pantechsolutions.net
Announcement
● Attendance Link at 9 pm
● Minimum attendance required for an E-Certificate is 27
Days. Attendance link will be valid for 1 hrs. after the event.
● For Internship Candidates no attendance required ,it will be
accessed from the LMS Portal. (learn.pantechsolutions.net)
● Recorded Video Streaming for LAB classes to improve
Learning Experience
● PPT will be uploaded in facebook group
● Source code download is available only on the portal
Assignment
● Project based on Thingspeak ,IFTTT ,ESP32 and Matlab
● Hardware or Software
● Video on phone ,upload to facebook via youtube.
● Submission Deadline on Friday
Mindset Lesson
● The power of Giving
● See Good in people ,people will see
good in you.
Introduction to Microsoft Azure
IoT
What is Azure Internet of Things
(IoT)?
The Azure Internet of Things (IoT) is a collection of Microsoft-managed
cloud services that connect, monitor, and control billions of IoT assets.
In simpler terms, an IoT solution is made up of one or more IoT devices
that communicate with one or more back-end services hosted in the
cloud.
Core Subsytems of Microsoft
Azure
All subsystem –Lambda
Architecture
All subsystem –Cross cutting needs
Conceptual representation of device
connectivity
Data flow and Stream Processing
These stages can be classified in four categories: storage, routing, analysis and action/display
Recommended data flow for Lamda
Architecture
Technology Options
● Stateless vs Stateful
○ Where possible, a solution should implement stateless processors, to reduce
operational cost and increase availability. On the other hand, stateful processing
allows for richer analysis, and is often required to implement higher level
features.
● Static vs dynamic rules
○ if analysis rules do not change and do not reference external data that changes,
it is possible to choose simpler technologies at a lower cost. In scenarios where
more flexibility is required to support variable load, frequent changes to stream
processing logic, and mutable external reference data available technologies are
more complex and expensive to deploy.
Stateless Stream Processing
Statefull Stream Processing
What is Azure IoT Hub
● IoT Hub is a managed service hosted in the cloud that acts as a
central message hub for communication between an IoT application
and its attached devices. You can connect millions of devices and
their backend solutions reliably and securely. Almost any device can
be connected to an IoT Hub.
● You can integrate IoT Hub with other Azure services to build
complete, end-to-end solutions. For example, use:
● Azure Event Grid to enable your business to react quickly to critical
events in a reliable, scalable, and secure manner.
● Azure Logic Apps to automate business processes.
● Azure Machine Learning to add machine learning and AI models to
your solution.
● Azure Stream Analytics to run real-time analytic computations on
the data streaming from your devices.
What is Azure IoT Central
Azure IoT Central is your app platform—one location that connects you with devices, partners,
app templates, and problem solvers.
After creating your application, the first step is to create and connect devices. Every device
connected to IoT Central uses a device template. A device template is the blueprint that
defines the characteristics and behavior of a type of device such as the:
● Telemetry it sends. Examples include temperature and humidity. Telemetry is streaming
data.
● Business properties that an operator can modify. Examples include a customer address
and a last serviced date.
● Device properties that are set by a device and are read-only in the application. For
example, the state of a valve as either open or shut.
● Properties, that an operator sets, that determine the behavior of the device. For
example, a target temperature for the device.
● Commands, that an operator can call, that run on a device. For example, a command to
remotely reboot a device.
You have several options for
creating device templates:
● Design the device template in IoT Central and then implement its
device model in your device code.
● Create a device model using Visual Studio code and publish the
model to a repository. Implement your device code from the model,
and connect your device to your IoT Central application. IoT Central
finds the device model from the repository and creates a simple
device template for you.
● Create a device model using Visual Studio code. Implement your
device code from the model. Manually import the device model into
your IoT Central application and then add any cloud properties,
customizations, and views your IoT Central application needs.
Customize the UI
● Customize the IoT Central application UI for the operators who are
responsible for the day-to-day use of the application.
Customizations you can make include:
● Configuring custom dashboards to help operators discover insights
and resolve issues faster.
● Configuring custom analytics to explore time series data from your
connected devices.
● Defining the layout of properties and settings on a device template.
Manage your devices
● Use the IoT Central application to manage the devices in your IoT
Central solution. Operators do tasks such as:
● Monitoring the devices connected to the application.
● Troubleshooting and remediating issues with devices.
● Provisioning new devices.
● You can define custom rules and actions that operate over data
streaming from connected devices. An operator can enable or
disable these rules at the device level to control and automate tasks
within the application.
Dashboards
?
Thank you