Scribd
Upload
385 views2 pages

1.1.3.12 Lab - Diagram A Real-World Process

The document describes three scenarios involving smart home processes: a lighting system that adjusts based on occupant movement, an irrigation system that detects soil moisture and weather, and a smart milk jug that detects pH and amount of milk and can order more. Students are asked to diagram each scenario and identify machine-to-machine, machine-to-person, and person-to-person connections.

Uploaded by

Zeidan Mohammad
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
385 views2 pages

1.1.3.12 Lab - Diagram A Real-World Process

The document describes three scenarios involving smart home processes: a lighting system that adjusts based on occupant movement, an irrigation system that detects soil moisture and weather, and a smart milk jug that detects pH and amount of milk and can order more. Students are asked to diagram each scenario and identify machine-to-machine, machine-to-person, and person-to-person connections.

Uploaded by

Zeidan Mohammad
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/ 2

Lab – Diagram a Real-World Process

Objectives
In this activity, you will diagram observable processes from real-world examples that include feedback
mechanisms.

Background/Scenario
Today, the IoE brings people, process, data, and things together by combining M2M, M2P, and P2P
connections. Information extracted from these networked connections creates new capabilities, richer
experiences, and economic opportunity.
In this activity, you will create a process diagram for a smart home. You will diagram subsystems, such as
lighting, a home irrigation system, and a smart milk jug. These subsystems will include feedback mechanisms
and the following three connection types: M2M, M2P, and P2P. You can use any of the diagramming
programs (Gliffy, Draw.io, or others) that you have explored in previous activities.

Scenario One: Lighting


In this smart home, the lights turn on automatically when the family is home in the evening. As the family
members move around the house, the lights adjust according to the pre-programmed level for certain
activities. For example, on a typical evening on a Saturday, the family has dinner and a movie at home. After
everyone has finished the meal, the dining room light turns off five minutes after everyone has left the room.
The family usually watches a movie in the media room after dinner. While the TV is on, the lights in the room
automatically adjust to a level suitable for viewing a movie.
The IoT connections evident in this scenario are:
1) M2M: The lights dim automatically when the TV is on.
2) M2P: The TV was turned on.
3) P2P: The family is enjoying a movie together.

© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 2
Activity – Create a Process Diagram for an IoT Solution

Scenario Two: Home Irrigation System


a. Create a scenario using a smart home irrigation system. The system can detect moisture levels in the soil
and use weather prediction to adjust the watering schedule.
b. Use a diagramming program to create a process diagram.
c. Describe the IoT connection types.

Scenario Three: Smart Milk Jug


a. A smart milk jug detects the pH level and remaining quantity of the milk in the jug. The milk jug can alert
the user when the milk is spoiled by measuring the pH level of the milk. An application can wirelessly
connect to the milk jug and inform the user of the quality and quantity of the remaining milk. The
application can also provide recipes for both fresh and spoiled milk. The application may also order the
milk from a grocery delivery service.
b. Use a diagramming program to create a process diagram.
c. Describe the IoT connection types.

© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 2

You might also like