|
Planning is Essential
Having the good luck and opportunity to build over 30 Internet NOCs in my day, from Sprint's first Internet NOC to over 28 Air Force NCCs. The most important thing you can do it to not focus on technology, but move your efforts to the systems architecture view. The time spent in planning up front will save your company more money in the short and long term.
Your organization must clearly define the scope of the NOC, the operational view(s) and capabilities, the system views and interface descriptions, and the baseline technical standards. Without doing this first, it is very inefficient to talk to vendors.
NOC and other network management operations are based on the horizontal integration of capabilities across vertical systems. Vendors tend to sell 'vertical systems' because they benefit by larger market share. However, these vertical systems usually do not scale, sacrifice capability for ease acquisition, and sacrifice interoperability for ease of installation. The attractiveness of 'ease of acquisition and installation' are pitfalls that are hard to avoid.
What is your NOC model? Web-based system control? Secure access from 'anywhere'? Comprehensive logging and event management? Application servers with web presentation? SQL accessible data storage and management? (there are more, BTW).
These and more issues should be well thought out on paper before moving to talk to vendors and talking specific technology buzz. Do you have a graphic of your operational view? Systems interface view?
[Edited by Neo on 11-21-2000 at 05:06 PM]
|