First question I would ask is what's wrong with the current system they
have ?
If the core system is good, why not build some things around the current
core system to modernize it instead of buying a full blown new system.
One example of modernization of document processing would be to automate
the policy generation using an automated document assembly solution that
can process the work instructions and create policy documents with very
minimal or NO coding.
RJS offers several products and consulting services that can help with
the entire document lifecycle from creation to capture to storage and
print production.
Make sure you're asking the hard questions before pulling the plug on
the current system.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 8
date: Thu, 13 May 2010 10:55:09 -0500
from: "sjl" <sjl_abc@xxxxxxxxxxx>
subject: Trying to keep it on "i"?
List -
I have a former client which currently runs their insurance applications
(claims and underwriting) on a System i. I helped with their original
implementation of an AS/400 COBOL-based applications back in the 1990's.
They are currently involved in a software search for a new application,
and
would prefer an IBM i solution because of their investment in
infrastructure
and staff.
As far as I know, most insurance software vendors have migrated away
from
the IBM i platform.
I have suggested that if they have current IBM Power hardware, however,
that
they could preserve their hardware investment by using a package which
could
run on AIX or Linux, and from what I recall in the recent IBM
announcement,
the Oracle database actually performs better on Power hardware than on
Sun
hardware.
Any thoughts or suggestions?
- sjl
midrange.com
