#DicasOZmap | Interpreting the Dashboard
If you've ever had trouble understanding the information on the dashboard charts, this tip was made especially for you!
As we will be working with the interpretation of the dashboard, we suggest that you already know the rest of its tools better, so if you still don't have mastery of the subject, just click here and stay inside.
To interpret the graphs correctly, the first thing that needs to be understood is how the “design” tool works:
Basically, the projects button works as a query bank, where all the projects created can be viewed in chronological order, making even the excluded projects available for analysis.
The idea of this tool is that you can make comparisons between projects when they were configured in a certain way and that with that you get statistics on how much your network has evolved over time. Therefore, when performing your analysis, make sure you have selected the correct projects, if you select more than one, the system will always add the data.
Observing the period button it is possible to enter different combinations of dates for analysis, so explore the tool until you find the most suitable date for the interpretation of the data you are looking for, but remember that the longer the period the greater the volume of data that the system will display.
By analyzing the pie charts, they will show the deployment status information for cables, boxes and clients. No matter how long the selected analysis period was, the system will always show the result of the last automatic system update (which occurs every day at midnight):
Now let's talk about column charts separately, note that on the right side of the chart you will have the minimum and maximum reached and the columns expand or decrease according to the evolution of the displayed data.
One of the graphs that uses this model is the Service Port Occupancy graph, which will show two data: the total number of existing ports, taking into account splitters, switches, mergers and connectors that allow connection with the customer and the occupation of these ports according to as time goes by. It is very important to know how to interpret this graph because it can show if the occupancy of the service ports is already reaching the limit.
In the photo below, we can see that, despite a large volume of service ports available, occupancy evolves linearly while the total number of ports increases at the end of the month, indicating a possible network expansion.
In the PON Port Occupancy chart, the system searches for all PONs and calculates the maximum service capacity they have, also displaying the number of customers already connected to these PONs over the course of the days. In the case of the photo below, we can see that the network still has enough service capacity according to the number of clients supported:
Let's check the inline graphs from here, they also show on the right side the minimum and maximum reached and the lines only move if there is any change in the displayed data, otherwise they stay straight.
The first graph deals with the occupancy of cables, it takes into account the levels of cables created, the system will calculate the occupancy through the use of the fibers of each cable, following all the way and bringing the data in percentage form.
The occupancy chart of boxes takes into account the levels of boxes created and all the equipment that allows connection with the customer within it, the system will calculate the occupancy of each level and the result will be displayed as a percentage.
The customer graph will show in a linear fashion how many customers were added to the network and how many were deleted over the days of the chosen analysis period.
The cable chart takes into account the levels created and the length of each one as the dates go by.
The box chart displays the total number of boxes created from each level in the system over the dates.
The pole chart shows the quantity in use and the quantity not used, for the system, a pole in use is one where there is a cable running.
Now that we've talked a little about how to interpret the Dashboard, how about starting to periodically check your network data?