0% found this document useful (0 votes)
146 views132 pages

Iot Merged

The document discusses key steps in developing an IoT system for home automation. It describes specifying requirements and models including purpose, process, domain, information and functional models. It also covers defining views such as operational and functional views. The document outlines integrating devices like a Raspberry Pi, sensor and actuator. It describes developing auto and manual control applications. Finally, it discusses stages of the data lifecycle including creation, storage, usage, archival and destruction.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
146 views132 pages

Iot Merged

The document discusses key steps in developing an IoT system for home automation. It describes specifying requirements and models including purpose, process, domain, information and functional models. It also covers defining views such as operational and functional views. The document outlines integrating devices like a Raspberry Pi, sensor and actuator. It describes developing auto and manual control applications. Finally, it discusses stages of the data lifecycle including creation, storage, usage, archival and destruction.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 132

iOt DOMAIN ANALYST

IOT DOMAIN ANALYST ECE 3502- ETH


Module 3
Lecture 14:
05/04/2021
Module 3: Simulation Scenarios

 Models to Simulate Real-World Scenarios


 Application of the Models
 Stages of Data Lifecycle
 Reuse Existing IoT Solutions
 Reusability Plan
 Models to Simulate Real-World Scenarios
 Application of the Models

Reference:

1. Arshdeep Bahga, Vijay Madisetti, “Internet of Things: A hands-on Approach”, University Press, 2015.

2. https://cocoa.ethz.ch/downloads/2014/01/1524_D1.3_Architectural_Reference_Model_update.pdf
Functional Model
The functional model is an abstract framework for understanding the main functionality groups of the IoT
architecture environment and their relationships.

Longitudinal Functionality Groups

 Application
 IoT Business Process Management
 Virtual Entity & IoT Service
 Service Organisation
 Communication
 Devices

Transversal Functionality Groups

 Management
 Security
Functional Model
 The functional model contains seven longitudinal functionality groups complemented by
two transversal functionality groups.
 These transversal groups provide functionalities that are required by the longitudinal
groups.
 The policies governing the transversal groups will not only be applied to the groups
themselves, but do also pertain to the longitudinal groups.
 As an example: for a security policy to be effective, it must ensure that there is no
functionality provided by a component that would circumvent the policy and provide an
unauthorized access.
 The functional model is a layered model and the main communication flows between the
FGs. Since the transversal FGs (Management & Security) interface with most of the other
FGs, their relationships are not explicitly depicted.
Functional Model
Longitudinal Functionality groups

 IoT Business Process Management


The IoT Business Process Management Functionality Group (BPM FG) relates to the integration of
traditional business process management systems, as they are common in the enterprise world, with the
IoT.

 Virtual Entity & IoT Service


Service Organisation: It is the central functional group that acts as a communication hub between several
other functional groups.
Functional Model
Longitudinal Functionality groups
 Communication
The CFG ensures reliable communication and flow control.
The CFG enables bridging among different networks, allowing Devices to perform as a network entry point
implementing forwarding, filtering, connection tracking and packets aggregation functions.
All those functionalities are as well supported by an error detection and correction infrastructure implemented
by this FG.
Transversal Functionality Groups
 Management
The Management Functionality Group (Management FG) is responsible for the composition and tracking of
actions that
involve one or more other
FGs. Example:
Turning the entire IoT system into a sleep mode during an energy-
harvesting cycle. Tracking of other FGs
 Security
The Security Functionality Group (Security FG) is responsible for ensuring the security and privacy of the
IoT system The Security FG is also in charge of protecting the user's private parameters
IoT Design MethodologySteps
IoT Design Methodology Steps for Home
Automation System
Purpose & RequirementsSpecification
To identify the system purpose, behavior and requirements.
 Purpose: A home automation system that allows controlling of the lights in a remotely using a
home application. web

 Behavior: The home automation system should have auto and manual modes. In auto mode, the
system measures the light level in the room and switches on the light when it gets dark. In manual
mode, the system provides the option of manually and remotely switching on/off the light.
 The requirements can be like data collection requirements, data analysis requirements, system
management requirements, data privacy and security requirements, user interface requirements.

• System Management Requirement: The system should provide remote monitoring and control
functions.
• Data Analysis Requirement: The system should perform local analysis of the data.
• Application Deployment Requirement: The application should be deployed locally on the device,
but should be accessible remotely.

• Security Requirement: The system should have basic user authentication capability.
Process Model Specification
It formally describes the use cases of the IoT system based on the purpose and requirement
specifications.
Domain Model Specification
 The domain model describes the main
concepts, entities and objects in the domain
of IoT system to be designed.
 It defines the attributes of the objects and
relationships between objects.
 It provides an abstract representation of the
concepts, objects and entities in the IoT
domain, independent of any specific
technology or platform.

 The entities, objects and concepts include:


 Physical entity
 Virtual entity
 Device
 Resource
Information Model Specification
 The Information Model defines the structure of all the information in the IoT system and adds more
details to the
Virtual Entities by defining their attributes and relations.

 But it does not describe the specifics of how the information is represented or stored.

0..* 0..*
Service Specifications
Service specifications define the services in the
IoT system

 Service types

 Service inputs/output

 Service endpoints

 Service schedules

0..* 0..*
IoT LevelSpecification
 Highlights the deployment level for IoT
system
Functional ViewSpecification
• It defines the functions of the IoT systems grouped into various
functional groups.
• The functional groups included in a functional view are:
• Device
• Communication
• Services
• Management
• Security
• Application
Functional ViewSpecification
Operational ViewSpecification
In this step, various options pertaining to the IoT
system deployment and operation are defined, such as, service
hosting
options, storage options, device options, application hosting options, etc
Device & ComponentIntegration
 The devices and components used
here are:
 Raspberry Pi mini computer
 LDR sensor
 Relay switch actuator
Application Development
 Auto
 Controls the light appliance automatically based on the lighting conditions
in the room.

 Light
 When Auto mode is off, it is used for manually controlling the light
appliance.
 When Auto mode is on, it reflects the current state of the light appliance.
Stages of Data Life cycle
The data life cycle is the sequence of stages that a particular unit of data goes through from its initial
generation or capture to its eventual archival and/or deletion at the end of its useful life. The various
phases of a typical data lifecycle are illustrated in the figures.

Generation
Creatio
n
Purging Capture

Action Collection
Storag
e
Archival Maintenance

Usag
e

Publication Synthesis
Archiva
Analysis Storage
l
Usage

Destructio
n Visualization
Stages of Data life cycle
 Data Creation
Data can be created in different forms like PDF, image, Word document or SQL database data and in any organization, data is
created in one of the 3 ways:
 Data Acquisition: acquiring already existing data which has been produced outside the organization.
 Data Entry: manual entry of new data by personnel within the organization.
 Data Capture: capture of data generated by devices used in various processes in the organization.

 Storage
Once data has been created, it needs to be stored and protected, with the appropriate level of security. A robust backup and
recovery process should also be implemented to ensure retention of the data during the lifecycle.

 Usage
During the usage phase of the data lifecycle, data is used to support activities in the organization. Data can be viewed,
processed, modified and saved. An audit trail should be maintained for all critical data to ensure that all modifications to data
are fully traceable. Data may also be made available to share with others outside the organization.

 Archival
Data archival is the copying and removal of data from all active production environments where it is stored in case it is
needed again, but where no maintenance or general usage occurs. If necessary, the data can be restored to an environment
where it can be used.

 Destruction
Data destruction or purging is the removal of every copy of a data item from an organization and is typically done from an
archive storage location. The challenge of this phase is to ensure that the data has been properly destroyed. It is important to
ensure before destroying data that the data items have exceeded their required regulatory retention period.
Data lifecycle and its analysis
Fundamental steps of a data analytics project plan(AI, Machine Learning and Big DATA)

Define the Goal Clean the Data Find Insights and Iterate
Visualize

Deploy Machine
Get the Data Enrich the Data
Learning

These seven data science steps ensure realization of business value from each unique project and
mitigate the risk of error.
Data lifecycle and its analysis
 Define the Goal
 Understand the business or activity of the data project

 Identify a clear objectives of what you want to do with data

 Get your Data


 Once the objectives are identified, collect and aggregate the data from different sources

Ways to collect the data

 Query database(using technical skills like MySQL to process the data)

 Scrape from the websites

 Connect to Web APIs


 Obtain data directly from files (downloading it from Kaggle or existing corporate data which are stored
in CSV)
Data lifecycle and its analysis
 Explore and Clean the Data

Clean the Data:


 Process of organizing and tidying up the data, removing what is no longer needed, replacing what is
missing and standardizing the format of the collected data.

Steps Involved

 Convert the data from one format to another and consolidate everything into one standardized format

 Filter the data


 Extracting and Replacing values(missing data sets or they could appear to be non-values, this is the
time to replace them accordingly)

 Split, Merge and Extract data (For example, the place of origin, contains both “City” and “State”.
Depending on the requirements, the data can be either merged or split)
Data lifecycle and its analysis
Explore the Data
 Once the data is ready to be used, and before processing using AI and Machine Learning, the data need
to be examined

 figure out the business question and transform them into a data science question

 inspect the data and its properties


 compute descriptive statistics to extract features and test significant variables. Testing significant
variables often is done with correlation. (e.g. exploring the risk of someone getting high blood
pressure in relations to their height and weight)

Enrich the Dataset


 Process of enhancing, refining, and improving raw data.
Data lifecycle and its analysis
 Build Helpful Visualizations
 Visualization is the best way to explore and communicate the findings and is the next phase of data
analytics project.

 Graphs are also another way to enrich the dataset and develop more interestingfeatures
 Data visualization to helps to identify significant patterns and trends of the data. A better picture of
the data can be obtained through simple charts like line charts or bar charts further to understand the
importance of the data.

 Get Predictive
 Machine learning algorithms help in getting insights and predicting futuretrends

 Reduce the dimensionality of the data set and select the relevant ones which contribute to the
prediction of results.
Data lifecycle and its analysis

 Interpret models and data. The predictive power of a model lies in its ability to generalize i.e. the ability
to generalize unseen future data
 Interpreting data refers to the presentation of data to a non-technical layman. This results in answering
to the business questions stated in objective together with the actionable insights that is found
through the data science process.
 Actionable insight is a key outcome of the data science process i.e. predictive analytics and later on
prescriptive analytics(i.e. to repeat a positive result, or prevent a negative outcome).

 Iterate
 To make the data useful and accurate, need to constantly reevaluate, retrain it, and develop new
features
Reuse existing IoT solutions & Reusability Plan
Reusing of existing components establish development of new technologies in less time and effort
One of the main functionalities that can be reused is related to Device Management layer and the Black-
box reuse

Steps Involved
 Identify the reusable asset
 Integrate the reusable asset
Ways to integrate the reusable asset to the new system
 Black-box reuse - The assets are integrated in the new system simply as they are
 White-box reuse - new functionalities are implemented on the existing components for integrating
them
In IoT development, due to the large scale of operations when building applications it is important to
know from the beginning the reuse strategy for integrating components based on the types of
functionalities that can be reused.
Reuse existing IoT solutions & Reusability Plan

 Evaluate the reusable asset:


 It is necessary to ensure that the quality of the reusable components does not compromise the overall
quality of the application and they do not deteriorate the quality of the new system.
 Extendible - to handle the variability of heterogeneous devices and technologies
 Flexible - to easily adapt to changes caused by the external environment and implement new
requirements,
 Reusable - to allow further reuse in future IoT applications, saving time and effort
 Functional - to offer several functionalities through APIs.
 Understandable and Effective

 What functionalities can be reused from IoT frameworks?


 Which reuse strategy should be adopted with respect to the functionality reused?
 What is the quality of the reused components with respect to the functionality reused?
Reuse existing IoT solutions & Reusability Plan
Re-usable Components
Some of the reusable components are
 Cloud data storage
 Cloud service
 Sensors
 Controllers
 IoT platform
 Computing devices
iOt DOMAIN ANALYST

IOT DOMAIN ANALYST ECE 3502- ETH


Module 3
Lecture 14:
05/04/2021
Module 3: Simulation Scenarios

 Models to Simulate Real-World Scenarios


 Application of the Models
 Stages of Data Lifecycle
 Reuse Existing IoT Solutions
 Reusability Plan
 Models to Simulate Real-World Scenarios
 Application of the Models

Reference:

1. Arshdeep Bahga, Vijay Madisetti, “Internet of Things: A hands-on Approach”, University Press, 2015.

2. https://cocoa.ethz.ch/downloads/2014/01/1524_D1.3_Architectural_Reference_Model_update.pdf
Functional Model
The functional model is an abstract framework for understanding the main functionality groups of the IoT
architecture environment and their relationships.

Longitudinal Functionality Groups

 Application
 IoT Business Process Management
 Virtual Entity & IoT Service
 Service Organisation
 Communication
 Devices

Transversal Functionality Groups

 Management
 Security
Functional Model
 The functional model contains seven longitudinal functionality groups complemented by
two transversal functionality groups.
 These transversal groups provide functionalities that are required by the longitudinal
groups.
 The policies governing the transversal groups will not only be applied to the groups
themselves, but do also pertain to the longitudinal groups.
 As an example: for a security policy to be effective, it must ensure that there is no
functionality provided by a component that would circumvent the policy and provide an
unauthorized access.
 The functional model is a layered model and the main communication flows between the
FGs. Since the transversal FGs (Management & Security) interface with most of the other
FGs, their relationships are not explicitly depicted.
Functional Model
Longitudinal Functionality groups

 IoT Business Process Management


The IoT Business Process Management Functionality Group (BPM FG) relates to the integration of
traditional business process management systems, as they are common in the enterprise world, with the
IoT.

 Virtual Entity & IoT Service


Service Organisation: It is the central functional group that acts as a communication hub between several
other functional groups.
Functional Model
Longitudinal Functionality groups
 Communication
The CFG ensures reliable communication and flow control.
The CFG enables bridging among different networks, allowing Devices to perform as a network entry point
implementing forwarding, filtering, connection tracking and packets aggregation functions.
All those functionalities are as well supported by an error detection and correction infrastructure implemented
by this FG.
Transversal Functionality Groups
 Management
The Management Functionality Group (Management FG) is responsible for the composition and tracking of
actions that
involve one or more other
FGs. Example:
Turning the entire IoT system into a sleep mode during an energy-
harvesting cycle. Tracking of other FGs
 Security
The Security Functionality Group (Security FG) is responsible for ensuring the security and privacy of the
IoT system The Security FG is also in charge of protecting the user's private parameters
IoT Design MethodologySteps
IoT Design Methodology Steps for Home
Automation System
Purpose & RequirementsSpecification
To identify the system purpose, behavior and requirements.
 Purpose: A home automation system that allows controlling of the lights in a remotely using a
home application. web

 Behavior: The home automation system should have auto and manual modes. In auto mode, the
system measures the light level in the room and switches on the light when it gets dark. In manual
mode, the system provides the option of manually and remotely switching on/off the light.
 The requirements can be like data collection requirements, data analysis requirements, system
management requirements, data privacy and security requirements, user interface requirements.

• System Management Requirement: The system should provide remote monitoring and control
functions.
• Data Analysis Requirement: The system should perform local analysis of the data.
• Application Deployment Requirement: The application should be deployed locally on the device,
but should be accessible remotely.

• Security Requirement: The system should have basic user authentication capability.
Process Model Specification
It formally describes the use cases of the IoT system based on the purpose and requirement
specifications.
Domain Model Specification
 The domain model describes the main
concepts, entities and objects in the domain
of IoT system to be designed.
 It defines the attributes of the objects and
relationships between objects.
 It provides an abstract representation of the
concepts, objects and entities in the IoT
domain, independent of any specific
technology or platform.

 The entities, objects and concepts include:


 Physical entity
 Virtual entity
 Device
 Resource
Information Model Specification
 The Information Model defines the structure of all the information in the IoT system and adds more
details to the
Virtual Entities by defining their attributes and relations.

 But it does not describe the specifics of how the information is represented or stored.

0..* 0..*
Service Specifications
Service specifications define the services in the
IoT system

 Service types

 Service inputs/output

 Service endpoints

 Service schedules

0..* 0..*
IoT LevelSpecification
 Highlights the deployment level for IoT
system
Functional ViewSpecification
• It defines the functions of the IoT systems grouped into various
functional groups.
• The functional groups included in a functional view are:
• Device
• Communication
• Services
• Management
• Security
• Application
Functional ViewSpecification
Operational ViewSpecification
In this step, various options pertaining to the IoT
system deployment and operation are defined, such as, service
hosting
options, storage options, device options, application hosting options, etc
Device & ComponentIntegration
 The devices and components used
here are:
 Raspberry Pi mini computer
 LDR sensor
 Relay switch actuator
Application Development
 Auto
 Controls the light appliance automatically based on the lighting conditions
in the room.

 Light
 When Auto mode is off, it is used for manually controlling the light
appliance.
 When Auto mode is on, it reflects the current state of the light appliance.
Stages of Data Life cycle
The data life cycle is the sequence of stages that a particular unit of data goes through from its initial
generation or capture to its eventual archival and/or deletion at the end of its useful life. The various
phases of a typical data lifecycle are illustrated in the figures.

Generation
Creatio
n
Purging Capture

Action Collection
Storag
e
Archival Maintenance

Usag
e

Publication Synthesis
Archiva
Analysis Storage
l
Usage

Destructio
n Visualization
Stages of Data life cycle
 Data Creation
Data can be created in different forms like PDF, image, Word document or SQL database data and in any organization, data is
created in one of the 3 ways:
 Data Acquisition: acquiring already existing data which has been produced outside the organization.
 Data Entry: manual entry of new data by personnel within the organization.
 Data Capture: capture of data generated by devices used in various processes in the organization.

 Storage
Once data has been created, it needs to be stored and protected, with the appropriate level of security. A robust backup and
recovery process should also be implemented to ensure retention of the data during the lifecycle.

 Usage
During the usage phase of the data lifecycle, data is used to support activities in the organization. Data can be viewed,
processed, modified and saved. An audit trail should be maintained for all critical data to ensure that all modifications to data
are fully traceable. Data may also be made available to share with others outside the organization.

 Archival
Data archival is the copying and removal of data from all active production environments where it is stored in case it is
needed again, but where no maintenance or general usage occurs. If necessary, the data can be restored to an environment
where it can be used.

 Destruction
Data destruction or purging is the removal of every copy of a data item from an organization and is typically done from an
archive storage location. The challenge of this phase is to ensure that the data has been properly destroyed. It is important to
ensure before destroying data that the data items have exceeded their required regulatory retention period.
Data lifecycle and its analysis
Fundamental steps of a data analytics project plan(AI, Machine Learning and Big DATA)

Define the Goal Clean the Data Find Insights and Iterate
Visualize

Deploy Machine
Get the Data Enrich the Data
Learning

These seven data science steps ensure realization of business value from each unique project and
mitigate the risk of error.
Data lifecycle and its analysis
 Define the Goal
 Understand the business or activity of the data project

 Identify a clear objectives of what you want to do with data

 Get your Data


 Once the objectives are identified, collect and aggregate the data from different sources

Ways to collect the data

 Query database(using technical skills like MySQL to process the data)

 Scrape from the websites

 Connect to Web APIs


 Obtain data directly from files (downloading it from Kaggle or existing corporate data which are stored
in CSV)
Data lifecycle and its analysis
 Explore and Clean the Data

Clean the Data:


 Process of organizing and tidying up the data, removing what is no longer needed, replacing what is
missing and standardizing the format of the collected data.

Steps Involved

 Convert the data from one format to another and consolidate everything into one standardized format

 Filter the data


 Extracting and Replacing values(missing data sets or they could appear to be non-values, this is the
time to replace them accordingly)

 Split, Merge and Extract data (For example, the place of origin, contains both “City” and “State”.
Depending on the requirements, the data can be either merged or split)
Data lifecycle and its analysis
Explore the Data
 Once the data is ready to be used, and before processing using AI and Machine Learning, the data need
to be examined

 figure out the business question and transform them into a data science question

 inspect the data and its properties


 compute descriptive statistics to extract features and test significant variables. Testing significant
variables often is done with correlation. (e.g. exploring the risk of someone getting high blood
pressure in relations to their height and weight)

Enrich the Dataset


 Process of enhancing, refining, and improving raw data.
Data lifecycle and its analysis
 Build Helpful Visualizations
 Visualization is the best way to explore and communicate the findings and is the next phase of data
analytics project.

 Graphs are also another way to enrich the dataset and develop more interestingfeatures
 Data visualization to helps to identify significant patterns and trends of the data. A better picture of
the data can be obtained through simple charts like line charts or bar charts further to understand the
importance of the data.

 Get Predictive
 Machine learning algorithms help in getting insights and predicting futuretrends

 Reduce the dimensionality of the data set and select the relevant ones which contribute to the
prediction of results.
Data lifecycle and its analysis

 Interpret models and data. The predictive power of a model lies in its ability to generalize i.e. the ability
to generalize unseen future data
 Interpreting data refers to the presentation of data to a non-technical layman. This results in answering
to the business questions stated in objective together with the actionable insights that is found
through the data science process.
 Actionable insight is a key outcome of the data science process i.e. predictive analytics and later on
prescriptive analytics(i.e. to repeat a positive result, or prevent a negative outcome).

 Iterate
 To make the data useful and accurate, need to constantly reevaluate, retrain it, and develop new
features
Reuse existing IoT solutions & Reusability Plan
Reusing of existing components establish development of new technologies in less time and effort
One of the main functionalities that can be reused is related to Device Management layer and the Black-
box reuse

Steps Involved
 Identify the reusable asset
 Integrate the reusable asset
Ways to integrate the reusable asset to the new system
 Black-box reuse - The assets are integrated in the new system simply as they are
 White-box reuse - new functionalities are implemented on the existing components for integrating
them
In IoT development, due to the large scale of operations when building applications it is important to
know from the beginning the reuse strategy for integrating components based on the types of
functionalities that can be reused.
Reuse existing IoT solutions & Reusability Plan

 Evaluate the reusable asset:


 It is necessary to ensure that the quality of the reusable components does not compromise the overall
quality of the application and they do not deteriorate the quality of the new system.
 Extendible - to handle the variability of heterogeneous devices and technologies
 Flexible - to easily adapt to changes caused by the external environment and implement new
requirements,
 Reusable - to allow further reuse in future IoT applications, saving time and effort
 Functional - to offer several functionalities through APIs.
 Understandable and Effective

 What functionalities can be reused from IoT frameworks?


 Which reuse strategy should be adopted with respect to the functionality reused?
 What is the quality of the reused components with respect to the functionality reused?
Reuse existing IoT solutions & Reusability Plan
Re-usable Components
Some of the reusable components are
 Cloud data storage
 Cloud service
 Sensors
 Controllers
 IoT platform
 Computing devices
ECE 3502- ETH

IOT DOMAIN ANALYST Module 3


Lecture 12:
25/03/2021
MODULE 3
SIMULATION SCENARIOS
Models to simulate real-world scenarios
Application of the models
Stages of data lifecycle
Reuse existing IoT solutions
Reusability plan
PROBLEM SUITABLE FOR
SIMULATION MODELING AND ANALYSIS
In general, whenever there is a need to model and analyze randomness in a
system, simulation is the tool of choice. More specifically, situations in which
simulation modeling and analysis is used include the following:

♦ It is impossible or extremely expensive to observe certain processes in the


real world, e.g., next year's cancer statistics, performance of the next space
shuttle, and the effect of Internet advertising on a company's sales

♦ Problems in which mathematical model can be formulated but analytic


solutions are either impossible (e.g., job shop scheduling problem, high order
difference equations) or too complicated (e.g.,complex systems like the stock
market, and large scale queuing models).

♦ It is impossible or extremely expensive to validate the mathematical model


describing the system, e.g.,due to insufficient data.
3
SELECTION OF SIMULATION SOFTWARE
Although a simulation model can be built using general purpose programming languages which
are familiar to the analyst, available over a wide variety of platforms, and less expensive, most
simulation studies today are implemented using a simulation package.

The advantages are reduced programming requirements; natural framework for simulation
modeling; conceptual guidance; automated gathering of statistics; graphic symbolism for
communication; animation; and increasingly, flexibility to change the model.

There are hundreds of simulation products on the market, many with price tags of $15,000 or
more.

Naturally, the question of how to select the best simulation software for an application arises.
Metrics for evaluation include modeling flexibility, ease of use, modeling structure (hierarchical v/s
flat; object-oriented v/s nested), code reusability, graphic user interface, animation, dynamic
business graphics, hardware and software requirements, statistical capabilities, output reports and
graphical plots, customer support, and documentation

4
SIMULATION PACKAGES-TYPES
The two types of simulation packages are
1. Simulation languages
and
2. Application-oriented simulators (Table 2).
Simulation languages offer more flexibility than the
application-oriented simulators.
On the other hand, languages require varying amounts of
programming expertise.

5
SIMULATION PACKAGES-TYPES
Application-oriented simulators are easier to learn and have modeling
constructs closely related to the application.
Most simulation packages incorporate animation which is excellent for
communication and can be used to debug the simulation program; a
"correct looking" animation, however, is not a guarantee of a valid
model. More importantly, animation is not a substitute for output
analysis.

6
BENEFITS OF SIMULATION MODELING
AND ANALYSIS
According to practitioners, simulation modeling and analysis is one of
the most frequently used operations research techniques. When used
judiciously, simulation modeling and analysis makes it possible to:

♦ Obtain a better understanding of the system by developing a


mathematical model of a system of interest, and observing the system's
operation in detail over long periods of time.
♦ Test hypotheses about the system for feasibility.
♦ Compress time to observe certain phenomena over long periods or
expand time to observe a complex phenomenon in detail.
♦ Study the effects of certain informational, organizational,
environmental and policy changes on the operation of a system by
altering the system's model; this can be done without disrupting the real
system and significantly reduces the risk of experimenting with the real
system. 7
BENEFITS OF SIMULATION MODELING
AND ANALYSIS
♦ Experiment with new or unknown situations about which only
weak information is available.
♦ Identify the "driving" variables - ones that performance
measures are most sensitive to - and the
inter-relationships among them.
♦ Identify bottlenecks in the flow of entities (material, people,
etc.) or information.
♦ Use multiple performance metrics for analyzing system
configurations.
♦ Employ a systems approach to problem solving.
♦ Develop well designed and robust systems and reduce
system development time.

8
PITFALLS TO GUARD
AGAINST IN SIMULATION
Simulation can be a time consuming and complex exercise, from
modeling through output analysis, that necessitates the
involvement of resident experts and decision makers in the
entire process. Following is a checklist of pitfalls to guard
against.
♦ Unclear objective.
♦ Using simulation when an analytic solution is appropriate.
♦ Invalid model.
♦ Simulation model too complex or too simple.
♦ Erroneous assumptions.

9
PITFALLS TO GUARD
AGAINST IN SIMULATION
Undocumented assumptions. This is extremely important and it is
strongly suggested that assumptions made at each stage of the
simulation modeling and analysis exercise be documented
thoroughly.
♦ Using the wrong input probability distribution.
♦ Replacing a distribution (stochastic) by its mean(deterministic).
♦ Using the wrong performance measure.
♦ Bugs in the simulation program.
♦ Using standard statistical formulas that assume independence in
simulation output analysis.
♦ Initial bias in output data.
♦ Poor schedule and budget planning.
♦ Poor communication among the personnel involved in the simulation
study.
10
ECE 3502- ETH

IOT DOMAIN ANALYST Module 3


Lecture 11:
23/03/2021
MODULE 3
SIMULATION SCENARIOS
Models to simulate real-world scenarios
Application of the models
Stages of data lifecycle
Reuse existing IoT solutions
Reusability plan
WHAT IS MODELING?
Modeling is the process of producing a model; a model is a
representation of the construction and working of some system of interest.
A model is similar to but simpler than the system it represents. One
purpose of a model is to enable the analyst to predict the effect of
changes to the system.
A model should be a close approximation to the real system and
incorporate most of its salient features. On the other hand, it should not be
so complex that it is impossible to understand and experiment with it.

3
MODELLING
A good model is a judicious tradeoff between realism and
simplicity. Simulation practitioners recommend increasing the
complexity of a model iteratively. An important issue in
modeling is model validity.
Model validation techniques include simulating the model under
known input conditions and comparing model output with system
output.

4
CLASSIFICATION OF MODELS
Generally, a model intended for a simulation study is a mathematical
model developed with the help of simulation software.
Mathematical model classifications
include deterministic (input and output variables are
fixed values)
or
Stochastic (at least one of the input or output variables is probabilistic);
Static (time is not taken into account) or dynamic (time-varying
interactions among variables are taken into account).
Typically, simulation models are stochastic and dynamic.

5
WHAT IS SIMULATION?
A simulation of a system is the operation of a model of the system. The
model can be reconfigured and experimented.
Usually, this is impossible, too expensive or impractical to do in the
system it represents.

The operation of the model can be studied, and hence, properties


concerning the behavior of the actual system or its subsystem can be
inferred.
In its broadest sense, simulation is a tool to evaluate the performance
of a system, existing or proposed, under different configurations of
interest and over long periods of real time.

6
SIMULATION
Simulation is used before an existing system is altered or a new system built, to
reduce the chances of failure to meet specifications, to eliminate unforeseen
bottlenecks, to prevent under or over-utilization of resources, and to optimize
system performance.
For instance, simulation can be used to answer questions like:
What is the best design for a new telecommunications network?
What are the associated resource requirements?
How will a telecommunication network perform when the traffic load increases
by 50%?
How will a new routing algorithm affect its performance? Which network
protocol optimizes Network performance?
What will be the impact of a link failure?

7
SIMULATION STUDY
The iterative nature of the process is indicated by the system
under study becoming the altered system which then becomes
the system under study and the cycle repeats.
In a simulation study, human decision making is required at
all stages, namely, model development, experiment design,
output analysis, conclusion formulation, and making decisions to
alter the system under study.
The only stage where human intervention is not required is
the running of the simulations, which most simulation
software packages perform efficiently.

8
SCHEMATIC OF A SIMULATION STUDY

9
DEVELOPING A SIMULATION
MODEL
The steps involved in developing a simulation model, designing a simulation
experiment, and performing simulation analysis are:

Step 1. Identify the problem.


Step 2. Formulate the problem.
Step 3. Collect and process real system data.
Step 4. Formulate and develop a model.
Step 5. Validate the model.
Step 6. Document model for future use.
Step 7. Select appropriate experimental design.
Step 8. Establish experimental conditions for runs.
Step 9. Perform simulation runs.
Step 10. Interpret and present results.
Step 11. Recommend further course of action.

10
DEVELOPING A SIMULATION
MODEL
Simulation models consist of the following components:
system entities, input variables, performance measures,
and functional relationships.

For instance in a simulation model of an M/M/1 queue, the


server and the queue are system entities, arrival rate and
service rate are input variables, mean wait time and maximum
queue length are performance measures,
and
'time in system = wait time + service time' is an example of a
functional relationship.

11
DEVELOPING A SIMULATION
MODEL
Simulation modeling comprises the following steps:

Step 1. Identify the problem. Enumerate problems with an


existing system. Produce requirements for a proposed system.

Step 2. Formulate the problem. Select the bounds


of the system, the problem or a part thereof, to be
studied. Define overall objective of the study and a few
specific issues to be addressed.

12
DEVELOPING A SIMULATION
MODEL
Step 3. Collect and process real system data.
Collect data on system specifications (e.g., bandwidth for a
communication network), input variables, as well as erformance of the
existing system. Identify sources of randomness in the system, i.e., the
stochastic input variables.
Step 4. Formulate and develop a model. Develop schematics and network
diagrams of the system (How do entities flow through the system?).
Translate these conceptual models to simulation software acceptable
form. Verify that the simulation model executes as intended.

13
DEVELOPING A SIMULATION
MODEL
Step 5. Validate the model. Compare the model's performance under known
conditions with the performance of the real system. Perform statistical inference
tests and get the model examined by system experts.
Step 6. Document model for future use. Document objectives, assumptions and
input variables in detail variables of a simulation model so that we may
observe and identify the reasons for changes in the performance measures.

14
DESIGNING A SIMULATION
EXPERIMENT

Step 7. Select appropriate experimental design. Select a


performance measure, a few input variables that are likely to
influence it, and the levels of each input variable.
Step 8. Establish experimental conditions for runs. Address the
question of obtaining accurate information and the most
information from each run. Determine if the system is stationary
(performance measure does not change over time) or non-
stationary (performance measure changes over time).

Step 9. Perform simulation runs. Perform runs according to steps


7-8 above.

15
PERFORMING SIMULATION ANALYSIS

Step 10. Interpret and present results. Compute


numerical estimates (e.g., mean, confidence intervals) of
the desired performance measure for each configuration
of interest. To obtain confidence intervals for the mean
of autocorrelated data, the technique of batch means can
be used.
Step 11. Recommend further course of action. This may include
further experiments to increase the precision and reduce the
bias of estimators, to perform sensitivity analyses, etc.

16
ECE 3502- ETH

IOT DOMAIN ANALYST Module 5


Lecture 17:
15/04/2021
MODULE 5
VALUE ENGINEERING AND ANALYSIS
Principles and phases of Value Engineering and Analysis,
Frameworks for Value Engineering in IoT solutions,
cost-function analysis of IoT solution components, action plans to
incorporate Value Engineering,
Data modelling requirements, Development models: Waterfall,
Agile, Spiral,
V models, monetization models for IoT use cases - ‘Outcomes As
A Service’ model.
VALUE ENGINEERING(VE)
VE is an organized/systematic approach directed
at analyzing the function of systems, equipment,
facilities, services, and supplies for the purpose of
achieving their essential functions at the lowest
life-cycle cost consistent with required
performance, reliability, quality, and safety.
The implementation of the VE process on a
problem typically increases performance,
reliability, quality, safety, durability, effectiveness,
or other desirable characteristics.
VALUE ENGINEERING (VE)
Value (V) = performance (f)/cost (c)

VE isn’t a cost-cutting technique instead a systematic functional


approach of maximize the performance

Cost here refers to the product lifecycle cost(not on initial and


other costs). Cost analysis techniques are different from VE.
WHY VE?
Scarcity of materials was the starting point during WW II
Now effective utilization of materials/key makes it a better
resource management

Ex: Temperature and humidity sensor (HW), number of gateway


for a smart home(HW).
Is this applicable to IoT and it SW too?
VE
IOT REFERENCE FRAMEWORK
HOW CAN VE APPLIED TO SW
MODELS?
Software Development Life Cycle (SDLC) is a
process used by the software industry to design,
develop and test high quality softwares.

The SDLC aims to produce a high-quality software


that meets or exceeds customer expectations,
reaches completion within times and cost
estimates.
SDLC MODELS
iOt DOMAIN ANALYST

ECE 3502- ETH


Module 4
IoT DOMAIN ANALYST Lecture 16:
01/04/2021
Module 4
Use Case Development
 Approaches to gather business requirements
 defining problem statements
 business requirements for use case
development
 Assets for development of IoT solutions.
Assets for development of IoT
solutions.
Assets for development of IoT solutions

What is asset tracking?

• Asset tracking is the process of tracking a physical asset (can be human or

equipment) within a manufacturing facility to identify their location

accurately and utilize them to the fullest.

• Nevertheless, effective asset management is something most manufacturers

consider challenging due to a lack of a digital, centralized place to track and

monitor their asset utilization.


Assets for development of IoT solutions
Smart technologies behind asset tracking
• Barcodes
• Radio Frequency Identification (RFID)
• NFC (Near Field Communication)
• GPS (Global Positioning System)
• Bluetooth Low Energy (BLE)
• Internet of Things (IoT)
4 key features best asset tracking systems include
• Asset tracking analytics
• Asset tracking reporting
• Asset tracking alerts
• Asset depreciation tracking
Assets for development of IoT solutions
IoT -enabled asset tracking

Track assets in real-time throughout the manufacturing factory

• How the IoT enables mobile asset tracking?

• Monitor equipments even in locations where humans can’t intervene

• Monitor equipments even in locations where humans can’t intervene

• Using IoT in Human Asset Management

https://www.hakunamatatatech.com/our-resources/blog/make-your-assets-work-
for-you-call-it-iot/ 5/6
https://technostacks.com/blog/how-iot-can-be-used-in-asset-management-tracking
iOt DOMAIN ANALYST

ECE 3502- ETH


Module 4
IoT DOMAIN ANALYST Lecture 14&15: 01/04/2021
08/04/2021
Module 4
Use Case Development
 Approaches to gather business requirements
 defining problem statements
 business requirements for use case development
 Assets for development of IoT solutions.
Requirement to develop a IoT Project
• Cloud computing: Cloud computing enables storage and processing of unstructured
and structured data into real-time information.
• Access: Another IoT requirement is its accessibility from anywhere and anytime.
• Security: Security is an important factor that forms a part of IoT requirements since
confidential and sensitive information is exchanged across the businesses.
• User experience: The more seamless the User Experience (UX), the greater the use of
IoT systems.
• Smart machines: Smart machines form the basic components or the starting point
from which all connected things can be derived.
• Asset management: Managing assets through cloud-based services ease the
functioning and maintenance of IoT systems.
• Big Data analytics: Analysis of big data provides intelligent information, an ideal
requirement for industrial purposes.

https://www.cloudcredential.org/blog/the-ultimate-guide-to-implementing-iot/
Approaches to gather business requirements
Top 5 user requirements of IoT edge platforms

1. Pick a platform with extensive protocol support for data ingestion

• To seamlessly bring data from devices into the edge platform, enterprises should choose leading IoT

platforms that support an extensive mix of protocols for data ingestion.

• The list of protocols for industrial-minded edge platforms generally includes brownfield deployment

staples such as OPC-UA, BACNET and MODBUS as well as more current ones such as ZeroMQ, Zigbee,

BLE and Thread.

• Equally as important, the platform must be modular in its support for protocols, allowing customization

of existing and development of new means of asset communications.


Approaches to gather business requirements
Top 5 user requirements of IoT edge platforms
2. Ensure the platform has robust capability for offline functionality
• To ensure that the edge platform works when connectivity is down or limited, enterprises should choose
leading IoT edge platforms that provide capabilities in four functional areas.
• First, edge systems need to offer data normalization to successfully clean noisy sensor data.
• Second, these systems must offer storage to support intermittent, unreliable or limited connectivity
between the edge and the cloud.
• Third, an edge system needs a flexible event processing engine at the edge making it possible to
generate insight from machine data when connectivity is constrained.
• Fourth, an IoT edge-enabled platform should integrate with systems including ERP, MES, inventory
management and supply chain management to help ensure business continuity and access to real-time
machine data.
Approaches to gather business requirements
Top 5 user requirements of IoT edge platforms
3. Make sure the platform provides cloud-based orchestration to support device lifecycle management
• To make sure that the edge platform offers highly secure device management, enterprises should select
IoT platforms that offer cloud-based orchestration for provisioning, monitoring and updating of
connected assets.
• Leading IoT platforms provide factory provisioning capabilities for IoT devices.
• These API-based interactions allow a device to be preloaded with certificates, keys, edge applications
and an initial configuration before it is shipped to the customer.
• In addition, platforms should monitor the device using a stream of machine and operational data that
can be selectively synced with cloud instances.
• Finally, an IoT platform should push updates over-the-air to edge applications, the platform itself,
gateway OSs, device drivers and devices connected to a gateway.
Approaches to gather business requirements
Top 5 user requirements of IoT edge platforms
4. The platform needs a hardware-agnostic scalable architecture
• Since there are tens of thousands of device types in the world, enterprises should select IoT platforms
that are capable of running on a wide range of gateways and specialized devices.
• These platforms should employ the same software stack at the edge and in the cloud allowing a
seamless allocation of resources.
• Platforms should support IoT hardware powered by chips that use ARM-, x86-, and MIPS-based
architectures.
• Using containerization technologies and native cross-compilation, the platforms offer a hardware-
agnostic approach that makes it possible to deploy the same set of functionalities across a varied set of
IoT hardware without modifications.
Approaches to gather business requirements
Top 5 user requirements of IoT edge platforms
5. Comprehensive analytics and visualization tools make a big difference
• As we’ve already discussed enterprises should choose IoT platforms that offer out-of-the-box capabilities
to aggregate data, run common statistical analyses and visualize data.
• These platforms should make it easy to integrate leading analytics toolsets and use them to supplement
or replace built-in functionality. Different IoT platform users will require different analyses and
visualization capabilities.
• For example, a plant manager and a machine worker will want to access interactive dashboards that
deliver useful information and relevant controls for each of their respective roles.
• Having flexibility in analytics and visualization capabilities will be essential for enterprises as they
develop IoT solutions for their multiple business units and operations teams.
• Enterprises worldwide are using IoT to increase security, improve productivity, provide higher levels of
service and reduce maintenance costs.

https://www.networkworld.com/article/3247801/the-top-5-user-requirements-of-iot-edge-platforms.html
Defining Problem
statements
“A problem well stated is half solved” — Charles Kettering
Problem Statement?
• The issue (problem), stated clearly and with enough contextual detail
to establish
• Why it is important.
• The method of solving the problem, often stated as a claim
• The designer should understand the problem way before defining a
potential solution.
• The problem definition should be a living document that can always
be revisited and updated often when necessary.
Questions to ask
Questions that help define a problem statement
• What problem are we trying to solve?
• How do we know this is a real problem?
• Why is it important to solve?
• Who are our users?
• How will we know if we’ve solved the problem?
Defining Problem statements
• Start with “How might we…”, or “What can we do to…” type of
questions.
• Frame according to specific users (User-centered approach)
• The 5 ‘W’s — Who, What, Where, When and Why
• Asking a lot of “why’s” (on both failures and success) help you to dive
deeper into the problem
Benefits of Problem statement
• Identify and explain the problem in a concise but detailed way.
• The problem statement provides a guide for navigating the project once it begins.
• It is continually referenced throughout the duration of the project to help the team remain focused
and on track.
• Near the completion of the project, this statement is again referred to in order to verify the solution
has been implemented as stated and that it does indeed solve the initial problem.
• The proposed solution and scope and goals of the solution are made clear through this statement.
• The problem statement is a statement that initiates the process by recognizing the problem. It is a tool
to gain support and approval of the project from management and stakeholders.
Problem statements – As a document
There are a few key elements to keep in mind when crafting a problem
statement that can have a positive impact on the outcome of the project.
• Describe how things should work.
• Explain the problem and state why it matters.
• Explain your problem's financial costs.
• Back up your claims.
• Propose a solution.
• Explain the benefits of your proposed solution(s).
• Conclude by summarizing the problem and solution.
Other Methods
• Affinity Diagrams
• Empathy Mapping
Affinity Diagram
The Affinity Diagram is a method which can help
you gather large amounts of data and organise
them into groups or themes
Empathy Mapping
• An empathy map is a collaborative visualization used to articulate what we
know about a particular type of user.
Defining Problem statements
What is a problem statement?
• Problem statement is a statement of a current issue or problem that requires timely action to improve
the situation.
• This statement concisely explains the barrier the current problem places between a functional process
and/or product and the current (problematic) state of affairs.
• This statement is completely objective, focusing only on the facts of the problem and leaving out any
subjective opinions.
• To make this easier, it's recommended that you ask who, what, when, where and why to create the
structure for your problem statement.
• This will also make it easier to create and read, and makes the problem at hand more comprehensible
and therefore solvable.
• The problem statement, in addition to defining a pressing issue, is a lead-in to a proposal of a timely,
effective solution.
Defining Problem statements
Why is a problem statement important?
• A problem statement is a communication tool.
• Problem statements are important to businesses, individuals and other entities to develop projects
focused on improvement.
• Whether the problem is pertaining to badly-needed road work or the logistics for an island construction
project; a clear, concise problem statement is typically used by a project's team to help define and
understand the problem and develop possible solutions.
• These statements also provide important information that is crucial in decision-making in relation to
these projects or processes.
Defining Problem statements
Problem statements have multiple purposes

• The problem statement has other purposes, too. One is to identify and explain the problem in a concise

but detailed way to give the reader a comprehensive view of what's going on.

• This includes identifying who the problem impacts, what the impacts are, where the problem occurs and

why and when it needs to be fixed.

• Another purpose of the problem statement is to clarify what the expected outcomes are. Establishing

what the desired situation would look like helps provide an overarching idea about the project.

• The proposed solution and scope and goals of the solution are made clear through this statement.
Defining Problem statements
Problem statements help guide projects
• The problem statement provides a guide for navigating the project once it begins.
• It is continually referenced throughout the duration of the project to help the team remain focused and
on track.
• Near the completion of the project, this statement is again referred to in order to verify the solution has
been implemented as stated and that it does indeed solve the initial problem.
• This can help in making sure that proper steps are being taken to prevent the same problem from
happening again in the future.
• Bear in mind that the problem statement does not attempt to define the solution, nor does is outline the
methods of arriving at the solution.
• The problem statement is a statement that initiates the process by recognizing the problem.
Defining Problem statements
How to write a problem statement
A problem statement is a tool used to gain support and approval of the project from management and
stakeholders. As such, it must be accurate and clearly written.
There are a few key elements to keep in mind when crafting a problem statement that can have a positive
impact on the outcome of the project.
• Describe how things should work.
• Explain the problem and state why it matters.
• Explain your problem's financial costs.
• Back up your claims.
• Propose a solution.
• Explain the benefits of your proposed solution(s).
https://www.indeed.com/career-advice/career-
• Conclude by summarizing the problem and solution. development/how-to-write-a-problem-statement
Business requirements for use case development
10 steps to a successful business case for IoT
1. Recognise the need for a business case
2. Start on the shop floor (organisation)
3. Identify meaningful data
4. Employ predictive analytics
5. Track your products and assets
6. Create new revenue models
7. Move from drawing board to reality
8. Choose the right IoT platforms and partners
9. Build a proof of concept
10. Rollout at scale
https://internetofbusiness.com/10-steps-to-a-successful-business-case-for-iot/
https://www.thingsquare.com/blog/articles/how-to-build-iot-business-case/

You might also like