**Draft**

Announcement

With the Hanoi release, EdgeX Foundry announces the availability of EdgeX Ready.

What It Is

The EdgeX Ready program is about demonstrating the ability to work with EdgeX.  The designation helps other community participants and solution vendors identify vendors who have gone through a self-assessment process to demonstrate that they are able to integrate one of their offerings with solutions using EdgeX.  Those vendors who have joined the program are highlighted on the EdgeX Foundry website with an EdgeX Ready badge next to their logo.

The initial, “crawl,” phase of the “self-assessment process” is to simply validate a device profile.  Users attest that they have authored a device profile and moved device-specific data through an EdgeX instance that they had set up themselves thereby demonstrating some familiarity with EdgeX and, more specifically, of device services and their associated device profiles.  Upon submission and approval of their device profiles and sample data, the users’ logos will be badged on the EdgeX Foundry website.

We are initially launching with MQTT- and REST-based device profiles.  This is just the beginning.  With community interest, we will expand the program to support additional device services.

Self-Assessment Process

We ask the vendors to do the following:

1. Instantiate an instance of the reference implementation of EdgeX with their device profile

2. Using a device that is described by their device profile, generate sample data, and send it to the appropriate device service

3. Confirm that the data arrives in Core Data
4. Validate their device profile using one of the tools provided by the Certification WG
5. Submit their validated device profile and sample data to the EdgeX Ready program

This workflow diagram below may help with understanding the process:

Device Profile Validators

[TBD]

Required Public Materials

The following materials are required to included in the EdgeX Ready Program submission:

• Participation Form – PDF (.pdf), Word document (.docx), possibly Open Document Format (ODF) Text Document (.odt)
• Device Profile – YAML (.yaml)
• Associated sample data – JSON (.json)
• Sample data schema – JSON (.json)
• (Optional) UUID of the device profile, if validated using IOTech's DCT website, in the form of 123e4567-e89b-12d3-a456-426614174000

Contributions

We at the EdgeX Foundry are very much interested in providing the EdgeX community with multiple options for validating device profiles for the EdgeX Ready Program.  If you have your own EdgeX validator and would like to contribute the implementation as open-source or share the service with the EdgeX community and the EdgeX Ready program specifically, we are interested in hearing from you!  Please reach out to us on Slack at #edgex-ready, email us at edgex-ready@edgexfoundry.org, or contact the Certification Team WG Chair directly at rodney@beechwoods.com and we can discuss next steps.

Availability

EdgeX Ready will be announced before the end of 2021.

FAQ

What does it cost to be EdgeX Ready?

No - the only requirement is that you sign up and become an EdgeX User

Do I need to have real sensors or devices to become an EdgeX Ready User?

No - using the MQTT and REST device services, you must be able to demonstrate that you can get data into EdgeX as a sensor or device would do, but you do not need a real sensor or device to accomplish the EdgeX Ready program.

TODO - Other things to address in this Wiki

• More details on the process.  Steps in the process.  Where to go for the tools.  What is accomplished at each step?  Wonder if we could create a diagram where each step is "click in" to get detailed instructions?
• Do we address EdgeX Ready in relationship to a particular version (maybe address this in the FAQ)?
• More info on EdgeX User - how to become one and where to go