Child Child Figure 11.33 Port inheritance graph. The NE screen is shown in Figure 11.30. With NEs, CCM allows: Querying: including querying of port templates and alarms, while the latter shows alarms which affect the current NE with alarm type, port number, data and time of alarm report, alarm priority and alarm severity. Creation of records: network element records, card records and port records, requiring a slot, card type, card status, and all ports and child ports; it is mandatory to enter the NE type, index, status, in-service date, customer and manufacturer. Modifying and deleting records Creating and applying port templates. Troubleshooting is a large part of the role of any staff at the NOC. Effective troubleshooting is first a matter of drilling down to understand precisely where a problem might be arising. CCM provides this drilldown ability from the NE screen. In particular, the following additional screens can be opened in the context of the NE whose record is currently displayed: alarms which affect an NE port templates adding ports from a template, which requires the name of the port breakdown template, the parent port for the ports in the breakdown template, the port slot number for the card slot on the NE and the child port prefix for the ports that will be created cross connections, which include the circuit name and card port/slots included in the cross connection associated SDH rings. In CCM, the tree structure of ports allows the possibility of parent only, parent and child, child only, or neither parent nor child (a lone node). When defining ports, it is essential to have a mental picture of the tree or hierarchical structure that is appropriate to one's purpose (see Figure 11.33). Whereas the AdventNet product provides the concept of templates for configura- tion tasks, the Clarity product provides templates for defining NEs. In particular, in CCM, a port template can be used to create ports quickly and even automatically. OSS for Telecom Networks TO Port Templates Clarity Port Templates Cre