and it is recording okay good morning good afternoon or good evening depending on where you're calling in from this is I believe our fifth installment of the DPM launch and learn today we're going to be focusing on devops insights um with that we're going to start with a poll and then I will hand it off to one of our product managers ien long but this poll is a little long so I'll give you a couple minutes to fill it let us know if you have any questions sorry I think I ended the poll can you open that back up um oh yes I can that back up give me a second sorry everyone let's try this again let's see relaunching Pole there you go for those of you that already filled it out this should be very quick the second time around look at that boom it's multi select two though [Music] so yeah don't worry you can't you can't fail on this quiz we'll give you all another minute to complete it it's about two minutes to complete the poll um and then we'll end it and get it on just all right and now closing the poll oh what interesting results answers all over the board here um e did you want me to share or did you wanna hop into it um sure I'll I'll get into it just just the looking at the pull results it looks like there's you know we are split across the board some people haven't heard of you know devops change velocity or aren't entitled to it or hearing about insights in DPM as well for the first time and then there's a other kind of side of the Corn that are currently using devops already uh insights as well even insights with DPM so a good mix here um so I will all be you know thank thank you for the customers already using devops I'll do a quick introduction about devops for those who haven't heard about it um but then we'll also Focus on our insights dashboards and then we'll hand it over to Caitlyn uh to go over uh a quick demo with um devops insights in digital portfolio management as well so thank you for filling out that poll uh for those who don't know me my name is Eileen Leong I am a product manager for the service now devops change velocity offering here uh been with service now for about four years uh previously worked at Oracle pivotal which was bought by VMware and then broadcom electric Cloud another devops company IBM so really all over the place a lot of big Enterprise companies and when we look at devops particularly all the companies I worked at and the customers that we have it's usually about scaling devops that makes it difficult for for users um so we'll talk about briefly what our offering is here so devops change velocity was really um an offering from service now that was uh learn from our customers we were seeing our customers going to Great Lengths to customize um their use of change management and trying to make devops work for them uh that that we ended up creating our own devops offering here um and the the pr statement the issues we're solving you know customers generally have these pain points listed here in the slide right where it's tough to just get visibility amongst your devops teams there's friction within change management itself and really hard to govern or audit the devops data that that they have today um and as I walk through uh this feel free to you know put in the comments if there's any questions or feedback along the way uh happy to just you know take as we go as well all right so uh devops change velocity itself we will uh our solution is using the devops data itself to help Drive the automation of change request itself through data driven problem policies uh we connect to different devops tools itself to provide visibility amongst all of that data and then with that data in service now we have the the endtoend traceability for audits uh you can um utilize a core of of itm with the incidents and outages and operational data and now connected all the way through to the devops data as well and so platform owners service now platform owners as well have better insights into uh their devops tools and data without having to go you know bug different people in different departments as well so with devops change velocity um or just in general the in the devops landscape we're seeing you know a shift in the operating models right so there are more and more you know in the past only having centralized teams um with kind of authorita of command of like the different tools you use and whatnot but now there are more and more devops teams that are distributed right and those distributed devops teams are trying to be more agile they're trying to release quickly um they're they're using more you know Cloud native Technologies more forward leaning um they're trying to move fast uh but at the same time uh what there needs to be um from what we're hearing from our customers is there needs to be some sort of right digital contract back to the centralized teams like it's great you're moving fast but we still need to ensure compliance ensure governance um and have auditability for it so if we look at the devops Landscapes and with the tools because there are so many autonomous teams right now right chose their own tools to optimize for their own needs uh the landscape of the tools even within an organization ends up looking pretty fragmented right so there's a lot of times I'm talking to customers and we show the slide and they're like hey those group of logos look exactly like my company right there's just a lot of different logos you're using Jenkins using as your devops jira some teams are using GitHub you know some haven't moved there um and while there's usually an effort to try to consolidate you know it's just not possible or you've made Acquisitions or whatnot that there's just a lot of different tools out there and because of that tool fragmentation there leads to the other challenges right the lack of visibility how do you know you know are there high performing teams or low performing teams what's being released um or time to delivery the the the devops teams the developers trying to work on code push code now they have additional administrative tasks you know how do I fill out the change management forms how do I um let you know other management or leadership know what I'm working on and it it slows them down um having to report all that and uh make sure that they're complying as well and uh the final box there just harder to stay compliance because there's this friction um trying to release fast but uh utilize change management or with change management itself what we're seeing is is a lot of change requests or changes being released that are actually even going undocumented as well so for a lot of customers you know as high as 80% of changes being released aren't actually documented obviously not great for governance or compliance as well whether it's just internal or some teams hav't moved into change management yet or you know they're just releasing bug fixes it becomes pretty tedious to keep track of everything um so with that you know high amount of changes not being documented not obviously not ideal for large Enterprises or customers in regulated Industries right so um this is the the general problem statement that that we're looking at and the pain for the personas is generally spread across multiple different personas here so like I mentioned the developers having you know the additional administrative tasks when they just want to be efficient and en code and release um the VP of appdev or just management leadership trying to figure out you know how are my teams doing what is being released how what is the latest changes really hard for them to get visibility the change management the themselves you know as we moved to being more agile and we're releasing a lot more frequently um even if they are creating all the changes right there's just so many changes now how does a change manager keep up with it how do they even know what's risky and not risky it makes their job also a lot more difficult and then moving further to the right you know governance like I mentioned it's harder to keep track of even operations support you know if there are more incidents or outages how do I tie it back to the correct changes into the correct teams that might have uh released recent code um so providing that traceability of devops data all the way through so now going into our actual devops change uh velocity uh application here so what we do is we integrate with all the devops tools um the secret sauce is really we do that in a passive way right we integrate we're really just collecting data from the tools um and then we normalize it into our own devops data model Within now right so whether you're using um bit bucket for commits or as your devops for commits or G GitHub for commits it doesn't matter it comes into us as a commit if you're using J agile 2.0 it doesn't matter we see them as work items those epics and features coming in and then pipelines as well right Jenkins or Azure devops we we get those pipeline executions so it's a great way to get data in in a normalized fashion so we just know hey these are pipelines that run these are the code commits and whatnot um it doesn't really matter what tools you're using we uh integrate with a lot of uh the majority of major tools out of the box but we also have um Frameworks where you can uh create your own user Integrations as well um if there's something that's not currently supported out of the box so with that uh collecting information for all the different tools we can you know create that digital thread of information right so here's an example in the screenshot of a pipeline execution that runs um before you you know this could be a Jenkins pipeline Azure devop pipeline but at the same time before you reach the prod deployment stage we can pause the pipeline we can automatically create that change request uh with all the appropriate data right so we make the connections of all the the unit test that's run for example or security tests that run the the commits the actual committers the work items and we can all tie that in and evaluate it in change um and wait for approvals before we continue for uh production deployment right so that's um really handy way to you know collect all the data easily view it automatically even approve it automatically before you release the production right so uh we we have out of the box devops change approval policies so with all the data that we get you can create policies around you know code coverage should be above 70% uh you should have these integration or these tests you know obviously not failed they have to be no current outages you can create your own policy and utilize that to help you automatically you know approve and release to production or if not some other combination of you know here's the data and still go through manual approvers if it still seems risky or you know still stop for manual approvals all the time if this a very critical app so there's different you know ways you can utilize the data here and then of course uh he I one quick question came up in the chat that might be useful to talk about in the context of what you were just covering um so the question is from Curtis and it's say he's asking how much impact should be expected if the change process team has customized change management and is not using release management properly gotcha yes thanks Curtis uh good question here we do see that um in general when you're adopting change automation it is a little bit of a journey right people want to step in it because they do have heavily customized change process so we have um different ways you can get started for example if you're currently manually creating change you could um just add devops data to it so not change any of your existing process right not edit p lines and just add the data to it right like select an artifact and we'll automatically pull in all the data um and then you can and then the next step up is can you automatically create the change and and utilize your same workflows um with the data and then beyond that slowly layer in like maybe for certain teams you start to automatically approve and use use different workflows for some teams test that out for like your high performing teams um if that's going well and then slowly expand that out uh but in general there is a little bit of an adoption journey and there's different ways you can step into it uh uh before you go full-blown you know change Automation and change approvals for for your whole entire organization there um but yeah that is something you would have to look at there's change managers themselves you know generally it's a a team effort that you'd have to work with the change manager as your devops teams as well to make sure they understand you know uh the the goal and and what how you're trying to help them and help the development team as well hope that answers your question uh if not feel free to you know come off mute or uh or add more to the chat as well and happy to take more additional questions offline some of these are obviously long conversations depending on your organization as well all right um and uh finally the last screenshot here of course as we're collecting all the data there's different use cases that uh you can you can use the devops data for right that first one being that change automation I talked about right helping your change requests change approvals go faster um and while we're getting all that data we can also show great devops insights as well right so um I'll I'll I'll uh pop into an instance after this to show some of our dashboards here here but uh we you know make all the connections from so when you bring in all the data you make uh kind of different devops applications where you Scope you know planning tools like work items along with coding tools like GitHub and your orchestration tool and because we have that thread between planning coding and orchestration we can give you a lot of great incense right like lead time when you open up a um epic or a story you know what's that time it is from when that story is created to the actual first code commit to all way of it being actually released right not just completed in Juro but actually deployed to production so we have great um metrics and Lead times around different uh areas such such as that um but I'll uh with that go ahead and jump into an instance for a demo any other questions before I move into uh demo portion of insights nothing in the chat I don't know if anybody wants to come up mute and ask a question feel free to interrupt me but I'll keep moving along here uh so this is our devops change workspace I I didn't mention this but us devops change velocity is part of itm pro so if you're an itm Pro user you already have uh devops um so you know if you install devops you would get uh a recommended way to onboard is is through the devops change workspace so I just launched that here with have the devops change workspace this is where you'd come and you connect tools um yeah pretty simple to do so you walk we walk you through it where you know you can connect to a planning tool like I mentioned coding tools orchestration so uh even artifact tools as well so we have aot lot of U tools out of the box um we are expanding our Integrations constantly we uh software quality we connect to like sonar Cube as example for code coverage and whatnot um in August we're releasing our integration with uh the set Ops team as well and we'll leverage a lot of their security tool integration so we'll be adding Vera code support check marks and whatnot out of the box um in the upcoming releases as well so uh you know good visualization of all the different tools that we support out of the box um and then once you connect to them get those web hooks up and running we get the data coming in uh then you can look at our insights module here right so uh this is our our link into uh digital portfolio management as well where we're going to well Caitlyn will show you some of the insights that will surface into there as well um but in devops change workspace we have our insights module um that screenshot of the summary page gives you kind of add a glance look at some of the uh the metrics that that most most customers are looking for including a quick look at hey all the applications with within devops just what is the data coming in for those right the work items commits quick glance at passing percentage right hotel reservation system that application not as great as this Corp site application that's doing really well in their their testing here um and then recent pipeline executions as well um we have a lot of great filters as well so the different applications you create and devops change velocity is your own kind of grouping we do have ties to the cmdb as well and and the ties that we make to the cmdb is is how it uh kind of flows into digital portfolio management potentially other areas in service now as well um but you can create the applications devops applications also tied towards the business app here as well so we have filters if you want to filter by a specific business app your know cmdb or even application Service as well so we have uh different filters like like that um or application product model as well or repo so you can really narrow down and look at you know as as a leader like how are my teams doing um specifically for the teams and uh quick look at the different uh insights uh tabs here that we have um we have a lot of breath right this is meant to really show you like because we are having so much data come into the system we can show you a lot of breath to our insights um customers of course come in and uh customize it add their own but it gives them an idea of like oh this is the data we can can tweak it to make it um relevant to their organization uh but this is the flow metrics tab uh often regarded as like value stream metrics the you want to see the flow of work moving through your system right can I see you know how how long it generally things stay work in progress my last releases is it all bugs or am I releasing some stories and epics right getting an idea of some of that distribution how long does it take when you plan something to actually getting it released right um a lot of days for some of these tasks here but it gives you an idea and then what's currently work in progress on these days right is it is it bugs features task and whatnot and then you can of course uh also even filter by I just want to look at epics at a higher level and do that as well um and then it defaults to you know last 30 days on most but of course you can come and easily change the date range to to what you want as well uh the change acceleration tab this is really for that first use case around automating change automatic uh or accelerating change requests right so you can see the general you know your change request volume you want to see the time to close changes going down obviously you don't want open changes for a long time time that are stalling your devops teams are you automating more or more of the manual um and are you if you're using policies to automatically accept them you know which ones are automatically accepting um which policies maybe keep failing for your devops teams right like maybe code coverage of 90% isn't possible yet and they they just can't make it and it will be a while so you get some little um good metrics here to see how you're moving towards helping with change acceleration even some Roi metrics as well for um determining how many hours you're saving the accelerate metrics are uh the classic Dora metrics right so the famous accelerate uh book um a lot of research has come in where for devop teams it's really these four metrics that determine High performing teams right we have the the development metric right from the time it takes from your first commit for when it releases you you want it to see going down obviously if it's it's going up then um you're not being as agile or there's something slowing down your process how often are you releasing you know not everyone's Facebook of the world releasing several times a day um but of course you you do want to be releasing generally more frequently than not it gives you an idea um and then if you pair that with a couple of the key operational metrics right the development metrics Dev Ops Dev Plus props you've got you know how are you doing for mttr for incidents is a change failure rate when you release um is that going well as well so if you have kind of looking at these four um if they're they're all pretty good that gives you a pretty good confidence level in in a specific app or specific service or that that team as well and then uh quality metrics here um we bring in from from sonar Cube and like I mentioned you know different security tools as well you can easily also the policies around like I mentioned code coverage Test passing percentage even vulnerabilities no zero critical vulnerabilities or whatnot and and just overall bug counts there um that's probably the era that we see the most um uh breath in in terms of insights of of customers coming in and wanting to drill in and more around around the vulnerabilities uh customizations there and then development um we have a lot of information coming from those coding Tools around the committers and and and and in their uh in their commits as well um and then operational stability we do have that tie in right to the the overall itsm ecosystem through through through the application service around the incidents and outages and service availability we can even bring in error budgets as well I don't have it here in this one um but if you install like uh SRM as well you'll bring in the error budget data as well so good breath and uh um data across essentially the entire life cycle of of uh software development here all right all right with that I gave you a really quick Whirlwind tour of you know our devops change velocity offering a look into our out ofthe box dashboards here um there's no questions I'll go ahead and pass it off to uh Kaitlyn now for digital portfolio management and how we uh work together there awesome thanks Eileen all right I'm gonna go ahead and share my screen so hope that was a a kind of a good background or additional context for anybody who isn't quite as familiar with devops or a good refresher if you are or maybe you learned something new um so one of the things right with DPM is we're solving for a particular Persona and this is a refresher slide the solution owner again solution being more of an archetype that represents somebody who might call thems a service owner Service delivery Manager application owner um you know or even a product manager uh somebody who owns something through the end-to-end life cycle and so they really do they really are interested in their build activities and some of those additional Ops run metrics and we saw a really natural Gap that from the solutions that we were providing and an opportunity working with the devops team to fill some of those those gaps that we were seeing so when we look at our problem statement solving for the solution owner one of the things that they do is they create that prioritized road map and they have to prioritize what they work on so um like Eileen was showing there's some key metrics around um how long things take to complete what the team is delivering and the amount of work that a team can take on at a given time and we didn't have that visibility without devops and so that was a key problem that we wanted to solve and we found a really nice solution working with that data that we had available the other side is assessing team performance so they really have to understand um how well their team is delivering and where they need to improve so they lack Insight uh into deployment frequency um how quickly the teams are restoring from when an incident is caused by a change and then also frequently the changes are failing so um again with this with eileene talked about the challenge of having all these disperate tools teams working in all these different places owners just really didn't have that visibility they didn't have that easy quick access to that information and so it creates a lot of blind spots and it hinders their ability to improve their team performance um and again we we identified that using and working with the devops data we could start to solve some of those and really focus on bringing those specific insights into DPM um and so what we did was as Eileen mentioned there's so much data that we could look at and pull in and and the number of filters that devops provides gives so much flexibility so that the the owner can really go in and and tweak and tailor what they want but what we can do in DPM is we can give them a really good starting point and give them more of the holistic picture in the context of other data that we can Surface so we didn't want to recreate the insights workspace or dashboard that devops has but we wanted to curate the information pull in some of those key stats and and really tailor the visualization in a way that we thought would benefit the owner and then if they needed more information we could link them back into the devops insights workspace so that they could adjust the filters um see different uh uh data types beyond what we're giving them again at that like first pass high level um so these are some of the key design challenges that we uh worked together to to tackle um and and where we ultimately focused our attention for this first kind of pass at how we solve for the the solution owner in DPM leveraging that key devops data okay so I'm going to do a quick KAIT you have a a question in chat Curtis asked do change scorecards Factor in or provide input into those uh not at the moment or ien I don't know I'm actually not super familiar with the change scorecard yeah some uh not out of the box for any of the insights as well some people you know will use change like score success scores in terms of you know part of their like change approval policies or whatnot but currently no out of the box widgets for those okay thanks yeah I didn't think so but I I wasn't entirely positive so I'm getting an instance up here um you'll have to bear with me a little bit so we had an instant snafu and um so this is not a typical demo instance that we use um but it will give you a good view into um the widgets that we surface the type of data and then how we link into the devops workspace and then I'll also show you how we've set it up so that you can kind of turn on specific devops metrics that you want that we ship out of box um or if you're not ready they don't they're not available for you so there is some configurability that we provide in our system properties I'm going to go ahead into the the DPM workspace um and one of the main places that we started with with the devops data is on the business application so focusing on um pulling in that key build uh like the the key flow metrics and particular for um the business applications and then also the accelerate metrics so those are the two tabs if you remember alen was showing in the insights that's what we are surfacing or focusing on um in in DPM for the business application Level um so you can see here on the build tab this is where we're highlighting those key flow metrics and again they're all around um how the team is delivering and what they're working on and so um what we wanted to do was look at a specific work item type so there was a ton of different types and a lot of different uh levels that an owner can look at in devops what we wanted to do at this level was really focus on Epic and Feature work in terms of that flow time and then again if they need more details they want to look at story flow time things like that they can they can launch into the the devops insights and get that level but we did Focus for average flow time really on that epic and feature level and then looking at distribution of work so is the team more focused on stories or bugs and how is that evolving over the past few months so um you can see here really clearly that distribution and the average over the last 30 days um so we're giving the owner insights into where then they may need to uh reprioritize their road map so for example if they've been focusing a ton on story work the defects might be piling up and they'll need to adjust that road map to focus more on on bug work potentially and then we also wanted to show work in progress cycle time so that um the owner can get a sense on on how long things are taking and I'm again I'm sorry for the data that it's looking the same it won't be the same um but you can see the first one is for epics um the second one is for stories uh last 30 days and then the third one is for um bugs if I can get that to show up last 30 days and then we show the work in progress items right in context so here you can compare or the owner can compare how long does something typically take in work in progress and how many can the team then cover at the same time um and and they can use that data again to create those road maps that are pretty accurate um and again kind of make adjustments as more data is coming in for them and then below the flow metrics we surface uh two key accelerate metrics and the reason we're putting these on the build tab is it's more related to build activities we surface two additional accelerate metrics On The Run tab and I'll show you that in a second um so here we're looking at the commit to deploy lead time and then also the average deployment or the the deployment frequency we give the average for the last 30 days and then we give a really nice um time series so then the owner can assess how this data is evolving and changing over over time and then if we go to the the Run tab we have uh these two additional acceler metrics so it's the meantime to restore from an incident caused by change so how quickly are the teams addressing those incidents um and then the change failure rate so this is telling you like how often they're changing or they're often they're failing I'm sorry I and I apologize the data isn't um isn't updated again this instance is is a little funky right now but you can see the the type of metrics that we're surfacing the really cool thing is that in addition to the devops change metrics we also show you this data for the non devops changes so it's represented as other unfortunately we we couldn't control the label on that one so it's a little maybe confusing but it's it's basically any non- devops change so your typical changes so any um incident caused by a change um what's the meantime to restore we give you that and you can compare your devops changes to your non- devops changes um and ideally right you should see improvements with your devops changes um just because you can improve that velocity um and then I'll show you when you when you link into devops so this is specifically accelerate so we'll take you to the accelerate Tab and we filter the um data to the business application that the user came from so they'll see all those metrics with that specific filter applied and then they can uh adjust the filters as needed um depending on what time period they want to see or what specific you know uh apps or combination of apps that they want to look at and again our data was had dropped off so this is showing no data available because there was zeros recently in the last 30 days maybe I can show the flow metrics instead um let me go back that was not a good example let's see here okay well this will normally show you the correct charts and then you can actually drill down to get to the source records um so that's also nice for the owner to it's like Progressive Deep dive um into those those data points and I'm sorry I'm not sure why um the data isn't working in this instance but um I hope at least that that gives an idea of the specific metrics the reason why we pulled in these particular ones and the the filters that we apply for the owner in the context of DPM and then the idea is that they can they can get to that very granular level of detail if they're interested in the devops workspace um the other thing I wanted to show is when you go into digital portfolio management um again as an admin we have this Administration section we covered this in a previous session um but we do have these properties the devops properties so this will become available when devops is installed so if you've installed the devops plugins on your instance this is available and by default it will not be enabled you can then choose to enable those metrics in DPM by checking the box and saving and then when we when the property is enabled we want to optimize the page the the business application Pages for the devops data so what we do is we show the flow metrics on the build tab um and we show the accelerate metrics so we'll give you all those that we just showed you they are uh treated as like separate sections so you can hide the flow metrics for example or you could hide specific accelerate metrics on the build and the Run depending on what you want to use or what you're ready to use um and then what we also do is we hide the agile 2.0 data from the build tab so that includes the epics stories releases and Sprints sections you can always reshow them but the reason we do that is agile is considered an integration with devops so that data will be shown um in those in those widgets and we didn't want there to be an obvious discrepancy between the data um so again you can you can show them if you want but we will we'll hide that um as part of that optimization for devops um and then uh you can always hide and show so there's no restriction around making those updates if we go to the business application page then here you'll be able to see the different content configurations so the as I mentioned the epics stories releases and Sprints these will all be hidden you can reshow them once that's activated and then with the devops um you can hide those specific sections depending on what you want to use and what you're ready for um so that's how you can and I'm in the wrong um I'm in the wrong scope but if I click here this will become editable so you can make those adjustments if needed um once that's enabled okay let's see I see a question from Mike um ah I see the apps are Serv yeah so that's something that we've talked about um providing this also on the app service level one of the things you probably noticed is for the app service we only have the Run tab and the reason is that when we talk to the um csdm Team they'll tell you that the business app is where you're supposed to do all your plan and your build and then the run really should be based on the app services so all the app service data is shown on the business application Run tab and then thus the applic ation service is more of that like instantiation of the business app itself but the more that we talk to customers the more that we actually hear this feedback that no a lot of that actual build is happening on specific app services and so surfacing build and run tabs for the app service um is being requested and so that's something that's in our in our backlog and something we want to bring in once we introduce those tabs and more of that full end to- end life cycle what we'd like to do is provide those same metrics just filtered at the at the app service level um you know related to the devop so then you could see again okay here's my business app level here are the app services and how that you know data is kind of uh related and rolled up so that is something that that we're looking at um you know coming down the pike but if anybody else is is on the call and can has any thoughts about that having the the full life cycle on the app service if if that makes Mak sense to you and if that's something that you're looking for please do let us know because it helps us prioritize our road map in terms of what uh folks are looking for um you know and what you're what you're ready for yeah and Caitlyn maybe in the csdm documentation too um because I I thought I've seen somewhere where they do show those those different iterations of the you know you have Dev you know you have Dev uh test and and production and it seemed to show that at the application service level which would make sense where that life cycle would be um so maybe there's some clarification within the csdm if that's a a case at the business app too just that we're foggy and we're we're we're just stepping all over each other in the csdm between the business app and the app service kind of making it like for like and if we do that why is it the same so maybe some clarification either specifically where we're not getting it or maybe there's clarification within the csdn documentation that can help with that yeah that's a good point I mean the the csdm is clear as mud right it takes uh it takes quite a bit of time and energy and at least for me to to fully wrap my head around it and then it doesn't help that it keeps changing so um yeah It's Tricky but we we do I think we it makes sense to to bring it in at least based on some of the feedback that we've been getting um so that is a gap that we have and and one thing that that we're we're working on addressing soon and then we can bring some of those particular insights and data at the app service level which I think will will go a long way for folks are there any questions related to this topic or for Eileen for myself um was this helpful did it make sense did it add more confusion um okay I think that's that's also typical Cassandra where again as f as people are as customers are learning about the csdm and getting things registered in the cmdb um you know everybody kind of comes at this at different levels and in different ways so um that makes sense GPM has it DPM has its ties into everything right it just opens up a lot more because what do we do I mean I see you can see that you can look at the life cycle of the product and then the the business application and then okay the app service so um I guess it's opening up for anyone to find their path to be able to do that but then I see oh what's the next thing right are you going to bring that strategic portfolio management in that where you have a you know pipeline based on the the road map that's there so um yeah I mean love that we have the whole visibility there and to find your little your your little uh your path to continue on all the all the paths are available and to find our path for it to make sense um I guess is where we where we struggle and find our way but also makes it exciting yeah we do we want to make DPM something that can be used used um by anyone you know at in any phase of the csdm adoption um or depending on what you're using and how you're using it so you know of course that's a work in progress for us too to to try to make it more flexible and dynamic and pulling all the different data points and everybody does it a little different and everyone has a little bit of a different um need so to speak so that's been a fun challenge for us but um yeah we're pretty excited about the stuff that we have in so far and um eileene mentioned the SE Ops work that's coming with them and so that's something that we've had on our backlog for a while is how we can Surface vulnerabilities and security incidents and things like that um in the context of the solutions and DPM for that owner Persona so um you know that's something that will hopefully be coming lots of lots of exciting things thanks hey Chris just a maybe something you know we have crawl walk run and other aspects of it too and as we dive into this with DPM like our MVP is on availability of offerings right and that rolls up the portfolio and you know that's at the basics of it and that'd be cool to see how people have progressed and where they are from uh you know just to get up and crawl on where that is and maybe there's documentation on all already but uh that'd be cool to to see someone that's at different stages of the journey with us that is good Insight that is actually something we're working on it just it takes a little bit of time for us to design that kind of content but thank you for the Insight are there other kinds of metrics that um people are generally looking for or or want in their dashboards that maybe you haven't seen in DPM or in devops insights or perhaps for the the crawl portion that that Mike mentioned where where uh most people starting with in terms of what kinds of insights they're looking at we have a sleepy group today everybody's in vacation mode already figure out how to serve coffee over Zoom the only thing I'd like to be able to see is a one view like in our dependency mapping that we have out there we have to go I know you guys are working on this but you know we have to look at two different views uh to go from offering all the way up into um the business application so now that we have and we're we're having all this Insight it'd be nice to be able to follow allow us to be able to have that view and the relationships all the way up and see it in one view from the dependency map and other spaces as well as far as uh dashboarding and things like that those that nice view of the relationships all the way through the map you mean yes so you said the the offering linked all the way to the business app yep yep so you can see it from it'd be cool I mean I I'd love to see it from the portfolio the way but yeah from the service offering to the application service we see that but then you have to go to a different view to get from application service up to the uh business application right so I know that's something that you're aware you're aware of but just to tie that whole view across as you guys look at things because we're you know as a digital portfolio we want to see that entire thing and now as you're bringing business application even more into scope that brings that that brings that need even even more relevant okay yeah that's great feedback any other thoughts comments no need to be shy y'all um we can close this early but rather you know use the time we've already have slaugh Mike is carrying the team today yeah thanks Mike you're getting Kudos in the chat as well well I'll ask a question since you guys are since you guys are begging for questions and this might already exist but one thing that's come up internally is just understanding like the consumption of the services um what what is the model to to view like the consumption of the service offerings is that through the service catalog or is there a way to say you know uh I'm not sure how you measure that can you talk a little bit about when you say consumption consumption what you uh are looking for specifically well we might have a little bit of a like a oneoff situation here but um you know internally uh to to my organization we have um several different businesses we provide services to and you know um some companies might consume one offering um versus a different one and so on and so forth and different Services right so we would want to keep track in kind of this digital portfolio who's consuming what services and then that so I I don't know I know that there's something in there to kind of track that um but I think it assigns it to like the user base and last time I looked at that I didn't really like how it did worked but just wondered does that exist or are you when you're saying there's something were you looking at the subscriber model that what you're talking okay that's it yeah so we do have the the subscriber tables that you can use and that's currently the way that we track who the service is being provided to um or like we could say like consumption so one of the way ways that you can do you there's different ways that you could subscribe it does get down to an individual user but you can subscribe by department or you could subscribe by company um uh these tables I've also seen a request for I think it's like subscribe by I want to say maybe an organization or something I'll have to I'll have to double check the exact terminology no we use the company field so that would work um I think what it did though I can't remember specifically but I think when you looked at the digital portfolio interface it showed even if you subscribed to by company I can't remember for sure but I thought it just showed all the employees that were subscribed to it underneath that company uh when you use the company field but I would rather just be able to see the company um yeah so we do have uh we have the way that it's represented is more through the um let me just quickly go to an offering there are and I don't know which has data we'll see they're like little boxes and it'll give you account but it's it's broken out by each of those tabs so it'll be location company um user let me go to the info tab so you should be able to click you should be able to see the companies there okay yes I think that might be different now than it was when I initially looked at it okay but it was in an early version when I was testing this so I see yeah so that's that's a way that we do it now and it seems like that could be something that that you guys use and then um you could use catalog items to see who is actually then requesting things for to the offering U because we do track we we provide some outof boox reporting for um people who are requesting catalog items related to an offering um but then you could also use catalog items to allow people or companies to subscribe to the offering um so there's different ways that we've seen uh people use the catalog item and the subscriber tables but that's that's what we support today for that excellent no great answer thank you for asking your question yes thank you gor very much appreciate it uh we only have one minute left so I'll go ahead and close out for today very quiet group but we do appreciate you joining today and learning a little bit more about devops and its relationship with DPM our next call is going to be on July 12th we'll be focusing on common service data models um as always if you have any questions between now and then feel free to reach out there should be a recap email coming your way then the next let's call it 48 Hours hopefully before you head out for uh the long weekend for those in the AMS and with that thank you all have a great weekend thank you thanks guys bye