 I'm Mark Proctor, and I'm the platform architect for BMS and BPMS. I'm a co-founder with Bob McWhorter, who's also at Red Hat, of the open source drills rule engine. I joined Red Hat ten years ago as a team of one, which have built up size B since then. I'm involved in the innovation side, inspiring and leading the open source projects, and I'm also involved with the product, making sure we deliver something that's stable and mature for our customers. BMS is a platform for automating decisions. We include a variety of things from solving mortgage applications to situational awareness, to helping to automate medical situations. It's quite an exciting field because of the variety of areas which you can help, whether it's financials, medical, telecoms. It's everywhere. BMS has always been popular with engineers because it allows them to get in and change things and not tied into a tightrope that can only go in one direction. So it means that, yes, we try and provide high-level tooling to get things done, but when they need to, they can get down and get mucky with the code. And that's one of our differentiators. One of the things we're working on in the 7 Series is to have a massive improvement in our tooling to really get it to the next level so that we can not just be a tool that's really popular with developers because it allows you to get deep and low with the code, but also it means we can appeal more to the citizen developers, which is our big theme for the 7 Series, which is going to happen towards the end of this year. We want people to be able to build applications end-to-end with our tooling. So we're going to go from being something developer-orientated with engines and with code, going all the way up to the stack with graphical drag-and-drop builders. Part of this effort has been a big push on usability. We've done a big investment on UXD. You have new designs. The entire tooling from top to bottom has been refreshed, been rewritten, and it's looking really quite professional so I'm personally very proud of it. So you have the new form builder, which is built on bootstrap grid views. And this allows you to have a responsive design and you can resize the forms from desktop to tablet to mobile devices. And it's a very slick layout tool. The same layout technology we use for forms can also be used for the new dashboard technology, which means you can drag charts with actually extensibility as you can write your own components and position those on the page. One of the core pieces of the BMS and the BPS product is the design of the BPM design that we use. On the rule side it's used for rule flow, how we orchestrate the organisation of our rules. On the process side it's used for the BPM spec. The core part of this is the BPM designer, which we've done a substantial effort into, working with the Lienzo community to deliver a next generation designer, something we believe now is going for commercial quality. One of the more interesting things going on within the BMS community right now is the Decisional Model Innotation Specification, DMM. This is used for decision tables and it integrates as part of a decisions requirement diagram which is used to integrate with the BPM end spec. So there's an overlap between the two. We've put a big effort in recently to revamp the decision tables and we've been working again with the Lienzo technology to have these new highly scalable decision tables that work within Decisional Model Innotation Specification. We'll provide an end-to-end low-code environment for application developments. We'll be able to deliver this on OpenShift and that means people can get going straight away without having to download and install anything. This is going to be a great way of us to be able to provide a business process path solution. One of the things I'm quite proud of working with industrialising nations is our relationship we've built with OSTI. OSTI is Argentina's largest health co-organisation and we've been working with them a number of years, started just from working with the developers in an open source environment, helping them to get to learn what the technology is. That was very successful. It gets noticed by their managers and their managers are even more successful with it and that's noticed by their managers. We build a relationship now right from the lowest developers right up to the CEO level. The relationship we have with OSTI has been quite a dynamic one. We've built relationships with developers which has allowed us to understand how the industry works and that's given us better ways to improve our development software. On the other side as well, we as Red Hat are leaders in open source distributed development, collaborative development and that's expertise we can give back to them how to improve how they write software, how to work with open source and how to make the best out of open source. We've also worked with them to play our part in OSTI ownership and to help the main focus of what we've done together is to help improve the customer experience.