-
Do all of your check imaging customers run the
same version of software?
-
How many different check imaging products
(platforms) does your company support?
-
Describe your company’s deployment of new
system releases? Does my bank have to do it or does your company
perform the upgrade?
-
Are check images stored in an open image format,
or will you hold my institution hostage with your company’s own
“proprietary” image format?
-
Describe your image system’s archive, back-up,
and recovery procedures?
-
Describe the process for adding pc’s or
workstations to the system? If we load another company’s software
on the same pc will you guarantee that your software will still
function properly with the system?
-
Explain
your company’s methodology for handling corrupt
index/image pointer files?
-
How many concurrent user licenses have you
proposed? With your
proposal, how many concurrent users can utilize any system function
simultaneously?
-
What database is used for check image capture and
processing?
-
What database is used for long term archival and
statements?
-
If a different database is used at capture than
for long term archival, how many checks can be imported per hour
into the long term archival database with the hardware being
proposed? Describe the transfer process (manual, automated, etc?)
-
Describe the reconciliation tools for determining
that the proper number of records and images have been transferred
and updated between the different database systems?
-
Is a database administrator required for optimum
system performance? Does your company charge for such a service?
-
Who owns the software that you are proposing? Do
different vendors provide the software for capture/processing and
archive/statements?
-
Describe your email statement system. How does
your company address the issue of security and file size?
-
Explain your company’s methodology for handling
corrupt index/image pointer files? Describe the recovery process to
ensure images are not lost.
-
What devices have you recommended in the past and
what do you presently support for long term archival? What do you
recommend today?
-
Describe the security capabilities of the system.
How does the system guarantee the integrity of the images and
database information?
-
Describe the system architecture. Is the system
mainframe based, client server based, or Browser-based? If not
Browser-based for all functions, please explain why not and what
your company’s plans are for the future to address the technology?
-
Please explain the options available for altering
statement design outside of my host capabilities. Must I rely on the
host to make changes to the statement design for them to appear on
my image statements? Explain the your process for providing the
lowest postal rates with CASS, PAVE, and Manifest Mailing
Certification.