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
Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager and Engagement Manager with over three decades of experience in software development lifecycle (SDLC) delivery.
Mark Whitfield, High-Level Career Summary from 1990 thru 2026
Over his career, he has transitioned from deep technical engineering on legacy systems (HPE NonStop formerly Tandem Computers) to enterprise-scale digital transformation, cloud migrations, and API-led integrations. He is also the author of a comprehensive online toolkit for project delivery frameworks.
Click the ‘Company Worked‘ links below for more detail as required.
Project Management Career Breakdown:
1. Early Engineering & Technical Analysis Era (1990–1995)
Geographical Location: Salford Quays, UK (office); London, UK; Client sites across Europe/ Middle East
Clientsinclude: Global Payments, Standard Chartered, Girofon, Rabobank, CRESTCo (Euroclear), Alrajhi Bank, LloydsTSB, HSBC, Santander, Bank of Ireland, Bank of Valletta (Malta) and both Commercial and Piraeus Bank (Greece)
Main Focus Items: Infrastructure consulting, volume testing, system management & monitoring, and Service Level Agreement (SLA) monitoring for critical path payment applications. Attending related conferences, EBUG, ITUG, BITUG, SATUG
Technology Areas: HPE NonStop monitoring, ATM/POS system & transaction monitoring and stock settlement.
Geographical Location: Woking / Bracknell / UK wide
Client: Lloyds Banking Group
Main Focus Items: Modernising legacy ATM software and directing hardware/software transitions. Implementing ProClassic/Enterprise and PC/E SmartClient (Win 7) to replace the existing ProCash/NDC (Win XP) Stacks on a variety of multivendor devices.
Technology Areas: Multi-vendor hardware & software integration for ATMs.
Geographical Location: Wigan / Greater Manchester, UK
Client: Betfred Online and Mobile
Supplier Management: for external software suppliers like Degree53, Playtech, Onionsack, Intelligent Payments (Myriad), Inspired, iovation, StreamUK, Finsoft, Ineda, OtherLevels, Appsflyer, Income Access, Activewin, Virgo, Virtue Fusion, In Game Media, Satellite Information Services (SIS) and IGT
Main Focus Items: Taking new sports and virtual gaming components live, integrating payment gateways, managing app release cycles, and handling regulatory compliance.
In addition to his consultancy work, Mark Whitfield actively publishes his extensive collection of Project Management Templates, which are actively utilized across the industry for RAID Logs, Agile Burndown Charts, and Plan on a Page (POaP) blueprints.
Mark Whitfield spent 18 years (August 1995 – September 2013) at Insider Technologies Limited (ITL), a Manchester-based software house specialising in high-availability tracking, service management, and transaction monitoring. Entering as a Senior Programmer, he climbed through the ranks to become an Operations Products Manager and, ultimately, the Project Manager for Strategic Technical Initiatives.
His core technical contribution revolved around developing and managing platform-health diagnostic modules, automated event filtering, and multi-currency transaction log trackers.
He focused heavily on the HPE NonStop (Tandem) kernel, integrating these mainframes with Windows, Unix, and Linux open systems. His work protected critical banking infrastructure, such as transaction loops feeding into ACI BASE24 ATM/POS switches and major national payment clearings.
Detailed Timeline Breakdown
🔹 The Foundational Tandem Era (1995–1999)
This period focused on building out bespoke low-level mainframe diagnostic scripts, real-time logging, and bracing critical infrastructure for the millennium bug.
1995: Joined Insider Technologies Limited at Salford Quays after departing Deluxe Data. He began programming SCOBOL green screens and engineering PATHWAY servers to query raw Guardian operating system procedures.
1996: Core developer for the flagship Reflex monitoring suite (Reflex 80:20). He co-authored the Console module for HPE NonStop Event Management Service (EMS) viewing, alongside tracking blocks for system components like CPU, Disk, and Processes.
1997: Transitioned into an infrastructure consulting capacity, designing code routines to test physical hardware throughput.
1998: Formally appointed as the ITL Operations Products Manager. He orchestrated high-performance benchmarking tests on newly deployed Tandem S7000 processing hardware nodes for Euroclear (formerly CRESTCo), validating infrastructure that handled 88% of UK equities.
1999: Directed critical, deep-level automated Y2K code auditing. This guaranteed that real-time tracking loops and MultiBatch scheduling automation would accurately handle the date rollover for clearing partners like the Bank of England and Deutsche Bank.
🔸 The Operations & Middleware Integration Era (2000–2005)
This era bridged the gap between rigid standalone mainframes and modern open-system dashboards, creating cross-platform monitoring frameworks.
2000: Spearheaded deep-layer integration projects connecting legacy frameworks to distributed enterprise collectors like TIVOLI, COMMAND/POST, and third-party file monitors.
2001: Supervised 24×7 enterprise support teams handling cryptographic security frameworks for Thales e-SECURITY products, overseeing the SafeSign Authentication and Management Server lines on Windows/Unix.
2002: Led technical rollouts for ITL’s interactive Systems Training Platform, deploying patented system-cloning configurations to let institutional clients practice outage responses safely.
2003: Drove cross-platform middleware compatibility protocols, building hooks between the NonStop kernel and WebSphere MQ (MQSeries) message streams to trap transactional anomalies in real-time.
2004: Advanced to Project Manager – Strategic Technical Initiatives, implementing PRINCE2 governance for new product R&D pipelines.
2005: Began standardising the technical architecture of Reflex ONE24, transitioning the vintage monitoring code toward centralized electronic web consoles.
🔹 The Strategic Initiatives & Product Management Era (2006–2013)
Whitfield shifted into pure-play product management, expanding corporate web assets and publishing technical documentation before navigating the company through an MBO.
2006: Pioneered custom transaction parsing frameworks for payment switches, resulting in the foundational engine layout of Sentra and the Real-Time Log Extraction (RTLX) engine.
2007: Acted as the primary corporate website architect and author, modernising Insider’s public presence by building out and managing content deployments on DotNetNuke (DNN).
2008: Managed implementation pipelines for XPERT24, a highly specialized utility engineered specifically for performance tracking across complex BASE24 XPNET banking environments.
2010: Guided software engineers through logic modifications to intercept multi-currency retail POS and ATM interchange drops down to the millisecond.
2011: Coordinated agile deployment sprints for financial institutions to meet strict compliance laws surrounding automated data storage and long-term file retention.
2012: Provided the project governance behind the scenes during Insider Technologies’ internal structural transitions, supporting a £3m Management Buyout (MBO).
2013: Authored a major technical summary published globally in the recognized HP NonStop industry journal, The Connection, defining payment software lifecycles. Concluded his 18-year run at ITL in September to join Wincor Nixdorf.
(Note: The product lines Whitfield built and governed were later acquired by ETI-NET in 2015, where his original RTLX utility was rebranded as C-Deep for Transaction Monitoring.)
C-Deep (formerly known as RTLX developed by Insider Technologies Limited) is an enterprise-grade, real-time transaction and payment monitoring software product. It is currently owned, maintained, and distributed globally by ETI-NET.
Product Overview & Key Features
The primary objective of C-Deep for HPE NonStop is to ensure fault tolerance, detect transactional vulnerabilities, and prevent outages within major financial ecosystems.
Target Environment: It is deployed alongside primary mission-critical payment engines, primarily operating as a high-performance add-on to ACI Worldwide’s BASE24™ solution or as a standalone tracker on HPE NonStop systems.
Architecture: The software utilizes lightweight extraction clients on the NonStop kernel to read Transaction Log Files (TLF) and POS Transaction Log Files (PTLF). It offloads data parsing to a C-Deep collector on Windows Server, keeping the primary switch’s CPU overhead at zero.
Data Retrieval: It stores and indexes historical transaction fields into annual databases for 10+ years, making it fully searchable to meet strict data regulatory compliance laws.
Granular Querying: Operators can isolate variables down to Bank Identification Numbers (BIN), detecting interchange timeouts, clearing delays, or switch drops down to the millisecond.
Detailed Timeline Breakdown by Era and Year
The technical evolution of this platform reflects the wider political and economic changes in global banking, transitioning from early bespoke mainframe logs to modern, automated cyber-resiliency environments.
🔹 The Foundational & Legacy Tandem Era (1989–2000)
This era centered around high-security, fault-tolerant mainframes built for NATO-aligned military communications and early banking networks following the end of the Cold War.
1989: Insider Technologies Limited is incorporated in the UK to manufacture specialized monitoring code for highly robust computer systems.
1990–1995: The vendor releases its foundational “Reflex” software suite for the Tandem Guardian operating system, offering real-time transaction diagnostics without interrupting physical processing operations.
1996–1999: The platform adds “MultiBatch” automation to orchestrate complex batch settlements. Engineering pivots toward critical Y2K code auditing to prove that automatic logging routines would survive the year 2000 date rollover.
🔸 The Multi-Platform & Financial Compliance Era (2000–2015)
This era mark’s the product’s rise to prominence as a core tool for transaction transparency across global clearings houses, reacting to rapid financial sector deregulation.
2001–2003: The architecture scales up from simple hardware tracking into dedicated operational security. The vendor expands the footprint into financial clearings, tracking transaction security for system-critical clearers like the Bank of England.
2004–2007: The developer releases RTLX (Real-Time Transaction Logging/Reactor), standardizing visibility from the point-of-sale terminal tap to the back-end ledger settlement. It adds cross-compatibility for Windows, Unix, and Linux systems alongside standard Tandem NSK systems.
2008–2012: Amid market volatility following the 2008 financial crash, transaction tracking rules tighten. RTLX adds specialized configuration engines to map high-volume dates (e.g., Black Friday) to proactively flag message queues and clear bottlenecks before causing outages.
🔹 The Acquisition & Integration Era (2015–Present)
This era sees consolidation in the HPE NonStop market, transforming the legacy product into a fully modern cyber-resilient and automated tracking ecosystem.
2015–2021: Real-time transaction frameworks become critical for compliance. To expand global distribution channels, ETI-NET formalizes an agreement to acquire and absorb Insider Technologies’ core system software catalog.
2022–2023: ETI-NET rebrands the classic software stack to streamline its message. The system monitoring side (Reflex) becomes Sentinel, while the specialized payment switch transaction monitor (RTLX) is official re-launched as C-Deep for Transaction Monitoring.
2024: ETI-NET pushes C-Deep through HPE Pointnext Services, making it directly purchasable within standard Hewlett Packard Enterprise customer channels. Integrations are updated to match the NIST 2.0 Cybersecurity Framework.
2025–2026: Modern upgrades focus heavily on end-to-end data auditing, automated email/SMS alerting systems, and specialized dashboard analytics tailored for complex, multi-currency transaction paths.
ETI-NET C-Deep real-time transaction and payment monitoring product timeline
Running natively on the fault-tolerant HPE NonStop platform (formerly Tandem Computers), it utilizes a modular architecture to acquire, authenticate, route, and authorize financial transactions.
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
The application modules of ACI BASE24 (spanning Classic and modern BASE24-eps configurations) are categorized in complete detail below:
💳 Channel Acquisition Modules
These front-end modules connect directly to consumer-facing self-service devices and touchpoints to ingest financial messages.
BASE24-pos: Facilitates electronic data interchange with Point of Sale (POS) merchant terminals, accepting debit, credit, and smart card transactions.
Stored Value Module (SVM): A localized sub-component within channel management dedicated to the online issuance, balance check, and validation of stored-value gift cards.
🔄 Routing, Switching, & Interfacing Modules
These modules orchestrate the delivery of messages from endpoints to localized authorization hosts or global networks.
BIC ISO Interface: Implements standard ISO 8583 payment messaging protocols to communicate directly with major international networks (such as Mastercard or Visa).
ACI Commerce Gateway: Operates as a secure payment gateway firewall, linking internal HPE NonStop processing routines with public internet channels.
🔐 Security & Authentication Modules
Data integrity modules protect transactions and enforce industry-standard security.
Transaction Security Services (TSS): Manages PIN verification, encryption/decryption tasks, and hardware security module (HSM) messaging, including native Triple DES (3DES) support.
These back-end engines decide whether a transaction flight should be accepted, declined, or deferred.
Enhanced Authorization Module: Runs customized business logic scripting to evaluate cardholder limits, fraud signals, and stand-in authorization processing.
Positive Balance File (PBF) Interface: Interfaces with real-time local file structures to check account limits when backend core banking host systems are offline.
📊 Back-Office & Data Management Modules
These modules ensure post-transaction data is accounted for, settled, and audited.
Interchange Log File (ILF) / Transaction Log File (TLF for ATM, PTLF for POS): Core architectural data constructs that maintain comprehensive records of all ongoing financial messages for balancing and error recovery.
BASE24-infobase: Provides centralized tools for operational reporting, financial data clearing, settlement processing, and accounting audits.
🛠️ HPE NonStop System Integration Architecture
BASE24 is highly reliable because it integrates with native HPE NonStop mainframe utilities:
PATHWAY (PATHCOM): Acts as the transaction processing middleware to dynamically load-balance BASE24 server processes across multiple CPUs.
Enscribe & NonStop SQL/MX: Serves as the native flat-file or relational database layer optimized for low-latency, high-concurrency write operations.
HPE Shadowbase / AutoTMF: Interacts with the Transaction Monitoring Facility (TMF) to enable active/active dual-site replication, providing instant failover for near-zero transaction downtime.
ACI BASE24 core components on HPE NonStop mainframe platform
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
Mark Whitfield’s project involvement with ACI Worldwide’s BASE24 / BASE24-eps and XPNET communication middleware is rooted deeply in his tenure at Insider Technologies Limited (ITL) and subsequent senior project management roles. His work primarily spans real-time performance monitoring, transactional tracking, and infrastructure management across HPE NonStop (Tandem) platforms.
His involvement across specific initiatives and client deployments is categorised below:
Product Development & R&D Projects
BASE24 XPNET Monitoring in Reflex ONE24
Role: R&D Lead and Software Developer.
Involvement: Researched and developed specialised software utilities to automatically detect and extract architectural information from XPNET components. He leveraged XPNET EMS (Event Management Service) events and user requests to facilitate real-time monitoring. These components were mapped into graphical drill-down object trees inside the Reflex Status Monitor application.
XPERT24 (Performance Monitoring & Tracking)
Role: R&D Lead, Technical Contributor, and Project Manager.
Involvement: Managed the lifecycle of this NSK-based monitoring tool, which tracks XPNET performance counters including states, traffic rates, and queues across lines, stations, nodes, and processes. The project also involved building mechanisms to track transaction approval and denial metrics over ATM and POS networks.
Client Deployment & Customisation Projects
HSBC Transaction Monitoring Project
Role: Technical Lead / Solution Designer.
Involvement: Designed and executed the implementation of ITL’s RTLX Reactor product on HP NonStop. The project required mapping monitoring solutions into HSBC’s heavily customised payment ecosystem to track ATM and POS transactions governed by BASE24.
Off-shore Retail Banking Transaction Tracking (Riyadh, Saudi Arabia)
Role: IT Project Manager (2013).
Involvement: Managed the delivery of a massive log-parsing project utilizing the BASE24 Classic payment framework. The project safely extracted, relayed, and optimized the parsing of multiple Terabytes of historical ATM and POS transaction logs archived on tapes, moving them into a modern reporting system.
Global Payments / Standard Chartered Integration Project
Involvement: Integrated real-time BASE24 transaction tracking and XPNET capabilities directly into external corporate enterprise frameworks, specifically IBM Tivoli and XPERT24.
Lloyds Banking Group (LBG) Estate Transformation
Role: Senior Project Manager.
Involvement: Led a massive migration strategy that decoupled ATM driving responsibilities away from BASE24 Classic running on HP NonStop platforms, transferring them to Wincor’s ProClassic Enterprise (PC/E) environment.
Mark Whitfield’s IT project management and software engineering career spans over three decades, progressing from early electronic banking programming on Tandem Mainframes (now known as HPE NonStop) to senior delivery of enterprise-scale middleware, cloud, and digital transformation initiatives.
The high-level chronological timeline (with links) of his professional eras and key project history is broken down below.
💻 1990–1995: Early Programming & Lead Analysis Era
During this foundational era, Whitfield operated as a Programmer and Lead Analyst specializing in core electronic banking software frameworks.
The Software Partnership / Deluxe Data (1990–1995): Developed and enhanced the sp/ARCHITECT-BANK platform. His technical responsibilities focused heavily on coding within Tandem Mainframe environments (now HPE NonStop) using C, C++, TAL, COBOL, and PATHWAY architectures.
Deluxe Data International Operations, Wingate House, Northway, Runcorn
Barclays On-Site Delivery (Early 1990s): Deployed on-site at the Barclays facility in Knutsford, Cheshire. He was responsible for core code development and system architecture design on the Barclays Business Master II (BBM II) electronic banking initiative and subsequent billing modules developed in Poole, Dorset.
Barclays, Wimborne Road, Poole, Dorset
🛠️ 1995–2013: Senior Development & Strategic Project Management Era
Transitioning to Insider Technologies Limited at Salford Quays, Manchester, Whitfield progressed into high-level technical project delivery and strategic product management.
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
Reflex Monitoring Suite R&D (1995–1996): Appointed as a core developer to design platform health and diagnostic plug-in modules for the flagship Reflex 80:20 tracking console.
CRESTCo Infrastructure Integration (1997–1998): Acted as a technical infrastructure consultant for CRESTCo (now Euroclear). Managed hardware benchmark coding and testing for newly deployed Tandem S7000 processing nodes.
CRESTCo in 1997 on St. Katherine’s Dock near Tower Hill tube station
Real-Time Tracking Protocols (1999–2001): Oversaw multi-organizational telemetry deployments for the Bank of England and Deutsche Bank, leveraging specialized MultiBatch scheduling utilities and automated file monitors.
Hewlett-Packard (HP) Certification Initiative (2002–2003): Successfully drove the rigid compliance and verification process to secure official certification for the first HP OpenView Operations (OVO) Smart Plug-In built for NonStop mainframe environments.
First HP OpenView Operations Smart Plug-In for HPE NonStop environments
ATM Log Extraction Deployments (2004–2007): Led technical delivery teams implementing automated transaction log extraction layers (RTLX and Sentra) to audit ATM networks for major retail financial brands like Alliance & Leicester (now Santander) and HSBC.
Cross-Border Retail Banking Rollout (2008–2010): Served as Project Manager overseeing a high-volume, cross-border ATM and Point-of-Sale (POS) environment monitoring expansion for a prominent Saudi Arabian Retail Bank.
Cross-border ATM and Point-of-Sale (POS) environment monitoring expansion
Enterprise Transaction Monitoring (2011–2013): Functioned as Project Lead to bridge retail banking transaction networks with corporate governance architectures. Integrated critical pathways for Standard Chartered and Global Payments into TIVOLI and XPERT24 using ACI’s XPNET infrastructure.
Wincor Nixdorf Banking Division (2013–2014): Retained as Project Manager for Professional Services. He directed a massive hardware and software transition stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme whilst also providing a qualified management link with Wincor Nixdorf, Paderborn (Germany) for subject matter expertise, as part of the transition.
🎮 2014–2016: Digital Infrastructure & Enterprise Betting Era
Whitfield shifted his delivery domain focus from banking mainframes into real-time high-transaction digital platforms.
Betfred Project Delivery (2014–2016): Managed IT infrastructure and digital systems alignment projects, supporting high-throughput retail and digital consumer gaming workflows.
☁️ 2016–Present: Cloud Integration, Middleware, & Public Sector Era
In this current era, Whitfield acts as a senior, SC-cleared Senior IT Project Manager specializing in hybrid cloud migrations and API-led integration.
Capgemini UK Consultancy (2016–Present): Leading massive corporate and public sector agile/waterfall delivery initiatives. His technical program management footprint expands across a vast roster of tier-one enterprise environments:
MuleSoft Ecosystem Deployments: Directing system integration projects utilising the Salesforce MuleSoft suite, spanning API lifecycle design, Anypoint Code Builder configurations, and hyper-automation flows.
Multi-Sector Enterprise Clients: Orchestrating cloud migrations, middleware application refactoring, and data pipelines for Jaguar Land Rover (JLR), Heathrow Airport, Royal Mail Group (RMG), NATS (National Air Traffic Services), Welsh Water, Rabobank, Barclays, and UK Export Finance (UKEF).
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK
HP OpenView Operations (OVO) is a foundational enterprise systems management (ESM) platform designed to centrally monitor and manage infrastructure, multi-vendor operating systems, and enterprise applications across distributed IT environments.
The system operates on an Agent-Server Architecture. Core components include:
Management Server: Central hub that aggregates system logs, processes alerts, correlates events, and triggers automated remediation scripts.
Smart Plug-ins (SPIs): Specialized modular add-ons that inject domain-specific monitoring logic for applications like Oracle databases, Microsoft Active Directory, or SAP.
Intelligent Agents: Lightweight background processes deployed on managed nodes to collect log events, metrics, and state data, formatting them into structured OVO messages.
1. HP OVO screenshot in 2002
2. HP OVO screenshot in 2002
See bottom of this post for HPE NonStop (previously Tandem) monitoring in OpenText Operations Bridge Manager. I overlooked an integration with HP OpenView Operations for a HPE NonStop product in 2002, called Reflex 80:20.
Detailed Timeline Breakdown by Era and Year
🌅 Era 1: Origins and The Foundation (Late 1980s – 1994)
This era established HP’s footprints in IT infrastructure management, pivoting from pure SNMP network map discovery toward server telemetry.
Late 1980s: HP releases Operations Center (OpC) as an add-on application for its core Network Node Manager (NNM) platform. It replaces slow SNMP polling with Remote Procedure Calls (RPC) to gather host logs.
1990–1993: HP scales OpC into a robust engine capable of executing basic automation scripts on remote UNIX boxes when specific thresholds break.
🚀 Era 2: The “ITO” and OpenView Operations Boom (1995 – 2000)
The framework shifted from isolated utilities into an integrated, market-dominating enterprise suite.
1995: HP tightly merges NNM and Operations Center into a single product called IT Operations (ITO) Version 3.x.
1996:HP OpenView Service Navigator is embedded into the product line. It provides a graphical hierarchy of business services instead of just a raw list of broken servers.
1999: The suite formally adapts to include broad SNMP traps alongside its core agents and is renamed HP OpenView Operations ITO.
🔄 Era 3: Platform Split and VantagePoint Transition (2001 – 2006)
HP decoupled its codebases to natively handle Windows NT/2000 scaling alongside legacy Unix environments while heavily investing in product renaming.
2001: HP briefy rebrands the suite to HP VantagePoint Operations (VPO). However, customer brand loyalty forces them to quickly pivot back to the popular HP OpenView Operations (OVO) naming convention.
2002: Codebases officially bifurcate into OVOU (OpenView Operations for Unix) and OVOW (OpenView Operations for Windows, built natively on Microsoft WMI frameworks).
2005:OVO Version 8.0 drops. It features heavy integration capabilities for external service desks, advanced HTTP/HTTPS agent communication protocols, and a refreshed Java GUI console.
🏢 Era 4: The Business Technology Optimization (BTO) Era (2007 – 2016)
Massive corporate acquisitions changed the software landscape. OVO ceased to be a standalone system monitoring tool and transformed into an automated operations center.
2007: HP drops the legendary “OpenView” moniker. Following the acquisitions of Mercury Interactive, Peregrine, and Opsware, the suite is rebranded as HP Operations Manager (HPOM) under the HP Business Technology Optimization (BTO) banner.
2009: HP rolls out Operations Manager i (OMi), integrating topology-based event correlation (TBEC) to suppress duplicate alert storms across the data center.
2015: Hewlett-Packard splits into two companies; the portfolio lands under Hewlett Packard Enterprise (HPE). The engine is bundled into the HPE Operations Bridge (OpsBridge) suite.
☁️ Era 5: Divestiture and Modern Legacy (2017 – Present)
2017: HPE spins off its enterprise software division. The entire legacy OpenView/Operations Manager portfolio is sold to Micro Focus.
2023:OpenText completes its acquisition of Micro Focus. The underlying technical heritage of the old OVO agents survives today, evolved into cloud-ready containerized architectures inside the modern OpenText Operations Bridge cloud monitoring portfolio.
OpenText Operations Bridge Manager Screenshot example
HPE NonStop (previously Tandem) Monitoring
Micro Focus Operations Bridge (now part of OpenText AI Operations Management) provides end-to-end IT monitoring by consolidating data from over 200 sources. For HPE NonStop, it utilizes specialized Management Packs to ingest metrics, system events, and health data for comprehensive, real-time hybrid IT analysis.
To monitor HPE NonStop servers using the modern OpenText Operations Bridge/AIOps platform, the setup revolves around the Operations Bridge Manager (OBM) and targeted management packs:
Management Packs for HPE NonStop: OpenText provides specific management packs and solutions designed for NonStop systems. These capture system health, CPU/disk metrics, pathway status, and system messages.
Operations Agent: A lightweight agent is deployed directly on the NonStop nodes, which securely streams local performance data and events back to the central OBM console.
Centralized Event Consolidation: OBM acts as a “manager of managers”. It ingests the NonStop events and correlates them alongside data from your cloud (AWS/Azure), containers, and network endpoints.
AIOps and Remediation: The platform utilizes built-in machine learning to reduce alert noise and accelerate root cause analysis. You can also use automated Runbooks to automatically remediate known issues on the NonStop platform.
Because the platform has been fully integrated into the OpenText portfolio, these integrations are supported across containerized deployments, on-premise, or SaaS models.
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;
Mark Whitfield is a Greater Manchester-based Senior IT Project and Engagement Manager.
With over 30 years in the IT and software development industry, he has continuously upskilled in project delivery, Agile methodologies, cloud platforms, and cyber security.
Phase 1: Foundational Education
1985 – 1988: Leigh College, UK
Focus: Computer Science and Biology (‘A’ Levels)
1988 – 1990: University of Greater Manchester (formerly Bolton Institute of Higher Education, BIHE)
Focus: Higher National Diploma (HND) in Computer Studies (Graduated with Distinction; First overall in the year)
Key Modules: System Analysis, Programming Methodology, Database Architecture, and Business Information Systems
Phase 2: Project Management & Professional Training
2000 – 2006: Industry Integration & Early Methodologies
Focus: Service-Oriented Architecture (SOA), Agile, Sales, and early project management
Courses/Certifications: Sales and Marketing (In-house Outsource, 2001), Web Services and SOA (Insider Technologies, 2005), PRINCE2 Foundation (2006), Designing Good Marketing Literature (SkillPath Seminars, 2006)
2009: Digital & Communications
Focus: Digital marketing and content
Courses: Writing for the Web, and Website Promotion and Visibility by Design (iTrain Education)
2011: Structured Frameworks
Focus: Formal project frameworks and delivery methodologies
Courses/Certifications: PRINCE2 Foundation & Practitioner (ILX Group), Agile Scrum (RADTAC)
2012: Operational Management
Focus: Service management best practices
Courses/Certifications: ITIL Foundation
Phase 3: Advanced Engagement & Enterprise Training
2017 – 2019: Capgemini Engagement & Compliance
Focus: High-level engagement management and corporate governance
Courses/Certifications: Advanced Engagement Management Certification (Level 2), Group Anti-Corruption, and Intellectual Property Rights (IPR) Training
2022: Cloud Modernization
Focus: Enterprise cloud computing fundamentals
Courses/Certifications: AZ-900 Microsoft Certified Azure Fundamentals
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 HPE NonStop architecture (originally engineered by Tandem Computers in 1976) is a specialized, 100% fault-tolerant computing platform designed to achieve continuous application availability and absolute data integrity. Unlike traditional mainframes or high-availability clusters that rely on rapid rebooting or switching resources upon a crash, NonStop prevents downtime entirely by masking failures through a hardware-software co-designed shared-nothing architecture.
At the physical tier, a NonStop system is built as a Loosely Coupled Multiprocessing (LCM) environment.
Independent Processor Modules: A single system consists of 2 to 16 independent CPUs (expandable via clustering up to 4,000+ CPUs). Each processor module contains its own dedicated Intel Xeon cores, memory, and I/O logic. Processors share no main memory, buses, or execution states. This isolation guarantees that a memory corruption or hardware crash in one CPU cannot physically propagate to another.
The Interconnect Fabric (ServerNet / RoCE): Because CPUs share nothing, they cooperate entirely by passing high-speed messages. Historically, this handled via a proprietary dual-bus named Dynabus, which evolved into ServerNet (the foundational grandfather of InfiniBand). Modern HPE NonStop X systems leverage RDMA over Converged Ethernet (RoCE) as the multi-gigabit interconnect fabric, providing dual-path, point-to-point messaging with sub-microsecond latency.
Dual-Ported, Redundant I/O Controllers: Every storage device, network interface, and controller card is physically dual-ported and cross-connected to two separate processor modules. If Processor A fails, Processor B seamlessly accesses the disk or network line using the alternate hardware path.
No-Spare, Active-Active Components: Every active element operates under a “no-spare” philosophy. Power supplies, cooling fans, and storage arrays are fully redundant and hot-swappable, ensuring the system can be repaired or upgraded while fully operational.
2. Operating System Architecture: NonStop OS (Guardian)
The foundational operating system is NonStop OS, which embeds the Guardian Kernel.
Distributed Copy Model: Every individual processor module loads and runs its own separate copy of the Guardian kernel. Rather than a monolithic OS orchestrating all chips, the system runs as a highly cooperative, message-driven distributed microkernel OS.
The Message System: The core of Guardian is its message router. Every operational request—whether writing a line to a database, opening a network socket, or checking a disk—is written as an inter-process message sent across the RoCE fabric. If a local resource is occupied, the message router redirects the request transparently across the fabric, making the entire cluster appear to applications as a single system image (SSI).
Continuous Heartbeats: All components and processors continually broadcast periodic “alive” heartbeat messages to one another. If a processor fails to respond to a heartbeat within a few milliseconds, the remaining CPUs immediately sever ties with it, declare it dead, and safely re-route pending workloads.
3. Software Fault Tolerance: Process Pairing
Hardware isolation is only half the battle. To tolerate software failures without dropping transactions, NonStop utilizes Process Pairs.
Primary and Backup Processes: When a critical application or system service starts, it creates two instances: a Primary Process executing on Processor 1, and a Hot-Standby Backup Process residing on Processor 2.
Real-Time Checkpointing: As the primary process performs work (e.g., executing a financial transaction step), it sends regular checkpoint messages to the backup process. These checkpoints copy vital state changes, register values, and memory updates.
Instant Takeover: If Processor 1 crashes, the Guardian OS instantly promotes the backup process to Primary. Because the backup contains the mirror state of the last transaction checkpoint, it picks up execution precisely where the failed process stopped. No state is lost, no connections drop, and the end-user experiences zero interruption.
4. Database & Storage Architecture: Enscribe, NonStop SQL, and TMF
Data integrity is paramount in NonStop’s design. It enforces strict ACID compliance at massive scale through layered data management software.
Enscribe & NonStop SQL/MX: NonStop supports Enscribe (a highly resilient structured file system) and NonStop SQL/MX (an ANSI-compliant relational database management system). Both are entirely decentralized, natively distributing table partitions across different physical disk drives managed by separate CPUs.
Mirrored Disks: Storage volumes are configured via volume-level mirroring (Disk 1 and Disk 2 track identical data blocks). Disk writes are executed in parallel across distinct I/O paths. If a drive fails or a sector corrupts, reads are immediately diverted to the mirror disc.
Transaction Monitoring Facility (TMF): TMF is the protected transaction manager. It acts as a distributed two-phase commit coordinator. If an application crashes mid-transaction, or an entire processing module loses power, TMF uses audit logs to back out incomplete transactions cleanly, guaranteeing that the database is never left in an inconsistent or corrupt state.
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.
In the HPE NonStop ecosystem, EMS (Event Management Service) is the core software subsystem responsible for collecting, formatting, filtering, logging, and routing system and application event messages. It provides fault-tolerant monitoring by gathering data from EMS collectors and selectively delivering alerts to consoles, log files, or automated management applications.
The evolution and detailed historical timeline of NonStop EMS events and architecture is broken down by era below:
1. The Tandem Guardian Era (Late 1970s – 1980s)
Focus: Foundation of Fault-Tolerant Event Logging
1976: Tandem releases the original Tandem/16 (NonStop I) system. Early event handling was primarily a rudimentary terminal console logging process.
1978: System administrators struggled with message scaling as clusters and terminal networks expanded. Tandem began developing structured event tracking, paving the way for standardized subsystem messages.
1980s: Introduction of early message formatting. Event messages 1 through 511 were reserved for unformatted, raw console events. The Event Management Service (EMS) was gradually formalized to centralize scattered terminal messages.
2. The D-Series & TMF Era (1990s)
Focus: Distributed Management & The Birth of Modern EMS
1991: Tandem releases the Cyclone/R (CLX/R) and later the Himalaya K-series using MIPS processors.
1993: The publication of the seminal EMS Reference Summaries standardized EMS APIs and SPI (System Programming Interface). Event IDs were structured into standardized subsystems (e.g., negative-numbered kernel messages).
1995: The NonStop Kernel introduced Open System Services (OSS), natively integrating Unix-like event logs into the Guardian architecture.
1997: Compaq acquires Tandem Computers. EMS underwent significant rewrites to interface with remote servers and client networks. The S-Series was launched utilizing ServerNet fabric, introducing advanced, distributed event collectors and distributors.
3. The Compaq Transition & HP Integration (2000s)
Focus: Web-Based Management and Automation
2000 – 2003: Legacy ViewPoint tools were expanded. The emergence of GUI interfaces and DSM/PM (Distributed Systems Management/Performance Monitor) allowed operators to browse and filter EMS logs on alternate/primary event files.
2003 – 2005: The transition to Web ViewPoint commenced, turning text-based EMS event logs into interactive, web-based graphical operations interfaces.
2006 – 2009: With HP fully in charge after merging with Compaq, EMS event viewing was modernized through TSM (Tandem/HP Systems Management) and the Open System Management (OSM) Event Viewer.
2015 – 2017: The platform is rebranded as HPE NonStop as the architecture migrates to x86 processors. EMS systems are upgraded to handle large datasets, feeding complex event processing (CEP) and SNMP trap frameworks for modern data centers.
2018 – 2023: HPE integrates NonStop systems with HPE GreenLake. EMS event logging is modernized with API-driven integrations, allowing system events to be consumed by off-platform enterprise loggers, Splunk, and cloud-management consoles.
2024 – 2026: EMS events operate in highly virtualized and hybrid cloud (x86 and Virtual NonStop) environments. Event management heavily relies on modern distributed systems where EMS distributors push logs seamlessly into centralized IT monitoring suites and continuous availability dashboards.
The eBUG (European BASE24 User Group) Conference is the premier annual gathering for financial institutions, retail banking professionals, and technical architects utilizing ACI Worldwide’s foundational retail payment engine, BASE24 and BASE24-eps.
Operating alongside global HPE NonStop hardware environments, the conference traditionally functions as a collaborative technical focus group (TFG) and customer roundtable. It brings together industry experts to address mission-critical transaction switching, regulatory compliance mandates, payment security architectures, and core software migrations.
Detailed Era Breakdown & Timeline
Era 1: The Classic BASE24 & ITUG Tandem Era (1980s – Late 1990s)
Focus: Evolution of core ATM/POS switching on Tandem (HPE NonStop) platforms, localized compliance, and basic card processing networks.
1982–1985: The birth of the early European user networks following the launch of BASE24 software by Applied Communications Inc. (now ACI Worldwide). Early meetings are heavily dependent on regional vendor user group support.
1992: Initial formations of explicit regional sub-committees under the International Tandem User Group (ITUG). The European base of users establishes formal communication pipelines.
1996: Increased focus on the early adoption of regional card mandates, standardising early transaction switching over X.25 networks, and prepping mainframe systems for high-availability roundups.
1999: A definitive milestone focused on Y2K compliance readiness. Conferences during this era are heavily centered on stress-testing legacy BASE24 code blocks, ensuring clock dates rollover flawlessly across financial networks without disrupting global merchant processing.
Era 2: The EMV Mandate & “Classic-to-EPS” Transition Era (2000 – 2010)
Focus: Overhauling core code for Chip & PIN (EMV) regulations, migrating toward open system frameworks, and introducing the next-generation BASE24-eps payment platform.
2003:The EMV Blueprint Era. The conference takes a primary steering role for European banks facing strict Eurocard, Mastercard, and Visa (EMV) liabilities. User sessions heavily focus on updating terminal messaging scripts.
2005: Introduction of BASE24-eps to the wider user group community. Discussions shift away from the classic architecture toward modern open-systems deployments, leveraging UNIX, Linux, and IBM z/OS alongside traditional NonStop environments.
2007 (Istanbul, Turkey): The group expands geographic footprints into the borders of Europe and Asia. Themes heavily stress global interoperability, cross-border transactional routing, and real-time fraud monitoring.
2008 (Vienna, Austria): High-water mark for attendance during the mid-2000s. Presentations focus on deep-dive technical configurations of BASE24-eps Release 08.2, service-oriented architecture (SOA) wrappers, and high-availability testing matrices.
2009 (Prague, Czech Republic): Real-time monitoring tools become a central talking point. Despite global financial pressures, the user community explicitly defends the strength of HPE NonStop infrastructure for running foundational retail networks.
Era 3: Security Hardening & The Independent Pivot Era (2011 – 2018)
Focus: Adapting payment loops to rigid PCI-DSS requirements, cloud capability tracking, and shifting the conference structure to independent consulting sponsorships.
2011: Focus turns squarely onto PCI-DSS Compliance and tokenisation. Roundtables detail architectural techniques to secure transaction journals, encrypt key lines, and prevent man-in-the-middle exploits at the ATM level.
2012 (London, UK): Held at the historic Trinity House near Tower Bridge, this event marks a structural pivot. Moving away from a pure ACI-hosted workspace, independent payment consultancies (such as PayX) drive user discussions. This Technical Focus Group explicitly evaluates the limits of legacy systems against “intelligent” multi-vendor ATM software.
2015: Immediate focus addresses the challenges of Real-Time / Instant Payments mandates across the Eurozone. Systems engineers share optimization scripting paradigms to support sub-second processing SLA ceilings.
2018: The rise of Open Banking / PSD2 Regulations. Technical breakout sessions outline how to safely open classic BASE24 architectures to third-party APIs through microservices wrappers and middleware adapters without breaking strict system uptime criteria.
Era 4: Modernisation & Cloud-Native Coexistence Era (2019 – Present)
Focus: ISO 20022 message standard migrations, cloud-native deployments, and containerization strategies.
2020–2022: Transition to hybrid tracking methodologies due to travel constraints. The baseline focus targets data integration, remote system management, and virtualized system-hardening techniques.
2023–2024:The ISO 20022 Mandate. Sessions are dominated by the industry-wide migration from legacy ISO 8583 message lines to the XML-based ISO 20022 financial standard. Systems architects present automated script parsers to translate real-time payment formats across legacy logic systems.
2025–2026: Integration of Cloud-Native BASE24-eps architectures. Contemporary meetups explore containerized execution patterns, utilizing AI models within the authorization loop to spot edge-case fraud patterns in real-time, and evaluating long-term roadmaps for hardware-security modules (HSMs).
eBUG (European BASE24 User Group) Conference Overview and Chronological Timeline
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.
Sentra is a premier tracking and service management software platform developed by Insider Technologies Limited. Designed specifically for high-volume, mission-critical operations, Sentra is deployed across major financial, government, and defense institutions. It specializes in real-time tracking, information mediation, and multi-platform service level agreement (SLA) monitoring.
Insider Technologies in 2003 (San Jose), Business, Process and Systems Management for the Financial and Messaging Markets
The system operates across Windows, HP NonStop, Linux, and Unix environments to guarantee maximum uptime for transaction processing and data transmission.
Product Description & Capabilities
Sentra acts as a powerful tracking diagnostics framework. It evaluates the flow of files, payments, and system events to prevent costly service outages.
Real-Time Transaction Extraction: Utilizes extraction agents to pull live transaction data—such as ATM and Point-of-Sale (POS) logs—from core banking applications.
High-Speed Middleware Ingestion: Relays transaction lifecycle files (TLF) directly to a Windows server and Microsoft SQL database. This uses the company’s proprietary, high-speed TCP/IP sockets protocol known as FastPipe.
Rigorous SLA Enforcement: Provides end-to-end monitoring metrics optimized to help financial firms achieve extremely demanding targets, including 99.999% system availability.
Detailed Timeline Breakdown by Year
Because Insider Technologies is a private, specialized enterprise software house, its continuous internal product updates are primarily mapped through corporate evolution and key platform milestones:
1989 — Corporate Foundation
Insider Technologies Limited is incorporated in Manchester, UK. It targets 24×7 mission-critical systems like Tandem Computers (which later evolved into HP NonStop computing architecture).
1990s to Early 2000s — The Monitoring Evolution
The company relies heavily on its early flagship monitoring software suites, Reflex and MultiBatch.
Recognizing a shift toward heterogeneous environments, engineering teams begin conceptualizing Sentra to bridge real-time tracking between Windows and legacy systems.
2004 — Core Sentra Framework Launch
Official design, infrastructure layout, and core coding begin for the specialized Sentra platform architecture.
Sentra is formalized to extend tracking metrics outside of traditional mainframe environments into multi-platform Linux, Unix, and Windows installations.
2006 — Banking Application Integration
Development accelerates on custom add-ons to integrate Sentra directly with core banking infrastructure.
Teams design specialized mechanisms to track high-volume transactions routed via ACI Worldwide’s popular BASE24™ transaction-processing software.
2008 to 2011 — The RTLX Reactor Expansion
Insider Technologies releases RTLX Reactor, a major add-on module built entirely on top of the Sentra framework.
This expands Sentra’s market footprint by offering retail banks direct, real-time diagnostic visibility into live ATM and POS cash terminal traffic.
2013 — Framework Optimization & Digital Web Presence
A multi-year architectural overhaul wraps up, introducing enhanced information mediation and updated corporate digital resources mapping the platform’s core tracking methodologies.
Celebrating 30 years in operation, Insider Technologies rolls out modernised visual dashboards and broader diagnostic tracking capabilities across the Sentra portfolio. This addresses the escalating scale of electronic payments.
2024 to 2026 — PartnerOne Era & Cyber-Resilience
Insider Technologies transitions into operating as part of the global PartnerOne group.
Sentra continues to serve as an indispensable middleware tracking and monitoring asset. It runs alongside updated proactive cybersecurity, XDR, and IT operations infrastructure tailored for the UK government, defense sector, and multinational banking institutions.
ActionView.400 is an enterprise tracking and diagnostics software solution developed by Insider Technologies Limited. It was purpose-built as a dedicated monitoring tool for the Open System Interconnection / Message Handling System (OSI/MHS) X.400 subsystem deployed on Tandem, Compaq, HP, and HPE NonStop server platforms.
The software acts as a critical infrastructure layer used heavily by banking institutions, telecommunications providers, and government/military defense sectors.
It ensures that high-volume, secure electronic mail infrastructure meets strict Service Level Agreements (SLAs) by allowing engineers to account for every message, calculate end-to-end processing times, and issue real-time tracking metrics.
Detailed Timeline Breakdown by Year
1989: Insider Technologies Limited is incorporated in Manchester, England, by a collective of IT industry veterans. The firm initially focuses on building service management and custom tracking middleware for the rapidly expanding Tandem NonStop server ecosystem.
1990s (Early to Mid): As X.400 protocols become the global standard for secure EDI (Electronic Data Interchange) and military messaging, Insider Technologies develops ActionView 400. The product is integrated directly into Tandem’s core software stack and begins shipping natively with Tandem NonStop platforms.
1997: Tandem Computers is acquired by Compaq. ActionView 400 is sustained through this transition to maintain critical operations for tier-one banks and national military infrastructures relying on NonStop systems.
2002: Compaq merges with Hewlett-Packard (HP). ActionView 400 is bundled under the HP NonStop software catalog (product designation T8443), managing and diagnosing log audits like the AUDLOG framework.
2000s (Mid to Late): Insider Technologies starts shifting forward-looking tracking requirements toward its newer central architecture platform, Sentra. While ActionView 400 continues handling legacy X.400 pipelines, Sentra begins acting as a unified web console to consolidate both X.400 and modern SMTP/MIME email flows across multi-vendor systems.
2015: HP splits its corporate structures. The NonStop computing line and the management of ActionView 400 shift over to Hewlett Packard Enterprise (HPE).
2018: In December 2018, HPE officially moves ActionView 400 to Obsolete status, marking the formal end of its product life cycle and standard vendor service life.
2019 – Present: Despite official obsolescence on the HPE hardware list, Insider Technologies continues to directly support and maintain the solution for deep-legacy military, defense, and governmental bodies. Because these sectors still mandate uncompromised, zero-loss X.400 message accounting, the software remains active, feeding tracking telemetry directly into Insider’s modern Middleware Monitoring and Sentra platform interfaces.
Sentra – unified web console to consolidate both X.400 and modern SMTP / MIME email flows across multi-vendor systems
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.
The Software Partnership (TSP) was a highly specialized British software house based in Runcorn, Cheshire, that played a key role in early cutting-edge electronic banking software. The firm famously developed sp/ARCHITECT-BANK, an innovative enterprise banking system built explicitly for Tandem Computers (now HPE NonStop) fault-tolerant server systems. I was based there between 1990 and 1995.
The Software Partnership Logo
Below is a detailed overview of the company’s operational history, alongside the corresponding hardware/software architectural eras of the HPE NonStop platform it relied upon.
Detailed Overview
Core Focus: The Software Partnership specialized in online transaction processing (OLTP) and electronic automated banking software. Long before the internet became mainstream, TSP engineered early desktop access environments for corporate bookkeeping and inter-account bank transfers.
Key Product: Its flagship software suite, sp/ARCHITECT, ran on Tandem’s highly unique, redundant architecture. The software handled complex high-volume retail transactions, ATM networking, and ledger balances.
Major Clients: High-profile financial institutions deployed TSP’s systems, including TSB (Trustee Savings Bank), Bank of Scotland, Rabobank, and Denmark’s Girofon.
Legacy: TSP initiated a massive lineage of financial tech operations in the Runcorn/Warrington area. After subsequent buyouts and transitions, its corporate DNA integrated into modern banking giants, eventually operating under Fidelity National Information Services (FIS).
Detailed Timeline by Era and Year
The history of TSP mirrors the evolution of the underlying fault-tolerant architecture originally built by Tandem, later managed by Compaq, HP, and currently Hewlett Packard Enterprise (HPE).
Era 1: The Tandem Founding & TSP Inception (Mid-1970s – 1989)
This era is marked by Tandem’s creation of the fault-tolerant server market, which birthed the niche that TSP filled.
1974–1976: Tandem Computers is founded and ships its first 16-bit NonStop I (T/16) system, utilizing complete component redundancy to guarantee close to zero downtime for the financial industry.
1981: Tandem introduces the NonStop II, transitioning to battery-backed DRAM memory and enabling early 32-bit addressing.
Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. It establishes offices first in Timperley (Wingate Drive), then moves to Crowngate (Norton House) in Runcorn. The team begins developing online banking architectures explicitly for Tandem OS (Guardian) and early UNIX nodes.
1989: Tandem launches the NonStop Cyclone, a high-end mainframe system featuring superscalar CPUs and fiber-optic interconnects.
Era 2: The MIPS RISC Transition & Corporate Buyouts (1990 – 1999)
TSP reaches peak software deployment exactly as Tandem shifts its internal processor technology.
1990: TSP establishes itself as a major regional employment hub for software engineers following a massive boom in terminal banking technology. Software programmers deploy sp/ARCHITECT-BANK code for massive retail banks internationally.
1991: Tandem shifts its structural hardware away from proprietary chips, introducing its first MIPS RISC-based NonStop systems.
1992: TSP expands its Runcorn footprint, moving to custom facilities at Wingate House on Northway, Runcorn.
1994: TSP is acquired by American firm Deluxe Electronic Payment Systems (a division of Deluxe Corporation, one of the largest check printers and transaction processors in the US). The corporate name transitions to Deluxe Data.
1997: Due to shifts in the enterprise hardware landscape, Compaq Computer Corporation acquires Tandem Computers for $3 billion, taking over the NonStop lineage.
Era 3: The Itanium Migration & eFunds Realignment (2000 – 2013)
The architecture sheds its proprietary processors for industry standards, and TSP’s corporate legacy transforms.
2000: Deluxe Data’s electronic payment wing splits off and rebrands as EFD eFunds.
2001–2002: HP (Hewlett-Packard) merges with Compaq, absorbing the NonStop portfolio. Simultaneously, HP begins shifting NonStop servers from MIPS architectures to Intel Itanium processors.
2007: 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.
Era 4: The Modern HPE NonStop X & Virtualization Era (2014 – Present)
The legacy of the high-availability software pioneered in Runcorn culminates in cloud and x86 integration.
2014: HP introduces NonStop X, completely migrating the underlying architecture to Intel x86-64 processors and implementing InfiniBand connectivity fabrics.
2015: Hewlett-Packard officially splits into two entities; the core mission-critical banking platform continues its five-decade lineage under Hewlett Packard Enterprise (HPE).
2020s–Present: HPE modernizes the software architecture to support Virtualized NonStop Software (vNS). Modern variants allow banking systems to run mission-critical apps seamlessly inside enterprise private clouds and scalable HPE GreenLake consumption models with 100% fault tolerance.
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
⚙️ sp/ARCHITECT
sp/ARCHITECT (specifically sp/ARCHITECT-BANK) was a foundational electronic banking and transaction framework engineered in the 1990s by The Software Partnership (a UK-based fintech house later acquired by Deluxe Data). It primarily powered corporate banking portals and telephone-driven banking services.
The platform acted as highly reliable middleware, serving as a bridge between the customer and back-end banking mainframes. The breakdown of its architecture, infrastructure, and core functions includes:
⚙️ Architectural Breakdown
Hardware & OS: Built to run natively on fault-tolerant Tandem NonStop computers (now HPE NonStop). This “shared-nothing” architecture was designed for absolute transactional uptime and zero data loss.
Programming Languages: Built using legacy enterprise standards. Code was primarily written in COBOL85 and TAL (Transaction Application Language) native to the Tandem ecosystem.
Middleware Integration: Utilized Tandem-specific middleware like Pathway and Remote Server Call (RSC) to handle client-to-host communications.
💻 Core Capabilities & Modules
Electronic Delivery Framework: Served as a multi-channel framework, accommodating a wide variety of early access devices like desktop clients, UNIX workstations, and smart phones.
Transaction Handlers: Deployed custom scripts/handlers that enabled end-users to securely access real-time account data and perform early inter-account transfers without visiting a physical branch.
Testing Utilities: Included proprietary simulation tools like sp/TESTBED, acting as a PC-to-host test harness so developers could emulate user queries and transaction flows.
🏦 Industry Footprint
European Rollout: Heavily adopted by large European financial institutions, including TSB, Rabobank, Bank of Scotland, and Girofon.
BBM II Integration: Powered landmark corporate desktop banking solutions like Barclays Business Master II (BBM II), long before modern web browser banking existed.
Evolution: Following its acquisition, its design philosophies eventually evolved into Deluxe Data’s broader CONNEX suite of payment solutions.
Mark Whitfield, an SC cleared Senior Project Manager based in the Manchester area, has over 30 years of experience transitioning from a software engineer to an IT program leader.
His extensive technical and project management training spans methodologies, cloud infrastructure, and software applications.
A detailed breakdown of his training, certifications, and academic background includes:
Project Management Methodologies
PRINCE2 Practitioner: Certified via the ILX Group.
Agile SCRUM: Trained in-house with RADTAC.
Advanced Engagement Management: Level 2 certification completed via Capgemini.
Project Fundamentals: Completed “Fundamentals of Successful Project Management” and “Managing Multiple Projects” via Skillpath.
Microsoft Project: Microsoft Project ’98 certified.
Technical & Cloud Training
Microsoft Azure: AZ-900 Microsoft Certified Azure Fundamentals.
MuleSoft: Completed outcome-based delivery training and is a specialized Delivery Manager.
Technical Programming: Includes foundational database and software language training, such as C++ and MS SQL 2000 query training, as well as VPS and Tandem (HPE NonStop) technical/development courses.
Productivity: Completed Microsoft Excel Refresher and Expert skills training (Udemy and Microsoft).
Formal Education
Higher National Diploma (HND): Graduated with a Distinction (top) in Computing (1990).
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.
These terms map directly to the foundational 1990s technology stack behind Barclays Business Master II (BBM II), one of the UK’s earliest enterprise electronic desktop banking platforms.
Before the mainstream internet, this corporate banking infrastructure relied on specialized high-availability mainframe software to process secure corporate transactions.
🧱 Architectural Component Breakdown
Barclays Business Master (BBM / BBM II): A landmark corporate desktop electronic banking solution developed by Barclays Bank. It allowed businesses to dial directly into the bank to perform inter-account transfers, check balances, and automate book-keeping long before web browser banking became standard.
sp/ARCHITECT (or sp/ARCHITECT-BANK): The core electronic banking software package that powered BBM. It was originally engineered in the late 1980s and early 1990s by The Software Partnership (a UK-based fintech software house based in Runcorn that was later acquired by Deluxe Data). It eventually evolved into the widely known CONNEX advantage payment solution.
NonStop (Tandem Computers): The underlying hardware and operating system environment. Because banking infrastructure requires absolute uptime, sp/ARCHITECT was built to run on Tandem NonStop fault-tolerant computers (now HPE NonStop). These systems utilize a unique “shared-nothing” architecture to ensure zero transactional data loss.
💻 Legacy Technical Environment
During the era when BBM was deployed across Barclays’ tech hubs (such as Knutsford), developers working on this specific stack utilized highly specialized mainframe tools:
Languages: Code for sp/ARCHITECT was primarily written in TAL (Transaction Application Language) or COBOL85, which were native to the Tandem platform.
Interfaces: Early implementations integrated desktop client interactions with the Tandem host via middleware components like Tandem Pathway and Remote Server Call (RSC) facilities.
The BITUG BIG SIG 2026 event is scheduled for Thursday, 4 June 2026.
Organized by the British Isles NonStop User Group (BITUG), this annual conference gathers HPE NonStop professionals, partners, and vendors across the region.
Event Details
Date: Thursday, 4 June 2026.
Location: Trinity House, London.
Key Focus Areas: HPE NonStop architecture roadmaps, technical breakout tracks, data security, and specialized data resiliency updates.
Attendees: The conference hosts end-users, system administrators, and developers, alongside community sponsors such as comforte, XYPRO, and ETI-NET.
Networking: Collaborative environments allowing users to connect directly with senior HPE executives and product experts.
Admission: Complimentary registration is available for active end-user members. Official ticket registration and full session listings are hosted on the BITUG Big SIG Event Page.
The BITUG BIG SIG 2026 event is scheduled for Thursday, 4 June 2026
The BITUG BigSIG 2026 conference, hosted by the British Isles Tandem User Group at Trinity House, London, brings together the premier vendors within the HPE NonStop ecosystem. Key participating vendors and sponsors focus on data integration, compliance, zero-trust security, storage, and infrastructure management tailored for mission-critical enterprise systems.
The primary vendors participating in the 2026 HPE NonStop ecosystem event are organized by their specialization below.
🛡️ Data Security & Cyber Resilience
comforte AG: Serving as a key event sponsor, comforte AG hosts dedicated breakout sessions demonstrating tokenization strategies designed to secure sensitive data elements and enhance corporate data usability without breaking downstream application logic.
XYPRO Technology Corporation: A long-standing HPE NonStop security partner delivering compliance management, real-time threat detection, and risk mitigation tools. They focus heavily on enabling Zero-Trust architectures and automating compliance reporting for frameworks like PCI-DSS.
CSP (Compliance Systems Platforms): Specializes in vulnerability management, security hardening, and automated security compliance checking. They provide the administrative tools required to monitor audit logs and secure environments against internal and external threats.
🔄 Data Replication & Continuity
NTI (Network Technologies International): Presenting active strategies for multi-platform data distribution. NTI highlights methods for data movement away from legacy Oracle GoldenGate setups while integrating real-time HPE NonStop compute platforms with enterprise IT and agentic AI pipelines.
Gravic, Inc.: Promotes its HPE Shadowbase software line. Gravic focuses on high-availability business continuity, active-active data replication, data validation, and real-time streaming analytics for global telecommunications and financial exchanges.
💾 Backup, Storage & Infrastructure Management
ETI-NET: Showcases technical advancements inside its Sentinel and BackBox VTC software suites. ETI-NET’s 2026 showcase highlights immutable data tiering, object-locking architectures designed to resist ransomware, and AI/ML-driven anomaly detection within data backups.
TCM Solutions: Focuses on physical and virtual NonStop optimization. TCM specializes in hardware management, KVM hypervisor integrations for Virtualized NonStop environments, and transitioning infrastructure architecture over high-performance fabrics like InfiniBand.
💳 Application Modernization & Payments
OmniPayments: Showcases cloud-adjacent, high-volume payment processing switch architecture. They highlight transaction survivability, fraud prevention integrations, and end-to-end tokenization for multi-channel banking networks.
NuWave Technologies: Specializes in middleware solutions that connect HPE NonStop heritage code with modern RESTful web services. They focus heavily on API management as enterprise building blocks to quickly web-enable NonStop applications without rewriting backend logic.
4tech Software: Delivers tactical operational monitoring, system auditing, and database performance management tools designed to keep NonStop SQL applications running with minimal administrative overhead.
The European BASE24 User Group (EBUG) was a prominent, community-led organization dedicated to the ACI BASE24 payment processing system. It provided a vendor-neutral forum for IT professionals, banks, and processors to collaborate, share knowledge, and discuss technical tracks like HPE NonStop monitoring and payment security.
Conference Timeline
1980s — Establishment: EBUG is formed as a regional community for European financial institutions utilizing the growing BASE24 platform.
Early 2000s — Technical Growth: EBUG annual conferences become prominent technical forums featuring specialized tracks focused on Tandem/HP NonStop hardware and payment system security.
2007 — Istanbul Conference: Features heavily attended technical sessions and workshops addressing growing transaction volumes and early EMV (chip card) migrations.
Insider Technologies regularly attended EBUG, booth in 2007
2008 — Vienna Conference: Notable for introducing ACI’s strategic shift to support IBM platforms alongside traditional HPE NonStop environments.
HP booth at Vienna EBUG, 2008
2009 — Prague Conference: Continues strong advocacy and technical troubleshooting for BASE24 on NonStop despite broader industry platform shifts.
HP Booth at Prague conference, 2009
2012 — London TFG: A technical focus group is held in London at Trinity House, bringing together engineers and ACI product managers to debug and refine system architecture.
Late 2010s to Present — The “Everybody Belongs” Era: As ACI broadened its product portfolio, the user group expands its scope to include other payment technologies like Postilion. The conference formally rebrands as an independent entity, later transitioning into The Payments Knowledge Forum, to serve all payment systems users inclusively.
European BASE24 User Group (EBUG) was a prominent, community-led organization
HPE NonStop Reflex (often referred to as Reflex 80:20) is a graphical, integrated IT management suite developed by Insider Technologies. It provides continuous health monitoring, automated workflow management, and diagnostic logging for mission-critical HPE NonStop environments, serving as a single, consolidated “pane of glass” for fault-tolerant network operations.
Detailed Timeline Breakdown by Era & Year
The history of the NonStop Reflex suite closely mirrors the architectural evolution of the underlying HPE NonStop (originally Tandem) fault-tolerant hardware platforms.
1. The Tandem / ITUG Era (1989 – 1996)
1989: Insider Technologies was founded in Salford Quays, Manchester, UK, establishing an early specialization in Tandem (NonStop) messaging software and message tracking utilities.
1990s: As massive online transaction processing (OLTP) workloads grew, native Tandem utilities proved increasingly cumbersome. This spurred the initial development of platform diagnostic and event-filtering tools that would soon become the Reflex suite.
1995: Insider Technologies actively codes and launches the initial iterations of Reflex 80:20, providing operators with an aggregated view of Tandem platform events.
2. The Compaq & Early HP Transition Era (1997 – 2014)
1997: Compaq acquires Tandem Computers. Reflex 80:20 begins updating its backend architecture to handle ServerNet clustering and the newly combined enterprise platforms.
2002: Hewlett-Packard (HP) acquires Compaq. HP begins the hardware migration from proprietary processors to Intel Itanium (HP Integrity NonStop).
2004: Insider Technologies formalizes its ongoing product development, heavily pushing both Reflex 80:20 and releasing new variants like Reflex ONE24 to support extended tracking for ATM and POS networks.
2007: Reflex and other Insider monitoring software platforms are highly integrated into FIS solutions, serving tier-one global banks and stock exchanges.
2013: Insider Technologies solidifies the Reflex 80:20 status as the ultimate consolidated replacement for legacy HP components, publishing technical insights in dedicated NonStop journals.
3. The Modern HPE & x86 Era (2014 – 2019)
2014: Hewlett Packard Enterprise (HPE) is formed and officially launches NonStop X, moving the architecture onto standard Intel x86-64 processors. Reflex 80:20 interfaces are updated to support InfiniBand fabrics and the newer Open System Services (OSS) environments.
2017 – 2019: HPE launches Virtualized NonStop (vNS), bringing continuous application fault tolerance directly to private and hybrid clouds. Reflex adapts its system management capabilities to securely monitor both physical x86 non-stop servers and virtual hypervisor instances.
4. The AI & Hybrid Cloud Era (2020 – 2026)
2020: HPE ends the sale of older Itanium-based platforms. Reflex fully commits its diagnostic support to modern HPE NonStop X and vNS environments.
2023 – 2024: The NonStop platform embraces AI integrations, expanded SQL/cloud workloads, and integrations with modern DevOps tools. Reflex tools receive updates to accommodate enhanced cyber resilience tracking and modern API-driven services.
2025: HPE celebrates 50 years of the fault-tolerant NonStop computing ecosystem. The Reflex suite provides compatibility for the upgraded, high-capacity hardware iterations running the L25 series OS.
2026: Reflex remains a staple ecosystem management suite for complex enterprise networks, processing and escalating exception conditions, EMS events, and subsystem alerts within the highly available HPE GreenLake consumption models.
The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;
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.
MultiBatch is a robust enterprise workload automation and job scheduling tool designed specifically for the HPE NonStop parallel architecture. Developed originally by Insider Technologies and subsequently managed/distributed alongside partners like ETI-NET, it enables organization-wide task automation.
MultiBatch provides high-performance, concurrent execution of batch schedules across multiple nodes. It natively supports both Guardian and OSS environments. By utilizing modern graphical user interfaces (GUIs) alongside traditional Pathway components, it eliminates the need for complex, manual, and high-maintenance TACL or JCL scripts.
Core Technical Capabilities
Parallel Execution: Uses NonStop architecture to execute batch workloads concurrently across one or multiple nodes.
Advanced Scheduling: Drives automated tasks based on time parameters, complex intervals, custom calendars, and direct cross-job dependencies.
Reusable Infrastructure: Environment classes—including PARAM, ASSIGN, DEFINE, FD, and environmental variables—can be configured once and safely shared across various jobs.
Inbuilt Disaster Recovery: Features automated, built-in monitor recovery mechanisms to preserve execution integrity during hardware or connection failures.
Seamless Migration: Simplifies moving production workloads between environments via a deep migration utility that automatically handles environmental translation without manual intervention.
Timeline Breakdown by Year and Version
The evolution of MultiBatch highlights its transition toward broader configuration capacities, simplified environment integrations, and eventual product lifecycle milestones.
2020: Operational and Security Consolidation
Version Focus: Pre-v10 Infrastructure (Enterprise Deployments)
Key Enhancements:
Formalized rigid separation of internal user roles, establishing MBAT.OPS for view-only status monitoring and MBAT.CONFIG for structural schedule maintenance.
Refined the “Migrator” module, eliminating manual TACL operations when extracting and inserting batch definitions across network test and production nodes.
Added capabilities allowing all MultiBatch jobs to execute securely under the system Batch Monitor Process (BMON) owner or explicitly assigned application user IDs.
2022 (November): MultiBatch Version 10.0 Launch
Version Focus: Architecture Restructuring
Key Enhancements:
Define Classes: Introduced reusable Define Classes to group environments cleanly.
Scale Upgrades: Upgraded the main Batch Monitor (BMON) subsystem to actively scale up to 2,500 jobs concurrently.
Parameterization: Modified the core configuration boundaries and decoupled utility processes (MBPARHK) to seamlessly process non-step related records across database structures.
Clean Up: Formally deprecated legacy components including UTCSV to reduce technical debt.
2023 (February): MultiBatch Version 10.1 Refinement
Version Focus: OSS Overhaul & Operational Control
Key Enhancements:
OSS Reworking: Re-engineered and optimized support for Open System Services (OSS) processes, granting them equal parity with traditional Guardian tasks.
On-Demand Execution: Enabled ad-hoc “On Demand Job” invocation directly through user channels without altering master schedules.
Conditional Variables: Extended character limits for Conditional Parameter values up to 100 characters.
Subsystem Unification: Consolidated Event Timer processing and Conditional Parameters fully into standard MultiBatch menus, auditing frameworks, and security tracking.
Control Commands: Integrated the SWITCH BMON command line directive to easily pass control between operational monitors.
Interface Upgrade: Rolled out an entirely new Ops GUI Server to modernize scheduling visibility.
Current Era: Version 10.2 Maintenance & Commercial Sunset
Version Focus: Version 10.2 / Product Lifecycle Transition
Key Milestones:
MultiBatch 10.2: Operates as the current, stable production tier delivered via ETI-NET, featuring deep parameterization and centralized network deployment protocols.
Commercial End of Life: As of March 1, 2026, new software licenses for Multi-Batch are no longer available for purchase. The software has officially reached the end of its commercial sales life.
Ongoing Support: Existing license holders retain full permission to execute, maintain, and run the product inside their environments according to their long-term licensing agreements.
HPE NonStop MultiBatch Batch Job Scheduling Overview and Timeline
sp/ARCHITECT was a pioneering electronic banking and funds-transfer software suite. Originally built by the UK-based Software Partnership (TSP), it ran natively on fault-tolerant Tandem (now HPE NonStop) systems. It provided highly available transaction routing and real-time electronic book-keeping for major international financial institutions.
Detailed Timeline by Era and Year
1. The Genesis & Independent Era (Mid-1980s – 1989)
Mid-1980s: The Software Partnership (TSP) is co-founded in Timperley, UK. Development begins on sp/ARCHITECT, designed with a client-server architecture.
1986: Tandem launches NonStop SQL, providing the underlying high-availability relational database foundation that sp/ARCHITECT relied upon to ensure absolute data integrity for banks.
2. Mainstream Banking Adoption Era (1990 – 1994)
1990: TSP relocates to Norton House in Runcorn, UK. sp/ARCHITECT achieves production deployment and is widely utilized for inter-account transfers and book-keeping by major banks like TSB and Bank of Scotland.
1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.
1994: Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation) acquires TSP to expand its global electronic funds transfer (EFT) footprint. The platform is globally marketed and supported, expanding to clients like Rabobank.
1990: TSP relocates to Norton House in Runcorn
1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.
3. Global Expansion & Compaq Transition Era (1995 – 2005)
1995 – 1997: The Runcorn-based team (operating as Deluxe Data) codes additional regional adaptations of sp/ARCHITECT for banks worldwide (e.g., Girofon in Denmark).
1997: Compaq acquires Tandem Computers, placing sp/ARCHITECT on Compaq’s enterprise roadmap.
2002: Hewlett-Packard (HP) acquires Compaq, absorbing the Tandem platform into the HP Integrity server line. The application undergoes adaptation to integrate modern Windows-based management systems (like DSM/NOW).
4. The HPE Modernization & Hybrid Era (2014 – 2026)
2014: HPE (Hewlett Packard Enterprise) is formed, spinning off from HP. NonStop shifts to Intel x86-64 architecture (NonStop X), requiring sp/ARCHITECT and related Tandem subsystems (like Pathway, COBOL, and TAL) to modernize for TNS/X processing.
2020: Legacy Itanium-based environments are phased out. sp/ARCHITECT systems, if still active, are migrated to virtualized NonStop (vNS) and operated within private cloud infrastructures.
2025/2026: HPE NonStop celebrates its 50th Anniversary. Applications originally designed on the sp/ARCHITECT schema are heavily evaluated for AI integration, continuous cyber resilience, and consumption-based models like HPE GreenLake.
The HPE NonStop community, historically rooted in Tandem Computers’ culture of openness, has held an annual gathering since the early 1980s.
Originally known as the International Tandem Users Group (ITUG) summits, the main conference evolved into the NonStop Technical Boot Camp (TBC), now organized by Connect Worldwide and heavily supported by Hewlett Packard Enterprise.
The conference serves as the premier annual gathering for NonStop users, focusing on technical education, mission-critical applications, and networking.
Detailed Historical Timeline (1990–2026)
The “Tandem/ITUG” Era (1990–1996)
Focus: Transitioning from proprietary stack machines to MIPS RISC microprocessors, introducing Open System Services (OSS).
1990: Tandem reaches peak revenue; ITUG meetings focus on fault tolerance in ATM networks.
1993: Introduction of NonStop Himalaya K-series using MIPS R4400 processors.
1994: NonStop Kernel (NSK) extended with POSIX-compliant Unix.
1995: Introduction of ServerNet, foundational for future x86 architectures.
The Compaq & HP Transition Era (1997–2014)
Focus: Integration into larger portfolios, migration from MIPS to Intel Itanium (TNS/E).
1997: Compaq acquires Tandem. ITUG summits begin navigating the new corporate structure.
2003: HP acquires Compaq. NonStop conferences become key components of HP’s high-end mission-critical offerings.
2008: Connect Worldwide (independent user group) takes over, revitalizing the “Technical Boot Camp” name.
The HPE NonStop X & Virtualization Era (2015–2019)
Focus: Migration to x86-64 (NonStop X), Virtualization (vNonStop), and cloud integration.
2015: Formation of Hewlett Packard Enterprise (HPE). Focus shifts to modernized “NonStop X” systems.
2016: vNonStop demoed at TBC, allowing fault-tolerant systems in virtual machines.
2017: TBC highlights AI and cybersecurity, reflecting modern enterprise needs.
2019: Discussions around “NonStop-as-a-Service” (XaaS) and GreenLake integration.
The AI & 50th Anniversary Era (2020–2026)
Focus: Hybrid Cloud, Artificial Intelligence, 50th Anniversary of NonStop.
2020: TBC goes virtual, with high attendance from a global community.
2022: Continued focus on XaaS (everything as a service).
2023-2024: Emphasis on cyber resilience, SQL improvements, and integration with modern DevOps tools.
2025/2026:HPE NonStop 50th Anniversary. Conferences focus on AI-driven transformation, cybersecurity, and the new business track.
Conference Insights and Evolution
The “Beer Bust”: A tradition started in the early days of Tandem, now a staple social event at the TBC to foster community and open communication.
Format: The NonStop TBC typically features 4 days of technical sessions, user case studies, and partner exhibitions (e.g., XYPRO, NTI).
Regional Events: Alongside the main TBC, regional events (e.g., MexTUG) occur throughout the year.
Key Themes: Uninterrupted performance, database integrity, and migration to x86/cloud.
NonStop TBC 2026 is scheduled for Sept 14–18 in Orlando, FL.
The history of Tandem Computers (now HPE NonStop) conferences is a nearly 50-year chronicle of community-driven knowledge sharing, evolving from the Tandem User’s Group (TUG) in 1978 to the modern HPE NonStop Technology & Business Conference (TBC).
These events have served as the primary venue for sharing best practices on fault tolerance, high availability, and mission-critical application design, bridging the gap between Tandem’s founding in 1974 and HPE’s current virtualized NonStop systems.
1974: Jimmy Treybig founds Tandem Computers in Cupertino, CA, with a mission to create fault-tolerant systems for online transaction processing (OLTP).
1976: First Tandem/16 (T/16) system shipped to Citibank, initiating the NonStop era.
1978:Creation of the Tandem User’s Group (TUG) in San Jose, CA, as the foundational user community. Introduction of the Encompass database management system.
1980–1989: Growth and Expansion
1981: TUG is renamed the International Tandem User’s Group (ITUG), reflecting global growth. Introduction of NonStop II.
1983: Introduction of the Tandem NonStop Extended Processor (TXP) and Guardian B-Series OS.
1984: Formation of the British Isles Tandem User Group (BITUG).
1985–1986: Introduction of the entry-level NonStop EXT system.
1987-1988: Large-scale adoption of Tandem systems by international financial institutions and growing ITUG conference attendance, often characterized by strong community spirit.
1989: Release of NonStop Cyclone and relational database software, challenging IBM’s dominance in transaction processing.
1990–1999: The Move to Open Systems & Acquisition
1990: Announcement of the Integrity S2 line for Unix-based fault tolerance.
1991: Release of Cyclone/R (CLX/R) based on MIPS R3000, signaling a move away from custom proprietary CPUs.
1993: Launch of the Himalaya K-series, supporting the MIPS R4400 and native mode NSK.
1994-1995: Introduction of Open System Services (OSS), extending the NonStop Kernel to include a Unix-like POSIX environment.
1997:Compaq acquires Tandem for $3 billion. Tandem releases the NonStop Himalaya S-Series, introducing the ServerNet interconnect technology.
2000–2010: Compaq-HP Merger and Modernization
2001: Hewlett-Packard merges with Compaq, taking over the NonStop product line and initiating a migration to Intel Itanium processors (TNS/E).
2001: ITUG is renamed to “Compaq Users Group” before transitioning to the combined Connect community group.
2002: Formation of a Tandem Alumni Group, celebrating the unique culture.
Legacy + Future: Current TBC conferences balance supporting existing high-value transaction applications with modernization approaches like REST APIs, Java, and DevOps.
Virtualization & Cloud: A major focus is deploying NonStop as virtualized instances (vNS) and integrating with public/hybrid clouds.
Community Continuity: Despite multiple mergers (Tandem HPE), the user community has remained tight-knit, with organizations like Connect hosting the NonStop TBC.
Continuous Availability: The core focus remains 100% uptime, with sessions analyzing how to achieve it in modern containerized environments.
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.
The International Tandem User Group (ITUG) is a non-profit association dedicated to users of the Tandem NonStop computing platform. Now part of the Connect Worldwide community, it facilitates education, networking, and technical exchange between users, vendors, and Hewlett Packard Enterprise (HPE).
ITUG Overview
Purpose: To provide a platform for sharing technical knowledge, advocacy, and strategic information regarding Tandem (now HPE NonStop) systems.
Key Resources: ITUGLIB, an extensive download library containing open-source software, technical white papers, and legacy Guardian tools.
Historical Timeline by Era
1. The Foundational Era (1974–1983)
1974: Tandem Computers is incorporated in California by Jimmy Treybig and a core team of former HP 3000 engineers.
1976: The first Tandem/16 (NonStop I) system ships to Citibank, establishing the fault-tolerant market.
1980: Regional groups begin forming, such as GTUG in Germany, to support the rapidly growing user base.
1981: Introduction of NonStop II, which adds 32-bit addressing capabilities.
2. Growth and Expansion Era (1984–1996)
1984: BITUG is founded in the British Isles, eventually becoming the largest user group outside the USA.
1986: Tandem launches NonStop SQL, the first fault-tolerant SQL database.
1991: The platform migrates from proprietary stack-based processors to MIPS RISC architecture (TNS/R).
1993: Release of the NonStop Himalaya K-series, further expanding scalability.
3. Acquisition and Integration Era (1997–2008)
1997: Compaq acquires Tandem Computers to bolster its enterprise server portfolio.
2002: Hewlett-Packard (HP) acquires Compaq, bringing Tandem “back home” to the company that inspired its founders.
2003: ITUG celebrates its 25th anniversary with participation from original Tandem executives.
2005: ITUG officially merges with other HP user groups (Encompass and HP-Interex) to form Connect, though it often retains the “ITUG” branding for its NonStop-focused division.
4. Modern Era (2009–Present)
2014: The platform completes its transition to Intel x86 architecture, branded as Integrity NonStop X.
2015: Hewlett-Packard splits; Tandem/NonStop becomes a core part of Hewlett Packard Enterprise (HPE).
Present: ITUG continues to operate under Connect Worldwide, hosting major annual events like the NonStop Technical Boot Camp (TBC).
……….
HP Connect (often referred to as Connect Worldwide) is a leading global IT user community dedicated to professionals using Hewlett Packard Enterprise (HPE) and HP Inc. solutions. It serves as an independent hub for peer-to-peer networking, technical education, and advocacy, primarily supporting users of high-availability systems like NonStop, ProLiant, and HP-UX.
Historical Timeline by Era
The community’s history is defined by the evolution and eventual merger of several legacy user groups representing the giants of the mid-20th-century computing world.
1. The Legacy Foundations (1960s – 1990s)
Before the name “Connect” existed, three distinct user groups served the customers of the companies that would eventually form the modern HP/HPE ecosystem:
DECUS (1961): The Digital Equipment Computer Users’ Society was one of the oldest and largest user groups, supporting DEC systems.
Interex (1974): Founded as the HP 3000 International Users Group, it later expanded to support HP 9000 and HP-UX users.
ITUG (1970s): The International Tandem User Group supported the high-availability Tandem NonStop server community.
2. The Consolidation Era (2000 – 2008)
Major corporate mergers necessitated the union of these independent communities:
2002: HP acquired Compaq, which had already acquired DEC and Tandem.
2004 – 2005: The DECUS community transitioned into Encompass, serving the Enterprise users of the merged entities.
2008:Connect Worldwide was officially launched through the merger of Encompass and ITUG, creating a single, unified global community for HP enterprise users.
3. The Unified “Connect” Era (2008 – 2015)
During this period, Connect Worldwide solidified its role as the primary independent voice for HP enterprise technology:
Global Advocacy: It represented over 50,000 members across 1,000+ member companies worldwide.
Technical Focus: The community focused heavily on HP’s “Converged Infrastructure” and mission-critical systems.
The “Boot Camp”: The NonStop TBC (Technical Boot Camp) became its flagship global event.
4. The Modern Era & Digital Transformation (2015 – Present)
Following the historic 2015 split of Hewlett-Packard into HP Inc. and Hewlett Packard Enterprise (HPE), the community adapted to a dual-focus landscape:
Specialised Sub-Communities: While “Connect” remains the umbrella for legacy enterprise users, newer platforms like the HP Support Community have risen to manage consumer and PC-specific technical needs.
HP Connect (Cloud Service): HP introduced a modern cloud-based tool also named HP Connect, which IT admins use to manage BIOS and security settings for corporate PC fleets via Microsoft Intune.
AI Integration: The latest era (2024+) focuses on the “HP AI Helix,” embedding AI management and security into the user experience.
The European BASE24 User Group (EBUG) was a prominent, community-led organization dedicated to the BASE24 payment processing system. It served as a vital hub for financial institutions and vendors to exchange technical knowledge, discuss platform migrations, and influence the development of ACI Worldwide products.
Group Overview
Primary Purpose: EBUG facilitated networking and technical collaboration among users of the BASE24 ecosystem, including the BASE24 Classic and BASE24-eps platforms.
Evolution of Scope: While it began with a strict focus on BASE24, it eventually expanded to include other ACI products like Postilion.
Independence: The group shifted from being an ACI-sponsored event to a supplier-agnostic forum known as “The Payments Knowledge Forum” after ACI ended its direct involvement.
Legacy Transformation: In its later years, it was affectionately referred to as the “Everybody Belongs User’s Group”, reflecting its inclusive stance as “The Independent Group for All Payments System Users”.
Detailed Timeline
The history of EBUG is marked by its annual conferences held in major European cities and its eventual transition to an independent entity:
1980s: EBUG is established as a regional group for the growing BASE24 community in Europe.
Early 2000s: EBUG events gain prestige, featuring technical tracks on HPE NonStop transaction monitoring and payment security.
2006–2008: High-profile meetings held in cities such as Istanbul (2007) and Vienna (2008). The 2008 Vienna event was notable for discussing ACI’s strategic shift toward IBM platforms.
2009: The conference takes place in Prague, continuing strong support for BASE24 on NonStop despite broader industry shifts.
2012: The Technical Focus Group (TFG) is held in London at Trinity House. This marks a turning point as the event moved off ACI’s premises, signaling a shift in sponsorship dynamics.
2013: EBUG holds a major forum in Westminster, London, at the Institution of Civil Engineers. By this time, it is officially rebranding toward the broader “Payments Knowledge Forum”.
2015: EBUG fully transitions into the Payments Knowledge Forum, an annual gathering in London that continues the 30-year legacy as an independent, supplier-agnostic body.
……….
The Payments Knowledge Forum (PKF) is an independent, user-led resource dedicated to the exchange of information regarding payment systems. It operates without vendor affiliation, bringing together financial institutions, retailers, processors, and consultants to share practical expertise and shape the future of payment activities.
Overview of the Payments Knowledge Forum
Purpose: PKF serves as a collaborative hub for payment system users to discuss industry challenges, regulatory changes, and technical innovations.
Composition: The forum is open to a wide range of industry stakeholders, including:
Financial Institutions: Banks and building societies.
Retailers: Businesses focusing on consumer point-of-sale and e-commerce.
Payments Processors: Entities managing the technical execution of transactions.
Consultants: Experts providing strategic and technical guidance.
Governance: It is uniquely “run by users for the benefit of users,” ensuring that the information shared is neutral and prioritises the operational needs of the participants over commercial vendor interests.
Activities: PKF hosts regular events and an annual conference to address evolving topics such as ISO 20022 migration, central bank digital currencies (CBDC), and security frameworks like PSD2.
Detailed Timeline of Major Payment Milestones
The following timeline tracks critical industry milestones often discussed and addressed within the forum’s scope:
2015: The Payments Strategy Forum was established by the UK Payment Systems Regulator (PSR) to create a long-term roadmap for UK payments.
November 2016: Publication of the “Payments Strategy for the 21st Century,” introducing concepts like Request to Pay and enhanced data standards.
March 2018: Regulatory Technical Standards (RTS) for PSD2 were published, initiating the transition to Strong Customer Authentication (SCA).
November 2018: Launch of TARGET Instant Payment Settlement (TIPS), enabling real-time fund transfers across Europe.
September 2019: Full implementation of PSD2 security measures, including the requirement for standardised API interfaces for third-party access.
2020–2024: Acceleration of digital payment adoption following the COVID-19 pandemic, with a notable decline in cash usage at points of sale.
October 2021: The Financial Stability Board (FSB) published global targets for cost, speed, and transparency in cross-border payments.
February 2024: Swedish krona successfully onboarded to the TIPS platform.
April 2025: Danish kroner scheduled for onboarding to the TIPS system.
September 2025: Publication of the Digital Euro innovation platform outcome report, detailing findings for future development.
April 2026: Review of the Senior Managers and Certification Regime (SM&CR) to enhance accountability in financial services.
June 2026: Deadline for firms to demonstrate credible timetables for addressing climate-related financial risks.
2026 (Targeted): Anticipated go-live dates for enhanced access to the CHAPS high-value payment system.
Annual Conference & Resources
The PKF holds an annual conference that serves as its primary knowledge-sharing event.
Recent/Upcoming: The 2026 Conference continues the forum’s tradition of deep-diving into operational resilience and the digital transformation of finance.
Direct Access: For the latest news and detailed membership information, visit the The Payments Knowledge Forum Official Site.
……….
Some HPE NonStop BASE24 related User groups on LinkedIn :
Mark Whitfield is a Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC), specializing in digital transformation, payment systems, and HPE NonStop (Tandem) technology.
He is SC cleared (valid until 2031) and currently works at Capgemini UK, having transitioned from a technical programming background to senior project leadership roles.
He is also the creator of PROject Templates, providing a comprehensive, editable suite of over 200 project management tools built over 24+ years of experience.
Comprehensive Career Timeline by Era
1. Technical Foundations & Mainframe Development (1990–1995)
1990: Graduated in Computing at University of Bolton; started as a programmer at The Software Partnership (later Deluxe Data), Runcorn.
1990–1994: Specialised in electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers (HPE NonStop), developing in COBOL85 and NonStop SQL for major banks.
1994: Developed batch billing modules for Barclays Business Master II (BBM II) on-site in Knutsford and Poole.
1995–2013: Worked at Insider Technologies Limited as Senior Development Engineer/ Project Manager.
1997: Conducted volume testing/benchmark software for CRESTCo (now Euroclear) on new S7000 hp NonStop nodes.
2002: Managed and attained the first HP OpenView Operations 2-way Smart Plug-In (SPI) certification for the HPE NonStop platform.
2000s (Early): Developed RTLX (Real-Time Log Extraction) for BASE24 POS and ATM transaction monitoring, collaborating with banking clients like HSBC and Global Payments.
2013: Delivered a large BASE24 transaction tracking project at Al Rajhi Bank in Riyadh, Saudi Arabia.
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.
ViewSys is a legacy, interactive system monitoring utility for HPE NonStop servers that provides real-time visibility into system resource utilization. Similar to PEEK and Measure, it allows system operators to view resource consumption as it happens, allowing for immediate analysis of the impacts of process relocations or controller path changes.
HPE NonStop ViewSys Overview
Purpose: Monitors system resources, including processor utilization, I/O performance, and memory usage, on NonStop systems.
Key Features: Provides online viewing of system resources, allowing for quick recognition of performance bottlenecks, which helps in performance tuning.
Functionality: Unlike Measure, which is typically analyzed offline, ViewSys offers an interactive, live, and graphical view of system performance.
Operation Requirement: Runs from HPE block mode terminals or non-Stop terminal emulators, presenting average resource usage for each polling interval.
The history of ViewSys is deeply intertwined with the development of the HPE NonStop OS and its monitoring toolkit.
Era 1: Tandem Era (The Early Days)
1976: Initial Tandem NonStop System introduced; basic system monitoring is manual and console-based.
1980s (Mid-late): As Transaction Monitoring Facility (TMF) and Pathway are introduced, the need for interactive monitoring grows.
1990s:ViewSys becomes a key utility for operators managing massive OLTP (Online Transaction Processing) workloads.
Era 2: Compaq/Early HP Era (The Transition)
1997: Compaq Acquires Tandem.
2003: HP Acquires Compaq. The monitoring focus begins to merge with Integrity-based architecture.
2004: The ViewSys User’s Guide highlights ViewSys alongside PEEK and Measure, standardizing its use for interactive monitoring.
2005: Introduction of HP Integrity “NonStop i” (TNS/E) servers using Intel Itanium processors. ViewSys adapted to monitor Itanium systems.
Era 3: Modern HPE Era (The Modernization)
2014: First NonStop X (TNS/X) systems on x86-64 are introduced. ViewSys remains a available tool, but modernization efforts begin.
2015: Hewlett Packard Enterprise (HPE) is formed.
2016-2020: Shift towards Web ViewPoint Enterprise (by Idelji Corporation), which provides web-based dashboards for monitoring EMS events and system metrics.
2020: Sales of Itanium-based systems end. Modern monitoring focuses heavily on NonStop X systems and virtualized environments.
Present: While legacy ViewSys may exist in older environments, it is largely superseded by modern GUI-based, browser-independent monitoring solutions like Web ViewPoint and Remote Analyst.
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
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
The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL.
Program Summary
The DDL dictionary program functions as a metadata management tool. Key capabilities include:
Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use.
Future Outlook
The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement.
Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats.
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.
The HPE NonStop Spoolcom (Spooler Command Language) program is the administrative interface for managing the Spooler subsystem on HPE NonStop systems. It allows operators to configure, monitor, and control print jobs, collectors, and print processes.
Program Summary
Purpose: Used to define and manage spooler objects such as collectors, devices, and jobs.
Key Functions: Starting/stopping the spooler, modifying device attributes, and controlling job states (e.g., hold, release, delete).
Architecture: Operates within the Guardian environment, communicating with the Spooler supervisor process to maintain 24/7 fault-tolerant printing operations.
Historical Timeline by Era
1. The Tandem Era (1974–1997)
1976: Introduction of the Tandem NonStop system; basic spooling capabilities were essential for early OLTP (Online Transaction Processing).
1980s: The Spooler evolved to handle complex routing and multiple collectors to support growing enterprise needs.
1997: Spooler D41 released, providing stable management for the MIPS-based architecture.
2. The Compaq & Early HP Era (1997–2014)
1999–2000: Release of Spooler D46, enhancing device ownership and virtual device support.
2001–2002: Spooler D48 released during the transition to the HP Integrity NonStop (Itanium) platform.
2012: Major updates to Spooler D48 to support H01 and H02 RVUs, improving scalability for high-end systems.
3. The Modern HPE Era (2014–Present)
2014: NonStop X (x86-64) introduced. Spoolcom adapted to support the new architecture and virtualised environments.
2018–2020: Focus shifted toward modernised interfaces. While Spoolcom remains the CLI standard, graphical alternatives like MultiBatch began gaining traction for batch management.
2023–2024: Continued integration with HPE GreenLake and hybrid cloud models, ensuring spooling services are available in private cloud deployments.
Futures and Roadmap
Modernisation: HPE is pushing toward “modernisation through tradition,” which includes better integration of legacy tools like Spoolcom with modern DevSecOps and cloud-native frameworks.
Kernel-Level Threading (KLT): Future updates aim to leverage KLT to improve the performance and scale-up capabilities of management processes.
Data-Centric Security: Integration with security platforms like TAMUNIO for field-level tokenization ensures that printed data remains compliant with PCI DSS 4.0 and GDPR.
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 SC-cleared Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC), specializing in Agile and Waterfall delivery for financial, automotive, and public sector clients. He has a strong background in HP NonStop (Tandem) systems and currently works for Capgemini.
Mark Whitfield, Senior IT PM and Project templates author
1990–1994: The Software Partnership (Runcorn): Programmer specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers.
1994–1995: Deluxe Data (formerly TSP): Lead Analyst/Programmer, focusing on software investigation, design, coding, and on-site installation for clients like TSB, Bank of Scotland, and Rabobank.
Development & Technical Specialization (1995–2013)
1995–2013: Insider Technologies Limited: Spent 18 years progressing from Senior Development Engineer to Project Manager for Strategic Technical Initiatives.
Key Roles: Managed Reflex 80:20 and Reflex ONE24 product development, technical pre-sales, and consultancy. Developed diagnostic software for monitoring payment systems (BASE24).
Notable Project: Managed a bid to replace legacy ATM tools at LloydsTSB (5000 ATMs) with Reflex ONE24.
Banking & Digital Project Management (2013–2016)
2013–2014: Wincor Nixdorf: Project Manager in the Professional Services Banking Division, managing a £5m+ work stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
2014–2016: Betfred: Senior Digital Project Manager for the Online and Mobile Division, delivering payment gateways and sportsbooks for iOS, Android, and Windows.
Senior Engagement Management (2016–Present)
2016–Present: Capgemini UK: Engagement Project Manager responsible for delivering both Waterfall and Agile digital projects.
2016 (Approx.): Assigned to a UK-wide Air Traffic organization (NATS) for Apple iOS app delivery.
2018–2019: MuleSoft (Secondment): Served as a Delivery Manager for the Anypoint Platform.
Current Focus: Cloud Migration (Hybrid) of 130 apps for UK Government.
Agile Management: “Mark provided an excellent barrier between us (developers) and a difficult client…ensuring that we followed the agile principles” — Callum Marriage (Developer).
MuleSoft/Capgemini Engagement: “Customers loved him. His was extremely detailed oriented and understood the often-complex needs…never became flustered in high pressure situations” — Delivery Manager, MuleSoft.
Betfred (2015): “I would highly recommend Mark for his ability to successfully multi-task under significant pressure… [he] produced a very comprehensive handover document” — IT Compliance Analyst, Betfred.
Capgemini/JLR Project: “Mark was able to do a good planning, with the correct resources, on time delivery and with good relationship between stakeholders” — Head of Integration Development.
Mark Whitfield’s website (mark-whitfield.com) serves as a professional portfolio and resource hub for his 30+ year career as a SC-cleared Senior IT Project Manager. It offers over 200 editable project management templates for Agile, Waterfall, and PRINCE2 methodologies, alongside career insights and project experience.
Website & Content Overview
Project Management Resources: The site, often known as PROject Templates, provides downloadable templates for planning, scheduling (Gantt charts), project initiation (PID), and project control.
Methodology Focus: Resources are tailored for PRINCE2 (including Agile Scrum), and Agile/Waterfall delivery methods.
Career Portfolio: Features his work history as a Senior IT Project Manager, including roles at Capgemini, Betfred, and various financial institutions.
Technical Specialization: Highlights expertise in HP NonStop systems, digital projects, and payment/transaction systems.
Professional Background: Mentions his experience with major clients such as Jaguar Landrover, Heathrow, Royal Mail, and various banks.
The site is designed for project managers looking for templates to speed up project documentation and for clients looking to review his career accomplishments.
Senior IT Project Manager & Project Templates author – Mark Whitfield
Templates sold on this website are designed for Microsoft Office (Excel, Word, PowerPoint) and MS Project (MPP) and are used for tracking and planning software development lifecycle (SDLC) projects.
Template Breakdown
The templates, often sold in a bundle, include over 200+ editable items aimed at project delivery. Key components include:
Project Planning (MS Project & Excel): Detailed Waterfall project planners with Gantt views, Agile Sprint plans, and Plan on a Page (POaP) examples.
RAID Logs (Risk, Action, Issue, Dependency): Comprehensive Excel trackers for managing risks, issues, assumptions, and dependencies.
Financial & Resource Management: Project finance trackers (forecasts, actuals, variance) and resource trackers for tracking team members and costs.
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.
Mark Whitfield is a Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC). He is currently a SC-cleared Engagement Manager at Capgemini UK.
Professional Background by Era
1990–1995: Early Programming (The Software Partnership/Deluxe Data)
Role: Programmer/Lead Analyst.
Focus: Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers (now HPE NonStop).
1995–2013: Senior Development & Product Management (Insider Technologies)
Role: Progressed from Senior Programmer to Project Manager for Strategic Technical Initiatives.
Focus: Developed platform health and diagnostic modules for the “Reflex” monitoring product.
2013–2014: Project Management (Wincor Nixdorf)
Role: Project Manager, Professional Services – Banking Division.
Focus: Managed the Wincor Nixdorf workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
2014–2016: Digital Project Management (Betfred)
Role: Senior Digital Project Manager, Online and Mobile Division.
Focus: Delivered payment gateways, sportsbooks, and virtual gaming components for iOS, Android, and Windows.
Focus: Leading digital transformation and cloud migration projects for public and private sector clients.
Technologies & Frameworks
Project Methodologies: Agile SCRUM, PRINCE2 (Practitioner), Waterfall, ITIL, and ISO QA.
Mainframe & Infrastructure: HPE NonStop (Tandem), IBM ESB, UNIX shell scripting, and Cloud (MS Azure/AWS).
Programming & Databases: C/C++, MS SQL, Java, COBOL85, TAL, TACL, and SCOBOL.
Tools: MS Project, MS Excel/Office, MuleSoft Anypoint Platform, and Jira.
Major Projects & Customers
UK Government: Managed a £13.5m cloud migration of 130 applications and the £1m+ Fish Export Service (FES) to CHIP portal.
Royal Mail Group (RMG): Managed a £4.3m data centre migration project involving over 1,100 interfaces.
Lloyds Banking Group (LBG): Led a £5m+ self-service software replacement project.
Other Notable Clients: Jaguar Land Rover (JLR), Heathrow, NATS (Air Traffic Control), Barclays, HSBC, Deutsche Bank, and Euroclear.
Awards & Education
Awards:
C&CA UK’s Communications & Engagement Award (2022) at Capgemini UK.
Project Recognition Award from Wincor Nixdorf for achievements on the LBG SSSR project.
Education:
HND in Computer Studies (Distinction) from the University of Greater Manchester (formerly BIHE), 1988–1990.
A-Levels in Computer Science and Biology from Leigh College.
Project Management Templates
Whitfield provides a library of over 200 editable resources through his site, PROject Templates, designed for Agile, Waterfall, and PRINCE2 7th Edition delivery. Key items include:
Plan on a Page (POaP): Over 35+ executive-level summary slides.
Detailed Project Plans: Templates in MS Project (MPP) and Excel for SDLC tracking.
RAID Logs: Comprehensive registers for risks, actions, issues, and dependencies.
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.
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.
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).
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).
The evolution of C++ on HPE NonStop systems traces the platform’s transition from proprietary Tandem architectures to modern x86-64 standards.
HPE NonStop C++ Evolution Timeline
Early 1990s: Introduction of Native C/C++ (TNS/R) With the move to MIPS-based TNS/R architecture, Tandem introduced native C and C++ compilers. These supported the Guardian and the then-new Open System Services (OSS) personalities.
2005: Itanium Transition (TNS/E) As the platform migrated to Intel Itanium processors (J-Series), the C++ compiler was updated to support the TNS/E (Tandem Native Stack / EPOC) architecture. This era introduced more robust Standard C++ Library support, though it required specific header management (e.g., CPATHEQ pragmas).
2015: x86 Migration (TNS/X) The launch of NonStop X (L-Series) on Intel x86-64 marked a major shift. The compiler suite was re-engineered to leverage the x86-64 Instruction Set Architecture, providing significantly higher performance for C++ applications.
2017: 64-Bit Addressing Support HPE introduced comprehensive 64-bit support for OSS processes (LP64 data model). This allowed C++ applications to access massive memory heaps beyond the previous 32-bit (ILP32) limits.
2020–2022: Modern C++ Standards (C++11/14/17) HPE updated its toolchains to support modern language standards. The NonStop Development Environment for Eclipse (NSDEE) 13.x versions specifically introduced a dedicated UI for setting the C++17 Language Standard.
2024: Kernel-Level Threading (KLT) The release of the L25.09 RVU brought Kernel-Level Threading to native C++ applications. This allowed C++ threads to execute concurrently across different IPUs, moving beyond the older POSIX User Threads (PUT) model.
2025: Cloud-Native Development HPE now offers the HPE NonStop Development Environment (NSDevEnv) in the public cloud, allowing developers to build fault-tolerant C++ applications using a cross-compiler model without on-premise hardware.
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.
Tandem Advanced Command Language (TACL) is the interpreted, high-level command and programming language for HPE NonStop (formerly Tandem) systems. Its timeline follows the evolution of Tandem hardware and the Guardian operating system.
Comprehensive TACL Timeline
1974–1976: Foundation of Tandem
Tandem Computers Inc. was founded. The initial operating system, Guardian, was designed for fault-tolerant computing.
Late 1970s: Initial Release
TACL was introduced in the 1970s as the primary command interface, replacing or augmenting earlier, more primitive command interpreters. It was written in TAL (Tandem Application Language).
1980s: Mature Programming Capabilities
TACL evolved from a simple shell into a powerful programming language. Key features like Macros, Routines, and Variables (TEXT, ALIAS, STRUCT) were solidified during this era to automate complex system tasks.
1994: D-Series (D30.00) Release
A significant update was documented in the TACL Programming Guide for D30.00, which detailed advanced features like Nowait I/O, Pathway Server integration, and SPI/EMS programmatic interfaces.
1997–2000s: Corporate Transitions (Compaq & HP)
1997: Compaq acquired Tandem.
2002: HP merged with Compaq, and TACL development continued under the HP NonStop banner.
2000: Updated reference manuals detailed TACL’s environment customization and the use of the _EXECUTE variable for program flow.
2010s: H-Series and HPE Era
2013: Comprehensive Reference Manuals were released, refining built-in functions for the H-Series architecture.
2015: Hewlett Packard Enterprise (HPE) was formed. TACL is now maintained as part of the HPE NonStop software stack.
Current: Legacy & Automation
TACL remains the essential tool for administrative tasks and system-level automation on modern HPE NonStop X (x86) platforms.
TAL (Tandem Application Language) is the original system programming language for the HPE NonStop (formerly Tandem) platform. Developed by Tandem Computers in the mid-1970s, it was designed to provide high-level efficiency while allowing low-level machine access, similar to C but with a syntax influenced by ALGOL.
Detailed Development Timeline
Mid-1970s: The Genesis
Tandem Computers, founded by James Treybig, introduces the first NonStop I system in 1976.
TAL is released as the primary language for writing the Guardian Operating System and system-level utilities.
The Tandem Advanced Command Language (TACL) is initially developed during this decade using TAL.
1980s: Growth and Maturity
1981–1983: Introduction of the NonStop II and TXP systems. TAL becomes the standard for developing mission-critical transaction applications like banking and point-of-sale systems.
1985: The TAL Reference Manual is updated (March 1985), formalising advanced features like DEFINEs, LITERALs, and complex pointer arithmetic.
1990s: Transition to RISC
Tandem introduces TNS/R (RISC) systems based on MIPS processors.
pTAL (Portable TAL) is introduced to allow TAL code to run “natively” on RISC hardware, offering better performance than the emulated TNS environment.
2000s–Present: Modernisation and Maintenance
2003–2005: HP (which acquired Compaq, who had bought Tandem) migrates NonStop to Intel Itanium (TNS/E) and later x86 architectures (TNS/X).
2006: The Common Run-Time Environment (CRE) is enhanced to support mixed-language programs (C, COBOL, pTAL) seamlessly.
Current Status: TAL is considered a legacy language, with most new development occurring in C/C++ or Java. However, it remains vital for maintaining the core Guardian OS and legacy banking kernels.
Typical Program Development Workflow
According to the TAL Programmer’s Guide, a developer follows this “timeline” to create a program:
Source Code Creation: Writing statements, removing comments, and defining PROCs and SUBPROCs.
Compilation: Running the TAL Compiler to generate an object file.
Binding: Using the Binder Program to link the object file with the TALLIB Run-Time Library.
Acceleration: Running the Accelerator (for TNS code) to optimise it for native hardware execution.
COBOL (Common Business-Oriented Language) has evolved from a 1959 “stopgap” experiment into a cornerstone of global finance, currently powering approximately 95% of ATM swipes and 80% of in-person credit card transactions.
The Early Years (1959–1965)
1959 (Origins): Following a meeting at the Pentagon in May, the Conference on Data Systems Languages (CODASYL) was formed to create a machine-independent language for business. It was heavily influenced by Grace Hopper’sFLOW-MATIC.
1960 (First Release): The COBOL-60 specifications were published. In December, the same program was successfully run on two different manufacturers’ computers (RCA and Univac), proving portability.
1961–1965 (Rapid Revisions): Successive updates included COBOL-61 and COBOL-65, which introduced critical features like the SORT and REPORT WRITER facilities.
Standardisation & Dominance (1968–1985)
1968 (COBOL-68): The American National Standards Institute (ANSI) published the first official standard, making COBOL the industry benchmark.
1974 (COBOL-74): This update added file organisation methods and the DELETE statement, further refining data management capabilities.
1985 (COBOL-85): A major milestone that introduced structured programming (e.g., END-IF, EVALUATE) to improve code readability and maintainability.
Modernisation & Object-Orientation (2002–Present)
2000 (The Y2K Crisis): COBOL regained global attention as programmers rushed to fix the “Millennium Bug” in legacy systems.
2002 (COBOL-2002): The first major update in 17 years introduced Object-Oriented (OO) features, Unicode support, and XML processing.
2014 (COBOL-2014): Simplified the language by making several niche features (like the SCREEN SECTION) optional and adopting IEEE 754 floating-point math.
2023 (COBOL-2023): The current ISO/IEC 1989:2023 standard added modern programming comforts like asynchronous messaging (SEND/RECEIVE), transaction processing (COMMIT/ROLLBACK), and bitwise operators.
Today, despite its age, an estimated 800 billion lines of COBOL remain in active use, with modernization efforts focusing on cloud integration and interoperability with Java and .NET.
The software known as sp/ARCHITECT (specifically the sp/ARCHITECT-BANK module) has a timeline tied to its development in Runcorn, Cheshire, by a firm originally called The Software Partnership.
Company & Product Timeline
Mid-1980s:The Software Partnership is co-founded by Nigel Walsh.
1989: The company begins significant operations in Runcorn, initially at Wingate Drive (Timperley) and later moving to Norton House in Crowngate.
1990–1994: Development period for sp/ARCHITECT in Runcorn. The software was a banking system used by major institutions including TSB, Bank of Scotland, and Rabobank.
1992: The firm relocates its Runcorn base to Wingate House on Northway.
1994: The Software Partnership is acquired by the American company Deluxe Electronic Payment Systems (a division of Deluxe Corporation).
Post-1994: Following the acquisition, the entity operated as Deluxe Data International Operations.
Later Transitions: The lineage of the Runcorn operations eventually merged into larger fintech entities, including eFunds, EFD, and ultimately FIS.
Deluxe Data, Wingate HouseThe Software Partnership, Norton House
sp/ARCHITECT-BANK module – development in Runcorn, Cheshire by The Software Partnership
HPE NonStop (originally Tandem) has a nearly 50-year history as the gold standard for fault-tolerant, “always-on” computing. Originally developed by Tandem Computers to eliminate single points of failure, the platform has survived through several major corporate acquisitions while evolving its underlying processor architecture.
Founding and The Tandem Era (1974–1997)
The “NonStop” architecture was born from the idea that a single hardware failure should never crash a system.
1974:Tandem Computers is founded by Jimmy Treybig and three former HP engineers.
1976: The first Tandem/16 (later NonStop I) is shipped to Citibank. It featured a “shared-nothing” architecture where each CPU had its own memory and copy of the Guardian OS.
1981:NonStop II is released, introducing 32-bit addressing to support larger applications.
1983: The NonStop TXP and Pathway software are introduced. Pathway revolutionized the platform by allowing programmers to write fault-tolerant apps without manually coding “checkpoints”.
1986:NonStop SQL is launched, the first fault-tolerant relational database.
1989:NonStop Cyclone arrives, a high-end mainframe-class system.
1991–1993: Transition to MIPS RISC processors begins with the Cyclone/R and the Himalaya K-series.
Corporate Acquisitions and Transition (1997–2014)
The platform changed hands twice in five years, but the mission-critical nature of the technology kept it alive.
The technical timeline for BASE24 and its core networking component, XPNET, reflects the evolution of high-availability payment switching on HP NonStop (Tandem) systems.
Technical Evolution Timeline
1980s: The Foundation
BASE24 Release: Originally developed by Applied Communications Inc. (now ACI Worldwide), BASE24 was built for the Tandem Guardian operating system.
XPNET Introduction: Developed as the Message-Oriented Middleware (MOM) to handle all transaction routing and communications. It introduced a multi-node architecture allowing different “satellite” processes (ATM, POS, Host) to communicate.
1990s: Scale and Maturity
Classic Era: BASE24 “Classic” became the industry standard for ATM and POS switching.
XPNET 3.x: Enhanced to support larger networks and more complex auditing through NCPCOM.
Language & DB: The system relied on TAL (Tandem Application Language), COBOL, and the Enscribe database.
2000s: The Shift to BASE24-eps
2003–2005: ACI introduced BASE24-eps (Electronic Payment Systems). This was a re-architecture using C++ and Java to provide platform independence.
XPNET 4.1: Released to support the transition, adding features like Common Transport Subsystem (CTS) for better Pathway integration and support for external processes.
z/OS Support: By 2009, BASE24-eps was fully ported to IBM z/OS using CICS and VSAM.
2010s – Present: Modernisation & Cloud
2014–2017: Continued updates to BASE24 Classic R6.0, maintaining its relevance for legacy users.
Cloud Enablement: Recent versions of BASE24-eps focus on REST API integration via tools like LightWave, allowing legacy XPNET paths to be exposed as web services.
Active/Active Environments: Modern implementations focus on “continuous availability” using GoldenGate for data replication between sites.
Key Technical Components
NMM (Network Management Module): The core process of XPNET that manages the configuration of lines, stations, and links.
LCONF: The Logical Network Configuration File used by XPNET to define how messages route between processes.
Auditing: XPNET provides the primary transaction auditing mechanism, which is still utilized by both Classic and eps versions.
The timeline of HPE NonStop ViewPoint (and its modern successor, Web ViewPoint) reflects the evolution of NonStop systems from Tandem’s fault-tolerant beginnings to Hewlett Packard Enterprise’s modern cloud-integrated management.
Detailed History Timeline
Pre-2000: Legacy ViewPoint
Originally developed for the Tandem NonStop platform to provide a graphical operations interface for monitoring system status and events.
Featured early support for DSM/PM (Distributed Systems Management/Performance Monitor) and event management through primary and alternate event logs.
2003–2005: Transition to Web ViewPoint
September 2003: Version 4 AAD released as an early iteration of the web-based management tool.
May–October 2004: Progressive upgrades (Versions 5.0 and 5 AAF) introduced refined management capabilities for S-Series servers.
March 2005: Version 5 AAG released, consolidating features for the S-Series.
November 2005:Web ViewPoint for Itanium (Version H01AAI) launched, marking the shift to the Intel Itanium-based Integrity NonStop architecture.
2013–2015: The x86 Revolution & Virtualization
2014: Support for Intel x86 architecture was officially announced, leading to the launch of NonStop X.
Evolution to Web ViewPoint Enterprise (WVP E): The platform evolved into an automated management product, eventually adding integration with cloud-based analytics like HPE Remote Analyst.
2018–Present: Modern Hybrid Cloud Era
L-Series Support: Continued updates provided support for L-Series operating environments and enhanced security monitoring.
2023–2024: Recent developments focus on Web ViewPoint Enterprise, featuring a global configuration platform and enhanced historical data capture through integrations like Sentinel for HPE NonStop.
For more specific documentation, you can browse the HPE NonStop Manuals on the HPE Support Center.
MultiBatch is a high-performance, mainframe-class workload automation and batch scheduling solution specifically designed for the HPE NonStop parallel architecture (formerly Tandem). It is developed by ETI-NET (formerly by Insider Technologies) to manage complex batch schedules across both NonStop Guardian and OSS environments.
Key Milestones and Timeline
1976 – Tandem NonStop Origins: The foundation for these systems was established with the introduction of the first NonStop servers by Tandem Computers.
2017 – MultiBatch Release: Insider Technologies announced an updated release of MultiBatch to enhance off-line processing flows for the HPE NonStop arena.
2019 – GUI and Monitoring Enhancements: Real-time status monitoring through a GUI interface was highlighted as a major differentiator, allowing users to visually track complex batch schedules like RTGS and securities settlements.
2020 – Business Benefits Proven: Case studies demonstrated that MultiBatch could reduce online-dealing batch times by up to 6 hours per day.
2022 – MultiBatch 10 for TBC:MultiBatch 10 was presented at the NonStop Technical Boot Camp (TBC), positioning it as the only workload manager for NonStop built on continuous innovation principles.
2024 – Modernization and Security: Recent updates focused on securing and modernizing the platform for high-performance multitasking.
Core Functionality
Parallel Execution: Supports batch schedules that run concurrently across multiple nodes, leveraging the NonStop architecture for high availability.
Hybrid Support: Seamlessly integrates both Guardian and OSS jobs within a single schedule.
Batch Prediction: Uses historical metrics in a status database to predict schedule completion times based on average and maximum elapsed run times.
Simplified Migration: Unlike NetBatch, it allows for extracting and inserting schedules between environments (e.g., test to production) without TACL changes.
MultiBatch is a high-performance, mainframe-class workload automation and batch scheduling solution
Mark Whitfield, an SC cleared, Senior IT Project Manager and Engagement Manager, spans over 30 years and transitions from specialized banking software development to high-level project leadership and cloud migrations.
Professional Career Timeline
1990 – 1994:Programmer at The Software Partnership (later Deluxe Data). Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers (now HPE NonStop) for major banks like TSB and Bank of Scotland.
1994 – 1995:Lead Analyst at Deluxe Data International, continuing support and development for banking customer systems.
1995 – 2013: Project Manager of Strategic Technical Initiatives at Insider Technologies Limited. Oversaw projects involving Reflex 80:20, Sentra development, and corporate website authoring.
2013 – 2014: Project Manager (Banking Division) at Wincor Nixdorf Limited, focusing on professional services for the banking sector.
2014 – 2016: Senior Digital Project Manager at Betfred Limited, managing the Online and Mobile Division.
The Software Partnership (TSP) was a Runcorn-based software house co-founded by Nigel Walsh in the mid-1980s. Specialising in on-line banking systems for Tandem and UNIX platforms, the company underwent several acquisitions that integrated its technology into global financial services.
Corporate Timeline
Mid-1980s: Founded as The Software Partnership.
1990: Initial operations were based at Wingate Drive in Timperley before moving to Norton House in Crowngate, Runcorn.
1992: Relocated to Wingate House on Northway, Runcorn.
1994: Acquired by the American firm Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation).
2000: The company transitioned to EFD eFunds.
2007: Became part of Fidelity National Information Services (FIS), eventually moving operations to Daresbury Park in Warrington.
Key Products
The company’s primary legacy is the development of sp/ARCHITECT-BANK, a software suite designed for secure card management and electronic transaction processing. This technology became a foundational component for the secure payment systems later managed by Deluxe Data and FIS.
The Software Partnership, Norton House, Crowngate, Runcorn, CheshireThe Software Partnership (TSP) was a Runcorn-based software houseDeluxe Data International Operations, Wingate House, Northway
Insider Technologies Limited is a UK-based software and services company founded in 1989 that specialises in 24×7 mission-critical systems, primarily for the financial, government, and defence sectors.
Key Historical Timeline
1989: Foundation. The company was incorporated on 27 February 1989. It was established in Manchester, England, by IT industry veterans.
1995–2013: Growth & Partnerships.
Became a significant HP Partner, developing solutions for the HP NonStop platform (formerly Tandem Computers).
Expanded its client base to include major institutions such as the Bank of England, Royal Bank of Scotland, and Euroclear.
2002: Training Platform Launch. Founded its interactive systems training platform, which eventually utilised its patented Cloning Technology.
2015: Leadership Transition. In October 2015, there was a major change in the board with the termination of appointments for directors Paul Cashmore, Richard Launder, and Anthony Mowatt, and the appointment of Andrew Donald Hall as a director.
2016–2017: Relocation. The company moved its registered office to 4th Floor, 2 City Approach in Eccles, Manchester, where it remains today.
2019: 30th Anniversary. Celebrated 30 years of operations, highlighting its long-term stability in the NonStop business technology community.
2020–2021: Recent Restructuring. Transitioned its ownership structure under Insider Technologies (Holdings) Limited.
2025: Current Status.
Now operates as part of the PartnerOne group, a global family of mission-critical software companies.
Continues as a Microsoft Gold Partner for Application Development.
Recent board changes include the appointment of Andrew Donald Hall and Jonathan Dionne as directors in late 2025.
Core Product Evolution
Reflex & MultiBatch: Software for business-critical 24×7 systems.
Sentra & RTLX Reactor: Monitoring and tracking products for Windows, Linux, and Unix platforms.
Mission-Critical Support: Provides 24×7 technical support for high-stakes payment and messaging systems.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers designed for 24/7, zero-downtime operations. Originally created by Tandem Computers in 1974, the architecture is now owned by Hewlett Packard Enterprise (HPE) and supports mission-critical workloads like banking and finance.
Key Aspects of HPE NonStop (Tandem):
Continuous Availability: Designed to eliminate single points of failure with 100% fault tolerance.
Architecture: Initially used a proprietary Tandem T/16 design; modern systems are based on HPE Integrity/x86 architectures.
Operating System: Traditionally runs the Guardian OS, which handles the system’s specialized, continuous processing capabilities.
Evolution: Founded by James Treybig in 1974, Tandem was acquired by Compaq in 1997, which then merged with HP in 2002.
Applications: Ideal for transactional applications requiring strict data integrity and real-time processing.
Modern Platforms: Current systems include HPE NonStop Compute NS9 X5 and NS5 X5.
The systems are still widely used today for mission-critical applications that cannot afford to be offline.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers.
Company Website – Open Content Management Framework, DotNetNuke
In the early part of the millenium, ITL requested that I design and author a new company website using the Open Content Management framework, DotNetNuke. This is a Visual Basic .NET Microsoft SQL database driven technology that enables website updates from any location with internet browser access.
As part of this exercise, website prominence was a key driver along with a more professional, corporate look-and-feel. The website is an ongoing programme of work that takes up a few hours a week of my time in taking it forward. I have attended 2 gbdirect (iTrain) website courses in this regard; ‘Writing for the Web’ and ‘Website Prominence and Visibility’. More information.
The HP NonStop (originally Tandem) timeline spans over 50 years of evolution in fault-tolerant computing, beginning with the vision of James Treybig and transitioning through several major corporate owners.
NonStop is a series of server computers introduced to market in 1976 by Tandem Computers Incorporated,[1] beginning with the NonStop product line.[2] It was followed by the Tandem Integrity NonStop line of lock-step fault-tolerant computers, now defunct (not to be confused with the later and much different Hewlett-PackardIntegrityproduct line extension). The original NonStop product line is currently offered by Hewlett Packard Enterprise since Hewlett-Packard Company’s split in 2015. Because NonStop systems are based on an integrated hardware/software stack, Tandem and later HPE also developed the NonStop OS operating system for them.
NonStop systems are, to an extent, self-healing. To circumvent single points of failure, they are equipped with almost all redundant components. When a mainline component fails, the system automatically falls back to the backup.
These systems can be used by banks, stock exchanges, payment applications, retail companies, energy and utility services, healthcare organizations, manufacturers, telecommunication providers, transportation, and other enterprises requiring extremely high uptime.
History
Originally introduced in 1976 by Tandem Computers Inc., the line was later owned by Compaq (from 1997), Hewlett-Packard Company (from 2003)[3] and Hewlett Packard Enterprise (since 2015). In 2005, the HP Integrity “NonStop i” (or TNS/E) servers, based on IntelItanium microprocessors, was introduced. In 2014, the first “NonStop X” (or TNS/X) systems, based on Intel x86-64 processors, were introduced. Sales of the Itanium-based systems ended in July 2020.[4]
Early NonStop applications had to be specifically coded for fault tolerance. That requirement was removed in 1983 with the introduction of the Transaction Monitoring Facility (TMF), along with Pathway transaction management software and SCOBOL applications (or, later, NonStop Tuxedo transaction management software), which handles the various aspects of fault tolerance on the system level.
Software
NonStop OS is a message-based operating system designed for fault tolerance. It works with process pairs and ensures that backup processes on redundant CPUs take over in case of a process or CPU failure. Data integrity is maintained during those takeovers; no transactions or data are lost or corrupted.
The operating system as a whole is branded NonStop OS and includes the Guardian layer, which is a low-level component of the operating system and the Open System Services (OSS) personality which runs atop this layer, which implements a Unix-like interface for other components of the OS to use.
The operating system and application are both designed to support the fault tolerant hardware. The operating system continually monitors the status of all components, switching control as necessary to maintain operations. There are also features designed into the software that allow programs to be written as continuously available programs. That is accomplished using a pair of processes where one process performs all the primary processing and the other serves as a “hot backup”, receiving updates to data whenever the primary reaches a critical point in processing. Should the primary stop, the backup steps in to resume execution using the current transaction.[5]
Languages supported include Java,[6]C, C++,[6]COBOL, SCOBOL (Screen COBOL), Transaction Application Language (TAL), etc. It uses the scripting and job control language TACL (Tandem Advanced Command Language), and is written in TAL and C.
Hardware
The HPE Integrity NonStop computers are a line of fault-tolerant, message-based server computers based on the IntelXeon processor platform,[4] and optimized for transaction processing. Average availability levels of 99.999% have been observed.[7] NonStop systems feature a massively parallel processing (MPP) architecture and provide linear scalability. Each CPU runs its own copy of the OS, and systems can be expanded up to over 4000 CPUs. This is a shared-nothing architecture—a “share nothing” arrangement also known as loosely coupled multiprocessing.
Due to the integrated hardware/software stack and a single system image for even the largest configurations, system management requirements for NonStop systems are rather low. In most deployments there is just a single production server, not a complex server farm.
Most customers also have a backup server in a remote location for IT disaster recovery. There are standard products to keep the data of the production and the backup server in sync, for example, HPE’s Remote Database Facility (RDF),[8] hence there is fast takeover and little to no data loss also in a disaster situation with the production server being disabled or destroyed.
The product was originally developed by Tandem Computers. Tandem was acquired by Compaq in 1997. Compaq was later acquired by Hewlett-Packard in 2002. When Hewlett-Packard split in 2015 into HP Inc. and Hewlett Packard Enterprise, Enscribe and the rest of the NonStop product line went to Hewlett Packard Enterprise.
The product primarily is used for online transaction processing and is tailored for organizations that need high availability and scalability for their database system. Typical users of the product are stock exchanges, telecommunications, POS, and bank ATM networks.
Five disk file structures: unstructured, key-sequenced, queue, entry-sequenced, and relative
Partitioned (multiple-volume) files
Multiple-key access to records
Relational access among files (where a field value from one file is used as a key to access a data record in another file)
Optional automatic maintenance of all keys
Optional key compression in key-sequenced data or index blocks
Support of transaction auditing through the Transaction Management Facility (TMF/MP). TMF is the main functional component of the NonStop Transaction Manager/MP product.
Optional compression of audit-checkpoint records
Record level locking and file level locking
Cache buffering
Optional sequential block buffering
Waited and Nowaited I/Os (multi-threading of I/O calls by the programmer)[2]
The NonStop OS Guardian APIs or the utility FUP (File Utility Program) can be used to work with Enscribe files.
A “convert” utility was provided by Tandem to aid in converting Enscribe files to NonStop SQL files, when desired.[3]
Many of the applications developed in HP NonStop servers (often critical ones) run on Enscribe databases.
History
Enscribe is designed to run effectively on parallel computers, adding functionality for distributed data, distributed execution, and distributed transactions.
First released in the early 1980s, and initially carrying an added charge until it was included with the operating system, the product became one of the few hierarchical data base systems that scales almost linearly with the number of processors in the machine: adding a second CPU to an existing server almost exactly doubled its performance.
The product was originally developed by Tandem Computers. Tandem was acquired by Compaq in 1997. Compaq was later acquired by Hewlett-Packard in 2002. When Hewlett-Packard split in 2015 into HP Inc. and Hewlett Packard Enterprise, NonStop SQL and the rest of the NonStop product line went to Hewlett Packard Enterprise.
The product primarily is used for online transaction processing and is tailored for organizations that need high availability and scalability for their database system. Typical users of the product are stock exchanges, telecommunications, POS, and bank ATM networks.[1]
History
NonStop SQL is designed to run effectively on parallel computers, adding functionality for distributed data, distributed execution, and distributed transactions.
First released in 1987, a second version in 1989[2] added the ability to run queries in parallel, and the product became fairly famous for being one of the few systems that scales almost linearly with the number of processors in the machine: adding a second CPU to an existing NonStop SQL server almost exactly doubled its performance.
The second version added /MP to its name, for Massively Parallel. A third version, NonStop SQL/MX, created a product that was more ANSI SQL compliant than its predecessor. NonStop SQL/MX has shipped on the NonStop platform since 2002, and can access tables created by NonStop SQL/MP, although only “Native SQL/MX tables” offer ANSI compliance and many “Oracle-like” enhancements. The HP Neoview business intelligence platform was built using NonStop SQL as its origins. NonStop SQL/MX is HP’s only OLTP database product.
Parts of the Neoview code base were open sourced in 2014 under the name Trafodion, which is now a top-level Apache project.
“COBOL85 nonstop” refers to the use of the COBOL85 programming language on HPE NonStop systems (formerly Tandem NonStop). The HPE NonStop platform is known for its fault-tolerant, continuous availability architecture, often used for critical, large-scale transaction processing.
Key aspects of COBOL85 on NonStop include:
Platform-Specific Implementation: HPE provided a specific implementation of the 1985 COBOL standard tailored to its unique Guardian operating system and hardware architecture.
Mission-Critical Applications: COBOL programs on NonStop are commonly used in industries such as finance, retail, and government for applications requiring high reliability and constant uptime (the “nonstop” nature of the system).
Fault Tolerance: NonStop systems achieve fault tolerance through mechanisms like process pairs, and the COBOL runtime library can interact with these features. For example, a PARAM NONSTOP OFF setting in a PATHMON configuration can prevent a COBOL85 server from running as a process pair if that behavior is not desired.
System Integration: Programmers can call Guardian procedures and use embedded SQL/MP statements within their COBOL85 programs to interact with the system’s robust file system and database.
Development and Maintenance: The combination of COBOL85 and HPE NonStop utilities is a specific skill set for developers maintaining these critical legacy systems.
Tools and Manuals: Documentation and tools, such as the INSPECT symbolic debugger and the FUP (File Utility Program), are specific to the NonStop environment and assist with development and maintenance.
HP NonStop refers to the line of fault-tolerant servers and software originally developed by Tandem Computers and now owned by Hewlett Packard Enterprise (HPE). These systems are designed for continuous operation and uninterrupted transaction processing by using redundant hardware components and independent processors to automatically failover in the event of a failure, ensuring high availability for critical applications in banking, telecommunications, and healthcare.
Origins and Evolution
Tandem Computers: Founded in 1974, Tandem introduced the NonStop system, a pioneering fault-tolerant computer with no single point of failure, revolutionizing continuous availability for online transaction processing.
Acquisitions: Tandem Computers was acquired by Compaq in 1997, and Compaq was later acquired by Hewlett-Packard (HP) in 2001.
Current Ownership: After the split of HP into Hewlett Packard Enterprise (HPE) and HP Inc. in 2015, the NonStop product line became part of HPE.
Key Features and Uses
Fault Tolerance: The systems are built with redundant components, including identical processors and storage devices, allowing them to automatically detect and recover from hardware or software failures without interruption.
High Availability: This fault-tolerant architecture is ideal for mission-critical applications that require constant uptime, such as financial transactions, emergency services, and large-scale banking systems.
Scalability: NonStop systems are designed for scalability, able to handle large commercial workloads by adding independent processors.
Specialized Database: The line includes NonStop SQL (currently SQL/MX), a relational database designed for the high availability and scalability needs of these systems.
Tandem Computers, NonStop Kernel (NSK), a timeline of the history and evolution of HP NonStop.
Note: some texts below AI generated for completeness.
Tandem’s NonStop computers, founded by Jimmy Treybig in 1974, were a revolutionary fault-tolerant system that sold its first server in 1976 to Citibank, achieving rapid growth through the 1980s before later becoming part of Compaq (1997), Hewlett-Packard (2003), and finally Hewlett Packard Enterprise (HPE). Key milestones include the 1983 introduction of the Transaction Monitoring Facility (TMF), which simplified development by handling fault tolerance at the system level, the introduction of the first NonStop X x86-based systems in 2014, and the phasing out of Itanium-based models by 2020.
1970s
1974:Tandem Computers Inc. is founded by Jimmy Treybig, with the goal of creating “NonStop” computers that don’t fail.
1975: The design of the first NonStop hardware, the Tandem/16, is completed.
1976: The first NonStop server ships to Citibank. The company experiences exponential growth.
1980s
1981: The NonStop II server is introduced, and Tandem joins the Fortune 500.
1983: The requirement for developers to code specifically for fault tolerance is removed with the introduction of the Transaction Monitoring Facility (TMF) and NonStop Tuxedo software.
1985: The first online-serviceable disk storage facilities, the V8 and XL8, are introduced.
1986: NonStop technology is used by the world’s 30 largest telecommunication companies and many top banks.
1988: Tandem acquires Ungermann-Bass, Inc. to enhance its networking capabilities.
Late 1980s: A new line of NonStop systems, including the CLX, CYCLONE, and Cyclone-R, is introduced, representing a significant redesign while maintaining fault-tolerant principles.
1990s
1990: Tandem reaches its peak revenue but begins a slow decline as the market shifts to faster, cheaper systems.
1991: Tandem announces the Tandem Image Processing System for digitized document management.
1997: Tandem is acquired by Compaq, becoming a server division within the company.
2000s
2003: Hewlett-Packard (HP) acquires Compaq, and the NonStop line becomes part of HP.
2005: The HP Integrity NonStop i (TNS/E) servers, based on Intel Itanium microprocessors, are introduced.
2010s
2014: The first NonStop X (TNS/X) systems, built on Intel x86-64 processors, are launched.
2015: Following the split of Hewlett-Packard, the NonStop division becomes part of Hewlett Packard Enterprise (HPE).
2020s
2020: Sales of Itanium-based NonStop systems end, marking a major shift to x86 architecture for the product line.
The Tandem NonStop history began in 1976 with Tandem Computers’ introduction of its fault-tolerant systems for critical transaction processing. After Tandem was acquired by Compaq in 1997, the NonStop line continued under Compaq, then Hewlett-Packard (HP) in 2003, and is now part of Hewlett Packard Enterprise (HPE) following the company’s 2015 split. Key developments include the 1983 introduction of the Transaction Monitoring Facility (TMF) and NonStop Tuxedo, the 2005 arrival of NonStop i servers based on Intel Itanium processors, and the 2014 launch of the NonStop X systems using Intel x86-64 processors.
Also;
1970s
1974: Tandem Computers is founded in Cupertino, California, by Jim Treybig.
1976: Tandem introduces its first NonStop fault-tolerant system.
1970s: Tandem’s architecture is designed for continuous availability and zero data loss, becoming the dominant manufacturer of fault-tolerant computer systems for ATM networks, banks, and stock exchanges.
1980s
1983: Tandem introduces the Transaction Monitoring Facility (TMF) and the Pathway transaction management software, removing the need for applications to be specifically coded for fault tolerance.
1986: Tandem launches NonStop SQL, the first fault-tolerant SQL database, which offers unique features for data integrity across nodes and can scale performance with additional nodes.
1989: A new version of NonStop SQL adds transactions that can be spread across multiple nodes, a groundbreaking feature for the time.
1990s
1997: Compaq acquires Tandem Computers, with NonStop becoming a server division within Compaq.
2000s
2003: Hewlett-Packard (HP) acquires Compaq, integrating the NonStop line into its operations.
2005: HP introduces the HP Integrity NonStop i servers (also known as TNS/E), which are based on Intel Itanium microprocessors.
2010s
2014: HP launches the first NonStop X systems (TNS/X), which are built on Intel x86-64 processors.
2015: Following the split of Hewlett-Packard, the NonStop division becomes part of Hewlett Packard Enterprise (HPE).
2020s
2020: Sales of the Itanium-based NonStop systems end.
2025 (Present): HPE continues to operate the NonStop platform, a technology that still serves critical infrastructure requiring high availability and continuous operation.
PROject Templates 
