good morning everybody and welcome to this week's Digital Services Forum bi-weekly meeting it's the bi-weekly one but we haven't had it in a month we're coming back after the Fourth of July holiday and today we're gonna open up a topic on architecture and it's called ecosystems architecture so it's a New Concept but we're also going to look at some some new tooling on the platform and we kind of flipped it around I thought I was going to introduce you to ecosystems architecture go into some use cases and then talk about tooling uh but we were able to get Don in the beginning so we're flipping the tooling to start off with we'll do a little bit of a reverse from what we did before now before we start I always like to just tell people because a lot of times they're on here for the first time so we' like to have an active chat going on while the meeting happens so if you can just put comments in especially if it's your first time go ahead and drop your name in the comments just so know we know who you are where you're from and then the other MERS can can go ahead and welcome you in and I will put a link to all the group's assets that are available so that you can have access to that immediately after the meeting welcome to the group if if it is your first time we love to have new members appreciate you jumping on all right so today donon is gonna he's our senior manager from inbound product management on the APM side so Don has been here before and he's presented to us at various times we like to have our product managers in especially when there's something new coming out that we could learn about and maybe even offer our opinions on going forward so we've had people like Mark bodman in here talking to us about early common service data models we've had Caitlyn a couple times talking about what's coming in DPM and then this is uh don is a a repeat H presenter on here coming back to talk specifically about the architecture side of it so Don are you on yet yes I am I don't all right so I think what I'm going to do is just hand you over the presenter so that you could take it and um and share your screen I know you have some things to show everybody and then I'll take it back over when you're done I know you have to leave at the bottom of the hour yeah absolutely thank you John and uh I will uh present my screen and U and so so and we first start maybe with a few slides and and so so so first thanks for hosting me John and everyone my name is Don orbak I'm John mentioned I'm leading the product product management for application portfolio management and I asked John we discussed with John to introduce to the New Concept and actually the New Concept not so new but you will see how we evolve to it is the delivery and announcement to of the Enterprise architecture so what you see is things that are coming up in our Senate do release so it's coming up pretty soon h of course things are not yet released so I need to show the safe aror notice and discuss them so so maybe maybe I'll start I'll start more with an overview of what we are doing and then I'll get to some details and show some of the things that we are doing so so the first and meaningful thing that we are doing is really we are relaunching our application portfolio management and evolving it to be a Enterprise architecture product so a service now will offer enterprise architecture as a product and it will be extension of the application portfolio management and not a res placement it I mean it will replace it as a product but all the use cases that we supported in the application portfolio management will be continue to be supported as the Enterprise architecture version is released and in general terms I I mean we are really building up a lot of material now because it's a big lunch H the main reasons why we are doing this is because we see a a future for Enterprise architecture which is just growing I would say there is re-engagement or repositioning of Enterprise architecture in general in many organization and it's becoming even more strategic now uh even with Gen with with they need to do governance on gen ability to to measure what is a usess gen with the agel side of things that you want to enable Enterprise architect to influence what other teams are doing maybe to be able to have to provide standards and guidelines but not to uh stop the other teams from running on agile and you definitely want to enable the ability for Enterprise architect to share and communicate more data with other stakeholders which are not Enterprise Architects because if eventually Enterprise Architects are are are a small team compared to the width and breid of a large organization it environment and they need to be H supporting other teams and be very much involved with them and when we look into all these things service now as a platform seems like a good choice especially for those customers who are using service now of course to to try to bring to collaboration all these uh different agendas and especially around ensuring that both Enterprise architect and non-enterprise architect can refer to the same data and can leverage the same data and so this is where the Enterprise architecture really come into play and eventually when we look into this we think that as service now customers it will be very much strategic to leverage our Enterprise architect product at least at least uh uh to be able to make all this I would say connected World between Enterprise architect non Enterprise architect and to ensure that the work of Enterprise architecture is not isolated is not done in an ivory Tower and is very much connected to what the organization is delivering so so these are some of the areas that leads us to this and uh before I go to the demo I just give a brief overview of uh what what what existed before we are going to do this lunch in xedu and what is coming up as a new thing and if we look at what really existed in the product and you can see that it's not new for us the idea of launching the APM as a Enterprise architecture product so we really already one and a half years ago we released the Enterprise architecture workspace which is the main UI tool that is now used AC course a lot a lot of customers in production to manage their Enterprise architecture and uh so it was a a little bit non-official that we were Enterprise architecture too and the reason because it was non-official because we had a lot of models but we were missing one model one specific big model that you will see soon is coming up inedo but when when you go and look into the Enterprise architecture product you really will be able to see that you have very comprehensive dashboarding capabilities uh ability to do application rationalization in a very uh graphical way and be able to present the diagram of where applications are landing in the time format if you want which application want to tolerate invest and so on also to manage other things that we didn't manage in the past like a digital Integrations or interfaces so the ability to understand which applications connect to which other application and what what are the interfaces and apis that they're using in order to connect it uh looking upwards into the business and aligning the business applications to the business capability management and also be able to score this business application and of course because we are part of the platform also be able to look into the very specific details of technology and where you're using technology uh that might be putting you in higher risk like risk of life cycle risk or end of support life cycles and on the other end also being able to set your own standards so which sofware is offered as for production which is not approved and so on so all of these things we can already do as part of the Enterprise architecture workspace so so then we're coming to kenu and the big thing and this is really a where I will focus most of the next 10 to 15 minutes when I will do the de demo is about the the new capabilities that we are adding and uh this new capability is really uh the ability to do a modeling and future State modeling into the Enterprise architecture workspace so this is more about diagramming and being able to set what will be a taking it from the Baseline of the current uh the current operational State and being able to move it to a future state of uh what would be or what we think should be the future state of the diagrams so we are really starting this is a journey and we are just putting the I would say the first uh step in it and delivering this in August sfga by the way we already release it in the what we call our Innovation labs in the May release so it's already out there in the service now store but now we are moving and releasing it as a General availability release in the beginning we'll support more we'll focus more on csdm but as you can see we are planning to extend to a more known standards like archimate and bpmn and we also going to and I will show some of these things today we're also going to support more would say high level business diagrams that can look at things top down like value stream management and business capability management business processes management and so on so the these are some of the things that I'm going to show now in the demo I'm not John if you want to take any questions for now if somebody has or wait until the end of the session to see if anybody has any questions so far I think we're good so far okay sounds good do you have a sense of when when you'll be to the AR to the Arkham Ade you know business model yeah aimet is currently planned for February release in 2025 so we we release on a Cadence of every three months so yeah yeah okay so February each February yeah yeah okay so over we uh this is the Enterprise architecture workspace and there are different models here I won't go into them in details today but the dashboarding and the business capability management and uh business capabilities and business uh more of the trm catalog that we offer and the newest addition to this is the really the diagram in and uh when we call it by the way Enterprise modeling and visualization so there is a little bit of I would say overloaded naming we have diagrams model visualization eventually there is one um one one capability that we added we just H I think we could have been more focused on the name selection but uh what we can see we have already pre-built diagram and diagrams specifically have a name they have also a category so you can categorize the diagrams into different categories let's see a little bit if I group this so it will give a sense of different categories so we can see applications architecture application communication and here I'm looking into my application migration diagrams and you can see there some uh diagrams that I've already pre-created in previous demo so I'm trying to be very creative on my naming but it's stay close to the same names all the time in my demos and and what we can see we have a versions for the diagram so there is a version of the diagram and there is approval approv version so we'll see that we have a concept of being able to using our workflow in service now to approve diagram so once I create it I might create different version and I might discuss different things and I might share it with different people and eventually there might be a version that I want to approve and this workflow of approval will go to an Enterprise architect usually but you can change this workflow and maybe have it sent to the security teams so to the application owner teams and so so they can approve it and if we go to specific diagram we can see that there will be quite a lot of details on a diagram but this is really depending of what I choose to uh show on this diagram in this case I'm showing the business capabilities that they have and I'm sure business application and application services and the software products and so there is quite a lot of information in the diagram and it's usually very very easy to you might ask so how do we get to all this data as a staffing point and the answer is that if you are if we're looking at our model and now go to the portfolio that I have so for example if I'm looking at one business application and this this is the uh data that we provide for different business application a lot of functional data and ownership data and what is our plan to do it we we are also able to uh now create a diagram so this is a new thing that we had actually not that new because in the past we could have just created diagrams in the Lucid chart now we are open we are enabling to create diagrams in a not just in Lucid chart but also in our own modeling tool so but this will be available both and and when we look into this I can go ahead and say okay I want to create a diagram of this business application and I want it to be a cloud ER version of this diagram so yeah please we got some questions on um licensing so this is all will this all be um does it require it says SPM PPM I think this will this all be like a new license Enterprise architecture or will this be so first in the past this product that you're seeing is APM so it's always require a different it wasn't the SPM license it was always the application portfolio management license but now we are really launching it so it will require the Enterprise architecture license in in caned we will call this product Enterprise architecture of course we have migration ways for existing customers but if we are talking about new customers they will need to buy the Enterprise architecture license this will be the name of the product again it will just be launch inur so if you go and loose look for it now in our document there is nothing there this is a future statement so Bruce and Adam does that question yeah I'm Sor I'm sorry it wasn't clear to me so we have existing um APM licensing like APM uh analyst for example I'm trying to remember what the terms are so those existing licensing will cover this capability it's it's a good question I can get more into this it so also on the APM we we used to have two types of licenses one was based on number of business application one was based on users so if we are going into looking into so for those customers with application portfolio management based on business application so they H get this capability if you're using the user based license which is the older older license it's pre Tokyo license then there is a way to migrate to the business application license but truly you will need to have further discusses discussion with the account manager on this but there is a way to migrate from user based license to the business application but it's eventually it's offered to the business application based license and if you're on a former user based license they needs to be immigration to this list okay so we have user-based licensing today so you think we'll have access to this capability and and the other question that I had was I've seen a lot of the EA work in the past really kind of depend upon being able to create demands or projects such as to retire business application and Trigger off that right so in my company we don't use any of that capability so I don't know how much of this capability might be hobbled if it depends on some SPM capabilities no there there is no dependency at all on SPM you can create demands for it but once demands are going to a general table which is available to all customers not just SPM in SPM they take this table and then they make modules of prioritization and so on but you can use this tool without any demand creation so for example if you take a decision to uh retire business app you can also capture it within the tool itself so it will be taken on the business application we also delivering a model of architectural decision record so you can take decisions and categorize them as a architectural decision record so the SPM I would say just because we on the platform is just an added benefit if you have SPM you can create a demand and it will go to standard privatization in SPM but it's not definitely not a required to use this to all right thank you so looking into list I can provide this architectural let's say it's application migration and I can choose what do I show so in this case I will show the application services and business capabilities and then I can create this diagram so it's really helping me to create the current state diagram and this is creating it with really few clicks and all this data is available because it's available in CNB data so all this data that se so for example if if I'm looking into business application let me just increase it a little bit if I'm looking into business application it's really represents the data on this business application that is available in the diagram and in the cmdb and it's always connected if I want to see all the details on this business application I can do the round trip and see the details on this business application so I'm always connected to the data on the platform more than this if I look into this diagram and I decide that well I didn't bring the information object how Ed it I can pull more data more related records from here so in this case let's say I want information objects I can pull them and now I also have the information objects attached to this diagram so it's very easy to patch data from the platform but that's the starting point this is the operational State this is the current state for me I can start maybe to create a future state so I will create a new version for this so now everything that I will make here will not be affec in version one so we have two versions everything that I will get on version two will not touch version one and I can start to play I can maybe add the notation I want to see to add actors and to add a uh who who invoke something and who is doing something so I can add this General things into this and I can add these notations and add this kind of data but I can also and this is really where the power of the of the platform and being connected to the platform C to player can also real element so I can say you actually I want to announce new business capability maybe it's a new completely new business capability that says it's a a cloud payroll and and again this is just I'm inventing a non nonsense stuff but I can create a cloud payroll business capability and I can even go ahead and decide to connect it to my uh business uh application let me just take more speed and I can connect it to the business application and save it and all these changes that I made now are really part of H this diagram they are not part of really the service now data model you can see for example if we look closely at the icons you can see that some data is not connected to the CV some data is V is connected to the CB and at one point of time I might get to a diagram that really reflects what I want to achieve and this is where we use the power of the workflows and I can create a workflow to submit it for approval in order to all agree around the singular architecture and secret diagram and this will be submitted what goes beyond the workflow is really depending up to your level of in of wish in our case we deliver out of the box just one level it just goes to the Enterprise architect but you can really enrich it with a more uh elaborated workflow and if I will pretend for one second the time the Enterprise architect which is able in our case and I will go to H see what Abel is seeing I will be able to see that now Abel when he is looking into this and is going through the diagrams so he is able to really uh approve this diagram or reject it of course and is's able to give the reason and now when he approved it this is an approved diagram if you remember I started with approved diagram in the system I I presented this concept going back to my uh original user I can really now look and see okay this is an approv diagram and I can also now do something that I could not done before which is to commit changes so I can now save the information information into the service now cndb and we can see that now this information was saved and even This Cloud payroll is now part of the system it's part of the CB system I didn't mention it but it's all a it's a the capabilities to share this diagram so I can decide which other users let's say I want to AB to be a viewer of this diagram I can also do this thing and and once I get an approved diagram it doesn't mean that this is the end of the the journey maybe there is more development and I can have a new version of this diagram or can even start a new journey and say no let's just duplicate it create a cloud or maybe now I decided specifically this is the AWS Cloud version so now I'm creating this so now I have the same diagram but it's just the AWS and I created version one and I can start to model on top of this I just want to uh what one thing that maybe I didn't show so far so this is what what I presented now was really the first version of the release uh this is going to be a follow up by Future development of several models which we are already working on one of them is the value stream management and announcing value streams and now they connect to business capabilities and other things is we are going to make it more fancy so not just fancy in terms of color but also in terms of functionality so for example the ability to show indicators and what is working well on these capabilities and apps and what's not so here we can see customer satisfaction score and Technology score and things of this kind there is also more capabilities to introduce the business capability model so this is more a visualization of how nested business capability support different areas in the organization and business application and uh maybe the last piece that I will show for today for the time is how uh business processes are being M so we can also track and this is the level of business process modeling already that we are capturing the different activities within the business process and if you're are familiar with our process automation designer so this is going to be a line with our process automation designer so if you are familiar with this it's going to really use the same technology behind the scenes and uh leveraging the same class model for our development and uh I'll stop here so these are some highlights of what we releasing senu and what we plan to release in November and February any questions uh on anything that I presented and we looks like there's a couple there's a couple different things in regards to the different types I see people talking about dependency views and service maps and I didn't see it either and so you know we have service Maps we have dependency maps and now we have this Arc diagram uh also so I think there's questions around overlaps or is one replacing the other or anything like that yeah if we look Ju Just as very short in a nutshell if we look at our modeling it doesn't replace the node map and and so on what we are doing is really enabling to build the next uh the next would say the future generation it's not about operational state if you if you only want to show operational State and service map the node map the cmdb maps are the right choice if you want to take this operational State as a starting point to build the future State the the imaginary State then the Enterprise visualization will be the right one uh this is by the way as I mentioned it's already available to download from Innovation labs in the service now store called Enterprise modeling and visualization and there is going to be a lot of features I see that I'm ask about several features but uh uh there going to be lot of feat by the way one of the feature is is the the launch from the node map into the modeling and visualization so we'll be able to say okay looking at current node map cdb launch it into the new modeling tool because I want to start modeling then we launch it exactly from where we are we're also going to show I would say a integration views so how different business application are integrated one with another this is also another view so and I mentioned arimed so we have big agenda we're trying to prioritize it also based on discussions like this I sorry I just see one end OFA do you want to ask something please um I did I wanted to make a comment on what Mike was saying so um I have been using the modeling tool now for a couple well I guess it's been about a month or so and what I did initially is I'm using service now I went ahead and I created the business capabilities to the service now business applications in SPM and APM and then did a demand so for each thing in the modeling tool I created data because it needs data and then I created the dependency View and then I created the map so then I had both of those then I went ahead into the modeling tool tool and brought it up so I could compare so that's just a suggestion to everyone so go ahead and and build out your data like I said I used you know SPM and APM for obvious reasons because that's my jam um but then that way you can really see it and I I love where this is going you know I've been on my business architecture path for like three years now and so um I'm excited about this whole journey thank yeah I like that because the concept right is that you know that we're always trying to figure out is Enterprise architecture design something and so they have the concept up there and then you know the service maps and the dependency maps are actually what's built down in the orange right of the csdm that's actually you know captured and and crawled and everything like that and you can almost overlay you know the drift from what was designed exactly exactly and as csdm 5 comes in and now we have the idea domain think about this when you're asking okay is it a duplicate and then that next one does it exist already my interpretation of that is do I have this business capability already so I can now use Enterprise architecture to see do I have this business capability already and if I do what business application is it or what is it what are we calling it now product we we renamed it it's gonna be called something else right but everything is is coming together y thank you for the feedback and and everybody else on this call I really appreciate it if more feedback come to mine please reach out to John and John knows how to find me so I I really appreciate it really really useful and thank you very much thanks to R I'll send you the recording over but uh appreciate you jumping on with us thank you right and we're going to go ahead and switch gears a little bit now this is my stuff I have that I'm going to talk to you about today is a little further it's uh it's introducing a new concept and I might be a little bit late for donon to rename his product but it's going to be about ecosystems architecture I'm going to talk to you a little bit about what that is first and then talk to you about a proposal for this uh you know around the tooling so if if I start out and if you look at the um the tooling for ecosystems architecture I'm I'm going to show you what I'm proposing first and then I'm going to try to defend that as best I can and any feedback you have that you could put in notes for me to improve upon this because it is a it is a first time showing it to the public uh so any feedback you can provide on this would be would be great so basically what it is is from a tooling perspective it's taking configuration ation management not cmdb not csdm but just general configuration management so the configuration management of everything in your business or I'm going to talk about a municipality today like a city or a county but um in some environments like we had somebody that were talking through this from a car manufacturer and their big things were supply chain uh you know their the supply of all their their vendors that they're used to provide it so the configuration management is all the assets you're buying to create your organization be it Hardware software physical virtual um all those different pieces kind of come into configuration management kind of what we all been working on and then we talked about this last meeting or two meetings ago maybe the foundational data and specifically around the geographical pieces so we talk about government this is one of the data sets that's that's a real primary concern for us so when I talk about architecture and ecosystems architecture we talk about blending like these two foundational things as tools for the ecosystem architect now in ecosystem architect a lot of people are saying oh is this a new category of Architects that's different from Enterprise Architects so ecosystems in the definition that you know everybody's writing about it's it's broader than Enterprise but a lot of Enterprise Architects are already doing the job they're already filling the role of ecosystems architecture so the basically the gist around it is we used to build an Enterprise with you put a data center in you put computers in the data center and then you run your apps on those computers and that's kind of where Enterprise architect was born this is ecosystems architecture is suggesting that need needs to be extended because don't sit in a data center anymore or around closed walls anymore Enterprises are all over the world there's pieces everywhere right so this is the concept of kind of going broader and looking at your architecture a little broader than you typically would with Enterprise architecture all right so the so basically Enterprise architecture is the concept or ecosystems architecture is the concept configuration management and geographical management are the tools that that ecosystem architect uses okay if we look at ecosystems and we think about them a natural ecosystem is a complex organization of of microorganisms working together if we look at a business ecosystem right it's it's the same thing but it's not microorganisms anymore it's businesses that are working together that form this complex offering there's technology ecosystems there's digital ecosystems uh there's even Enterprise ecosystems so if we go down these pretty quickly Amazon would be a good example of a natural ecosystem right the Amazon rainforest or the Great Barrier Reef if we look at a business ecosystem a bunch of different types of businesses working together you can think of Tesla where there's a bunch of businesses in ecosystem formed around sustainability so they have their cars they have their solar um Apple's very similar technology ecosystems Microsoft has their office suite they have their azure sweet different pieces that they put together and offer them digital ecosystem Facebook is a real good one they have a bunch of properties that are around sharing personal data and then Enterprise ecosystems like some of the extreme examples here are like GE right that pulls together a bunch of different types of businesses and runs them as an Enterprise can we so we think at that level uh really what we have is we we think about the entire ecosystem so everything that we're doing and bringing that in there's somebody that's thinking at this this next level up like how is it impacting the whole of My Health Care Organization or how is it impacting the whole of my government organization whatever that might be there's a first version of this book that talks about some of the concepts and really what brought this on was the coming of AI when you look at AI pieces we had a service now person come up the other day talk about Ai and service now and we already have over a hundred different pieces of AI technology that are working on different parts of how we do business at service now so those AI pieces are all over the place right so how so there's a lot of governance that comes around that so so AI is really what's pushing outside of the boundaries of what we traditionally think of as an Enterprise and that's what this book is about so this book had us a version one that's very kind of out there thinking I'll call it but version two comes down to more what are the use cases how do we use this how do we work differently with architecture than we work today so I I remember this story that my brother-in-law told me a while ago and I thought it would be a good story to tell to get us started because if you think of ecosystems a lot of people think of these natural ecosystems and how the microorganisms work together so this is a picture back in 1903 they they brought in this thing that they thought was a good idea in in the South and it's called H kudu so they were trying to figure out a better way to feed the livestock so they brought in these kudu plants in order to create a better way to feed them so what happened is kudu was really like the environment there so when they brought it from Asia and they brought it into the Deep South it grew like crazy so today what happens is that kudu cost the Deep South between hundred and $500 million dollar a year between eradication replacing power lines that this kudu takes down so an ecological nightmare for the South and and they're still dealing with it and it's spreading throughout the United States couple back in 2009 the kudu beetle came down south and everybody's like this is great they're going to eat all the kudu right that that's what they like that's where they come from well turns out the kudu beetle prefers soybeans which is the main crop of the South so on top of the hundred $500 million loss because of all the the overtaking of the vegetation additionally they have a 20% crop yield loss for soybeans because now they have the beetle down there that's thriving so this thing that started all the way back in the 1900s is now spreading from Asia came over to the South and now it's even spreading in the northwest of the United States so this is an example of architectural thinking right if this design to bring this stuff in had never happened and people had done the ecological studies to make sure what I'm bringing into my environment makes sense this could have been prevented so if we bring this back down to our level now right we think about the humans that we deal with the United Nations came up with the ecosystems architecture the future and what the United Nations says is you know people have needs when we form governments and organizations of people they have really basic needs you need water you need a place to live and for those of you that work in government you'll probably understand that there's agencies created for all this stuff so that's really the foundation for it a lot is they're saying how do we create these ecosystems so that we can basically support humans better right so that United Nations really does that if we go safety needs right we move into the energy and utilities area all of the safety pieces social needs esteem needs right and then all the way up to where we're like creating our businesses and what are we doing for trade uh so that humans can actually make a living right so if you look at the United Nations that's what they're actually looking at now for so I can give you some use cases on on how we can use configuration management to get together with the geographical management together with the practice of ecosystems architecture I want to share a quick one minute video I'm gonna might have to reshare here because I got to make sure I share my um one I share a one minute video here on this uh this futuristic city that we're going to use as our use case but I want you to think about how you would do this for for your organization I'm going to be quiet for a minute here while you guys listen to this to protect and enhance nature the a revolution in Civilization is taking place imagine a traditional City and consolidating its footprint designing to protect and enhance nature the Li's communities are organized in three dimensions within 5 minute walk neighborhoods travel end to end in 20 minutes designed by World leading Architects the line is 500 M tall 200 M wide 170 km long and housed within an elegant mirror glass facade the line is designed as a series of unique communities providing Equitable views and immediate access to the surrounding nature at the heart of the globe's key trade routes a place for Commerce and communities to thrive the line the city that delivers new wonders for the world all right so that is an example I got off the internet about the line which is one of five areas that neom is creating now when neom thinks about the line they they organize their their leaders I guess in in different sectors so there's a leader of design and construction there's a leader of Education and Research all the things that you would need if you're building 120 mile long line through the middle of Saudi Arabia and you're you're trying to think of what are you know how do I create this this ecosystem right to work with all these people in it right with 11 million people in that line so these are all the areas I think about very much in line with the what the United Nations was actually reporting on and underneath each of these if we think about having an ecosystems architect and we think about having that ecosystems architect have the gis information together with the configuration management information these are some of the use cases that you might think about right so there's very specific sector-based use cases for configuration management to track the it assets for the digital infrastructure and also the geographical information so you can monitor the technology through there there's a lot you can do here with enhanced connectivity and then you can do the same thing on any of these sectors right any of these sectors have use cases for geographical information together with the configuration management information so as I start to go through these what I'm going to do is shrink these areas and then create basically pictures on the right with the use cases about how all this stuff happens with these these two tools that you have at your disposal as an ecosystems architect okay so each of these would talk about what do we do how do we use that configuration management data so it's basically really thinking Next Generation about the cmdb not tracking laptops and servers but tracking everything that has configuration all assets that have configuration so that's really that that level of thinking we're trying to get to here now the enter the The Architects that are involved whether it's the ecosystems Architects or the architects in the specific environment that are in charge of manufacturing the big use cases are really going to come down to is what are those cross sector things so what are the big goals of neom right as a city or if it's your company and you're doing manufacturing like like boing it would be to deliver airplanes or um you know different companies to do different things so whatever your sectors are right you you'd have those use cases within the sectors but what you'd also have is you'd also have these examples where you would have big things that would cross all the sectors right so in this neom this futuristic city I need to be able to look at all of those things I have right all of my assets that are configured in different ways so I need to know some information about the configuration so that I can look at what are the new ways that we can enhance sustainability what are the ways that we can improve the quality of life so if I have all that information like geographic distribution of everything and where it is and how it's configured to work with other things within the neom ecosystem you know how can I support these use cases better with that foundational data so another one that came up here like a runner up on these top three was Disaster Recovery right Disaster Recovery we had somebody present on that about a year and a half ago when you think of Dr right it really crosses all sections of an organization so when you get that data and if you have somebody running the cmdb and their main focus on the cmdb is just to take care of the data center right it's you don't really get this opportunity to leverage the data in quite the same way as what I'm proposing here as like an ecosystems architecture would um an ecosystems architect would actually propose so the thinking here right is to kind of escalate the the thinking behind ecos systems management a lot of the workshops that I've done with a lot of people are on the call today right a lot of the workshops focus on the cmdb is part of the service now platform and what we've been doing in a lot of cases we've been elevating that cmdb and cstm data so that we can have a better Global picture of our services and then all of the assets that support those Services right so that configuration of the services rather and and then we we can do these types of things right we can think about how can we use that data to support those bigger use cases so I think a lot of the you know the big part here right is that when we look at this we have to think about the configuration management differently we have to think about the geographical information differently there's all these relationships on that side about how your different areas are organized whether it's a shape around a football field in a city using using the city example or it's a um a specific address like geographical address of an office or it's the fifth floor in building five right so that's that geographical information and the relationship of those geographical spaces is really important as as an augmentation to those assets that you have so there's different relationships of those spaces just like there are in the assets and in order to elevate the value of this data right you need to also elevate the the position right the people that use this data so the proposal here basically is for an ecosystems architect to come in and be able to position that data as very strategic to the organization and not only how it operates within the Enterprise but how it operates across the entire ecosystem and so all all of its vendors all of its different databases and data sources and all this AI stuff that's going all over the place right like there's no there's no more Enterprise as the Enterprise used to be right we still need that that Enterprise architecture thinking we still need to have you know that function doesn't go away but we get a lot of more of these Enterprise Architects that start to fill that role of the ecosystems architect to have that broader perspective so if you want to learn more about the ecosystem architecture there is that book I I'll put a link when I upload these slides in case you want to use these slides but my thinking here was this group will be able to use kind of that same maybe this is a template to describe ecosystems architecture in your own environment uh some people already say that we're not really doing Enterprise architecture here so this may be a different way to reposition Enterprise architecture in your organization right to have that broader thinking that you really need for that next generation of technology and how it's going to support all these different environments so what you'll have here is you'll have like I said that template and and this will be your sectors on here right so I gave neom as an example I pulled it off the internet and I thought it was really cool to kind of get everybody thinking that way but the idea here is whatever you determine your ecosystems are that you'll be supporting with the configuration data together with the geographical data you can now make a really strong case that architecture has to have a play in this and that every sector I'll have an answer for on how I'm going to use that data right instead of recreating this data all over the place every time you buy something for facilities or you buy something for construction you're spreading this data out everywhere so it's not but this is making a case to bring it all together the configuration management data in one spot and the geographical information data which you know evidence from a couple meetings ago right people have that spread all over the place too so it gets really hard there's no it's I guess this is more a master data management proposal but it's also a proposal for new use cases new ways of thinking about how you architect Enterprises okay so that hopefully you guys can use this as a template and U apply it on your own I'd love to see somebody present this back to me with their organization mapped out something like this uh but I'll I'll be providing subsequent upgrades to this so that we have you'll have the template at least out on on the Forum so that you can pull it down and use it right the last piece on here I had is um I'm going to go ahead and just give some information the all this stuff you'll see here if you come out to that link I put in the chat and you type on uh you go to The Forum and then you go there'll be a a Blog in the Forum so you can go to the digital service Forum blog and that will give you access to the recording of this video and then donon slides and my slides will be up there by Monday right so you'll have access to all this in the community you can also sign up here for future sessions or go ahead and get information from past sessions so if you are interested in that conversation we had U you know led by a bunch of you guys I didn't really lead that one but on location data you can go back to that on this community I want to open it up for questions on anything on ecosystems architecture or any feedback on how hey John that was good but you should have gone at it this way right to introduce that New Concept and the new way of thinking any feedback you guys have now would be great or if you send me an email or put it on the community that would also be great hey John it's alen prosa hey Alan hey there um this is great um thank you very very much for this um it's huge it's overwhelming um and so just to try to um you know understand and comprehend it it's figuring out okay how am I going to eat this elephant or how am I I'm just going to walk around the elephant to understand what are all the pieces and the um and the interconnections still trying to process you know where ecosystems architecture is that like a VIN diagram overlap between between you know config and and Geographic um so it it's still you know settling um in my head seems like a really good thing um just off the top of my head what would probably enable um um um Embrace um and and engagement of this would be some sort of a road map something along the lines of um Foundation crawl walk run fly um just as a a way to to approach it because um because it's large so so I would say that that would be that would be a critical next step to get to getting support um like you know getting started with with ecosystems architecture you know where do I begin that could probably help I love that and one of the suggestions I had from one of my team when I showed it to this this to them on Monday was um like a maturity diagram you can go but my thinking so far is that one of the things you have to do is present configuration management outside of it right you got to pull that out of it and talk about a truck that's out there you know fixing a telephone pole right or cutting kudu off a wire right like there's something that has to show because I think people when you say cm DB right away people think of laptops and servers in a in a database right they don't think of facilities assets or instruction assets right or those types of things so that might be kind of like a phase one is you know do something outside of use the configuration management outside of an IT area yeah I like um another another way to to bridge out could be um either device management or or Internet of Things um because because both of those both of those get get out of the um uh like either the Ivory Tower or the walled city of of the data center um and and with a device with with a device out in the world it's not as regularly controlled um and so how you know how does that get configured what do we need to to know about that um and once you're outside of the data center it might be easier to get that bridge that you want okay so let's so let's think about some other things that aren't aren't it that have configuration or and and perhaps the the problem approach to that would be okay once you're outside there what's something that that causes a problem once your configuration goes wrong um and and how could that be prevented just those are ideas up top of my head yeah I love the use case idea and that's kind of where I'm going here but I think I need some pictures and more more descriptive things so that I can maybe pick a sector that they're really interested in like if I had you know people that were in here for food right I can click on it and talk about that topic so that this way it's more spread around and kind of options that's my thinking here is there'll be those stories that I could tell on each area as we go forward all right love that cool anybody else have GIS stands for geographical Information Systems Carol so we talked about that as foundational data a few meetings ago um so that's that's all of your location data that is you know in the Erp according to Eda right she said that's where it belongs most of the time some other people were saying it comes from active directory so kind of chasing that data about the location of things right in in my organization I love Forest management as an analogy that's a really good one we're working with uh the um Federal us one that's doing a wildlife observations right so that would be a really good one so if they identify new Wildlife they could take a picture and they put it into the federal database assets versus CIS Mitch yeah I I definitely cross the boundary there um the how it's configured versus how you know versus the physical or virtual asset that we're actually describing that's a line that we often cross back and forth over seamlessly but I think we got to be I think you're suggesting we need to be more deliberate in that right yeah the the other thing I'm trying to think of a bridge also is of something that's familiar you know because as we go to the right now you know as we focus in the services in this area right we we we you know we Bend our need to the cap business capability it just feels almost like like a a bubble around or a higher level of business capability as an ecosystem or yeah and I like the Tesla's situation too where okay you know what the the ecosystem that you depend on on that's outside your organization you want to you want to build that ecosystem within your organization so that you can control it like you know they took on chips or they took on the battery manufacturing right instead of having all these different things and maybe that's an ecosystem of itself that you bring in to your organization yeah yeah yeah yeah complex basically it's a complex model for like things operating together like the organisms or the businesses so you can kind of do that around anything you want to right if you it just it's a little broader thinking that's what Mark said right that Mark said that we're specifically calling out the fact that we need a a broader thinking methodology around architecture right because of how it's changed over the years and Enterprise architecture hasn't really changed that much I think when we had bill in here talking about business architecture I don't know if you guys remember that but I think it was last year that video got a lot of watches from that session but uh that's kind of that too right like they separated themselves out of Enterprise architecture and specifically modeling the business um that that was a little different too than you know kind of challenging the Enterprise architecture traditional definition if you will all right oh we're over two minutes sorry everybody thank you very much for all the feedback on this if you have any more thoughts afterwards I know it's a big topic send them my way I appreciate the feedback so far thank you John thanks