{ "uri": "https://www.find-tender.service.gov.uk/api/1.0/ocdsRecordPackages/ocds-h6vhtk-068c6d", "publisher": { "name": "Cabinet Office", "scheme": "GB-GOR", "uid": "D2", "uri": "https://www.gov.uk/government/organisations/cabinet-office" }, "publishedDate": "2026-04-28T11:18:50+01:00", "license": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/", "publicationPolicy": "https://www.gov.uk/government/publications/open-contracting", "version": "1.1", "extensions": [ "https://standard.open-contracting.org/profiles/eu/latest/en/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_amendment_rationale_classifications_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_budget_breakdown_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_contract_completion_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_documentation_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_pagination_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_suitability_extension/master/extension.json", "https://raw.githubusercontent.com/portaledcahn/ocds_Links_extension/main/extension.json", "https://raw.githubusercontent.com/cabinetoffice/ocds_uk_extension/main/extension.json" ], "packages": [ "https://www.find-tender.service.gov.uk/api/1.0/ocdsRecordPackages/ocds-h6vhtk-068c6d" ], "records": [ { "ocid": "ocds-h6vhtk-068c6d", "releases": [ { "ocid": "ocds-h6vhtk-068c6d", "id": "038431-2026", "tag": [ "planning" ], "date": "2026-04-28T11:18:50+01:00", "initiationType": "tender", "parties": [ { "name": "Transport for Greater Manchester", "id": "GB-PPON-PNJQ-2746-NWYT", "identifier": { "scheme": "GB-PPON", "id": "PNJQ-2746-NWYT" }, "address": { "streetAddress": "2 Piccadilly Place", "locality": "Manchester", "postalCode": "M1 3BG", "country": "GB", "countryName": "United Kingdom", "region": "UKD33" }, "contactPoint": { "email": "procurement@tfgm.com" }, "roles": [ "buyer" ], "details": { "url": "https://tfgm.com", "classifications": [ { "scheme": "UK_CA_TYPE", "id": "publicAuthoritySubCentralGovernment", "description": "Public authority - sub-central government" } ] } } ], "buyer": { "id": "GB-PPON-PNJQ-2746-NWYT", "name": "Transport for Greater Manchester" }, "planning": { "milestones": [ { "id": "engagement", "type": "engagement", "description": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms.", "dueDate": "2026-05-29T23:59:59+01:00", "status": "scheduled" } ], "documents": [ { "id": "038431-2026", "documentType": "marketEngagementNotice", "noticeType": "UK2", "description": "Preliminary market engagement notice on Find a Tender", "url": "https://www.find-tender.service.gov.uk/Notice/038431-2026", "datePublished": "2026-04-28T11:18:50+01:00", "format": "text/html" } ] }, "tender": { "id": "ocds-h6vhtk-068c6d", "legalBasis": { "id": "2023/54", "scheme": "UKPGA", "uri": "https://www.legislation.gov.uk/ukpga/2023/54/contents" }, "title": "Supporting Transport for Greater Manchester in Shaping a TfGM Owned Unified Data Model (UDM)", "description": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nStrategic Context\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nUnified Data Model (UDM) - Current Thinking\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nRelationship to Vendor Provided Solutions\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nBusiness Drivers and Challenges\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nPurpose of this Market Engagement\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nWhat TfGM Is Asking the Market to Respond To\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms.\nNext Steps\nFeedback from this market engagement will be used to inform TfGM's future strategy, roadmap and potential commissioning of advisory or delivery support for building a strong data foundation.\nParticipation in this engagement does not guarantee involvement in any subsequent procurement.", "items": [ { "id": "1", "additionalClassifications": [ { "scheme": "CPV", "id": "48000000", "description": "Software package and information systems" }, { "scheme": "CPV", "id": "72000000", "description": "IT services: consulting, software development, Internet and support" } ], "deliveryAddresses": [ { "region": "UK", "country": "GB", "countryName": "United Kingdom" } ], "relatedLot": "1" } ], "value": { "amountGross": 200000, "currency": "GBP" }, "mainProcurementCategory": "services", "aboveThreshold": false, "lots": [ { "id": "1", "suitability": { "sme": true }, "contractPeriod": { "startDate": "2026-08-01T00:00:00+01:00", "endDate": "2027-01-01T23:59:59Z" }, "status": "planning" } ], "status": "planning" }, "language": "en", "extensions": [ "https://standard.open-contracting.org/profiles/eu/latest/en/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_amendment_rationale_classifications_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_budget_breakdown_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_contract_completion_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_documentation_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_pagination_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_suitability_extension/master/extension.json", "https://raw.githubusercontent.com/portaledcahn/ocds_Links_extension/main/extension.json", "https://raw.githubusercontent.com/cabinetoffice/ocds_uk_extension/main/extension.json" ] } ], "compiledRelease": { "tag": [ "compiled" ], "id": "ocds-h6vhtk-068c6d-2026-04-28T11:18:50+01:00", "date": "2026-04-28T11:18:50+01:00", "ocid": "ocds-h6vhtk-068c6d", "initiationType": "tender", "parties": [ { "id": "GB-PPON-PNJQ-2746-NWYT", "name": "Transport for Greater Manchester", "identifier": { "scheme": "GB-PPON", "id": "PNJQ-2746-NWYT" }, "address": { "streetAddress": "2 Piccadilly Place", "locality": "Manchester", "postalCode": "M1 3BG", "country": "GB", "countryName": "United Kingdom", "region": "UKD33" }, "contactPoint": { "email": "procurement@tfgm.com" }, "roles": [ "buyer" ], "details": { "url": "https://tfgm.com", "classifications": [ { "scheme": "UK_CA_TYPE", "id": "publicAuthoritySubCentralGovernment", "description": "Public authority - sub-central government" } ] } } ], "buyer": { "id": "GB-PPON-PNJQ-2746-NWYT", "name": "Transport for Greater Manchester" }, "planning": { "milestones": [ { "id": "engagement", "type": "engagement", "description": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms.", "dueDate": "2026-05-29T23:59:59+01:00", "status": "scheduled" } ], "documents": [ { "id": "038431-2026", "documentType": "marketEngagementNotice", "noticeType": "UK2", "description": "Preliminary market engagement notice on Find a Tender", "url": "https://www.find-tender.service.gov.uk/Notice/038431-2026", "datePublished": "2026-04-28T11:18:50+01:00", "format": "text/html" } ] }, "tender": { "id": "ocds-h6vhtk-068c6d", "legalBasis": { "id": "2023/54", "scheme": "UKPGA", "uri": "https://www.legislation.gov.uk/ukpga/2023/54/contents" }, "title": "Supporting Transport for Greater Manchester in Shaping a TfGM Owned Unified Data Model (UDM)", "description": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nStrategic Context\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nUnified Data Model (UDM) - Current Thinking\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nRelationship to Vendor Provided Solutions\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nBusiness Drivers and Challenges\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nPurpose of this Market Engagement\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nWhat TfGM Is Asking the Market to Respond To\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms.\nNext Steps\nFeedback from this market engagement will be used to inform TfGM's future strategy, roadmap and potential commissioning of advisory or delivery support for building a strong data foundation.\nParticipation in this engagement does not guarantee involvement in any subsequent procurement.", "items": [ { "id": "1", "additionalClassifications": [ { "scheme": "CPV", "id": "48000000", "description": "Software package and information systems" }, { "scheme": "CPV", "id": "72000000", "description": "IT services: consulting, software development, Internet and support" } ], "deliveryAddresses": [ { "region": "UK", "country": "GB", "countryName": "United Kingdom" } ], "relatedLot": "1" } ], "value": { "amountGross": 200000, "currency": "GBP" }, "mainProcurementCategory": "services", "aboveThreshold": false, "lots": [ { "id": "1", "suitability": { "sme": true }, "contractPeriod": { "startDate": "2026-08-01T00:00:00+01:00", "endDate": "2027-01-01T23:59:59Z" }, "status": "planning" } ], "status": "planning" }, "language": "en", "extensions": [ "https://standard.open-contracting.org/profiles/eu/latest/en/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_amendment_rationale_classifications_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_budget_breakdown_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_contract_completion_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_documentation_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_pagination_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_suitability_extension/master/extension.json", "https://raw.githubusercontent.com/portaledcahn/ocds_Links_extension/main/extension.json", "https://raw.githubusercontent.com/cabinetoffice/ocds_uk_extension/main/extension.json" ] }, "versionedRelease": { "ocid": "ocds-h6vhtk-068c6d", "initiationType": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "tender" } ], "parties": [ { "id": "GB-PPON-PNJQ-2746-NWYT", "name": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Transport for Greater Manchester" } ], "identifier": { "scheme": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "GB-PPON" } ], "id": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "PNJQ-2746-NWYT" } ] }, "address": { "streetAddress": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2 Piccadilly Place" } ], "locality": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Manchester" } ], "postalCode": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "M1 3BG" } ], "country": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "GB" } ], "countryName": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "United Kingdom" } ], "region": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "UKD33" } ] }, "contactPoint": { "email": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "procurement@tfgm.com" } ] }, "roles": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": [ "buyer" ] } ], "details": { "url": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "https://tfgm.com" } ], "classifications": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": [ { "scheme": "UK_CA_TYPE", "id": "publicAuthoritySubCentralGovernment", "description": "Public authority - sub-central government" } ] } ] } } ], "buyer": { "id": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "GB-PPON-PNJQ-2746-NWYT" } ], "name": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Transport for Greater Manchester" } ] }, "planning": { "milestones": [ { "id": "engagement", "type": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "engagement" } ], "description": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms." } ], "dueDate": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2026-05-29T23:59:59+01:00" } ], "status": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "scheduled" } ] } ], "documents": [ { "id": "038431-2026", "documentType": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "marketEngagementNotice" } ], "noticeType": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "UK2" } ], "description": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Preliminary market engagement notice on Find a Tender" } ], "url": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "https://www.find-tender.service.gov.uk/Notice/038431-2026" } ], "datePublished": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2026-04-28T11:18:50+01:00" } ], "format": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "text/html" } ] } ] }, "tender": { "id": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "ocds-h6vhtk-068c6d" } ], "legalBasis": { "id": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2023/54" } ], "scheme": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "UKPGA" } ], "uri": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "https://www.legislation.gov.uk/ukpga/2023/54/contents" } ] }, "title": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Supporting Transport for Greater Manchester in Shaping a TfGM Owned Unified Data Model (UDM)" } ], "description": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "Transport for Greater Manchester (TfGM) is seeking to engage with the market to inform the development of a TfGM owned Unified Data Model (UDM) that will provide a robust, reusable data foundation for the Bee Network and wider organisational needs.\nTfGM manages a complex, multi modal transport network covering highways, bus, tram, and active travel, supported by a diverse technology estate and multiple third party suppliers. TfGM is increasingly dependent on timely, reliable and coherent data to support operational decision making, performance management, planning, and future digital capabilities.\nThis engagement seeks to draw on market experience and expertise to help TfGM refine its thinking, validate assumptions, and shape a sustainable approach to developing and governing a UDM that can meet both current and future business objectives.\nStrategic Context\nTfGM has defined three strategic objectives for the Bee Network and the wider organisation by 2030:\n1.\tCreate a single view of the transport network across modes and operational domains\n2.\tEstablish a single source of truth for operational, performance and asset information\n3.\tDevelop a digital twin capability to support planning, simulation and assurance\nTfGM recognises that achieving these objectives requires a strong and coherent data foundation, rather than a dependence on individual systems or suppliers.\nA TfGM owned Unified Data Model is being explored as a key enabler that can:\n•\tProvide a canonical representation of the transport network and its components\n•\tSupport consistent interpretation of data across systems and functional areas\n•\tEnable reuse of data across operational, analytical and strategic use cases\n•\tUnderpin digital twin capabilities over time\nUnified Data Model (UDM) - Current Thinking\nTfGM is exploring the establishment of a TfGM owned and governed Unified Data Model, defined at a conceptual and logical level, independent of any single vendor or technology.\nKey principles being considered include:\n•\tThe UDM represents core network entities, events, states and relationships in a consistent and extensible way\n•\tIt acts as a canonical or reference model, against which data from multiple sources and platforms can be aligned\n•\tIt is owned and governed by TfGM, allowing long term stability and control\n•\tIt is designed to support both real time and historical views of the transport network\nWhile initial thinking has been informed by Highways together with Operational Control Centre use cases, TfGM is now considering the need to evolve this thinking into a business wide UDM, capable of supporting a much broader range of consumers and use cases across the organisation.\nRelationship to Vendor Provided Solutions\nTfGM anticipates that different suppliers may provide solutions that utilise their own internal or proprietary data models.\nThe intent of a TfGM owned UDM is not to replace or mandate supplier data models, but to:\n•\tEnable federation, mapping or abstraction across multiple vendor data models\n•\tFacilitate portability of data and capability between solutions over time\n•\tReduce dependency on tightly coupled, proprietary representations of TfGM's network\n•\tSupport coexistence of multiple platforms while maintaining a consistent enterprise view\nTfGM is therefore particularly interested in approaches that allow vendor solutions to:\n•\tIntegrate with, publish to, or consume from a TfGM UDM\n•\tMap or transform data between proprietary models and the TfGM canonical model\n•\tOperate independently while still contributing to a single, coherent picture of the network\nBusiness Drivers and Challenges\nTfGM is seeking to address a number of challenges through this work, including:\n•\tFragmented and inconsistent representations of the transport network across systems\n•\tDuplication of data modelling effort between projects and suppliers\n•\tDifficulty reusing data across operational, analytical and planning contexts\n•\tLimited ability to decouple strategic data assets from individual vendor solutions\n•\tRisk of long term vendor lock in as new platforms are introduced\nThe UDM is seen as a potential mechanism to centralise meaning without centralising systems, enabling TfGM to evolve its digital landscape in a controlled and flexible manner.\nPurpose of this Market Engagement\nTfGM is not undertaking a procurement through this engagement.\nThe purpose is to engage with organisations that have experience supporting large, complex, data intensive organisations to:\n•\tShape, validate or implement unified or canonical data models\n•\tAlign data architecture with long term digital strategy and roadmaps\n•\tDesign governance models that balance consistency with flexibility\n•\tEnable interoperability across supplier ecosystems\nTfGM wishes to use this engagement to test and refine its thinking around:\n•\tWhether a TfGM owned UDM is the right strategic approach\n•\tHow such a model should be scoped, structured and governed\n•\tHow it should evolve from domain specific (e.g. Highways) to enterprise wide\n•\tHow it can practically support digital twin ambitions over time\nWhat TfGM Is Asking the Market to Respond To\nSuppliers are invited to provide high level responses covering:\n•\tRelevant experience of delivering or supporting unified data models or similar constructs at scale\n•\tHow they would support TfGM in shaping, validating or maturing a TfGM owned UDM\n•\tHow a UDM can support: \no\tFederation across multiple vendor platforms\no\tPortability of data and capability over time\no\tLong term digital twin development\n•\tViews on governance, ownership and change control for an enterprise UDM\n•\tWhat a typical engagement and delivery model might look like (e.g. discovery, assurance, roadmap definition)\nResponses should focus on approach, principles and experience, rather than promotion of specific proprietary products or platforms.\nNext Steps\nFeedback from this market engagement will be used to inform TfGM's future strategy, roadmap and potential commissioning of advisory or delivery support for building a strong data foundation.\nParticipation in this engagement does not guarantee involvement in any subsequent procurement." } ], "items": [ { "id": "1", "additionalClassifications": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": [ { "scheme": "CPV", "id": "48000000", "description": "Software package and information systems" }, { "scheme": "CPV", "id": "72000000", "description": "IT services: consulting, software development, Internet and support" } ] } ], "deliveryAddresses": [ { "region": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "UK" } ], "country": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "GB" } ], "countryName": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "United Kingdom" } ] } ], "relatedLot": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "1" } ] } ], "value": { "amountGross": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": 200000 } ], "currency": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "GBP" } ] }, "mainProcurementCategory": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "services" } ], "aboveThreshold": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": false } ], "lots": [ { "id": "1", "suitability": { "sme": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": true } ] }, "contractPeriod": { "startDate": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2026-08-01T00:00:00+01:00" } ], "endDate": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "2027-01-01T23:59:59Z" } ] }, "status": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "planning" } ] } ], "status": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "planning" } ] }, "language": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": "en" } ], "extensions": [ { "releaseID": "038431-2026", "releaseDate": "2026-04-28T11:18:50+01:00", "releaseTag": [ "planning" ], "value": [ "https://standard.open-contracting.org/profiles/eu/latest/en/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_amendment_rationale_classifications_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_budget_breakdown_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_contract_completion_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_documentation_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_pagination_extension/master/extension.json", "https://raw.githubusercontent.com/open-contracting-extensions/ocds_suitability_extension/master/extension.json", "https://raw.githubusercontent.com/portaledcahn/ocds_Links_extension/main/extension.json", "https://raw.githubusercontent.com/cabinetoffice/ocds_uk_extension/main/extension.json" ] } ] } } ] }