1. Core, Device Service, Application Breakout
6/1/2017

2. General Agreements
Importance of getting the APIs right trumps dealing with performance or other potential issues at this time
Use existing Java services for now
Focus on “quality” issues first
Minimal viable product must include base security/sys management services
Performance targets:
2GB memory
2-3 minute start/boot time
Latency times acceptable for now but need to be predictable. (300ms to export; 500ms from capture to actuation).
Build the first release toward “forgiving” use cases
Example – building automation
What we call the next formal release is TBD (beta, alpha, …??)
Target fall conference for unveiling (exact venue TBD and based on deliverable progress)
In parallel: work technology choices for theoretical minimum footprint and streaming data

3. Consensus MVP MVP security services and hooks into the other services
In particular – protect from the outside (e.g. – protect the service APIs)
Have a longer term plan/story
Acknowledge the APIs with change with security
MVP system management services and hooks into the other services
Review and stabilize the APIs of the other services
Including native data model
Improve the install process
Provide an export SDK or extension capability
Make it easier to get data out
MVP will be based on use case – what protocols / standards do we need to support to start?
Create a collection of device services from the SDK to support intended forgiving use case(s)
Virtual Device service (already done) also MVP
Improve and increase the examples and documentation
Require a testing process/framework (general QA effort)
Make sure all the microservices deliver when working together

4. Proposed Working Groups & Tasks
Device & Device SDK WG
Determine supported devices/protocols based on forgiving UC for first release
Build first Device Services
Virtual DS improvements as required
Add security & system management hooks into device services (and SDK)
Review APIs & SDK and recommend API changes
Add/improve DS docs/examples
Core WG
Review/stabilize core & supporting services APIs and internal data model
Responsible for overall MVP performance targets
Add security & system management hooks into core services
Add/improve core and supporting services docs/examples
Evaluation for lowering footprint and supporting streaming analytics in parallel

5. Proposed Working Groups & Tasks
Applications WG
Review/stabilize export layer APIs
Define supported MVP export protocols/standards for 1st release
Implement Export Services extensions (SDK?) & client registration to meet MVP
Add/improve export service docs/examples
QA/Test WG
Develop Test Harness/Framework
Provide means to measure performance, footprint, etc.

6. Proposed Working Groups & Tasks
DevOps WG
Improve EdgeX installation
Miscellaneous
Defer development of Roadmap to TSC
Defer naming and marketing of first release to the board
Define Use Cases and if they can be leveraged from other standards group

7. Potential Resource Contribution
Impact Labs – interest in device & core services
½ person
NetFoundry – interest in core and export services
1 person
IBM – global interest
1 ½ persons
Switch Automation – interest in drivers, fault detection
Unknown number at this time
Mainflux – interest in potential code contribution as well as device and core services
RFMicron – interest in device (specific sensor types) and core services
RFMicron – interest in device (specific sensor types) and core services
1 person
IoTech – interest in device SDK, core and export services
Unknown number at this time
Linaro – interest in device and core services
Canonical – interest in device services
Dell – global interest
3+ people