Category: NSK

BITUG BIG SIG

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.

Program Highlights

  • Breakout Tracks: Strategic vendor sessions outlining software developments and architectural security.
  • 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 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.

European BASE24 User Group (EBUG) was a prominent, community-led organization

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.
European BASE24 User Group (EBUG) was a prominent, community-led organization
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.
European BASE24 User Group (EBUG) was a prominent, community-led organization
HP booth at Vienna EBUG, 2008
  • 2009 — Prague Conference: Continues strong advocacy and technical troubleshooting for BASE24 on NonStop despite broader industry platform shifts.
European BASE24 User Group (EBUG) was a prominent, community-led organization
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 System Monitoring Reflex Product

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;

C-Deep (Transaction Monitoring)

The Insider Reflex product at ETI-NET is now called Sentinel for NonStop Monitoring;

Sentinel (Nonstop Monitoring)

C-Deep for Transaction Monitoring & Sentinel for HPE NonStop Monitoring

BASE24 and BASE24-eps architecture overview

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

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

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

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

BASE24 and BASE24-eps architecture overview
BASE24 architecture overview

Core Structural Component Layers

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

1. Network & Message Routing Component (XPNET)

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

2. Perimeter Access Layer (Device Handlers)

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

3. Core Transaction Logic (Authorization System)

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

4. Boundary Channels (Interchange & Host Interfaces)

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

5. Offline & Administrative Subsystems

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

Architectural Divergence: Classic vs. EPS

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

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

End-to-End Component Transaction Flow

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

BASE24 and BASE24-eps architecture overview

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

HPE NonStop MultiBatch Batch Job Scheduling Overview and Timeline

Overview

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 & funds-transfer software suite

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
1990: TSP relocates to Norton House in Runcorn
1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.
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.

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

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

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

Event Location

Orlando, Florida

Venue

The Rosen Plaza 9700 International Drive

Contact Us

info@connect-community.org

TBC’26

HPE NonStop Conferences Insight and Timeline by Era

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.
  • 2005: Introduction of HP Integrity NonStop i servers based on Intel Itanium.
  • 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. 

Detailed Historical Conference & Product Timeline (1970s–Present)

  • 1974–1979: The Founding Era
    • 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.
    • 2005: Introduction of Integrity NonStop servers, fully leveraging Intel’s Itanium architecture.
  • 2011–Present: HPE NonStop and Cloud Era
    • 2014: Formation of HPE (Hewlett Packard Enterprise).
    • 2015: Introduction of NonStop X, moving from Itanium to Intel x86-64 processors.
    • 2023-2024: Celebration of 50 years of Tandem/NonStop. The platform embraces virtualization and converged infrastructure.
    • 2025/2026: NonStop TBC 2026 is scheduled for Sept 15-17 in Orlando, FL, focusing on AI integration, modernization, and hybrid cloud. 

Key Conference Themes & Insights (2026 Perspective)

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