1. Certification Plan
EdgeX TSC F2F
May 1, 2019 1

2. Certification Objective
Support multi-vendor ecosystem
Public commitment to API and use standards
Reduce risk for users (improve adoption)
Plan document:

3. Scope EdgeX “Components”
Device Services
Application Functions
Core Services
For now, does not attempt to certify full implementations or components that don’t interact with core

4. EdgeX Certified Components will…
Be compliant with the EdgeX APIs for its type of service
Be interoperable with other EdgeX services
Support for EdgeX system management agent
Be robust; reliable, able to recover from faults, start in any order, wait for dependent services, etc.
Provide documentation on functionality and deployment
Not negatively impact the operation of other EdgeX services

5. Certification Levels Self-Assessment Formal Certification
Organization conducts self-evaluation to confirm meeting defined requirements
Formal Certification
Testing conducted by neutral certification authority

6. Recommendation based on TSC Discussion
Do Self-Assessment first
Assessment is black box tests + checklist of instructions
Start with Device Services, but others if possible
Available by end of 2019 using artifacts from Fuji release
Define process to promote “assessed” components

7. Planning Requests Technical Business Black box tests
EdgeX “test harness”
Documentation on assessment procedures and results to capture
Business
Program promotion (“EdgeX Ready”?)
Review process for promoting assessed components

8. Certification WG Meetings Mondays, 7am PDST
Plan document:
Randy Thompson

9. Assumptions Do not require submitters to provide source code.
Services submitted for certification are expected to be packaged in Docker/Docker Compose.
EdgeX is agnostic with regard to platform hardware and OS, but that platform independence is not tested.  
Certification is not dependent on the programming language or technology used in the service.
EdgeX is orchestration agnostic.  Services should be designed that way and should not make any assumption about orchestration/ QoS
Certification will be to an EdgeX release.