---
title: "Appian platform licensing - CMS 2025"
ocid: "ocds-h6vhtk-059c5b"
canonical_url: "https://d3tenders.com/contract/?ocid=ocds-h6vhtk-059c5b"
markdown_url: "https://d3tenders.com/contract/ocds-h6vhtk-059c5b.md"
json_url: "https://d3tenders.com/contract/ocds-h6vhtk-059c5b.json"
source: "Find A Tender Service"
current_stage: "Award"
buyer: "THE INDEPENDENT OFFICE FOR POLICE CONDUCT"
published: "2025-09-17"
---

# Appian platform licensing - CMS 2025

Buyer: THE INDEPENDENT OFFICE FOR POLICE CONDUCT  
Current stage: Award  
OCID: ocds-h6vhtk-059c5b

[View canonical contract page](https://d3tenders.com/contract/?ocid=ocds-h6vhtk-059c5b)  
[Download OCDS JSON](https://d3tenders.com/contract/ocds-h6vhtk-059c5b.json)

## Summary

The Independent Office for Police Conduct (IOPC) has embarked on a procurement process for the renewal of Appian platform licensing, a key component of its Case Management System (CMS). This procurement, primarily focused on IT services such as consulting, software development, Internet, and support, is within the services category and is geographically located in the United Kingdom. The procurement method employed is a limited approach, entailing an award procedure without the prior publication of a call for competition. The tender, tagged under the industry classification CPV 72000000, reached an unsuccessful procurement stage on 17th September 2025. This contract aims to ensure operational continuity and to maximise the return on the strategic investment made by the IOPC in the Appian platform, despite a lack of competitive bidders in the licensing market.

This tender presents potential growth opportunities for businesses capable of providing licensing for the Appian platform independently of development services. Firms with expertise in maintaining direct enterprise relationships, offering competitive pricing, and ensuring continuity of licensing arrangements would be well-suited to meet the requirements outlined by the IOPC. The Contracting Authority's preference for separating licensing and development contracts elucidates a demand for suppliers who can manage licensing needs flexibly, thereby reducing dependency on singular vendor bundles and enhancing strategic procurement options for the IOPC. Such a model is ideal for companies that can offer scalable solutions aligned with the public sector's operational and strategic procurement objectives.

## Notice

Renewal of an existing contract with Appian for the provision of the Appian software platform upon which our Case management system is built.

### Lot Information

Lot 1

The Independent Office for Police Conduct (IOPC) has made a strategic investment in the development of its Case Management System (CMS) using the Appian platform. To continue leveraging the benefits of this investment and maximise the return on investment it is essential to maintain access to the Appian software through ongoing licensing. Appian licences are available directly from Appian or through a limited number of partners, with licencing typically bundled with development services. The IOPC has chosen to separate licensing from development to retain flexibility and avoid vendor lock-in. There is an absence of competition offering Appian licensing independently of development services and able to offer a continuation of the same licensing we currently benefit from.

### Procurement Information

The Independent Office for Police Conduct (IOPC) proposes a direct award for the renewal of Appian platform licences. This approach is based on a combination of strategic, operational, and commercial considerations that support continuity, value for money, and risk mitigation. 1. Maximising Return on Investment The IOPC has invested significantly in the development of its Case Management System (CMS) on the Appian platform. Continuing with Appian licensing ensures the organisation can fully leverage this investment, avoiding the disruption, cost, and risk associated with migrating to an alternative platform. 2. Direct Relationship with Appian The IOPC has maintained a strong and effective direct relationship with Appian over the past four years. This relationship enables direct engagement for platform and licensing queries, ensuring timely and accurate support. It is unclear whether the same level of responsiveness and direct access would be preserved if licences were procured through a third-party reseller, potentially introducing delays or communication barriers. 3. Separation of Build and Platform Contracts Suppliers that build on the Appian platform typically bundle licensing and development services into a single contract. The IOPC has deliberately avoided this model to reduce dependency on a single supplier. By separating the licensing and build contracts, the IOPC retains the flexibility to change development partners without impacting the licensing arrangement. This approach has proven effective in reducing organisational risk and remains a key principle in the ongoing procurement strategy. 4. Limited Supplier Competition Limits the potential for meaningful competition in the licensing-only market, making a direct award the most practical and commercially sound option. 5. Continuation of Current Contract Terms Appian will continue to offer the existing licensing model. This model is particularly advantageous during periods of organisational growth, as it provides predictable costs and scalability. 6. Operational Continuity Appian underpins critical operational services within the IOPC. Procuring licences directly from the platform vendor ensures continuity of service, avoids compatibility issues, and maintains compliance with existing configurations and support arrangements. 7. Strategic Procurement and Commercial Control Separating the licensing and development contracts allows the IOPC to negotiate each element independently, ensuring better commercial control, transparency, and value for money.

## Key Details

| Field | Value |
| --- | --- |
| Publication source | Find A Tender Service |
| Latest notice | https://www.find-tender.service.gov.uk/Notice/057386-2025 |
| Notice type | Award Notice |
| Procurement type | Standard |
| Procurement category | Services |
| Procurement method | Limited |
| Procurement method details | Award procedure without prior publication of a call for competition |
| Tender suitability | Not specified |
| Awardee scale | Not specified |
| All stages | Award |

## Dates

| Field | Value |
| --- | --- |
| Publication date | 17 Sep 2025 |
| Submission deadline | Not specified |
| Future notice date | Not specified |
| Award date | 17 Sep 2025 |
| Contract period | Not specified |
| Recurrence | Not specified |

## Values

| Field | Value |
| --- | --- |
| Tender value | Not specified |
| Lots value | Not specified |
| Awards value | Not specified |
| Contracts value | Not specified |

## Status

| Field | Value |
| --- | --- |
| Tender status | Unsuccessful |
| Lots status | Cancelled |
| Awards status | Unsuccessful |
| Contracts status | Not specified |

## Buyer

| Field | Value |
| --- | --- |
| Main buyer | THE INDEPENDENT OFFICE FOR POLICE CONDUCT |
| Locality | LONDON |
| Post town | East London |
| Postcode | E14 4PU |
| Country | England |
| ITL 1 | TLI London |
| ITL 2 | TLI4 Inner London - East |
| ITL 3 | TLI42 Tower Hamlets |
| Local authority | Tower Hamlets |
| Electoral ward | Canary Wharf |
| Westminster constituency | Poplar and Limehouse |
| Delivery location | Not specified |

## CPV Codes

### Divisions

- 72 - IT services: consulting, software development, Internet and support

### Codes

- 72000000 - IT services: consulting, software development, Internet and support

## Release History

- 17 Sep 2025 at 13:45 - Award - Award Notice - https://www.find-tender.service.gov.uk/Notice/057386-2025

## Notice URLs

- https://www.policeconduct.gov.uk

## Provenance

This Markdown file is an alternate public rendering of the D3 Tenders contract record. The canonical page is https://d3tenders.com/contract/?ocid=ocds-h6vhtk-059c5b. The underlying structured data is available as OCDS JSON at https://d3tenders.com/contract/ocds-h6vhtk-059c5b.json.
