Capgemini Projects Managed from 2016 thru 2025, Summary

Mark Whitfield is an SC-cleared Senior IT Project Manager and Engagement Manager at Capgemini UK (Custom Bespoke Solutions).

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

Joining in January 2016, he has orchestrated enterprise-scale cloud migrations, middleware application refactoring, and API-led integration architectures across public sector and tier-one corporate clients.

Capgemini UK, Floor 7, Venus Building, Trafford Quays, Manchester. M41 7HA — Capgemini UK, Floor 7, Venus Building,
Trafford Quays

Below is the complete portfolio overview and highly detailed chronological breakdown by year of his project delivery history at Capgemini.

Project Portfolio Overview

Role Title: Certified Engagement Manager / Delivery Manager (A8 Core Level)
Methodologies: Agile Scrum ceremonies, Waterfall frameworks, and hybrid delivery patterns
Core Competencies: Hybrid cloud migrations, API lifecycle architectures, cross-data centre integration, multi-supplier governance, and financial forecasting
Key Clients Served: UK Government, MuleSoft / Salesforce, Jaguar Land Rover, Royal Mail Group, NATS, and Welsh Water

Detailed Capgemini Projects Timeline Breakdown by Year:

2016 – 2017: Aerospace & Defence Integration & Postal Infrastructure

Aerospace & Defence Mobile Apps: Managed an Agile Scrum delivery stream for a UK-wide Air Traffic organisation (NATS). He supervised the development of dual-layered Apple iOS applications rendering real-time airspace positioning data, separating sensitive internal military maps from public views.
Salesforce Portal Deployment: Led the enterprise integration and deployment of a Salesforce-driven Single Customer View (SCV) portal platform for defence stakeholders.
Postal Services Migration (May 2016 – Oct 2016): Appointed as PM for an award-winning £4.3 million Data Centre Migration project for a major postal client (Royal Mail Group). He directed 90 Capgemini engineers to shift 1,100+ critical interfaces—migrating file transmissions written in UNIX shell scripts and upgrading 150 interfaces processing through IBM ESB to safe software versions right before peak seasonal trading lockouts.

2017 – 2018: Automotive Supply Chain Middleware

Jaguar Land Rover iFAB Project: Directed the complex 12-month iFAB Middleware Project architecture development scheme. This cross-functional framework connected globally dispersed manufacturing supply components.
Supplier Governance: Coordinated on-site daily standups alongside integration engineering leads to accurately synchronize multiple software suppliers handling distinct tiers of middleware, messaging queues, and front-end architectures.

2018 – 2019: Enterprise API Platform Delivery (MuleSoft)

MuleSoft HQ Augmentation (October 2018 – June 2019): Embedded directly into MuleSoft’s London headquarters (Salesforce Tower) as a Senior Delivery Manager.

MuleSoft's London office is located within the Salesforce Tower (formerly known as Heron Tower) at 110 Bishopsgate. — MuleSoft’s London office is located within the Salesforce Tower at 110 Bishopsgate.

Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles. This encompassed configuring Anypoint Code Builder structures, validating hyper-automation runtime layers, and ensuring architectural compliance against regulatory framework rules.

Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles. — Anypoint Platform is the leading enterprise platform for building APIs, integrations & application networks

2019 – 2021: Large-Scale Public Sector Cloud Migration

UK Government Hybrid Cloud Transformation: Commanded a massive modernization program migrating a highly complex estate of legacy code.
130 Applications Transformed: Acted as the primary client escalation point to refactor, re-host, and re-platform 130 public-sector software applications into hybrid cloud environments. His responsibilities included aligning the massive multi-stack migration with strict GDPR protection directives and managing offshore project delivery targets.

2022: Utility Infrastructure & Cloud Upgrades

Water Utility EQS Cloud Shift: Dual-managed a £0.5 million technical contract moving an legacy document management environment (EQS) onto Microsoft Azure cloud structures via Enablon for Welsh Water and Scottish Water.
MS Dynamics 365 Evolution: Supervised a £0.4 million discovery and blueprint phase to move 12 legacy Microsoft Dynamics 2016 instances operating on outdated shared 8.2 infrastructure onto the unified Microsoft Dynamics 365 Online ecosystem. This involved authoring precise Statements of Work (SoW), custom exit strategies, and foundational Microsoft Project (MPP) tracking models.
Accolades: Won the prestigious Capgemini C&CA UK Communications & Engagement Award in December 2022 for outstanding delivery inside the Cloud & Custom Applications business unit.

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

Verified Sourcing & Portfolio Links

Read his full professional bio on the Mark Whitfield Profile Page.
View his deep-dive career record on the Mark Whitfield Career Timeline.
Review his technical case studies via the Mark Whitfield Recent Experience Page.
Verify specific dates, client listings, and program contexts at the Mark Whitfield Project History Timeline.
Check his formal certifications and awards on the Mark Whitfield Training & Awards Registry.

Capgemini Projects Managed from 2016 thru 2025, Summary

PCI DSS (Payment Card Industry Data Security Standard) is a global security framework

PCI DSS (Payment Card Industry Data Security Standard) is a globally recognized set of security guidelines designed to ensure businesses that accept, process, store, or transmit credit card information maintain a secure environment to protect cardholder data.

Who Needs It

If your business takes payments online, over the phone, or in-store, PCI DSS applies to you. It is mandatory for all merchants, financial institutions, and service providers handling card data, regardless of the company’s size or transaction volume.

The 12 Core Requirements

The standard consists of 12 fundamental requirements organized into 6 main control objectives:

Network Security: Install and maintain network security controls (e.g., firewalls) to protect cardholder data.
Secure Defaults: Never use vendor-supplied defaults for system passwords and other security parameters.
Protect Stored Data: Safeguard stored account data via encryption, hashing, or truncation.
Encrypt Transmissions: Strongly encrypt cardholder data across open, public networks.
Malware Protection: Protect all systems and networks against malicious software.
Maintain Secure Systems: Regularly update software, apply security patches, and develop secure systems.
Restrict Access: Restrict system and cardholder data access on a strict “need to know” basis.
Authenticate Users: Identify users and authenticate access to system components.
Restrict Physical Access: Control and restrict physical access to cardholder data and hardware.
Log and Monitor: Log and continuously monitor all access to network resources and cardholder data.
Regular Testing: Regularly test security systems and network processes for vulnerabilities.
Information Security: Maintain formal policies that address information security for all personnel.

Why Compliance Matters

Achieving compliance—often demonstrated through a Self-Assessment Questionnaire (SAQ) or a Report on Compliance (RoC)—protects your customers and your business from data breaches. Non-compliance can result in devastating penalties, forensic investigation costs, loss of merchant processing privileges, and heavy brand damage.

For more specific details, requirements, and self-assessment tools tailored to your business, refer to the official PCI Security Standards Council website.

API (Application Programming Interface) for Business Analysts BA

An API (Application Programming Interface) is a set of rules that lets different software programs communicate and share data with each other. Think of it like a waiter in a restaurant: you (the application) place an order (a request), and the waiter takes it to the kitchen (the server) and brings back exactly what you asked for.

How They Work

The Request: One program asks another for specific data or actions using an API call.
The Rules: The API dictates exactly how this request must be formatted to ensure security and consistency.
The Response: The receiving program processes the request and sends the requested information or executes the task.

For business analysts (BAs), APIs are crucial business enablers that connect systems, automate workflows, and drive revenue. Categorizing APIs helps BAs identify technical impacts, scope integration requirements, and align solutions with strategic business goals.

Categorization can be divided into three primary frameworks: Access Level, Business Purpose, and Architecture Style.

1. By Access Level (Audience)

This categorization defines who has permission to use the API and dictates security requirements.

Internal (Private) APIs: Developed by a company strictly for internal use. These connect backend systems (e.g., a CRM talking to an ERP) or allow different internal departments to share data securely.
Partner APIs: Shared specifically with external business partners or vendors. These require strict authentication and agreements to streamline supply chain or B2B operations (e.g., granting a distributor inventory access).
Public (Open) APIs: Exposed to developers and the general public to foster third-party integrations, app development, or ecosystem growth. They often require an API key or OAuth for tracking usage.

2. By Business Purpose (API-led Connectivity)

This approach, often used in integration methodologies like MuleSoft, categorizes APIs by their role in the enterprise architecture.

System APIs: Unlock data directly from core systems of record (e.g., a legacy database, an ERP, or a billing system).
Process APIs: Interact with and shape data across multiple systems to break down data silos (e.g., an API that takes order fulfillment data and formats it for shipment and inventory updates).
Experience APIs: Provide a business context for the data to be easily consumed by end-user interfaces like mobile applications, web portals, or chatbots (e.g., fetching a 360-degree customer view).

3. By Architecture Style (Technical Format)

While solution architects define the exact protocol, BAs must understand these styles to document data flow, map payloads, and communicate limitations with developers.

REST (Representational State Transfer): The most common web API standard. It uses HTTP methods to transfer data in simple formats like JSON.
SOAP (Simple Object Access Protocol): An older, highly structured protocol heavily used in enterprise and highly regulated industries (like banking and healthcare).
GraphQL: A query language for APIs that allows the client (e.g., a mobile app) to request exactly the specific data it needs, rather than fetching entire datasets.
Webhooks: Automated, event-driven APIs. Rather than a client requesting data, the server “pushes” data to the client the moment a specific event happens (e.g., sending a receipt to an app the instant a payment clears).

Key API Concepts for BAs

Business analysts rarely build APIs, but they must understand high-level concepts to document API requirements effectively:

Payload: The data that is being sent (Request) or received (Response).
CRUD / HTTP Methods: The basic actions mapped to data. BAs need to understand GET (Read), POST (Create), PUT/PATCH (Update), and DELETE (Remove).
Status Codes: Standardized numbers that indicate the result of a request (e.g., 200 for success, 404 for not found, or 500 for server error).
Documentation: BAs use standards like Swagger/OpenAPI to interpret how an API should behave.

Status Codes, Standardized numbers that indicate the result of a request (e.g., 200 for success, 404 for not found, or 500 for server error) — API Status Codes – standardized numbers
that indicate the result of a request

API (Application Programming Interface) for Business Analysts BA

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.

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

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

Real-Time Tracking Protocols (1999–2001): Oversaw multi-organizational telemetry deployments for the Bank of England and Deutsche Bank, leveraging specialized MultiBatch scheduling utilities and automated file monitors.
Hewlett-Packard (HP) Certification Initiative (2002–2003): Successfully drove the rigid compliance and verification process to secure official certification for the first HP OpenView Operations (OVO) Smart Plug-In built for NonStop mainframe environments.

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 Retail Banking Rollout (2008–2010): Served as Project Manager overseeing a high-volume, cross-border ATM and Point-of-Sale (POS) environment monitoring expansion for a prominent Saudi Arabian Retail Bank.

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.

Betfred Project Delivery (2014–2016): Managed IT infrastructure and digital systems alignment projects, supporting high-throughput retail and digital consumer gaming workflows.

☁️ 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 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).

Mark Whitfield Career Timeline by era and project

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

Professional Training

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.

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 Gantt View 1

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 Delivery Costings

Microsoft Excel XLS PRINCE Project Plan with 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.

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

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.

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

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

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

Mark Whitfield attending an EBUG conference
(BASE24 User Group) — Attending an EBUG conference
(European BASE24 User Group)

Foreground, attending a British Isles TANDEM User Group (BITUG) — Foreground, attending a British Isles
TANDEM User Group (BITUG)

Insider Technologies Limited, ITL, website in 2009 — Insider Technologies Limited
(website author in 2009)

Company Overview

🏢 Corporate Identity & Status

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

🌐 Core Domain & Industries Served

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

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

🛠️ Core Technology Stack & Competencies

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

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

In-Depth Product & Political-Technical Timeline

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

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

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

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

Political Context: Following the September 11 attacks, global anti-money laundering (AML) and counter-terrorism financing (CTF) frameworks heavily expanded. Financial regulators demanded exact, audible end-to-end payment tracking.
Technical Context: Enterprises began migrating away from single-architecture mainframes toward heterogeneous IT environments, requiring tools that could jump across Windows, Unix, and Linux simultaneously.

2002–2004
- Sentra Development: Launch of Sentra, expanding the firm’s portfolio beyond HPE NonStop into cross-platform environment monitoring for Windows, Linux, and Unix systems.
- Reflex 80:20 & Reflex ONE24: Advanced variations of the Reflex tracking system were built to cater to specialized real-time electronic payment flows like BASE24 with XPNET.
2005–2010
- RTLX Reactor (page 12) and Middleware Monitoring: The release of RTLX Reactor provided message tracking capabilities tailored for IBM WebSphere MQ, allowing institutions to trace various payment and other data through complex middleware chains.

BASE24-eps extraction and RTLX — BASE24-eps extraction
and RTLX (in 2007)

2011–2015
- Corporate Structuring: The creation of Insider Technologies (Holdings) Limited reinforced corporate expansion as the company deepened its footprint in secure military messaging for government defense bodies.

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

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

RTLX Reactor (in 2012) for tracking BASE24-eps and BASE24 XPNET transactions — RTLX Reactor (in 2012) for tracking
BASE24-eps & BASE24 XPNET transactions

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

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

C-Deep (Transaction Monitoring)

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

Sentinel (Nonstop Monitoring)

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

Share this:

Share this:

Share this:

Share this:

Share this:

Microsoft Excel XLS PRINCE2 spreadsheet screenshots

Share this:

Share this:

Share this: