Category: Career

Overview of BASE24 and XPNET plus application timeline by era

Overview of BASE24 and XPNET

BASE24 is an enterprise-grade electronic funds transfer (EFT) software suite developed by Applied Communications Inc. (now ACI Worldwide). It handles real-time transaction acquiring, authenticating, routing, switching, and authorization across ATMs, Point-of-Sale (POS) networks, and digital payment channels.

XPNET (Exchange Protocol Network) is the fundamental communications middleware layer designed explicitly for BASE24 on fault-tolerant systems. It acts as an abstraction layer managing interprocess communications (IPC), network protocols (e.g., Bisync, X.25, TCP/IP), line management, device messaging, and high-volume transaction routing. Together, they form the transactional backbone for a majority of the world’s top financial institutions.

I worked on BASE24 / BASE24-eps transaction tracking and XPNET monitoring at Insider Technologies Limited (ITL) in the early part of the millennium. See also HP NonStop Connection Journal article in 2013.

BASE24-eps extraction and ITLs RTLX in 2007
BASE24-eps extraction
and ITLs RTLX (in 2007)
RTLX Reactor (in 2012) for tracking BASE24-eps and BASE24 XPNET transactions
RTLX Reactor (in 2012) for tracking
BASE24-eps & BASE24 XPNET transactions

Deep-Dive Architecture and Technology Stack

1. BASE24 Core Design

  • Process Pair Architecture: Designed natively around Tandem’s process pairs. A Primary Process performs the active transaction switching while a Backup Process remains synchronized in a standby state. If the hardware or primary process fails, the backup takes over instantly with zero data loss or session drops.
  • Functional Modules: Divided into specific transactional entities:
    • ATM (Automated Teller Machine Device Handler): Direct control and state management of physical terminals using custom message streams (e.g., Diebold, NCR).
    • POS (Point of Sale): Merchant terminal management and merchant accounting integration.
    • Auth (Authorization Processor): Internal validation scripts against account records or stand-in limits.

2. XPNET Middleware Engine

  • Line and Station Infrastructure: XPNET maps communication through abstract configurations. A Line represents a physical or logical network pipe, and a Station represents an endpoint (e.g., an interchange gateway or terminal node).
  • Dynamic Load Buffering: Employs internal memory queue structures to absorb traffic spikes from international card networks (such as Visa and Mastercard) without spilling into disk storage.
  • Protocol Multi-threading: It decouples low-level link dynamics (e.g., CRC checking, dropouts) from core business logic, converting legacy and modern network formats into standardized internal transaction tokens.

Application Development Timeline & Political Breakdown

The timeline below details how geopolitical, regulatory, and corporate ownership developments directly shaped versioning and core code changes in BASE24 and XPNET.

Era 1: The Tandem & Expansionist Era (1975–1992)

  • Geopolitical & Industry Context: The rise of consumer credit card networks, personal checking accounts, and the physical expansion of banking via ATMs. Regional networks were fragmented, necessitating specialized software to cross-connect them.
  • Corporate Dynamics: Applied Communications Inc. (ACI) operated as an independent software house in Omaha, Nebraska, forming a deep partnership with Tandem Computers before being acquired by US West (1988) and later Tandem directly (1991).
  • Year-by-Year Code & Technical Milestones:
    • 1975–1981: Initial exploration of high-availability banking systems on Tandem NonStop computers. Developers laid the groundwork using Tandem Screen COBOL and low-level communication drivers.
    • 1982: BASE24 v1.0 officially launches. The original codebase was written in TAL (Tandem Application Language), a high-performance, structured system programming language designed specifically for NonStop systems.
    • 1985: A primitive version of XPNET is spun out from early shared-memory messaging code to support multi-protocol lines (Bisync, Async) without forcing restarts of the core application.
    • 1987: Introduction of early ISO 8583 message formatting engines within the core routing code. This allowed the software to natively interpret standard financial messaging frames across distinct interbank networks.
    • 1991: Tandem acquires ACI. Code refactoring focused heavily on optimizing interactions with Tandem’s native file system (Enscribe) and expanding the XPNET process memory layout to take advantage of new Tandem CLX architecture performance.

Era 2: The TSA Corporate & Public Market Era (1993–2000)

  • Geopolitical & Industry Context: Globalization of financial services, the consolidation of national card switches, and the commercial explosion of internet banking and POS devices.
  • Corporate Dynamics: Tandem divested ACI to a private holding company, leading to the creation of Transaction Systems Architects (TSA) in late 1993. TSA went public on NASDAQ in 1995, pushing development velocity to meet Wall Street expectations.
  • Year-by-Year Code & Technical Milestones:
    • 1993–1994: Standardized compilation routines moved to Tandem’s pTAL (portable TAL) to bridge code execution compatibility between older CISC-based architectures and the newly emerging MIPS RISC processors.
    • 1995–1996: BASE24 version 4.x introduces advanced multi-institution handling inside a single logical codebase, allowing multi-tenant processing for third-party credit card consolidators.
    • 1997: Release of BASE24 v5.x, featuring significant expansions in XPNET (v2.x) to accommodate native TCP/IP sockets alongside aging X.25 line infrastructures.
    • 1998–1999: Heavy investment into Y2K compliance remediation. Code changes involved updating binary-coded decimal (BCD) date configurations, expanding date-storage windows across Enscribe files, and deploying the BASE24 Year 2000 System Assessment frameworks globally.

Era 3: Enterprise Platform Shift & Consolidation (2001–2014)

  • Geopolitical & Industry Context: Post-9/11 regulatory changes (e.g., USA PATRIOT Act), the implementation of modern security standards like Triple DES (TDES), and the birth of the PCI-DSS (Payment Card Industry Data Security Standard). Mainframes and alternative hardware processors (IBM, HP-UX) became fierce competitors to Tandem.
  • Corporate Dynamics: TSA officially rebranded to ACI Worldwide, Inc. (ACIW) in 2007. A strategic decision was made to rewrite the platform to break vendor lock-in and provide cross-platform flexibility.
  • Year-by-Year Code & Technical Milestones:
    • 2001–2002: Standard cryptographic layers within BASE24 are systematically modified to enforce Triple DES compliance across automated teller machines.
    • 2003: ACI introduces BASE24-eps (Enterprise Payments System). This marked a foundational architecture shift, moving away from TAL/pTAL entirely to an object-oriented paradigm written in C++ and designed to execute cross-platform (HPE NonStop, IBM z/OS, AIX, Linux).
    • 2005–2006: BASE24-es/eps code integrates with enterprise middleware layers such as IBM WebSphere MQ, using CICS containers on z/OS to deliver modern service-oriented architecture (SOA) web services wrappers.
    • 2008–2010: ACI shocks the banking industry by announcing the sunsetting of standard maintenance for classic Tandem NonStop BASE24 by late 2011. Millions of lines of legacy TAL code are effectively frozen, forcing major migrations toward BASE24-eps.
    • 2011–2013: Code enhancements center around PA-DSS validation and securing encryption pathways to ensure tokenized processing. XPNET 3.x is deployed onto newer HP Integrity Itanium-based J-Series and H-Series blades.

Era 4: Modernization, Cloud-Native, and Open Systems (2015–Present)

  • Geopolitical & Industry Context: The dominance of Real-Time Payments (RTP, FedNow, ISO 20022 formats), cloud computing mandates, and aggressive cost-reduction pushes away from high-maintenance legacy hardware configurations.
  • Corporate Dynamics: ACI pivots sharply to open-ecosystem SaaS delivery, cloud partnerships (AWS, Microsoft Azure, Google Cloud), and co-development with IBM to optimize cross-platform throughput.
  • Year-by-Year Code & Technical Milestones:
    • 2015–2016: BASE24-eps code is successfully ported to Red Hat Enterprise Linux (RHEL) on standard x86 processors. This architectural pivot offered a reduction in total cost of ownership (TCO) compared to legacy hardware by providing massive processing scaling.
    • 2018–2020: The introduction of standard ISO 20022 messaging libraries into the switching matrix to support instant transaction settlement schemes globally.
    • 2021–2024: Legacy middleware systems are phased down. Modern releases feature direct REST API hooks, cloud-adaptor hooks, containerised microservices integration, and extended configuration capabilities via the ACI Desktop GUI.
    • 2025–2026: ACI partners with IBM to launch native 64-bit deployment optimizations for BASE24-eps running on IBM Z mainframes (including z16/z17 configurations), incorporating hardware-driven AI fraud analysis models and full PCI-SSF (PCI 4.0) certification.

Overview of BASE24 and XPNET plus application timeline by era

Over 200 editable templates tailored for Agile Scrum, Waterfall, and PRINCE2 frameworks

Mark Whitfield’s premium project management toolkit consists of over 200 editable templates tailored for Agile Scrum, Waterfall, and PRINCE2 frameworks. Built across 30+ years of digital and IT delivery, these frameworks prioritize corporate governance, seamless stakeholder reporting, and visual lifecycle control.

Example of many plan on a page poap ppt templates
Many POAP, Plan on a Page example templates

Below is the comprehensive, scannable breakdown of the core artifacts categorized by lifecycle focus, purpose, and application format. Purchase project templates here.

📅 1. Master Planning & Visual Roadmapping

These tools serve as the operational foundation for tracking dependencies, defining Work Breakdown Structures (WBS), and establishing executive visibility.

  • Detailed Software Development Life-Cycle (SDLC) Plan
    • Focus: End-to-end task tracking from inception and elaboration to construction, testing, and transition.
    • Format: Microsoft Project (.mpp) & Microsoft Excel (.xlsx).
    • Source Page: Mark Whitfield PMO Toolkit
  • PRINCE2 7th Edition Master Project Plan
    • Focus: Standardized governance processes structured according to the latest PRINCE2 methodology.
    • Format: Microsoft Project (.mpp) & Microsoft Excel Gantt Tracker.
    • Source Page: Mark Whitfield PRINCE2 Master Walkthrough
  • Plan on a Page (POaP) Blueprint
    • Focus: High-level, timeline-focused visual summaries mapping deliverables and milestones to client monthly views.
    • Format: Microsoft PowerPoint (.pptx, 30+ layout variations) & MS Excel.
    • Source Page: Mark Whitfield POaP Templates
Example MS Excel Project Plan template
Example MS Excel Project Plan template

🛡️ 2. Risk, Governance & Operational Control

These registers form the “engine room” of project health management, shifting risk mitigation from reactive to predictive.

  • Comprehensive RAID Log & Tracker
    • Focus: Integrated visibility over Risks, Actions, Issues, and Dependencies, alongside change requests and supplier impacts.
    • Format: Microsoft Excel (.xlsx featuring self-populating chart dashboards).
    • Source Page: Mark Whitfield Operational Tracking Tools
  • Agile Story Dependency Tracker
  • RACI Matrix
    • Focus: Mapping roles and responsibilities across project deliverables (Responsible, Accountable, Consulted, Informed).
    • Format: Microsoft Excel (.xlsx).
    • Source Page: Mark Whitfield Folder Structure & Guide
Example MS Excel RACI matrix template
Example MS Excel RACI matrix template

📊 3. Performance reporting & Stakeholder Engagement

Designed to eliminate subjective performance analysis and maintain executive-level clarity.

  • Weekly / Monthly Project Status Report
    • Focus: Summarizing target completion, look-aheads, RAG indicators, and critical decisions for clients.
    • Format: Microsoft Word (.doc) & Microsoft PowerPoint (.pptx).
    • Source Page: Mark Whitfield Premium Delivery Page
  • Stakeholder Analysis & Influence Matrix
    • Focus: Mapping stakeholder influence versus organizational impact to tailor communication (Involve, Inform, Consult, Monitor).
    • Format: Microsoft Excel (.xlsx).
    • Source Page: Mark Whitfield Folder Structure & Guide
  • Project / Programme Kick-Off Deck
    • Focus: Initial team mobilization, workspace onboarding, and client approach alignment.
    • Format: Microsoft PowerPoint (.pptx).
    • Source Page: Mark Whitfield Main Purchase Index
Example PPT slide for Org. Structure
Example PPT slide for Org. Structure

💰 4. Financial Trackers & Value Realization

These artifacts manage fiscal discipline, pricing bids, and mapping long-term outputs to business outcomes.

  • Full Project Financial Tracker
    • Focus: Internal/external cost variance, forecasting models, contractor day rates, margin tracking, and expense visibility.
    • Format: Microsoft Excel (.xlsx with embedded financial trend charts).
    • Source Page: Mark Whitfield Premium Delivery Page
  • Statement of Work (SOW) Templates
    • Focus: Work order structuring and delivery guardrails for both commercial Waterfall and Agile contracts.
    • Format: Microsoft Word (.doc).
    • Source Page: Mark Whitfield Operational Tracking Tools
  • Benefits Realization Analysis Tracker
    • Focus: Comparing projected baseline targets with actual organizational outcomes post-deployment.
    • Format: Microsoft Excel (.xlsx).
    • Source Page: Mark Whitfield Premium Delivery Page
Example Excel Project Financial Tracker
Example Excel Project Financial Tracker

🏃 5. Agile Delivery Tools

Alternative visual logs created for environments where dedicated software like Jira or Azure DevOps is unavailable.

  • Agile Burn Down & Burn Up Charts
    • Focus: Visualizing sprint velocity, work remaining, and scope creep across iterative delivery cycles.
    • Format: Microsoft Excel (.xlsx with automatic mathematical plotting).
    • Source Page: Mark Whitfield Folder Structure & Guide
  • MS Teams Planner & To-Do Guide
    • Focus: Step-by-step framework configuration for running Kanban-style card streams in the cloud.
    • Format: Microsoft Word Walkthrough (.docx).
    • Source Page: Mark Whitfield Master Index
Example Agile Scrum Burn Up Chart
Example Agile Scrum Burn Up Chart
Example Agile Scrum Burn Down Chart
Example Agile Scrum Burn Down Chart

PRINCE2 or PRINCE2 Agile, features discussion

The choice between PRINCE2 and PRINCE2 Agile depends entirely on your project environment: PRINCE2 is best for highly structured, predictable projects with fixed requirements, while PRINCE2 Agile is designed for dynamic environments that require iterative delivery and flexibility.

Both methodologies are owned by PeopleCert and build upon the same core governance framework.

Core Differences

The table below breaks down how these two frameworks compare across key project dimensions:

PRINCE2 and PRINCE2 Agile features
Comparison PRINCE2 and PRINCE2 Agile features
PRINCE2 and PRINCE2 Agile features

PRINCE2 Breakdown

Traditional PRINCE2 (Projects IN Controlled Environments) is a structured, process-based approach for project management. It provides a clear blueprint for roles, responsibilities, and management stages.

  • Fixed Targets: It fixes the project scope, time, and cost upfront to minimize risk.
  • The 7 Principles: It relies on universal principles, such as continued business justification and defined roles.
  • Management Stages: Projects are broken into distinct sections to review progress before moving forward.
  • Predictability: Ideal for large infrastructure, construction, or compliance-heavy projects where changes are costly.

PRINCE2 Agile Breakdown

PRINCE2 Agile does not replace traditional PRINCE2; instead, it wraps agile delivery methods around the existing PRINCE2 governance framework. It allows corporate management to maintain control while development teams use frameworks like Scrum or Kanban.

  • The Hexagon: It fixes time, cost, quality, and benefits, but makes scope and risk flexible.
  • Agile Integration: It introduces agile concepts like daily standups, burn charts, and retrospectives.
  • Maturity Tool: It uses the “Agilometer” to assess if a project is suitable for agile execution.
  • Speed to Market: Ideal for software development, creative industries, or any project requiring quick consumer feedback.

Which Certification Should You Choose?

  • Choose PRINCE2 if you work in a traditional industry, need to establish clear corporate governance, or manage projects with strictly defined outcomes.
  • Choose PRINCE2 Agile if you already work in an agile environment and need to add corporate structure, or if your organization is transitioning from waterfall to agile.

Mark Whitfield, May 2011 – Registered PRINCE2 Practitioner with ILX

Mark Whitfield May 2011, Registered PRINCE2 Practitioner with ILX

sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire

The Software Partnership Logo
The Software Partnership Logo

The core electronic banking software product sp/ARCHITECT-BANK was originally developed by The Software Partnership (TSP), a highly specialized British software house co-founded by Nigel Walsh in Runcorn, Cheshire.

Engineered to deliver high-availability, fault-tolerant electronic and desktop home-banking services, it ran natively on Tandem NonStop mainframe computers (now HPE NonStop).

The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire

Over the decades, the product evolved through major corporate acquisitions, eventually being integrated into enterprise-level banking suites like CONNEX Advantage under eFunds and FIS.

The detailed timeline of the product, broken down by corporate era and year, is provided below by Mark Whitfield.

Click the previous link for more sp/ARCHITECT BANK project level detail between 1990 thru 1995.

Also, here is a LinkedIn group for the company Alumni.

🌅 Era 1: The Inception and Independent Software House Era (Mid-1980s–1993)

During this foundational era, The Software Partnership engineered the core product from scratch to meet the emerging demand for “Direct Electronic Banking” before the commercial internet became prevalent.

  • 1985: The Software Partnership (TSP) is co-founded by Nigel Walsh in Runcorn, Cheshire. Development begins on a standard product architecture designed specifically for the transaction processing monitor (PATHWAY) and operating system (Guardian) of Tandem Computers.
  • 1988–1989: The company establishes sp/ARCHITECT (and its core module, sp/ARCHITECT-BANK) as a premier client-server base package for corporate and home-office electronic banking.
  • 1990: The engineering team scales up to build standard product releases written in COBOL85 and utilizing NonStop SQL databases. They develop proprietary testing utilities like sp/TESTBED to simulate PC-to-mainframe interfaces. Mark Whitfield joins the company after graduating in Computing in late 1990.
  • 1991: Major deployment begins for the high-profile Barclays Business Master II (BBM II) desktop corporate banking application, with TSP placing teams (including Mark Whitfield) on-site at Barclays in Knutsford, Cheshire.
Barclays, Radbroke Hall, Knutsford, Cheshire
Barclays, Radbroke Hall, Knutsford, Cheshire
  • 1992: A batch billing and invoicing suite of modules is engineered over 3-months and appended to the Barclays installation at Poole, Dorset. Mark Whitfield is assigned to this HPE NonStop (Tandem) billing/ invoicing development on the UK south coast. Simultaneously, TSP expands internationally into continental Europe.
Barclays, Wimborne Road, Poole, Dorset
Barclays, Wimborne Road, Poole, Dorset
  • 1993: TSP develops an automated, touch-tone voice menu system for Girofon (Denmark). The code interfaces phone lines through Periphonics Interactive Voice Response (IVR) hardware directly into the back-end Tandem banking system. Concurrently, the core application handles desktop money transfers and early logic checking for clearing giants TSB and Bank of Scotland. Mark Whitfield is also involved with supporting this IVR technology.

🤝 Era 2: The Deluxe Data International Era (1994–1999)

Recognizing the massive European banking client footprints of sp/ARCHITECT, US-based electronic funds transfer (EFT) specialist Deluxe Data acquired TSP to merge their direct banking and card processing capabilities.

  • 1994: Deluxe Data Corporation acquires The Software Partnership. The Runcorn offices are reorganised as Deluxe Data International Operations.
Deluxe Data International Operations, Wingate House, Northway
Deluxe Data International Operations, Wingate House, Northway
  • 1995: The product undergoes heavy code optimization to satisfy customer acceptance loops for international clearers, notably deploying direct electronic banking solutions for major Dutch institutions like Rabobank. Mark Whitfield moves on from Deluxe Data (after 5 years) to Insider Technologies Limited in Salford Quays in late 1995. This to continue HPE NonStop programming work for both monitoring and diagnostic products like Reflex 80:20.
  • 1996: Development transitions toward hybrid enterprise networking. The sp/ARCHITECT system is updated with custom TCP/IP software interfaces to allow newer mid-range UNIX servers (such as IBM RS/6000) to safely communicate with the core Tandem server environment.
  • 1997: Deluxe Data expands the core platform’s messaging logic using Tandem’s Remote Server Call (RSC) facility. This enables early Windows NT operating systems to request live financial data from the sp/ARCHITECT host.
  • 1998: An automated, multi-process file transfer protocol is integrated natively into the bank database, leveraging Connect:Direct transport layers to securely transfer corporate SWIFT financial data files.

🚀 Era 3: The eFunds & Corporate Consolidation Era (2000–2006)

Deluxe Data’s technologies spun off into a new corporate entity called eFunds Corporation, altering the delivery model of the legacy software.

  • 2000: Deluxe Electronic Payment Systems officially merges with other divisions to form eFunds Corporation (EFD). The sp/ARCHITECT package becomes a core pillar of eFunds’ international banking portfolio.
  • 2002–2004: To modernise the transaction handling backbone, components of the sp/ARCHITECT platform are refactored. The system’s underlying communication routing is systematically aligned with CONNEX, a dominant market-leading Electronic Funds Transfer (EFT) processing engine.
  • 2005–2006: eFunds transitions the direct client-server software layers into highly secure corporate portals, providing the foundational logic for what would eventually be rebranded as the CONNEX Advantage banking solution.

🏢 Era 4: The FIS Integration and Legacy Modernisation Era (2007–Present)

The final stage of the product timeline represents its absorption into global banking infrastructure software, where its high-availability DNA remains active in institutional transaction environments.

  • 2007: Financial technology behemoth Fidelity National Information Services (FIS) acquires eFunds Corporation for approximately $1.8 billion. Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.
Fidelity National Information Services (FIS) Aegon House in Daresbury, Warrington 2007
Fidelity National Information Services (FIS) Aegon House, Warrington (in 2007)
  • 2010: FIS fully absorbs the remaining codebase, utilizing its core Tandem architecture algorithms to fortify transaction processing stability.
  • 2015–2020: The architectural concepts pioneered by sp/ARCHITECT-BANK continue to govern high-volume legacy systems. The logic stays preserved in COBOL85 code bases running on modern HPE Integrity NonStop (Intel Xeon-based) fault-tolerant environments.
  • 2020s–Present: Modern banking infrastructures gradually migrate from the classic database frameworks toward microservice configurations and open-banking APIs. However, the core system layout remains a primary point of historical reference for designing high-throughput, 24/7/365 fault-tolerant banking systems.

sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire

sp/ARCHITECT-BANK Code Evolution Timeline

The timeline below details how the code’s core design, language implementations, and application deployment strategies transformed by era and year.

1. The Monolithic & TAL Foundation Era (1980s – Early 1990s)

During this era, the application focus was strictly high-throughput, fault-tolerant electronic funds transfer (EFT) and point-of-sale (POS) switching systems natively built for Tandem Guardian environments.

  • Late 1980s: The core design of sp/ARCHITECT is established using TAL (Tandem Application Language). Applications are deployed as single-system monoliths. Code optimization focuses heavily on low-level bit manipulation and message structuring to survive CPU or inter-process failures without losing in-flight transactions.
  • 1991–1993: Structuring of modular execution libraries. Early iterations of the codebase segment transaction processing routes from core database logging routines. The introduction of Tandem’s newer NonStop SQL forces early integration layers to transition from standard unstructured unstructured file systems (Enscribe) to early relational tracking.

2. Distributed Client/Server & pTAL Migration Era (Mid 1990s – Early 2000s)

The architectural demands shifted from single-frame monoliths toward distributed banking systems, giving rise to “Distributed Monoliths” and client/server network structures.

  • 1995–1996: Hardware evolutions transition from the older CISC-based Tandem systems to RISC architectures (MIPS processors). sp/ARCHITECT undergoes a massive compilation shift to pTAL (portable TAL) to preserve legacy code performance across new instruction sets.
  • 1998–1999: Tandem’s acquisition by Compaq pushes the software suite to handle open standard protocols. The application code begins abstracting system calls to prepare for broader networking interfaces.
  • 2001–2003: Deluxe Data / eFunds eras. The code sees the introduction of C/C++ wrappers around the legacy pTAL components. Systems are decoupled into a clear 3-Tier architecture: front-end terminal networks, back-end pTAL transactional engines, and standardized clearing houses.

3. Open Systems, Modern Middleware, & Java Integration Era (Mid 2000s – 2010s)

Following HP’s acquisition of Compaq and subsequent software realignments, the sp/ARCHITECT codebase was re-engineered to prevent vendor lock-in and adopt modern enterprise standards.

  • 2005–2007: Java is introduced into the sp/ARCHITECT ecosystem. New application modules, specifically merchant portal interfaces and settlement reporting tools, are written entirely in Java and run via OSS (Open System Services) environments.
  • 2010–2012: FIS acquisition era integration. Legacy pTAL code blocks are systematically refactored or heavily wrapped in C++ using object-oriented principles to ensure long-term maintenance. The transaction routing engine is altered to support early SOA (Service-Oriented Architecture) paradigms via web-services hooks.
  • 2015–2018: Mainstream deployment of COB (Core Banking) standard formats within the application layer. The system moves away from old proprietary network messaging layouts to ISO 20022 compliance frameworks, utilizing dedicated conversion engines native to the sp/ARCHITECT stack.

4. Modern Cloud-Adjacent & Hybrid Infrastructure Era (2020s)

The current evolutionary footprint centers on maintaining the absolute sub-millisecond reliability of the core architecture while exposing capabilities to dynamic cloud endpoints.

  • 2021–2023: Modernization of the application payload. High-performance micro-frontends handle real-time fraud monitoring and data streaming using asynchronous event-driven pipelines (e.g., Kafka event consumers interfacing directly with the NonStop core runtime environments).
  • 2024–2026: Transition to containerized orchestration and cloud-adjacent infrastructure. The sp/ARCHITECT footprint utilizes x86-based virtualized NonStop systems (NSX), enabling legacy core modules (derived from the original TAL logic) to execute seamlessly on modern virtual environments alongside Linux-based multi-tenant applications.

Insider Technologies Limited (ITL), Company Overview and Timeline by Year

ITL is a specialized UK-based software house & service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions

Insider Technologies Limited is a specialized UK-based software house and service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions for business-critical, 24/7 mission-critical architectures. I worked at ITL in Salford Quays from 1995 through to 2013.

Mark Whitfield attending an EBUG conference (BASE24 User Group)
Attending an EBUG conference
(European BASE24 User Group)
Foreground, attending a British Isles TANDEM User Group (BITUG)
Foreground, attending a British Isles
TANDEM User Group (BITUG)
Insider Technologies Limited, ITL, website in 2009
Insider Technologies Limited
(website author in 2009)

Company Overview

🏢 Corporate Identity & Status

  • Legal Name: Insider Technologies Limited
  • Founded: 27 February 1989
  • Headquarters: Manchester, UK (Albert Street, Eccles)
  • Ownership: Operating as a private independent software company, recently integrated as part of PartnerOne.
  • Strategic Partnerships: Certified Microsoft Gold Partner for Application Development and long-standing Hewlett Packard Enterprise (HPE) partner.
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point

🌐 Core Domain & Industries Served

The company delivers real-time, event-driven diagnostic, tracking, and compliance middleware solutions across three main highly-regulated global verticals:

  • Banking & Financial Services: Monitoring real-time electronic payments, ATM/POS systems, and transaction workflows (e.g., BASE24, XPNET environments).
  • Government & Defence: Secure enterprise military messaging tracking and digital evidence handling.
  • Telecommunications: Tracking data traffic and critical infrastructure middleware.

🛠️ Core Technology Stack & Competencies

Insider Technologies specializes in niche high-availability operating environments—specifically HPE NonStop (historically Tandem Computers and HP NonStop) running Guardian and Open System Services (OSS) environments—alongside enterprise Windows, Linux, and Unix systems. Their expertise spans database transaction management, BASE24 XPNET monitoring, IBM WebSphere MQ tracking, and low-level development (SQL, TAL, TACL, COBOL85, C++, Pathway).

Insider Technologies, the Core products in 2003
Insider Technologies –
Core products in 2003

In-Depth Product & Political-Technical Timeline

This timeline breaks down how Insider Technologies evolved its software suite. It demonstrates how their technical development directly responded to shifting geopolitical landscapes—ranging from late-Cold War military messaging security to post-9/11 financial regulations and modern European cloud autonomy initiatives.

🔹 The Foundation & Legacy Tandem Era (1989–1999)

  • Political Context: The final years of the Cold War and the 1990s globalization boom demanded high-security, fault-tolerant mainframes for NATO-aligned military communications and early global banking clearing networks.
  • Technical Context: Tandem Computers dominated the un-interruptible 24/7 market. Software was required to monitor these platforms without causing processing overhead.
  • 1989
    • Company Incorporation: Insider Technologies is incorporated in the UK to engineer bespoke software for highly robust technical ecosystems.
  • 1990–1995
    • Reflex (Core Release): Release of Reflex, a foundational service management and real-time transaction diagnostic tool built specifically for the Tandem Guardian operating system.
  • 1996–1999
    • MultiBatch Software: Further Develop and Extend MultiBatch to orchestrate and safely automate complex batch processing on Tandem machines alongside the evolution into HP NonStop computing frameworks.
    • Y2K Compliance Focus: Technical adjustments were deployed across Reflex and MultiBatch to assure financial institutions that automated transaction logging would not fail during the millennium rollover.

🔸 The Multi-Platform & Financial Compliance Era (2000–2015)

  • Political Context: Following the September 11 attacks, global anti-money laundering (AML) and counter-terrorism financing (CTF) frameworks heavily expanded. Financial regulators demanded exact, audible end-to-end payment tracking.
  • Technical Context: Enterprises began migrating away from single-architecture mainframes toward heterogeneous IT environments, requiring tools that could jump across Windows, Unix, and Linux simultaneously.
  • 2002–2004
    • Sentra Development: Launch of Sentra, expanding the firm’s portfolio beyond HPE NonStop into cross-platform environment monitoring for Windows, Linux, and Unix systems.
    • Reflex 80:20 & Reflex ONE24: Advanced variations of the Reflex tracking system were built to cater to specialized real-time electronic payment flows like BASE24 with XPNET.
  • 2005–2010
    • RTLX Reactor (page 12) and Middleware Monitoring: The release of RTLX Reactor provided message tracking capabilities tailored for IBM WebSphere MQ, allowing institutions to trace various payment and other data through complex middleware chains.
RTLX Reactor, 2013 article - The Connection Journal
RTLX Reactor, 2013 article –
The Connection Journal
BASE24-eps extraction and RTLX
BASE24-eps extraction
and RTLX (in 2007)
  • 2011–2015
    • Corporate Structuring: The creation of Insider Technologies (Holdings) Limited reinforced corporate expansion as the company deepened its footprint in secure military messaging for government defense bodies.

🔹 The Cyber Autonomy & Sovereignty Era (2016–Present)

  • Political Context: Escalating nation-state cyber warfare, strict GDPR regulations, and the UK/EU push for technological sovereignty and domestic digital ecosystem resilience heightened the reliance on trusted, onshore technology suppliers.
  • Technical Context: High-threat environments demand zero-trust visualization, time-accurate logging across digital evidence files, and advanced protection against internal exfiltration vectors.
  • 2019
    • 30-Year Milestone & Modernization: The company celebrates its 30th year, accelerating development on modern mobile application extensions to permit real-time, remote secure alerts for operations teams.
  • 2022–2025
    • PartnerOne Integration: Insider Technologies aligns its operations under the PartnerOne portfolio, preserving its UK identity while supercharging its enterprise-scale data infrastructure solutions.
    • Corporate Integration combines Insider’s expertise with PartnerOne’s portfolio to deliver advanced analytics and secure messaging systems to banking, defence, and telecommunications markets.
    • Defense and Public Safety Porting: Technical deployment of specialized capabilities covering digital evidence security, timekeeping tracking, and legacy virtualization modules aimed explicitly at helping the UK Government maintain its historical tech stacks safely.
RTLX Reactor (in 2012) for tracking BASE24-eps and BASE24 XPNET transactions
RTLX Reactor (in 2012) for tracking
BASE24-eps & BASE24 XPNET transactions

Insider Technologies Limited (ITL), Company Overview and Timeline by Year

The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;

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

Mark Whitfield – Education and Professional Training Timeline Summary

Mark Whitfield is a Greater Manchester-based Senior IT Project and Engagement Manager.

With over 30 years in the IT and software development industry, he has continuously upskilled in project delivery, Agile methodologies, cloud platforms, and cyber security.

Mark Whitfield - Education and Professional Training Timeline Summary

Phase 1: Foundational Education

  • 1985 – 1988: Leigh College, UK
    • Focus: Computer Science and Biology (‘A’ Levels)
  • 1988 – 1990: University of Greater Manchester (formerly Bolton Institute of Higher Education, BIHE)
    • Focus: Higher National Diploma (HND) in Computer Studies (Graduated with Distinction; First overall in the year)
    • Key Modules: System Analysis, Programming Methodology, Database Architecture, and Business Information Systems

Phase 2: Project Management & Professional Training

  • 2000 – 2006: Industry Integration & Early Methodologies
    • Focus: Service-Oriented Architecture (SOA), Agile, Sales, and early project management
    • Courses/Certifications: Sales and Marketing (In-house Outsource, 2001), Web Services and SOA (Insider Technologies, 2005), PRINCE2 Foundation (2006), Designing Good Marketing Literature (SkillPath Seminars, 2006)
  • 2009: Digital & Communications
    • Focus: Digital marketing and content
    • Courses: Writing for the Web, and Website Promotion and Visibility by Design (iTrain Education)
  • 2011: Structured Frameworks
    • Focus: Formal project frameworks and delivery methodologies
    • Courses/Certifications: PRINCE2 Foundation & Practitioner (ILX Group), Agile Scrum (RADTAC)
  • 2012: Operational Management
    • Focus: Service management best practices
    • Courses/Certifications: ITIL Foundation

Phase 3: Advanced Engagement & Enterprise Training

  • 2017 – 2019: Capgemini Engagement & Compliance
    • Focus: High-level engagement management and corporate governance
    • Courses/Certifications: Advanced Engagement Management Certification (Level 2), Group Anti-Corruption, and Intellectual Property Rights (IPR) Training
  • 2022: Cloud Modernization
    • Focus: Enterprise cloud computing fundamentals
    • Courses/Certifications: AZ-900 Microsoft Certified Azure Fundamentals

For more granular details on his certifications and career history, you can check Mark Whitfield Professional Training.

Mark Whitfield PM – Website & Blog focus areas

The blog posts by Mark Whitfield, a Senior IT Project and Engagement Manager, primarily focus on practical project management (PM) frameworks, methodology implementation, and digital delivery execution.

Mark Whitfield PM - Website and Blog focus areas

Hosted on his platform, PROject Templates, the blog acts as an extension of his 30+ year career transitioning from mainframe engineering to leading large-scale Agile and Waterfall digital transformations.

Blog Overview and Key Topics

The core purpose of the blog is to guide project professionals through real-world deployment challenges while showcasing an ecosystem of over 200 editable Microsoft Office templates.

The main content focus areas include:

  • Framework Implementation: In-depth overviews on aligning project lifecycles with PRINCE2 (7th Edition), Agile Scrum, and Kanban methodologies.
  • Detailed Project Planning: Actionable steps for setting up Software Development Life Cycles (SDLC), defining dependencies, establishing milestones, and handling project baselines.
  • Operational Checklists: Daily, highly practical guides tailored for specific team roles, such as his “Daily Checklist for Scrum Masters”.
  • Risk and Governance Control: Best practices on organizing and managing RAIDs logs (Risks, Actions, Issues, Dependencies), change requests, and corporate project governance.
  • High-Level Reporting: Frameworks for structural communication with stakeholders, utilizing Plan on a Page (POaP) examples, dashboard designs, and financial budget tracking templates.
  • Digital & Cloud Delivery Lessons: Real-world insights drawn from his corporate and public sector experiences, covering topics like middleware architecture deployments and hybrid cloud application refactoring.

European Countries & Student Loan Requirements

In Europe, “free” higher education almost always refers to zero tuition fees at public universities, though you will still need to pay for living expenses (rent, food, books). No European country requires student loans; rather, loans are an optional choice to fund living costs.

Use the regional breakdown below to see which countries offer zero tuition and which generally require you to pay.

Countries with Free (or Almost Free) Tuition

Countries with Free (or Almost Free) Tuition
Countries with Free (or Almost Free) Tuition

These countries charge no tuition fees (or very minimal administrative fees) for eligible students:

  • Germany: Public universities are completely tuition-free for both domestic and international students, including those from outside the EU. You only pay a small semester fee (approx. €150-€350).
  • Norway: Free of charge for all students, regardless of nationality.
  • Austria: Free for EU/EEA students. For non-EU students, the fee is generally a very low €727 per semester.
  • France: Public university tuition is heavily subsidized and extremely low (approx. €170 to €2,700 per year, depending on the degree).
  • Iceland: Free tuition at public universities, though a registration fee of roughly €400-€600 is required.
  • Czech Republic: Public universities are free if you study a program taught in the Czech language. English programs require tuition.
  • Greece: Free tuition for EU/EEA nationals; non-EU students pay very low fees (around €1,500/year).
  • Poland: Tuition is free for Polish citizens and EU/EEA students.

Countries with Free Tuition for EU/EEA Students Only

These countries offer free degrees if you are a European citizen, but charge international (non-EU/EEA) students:

  • Denmark: Free for EU/EEA students; international students pay up to €16,000 per year.
  • Sweden: Free for EU/EEA students; international students pay full tuition.
  • Finland: Free for EU/EEA students. Non-EU students pay tuition for English-taught programs.
  • Slovenia: Free for full-time undergraduate students from the EU.

Countries That Generally Require Tuition (and Potential Loans)

In these countries, you will pay tuition fees ranging from a few hundred to several thousand Euros per year, making student loans or personal savings more necessary:

  • United Kingdom: In England and Wales, tuition fees can cost up to £9,250 a year for domestic students, and higher for international students. Students heavily utilize the government’s Student Loans Company to cover both fees and maintenance.
  • The Netherlands: Yearly tuition fees for EU students are around €2,500, with higher fees for international students. Dutch citizens and eligible EU students can take out loans through DUO.
  • Italy & Spain: Both charge moderate tuition fees for public universities based on family income or the specific region, making it much more affordable than the UK but rarely entirely free without scholarships.