like to thank everyone for joining us for our Digital Services Forum this week you know our leader John is out on a much due holiday vacation so he's asked me to kind of step in and be a little bit of a Master of Ceremonies you know just to remind everyone that maybe looking at this for the first time or that is joining us again the idea of this Services forum is to talk about different approaches to leverage the platform better you know utilize the data the process processes methodologies to make all of you successful as we're going through this you know if you have questions feel free to put them in the chat I know that myself and AJ who AJ is the blonde that I see on the speaker um give AJ do you want to go ahead and introduce yourself sure my name is Amanda Justice I go by AJ I'm about 10 weeks into my servicenow journey I came from a servicenow customer that I've been a servicenow customer for the last 10 years and I set in our Enterprise architecture group as a field CTO and here to kind of support Michelle because I have actually deployed these within within a customer a few times now and so I might be able to kind of share my perspectives on Lessons Learned and successes I've had over the course of my career but I'm basically Michelle's wing woman today to help support the discussion great thank you so much for that and I forgot to introduce myself I probably know some of you guys but Rachel trombetta I'm an Enterprise architect field CTO working on the eastern half of the U.S you know my expertise is really in manufacturing AJ is huge and very humble about hers and the utility space I've got a little bit of that for working for General Electric for 13 and then retail space and then without further Ado I you know want to hand it over to Dr Michelle super from our European team and give her a chance to introduce herself and give you an overview of what we're going to talk about today and Michelle if you could also let the team know would you rather them come off mute you answer questions in line or wait till the end that's your choice today um it's probably easy if we wait for questions to the end um if you have any questions in between then feel free to put them in the chat and uh we'll see what we can do great thank you okay so let's get started thank you for having me here it's always good to give a webinar and share knowledge and we're going to be talking today about application portfolio rationalization and a management approach using servicenow I'm going to go into a more cos Cornwall practical way of doing Enterprise architecture so it's not all going to be about the now platform today we're going to be looking at techniques that you can use within your own organizations to help to rationalize your application portfolio um and set it up ready for success with the now platform foreign let me change there we go right so an introduction to me first of all so you know who I am uh Dr Michelle supper um and I'm a senior advisory executive architect in the emea Enterprise architecture team um I created a methodology called guided architecture which some of you might have experienced already with servicenow Enterprise Architects we've now trained a hundred nearly 190 Enterprise and platform Architects across across servicenow in this methodology to help our customers and how did I get to this point well um the phds in astrophysics but the in terms of my my professional career I started off as a system architect um with the ministry defense over here in the UK and Secret Service um designed all kinds of things I'm not allowed to talk about and then I went on to become a consultant Enterprise architect a government public and private sector um before I joined service now I was at the open group with standards body where I was director of three Enterprise architecture standards forums um so uh looking after a thousand Enterprise Architects and helping them to to write the standards that we all use um and through that and yeah a lot of years of working with the open group generally um I've now been contributing author to a book eight standards several guides and white papers including it for it version 3 which was released last week um I have been doing um architecture for 13 years um I'm still learning um and I'd like to share all this experience with you so um also a Shameless plug please do join the Enterprise architecture Forum on LinkedIn here's a link in the chat I'll let you in when I finish speaking um this is a place where we have conversation where we share knowledge about Enterprise architecture techniques so please do join now an overview to what we're going to be talking about today so first of all we're going to have a look at a high level approach to application rationalization this is something which a lot of organizations struggle with organizations of a certain age of a certain size tend to accumulate large numbers of applications so what I'm going to do is take you through a high level approach to helping you see the wood for the trees how to how do you start to handle that situation when you have more applications then you can manage easily um then we're going to be looking at transformation so patterns for migration onto the now platform and then how to do ongoing portfolio management so how to use the servicenow APM package um and the benefits that that package can give you alongside other packages that sit on the now platform and also how to use an Enterprise architecture tool alongside the APM package and the benefits that that gives so start off with a high level approach for application rationalization um so there are four uh little phrases in this in this process as I envisage it the first one is Discovery the second one quick wins and opportunities then we move into transform build and learn and then finally into continual Improvement and if you follow this process as part of a digital transformation with servicenow then it's possible to get architecture architect support throughout your journey so at the beginning um in in pre-sales and the beginning of your your transformation you'd have help from Enterprise architecture my team and others like me um then you'd move across into platform Architects as you started to do implementation and integration onto the platform and finally you move across into customer success architects who can help you to get as much value as possible out of the out of the platform so this isn't a journey that you have to make alone and let's have a look at each of these phases in a little bit more detail so if we start off with discovery this is where you start to gather your candidates for rationalization where you understand you know and build the list of all the applications that you want to consider as part of the transformation as plus the rationalization activity and as part of this you want to be understanding different characteristics of those applications so what do they do what is their function do you know their life cycle status are there users users and owners and how many users are there associated with with each of those applications what do you know about the licensing and the development support costs and all these other different characteristics and the more contextual information you have um in relation to an application that the more easily you can make strategic decisions about it and so Discovery is something that used to be done you know just walking around the floor plate of the office and asking people what application do you have what do you use these days we have on the now platform Discovery and visibility part of item which would help you to automatically find out and and crawl through your networks and find out what applications you have and get a lot of this information which which really does help a lot second one would be quick wins and opportunities so once you've got that list from the first phase you can analyze it and identify quick wins for immediate retirement um what we have here you know is in the picture is the low hanging fruit it's the way it's often referred to um it's this phase you can start to look at how the now platform could possibly replace applications that you have which could then be retired you can start to make decisions about how you're going to integrate the apps that you want to keep and how you're going to align them with the platform and you can also start to identify apps which are suitable for redevelopment as custom apps on the platform so there are different options that you can take with applications um so you know this is why it's important to get first get that big list and understand them completely and then you can start to make those strategic decisions when you've decided your priority order for actions against the business capability um you can look at you know how much value you're going to get cost Savings of course don't forget there will be costs associated with rationalization activity and that's also something you have to bear in mind um and at this stage when you're starting to scope out the scale of the work you're going to do this is the the sort of phase of a rationalization project when you might want to identify a delivery partner who can assist uh with the decision making and with the implementation work the next phase would be transform build and learn this is where if you can retire applications you do so and that really does help to simplify your landscape where you start to integrate any applications that you want to keep with using the integration Hub Into the Now platform and where those candidates that you think you can rebuild can be rebuilt on the now platform with the app engine and to support this there were things that can be done within your organization so you can start to upscale application development teams and line of business developers they will know your business better than any external organization would and so it helps to have these skills in-house it also provides continuity for when things need to be maintained um you can create a center of excellence for servicenow so low code application development to make sure that these things can be maintained in the future and as stuff starts to be built up onto the now platform this is when you can start to deploy machine learning and artificial intelligence enhancements that will help you to realize even greater efficiencies and the more platform you use but the more efficiencies you can get because you'll be able to share the data cleanly across the platform and finally continual Improvement so this phase that you start to use the now platform to Monitor and manage this application landscape that you've now created for yourself so if you started off with let's say chaos thousands of applications that we had a lot of Legacy things things that need to be removed um by this point you will have tidied up your application landscape quite considerably you now can see the wood for the trees everything in your landscape is relevant and everything there is giving value back to your organization so now you want to maintain the health of that and this is where you can start to use parts of the now platform things like visibility to keep a view of everything you can use the APM to manage your applications and also things like ham and Sam so that's hardware asset management software Asset Management which will help continuously to inform um strategic decisions enhance that business continuity reduce your costs and improve agility agility is something that a lot of people want but they're not sure how to get it um and so uh your way of looking at this if you have too many applications and you're not sure what you can change because if you change something then all your systems might collapse you know that is going to bring in a certain fear a certain level of risk right the more the more clearly you can understand your systems the easier it is to make a change and the easier it is to be agile and adjust to fit conditions in the market so um Simplicity is King here to support all this review architecture governance so look at the principles that you're using look at your governance boards make sure that they're effective establish application request methodology to make sure that applications don't start to proliferate again so you don't have many many more and start to create that system development culture so that people will you know instead of going out to find and buy an application we'll start to think how can I use the data I have and develop an application easily a report that will help me to get the the response I need okay so that's the first part that's a high level approach that I would take to rationalization so next I'm going to talk about um a way of triaging applications so let's say you're in a situation where you found you've got two and a half thousand applications in a list and you're not quite sure what to do with them it's it's very hard to you know to even get started when you're faced with this huge amount and I've seen I've seen customers with more than that um so you know if if you're in the situation um there is a way through and this is how to do it so I'm going to share with you an approach which I developed and used at the UK Ministry of Justice to help to rationalize the applications that they used in their prison service um and it's very simple it's based on grids which we'll go through in a moment and I've extended it out to the now platform so that we can start to very quickly um understand and and triage that big list of applications we make in Discovery and then start to make the decisions that we need to to move um to move on to the now platform okay so the first of these grids in the method is this one this is the Strategic relevance and impact grid um it was developed by McFarland and he was introduced by him in the Harvard Business Review uh in 1984 so yeah this has been established for a long time now um but in this strategic relevance and impact grid what you do is you just draw a quadrant graph like this um and you distribute the applications within it depending on what they are what them what their relevance to your organization is and their health well okay so ideally you want your applications to be in the green boxes at the Top If an application is strategic then is vital to the whole Enterprise these applications are going to be your top priority these are the ones you're going to fund first you know if you're limited in your budget if one of your strategic applications goes down your whole organization will fail so we saw this yesterday when when WhatsApp fell over they must have attacked some some strategic application and then the whole of what's that went down that will be a strategic application um Factory is an or operational is vital to a part of the Enterprise your second priority the things that you found second these will be things like an HR tool for example it's it's vital to the HR department but not to the rest of the organization so it's it's a factory tool something which is in turnaround is a new application which is on the horizon it's something that you don't have yet it might be an application or platform or some new functionality you can see it coming it's going to have a strategic impact it's something you have to be aware of but it's not actually in your landscape at the moment but you can there's a place for it to be put in that and turn around and support is something which is non-essential it's low business value and it's something you can consider Outsourcing or divesting so often if you've had an organization that's been running for a few years in a few decades maybe the organization might have changed you'll have Legacy things these are you know or the organization that has no it's not looking in that particular area anymore but it's still got applications that are relevant to something it doesn't do that would be one of these things okay these are the low hanging fruit this is this is the support box all right okay so here are some applications distributed within this grid okay I'm not going to consider real applications so just putting some examples in here this is how you do it just name the applications in each grid it is really that simple the second grid I'm going to show you is this one this is an application portfolio optimization grid this is the one that looks at the the fit and the health of the organizer of the applications so healthy applications which are low risk good fit business-wise and technically sit up in the healthy applications quadrant that's the only place an application wants to be if an application isn't healthy it might sit in functional re-engineering so this is this is what happens when a business has changed but the applications haven't caught up yet they need to be adjusted in order to better fit the needs of the business so perhaps a process has changed and a process workflow has to be redesigned with an application then that application will require functional re-engineering if it's sitting in technical re-engineering then it means that something has to be done to the application to maintain its health so perhaps it has to be migrated to a different platform the infrastructure needs upgrading it might need a security patch that kind of a thing so something technically needs to be done to it to bring it into Health to to move the application from technical up to healthy so that's where that's what technical engineering is retirement candidates again this is for legacy stuff and for old things these are the applications at high risk they're poor business fit poor technical fit and this is where you need to consider what to do with them it it's very rare that you can simply turn something off um I was talking with customers this morning who weren't sure how an application connected to to its users and they said oh we could just turn it off and see who shouts loudest and of course that is one way of doing it um but there are other things to consider as well so for example um if you have um if you have data that's sitting inside that application that data might need to be decommissioned properly it might need to be transferred to somewhere else or archived somewhere um so you know this is how to yeah you you can't just turn these things off think carefully about how you're going to um retire an application cleanly um and make sure that it doesn't cause damage so if we take our applications and distribute them again okay here we are so I've distributed some applications um and this is a fun bit now so now we can start to combine the grids together on the so when we start to combine them together this is when we get real deep insights and this is why I use multiple grids so um if you take this for example we can say oh look strategically these are the applications which are strategic only one of them is healthy and three of them need some re-engineering either technical or functional okay so if you were going to if this was the result of your grid then you your strategic applications would be of top priority um this one will be fine it's healthy but then you you'd have to work on these immediately because you don't want those to fall over so you'd fix them then you move into your factory they all need some up some functional technical re-engineering there as well and then we've got the support where we can retire something and look at ways of retiring the others as well okay so it's a way quickly to triage things and this is this works really well in a workshop type environment as well so you can you can sit with people together and yeah even with Post-it notes on quadrants and just quickly get through thousands of applications and understand what you need to do with them um if you want to get um you know things more visible you can you can make things easy to see if you color code them you can also add another dimension if you want so here we've got ticks and dots so what you have here is let's say you know who the owner of the application is you can put a tick next to it and if there's a DOT then you don't know who the owner is when I did this at the ministry of Justice I found that several Applications had no owner and and that implied that they weren't being managed actively um and so you know that represents a very high risk so this is you know this is a way you can quickly get a grasp of your application landscape so there you go and the final one this is where we start to extend it out into um the now platform itself so this is where you have to start making decisions about what you're going to do with those applications um and I've given you four options here you can either replace okay so you can replace the application entirely by a package on the now platform or a function on the now platform um and if you do that then you get the value of being able to simplify your landscape you get to retire an application or several applications at a time um and you get to use more of the platform functionality which if your customer you've paid for so you might as well use okay migrate is um something where you can't simply replace it automatically you have to start thinking about how you're going to do that so you might have to start moving data across first or functionality across those decisions to be made and some action that needs to be taken to migrate something actively across onto the platform a custom app is something that's going to be requiring some development work so um it it's worth keeping a note of the things that are going to need custom maps because that way you can start to get your development teams tasked up properly and schedule the which path you're going to take to get to to uh to get all those things developed properly together which order you're going to make them in and finally keep so that is you've got an application you really like it it can't be changed and so you're going to keep it and now there's a choice of how you're going to integrate it with the platform if necessary or how are you going to make sure that its functionality doesn't overlap with anything that the platform is doing okay okay so those are that's the grids so if you were faced with that big decision you've got thousands of applications I'd recommend using these grids they can quickly help you to triage things down um and using the different quadrants and cross-referencing them by combining the grids you get a really deep insight into what to do and from there you can start to build a roadmap of activity and how you're going to move forward and which things are you going to retire what are you going to update and what you what will you migrate what will you integrate okay so next thing you've got patterns for migration to the platform so often we will think about our applications um just by themselves um if you are an end user within an organization you'll be looking um you know very much at one application your focus is in that application you might not realize that there are perhaps a dozen applications within your organization that do the same thing and so you know if in that case you have fragments of functionality and you might have fragmented processes as well so let's look at these two let's look at these two patterns and I'll show you how with this you can start to make um you know big leaps towards moving on to the platform I've got some nice little animations to help us on this journey so first pattern I'd like you to consider is fragments of functionality so here we have a situation where maybe there's a big application that your organization has got and let's say it was bought 10 years ago as time has gone on you found that this this big application didn't cover all the functionality that was needed um so over time your developers have created little add-ons little plugins to this big application so you now have something that looks a bit like a covered virus when you have a big application um and the the smaller ones all interfacing with it and the big application might also be feeding off a data source so I'm sure this this kind of landscape looks quite familiar to you this pattern will be familiar so how do we move this onto the platform um I have dealt with customers who've looked at this kind of this kind of arrangement and their immediate focus is to think we'll move the small pieces onto the platform if you do that then all of these arrows here all these interfaces will have to be recreated so you're still going to be interfacing that that big application integrating it many times to the now platform to do all these different things to the different pieces so maybe not the best approach here's a different way so if we take the now platform we take a now platform package something that can replicate this one approach would be to transfer the function of the big application if you can to the platform if you do that then you can then move that across and now you have the chance to move the functionality of the smaller applications the plugins and move those to the platform as well there you go and then you can integrate the data source for the now platform so if you're in the situation where you have this big application and there's smaller pieces around it if you map those out ahead of time you'll be able to then move them across as a piece Into the Now platform that that gives you a serious opportunity to do real rationalization of many applications at once and also the potential to save money if you only take the small plugins across then you're still going to be maintaining that larger application and the now platform together and paying for both if it's possible for you to move the big application across then it's a chance to rationalize away and retire that big application along with all of the different plugins as well and bring that all into one piece so well worth considering this pattern the next one I'd like you to consider is fragmented processes so you might have a process it's fragmented across many applications so these arrows down here represent a process and these dots represent the applications that are running to make this process happen so you know think about you know finding all these different um all these different uh applications here and when I say find the applications I do mean all of them okay so and do fill in the gaps you might find that people are using Excel spreadsheets macros little plugins all kinds of workarounds if if systems aren't working properly so do make sure that you have got all of the of the applications in a process and when you know all of them and you can you can map the data flow all the way through and now you have a real opportunity to automate that whole process on the now platform so you can take what all of these things are doing if you have an appropriate package on the now platform that can handle it then you can transfer the function of those applications to the platform and automate the whole thing end to end of course this is just an example of one small process it's possible to do this across entire value streams you can you know if if you want to do value stream analysis that's a very good way of looking at across multiple business capabilities within your organization and rationalizing many applications at once and automating into into one end-to-end process one end-to-end workflow which can massively improve the efficiency of what you're doing in the business so there you go so now we've transferred it across the platform okay so that brings us to here we've now first been in this huge uh chaotic Forest of applications we've rationalized away we've seen the wood for the trees we've moved a lot of stuff onto the platform so now we have to put it at a place where landscape is clean it's tidy we have just the applications that we want and they're all giving value to us so now what we want to do is maintain the health of our of our application landscape into the future um so this is where we can start to use things like service now's APM and if we like we can also extend that use out to use the APM alongside an Enterprise architecture tool so I'm going to show you how these things work very briefly okay so what does servicenow's APM module do so the APM sits inside the the cmdb um so the databases Central to the now platform and what it does is it brings together the Tactical and operational information on the applications and their current status okay very important is their current status it does not do future estate modeling okay um the APM is going to provide you with a dashboard and on that dashboard you can see what applications you have and how they're doing and that gives you information like the owners use the costs lifecycle stage the associated risk all those things which we mentioned before in Discovery so APM can also associate applications with each other so it can tell you what's connected and with other Concepts and it can start to do calculations as well so it shows you how the applications connect it can show you how applications connect to your business capabilities and here you have a choice so if you have your own business capability map you can feed that in and it will show you can wire it up to show how they connect or you can use the built-in capability map that's that's been derived from the apqc standard which comes with APM foreign architecture repository tool do okay so Enterprise architecture tools are separate to the now platform you know third parties um but they provide different functionality and they can really help so as an Enterprise architect I advocate the use of the EA repository tool I I can't see how Enterprise architect of a large organization can be managed effectively without one these days um so there are several tools that can be integrated with the now platform directly to the cmdb um these ones are ins Biz design in Supply and then ax all of these have got integration apps available and the nice thing about these tools is that they give you visualization of of your Enterprise architecture they bring that data to life for you they help you to analyze it and they enable you to do a future State Design they help you to to map out what you want ahead of time and test things before you put it into play so they all of these tools will support different modeling disciplines you can do things like solution architecture security architecture you can map out your business processes so if you're currently using it at a different different tool to map business process that's another rationalization you can do if you bring in an Enterprise architecture tool because they all support bpmn and actually when when your business processes are within your Enterprise architecture repository tool you can then connect them to other parts of your architecture and then they become really valuable so you can say ah this capability supports these business processes you can say this data if you have your data flows in there this data is associated with this process these applications it's people all of these things can be connected together um for me the the value of an Enterprise architecture is in the way that it connects data together so yeah the more data you can put in there the better um you can start to do that information data modeling value streams you can do Journey mapping for your customers strategy modeling and so on so there's lots of things you can do with an EA tool and of course they give you visualization dashboarding and and other tools other functionality okay with applications they help you to draw out Landscapes you can actually visually see how things connect together that's very useful and communication diagrams will show how data is flowing um so all of these are helpful um Enterprise architectural enables you to um identify which of your business capabilities are aligned to which of your goals it's really important to make sure if you're doing any change that any change you make aligns to the stress you should choose the Strategic intent of your organization so if you can map those things back then all the better and it helps you to plan those Target States and the transition States and that'll help you to optimize the application portfolio um and it helps you to establish a common decision-making basis um so rather than just making a decision based on a sentiment you can actually have evidence and all these things can be used to support business cases so that's the case for an EA repository tool of course when you have a tool which integrates with the cmdb um the cmdb of the now platform can gather the information so you'll use things like Discovery visibility service mapping on the now platform fill up that information on the cmdb you can pass all that information live straight to your repository tool to keep it up to date so it becomes a very powerful Partnership if you have these two things in place so a quick guide to the abbreviations that we use because you'll need them for the next diagram I'll just let you read those for a moment these are different packages that sit on the now platform um there'll be a pop quiz later so here's a diagram so here's APM all right so the bare minimum or the basic standard would be this piece here for APM there's the APM package and it provides the dashboard the APM sits inside as the MDB okay so that would be the minimum part what you can do though is you can use other packages on the now platform to support the use of the APM and the more pieces that you have uh the more contextual information you get it enhances the data that you have within the APM and you get a much better picture so for example um the SPM is going to give you the demands and the projects so with that you can start to make an application roadmap and all the information is going to go into cmdb if you have irm then that's going to feed in all the information that you need about risks policies controls penetration testing and so on if you have items some harm that's going to give you all the information you need about your technology portfolio your life cycle data item with Discovery and service mapping is going to is really key to this and that's going to feed in the application list and the relationships and between the applications and the instances of servicenow that you have devops give development information and there's also a line back here as well so now the APM dashboard can push things back here into DPM which will help you to then build out an a roadmap of implementation tasks and then to to task individual roles or people to go and do those things okay so all of this works together so let's see what happens so if you just you know I'm not saying at any point they should get all of the things on the platform of course you're welcome to do that and more than happy to um but if let's you can you can pick and choose the pieces that you need so let's say you use APM and cmdb then they will provide the um the the Enterprise architecture tool if you connect it they will give you cmgb content and you have to manually input everything else but just with this bare minimum you will still be able to create as is and to be views um of your application landscape if you add in on top of this the item discovery and service mapping then you also have populated application inventory and all the relationships that you need between the applications and the instances and then with this the Enterprise architecture tool will be able to give you populated repositories and Landscape portfolio catalog communication diagram that shows how all those applications are connected together and what data's flowing between them and service mapping add in SPM and now you've got all those roadmaps so now um if you have a tool which has a two-way integration you'll be able to um map out and plan what you want to do with your 2B View and then pass all those tasks back um from the Enterprise architecture tool Into the Now platform to be scheduled and action by by real people and actually Implement things if you add in item summon ham this is all the things that you need to manage your technology portfolio um so with all of that you can use your Enterprise architecture tool to start creating detailed application management dashboards heat Maps things that you can use to planning and manage all your ID assets a lot of this can be done on directly on the APM dashboard as well so it's not entirely dependent on having a tool for that part irm will give you risk policies and controls and risk assessments and all of this risk information what are heat Maps Okay so in the here we've got a question in the in the chat a heat map is when you have a diagram let's say and you make the diagram just black and white you can then color parts of that of that diagram to indicate different characteristics so you might heat map a diagram to show costs of applications or numbers of users or where is the risk in this system and it's a really good visual way of seeing immediately what um where where things need attention that's what a heat map is okay um so if you if you add in all your your irm data so you've got your your risks then an EA tool can give you risk management data dashboards and risk overlays on other diagrams really good actually if you're doing um gdpr mapping and you're you you're looking at your applications and then you map those applications so the data flows and then you say which of these data flows um are gdpr sensitive and then you know these you can show all this on a diagram which makes your security Architects very happy and because then they know where they need to you know Focus their attention I finally DPM um sits within the now platform and what this does it brings together all the information that you have um and it allows you to see all the information that you have in your it assets and to monitor your it operations on an ongoing basis so a way of looking at this um the now platform Maps exactly what you have now what exists on your network and the EA tool can be used to map what will exist or what you what you're thinking about is is your it's where you can start to plan things okay so your options your development options your potential 2B views all of that stuff can be um quite happily mapped out in the into an Enterprise architecture tool and your day-to-day management of it can be done Direct in the now platform so what's the benefits so if we're looking at the benefits of using the now APM package with an Enterprise architecture tool um most of these EA tools now are Cloud hosted um so they're all online um if you have yeah obviously the now platform is as well and so what you have then is two tools which are Cloud hosted there's a frequent easy upgrade Cadence so um it's it's these things can be maintained easily um you get a single source of truth if you're mapping everything out of the cmdb and it also encourages you to put all your data into the CMD being align better to the csdm so if you populate that cmdb make sure that's your single source of Truth as far as possible and then use the integration applications that we have to go into those EA tools and they can automatically populate that repository for you from that source of Truth and keep it up to date so anytime anything changes in your landscape it will update the repository for you it gives you visibility of the current assets okay your whole Global application State and any other platforms you have there in your yeah so it's and all your services so um it's a really good quick easy way of maintaining your Enterprise architecture and having all this visibility enables you to start planning how to simplify your landscape and really rationalize those application Technologies um when you when you can see what you have it then you can make decisions about it um when you have too many processes or processes across purposes your business is not going to be efficient if you can see where those processes are if you can defragment them automate them um and and get them flowing through the platform then things will get better um and having the a tool enables you to do that strategic planning for the future so if you're looking about where should data be mastered you can make a clean delineation you can say that current data existing things can be Mastered on the platform any future State any road mapping anything which doesn't exist for real with just an idea that stuff can be mastered in an Enterprise architecture tool um okay in terms of controlling governance processes um you get total visibility if you do this so you get to see all of your applications there's nowhere to hide um controls are associated with the applications um and you can align your business to your strategy and and visualize that and it makes it much easier to adhere to principles and constraints so if you're if you're running um I can't read all of that doing sorry I willed in a moment um if you're if you're running um a good governance strategy and you're running um your your applications through APM um then you can start to combine those things so if you you can use the information that you have um either through the APM or through your EA tool to uh to support your governance processes and these things are extensible so you continue to get value over time from both you can continue to extend your use of the platform and you can extend um the the breadth and depth of the Enterprise architecture model that you have the a tool so basically what I'm saying is you get the best of both worlds if you use these things together the platform gives you the visibility the repository gives you the visualization um and between those two things you you get to see what you have in your organization you get to manage it more easily um and that Whirlwind of a presentation um comes from an end there so now I can take questions yeah sure okay so I put it in the chat but effectively during your presentation which is awesome you had talked about the fragmented processes and so yeah that happens but in servicenow do not part of 8 PM but just well it's part of the business app table on the form you have an architecture type field and the idea is you select one of the choices being architecture host then you have to select the platform application so sorry one of the platform hosts would be the selection of that field and then it makes mandatory the other field where you have to select the actual platform application which is a reference field I I think back to the business app so you're linking two business apps together in that relationship that was similar to what you did in the model in your slide where you said okay all these business apps they sprung up over time they're now going to be put in this so-called platform and I'm pointing out that may be one of the ways that it could be done because you were not very clear on how exactly you do that like do you do that to wraps rats when you you basically consolidate right and then it becomes part of that platform you buy another application that is a platform app that now all this functionality goes and gets rebuilt on that and then it continues because there's another scenario where uh you have this attribute that Mark bodman had talked about where business apps uses reference attribute to business apps and that is not the same as when you create some of the you know business app consumes application Service uh Business Service offering technical service offering depends on uh the application service so those relationships are created when you're filling out your csdn b c csdm I'm just curious about this user's reference attribute how is that different in this business application to business application relationship that you mentioned and how is that different than using the architecture type field or platform and platform host it was a lot but really uh he really made me start thinking with that one or those few slides that you presented this which was very well done thank you right thank you um you're going to have a lot more detail than I would normally go into um so I'm not quite able to answer the question to the technical level that you've answered you've asked it um if I if I if I stay at my abstract sort of level we're talking about fragmented processes yeah so um if we look at it just from an Enterprise architecture perspective um and I'll give you and give you an analogy from a place I used to work I used to work for a Housing Association um over here in the UK so a place that that provides houses to people can't afford and they um they had a a process which they asked me to look at which was how they um how they send maintenance teams out to do maintenance and clear up rubbish outside people's homes you think it would be quite simple um they've managed to make it incredibly complicated to the point where when I mapped it out I found that they were using 18 different applications um and and spreadsheets in between to pass information um about the homeowner their you know their address what needed to be done um and across into the the maintenance staff and then they got to pass this information around each other to schedule things and then to send somebody out to go do the task come back and report back on it and because they made it so complicated the whole process took over a week instead of just taking a day so what I'm saying is rather than you know when I when I work with customers who are doing rationalization um they tend to think oh this process is in this application I'll just move that over there um what I'm saying is widen out the scope to a whole end-to-end process look at all the different applications that are being used in that and see if that whole end-to-end process can be re-engineered into something which is more efficient before moving into the platform um so so taking all those different fragments and bring them together into something better and recreating that on the on the on the well creating that on the platform rather than recreating the mess that was there before is does that make it clearer yeah yeah thank you for clarifying that and that's easier said than done that's for sure oh yeah but it's it's kind of essential um otherwise we end up with a situation I'm sure you've seen in other places as well where um people will say you know let's let's move this onto a platform and they'll end up recreating exactly the bad situation they had but in a different place whenever whenever we have sorry I was just say uh your answer is a very strategic high level and appreciated and I think mine were more tactical with regards to how the how servicenow built things to make all those connections but I'll I'll pursue that in another Avenue to get a more precise technical piece on there's how you should do it from where you just explained and that makes sense and it's very difficult to do I think people conceptualize all those moving parts and how to redo the whole thing and then there's what service now is provided in the platform for you to actually visualize that by making all the connections so I need to pursue that further thank you yeah with regards of visualization I think that we are doing something there's something coming up where there's a connection into Lucid shots so things will be becoming more visual soon on the platform um but uh we are Michelle I might be able to help a little bit with that for example do you have a platform architect uh yes we do or an Enterprise architect sorry so I meant the same you might reach out to them we do some csdm workshops that we can help you with what that would look like because it if we use servicenow as an example that's a perfect use case of how do you look at an entire process and what is a process versus a service and I think we can help you with that it's a lot more than we could answer in three minutes I just wanted to give you a place to go help and if they get stuck um feel free to have them reach out to me Rachel trombetta during Enterprise architect and we'll help get them connected oh absolutely thank you you're welcome and Michelle I want to be mindful of time you've got about three minutes left yeah so there's a question here of my use of the word platform whether it's specific to service now more generically when I when I say moving it onto onto the platform or using a package on the platform I'm talking about servicenow um but if you if you're talking about um the the if you talk about how to how to map platforms together um and and visualize them then then any platform that is connected to the now platform could be mapped and created into into a visualization of an application landscape um one other thing when we were talking about drawing out have you seen how Inspire who's one of our partners does the actual drawing of the visualization layer that then overlays on top of cmdb uh yes okay that might be something Louis that to take a look at yeah so all of the Enterprise architecture tools I mentioned will do that um so Inspire has their own notation um Biz design would use archimate um I recently created an archimate visual a market model of the csdm which is um gave that to business design which is where the integration app has come from um so so um there's there's different ways of of mapping out and visualizing um often when you take the Enterprise architecture data and you put it into a more visual form it really does help you to do analysis it helps you to see the patterns and the trends that you can't just see in a list of data so I do encourage you and whatever you're using whether using an EA tool or or you know just physio just please map things out and get that yeah really do get the the value in the visualization um so you can see what's going on okay well thank you God thank you everyone so much for your time today and Michelle great content I always learn something everything that you present um we will be posting this video when John gets back because he's the only one I think that knows how to do this unless it's Dynamic and stay tuned in two weeks we'll have another topic and send that out to all of you guys okay thank you thank you you thank you so much cheers