Sustainable operation structure of CBM will be confirmed as follows. As for (a), it will be confirmed by the description of the operation manuals. As for (b) and (c), it will be confirmed by observing the application maintenance structure of CBM if the ratios of outsourcers are decreased. (a) The work flow definition for the incident which is in-house oriented. (b) Assist for the demarcation of CBM and system developer for the regular system operation work. (c) Support CBM to define the role and responsibility of the system, to maintain by its own staffs, using master table administration and programs equipped with selective parameter. The demarcation of the consultant and system developer will be defined as followings. Consultant; • System Design Phase; Guide CBM to define the work scope of CBM for system operation work. • System design confirmation; Confirm it is equipped with the system maintenance function so as to maintain by CBM. • Support to define organisational structure, segregation of duties, definition of authority, definition of insource / outsource. The system developer; • Prepare the system operation manuals which describe operation of the facility, explain the system console operation, show measures against alerts, and etc. The activities mentioned above focus on the scope of the 2nd Development. In the case of the facility which is handed over from the 1st Development and use for the 2nd Development are in the scope. MCH and CBM-OA are excluded. 5. Soft Component activity (input plan) 5.1 Executing structure The executing structure is illustrated as below. Total of 11 members headed by the Operation Support Leader are planned to be assigned. Of all these, 6 officers are to be business and application-related. 5