Category: Pathway

BASE24 and BASE24-eps architecture overview

The BASE24 electronic payment system developed by ACI Worldwide exists in two primary architectural generations:

BASE24 Classic (historically deployed on HPE NonStop / Tandem fault-tolerant hardware) and

BASE24-eps (Enterprise Payments System, built using an object-oriented C++ framework deployable across open systems, z/OS, and cloud infrastructure).

Despite structural differences, both share a highly optimized, component-based transaction routing engine.

BASE24 and BASE24-eps architecture overview
BASE24 architecture overview

Core Structural Component Layers

The component architecture maps the complete end-to-end lifecycle of a financial message (such as ISO 8583) through five distinct functional sub-systems:

1. Network & Message Routing Component (XPNET)

  • Purpose: Coordinates all message traffic across internal processes and physical network nodes.
  • Function: Operates as a specialized middleware network manager that decouples low-level communication links from upper transaction routing layers.
  • Configuration: Relies on a Logical Network Configuration File (LCONF) to define active execution nodes, hardware lines, and physical stations.

2. Perimeter Access Layer (Device Handlers)

  • Purpose: Translates device-specific message protocol formats into the system’s unified internal format.
  • ATM Device Handlers (ATMDH): Manage direct connectivity to automated teller machines, unpack specific vendor dialects (such as Diebold or NCR states), and track terminal hardware statuses.
  • POS Device Handlers (POSDH): Interface with point-of-sale acquirer terminals and merchants.
  • Security Operations: Triggers immediate payload encryption/decryption and Hardware Security Module (HSM) PIN-block translation directly within this ingestion ring.

3. Core Transaction Logic (Authorization System)

  • Purpose: Determines whether a payment request should be accepted, rejected, or modified.
  • Full On-Us Authorization: Inspects internal databases for matching account records, positive balances, and velocity thresholds to issue real-time decisions.
  • Parametric/Negative Checks: Validates card status against offline negative files, usage restrictions, or custom risk parameters.
  • Scripting Engine: Modern BASE24-eps variants execute localized transaction routing scripts via customized operators without forcing a compile rewrite of the core engine core.

4. Boundary Channels (Interchange & Host Interfaces)

  • Interchange Interfaces (ICH): Package and transform the transaction payload into international network profiles (e.g., Visa, Mastercard, regional switches). It handles strict message mapping and regional network check requirements.
  • Host Interfaces (HIF): Create synchronous links back to an institution’s underlying Core Banking system to apply ledger adjustments, check balances, or execute real-time holds.

5. Offline & Administrative Subsystems

  • Extract Component: Gathers active transaction logs and streams filtered payloads out to analytical reporting databases.
  • Refresh Component: Updates terminal operational data, key packages, and card exclusion lists from parent systems down to active execution nodes.
  • Settlement Initiator: Groups, cleanses, and batches net-clearing totals to finalize payment entries into regional clearinghouses.

Architectural Divergence: Classic vs. EPS

The structural design varies significantly depending on the generation of the software deployment:

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

End-to-End Component Transaction Flow

  1. An ATM transaction arrives at the network interface layer managed by XPNET.
  2. The message is routed to the Device Handler, which strips hardware packaging and requests translation from the HSM.
  3. The clean internal message passes to the Authorization Engine.
  4. If it is a “Not-On-Us” card, the engine identifies the destination BIN and transfers routing control to the Interchange Interface.
  5. The Interchange Interface maps the payload to the external scheme standard (such as Visa) and transmits it to the external network.
  6. The outbound network response is unwrapped by the Interchange component and tracked through the core engine to log final response codes.
  7. The transaction safely records inside the active log file, allowing the Extract / Settlement components to pick it up later during batch processing.

BASE24 and BASE24-eps architecture overview

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

HPE Nonstop Technology Architecture – specialized, 100% fault-tolerant infrastructure

The official HPE Nonstop Technology Architecture is a specialized, 100% fault-tolerant infrastructure built with a tightly integrated hardware and software stack designed to eliminate any single point of failure. Formal instruction and architectural frameworks have been modernized under the newly relaunched HPE Nonstop Compute Training Portfolio curriculum.

Originally developed by Tandem Computers in 1976, the platform eventually became part of Hewlett Packard Enterprise (HPE). Unlike standard servers that can crash due to a single component failure, NonStop uses a tightly integrated, “shared-nothing” architecture to ensure that if a hardware or software component fails, another instantly takes over with zero downtime or data loss.

Core Architectural Features

To understand how HPE NonStop works, you need to understand its unique design principles:

  • Shared-Nothing Architecture: Every processor has its own dedicated memory, I/O channels, and copy of the operating system. No single component is shared, eliminating any single point of failure.
  • Process Pairs: Applications run using a primary process and a backup process on a different processor. The primary process constantly copies its state to the backup. If the primary fails, the backup immediately takes over.
  • Massive Scalability: Systems can scale up seamlessly from small distributed environments to massive clusters containing up to 24,000 processor cores without interrupting running operations.
  • Hardware Platform: The modern software environment runs on industry-standard x86 architectures, available as physical server racks (like the HPE NonStop NS9 X5) or as virtualized instances in hybrid cloud environments.

Dual Operating Environments

HPE NonStop runs a specialized operating system called NonStop OS. Inside this OS, developers and administrators interact with two distinct environments:

  • Guardian Environment: The native, proprietary environment optimized for high-volume Online Transaction Processing (OLTP). It handles tasks sequentially through process-oriented manually-started jobs rather than traditional automated queues.
  • Open System Services (OSS): A UNIX-like, POSIX-compliant environment built on top of the NonStop kernel. This allows organizations to run standard open-source applications, tools, and scripts natively alongside Guardian.

Ecosystem and Use Cases

HPE NonStop is rarely used for standard office automation or basic web hosting. Instead, it serves as the backbone for global industries where an hour of downtime could cost millions of dollars:

  • Financial Transactions: Powers global stock exchanges, automated teller machines (ATMs), and retail point-of-sale credit card processing, eg. BASE24.
  • Travel and Logistics: Runs critical airline reservation systems and real-time cargo routing infrastructure.
  • Database Management: Features its own highly secure, distributed database engine called NonStop SQL, which guarantees absolute data integrity across all transactions.
  • Modern Development: Supports traditional languages like COBOL85 and ANSI C, alongside modern DevOps integrations like Git, Ansible, and Eclipse-based IDE environments.

If you plan to work directly with these systems, you can explore formal pathways like the Concepts and Facilities for HPE NonStop Systems course provided by HPE Education Services.

Core Architectural Layers (Diagram Blueprint)

An architectural blueprint of an HPE NonStop environment typically separates the layout into three core interdependent layers:

  • Hardware & Fabric Layer: Consists of independent, loosely-coupled Processor Nodes (handling up to 24,000 cores globally) connected via an ultra-fast InfiniBand or ServerNet system fabric backbone.
  • I/O & Subsystem Layer: Utilizes Cluster I/O Protocols (CLIMs), splitting tasks between Storage CLIMs (SCLIMs) and Network CLIMs (NCLIMs) to isolate external communication from main processing.
  • Operating System & DB Layer: Runs the NonStop OS, which simultaneously manages the traditional Guardian environment, Open System Services (OSS) for UNIX/Linux paradigms, and the NonStop SQL distributed database engine.

Recommended Architecture Training Curriculum

HPE organizes its technical blueprints into structured educational paths for engineers.

1. Foundational Blueprint Concepts

  • Course Code: U4147S (HPE Nonstop Compute System Fundamentals).
  • Focus: Delivers a top-down view of system goals, transaction processing, and fundamental architecture.
  • Key Modules: Explores Guardian vs OSS, Pathway application management, and basic database interaction.

2. System Operations & Administration

  • Course Code: H1SC3S (HPE Nonstop Compute System Administration I).
  • Focus: Maps physical and virtual components to real-world deployment.
  • Key Modules: Covers Processor Nodes, configuring SCLIMs/NCLIMs, and hands-on fault-scenario testing.

3. Low-Level OS Internals

  • Course Code: U8609S (HPE Integrity Nonstop Operating System Architecture).
  • Focus: Deep dive into runtime architecture, process control, and memory allocation.
  • Key Modules: Focuses on Inter-process Message Systems, synchronization mechanisms, and system debugging.

Training Delivery Options

Enrolling via HPE Education Services grants access to various professional development features:

  • HPE vLabs: Direct sandbox access to practice configuration and live fault injection inside virtual environments.
  • Digital Learner Credits: Flexible licensing options to assign corporate learning units across teams.
  • Modernized Tracks: Courses have been fully overhauled to support contemporary cloud paradigms and hybrid integration via HPE GreenLake frameworks.

My HPE NonStop (Tandem Computers) Certificates :

Insider Tech : 1995 – 2013
HPE NonStop (Tandem) Career Experience at Insider Technologies Limited, ITL
BASE24 eps monitoring

Connect NonStop Registration Sept. 2026, NonStop Technology & Business Conference

Connect NonStop Registration 2026, NonStop Technology & Business Conference
Event Date

September 15-17, 2026 (HPE Education Sept. 14)

Event Location

Orlando, Florida

Venue

The Rosen Plaza 9700 International Drive

Contact Us

info@connect-community.org

TBC’26

BASE24 Overview and Historical Timeline

BASE24 is a foundational electronic payments software suite developed by ACI Worldwide, first launched in 1982 to provide “always-on” (24/7/365) transaction processing, primarily on HP NonStop servers.

It is used by large financial institutions to acquire, authenticate, route, switch, and authorize card- and non-card-based financial transactions across multiple channels, including ATMs, point-of-sale (POS) terminals, and mobile/internet banking. 

The product has evolved from “Base24 Classic” into BASE24-eps (formerly BASE24-es), a modern, object-oriented, platform-independent payments engine designed to support high-volume, real-time transaction processing in hybrid or cloud-based environments. 

Comprehensive Historical Timeline of BASE24 

  • The Foundation Era (1975–1981): ACI (Applied Communications, Inc.) was founded in Omaha, Nebraska, in 1975, initially developing software for fault-tolerant Tandem NonStop computers. The focus was on connecting the first wave of ATMs to bank systems.
  • The Launch and Global Expansion (1982–1990):
    • 1982: BASE24 product family is officially launched, serving as the “baseline” software for 24-hour operations.
    • 1986: By 1986, ACI has 131 customers in 14 countries, expanding globally.
    • 1987: ACI receives the U.S. President’s “E” Award for Excellence in Export.
  • Public Company and Modernization (1995–2000):
    • 1995: ACI becomes a public company.
    • 1997: Adopts the name ACI Worldwide.
    • 1996–2000: Initial expansion of support to platforms beyond Tandem, including IBM mainframes and UNIX, to support rising internet commerce.
  • The Transition to Open Systems: BASE24-eps (2001–2010):
    • Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a Next-Gen, C++ based engine.
    • 2003: BASE24-eps is live on HP NonStop, IBM zSeries, and IBM pSeries/Sun Solaris.
    • 2006: ACI announces a version of BASE24-es to support UK Faster Payments.
    • 2008–2010: ACI moves toward a unified strategy, with BASE24-eps becoming the mainstream offering while Classic matured.
  • Modernization and Cloud Era (2011–Present):
    • 2011: BASE24-eps wins the Most Innovative Financial Product Award.
    • 2015: ACI celebrates 40 years of operation and introduces advanced fraud detection (Proactive Risk Manager) integrated with BASE24-eps.
    • 2023: ACI goes live as an early adopter of the Federal Reserve’s FedNow Service, using modernized BASE24-eps technology.
    • 2024–2025: BASE24-eps becomes fully PCI-SSF compliant (PCI 4.0), running on Red Hat Enterprise Linux and supporting hybrid cloud deployments. 

Key Features of BASE24-eps

  • Fault Tolerance: Designed for high availability with near-zero downtime.
  • Multi-Channel Support: Manages ATM (NCR, Diebold Nixdorf), POS, and Mobile/Web traffic in a single engine.
  • Scripting Engine: Uses JavaScript-like scripts to allow customers to define authorization logic without modifying the core system.
  • Universal Connectivity: Supports 40+ global and regional network interfaces (Visa, Mastercard, etc.).
  • Platform Independence: Runs on HPE NonStop, IBM z/OS (CICS), and Linux/x86_64.
  • Real-time Fraud Prevention: Integrated with ACI Proactive Risk Manager. 

BASE24 Classic vs. BASE24-eps

  • Classic: Monolithic, Tandem-dependent, older technology.
  • eps: Object-oriented (C++), open systems architecture, 30% faster processing, supports cloud-native approaches. 

BASE24 Overview and Historical Timeline

Tandem Computers ( HPE NonStop ) Overview & Detailed Timeline

Tandem Computers, founded in 1974 by James (Jimmy) Treybig, revolutionized the computing industry by pioneering fault-tolerant computer systems. Designed specifically for online transaction processing (OLTP) in banking, stock exchanges, and telephone switching, Tandem’s “NonStop” systems provided near-zero downtime by utilizing redundant, modular processors and a “shared-nothing” architecture. 

Tandem remained an independent, rapidly growing company until it was acquired by Compaq in 1997, later becoming part of Hewlett Packard Enterprise (HPE). 

Overview of Key Technologies

  • NonStop Architecture: The core design featured multiple independent processors, each with its own memory and I/O bus, interconnected by a redundant inter-CPU bus called the Dynabus.
  • Guardian OS: A message-based operating system designed to detect faults immediately (“fail-fast”) and mirror process states to a backup processor, allowing seamless failover.
  • NonStop SQL (1986): The first fault-tolerant SQL database, known for linear scalability.
  • ServerNet (1995): A high-speed, scalable, point-to-point network system that replaced the Dynabus and influenced modern InfiniBand standards. 

Detailed Historic Timeline by Era and Year

The Founding Era (1974–1979) 

  • 1974: Tandem Computers is founded in Cupertino, California, by Jimmy Treybig, formerly of HP. Initial venture capital investment comes from Kleiner & Perkins.
  • 1975: Design of the Tandem/16 (T/16) is completed.
  • 1976: The first T/16 NonStop system is shipped to Citibank.
  • 1977: Tandem goes public; sales begin rapid, exponential growth.
  • 1978: Introduction of the ENCOMPASS database management system.

The Growth and Competition Era (1980–1989)

  • 1980: Inc. magazine ranks Tandem as the fastest-growing public company in America.
  • 1981: NonStop II is introduced, supporting 32-bit addressing to allow for larger applications.
  • 1982: Competition intensifies as Stratus Technologies enters the fault-tolerant market. Tandem faces its first quarter of declining growth.
  • 1983: Introduction of the NonStop TXP, the first entirely new implementation of the TNS architecture with cache memory.
  • 1985: Attempted entry into the PC market with the MS-DOS-based Dynamite PC, which fails commercially and is withdrawn.
  • 1986: Introduction of the NonStop VLX (32-bit datapath) and the revolutionary NonStop SQL database.
  • 1987: Introduction of the low-cost NonStop CLX for small office environments.
  • 1988: Tandem acquires Ungermann-Bass, Inc. to strengthen networking capabilities.
  • 1989: Introduction of the NonStop Cyclone, a high-end ECL-based processor aimed at mainframe markets. 

The Open Standards & MIPS Transition Era (1990–1996)

  • 1990: Tandem introduces the Integrity line of fault-tolerant Unix systems.
  • 1991: Cyclone/R (CLX/R) is released, marking the start of the migration from proprietary stack machines to MIPS R3000 RISC microprocessors.
  • 1993: Introduction of the NonStop Himalaya K-series using faster MIPS R4400 processors.
  • 1994: NonStop Kernel (NSK) is extended with Open System Services (OSS), a POSIX-compliant Unix environment.
  • 1995: Introduction of ServerNet, designed for extremely low-latency inter-processor communication.
  • 1995–1997: Partnered with Microsoft on the “Wolfpack” project, which becomes Microsoft Cluster Server. 

Acquisition and Integration Era (1997–Present)

  • 1997: Compaq acquires Tandem Computers for roughly $3 billion. The Himalaya S-Series is introduced.
  • 1998: Compaq acquires DEC, leading to a shift in engineering strategy towards Alpha/Itanium instead of MIPS.
  • 2001: Compaq terminates Alpha engineering, committing to Intel’s Itanium (Merced) processors.
  • 2002: Hewlett-Packard acquires Compaq. Tandem becomes the core of the HP Integrity NonStop Server division.
  • 2005: The first HP Integrity NonStop servers (TNS/E) based on Itanium processors are released.
  • 2014: Completion of the migration to Intel x86 architecture (NonStop X). 

Note: Following the split of HP into Hewlett Packard Enterprise (HPE) and HP Inc., the NonStop product line continues to be developed and supported by HPE.

Tandem Computers Overview and Detailed Timeline

HPE NonStop EMSDIST, Event Management Service EMS Distributor Timeline by Era

HPE NonStop EMSDIST (Event Management Service Distributor) is a critical component within the HPE NonStop operating system responsible for distributing and managing event messages (logs) generated by the system, subsystems, or applications. It is part of the Event Management Service (EMS), which is essential for fault-tolerant monitoring. 

EMS events (via EMSDIST) seen in the Reflex 80:20 application ( now Sentinel (Nonstop Monitoring) by ETI-NET)

EMSDist Overview

  • Purpose: EMSDIST reads events from an EMS collector process ($0, $ZLOG, etc.) or a collector logfile, filters them based on user criteria, and sends them to a user-specified destination (such as a terminal, printer, or another file).
  • Key Functionality: It enables both real-time monitoring and historical analysis of events.
  • Event Handling: It handles EMS messages, including those generated by the EMS subsystem itself (messages 513-999) and those from EMS distributors (messages > 1000).
  • Integration: Often used in conjunction with TACL (Tandem Advanced Command Language) for automated event management scripts. 

Detailed Historic Timeline and Evolution

EMSDIST has evolved alongside Tandem / Compaq / HPE NonStop systems, transitioning from basic console management to complex distributed management systems. 

1. The Tandem Guardian Era (Late 1970s – 1980s)

  • Context: The emergence of Tandem NonStop systems focused on continuous availability.
  • EMS Origins: Initial event handling was largely via console messages. As systems grew, the need to manage logs across multiple processors led to early Event Management Service components.
  • Role of EMSDist: Early distributors primarily moved messages from local collectors to a central console or tape log.

2. The D-Series & TMF Era (1990s)

  • Context: Introduction of sophisticated transaction monitoring and distributed databases.
  • 1996: A significant EMS Reference Summary was released (PN 114754), formalizing the structure of EMS collectors and distributors.
  • Capabilities: EMSDIST became capable of filtering high-volume events, separating critical errors from warning messages (513-1019).
  • Evolution: Began integrating with the Distributed Systems Management (DSM) suite for better network-wide event visibility. 

3. The Compaq & Integrity (J-Series/H-Series) Era (2000s – 2010s)

  • Context: Shift from MIPS-based processors to Intel Itanium (Integrity) servers.
  • 2003-2005: Integration with Windows-based management systems (DSM/NOW) and improvements to the Multi Event Viewer (MEV).
  • 2014: HP Integrity NonStop Operations Guides emphasized using EMSDIST alongside modern tools like OSM (Open System Management) Event Viewer, especially for H-Series and J-Series systems.
  • Key Capability: Improved handling of large logs, with better time-based querying (TIME and STOP options) for auditing and troubleshooting. 

4. The HPE NonStop X & Modern Era (2015 – Present)

  • Context: Adoption of x86 architecture and cloud-ready systems (L-Series).
  • 2015: HPE takes over the portfolio, accelerating integration with HPE InfoSight for AI-driven log analysis.
  • Modernization: While EMSDIST remains, modern environments heavily leverage NS Software Essentials and third-party tools for advanced analytics.
  • Continued Importance: EMSDIST remains essential for analyzing historical logs via the LOGFILE option, especially when dealing with cold-standby or restored logs from tape/disk. 

Key Functional Milestones

  • Message Categorization: Formalization of messages 513-999 (collectors) and >1000 (distributors) for structured analysis.
  • Filtering Efficiency: Implementation of complex FILTER parameters allowed operators to filter events by process, user, or time.
  • Logfile Access: The ability for EMSDIST to process archived or older LOGFILE entries independently of the live $0 collector.
  • Template Support: Ability to use specific =_EMS_TEMPLATES for customizable output formatting. 

HPE NonStop EMSDIST, Event Management Service Distributor Timeline by year

IT Mark Whitfield, SC Cleared Senior Project Manager

Mark Whitfield is a highly experienced SC cleared Senior IT Project Manager and Engagement Manager with over 30 years in the IT industry, specializing in both Agile and Waterfall delivery for large-scale blue-chip companies, digital projects, and payment systems. After starting as a programmer, he transitioned into project management, eventually working with Capgemini and establishing a professional templates resource site. 

SC cleared Senior IT Project Manager and Engagement Manager

IT Project Management Overview

  • Key Expertise: Senior IT Project Management (Agile / Scrum / Waterfall / PRINCE2), Delivery Management, Business Transformation, and SC clearance.
  • Sector Focus: Banking, Finance, Transportation (Heathrow, NATS), Retail, Government (Local Regional Government – LRG), Aerospace & Defence, and Gambling.
  • Technical Background: Programming in COBOL85, Tandem TAL, SQL, C, C++, Java, and experience with HPE NonStop (BASE24) systems.
Tandem TAL Programming certificate, 1995
  • Tools & Methodologies: PRINCE2, Agile SCRUM, Microsoft Project (MPP), Excel RAID logs, and Jira.
  • Value Proposition: Focuses on improving revenue, cost, and Customer Satisfaction (CSAT) through structured SDLC methodologies. 

Detailed Historical Timeline

Era 1: Programming & Technical Development (1990–1995) 

  • 1990: Graduated in Computing and joined The Software Partnership (later Deluxe Data) in Runcorn as a programmer specializing in electronic banking software (sp/ARCHITECT) on Tandem Computers (now HPE NonStop).
  • 1990-1995: Developed code (COBOL85/NonStop SQL) for major banks, including TSB, Bank of Scotland, Rabobank, and Girofon.
  • 1993 (May): Completed Tandem Guardian Principles Course.
Tandem Guardian Principles Course, 1993
  • 1994: Deluxe Electronic Payment Systems acquired The Software Partnership.
  • 1995 (June): Completed HP NonStop Performance Analysis and Tuning.
Deluxe Electronic Payment Systems acquired The Software Partnership in 1994
HP NonStop Performance Analysis and Tuning, 1995

Era 2: Specialized Software & Product Management (1995–2013) 

Insider Technologies Limited (ITL) in Salford Quays
  • 1995 (August): Joined Insider Technologies Limited (ITL) in Salford Quays as a senior programmer, later moving into product / project management.
  • 1995-2013: Focused on monitoring (Reflex) and batch scheduling (MultiBatch) software for HPE NonStop systems, serving clients like Barclays and Alliance & Leicester.
  • 2000 (May): Completed Microsoft Project ’98 Certification and began training other ITL project managers on scheduling best practices.
  • 2007: Insider Technologies products (Reflex) integrated into FIS solutions.
  • 2013: Published work in the HP NonStop journal “The Connection”. 
HPE NonStop journal “The Connection” – article for the Insider Technologies product, RTLX

Era 3: Senior IT Project Management (2013–2016) 

  • 2013-2014: Worked at Wincor Nixdorf as an IT Project Manager (PRINCE2 / Agile Scrum) on a £5m+ LBG Self-Service Software Replacement (SSSR) program for Lloyds Banking Group, migrating ATM systems from HP NonStop to AIX.
  • 2014-2016: Joined Betfred as a Senior Project Manager, delivering payment gateways, sportsbook, and virtual gaming projects in Agile SCRUM for mobile and online platforms. 

Era 4: Engagement Management & Public Sector (2016–Present) 

  • 2016 (January): Joined Capgemini UK as a client-facing Engagement Manager (SC cleared).
  • 2016 (August): Founded Mark Whitfield Consultancy Ltd, managing independent IT, network, and improvement projects.
  • 2016-2018: Led Waterfall / Agile projects for automotive, local government, and postal services.
  • 2018-2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
  • 2023-2024 (Nov-Feb): Served as Technical Delivery Manager for a UK Government account, overseeing a £1m+ Fish Export Service (FES) to Common Entry Health Document (CHED) Inspection Portal (CHIP) project.
  • 2026: Continued to provide project management thought leadership and template resources for Agile/Scrum/PRINCE2. 
Agile Scrum Burn down Chart template in Microsoft Excel
Microsoft Project MPP MSP Project Plan Template examples
Plan On a Page POaP templates plus MPP MS Project and MS Excel Project Plan templates

Key Projects & Clients

  • UK Gov / Capgemini: Fish Export Service (FES) Cloud Migration.
  • MuleSoft: Anypoint Platform.
  • Wincor Nixdorf/Lloyds: ATM/Self-Service Software Replacement.
  • Jaguar Landrover (JLR), Heathrow, Royal Mail Group, NATS, Euroclear: Various IT and Digital projects.
  • Banking: Rabobank, Barclays, HSBC, Bank of England, Standard Chartered. 

IT Mark Whitfield, SC Cleared Senior Project Manager

sp/ARCHITECT electronic banking by The Software Partnership TSP

sp/ARCHITECT was a pioneering electronic banking and funds-transfer software suite originally developed by the Runcorn-based firm The Software Partnership (TSP). Following its acquisition by the American firm Deluxe Electronic Payment Systems in 1994, the Runcorn office became the European hub for what was then rebranded as Deluxe Data. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP

Overview

The Runcorn operation specialised in high-availability, mission-critical banking software, specifically the sp/ARCHITECT-BANK product. This software was designed to run on Tandem Computers (now HPE NonStop), which were known for their fault-tolerant architecture. The “sp/ARCHITECT” platform was highly valued for its client-server design, allowing it to be adapted for various hardware brands, including Unix-based systems. 

Historical Timeline

  • Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. The company starts developing online banking systems in Timperley before moving to Runcorn.
  • 1990: The firm establishes itself at Norton House in Crowngate, Runcorn, focusing on electronic banking software for major clients like TSB and Bank of Scotland.
  • 1992: The Runcorn office relocates to Wingate House on Northway.
  • 1994: Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation) acquires The Software Partnership for an undisclosed sum. The acquisition is aimed at helping Deluxe expand its global presence and accelerate the use of the sp/ARCHITECT suite.
  • 1994–1995: The Runcorn office operates as Deluxe Data, providing software design, coding, and 24-hour support for international clients including Rabobank.
  • 2000: Following a series of corporate shifts, the company name changes to EFD eFunds.
  • 2007: By this year, the operation has transitioned to Fidelity National Information Services (FIS) and is based in Aegon House, Daresbury, Warrington. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP