 Please a warm welcome for for Eldar and Kai and remotely for for Karsten. So Welcome gentlemen over to you. Thank you Steve. Oh Hope you guys can hear me. Thank you for having us We'll present a few insights into the reference architecture Aviation that we've been drawing up with Lufthansa Don't know if you know Lufthansa at all kept Gemini, but I assume you do Lufthansa, how much do we know about Lufthansa? Lufthansa is a group of company quite diverse And as a group also contains not just Lufthansa, but Austrian Swiss Brussels German wings and Euro wings and that little fact of having low-costers and full-service airlines is going to come Into the presentation a little bit later on so in case you can't understand me that's probably because I Spend a little bit of time in in Africa small place called Cape Town and then moved across to a little island called Australia So not too far from here small place Melbourne So if you don't get my accent, I do apologize Just let me know and I'll try to kind of come up with the proper high English word for it. Anyway, shall we get into it? Who of you Has ever been involved in drawing up a reference architecture? I'll quite a few people cool That's a lot of a lot of hands that went up. I might just see if we can Because it is quite a quite a significant undertaking doing a reference architecture and it's Especially in an industry that is as diverse as an example as the aviation industry there's a whole heap of things that Need to be kind of considered So why would we do a reference architecture in aviation? When I went back from from the small island somewhere in the southern Pacific To small place in the center of kind of Europe called Frankfurt we had a significant challenge around Around skills and resources at Lufthansa and Kepgemina and Lufthansa have been Partners for a long long time and Gemini has supported the development of the architecture capability and management capability for Eons So going back a bit like what Chris was saying. There's a there's a significant shortage of skills in the market and Castin and I at some stage Sit down and said, how do we deal with this? We've got so many people here working on so many things and We don't really find the right skills And at some stage I just went To him I think he's probably going to claim it was over a coffee I believe it was a beer or two, but I can't really remember And I said, let's just come up with a reference architecture as a tool to educate our architects coming from different industries and having to work on significant projects within within Lufthansa so we did Our challenges as I mentioned that we had and Chris also mentioned it it is Probably stand a bit like what everyone here would have Would have experienced it's it is plenty of politics every large organization Suffers from politics and the alignment to strategy We've heard also Chris early on talking about how do I provide the right value at the right time? To my customers and back into the organization As I mentioned we didn't have We didn't have enough people and not enough people with the right skills and we thought our reference architecture Would be one building block to help us out Drive those adoption of skills and obviously the aviation IT knowledge is quite scarce nowadays ten years ago a lot of aviation IT professionals obviously left the industry because of circumstances and the global downturn and obviously bringing them back online is quite quite a challenge We had a another challenge around the content that we saw within within the aviation industry Managing Knowledge managing the artifacts are not really that simple. So we figured Why not put another? Reference architecture on top and make it really unmanageable and Then the standard challenge Right budget who's got the cash to fund this work because it's obviously not simple and takes a bit of time and So this this kind of the formator challenges, I'm sure Everyone who's worked in this space would have probably come up against similar challenges So we figured as I said, you know a beer or coffee later. We've got These these challenges sorted out so we had kind of intricate domains across the whole group of love tons are we had Varying management support mainly none initially We had a global group of companies Plenty of corporate politics and and about 14 architects and about 28 opinions on How to go about doing it. So we said it's a great idea. All right, you can't have better Kind of a better starting position than this So we called Chris and said Chris you're part of the open group. You've done this before Can you come and help us set this up? Chris came in We had a brilliant discussion about it and said from now on we're gonna drive that five star aviation reference architecture Five stars because of what anyone an idea Full service airline. We had a long discussion forever in a day whether we should do a reference architecture for the new Airlines a low-cost airlines a completely different business strategy segmentation business focus priorities design principles all of it versus the traditional Full carrier architecture that kind of the you'd associate with with the love tons of group So he said all right, let's do the five star aviation reference architecture Oh Okay, oh Keep going with this. So we had a team and Ella's gonna kind of introduce the the most important architects quickly to you Okay on this slide we we see our crew of architects and Also people from the Lufthansa group also architects the three Main person are a Kai cast and bright hop as already mentioned and me as a lead architect of this project and we have Other architects that are responsible for modeling each Domain which is part of our reference architecture Yes, this crew my grow or What can be the same as now it's it's it's a agile It's a agile team The next slide So maybe just one last item on this we we sat down and we figured What's the point of driving a reference architecture that only two three? Kind of outstanding architects worldwide will be able to draw up and then communicate We've got a skills and resource shortage to deal with so let's just put it on kind of as many shoulders as we can right Of course you're gonna lose one or two people going in and coming into the project or Leaving the project so there's a little bit of movement all the time But we started with a with a group of 14 architects just just assembling the 14 architects here was Tiny little bit of a challenge But it was important for us to kind of spread the word and the workload the base that we had to deal with just as a Again people that have done this before they're probably just not in anger here Documentation we had a plethora of documents sitting everywhere artifacts Kind of project deliverables different different cycles and at that stage Lufthansa was going to a major transformation three major programs Roughly spending about 250 million dollars to kind of earn the fifth star that for for customer What's it called? experience customer experience and a massive bi implementation on kind of focusing more on on The operations and then obviously a revenue management project that we also dealt with We had tacit knowledge to spot everywhere We invited kind of two or three people to come in and talk to us about the business domains and Experts that would come and sit us and they normally brought along another five or ten people to to just have a discussion access to material was pretty limited because no one was willing to kind of give up their They're smarts or the other gems for us to be able to do to then Put it into into the reference architecture and we had standards I mean the standard was that we had plenty of standards, right? You know how it goes there was not a standard that we didn't have so we figured we needed some sort of an intuitive framework and Some models to be able to drive this in a consistent fashion and our budget plenty of discussions plenty of Ways of working it So the big question was always, you know, who pays for what and when and then who gets the benefits and there's phenomenal Anytime we talked about benefits here benefits for you to claim we had cues of the office buildings For everyone to put their hands up and say I want to share this but when it came to You know, can you put some dollars on the table for us? You know, there was like no one there So we kind of came Came to to an arrangement that we kind of steel boron bag in that order not the bag boron steel Just to be able to to develop the the reference architecture So that's the context and Couple of significant items that we wanted to kind of maybe present to you that we found quite interesting and quite helpful Four significant Areas that we dealt with one was obviously Defining the benefits of our reference architectures Chris touched on a whole heap of points and they all true And but they look different when you kind of in the trenches of of driving all of this there's Purpose and the framework that we we had to kind of determine and work out where the Had to agree on the modeling notation and domains and remember we had experts sitting there expecting a whole heap of kind of wise stone stuff while we had 14 architects having 28 plus opinions all of all of whom said we have a better framework and a better way of doing this And then as a last item, it's kind of like what happened then we finished the initial iteration of the reference architecture as a starting point and A little bit later on I'll take you through what where we had what we up to now and where we're going with all of this So the benefit benefits it took us Quite a quite a long time To kind of digest the coffee that we had and said we had a great idea, but It's a bit different when you have to go up to the exec and say guys. Can you know? work out How much this is going to cost and help us fund it? So we needed to put tangible benefits on the table and not just some some wild and weird stuff we said we needed to commit to A number of things that could actually be measured so one of one of the things that we Looked for was Hard facts and we found out the time-to-market is the thing that was driving a lot of the stuff that was going on so For for us at that stage we didn't have enough architects enough IT skilled people enough managers that would understand their their domains and the interaction the Interoperability So we needed to kind of educate our suppliers and the partners With the people coming into the projects or being able to help us run the various environments and platforms and that worked Also, we saw this as a as a means for higher productivity We've seen I think about three quarters our Torgaff certified here once you have the basic background of The framework and you see the reference architecture. It's so much easier Getting things done because you share the language you share the The objectives and you know how to kind of be productive and and provide value straight away And then obviously we're looking to kind of In a management view describe the capabilities that we saw that were important for Lufthansa at that stage But also for the future and there's a small thing that's that's cropped up in the last couple of years something. It's called Digital something I don't know In that in that sense, there's there's a whole heap of value being able to be unlocked if you know your position and if you know how to Kind of grow Merge acquire or just bring in new skills and capabilities for for your customers And again that digital reference is going to we're going to show you a little bit more later on But that was quite handy coming in as well. Cool. So After kind of knowing what the benefits were we looked at the purpose for it and said, all right, how do we kind of bring in The fundamental purpose that we can communicate for this reference architecture and it was it was Driving the common understanding Chris referred to it everyone else. I've talked about reference architecture Architectures refers to it. It is about understanding content and capabilities and then obviously having the ability to develop that further it is sharing that that language and having An architecture community be it within or with an extended architecture community that is able to understand what you're talking about with a defined set of of terms and Words It's it is about being able to compare Provider and solutions. I don't know how many RFPs. I've done and how many how many software selection tools of kind of Gone through and every time you get some sort of of Submission you wish people would share Kind of the meaning and definitions of the words and it just doesn't happen And it takes so much time to clarify to work out what it is and then to kind of align everyone so just making sure that we could Quickly find the right level of understanding on that was really really important and be be able to compare it and we had a We looked at different levels of of Business domain expertise that we could describe So one was obviously architecture because that's was the closest But also looked at kind of procurement areas Infrastructure and the overall business management side of things Just to make sure that we could kind of sell the purpose and the benefits to the whole of the the Lufthansa group And obviously the purpose was for us to be able to take this and then speed up the development and the definition across the two hundred and fifty million dollars at Euros are just about the same so To then being spent wisely and helping us reduce our workload because we didn't have enough Kind of architects and IT people and knew what they were doing So how did we do that elder? Okay Which a button I have to press to go forward this one Here we see the procedure how we Constructed our reference architecture at first we selected the industry standard and in a second step we Defined the domains and After having defined that all the domains aviation domains we developed all architectures for each domain by each member of our crew we have seen before and Then we published the results and actually we have submitted also this architecture definition document to the open group to get standardized At the middle of this year. I think it's June July approximately some Publications and access bring a phallar has been done as well about this topic and some journals in German language Yes, this we have we have some preliminary results here This was too fast here we see our framework areas and At least 75 percent of you should know these areas With regard to the statistics we have seen in the opening speech Of togaf certified people we have here the four classical togaf layers business architecture application architecture data and technology architecture and then we have two Requirements for the overall architecture we are developing this is the consistency between these layers and the ability to easily and in Intuitively understand or comprehend this architecture Because an aviation Architecture is not it's not a simple architecture. There are many domains. We will see as we will see later Yes, here we see the continuum cool, so Obviously we're looking to kind of use what we knew about Lufthansa now Lufthansa on the continuum would be closer to an organization specific architecture but Lufthansa has a number of Customer and and company specific Competitive processes that we didn't necessarily want to kind of present to the world So we took what was kind of generic Plus the Lufthansa competitive advantages that we saw obviously had plenty of Plenty of discussions and meetings to strip out the essence of that Competitive advantage and then develop an industry specific reference architecture, so we went kind of from the right-hand side to hopped into industry specifics And at that stage made a lot of sense because we're dealing with The thing that we as the architects involved new best and that was revenue management and revenue management is Kind of about pricing and yield management and as you probably know Lufthansa is currently I believe Quite a profitable Airline unlike I don't know probably two-thirds of the airlines worldwide So in that sense they were quite keen to protect the way that they manage their revenue and manage the yield So that's why we went from Kind of the organization specific back to the industry, which is one of the reasons why we're here I'm not not talking to kind of just Lufthansa guys Yeah, cool Here we see the notation we reuse for our architecture definition document Here are shown the elements of the business architecture. We use symbols for the business domain which can be nested using subdomains and With in subdomains we can also Place business capabilities We have also process elements, which we know from the business modeling notation A Starting state and end state all this which we know already from the OMG. It's it's not a new standard It's it's already standardized Here we see a very simple representative model of a Simple activity of course the activities and processes in the aviation architecture are much more complex But just to illustrate how it it is Illustrated we see input artifacts Into an activity output artifacts, which are an outcome of an activity and The complete chain of this process by connecting the activities to each other Here we see some Some symbols from the other layers application architecture data architect a technology architecture and an application is given just by a simple square was a double edged border and A technology component as well. So we We differentiate easily components from capabilities and Data elements entities and information objects as we know them from the Entity relationship diagrams very a standardized and simple Method to illustrate Relations between data and the hierarchy of data Here we see an Exemplary entity relationship diagram. We have an information object and we have two nested entities will have a relation between each other and Also entities may be placed outside of information objects and we can connect them as we want using one-to-one one-to-n or end-to-m Connections or relations Here we see the domain model We have 40 We have 40 sub domains which are nested in several Domains such as cargo maintenance product network and fleet planning revenue Management and pricing which is a very important and also amazing domain because in this domain a lot of knowledge is Concentrated how to How to determine the best price? For the customer and but also the best revenue for the for the company and In this domain the Lufthansa Unfortunately does not provide the Insights how we can How we can calculate the price on which basis and How does it really work because it's intellectual property of course so in simple terms it's easier getting blood out of the stone revenue management information out of Lufthansa as you can imagine But the revenue management being at the heart of the airline certainly helped us kind of get to a core providing value back to To all of the the various business areas and domains so that helped us rather than picking up Kind of a cargo domain that would have been important for Lufthansa, but not necessarily at the heart of the organization So then we have marketing customer care We have flight operations all activities that happen with in the aircraft during a flight And we have supportive domains such IT services finance all those domains we We cannot we cannot Assign to one of the business domains. They are located in the supportive domains Yes, we have 40 sub domains and we could deep dive Deep dive more deeper into each sub domain by 40 additional Boring slides, but alternatively we can also connect to cast bright hoped our architect lead architect from Lufthansa, which can give us some insights into each domain if you have any question later Yes for those who cannot read clearly what is written here My takes a seat and the remaining seats in the first row here But this slide is just to give an impression of the size of our reference architecture and how it looks like when we take a look At all we get we get a view of the complete aviation architecture at a glance so You will be able to read this in the architecture definition document after this will get published by the open group Yeah, what happened then and Kike you go more in the next steps. Cool. Yeah So now since we've we've come up with a whole heap of insights across five star airline and We look back kind of now I'm probably been on the on the run for about two years now Different architects having set up a system that was able to For us to to take a tiny little component and then Expand on it. So we've got the people the structure the the notation and What we wanted to achieve was to build the architecture community To have the ability to bring people into the aviation industry And then obviously have them be productive and add value straight away and obviously as part of kept him and I being a Massive supporter of the open group and Lufthans are also seeing value lots and lots of value and within the open group sharing this knowledge and The ideas behind the concepts the way that we work best practices methods we've Kind of decided that under the guidance of Chris that we would kick up an industry vertical So this is also kind of in the works right now and we're looking at Deciding and and kind of firming up how we want to do this can't invite all of the Airlines because that'd be like what's it? Kind of Parliament or or you know, you'd never ever get any work done anymore So we'll need to kind of scale up and it's a bit like a job you add a few people and you kind of get going again and based on Based on unless We've seen also some mouse come to we've got a lot of architects now that are highly skilled and Have the tools and the methods the structure the knowledge to kind of easily draw up reference architectures So they've done that in their spare time and it's just absolutely amazing What people can do when they know how to do things and they just want to do it again and again So we've we've developed I think the pharma reference architecture What else is? Utilities all kinds of different different reference architectures that have come out or Found an update but on top. I mean that little word that I mentioned earlier. I think it's digital Pop back up. So we've said there's a different It's evolution of architecture and it's called digital architecture. So we need to kind of honor this It's not just an industry digital goals beyond And there's some miles and I've never really understood what it stands for but it's IOT you guys probably wouldn't know right so again something different that goes Beyond and this is crossing The kind of information divide something that is at the heart of the open group kind of make it interoperable All right, so we've looked at it and said We're gonna kind of not only do industry specific reference architectures, but also digital IOT and others Next one is probably artificial intelligence. Don't know how to do that, but we'll work it out. Cool We've talked about that, yeah, do you want to keep going? Sorry Yes, and we constructed an architecture community we have What keep going okay Next one. I here we see Here we see some sample architectures that evolve After having finished our first draft of the aviation architecture. We have a large IOT reference architecture involving all concepts frameworks and building blocks of the Yeah, internet of things and we have a digitalization reference architecture involving all building blocks That cover the for digitalization steps text hands and connect ingest analyze prepare and utilize and This digitalization reference architecture also comprises Cognitive computing artificial intelligence and augmented reality Yes, and here we here we are Finished with our presentation and if you have questions we can bring custom into into play We have one minute We're sorry you can't be here to join us, but thank you for for joining here We'll we'll get some questions. So the the first one that we had was do did you use anything from Cesar? The EU reference architecture for air traffic management If I did get the point very correct and the question was about Cesar. Yes Yeah, and no, we didn't use anything from it We are involved in that project and we know that they have created an extensive enterprise architecture architecture framework and but at the time he started with our architecture framework that I just presented and He didn't use Okay, thank you. So while while we have you We'll take advantage of you Kirsten with our speakers don't mind what is the biggest benefit for Lufthansa from this new reference architecture and Second part of the question. What benefit do you think other airlines or aviation companies will see? I Think at least we are convinced One of the major benefits would be a common on body the common understanding and so We have created the enterprise architecture framework based on talk up for our company and One of the main things to experience we see is that architects within the community will understand it each other and So then that was I think one of my reasons before that maybe the preference architecture for the aviation industry The sense and that it's to the fact that in the architects within the aviation industry maybe of all Understand each other better in the future at least that that's our hope and Besides of that, it's not the architects. Maybe over the architects so we have we will create with the Architects and companies with part marks and maybe even with and maybe the software providers common understanding What are the components the building blocks and of the architectural to be like to have? Okay, thank you Let's see next question. How important is achieving is related to that I guess how important is achieving industry-wide adoption of the aviation reference architecture for Lufthansa and Capgemini and We've talked about the second the second part of the question has already been answered. So how important is adoption? by the industry to Capgemini and to Lufthansa My part of you, it's important to create it but it would not make sense So even if I if I'm not there with you in San Diego I hope that somebody will follow us and It works in the future reference architecture. So and find some adoption within the aviation industry with Ends that part and other problems Okay, thank you. You're starting to break up at this end cast and but we'll we'll press on How did insights from revenue management drive key performance indicators throughout BDAC domains and did those KPIs help implementation and adoption I don't think that the KPIs from revenue management have driven Extensively the the reference architecture KPIs from revenue management will drive our internal architecture and will drive the of IP landscape But I don't see a direct influence of type ice problem From reference management management with for the reference architecture since if you look for the reference architecture, you'll find some building blocks you will find and Then you will find all ends and and I think that's more or less Let's say natural structure For my part of you mostly not influenced by the API Okay, thank you Let's see What are the common vocabulary standards used within your architecture Common vocabulary standards. I mean togaff being one Custom you want to answer it Yes, it's bit hard to understand. So that's reason why I've asked What's the content of the question is and I assume that Yes, we have used the vocabulary of And then you have to look to more internal glossaries and terms of MIT terms definitions and with the help of the Kai and I've created let's say more or less a common vocabulary of that Thank you. So Good question. I think What questions can you answer now that you couldn't answer before the reference architecture? From all point of view, I don't think that we could answer any additional questions since more or less based on Architecture not the same since it's a reference architecture a generalized version and but With our internal Architecture we could answer exactly the questions we could answer with reference architecture now So we have a view on the structure of the ET landscape and the functional building blocks We have a view on exactly what Ella just presented some minutes before so that would help us and Well as before it would be as I mentioned before helpful to spread this knowledge Within the industry. So hopefully you could answer some questions in the future more Understand understand lots of other questions that we we don't have time for because we have we have to move on but There are There were a couple of questions about Kai, I think specifically you referenced Reference architectures from other verticals In in your work. Are they being published as standards or are they likely to be or were they already published when you saw them? Just a quick answer to that We've used what we what we could find kind of as a best practice So we've looked for I think we've used the the mining reference architecture quite heavily Just to understand how do you go about doing it? And then obviously we've based on the aviation reference architecture. We're driving a number of other industry architectures but they well in the process of being Kind of standardized or published So and that's an ongoing effort Across the board. So yes, and yes simple answer and really the last one because I promised the people with connectivity issues To their question in a global marketplace, why would we not publicly openly share our taxonomies ontologies? Recognizing that data is not Data with us to trouble with writing isn't it data is not the IS But the machines processing or using the data Recognizing that data is not the IP IP Okay, recognizing that data is not the IP, but the machines processing or using the data. So why wouldn't we share? openly taxonomies and ontologies in today's world global marketplace Well simple answer from my point of view because I think we've got too many people that are scared They want to hang on and monopolize the the knowledge and power thinking that they can kind of Freeze the moment and kind of be more successful or better equipped When you let go and you kind of strive to Do things better every day? You come to the conclusion just mentioned that it's about The insides and the processes and the machines not about the data from my point of view Why we make? Architectures open we can see in the IOT if area There are some Projects then they think okay. We keep our devices close. We keep the protocols proprietary and the other the part of The IOT words says we make everything open We make it a standard and we make things to speak and to communicate openly together each with each other and today we see that the open the standards which are open they are simply winning and they are simply used and no one is buying or Developing or using Appropriatory standard for for his future business and the company so in And somehow I think Openness wins in this case great words to end on thank you. Thank you both very much and Castan if you're there, thank you too, but Great job. Thank you very much