hi I'm Kevin willamowski Senior outbound product manager in the Telecom media and Technology business unit at service now today I'd like to take you through an overview and demonstration of the features we are releasing for the Telecommunications Network inventory product effective the Washington DC release let's dive in most of the content that we look at today exists uh as of the Washington DC release but if we go over any forward-looking information any product features that are not currently in the product we definitely encourage you to only make purchasing decisions based on what is currently available now in the product so an overview of the new features and enhancements for Telecom Network inventory and the Washington DC release we've got planned revisions uh the ability to create future versions of existing Network designs we are introducing capacity management so a new plug-in that installs with Telecom Network inventory Advanced that allows you to manage the capacity associated with your cards slots ports and Equipment topology visualization uh is now available in network inventory so the ability to create network topologies and then a UI specifically to render those topologies we've also introduced rack management capability a UI that shows the front and back of equipment racks with the ability to drill into those racks to get additional detail on the equipment that's mounted there channelized bandwidths is new with the feat or with the Washington DC release this is the ability to create logical connections that have channelized logical connections associated with them we'll go into the use cases for that we are introducing a new data model to support our ability to manage fiber cables and fiber strands and then we'll wrap up with a workspace re architecture of the network inventory workspace and some of the updates that we've made to that workspace so starting with planned revisions planned revisions allows TNI users to create future versions of existing Network equipment or connections so often when you are planning and building your network you're evolving that over a period of time you may need to take a look at existing network connections today and know that tomorrow those need to change where they're going so planned revisions provides the ability of users of TNI to create cloned versions of existing designs make changes to those designs and then promote those changes to live in the future versions let's take a look at how that works in the Washington DC version of Telecom Network inventory we are introducing a new feature called Planned revisions planned revisions allows users of TNI to take existing Network designs make changes to those designs that are going to reflect a future design what we'll do is we'll go to our change models we'll do a new change request so plan revisions doesn't come with an out-of-the-box change flow because the types of things that you'll do for Planned revisions are going to be a lot of different types of things and there's no way to con there's no way to pull those together into one change flow so the way you'll do that is to create a normal change request and then we'll just add the tasks associated with this revision so I've opened my new change request I'm going to go to my tasks and I'll do a new task and the one I'll choose is called revise CI revised CI is going to take that circuit path and make a copy of it and then all the changes will be done to the copy of this so let's go ahead and add a quick description and we'll save that so now we'll add one more task here and the task type is called operationalize CI so when we operationalize what's going to happen is all the changes that were made to the duplicate Ci or the Clone CI are then going to be taken and applied to our original live version and so that's the operationalizing of those changes so let me finish adding my descriptions and we'll save that so now I've got my change request for my planned revision I have both of my tasks one to um revise and want to operationalize the CI so here is my circuit that I want to make changes to if I look at my connection elements I will see that right now this circuit consists of two things two logical connections uh each of these logical connections are 10 gigabits each and in this example I want to add another 10 gabit connection here to bump this capacity from a 20 gig to 30 gig so to do that let's go ahead and get a copy of this name because we're going to go back into our tasks and so I'm going to give it the CI that I want to make changes to and when we do that and submit you'll see that it is now updated successfully and if we open it you will see that it's now got a V1 for version one attached to it so it's the same circuit that we looked at originally this is just a clone of it and um identified by this version one so now what I can do is I can go back into my connection elements and I will add that capacity so I'm going to add a logical connection I know the logical connection that I want CU I've built this prior to going into my revisions so this 103 I'm going to add and sequence and Route uh on this one I'm going to keep this as a sequence one so all three of these are going to be the same sequence and in this case the third will be route three so we'll save that and now when we go and we look at our ver version one we could see that we've got three connection elements now showing so now I've made my changes so that all looks good I can go ahead and close this so now we'll go back to our change request and we'll operationalize those changes so if we click on our other task here you'll see that I can either put in that CI name that um that I did on the other task uh or what I can do is just put in the change request number and then all of the things that you know that were made that had changes made to them will then be operationalized so in this case let's go ahead and just use the whole change request all right so now when we submit it's now automatically closed and if I take a look at my version one it was in design and build as for my status if we reload that we'll see now that it's been changed to put the end of life and retired all right so and if we go look at our original circuit path you'll see I've got my connection elements here and if we refresh that you'll see that now my original existing path has now been successfully revised and I've added my capacity so that is how planned revisions work in our Telecom Network inventory Washington DC release thank you very much capacity management has been introduced with the Telecom Network inventory Washington release so a framework now ships with the product there's a plug-in that gets installed when you install Network inventory Advanced that plug-in has some tables associated with that that allow you to Define what it is you want to measure capacity on uh allows you to create the functions associated with calculating those capacity measurements and then a metrics table which allows you to see all of the items in your network that have had capacity measured against them Telecom Network inventory for the Washington DC release is introducing a capacity management framework for Network inventory let's dive into that and see what that consists of in the Washington DC version of TNI when you install Network inventory Advance it will automatically install a capacity management plug-in that plugin contains three tables that are used to manage network capacity uh in TNI those tables are definition functions and metrics let's take a look at each the definition table is where you would Define what it is that's being managed for capacity so you can see that out of box we've included several different measurements we've got port capacity available on cards we've got slot capacity available for cards we've got both port and Slot capability or capacity for equipment overall Network Port availability and then we have a couple rack um capacity measurements and slot and subslot availability if we take a look at the capacity for slots and cards you'll see that we have a definition this defines the slot capacity functions for the card entity we've got functions associated with this I'll go into the functions in a second but essentially these are where you define how you're going to measure capacity so in this case the functions being used for this definition are card Max slots and card occupied slots I can also set filter criteria to define specific measurements so in this case where I'm measuring total slot capacity for cards On Any Given device I can actually go in and create a rule to measure capacity for maybe just a particular vendor so I want to measure capacity associated with all of my Cisco cards I can do that so these are definitions for capacity management the next area we'll look at are the functions now as I said functions are where you define the logic used to measure the capacity so keeping with our card slot functions let's take a look at that so when we go into the functions let's edit this record the first thing that will see is uh this function here if we click that there are three different choices to choose from the first is Max second is occupied third is available so basically this is defining what type of calcul do you want to create in this case it's going to show me the maximum number of slots available but I could also uh select just show me the total occupied slots and then show me total available slots in this particular one we're just choosing the max slots and then the strategy there's several strategies that you could use and the strategy is where you define the reference value that's going to be used in Your Capacity measurement so the choices I have here static value is if you you have just a fixed value associated with a device that you want to use in your calculation so I just want to plug in the number 12 because I know 12 is the number of slots I can actually do an aggregate query count this allows me to choose a table that I can go run a query on to determine the value that I want to measure the capacity against I can choose a value field where if I select that it allows me to just choose a table and select a an attribute from that table so if I want to say select the equipment model table and then total rack units available I can select the value from that just by using the value find and then the last one we have here is script and that's the one that we're currently using for calculating the card Max slot capacity and a script will allow you to obviously create a script to further Define the criteria and how you want to measure the capacity so now let's take a look at our metrics table the metrics table includes the measurements that have been calculated associated with all of the items in your network inventory that have had a capacity measured against it so in this case let's go look at equipment slot capacity we'll show those and then specifically let's go look at this particular CI so we saw that that the functions used in calculating the slot capacity for cards were the max available and the Max uh occupied but you could see that there are four different values here and what happens is whenever you provide the values for what the maximum was and what the occupied is it will automatically create the calculations for what's available and then the percentage of usage associated with it so if we go back into Network inventory workspace we can see on our inventory management page some of the widgets that are utilizing these capacity measurements so I've got my rack availability showing me racks with available units so it's calculating those uh Avail rack unit availability as well as maximum contiguous units and Slot availability and Port availability so this is an overview of the capacity management plug-in that is part of network inventory Washington DC release thank you very much the topology visualization UI is new with the Washington DC release of TNI this allows users to render topological Network views on a canvas uh one or more of those views so that you can see how they interact with each other let's take a look at what that feature looks like the network topology viewer is new in the Washington DC release of TNI let's take a look so in network inventory workspace I'm going to navigate to a new uh menu item on the left hand side which is called Network viewer when we click on network viewer that's going to bring us to a canvas where uh we will be able to select different network topologies to render and to look at so I'm going to go take a look at my network topologies I'm going to filter for a couple here let's take a look at this mesh topology so what we what will happen is I'll I'll select the topology when you create a topology a topology is really just a logical collection of network sites network devices and network connections so in this case I've got a topology of a mesh uh type of network so I've got various Network nodes that are interconnected and if I connect if I click on any one of these nodes it will and it will animate the connection line showing the connections from that node to all the other nodes uh I can click on this information button on the right hand side and get access to information about the equipment at these nodes uh just by clicking on uh this device or I can get information on The Logical connections between these devices and nodes uh by clicking directly on the pill I can also go in and show multiple topologies to see how they interact with each other so in this case I want to take a look at a tree topology and how it interacts with my uh mesh topology so in this case I can see I've got three nodes of which uh there are multiple nodes coming off each of those three so if I click again on any of those nodes you'll see uh the animated connections of the the lines that connect from that node to other devices uh I can obviously move these around and resize and reshape as needed uh and then after that I can also um just reset everything to normal I can reset it and re and fit everything to the screen so this is a view of the network topology user interface new for TNI in the Washington DC release rack management UI is new with the Telecom Network inventory Washington release this capability allows users to visually see their equipment racks and the equipment rack units associated with those racks whether those rack units have equipment installed with them or whether those rack units are reserved for other users or whether they're available in the Washington DC release of TNI we've introduced a new equipment rack visualization user interface let's take a look at it so what I'm going to do is I'm in network inventory workspace I'm going to navigate to my equipment holders class so if we click on equipment holders that's going to take us to all of our equipment holders and specifically we want to filter for just the equipment racks so we'll go search for class equals equipment rack all right now I have a list of all of my equipment racks and the one in particular I'm interested in is this demo rack 48 one let's click on that so now we go into our equipment rack user interface and we'll start off with the visual representation of the rack the default view is for both the front and rear view of these racks although I can if I want to select just the front or just the rear but the default is both sides so I can see this is an equipment rack that has been created with 48 rack units in it and then within those rack units I can see where there's equipment mounted so in this case I can see an ASR 9006 is occupying rack units 45 through 48 it's got an status of operational if wanted I can click on that and get additional information on this card right here uh so things like asset information uh expiration of the warranty the serial number maybe the support group or the name of the in uh individual or team that's responsible for this device and then if I need to I can actually drill into this particular piece of equipment and make changes so if we scroll down a bit we can see that uh these rack units uh default to available but you can actually go in and reserve them so a lot of times that's useful so if you're if you're planning to install new equipment at a site a lot of times uh in advance of that you'll want to go and make sure that you've got your rack units saved uh or reserved for you so you can do that as well uh you can uh install equipment so that it's just on the front or just on the rear so you can show the equipment if it's mounted just on the front it will show that if it's mounted just on the back it will show that so in this case I've got a device that's occupying the front rack units 20 and 21 um but on the rear side of that rack I can see I've got different equipment that's in 20 and then nothing in 21 and something else in 22 uh part of the equipment holder class includes uh something called a shelf so you can actually instantiate an equipment holder shelf inside the equipment holder rack and then you can relate uh equipment to that shelf so in this case I've got a shelf but on that shelf I have two devices resting so I've got two Ru uh two two Ru devices uh that are shown resting on this particular shelf so in addition to the rack uh visualization you also have some widgets here uh the top one showing the rack utilization percentage as well as the maximum available contiguous rack units so in this case in this rack I've got uh a maximum of nine that are all together and a total of 19 out of 42 that are being used if there are any change requests or change tasks associated with equipment being installed in this rack the quantity would be uh located here and you could click into those as well and then finally I've got an equipment view that shows the quantity and the type of equipment that's located in this equipment rack so this is a view of the equipment rack um user interface that's new with the TNI Washington DC release channelized bandwidths are new with the toggle Network inventory Washington DC release bandwidth channelization is used in a couple different areas primarily it's used right now for Broadband fiber providers and we use channelized logical connections to allow those users to create network connections that have multiple lambdas or wavelengths on them so you could create one logical connection and have any number of child logical connections associated with that logical connection and those child logical connections can be individual lambdas let's take a look at what that looks like channelized bandwidths for logical connections is a feature that's been introduced for Telecom Network inventory in the Washington DC release channelized bandwidths are used in a couple different scenarios the primary scenario would be for a Broadband fiber provider uh to model logical connections for their dwdm Network so you have network connections that have multiple wavelengths of fiber optic signals going over one circuit and logical connection channelization is used to allow each of those wavelengths its own logical connection as part of that parent logical connection so you could have one fiber circuit that has eight different wavelengths going over it and that's done through logical connection channelization let's see how we do that so if we go into our logical connection models we're going to create two different logical connection models the first we're going to call this Optical multiplexor section so this is a a logical connection model that's going to be used to represent the circuit uh that will carry the channelized bandwidths so you can see my model category is set to logical connection if I scroll down I can see that there is a behavior field here that is set to connection if I look at that you'll see that there's two choices the first is connection the second is channel we're going to use the channel connection uh the channel Behavior to Define our channelized uh logical Connections in just a second and then we also need a reference to our logical interface model and that's been done here that's our Optical Channel interface we'll take a look at that in a second so here's our Optical Channel model this is the model that's going to be used to represent the channelized individual wavelengths on that logical connection circuit so again our model category is logical connection and if we scroll down we can see that this time the behavior is set to channel and The Logical interface model referenced here is our Optical Channel interface and so let's go up and take a look at our Optical Channel interface so this is a network interface model different from The Logical connection models so this is going to be a model for our ports Associated well actually not the ports because these are virtual interfaces so it' be a virtual network interface and when we're setting this uh this Optical Channel interface anytime you're setting the channelization on the model you need to or on the interface model you need to set this flag to Virtual and then you can uh say the port bandwidth for this particular one is going to be one Lambda and so we've got the three models that are used to create these logical connection channels channelized uh circuits the one thing that we're going to do to tie them together is we're going to create these Network model relationships so you can see that on my logical connection model for my circuit I've got two different relationships I've got one relationship that was created uh that's going to assign 48 child lambdas to the circuit and then I've got another relationship that was created for this circuit that's only going to create eight lambdas um or eight channels each for a Lambda or a wavelength so if we drill into the 8 Lambda relationship here you can see that my parent bandwidth is going to be eight lambdas my child bandwidth is one Lambda and it's referencing my Optical multiplexor section model and it's also referencing my child product model my channelized uh logical connection for my Optical channels so if we go back and take a look at some of the circuits that were created using these models they were done using this uh template so I went and I created a 8 Lambda uh om template this is a template that's going to be used when we create a logical connection that has eight Lambda uh eight child channels one for each Lambda and I can see that the related templates associated with this are eight goes from 0 to seven and each of these represents a channel on this on this circuit so let's take a look at one of these logical connections that were created using these models and template so I can see I've got my logical connection and more importantly I can see that if I look at my infrastructure relationships here I've got 1 2 3 4 five six 7 eight child channels and each of these channels is associated with a wavelength now the naming conventions for uh logical connection channels uh is pretty standard it's out of the box um but you can Implement Logic for your naming so that your channels have some indication as to the particular wavelength associated with that channel like we've done here so that's a quick review of logical connection channelization a new feature from TNI in the Washington DC release with tn's Washington release we've updated the data model to include some additional tables that'll allow users to better manage their fiber cables and fiber strands the Washington DC release of Telecom Network inventory has introduced several new classes to the cmdb to support uh updated version of our ability to model fiber optic cables and fiber strands let's take a look at the classes that were added and then we'll go into TNI and see how this looks starting on the right hand side uh we introduced two model classes uh both descending from Enterprise good model and then um originally from product model so we've got a cable model that was introduced out and is available out of the box as well as a strand model extending from the hardware class we created a new class called connection medium and the attributes associated with this class will allow the user to stipulate the equipment on either end that this cable will connect to um or the network site or the interface uh associated with that site as well as the connector type on it uh and then couple uh attributes for the length and the unit of measurement of length from the connection medium class we created two classes called Strand and Cable these are more generic classes um for strands and for cables and then from an industry specific perspective we extended Optical fi optical fiber cable from cable class and optical fiber strand from The Strand class and these two classes are the ones that will be utilized by TNI to store information about fiber cables and fiber strands the use case that we'll go through today um is based on a pretty simple uh view of three Network sites there are two fa two Fiber Optic Cables connecting these three sites so I have one cable that's connecting our Fresno site to a site called LaMore that cable has some number of fiber strands associated with it and then from the LaMore site to the Hanford site I have a SE uh a second cable that also has some Fiber strands associated with it we go into TNI and take a look at what these cables look like and then the strands in them we will see that in our Network inventory workspace we have a class called strands which will show you all of the fiber strands associated with cables in your network and then another class uh that lists your cables so if we look from a cable persp perspective um we can go into this lh01 cable this will show me the SES uh between which this cable runs and more importantly it'll show me uh on this related list tab I've got two strands I can also see those strands showing up in the CI relationships panel here but if we go look at those strands we'll click on that and that will show me that I've got strands three and four uh showing a associated with this cable um the aside termination is actually to to another strand from another cable so strands one and two on that FL cable look like they're spliced to strands three and four so that's pretty interesting so if we go down and look at one of these strands we will see strand three it's terminating on strand one at another site and on the Z side it's it's uh terminating at a fiber distribution panel I can see the cable that's associated with this Strand and then the Strand number associated with this particular strand uh and I can also see that this strand is consumed by a physical connection so this physical connection going from Fresno to Hanford if we can drill into that we will see that this physical connection has two connection elements and those connection elements put them in order are strand one from this f01 cable and then strand three from that second cable so if we go back and look at our diagram we will see the FL cable so that's strand one and you can see strand one is spliced to strand three so what I've done is I've created one physical connection and that physical connection F FR FDF 01 a to hn FDF 01 C has two sequences two connection elements in it and those connection elements are strands one and strands three off their respective cables and again if we go back into TNI we can see that this physical connection has those two strands as part of it this physical connection can then be used by logical connections if needed so this physical connection can be consumed by a logical connection that's providing a higher level service on top of this that's utilizing these fiber strands so that's a quick overview of the fiber optic cable and fiber strand capability that is new with the Washington DC release for TNI thank you and wrapping up the features for the Telecom Network inventory Washington DC release we've also done a little bit of cleanup on our Network inventory workspace and we've done some re architecture there specifically adding some new capabilities uh for capacity management and also a new content tree navigation for your network inventory let's take a look at those in the Washington DC release of Telecom Network inventory we've made some changes to the network inventory workspace let's take a look at those changes we are keeping the original homepage uh and that is widgets associated with site totals um total numbers of sites in maintenance Network sites by status quantities of equipment by categories as well as Network equipment by manufacturer and then Network equipment by state again all of these widgets are configurable in our workspace so this is not changing nor is the original list view of the menu uh for Network inventory workspace so you'll still have your traditional list here of your sites your equipment classes uh and all of the other functions associated with network inventory workspace what we've added are two new options on the left here the first is this network viewer so when you click on that you'll be presented a blank canvas and this will allow you to go in and to choose different network topologies you can choose one or more network topologies uh to visualize and so if I just add a couple of these here I can get all this information I can see how they interact with each other I can click on nodes to get information about the devices in these topologies so this is the first thing that we've done we've added this topology viewer the second thing we've done is we've added this inventory uh option here and this has two tabs associated with it the first tab is the overview and on the overview screen what you're getting is a network wide view of various uh capacity management and quantity statistics of of the devices in your network so equipment by model uh quantities by model equipment by manufacturers then you've got rack unit availability you've got uh capacity measurements to see how many racks are at threshold capacity uh as well as slot and Port availability I can also click on this and go and and pull in individual Network sites to get a view of just the quantities associated with those sites so in this case I've added those three you can see that it's changed my uh my metrics and my widgets on my dashboard here the second uh tab here is the inventory list and the inventory list gives you a Content Tree View and so starting at the location level you can find your location and then drill down in those locations to find uh your network sites so in this case this is my Martin uh location I can drill into into there and see that I've got a central office uh under that under that location and if I drill in I can see the connections associated with the central office as well as the equipment so if I click on my logical connections I will see a list of all of The Logical connections that originate or terminate in this network site as well as physical connections and a list of all of the equipment so these are the changes we've made to the network inventory workspace for the Washington DC release and that wraps up this overview of the Washington DC release features for Telecom Network inventory thank you for watching