M 4 iot..

IoT Domain Analyst
Dr. Arvind Kumar | School of Electronics Engineering, VIT Vellore |
https://sites.google.com/view/arvindk

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.
02-03-2022 https://sites.google.com/view/arvindk 2

Requirement Gathering Techniques
Techniques describe how tasks are performed under specific circumstances. A task may have
none or one or more related techniques. A technique should be related to at least one task.
The following are some of the well-known requirements gathering techniques −
➢Brainstorming
➢Document Analysis
➢Focus Group
➢Interface analysis
➢Interview
➢Observation
➢Prototyping
➢Requirement Workshops
➢Reverse Engineering
➢Survey/Questionnaire

Document Analysis
➢ Reviewing the documentation of an existing system can help when creating AS–
IS process document, as well as driving gap analysis for scoping of migration
projects.
➢ In an ideal world, we would even be reviewing the requirements that drove
creation of the existing system – a starting point for documenting current
requirements.
➢ Nuggets of information are often buried in existing documents that help us ask
questions as part of validating requirement completeness.
Cont’d….

Focus Group
➢ A focus group is a gathering of people who are representative of the users or
customers of a product to get feedback.
➢ The feedback can be gathered about needs/opportunities/ problems to identify
requirements, or can be gathered to validate and refine already elicited
requirements.
➢ This form of market research is distinct from brainstorming in that it is a managed
process with specific participants.
Cont’d….
Brainstorming is a group creativity technique by which efforts are made to find a conclusion
for a specific problem by gathering a list of ideas spontaneously contributed by its members

Requirement Gathering Techniques

➢ Interface analysis
➢ Interfaces for a software product can be human or machine.
➢ Integration with external systems and devices is just another interface.
➢ User centric design approaches are very effective at making sure that we create usable
software.
➢ Interface analysis – reviewing the touch points with other external systems is important
to make sure we don’t overlook requirements that aren’t immediately visible to users.
Cont’d….

◼ Interview
❑ Interviews of stakeholders and users are critical to creating the great software.
❑ Without understanding the goals and expectations of the users and stakeholders, we
are very unlikely to satisfy them.
❑ We also have to recognize the perspective of each interviewee, so that, we can
properly weigh and address their inputs.
❑ Listening is the skill that helps a great analyst to get more value from
an interview than an average analyst.
Cont’d….

Observation
❑ By observing users, an analyst can identify a process flow, steps, pain points and
opportunities for improvement.
❑ Observations can be passive or active (asking questions while
observing).
❑ Passive observation is better for getting feedback on a
prototype (to refine requirements),
❑ Active observation is more effective at getting an understanding of an existing
business process. Either approach can be used.
Cont’d….

• Prototyping
• Prototyping is a relatively modern technique for gathering requirements.
• In this approach, you gather preliminary requirements that you use to build an initial
version of the solution - a prototype.
• You show this to the client, who then gives
you additional requirements.
• You change the application and cycle around with the client again.
• This repetitive process continues until the product meets the critical mass of business
needs or for an agreed number of iterations.
Cont’d….

Cont’d

◼ Requirement Workshops
parties
• Workshops can be very effective for gathering requirements.
• More structured than a brainstorming session, involved
collaborate to document requirements.
• One way to capture the collaboration is with creation of domain-model
artifacts (like static diagrams, activity diagrams).
• Aworkshop will be more effective with two analysts than with one.
Cont’d….

Cont’d….
Reverse Engineering
➢When a migration project does not have access to sufficient
documentation of the existing system, reverse engineering will
identify what the system does.
➢It will not identify what the system should do, and will not identify
when the system does the wrong thing.

Cont’d….
Survey/Questionnaire
➢When collecting information from many people – too many to
interview with budget and time constraints – a survey or
questionnaire can be used.
➢The survey can force users to select from choices, rate something
(“Agree Strongly, agree…”), or have open ended questions allowing
free-form responses.
➢Survey design is hard – questions can bias the respondents.

• 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/
Requirement to develop a IoT Project

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.

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.
Enterprise Resource Planning (ERP) and Manufacturing Execution Systems (MES) share some
common purposes in the manufacturing environment.

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.

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.

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

Activities in Requirement Analysis &
Specification

Requirement Engineering Process

References
• https://www.tutorialspoint.com/business_analysis/business_analysis_
requirement_gathering_techniques.html

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.

➢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.

Cont’d
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.

Cont’d
➢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.

Cont’d
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

Cont’d
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.

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.

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.

02-03-2022 https://sites.google.com/view/arvindk
35

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?

➢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
➢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.

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.

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.

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.

Designing Use Cases for a Project
➢Before we start working on any project, it is very important that we are
very clear on what we want to do and how do we want to do.
➢What are Use Cases?
• In software and systems engineering, a use case is a list of actions or event steps,
typically defining the interactions between a role (known in the Unified Modeling
Language as an actor) and a system, to achieve a goal.
• The actor can be a human, an external system, or time.
• In systems engineering, use cases are used at a higher level than within software
engineering, often representing missions or stakeholder goals.
• Another way to look at it is a use case describes a way in which a real-world actor
interacts with the system.
• In a system use case you include high-level implementation decisions. System use
cases can be written in both an informal manner and a formal manner. (Wiki)

Designing Use Cases for a Project
➢What is the importance of Use Cases?
• Use cases have been used extensively over the past few decades. The
advantages of Use cases includes:
• The list of goal names provides the shortest summary of what the system will offer
• It gives an overview of the roles of each and every component in the system. It will help
us in defining the role of users, administrators etc.
• It helps us in extensively defining the user’s need and exploring it as to how it will work.
• It provides solutions and answers to many questions that might pop up if we start a
project unplanned.

How to plan use case?
➢Following example will illustrate on how to plan use cases:
➢Use Case: What is the main objective of this use case. For eg. Adding
a software component, adding certain functionality etc.
➢Primary Actor: Who will have the access to this use case. In the
above examples, administrators will have the access.
➢Scope: Scope of the use case
➢Level: At what level the implementation of the use case be.
➢Flow: What will be the flow of the functionality that needs to be
there. More precisely, the work flow of the use case.

How to plan use case?
➢Some other things that can be included in the use cases are:
• Preconditions
• Postconditions
• Brief course of action
• Time Period

Use Case Diagram
It would help us to understand the role of various actors in our
project. Various actors in the below use case diagram are: User and
System.
The main use cases are in the system and the diagram
illustrates on how the actors interact with the use cases. For eg.
During Sign Up, only users need to interact with the use case
and not the system whereas when it comes to categorizing
posts, only system would be required.

Developing a Use Case
➢When developing use cases you should start with a functional partition—a
listing of the major functional categories of the application. This will help
identify what areas need to be focused on.
• Step 1: Identify who is going to be using the system directly. These are the Actors.
• The main component of use case development is actors.
• An actor is a specific role played by a system user and represents a category of users that
demonstrates similar behaviors when using the system.
• The actors may be people or computer systems.
• A primary actor is one having a goal requiring the assistance of the system.
• A secondary actor is one from which the system needs assistance to satisfy its goal.
• One of the actors is designated as the system under discussion.
• A person can play several roles and thereby represent several actors, such as computer-
system operator or end user.

• Step 2: Pick one of those Actors.
• To identify a target system’s use case, we identify the system actors. A good starting
point is to check the system design and identify who it is supposed to help.
• Step 3: Define what that Actor wants to do with the system. Each of these
things that the actor wants to do with the system become a Use Case.
• The things that the actors want to do with the system become goals.
• The goal is the end outcome of the actions of the user.
• There are two types of goals. The first type is a rigid goal. This goal must be completely
satisfied and describes a target system’s minimum requirement. The second type of goal
is a soft goal.
• This usually describes a desired property for a target system and does not need to be
completely satisfied.
• To identify use cases, we can read the requirement specification from an actor’s
perspective and carry on discussions with those users who will function as actors.
• By defining everything that every actor will be able to do in interaction with the system,
the complete functionality of the system is defined.

• Step 4 For each of those Use Cases decide on the most usual course when
that Actor is using the system. What normally happens.
• A use case has one basic course and several alternative courses.
• The basic course is the simplest course, the one in which a request is delivered without
any difficulty.
• There may be alternative courses that describe variants of the basic course and the
errors that can occur. T
• hese are documented as extensions to the use case.
• Step 5: Describe that basic course in the description for the use case.
• The use scenario is written from the user’s perspective in view in easy to understand
language. This step is very similar to documenting a process flow.
• The steps necessary to achieve the identified goal are written out.
• Step 6 Once you’re happy with the basic course now consider the alternatives
and add those as extending use cases.
• The extensions are written in the same manner as the original use case but they provide
alternatives to the simplest path.

Business requirements for use case development
10 steps to a successful business case for IoT
➢Recognise the need for a business case
➢Start on the shop floor
➢Identify meaningful data
➢Employ predictive analytics
➢Track your products and assets
➢Create new revenue models
➢Move from drawing board to reality
➢Choose the right IoT platforms and partners
➢Build a proof of concept
➢Rollout at scale

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)

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.

IoT -enabled asset tracking
➢Track assets in real-time throughout the manufacturing factory
• How the IoT enables mobile asset tracking?
• Monitor equipment even in locations where humans can’t intervene
• Monitor equipment even in locations where humans can’t intervene
• Using IoT in Human Asset Management
https://technostacks.com/blog/how-iot-can-be-used-in-asset-management-tracking
https://www.hakunamatatatech.com/our-resources/blog/make-your-assets-work-for-you-call-it-iot/ 5/6

• 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

Business Requirements
➢Business Requirements describe why the organization is undertaking
the project.
➢They state some of the benefits that the organization or its customers
expect to receive from undertaking the project.
➢Business requirements may be documented in several ways such as a
project charter, business case, or in a project vision and scope
statement.
➢Business requirements help get the project owner, stakeholders and
project team on the same song sheet. But you can’t build software
from such high-level information.

Cont’d
We consider the following business requirements:
➢Problem Statement
➢Project Vision
➢Project Constraints (Budget, Schedule, and Resource)
➢Business Objectives
➢Project Scope Statements (Features)
➢Business Process Analysis
➢Stakeholder Analysis
➢IT Service Impact Analysis

Business requirements
➢Business requirements also define the scope of the solution. Solution
scope is generally defined using features.
➢Features are prioritized based on business value and implementation
complexity, and are later used for
➢eliciting stakeholder requirements and defining solutions
requirements. Not properly defining solution scope
➢generally results in scope creep and solutions that are not aligned
with business needs. Business requirements
➢are generally documented in a Business Requirements Document
(BRD).

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.

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.

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.

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.

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.

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.
https://www.indeed.com/career-advice/career-
development/how-to-write-a-problem-statement

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.

• 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

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://technostacks.com/blog/how-iot-can-be-used-in-asset-management-tracking
https://www.hakunamatatatech.com/our-resources/blog/make-your-assets-work-for-you-call-it-iot/ 5/6

THANK YOU !
ARVINDKR.NITT@GMAIL.COM
HTTPS://SITES.GOOGLE.COM/VIEW/ARVINDK

M 4 iot..

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to M 4 iot..

Similar to M 4 iot.. (20)

More from VIT VELLORE

More from VIT VELLORE (11)

Recently uploaded

Recently uploaded (20)

M 4 iot..