(A). Technical Requirements - Seylan Bank

Annexure-IISl.No.(A). Technical RequirementsFunctions1 Integration Application Requirements1.1 Ability to integrate to support online , real time & batchoperations1.2 Integrator’s support for scheduling and defining of Jobs1.3 Application should handle automatic switchover in clusterenvironment2 Database RequirementsThe system should be able to use any database software of thebanks choice i.e. Oracle, MS SQL etc2.1 Ability to Patch management/ upgradation of database ( vendorhas to maintain the application software compatibility with thelatest version of Database)2.2 Ability to support for pooling multiple database connectionswhen the load on the application increases.2.3 Ability of the database to support clustering. Indicatethe number of clusters that can be configured.2.4 Ability to support online replication.2.5 Ability to implement SANs for data storage in the architectureVendor’sResponse(S/U)Comments3 Hardware and Operating system specification3.1 The Operating system should support Treasury application / IPV4/V63.2 Hardware parameters (like CPU, Memory, hard disk)recommended should not cross the 70% utilization levels at anypoint in time.3.3 Should be able to support different protocols (TCP/IP, IPX,etc.)3.4 Bank anti‐virus software compatibility of the produts on allmachines & Update on a regular basis3.5 Implement patches / upgrades on all softwares, firmwares3.6 Hardware equipment recommended should be scalable tosupport increased requirements of the Bank0prisk_rfp_try vr. 1.0 Tec_spec copy right reserved with the issue Page 1

Sl.No.Functions3.7 Hardware recommended should have built‐in redundancyfeatures such as dual Power supply, dual NIC, RAID etc3.8 Hardware recommended should have efficient hardwaremonitoring and diagnostic functions3.9 Hardware should be rack optimized3.10 The Server should be horizontal & Vertical scalable.3.11 The hardware recommended components should be hotbl4 Backup & recovery4.1 The backup success rate should be 99.99% at all times for theIntegrated Treasury solution (Media and the methodology)4.2 Should support online replication to backup site4.3 Disaster Recovery site to be up & running 24*74.4 Reliable integrity verification functionality for backups4.5 The solution should be compatible with all types of backupdevices.4.6 The solution should support all backup application softwares4.7 Should support IP protocol4.8 Should be capable of automating the backup process for all theapplications/ database in the Primary & Disaster Recovery sites.4.9 Application should recover and become fully operational within 30minutes from the Disaster Recovery Site in case of a disaster atTreasury Department at Head Office.5 Availability Parameters5.1 Hardware recommended should support load balancing(CPU, Hard Disk, memory, etc.)Vendor’sResponse(S/U)Comments5.2 Hardware configuration recommended should be available for24*76 Interfaces6.1 The system should be able to interface with the following,online and seamlessly without keeping any transactionspending for processing :6.2Core Banking Risk Management Basel 2 ALMThe Solution should interface seamlessly with individualmodules and provide Straight Through Processing. Datashould flow from Front Office, Mid Office & Back Office andselected data should flow in the reverse direction.0prisk_rfp_try vr. 1.0 Tec_spec copy right reserved with the issue Page 2

6.3 The system should Seamlessly Integrate with Core BankingSolution (Mysis) and the front office Cashier system without anymanual intervention6.4 The system should provide interface capabilities with all SBKapplications, RTGS, SWIFT, & Other Treasury applications6.5 System should be able to import rates, deals and/or pricesand ratings from independent price providers like Reuters,Bloomberg, CCIL, Moody’s, Fitch etc (web based applications)6.6 The system should provide interface with third party serviceproviders, for eg. STP for Equity market6.7 The system should provide interface for generation of requisitedata from Treasury Database to other Applications/Processes(ASCII fixed length /delimited variable length record format,csv format ,excel format etc.) for other processes like ALM etc.6.8 Live data on rate etc. should be provided on screen only6.9 Drill down on interface record should be available to see errordescription6.10 Provide support to ISO 8583, XML, WAP, SMS, etc. standardmessaging protocols for interfacing.6.11 The system should have the ability to rollback a transaction to aparticular stage and restart, if required.6.12 Provide ability to define business rules for validation andtranslation of incoming messages6.13 The application should have the ability to support MicrosoftInternet Explorer, Firefox, and other such browsers (all latestversions)7 Web Server7.1 The application should have the ability to support Apache,Netscape enterprise, Commerce server, Microsoft IIS, IBM websphere etc. as web servers7.2 The web server should have the capability of writing tomultiple logs7.3 The web server should have the capability to support VirtualServers7.4 Should support network monitoring agents like SNMP agent,etc.7.5 Should be able to support Integrated certificate server, SSLwith 128 bit encryption mechanism or more0prisk_rfp_try vr. 1.0 Tec_spec copy right reserved with the issue Page 3

7.6 Should be able to install on Windows platforms, UNIX flavours,etc (Operating systems).7.7 Should be hardened to disable unnecessary features andplug known security vulnerabilities8 Application Server8.1 The application should be able to support web server access8.2 The application should be able to support Server sidelanguages like ASP, JSP, Personal home page, Cold Fusion MarkupLanguage (CFML), Common Gateway Interface (CGI), etc.8.3 Client side scripting/ programming languages like Java scripts, VBscripts, Java Applets, ActiveX, etc should be supported8.4 The application should support the application layer technologieslike Java, C++, Netscape server application process interface,Internet server application process interface, etc. should besupported8.5 Database Connectivity support should at a minimum beODBC, JDBC, etc.8.6 Support for standard querying engines (ie. MQ, MSMQ, etc.)8.7 The system should provide interface to standard firewalls(application proxy, stateful inspection and mix of both)9 External Interfacing9.1 File formats supported for message based integration (XML, Text,flat file, etc.)9.2 Message formats supported by the application (ISO 8583, etc.)9.3 Integration with a Messaging Middleware like MQ Series, MSMQ, XML, etc.9.4 Support for standard componentframeworks(B) General10 Audit Trail10.1 The system should provide comprehensive audit trail featuressuch as:10.2 Daily activities log are merged into the history log files10.3 Date, time and user‐stamped transaction list are generatedfor different transactions10.4 Transaction screens display system informationincluding0prisk_rfp_try vr. 1.0 Tec_spec copy right reserved with the issue Page 4

10.5 Daily activity reports are provided to highlight10.6 Support for recording of Unsuccessful attempts to log‐in to thesystem10.7 System to provide session log files. The user should be able toanalyze the information (e.g., account id, session time etc.)10.8 System should provide tracking of the client’s IP & NetworkInterface address10.9 The application should facilitate definition of user‐defined logfiles for tracking sessions11 User Access Controls11.1 Application administrator should be separated form System11.2administratorAt least 3 levels of user access be provided for incompatible11.3functionsRole base/ discretionary access Control system be provided11.4 User role allocation be a system parameter and be performed byapplication administrator11.5 Windows 2003 (and Upward) AD authentication12 INPUT/OUTPUT :12.1 Link from Excel & Other Applications12.2 Export of Reports & Inquiries into different formats likeWord, Excel, pdf, Text & CSV etc.13 REPORTS :13.1 Flexible Report Builder for generating simple reports. Thesystem should have a report writing wizard that provides userswith step by step menus and allows them to draw up simplereports13.2 Drilling up/down of reports on the screen should be available13.3 The system should allow users to print reports directly formthe system. Option should be available to print reports inA4/Legal/A3 page using Inkjet/Laser Printer. The default modefor printing of reports (bulk/volume) should be High SpeedDMP/LMP13.4 Provision should be available for generating & printing anyprevious day’s report i.e. backdated reports.‐‐‐‐‐‐the End‐‐‐‐‐‐0prisk_rfp_try vr. 1.0 Tec_spec copy right reserved with the issue Page 5