 Next, I actually do want to have a conversation. I'm going to invite Fareed from Kone up. And we're going to have a talk about how Kone is using Cloud Foundry to support a very specific industrial use case. So Fareed, come on up. Thank you for joining us. Thank you for having me. Have a seat. Thank you. All right. Let me get my notes here. Otherwise, I'll ramble aimlessly. Sneak, sneak. Excellent. So why don't we first start with can you introduce yourself and I think tell others what does Kone do? Sure. Kone is a manufacturer of elevators, escalators, and automatic doors. We build both hardware and software for our products. I'm leading the IoT architecture team in Kone. Additionally, we also provide maintenance and residential services for our users. So all the products that we actually manufacture, we also service them ourselves. So we have a large number of service technicians who are visiting the sites and maintaining those equipment, as well as we are now starting to provide new services for our residential customers as well. So passengers would be able to call the elevators remotely. So imagine the scenario that you wake up, you get ready to go to work, and already in your apartment, you call the elevator that by the time I reach the lobby, the elevator should be waiting for me. So that's, for example, one of the use cases that we have accomplished with SELF. So I must be dense because I frankly didn't know about Kone until we had our first conversation. But now I notice that the elevator in the hotel that I'm staying at is from Kone. Does the app work yet? Because I've had to wait a couple of times. It does, but probably not for that building. I'll ask the constable. So we are still building those applications. So IBM is basically our main partner in the IoT development that we are doing together with the BlueMix, which is essentially based on a cloud foundry for the versions that we're using. In the public cloud, we are building applications on Liberty Java runtime and Node.js applications like how we manage our devices. So essentially, we use Watson IoT platform to perform device management, operations like updating remote configurations, updating remote software. But those are key functionalities that we use from Watson IoT. Essentially, that is a product available as a service. But there are a lot of things which are then Kone specific, which are unique to our business use cases and our business model. And those business logic and part of the business processes we have implemented then as Node runtime applications on cloud foundry. So essentially, we are using both the service aspect of cloud foundry and the application aspect, the application runtime aspect of it. And I think you told me when we were speaking earlier that you're making use of not just the cloud foundry runtimes, but some of the services, the backing services that are unique to IBM. So you're using, I believe, the Watson IoT service? Sure. Mainly, our IoT platform is connected with the Watson IoT services. But then a lot of the applications that we are developing that are then used by our maintenance technicians to diagnose our elevators and our residential customers to call the elevators are based on Node and Java runtime applications, which then use services like Kafka, Qs, or Message Hub from Bluemix perspective, or Swift, or Object Storage. So a lot of open source platform and services like CouchDB and Cloudant and so on are used as part of our portfolio. Great. One of the things we frequently hear when somebody comes up to tell us about their story of adoption of cloud foundry or one of the distributions, is that frequently it's a process of adopting organizational change at the same time as you do the technology change. But you had a slightly different story. Yeah, we have been developing software for long periods of time. So all the elevators and escalators that we manufacture actually have Kony designed and developed software. So for our software development department, we have been using agile and safe framework for several years now. So when we started doing our IoT development, our IoT program was simply an add-on to our existing Lyft software and people flow software and other software programs that we have already in our organization. So it was quite an easy fit. We have quarterly planning teams get together from IoT teams to device development teams to group development teams. All these teams get together and we build the plan, the software development together. Cool, cool. Why don't you walk through one of the example applications that you've developed? Sure, sure. You talked about API wrapping, that type of thing. Yeah, so these are the examples that we just discussed mainly on how we are configuring and controlling our elevators remotely. But at the same time, we are developing and evolving an ecosystem around the residential and people flow business areas. So if you're interested, and I would recommend that you go and visit developer-api.cony.com. And you will see a list of APIs that developers can actually use to build their own applications. And those APIs are then built on API Connect, which then again, another service that we use from IBM Bluemix, essentially running on a Cloud Foundry. And the supporting business logic for those APIs are again built as no run times and in Java applications. So what's interesting is that you're kind of becoming a, or you're hoping, to have a bit of a technology platform business model, where a lot of you have devices everywhere. And that has a lot of data and has a lot of potential for interesting use cases. So what are some of the things you've been doing to try to create a developer ecosystem and inspire developers to work with your APIs? We have been partnering with a different small to medium size company. So we have partners from companies from Estonia, naturally closer fit to Finland to start with, and companies from all over the world, where we are working directly with those partners and registering those partners as our API users. So essentially we are trusting them to be part of the ecosystem, to build the applications together with us, that then our end users and customers can use. At the same time, internally within Kone, we are also building applications using those same APIs to help our passengers and users use those equipment and services. Excellent, excellent. So you're at the Cloud Foundry Summit, and there's a number of people here that, lots of them use Cloud Foundry, but there are some developers and project leads that are part of the community. So can you maybe give us a couple of examples of things that you'd like to see out of the upstream so that IBM can productize it? Sure, sure. Yeah, so it's always challenging because things are developed and released from Cloud Foundry and Productize, and then IBM takes them in and releases them, and then eventually they become available for the customer. But some of the things that we have been really looking forward to, and okay, I was in some of the sessions yesterday for UAA, and I understood that those are actually now on the roadmap and coming soon. So one of the things which is interesting is fine-grained access control and fine-grained user management, which we are really looking forward to so that we are able to work with multiple development partners in similar spaces or organization or in similar runtime environments where we can limit the access for those users or developers as we would please. Yeah, it's actually a request that we've heard from a lot of end users, and I think just as importantly, the community responded, the project just got spun up specifically to go do a lot of that work in combination with our UAA project team. So hopefully it gets done. It gets done in a way that is helpful to you and I'd encourage you to interact with the project teams so that you can be someone who's feeding your use case examples. Definitely. Excellent. All right. Well, thank you so much for coming. I appreciate it. Thank you for having me. Great to be here. All right, thank you. All right, thank you very much.