 plan are critical inputs for the define roadmap process. Roadmap Feature Input Features to be developed as part of the roadmap should be made available by the PLM or marketing function with the following information: Customer visible impact of the feature Motivation for the feature (needed by a certain customer, needed for standard compliance, etc.) Importance of the feature in terms of revenue generation capability Feature complexity in development and testing Dependency on other features Applicable Standards Standards that impact the features under development need to be known and understood to accurately define the roadmap. Also, roadmaps need to define the standard baseline to which they adhere, and customers use this information to understand the feature functionality, which can differ from release to release. CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Resilience Management Plan The resilience management plan should give the following input to the roadmap: Which resilience measures need to be developed as part of the roadmap Prioritized input regarding service level definitions Prioritized list challenges that need to be handled with information about past system behavior under challenges Cost or impact due to degradation of KPIs or lack of resilience handling Resilience input defined in terms of system aspects that could be estimated and developed as part of the roadmap Operability Management Plan Operability aspects of the network need to be derived from the operability management plan, including input about: Support provided for management of fault, configuration, accounting, performance, and security (ITU-T M.3400 standard) as per industry and organization standards Specific operability aspects that need to be taken care of for deployment and monitoring aspects of the network Business Continuity Plan Input Aspects of business continuity planning definitely impact a roadmap that is under development. Requirements for this have to be part of the defining roadmap process. However, some observations 