into the following application components or infrastructure special features. Hereafter, the system scope and design features will be considered in each application component or infrastructure special feature. The requirements related to (B) above will be introduced according to consideration of the infrastructure special features in Table 3-3. On the other hand, CBM-OA – a part of the CBM ICT system providing office automation (OA) applications and other basic office functions – will not be included in the Phase 2 development scope. In addition, MCH, the subsystem under the current CBM-NET, which is under stable operation, will be outside the scope as well. Table 3-2 Relation between application components and requirements Application Components 1. STP 2. ISO 20022 adaptation 3. Liquidity saving feature and message queuing 4. ACH 5. Cheque Truncation 6. Anti-money laundering function 7. Alert and dashboard function Requirements (b) Direct linkage system between CBM-NET and the other financial systems (a) Compatible for ISO 20022 standards (c) Liquidity saving facilities (LSF) that allow FIs to settle transactions with low liquidity (h) Function of forward dating transactions (g) Establish retail payment system (h) Function of forward dating transactions (j) 24-hour operation (i) Cheque settlement with digital image data (k) Anti-money laundering function (l) Alert Source: Preparatory Survey Team Table 3-3 Relation between infrastructure special features and requirements Infrastructure Special Features 8. Disaster Recovery 9. Redundancy of the data 10. User authentication 11. Automatic data exchange Requirement (m) Data backup for disaster recovery (f) Implement clustering for the existing database management system (e) Reinforced of user authorization function (d) Automatic data exchange within subsystems of CBM-NET Source: Preparatory Survey Team 19