We handle all changes to all of our systems thru Change Management "Request for Change (RFC)" process in which the change is put in a request which is then routed to key personnel for review and in some case approval (depending on the risk of the change). In a lot of ways, we aren't in control of when FiServ applies changes, but like for a new release, it's handled as a project. Project Release notes are sent to key personnel, like systems, compliance and others who review and determine what they will need to do, log the tasks in the project schedule and then implement, test, and release. Examiners like to see the way the process is handled
Original Message:
Sent: 04-05-2022 04:43 PM
From: Laure Slezak
Subject: Tracking and documenting Fiserv releases/updates
How do you currently track updates/releases from Fiserv, logging any updates that need to be done on your end? We were thinking of potentially using our software for exam findings by using the email notifications from Fiserv, but I don't believe the findings software integrates with Outlook in that way and adding them manually in would be such a tedious task. I'm looking for any suggestions anyone else has. Thanks in advance!