The Software Partnership was a highly specialized software house in Runcorn

The Software Partnership (TSP) was a highly specialized British software house based in Runcorn, Cheshire, that played a key role in early cutting-edge electronic banking software. The firm famously developed sp/ARCHITECT-BANK, an innovative enterprise banking system built explicitly for Tandem Computers (now HPE NonStop) fault-tolerant server systems. I was based there between 1990 and 1995.

The Software Partnership Logo, Runcorn Software House, Deluxe Data
The Software Partnership Logo

Below is a detailed overview of the company’s operational history, alongside the corresponding hardware/software architectural eras of the HPE NonStop platform it relied upon.


Detailed Overview

  • Core Focus: The Software Partnership specialized in online transaction processing (OLTP) and electronic automated banking software. Long before the internet became mainstream, TSP engineered early desktop access environments for corporate bookkeeping and inter-account bank transfers.
  • Key Product: Its flagship software suite, sp/ARCHITECT, ran on Tandem’s highly unique, redundant architecture. The software handled complex high-volume retail transactions, ATM networking, and ledger balances.
  • Major Clients: High-profile financial institutions deployed TSP’s systems, including TSB (Trustee Savings Bank), Bank of Scotland, Rabobank, and Denmark’s Girofon.
  • Legacy: TSP initiated a massive lineage of financial tech operations in the Runcorn/Warrington area. After subsequent buyouts and transitions, its corporate DNA integrated into modern banking giants, eventually operating under Fidelity National Information Services (FIS).

Detailed Timeline by Era and Year

The history of TSP mirrors the evolution of the underlying fault-tolerant architecture originally built by Tandem, later managed by Compaq, HP, and currently Hewlett Packard Enterprise (HPE).

Era 1: The Tandem Founding & TSP Inception (Mid-1970s – 1989)

This era is marked by Tandem’s creation of the fault-tolerant server market, which birthed the niche that TSP filled.

  • 1974–1976: Tandem Computers is founded and ships its first 16-bit NonStop I (T/16) system, utilizing complete component redundancy to guarantee close to zero downtime for the financial industry.
  • 1981: Tandem introduces the NonStop II, transitioning to battery-backed DRAM memory and enabling early 32-bit addressing.
  • Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. It establishes offices first in Timperley (Wingate Drive), then moves to Crowngate (Norton House) in Runcorn. The team begins developing online banking architectures explicitly for Tandem OS (Guardian) and early UNIX nodes.
  • 1989: Tandem launches the NonStop Cyclone, a high-end mainframe system featuring superscalar CPUs and fiber-optic interconnects.

Era 2: The MIPS RISC Transition & Corporate Buyouts (1990 – 1999)

TSP reaches peak software deployment exactly as Tandem shifts its internal processor technology.

  • 1990: TSP establishes itself as a major regional employment hub for software engineers following a massive boom in terminal banking technology. Software programmers deploy sp/ARCHITECT-BANK code for massive retail banks internationally.
  • 1991: Tandem shifts its structural hardware away from proprietary chips, introducing its first MIPS RISC-based NonStop systems.
  • 1992: TSP expands its Runcorn footprint, moving to custom facilities at Wingate House on Northway, Runcorn.
  • 1994: TSP is acquired by American firm Deluxe Electronic Payment Systems (a division of Deluxe Corporation, one of the largest check printers and transaction processors in the US). The corporate name transitions to Deluxe Data.
  • 1997: Due to shifts in the enterprise hardware landscape, Compaq Computer Corporation acquires Tandem Computers for $3 billion, taking over the NonStop lineage.

Era 3: The Itanium Migration & eFunds Realignment (2000 – 2013)

The architecture sheds its proprietary processors for industry standards, and TSP’s corporate legacy transforms.

  • 2000: Deluxe Data’s electronic payment wing splits off and rebrands as EFD eFunds.
  • 2001–2002: HP (Hewlett-Packard) merges with Compaq, absorbing the NonStop portfolio. Simultaneously, HP begins shifting NonStop servers from MIPS architectures to Intel Itanium processors.
  • 2007: Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.

Era 4: The Modern HPE NonStop X & Virtualization Era (2014 – Present)

The legacy of the high-availability software pioneered in Runcorn culminates in cloud and x86 integration.

  • 2014: HP introduces NonStop X, completely migrating the underlying architecture to Intel x86-64 processors and implementing InfiniBand connectivity fabrics.
  • 2015: Hewlett-Packard officially splits into two entities; the core mission-critical banking platform continues its five-decade lineage under Hewlett Packard Enterprise (HPE).
  • 2020s–Present: HPE modernizes the software architecture to support Virtualized NonStop Software (vNS). Modern variants allow banking systems to run mission-critical apps seamlessly inside enterprise private clouds and scalable HPE GreenLake consumption models with 100% fault tolerance.
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire

⚙️ sp/ARCHITECT

sp/ARCHITECT (specifically sp/ARCHITECT-BANK) was a foundational electronic banking and transaction framework engineered in the 1990s by The Software Partnership (a UK-based fintech house later acquired by Deluxe Data). It primarily powered corporate banking portals and telephone-driven banking services.

The platform acted as highly reliable middleware, serving as a bridge between the customer and back-end banking mainframes. The breakdown of its architecture, infrastructure, and core functions includes:

⚙️ Architectural Breakdown

  • Hardware & OS: Built to run natively on fault-tolerant Tandem NonStop computers (now HPE NonStop). This “shared-nothing” architecture was designed for absolute transactional uptime and zero data loss.
  • Programming Languages: Built using legacy enterprise standards. Code was primarily written in COBOL85 and TAL (Transaction Application Language) native to the Tandem ecosystem.
  • Middleware Integration: Utilized Tandem-specific middleware like Pathway and Remote Server Call (RSC) to handle client-to-host communications.

💻 Core Capabilities & Modules

  • Electronic Delivery Framework: Served as a multi-channel framework, accommodating a wide variety of early access devices like desktop clients, UNIX workstations, and smart phones.
  • Transaction Handlers: Deployed custom scripts/handlers that enabled end-users to securely access real-time account data and perform early inter-account transfers without visiting a physical branch.
  • Testing Utilities: Included proprietary simulation tools like sp/TESTBED, acting as a PC-to-host test harness so developers could emulate user queries and transaction flows.

🏦 Industry Footprint

  • European Rollout: Heavily adopted by large European financial institutions, including TSB, Rabobank, Bank of Scotland, and Girofon.
  • BBM II Integration: Powered landmark corporate desktop banking solutions like Barclays Business Master II (BBM II), long before modern web browser banking existed.
  • Evolution: Following its acquisition, its design philosophies eventually evolved into Deluxe Data’s broader CONNEX suite of payment solutions.

Capgemini Engagement Manager is a senior-level, client-facing role

A Capgemini Engagement Manager is a senior-level, client-facing role responsible for end-to-end delivery of complex business and technology transformation programs. They bridge strategy and execution, acting as a trusted advisor to clients while maintaining operational and financial control over projects.

Mark Whitfield PM, Capgemini Engagement Manager from 2016
Engagement Manager, from 2016

Key Responsibilities

  • End-to-End Delivery: Overseeing projects from start to finish, ensuring milestones, SLAs, and contractual obligations are met on time and within budget.
  • Financial Accountability: Managing project budgets, revenue tracking, forecasting, invoicing, and contract compliance.
  • Stakeholder Management: Acting as the primary client point of contact while aligning cross-functional and globally distributed delivery teams.
  • Risk & Governance: Identifying potential roadblocks, proactively managing risks, and ensuring strict adherence to project governance standards.
  • Business Growth: Spotting opportunities for additional business and supporting bid activities for account expansion.
Mark Whitfield, Engagement Management EM Level 2 Exam Passed 2017
Mark Whitfield, Engagement Management EM Level 2 Exam Passed 2017

Ideal Candidate Profile

  • Experience: Typically requires a degree in Business, Engineering, or IT, combined with at least 5+ years of experience in project management or service delivery within a B2B environment.
  • Skills: Strong commercial acumen, proficiency in formal methodologies (e.g., Agile, ITIL), and the ability to lead diverse, multinational teams.
C&CA UK's Communications & Engagement Award Winner 2022, Cloud & Custom Applications, Mark Whitfield
C&CA UK’s Communications & Engagement Award Winner 2022, Cloud & Custom Applications, Mark Whitfield

Explore current vacancies and learn more about the EM community through the Capgemini Careers Portal or their specific Engagement Management Careers overview.

Capgemini Engagement Manager, from 2016.

Capgemini Campus – Serge Kampf Les Fontaines, Chantilly, France – Advanced Engagement Management Course – November 2017 Class – 2nd from left, Mark Whitfield
Capgemini Campus – Serge Kampf Les Fontaines, Chantilly, France – Advanced Engagement Management Course – November 2017 Class – 2nd from left

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.
HPE NonStop article by Mark Whitfield in 2013, working for Insider Technologies Limited in Salford Quays

Functional BA vs Technical BA vs Product BA

Functional BA vs Technical BA vs Product BA
Functional BA vs Technical BA vs Product BA

While all three roles fall under the “Business Analyst” umbrella, they differ in their primary focus: Functional BAs translate business needs into user requirements, Technical BAs focus on system architecture and integration, and Product BAs drive the product’s market value and long-term strategy.

1. Functional BA (The ‘Business’ Translator)

The Functional BA acts as the primary bridge between business stakeholders and the IT delivery team. They focus on what the business needs to achieve and how users will interact with the system.

  • Core Focus: Business processes, stakeholder communication, and end-user experience.
  • Day-to-day Responsibilities: Gathering requirements, mapping out user journeys, defining acceptance criteria, and creating process flow diagrams.
  • Key Skills: Stakeholder management, requirements elicitation, and deep domain knowledge (e.g., finance, healthcare).

2. Technical BA (The ‘System’ Architect)

The Technical BA bridges the gap between the functional requirements and the software development team. They focus on how the system will be built, ensuring the proposed solution is technically feasible, scalable, and secure.

  • Core Focus: System architecture, data flow, integrations, and non-functional requirements (like performance).
  • Day-to-day Responsibilities: Defining API structures, mapping data models, documenting system interfaces, and writing complex technical user stories.
  • Key Skills: Understanding of system integrations, database structures, basic coding logic, and system-to-system communication.

3. Product BA (The ‘Value’ Strategist)

The Product BA merges business analysis with product management principles. Rather than just fulfilling requested requirements, they focus on why a product or feature should be built, ensuring it aligns with overarching company goals and delivers tangible ROI.

  • Core Focus: Product strategy, feature prioritization, market viability, and user adoption.
  • Day-to-day Responsibilities: Conducting market research, managing the product backlog, defining Key Performance Indicators (KPIs), and analyzing user feedback/metrics.
  • Key Skills: Product discovery, data analysis, competitive analysis, and strategic roadmapping.

PMBOK Guide 8th Edition

PMBOK Guide 8th Edition
PMBOK Guide 8th Edition

The PMBOK Guide 8th Edition is an integrated, value-driven framework that bridges the high-level principles of the 7th edition with the practical, process-oriented structure of older editions. It reintroduces 40 non-prescriptive processes alongside six core principles and seven performance domains.

📚 The Structure: Two Books in One

Similar to its predecessors, the printed volume of the 8th Edition includes two integrated publications:

  1. The Standard for Project Management: An official ANSI standard that focuses on strategic alignment, value delivery systems, and global applicability.
  2. A Guide to the Project Management Body of Knowledge (PMBOK Guide): The practical handbook containing the processes, tools, techniques, and tailoring considerations.

🟢 The 6 Core Principles

The 8th Edition streamlines the 12 principles from the 7th edition into six actionable pillars designed to guide professional behavior and mindset:

  • Adopt a Holistic View: Think in terms of systems and understand how a project integrates with organizational strategy.
  • Focus on Value: Direct efforts toward long-term outcomes and net-positive benefits rather than just output production.
  • Build Accountable Leadership: Cultivate a culture of transparency, clear responsibilities, and high-performance teamwork.
  • Embed Quality: Ensure quality processes and continuous improvement are woven into every phase of the work.
  • Integrate Sustainability: Consider the long-term environmental, social, and economic impacts of project delivery.
  • Build Empowered Teams: Foster environments where team members are supported, trusted, and empowered to solve problems.

🔵 The 7 Performance Domains

These represent key areas of practice, serving as the technical “what” of your project:

  1. Governance: Setting the rules, decision frameworks, and oversight mechanisms.
  2. Scope: Defining boundaries, deliverables, and requirements.
  3. Schedule: Managing timeframes, milestones, and critical paths.
  4. Finance: Budgeting, forecasting, and cost management.
  5. Stakeholders: Managing expectations, engagement, and communications.
  6. Resources: Allocating people, equipment, and physical/material assets.
  7. Risks: Identifying, analyzing, and mitigating uncertainties.

🟠 The 40 Evolved Processes & Focus Areas

A highly praised update in the 8th edition is the return of process guidance. To offer structured “how-to” guidance without becoming rigid, the processes are grouped into five Focus Areas (replacing the traditional Process Groups):

  • Initiating
  • Planning
  • Executing
  • Monitoring & Controlling
  • Closing

Across these five focus areas, there are 40 non-prescriptive processes that detail the typical inputs, tools, techniques, and outputs (ITTOs). The guide includes explicit tailoring advice on how to adapt these processes for predictive, hybrid, and agile environments.


💡 Key Modern Additions

Reflecting over 48,000 global practitioner data points, the 8th Edition expands coverage into modern project environments:

  • Artificial Intelligence (AI): Guidance on using AI and data analytics in project management.
  • Project Management Offices (PMOs): Expanded focus on PMO structures and strategic value alignment.
  • Procurement & Contracting: Modernized contracting types, dispute resolution, and vendor management.

📝 PMP Exam Note

If you are planning to take the PMP exam, make sure to check the official PMI PMP Certification Overview for the most up-to-date Exam Content Outline (ECO). The exam relies heavily on the ECO, and the 8th Edition guide serves as foundational reference material.

Business Analysis (BA) from week to week, across an example project

Business Analysis (BA) from week to week, across an example project
Business Analysis (BA) from week to week, across an example project

Another example;

Business Analysis (BA) across an example project—like building a custom mobile app—follows a dynamic, week-to-week lifecycle. It shifts focus from initial high-level strategy and stakeholder alignment to granular requirements, testing support, and post-launch evaluation.

Here is how a typical BA lifecycle breaks down across an example 8-week project timeline:

Week 1: Project Kickoff & Discovery

  • Focus: Understanding the business problem and setting boundaries.
  • Activities:
    • Facilitating kickoff workshops with key stakeholders.
    • Creating a Business Case or Vision Document to define the “why.”
    • Identifying key project sponsors, users, and subject matter experts (SMEs).

Week 2: Stakeholder Engagement & Elicitation

  • Focus: Extracting needs from the people who matter.
  • Activities:
    • Conducting interviews, surveys, and Focus Groups to gather initial wants and needs.
    • Mapping out high-level Business Processes (current “As-Is” workflows and future “To-Be” workflows).

Week 3: Analysis & Requirements Definition

  • Focus: Turning raw data into structured requirements.
  • Activities:
    • Writing user stories and establishing Acceptance Criteria (often using the Given-When-Then format).
    • Creating documentation like process models, wireframes, and data dictionaries.

Week 4: Prioritization & Scope Management

  • Focus: Deciding what gets built first.
  • Activities:
    • Facilitating prioritization sessions using frameworks like the MoSCoW Method (Must have, Should have, Could have, Won’t have).
    • Defining the Minimum Viable Product (MVP) to prevent scope creep.

Week 5: Backlog Refinement & Solution Design

  • Focus: Preparing work for the development team.
  • Activities:
    • Refining the product backlog alongside the Product Owner.
    • Working directly with UI/UX designers and technical architects to ensure designs align with business rules.

Week 6: Development Support & Clarification

  • Focus: Answering daily questions and unblocking the team.
  • Activities:
    • Hosting Agile ceremonies like Sprint Planning and Daily Stand-ups.
    • Clarifying edge cases and adjusting requirements if technical constraints arise during development.

Week 7: Testing & Validation

  • Focus: Ensuring the solution works and meets business needs.
  • Activities:
    • Assisting Quality Assurance (QA) teams by explaining acceptance criteria.
    • Facilitating User Acceptance Testing (UAT) with real business users to sign off on the software.

Week 8: Deployment & Post-Implementation Review

  • Focus: Launching the product and measuring success.
  • Activities:
    • Helping prepare training materials, user manuals, and release notes.
    • Conducting a Retrospective to identify process improvements for the next project phase.

Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner

Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner specializing in digital transformation, Microsoft Dynamics 365, and Power Platform solutions.

Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner
Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner

Headquartered in Cheadle, Cheshire, the company delivers expert solution architecture, implementation, and managed support to public and private sector organizations.

Executive Staff & Leadership

  • Kieran Gerard Holmes: Director and Principal Solution Architect. A senior Microsoft expert with certifications across Dynamics 365, Power Platform, and Microsoft AI.
  • Wider Consulting Team: The company is built around a close-knit, highly qualified team of Microsoft Certified Professionals (MCPs) and Solutions Architects who focus on mid-market and enterprise digital change.
NHS, End User Services
NHS, End User Services

Timeline Breakdown by Year

Centiun has grown rapidly in the cloud and AI solutions space. Key milestones include:

  • 2025 (Company Foundation & Initial Certifications)
    • October 30, 2025: Centiun Limited was officially incorporated, establishing its registered headquarters at Cheadle Royal Business Park in Cheshire.
    • Late 2025: Secured nationally recognized Cyber Essentials certification and completed registration with the Information Commissioner’s Office (ICO) for secure data management compliance.
    • Late 2025: Began publishing specialized insight articles focused on legacy app modernization and driving intelligent, data-driven decisions via Microsoft Power BI.
  • 2026 (Expansion & AI Solutions)
    • Early 2026: Positioned itself as a strategic Microsoft SME partner providing personalized digital transformations, cloud migrations, and technical governance.
    • Spring 2026: Expanded consulting efforts into “Agentic Customer Experience (CX)”—advising organizations on how to implement Microsoft Copilot, AI agents, and Dynamics 365 Contact Center workflows.
    • Spring/Summer 2026: Continued to build digital footprints across public bodies, healthcare, non-profit, and financial services sectors.

To explore how their architects can assist with your Microsoft transformations, request a consultation or view their technology resources on the Centiun website.

Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner
Centiun is a UK-based IT consultancy and Microsoft AI Cloud Partner