|
<< Click to Display Table of Contents >> Information on operational reliability |
Most objects in dpCom have data fields to indicate the risk classification (a code-listed value) and an estimate of the number of active connections (a numeric value) that pass the object. This value can be set manually or calculated by dpCom using the tool show risk classification.
The risk classification code lists (RISK_CLASSIFICATION_CL, one for opto and one for piping) have fields that specify the limits for the number of active connections. For PTS, the following values must be stated:
CODENUM |
CODETEXT |
ACTIVE |
INTERVAL_MIN |
INTERVAL_MAX |
1 |
A |
1 |
200000 |
9999999999 |
2 |
B |
1 |
30000 |
199999 |
3 |
C |
1 |
8000 |
29999 |
4 |
D |
1 |
2000 |
7999 |
5 |
E |
1 |
0 |
1999 |
The nomenclature for different types of objects and equipment does not completely agree between dpCom and PTS. For example, PTS talks about Site and Node as two slightly more abstract concepts. A Node can here either be what normally becomes a node in dpCom, but it can also be a rack or maybe just an ODF and a switch. The code-listed field classification can be used to give an object a more PTS-compliant name.
According to PTS, a Site consists of one or more nodes. A site in dpCom could correspond to a node (eg distribution node) where each rack is a Node. A Site could also be a building with a number of distribution nodes in it.
The solution in dpCom to handle this consists partly of the possibility of using the classification field to indicate, for example, that this distribution node is a Site and that this rack is a Node.
To handle a Site that consists of several Nodes that in dpCom are really nodes, there is a specific object, Siterelation. A siterelation works in the same way as a network relation, ie it can link to a number of other objects.
The object type RSA is for collecting a number of objects (eg wells, cables, switches) that are judged to share an RSA. The RSA object can then use linked documents to access the actual RSA document. If the document link is set to be of type RSA (added to the code list FILE_CATEGORY_CL) then the tool Compilation risk class will list the document.
An RSA document that only applies to a single object can be document linked directly to the object. If this link is set to be of the RSA type, the Risk Class Summary tool will list the document.
Documents for action plan are handled in a similar way as RSA documents. The difference is that the document link type must be Action Plan. Note that the RSA Object Type is also used for action plans.
In dpCom there are three object types for power supply, UPS, transformer and other power supply. These can be placed directly in a node or in a rack.
To indicate what a power supply really supplies, power supply relations are used. Such a relationship links the power supply object with the objects (rack, node, switch…) that are supplied.
DpCom supports two types of redundancy management. The chain tool has support for indicating that two chains are redundant with each other. This then becomes a redundancy at the fiber level.
To specify redundancy at a higher level (for example, redundant nodes, cables or routers) redundancy relationships are used. A redundancy relationship links to two objects that are thus considered to be redundant with each other.
The tool can be started for an individual object, including a parent service, and it can be applied to a number of selected objects. Objects can then be selected in several ways, e.g. Press Ctrl an left-click on a number of objects, select with dialog, search and selection in the Query Tool etc.
The tool then performs an analysis of risk classification by identifying all services that pass through the object. The value of the field "number of active connections" for the services is then summed and presented in the tool as the calculated number of active connections. This value is also used to present an estimated risk classification.
In the event that a service has no value for "number of active connections", a reliable calculation can not be made. This is reported in the tool by entering the number of services that do not have this value. Note that this applies when the value is missing, the value 0 is considered to be a correct value and can for example be used for services that are not active.
The Update Quantity and Update Classification buttons copy the calculated value to the object's own field for active connections and risk classification. This copy is made for the lines where the Update line field is checked. Note that the copying takes place immediately and that the affected objects are thus changed.
It is possible to filter the contents of the tool by, for example, specifying that only rows where the calculated number does not match the existing value should be displayed.
It is also possible to build hierarchies of services. In the calculation of the risk classification, only services that are at the bottom of the hierarchy are included, ie all overarching services are ignored in the calculation.
Calculation also takes place for superior services.
This tool is started from one or more services. The objects displayed in the tool are all objects that can be affected by the service, ie the result of a tracking of the service including all overlying objects.
If the service you start from has overlay services, they will also be included in the list of objects. In addition, all items affected by the overriding services are included in the list.
The tool then works in the same way as the tool Show risk classification. For the service types uplink and capacity, their specific roles in the hierarchy are used to adjust the risk calculations:
•Uplink services – The risk classification includes only services at the bottom of the hierarchy. Higher-level services are ignored, following the same logic as for other services with parent-child relationships.
•Capacity services – The risk classification includes all levels of parent services in the hierarchy. This means that all parent capacity services are summed to provide a complete picture of their impact on the number of active connections.
The purpose of the tool is primarily to smoothly update affected objects when a service is added or changed.
The tool presents a summary of a number of aspects concerning risk classification and operational reliability for a collection of selected objects. The following information is presented (see descriptions of the information under the Information section):
Access: The value of the Classification field.
Designation: The object's ID field.
Function: dpCom's name of the object type.
Geographical location: Coordinates of the object, a point for point objects, start and end for line objects, street address where such is specified.
Risk analysis: A listing of RSA documents as described in the chapter Handling RSA.
Asset class: The value of the Risk classification field.
Reserve power: Listing of power supply objects as described in chapter Handling power supply.
Redundancy: Listing of IDs for objects that are specified to be redundant to the object as described in chapter Managing redundancy.
Risk analysis: A listing of action plan documents as described in chapter Handling an action plan.