 Hello, I'm Glenn Darling from the Open Horizon team, and I'd like to talk to you about secure device onboarding with Zero Touch. Imagine being able to buy diverse edge devices from various distributors or retailers, shipping them off to one of your remote sites like a store, or a power plant, or a substation, or any of your remote locations, and then just getting the local technician to plug the thing in, apply power and network, and then have it magically, okay, not magically, but fully autonomously, install and configure all of the required software, no SSH, no USB, nothing else. Would that help your business? Would that enable you to save some money? Well, Open Horizon with secure device onboarding, or SDO, will do exactly that on Intel and ARM devices, and optionally it can use the hardware root of trust, or like a trusted platform module if you have it on the device. So how does it work? First of all, the SDO software is installed at the manufacturer, and then an ownership voucher is created, and it always goes along with the device. The ownership voucher stays with the device as it goes through the whole supply chain, so factory to distributor to whatever, and ends up at the end customer. Then when the end customers receive the devices and their vouchers, they load the vouchers into an Open Horizon management hub. And then in turn the Open Horizon management hub uses this voucher to tell the SDO rendezvous server how to install the Open Horizon agent onto the corresponding device and configure it for this specific management hub. Now from that point onward it's fully automated, and we have our little agents that are going to take care of everything for us, so it'll be zero touch. So once the voucher is loaded onto Open Horizon, and the SDO rendezvous server has been informed, the customer can then just start connecting their devices. On first power-up each device reaches out to the well-known address of the SDO rendezvous server with an identifier corresponding to its specific ownership voucher. The SDO rendezvous server responds with an Open Horizon agent install script and configuration details for this specific device. Then the SDO rendezvous server is no longer required. The device can then automatically install and configure the agent for the appropriate Open Horizon management hub, and that happens without any user action at all. The configuration includes the appropriate Open Horizon device credentials and the deployment pattern or policy. The agent will then reach out to the management hub and negotiate the appropriate software deployment using normal Open Horizon procedures. So let's do a quick review. In the factory, ownership vouchers are created and SDO software is installed onto the device. Vouchers and devices stay together all the way out to the customer. The end customer loads the vouchers into an Open Horizon management hub, and the Open Horizon management hub sits up the SDO rendezvous server for each individual device. With zero touch, the devices power up, contact the SDO rendezvous server to get their install scripts and their configuration details. The device is then installed and configured the Open Horizon agent, and then from then on the Open Horizon agent can take control, negotiate with the Open Horizon agbots as usual to manage all of the containerized application software life cycles on the device from then onward. So this is available now as a tech preview only, so it's not for production use in IBM Edge application manager version 4.1, which is an Open Horizon installation. If you wish to get some more information about this, you can use the URL shown in yellow on the screen here. Hope you enjoyed this presentation and make good use of our SDO support.