Category: HP NonStop

Mark Whitfield, Senior Project Manager, Career Summary

Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager and Engagement Manager with over three decades of experience in software development lifecycle (SDLC) delivery.

Mark Whitfield, High-Level Career Summary from 1990 thru 2026

Mark Whitfield, High-Level Career
Summary from 1990 thru 2026

Over his career, he has transitioned from deep technical engineering on legacy systems (HPE NonStop formerly Tandem Computers) to enterprise-scale digital transformation, cloud migrations, and API-led integrations. He is also the author of a comprehensive online toolkit for project delivery frameworks.

Click the ‘Company Worked‘ links below for more detail as required.

Project Management Career Breakdown:

1. Early Engineering & Technical Analysis Era (1990–1995)

  • Company Worked: The Software Partnership / Deluxe Data International
  • Geographical Location: Runcorn (head office) / on-site at both Knutsford / Poole, UK (for Barclays delivery)
  • Clients include: Barclays Bank (BBM II), RaboBank, Bank of Scotland, Girofon, TSB
  • Main Focus Items: Core software design, coding, and back-end integration for electronic desktop banking.
  • Technology Areas: Electronic banking software systems. Periphonics interactive (touch-tone phone) voice software.
  • Software Languages/ Products: sp/ARCHITECT-BANK, SQL, COBOL, SCOBOL, PATHWAY, PATHMAKER, ENSCRIBE, INSPECT, EMS, Tandem Mainframes (now HPE NonStop)
  • Methodology: Early iterative development & structured Waterfall lifecycles.

2. Technical Consultancy & Product Management (1995–2013)

  • Company Worked: Insider Technologies Limited (ITL)
  • Geographical Location: Salford Quays, UK (office); London, UK; Client sites across Europe/ Middle East
  • Clients include: Global Payments, Standard Chartered, Girofon, Rabobank, CRESTCo (Euroclear), Alrajhi Bank, LloydsTSB, HSBC, Santander, Bank of Ireland, Bank of Valletta (Malta) and both Commercial and Piraeus Bank (Greece)
  • Main Focus Items: Infrastructure consulting, volume testing, system management & monitoring, and Service Level Agreement (SLA) monitoring for critical path payment applications. Attending related conferences, EBUG, ITUG, BITUG, SATUG
  • Technology Areas: HPE NonStop monitoring, ATM/POS system & transaction monitoring and stock settlement.
  • Software Languages/ Products: Reflex, RTLX, Sentra, TIVOLI, COMMAND/POST, XPERT24, XPNET, HPE NonStop, HP OpenView Operations, BASE24 Classic, BASE24-eps, C, C++, SQL, SCOBOL, COBOL, TAL, PATHWAY, ENSCRIBE, EMS, MS Project
  • Methodology: Structured Waterfall, Agile Scrum & Custom Product Engineering Lifecycles.
  • Also: Designer and author of a new company website using an Open Content Management framework identified as part of a Research phase.

3. Professional Services Banking Delivery (2013–2014)

  • Company Worked: Wincor Nixdorf
  • Geographical Location: Woking / Bracknell / UK wide
  • Client: Lloyds Banking Group
  • Main Focus Items: Modernising legacy ATM software and directing hardware/software transitions. Implementing ProClassic/Enterprise and PC/E SmartClient (Win 7) to replace the existing ProCash/NDC (Win XP) Stacks on a variety of multivendor devices.
  • Technology Areas: Multi-vendor hardware & software integration for ATMs.
  • Software Languages/ Products: BASE24 Classic, ProClassic Enterprise (PC/E), Oracle, AIX Platform, Windows 7
  • Methodology: Strict PRINCE2 Waterfall and Agile transition methodologies.
  • Also: Wincor ‘Above and Beyond’ award for Customer Satisfaction, Commitment to Excellence and Commitment to One Wincor

4. Digital Sportsbook Transformation (2014–2016)

  • Company Worked: Betfred
  • Geographical Location: Wigan / Greater Manchester, UK
  • Client: Betfred Online and Mobile
  • Supplier Management: for external software suppliers like Degree53, Playtech, Onionsack, Intelligent Payments (Myriad), Inspired, iovation, StreamUK, Finsoft, Ineda, OtherLevels, Appsflyer, Income Access, Activewin, Virgo, Virtue Fusion, In Game Media, Satellite Information Services (SIS) and IGT
  • Main Focus Items: Taking new sports and virtual gaming components live, integrating payment gateways, managing app release cycles, and handling regulatory compliance.
  • Technology Areas: Fraud detection, consumer mobile/desktop betting platforms.
  • Software Languages/ Products: Java, iOS, Android, MS SQL, ASP.NET
  • Methodology: Agile SCRUM.

5. Enterprise Cloud & Integration Delivery (2016–Present)

  • Company Worked: Capgemini UK Consultancy
  • Geographical Location: Manchester / London and UK wide
  • Clients include: Jaguar Land Rover (JLR), Royal Mail Group (RMG), NATS, UK Gov, Heathrow, MuleSoft (augmented)
  • Main Focus Items: Managing hybrid cloud migrations, re-hosting/ refactoring applications, API-led connectivity, and complex manufacturing supply chain data pipelines.
  • Technology Areas: Hybrid cloud infrastructure and system integration.
  • Software Languages/Products: MuleSoft Anypoint Platform, Azure, AWS, Power Platform, Enablon
  • Methodology: Hybrid Agile and PRINCE2.
  • Also: C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK.

In addition to his consultancy work, Mark Whitfield actively publishes his extensive collection of Project Management Templates, which are actively utilized across the industry for RAID Logs, Agile Burndown Charts, and Plan on a Page (POaP) blueprints.

Insider Technologies Limited, Timeline of HPE NonStop Activity

Mark Whitfield spent 18 years (August 1995 – September 2013) at Insider Technologies Limited (ITL), a Manchester-based software house specialising in high-availability tracking, service management, and transaction monitoring. Entering as a Senior Programmer, he climbed through the ranks to become an Operations Products Manager and, ultimately, the Project Manager for Strategic Technical Initiatives.

Insider Technologies Limited, Spinnaker Court, Chandlers Point, Salford Quays, Broadway. M50 2YR
Insider Technologies Limited,
Spinnaker Court, Chandlers Point,
Salford Quays, Broadway. M50 2YR

His core technical contribution revolved around developing and managing platform-health diagnostic modules, automated event filtering, and multi-currency transaction log trackers.

He focused heavily on the HPE NonStop (Tandem) kernel, integrating these mainframes with Windows, Unix, and Linux open systems. His work protected critical banking infrastructure, such as transaction loops feeding into ACI BASE24 ATM/POS switches and major national payment clearings.

Detailed Timeline Breakdown

🔹 The Foundational Tandem Era (1995–1999)

This period focused on building out bespoke low-level mainframe diagnostic scripts, real-time logging, and bracing critical infrastructure for the millennium bug.

  • 1995: Joined Insider Technologies Limited at Salford Quays after departing Deluxe Data. He began programming SCOBOL green screens and engineering PATHWAY servers to query raw Guardian operating system procedures.
  • 1996: Core developer for the flagship Reflex monitoring suite (Reflex 80:20). He co-authored the Console module for HPE NonStop Event Management Service (EMS) viewing, alongside tracking blocks for system components like CPU, Disk, and Processes.
  • 1997: Transitioned into an infrastructure consulting capacity, designing code routines to test physical hardware throughput.
  • 1998: Formally appointed as the ITL Operations Products Manager. He orchestrated high-performance benchmarking tests on newly deployed Tandem S7000 processing hardware nodes for Euroclear (formerly CRESTCo), validating infrastructure that handled 88% of UK equities.
  • 1999: Directed critical, deep-level automated Y2K code auditing. This guaranteed that real-time tracking loops and MultiBatch scheduling automation would accurately handle the date rollover for clearing partners like the Bank of England and Deutsche Bank.

🔸 The Operations & Middleware Integration Era (2000–2005)

This era bridged the gap between rigid standalone mainframes and modern open-system dashboards, creating cross-platform monitoring frameworks.

  • 2000: Spearheaded deep-layer integration projects connecting legacy frameworks to distributed enterprise collectors like TIVOLI, COMMAND/POST, and third-party file monitors.
  • 2001: Supervised 24×7 enterprise support teams handling cryptographic security frameworks for Thales e-SECURITY products, overseeing the SafeSign Authentication and Management Server lines on Windows/Unix.
  • 2002: Led technical rollouts for ITL’s interactive Systems Training Platform, deploying patented system-cloning configurations to let institutional clients practice outage responses safely.
  • 2003: Drove cross-platform middleware compatibility protocols, building hooks between the NonStop kernel and WebSphere MQ (MQSeries) message streams to trap transactional anomalies in real-time.
  • 2004: Advanced to Project Manager – Strategic Technical Initiatives, implementing PRINCE2 governance for new product R&D pipelines.
  • 2005: Began standardising the technical architecture of Reflex ONE24, transitioning the vintage monitoring code toward centralized electronic web consoles.

🔹 The Strategic Initiatives & Product Management Era (2006–2013)

Whitfield shifted into pure-play product management, expanding corporate web assets and publishing technical documentation before navigating the company through an MBO.

  • 2006: Pioneered custom transaction parsing frameworks for payment switches, resulting in the foundational engine layout of Sentra and the Real-Time Log Extraction (RTLX) engine.
  • 2007: Acted as the primary corporate website architect and author, modernising Insider’s public presence by building out and managing content deployments on DotNetNuke (DNN).
  • 2008: Managed implementation pipelines for XPERT24, a highly specialized utility engineered specifically for performance tracking across complex BASE24 XPNET banking environments.
  • 2009: Directed extensive migration initiatives, shifting clients from obsolete platform tracking matrices onto unified monitoring frameworks.
  • 2010: Guided software engineers through logic modifications to intercept multi-currency retail POS and ATM interchange drops down to the millisecond.
  • 2011: Coordinated agile deployment sprints for financial institutions to meet strict compliance laws surrounding automated data storage and long-term file retention.
  • 2012: Provided the project governance behind the scenes during Insider Technologies’ internal structural transitions, supporting a £3m Management Buyout (MBO).
  • 2013: Authored a major technical summary published globally in the recognized HP NonStop industry journal, The Connection, defining payment software lifecycles. Concluded his 18-year run at ITL in September to join Wincor Nixdorf.

(Note: The product lines Whitfield built and governed were later acquired by ETI-NET in 2015, where his original RTLX utility was rebranded as C-Deep for Transaction Monitoring.)

ETI-NET C-Deep real-time transaction and payment monitoring product timeline

C-Deep (formerly known as RTLX developed by Insider Technologies Limited) is an enterprise-grade, real-time transaction and payment monitoring software product. It is currently owned, maintained, and distributed globally by ETI-NET.

Product Overview & Key Features

The primary objective of C-Deep for HPE NonStop is to ensure fault tolerance, detect transactional vulnerabilities, and prevent outages within major financial ecosystems.

  • Target Environment: It is deployed alongside primary mission-critical payment engines, primarily operating as a high-performance add-on to ACI Worldwide’s BASE24™ solution or as a standalone tracker on HPE NonStop systems.
  • Architecture: The software utilizes lightweight extraction clients on the NonStop kernel to read Transaction Log Files (TLF) and POS Transaction Log Files (PTLF). It offloads data parsing to a C-Deep collector on Windows Server, keeping the primary switch’s CPU overhead at zero.
  • Data Retrieval: It stores and indexes historical transaction fields into annual databases for 10+ years, making it fully searchable to meet strict data regulatory compliance laws.
  • Granular Querying: Operators can isolate variables down to Bank Identification Numbers (BIN), detecting interchange timeouts, clearing delays, or switch drops down to the millisecond.

Detailed Timeline Breakdown by Era and Year

The technical evolution of this platform reflects the wider political and economic changes in global banking, transitioning from early bespoke mainframe logs to modern, automated cyber-resiliency environments.

🔹 The Foundational & Legacy Tandem Era (1989–2000)

This era centered around high-security, fault-tolerant mainframes built for NATO-aligned military communications and early banking networks following the end of the Cold War.

  • 1989: Insider Technologies Limited is incorporated in the UK to manufacture specialized monitoring code for highly robust computer systems.
  • 1990–1995: The vendor releases its foundational “Reflex” software suite for the Tandem Guardian operating system, offering real-time transaction diagnostics without interrupting physical processing operations.
  • 1996–1999: The platform adds “MultiBatch” automation to orchestrate complex batch settlements. Engineering pivots toward critical Y2K code auditing to prove that automatic logging routines would survive the year 2000 date rollover.

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

This era mark’s the product’s rise to prominence as a core tool for transaction transparency across global clearings houses, reacting to rapid financial sector deregulation.

  • 2001–2003: The architecture scales up from simple hardware tracking into dedicated operational security. The vendor expands the footprint into financial clearings, tracking transaction security for system-critical clearers like the Bank of England.
  • 2004–2007: The developer releases RTLX (Real-Time Transaction Logging/Reactor), standardizing visibility from the point-of-sale terminal tap to the back-end ledger settlement. It adds cross-compatibility for Windows, Unix, and Linux systems alongside standard Tandem NSK systems.
  • 2008–2012: Amid market volatility following the 2008 financial crash, transaction tracking rules tighten. RTLX adds specialized configuration engines to map high-volume dates (e.g., Black Friday) to proactively flag message queues and clear bottlenecks before causing outages.

🔹 The Acquisition & Integration Era (2015–Present)

This era sees consolidation in the HPE NonStop market, transforming the legacy product into a fully modern cyber-resilient and automated tracking ecosystem.

  • 2015–2021: Real-time transaction frameworks become critical for compliance. To expand global distribution channels, ETI-NET formalizes an agreement to acquire and absorb Insider Technologies’ core system software catalog.
  • 2022–2023: ETI-NET rebrands the classic software stack to streamline its message. The system monitoring side (Reflex) becomes Sentinel, while the specialized payment switch transaction monitor (RTLX) is official re-launched as C-Deep for Transaction Monitoring.
  • 2024: ETI-NET pushes C-Deep through HPE Pointnext Services, making it directly purchasable within standard Hewlett Packard Enterprise customer channels. Integrations are updated to match the NIST 2.0 Cybersecurity Framework.
  • 2025–2026: Modern upgrades focus heavily on end-to-end data auditing, automated email/SMS alerting systems, and specialized dashboard analytics tailored for complex, multi-currency transaction paths.

ETI-NET C-Deep real-time transaction and payment monitoring product timeline

Mark Whitfield HPE NonStop Tandem Experience over three decades

Mark Whitfield is a Senior IT Project Manager with over three decades of experience, heavily rooted in HPE NonStop (formerly Tandem).

His career has transitioned from hands-on NonStop development and product management into large enterprise cloud and digital transformation projects.

Mark Whitfield’s IT project management and software engineering career spans over three decades
Mark Whitfield – Senior IT
Project Manager – SC cleared

His NonStop specific projects and career trajectory can be broken down (at a high-level) by era, location, and focus as follows:

1990–1995: Early Programming

  • Location: Barclays, Poole, Dorset, UK
  • Focus: Electronic banking programming and development on Tandem Mainframe Computers.
  • Projects: Wrote, developed, and maintained software like sp/ARCHITECT-BANK and associated billing software (in Poole, 1993). This involved building early electronic banking systems for desktops long before internet banking was prevalent.
1993, Barclays, Poole, Dorset, UK
1993, Barclays, Poole, Dorset, UK

1995–2013: Senior Development & Product Management

  • Location: Insider Technologies, Salford Quays, Manchester, UK
  • Focus: NonStop product management, software design, and real-time event monitoring.
  • Projects: Product managed software lifecycles for four monitoring products (two NonStop based). This included creating health and diagnostic tools (RTLX, Reflex 80:20, Reflex ONE24, XPERT24) for mission-critical NonStop environments. He also deployed volume testing on early HP NonStop S7000 nodes for CRESTCo in London in 1997.
Spinnaker Court, Chandlers Point, Insider Technologies, Salford Quays, Manchester, UK
Insider Technologies, Salford Quays, Manchester, UK

2013–2014: Legacy Migration & Consulting

  • Location: Wincor Nixdorf & ATM/POS Financial Services, UK
  • Focus: Modernization and migration of legacy systems.
  • Projects: Managed a £5M+ replacement of legacy HP NonStop software systems at a large UK retail bank, migrating functionalities to AIX-based J2EE and Oracle architectures.
Diebold Nixdorf Ltd, Cain Rd, Binfield, Bracknell, RG12 1WP
Diebold Nixdorf Ltd, Cain Rd,
Binfield, Bracknell, RG12 1WP

2016–Present: Cloud Transformation & Digital Delivery

  • Location: Capgemini UK, Trafford Quays / UK-Wide
  • Focus: Delivery of enterprise-scale middleware, digital transformation, and cloud.
  • Projects: Acts as an Engagement Manager and SC-Cleared Project Manager. Focus includes Agile software delivery for Air Traffic organisations (e.g., iOS applications for military and public-facing airspace tracking) and rolling out middleware solutions.
Capgemini UK, Floor 7, Venus Building, Trafford Quays, Manchester. M41 7HA
Capgemini UK, Floor 7,
Venus Building, Trafford Quays
C&CA UK's Communications & Engagement Award Winner 2022 - Cloud & Custom Applications - Capgemini UK
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK

For more career detail, click here.

ACI BASE24 core components on HPE NonStop mainframe platform

ACI BASE24 is a market-leading electronic funds transfer (EFT) software application developed by ACI Worldwide. It serves as the transaction processing backbone for global banking.

Running natively on the fault-tolerant HPE NonStop platform (formerly Tandem Computers), it utilizes a modular architecture to acquire, authenticate, route, and authorize financial transactions.

BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

The application modules of ACI BASE24 (spanning Classic and modern BASE24-eps configurations) are categorized in complete detail below:

💳 Channel Acquisition Modules

These front-end modules connect directly to consumer-facing self-service devices and touchpoints to ingest financial messages.

  • BASE24-atm: Manages ATM device configurations, handles cash dispenser commands, controls screen displays, and processes terminal commands.
  • BASE24-pos: Facilitates electronic data interchange with Point of Sale (POS) merchant terminals, accepting debit, credit, and smart card transactions.
  • Stored Value Module (SVM): A localized sub-component within channel management dedicated to the online issuance, balance check, and validation of stored-value gift cards.

🔄 Routing, Switching, & Interfacing Modules

These modules orchestrate the delivery of messages from endpoints to localized authorization hosts or global networks.

  • XPNET: The foundational communication middleware module on HPE NonStop that handles network connectivity, balancing transaction routing across regional hosts.
  • BIC ISO Interface: Implements standard ISO 8583 payment messaging protocols to communicate directly with major international networks (such as Mastercard or Visa).
  • ACI Commerce Gateway: Operates as a secure payment gateway firewall, linking internal HPE NonStop processing routines with public internet channels.

🔐 Security & Authentication Modules

Data integrity modules protect transactions and enforce industry-standard security.

🏦 Business Logic & Authorization Engines

These back-end engines decide whether a transaction flight should be accepted, declined, or deferred.

  • Enhanced Authorization Module: Runs customized business logic scripting to evaluate cardholder limits, fraud signals, and stand-in authorization processing.
  • Positive Balance File (PBF) Interface: Interfaces with real-time local file structures to check account limits when backend core banking host systems are offline.

📊 Back-Office & Data Management Modules

These modules ensure post-transaction data is accounted for, settled, and audited.

  • Interchange Log File (ILF) / Transaction Log File (TLF for ATM, PTLF for POS): Core architectural data constructs that maintain comprehensive records of all ongoing financial messages for balancing and error recovery.
  • BASE24-infobase: Provides centralized tools for operational reporting, financial data clearing, settlement processing, and accounting audits.

🛠️ HPE NonStop System Integration Architecture

BASE24 is highly reliable because it integrates with native HPE NonStop mainframe utilities:

  • PATHWAY (PATHCOM): Acts as the transaction processing middleware to dynamically load-balance BASE24 server processes across multiple CPUs.
  • Enscribe & NonStop SQL/MX: Serves as the native flat-file or relational database layer optimized for low-latency, high-concurrency write operations.
  • HPE Shadowbase / AutoTMF: Interacts with the Transaction Monitoring Facility (TMF) to enable active/active dual-site replication, providing instant failover for near-zero transaction downtime.

ACI BASE24 core components on HPE NonStop mainframe platform

2. BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

Mark Whitfield’s project involvement with ACI Worldwide’s BASE24 / BASE24-eps and XPNET communication middleware is rooted deeply in his tenure at Insider Technologies Limited (ITL) and subsequent senior project management roles. His work primarily spans real-time performance monitoring, transactional tracking, and infrastructure management across HPE NonStop (Tandem) platforms.

His involvement across specific initiatives and client deployments is categorised below:

Product Development & R&D Projects

  • BASE24 XPNET Monitoring in Reflex ONE24
    • Role: R&D Lead and Software Developer.
    • Involvement: Researched and developed specialised software utilities to automatically detect and extract architectural information from XPNET components. He leveraged XPNET EMS (Event Management Service) events and user requests to facilitate real-time monitoring. These components were mapped into graphical drill-down object trees inside the Reflex Status Monitor application.
  • XPERT24 (Performance Monitoring & Tracking)
    • Role: R&D Lead, Technical Contributor, and Project Manager.
    • Involvement: Managed the lifecycle of this NSK-based monitoring tool, which tracks XPNET performance counters including states, traffic rates, and queues across lines, stations, nodes, and processes. The project also involved building mechanisms to track transaction approval and denial metrics over ATM and POS networks.

Client Deployment & Customisation Projects

  • HSBC Transaction Monitoring Project
    • Role: Technical Lead / Solution Designer.
    • Involvement: Designed and executed the implementation of ITL’s RTLX Reactor product on HP NonStop. The project required mapping monitoring solutions into HSBC’s heavily customised payment ecosystem to track ATM and POS transactions governed by BASE24.
  • Off-shore Retail Banking Transaction Tracking (Riyadh, Saudi Arabia)
    • Role: IT Project Manager (2013).
    • Involvement: Managed the delivery of a massive log-parsing project utilizing the BASE24 Classic payment framework. The project safely extracted, relayed, and optimized the parsing of multiple Terabytes of historical ATM and POS transaction logs archived on tapes, moving them into a modern reporting system.
  • Global Payments / Standard Chartered Integration Project
    • Role: Project Manager / Technical Consultant (2011–2013).
    • Involvement: Integrated real-time BASE24 transaction tracking and XPNET capabilities directly into external corporate enterprise frameworks, specifically IBM Tivoli and XPERT24.
  • Lloyds Banking Group (LBG) Estate Transformation
    • Role: Senior Project Manager.
    • Involvement: Led a massive migration strategy that decoupled ATM driving responsibilities away from BASE24 Classic running on HP NonStop platforms, transferring them to Wincor’s ProClassic Enterprise (PC/E) environment.

Mark Whitfield 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

ACI BASE24 core components on HPE NonStop mainframe platform

Mark Whitfield Career Timeline by era and project

Mark Whitfield’s IT project management and software engineering career spans over three decades, progressing from early electronic banking programming on Tandem Mainframes (now known as HPE NonStop) to senior delivery of enterprise-scale middleware, cloud, and digital transformation initiatives.

Mark Whitfield’s IT project management and software engineering career spans over three decades
Mark Whitfield – Senior IT
Project Manager – SC cleared

The high-level chronological timeline (with links) of his professional eras and key project history is broken down below.

💻 1990–1995: Early Programming & Lead Analysis Era

During this foundational era, Whitfield operated as a Programmer and Lead Analyst specializing in core electronic banking software frameworks.

  • The Software Partnership / Deluxe Data (1990–1995): Developed and enhanced the sp/ARCHITECT-BANK platform. His technical responsibilities focused heavily on coding within Tandem Mainframe environments (now HPE NonStop) using C, C++, TAL, COBOL, and PATHWAY architectures.
Deluxe Data International Operations, Wingate House, Northway
Deluxe Data International Operations,
Wingate House, Northway, Runcorn
  • Barclays On-Site Delivery (Early 1990s): Deployed on-site at the Barclays facility in Knutsford, Cheshire. He was responsible for core code development and system architecture design on the Barclays Business Master II (BBM II) electronic banking initiative and subsequent billing modules developed in Poole, Dorset.
Barclays, Wimborne Road, Poole, Dorset
Barclays, Wimborne Road,
Poole, Dorset

🛠️ 1995–2013: Senior Development & Strategic Project Management Era

Transitioning to Insider Technologies Limited at Salford Quays, Manchester, Whitfield progressed into high-level technical project delivery and strategic product management.

Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
  • Reflex Monitoring Suite R&D (1995–1996): Appointed as a core developer to design platform health and diagnostic plug-in modules for the flagship Reflex 80:20 tracking console.
  • CRESTCo Infrastructure Integration (1997–1998): Acted as a technical infrastructure consultant for CRESTCo (now Euroclear). Managed hardware benchmark coding and testing for newly deployed Tandem S7000 processing nodes.
CRESTCo in 1997 on St. Katherine’s Dock near Tower Hill tube station
CRESTCo in 1997 on St. Katherine’s Dock
near Tower Hill tube station
first HP OpenView Operations (OVO) Smart Plug-In built for NonStop mainframe environments
First HP OpenView Operations Smart Plug-In
for HPE NonStop environments
  • ATM Log Extraction Deployments (2004–2007): Led technical delivery teams implementing automated transaction log extraction layers (RTLX and Sentra) to audit ATM networks for major retail financial brands like Alliance & Leicester (now Santander) and HSBC.
ATM Log Extraction Deployments (2004–2007) - RTLX Reactor
ATM Log Extraction Deployments
(2004–2007) – RTLX Reactor
cross-border ATM and Point-of-Sale (POS) environment monitoring expansion
Cross-border ATM and Point-of-Sale (POS) environment monitoring expansion
  • Enterprise Transaction Monitoring (2011–2013): Functioned as Project Lead to bridge retail banking transaction networks with corporate governance architectures. Integrated critical pathways for Standard Chartered and Global Payments into TIVOLI and XPERT24 using ACI’s XPNET infrastructure.
RTLX Reactor, 2013 article - The Connection Journal
RTLX Reactor, 2013 article –
The Connection Journal

🏦 2013–2014: Professional Services Banking Delivery Era

Whitfield moved into consultant-driven professional services, directly aligning tech components with client business roadmaps.

Diebold Nixdorf Ltd, Berkshire, One The Blvd, Cain Rd, Binfield, Bracknell, RG12 1WP
Diebold Nixdorf Ltd, Cain Rd,
Binfield, Bracknell, RG12 1WP
  • Wincor Nixdorf Banking Division (2013–2014): Retained as Project Manager for Professional Services. He directed a massive hardware and software transition stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme whilst also providing a qualified management link with Wincor Nixdorf, Paderborn (Germany) for subject matter expertise, as part of the transition.

🎮 2014–2016: Digital Infrastructure & Enterprise Betting Era

Whitfield shifted his delivery domain focus from banking mainframes into real-time high-transaction digital platforms.

☁️ 2016–Present: Cloud Integration, Middleware, & Public Sector Era

In this current era, Whitfield acts as a senior, SC-cleared Senior IT Project Manager specializing in hybrid cloud migrations and API-led integration.

Capgemini UK, Floor 7, Venus Building, Trafford Quays, Manchester. M41 7HA
Capgemini UK, Floor 7,
Venus Building, Trafford Quays
  • Capgemini UK Consultancy (2016–Present): Leading massive corporate and public sector agile/waterfall delivery initiatives. His technical program management footprint expands across a vast roster of tier-one enterprise environments:
    • MuleSoft Ecosystem Deployments: Directing system integration projects utilising the Salesforce MuleSoft suite, spanning API lifecycle design, Anypoint Code Builder configurations, and hyper-automation flows.
    • Multi-Sector Enterprise Clients: Orchestrating cloud migrations, middleware application refactoring, and data pipelines for Jaguar Land Rover (JLR), Heathrow Airport, Royal Mail Group (RMG), NATS (National Air Traffic Services), Welsh Water, Rabobank, Barclays, and UK Export Finance (UKEF).
C&CA UK's Communications & Engagement Award Winner 2022 - Cloud & Custom Applications - Capgemini UK
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK

Mark Whitfield Career Timeline by era and project

SC Cleared Senior IT Project Manager Mark Whitfield
Senior IT Project Manager,
Mark Whitfield

Professional Training

Certificates

Recommendations

Education Summary

Graduation

Overview of HP OpenView Operations (OVO) and Timeline

Overview of HP OpenView Operations (OVO)

HP OpenView Operations (OVO) is a foundational enterprise systems management (ESM) platform designed to centrally monitor and manage infrastructure, multi-vendor operating systems, and enterprise applications across distributed IT environments.

The system operates on an Agent-Server Architecture. Core components include:

  • Management Server: Central hub that aggregates system logs, processes alerts, correlates events, and triggers automated remediation scripts.
  • Smart Plug-ins (SPIs): Specialized modular add-ons that inject domain-specific monitoring logic for applications like Oracle databases, Microsoft Active Directory, or SAP.
  • Intelligent Agents: Lightweight background processes deployed on managed nodes to collect log events, metrics, and state data, formatting them into structured OVO messages.
HP OVO screenshot in 2002, HPE NonStop (previously Tandem) Monitoring
1. HP OVO screenshot in 2002
2. HP OVO screenshot in 2002, HPE NonStop (previously Tandem) Monitoring
2. HP OVO screenshot in 2002

See bottom of this post for HPE NonStop (previously Tandem) monitoring in OpenText Operations Bridge Manager. I overlooked an integration with HP OpenView Operations for a HPE NonStop product in 2002, called Reflex 80:20.

Detailed Timeline Breakdown by Era and Year

🌅 Era 1: Origins and The Foundation (Late 1980s – 1994)

This era established HP’s footprints in IT infrastructure management, pivoting from pure SNMP network map discovery toward server telemetry.

  • Late 1980s: HP releases Operations Center (OpC) as an add-on application for its core Network Node Manager (NNM) platform. It replaces slow SNMP polling with Remote Procedure Calls (RPC) to gather host logs.
  • 1990–1993: HP scales OpC into a robust engine capable of executing basic automation scripts on remote UNIX boxes when specific thresholds break.

🚀 Era 2: The “ITO” and OpenView Operations Boom (1995 – 2000)

The framework shifted from isolated utilities into an integrated, market-dominating enterprise suite.

  • 1995: HP tightly merges NNM and Operations Center into a single product called IT Operations (ITO) Version 3.x.
  • 1996: HP OpenView Service Navigator is embedded into the product line. It provides a graphical hierarchy of business services instead of just a raw list of broken servers.
  • 1999: The suite formally adapts to include broad SNMP traps alongside its core agents and is renamed HP OpenView Operations ITO.

🔄 Era 3: Platform Split and VantagePoint Transition (2001 – 2006)

HP decoupled its codebases to natively handle Windows NT/2000 scaling alongside legacy Unix environments while heavily investing in product renaming.

  • 2001: HP briefy rebrands the suite to HP VantagePoint Operations (VPO). However, customer brand loyalty forces them to quickly pivot back to the popular HP OpenView Operations (OVO) naming convention.
  • 2002: Codebases officially bifurcate into OVOU (OpenView Operations for Unix) and OVOW (OpenView Operations for Windows, built natively on Microsoft WMI frameworks).
  • 2005: OVO Version 8.0 drops. It features heavy integration capabilities for external service desks, advanced HTTP/HTTPS agent communication protocols, and a refreshed Java GUI console.

🏢 Era 4: The Business Technology Optimization (BTO) Era (2007 – 2016)

Massive corporate acquisitions changed the software landscape. OVO ceased to be a standalone system monitoring tool and transformed into an automated operations center.

  • 2007: HP drops the legendary “OpenView” moniker. Following the acquisitions of Mercury Interactive, Peregrine, and Opsware, the suite is rebranded as HP Operations Manager (HPOM) under the HP Business Technology Optimization (BTO) banner.
  • 2009: HP rolls out Operations Manager i (OMi), integrating topology-based event correlation (TBEC) to suppress duplicate alert storms across the data center.
  • 2015: Hewlett-Packard splits into two companies; the portfolio lands under Hewlett Packard Enterprise (HPE). The engine is bundled into the HPE Operations Bridge (OpsBridge) suite.

☁️ Era 5: Divestiture and Modern Legacy (2017 – Present)

  • 2017: HPE spins off its enterprise software division. The entire legacy OpenView/Operations Manager portfolio is sold to Micro Focus.
  • 2023: OpenText completes its acquisition of Micro Focus. The underlying technical heritage of the old OVO agents survives today, evolved into cloud-ready containerized architectures inside the modern OpenText Operations Bridge cloud monitoring portfolio.
OpenText Operations Bridge Manager screenshot example
OpenText Operations Bridge Manager Screenshot example

HPE NonStop (previously Tandem) Monitoring

Micro Focus Operations Bridge (now part of OpenText AI Operations Management) provides end-to-end IT monitoring by consolidating data from over 200 sources. For HPE NonStop, it utilizes specialized Management Packs to ingest metrics, system events, and health data for comprehensive, real-time hybrid IT analysis.

To monitor HPE NonStop servers using the modern OpenText Operations Bridge/AIOps platform, the setup revolves around the Operations Bridge Manager (OBM) and targeted management packs:

  • Management Packs for HPE NonStop: OpenText provides specific management packs and solutions designed for NonStop systems. These capture system health, CPU/disk metrics, pathway status, and system messages.
  • Operations Agent: A lightweight agent is deployed directly on the NonStop nodes, which securely streams local performance data and events back to the central OBM console.
  • Centralized Event Consolidation: OBM acts as a “manager of managers”. It ingests the NonStop events and correlates them alongside data from your cloud (AWS/Azure), containers, and network endpoints.
  • AIOps and Remediation: The platform utilizes built-in machine learning to reduce alert noise and accelerate root cause analysis. You can also use automated Runbooks to automatically remediate known issues on the NonStop platform.

Because the platform has been fully integrated into the OpenText portfolio, these integrations are supported across containerized deployments, on-premise, or SaaS models.

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