During his tenure as an IT Project Manager at Wincor Nixdorf (Banking Division) from 2013 to 2014, Mark Whitfield focused on large-scale retail banking software modernisation and multi-vendor hardware migrations.
He spearheaded a £5+ million workstream on-site for Lloyds Banking Group (LBG) as part of their Self-Service Software Replacement (SSSR) programme.
The focus areas and technical outputs of his work during this era are detailed below.
🏛️ Era Focus Areas (2013–2014)
Legacy ATM Modernisation: Managing the transition of core banking infrastructure away from legacy terminal systems to prevent service outages and meet stricter post-2008 operational risk regulations.
Multi-Vendor Integration: Directing complex hardware and software integration streams to ensure Wincor Nixdorf solutions successfully paired with third-party banking frameworks.
International Technical Liaison: Acting as a qualified management link between the local UK delivery teams and Wincor Nixdorf’s central engineering base in Paderborn, Germany, for advanced subject matter expertise.
Methodology Pivot: Implementing project governance frameworks that bridged strict PRINCE2 Waterfall structures with Agile Scrum delivery models.
💻 Technical Outputs
ATM Terminal Driving Migration: Transferred critical automated teller machine (ATM) driving responsibilities away from legacy BASE24 Classic running on HPE NonStop mainframes over to Wincor’s ProClassic Enterprise (PC/E) product suite deployed on an AIX platform.
OS Lifecycle Upgrades: Successfully planned and executed the infrastructure upgrade of the Lloyds Banking Group ATM hardware estate from the end-of-life Windows XP operating system to Windows 7.
Database & Platform Architecture: Delivered backend systems alignment leveraging Oracle databases integrated across distributed UNIX/AIX environments.
Mark Whitfield served as an IT Senior Digital Project Manager (often operating in product and application delivery roles) within the Online and Mobile Division at Betfred from December 2014 to January 2016.
During this era, his responsibilities crossed the boundary between project management and digital product delivery. He was heavily focused on shifting legacy digital footprints toward modern mobile, web, and multi-vendor integrations.
Below are the focus areas and technical outputs from his tenure at Betfred, grouped by operational era and delivery cycle:
📱 1. Digital Platform & Mobile Era (Core Product Delivery)
This area focused on the rapid evolution of the sportsbook and the deployment of consumer-facing native and web applications.
Focus Areas: Mobile product lifecycle management, multi-platform deployment, and real estate feature upgrades for .COM and .mobi channels.
Technical Output:
Native Applications: Delivered and updated native mobile applications across iOS, Android, and Windows Phone.
Sportsbook Verticals: Built, optimized, and deployed major UI/UX updates for the football and horse racing sportsbooks.
Virtual Gaming: Integrated online, computer-generated virtual gaming modules and RNG (Random Number Generator) components into the digital ecosystem.
🔒 2. Payment Systems, Security, & Compliance Era
A major focus was placed on building high-throughput payment pipelines and establishing robust compliance mechanics to handle compromised trading environments.
Focus Areas: Fraud mitigation, multi-currency processing, payment gateway migrations, and strict adherence to gambling regulations.
Technical Output:
Payment Gateways: Delivered end-to-end payment gateway mechanisms supporting diverse credit/debit, e-wallet, and localized payment methods.
Fraud Detection Systems: Integrated advanced fraud detection and risk analysis modules into backend transactional pathways.
Emergency System Change Requests (SCRs): Architected and executed critical hotfixes for compliance directives, regulatory alignment, and security mitigations.
🔄 3. Software Development Lifecycle (SDLC) & Release Era
This era was characterized by a massive transition away from rigid legacy setups into continuous delivery models.
Focus Areas: Transitioning environments from Waterfall to the Agile Scrum framework, managing distributed cross-functional teams, and stabilizing deployment cadences.
Technical Output:
Monthly Release Cycles: Structured and executed the monthly internet software release train to stabilize production code across the web real estate.
Middleware & API Integrations: Managed complex integrations connecting frontend frameworks with heavy transactional middleware and core banking/wallet ledgers.
🤝 4. Multi-Vendor Sub-System Integration
Because Betfred’s tech stack relied heavily on third-party niche solutions, Whitfield acted as the technical delivery anchor across an extensive network of specialized vendors.
Frontend & UX: Coordinated front-end developments with agencies like Degree 53.
Core Gaming & Content Systems: Integrated third-party components from industry staples including Playtech, Inspired, IGT, and Virtue Fusion.
Data Feeds & Push Tech: Managed real-time data ingestion and notification engines built by Onionsack, OtherLevels, Satellite Information Services (SIS), and StreamUK.
Analytics & Performance: Integrated user attribution and marketing pipelines utilizing Appsflyer, Income Access, and Activewin.
During his time at The Software Partnership (acquired by Deluxe Data International in 1994), Senior IT Project Manager Mark Whitfield operated as a Programmer and Lead Analyst. This era lasted from 1990 to 1995 and focused on foundational electronic banking software frameworks, specifically the sp/ARCHITECT-BANK platform.
The key projects and focus areas within this era are structured below by client timeline, focus areas, and technical outputs:
🏦 1990–1992: Barclays Bank (Knutsford, Cheshire)
Focus Area: On-site architectural design and core mainframe development for high-profile business banking.
Technical Output: Designed and coded back-end software modules for the Barclays Business Master II (BBM II) desktop banking project.
📞 1992–1993: Girofon (Denmark)
Focus Area: Telephonic integration and automated remote banking solutions.
Technical Output: Developed an automated, menu-driven touch-tone phone banking suite. This allowed voice commands to dial into a Periphonics VRAM device to fetch live customer balances directly from back-end mainframes.
📊 1993: Barclays Bank (Poole, Dorset)
Focus Area: Financial transactional automation and corporate service invoicing.
Technical Output: Created and integrated a custom batch billing suite of modules that attached to the BBM II application to automate client usage invoicing.
💻 1993–1994: TSB & Bank of Scotland
Focus Area: Early digital forensics, fund movements, and logic architecture.
Technical Output: Conducted digital investigations and engineered logic design and mainframe code to support early inter-account desktop money transfers.
🌍 1994–1995: Rabobank
Focus Area: International systems deployment, optimization, and validation.
Technical Output: Led software optimization protocols, wrote custom electronic coding patches, and validated on-site deployments for global operations.
⚙️ Core Technical Stack & Environment Summary
Across all eras at The Software Partnership, the standardized environment utilized for these outputs included:
Hardware & Operating Systems: Tandem Mainframe Computers (now HPE NonStop) operating on the Tandem Guardian O/S.
Programming Languages: COBOL85, NonStop SQL, SCOBOL (Screen COBOL for “green screen” terminal emulations), C, C++, and TAL.
Subsystems & Tools: PATHWAY, PATHMAKER, ENSCRIBE, EMS, and INSPECT.
Methodologies: Early iterative development and structured Waterfall lifecycles.
As a client-facing, SC-cleared Engagement Manager and Senior Project Manager for Capgemini UK (2016–Present), Mark Whitfield’s focus areas and project outputs fall into Phase 5 (Enterprise Cloud, Integration & Public Sector Delivery) of his overall professional trajectory.
His tenure at Capgemini UK is marked by managing complex hybrid migrations, enterprise system integrations, and multi-million-pound public and private sector contracts using hybrid Agile and PRINCE2 methodologies.
🌐 Era 1: Public Sector & Cloud Migration (2019–Present)
This era aligns with the UK government’s “Digital by Default” mandate and a nationwide public sector transition toward highly secure, cost-optimized, and green cloud platforms.
Re-hosting, re-platforming, and refactoring legacy software architectures.
Cross-functional alignment with rigid government data privacy guidelines (GDPR).
Coordinating large-scale onshore and offshore engineering delivery resources.
Project Outputs:
Directed a massive £13.5 million programme to migrate over 130 public sector legacy applications onto Microsoft Azure and AWS platforms.
Delivered a Proof of Concept (POC) indicator project worth £375k ahead of the wider national public infrastructure cloud framework rollout.
🔌 Era 2: MuleSoft Ecosystem & Enterprise API Integration (2018–2019)
During this phase, Whitfield was augmented as a Delivery Manager into MuleSoft (a Salesforce company) operating out of the London Salesforce Tower.
Focus Areas:
API-led connectivity frameworks and microservices architecture deployment.
Hyper-automation and multi-site enterprise system integrations.
API lifecycle design and Anypoint Code Builder configurations.
Guiding high-influence blue-chip clients through API connectivity governance.
Project Outputs:
Successful deployment of production-ready APIs to unlock siloed, legacy back-end system data.
Delivered complex data pipelines to support modernized, interconnected digital applications for tier-one global brands.
🛫 Era 3: Major Corporate Infrastructure & Sector Delivery (2016–2018)
Upon joining Capgemini in January 2016, Whitfield initially spearheaded highly secure, custom bespoke solutions across critical commercial and defensive sectors.
Focus Areas:
High-security, multi-site project tracking, financial forecasting, and stakeholder governance.
Automated manufacturing, aerospace, defense, and logistics supply chain data tracking.
Complex Agile SCRUM sprint ceremonies with heavy cross-team interdependencies.
Project Outputs:
Aerospace & Defence (NATS): Oversaw the secure delivery of custom Apple iOS apps providing real-time, public-facing, and military airspace data.
Postal Services (Royal Mail Group): Managed an award-winning £4.3 million project utilizing 90 Capgemini engineers to safely migrate over 1,100 system interfaces across dual data centers.
Automotive Integration (Jaguar Land Rover): Directed extensive enterprise architecture planning, pipeline resource mapping, and Scrum team management for a major supply chain initiative.
During his 18-year tenure (1995–2013) at Insider Technologies Limited (ITL) in Salford Quays, UK, Senior IT Project Manager Mark Whitfield advanced from a core technical engineer into strategic product and project management.
His time at the company is defined by two distinct operational eras, marked by a clear shift from code development to enterprise delivery:
🛠️ 1. The Engineering & Technical Development Era (1995–2004)
During this period, Whitfield operated primarily as a Senior Programmer, focusing on platform health, system diagnostics, and transaction log extraction architectures for highly critical financial systems.
Main Focus Areas:
Infrastructure consulting, automated system management, and volume stress-testing.
Service Level Agreement (SLA) monitoring for critical path payment pipelines.
HPE NonStop (formerly Tandem Computers via Compaq) platform optimization and software engineering.
Technical & Project Outputs:
Reflex (Reflex 80:20) Co-Development: Designed and authored platform health and core diagnostic plug-in modules, including Console (for EMS event viewing and filtering), Status Monitor (for tracking HPE NonStop platform components including CPU, Disk, Process, Enscribe Files, MQ, XPNET, TCP/IP, MultiBatch jobs), and Service Monitor (multi-line, rule-based multi-component analysis).
CRESTCo Infrastructure Benchmark (1997): Contracted on-site to CRESTCo (now Euroclear) to write custom benchmarking software evaluating stock settlement software performance on newly introduced S7000 HPE NonStop systems.
HP OpenView Certification (2002): Successfully engineered and secured the industry’s first HP OpenView Operations Enterprise Manager 2-way Smart Plug-In (SPI) certification for HPE NonStop environments.
📈 2. The Strategic Product & Project Management Era (2004–2013)
In this phase, Whitfield transitioned into a Product Manager and Project Manager role (Strategic Technical Initiatives), taking charge of complete software development lifecycles (SDLC) using structured PRINCE2 and early Agile Scrum frameworks.
Main Focus Areas:
ATM/POS transaction monitoring and real-time electronic payments tracking.
Web-enabled client-server browser monitoring frameworks and middleware solutions.
Pre-sales technical bidding, executive demos, and client deployment validation across Europe and the Middle East.
Technical & Project Outputs:
RTLX Reactor & Sentra Suites: Managed the commercial rollout and high-volume deployment of the browser-enabled Real-Time Log Extraction (RTLX) suite and Sentra monitoring solutions to capture and parse ATM/POS logs.
Enterprise Bank Implementations: Directed mission-critical payments monitoring integrations (notably processing ACI BASE24 Classic and BASE24-eps transactions over XPNET middleware) for tier-1 financial heavyweights including HSBC, Alliance & Leicester, Standard Chartered, and Al Rajhi Bank (Saudi Arabia).
Open CMS Corporate Re-platforming: Researched, designed, and authored a complete overhaul of Insider Technologies’ public corporate website using an Open Content Management framework (DotNetNuke).
💻 Core Technology Stack (1995–2013)
Across both eras at Insider Technologies, Whitfield’s environment relied on high-availability, fault-tolerant ecosystems:
Platforms & Operating Systems: HPE NonStop (Tandem K-Series, S-Series, and Itanium J-Series), Guardian O/S, Windows 2000/XP, Linux, and Unix.
Languages & Toolsets: Pathway, INSPECT, SPOOLCOM, Peruse, TAL (Tandem Application Language), NonStop C, C++, COBOL85, SCOBOL, NonStop SQL, TACL, and Enscribe.
Enterprise Software Interfaced: ACI BASE24 Classic, BASE24-eps, XPNET, ICE (Insession), TIVOLI, COMMAND/POST, and HP OpenView Operations (HP OVO).
Microsoft Project—whose native file format extension is .mpp—is one of Microsoft’s longest-running products, originally originating from a DOS-based tool acquired in 1984. Over its four-decade lifespan, it has evolved from a basic critical path method (CPM) scheduler into a core enterprise project and portfolio management (PPM) system.
The .mpp format, which is the proprietary binary file structure used to store metadata, task hierarchies, schedules, and resource assignments, has undergone multiple structural changes to support new features like Agile workflows, critical path mapping, and multiple timelines. Buy MPP MS Project templates (like those above) here.
Chronological Timeline of Microsoft Project (1984 to Present)
1984 – 1986 (The DOS Era): The first commercial version, MS Project 1.0, was released for MS-DOS in 1984. It laid the foundation for Critical Path Method (CPM) scheduling.
1990 – 1993 (Transition to Windows/Mac): The first Windows version (Project 1.0 for Windows) launched in 1990. Microsoft subsequently released a Macintosh version in 1991, but officially ceased its Mac development by 1994.
1995 – 2003 (The Office Integration): With releases like Project 95, Project 98, and Project 2000, the software began to mirror Microsoft Office’s user interface, introducing PERT charts (later renamed Network Diagrams), multiple baselines, and resource pooling.
2007 – 2010 (The Ribbon and Server Era): Project 2010 became the first 64-bit version, introducing a modern ribbon and Backstage view. This era saw widespread use of Project Server for enterprise collaboration.
2013 – 2019 (Cloud & Modern UX): Integrating deeply with the Microsoft 365 environment, these versions introduced resource capacity heat maps, agile task fields, and native Plan-on-a-Page (POAP) timeline views.
2021 – 2024 (Modern Desktop Suite): The latest perpetual releases (Project 2021 and Project 2024) act as heavy-duty scheduling engines that integrate with modern tools like Power BI and Microsoft Teams.
Future Direction of the .MPP Format and Project Management
As of 2026, Microsoft is executing a major platform restructuring. The .mpp format will remain the standard file extension for the standalone, offline desktop application (e.g., Project Professional 2024/Subscription Edition), serving enterprise users who require complex scheduling, multi-project rollups, and deep resource optimization. Buy MPP MS Project templates here.
However, Microsoft is shifting its cloud and portfolio-level infrastructure entirely away from legacy SharePoint-based architectures. This structural shift impacts the .mpp ecosystem in several key ways:
Retirement of Project Online: Microsoft Project Online (the cloud-based service that previously stored and synchronized .mpp projects in the cloud) is officially fully retired.
Consolidation under Microsoft Planner: Microsoft’s cloud-based work management is converging entirely under the unified Microsoft Planner app (which incorporates former “Project for the web” capabilities).
Transition to Modern Cloud Formats: In the web and cloud ecosystem, the rigid and complex .mpp file is being replaced by Microsoft’s cloud-native architecture (which can be exported to standard .xml formats for interoperability).
Continued Desktop Support: Organizations requiring complex WBS (Work Breakdown Structure) views, complex dependencies, and local file storage can still utilize the desktop client versions (e.g., accessed via Microsoft Project Plan 3) which natively open .mpp files.
Viewer and Interoperability Utilities: Because native .mpp files cannot be opened by Microsoft Planner or Excel, Microsoft provides the XML Format Standard (MS-XDI) as the primary avenue for transferring custom scheduling data between desktop platforms and modern cloud APIs.
Microsoft Project MPP format, timeline & future direction
The European BASE24 User Group (EBUG) was established in the 1980s as an independent, community-led organization for users of the BASE24 payment processing system developed by Applied Communications, Inc. (now ACI Worldwide).
Originally a regional forum for IT professionals in Europe to discuss HPE NonStop (Tandem) transaction monitoring and network security, the group expanded globally over time.
Insider Technologies regularly attended EBUG, booth in 2007 – RTLX now ETI-NET C-Deep
Following ACI’s withdrawal of direct corporate backing, EBUG evolved into “The Independent Group for All Payments System Users”—affectionately known as the Everybody Belongs User’s Group—welcoming users of multiple payment platforms like Postilion.
The detailed historical timeline of EBUG and the evolution of its core system, BASE24, outlines its development from a regional user collective to a global payments forum:
The Foundation Era (1975–1989)
1975: ACI is founded in Omaha, Nebraska, initially developing software for fault-tolerant Tandem NonStop computers to connect ATMs to bank networks.
1982: The BASE24 product family is officially launched globally, acting as “baseline” software for 24-hour financial operations.
1980s:EBUG is established as a regional European community for BASE24 users to collaborate on ATM networking and transaction processing.
Early 2000s: EBUG annual conferences grow in prestige, featuring technical tracks on BASE24 transaction logging, Point-of-Sale (POS) networks, and network resilience.
2007: EBUG hosts a high-profile international conference in Istanbul, Turkey.
2008: EBUG hosts its annual meeting in Vienna, Austria, which is historically noted as a pivotal year where ACI began supporting immediate payments in Europe and discussed a strategic shift toward IBM platforms. ACI officially announces the future retirement of “BASE24 Classic”.
2009: The conference is held in Prague, Czech Republic, maintaining strong community support for BASE24 on Tandem servers despite broader industry shifts.
Global Expansion, Rebranding & The Cloud Era (2010–Present)
2012: ACI introduces BASE24-eps, their next-generation, platform-independent payments engine designed to replace the legacy BASE24 on HPE NonStop. EBUG’s technical focus shifts to real-time payments and log extraction.
2013: With ACI ending direct involvement, the user group officially rebrands as the “Everybody Belongs User’s Group” at their conference in London, expanding attendance to professionals from Mexico, South Africa, and Australia.
2015: ACI celebrates 40 years in payments. EBUG solidifies its status as a supplier-agnostic payments forum, opening sessions to non-BASE24 users.
2020s: With BASE24 Classic retired, legacy users migrate to modern systems like BASE24-eps for cloud deployments and immediate payments.
Recent Years: ACI goes live as a pioneer in the Federal Reserve’s FedNow Service, building upon the decades-long transaction switching architecture first developed in the 1970s and 1980s.
European BASE24 User Group (EBUG) Timeline from Inception
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
PROject Templates 