(I) Any costs to expand the number of users or area after the go-live Since this cost is not categorized to the hardware and software product maintenance cost explained in 3.4.2.1, any other costs will be incurred after the go-live shall be borne by CBM. (J) Cost of the application process for use from the FIs As explained in (D), a system owned by an organization other than CBM will not be in scope of this project. (K) Distribution of documents for users of FIs and CBM As explained in below (3)(C), the communication with users will be a role of CBM. The distribution of documents for those users is also the role of CBM. The support for the preparation of documents descripted in 3.2.4.8 will be covered by Phase 2. (L) Preparation for running tests (including confirmation of the test plan, business operation manual, system operation manual, DR manual, assignment of staff to educate and train, confirmation of condition for go-live assessment) before the running test 1 working with Technical Cooperation Project The schedule of running tests are descripted in 3.2.4.7.1 and some of the preparation items will be able to have a support from soft component as descripted in 3.2.4.8. (M) Connection test after connection test 2 and running test after running test 2 (for FIs that cannot prepare the STP environment until the above period) As explained in 3.2.4.7.1, the connection test and the running test for FIs after group 2 will not be included to Phase 2 scope and shall be conducted by coordination of CBM, based on the experience of above tests. (2) Hardware/Facilities, etc. (A) Any costs related to payments for technical support for hardware and facilities after the go-live According to 3.4.2.1, any of these costs shall be borne by CBM. 99