Skip to content
ATIS Best Practices

Search

1098 matching practices

NumberBest Practice
13-10-0495Network Operators, Property Managers, and Public Safety should consider pre-arranging contact information and access to restoral information with local power companies.
13-10-0496Network Operators, Property Managers, and Public Safety should consider storing their portable generators at critical sites that are not otherwise equipped with stationary generators.
13-10-0498Network Operators, Property Managers, and Public Safety should consider alternative measures for cooling network equipment facilities (e.g., powering HVAC on generator, deploying mobile HVAC units) in the event of a power outage.
13-10-0501Network Operators, Service Providers, and Public Safety should report problems discovered from their operation of network equipment to the Equipment Supplier whose equipment was found to be the cause of problem.
13-10-0511Network Operators, Service Providers, Equipment Suppliers, and Public Safety should ensure that appropriate operations personnel involved in the direct operation, maintenance, provisioning, security, troubleshooting, repair, and support of network elements are provided periodic training.
13-10-0512Network Operators, Service Providers, Property Managers, and Public Safety should perform periodic inspections of fire and water stops where cable ways pass through floors and walls (e.g., sealing compounds).
13-10-0514Network Operators, Service Providers should when available, utilize a device management architecture that provides a single interface with access to alarms and monitoring information from all critical network elements.
13-10-0517Equipment Suppliers should design network elements and associated network management elements with the combined capability to dynamically handle peak load and overload conditions gracefully and queue or shed traffic as necessary (e.g., flow control).
13-10-0524Network Operators and Service Providers should operate an information-only route database containing the routing advertisement source and cannot be changed by peers, customers, and other users, should be highly secure, and should not affect or impact the actual routing table.
13-10-0526Network Operators and Service Providers should operate a route registry database of all the routes advertised by their network with the source of that advertisement, with which outside entities can communicate with.
13-10-0531Network Operators, Service Providers, and Public Safety should require staff to use grounding straps when working with equipment where appropriate.
13-10-0540Equipment Suppliers should share countermeasures resulting from analysis of an outage with Network Operators and Public Safety using the same equipment.
13-10-0542Equipment Suppliers should include steps to prevent and detect malicious code insertion from Original Equipment Manufacturers (OEMs), contractors, and disgruntled employees.
13-10-0546Network Operators, Service Providers, and Public Safety should consider minimizing single points of failure (SPOF) in paths linking network elements deemed critical to the operations of a network.
13-10-0547Network Operators, Service Providers, and Public Safety should place critical network databases (e.g., directory server, feature server, Service Control Point (SCP)) in a secure environment across distributed locations to provide service assurance (e.g., maintainability, connectivity, security, reliability) consistent with other critical network elements.
13-10-0548Network Operators, Service Providers, and Public Safety should have an internal post mortem process, which engages Equipment Suppliers and other involved parties as appropriate, to complete root cause analysis of major network events with follow-up implementation of corrective and preventive actions to minimize the probability of recurrence.
13-10-0552Equipment Suppliers should perform software fault insertion (including simulating network faults such as massive failures) as a standard part of the development process.
13-10-0553Equipment Suppliers should perform hardware fault insertion testing (including simulating network faults such as massive failures) as a standard part of the development process.
13-10-0554Equipment Suppliers should converge hardware and software fault recovery design processes early in the development cycle.
13-10-0557Equipment Suppliers should take steps to minimize the possibility of having a silent failure on any system component, especially critical components, throughout the life of the product.

Download matching Best Practices

Next results