hi I'm Kevin willamowski Senior principal outbound product manager in the Telecom media and Technology business unit at service now and today I'd like to go over the Telecommunications Network inventory features that that have been released for our xanadoo release pretty much everything we'll talk about today is currently now available in the product but if for some reason we talk about something that's uh futur looking then the Safe Harbor notice does apply please only make purchase decisions based based on what is currently generally available in our products all right so let's take a look at our TNI zanadu features so there are four primary features that have been released with the xanadoo version of TNI the first we'll talk about is uh some updates to our circuit visualization capability uh next we'll talk about some updates that we've made to the planned revisions feature that was introduced in the previous re uh version of TNI we will then talk about uh the inventory model and template import export utility which is a very exciting new feature uh that's being introduced in TNI and then we'll wrap it up with a review of the changes that were made in our equipment rack management user interface so circuit visualization uh what we've done is we've added some capabilities to the uh the pallet where we can uh show the circuit designs and in particular what we've done is we've Incorporated the ability to see a a network circuit in it both its current View and its planned review so if you have a planned revision on a network circuit you can show that circuit on this canvas and you can compare and contrast the current version versus the revised version so just a nice way of uh giving the ability to kind of do stare and compare uh between the two designs we've also introduced topology as part of the ability to represent in the circuits so if you could see in the middle of this diagram there is a an icon that says seattle. Z1 that icon represents a network topology and so now topologies can be incorporated into visual diagrams of your circuits and then finally what we've done is added the ability to identify a protection pack for a logical connection so a lot of network types of connections have primary and secondary or primary and backup paths associated with them and so in the circuit visualization for TNI zanadu we have now introduced the ability to Overlay a protection path on a logical connection diagram the personas uh affected by this new feature are primarily LLY the inventory agent that's the main uh TNI uh Persona this is the typically the user who will be in there um viewing circuits uh and circuit diagrams comparing uh diagrams of circuits uh between each other uh also going in and reviewing logical connections that have planned revisions associated with them as well as verifying that protection paths associated with logical connections are visible and and there for the viewer all right let's take a quick look at the video uh about these changes in the zanadoo release of TNI we've added some new features to our Network diagram circuit visualization capabilities let's take a look the first thing that you'll notice when we go into our logical connections is this overview tab that we've added and that overview tab gives us more detailed information about the connection elements in the circuit so you can see that this particular circuit consists of two connection elements two logical connections but what the overview tab shows us is specifically the design information associated with each end of those logical connections so here's my connection name and my connection end so on the aside that's at this Dallas central Office hub gives me my equipment that it's terminating into if that equipment's in a rack I have that information there as well if we just scroll back this way uh now I've got my port information associated with each end the a end and the Z end of these physical connections and then if there's any additional information like a VLAN ID or an IP address uh or certainly the bandwidth associated with these connections that's all visible in this circuit layout record uh view so that's the first thing that we did the second we did is we created this view connection button which brings you to uh a a screen very similar to how we introduce this feature so this allows you to see these circuits uh if that circuit has underlying connection elements I can drill into it now what you'll notice is that I've got a little clock icon here and what that tells me is that anytime I see that on a on a network connection that tells me that there is a planned revision that is open and active against this so if I wanted to see that revision I can click on this revision button down here and that gives me the ability to toggle between the current View and what the revised view will be and you can see that these plan changes are showing up in green uh and and differentiating themselves from the current view uh of these of these Design Elements so I have that revision view the ability to toggle between that I also have uh a protection path ability so um I can take a look at this particular circuit if this circuit has a protection path that's been identified um we've and added the ability to create a relationship between logical connections where one is the primary and the other is providing redundancy backup so in this case this particular circuit has a protection path associated with it if I look at that I can go in here and see that there's my protection path and this is how it's displayed in The View so plan revision version two let's take a look at the new capabilities that we added to this feature uh we've already talked about a circuit overview page I covered that on the on the circuit visualization um and then the circuit revision history we now allow the ability to keep uh a history of these revisions you can keep them for uh you can keep them archived for up to a year and then you can set it so that uh you can automatically delete them after that uh and then also the ability to uh validate whether your revision has changed from what the original version was so in a lot of cases you may have uh Engineers who are working on a planned revision they'll create the clone of it so they can start working on it but they may not actually get to it for a day or two and in the meantime perhaps somebody behind them has come and made some changes to the original version of that this ability allows the engineer to compare the copy of that version and what they're about to change versus what the original one was so let's take a look at the Persona associated with this again this is the inventory agent um this is the person who's going to be able to see the revision history of a connection uh they're going to be the ones to see the summary of The Logical connections and take a look at that circuit layout record that gives the definition of um the terminating points so the actual Port position where those circuits are terminating and then also the ability to validate a revision against its original to make sure that uh no uh unplanned changes had been already made in the Xanadu release of TNI we've made some updates to the planned revision feature let's take a look at those updates so the first thing we'll do is we'll go into our change models we'll navigate to a new one that we've created called plan revision you'll remember when we ENT introduce this feature we did not have an out-of-the-box change model for this we instead instructed users to use the normal change request and then to manually add the tasks associated with revising your CI and operationalizing it we've now created this out of the box change Fel so I can open that up click save then go to my tasks and see I've got my revised CI task and my operationalized CI task we've also thrown in an uh an additional task as a placeholder to represent perhaps uh work that would be done uh through Field Services management so uh a task could be sent to FSM to have a technician actually dispatched to the field to make these changes that are being done in the revision uh so we provide that out of the box for you it's it's um it's there for you to use if you choose to uh it's not mandatory so uh I'm not going to go through the entire process of creating a revision and operationalizing it but what I will do is show you where some of the new updates have been made so when I select my revision or when I select my CI that I want to be revised I can see that it is gone and it's created uh my up my updated version It's created a clone of that CI that I will then make all my changes to but if we reload this form what you will see is we've got a new UI button here a UI action button called validate revision and the purpose of this is in in an operational uh environment uh it's possible that an engineer will create a revision of a CI and they may be working on it for a day or two before they operationalize those changes and unannounced to them someone could make a change to the original CI so in order to identify if somebody has changed the CI that you're working on we've created this ability to as you put this in select this validate revision if there are no changes that have been made it will say successful if there are changes that have been made to the underlying uh to the original CI then you'll get a notice that there were changes made uh and then instruct you to to review those changes before you proceed uh you can proceed and your changes will overwrite the changes that were made to the original uh but we're at least flagging the fact that there have been changes made so that you can go remediate that if you need to so I've gone in and I've made a change to my revision what I've done is I've gone and I've Chang the bandwidth from 10 gbits to 1 gbit so if we look at our original you'll see that the bandwidth on our original without the V1 is showing 10 gig and if we look at our revision you'll see that that bandwidth has now been changed I'll save those changes and I will operationalize those changes and be right back so I have oper operationalized my changes I have saved that and you can see that on my activity um you can see that my version one has been decommissioned so if we go look at um we'll go look at our version one we'll reload that form and we'll see that now this uh life cycle stage is now end of life and status is retired and if we look at our original and we reload that form you'll see that the change has been made uh from 10 gigb 10 gig to 1 gigabits on the bandwidth so in addition to the validate revision we've also added a system property uh related to valid uh related to planned revisions so I've navigated to the te uh to the system properties and I want to look for uh Network inventory core and then when we see the system properties associated with network inventory core you will see that we have an uh a revision Val ignore fields for logical connections so when we open that what you will what you'll find is the ability to add Fields associated with your logical connections in this case that you do not want compared between the original and the Clone CI there may be fields that you expect to be different like the revision version um or the bandwidth or could be any of the characteristics any fields in that form that you expect to be different and you don't want called out on that validate revision this property allows you to add those fields uh to this system property setting and then those fields will be ignored when you um when you validate your revision so we've also created an archive rule associated with planned revisions so let's go take a look at that if we go to Archive rules and we'll type inventory revision we'll see that there is an inventory revision history archival rule that has now been created cre and when you click on that you'll see that there's already a condition set here and this is basically saying to go ahead and for any planned revisions uh archive those revisions for uh for up to a year uh and then you can also have a setting in here that says you know after after one year automatically delete them as well and then finally if we go back into uh Network inventory workspace let's take a look at that logical connection that we made some changes to and we can go and we can see that there is an inventory revision history related list tab that's now been provided we can click on that we can see uh each of the changes that have been made we can drill into those changes to see um not only what was changed but um you can see the the payloads associated with um the changes that were made that were um sent to the original as well as what that payload looked like like from when you cloned it so you have full uh traceability of what was changed through each revision on a CI and that's uh attached to that CI uh On a related list so that's an overview of the changes that we've included in the plan revision capabilities for TNI Xanadu thank you very much next up let's talk about the inventory model and template Import and Export utility that is now introduced with the TNI Xanadu version uh exciting uh exciting events happening here um so in TNI uh previously in order to create equipment models and templates that had to be done through the UI um for some devices particularly uh highly complex devices the process was a little confusing and a little onerous um to be honest so what we've done is we've uh taken the feedback on on that and we've created a a more familiar Paradigm um perhaps a spreadsheet based Paradigm where a user can capture the information that's required in a spreadsheet template that we provide uh and then have that imported uh into an instance and then also the ability to export your models and templates so that you could move them around to other instances the affected personas here there are two uh the catalog manager certainly that's the person um that is going to be responsible for uh importing the models and also the model relationships um they're also typically the ones that are going to be moving model data from one instance to another and then of course the template manager the template manager is going to be importing templates and related templates from external uh sources and then also moving those templates uh from in one instance to another let's take a look at the feature in the xanadoo release of TNI we have introduced a new way of equipment model and Equipment template management let's take a look at how we originally deal with equipment models and templates the process to create equipment models in TNI is basically that you have to create a model of the device and then a model of the slot of each type of slot that that device has and then a model for the types of cards that occupy those slots and then the models for the network interfaces associated with those cards and for some complex equipment this process was confusing um and a little frustrating sometimes so what we've done is introduced a a familiar Paradigm to this and that is the ability to create these models and their relationships in a in a spreadsheet format and then upload that spreadsheet into TNI and have these models and their cor uh and their corresponding templates automatically created so let's take a look at how we do that first thing that we did was we introduced uh a couple new capabilities on the uh menu here and uh one of them is import models and the other is import templates so in order to access these uh you need to be the Persona inventory catalog manager or inventory template manager but essentially they would come here and uh if you want to import a model uh this is where that would be done uh basically you just click new now if you don't have the spreadsheet already filled out uh you can create this create uh click this create Excel template that's going to create a a file so we'll go open that file up and then you'll see that in this file you've got this essentially the representation of this in this case this is an asr1001 so this is this is a file that we've provided out of the box that provides kind of a guide to how to go ahead and and fill this in and use this to create your own models so you can see from the top here here's my equipment model classes Network equipment uh I've got this entity ID here and then this entity ID will be used as as part of how the system reads this file so eq-1 would basically align with the actual chassis and then you've got uh SL1 SL 2 3 4 5 and each of those is aligned with a slot or the slot model associated with this device same with the cards and same with the interfaces and then the counts associated with them you you would stipulate those in this spreadsheet as well this is the bare uh bare minimum information that you need to create these uh these models but if you look across the top here you'll see that there are other attributes that if you have you can fill these in as well and it will be a more complete template when you uh when you go into TNI so in our situation here just for demonstration purposes let's just say that we're going to create a new equipment model for an ASR 60001 so I'm going to um do a replace so ASR 10001 with ASR 60001 and so now we've gone ahead and made those changes all right and if I save that and then we can go back into TNI now I can go ahead and attach that file so this will be ASR 60001 model attach our file and then we will import it so this is going to give you a status as it's going it's uh going through it's transforming it's loading loading different records and you can see that it is now complete so we'll just refresh the screen and you can see that of that spreadsheet uh a total number of 40 records uh were uh inserted um or or provided of those 40 34 were inserted and six were ignored so if we look at let's go look at our list of equipment models you could see that now we've got an ASR 601 model and when we create that it creates it just as you would have done manually through the UI it's created all the network model relationships it's created all of those subtending child product models and of course made those relationships so that is a quick overview of the equipment model and template uh capabilities that we've added to the TNI xanadoo release thank you very much okay and before moving on this I just wanted to um make one comment on the the example that I gave where I took a spreadsheet um associated with an ASR a different version of that ASR and I changed I just did a replace on the name ASR 101 to 601 obviously in that particular use case uh I'm I'm saying that none of the slot card Port configurations will be different obviously if you're if you're using that sample template to create a totally different device then you'll need to make sure that you that you update it accordingly and that you add the the new models um for each of the rows where you need to um that just changing the name won't necessarily uh change everything underneath it for you all right and then wrapping up this overview of the TNI xanadoo features uh is our equipment rack management UI version two uh so exciting changes that have been introduced on our rack management UI specifically the ability to edit the rack so now you can click on an edit button and then the ability to drag new equipment into that rack um move equipment within the rack uh or Reserve rack unit spaces uh or just remove equipment from the rack totally uh We've also added some power and weight kpi information um and uh created the ability to to add equipment into that rack right from the rack view so let's uh take a look at the personas associated with this this is again the network inventory agent uh this is the person who's going to be viewing those power and weight requirements uh they'll be looking at um the rack configuration figuring out what equipment needs to be there what needs to be removed um and also if any rack units need to be reserved uh this Persona will be doing that as well so let's take a look at the at this feature in the xanadoo version of TNI we've made some updates to the equipment rack visualization so let's go take a look and see what we did so I'm going to go look at a new equipment rack here and what you'll notice right away is that uh We've added a couple different uh metrics along the side here so in addition to the metrics associated with the rack unit availability and how many contiguous avail rack units there are in the rack we've also added a metric for allocated power in the rack as well as the bearable weight of the rack we've also now allowed users to edit uh right from the rack so when we go and we click the edit button we will now go into edit mode and then you'll see that you have uh a list of equipment that's available to you so if an engineer wants to go install new equipment in a rack uh they can do so right from the rack drawing right here and there's a couple different ways to do that the first would be uh to click on the device that you want to add and then click add to the rack and then you'll be presented a little screen that allows you to choose where that equipment can go in the rack based on how many rack units it has and how many available contiguous rack units there are in the rack so you can go ahead and figure out put it in through one rack units one through five and then you'll see that we've got new new equipment here you'll also see that when we make changes to the rack what we're looking at here is uh two versions of the front there's the current existing version of that rack and then as you edit that rack now you're seeing the changes that have been made so you have a a before and after look to see how you're doing uh and what you're doing in the rack the other way of moving equipment into the rack uh is to just go ahead and grab it and bring it over onto the rack and then you can see as I hover over where it can go it shows where it could be installed so those are the changes that we've made to the rack visualization in Xanadu version of TNI thank you very much and just wrapping up this video one thing I also wanted to mention is that uh when you make changes to that rack and then you click save changes that will automatically create a change request and that change request will have change tasks associated with each individual change you made in that rack and that wraps up our TNI xanadoo release overview thank you very much