BASE24 classic vs BASE24-eps

Posted on 5th Nov 2017 11827 views

According to a report of HP in 2009, created by FSS (Financial Software Systems), this is the comparison between BASE24 classic and BASE24-eps, in a nutshell. Some modifications have been made where the information was outdated.

The information below is just for reference and should not be used as an assessment, but an assessment can be made with this as reference points.

Give that BASE24 classic only runs on HP NonStop, a platform comparison is not included in this report. HP Nonstop are now called HP Integrity NonStop

Comparison table below: [break]

BASE24 classic	BASE24-eps
• Open source system; customer has access to full application source code for the modules licensed • Customer has better control of customizations and the application code • Modular design	• For version 08.2 and above, only limited source code for business components is provided • Development environment and source code must be licensed separately • Not modular; large block of bounded code • While customers have limited ability to change the application code, the new scripting functionality enables customers to change the business logic
• Transaction-, product- and module-based licensing are supported	• Only transaction-based licensing is supported
• Proven system, running successfully at major customer locations around the world • Supports a basic card module for card production and PIN generation • Telebanking module support is available through RBSI module; used for integration with interactive voice response (IVR) or telebanking devices	• Fewer implementations, as compared to BASE24 or other switches; no major implementations that drive mass terminal volumes; application not completed • No card production support; external application is required • Telebanking module support is not available at this time
• Pathway-based screens use terminal emulation • Graphical user inter face (GUI) could be developed using third-party products	• Provides a comprehensive graphical user interface (GUI source code is not provided to the customer)
• Supports limited routing methods; additional routing requirements can be tailored to meet customer needs	• Supports powerful routing; combination of parameters for routing a transaction, including source, destination, transaction type, account type and authentication method • Also supports primary and alternate authorizers, automatic re-routing and more
• Standard pre-screening and authorization support is available under the base code; • Additional authorization requirements can be handled through customizations; authorization can be based on status code, positive/negative file lookup or hard coded exceptions	• Scripting support for authorization; pre-screening and authorization logic can be performed using scripts • User-created scripts can determine how to treat each item at the individual cardholder level
• Standard reports and extracts are provided by the application process; additional report or extract requirements can be customized • Log file reports can be easily extracted from an external MIS system	• Scripting support for authorization, reports and extracts