okay we're at three after the hour uh I'm gonna go ahead and get started um thank you for joining us today we're here to talk about uh application portfolio management and the technology portfolio management function within APM so some of the information we present today uh may have forward-looking statements we're going to talk a little bit about what's coming in the future with uh TPM and APM so as always we have to give you this Safe Harbor notice because we may talk about things but until it's delivered and released there you know there are no guarantees we can tell you what's on the roadmap and what our intentions are but we just it's not a um absolute guarantee that it'll make it so during the session there will be q a please use the Q a uh you'll see a little there's chat then you'll see another thing called q a please use that to ask your questions I got a team of my peers on with me Molly and Scott they're here to answer questions behind the scenes some bigger questions or or questions that you want to answered live they'll present them live at the end of the session so we can do q a and we'll we'll actually have some discussion at the end this session is going to be recorded and it's going to be shared on the servicenow community it takes a few days processing maybe a week and we'll have it up after the session ends if you will you'll be given a little short survey if you wouldn't mind we really appreciate it if you'd fill it out it helps us to build new sessions and do a better job in presenting this kind of information to you so my name is Mark Casto I'm a principal product success manager in the Strategic portfolio Management Group that's the group that builds the APM product and I'm here to help her customers get value and and Achieve New Heights in in their APM implementations our objectives today is to introduce you to the technology portfolio management facilities within APM and so that you can start where you are hopefully you have you know some of the foundational things as an application inventory but how can you build towards uh technology portfolio management what is it in general so that you understand what it is how it works and the idea is to make sure that if you're not ready now you at least conclude on your roadmap to um enable this really valuable capability aligning your Technologies and understanding your obsolescence risk of those Technologies to your application portfolio so the agenda for today is talk about technology portfolio management past and present um and you may not know what we'll be talking about today there's there's been a feature in APM for quite some time for several years now I'll call technology portfolio management just this year in May we had a store release of a new version we're going to cover both versions in this session because both of them are viable one might be better for you depending upon where you are and what facilities you have available to you and we'll talk about all that again our goal is to make sure that you're set up for success with this um we're going to talk about how you evaluate your systems for TPM Discovery success what if you don't have Sam Crow you're going to see one of the the um pieces that we work with APM is really strong about utilizing various other applications on the on the platform what if you don't have Sam Pro that's that's one of the the other applications that we really have strong dependencies on can you do it can you can you implement GPM the short answer is yes you can we're going to show you how you do that today um what's in the future for TPM and then q a so before we get rolling if you would we'd like to understand where you are so um does your company have a technology currency or an obsolescence program this would be a program where you understand what technologies are being used and deployed and you track the vendor life cycles to see if something's out of support out of extended support or at the end of life and you try to take action against it we'd like to understand how you're doing it and we'll just give it a couple of minutes here for the poll where everybody respond okay looks like we've got as many responses as we're going to get um so we are looking at you know a number are just beginning 40 um 20 are using um TPM that's fantastic um some other commercial tools and 27 of you are using um home build systems Excel sharepport SharePoint Etc that's great that's really great um so now on with the show let's talk about how you can use and and what is technology portfolio management so first part of Technology portfolio management and the assumption is is that you have a managed portfolio of business applications in APM one of the next steps in maturity is to take that inventory and begin to align that inventory to the technologies that the these systems Enterprise systems that are in your business application inventory align the technologies that they're comprised of um there's some cases where you don't do this for example SAS although SAS can be represented as a single software so we could talk about how you might represent South SAS but the first part of this is to establish a technology bill of materials and we do it at the deployment layer so you conceptually or rather abstractly you have a business application application Services represent deployments of that business application that's where we capture this information because each deployment can be different and having a different set of Technologies we want to be able to understand that and manage that utilizing a catalog of software Hardware Technologies and publisher manufacturer life cycles this is how we can go about identifying obsolescence and we provide a means to create actions in the form of a business case or specifically a demand in service now so to understand the the function of this from a csdm as hopefully everybody knows csdm is the backbone of APM and here it is in the csdm model we have the business application we have the application service that's that deployment of a business application and then down here product models product models are what we associate at the application service level um to represent the technologies that are in use and it's both hardware and software so it's not software tends to get more focused but we also do Hardware so the original TPM use software models our new TPM we're taking a different approach we're going to look into that in the case where you have available Sam Pro Discovery and service mapping working together you have the opportunity to automate this think of it as TPM Discovery so we it can't do every single bit of it but what if you could get 70 80 percent of your applications aligned to their Technologies utilizing the information that's already there again power of the platform so the full automation story how would that automation work we start with discovery that finds that horizontal cmdb population of sea eyes the infrastructure CIS so Discovery as it identifies and adds Hardware software CIS and cndb in APM we have our inventory of business applications and in between we create our application Services we use service mapping to associate that discovered CI discovered infrastructure we map it to the deployments of the application so we understand what is this infrastructure serving this database This Server these routers are forming a network that these servers are tied to all of these we understand these dependencies by using service mapping and that rolls in that manner we roll up to the application portfolio the alignment to the actual physical world the physical construction of of these applications Services these deployments at the same time software Asset Management Hardware Asset Management are working with Discovery as this discovery goes through the software Discovery phase it identifies the software also identifies the hardware models that identifies the software installed on servers and that gets normalized we then utilize TPM through the product models the product software products we utilize that to create this alignment create this this technology Bill and materials and then we use demands in SPM if you have full SP and you can use products have projects epics Etc as well to to drive activity so why a new TPM we've spent the last couple of years with a large number of customers implementing TPM and as we worked with these customers and help them we've we've seen some themes that called for a need for for a new and stronger product um first off we wanted to be able to introduce full automation we want to have a job running in the background that just maintains as much of this information as we possibly can and this is again this is where Discovery service mapping and Sam Pro are available there are possibilities again that we'll talk about towards the end of what you could populate if you have other systems for Asset Management um and and we can describe the tables that have to be populated so there's a possibility of doing it without these facilities but of course why wouldn't you want to do it all on the same platform it's efficient it's powerful to have that we wanted to improve our performance we wanted to find audit capabilities from life cycle determination is not exact match so understanding and compiling the vendor life cycles for thousands of products is a gargantuan task it is a huge challenge our Content Library provides it but even so we still are not able to capture every single life cycle we have a mechanism so that we can update the life cycles and maintain the Content Library but every day there's new systems there's new versions released all of this stuff has to be kept up to date and So within the new TPM and even with old TPM now if you've updated you will get the capabilities where we use heuristics to try to find a better match for life cycles we're going to talk about this a little later um but understand we need to use these heuristics we want to be able to provide an audit capability so you can understand that we didn't find an exact match but here's the best life cycle we could find also we needed support the new EA workspace and the next experience UI in these things so differences between the new TPM and the original TPM the new one no longer uses software models so that's crucial there's some some reasons behind it mainly is that software models can be versionless and what we're concerned with here requires unequivocally that we speak of versions of software so inversionless software model causes this huge problems there are some solutions using the full version but it's just caused too many difficulties so now we're using the software Discovery models that come from the normalization and again we're going to look at this in detail in a moment though we're using those software Discovery models which are normalized they're first step in normalization of installed software on the servers life cycle dates are cashed so rather than query you know real time when we try to render them for you we're going to aquarium uh at the time that we do the discovery job we cash them so when you go to display it or make some sort of analysis it's cached in the table that's maintained but it's cached so it's very fast we wanted to improve the performance um we use Association of software product to better support alignment with technology reference model trm we're going to have a session later on this summer about trm so stay in touch with us for that but technology reference model real short is that's where you identify your technology standards and one of the key things that it does is it uses software products versus the software versions it actually uses both again we'll have a PRM session talk about that we also maintain the server installation information this was a key missing element that we were told about as we worked with other customers implementing TPM we identify the technology and it's Associated to a business application application service but what server was it installed on well we don't know we threw that information away as we did our processing now we keep it it's right there you can work with it you can you can make to-do lists or changes and you can specifically identify the servers that need to have an upgrade Etc and we associate everything in the previous version we would make suggestions and you had to go pick which one's applied now we've taken the reverse action and this was under uh you know advisement from customers that said I'd rather have a list of too much than a list of nothing because somebody didn't go in there and do their analysis so now we apply everything and then it's the it owner's job to go narrow down that list and remove any technologies that are not applicable so we're taking an opposite approach to that currently it's not well suited for Sam customers but there is there is new development coming that is going to make it much simpler and we will easily support non-software Asset Management customers it does not recognize CI relationships this is really critical your application Services need to be mapped that does not mean that they have to be top down mapped traditional top-down service mapping is difficult and it can take quite a bit of time there are multiple methods for doing service mapping tag base Dynamic CI Dynamic application service which basically takes those CI relationships and creates the proper mapping records again we're going to look at the data models so that you better understand this but don't take that as a serious impediment because every application Service as soon as you can get there should have at least some rudimentary Association in service mapping that's how our system works the best if you want to use incidents suggested or the incident impacted Services you need to have mapped application services to do that so it's pretty critical not just for this but it's for other facilities as you work across the platform can you still use the original yes you could use them both at the same time the original is not going to be updated we're going to put all of our our work and and everything into the new version but the original is still out there um and we'll see some key visual differences when we get into the demonstration we're going to do live demonstration on this today so the new APM technology data model quite similar to what we had before [Music] we start with a business application business applications have one or more application services and we talked about service mapping here's the table that's key service CI Association so the service CI Association is a table when you do service mapping it's a nice flat table that lists everything that's associated to a particular service we just simply look in this table for the servers I'd say infrastructure CI is here really this is this is servers that we're looking for so we get the servers off of anything that is a computer type so servers are computers uh laptops are computers and we're probably not going to find laptops but servers Windows servers are servers Linux servers are servers servers are computers so we start at the computer level we've looked for the software installations those software installations are normalized into the software Discovery Model at the computer at the hardware level there's already a Association if you have Hardware Asset Management there will already be an association to the hardware model so we pick that up we take that information that's discovered uh software Discovery Model which has a normalized version of the publisher the product the version that was found the Edition and we use that information to create a TPM discovered technology record upon the creation of that record it takes the information and creates a TPM livestock technology life cycle this is where we go grab the appropriate life cycles that we cash them those are tied to software product and essentially tied back we would take the version specific life cycles and we cast the dates back over here so ga they in the support Day end of extended support and end of life we have those all readily available and our analysis lets you identify risks by looking at any one of the in the support extended support or noi the original semi-automation model and so the original model we'll look at it in demonstration there's a button called manage Technologies uh managed technology models of the business application and you could go use that pick an app service tell it to fetch it's software models and it would basically go do a similar analysis and it would create a list of suggestions that we see here so start off business application pick an app service it depending upon what kind of app service it would either use that CI Association table or it would crawl the relationships the CI relationships um and find service from the servers we have software installation Discovery models we use the engine use and API from Sam to find software models and we created a list of suggestion software models the I.T owner the SME that's running it they would then pick which ones should be aligned and there you go you have the app service aligned to various software models and hopefully linking up to life cycles there again there were some issues we'll talk about how that works in a later part so how are software published your lifox Cycles determined so here we are we're talking about it both the original new TPM publish your life cycles or Source from the software product lifecycle table that didn't used to be the case four years ago we changed in the Quebec because there was changes how software asset management work so now what we have to do is we have to run an essentially a query called Sam software Asset Management API in that query we use the publisher that's the the manufacturer we use the software product we use the version we use the addition and we use something called the vert full version that's actually the build number that's used that's found as a part of of discovery and by using those those elements we can form up query and pull in the a set of life cycles includes potentially General availability and the support and of extended support and end of life for the various products manufacturers are all over the place about how they publish life cycles so you may only have GA and Endo support or you might have GA and end of life it just varies Microsoft has a tendency not to publish end of life they publish General availability into support end of extended support but you don't find the end of life so it's just all over the place but we provide you the best that we can and using those elements you can still do your obsolescence you just need to ex you know accept and translate into support that's a bad issue right there even if you're on extended support you you want to be getting off of you want to be banking plans to upgrade that sort of thing so we can provide you with that information so TPM implementation requirements for the implementation of a new TPM as I mentioned it should be fairly low outbreak when we do have certain Expectations first you've got to have an application business inventory cmdb needs to be in place for discovered Hardware computers servers the server computer software installation needs to be populated software Discovery models need to be populated and normalization processes your application Services need to be mapped both to the business application and the infrastructure so this is that service CI Association this is really a key table and if you're evaluating success of the of TPM and using it this is one of the key tables that you want to look at I'll show you how I build views so that you can examine the success of of a particular um you know is there anything to find out there and so we'll talk about that later on an evaluation script actually and just doing it with a view one of the things I'm going to show you today is there's toolkits been posted on the community that has all of this information for you thank you so installing new TPM the original TPM it's installed with APM and so it's it's going to be turned on since you install your APM plugin the new one though is part of a store reading so it's actually embedded as part of the Enterprise architecture workspace by installing architecture workspace you should get it there's actually two plugins so to be certain that you're getting everything download go and request download and install the application portfolio management Enterprise architecture workspace and also activate technology portfolio and management those two things give you the new facility so again we want to review the technology new technology flow so as a foundation we have business application we have our application servers Services their mapped to the infrastructure specifically the servers we have content like in that software products and the version specific life cycles either manual you can do it on an individual business application manually doing this analysis but preferably we've got a job a schedule job and set it up to run once a week um maybe once a month whatever um or you can run it manually and and it'll run it against all business applications that's really the preferred way to do it as we said we wanted to automate everything so the TPM evaluation gets launched by say scheduled job we start with a business application for each application service we get the servers we examine software installations we examine the hardware Discovery models and we create first a TPM discovered technology record which references the software Discovery Model the business application application service the server involved that we were working with and then creation of that record through a business rule creates a TPM technology life cycle what this does it's actually a performance thing because this record gets created by this scripted engine then a business rule takes over and it's asynchronous so it goes out picks up the cash life cycle finishes out the discovery while everything continues on it's pretty efficient it's very very fast so the original let me go back to that just to make sure we've got it all so business application app service get the servers finest software Discovery models as a part of each server we're picking up the hardware model as well and we'll see that when we look at the data in a moment uh and look at it in a live system and then we create discovered technology records paired with a TPM technology life cycle which is our life cycle cash so now the original if you're not ready and don't have the right facilities you want to use the original the way it's sending the automation flow alert is it owner would click manage technology models then when I presented with a list to application services and they select right click and select fetch technology models that starts the the crawl if you will it gets the infrastructure CIS as we saw either via the CI relationship or if it's a discovered or a mapped application service it's going to use that CI Associated table it's then going to look at software installation Discovery models it gets a list of suggested software models and the IT owner the SME running the thing they have to go pick a set of software models and move it over to the application service to software model table that the hardware part of it it just as soon as it finds the server if it's got Hardware it automatically Associates it so that's the original flow so how do you determine is there data available to discover what's you know what's the model to follow and I talked about a couple of things using a I'm going to demonstrate um actually using a database view that I developed as an example um you could to some extent use cmdb Query Builder as well in this case you know the the model is business app app service to infrastructure so I'm skipping how we connect it's either the railcis uh where like that cmdb or LCI so relate CI relationships or it's the service CI associations table software installations software Discovery Model which I'm using a dotted line it's a you know it's by a query that we find the software models the software Discovery Model has a direct reference to the software product software product has references on the version specific life cycles we can use that information there to know so in all cases again we're using a query publisher product version Edition full version is what allows us to pick up the correct life cycles so now we've talked about it quite a bit let's look at it for real let's get into the system and do a little bit of demo so this is a Utah system that I'm using here I'm going to blow it up a little bit so everybody can see and first let's start with the original this was the original application portfolio management home page and you had technology portfolio from here you go to technology portfolio management and what we see here is we see a breakdown we have the business application we have a list of application services by the way I have this P for production turned on so I only see my production app services and then for each application service I see the software models and the hardware models that are associated with it I also see projects and demands and even epics if I had epics Associated to this this business application so in this view it's rather nice I see the software I see the activities that are ongoing I could create a demand to address maybe I've got this red line I've got risk right here I need to do something about it so I can maybe make sure and put a demand in to upgrade SQL Server 2012 Enterprise um the other things that we're showing here is the risk evaluation it's all based off these life cycles these life cycle views are showing us where we have the phases so this phase is end of extended support and Beyond this point it's it's in the life the end of extended support occurred here this thing's in into life here's an end of support so it's kind of yellow the problem leading up to it and here again it's end of extended support on this model so this gives us a nice visual Beyond this though there was you know you're kind of limited on the kind of things you could do you can do one thing that is very nice you can pivot this and look at it by software imagine you find out there's some sort of um some vulnerability on Exchange Server 2016. well who's using that oh I can open it up I pivot I look at it by software and I see what applications are using Exchange Server 2016 or what applications you're using our server 2016. so it gives me a way to look at it from the software side versus looking at it from from just the business application so a pretty powerful view we had some other views here product classification backlogs just going to show us those demands and projects or by sdlc component if you're running your connection from your business application to your application service by sdlc component you would see it I don't have any data in here that would fit that and so I don't get anything back so it's just in my data system so that is the original TPM where we started pretty powerful um but we're missing I if I wanted to know I need to fix glassish Enterprise server uh where do I go find it oh what server is it on I don't I don't know I have to go looking around digging around to go try and figure that out so one of the things we wanted to do is improve that facility here is the Enterprise architecture workspace starts off with a home page view at the very top we have a set of insights the insights are calls to action these are things that you need to know about the insights are extremely configurable it's designed for you to configure the insights you want to see and need to understand one of the key insights that we have here is technology portfolio so this is the new TPM stuff that's in play here so from this I have technology portfolio um insights and perhaps I want to see 12 months out because I'm going to do budget planning for next physical year what applications have got a problem they have some sort of life cycle risk I could view that list here's the list grouped by the application so I see the applications that have a problem I expand it I see where it's installed what server it's on I see the product I see the life cycle dates in question here in the technology life cycle entry I can see the the details of what version so I have all of the information here at my fingertips it's not fancy we don't have nice little lines and all that that is coming that is one of the big features that's coming it's going to be presented here in the EA workspace but we felt it was more important to get something workable out I can export this I can turn it into a list of servers that need an upgrade and attach that list to servers to a to a change and and go Implement a change I can I can actually actually get work done with this I can sort this by the product and filter It Out by products I only want to see the ones that are TV server or Oracle DB or maybe I only want to see ones that are Windows server or SQL Server I can sort these things out and understand them so in some ways this is even more powerful at the front end of this we show you a earliest we call it the earliest life cycle date this is the earliest critical day that's causing you a problem right now causing you risk there may be others but here's the critical date you need to know about and that's the date that we're driving that Insight from so back over here in insights I look at it from the application perspective that's great maybe I just want to see it in more detail at the server side so here's the four servers that got a problem I see the server and I see the software installs on so again I can take action it's just it's just pivoting that same data set that gives me ways to work um in in different ways just depends upon what I need to know maybe I want to know that the app service level Etc here's that software view again I can look at it by the software again start a little bit slow so here's the software for you and I can see all my installations again pretty great view I can export this I can work with it I have export to list export right here you're going to export to Excel and I can really start to work with it take action so new features that are coming new facilities we're going to be able to create demands and some of the things we're talking about is the ability to apply that list add that list to demand actually add some of this information or link it back to a view so the not only do we create a demand but we have the context behind it just while we're here on the the Enterprise architecture workspace I want to have a couple of of pointers here this is just a portfolio of review business application capabilities info objects Etc portfolio Health again all of this is highly configurable here's things that need attention we talked about the life cycles how sometimes you may not get a correct life cycle so one of the things is is the portfolio technology portfolio audited this tells us where we've been we got a full version heuristic match meaning we had the full version but we didn't get a direct match we had to use a heuristic to find a proper in the life for this and so it tells us which technology life cycle which you install basically leads us back to the the installation and the application we're working with so we can approve those and manage those maybe we want to ignore so let's talk a little bit about and by the way here's the all product View so let's talk about how we might execute this so if I go to sorry I've got a little bit of uh slowness I think it's probably competing with the video here so as I go to my business application sort my business application I go to my attendance payroll system application I can run my TPM analysis with the new TPM quite simply right here you see in the upper right I can click the Ellipsis and pick update TPM data that has lost the job behind the scenes to go update those tables that we're looking at but it only does it just for this application if we look over here in the portfolio of in all of our workspaces and servicenow we're putting in these portfolio views basically it gives you links to the tables that you want to work with but one of the things we have here in the technology portfolio management is the logs so here we see where I kicked off that that job the business application was attendance and payroll management and it ran in um like you know one tenth of a of a second so ran pretty quick this one where it's empty this is where the scheduled job is run so if I kick it off there is no business application listed it's doing running against all business applications and so what happens is you could come in here review this log and see if it's running see what percentage it is is completed did it fail and there's an issue Etc so you can work with it there so that's one of the important things that's kind of a Administration facility but it's important to know about when you run this thing so the other way of executing this you'd have to be admin and I am admin so under scheduled jobs system definition schedule jobs if I go and locate the populate TPM discovered Technologies and life cycles I can execute this job or better yet I can set up a schedule for it I'd have to put it in edit mode if I can set up a schedule for it and have this thing run or I could kick it off now because I know some things change that actually started one of those jobs it's going to unfortunately run pretty quick so I don't think we'll catch it in action but we could go back or you try to look at the logs you can just refreshed yeah and uh it ran for what was that less than a second I mean three tenths of the second so that's the new TPM that's the facilities that we have for it again it's growing we're going to have a gambling we're going to have more risk analysis and more export capabilities you're going to be able to create demands take action type of things before we leave I want to make sure that everybody's enabled on all possibilities so we'll take a look at the original technology portfolio management with it you go to the business application there was no job for it because it's it's 50 manual activity you click the manage technology models here it will show you the application services so in the application services I can fetch product models it's going and I tell it I want both hardware and software and do force a check all the installs basically go back through all the hardware check all the install software it does try to cash in its results so it can be efficient because it could be time consuming um here demo data I'm going to let it just run quickly when it's complete I drill in and I see that I have 30 Associated or suggested software models I see some were ignore because I've run this before there's some are new some were ignored by me previously some are are going to show up as um Association actually none of these have shown up as Associated but I could pick a Windows server and maybe SQL Server standard here and I can now go and Associate them it's going to add to this application service software models so the final thing I wanted to demonstrate for us is under databases and again this is covered in detail in the toolkit up on the community but just to show you how we would use it TPM Discovery view is what I've called this one and basically you see I I skipped the business application but I start with the application service I followed through that service CI Association table I give the computers I look at the installs I look at the discovery models by running this I can see what how much I have out there that's potentially discoverable I have 32 records where I can find something and I see the product is SQL server power bi Etc and I see the display showed me some of the versions um and then I see this one these actually over here will be the um Discovery models so this lets me know what I might expect when I go to run that TPM engine you see there's only 32 records that's why the thing ran in and it wasn't three tenths it was you know three one hundredths of a second so it ran really fast um we've seen it do a two to three thousand business application system probably ran about 30 minutes so it's something you can run overnight to analyze your whole system so that is our live demo hey Mark got a question sure great time for it all right uh can you integrate other EA tool platforms AKA plan view orbis with the Enterprise architecture feature of TPM in other words um I I guess the question what Enterprise architecture like this uh the technology alignment I mean it's all in tables so the short answer is yes you can integrate um you would you know you would have to create some sort of export out of the appropriate tables into those remote systems there are a couple Integrations that that we know of we do know of um one of our competitors that has something similar they're actually using a broken data model they have their data model well and they're they're getting some bad analysis because of that so um but that's not what we're on here about today so short answer is yes you can integrate so um with the demo today that's that's kind of I mean we're at the point for questions so other questions other comments um other things you'd like to know I don't have anything yet in um q a [Music] and you know one thing that did all does come up is you know we have um that slide that has differences you know from the old to the new and we had this setup in our other session about what is the old versus what is the new and I had you know old TPM versus Utah TPM right or I guess I shouldn't say Utah it's probably more uh Tokyo and Utah TPM yeah yeah store TPM and original TPMS there you go yeah yeah so the key difference is we don't use software models yeah we're using the discovery models instead we stopped there and we cache everything some of the features that we've got to implement that are on the roadmap is the ability to manually create records in that data model right now it's designed to work well with Discovery service mapping and Sam Pro and pull that information in but if you want to do it manually you have to go manipulate some ACLS and work with stuff so it's it's a little bit difficult to work with that's something that we're working on for the next release or maybe the fall release there'll be releases in August and in November so we want to be able to support not only um manual energy entry of this because honestly you're going to get 75 maybe 80 percent at best that's how much running in the data center but things like SAS things that are in containers so we don't have a way to examine containers and pull out software versions out of containers right now so those are things that we're going to be working on and improving because we the idea is to make this as automated as possible so if you think about modern CI CD pipelines and how modern infrastructures configuration is done we could read the yaml files we could read container configurations and understand what software is part of that container running in various containers and and look at the maybe kubernetes open shift configuration and figure out hey this is an application here are the pieces that go together that make it up and pull that in we're not there yet that's that's a goal that we want to get to but it's going to take us a year or so to gain that understanding um I will say here now we would love to have design partners that want to work on that because we really need to get some some real world feedback on this stuff on how to do this so um other questions other thoughts um one of the things to talk about would be Integrations so if you don't have sandpro you can populate um you could directly populate that TPM discovered technology and TPM uh life cycle discovered life cycle tables that would be a very simple way of doing integration from some other asset management system um that's that's a possibility we're trying again we're going to be working to improve that for the original TPM the same thing applies you need to populate really just the application service software model table you'll have to create software models and life cycles but you you know you just populate that one app service to software model table so that's how you would do it if you don't have Discovery Sam Pro all of that working one of the other subjects I wanted to touch on is SAS what do you do about SAS oh you got a question Molly I do have one more question so um Sheen or Sean sorry is asking about um you had three options when you went to your business application and then you uh did the manage technology model button yep you had um when you retrieve those logs you had three options and um they're only seeing one for Hardware is that because you have something else installed or what yes that is because you don't have software Asset Management be recognized and uh that same Pro Sam Pro fan Pro yes because it says probably Sound Pro right yeah you gotta have Sam Pro so the hardware could be identified it doesn't require ham grow but this option for here doesn't show up unless you have um the same Pro okay got 12 questions I'm not sure uh Diane you might want to type something in uh you said something about their 12 questions in question and answer um please type something in the Q a to let me know what you're you're wondering yeah well the questions right now have been answered right let them get answered online type answers right there are 12 oh okay um oh um is there another q a tab uh no no I the answers are the ones that I've been answering and I guess maybe that's what you're seeing I'm not sure what you're seeing yeah and Sean I we we one of the things we're working on is removing that dependency on Sam Pro both in trm and and TPM the new TPM doesn't require Sam Pro but it can't do much without sandpro it installs Sam foundation so the tables are there um but it uh you know the original TPM really expected samcro so there was a question Sean you were asking about um cloud services yes it would record recognize virtual machines Cloud servers if you're doing your Cloud servers infrastructure as a service um it can you can get Cloud Discovery to bring your application discovered software it's all about having something that's derived from Hardware that has the installed software but it is dependent upon Discovery doing its job and populating foreign was one um here about you know if I had my business applications and it's from Diane if I had my business applications already uh related to my servers how best to do that uh uh you know and I said to create your application services and have those mapped to your servers and then map the business applications to the app Services exactly that's that's pure csdm so these things won't work if you're not following csdm but the data model is yeah business application and you can see it here in this view you can see business application it consumes application Services those applications services in turn are related by some means now these are using CI relationships but it could be dynamic Ci's it could be dynamic query CIS so there's various options by which an application service can be mapped but that's how it needs to be Associated because it's going to go from the business application to the application service who from the application service that's where it's going to try to find the sea eyes great so here's a list for example of the CIS that are associated to that app service that I was just on so again this this is early on we're looking for feedback we want to improve it the ideas to simplify it as much as we can so um we are around you've got our our identity send us send us your questions I I do encourage you to use um the community I for example um there was something I did want to share with you before we got to that foreign posted this I posted this a couple of days ago actually I posted it yesterday so this is where we'll be gathering not only these recordings but information on implementing both the original TBM and the new TPM so as we gather more information as there's improvements we'll be updating this article up on the community it's under application portfolio management APM articles technology portfolio management getting started and so I've got a copy of this deck that we used I've got various descriptions including a description of how you go about building that that database view for checking your Discovery success so if there's no other questions um we really really appreciate your time today thank you for joining us and um let us know what you find let us know how things go um we would really we'd love to to hear your experiences thanks everyone bye now foreign