The European BASE24 User Group (EBUG) was established in the 1980s as an independent, community-led organization for users of the BASE24 payment processing system developed by Applied Communications, Inc. (now ACI Worldwide).
Originally a regional forum for IT professionals in Europe to discuss HPE NonStop (Tandem) transaction monitoring and network security, the group expanded globally over time.
Insider Technologies regularly attended EBUG, booth in 2007 – RTLX now ETI-NET C-Deep
Following ACI’s withdrawal of direct corporate backing, EBUG evolved into “The Independent Group for All Payments System Users”—affectionately known as the Everybody Belongs User’s Group—welcoming users of multiple payment platforms like Postilion.
The detailed historical timeline of EBUG and the evolution of its core system, BASE24, outlines its development from a regional user collective to a global payments forum:
The Foundation Era (1975–1989)
1975: ACI is founded in Omaha, Nebraska, initially developing software for fault-tolerant Tandem NonStop computers to connect ATMs to bank networks.
1982: The BASE24 product family is officially launched globally, acting as “baseline” software for 24-hour financial operations.
1980s:EBUG is established as a regional European community for BASE24 users to collaborate on ATM networking and transaction processing.
Early 2000s: EBUG annual conferences grow in prestige, featuring technical tracks on BASE24 transaction logging, Point-of-Sale (POS) networks, and network resilience.
2007: EBUG hosts a high-profile international conference in Istanbul, Turkey.
2008: EBUG hosts its annual meeting in Vienna, Austria, which is historically noted as a pivotal year where ACI began supporting immediate payments in Europe and discussed a strategic shift toward IBM platforms. ACI officially announces the future retirement of “BASE24 Classic”.
2009: The conference is held in Prague, Czech Republic, maintaining strong community support for BASE24 on Tandem servers despite broader industry shifts.
Global Expansion, Rebranding & The Cloud Era (2010–Present)
2012: ACI introduces BASE24-eps, their next-generation, platform-independent payments engine designed to replace the legacy BASE24 on HPE NonStop. EBUG’s technical focus shifts to real-time payments and log extraction.
2013: With ACI ending direct involvement, the user group officially rebrands as the “Everybody Belongs User’s Group” at their conference in London, expanding attendance to professionals from Mexico, South Africa, and Australia.
2015: ACI celebrates 40 years in payments. EBUG solidifies its status as a supplier-agnostic payments forum, opening sessions to non-BASE24 users.
2020s: With BASE24 Classic retired, legacy users migrate to modern systems like BASE24-eps for cloud deployments and immediate payments.
Recent Years: ACI goes live as a pioneer in the Federal Reserve’s FedNow Service, building upon the decades-long transaction switching architecture first developed in the 1970s and 1980s.
European BASE24 User Group (EBUG) Timeline from Inception
Focus: Electronic banking programming and development on Tandem Mainframe Computers.
Projects: Wrote, developed, and maintained software like sp/ARCHITECT-BANK and associated billing software (in Poole, 1993). This involved building early electronic banking systems for desktops long before internet banking was prevalent.
Location: Insider Technologies, Salford Quays, Manchester, UK
Focus: NonStop product management, software design, and real-time event monitoring.
Projects: Product managed software lifecycles for four monitoring products (two NonStop based). This included creating health and diagnostic tools (RTLX, Reflex 80:20, Reflex ONE24,XPERT24) for mission-critical NonStop environments. He also deployed volume testing on early HP NonStop S7000 nodes for CRESTCo in London in 1997.
Insider Technologies, Salford Quays, Manchester, UK
Location: Wincor Nixdorf & ATM/POS Financial Services, UK
Focus: Modernization and migration of legacy systems.
Projects: Managed a £5M+ replacement of legacy HP NonStop software systems at a large UK retail bank, migrating functionalities to AIX-based J2EE and Oracle architectures.
Focus: Delivery of enterprise-scale middleware, digital transformation, and cloud.
Projects: Acts as an Engagement Manager and SC-Cleared Project Manager. Focus includes Agile software delivery for Air Traffic organisations (e.g., iOS applications for military and public-facing airspace tracking) and rolling out middleware solutions.
BASE24 is an enterprise-grade electronic funds transfer (EFT) software suite developed by Applied Communications Inc. (now ACI Worldwide). It handles real-time transaction acquiring, authenticating, routing, switching, and authorization across ATMs, Point-of-Sale (POS) networks, and digital payment channels.
XPNET (Exchange Protocol Network) is the fundamental communications middleware layer designed explicitly for BASE24 on fault-tolerant systems. It acts as an abstraction layer managing interprocess communications (IPC), network protocols (e.g., Bisync, X.25, TCP/IP), line management, device messaging, and high-volume transaction routing. Together, they form the transactional backbone for a majority of the world’s top financial institutions.
RTLX Reactor (in 2012) for tracking BASE24-eps & BASE24 XPNET transactions
Deep-Dive Architecture and Technology Stack
1. BASE24 Core Design
Process Pair Architecture: Designed natively around Tandem’s process pairs. A Primary Process performs the active transaction switching while a Backup Process remains synchronized in a standby state. If the hardware or primary process fails, the backup takes over instantly with zero data loss or session drops.
Functional Modules: Divided into specific transactional entities:
ATM (Automated Teller Machine Device Handler): Direct control and state management of physical terminals using custom message streams (e.g., Diebold, NCR).
POS (Point of Sale): Merchant terminal management and merchant accounting integration.
Auth (Authorization Processor): Internal validation scripts against account records or stand-in limits.
2. XPNET Middleware Engine
Line and Station Infrastructure: XPNET maps communication through abstract configurations. A Line represents a physical or logical network pipe, and a Station represents an endpoint (e.g., an interchange gateway or terminal node).
Dynamic Load Buffering: Employs internal memory queue structures to absorb traffic spikes from international card networks (such as Visa and Mastercard) without spilling into disk storage.
Protocol Multi-threading: It decouples low-level link dynamics (e.g., CRC checking, dropouts) from core business logic, converting legacy and modern network formats into standardized internal transaction tokens.
Application Development Timeline & Political Breakdown
The timeline below details how geopolitical, regulatory, and corporate ownership developments directly shaped versioning and core code changes in BASE24 and XPNET.
Era 1: The Tandem & Expansionist Era (1975–1992)
Geopolitical & Industry Context: The rise of consumer credit card networks, personal checking accounts, and the physical expansion of banking via ATMs. Regional networks were fragmented, necessitating specialized software to cross-connect them.
Corporate Dynamics: Applied Communications Inc. (ACI) operated as an independent software house in Omaha, Nebraska, forming a deep partnership with Tandem Computers before being acquired by US West (1988) and later Tandem directly (1991).
Year-by-Year Code & Technical Milestones:
1975–1981: Initial exploration of high-availability banking systems on Tandem NonStop computers. Developers laid the groundwork using Tandem Screen COBOL and low-level communication drivers.
1982:BASE24 v1.0 officially launches. The original codebase was written in TAL (Tandem Application Language), a high-performance, structured system programming language designed specifically for NonStop systems.
1985: A primitive version of XPNET is spun out from early shared-memory messaging code to support multi-protocol lines (Bisync, Async) without forcing restarts of the core application.
1987: Introduction of early ISO 8583 message formatting engines within the core routing code. This allowed the software to natively interpret standard financial messaging frames across distinct interbank networks.
1991: Tandem acquires ACI. Code refactoring focused heavily on optimizing interactions with Tandem’s native file system (Enscribe) and expanding the XPNET process memory layout to take advantage of new Tandem CLX architecture performance.
Era 2: The TSA Corporate & Public Market Era (1993–2000)
Geopolitical & Industry Context: Globalization of financial services, the consolidation of national card switches, and the commercial explosion of internet banking and POS devices.
Corporate Dynamics: Tandem divested ACI to a private holding company, leading to the creation of Transaction Systems Architects (TSA) in late 1993. TSA went public on NASDAQ in 1995, pushing development velocity to meet Wall Street expectations.
Year-by-Year Code & Technical Milestones:
1993–1994: Standardized compilation routines moved to Tandem’s pTAL (portable TAL) to bridge code execution compatibility between older CISC-based architectures and the newly emerging MIPS RISC processors.
1995–1996: BASE24 version 4.x introduces advanced multi-institution handling inside a single logical codebase, allowing multi-tenant processing for third-party credit card consolidators.
1997: Release of BASE24 v5.x, featuring significant expansions in XPNET (v2.x) to accommodate native TCP/IP sockets alongside aging X.25 line infrastructures.
1998–1999: Heavy investment into Y2K compliance remediation. Code changes involved updating binary-coded decimal (BCD) date configurations, expanding date-storage windows across Enscribe files, and deploying the BASE24 Year 2000 System Assessment frameworks globally.
Era 3: Enterprise Platform Shift & Consolidation (2001–2014)
Geopolitical & Industry Context: Post-9/11 regulatory changes (e.g., USA PATRIOT Act), the implementation of modern security standards like Triple DES (TDES), and the birth of the PCI-DSS (Payment Card Industry Data Security Standard). Mainframes and alternative hardware processors (IBM, HP-UX) became fierce competitors to Tandem.
Corporate Dynamics: TSA officially rebranded to ACI Worldwide, Inc. (ACIW) in 2007. A strategic decision was made to rewrite the platform to break vendor lock-in and provide cross-platform flexibility.
Year-by-Year Code & Technical Milestones:
2001–2002: Standard cryptographic layers within BASE24 are systematically modified to enforce Triple DES compliance across automated teller machines.
2003: ACI introduces BASE24-eps (Enterprise Payments System). This marked a foundational architecture shift, moving away from TAL/pTAL entirely to an object-oriented paradigm written in C++ and designed to execute cross-platform (HPE NonStop, IBM z/OS, AIX, Linux).
2005–2006: BASE24-es/eps code integrates with enterprise middleware layers such as IBM WebSphere MQ, using CICS containers on z/OS to deliver modern service-oriented architecture (SOA) web services wrappers.
2008–2010:ACI shocks the banking industry by announcing the sunsetting of standard maintenance for classic Tandem NonStop BASE24 by late 2011. Millions of lines of legacy TAL code are effectively frozen, forcing major migrations toward BASE24-eps.
2011–2013: Code enhancements center around PA-DSS validation and securing encryption pathways to ensure tokenized processing. XPNET 3.x is deployed onto newer HP Integrity Itanium-based J-Series and H-Series blades.
Era 4: Modernization, Cloud-Native, and Open Systems (2015–Present)
Geopolitical & Industry Context: The dominance of Real-Time Payments (RTP, FedNow, ISO 20022 formats), cloud computing mandates, and aggressive cost-reduction pushes away from high-maintenance legacy hardware configurations.
Corporate Dynamics: ACI pivots sharply to open-ecosystem SaaS delivery, cloud partnerships (AWS, Microsoft Azure, Google Cloud), and co-development with IBM to optimize cross-platform throughput.
Year-by-Year Code & Technical Milestones:
2015–2016: BASE24-eps code is successfully ported to Red Hat Enterprise Linux (RHEL) on standard x86 processors. This architectural pivot offered a reduction in total cost of ownership (TCO) compared to legacy hardware by providing massive processing scaling.
2018–2020: The introduction of standard ISO 20022 messaging libraries into the switching matrix to support instant transaction settlement schemes globally.
2021–2024: Legacy middleware systems are phased down. Modern releases feature direct REST API hooks, cloud-adaptor hooks, containerised microservices integration, and extended configuration capabilities via the ACI Desktop GUI.
2025–2026: ACI partners with IBM to launch native 64-bit deployment optimizations for BASE24-eps running on IBM Z mainframes (including z16/z17 configurations), incorporating hardware-driven AI fraud analysis models and full PCI-SSF (PCI 4.0) certification.
Overview of BASE24 and XPNET plus application timeline by era
The core electronic banking software product sp/ARCHITECT-BANK was originally developed by The Software Partnership (TSP), a highly specialized British software house co-founded by Nigel Walsh in Runcorn, Cheshire.
Engineered to deliver high-availability, fault-tolerant electronic and desktop home-banking services, it ran natively on Tandem NonStop mainframe computers (now HPE NonStop).
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
Over the decades, the product evolved through major corporate acquisitions, eventually being integrated into enterprise-level banking suites like CONNEX Advantage under eFunds and FIS.
🌅 Era 1: The Inception and Independent Software House Era (Mid-1980s–1993)
During this foundational era, The Software Partnership engineered the core product from scratch to meet the emerging demand for “Direct Electronic Banking” before the commercial internet became prevalent.
1985: The Software Partnership (TSP) is co-founded by Nigel Walsh in Runcorn, Cheshire. Development begins on a standard product architecture designed specifically for the transaction processing monitor (PATHWAY) and operating system (Guardian) of Tandem Computers.
1988–1989: The company establishes sp/ARCHITECT (and its core module, sp/ARCHITECT-BANK) as a premier client-server base package for corporate and home-office electronic banking.
1990: The engineering team scales up to build standard product releases written in COBOL85 and utilizing NonStop SQL databases. They develop proprietary testing utilities like sp/TESTBED to simulate PC-to-mainframe interfaces. Mark Whitfield joins the company after graduating in Computing in late 1990.
1991: Major deployment begins for the high-profile Barclays Business Master II (BBM II) desktop corporate banking application, with TSP placing teams (including Mark Whitfield) on-site at Barclays in Knutsford, Cheshire.
Barclays, Radbroke Hall, Knutsford, Cheshire
1992: A batch billing and invoicing suite of modules is engineered over 3-months and appended to the Barclays installation at Poole, Dorset. Mark Whitfield is assigned to this HPE NonStop (Tandem) billing/ invoicing development on the UK south coast. Simultaneously, TSP expands internationally into continental Europe.
Barclays, Wimborne Road, Poole, Dorset
1993: TSP develops an automated, touch-tone voice menu system for Girofon (Denmark). The code interfaces phone lines through Periphonics Interactive Voice Response (IVR) hardware directly into the back-end Tandem banking system. Concurrently, the core application handles desktop money transfers and early logic checking for clearing giants TSB and Bank of Scotland. Mark Whitfield is also involved with supporting this IVR technology.
🤝 Era 2: The Deluxe Data International Era (1994–1999)
Recognizing the massive European banking client footprints of sp/ARCHITECT, US-based electronic funds transfer (EFT) specialist Deluxe Data acquired TSP to merge their direct banking and card processing capabilities.
1994: Deluxe Data Corporation acquires The Software Partnership. The Runcorn offices are reorganised as Deluxe Data International Operations.
Deluxe Data International Operations, Wingate House, Northway
1995: The product undergoes heavy code optimization to satisfy customer acceptance loops for international clearers, notably deploying direct electronic banking solutions for major Dutch institutions like Rabobank. Mark Whitfield moves on from Deluxe Data (after 5 years) to Insider Technologies Limited in Salford Quays in late 1995. This to continue HPE NonStop programming work for both monitoring and diagnostic products like Reflex 80:20.
1996: Development transitions toward hybrid enterprise networking. The sp/ARCHITECT system is updated with custom TCP/IP software interfaces to allow newer mid-range UNIX servers (such as IBM RS/6000) to safely communicate with the core Tandem server environment.
1997: Deluxe Data expands the core platform’s messaging logic using Tandem’s Remote Server Call (RSC) facility. This enables early Windows NT operating systems to request live financial data from the sp/ARCHITECT host.
1998: An automated, multi-process file transfer protocol is integrated natively into the bank database, leveraging Connect:Direct transport layers to securely transfer corporate SWIFT financial data files.
🚀 Era 3: The eFunds & Corporate Consolidation Era (2000–2006)
Deluxe Data’s technologies spun off into a new corporate entity called eFunds Corporation, altering the delivery model of the legacy software.
2000: Deluxe Electronic Payment Systems officially merges with other divisions to form eFunds Corporation (EFD). The sp/ARCHITECT package becomes a core pillar of eFunds’ international banking portfolio.
2002–2004: To modernise the transaction handling backbone, components of the sp/ARCHITECT platform are refactored. The system’s underlying communication routing is systematically aligned with CONNEX, a dominant market-leading Electronic Funds Transfer (EFT) processing engine.
2005–2006: eFunds transitions the direct client-server software layers into highly secure corporate portals, providing the foundational logic for what would eventually be rebranded as the CONNEX Advantage banking solution.
🏢 Era 4: The FIS Integration and Legacy Modernisation Era (2007–Present)
The final stage of the product timeline represents its absorption into global banking infrastructure software, where its high-availability DNA remains active in institutional transaction environments.
2007: Financial technology behemoth Fidelity National Information Services (FIS) acquires eFunds Corporation for approximately $1.8 billion. Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.
Fidelity National Information Services (FIS) Aegon House, Warrington (in 2007)
2010: FIS fully absorbs the remaining codebase, utilizing its core Tandem architecture algorithms to fortify transaction processing stability.
2015–2020: The architectural concepts pioneered by sp/ARCHITECT-BANK continue to govern high-volume legacy systems. The logic stays preserved in COBOL85 code bases running on modern HPE Integrity NonStop (Intel Xeon-based) fault-tolerant environments.
2020s–Present: Modern banking infrastructures gradually migrate from the classic database frameworks toward microservice configurations and open-banking APIs. However, the core system layout remains a primary point of historical reference for designing high-throughput, 24/7/365 fault-tolerant banking systems.
sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire
sp/ARCHITECT-BANKCode Evolution Timeline
The timeline below details how the code’s core design, language implementations, and application deployment strategies transformed by era and year.
1. The Monolithic & TAL Foundation Era (1980s – Early 1990s)
During this era, the application focus was strictly high-throughput, fault-tolerant electronic funds transfer (EFT) and point-of-sale (POS) switching systems natively built for Tandem Guardian environments.
Late 1980s: The core design of sp/ARCHITECT is established using TAL (Tandem Application Language). Applications are deployed as single-system monoliths. Code optimization focuses heavily on low-level bit manipulation and message structuring to survive CPU or inter-process failures without losing in-flight transactions.
1991–1993: Structuring of modular execution libraries. Early iterations of the codebase segment transaction processing routes from core database logging routines. The introduction of Tandem’s newer NonStop SQL forces early integration layers to transition from standard unstructured unstructured file systems (Enscribe) to early relational tracking.
2. Distributed Client/Server & pTAL Migration Era (Mid 1990s – Early 2000s)
The architectural demands shifted from single-frame monoliths toward distributed banking systems, giving rise to “Distributed Monoliths” and client/server network structures.
1995–1996: Hardware evolutions transition from the older CISC-based Tandem systems to RISC architectures (MIPS processors). sp/ARCHITECT undergoes a massive compilation shift to pTAL (portable TAL) to preserve legacy code performance across new instruction sets.
1998–1999: Tandem’s acquisition by Compaq pushes the software suite to handle open standard protocols. The application code begins abstracting system calls to prepare for broader networking interfaces.
2001–2003: Deluxe Data / eFunds eras. The code sees the introduction of C/C++ wrappers around the legacy pTAL components. Systems are decoupled into a clear 3-Tier architecture: front-end terminal networks, back-end pTAL transactional engines, and standardized clearing houses.
3. Open Systems, Modern Middleware, & Java Integration Era (Mid 2000s – 2010s)
Following HP’s acquisition of Compaq and subsequent software realignments, the sp/ARCHITECT codebase was re-engineered to prevent vendor lock-in and adopt modern enterprise standards.
2005–2007: Java is introduced into the sp/ARCHITECT ecosystem. New application modules, specifically merchant portal interfaces and settlement reporting tools, are written entirely in Java and run via OSS (Open System Services) environments.
2010–2012: FIS acquisition era integration. Legacy pTAL code blocks are systematically refactored or heavily wrapped in C++ using object-oriented principles to ensure long-term maintenance. The transaction routing engine is altered to support early SOA (Service-Oriented Architecture) paradigms via web-services hooks.
2015–2018: Mainstream deployment of COB (Core Banking) standard formats within the application layer. The system moves away from old proprietary network messaging layouts to ISO 20022 compliance frameworks, utilizing dedicated conversion engines native to the sp/ARCHITECT stack.
4. Modern Cloud-Adjacent & Hybrid Infrastructure Era (2020s)
The current evolutionary footprint centers on maintaining the absolute sub-millisecond reliability of the core architecture while exposing capabilities to dynamic cloud endpoints.
2021–2023: Modernization of the application payload. High-performance micro-frontends handle real-time fraud monitoring and data streaming using asynchronous event-driven pipelines (e.g., Kafka event consumers interfacing directly with the NonStop core runtime environments).
2024–2026: Transition to containerized orchestration and cloud-adjacent infrastructure. The sp/ARCHITECT footprint utilizes x86-based virtualized NonStop systems (NSX), enabling legacy core modules (derived from the original TAL logic) to execute seamlessly on modern virtual environments alongside Linux-based multi-tenant applications.
Insider Technologies Limited is a specialized UK-based software house and service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions for business-critical, 24/7 mission-critical architectures. I worked at ITL in Salford Quays from 1995 through to 2013.
Attending an EBUG conference (European BASE24 User Group)
Foreground, attending a British Isles TANDEM User Group (BITUG)
Insider Technologies Limited (website author in 2009)
CompanyOverview
🏢 Corporate Identity & Status
Legal Name: Insider Technologies Limited
Founded:27 February 1989
Headquarters: Manchester, UK (Albert Street, Eccles)
Ownership: Operating as a private independent software company, recently integrated as part of PartnerOne.
Strategic Partnerships: Certified Microsoft Gold Partner for Application Development and long-standing Hewlett Packard Enterprise (HPE) partner.
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
🌐 Core Domain & Industries Served
The company delivers real-time, event-driven diagnostic, tracking, and compliance middleware solutions across three main highly-regulated global verticals:
Government & Defence: Secure enterprise military messaging tracking and digital evidence handling.
Telecommunications: Tracking data traffic and critical infrastructure middleware.
🛠️ Core Technology Stack & Competencies
Insider Technologies specializes in niche high-availability operating environments—specifically HPE NonStop (historically Tandem Computers and HP NonStop) running Guardian and Open System Services (OSS) environments—alongside enterprise Windows, Linux, and Unix systems. Their expertise spans database transaction management, BASE24 XPNET monitoring, IBM WebSphere MQ tracking, and low-level development (SQL, TAL, TACL, COBOL85, C++, Pathway).
Insider Technologies – Core products in 2003
In-Depth Product & Political-Technical Timeline
This timeline breaks down how Insider Technologies evolved its software suite. It demonstrates how their technical development directly responded to shifting geopolitical landscapes—ranging from late-Cold War military messaging security to post-9/11 financial regulations and modern European cloud autonomy initiatives.
🔹 The Foundation & Legacy Tandem Era (1989–1999)
Political Context: The final years of the Cold War and the 1990s globalization boom demanded high-security, fault-tolerant mainframes for NATO-aligned military communications and early global banking clearing networks.
Technical Context: Tandem Computers dominated the un-interruptible 24/7 market. Software was required to monitor these platforms without causing processing overhead.
1989
Company Incorporation: Insider Technologies is incorporated in the UK to engineer bespoke software for highly robust technical ecosystems.
1990–1995
Reflex (Core Release): Release of Reflex, a foundational service management and real-time transaction diagnostic tool built specifically for the Tandem Guardian operating system.
1996–1999
MultiBatch Software: Further Develop and Extend MultiBatch to orchestrate and safely automate complex batch processing on Tandem machines alongside the evolution into HP NonStop computing frameworks.
Y2K Compliance Focus: Technical adjustments were deployed across Reflex and MultiBatch to assure financial institutions that automated transaction logging would not fail during the millennium rollover.
🔸 The Multi-Platform & Financial Compliance Era (2000–2015)
Political Context: Following the September 11 attacks, global anti-money laundering (AML) and counter-terrorism financing (CTF) frameworks heavily expanded. Financial regulators demanded exact, audible end-to-end payment tracking.
Technical Context: Enterprises began migrating away from single-architecture mainframes toward heterogeneous IT environments, requiring tools that could jump across Windows, Unix, and Linux simultaneously.
2002–2004
Sentra Development: Launch of Sentra, expanding the firm’s portfolio beyond HPE NonStop into cross-platform environment monitoring for Windows, Linux, and Unix systems.
Reflex 80:20 & Reflex ONE24: Advanced variations of the Reflex tracking system were built to cater to specialized real-time electronic payment flows like BASE24 with XPNET.
2005–2010
RTLX Reactor (page 12) and Middleware Monitoring: The release of RTLX Reactor provided message tracking capabilities tailored for IBM WebSphere MQ, allowing institutions to trace various payment and other data through complex middleware chains.
Corporate Structuring: The creation of Insider Technologies (Holdings) Limited reinforced corporate expansion as the company deepened its footprint in secure military messaging for government defense bodies.
🔹 The Cyber Autonomy & Sovereignty Era (2016–Present)
Political Context: Escalating nation-state cyber warfare, strict GDPR regulations, and the UK/EU push for technological sovereignty and domestic digital ecosystem resilience heightened the reliance on trusted, onshore technology suppliers.
Technical Context: High-threat environments demand zero-trust visualization, time-accurate logging across digital evidence files, and advanced protection against internal exfiltration vectors.
2019
30-Year Milestone & Modernization: The company celebrates its 30th year, accelerating development on modern mobile application extensions to permit real-time, remote secure alerts for operations teams.
2022–2025
PartnerOne Integration: Insider Technologies aligns its operations under the PartnerOne portfolio, preserving its UK identity while supercharging its enterprise-scale data infrastructure solutions.
Corporate Integration combines Insider’s expertise with PartnerOne’s portfolio to deliver advanced analytics and secure messaging systems to banking, defence, and telecommunications markets.
Defense and Public Safety Porting: Technical deployment of specialized capabilities covering digital evidence security, timekeeping tracking, and legacy virtualization modules aimed explicitly at helping the UK Government maintain its historical tech stacks safely.
RTLX Reactor (in 2012) for tracking BASE24-eps & BASE24 XPNET transactions
Insider Technologies Limited (ITL), Company Overview and Timeline by Year
The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;
BASE24 is a market-leading, fault-tolerant Electronic Funds Transfer (EFT) software application developed by ACI Worldwide. For decades, it has served as the backbone for global banking, processing billions of ATM, Point of Sale (POS), and smart card transactions.
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
The product achieves its landmark 24/7/365 uptime by running natively on the HPE NonStop architecture—originally engineered by Tandem Computers.
1. Underlying Technology Stack
BASE24 Classic was built from the ground up to utilize the unique properties of the Tandem/HPE NonStop platform:
Database:Enscribe, a native hierarchical/flat file database optimized for ultra-fast, unstructured file access. Newer iterations use NonStop SQL/MX.
Programming Languages: Primarily TAL (Tandem Application Language), pTAL, and COBOL/SCOBOL.
Middleware:PATHWAY (PATHCOM), which acts as the transaction processing monitor to dynamically manage and load-balance server processes.
2. High-Level Component Architecture
BASE24 relies on an interconnected network of specialized processes that route and manage messages.
A. XPNET (The Networking Engine)
XPNET is a critical, proprietary communication subsystem. It provides the messaging infrastructure where applications interface with network communication lines. XPNET acts as the buffer layer, monitoring physical lines, enforcing transaction timing checks, and distributing data loads uniformly across CPUs.
B. Device Handlers (DH)
Device Handlers act as the translators for peripheral devices.
Function: They intercept hardware-specific protocol messages (e.g., Diebold or NCR formats from ATMs) and normalize them into BASE24’s internal standard message format.
Security: DH processes handle terminal-level PIN encryption, coordinate MAC (Message Authentication Code) keys, and initiate terminal downline loads.
C. Authorization Process (AUTH)
AUTH is the core decision engine of the application.
Function: It validates card restrictions, tracks card usage accumulations, and performs transaction risk checks.
Fallback Management: If a bank’s core system goes offline, AUTH drops into “Stand-Alone” or “Negative/Parametric Authorization” mode, approving transactions locally up to safe, pre-defined limits.
D. Host Interfaces (HI)
The Host Interface connects BASE24 to the financial institution’s primary backend core banking systems. It handles “On-Us” transactions—meaning the card used belongs to the bank owning the terminal.
E. Interchange Interfaces (II)
The Interchange Interface formats, translates, and routes transactions to global credit/debit networks (such as Visa, Mastercard, AMEX) or regional switches. It transforms internal BASE24 data formats into compliance standard formatting, such as ISO 8583. It handles “Not-On-Us” transactions.
3. Core Database & File Structure
BASE24 captures system activities across specialized transactional and tracking files, mostly utilizing Enscribe:
TLF (Transaction Log File): The primary log capturing every ATM event, amount, response code, and terminal ID in real-time.
PTLF (POS Transaction Log File): Mirrors the utility of the TLF, but optimizes records strictly for merchant POS transactions.
LCONF (Logical Network Configuration File): Dictates how network configurations, devices, institutions, and communication paths map into XPNET.
CAF (Cardholder Authorization File): Stores specific card numbers, limits, and statuses used for stand-alone authorization if host links break down.
4. Daily Operational Processes
Beyond live message switching, BASE24 executes several critical back-office operations:
Extract: Periodically filters transaction data from live TLF/PTLF logs to move to external billing arrays.
Refresh: Downloads updated data dumps (such as blacklisted cards or updated balances) from core hosts into local BASE24 database files.
Settlement Initiator: Aggregates transaction volumes at specified cutoff times to reconcile balanced records between ATMs, POS terminals, and clearing networks.
5. Why Tandem/HPE NonStop is Essential to BASE24
BASE24 relies on the hardware/software synergy provided by HPE NonStop to achieve near-zero downtime:
Shared-Nothing Architecture: Processors operate independently with their own memory stacks. If a physical CPU suffers hardware failure, it cannot corrupt the rest of the application.
Process Pairs: BASE24 components operate via a primary process in one CPU and a backup process in an alternate CPU. The primary constantly syncs checkpoint data with its backup. If the primary drops, the backup assumes processing instantly without interrupting transaction flights.
Active/Active Configuration: Utilizing replication software like HPE Shadowbase or DRNet, financial firms link distinct geographic NonStop locations. Both processing sites operate concurrently, managing localized transactions and replicating states reciprocally.
6. Product Evolution: BASE24 Classic vs. BASE24-eps
ACI Worldwide evolved the platform from BASE24 Classic into BASE24-eps (Enterprise Payment System):
Product Evolution: BASE24 Classic vs. BASE24-eps
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.
Detailed List of NonStop Programming Languages
1. Core Proprietary & System Languages
TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.
2. Enterprise & Enterprise Legacy Languages
COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.
3. Standard Mainstream Languages
C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.
4. Modern Open-Source Options
Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.
Detailed Timeline Breakdown by Era and Year
The evolution of NonStop languages maps directly across distinct engineering ownership eras.
The Proprietary Foundation Era (Tandem Computers: 1974–1989)
1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.
The Open Systems & Hardware Transition Era (Compaq: 1990–2001)
1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.
The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)
2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.
The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)
2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.
HPE NonStop Tandem Programming Languages and Development Timeline
HPE NonStop Pathway is a premier transaction processing and application server environment (TS/MP) that powers mission-critical Online Transaction Processing (OLTP). It handles critical application services—such as fault tolerance, load balancing, memory management, and process scheduling—automatically, allowing developers to focus strictly on business logic.
HPE NonStop Pathway is a transaction processing & application server environment (TS/MP)
Detailed Timeline Breakdown
The history and evolution of the Tandem NonStop platform and its Pathway environment span decades of architectural transformations and corporate ownership, categorized by distinct hardware and software eras:
1. The Tandem Era (1974–1997)
1974: Tandem Computers Inc. is founded by Jimmy Treybig to build the first fault-tolerant commercial hardware.
1976: The first Tandem NonStop system (NSI) is launched. Early apps had to be manually coded for fault tolerance.
1981: NonStop II is released, bringing 32-bit addressing.
1983: The Transaction Monitoring Facility (TMF) is introduced. Together with the launch of the Pathway transaction management software, the need for programmers to write manual fault-tolerance logic into their code is officially eliminated.
1986: Tandem releases the EXT as an entry-level system, followed by the VLX.
1991: Tandem introduces the Cyclone/R and initiates a massive architectural shift away from proprietary stack machines towards MIPS RISC processors.
1997: Compaq acquires Tandem Computers, placing the NonStop product line under its umbrella.
2. The Compaq & Early HP Era (1997–2014)
2001–2002: Hewlett-Packard (HP) merges with Compaq. The platform is rebranded as HP NonStop.
2005: The HP Integrity NonStop (TNS/E) series is introduced, migrating the fault-tolerant platform to Intel Itanium microprocessors. Pathway continues to be the main driver for high-volume banking and telecom applications.
2011: Further hardware advancements lead to the release of HP Integrity NonStop BladeSystems.
3. The Modern HPE Era (2015–Present)
2015: Hewlett-Packard splits, and the NonStop environment transitions to Hewlett Packard Enterprise (HPE).
2015/2016: Introduction of NonStop X (TNS/X) systems, marking the platform’s migration to standard Intel x86-64 processors and adopting InfiniBand interconnects. Pathway capabilities are updated to span dynamic server classes across multiple systems (Pathway Domains).
Present: HPE continues to modernize the NonStop architecture, integrating the platform with HPE GreenLake for consumption-based models and providing native support for modern DevOps tools and hybrid cloud deployments.
Mark Whitfield is an SC-cleared Senior IT Project and Engagement Manager with over 30 years of experience. His career spans from early mainframe programming to leading multi-million-pound cloud migrations and digital transformations for major financial, utility, and government clients.
The chronological breakdown of his professional project portfolio, structured by his definitive career eras, is detailed below:
1. The Technical Era (1990–1995)
During this foundational era, Mark worked as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data in 1994). He focused strictly on the development, optimization, and deployment of the sp/ARCHITECT-BANK electronic banking solution on Tandem Mainframe Computers.
Details: Handled the custom design and backend coding for a high-profile desktop electronic business banking application.
Project: Automated Touch-Tone Phone Banking Suite
Year: 1992–1993
Client: Girofon (Denmark)
Budget: Client-retained vendor contract
Details: Coded automated, menu-driven voice solutions operating on a Periphonics VRAM device to fetch live customer balances directly from mainframes.
Project: Early Digital Inter-Account Transfers
Year: 1993–1994
Client: TSB & Bank of Scotland
Budget: Internal product development
Details: Directed logic design and mainframe coding to support pioneering inter-account electronic funds transfers.
Project: International Banking Optimization
Year: 1994–1995
Client: Rabobank
Budget: Vendor-driven custom development framework
Details: Managed localized software optimization, custom patches, and deployment testing for global banking operations.
2. The Infrastructure & Monitoring Era (1995–2014)
Mark transitioned into a Product and Project Manager role at Insider Technologies Limited (and later a brief stint at Wincor Nixdorf). His focus shifted heavily toward platform diagnostics, high-availability transaction monitoring, and financial hardware software integrations.
Project: Reflex (Reflex 80:20) System Co-Development
Year: 1995–2004
Client: Multiple Tier-1 Investment Banks (including Euroclear/Crestco, Bank of England, and Deutsche Bank)
Budget: Part of a broader £3M Management Buyout (MBO) product portfolio
Details: Acted as Senior Programmer and Technical Lead to co-develop diagnostic monitoring modules for high-availability mainframes.
Details: Managed the integration of transaction tracking across ATM networks using ACI’s XPNET and HP NonStop architecture.
Project: Legacy ATM Software Modernisation
Year: 2013–2014
Client: Major UK Retail Bank (via Wincor Nixdorf Professional Services)
Budget: Corporate financial service transformation
Details: Served as Project Manager executing the swap-out of outdated, legacy ATM client systems for modernized software stacks.
3. The Digital and Cloud Era (2014–Present)
This era highlights Mark’s leadership of large-scale Agile and Waterfall digital delivery frameworks, moving from corporate gambling technology to complex, high-budget UK public sector programs.
Project: Mobile & Online Gaming Sportsbook Platforms
Details: Led Agile Scrum development teams to upgrade payment gateways, implement fraud detection, and roll out football/horse racing mobile interfaces.
Project: National Air Space Real-Time Mobile Applications
Year: 2016
Client: NATS (UK-wide Air Traffic Organisation)
Budget: Corporate custom applications initiative
Details: Managed the secure Agile delivery of Apple iOS applications displaying live military and public airspace information.
Project: Core Systems Interface Data Centre Migration
Year: 2016 (May–October)
Client: Royal Mail Group (RMG) / Postal Services
Budget:£4.3 Million
Details: Led a massive cross-functional team of 90 Capgemini engineers to migrate over 1,100 platform data interfaces ahead of peak annual trading.
Project: Automated Call Centre CCaaS Telephony Implementation
Year: 2017 (May onwards)
Client: Local Regional Government
Budget:£400,000
Details: Deployed a programmatic dialler system linked with Microsoft Azure CRM to facilitate the “Support for Mortgage Interest” campaign.
Project: Automotive Online Car Sales and Digital Readiness
Year: 2017 (October)
Client: Jaguar Land Rover (JLR) / Aston Agile Delivery Centre
Budget:£1.1 Million (Split into a £670k Customer Sales Portal and a £430k Readiness project)
Details: Engagement Manager implementing a new-car ecommerce vehicle pipeline.
Budget:£1 Million+ (Part of a larger £13.5M cloud program moving 130 apps)
Details: Orchestrated the launch and configuration of Azure Cloud frameworks migrating 12 historical Dynamics 2016 platforms to Dynamics 365 Online.
Project: Fish Export Service (FES) to CHIP Inspection Portal
Year: 2023–2024 (Nov–Feb)
Client: UK Government / Northern Ireland Trading Framework
Budget:£1 Million+
Details: Served as Technical Delivery Manager directing Agile Scrum teams to build cloud-hosted APIs supporting catch verification under the Windsor Framework.
The HPE NonStop Technology & Business Conference (Nonstop TBC 2026)—hosted by Connect Worldwide—will take place from September 14 to September 17, 2026, at The Rosen Plaza in Orlando, Florida.
This signature annual event brings together enterprise IT leaders, software engineers, and solution architects to explore innovations shaping mission-critical environments.
Core Event Schedule
The four-day conference partitions its educational and collaborative tracks as follows:
September 14: Dedicated exclusively to HPE Education Day, featuring expanded deep-dive technical pre-conference courses.
September 15–17: The primary conference technical program and breakout sessions.
Key Focus Areas & Tracks
The 2026 event focuses heavily on bridging mission-critical legacy stability with modern software frameworks:
AI-Driven Transformation: Adapting continuous availability to the demands of modern artificial intelligence and machine learning workloads.
Digital Resilience & Security: Mitigating modern risks, modernising backup systems, and maintaining absolute runtime security.
FinTech & Payments: Real-world operational strategies from global peers managing transaction-heavy workloads.
Expanded Business Track: New for 2026, this track aligns executive business drivers with technical architectures for practical IT roadmap building.
Logistics and Pricing
Venue: The Rosen Plaza Hotel, situated at 9700 International Drive, Orlando, Florida.
Pricing: A newly reduced Early Bird Registration ticket is available for $895.
Accommodations: Registered attendees gain access to a dedicated Connect block rate of $181 per night (including tax).
Sponsorships: Major industry partners, such as comforte, sponsor the event, granting enterprise buyers direct visibility into third-party NonStop infrastructure add-ons.
XPNET (often distributed as part of the NET24 suite) is a proprietary, mission-critical Message-Oriented Middleware (MOM) and network management infrastructure developed by ACI Worldwide.
It is designed to run primarily on fault-tolerant HPE NonStop (Tandem) systems. XPNET acts as the foundational layer for ACI’s globally dominant payment engines, BASE24 and BASE24-eps.
It provides the multi-node network architecture, data routing, inter-process communication, and transaction logging required to safely process hundreds of millions of ATM, Point of Sale (POS), and mobile payments daily.
Key Architectural Technical Description
Core Function: XPNET acts as the vital gateway between terminal devices (ATMs, POS terminals), regional interchanges (Visa, MasterCard), and a bank’s back-end host system.
Network Environment File (NEF): All physical and logical configurations of an XPNET deployment—including nodes, links, processes, stations, and communications lines—are centrally defined inside the NEF.
Fault Isolation: XPNET monitors processes using a distributed architecture. If an interface process or line drops, XPNET safely queues or reroutes transactions to achieve “five-nines” (99.999%) financial system uptime.
Audit and Tracing: XPNET intercepts all systemic message traffic, managing the core Transaction Log File (TLF) and generating event messaging for fraud monitoring and performance profiling.
Detailed XPNET Historical Timeline Breakdown
The evolution of XPNET is deeply intertwined with ACI’s flagship software, scaling alongside the transformation of global electronic funds transfers (EFT).
1982 – 1989: The Genesis Era
1982: ACI launches BASE24 to manage early ATM networks. To handle low-level Tandem interprocess communication, ACI designs precursor communication layers.
1986: ACI scales internationally to 131 major clients across 14 countries, increasing the demand for a standard, highly secure, policy-driven message-switching architecture to accommodate disparate global telecommunication protocols.
1990 – 1999: NET24 and XPNET Standardisation
1993: ACI is reorganised under Transaction Systems Architects (TSA). The communications infrastructure is formalised as NET24-XPNET, decoupled cleanly from application logic.
1995: ACI goes public on NASDAQ. XPNET becomes the mandatory structural platform for any financial institution deploying BASE24 “Classic”.
1998: ACI acquires IntraNet. XPNET is updated to handle wholesale wire transfers and high-value Automated Clearing House (ACH) data alongside retail consumer swipes.
2000 – 2009: The Next-Gen Transition (BASE24-eps)
2002: ACI launches BASE24-eps (Enterprise Payments System). XPNET is radically re-engineered to support both classic structural architecture and next-generation message formats, utilizing its Common Transport Subsystem (CTS) to act as a Tandem Pathway client/server.
2008: ACI optimises BASE24-eps for IBM System z architectures, but updates the NonStop-native XPNET to Version 08.2 to handle expansive regional payment networks across Europe and Asia.
2010 – 2019: Litigation and Global Footprint Consolidation
2011 – 2014: Third-party performance suites, such as IR Prognosis XPNET Manager,Insider Technologies XPERT24 and Reflex ONE24 explode in popularity, allowing banks to map live visual diagnostics of their XPNET lines and queues.
2017: ACI and MasterCard reach an agreement to resolve a massive legal dispute. As part of the settlement, MasterCard purchases a perpetual components license for NET24-XPNET middleware to legally fuel its core debit-switching network infrastructure.
2020 – 2026: Legacy Modernisation & The API Era
2021: With financial institutions pivoting toward digital microservices, ACI introduces hybrid compatibility layers. Companies like NuWave introduce direct API bindings to XPNET, allowing legacy HP NonStop payment architectures to map to modern REST web services without rewriting base COBOL/C code.
2025 – 2026: ACI celebrates 50 years of enterprise infrastructure engineering. While cloud-native solutions like ACI Connetic roll out for real-time rails, NET24-XPNET Version 4.x remains a heavily maintained, actively running baseline layer across tier-1 legacy banking systems worldwide.
XPERT24 (XPNET Performance Monitoring and Tracking) is a specialised financial middleware software product developed by Insider Technologies Limited. It provides real-time transaction tracking and operational counter monitoring for the BASE24™ transaction processing infrastructure.
Product Description
XPERT24 functions as a critical diagnostics layer for companies running BASE24 bank card payment systems. Built to sit on HP NonStop systems, the software uses PATHWAY servers to automatically detect, capture, and analyse data points from the underlying network. Its core features include:
XPNET Counter Monitoring: Tracks infrastructure health via rate, state, and data queue counters.
Interchange Performance: Monitors live transaction metrics, including approval and denial rates for ATM and POS transactions.
Throughput Optimization: Provides clear system visibility to avoid high-volume traffic jams or transaction delays.
Detailed Timeline Breakdown
The lifecycle of the XPERT24 software package moved from initial technical specification into corporate ecosystem expansions:
2001 — Initial System Baseline & Prep
Training and Scoping:Insider Technologies Limited launched internal Sales & Marketing campaigns to map mid-market banking software demands.
System Language Adaptation: Engineering teams refined core HP NonStop transaction tracking metrics.
2006 — Structural Architecture Layout
Design Initiatives: Product groups commenced documentation guidelines to build customer-facing technical literature.
Database Modeling: Initial designs mapped how transaction records could safely pass without lagging the live bank engine.
2007 — Server Logic Creation
Server Infrastructure Setup: Developers initiated building structural frameworks inside development kits.
Pathway Server Logic: Logic was written to make sure the software query scripts safely gathered data without interrupting processing.
2008 — Production Release & Launch Era
Official Software Launch: Insider Technologies launched the operational XPERT24 system to production status.
Hypervisor UI Integration: The company produced dedicated BASE24-eps™ and XPNET layer Hypervisor graphical displays.
Industry Showcase: Technical user interfaces were presented directly to the Electronic Banking User Group (EBUG) and the Satellite Transaction User Group (SATUG).
Web Monitoring Foundations: Teams rolled out technical requirements to present live transaction counters into standard web browsers.
2011 — Project Management & Standardization
Agile Shift: Development pipelines migrated entirely onto the Scrum framework.
Process Alignment: The product management structure was retrofitted to follow strict PRINCE2 guidelines to help service major government and banking institutions.
HPE NonStop MultiBatch is an advanced workload automation and scheduling manager designed explicitly for mission-critical HPE NonStop environments. Originally created to support complex scheduling needs in banking and finance, it automates job flows and parallel processing across multiple CPUs.
Detailed Description
The original NonStop batch scheduler (NetBatch) was built for basic sequential job queues. As large enterprises required deeper integration with databases, real-time events, and complex parallel schedules, MultiBatch (developed originally by Insider Technologies, now part of ETI-NET) emerged.
Core Functions: It automates job submission, tracks job flow, handles conditional parameters, manages event timers, and triggers jobs “On Demand” based on real-time system events.
High Availability: Like the underlying HPE NonStop system, MultiBatch is engineered for fault tolerance, ensuring automated workflows do not fail due to hardware or software interruptions.
Enterprise Integration: It supports Open System Services (OSS) and standardizes auditing, security, and menu-based operations across distributed NonStop systems.
Breakdown by Year / Era
The evolution of MultiBatch parallels the architectural changes of the HPE NonStop platform.
1985–1990s: Tandem Era & Origin
1985: Conceived. MultiBatch was developed by Insider Technologies specifically to meet the complex batch schedule demands of large financial institutions that exceeded native NetBatch capabilities.
Early 1990s: The system was officially rolled out for Tandem processors to automate transaction data loads and daily reconciliation tasks for ATMs and financial ledgers.
1997–2014: Compaq & Early HP Era
1997: Following Compaq’s acquisition of Tandem, MultiBatch was adapted to support the NonStop Himalaya systems and server software, which expanded data and network scaling.
2000s: During the HP Itanium and MIPS Era, MultiBatch evolved to support more dynamic processing pools and expanded job limits, increasing fault tolerance under the HP-UX integrated environment.
2014–2020: Transition to NonStop X & Modernization
2014: As HPE shifted the platform to standard Intel x86-64 processors (NonStop X), MultiBatch was updated for L-series operating systems to run efficiently on high-speed InfiniBand fabrics.
2019: Insider Technologies made significant updates to MultiBatch to modernize the GUI and improve code stability for the new generation of NonStop users transitioning to X-series hardware.
2020–Present: MultiBatch 10 & 10.2
2023: MultiBatch 10 was released. It included a new Operations GUI Server, significantly increased configuration limits (e.g., supporting up to 2,500 jobs), enhanced conditional parameters, improved processing of Open System Services (OSS), and “On Demand” job capabilities.
2025: MultiBatch 10.2 was released by ETI-NET. This update focused heavily on digital resilience, providing deep alignment with the NIST Cybersecurity Framework to protect against operational and cyber threats.
Current Status: Fully integrated into modern systems supporting the HPE GreenLake consumption-based cloud model, MultiBatch 10.2 serves as the primary automation engine for large enterprises executing complex HTAP (Hybrid Transaction/Analytical Processing) workloads.
Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:
Architecture: The foundational “shared-nothing” parallel architecture. Featured redundant components (processors, disks, power supplies) connected by a proprietary dual-bus (Dynabus). The operating system provided instant automated failover.
Architecture: Expanded into 32-bit computing. To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while heavily emulating the original instruction set for compatibility.
3. The Himalaya/ServerNet Era (1997–2004)
Years: 1997–2004
Processors: MIPS R-series
Architecture: Replaced the legacy Dynabus with ServerNet, a high-speed system interconnect that served as an early precursor to modern networking fabrics. (Compaq acquired Tandem in 1997, which subsequently merged with HP in 2002).
4. The Integrity Itanium Era (2005–2013)
Years: 2005–2013
Processors: Intel Itanium (TNS/E)
Architecture: Branded as HP Integrity NonStop (NonStop i). The platform moved off proprietary silicon to standard Intel Itanium processors. This was driven by the “NonStop Advanced Architecture” (NSAA), lowering hardware costs while maintaining Availability Level 4 (AL4) standards.
5. The NonStop X (x86-64) Era (2014–Present)
Years: 2014–2026
Processors: Intel Xeon x86-64 (TNS/X)
Architecture: Fully decoupled the OS from proprietary hardware by shifting to standard Intel x86-64 processors and InfiniBand fabric. The latest compute nodes (such as the NS5 X5 and NS9 X5) utilize modern Intel Xeon Scalable processors to maintain maximum Availability Level 4 (AL4) workloads.
6. The Virtualized NonStop Era (Present)
Years: 2015–Present
Processors: Virtual Machines / Cloud / x86
Architecture: HPE extended the platform to support Virtualized NonStop Software, allowing fault-tolerant enterprise workloads to run entirely in private clouds via standard VMware or hybrid architectures, independent of specific physical servers.
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 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.
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
End-to-End Component Transaction Flow
An ATM transaction arrives at the network interface layer managed by XPNET.
The message is routed to the Device Handler, which strips hardware packaging and requests translation from the HSM.
The clean internal message passes to the Authorization Engine.
If it is a “Not-On-Us” card, the engine identifies the destination BIN and transfers routing control to the Interchange Interface.
The Interchange Interface maps the payload to the external scheme standard (such as Visa) and transmits it to the external network.
The outbound network response is unwrapped by the Interchange component and tracked through the core engine to log final response codes.
The transaction safely records inside the active log file, allowing the Extract / Settlement components to pick it up later during batch processing.
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.
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.
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.
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.
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.
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
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 1994HP 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 examplesPlan 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.
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
HPE NonStop PATHCOM is the interactive management interface for the Pathway transaction processing environment. It allows administrators to configure, monitor, and control PATHMON-governed objects such as serverclasses, TCPs (Terminal Control Processes), and links.
Historical Timeline: The Evolution of Pathway & PATHCOM
The history of PATHCOM is inseparable from the Tandem NonStop platform, which pioneered fault-tolerant Online Transaction Processing (OLTP).
The Tandem Era (1974 – 1997)
1974 – 1976: Tandem Computers is founded. The first NonStop I system ships in 1976.
1983: Tandem introduces Pathway software alongside the Transaction Monitoring Facility (TMF). This milestone removes the requirement for developers to manually code fault tolerance into applications, as the Pathway infrastructure (managed via PATHCOM) handles it automatically.
Early 1990s: The platform migrates from proprietary stack machines to MIPS RISC processors (TNS/R architecture). PATHCOM evolves to manage more complex distributed environments.
1994: Open System Services (OSS) is introduced, allowing NonStop to support a Unix-like POSIX environment.
2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads.
The Modern HPE Era (2014 – Present)
2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality
Future of NonStop Pathway
HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:
Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
Open Integration: Continued emphasis on open application development environments and open-source frameworks.
Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.
HPE NonStop Inspect is the primary symbolic, source-level debugger for applications running on the HPE NonStop (formerly Tandem) operating system. It allows developers to interactively control program execution, examine and change data variables, and debug complex multi-process applications in both the Guardian and Open System Services (OSS) environments.
Program Summary
The Inspect debugger family facilitates high-availability software development through several specialized versions:
Inspect (Legacy): A command-line tool for TNS, TNS/R, and TNS/E systems.
Native Inspect (eInspect/xInspect): Adapted from GDB for Itanium and x86 architectures; it provides a command-line interface with scripting capabilities.
Visual Inspect: A Windows-hosted GUI debugger that provides “point-and-click” efficiency for setting breakpoints and displaying variables.
NSDEE (Eclipse): Modern debugging integrated into the Eclipse-based development environment, supporting NonStop Application, Attach Process, and Snapshot debug configurations.
Historic Timeline by Era
The evolution of the NonStop debugger mirrors the platform’s hardware transitions over five decades.
The Tandem Era (1974 – 1997)
1974: Tandem Computers is founded; the platform begins with T/16 (NonStop I).
1980s:Inspect is introduced as the standard interactive debugger for the TNS (Tandem Network Strategy) CISC architecture.
Early 1990s: Migration to MIPS-based TNS/R systems; Inspect is updated to support RISC instruction sets and optimized compilers.
The Compaq & Early HP Era (1997 – 2014)
1997: Compaq acquires Tandem.
2002: HP acquires Compaq; migration to TNS/E (Intel Itanium) architecture begins.
2005 – 2010:Visual Inspect becomes a staple for developers seeking a GUI experience on Windows.
2013: Release of the Inspect H01 Manual, documenting full support for TNS/R and TNS/E concurrent debugging.
The Modern HPE Era (2014 – Present)
2014: Introduction of NonStop X (x86-64 architecture). Native Inspect (xInspect) is launched, based on GDB, to support the move away from Itanium.
2015: HPE is formed; focus shifts to the NonStop Development Environment for Eclipse (NSDEE).
2020 – 2024: Enhancements in NSDEE include improved OSS process handling and support for large-scale application debugging.
HPE’s roadmap for NonStop focuses on modernisation through tradition, ensuring that legacy tools like Inspect remain compatible while transitioning to cloud-native and virtualized environments.
Virtualized NonStop (vNS): Debugging tools are being adapted to work seamlessly within enterprise private clouds and HPE GreenLake consumption models.
Richard Buckle, founder of Pyalla Technologies, is a prominent thought leader in the HPE NonStop community known for his “Real Time View” column. His work provides a detailed chronological perspective on the platform’s evolution from its Tandem origins to modern cloud-native implementations.
The Tandem Era: Foundations (1974 – 1997)
This era established the core architecture of fault tolerance and “non-stop” processing.
1974: Tandem Computers is founded; the first “NonStop” system is commissioned.
1970s – 1980s: The platform gains dominance in financial services, telco, and healthcare.
1996: Managed service models begin for Tandem users, with firms like Tandem Computer Management (TCM) winning major contracts like Bank of Scotland.
The Compaq & Early HP Era: Transition (1997 – 2013)
A period of shifting corporate ownership and the end of the original Cupertino campus era.
1997: Compaq acquires Tandem Computers.
2002: HP acquires Compaq, bringing NonStop into the HP Enterprise fold.
2008: The official end of the Cupertino Tandem campus as NonStop teams move to other facilities.
The X86 & Virtualization Era: Modernization (2013 – 2023)
Buckle documented the massive shift from proprietary hardware to industry-standard Intel x86 architecture.
2013: Announcement at NonStop TBC that the platform will support Intel x86.
Mark Whitfield is a highly experienced IT Senior Project Manager and Engagement Manager based in Manchester, UK, specializing in Agile Scrum, PRINCE2, and Waterfall methodologies. He holds a degree in Computing (1990) and has extensive experience in IT hardware solutions, financial services, and Aerospace & Defence.
Here is a comprehensive summary of his profile, with links based on the provided search data:
Professional Profile
Name: Mark Whitfield
Role: IT Senior Project Manager / Engagement Manager (SC Cleared)
Mark Whitfield is a highly experienced IT Project Manager, Senior Developer, and SC-cleared consultant with over 30 years of experience, specializing in HP NonStop (Tandem) systems, banking software, and digital transformation projects. He is currently an Engagement Project Manager at Capgemini.
Career Overview
Specialism: HP NonStop (Tandem) mainframes, BASE24, transaction monitoring, Agile/Waterfall methodologies.
1990: Graduated in Computing and started as a Programmer for The Software Partnership in Runcorn, specializing in sp/ARCHITECT-BANK on Tandem Computers.
1990-1994: Developed banking code for TSB, Bank of Scotland, Rabobank, and Girofon (Denmark).
1992: Worked on the Barclays Business Master II (BBM II) project in Knutsford.
1994: Company taken over by Deluxe Data (later FIS).
2. Insider Technologies & Monitoring Era (1995–2013)
1995–2013: Joined Insider Technologies Ltd as a Senior Development Engineer and Project Manager.
1995-2004: Developed monitoring/diagnostic software (Reflex 80:20, Reflex ONE24) for HP NonStop payment systems.
1997: Worked on projects for CRESTCo.
Early 2000s: Focused on HP NonStop transaction/payment monitoring for ATM/POS devices using ACI’s XPNET.
2005-2013: Managed first HP OpenView Operations Smart Plug-In certification for NonStop; designed XPERT24.
2011: Certified as a PRINCE2 Practitioner.
3. Banking Transformation & Consultancy Era (2013–2016)
2013–2014: Wincor Nixdorf UK – Worked as a Project Manager in Professional Services for the Banking Division.
2013-2014: Assigned to Lloyds Banking Group (LBG) for the Self-Service Software Replacement (SSSR) program (ATM estate upgrade).
2014–2016: Joined Betfred as an IT Project Manager in the gambling/casinos industry, delivering mobile/online payment gateways (iOS, Android).
4. Digital Transformation & Capgemini Era (2016–Present)
2016: Joined Capgemini UK as a client-facing Engagement Manager.
2016-2017: Led digital projects for automotive, local government, and aerospace sectors.
2017: Obtained Microsoft Excel Expert skills and Advanced Engagement Management certifications.
2018–2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
2022: Completed Microsoft Azure Fundamentals (AZ-900) certification.
2023–2024: Assigned to a UK Government account for a cloud migration of 130+ applications and the Fish Export Service (FES) project.
Key Qualifications
PRINCE2 Practitioner & Agile Scrum
ITIL Certified
SC Cleared (UK Government)
Technical Skills: C, C++, MS SQL, COBOL, TAL, Java, ASP.NET, HP NonStop
The HPE NonStop architecture is defined by its “shared-nothing” design, where every hardware and software component is redundant and operates independently to ensure 100% operational continuity. For over 40 years, it has evolved through four distinct hardware eras while maintaining upward software compatibility.
1. The Tandem Era (1974–1997): Proprietary Foundations
Architecture Approach: Founded by James Treybig, Tandem introduced the first commercial fault-tolerant system using a proprietary 16-bit stack-based architecture.
Key Technical Milestones:
1976 (NonStop I/T16): Introduced the Dynabus, a custom inter-processor backplane, and the Guardian OS, which used message-passing instead of shared memory to isolate faults.
1981–1983 (NonStop II & TXP): Introduced 32-bit addressing and the Transaction Monitoring Facility (TMF), which allowed applications to be fault-tolerant without specialized coding.
1986–1989 (VLX & Cyclone): Scaled to the mainframe market with ECL gate-array chips and the first fault-tolerant relational database, NonStop SQL.
2. The MIPS Era (1991–2004): Migration to RISC
Architecture Approach: To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while emulating the original instruction set for compatibility.
Key Technical Milestones:
1991 (Cyclone/R): The first MIPS-based system.
1997 (Himalaya S-Series): Replaced Dynabus with ServerNet, a high-speed system interconnect that later evolved into the industry-standard InfiniBand.
Ownership Shift: Compaq acquired Tandem in 1997, and HP merged with Compaq in 2002.
3. The Itanium Era (2005–2013): HP Integrity NonStop
Architecture Approach: Branded as Integrity NonStop (NonStop i), this era moved the platform to Intel Itanium processors.
Key Technical Milestones:
2005 (NS-series/J-series): Focused on “NonStop Advanced Architecture” (NSAA), leveraging standard HP server components to lower costs while maintaining Availability Level 4 (AL4).
Technical Commentary: While powerful, the reliance on Itanium’s EPIC architecture eventually limited growth as the industry consolidated around x86-64.
4. The Modern HPE Era (2014–Present): x86-64 & Virtualization
Architecture Approach: Shifted to standard Intel x86-64 processors (NonStop X), fully decoupling the software stack from proprietary hardware.
Key Technical Milestones:
2014 (NonStop X/TNS/X): Introduced the L-series operating system. The architecture transitioned to a standard InfiniBand fabric for inter-processor communication.
2017–2020 (vNS): Launched Virtualized NonStop (vNS), allowing the environment to run on standard hypervisors like VMware, bringing fault tolerance to private and hybrid clouds.
2025 (NS9 X5): Modern systems now support up to 8 TB of RAM and are integrated into the HPE GreenLake consumption-based cloud model.
Tandem TAL (Transaction Application Language) is a block-structured, procedural language designed in the mid-1970s for Tandem’s NonStop fault-tolerant operating systems, optimized for systems programming, high-reliability OLTP, and direct hardware interaction. It is heavily influenced by ALGOL and HP 3000 systems, allowing high-performance, message-based applications, and remains supported on modern HP Enterprise NonStop x86-64 platforms.
Tandem TAL Programming certificate back in 1995, Mark Whitfield
Overview of TAL Programming
Purpose: Developed to run on Tandem’s GUARDIAN operating system to build highly available, fault-tolerant transactional systems.
Characteristics: Procedural, block-structured, efficient (closer to assembly than C), and designed for speed and direct memory access, according to a NonStop Insider article.
Features: Strong support for data manipulation, process management, and message-based IPC (Inter-Process Communication) necessary for node-to-node replication, as described on the Wikipedia page on Tandem Computers.
Relation to TACL: While TAL is for creating compiled applications, TACL (Tandem Advanced Command Language) is the interpreter/macro language used for command procedures and system interaction, as explained in a Scribd document.
Historical Timeline of TAL
1975–1976 (Founding Era): TAL is created for the first Tandem/16 system shipped in 1976, heavily utilizing expertise from HP 3000 systems programming, according to a personal blog post.
Early 1980s (Expansion): TAL becomes the standard for ATM networks and banking systems, requiring high-reliability code, as seen in this blogger.com article.
1985 (Evolution): TAL is used to build complex OLTP environments, distinguishing it from nascent PC markets as noted in archived Tandem press clippings.
1990s (Native TAL): Introduction of “Native” TAL (T/TAL) to handle new architecture requirements and move from 16-bit to 32-bit environments, according to a TAL Programmer’s Guide document.
1997 (Compaq Merger): Tandem is acquired by Compaq; TAL continues as the core systems language.
2001 (HP Merger): Tandem (via Compaq) is acquired by HP, bringing TAL to the HP Integrity (Itanium) platform.
2010s–Present (Modernization): TAL applications are ported to HP Enterprise NonStop x86-64, with support for running TAL programs on Intel processors and in virtualized instances, according to a NonStop Insider article.
Present Day
TAL remains essential for maintaining legacy systems, but new applications often utilize C/C++ or Java on the modern NonStop platform, as noted in the Wikipedia page on Transaction Application Language.
TAL applications are still relevant due to the “single system image” and fault-tolerance features that define the current NonStop environment, according to the NonStop Insider article.
PTAL Overview and Timeline
Tandem PTAL (Portable Transaction Application Language) is a block-structured, procedural systems programming language used on HPE NonStop (formerly Tandem) servers. It is the portable successor to the original TAL (Transaction Application Language), designed to allow high-level systems programming without an assembler while maintaining near-machine efficiency.
Overview: TAL, PTAL, and epTAL
The language evolved to support different processor architectures over Tandem’s 50-year history:
TAL (Original): Designed for the 16-bit CISC stack machine architecture (TNS). It has the syntax of ALGOL/Pascal but the low-level semantics of C.
PTAL (Portable): Introduced during the migration to MIPS RISC processors (TNS/R). It removed machine-specific constructs to allow code to be compiled into native RISC instructions.
epTAL (Extended): Developed for the migration to Intel Itanium processors (TNS/E).
Historical Timeline by Year
Year Milestone
1974, Tandem Computers founded by James Treybig; initial design of the Tandem/16 hardware begins.
1976, TAL released. The Tandem/16 (NonStop I) ships with TAL as its only programming language.
1981, NonStop II introduced, adding 32-bit addressing support to TAL via an “extended data segment”.
1983, NonStop TXP launched; first major reimplementation of the instruction set architecture supported by TAL.
1986, NonStop VLX introduced with 32-bit data paths; NonStop SQL released, often managed via TAL-based systems.
1989, NonStop Cyclone released, the high-end mainframe competitor for the TAL environment.
1991, PTAL Development starts with the release of Cyclone/R, the first MIPS-based machine. TAL code is initially translated via an “Accelerator” tool before native PTAL compilers take over.
1993, Himalaya K-series released; native mode operating system (NSK) and native compilers (PTAL) become standard.
1997, Compaq acquires Tandem. Migration begins from MIPS to Alpha (later abandoned).
2002, HP merges with Compaq. Development focuses on the Itanium (TNS/E) architecture.
2005, epTAL introduced for the new Integrity NonStop i servers based on Intel Itanium microprocessors.
2014, x86 Migration. NonStop X (TNS/X) systems are released, transitioning the TAL/PTAL environment to Intel x86-64 processors.
Insider Technologies RTLX (now C-Deep (Transaction Monitoring) https://etinet.com/products/c-deep-transaction-monitoring/ ) is a real-time monitoring and tracking solution designed to provide end-to-end visibility for high-volume electronic payments and transactional processes. It specifically ensures that every stage of a payment—from the initial card “tap” at a point-of-sale (POS) terminal to the final movement of funds from an account—is monitored to maintain operational continuity.
RTLX Overview
Function: Real-time transaction and payment monitoring.
Platforms: Runs on HP NonStop, Windows, Linux, and Unix.
Core Value: Simplifies “Big Data” for IT operations by alerting teams to potential failures before they impact consumers (e.g., preventing ATM or online banking outages).
Key Use Case: Used by major financial institutions like the Bank of England and Royal Bank of Scotland for settlement and transaction security.
RTLX Historical Timeline
The development of RTLX is closely tied to Insider Technologies’ growth as a specialist in mission-critical HP NonStop environments.
1990s: The company establishes its “DNA” in the HP NonStop (Tandem) platform, developing core products like MultiBatch and Reflex.
1995: Insider begins a period of rapid growth, providing technical support for critical UK financial infrastructure, including Euroclear (formerly CRESTCo), which settles 88% of UK equities.
The Expansion Era (2001–2014)
2002: Launch of the state-of-the-art Systems Training Platform, featuring 4x patented cloning technology for hyper-realistic simulations.
2004–2013: Development of the Reflex suite (Reflex 80:20 and Reflex ONE24) and the introduction of Sentra and RTLX Reactor monitoring products.
2014: Insider expands its product initiatives to include diagnostic and trending solutions for real-time electronic payments, solidifying the role of RTLX in global banking.
The Acquisition & Integration Era (2015–Present)
2015: ETI-NET acquires Insider Technologies on 1 July, integrating its monitoring expertise with ETI-NET’s mainframe storage and backup solutions.
2019: Insider celebrates its 30th year of operations, highlighting RTLX’s role in monitoring modern POS and “tap” payment systems.
2023–Present: Insider becomes part of the PartnerOne group, a global family of mission-critical software companies, further scaling its threat detection and real-time monitoring capabilities.
RTLX by Insider Technologies, Overview and Timeline by Year
HP NonStop MultiBatch is a “mainframe-class” workload automation and batch scheduling manager developed by Insider Technologies (distributed by ETI-NET). It is designed specifically for the HPE NonStop (formerly Tandem) platform to automate, manage, and secure complex batch processing across both Guardian and OSS environments.
Product Overview
While the native NonStop scheduler is NetBatch, MultiBatch is positioned as a modern, high-performance alternative that provides deeper integration with the NonStop architecture.
Workload Automation: Manages thousands of concurrent jobs with sophisticated calendaring and dependency tracking.
Architecture: Built to leverage NonStop’s fault tolerance and linear scalability, allowing batch schedules to execute across multiple networked nodes.
Interfaces: Modernized from command-line tools to a suite of role-based Graphical User Interfaces (GUIs) for operations and management.
Security: Includes a secure, audited environment with full support for NonStop-specific security attributes like High-PIN and CPU selection.
Historical Timeline by Era
The evolution of MultiBatch is closely tied to the history of the Tandem/NonStop platform, which spans over 50 years of ownership changes and architectural shifts.
1. The Tandem Era (1974 – 1997)
1974: Tandem Computers founded by James Treybig to build the first fault-tolerant commercial systems.
Late 1980s – Early 1990s: MultiBatch originated during this period (reportedly in the early 1990s) to address the needs of large financial institutions requiring complex batch schedules beyond the capabilities of the original NetBatch.
1991: Release of the Cyclone/R and the start of the migration from proprietary stack machines to MIPS RISC processors.
2. The Compaq & Early HP Era (1997 – 2014)
1997: Compaq acquires Tandem.
2002: Hewlett-Packard (HP) merges with Compaq. The NonStop platform begins its migration from MIPS to Intel Itanium (branded as Integrity NonStop).
Mid-2000s: MultiBatch matures as a mission-critical tool for global banks and stock exchanges. Development focuses on MultiBatch 7 and 8, enhancing GUI capabilities and adding support for Open System Services (OSS).
3. The Modern HPE Era (2014 – Present)
2014: NonStop X is introduced, moving the architecture from Itanium to Intel x86-64.
2018 – 2020: MultiBatch 9.5 is released with an enhanced GUI. It increasingly becomes the primary alternative as HPE shifts focus away from active sales of the legacy NetBatch product.
2023 – 2024: Release of MultiBatch 10, introducing “Define Classes,” support for up to 2,500 jobs, and improved OSS process handling. This era focuses on “modernisation through tradition,” aligning with HPE’s push for virtualized NonStop and hybrid cloud deployments.
BASE24 is the world’s most widely used payment processing platform, developed by ACI Worldwide. Originally designed for ATM networks, it evolved into a comprehensive system for acquiring, authenticating, and routing card-based and digital transactions across various channels. It is known for its high-performance, fault-tolerant architecture, processing nearly 50% of the world’s electronic transactions at its peak.
Comprehensive Timeline by Era
Era 1: Foundations & The Rise of BASE24 Classic (1975–1990s)
This era focused on high-availability software for the emerging automated banking industry, specifically for Tandem NonStop servers.
1975: ACI founded in Omaha, Nebraska, to develop software for the new “NonStop” server computers used by banks and stock exchanges.
1981: Secured its first international client, an Australian bank, marking the start of global expansion.
1982:Launch of BASE24, the first global product designed for 24-hour system operations, originally focused on ATM networks.
1986: Rapid growth led to 131 customers across 14 different countries.
Era 2: Expansion & Public Transition (1995–2000s)
The platform expanded into Point of Sale (POS) and branch systems while the company underwent major structural changes.
1995: The company went public on NASDAQ as Transaction Systems Architects (TSA).
1997: Officially adopted the name ACI Worldwide.
Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a next-generation platform using C++ and object-based architecture to replace the legacy monolithic design.
Era 3: Modernisation & The “eps” Shift (2005–2015)
ACI shifted focus toward BASE24-eps, a more flexible, open-architecture version designed for multi-channel transaction processing.
2005: ACI launches BASE24-eps, featuring a modular engine capable of processing approximately 2,000 transactions per second (TPS) with extremely low latency.
2007: TSA officially rebranded all operations under the ACI Worldwide, Inc. (ACIW) name.
2008: Announced that BASE24 Classic would begin maturing in 2011, urging customers to migrate to the eps platform for better integration with modern systems like IBM System z.
2011–2012: Release of BASE24-eps 11.1, adding support for DB2 on IBM System p, enhanced EMV acquiring, and tools for easier migration from legacy BASE24.
Era 4: Cloud & Universal Payments (2015–Present)
The platform moved toward cloud-native capabilities and broader ecosystem integration.
2015: ACI celebrated its 40th anniversary, continuing to power electronic payments for over 6,000 organisations worldwide.
2018: Introduction of UP BASE24-eps on Linux in the Cloud, demonstrating significantly reduced Total Cost of Ownership (TCO) through public and private cloud deployment.
Present: BASE24 remains a core pillar of ACI’s portfolio, supporting traditional card, ATM, mobile commerce, and internet banking transactions.
BASE24-eps by ACI Worldwide timeline by era and year
BASE24-eps is a modular, high-availability payment processing engine developed by ACI Worldwide. It evolved from the original “BASE24 Classic” to provide a more flexible, open-system architecture for acquiring, authenticating, routing, and authorizing electronic transactions.
Base24-eps Overview
Architecture: Unlike the TAL-based Classic version, BASE24-eps uses an object-oriented design written primarily in C++ and Java.
Key Features:
Multi-Channel Support: Manages transactions from ATMs, POS terminals, mobile, and ecommerce.
Late 1970s: Development of the original BASE24 (now known as “Classic”), focused on high-uptime ATM processing.
1981: First international customer (an Australian bank) signs on, starting the global expansion of BASE24.
Transition & Development Era (2000 – 2005)
Early 2000s: ACI begins developing the “next generation” platform, initially called BASE24-es (extended systems), which later becomes BASE24-eps (enterprise payment system).
2003 – 2004: The product begins migrating to open architectures, moving away from platform-specific languages.
Mainstream Adoption Era (2006 – 2013)
2007: ACI highlights BASE24-eps as its strategic future platform in investor overviews.
2008: ACI announces the maturation of BASE24 Classic (ending standard maintenance in 2011), urging customers to migrate to BASE24-eps.
2009: IBM Redbooks releases technical guides for BASE24-eps 08.2 on z/OS, solidifying its place in enterprise banking.
2013: Release of BASE24-eps 2.0, introducing the “customer component” and enhanced service-enabling wrappers.
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager with over 30 years of experience, specializing in the software development lifecycle (SDLC) for large-scale digital and financial payment systems.
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager
Key Projects: Leading high-value digital transformations and cloud migrations for UK Government applications, automotive (Jaguar Land Rover), and aerospace (Air Traffic Management iOS apps).
2014–2016: Betfred Limited (UK)
Role: IT Senior Digital Project Manager, Online and Mobile Division.
Key Projects: Managed multiple Agile SCRUM projects for payment gateways, sportsbooks, and virtual gaming components across iOS, Android, and Windows platforms.
2013–2014: Wincor Nixdorf Limited (UK)
Role: Project Manager, Professional Services – Banking Division.
Key Projects: Managed a £5M+ workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) program, migrating legacy HP NonStop systems to AIX-based Oracle technologies.
HP NonStop (originally Tandem) training focuses on the platform’s unique fault-tolerant architecture, designed to ensure 24×7 availability and data integrity for mission-critical industries like finance and telecommunications. Current training is provided by HPE Education Services, which offers expert-led courses ranging from basic concepts to advanced system management and database administration.
Training Overview
HPE’s curriculum is structured to support IT teams at all levels—from beginners to experienced operators—and can be customised for specific business needs. Key training areas include:
System Operations: Managing NonStop environments, including S-Series or newer x86-based systems.
Radbroke Hall is a 64-acre “Innovation Campus” in Cheshire that serves as the global technology and operations hub for Barclays. Originally built as a French chateau-style private residence in 1917, it transitioned through use by a nuclear research group before Barclays acquired it in 1972. Today, it employs approximately 4,000–6,500 staff and has been the development site for pioneering banking technology, including the first ATMs, debit cards, and mobile banking platforms.
Radbroke Hall History Timeline
Era 1: Private Residence (1914–1956)
1914: Construction begins on the Hall for Manchester textile manufacturer Claude Hardy and his wife Olga.
1916: Claude Hardy dies; Olga oversees the completion of the Portland stone building alone.
1917: The Hall is completed as a private residence.
1920s–1930s: The Hall remains largely unoccupied during these decades.
Era 2: Industrial & Nuclear Research (1956–1972)
1956: The Hardy family sells the estate to The Nuclear Power Group.
1956–1972: The site is used for nuclear energy research, with offices and a testing tower constructed on the grounds.
Era 3: The Barclays Transformation (1972–1990s)
1972: Barclays purchases the site from The Nuclear Power Group to reduce high rental costs in London.
1972 (Relocation): Approximately 1,400 staff are relocated from London or hired locally; many find the move from London to the “rural North” a significant culture shock.
1970s–1980s: The site begins its role as an IT hub, instrumental in developing the first cash machines (ATMs) and debit cards.
1985: Barclays reorganises its UK and International banks into a single entity, further centralising tech and staff services at Radbroke.
Era 4: Global Tech & Modernisation (2000s–Present)
Early 2000s: The campus leads the development of Barclays’ online and mobile banking applications.
2012: Barclays celebrates the 40th anniversary of its presence at Radbroke Hall.
2017: The original Hall building marks its 100th anniversary.
2021: Barclays announces a major redevelopment plan to modernise the campus, including the demolition of older buildings (Kilburn, Lovelace, and Brooker Houses) to create a new central “town square” and “re-green” 80,000 sq. ft. of land.
2024: Investment continues to transform Radbroke into a “world-class campus” focused on the future of work and advanced banking APIs.
Barclays House, located at 1 Wimborne Road, was a dominant fixture of the Poole skyline for 46 years. Originally built to decentralise Barclays Bank International operations from London, the nine-storey brutalist structure served as a major regional headquarters from 1976 until its closure in 2022. Following its vacancy, the building was earmarked for conversion into a residential complex featuring 362 apartments.
Historical Overview
Purpose: The building was commissioned to move staff away from high London costs and boost local employment in Poole.
Architecture: Designed by Wilson, Mason and Partners, it features three interlinked octagonal/hexagonal towers in the brutalist style.
Landmark Features: A massive 14-foot aluminium eagle logo (the Barclays emblem) adorned the front of the building for decades.
Detailed Timeline Breakdown
The Development Era (1960s – 1975)
Late 1960s: Poole is selected as the primary location for Barclays Bank DCO (Dominion, Colonial and Overseas) decentralisation.
1971 (August): Planning permission is granted for the project after a public inquiry, with an estimated cost of £5 million.
1972 (September): Construction begins, led by the John Laing Group.
1975 (June): Construction is officially completed.
The Operational Era (1976 – 2021)
1976 (January): Barclays first occupies the building.
1976 – 1980s: Workforce grows rapidly; in its first year, it employed 800 people, eventually peaking at roughly 2,500 employees.
2007 (January): A planning bid to demolish the building for flats is refused due to its scale and lack of amenity space.
2008: Barclays announces plans to build a new HQ in Poole, though these did not result in immediate relocation from the Wimborne Road site.
2016: The building undergoes a major refurbishment to celebrate its 40th anniversary.
The Closure & Transition Era (2022 – Present)
2022 (January 26): Barclays officially closes its doors at Wimborne Road after 46 years.
2022 (October 27): The iconic Barclays eagle logo is removed from the building’s facade by cranes.
2022 (December): Remaining staff (approximately 700) are relocated to new offices in Bournemouth.
2023: VCRE Four Poole submits a planning bid to convert the structure into 362 homes.
2024 (March 8): The separate Poole High Street branch also closes.
Mark Whitfield is a highly experienced IT professional with a career spanning over 30 years, transitioning from a technical programmer to a senior digital engagement and project manager. His expertise is rooted in HPE NonStop (Tandem) systems and has evolved to encompass complex Agile and Cloud delivery across diverse industries.
Early Technical Era (1990–1995)
Following his graduation in Computing in 1990, Whitfield began his career as a Programmer at The Software Partnership (later Deluxe Data).
Focus: Electronic banking software, specifically sp/ARCHITECT-BANK on Tandem Mainframe Computers.
Key Work: Developed code for major banks including TSB, Barclays, and Rabobank. This included early digital innovations like voice-driven phone banking and inter-account transfers before the internet was widespread.
Growth and Product Management Era (1995–2004)
Whitfield joined Insider Technologies Limited (ITL) in 1995 as a Senior Programmer.
Focus: Platform health and diagnostic software for HPE NonStop systems.
Key Projects:
Co-developed diagnostic plug-ins for the Reflex monitoring suite.
Managed the first HP OpenView Operations (OVO) Smart Plug-In certification for the NonStop platform in 2002.
Consulted for CRESTCo (Euroclear) in 1997, conducting benchmark testing on new S7000 nodes.
Strategic Leadership and Project Management Era (2005–2014)
During this decade, he transitioned into IT Project Management, focusing on high-value financial transaction tracking.
Focus: Waterfall and Agile project delivery for payment systems and banking infrastructure.
Key Milestones:
2011: Led a massive transaction tracking project at Al Rajhi Bank (Saudi Arabia), parsing terabytes of tape-archived data into a normalised SQL database.
2013–2014: At Wincor Nixdorf, managed a £5+ million project for Lloyds Banking Group to migrate ATM driving responsibilities from legacy systems to AIX-based Oracle technologies.
Senior Digital Engagement Era (2014–Present)
Since 2014, Whitfield has focused on senior-level digital transformation and engagement management.
Betfred (2014–2016): Served as Senior Digital Project Manager for online and mobile platforms (iOS/Android), managing fraud detection and payment gateway integrations.
Capgemini (2016–Present): Joined as an Engagement Manager (SC cleared).
Focus: Managing large-scale Agile and Waterfall digital projects across aerospace, defence, and government sectors.
Notable Projects: Leading a £13.5m programme to migrate 130 UK government applications to the cloud (AWS/Azure) and delivering real-time airspace monitoring apps for air traffic organisations.
1981:NonStop II is introduced, adding 32-bit addressing capabilities and replacing magnetic core memory with battery-backed DRAM.
1983:NonStop TXP (Transaction Processing) launches as the first new implementation of the architecture, featuring cache memory and 2.0 MIPS performance.
1986: Introduction of NonStop VLX (Very Large eXpansion) and NonStop SQL, the first fault-tolerant relational database designed for linear scalability.
1987:NonStop CLX launches as a lower-cost, compact minicomputer for remote office environments.
1989:NonStop Cyclone is released for high-end mainframe markets, featuring superscalar CPUs and fiber optic interconnects.
3. The MIPS RISC Transition & Acquisitions (1991–2003)
1991:Cyclone/R (or CLX/R) marks the move to MIPS R3000 RISC processors, using object code translation to maintain backward compatibility.
1993:Himalaya K-series is released using MIPS R4400 processors.
1995:Open System Services (OSS) is added to the NonStop Kernel to provide a POSIX/Unix-like environment.
1997:Compaq acquires Tandem Computers. The Himalaya S-Series introduces ServerNet, which later becomes the InfiniBand industry standard.
2002/2003: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard.
4. The HP Integrity & x86 Era (2005–Present)
2005:HP Integrity NonStop (TNS/E) is introduced, migrating the platform to Intel Itanium microprocessors.
2014:NonStop X (TNS/X) launches, shifting the architecture to Intel x86-64 processors for greater industry-standard alignment.
2015: Following the HP corporate split, NonStop becomes part of Hewlett Packard Enterprise (HPE).
2020: Sales of Itanium-based systems officially end in July 2020.
2024–2025: HPE expands the platform with Virtualized NonStop Software for private clouds and consumption-based models via HPE GreenLake.
HP NonStop Tandem Overview and Timeline History by year
HPE NonStop (formerly Tandem and Compaq NonStop) is a family of fault-tolerant, integrated hardware and software systems designed for mission-critical enterprise workloads. Since its introduction in 1976, it has served as the backbone for high-volume transaction environments like banks, stock exchanges, and payment systems, offering 100% continuous uptime.
Core Architecture and Features
The platform is defined by its “shared-nothing” architecture, where every component is redundant to eliminate single points of failure.
Continuous Availability: If a hardware or software component fails, a backup takes over immediately without disrupting the application, a process often managed through process pairs (primary and hot backup processes).
Linear Scalability: You can add capacity (CPUs, memory) seamlessly without downtime. Systems can scale from a few processors to clusters of over 4,000 CPUs while maintaining a single-system image for management.
Integrated Stack: Unlike standard servers, NonStop includes a fully integrated stack of hardware, the NonStop OS (a proprietary kernel), a relational database (NonStop SQL), and middleware.
Fail-Fast Design: Modules are self-checking; they stop immediately upon detecting an error to prevent data corruption, allowing the redundant backup to resume processing from the last known good state.
Current Hardware and Deployment
While historically based on proprietary or Itanium processors, modern NonStop systems (NonStop X) utilize industry-standard Intel Xeon processors and high-speed InfiniBand interconnects.
High-End Systems: Models like the NS9 X5 are built for the most demanding high-volume transaction processing (OLTP).
Mid-Range/Entry Systems: Models like the NS5 X5 offer fault tolerance for smaller enterprises or development environments.
Virtualization & Cloud:HPE Virtualized NonStop Software allows the platform to run on standard private cloud infrastructure (e.g., VMware, OpenStack), and it is also available via HPE GreenLake as a consumption-based, pay-as-you-go service.
Software and Security
Database: Supports NonStop SQL/MX and SQL/MP for multi-tenant, fault-tolerant data management.
Development: Supports modern languages like Java, C++, Python, COBOL, and the TACL scripting language. Developers can use the Eclipse-based IDE for building and debugging applications.
Security: Built with Zero Trust principles, including hardware-level vulnerability mitigations (e.g., against Spectre/Meltdown) and real-time threat detection.
Detailed Architecture
HPE NonStop architecture is a fault-tolerant, shared-nothing, massively parallel computing platform designed for 100% operational continuity. Originally developed by Tandem Computers, it is engineered so that no single hardware or software failure can bring down the system.
Core Architectural Pillars
Shared-Nothing Architecture: Each processor has its own dedicated memory, I/O bus, and copy of the HPE NonStop Operating System (NSK). This eliminates resource contention and single points of failure found in shared-memory systems.
Massive Scalability: Systems scale linearly by adding more processors. A single node can support up to 16 CPUs, and multiple nodes can be clustered to support over 4,000 CPUs.
Fault Tolerance (Process Pairs): Software availability is maintained through “process pairs”—a primary process and a passive backup process. If the primary fails, the backup immediately takes over without losing data or state.
Fail-Fast Design: Hardware and software modules are designed to stop immediately upon detecting an error (“fail-stop”) to prevent data corruption from propagating.
Hardware Components
Compute Nodes: Modern HPE NonStop X systems use standard Intel Xeon x86-64 processors but implement fault tolerance through specialized system interconnects.
System Interconnect (Fabric):
InfiniBand: Used in NonStop X systems for high-speed, low-latency communication between CPUs and I/O devices (up to 56 Gbps).
ServerNet: The legacy high-speed, point-to-point switched fabric used in older S-series and Integrity i-series systems.
CLIMs (Cluster I/O Modules): Specialized offload engines for networking (IP CLIM), storage (Storage CLIM), and telco protocols. They handle I/O processing to free up the main host CPUs.
Integrated Software Stack
The NonStop platform is a “tightly coupled” environment where hardware and software are integrated for availability.
NonStop OS (NSK): A message-based operating system that manages the distributed resources as a single system image.
HPE NonStop SQL/MX: A distributed, fault-tolerant relational database that provides ANSI SQL compliance and automatic load balancing across the cluster.
HPE Pathway (TS/MP): An application server and middleware framework that manages workload distribution, load balancing, and automatic process restarts.
TMF (Transaction Monitoring Facility): Ensures database integrity by managing atomic transactions; if an update fails, TMF automatically rolls back the changes.
Modern Deployment Options
HPE Virtualized NonStop (vNS): The complete software stack decoupled from proprietary hardware, allowing it to run as a set of virtual machines on industry-standard x86 servers within a private cloud (VMware).
HPE GreenLake: A consumption-based model providing NonStop capabilities as a cloud-like service.
Mark Whitfield is an experienced IT Project Manager and software developer who has spent over 22 years specialising in HP NonStop (formerly Tandem) systems. He is currently an Engagement Project Manager at Capgemini.
Career & Expertise
Whitfield’s career in HP NonStop began in 1990 and includes significant technical and leadership roles across the financial and technology sectors:
Software Development: Early in his career, he worked as a programmer for The Software Partnership (later Deluxe Data/FIS), focusing on electronic banking software like sp/ARCHITECT on Tandem mainframes.
Insider Technologies (1995–2013): He spent 18 years at Insider Technologies as a Senior Development Engineer and Project Manager. His work involved:
Developing monitoring and diagnostic software such as Reflex 80:20, Reflex ONE24, and RTLX (Real-Time Log Extraction) for payment systems.
Managing the first HP OpenView Operations Smart Plug-In certification for the NonStop platform.
Designing XPERT24, a performance tracking product for ACI’s XPNET layer.
Capgemini (2016–Present): As an Engagement Project Manager, he has led digital projects for major clients in the automotive, government, and aerospace sectors, including a cloud migration for UK Government applications.
Technical Contributions
Publications: He has authored articles for globally published journals like The Connection (2013), discussing topics such as querying terabytes of legacy transaction log data from NonStop mainframes.
Project History: He has managed high-value projects, including a £5 million initiative to migrate legacy HP NonStop software to AIX-based technologies for a large UK retail bank.
Training: He is trained in various NonStop-specific technologies, including TAL (Transaction Application Language), COBOL85, PATHWAY, and NonStop SQL.
Whitfield also maintains a professional website, mark-whitfield.com, where he provides project management templates and resources related to HP NonStop and Tandem systems.
Mark Whitfield provides a comprehensive bundle of over 200 editable project management templates designed for Agile, Waterfall, and PRINCE2 methodologies. These templates are based on over 30 years of project delivery experience and are available for purchase via his official website or Etsy shop.
Key Template Categories
The bundle includes a wide variety of tools across different formats (Excel, PowerPoint, Word, and MS Project):
Planning & Scheduling:
Plan on a Page (POaP): Over 30 PowerPoint slide examples for executive-level summaries.
Detailed Project Plans: MS Project (MPP) and Excel templates for SDLC, PRINCE2 7th Edition, and Agile Scrum projects.
Gantt Charts: Built-in tracking views for both MS Project and Excel.
Tracking & Control:
RAID Logs: Comprehensive logs for tracking Risks, Actions, Issues, and Dependencies, plus additional tabs for Change Requests and Lessons Learned.
RACI Matrix: Templates to define project roles and responsibilities (Responsible, Accountable, Consulted, Informed).
Finance Trackers: Tools for internal and external forecast vs. actual costs, including margin and variance tracking.
Agile Specific Tools:
Burn Down & Burn Up Charts: Excel-based alternatives when tools like Jira are unavailable.
Agile Story Dependency Tracking: Specifically for managing dependencies between agile stories and external suppliers.
Reporting & Governance:
Status Reports: Weekly and monthly templates in Word and PowerPoint formats.
Stakeholder Analysis: Power/interest mapping and engagement plan templates.
Benefits Realisation: Plans to track project outcomes against initial business goals.
Purchase Benefits
Lifetime Upgrades: Once purchased, all future additions and updates to the template package are provided for free.
Compatibility: Templates are designed for Microsoft Office 365 but also include Excel versions compatible with earlier software.
Support: The package typically includes walkthrough Word documents to guide users on how to use each major template.
Mark Whitfield HP NonStop Tandem experience & Project Management Templates
This resume summarizes the career of Mark Whitfield, a Senior IT Project Manager with over 30 years of experience specializing in digital and software development lifecycles, cloud migrations, and HP NonStop systems.
Core Focus: Senior Project Management for Digital/ Software Development Lifecycles (SDLC).
Expertise: Transitioning from a technical background in programming (pre-2000) to senior leadership in large-scale projects for global blue-chip companies.
Key Skills & Competencies
Methodologies: PRINCE2 Practitioner, Agile (Scrum/ Kanban), Waterfall, ITIL, ISO QA.
Project Controls: MS Project, Budget & Burn Tracking, GDPR compliance, Supplier & Stakeholder Management, Statement of Work (SoW).
Technical Proficiencies:
Platforms: HP NonStop (Tandem), Cloud Migration (Hybrid).
Languages (Historical): C/C++, Java, COBOL85, TAL, TACL, SCOBOL, SQL, MS SQL.
Utilities: PATHWAY, SCF, FUP, INSPECT, XPNET.
Professional Experience
Senior IT Project Manager (Various Projects):
Managed large-scale solutions for clients including Jaguar Land Rover (JLR), Heathrow, Royal Mail Group (RMG), NATS, and Euroclear.
Extensive work within the financial sector for Bank of England, Barclays, HSBC, Santander, Standard Chartered, Deutsche Bank, and Global Payments.
Government and public sector projects for Defra, UKEF, Welsh Water, and Scottish Water.
Early Career (Programmer / Technical Lead):
1990 – 1995: Programmer at The Software Partnership (later Deluxe Data) in Runcorn, specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers.
Education & Certifications
Degree: Higher National Diploma (HND) in Computing (Distinction, Graduated 1990).
Periphonics Corporation, founded in 1969, was a pioneer in the Interactive Voice Response (IVR) industry. The company evolved from a boutique voice response manufacturer into a key subsidiary of global telecommunications giant Nortel Networks by the late 1990s.
Founding & Early Era (1969 – 1979)
1969: Periphonics Corporation is co-founded in Bohemia, New York, by S. Thomas Emerson, who served as the original CTO.
Early 1970s: The company focused on manufacturing early computerized voice response systems.
1974: S. Thomas Emerson is named “Inventor of the Year” by the U.S. Patent Office for his work in computer technology.
Expansion & Market Leadership (1980 – 1998)
1983: Periphonics deployed the first-ever voice “call tree” (IVR system).
1980s: The company became a subsidiary of Exxon Corporation during a period of diversification by the oil giant into technology.
1991: Periphonics Limited (UK) is established to expand operations into the European market.
1992: Supplied and installed voice processing systems for the Emirates Telecommunications Corporation.
1998: Launched CallSponsor CT, a major computer telephony product that integrated IVR, skills-based routing, and call blending into a single suite.
The Nortel Era & Beyond (1999 – 2009)
1999: Nortel Networks acquires Periphonics Corp for approximately $435 million to bolster its e-commerce and internet-based service offerings.
2001: Nortel rebrands the core Periphonics technology as the Nortel Speech Server.
2005: Periphonics Limited (UK division) enters a declaration of solvency and begins liquidation as part of Nortel’s broader restructuring.
2009: Following Nortel’s bankruptcy, the assets and legacy Periphonics technologies were sold off to various telecommunications firms.
Key Products Through the Eras
Early Voice Response Units (VRUs): Proprietary hardware-based systems for high-energy physics data acquisition and early banking.
IVR “Call Trees” (1983): The foundational technology for modern automated phone menus.
CallSponsor CT (1998): A turnkey “computer telephony” suite designed to reduce installation and debugging times for call centres.
Nortel Speech Server (2000s): The evolved version of Periphonics technology integrated into Nortel’s digital network infrastructure.
Periphonics Corporation, founded in 1969, was a pioneer in the Interactive Voice Response (IVR) industry
HPE NonStop (formerly Tandem) has evolved through distinct architectural eras, each introducing specific programming languages and environments to maintain its legendary fault tolerance.
1. The Tandem Stack Machine Era (1974–1990)
This era focused on the proprietary 16-bit stack-based architecture (TNS), where software was designed to “fail-fast” and operate in process pairs.
Nov 1974: Tandem Computers founded by Jimmy Treybig.
May 1976:TAL (Transaction Application Language) launched with the first Tandem/16 (NonStop I) system. It was the only language available at launch, derived from HP 3000’s SPL.
Late 1970s:COBOL74, FORTRAN, and MUMPS were added to support business and scientific applications.
1981:NonStop II introduced support for 32-bit addressing, enabling larger application memory.
1983:SCOBOL (Screen COBOL) emerged alongside the Pathway transaction manager to handle terminal-based user interfaces and fault-tolerant logic.
1986:NonStop SQL released as the first fault-tolerant relational database language.
1987:C was introduced to the platform.
1989:Integrity S2 line launched using MIPS processors, introducing a variant of Unix called NonStop UX.
2. The MIPS RISC / Himalaya Era (1991–2004)
As Tandem migrated to MIPS processors (TNS/R), it introduced a Unix-like personality to attract modern developers while maintaining its legacy Guardian environment.
1991:Cyclone/R launched. Most software still ran in TNS stack mode using an “Accelerator” tool to translate code to MIPS instructions.
1993:Himalaya K-Series released with native-mode compilers for C and COBOL to leverage MIPS performance.
1994/1995:Open System Services (OSS) introduced a POSIX-compliant environment, enabling C++ and standard Unix utilities.
1995:Java was first supported on the platform.
1997: Compaq acquired Tandem; ServerNet became the standard interconnect.
Late 1990s: Support for scripting languages like Perl, Python, and PHP began appearing in the OSS environment.
3. The HP Integrity Itanium Era (2005–2013)
Following the HP merger, the architecture moved to Intel Itanium (TNS/E), branded as HP Integrity NonStop.
2005:NonStop i introduced. Compilers for C, C++, and Java were updated for the Itanium architecture.
2000s:pTAL (Portable TAL) became the standard for system-level programming to bridge legacy TAL code to modern RISC/Itanium architectures.
2011: Enhanced support for modern web languages and frameworks within the OSS environment.
4. The Modern x86 / NonStop X Era (2014–Present)
HPE migrated the entire stack to standard Intel x86-64 processors (TNS/X) while retaining binary compatibility for legacy applications.
2014:NonStop X launched. All languages (COBOL, C, C++, Java) were migrated to target x86-64.
2015: Transition to Hewlett Packard Enterprise (HPE) branding.
Recent Years: Integration of modern open-source dev-ops tools and languages, including JavaScript (Node.js), Python 3, Go, and Samba via the HPE NonStop OSS environment.
HPE NonStop (formerly Tandem) programming has evolved from proprietary languages designed for fault-tolerant, transaction-oriented processing (TAL, COBOL85) to supporting open-source languages (Java, C++, Python, PHP) on modern x86-64 hardware. The ecosystem spans from the initial Guardian OS to modern J-series and L-series OS, supporting TNS, TNS/R, TNS/E, and TNS/X architectures.
Key Programming Languages & OS Timeline
1970s–1980s (Tandem Guardian): Core development centered on TAL (Transaction Application Language) (system programming), COBOL85 (business logic), and TACL (Tandem Advanced Command Language) (command shell scripting).
1990s (Guardian 90 / NonStop UX): Introduction of C and C++ for more flexible application development, alongside Pascal and FORTRAN.
2000s (H-Series / J-Series – Itanium): Shift towards Java and enhanced support for C/C++ in the Pathway server environment.
2010s–Present (J-Series / L-Series – x86-64): Modern NonStop systems, particularly on x86-64, expanded to include scripting languages like Perl, PHP, and Python within the Open System Services (OSS) environment.
pTAL (Portable TAL): Introduced to bridge native TAL to newer, more portable processor architectures.
Operating System & Architecture Evolution
Guardian (TNS): The foundational OS, relying on Tandem’s native stack, with TAL as the primary low-level language.
OSS (Open System Services): Introduced to bring POSIX-compliant, Unix-like functionality to NonStop, enabling easier porting of C/C++ and open-source applications.
Modern OS (J-series/L-series): Supports both Guardian (native) and OSS environments, allowing for a hybrid approach where traditional transaction processing (COBOL/TAL) mixes with modern web services (Java/Python).
HPE NonStop Pathway (now often part of NonStop TS/MP) has a legacy spanning nearly five decades, evolving from a terminal management system into a sophisticated middleware for high-scale, fault-tolerant Online Transaction Processing (OLTP).
Comprehensive Evolution Timeline
1976: Genesis (Tandem Computers) The HP NonStop platform was originally introduced by Tandem Computers Inc. as the first fault-tolerant commercial computer. Pathway was soon developed to manage the distribution of transaction requests across multiple server processes.
1980s: The Classic Pathway Era Pathway became the standard for “Screen COBOL” applications. It introduced the PATHMON process to monitor and manage serverclasses, ensuring that if one process failed, another would immediately take its place.
1997: Compaq Acquisition Compaq acquired Tandem, integrating the NonStop technology into its enterprise portfolio. During this time, Pathway began adapting to newer networking protocols and client-server architectures.
2002: Hewlett-Packard (HP) Acquisition HP merged with Compaq, and the platform was rebranded as HP NonStop. Pathway evolved into NonStop TS/MP (Transaction Services/Massive Parallelism), allowing for even greater scalability across massive clusters of processors.
2014–2015: The x86 Revolution HP announced the NonStop X architecture, moving the platform from Itanium processors to standard Intel x86 hardware. Pathway (TS/MP) was optimized to run on this new architecture, providing the same high availability with modern hardware performance.
2015–Present: HPE and Modern Middleware Following the split of HP, Hewlett Packard Enterprise (HPE) continued developing Pathway. Modern versions (like NonStop TS/MP 2.8) support advanced features like:
Dynamic Server Processes: Automatically scaling server instances based on load.
Heterogeneous Interoperability: Allowing TUXEDO or Java clients to access Pathway servers.
Virtualization: Deployment via HPE NonStop Virtual Enterprise (vNS).
Core Components Over Time
PATHMON: The “manager” process that monitors all objects in the environment.
PATHCOM: The command-line interface used to configure and start Pathway objects.
PROject Templates 
