Category: NSK

Tandem Computers ( HPE NonStop ) Overview & Detailed Timeline

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

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

Overview of Key Technologies

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

Detailed Historic Timeline by Era and Year

The Founding Era (1974–1979) 

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

The Growth and Competition Era (1980–1989)

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

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

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

Acquisition and Integration Era (1997–Present)

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

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

Tandem Computers Overview and Detailed Timeline

HPE NonStop ViewSys Overview and Timeline by Era

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. 

Detailed Historic Timeline: ViewSys & NonStop Monitoring Evolution

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 ViewSys Overview and Timeline by Era

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

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

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

EMSDist Overview

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

Detailed Historic Timeline and Evolution

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

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

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

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

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

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

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

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

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

Key Functional Milestones

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

HPE NonStop EMSDIST, Event Management Service Distributor Timeline by year

sp/ARCHITECT electroinic banking by The Software Partnership TSP

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

sp/ARCHITECT electroinic banking by The Software Partnership TSP

Overview

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

Historical Timeline

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

sp/ARCHITECT electroinic banking by The Software Partnership TSP

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

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. 

Internet Links & Manuals

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

HPE NonStop PATHCOM, interactive management interface, Pathway transaction processing environment

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. 

The Compaq & Early HP Era (1997 – 2014) 

  • 1997: Compaq acquires Tandem.
  • 2002: HP merges with Compaq.
  • 2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
  • 2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads. 

The Modern HPE Era (2014 – Present)

  • 2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
  • 2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
  • 2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality

Future of NonStop Pathway

HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:

  • Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
  • Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
  • Open Integration: Continued emphasis on open application development environments and open-source frameworks.
  • Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.

HPE NonStop PATHCOM, interactive management interface, Pathway transaction processing environment

HPE NonStop Spoolcom subsystem Spooler Command Language program Overview and Timeline

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. 

Useful Resources

HPE NonStop Spoolcom subsystem Spooler Command Language program – Overview and Timeline

HPE NonStop Inspect debugger Overview and timeline by year

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.
  • 2025: HPE celebrates 50 years of NonStop; updates to the OS introduce greater development and debugging flexibility for named processes on NS5 X5 and NS9 X5 platforms. 

Future Outlook

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.
  • AI Integration: Future enhancements likely include AI-driven diagnostics and automation within the debugger infrastructure to manage the complexity of modern REST/JSON API gateways and Kafka messaging buses.

HPE NonStop Inspect debugger Overview and timeline by year

Richard Buckle of Pyalla Technologies, is a thought leader in the HPE NonStop community

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.
  • 2014 – 2015: Launch of HPE Integrity NonStop X, utilizing InfiniBand and x86 architecture.
  • 2016: Demonstrations of Virtual NonStop (vNonStop), moving the platform toward software-defined infrastructure.
  • 2020 – 2021: Focus shifts to hybrid cloud and containerized environments. 

The 50th Anniversary & AI Era: Resilience (2024 – 2026+)

Current columns focus on “Business Resilience” and the integration of AI into mission-critical systems. 

Richard Buckle of Pyalla Technologies, is a thought leader in the HPE NonStop community

Real Time View

Senior IT Project Manager & Project Templates author – Mark Whitfield

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

Comprehensive Career Timeline

Early Career & Foundations (1988–1995) 

  • 1988–1990: Completed Higher National Diploma (HND) in Computing at Bolton Institute of Higher Education (BIHE).
  • 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. 

Client & Colleague Recommendations

Mark Whitfield is noted for being a detail-oriented manager who provides a strong barrier between developers and difficult clients, while maintaining a friendly, professional, and diplomatical approach. 

  • 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. 

Key Areas of Expertise

  • Methodologies: PRINCE2 Practitioner, Agile SCRUM, ITIL, ISO9001:2008.
  • Tools: MS Project, MS Excel/Office, RAID logs.
  • Technical Background: HP NonStop (Tandem) Systems, BASE24, C++, TAL, COBOL.
  • Industries: Financial/Banking, Aerospace & Defence, Government, Automotive, Gambling. 

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.
  • Project Governance (Word & PowerPoint): Project initiation documentation (PID), status reports, RACI matrices (responsible, accountable, consulted, informed), and project organization charts.
  • Agile/Scrum Tools: Burn-down and burn-up charts, story dependency trackers, and Kanban templates.
  • Closeout: Lessons learned logs and benefit realization analysis trackers. 

Where to Buy

  • Official Website: mark-whitfield.com (PROject Templates) is the primary source, offering a bundle with free lifetime upgrades.
  • Etsy: Mark Whitfield’s templates are available for purchase here, particularly for those needing alternative payment methods.
  • Eloquens: He maintains a channel on Eloquens for downloading professional templates. 

The templates are fully editable, allowing users to tailor them to specific project requirements. 

Mark Whitfield, Senior IT Project Manager

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)
  • Key Skills: Agile Scrum, PRINCE2, ITIL, Financial Forecasting, Stakeholder Management, Technical Initiative Leadership.
  • Education: Computing (Graduated 1990). 

Comprehensive Career History

  • Capgemini UK (Jan 2016 – Present): SC Cleared Engagement Manager (A8) in Custom Bespoke Solutions.
    • Recent Experience: Project Manager for a UK-wide Air Traffic organisation, delivering new Apple iOS Apps for military and public use.
  • Betfred Limited (Dec 2014 – Jan 2016): IT Senior Digital Project Manager, Online and Mobile Division.
  • Wincor Nixdorf Limited (Sep 2013 – Dec 2014): Project Manager, Professional Services – Banking Division.
    • Key Project: Managed a £5+ million project replacing legacy HP NonStop software systems with AIX-based J2EE/Oracle technologies for a major UK bank.
  • Reflex / Insider Technologies (Aug 1995 – Sep 2013): Project Manager – Strategic Technical Initiatives.
  • eFunds (1994 – 1995): Lead Analyst. 

Certifications & Training

  • Cloud & Project Management: AZ-900 Microsoft Certified Azure Fundamentals (2022), Advanced Engagement Management (2017), Registered PRINCE2 Practitioner (2011).
  • Agile: Agile SCRUM Training (2011).
  • Technical: TANDEM Performance Analysis (1995), C++ for Non-C Programmers (1997), Querying MS SQL 2000 (2009). 

Awards

  • C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications (Capgemini UK, Dec 2022).
  • Project Recognition Award – Wincor Nixdorf (Retail Banking Project). 

Web Presence & Documents

Mark Whitfield, Senior IT Project Manager

By era;

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.
  • Key Industries: Financial services, electronic banking, government, automotive, aerospace.
  • Core Competencies: Software development (C, C++, COBOL, TAL), Project Management (PRINCE2 Practitioner, Scrum), Pre-sales technical consultancy. 

Career Timeline by Era and Year

1. The Foundation & Tandem Era (1990–1995)

  • 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

HPE NonStop architecture overview and technical commentary and approach by era and year

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. 
  • Summary of Architectural Evolution

TAL & PTAL Programming Language on Tandem HPE NonStop

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, Website Author – Background and Career Timline

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.
  • 2016–Present: Senior Engagement Management (Capgemini)
    • Role: Engagement Manager (A8), Custom Bespoke Solutions.
    • 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. 

Mark Whitfield Background and Career Timline

RTLX by Insider Technologies, Overview and Timeline by Year

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. 

EBUG Conference, Mark Whitfield – Product Manager

The Foundational Era (1989–2000)

  • 1989: Insider Technologies Limited is founded in Manchester, UK, by IT industry veterans.
  • 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 Overview and Historical Timeline

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.
  • 2015: Hewlett-Packard splits into HP Inc. and Hewlett Packard Enterprise (HPE).
  • 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 by ACI Worldwide timeline by era and year

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:

Detailed Timeline

The Foundation Era (1970s – 1990s)

  • 1975: ACI is founded in Omaha, Nebraska, initially developing software for NonStop server computers.
  • 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. 

Modernization & Cloud Era (2014 – Present)

HP NonStop Tandem Training provided by HPE Education Services

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.
  • Architecture & Concepts: Understanding fault tolerance, “fail fast” mechanisms, and message-based operating systems.
  • Database Management: Specialized courses for NonStop SQL/MX, SQL/MP, and Enscribe.
  • Application Development: Training in languages like C/C++, COBOL, and TAL (Transaction Application Language).
  • Modern Environments: Transitioning to virtualised instances and hybrid cloud infrastructures. 

Detailed course information, including outlines and lab access, is available through the HPE NonStop Compute training portfolio. 

Detailed Textual Timeline: Era & Year

The NonStop platform has undergone three major architectural shifts since its founding.

1. The Tandem Era (1974–1997)

  • 1974: Tandem Computers Inc. is founded by James (Jimmy) Treybig.
  • 1975: Design of the Tandem/16 (later NonStop I) is completed.
  • 1976: The first system is shipped to Citibank, marking the birth of commercial fault-tolerant computing.
  • 1981: NonStop II is introduced, adding 32-bit addressing support.
  • 1983: NonStop TXP launches as the first new implementation of the instruction set, featuring cache memory.
  • 1983: Transaction Monitoring Facility (TMF) and Pathway are introduced, removing the need for applications to be manually coded for fault tolerance.
  • 1986: NonStop VLX is released with 32-bit datapaths and NonStop SQL, the first fault-tolerant SQL database.
  • 1987: NonStop CLX is introduced for the low-end/distributed market.
  • 1989: NonStop Cyclone debuts for high-end mainframe-level performance.
  • 1991: Migration to MIPS architecture begins with the Cyclone/R.
  • 1993: NonStop Himalaya K-series is released, using native MIPS R4400 processors.
  • 1994: Open System Services (OSS) adds a POSIX-compliant environment to the NonStop Kernel.
  • 1997: NonStop Himalaya S-Series introduces ServerNet, replacing older bus architectures. WikipediaWikipedia +7

2. The Compaq Era (1997–2002)

  • 1997: Compaq acquires Tandem Computers.
  • 1999: Zero Latency Enterprise (ZLE) solutions are introduced for real-time information access.
  • 2001: Compaq announces the migration of the entire NonStop line to Intel Itanium processors. 

3. The HP / HPE Era (2002–Present)

  • 2002: HP merges with Compaq, bringing the NonStop division under HP.
  • 2005: HP Integrity NonStop (“NonStop i” or TNS/E) is launched, completing the migration to Itanium.
  • 2014: NonStop X (TNS/X) is introduced, transitioning the platform to Intel x86-64 architecture.
  • 2015: Hewlett-Packard splits; NonStop becomes part of Hewlett Packard Enterprise (HPE).
  • 2020: Sales of Itanium-based systems officially end.
  • 2023–2024: NonStop evolves to support virtualised instances and deployment on hybrid infrastructures. 

HP NonStop Tandem Training provided by HPE Education Services

HP NonStop Tandem Overview and Timeline History by year

HP NonStop is a series of fault-tolerant server computers designed for online transaction processing (OLTP) and mission-critical applications that require 100% uptime. Originally introduced by Tandem Computers Inc. in 1976, the platform uses a proprietary, integrated hardware and software stack known as NonStop OS (formerly Guardian) to eliminate single points of failure through massive redundancy and “fail-fast” logic. 

Historical Timeline by Era

1. The Tandem Founding Era (1974–1981) 

  • 1974: Tandem Computers Inc. is founded by James (Jimmy) Treybig and a team from Hewlett-Packard’s HP 3000 division.
  • 1976: The first system, the Tandem/16 (later NonStop I), is shipped to Citibank.
  • 1977: Tandem systems gain early traction as intelligent front-end processors for bank ATM networks. 

2. The Stack Machine Expansion (1981–1990) 

  • 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 HP NonStop Tandem experience & Project Management Templates

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