sms or to updated the challenge or threat list based on additional input. Any change to the resilience strategy could initiate roadmap update requests that need to be handled as part of roadmap change control. Resilience Management Plan Updates The nature of input received could also initiate updates by the way resilience management is planned. CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Plan Operability Management One of the important aspects of pro-active evolution, as discussed in Chapter 5, is the ability to predict and stay ahead of latest developments and industry trends, which should be incorporated in the network to continue to evolve. We capture input in this category under operability management as well as under the different subcategories of fault, configuration, accounting, performance, and security (FCAPS). This is illustrated in Figure 6-14. Input Tools and Techniques Roadmap management plan Output Product analysis Enterprise/domain Industry standards Operability factors Customer management plan Organization input requirement analysis Figure 6-14. Operability management Plan Operability Management: Tools and Techniques Product Analysis Under product analysis, as a technique, it is important to understand which critical aspects of the product should be considered under FCAPS to be able to deliver and evolve a roadmap of good quality, including items like: Support for the latest logging techniques Requirements for troubleshooting issues remotely Ability to monitor critical statistics of system functionality Ability to collect real-time performance data Industry Standards Industry standards could include well-accepted baselines that networks should be compliant with. These include: Competitor network analysis Deployment and operational baselines that could be prevailing in the industry CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Customer Requirement Analysis Customers could also have specific requirements that need to be satisfied as part of the operability requirements, including Specific 