1 / 18

Doron Tamari 02.2006

Current Situation

laszlo
Télécharger la présentation

Doron Tamari 02.2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    2. Current Situation Messages are kept in MINT Archive database for a short period of time (months), no long term Archive solution Old Microfiche files cannot be imported back to the application for search or printing Microfiche files are stored without any order on server directory, no tool for search/find specific msg Files can be deleted or lost. Data within the files can be changed! The existing Search criteria's (Live/Archive database) are weak, very limited, most fields none indexable, search execute in sequence order Normally, at the end of the process, you cannot find your msg on the database and get frustrated No integration with bank legacy applications Therefore

    3. MINT Long Term Archive Tool Long term storage system for unlimited period (i.e. 10 years archive, as per banks regulations) Parsing messages with extraction of message structure (in Print/Microfiche format) Keep only relevant payments/business messages (i.e. filter out system messages gpa, o6ox, 08x, n1x) Save messages and their fields extracted can be defined per customer specifications in a standard SQL database Queries can be made using available GUI or via program (SQL commands) High Security Aspects: Hard copy of the message is stored in database in compress mode No access for users to modify data Archive messages can be encrypted/Digital-Signature to ensure higher-level integrity and confidentiality Every access to view a message is kept in system log

    4. MLTA, more features Presents messages in PDF format: with user-name/date/time stamp & special page banner/background (i.e. MINT Archive) Backwards compatibility: can handle old formatted msgs (i.e. SWIFT 52x, 100) Enhanced & extensive query capabilities: every field tag (SWIFT, SIC/ESIC/SECOM, any other msg format, transformation in/out) all amounts, different formats, repetition amounts fields ISIN & IBAN data is kept as separate index field Can completely replace the current end users searching for msgs in MINT: make it fully on-line messages update (via MQS, MOA, etc.) GUI screen prompts in 4 languages (user may select his preferred language on login) User can Save/Load their special search criteria Sort your selection results, on the fly

    5. MLTA, Technologies Software entirely based on Java 2 technology Will run wherever a standard JVM is available: Linux, MS Server, Unix, MF, etc. Any SQL compliant RDBM can be used for storage: DB2 Oracle, Sybase, MS SQL Server Open architecture allows integration with legacy systems High performance on large sets Client GUI Java application on each PC or centrally (i.e. Citrix Server) Browser client can be supported (user order depended)

    6. MLTA, Integration and Scalability The software is developed entirely in-house, only RDBM (and PDF) licenses are needed Time-proved, short period installation Can be scaled up from PC-Based architecture installation to high-end mainframe/storage system Can be installed as is or further extended to implement customer features (i.e. add index as search field on any message fields) New msg format is based on tables driven modifications Ready for integration with legacy systems

    7. MLTA, Basic Implementation Implementation options, full automation: Update the database once a day (EOD process) Generate Microfiche files x times per day Full on-line messages storage (via MQS, MOA), when reached to final stage send msg in Print Format directly to the database Filtering un-needed msgs on Flow/Distribution, or during the Parsing to database 3 days implementation per instant (as is, without customization) & GUI training/usage Self Maintenance & Enhancements (knowledge: Java 2, SQL, RBDM Admin) or by consulting company, based on T & M Please take short tour:

    18. Tamari Doron Tel/Fax: 00 41 (0) 91 6309131 Mobile: 00 41 (0) 78 7646076 tamari.doron@topping.ch

More Related