. 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 white papers are required from a business analyst is in fraud management space. The NGN is an IP-based network and the chances of security breach and fraud that existed in the IP world is valid in the case of NGN. Fraud management is a key area of focus for NGNM and the business analyst can contribute with white papers in this space. OSS development needs input from the business analyst and SO regula- tory guidelines are required for telecom space. The changes in regulations have an impact on the business guidelines on the company and the reg- ulatory implications in an NGN environment can be identified by the business analyst. 2. System analyst/solution architect dealing with system/architecture block in System analyst/architect can look into technical marketing that involves promoting NGOSS components including eTOM, SID, TAM, and TNA as the enabler for managing heterogeneous networks with common models. Various NMS solutions are coming up in the market that have capabilities to better manage NGN and are built using NGOSS models. Legacy solution needs are bes