Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

i_Pro_PM_Templates on Flevy is a comprehensive library of 19 project management templates

The i_Pro_PM_Templates collection on Flevy is a highly comprehensive library of 19 specialized project management resources spanning Waterfall and Agile methodologies. Developed by a contributor with 30 years of project management experience, these fully editable files (PowerPoint, Excel, Word, and MS Project) are designed to bridge corporate strategy with rapid execution. The complete 200+ template ZIP file package can be purchased here also.

The specific templates offered by i_Pro_PM_Templates are organized below by their operational category and core function:

🗺️ 1. Project Planning & Roadmaps

Designed to provide executive stakeholders and project teams with high-level visualization and structured timelines.

  • Plan on a Page (PoaP) 30+ Examples (PowerPoint): Synthesises complex timelines into an executive-ready format.
  • Project Plan on a Page Template (Excel): Tracks milestones and deliverables on a single sheet.
  • Waterfall Project Planner with Gantt View (Excel): Automates timeline bars and highlights dependency tracking.
  • Microsoft Project Plan Editable Templates (MPP / MSP): Implements native tracking with pre-populated project paths.

📊 2. Project Governance & Status Reporting

Built to manage the cadence of team communications, track risks, and report progress up to the PMO.

  • Weekly Status Report (PowerPoint): Provides standardized internal and external updates for Agile or Waterfall projects.
  • Status Report with PoaP, RAIDs, & Burn Down (Excel): Combines execution charts with high-level summary roadmaps.
  • MS Excel RAID Log: Acts as a central command log for Risks, Issues, Dependencies, and Change Requests (CRs).

⚖️ 3. Value & Benefits Realization

Ensures project delivery aligns with financial targets and baseline calculations.

  • Programme & Project Benefits Realization Tracker (Excel): Uses automated calculations and RAG status indicators to ensure value delivery.
  • Project Finance Tracker (Excel): Integrates budget forecasting against actual financial performance.

📦 4. Comprehensive Master Toolkits

Bundled suites that consolidate hundreds of micro-assets into standalone lifecycle frameworks.

  • 200+ Project Management Templates Bundle (PDF/ZIP): Features customizable documents covering initialization through to closeout.
  • PRINCE2 Templates + MPP & Excel Pack: Embeds strict PRINCE2 project stages into functional tracking models.
  • MS Teams Free Planner Guide: Details how to organize and execute Agile backlogs directly inside Microsoft Teams.

A detailed breakdown of the exact templates published by this author, structured by their functional use and file format, includes the following:

📈 PowerPoint (PPT / PPTX) Formats

  • Plan on a Page (POaP) Examples: A 39-slide PowerPoint document providing high-level visual roadmap templates to summarize project delivery tracks for executives.
  • Weekly Status Report (Internal / External): A 15-slide PowerPoint designed for recurring project health reporting, configured for both Agile and Waterfall methodologies.

📊 Excel (XLS / XLSX) Formats

  • Waterfall Project Planner: A structured spreadsheet featuring built-in, automated Gantt view generation tools for scheduling sequential project stages.
  • Status Report with Plan on a Page & RAIDs: A hybrid workbook integrating high-level timelines, a Risk, Assumptions, Issues, and Dependencies (RAID) log, and an Agile burn-down chart tracker.
  • PRINCE2 Editable Planning & Cost Tracker: A financial tracking sheet customized specifically to align with the stage-gate requirements of the PRINCE2 methodology.

🛠️ Microsoft Project (MPP) Formats

  • Microsoft Project Plan Template: A baseline editable project plan native schedule built for resource loading and critical path tracking.
  • PRINCE2 Microsoft Project Plan: A pre-configured schedule mapped directly to standard PRINCE2 product breakdowns and stages.

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.

Father’s Day present, home made Space Invader band

Father's Day present, home made Space Invader band
Father’s Day present, home made
Space Invader band

PRINCE2 project templates, Excel (.xls/.xlsm) & MS Project (.mpp) formats

You can find downloadable PRINCE2 project templates in Excel (.xls/.xlsm) and Microsoft Project (.mpp) formats across several specialized platforms. Because PRINCE2 is a highly structured methodology, standard templates usually map its specific processes (like Starting Up, Initiating, and Controlling a Stage) directly onto Gantt charts and tracking sheets.

PRINCE2 MS Excel .xls plan in a spreadsheet
PRINCE2 MS Excel .xls plan
in a spreadsheet
PRINCE2 MS Project .mpp plan in a project file
PRINCE2 MS Project .mpp plan
in a project file

The primary download options, ranging from premium practitioner bundles to free resource packages, are categorized below:

Comprehensive Premium Bundles (MPP & XLS)

If you require a fully integrated toolkit built specifically for the official PRINCE2 framework, individual project management practitioners offer comprehensive marketplace downloads:

  • Mark Whitfield PM Templates: Offers a dedicated seventh edition package including MW MS Project Plan Template PRINCE2 v0.2.mpp alongside its exact equivalent spreadsheet MW Excel PRINCE2 Project Plan Template v0.2.xlsm. You can download this Prince2 toolkit package plus others, on the Mark Whitfield Official Site or through the Mark Whitfield Etsy UK Shop.
  • Flevy Marketplace: Provides highly structured, professional enterprise files. You can purchase and download the PRINCE2 Templates + Microsoft Project MPP & MS Excel Document directly from their platform, which packs the MPP tracking timelines and XLSM / XLS sheets together.

PRINCE2 project templates, Excel (.xls/.xlsm) & MS Project (.mpp) formats

Microsoft Excel XLS PRINCE2 spreadsheet screenshots

Microsoft Excel XLS PRINCE Project Plan with Task Descriptions
Microsoft Excel XLS PRINCE Project Plan with Task Descriptions
Microsoft Excel XLS PRINCE Project Plan with Gantt View 1
Microsoft Excel XLS PRINCE Project Plan with Gantt View 1
Microsoft Excel XLS PRINCE Project Plan with Gantt View 2
Microsoft Excel XLS PRINCE Project Plan with Gantt View 2
Microsoft Excel XLS PRINCE Project Plan with Gantt View 3
Microsoft Excel XLS PRINCE Project Plan with Gantt View 3
Microsoft Excel XLS PRINCE Project Plan with Delivery Costings
Microsoft Excel XLS PRINCE Project Plan with Delivery Costings
Microsoft Excel XLS PRINCE Project Plan with Charts
Microsoft Excel XLS PRINCE Project Plan with Charts
Microsoft Excel XLS PRINCE Project Plan with PRINCE2 Stage Charts
Microsoft Excel XLS PRINCE Project Plan with PRINCE2 Stage Charts

Standard Artifacts Included in Download Packages

When downloading a comprehensive .zip toolkit, the package typically contains the core structural elements of the framework divided across your scheduling software:

  • MS Project (.mpp): A pre-constructed Prince2 waterfall delivery layout mapped with the 7 key PRINCE2 stages, built-in dependency workflows, milestone gates, and methodological prompts embedded in the task notes.
  • MS Excel (.xls/.xlsm): Mirrored project planning sheets (with costing) utilizing native formulas to auto-populate Gantt charts, alongside targeted operational spreadsheets like RAID logs (Risks, Assumptions, Issues, Dependencies), RACI matrix charts, resource trackers, and project budget tools.

Requirement versus User Story

Project requirements are comprehensive, formal specifications describing what a system must do, usually written from the system’s perspective. User stories are short, lightweight descriptions of functionality written from the end-user’s perspective to drive team collaboration and conversation.

The distinction between these two approaches shapes how modern development teams capture scope and value.

Requirement versus User Story
Requirement versus User Story

Understanding Project Requirements

  • Focus: System functionality, technical constraints, and business rules.
  • Perspective: Written from the viewpoint of the system or product (e.g., “The system shall generate daily PDF reports.”).
  • Format: Heavy documentation, PRDs (Product Requirements Documents), spreadsheets, or flowcharts.
  • Methodology: Traditionally used in waterfall methodologies to define the scope comprehensively before any design or development begins.

Understanding User Stories

  • Focus: The user’s goal, business value, and the “why” behind a feature.
  • Perspective: Written from the viewpoint of the persona using the system (e.g., “As a Sales Manager, I want to review daily signups so that I can prioritize my sales calls.”).
  • Format: Short, often using the template: As a [User], I want to [Action], so that [Benefit]. Accompanied by Acceptance Criteria.
  • Methodology: An Agile-first tool. They are designed to act as an “invitation to a conversation” rather than a finalized contract.

Key Differences at a Glance

How They Work Together (The Hybrid Approach)

Most modern software development teams don’t abandon requirements entirely, but they shift the format. They use lightweight User Stories to represent the core value, and then pair them with technical Acceptance Criteria or supplementary design specifications to clarify the exact requirements the system must satisfy.

Requirement versus User Story

Hindley Green County Primary School, Thomas Street

Hindley Green Community Primary School (formerly known as Hindley Green County Primary School), located on Thomas Street, Hindley Green, Wigan, has a rich history transitioning from a traditional local authority “Council” school into a modern 21st-century academy.

The detailed chronological timeline of the school, organized by major administrative and historical eras, is structured below.

1. The Early Council School Era (Pre-1950s)

Originally established as the local “Council” school, this era marked the establishment of the school grounds on Thomas Street as Hindley Green expanded.

  • Early 20th Century: The open field that would eventually become the footprint of Thomas Street and the extended school boundaries was initially a standard play plot used by local children, bound by hawthorn hedges.
  • Interwar / Post-WWII Expansion: A dedicated school structure was built to accommodate Hindley Green’s growing population. Iron boundary rails were erected, replacing the older hedges as the school football field and permanent structures took shape.
  • 1947: Freddie Hardman served as the prominent Headteacher during the post-war reconstruction period.

2. The Late County Primary Era (1950s – 1990s)

During this period, the school operated officially as Hindley Green County Primary School (CP) under the Lancashire (and later Wigan) Local Education Authority.

  • 1953: The school continued to feed local academic pathways, with eligible students sitting the historical 11+ examinations to transition into the nearby Hindley and Abram Grammar School (HAGS).
  • 1977: The school held extensive community celebrations to mark the Queen’s Silver Jubilee, a major milestone preserved in the school’s historical photographic archives.
Hindley Green County Primary School, Thomas Street
Hindley Green County Primary School,
Thomas Street
Thomas Street, Hindley Green County Primary School, Mark Whitfield, bottom row second from right
myself, bottom row, 2nd from right
(1975/ 76)

3. The Modern Community Primary Era (2000s – 2014)

The school dropped the “County” designation to become Hindley Green Community Primary School, expanding its infrastructure and early years provisions.

  • 2002: The school community hosted a massive historical dress-up party to celebrate the Queen’s Golden Jubilee.
  • 2004: The school underwent a full inspection by Ofsted on 21 June 2004, securing its educational frameworks for the new decade.
  • 2008: Another comprehensive Ofsted inspection took place on 6 November 2008.
  • 2009: Ofsted conducted a targeted interim monitoring visit on 12 May 2009.
  • 2010: A major modern infrastructure expansion began. In September 2010, construction firm Eric Wright Group initiated on-site work to build vibrant new facilities and structural updates for the primary school.
  • 2012: Following the structural expansions, Ofsted conducted a full framework inspection on 3 October 2012.
  • 2014: On 10 June 2014, the school achieved a “Good” rating from Ofsted under its local authority architecture. This marked the final year the school operated in its original legal structure before closing its local authority registry on 31 December 2014 to prepare for conversion.

4. The Academy Trust & QUEST Era (2015 – Present)

To secure independent funding and collaborative governance, the school transitioned into an academy.

  • 2015: On 1 January 2015, the school officially converted into an academy. It joined QUEST (A Church of England Schools Trust) under the sponsorship of The Keys Federation.
  • 2017: As a newly established academy, the school underwent its first short Ofsted inspection on 12 September 2017, maintaining its robust standards.
  • 2023: A full-scale school inspection was carried out by Ofsted on 19 January 2023. This same year, the school unveiled a prominent community superhero and princess mural to establish a lasting legacy for late pupil Holly Prince.
  • 2026: Operating at a healthy co-educational capacity of roughly 381 to 410 pupils (ranging from ages 3 to 11), the school provides crucial early years funded childcare alongside its standard Key Stage 1 and Key Stage 2 primary curriculum.

Hindley Green County Primary School, Thomas Street

Legacy Enterprise Management Systems, EMS

Legacy enterprise managers (often spanning IT Service Management, Network Node Management, and Event Correlation) defined enterprise IT in the 1980s, 1990s, and 2000s. The following are major, pioneering platforms, their primary functions, and their eventual modern replacements:

Legacy IT Operations Management (ITOM)

  • HP OpenView: A flagship suite that included Network Node Manager (NNM) for topology mapping and Operations Manager (formerly OVO) for centralized event and alert monitoring across Unix, Windows, and mainframes. I overlooked the integration of the HP NonStop product Reflex 80:20 with HP OpenView.
    • Modern equivalent: Evolved into Micro Focus Operations Bridge, later absorbed by OpenText.
  • IBM Tivoli: A massive suite born from the acquisition of Candle and Tivoli Systems. The core components included Tivoli Enterprise Console (TEC) for event correlation and Tivoli Netcool/OMNIbus for real-time network and service monitoring. I overlooked the integration of the HP NonStop product Reflex 80:20 with IBM Tivoli.
    • Modern equivalent: Evolved into IBM Cloud Pak for Watson AIOps.
  • BMC Patrol: One of the premier tools for deep system, application, and database monitoring (often known for its KM – Knowledge Module – architecture).
    • Modern equivalent: BMC TrueSight Operations Management and BMC Helix.
  • CA Unicenter: A comprehensive, all-in-one mainframe and distributed systems management tool for job scheduling, asset management, and event monitoring.
    • Modern equivalent: Rebranded under Broadcom, largely integrated into their enterprise software division.
  • Sun Microsystems SunNet Manager / Solstice Enterprise Manager: Early pioneers in Unix-based network management and remote system administration.
    • Modern equivalent: Discontinued; mostly absorbed by Oracle Enterprise Manager.

Enterprise Event Correlation & Command Centers

  • Command/Post (Boole & Babbage): One of the earliest automated event correlation engines designed for mainframes, which later expanded into distributed environments. Acquired by BMC.
  • Micromuse Netcool: Famous for its ultra-fast, rules-based Omnibus, capable of ingesting vast amounts of SNMP traps and Syslog messages across telecommunications and large enterprise networks. Acquired by IBM.

Network and Performance Managers

  • HP OpenView Performance/SysView: Tools specifically built for historical performance charting, OS native monitoring, and deep metric extraction.
  • Novell NMS (NetWare Management System): The standard for managing legacy Novell NetWare servers and IPX/SPX network topologies.

Most of these tools were displaced by modern APM (Application Performance Monitoring) and AIOps (Artificial Intelligence for IT Operations) platforms that feature cloud-native architectures, distributed tracing, and out-of-the-box integrations. Common replacements include:

  • Datadog
  • Dynatrace
  • Splunk / Splunk IT Service Intelligence
  • LogicMonitor
  • ScienceLogic

HP OpenView Operations

HP OpenView Operations Enterprise Manager integration with Reflex 80:20

First HP NonStop 2-way Smart Plug-In (SPI) for HP OVO HP OpenView Operations
First HP NonStop 2-way Smart Plug-In
(SPI) for HP OVO

Requested to research and produce a design for integrating the ITL NSK based Reflex 80:20 product with the hp OpenView Operations (hp OVO) enterprise manager. This initially involved a trip to Lisbon to attend the hp OpenView Universe event that represents the technical showcase for this enterprise level product. I then put together a number of design documents and managed a development team tasked with engineering an hp OpenView Smart Plug-in (SPI) to interact with Reflex 80:20 on the hp NonStop platform. This hp SPI approach represents the latest technology for integrating third-party products and provides an unparalleled approach for enabling remote platform control and management under hp OVO.

Once the Reflex SPI development was complete, I overlooked acceptance testing at the hp labs at Fort Collins, Colorado and was instrumental in attaining HP certification for the Reflex 80:20 product. As part of the certification process, I produced a comprehensive Reflex SPI user guide along with supporting marketing literature. More information.

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