Implementation Figure 17.1 NGNM lifecycle. (From TMF TR133 NGNM Strategy document). block by service provider, the service developers create an architecture that is not tied to a specific technology or vendor product and is a technology neu- tral architecture (TNA) that satisfies the requirements. Implementation: This block is the intersection of technology specific space and service developer space. A technology specific implementation of the TNA is performed in this block. The implementation is performed by the service provider. Deployment: This block is the intersection of technology specific space and service provider space. Once the implementation is completed by the service developers, the service providers need to deploy the solution. This activity is captured in the deployment block. These four blocks constitute the telecom lifecycle and is used to give holistic vision in all forms of development activities. The lifecycle is discussed in detail in the chapter on NGOSS lifecycle. NGNM focus is also split into these four blocks by TMF in the TR133 document. Rather than activities in the block, TR133 shows what should be the contribution from the key stake holders of individual blocks toward NGNM. 1. Business analyst dealing with business block in NGNM The operational parameters in a service provider space needs to be clearly defined for which the business analyst needs to define key performance indicators (KPIs) for operations that can be measured and monitored. For Fundamentals of EMS, NMS and OSS/BSS proper monitoring of these operational KPIs, there should be tools that can capture the required information and represent it in a user-friendly format like plots/graphs or events that can be tagged. An end-to-end pro- cess needs to be defined for the same. Revenue assurance is an important part of business and has key challenges to be addressed in the NGN environment. Research and resulting white papers to address the issue in revenue assurance can be brought out by a business analyst. Another key area where