1. System Management Working Group

2. System Management Big Questions
Edge Device/ Host Management versus EdgeX Device Management versus Device Management
Are you containerized or not? Do you have control of the host or not? Restarting the EdgeX service tree versus restarting the host. How much control in/out of the container?
Target: EdgeX Device Management
Several management standards available:
TR-069, LwM2M, MEC
Target LwM2M as the launch management protocol
How much management?
Base LwM2M set: i.e. Start, Stop, Restart
How Much Monitoring? Is Alive versus Is Healthy
Target: Is Alive
To be investigated:
Onboarding
Commissioning
Identity
Dependencies
Need device identity from Security
Health status and primitives functionality in core
Out of Scope
OTA Updates
Configuration Management
Health monitoring
Connected Device Management

3. Systems Management Initial release Systems Management Microservice
1 simple E2E reference path
Leverage an open source tool to demonstrate Server Side device management on a simple identity pool

4. Future Questions Policy on the edge Health Monitoring
Ownership transfer
Manufacturer firmware
Manufacturing onboarding
Health Monitoring

5. Identity
Local provisioning of an EdgeX device to give it a UUID as its identity. Hardware and software.
How to establish identity? Certs, local generation, blockchain
Identity is a module – Use a centralized, local, hardware, generated.
Bootstrapping: Identity, Configuration Management, Service Provisioning
EdgeX gets identity within the domain of EdgeX – this may be EdgeX- unique or tied to the container or OS. It is distribution and implementation dependent.

6. Management Specifications
TR-069
MEC
LwM2M
Firmware Management
Hawkbit
Container Management
MANY