Network Supportability

The ability of the customer to sustain the required level of performance (that architected and designed into the network) over the entire life cycle of the network is an area of networking that is often neglected. It is a mistake to assume that a successful network architecture and design meets the requirements only on the day that it is delivered to the customer and that future requirements are the responsibility of the customer.
Experience indicates that 80% of the life cycle costs of a system are the operations and support costs, and only 20% is the cost incurred to develop, acquire, and install it. 

 

Good network architects /designers will take into account the major factors that affect operability and supportability as they make their decisions. Knowledgeable customers will insist that they understand the operations and support implications of a network architecture and design. At times, such issues may be of more concern than the feasibility of a new technology.

The postimplementation phases of a network's life cycle can be broken into three elements: operations, maintenance, and human knowledge. The operations element focuses on ensuring that the network and system are properly operated and managed and that any required maintenance actions are identified. The maintenance element focuses on preventive and corrective maintenance and the parts , tools, plans, and procedures for accomplishing these functions. The human knowledge element is the set of documentation, training, and skilled personnel required to operate and maintain the network and system. Design decisions affect each of these factors and have a direct impact on the ability of the customer to sustain the high level of service originally realized upon implementation of the network.

Failure to consider supportability in the analysis, architecture, and design processes has a number of serious consequences. First, a smart customer, when faced with a network architecture/design that obviously cannot be operated or maintained by his or her organization, will reject the network project or refuse to pay for it. Second, a customer who accepts the architecture/design and subsequent implementation will have inadequate resources to respond to network and system outages, experience unacceptable performance after a period of time, and may suffer adverse effects in his or her operation or business.

 

Other customers will be highly dissatisfied with their networks and either require the architect/designer to return and repair it by providing adequate materials to sustain its required performance level or will prematurely replace it. None of these cases reflects positively on the network architect/designer or implementation team and often lead to finThe scope of requirements for the protocol stack applies to the medium access control (MAC) and Physical Layer (PHY) interface and to the application itself. No attempt is made to mandate that some of the requirements be met in the Network, Transport, or Application layers.