let's have a chat on uh what we're actually doing concerning uh future State planning on the service now platform um first and foremost of course the Safe Harbor uh those of you who seen this is classic slide um so basically means this is a presentation it can contain forward-looking statements basically means it might not be what we will do but I will show you some things anyway which is in the the planning stage uh it reflects basically what we believe in our s and service now so let's get the formalities over uh for those of you who started up uh this session here is actually a part of the uh live on service now uh it's a created event series that connects everyone yourself and service now experts and peers or Partners like myself um to help deploy the right products and achieve the values faster that you're looking for um so we hope uh to join us again in other webinars in the series there'll be something at the end right where we show us well for the next webinar that that comes up that you can look for um but for now I think um you can also schedule it or scan the QR code which you have here and I can see someone is writing me which is great um so you will get that but let's have a look so um we basically uh have time we should have some time at the end for some Q&A so if you have any questions um you can just write it in the Q&A area then I will see if I have time for that if I don't have time for that we do as we always do then we will take questions we will answer that um and then send it out to you afterwards so you will get an answer to that um the presentation here is recorded it will be shared as part of the service now community and after the event there will be as well a short survey um that you can answer um basically our goto actions uh if you want to uh hear more about that there actually two surveys there's another one that comes up but um this is anyway what goes on at the end all right right let's jump into the meat of the matter let's have a look at the agenda as we have here uh first and foremost we will have a look of course on the industry uh overview about where we are um then we will take a look at Apple we've done uh by our marketing team uh which was recently conducted about where is the the talk about future State modeling where is it in people's conscience at the moment this is something that companies are really looking for um in comparison to for other things that are current uh and and relevant for them um there's a poll being done we will do one here as well I would expect it should show you interested because otherwise while you're here there a little bit biased but nevertheless we will take the result of that and say that's how it is for the market um then of course we will go into having a look at the the steps we need to take to really be successful with future State planning there are some best practices we learn through many years and many uh clients and customers that we work with we will have a look at that there two use cases I will basically talk about them as well and I will also go in and do a live demonstration about how we on the APM in combination of APM and designer really work with current state and future States and can make these different transition ideas U for what we want to do so with that let's have a look at a poll here so hopefully everyone should have poll question number one showing up um whether what what's relevant for your environment for where you are concerning Enterprise architecture are you looking at current states the future States stat of quality and others and I will just give you guys half a minute 45 minute 45 seconds to answer that wow a lot of par that's really cool guys thanks for this so my marketing L is here that's actually Marina where we should have a little bit of background music like the elevator music and so on why people are writing the poll here there's still people that are putting things in so thanks for that guys okay if okay so 40 people have answered I think let's stop there 41 okay still popping in but basically as you can see what we can see here is that current state is something that 27% of you guys are focused on that just makes sense right because honestly as you will see in the steps we can't really talk about future State planning without understanding what we have there are a few gaps we need to be aware of a little bit of danger around the current state modeling and current state in itself how we work with that future State planning of course absolutely essential I would say as an architect this is really our ABC if we're not the ones who go out and make suggestions for future states of what we should do based on business requirements we get in and considering all the different assets and other things we have that's basically I would say a fundamental thing that Architects are doing so I'm very happy that 51% of you are looking at that data quality 15% that's actually pretty good guys data quality is absolutely essential um which is by the way another webinar we did on that what we really do around data quality I will mention a little bit why it's so important um and then of course others that we uh other topics that you have here so let me stop sharing that and then move to the next slide which shows what our marketing guys have found out so we have basically in the big survey we did here with about 5,000 people answered that you can see we're very close so they basically have 22% for current state you guys were 27% so that's pretty close 61% for the future State you guys had 51 and then 15 on data quality uh what what you guys voted and we have 12% here so you reflect pretty good what the market of 5,000 people um think as well so yeah well done well done I would say that's pretty cool all right let's get into the matter and talk a little bit about what we are talking about when we are talking about future State planning so we have basically two basic things when we talk about current state elements so in the world of where we live here we say things are committed so committed elements basically means elements or CI elements as it's called in service now that basically means it exists so it's part of a table we can see it we can see the data traditionally we would say if it's committed then it's part of our current state it has what's been picked up by the by the um uh the data scan where basically that has gone in what has been found on the network that what people are working with that's what we see in the service now platform for the business applications for the APM this is what we would call the current state this is currently what I have now future State elements as I will demonstrate here in the designer are elements which are still aligned with the data model and the tables that we have in service now but they're not yet committed they are suggestions for change right so in that sense we can actually fit it out we can put in for instance another business application we can even fill out information on that business application you know for instance how critical be who will be the owner of that what is it what's the purpose of what what is it actually doing what is it related to you know which capabilities is it providing which software and Hardware lies underneath it which software products are part of as well of the applications etc etc we can specify that even if the element does not exist yet and that's really cool so that basically means we can work with a combination of live data straight from service now and remember what I will show you later is an embedded uh Solution on the design which is basic the way I always explain it this is like a functional extension of your service down platform there is no fin client or fit client or fin client there's no Integrations that is it is literally your service now platform where that modeling capability has just been added for your for your current state a future State planning that means as well we can drag in basically anything we have on service now whether that being you know other CI elements of business applications that we have here from APM relationships reference fields and other things that we're using in service St which is relevant we can just drag that in we don't need to integrate to it and that's again one of the beauties of why we created it in this way originally is we we're not big fans of doing that integration when we have a fantastic platform like service now why are we not just extending the capability of the platform itself to do that right which is exactly what we're doing here so again future State elements that we're saying it is recognized classes all so it's now lingo it's recognized CI elements of tables of service now but it is not committed but because it's recognized as a valid element that means we can also work with it as if it was actually an element already committed which I will show you some examples on where we can actually as well do um suggested or future State relationships of that element and it's all aligned to the underlying data model that you have in service now so that's actually pretty cool so we're not working anymore like in traditional I would say modeling tools you have out there where we're just putting shapes together with different lines here guys we're combining and really have the real data model underneath and we have the real elements as well that we can link up to and again we have access to everything so when we're talking about how do we actually do that and what are the steps thank you what are the steps oh my God come on thank you what are the steps basically me to go through we need of course to understand the current state so the very first first thing you do is need to understand what you have right it's a little bit like one of these because how can I plan something if I don't know what I have how will I change what I don't know what I have it doesn't really make any sense so of course you need to start by understanding what is the current state what is it I have for instance in the APM what applications do I have right and of course you need to do a little bit of pre-work and specify the difference between well what is an application what is a software product what is a service how do I distinguish that how do I box them there are of course definitions for that which service now has and we using as well so we also have that of course you know number one you need to do defining what you're actually looking for and then you go out and do a collection of the data I mentioned a few minutes ago there is a little bit of a danger in focusing too much on the current state because that you you need to be reasonable in what you go out and discover you can literally just continue for years in digging into the lowest level of details of your current state and so on because it is an everchanging environment you will never be finished but you need to bring in enough of your current state that it's you have a valid enough data quality of your current state that you can start doing the next step which is exactly saying okay so what is the changes I need to do what is the business requirement we have do we have any new services do we have any new products do I have any new processes I need to run and support basically by my applications do I have any new business capabilities is what we do in the organization maybe organization is doing something new maybe you need to support that and you need to have applications in the background do you have an application that provides that functionality in order to deliver that capability and if you don't have that what do we put in place when do we put it in place or you do the reverse right do I have something do I have a process we're not running anymore do I have a capability we don't do anymore yeah well I'm in a bank cloud or I'm in healthcare or pharmaceutical and we're not doing this next year we're moving on to new product so that means basically a certain capability we provided uh processes we've been running in order to do that we don't need to do that anymore and that means of course then we can reverse that and then we can look as well in the future I don't need this application anymore because that process which used it is not going to run anymore to basically provide that capability so the future State and the way you typically get in but I'm I know I'm preaching to the choir here because you guys are sitting out there so that's how it works that's based on the requirement that we get from the business and as well from you could say the support functions from it etc etc for what they need to do now once you understand what I have once I understand okay um I will now start you know creating different scenarios for what that capability could be done how are we actually going to do that we could even have different suggestions for different applications we would use right this is exactly where we go in and take number three and we say I I will create create different future States and I'll make a very very simple example for you in when we get to that a little bit further about how that would do but you could have different suggestions for how we would actually provide that capability in the future right and and you know when you talk to a management they're always looking at things like okay do I have the resources do I have the knowhow and what's the timeline to get this implemented does that does that work with the strategy and everything else we're doing and of course what's the cost behind that is that within budget what I need to have so your different future States could of course reflect you know we will have maybe a cheap solution maybe you have an in-house solution maybe you have two or three different suggestions for something that you purchase whatever that is right so the different scenarios you can line them up and then make the management look at the pros and cons for each of the scenarios and make the decision so once they made a decision and says yes clous I love option number two that's exactly what we want to do then we go ahead and create the road map so that's basically looking at where am I today where do I need to go now what did the management decide on what we want to do and then I'm basically doing my road mapap planning for that transformation I need to do in order to get there there are things that need to be shut down there are things that need to be purchased that needs to be added and all of the dependencies that's what we do in the road map planning and then once we have that we go ahead and make the execution a lot of these executions of course are done by projects right because projects Is How We classically Do the transformation execution in our company and then of course you can link that to your future State and we can link that for how strategic important it is etc etc so again just to sum up current state understand what you have create the future State examples based on the requirements that you have from the business do a comparison based on the key parameters that your business is looking for whether that being timeline resources money or even other factors standardization maybe there are certain vendors they don't want to use anymore right so we're standardizing and all going to I don't know the Microsoft or Del stack or service now right as an example do the planning and then of course do the execution and measure that so with that let's have a look here at an example from a healthcare provider I will not go in the details the slides will be provided and can be provided afterward as well um but basically here's an example for instance of a healthcare provider they went into merer acquisition they need to bring up all of their operational data they need to make some plans and some governance around that because it's a merchant acquisition so you know the the the the the the systems they had was really spread everywhere it was not really collected you know in one place so they needed to have here a solution where they could really gather all of that and then create a future state where they're keeping certain systems that they need other systems might be duplx right because in a merger you typically will have different systems or applic ations that goes in and do the same thing which is by the way a very good thing to do rationalizations on look at the functionality of your apps and how many you have that actually provides the same thing um hint hint I can tell you some War stories about companies we work with well oh God don't go there anyway it's a good thing to look at have a look at that about what you know what apps are providing how many are doing the same but then you have the same requirement and they needed of course to have a solution where they had a good overview of the EA landscape as well as impact what's the what's the impact going to be for the change I'm doing for the organization and the rest of the ecosystem and everything that they had there so the values they had is exactly the redundancies this could be the functional redundancies as I spoke about you'll be shocked how many redundancies you actually have in large organizations and yes I know that because I used to work with that and I've done that exercise together with my business partner in the company we work in or our Professional Services team you know what they're doing as well is a lot of these things which edce costs it's kind of a duh right if you talk to management they always want to have the same thing well they typically want to have something better at less cost yeah who doesn't right um but that's another thing but they they they actually achap with this um having everything on a single source of Truth and I I know guys this is a service now series we're doing but come on what service now is is doing is just absolutely fantastic you know how we actually now have a strategic Central source of Truth here for the majority of that information and then when we building this modeling and future State capability on that platform as well without any integration you have all the data available BL me I mean this is come on guys that's just Next Level that's just fantastic holistic of course proactive approach to EA so we have really the overview where we can drill that down again because you know everything's interconnected we can see that we understand the impact of course a modernized ea landscape I think that speaks for itself modeling the new initiative of course to show the future impact and normalization of the data very very important I think a lot of you a lot of companies we work with that normalization itself is just complete nightmare especially when you have a lot of different systems or God you know in the company I used to work with I'll give you an example I became responsible for the application portfolio for free business units and two service units and I was very politically naive I thought yeah yeah okay that's cool I need to create a repository for the APM because I was basically building up I need to understand what we had so what does clous do he invites everyone into a room for two hours and let's discuss how we work with applications what happened in reality is I had a session for two hours with people screaming at each other right because oh no we don't need that data in that that's completely rubbish and what you're talking about is completely I was about to swear I'm not allowed to do that because we're recording but literally I had a screaming contest for two hours and then I went out of the room and said what what in God's name happened here but of course what happened was that everyone was coming from their own perspective I had one business unit was basically specifying an application as a piece of software I had another business unit where cardi was actually working who was actually looking at this from an EA perspective in the right way of specifying an application I have another business unit who looked at applications as Services right everything was Services yeah an application that's a service and then obviously if you have not harmonized that you know you're talking about apples pears and bananas and everything else and then of course you can't really so the first exercise we did was of course to sit down and understand and come to a common understanding what is an app what is a software what is a service and then once you have defined that then we can also go in and say okay what is the basic information we need for an application what do we need and honestly it's very simple right you need a name so and it should be unique and not even that is easy we actually have to have Alias field as well because we had applications where they were running in Russia or they were running in China and they did not have a normal name like well a name in the ISO certification what we used to have they had a Chinese name but you can't put that in your application portfolio because no one understands that unless they're Chinese right so things like that and you need to understand of course what is it doing why do I have these applications if I don't know what they're doing why are they there yeah well class we had them for 10 years I don't care if we don't know what they're doing you know we need to understand for every single app we have what are they doing and then we need to look at you know function redundancy and of course the last thing is you know we we need to have ownership you know in principle guys you should not have assets that no one is is taking accountability for why do you have them I can tell you when I did when I was an IT manager when I had assets that no one took responsibility for you know what I did I turned them off and whoever came screaming into my office because something was not running became by default then the owner then someone is accountable for that specific asset which the company is blindly paying for and we're using resources for so again fundamental thing current state what do we have who's owning that what is it doing and then of course we can start linking it to what it's impacting you know what's it providing what's lying underneath and then we can start the future planning what's going to happen in the future based on the requirement we have and so on anyway long story short normalization of the data of course it's in there and then you need to have a good governance yeah I need to be careful here guys I can talk about that as well because governance guys if you don't have an EA function you need to have a governance in there you need to have an an an architecture governance board where you go in and basically Define these things that everyone is following there there different ways there is a webinar on that as well for those of you who are lucky enough that Architects is recognized by your top level you will have you know a governance board where you can make decisions for those of us who are not not that lucky and we're in an organization where we were not really seen as something that should make decisions we could make recommendations anyway I need to be careful of the time here otherwise I will go on a tangent and talk about that but that's also something of course that these guys did in the healthcare uh with the data how they govern that and of course accuracy and accuracy we talking as well like I think it was 15% of you guys talk about data quality and again data quality as some of you may know is the number one enemy to any EA initiative we're doing because if our data quality is not up to par it doesn't really matter what we show our business and suggest for transformation if people don't trust what they're looking at basically Buck it right so data quality how we govern that that's of course also another webinar I think we've done correctly here Marina I think we've done that we support that as well but that's very important topic but let's keep to the current state and future States we're talking about here so the Second Use case we have here that was exactly that that basic things where we take look we got to have future State planning we got to do future State planning with APM and as you can see on we on the slide here right we we have our current state we understand what's coming in maybe it's manually inputed maybe it's come from a list maybe it's come from your scan data but it's currently what we have and we have the base information in there we know what it's doing people are taking accountability for that so we're starting to have that and then we need to see okay what do we do then when we have suggestions for new models for new elements we want to do a transformation we want to make a suggestion how do we do that and that's exactly when we needed the modeling part in service now which is exactly what I will show you what comes then with the designer so then you can exactly model that you can use all the current state elements relationships and everything else that you have you can make basically I I there different ways to do it the way I like to do it is I use the layer capability um that we have in designer which I will show you which is for those you who ever work with Photoshop it's like you have the different pieces of paper you can put on each other and then you can switch swap around them so you can see different state suggestions for um for what we're doing and what we're suggesting of course modeling the new elements and relationships we can see in the bigger picture how that how that will fit and that of course is part of our strategic planning optimization what we're doing based on the new requirements etc etc and then this is a very cool way where you can actually model and introduce new elements and relationships that is even governed and that's another thing in traditional tools you don't have that governance in there with the governance workflow or even the direct link because it's just shapes and lines in traditional tools here you're basically part of the platform and can always check what you are suggesting whether that actually fits the meta model or the model you have underneath right for your suggestion maybe you want to link something together which is not part of the model right and that's again why you bring that up to the architect board and have a discussion on that if your use case is sound then someone will update the model or maybe there are suggestions to do something else of course we combine that as well with impact analysis this is where we go out when you use the dashboards you use the report capabilities that we have there and then we can understand for the different suggestions we're doing how's that impacting and we can even as I will show you as well put color indicators on this so here are different examples as well for how we actually different examples for what we can do with the designer we have of course things like the capability maps and value diagrams and strategic Maps we can do um I'm not go in a lot of this but I think it the important thing is that you get a feeling for all the different things that we can do with the designer itself uh and how we support different use cases like exactly current state and future States or doing data lineage and understand how everything is interconnected from the top down through the vision Mission the goals the strategies the objectives we have the programs and projects which is doing your executions the impact it has on your capabilities and processes and applications and services etc etc so let me go in and do a live demonstration yes no did not want to show you that and unlocked out that's wonderful okay let just log in again I call these presentation box guys because it always just happens when you present right there you have it anyway what we're looking at here is the designer this is part of the um uh of the service now platform you can see on one of the the the demo instances that I have here it's basically just started up traditionally out here from your application menu so you can see here in that case I have my business applications um and then what I can do here here is of course I have all of the traditional shape libraries and everything else here on the left hand side office ribbons for those of you who don't know the designer that's something that we put in as well don't let the UI kid you um because it is still service now we just created a different UI which is more you know focused on on modeling on the right hand side is exactly where I want to bring in this is where we have the repository browser now the repository browser of the designer is something where we can basically configure and set up to access any table that you have in service now so whether that's you know it it doesn't matter you can basically come whether that's you know standard tables that you get whether that's modules that you're getting whether it's something that you have created yourself in your Enlightenment State and done that in service now you can basically put that in and that grants us direct access to that it's not an integration remember what we're looking at here guys is an embedded part of the solution itself so in this case I will just say all right I have um a canvas here and I want to go into the APM I want to go into my business applications here so I have basically the list of all the different applications that I see and in this case I will just go in and take I have an application called bampo so the bampo are here is actually now a a shape representation which is directly linked automatically to the backend CI element in service now Al in in APM as you see here right so just pulling that in I automatically have a link to it can see all the base information everything that I have here including as well the relationships and other stuff which is related to this specific element and what I can do with that of course is I can just go in and load relationships or reference Fields if I have that so I see there's some reference Fields I have here related list and build herchies but in this case I want to say I want to build really my current state so what what do I have at the moment connected to this specific application and let me just select everything I can see the different types that I have here other applications capabilities is providing information objects which is being consumed by that application processes which is where this application is part of projects probably there's an impact or maybe there's a change going on there software product and Technical capabilities of what the application is providing so let me just load that and as you can see here then I very quickly have an overview I can see the applications capability processes projects and so on which is here um okay so that's basically my current state of where I am I could of course go in here and just go to my templates I have different template types and Footers and everything else I would just use a standard header up here we just put that there so that's basically my uh suggestion for uh um I don't know the the removal or um transformation of bamboo HR for 2024 right then of course I can put description and everything else now another thing I can do here before I move on is I will say I know my manager is very interested in the criticality of the applications what we're doing here so when we talk about criticality we're talking about the business criticality how important it is for business so in that case I will go up to my indicators here I will go to the business application and then all of these are basically fields which I have available on my business applications in this case in My Demo instance on APM so I will just select the criticality field and then I'm telling the designer you know what designer uh color it based on the background color let's just do that so now it went ahead it basically read the different criticality that we have of the applications and you can see it it immediately colored that all right now what I will now do is I will say okay all of this is committed every single element that we're looking at here is in service now we can do a drill in I will just go in and now I will have a look at the layers so the layers remember is what I spoke about earlier this is the preferred way of how I doing it but again guys you have different styles different ways to do it I will show how I trally do it so for the layers you always have a standard layer it's just called a background layer there you have it that's the background layer but in this case I will go ahead and I will just rename that and say that's basically what I would call my current state this is currently what I have in service now now what I will do now is I'll create a new layer and I will call this layer my suggestion a that's my first suggestion so I want in this example to do a transformation where we're moving away from bankar that's what I'm trying to do here and in the first example well I will just go again to my business applications in APM I will just search for HR yeah then I'm getting all the different applications I have here which is basically on HR and I will say let me take Sr by the way this is completely made up right I don't think sap actually has an AR system correct me if that's the case but nevertheless in our world that we have here they do so they came up with a fantastic new HR capability awesome we like sap because it's I don't know why it's fantastic and old and costly and everything but for some reason we like it so it's part of our standard we have in the organization and I'll say no no no we should really move to the sa PHR so let me put that in that is currently an existing element of course that we have in service now now what I can do as well is I will just drag a line between my current bamboo HR and the sap HR and you will see as soon as I do that it basically suddenly my line is blue and it says has Target so what designer has done actively is it actually looked up in the back end of service now it literally looked into a table called the suggested relationship table and it found um basically between two application is a relationship type called has Target so here's another tricky thing if you have multiple relationship types between two classes like applications what you can actually do is I could just go in and right click that say edit data so now I'm in the details of the suggested relation ship remember this relationship doesn't exist in service now it's actually a suggested or future State relationship I'm introducing here but I could go in and actually change that in case it had others right there are other relationship types between business applications that exchange data with or interfaces with of course I can express that and it will just go and read that basically from your relationship type table as well between to business applications again that fits completely with the the data model you have in service now it always relates up to that so in this case I would say stay with has Target I would say yeah ideally we should probably do that at the beginning of the year obviously not the first of January because no one does anything on the first of January I think everyone is watching ski jumping at least in Europe that's what we're doing anyway the second where we are a little bit back mentally that's when we want to do it so I will just say apply and then we have that okay that's my suggestion one I want to bring to my to my management and of course I could color that as well well by other things than criticality maybe that cost information or anything like that then I could just create another cost indicator here and say uh maybe Opex maybe there's some operational expenses let me just get that as a border Ah that's a bit silly as a as a circle here let me just add that as well for the business applications if there is anything that was actually a little bit as you can see that's Now red that means it's holy moly that's is very costly obviously well sap kind of probably makes sense anyway I will leave that I will not touch that topic it's a by the way don't ever make a suggestions to remove sap in your organization unless you want to do political suicide just don't do that because there's always some senior managers who probably were part of implementing it so they will say no no no we need to keep it and who is this guy and we know where you live so just don't do that it's just an example right we love sap remember anyway second suggestion let me do another suggestion here let me go in and just add another layer I will make that my suggestion B and in my suggestion B I know for instance that for some reason in my organization here we have a lot of very smart HR people so my suggestion would actually be why are we not creating our own HR System why are we not using that why should I go out and buy that maybe you even have an architectural principles that says make over buy right so if we can we make it before we go want buy it nevertheless in the example here I will go and say yes I'm now suggesting to do another application you will notice I go on the left hand side so and now go into the standard shape libraries these are shapes that are not connected to any elements they are just shapes but I'm will show you what I can do with them so here's the different shapes I have initiated here yeah I don't want to use that application component I don't know some of you like you use that that's fine in my example here I will just take this one up here business application let me drag that in and I want to say we are building now in-house an alternative to Bamboo HR uh I don't know we want to build Willow HR just to keep on the topic and Willow HR is now a suggested new uh business application that I'm suggesting in my suggestion B the thing is though the designer you notice I just dragged it in as a shape but here's the thing I can now actually go in edit the data of that shape and I can tell the signer you know what the signer this shape here actually belongs to the following table in service now okay so even if you don't commit it at this stage it's just living on your diagram as you have here you can go in and say no no no no designer if I ever commit that it belongs to the business application class or as we saying service now lingo it belongs in the business application APM table okay then the designer knows that awesome and again I can go in here and say I would want to start that on the second of January when we're mentally back and then you can see as well here you can configure and set up as well any field that you have on that specific class in this case a APM business application you can actually then set it up and give it how critical it's going to be it's going to be well it's an ASR system so obviously it's going to be high you will have a riot with torches and everything people don't get their salaries so that's pretty high the user base that's going to use the system is up to 100 people the business unit and again look here I'm I'm actually doing lookups into the service now uh tables so there's a business unit table I'm doing here and for the steward I will just do a look up in the user table right I can even do a look up here and have a look and say yeah who's going to be the steward um I don't know if you're in there Marina let's see uh you are not but Maria is in there so I will put Maria in there she's then the steward in our world that's basically what we call the data Steward the one who is responsible to maintain and validate the data of that specific object different story different webinar nevertheless as you can see you can put that in I will just apply that so now I actually configured that for the business application here and again cool thing notice what happens to my line when I'm connecting it from an existing business application to a future State suggested business application because we already specified to the designer that it potentially belong to the business application table of service now that means when I'm just dragging the line it actually does that conversion again and you can see it actually says has Target and that's aligned to your data model of service now so even if it just exists in your design environment here in your model because you specified which table it belongs to we can still follow the governance that we have around the meta model specifications and everything that we have which is pretty awesome right so in that case you can see we have that that's cool um even coloring if I go again in here and edit that um yeah well I already put that in so I think that's fine so now I have two suggestions very very simple We have basically a current state we have one suggestion here for going to the sap HR and we have another suggestion where we want to build our own and do the willow HR of course you can extend that with other things that's relevant for the use case I will just keep this very very simple for this case here um but as you can see you can drag in anything that's relevant for you for that specific decision now what I will do with this is I will save that I will call that my bamboo uh HR uh suggested transformation trans formation 2024 let me just save that saving saving saving there we are and then I'm going now to the next step so I've created this and now I want to basically bring it in for my management so I will go to the detail of the diagram which looks like this so now we can see the diagram we created here I have a a lot of other information over here can fill out blueprint and category belongs to and so on and so on what we can do of course is we could actually start up here and submit it submit it for an assessment review and that's again the the the the benefit we have of just being embedded with service now the beauty is we can literally just use whatever the capability of functionality the S my platform has which is wonderful so what we can do with that is and what we've done I can just go in for the designer let me just show you we actually have an approval process that looks like this so this is the approval process that I could activate by pressing that button and then it would start that up right as you can see here we the creator of the diagram it will go to the next stage we have a group which is called the contributors which is other people that are creating models as well so then we'll see if that fits the ideas we want to have and then of course you can go up to an assessment group and a committee group in the end who will make the final approval of the transformation and what they want to have so that is something you can activate as I said up here let me just go in recent that's what you activate up here you can also do the other one which is a lot more basic and say look I just need to bring this to my management class there's one guy I need to bring that to him and he'll basically approve whether that's okay or not so in that case what I would do is I would say okay I will now show him this diagram in what we call the presentation mode of the designer the presentation mode of designer is a very very simple uh view where you're basically just seeing the diagram itself why do you do that CLA well I can tell you why we do it because we're corporate guys and we know that if you show too much to your management and typically your management are pretty smart people they will ask you to press all sorts of things which you're not ready really to present and honestly you just need them to see this they don't need to see all the other cool stuff we can do in designer and for the modeling this is what they have and I know for you guys who basically present it on the CX level as well you know that your management typically have two minutes for you before their brains going somewhere else with the next Hot Topic and so on so you better be on key and you better be Shout with your communication to them nevertheless I would show him this and say that's basically my current state as you can see here that's the criticality which I know you're interested in you can see three of them here pretty critical the first suggestion the Mr manager we're doing and again here I have my different layers I will just activate the next layer and say we could actually go in here and we could you know transform that by next year into the sap PHR uh it has of course the downside that is pretty costly so the license to do that is probably going to have an impact nevertheless if that's a strategic decision from the company that's what we're doing money is not an issue they would never say that but let's just say it's within budget right they will do that then maybe they will go ahead and say okay let's do number one but I think my management here will say well CLA what's the alternative and I would say well you know we have this initiative we have a lot of HR people now sitting idle why don't we combine their knowledge with our big development team we have and go ahead and create another future version of that HR which is the vow HR and maybe my man manager saying you know what cloud that's just that's just awesome that's exactly what we spoke about at the management team I want to have that so what I do then of course with this is I go up in the little panel that I have up here for my uh for my read only so my presentation mode I will in this case find the Little Dot over here which is my comment section and I'll make a comment and say management approve the willow HR uh application fantastic and by the way the comment field you have here is available for anyone who can read the diagram right so it's part of our collaboration we have around diagram itself nevertheless I have a decision management decided on the willow HR I will say Thank you Mr management I will leave the room again I will go back onto my my computer my designer will say okay so what's the next step what I can do now if you notice down here at the bottom we have what's called current and what is called future elements and relationships current basically means that they exist within service now in the tables the future means it's a suggested element or relationship that is aligned to the existing tables and metamodel we have there but it still just belongs as part of the diagram so in that case we can say okay my management approved basically here of the willow HR business applications I will just Mark that and I will Mark as well the relationship here between the bambo HR and as well the willow H so now we creating both the CI element and relationship at the same time they have approved that and I will now go ahead and press the commit button by the way there is a role behind that so those of you who have a little bit of security knowledge don't freak out you can control all of this role based but you know it is a demo so I'm showing you here all the belts and whistles that you have of course we have prop governance how can do that I'm an admin on the system so I can do it I have to commit role and I will just go ahead and commit that and then you can see it's committing the element it's committing the relationship and now it's telling me cl that element and that relationship has now been committed and exist in the APM business application and the relationship table as well cool so here's another very cool feature that happens is when you open up the diagram and let me just edit it again so what happens is the designer actually does an active comparison between what you have on your diagram based on the last safe State and the data you have in the service now tables now if there's a difference so if something happened since you last saved the diagram then it will come up with a popup like this and tell you whoa whoa hold on CLA buddy since you last saved this one element and one relationship one is a business application called Willow HR and as well a business application has Target relationship has actually been committed they now exist in service now they didn't the last time you saved the diagram are you interested in Saving another version of the diagram because of course we support versioning of the diagrams and models as well in that case I will say yes please and I have an interesting presentation but there excellent and and you even have a red dotted line between the element and relationship which changed okay so again to sum up use the live data I have in service now basically visualize what you currently have interconnected color it with whatever your Senior Management or decision governance is going to be based on in my case it was just criticality and maybe some operational expenditures but it could be other factors that you can put in and then you can create like with the layers different suggestions send it through an approval process or go into the presentation mode as I did directly with your management make a decision get that documented go in then and commit that and now that exists in service now and to prove my point I can actually click this new element and click the details and will bring me into the form view of that specific element and you can see all the things I need to fill out so maybe you send it to anme subject matter expert who will go in and fill it out for a new object so that's a very simple example of how we're basically working with APM in service now in the design of a current state and as well for the different transition States and everything that we have there and I have just been informed by my Senior Management that I have 10 minutes left thank you Marina for that so just to do a key takeaway and a sum up here so remember 61% of the EA Industries current focus is on the future State planning which is brilliant because we need to go there there are the five steps as you saw earlier we looked at that for the five recommended steps that you need to do when you're doing future State planning um I didn't really have a lot of time to talk about that but obviously if you don't do all of the steps it will have an impact that's clear um but these are the basic five steps that well not only me but a lot of the smart guys that I'm surrounded with um have told me this is the things that we learned for the last I have got 20 years the step basic steps you need to follow model of course the future initiative directly on service now don't use well it's up to you but if you want to be smart why not you know model it directly on service now use your APM you know elements you have that you have it already it's in your organization you have APM why not do your modeling and diagramming and future State planning there as well it just makes common sense at least in my world that's why we created it and of course identify the risk this is something you can do with the indicators the colors based on the mindset of your management right where they are you should color that remember guys you have 2 minutes that's it then the m is going somewhere else so it has to be sharp it has to be clear and give them at least three options uh available for what to do it's another little hint I think we learned in corporate life is don't just give them one but give them give them a selection of something right otherwise they freak out and then they to say no anyway uh easily do of course the future State planning I think what I showed you guys just shows how easy that is and again you already have it you have the DAT on APM combine that and then you have that and you have exactly that single source of Truth for the data and I can see there's a poll that is being pulled up as well with that guys thank you everyone for participating this was a lot of fun uh I hope it made sense I hope it gave you an idea of what we actually do in in service now and how we work with that in relations to um to Future State planning uh was a pleasure uh and hope to talk to you maybe sometime in the future thanks everyone