Scenario One B: Configurator
- Joseph Pearson
A cell phone and/or tablet app will be created that can register an Edge Node (Scenario One A) or Edge Device (Scenario Two), onboard that device to an Open Horizon exchange running on a farm gateway machine (Scenario One C), and configure that node or device. Additionally, it should be able to re-configure an already-onboarded node or device. It should also be able to decommission a node or device (unregister).
Target release | |
|---|---|
Epic | |
Document status | DRAFT |
Document owner | @Joseph Pearson |
Designer | |
Developers | |
QA |
Goals
Scan a QR code or similar to identify Edge Device type, capabilities, optionally purpose
Connect device to software running on a specific local Edge Node
Specify the Edge Device purpose through properties and constraints
On-board the Edge Device to enable data collection and set up actions/triggers and events
Enable person to re-configure an existing (already on-boarded and functioning) Edge Device
Enable person to de-commission and un-register an Edge Device
Background and strategic fit
Link to arch design of mimik edgeEngine/Open Horizon integration.
Assumptions
An Edge Node already exists an contains a registered Agent and a workload for managing Edge Devices
A QR code or similar has been created with the required information and attached to the Edge Device
Requirements
Title | User Story | Importance | Notes | |
|---|---|---|---|---|
| 1 | Investigate mimik's Edge SDK for suitability | |||
| 2 | Identify existing API calls for on-boarding, modifying, registering, un-registering, identifying Edge Node to use | See GitHub Issue #1 |
| |
| 3 | Identify data needed to encode in QR code on Edge Device | |||
| 4 | Create mechanism and process for printing QR code (sticker?) |
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|