Customer Common File Training And Set Up


Published on

Customer Common File Training And Set Up

Published in: Economy & Finance
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Customer Common File Training And Set Up

  1. 1. Internal Training Customer Common File Training and Set Up Orlando Moreno 408.656.2498
  2. 2. LACC Internal Training New Hires Introduction Welcome to LACC Professional Services
  3. 3. LACC Internal Training New Hires Participants Brief Summary of Roles Expectations of the Training Rules of Engagement Agenda
  4. 4. Agenda Customer Common File – Training and Setup  Definition of the client Common File  Foundation for creation – CF Database Set up of parameters  Ownership of Common File  Changing of parameters  Training approach  Decision makers - What, who, when definition of CF  What are we trying to accomplish when a task is completed in implementation cycle  Who is responsible, Who is trained
  5. 5. Definition of Client Common File  Clients start defining their Common File during/after the training sessions  Clients will require guidance-hand/holding during this process  Consultancy hats are put on  Client makes final decisions on how Common File is define
  6. 6. 1. PURPOSE AND/OR SCOPE Review and assist the client with the implementation of the Common File parameters to effectively meet the clients current product and processing requirements. This is a part of the special process that encompasses all phases of conversion, installation and project management methods for new CBS clients. 2. PREREQUISITES Not Applicable. 3. DEFINITIONS  Common File Term Definition Definition: CBS ICBS LADF Comprehensive Banking System International Comprehensive Banking System Quality System Forms LADW0007 LADP LADW Quality System Procedures Quality System Work Instructions 4. PROCEDURE Common File Definition This is an interactive work session between Fiserv and the client’s resources (project team, trainers, conversion team, etc.). The goal of the session(s) is to develop a completed Common File. (i) This phase of the project consists of developing with the client bank specific Common File features, functions and parameters for each of the following modules: Financial Transaction Management (FTM), Process Server, Transactions, Time, Loans and General Ledger. (ii) The session(s) date is scheduled through the Project Manager who reviews the NIKU resource project schedules to obtain available dates and resources based on prior scheduled commitments. At this time a Fiserv resource is assigned (banker or programmer analyst) to this phase of project. (iii) Approximately four to six weeks following the Pre-Implementation Analysis session, The designated Fiserv personnel and client project team meet in Orlando or at the client site to start the Common File Definition. The number of days required for this task is based on the requirements of the project. The length of each Common File Definition task is generally 3 to 5 days depending on the module.
  7. 7. LACC Internal Training New Hires Environments Common File Demo/Training Conversion Tip: Make sure you have required sign-on information for each of the environments
  8. 8. Environments Description/Purpose  Common File Environment- – This is the true/Final Common File that will apply to the Clients production environment. – This is the environment Fiserv/Client must make sure is defined as per the institution processing requirement needs – This is the environment used for the Common File Sign off task
  9. 9. Environments Description/Purpose  Demo/Training Environment – This is the environment that may be used for the Common File training sessions – This environment may also be used to run test on parameters set, change and see results. – Based on results gathered the True Common file environments is updated. – Changes in this environment are not controlled
  10. 10. Definition of the Client Common File Different Approaches: Converting Clients De-Novo Clients Upgrades Pre-Requisites PIA completed Established teams (Clients/Fiserv’s) of members taking ownership  TIPS Understand the implications the Common File parameters have Converted data New Data
  11. 11. Foundation for creation – CF Database Set up of parameters  The backbone of how each of the ICBS application will process  Participants have full understanding of how ICBS Common File Parameters affect their product processing  Different Parameters need to be defined depending on the institution type.  Fiserv team to provide support for questions that arise in regards to the parameters define
  12. 12. Ownership of Common File  Fiserv guides/instructs the client on how the parameters are defined  Fiserv has the right to lock down the Common File at a given time.  Locking the Common File is a way of ensuring guaranteed results with defined parameters  The signing-off the Common File is the official client accepting ownership  Document LADF0019 is Fiserv’s Official Common File Review-Sign Off document
  13. 13. LACC IMPLEMENTATION SERVICES COMMON FILE REVIEW SIGN-OFF BANK NAME: REVIEW DATE: LIBRARY: RELEASE LEVEL: The following is a list of Common File tasks that must be completed by the Bank before the Pre-Conversion and Conversion phase. All parameters must be reviewed and signed-off by both the Bank and Fiserv project teams. FUNCTION FISERV BANK NUMBER COMMON FILE PARAMETERS INITIALS INITIALS SHARED / BANK WIDE 002110-01 System Header 002110-02 Bank Name/Address 002110-03 Holiday Table 002110-04 Branch Name/Holidays 002110-05 Officer Names 002110-09 * Levy 002070 Automatic Numbering 002563 Reports (Common Base) 002580 Link Number Profile 002930 User Defined Notices 003050 Backup Parameters 002210 Work With Tax Code Reference Tables 002230 State Reference Table 002240 Stl Reference Table 002120-15 * Gl Tax Account Interface 002600-10 Related Product Types (Brands) 002600-11 Related Dealers (Brands) 002600-12 Service Locations (Brands) 001300 Document Location 001310 Document Definition 001320 Document Usage 001330 Document Tracking Reports 002605 Correspondence Bank Profile 002607 Correspondence Printer Definition 002608 Allowable Correspondence Fields 002610 Correspondence Definition
  14. 14. Changing Parameters  Throughout the process of getting familiarized with the systems changes are ok in the Demo/Testing Environment  Changes Made to the Gold Common File once is “Locked Down” require a Change Request Form  Fiserv’s official Common File Change Request Form is LAD0018 Tips: It is ok to enquire as to why the change. Does it make sense at this point in time It is also ok to reject the change if a negative impact may result from the change
  15. 15. LACC IMPLEMENTATION SERVICES COMMON FILE CHANGE REQUEST FORM BANK NAME: DATE REQUESTED: PHONE NUMBER: REQUESTED BY: FILE LIB: List below the exact changes that are needed in Common File. If it is agreed upon by the Bank and FIserv, the changes will be made on the FIserv copy. You will be responsible for making the changes on your copy. Keep in mind that the Common File that will be used for Conversion will be the copy that resides at FIserv. APPLICATION PARAMETERS: (check all that apply) DD ( ) CI ( ) EF ( ) AB ( ) CR ( ) SV ( ) TM ( ) LN ( ) GL ( ) GN ( ) FUNCTION NUMBER/NAME: DESCRIPTION OF CHANGE: FIserv Only Bank Only DATE RECEIVIED: DATE NOTIFIED: DATE CHANGED: ACCEPTED BY: APPROVED BY: DATE CLOSED:
  16. 16. Training Approach  Training will be based on the type of Client becoming a member of the Fiserv family Bank, Credit Union  Client established team will be responsible for the definition and controlling CF  Fiserv provides an agenda and recommended audience for each training session  By the time training starts Fiserv team is knowledgeable in regards to the products the client offers/will offer (based of the PIA)
  17. 17. Decision Makers what, who, when ?  Common File is a joint effort between Fiserv and Client  Fiserv provides the input via SMEs (us) how the system will process based on a specific parameter  Client based on the daily operation requirements defines CF accordingly  Team Leads/Mgt for each application will make the decision on CF parameters
  18. 18. Miscellaneous  Experiences  Additional Tips  Recommendations
  19. 19. Questions? Orlando Moreno 408.656.2498