Mark Whitfield, Senior Project Manager, Career Summary

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

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

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

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

Project Management Career Breakdown:

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

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

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

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

3. Professional Services Banking Delivery (2013–2014)

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

4. Digital Sportsbook Transformation (2014–2016)

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

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

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

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

Mark Whitfield HPE NonStop Tandem Experience over three decades

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

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

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

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

1990–1995: Early Programming

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

1995–2013: Senior Development & Product Management

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

Spinnaker Court, Chandlers Point, Insider Technologies, Salford Quays, Manchester, UK — Insider Technologies, Salford Quays, Manchester, UK

2013–2014: Legacy Migration & Consulting

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

Diebold Nixdorf Ltd, Cain Rd, Binfield, Bracknell, RG12 1WP — Diebold Nixdorf Ltd, Cain Rd,
Binfield, Bracknell, RG12 1WP

2016–Present: Cloud Transformation & Digital Delivery

Location: Capgemini UK, Trafford Quays / UK-Wide
Focus: Delivery of enterprise-scale middleware, digital transformation, and cloud.
Projects: Acts as an Engagement Manager and SC-Cleared Project Manager. Focus includes Agile software delivery for Air Traffic organisations (e.g., iOS applications for military and public-facing airspace tracking) and rolling out middleware solutions.

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

C&CA UK's Communications & Engagement Award Winner 2022 - Cloud & Custom Applications - Capgemini UK — C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK

For more career detail, click here.

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

Salesforce MuleSoft Overview & Development Timeline

Salesforce MuleSoft is an industry-leading Integration Platform as a Service (iPaaS) and automation solution that enables organizations to securely connect data, applications, and devices across hybrid cloud and on-premises environments. Instead of relying on rigid, custom-coded point-to-point connections, MuleSoft uses an API-led connectivity approach. This methodology treats every system connection as a modular, reusable building block (System, Process, and Experience APIs).

From October 2018 – June 2019, I was assigned as a Delivery Manager at MuleSoft (augmented) to deliver the Anypoint Platform.

Core Capabilities

Anypoint Platform: The flagship product covering the entire lifecycle of API design, testing, deployment, governance, and monitoring.
MuleSoft Automation: A suite combining Composer (no-code integration for business teams) and Robotic Process Automation (RPA) to automate workflows across legacy and modern platforms.
Salesforce Ecosystem Synergy: Acts as the data integration engine for Salesforce Customer 360, bringing siloed third-party systems together to establish a single customer view.

Outcome Based Delivery (OBD) Model, C4E, Center for Excellence

Detailed Timeline Breakdown

The evolution of MuleSoft spans four distinct eras, progressing from a niche open-source project to an enterprise integration powerhouse, culminating in its massive acquisition and expansion under Salesforce.

Era 1: The Open-Source Roots (2003 – 2008)

This era focused on addressing the tedious “donkey work” of custom data integration through open-source software.

2003: Developer Ross Mason creates the Mule open-source project. He writes an architecture framework to move away from rigid, proprietary integration infrastructure. The project name stems from the literal “mule work” or drudgery of writing point-to-point connections.
2006: Ross Mason and Dave Rosenberg co-found MuleSource in San Francisco. The company is built to commercialize the open-source Mule Enterprise Service Bus (ESB) project.
2007: Lightspeed Venture Partners leads a Series A funding round to back the growing open-source platform.
2008: The company expands its product landscape by focusing on developer adoption and expanding core enterprise middleware features.

Era 2: Cloud Transition and iPaaS Transformation (2009 – 2016)

During this era, the company pivoted to a subscription-based software-as-a-service model, targeting cloud applications and APIs.

2009: The company officially changes its name from MuleSource to MuleSoft. Greg Schott is hired as CEO to restructure the business, transitioning from a pure open-source model to a hybrid commercial enterprise subscription model.
2010: The development of dedicated cloud tools kicks off, responding to a massive industry shift from on-premises systems toward software-as-a-service (SaaS) applications.
2012: MuleSoft launches CloudHub, the industry’s first true multi-tenant Integration Platform as a Service (iPaaS).
2013: MuleSoft acquires ProgrammableWeb, the leading repository for web application programming interfaces (APIs), positioning itself as the voice of the emerging API economy.
2014: The company officially rolls out the Anypoint Platform, a unified product suite designed to dismantle the barriers between data applications, SaaS platforms, and APIs.
2015: MuleSoft secures a $128 million funding round led by New Enterprise Associates, with Salesforce Ventures participating as a strategic investor. Revenue breaks past the $100 million mark.
2016: The enterprise focus shifts entirely toward championing API-led connectivity over standard enterprise service bus middleware architectures.

Era 3: IPO and the Salesforce Acquisition (2017 – 2018)

The era defined by rapid financial maturation and a landmark enterprise SaaS consolidation.

2017: MuleSoft launches its Initial Public Offering (IPO) on the New York Stock Exchange under the ticker symbol MULE, valuing the business at over $1.5 billion on its first day of trading.
2018 (March): Salesforce announces a definitive agreement to acquire MuleSoft for an enterprise value of approximately $6.5 billion, making it Salesforce’s largest acquisition up to that point.
2018 (May): Salesforce completes the acquisition. MuleSoft is positioned to power the new Salesforce Integration Cloud to unlock legacy and external database silos for CRM clients.

Era 4: Modern Era—Automation and Unified Customer 360 (2019 – Present)

This era represents the deep technological coupling of MuleSoft with cloud architecture, AI, and low-code applications.

2019: Salesforce shifts strategy, abandoning the “Integration Cloud” branding to lean heavily on the trusted MuleSoft brand. The technology is deeply embedded directly into core platforms like Sales and Service Clouds.
2020: MuleSoft updates its core data engine engine with Mule 4, optimizing performance, reducing custom script overhead, and easing API lifecycle management workflows.
2021: The brand releases MuleSoft Composer, a click-based, no-code application integrated directly inside the Salesforce user interface, enabling business users to connect systems without relying on IT engineers.
2022: Salesforce expands MuleSoft’s reach beyond APIs by acquiring Servicetrace and launching MuleSoft RPA, building a comprehensive hyper-automation ecosystem alongside Composer.
2023–2024: MuleSoft adapts to the AI revolution by releasing Anypoint Code Builder and embedding Einstein AI into the workflow. Developers use natural language prompts to automatically generate integration flows and API designs.
2025–2026: MuleSoft is fully integrated as a core architectural foundation for Salesforce Data Cloud and Agentforce. It serves as the primary system of connectivity to securely feed legacy, real-time enterprise data into autonomous AI agents.

Salesforce MuleSoft Overview & Development Timeline

2. Welcome Salesforce, London Office external — 2. Welcome Salesforce, London Office (external)

HPE NonStop Tandem Programming Languages and Development Timeline

The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.

Detailed List of NonStop Programming Languages

1. Core Proprietary & System Languages

TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.

2. Enterprise & Enterprise Legacy Languages

COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.

3. Standard Mainstream Languages

C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.

4. Modern Open-Source Options

Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.

Detailed Timeline Breakdown by Era and Year

The evolution of NonStop languages maps directly across distinct engineering ownership eras.

The Proprietary Foundation Era (Tandem Computers: 1974–1989)

1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.

The Open Systems & Hardware Transition Era (Compaq: 1990–2001)

1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.

The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)

2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.

The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)

2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.

HPE NonStop Tandem Programming Languages and Development Timeline

Popular Computing Weekly British Computer Magazine from 1982 thru 1990

Popular Computing Weekly (frequently abbreviated as PCW) was a highly influential British computer magazine published from 23 April 1982 to 14 June 1990.

Launched by Sunshine Publications and led by founding editor Duncan Scot, it stood out by providing rapid-fire weekly news, hardware reviews, type-in software programs, and gaming coverage at the height of the UK’s home microcomputer boom.

Over its eight-year lifespan, it produced 415 issues, adapting its identity from a broad hobbyist guide to a gaming-centric publication before closing in the early 1990s.

Magazine Overview & Core Elements

Unlike glossy monthly publications such as Personal Computer World or Your Computer, Popular Computing Weekly acted as a fast-paced “newspaper” for the UK micro community. Because it hit newsagent shelves every seven days, it could report on dramatic price drops, industry buyouts, and hardware delays weeks before monthly rivals.

The magazine catered to a wide array of early systems, including the ZX Spectrum, Commodore 64, BBC Micro, Amstrad CPC, Atari 8-bit, Dragon 32, VIC-20, and later the 16-bit machines. Its format generally consisted of:

News Desk: Urgent industry reporting, micro-market trade wars, and launch delays.
Hardware and Software Reviews: Critical evaluations of new home computers and software titles.
Type-In Listings: Pages of raw BASIC or Machine Code that readers meticulously copied into their systems to run games and utilities.
Gaming Coverage & Puzzles: Dedicated spaces for arcade game high scores, maps, and adventure hints.

Detailed Timeline Breakdown (1982–1985)

1982: Launch and the 8-Bit Explosion

April: On 23 April 1982, Issue 1 was published by London-based Sunshine Publications. The launch editor, Duncan Scot, managed the first 8 issues before handing the reins over to Brendon Gore.
May–June: The magazine’s debut directly coincided with Sir Clive Sinclair’s unveiling of the ZX Spectrum. Popular Computing Weekly quickly positioned itself as a critical hub for Spectrum and BBC Micro setup guides and technical support.
System Agnosticism: Early volumes accommodated a highly fractured market, including type-in listings for the ZX81, VIC-20, Acorn Atom, TRS-80, and early Apple II systems.
Cover Price: The early issues cost just 30p.

1983: Price Wars and Rising Circulation

The Boom Year: Home computing exploded in the UK. PCW capitalised on its fast turnaround to report on brutal, ongoing price slashes initiated by Commodore, Sinclair, and Atari.
Market Diversification: Content expanded heavily to track new contenders like the Oric-1, Dragon 32, and the newly launched Commodore 64.
Commercialisation: Software companies grew rapidly. Advertising pages surged with multi-page spreads from early publishing giants like Imagine Software, Ocean Software, and Ultimate Play The Game.

1984: Amstrad’s Arrival and Market Shocks

April: The magazine closely documented Alan Sugar’s entry into the computer market with the Amstrad CPC 464, which changed the landscape by packaging a computer, keyboard, and monitor into an all-in-one unit.
The Crash Warning: PCW reported extensively on the high-profile financial collapse of Imagine Software and structural corrections across the British software industry.
The MSX Standard: The magazine devoted substantial print space to tracking the arrival of Japanese MSX standard computers (such as Toshiba’s HX-10) attempting to break into the UK.

1985: Transition to 16-Bit and Gaming Domination

January: The magazine followed the rocky release of the business-oriented Sinclair QL and the debut of the dual-mode Commodore 128.
May: The news desk shifted focus to the 16-bit horizon, tracking early announcements for the Atari 520ST and Commodore Amiga.
Pricing: Driven by inflation and increased page counts, the cover price rose to 40p.
Software Pivot: As users grew tired of typing in complex code by hand, the publication reduced its raw code listings and pivoted towards dedicated, full-colour video game previews, software reviews, and maps.

Post-Early Eighties Legacy (1986–1990)

Beyond its golden era, the publication continued to evolve through the late 1980s. By 1989, regular home micro content declined as the industry consolidated around IBM-compatible PCs, the Amiga, and the Atari ST. To compensate for falling sales, PCW incorporated Computer Gamesweek in 1989, morphing almost entirely into a video games magazine.

1. Popular Computing Weekly British Computer Magazine from 1982 thru 1990

2. Popular Computing Weekly British Computer Magazine

Sunshine Publications eventually closed the magazine on 14 June 1990 with its 415th issue, ending its run as a primary historical record of the 1980s British microcomputing phenomenon.

Mark Whitfield – Senior Project Manager – training received

Mark Whitfield, an SC cleared Senior Project Manager based in the Manchester area, has over 30 years of experience transitioning from a software engineer to an IT program leader.

His extensive technical and project management training spans methodologies, cloud infrastructure, and software applications.

A detailed breakdown of his training, certifications, and academic background includes:

Project Management Methodologies

PRINCE2 Practitioner: Certified via the ILX Group.
Agile SCRUM: Trained in-house with RADTAC.
Advanced Engagement Management: Level 2 certification completed via Capgemini.
Project Fundamentals: Completed “Fundamentals of Successful Project Management” and “Managing Multiple Projects” via Skillpath.
Microsoft Project: Microsoft Project ’98 certified.

Technical & Cloud Training

Microsoft Azure: AZ-900 Microsoft Certified Azure Fundamentals.
MuleSoft: Completed outcome-based delivery training and is a specialized Delivery Manager.
Technical Programming: Includes foundational database and software language training, such as C++ and MS SQL 2000 query training, as well as VPS and Tandem (HPE NonStop) technical/development courses.
Productivity: Completed Microsoft Excel Refresher and Expert skills training (Udemy and Microsoft).

Formal Education

Higher National Diploma (HND): Graduated with a Distinction (top) in Computing (1990).

You can review his detailed credential breakdown on the PROject Templates Professional Training Page.

HPE NonStop architecture (Tandem Computers) by Era and Year

Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:

1. The Tandem Founding Era (1976–1981)

Years: 1976–1981
Processors: Proprietary 16-bit stack processors (e.g., Tandem/16, NonStop II)
Architecture: The foundational “shared-nothing” parallel architecture. Featured redundant components (processors, disks, power supplies) connected by a proprietary dual-bus (Dynabus). The operating system provided instant automated failover.

2. The Cyclone & Early RISC Era (1981–1996)

Years: 1981–1996
Processors: Proprietary non-RISC (NonStop Cyclone) & MIPS R-series RISC
Architecture: Expanded into 32-bit computing. To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while heavily emulating the original instruction set for compatibility.

3. The Himalaya/ServerNet Era (1997–2004)

Years: 1997–2004
Processors: MIPS R-series
Architecture: Replaced the legacy Dynabus with ServerNet, a high-speed system interconnect that served as an early precursor to modern networking fabrics. (Compaq acquired Tandem in 1997, which subsequently merged with HP in 2002).

4. The Integrity Itanium Era (2005–2013)

Years: 2005–2013
Processors: Intel Itanium (TNS/E)
Architecture: Branded as HP Integrity NonStop (NonStop i). The platform moved off proprietary silicon to standard Intel Itanium processors. This was driven by the “NonStop Advanced Architecture” (NSAA), lowering hardware costs while maintaining Availability Level 4 (AL4) standards.

5. The NonStop X (x86-64) Era (2014–Present)

Years: 2014–2026
Processors: Intel Xeon x86-64 (TNS/X)
Architecture: Fully decoupled the OS from proprietary hardware by shifting to standard Intel x86-64 processors and InfiniBand fabric. The latest compute nodes (such as the NS5 X5 and NS9 X5) utilize modern Intel Xeon Scalable processors to maintain maximum Availability Level 4 (AL4) workloads.

6. The Virtualized NonStop Era (Present)

Years: 2015–Present
Processors: Virtual Machines / Cloud / x86
Architecture: HPE extended the platform to support Virtualized NonStop Software, allowing fault-tolerant enterprise workloads to run entirely in private clouds via standard VMware or hybrid architectures, independent of specific physical servers.

Globally published HP NonStop journal – ‘The Connection’

HPE NonStop article by Mark Whitfield in 2013, working for Insider Technologies Limited in Salford Quays

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this: