features that are required for regulatory or compliance aspects Features that are required to cover deployment and acceptance tests from network vendors Operational implications derived by customers from their past network analysis Plan Operability Management: Output Operability Management Plan We define the operability management plan as the single source for all information related to aspects of operability that act as input for roadmap evolution, including: Operability aspects that are to be targeted by the network, including ways to baseline different aspects of operability Information about stakeholders that are responsible for operability aspects of the network Information about how aspects of operability are to be monitored for evolving processes and how these should be tracked from industry sources, trade publications, standard bodies, and other networking groups of importance Process steps about how requirements to operability improvement are to be collected and reviewed as part of the roadmap review process Summary It has been our endeavor throughout this chapter to illustrate how a set of processes could be defined under a framework to ensure that the network roadmap stays updated, relevant, and continues to evolve as per changes in the business, market, and industry conditions. As mentioned in Chapter 5, processes and tools are only useful to the extent that they guide the user to think in certain ways. It is the user who needs to be motivated enough to think on the same lines. The most important reason for you to do so may be that, like all human tendencies, the tendency to improve oneself is the most far-reaching in terms of advancement of human prowess. We expect that the process of evolution of network roadmaps will help make the network better in itself, and at the time and to help it evolve and keep itself relevant, effective, and able to meet business needs. Index spectrum harmonization, 66 VoLTE implementation, 67 Advanced Networked Systems Dongles vs. smartphone, 74 Architecture (ANSA), 122 A