You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Micro-fulfillment Center app template tutorial | Microsoft Docs
3
-
description: A tutorial of micro-fulfillment center application template for IoT Central
2
+
title: Micro-fulfillment center app template tutorial | Microsoft Docs
3
+
description: A tutorial about the micro-fulfillment center application template for Azure IoT Central
4
4
author: avneet723
5
5
ms.author: avneets
6
6
ms.service: iot-central
@@ -11,98 +11,81 @@ ms.date: 01/09/2020
11
11
12
12
# Tutorial: Deploy and walk through a micro-fulfillment center application template
13
13
14
-
In this tutorial, we will leverage the Azure IoT Central ***Micro-fulfillment center*** application template to show you how to build a retail solution. You will learn about how to deploy the MFC template, what is included out of the box and what you might want to do next.
15
-
16
-
In this tutorial, you learn how to:
17
-
> [!div class="checklist"]
18
-
> * Use the Azure IoT Central **Micro-fulfillment center** template to create a retail application
19
-
> * Walk through of the application
14
+
In this tutorial, you use the Azure IoT Central micro-fulfillment center application template to build a retail solution. You learn about how to deploy the template, what's included in it, and what you might want to do next.
20
15
21
16
## Prerequisites
22
-
To complete this tutorial series, you need:
23
-
* An Azure subscription. You can optionally use a free 7-day trial. If you don't have an Azure subscription, you can create one on the [Azure sign-up page](https://aka.ms/createazuresubscription).
17
+
To complete this tutorial series, you need an Azure subscription. You can optionally use a free 7-day trial. If you don't have an Azure subscription, you can create one on the [Azure sign-up page](https://aka.ms/createazuresubscription).
24
18
25
19
## Create an application
26
20
In this section, you create a new Azure IoT Central application from a template. You'll use this application throughout the tutorial series to build a complete solution.
27
21
28
22
To create a new Azure IoT Central application:
29
23
30
-
1.Navigate to the [Azure IoT Central application manager](https://aka.ms/iotcentral) website.
31
-
1. If you have an Azure subscription, sign in with the credentials you use to access it, otherwise sign in using a Microsoft account:
24
+
1.Go to the [Azure IoT Central application manager](https://aka.ms/iotcentral) website.
25
+
1. If you have an Azure subscription, sign in with the credentials you use to access it. Otherwise, sign in by using a Microsoft account:
32
26
33
-
27
+
34
28
35
29
1. To start creating a new Azure IoT Central application, select **New Application**.
36
30
37
31
1. Select **Retail**. The retail page displays several retail application templates.
38
32
39
33
To create a new micro-fulfillment center application that uses preview features:
40
-
1. Select the **Micro-fulfillment center** application template. This template includes device templates for all devices used in the tutorial. The template also provides an operator dashboard for monitoring conditions within your fulfillment center as well as the conditions for your robotic carriers.
34
+
1. Select the **Micro-fulfillment center** application template. This template includes device templates for all devices used in the tutorial. The template also provides an operator dashboard for monitoring conditions within your fulfillment center, as well as the conditions for your robotic carriers.
44
37
45
-
1. Optionally, choose a friendly **Application name**. The application template is based on the fictional company Northwind Traders.
38
+
1. Optionally, choose a friendly **Application name**. The application template is based on the fictional company Northwind Traders.
46
39
47
-
>[!NOTE]
48
-
>If you use a friendly **Application name**, you still must use a unique value for the application **URL**.
40
+
>[!NOTE]
41
+
>If you use a friendly application name, you still must use a unique value for the application URL.
49
42
50
-
1. If you have an Azure subscription, enter your *Directory, Azure subscription, and Region*. If you don't have a subscription, you can enable **7-day free trial** and complete the required contact information.
43
+
1. If you have an Azure subscription, enter your directory, Azure subscription, and region. If you don't have a subscription, you can enable 7-day free trial, and complete the required contact information.
51
44
52
-
For more information about directories and subscriptions, see the [create an application quickstart](../preview/quick-deploy-iot-central.md).
45
+
For more information about directories and subscriptions, see the [Create an application](../preview/quick-deploy-iot-central.md) quickstart.
58
50
59
51
## Walk through the application
60
52
61
-
### Dashboard
62
-
63
-
After successfully deploying the app template, you will first land on the **Northwind Traders micro-fulfillment center dashboard**. Northwind Trader's is a fictitious retailer that has a micro-fulfillment center being managed in this IoT Central application. On this operator dashboard, you will see information and telemetry about the devices in this template along with a set of commands, jobs, and actions that you can take. The dashboard is logically split into two sections (left and right). On the left, you have the ability to monitor the environmental conditions within the fulfillment structure and on the right, you can monitor the health of a robotic carrier within the facility.
53
+
After successfully deploying the app template, you see the **Northwind Traders micro-fulfillment center dashboard**. Northwind Traders is a fictitious retailer that has a micro-fulfillment center being managed in this Azure IoT Central application. On this operator dashboard, you see information and telemetry about the devices in this template, along with a set of commands, jobs, and actions that you can take. The dashboard is logically split into two sections. On the left, you can monitor the environmental conditions within the fulfillment structure, and on the right, you can monitor the health of a robotic carrier within the facility.
64
54
65
-
From the dashboard you can:
66
-
* See device telemetry such as # of picks, # of orders processed, and properties such as the structure system status, etc.
67
-
* View the **floor plan** and location of the robotic carriers within the fulfillment structure.
68
-
* Trigger commands such as resetting the control system, updating carrier's firmware, reconfiguring the network, etc.
55
+
From the dashboard, you can:
56
+
* See device telemetry, such as the number of picks, the number of orders processed, and properties, such as the structure system status.
57
+
* View the floor plan and location of the robotic carriers within the fulfillment structure.
58
+
* Trigger commands, such as resetting the control system, updating the carrier's firmware, and reconfiguring the network.
69
59
70
-
> [!div class="mx-imgBorder"]
71
-
> 
72
-
* See an example of the dashboard that an operator can leverage to monitor the conditions within the fulfillment center.
73
-
* Monitor the health of the payloads running on the gateway device within the fulfillment center.
60
+
61
+
* See an example of the dashboard that an operator can use to monitor conditions within the fulfillment center.
62
+
* Monitor the health of the payloads that are running on the gateway device within the fulfillment center.
74
63
75
-
> [!div class="mx-imgBorder"]
76
-
> 
64
+
77
65
78
-
## Device Template
79
-
If you click on the Device templates tab, you will see that there are two different device types that are part of the template:
80
-
***Robotic Carrier**: This device template represents the definition for a functioning robotic carrier that has been deployed in the fulfillment structure and is performing appropriate storage and retrieval operations. If you click on the template, you'll see that the robot is sending device data such as temperature, axis position and properties like robotic carrier status, etc.
81
-
***Structure Condition Monitoring**: This device template represents a device collection that allows you to monitor environment condition as well as the gateway device hosting various edge workloads to power your fulfillment center. The device sends telemetry data such as the temperature, # of picks, # of orders, etc. in addition to state and health of the compute workloads running in your environment.
66
+
## Device template
67
+
If you select the device templates tab, you see that there are two different device types that are part of the template:
68
+
***Robotic Carrier**: This device template represents the definition for a functioning robotic carrier that has been deployed in the fulfillment structure, and is performing appropriate storage and retrieval operations. If you select the template, you see that the robot is sending device data, such as temperature and axis position, and properties like the robotic carrier status.
69
+
***Structure Condition Monitoring**: This device template represents a device collection that allows you to monitor environment condition, as well as the gateway device hosting various edge workloads to power your fulfillment center. The device sends telemetry data, such as the temperature, the number of picks, and the number of orders. It also sends information about the state and health of the compute workloads running in your environment.
82
70
83
-
> [!div class="mx-imgBorder"]
84
-
> 
71
+
85
72
86
-
If you click on the Device groups tab you will also see that these device templates automatically have device groups created for them.
73
+
If you select the device groups tab, you also see that these device templates automatically have device groups created for them.
87
74
88
75
## Rules
89
-
When jumping to the rules tab, you will see a sample rule that exists in the application template to monitor the temperature conditions for the robotic carrier. You could use this rule to alert the operator if a specific robot in the facility is overheating and needs to be taken offline for servicing.
90
-
91
-
Please leverage the sample rule as inspiration to define rules that are more appropriate for your business functions.
76
+
On the **Rules** tab, you see a sample rule that exists in the application template to monitor the temperature conditions for the robotic carrier. You might use this rule to alert the operator if a specific robot in the facility is overheating, and needs to be taken offline for servicing.
92
77
93
-
-**Robotic carrier too warm**: This rule will trigger if the robotic carrier reaches a temperature threshold over a period of time.
78
+
Use the sample rule as inspiration to define rules that are more appropriate for your business functions.
94
79
95
-
> [!div class="mx-imgBorder"]
96
-
> 
80
+
97
81
98
82
## Clean up resources
99
83
100
-
If you're not going to continue to use this application, delete the application template by visiting**Administration** > **Application settings** and click**Delete**.
84
+
If you're not going to continue to use this application, delete the application template. Go to**Administration** > **Application settings**, and select**Delete**.
101
85
102
-
> [!div class="mx-imgBorder"]
103
-
> 
86
+
104
87
105
88
## Next steps
106
-
* Learn more about the [micro-fulfillment center solution architecture](./architecture-micro-fulfillment-center-pnp.md)
107
-
* Learn more about other [IoT Central retail templates](./overview-iot-central-retail-pnp.md)
108
-
*Learn more about IoT Central refer to [IoT Central overview](../preview/overview-iot-central.md)
89
+
* Learn more about the [micro-fulfillment center solution architecture](./architecture-micro-fulfillment-center-pnp.md).
90
+
* Learn more about other [Azure IoT Central retail templates](./overview-iot-central-retail-pnp.md).
91
+
*Read the [Azure IoT Central overview](../preview/overview-iot-central.md).
0 commit comments