194399-2026 update-add 5 http://www.transnetbw.de ORG-0001 TransnetBW GmbH TransnetBW GmbH Osloer Str. 15-17 Einkauf & Contract- und Claimmanagement Stuttgart 70173 DE111 DEU HRB Nr. 740510 S. Schittenhelm mship-pbps-procurement@transnetbw.de ORG-0002 TransnetBW GmbH TransnetBW GmbH Osloer Straße 15-17 Stuttgart 70173 DE111 DEU 123456-2024 +49 711 218583632 mshiplfc@TransnetBW.de https://op.europa.eu ORG-0000 Publications Office of the European Union Publications Office of the European Union Luxembourg 2417 LU000 LUX PUBL +352 29291 ted@publications.europa.eu 00199914-202657/20262026-03-23+01:00 2.3 eforms-sdk-1.14 e2ffabd8-562d-4f58-b818-af591c2af790 2026-03-20Z 07:18:31Z 01 32014L0025 pin-only DEU ENG https://www.transnetbw.de/de pub-undert electricity ORG-0002 ted-esen ORG-0000 ted-esen ORG-0001 mk-RfI-MSHIP-PBPS-Market Surveys MSHIP Market Surveys for Platform Base and Platform Services MSHIP Market Surveys for Platform Base and Platform Services siehe englische Beschreibung The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self- hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Please note that also responses are invited and will be considered that do not cover all listed functionalities. services siehe englische Beschreibung. Initial Situation Germany 'Energiewende' (energy transition - see https://www.netzentwicklungsplan.de/en/verstehen/glossar/e ) and the goals of the German Electricity Network Development Plan (NEP - see https://www.netzentwicklungsplan.de/en) challenges the transmission systems operators to expand and enhance their capabilities to operate the grid of the future (see link to NEP). MSHIP Program objectives TransnetBW started to setup a program ("MSHIP") with multiple projects - one of the objectives: To evolve technical capabilities (hardware and software) to be prepared for the next 22 years to be able to implement required applications faster and more efficient (see NEP 2037/2045 with focus on achieving a climate-neutral grid by 2045). 72212211 siehe Englisches Feld Official name: TransnetBW GmbH Email: mship-pbps-procurement@transnetbw.de Legal type of the buyer: Public undertaking Activity of the contracting entity: Electricity-related activities Procedure RFI - Bare-Metal Provisioning RFI - Network and Security Configuration Automation RFI - Kubernetes Cluster Lifecycle Management RFI - Kubernetes Distribution General Information: The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self-hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Purpose of this RFI: The purpose of this RFI is to identify potential providers and solutions that can meet the requirements of MSHIP - Platform Base and Platform Services. 1) The RFI is intended to provide an initial market overview and to evaluate possible technological approaches and their ability to integrate into the existing MSHIP architecture. 2) The aim is not to commit to a specific system, an architecture or provider in advance. Openness to different approaches remains the main guiding principle. The information gathered will serve as a basis for future decisions and possible tenders. Participation in this market exploration will not result in any advantages or disadvantages for the participants as potential bidders in a future - not yet binding - tender procedure. Expectations: - Solutions and Technologies: Overview of available products and technical approaches tailored to the technical platform and technical enablement service and assessment of security, flexibility and technology standards - Integration and Compatibility: Guidelines for interoperability with existing MSHIP components and compliance with relevant standards/legislation - Market Overview: Insight into the experience, capabilities and potential capacities of relevant providers - Basis for Future Planning: Use of the information to further develop detailed requirements and possible tender documents Partial Response Partial response to our questions are explicitly encouraged. Please note that submissions will be considered even if they do not cover the full scope of requirements, as we highly value specialized insights and expertise in your specific area. Process Short summary of the process in advance -Register via E-Mail -Receive an NDA to sign -Sign the NDA and send it to us -Get access to the strictly confidential information Process in detail To participate in the RFI process interested parties are required to follow the following procedure. To gain access to further information and documentation, please register (follow section 'Registration' in chapter 'Communication Channels'). In your registration e-mail, please specify a contact and e-mail-address(es) to be used to communicate with your company on this matter. Once this step is complete, we will provide you a Non-Disclosure Agreement (NDA). Please note that, due to the strictly confidential nature of the information involved, all participant parties must sign the NDA as a prerequisite to receive additional documents. Schedule - RFI Release: 2026-03-20 - Submission of signed NDA (Prerequisite and mandatory for RFI participation): 2026-04-07 - 09:00 CET - Send-out of RFI documents (Only for participants who signed an NDA): 2026-04-08 - Deadline for Clarification Questions: 2026-04-27 - 09:00 CEST - Submission Deadline for RFI Responses: 48 calendar days after receiving the RFI documents, but at the latest: 2026-05-25 - 09:00 CEST Communication Protocol To maintain process integrity and efficiency, all inquiries must be submitted exclusively through the designated RFI communication channels listed below. Please refrain from contacting TransnetBW staff, supporting Business Partners, or representatives - whether directly, indirectly, or via third-party intermediaries Adhering to these guidelines ensures that all participants receive identical information simultaneously and prevents unnecessary administrative burden. Please be advised that failure to comply with these communication rules may lead to disqualification from the process Communication Channels Registration Interested parties wishing to participate in the RFI process are invited to contact us as follows: Subject: "MSHIP RFI [ RFI NAME ] - REGISTRATION - [ Your Company Name ]" Write to "MSHIP PBPS RFI Team" E-Mail: mship-pbps-procurement@transnetbw.de Format: inline Text or Attachments Allowed file formats for attachments: PDF Clarification Questions Should you require clarification regarding the RFI's content or structure, please reach out via the following contact points. To facilitate a prompt and effective resolution, we kindly ask you to structure your questions as follows: Subject: "MSHIP RFI [ RFI NAME ] - QUESTIONS - [ Your Company Name ]" Write to "MSHIP PBPS RFI Team" E-Mail: mship-pbps-procurement@transnetbw.de Format: inline Text or Attachments Allowed file formats for attachments: PDF, PNG, DOCX, XLSX Submissions Please send your completed documents and responses to this according to the RFI schedules. Subject: "MSHIP RFI [ RFI-Name ] - RESPONSE - [ Your Company Name ]" E-Mail: mship-pbps-procurement@transnetbw.de Allowed file formats for attachments: PDF, PNG, DOCX, XLSX DE111 DEU PAR-0000 ORG-0001 ORG-0001 true MSHIP Market Survey for Bare-Metal Provisioning MSHIP Market Survey for Bare-Metal Provisioning MSHIP Market Survey for Bare-Metal Provisioning siehe englische Beschreibung Official name: TransnetBW GmbH Email: mship-pbps-procurement@transnetbw.de Legal type of the buyer: Public undertaking Activity of the contracting entity: Electricity-related activities Procedure RFI - Bare-Metal Provisioning Title: MSHIP Market Survey for Bare-Metal Provisioning General Information: The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self-hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Context Bare Metal: For MSHIPs Platform, the bare-metal provisioning layer plays a foundational role - taking physical hardware from rack-and-power to a running operating system ready for use. The solution for bare-metal provisioning is planned to support the full lifecycle of bare-metal systems: initial setup, provisioning, re-provisioning, repurposing, and decommissioning. The handover point to downstream systems (e.g. Kubernetes Cluster Lifecycle Management) is a key integration boundary. The bare-metal provisioning infrastructure will be designed to maximize automation through Infrastructure as Code-based workflows, while preserving deliberate control over hardware enrollment decisions. It must integrate seamlessly with the surrounding data center infrastructure, in particular the underlying network and security architecture. We aim to leverage the positive developments from the bare-metal and cloud-native ecosystem of recent years, aligning as closely as possible with industry trends around open-source software, hardware abstraction, declarative configuration models, and integration with Kubernetes-based application platforms. At the same time, the solution must adhere to industry security standards and be suitable for use in a KRITIS environment, with minimal external dependencies. Purpose of this RFI: The purpose of this RFI is to identify potential providers and solutions that can meet the requirements of MSHIP - Platform Base and Platform Services. 1) The RFI is intended to provide an initial market overview and to evaluate possible technological approaches and their ability to integrate into the existing MSHIP architecture. 2) The aim is not to commit to a specific system, an architecture or provider in advance. Openness to different approaches remains the main guiding principle. The information gathered will serve as a basis for future decisions and possible tenders. Participation in this market exploration will not result in any advantages or disadvantages for the participants as potential bidders in a future - not yet binding - tender procedure. Expectations: - Solutions and Technologies: Overview of available products and technical approaches tailored to the technical platform and technical enablement service and assessment of security, flexibility and technology standards - Integration and Compatibility: Guidelines for interoperability with existing MSHIP components and compliance with relevant standards/legislation - Market Overview: Insight into the experience, capabilities and potential capacities of relevant providers - Basis for Future Planning: Use of the information to further develop detailed requirements and possible tender documents Partial Response Partial response to our questions are explicitly encouraged. Please note that submissions will be considered even if they do not cover the full scope of requirements, as we highly value specialized insights and expertise in your specific area. Process Short summary of the process in advance -Register via E-Mail -Receive an NDA to sign -Sign the NDA and send it to us -Get access to the strictly confidential information Process in detail To participate in the RFI process interested parties are required to follow the following procedure. To gain access to further information and documentation, please register (follow section 'Registration' in chapter 'Communication Channels'). In your registration e-mail, please specify a contact and e-mail-address(es) to be used to communicate with your company on this matter. Once this step is complete, we will provide you a Non-Disclosure Agreement (NDA). Please note that, due to the strictly confidential nature of the information involved, all participant parties must sign the NDA as a prerequisite to receive additional documents. Schedule - RFI Release: 2026-03-20 - Submission of signed NDA (Prerequisite and mandatory for RFI participation): 2026-04-07 - 09:00 CET - Send-out of RFI documents (Only for participants who signed an NDA): 2026-04-08 - Deadline for Clarification Questions: 2026-04-27 - 09:00 CEST - Submission Deadline for RFI Responses: 48 calendar days after receiving the RFI documents, but at the latest: 2026-05-25 - 09:00 CEST supplies 48100000 DE111 DEU PAR-0001 ORG-0001 ORG-0001 true MSHIP Market Survey for Network and Security Configuration Automation MSHIP Market Survey for Network and Security Configuration Automation MSHIP Market Survey for Network and Security Configuration Automation siehe englische Beschreibung Official name: TransnetBW GmbH Email: mship-pbps-procurement@transnetbw.de Legal type of the buyer: Public undertaking Activity of the contracting entity: Electricity-related activities Procedure RFI - Network and Security Configuration Automation Title: MSHIP Market Survey for Network and Security Configuration Automation General Information: The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self-hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Context Network and Security Configuration Automation: The infrastructure as a whole and the network infrastructure in particular, will be designed by automated and zero-touch provisioning principles, Infrastructure as Code-based configuration management, and by reducing manual operational tasks wherever it is sensible to do so. We aim to leverage the positive developments in the cloud-native data center networking field of recent years, aligning as closely as possible with industry standards around open-source software, white-label hardware, modular solutions, and horizontally scalable topologies. At the same time, the solution must adhere to highest security requirements and be suitable for use in a KRITIS environment, with minimal external dependencies. The network infrastructure and its provisioning must integrate seamlessly into the overall architecture, which also includes bare-metal provisioning of nodes that will subsequently host a Kubernetes-powered application layer. Purpose of this RFI: The purpose of this RFI is to identify potential providers and solutions that can meet the requirements of MSHIP - Platform Base and Platform Services. 1) The RFI is intended to provide an initial market overview and to evaluate possible technological approaches and their ability to integrate into the existing MSHIP architecture. 2) The aim is not to commit to a specific system, an architecture or provider in advance. Openness to different approaches remains the main guiding principle. The information gathered will serve as a basis for future decisions and possible tenders. Participation in this market exploration will not result in any advantages or disadvantages for the participants as potential bidders in a future - not yet binding - tender procedure. Expectations: - Solutions and Technologies: Overview of available products and technical approaches tailored to the technical platform and technical enablement service and assessment of security, flexibility and technology standards - Integration and Compatibility: Guidelines for interoperability with existing MSHIP components and compliance with relevant standards/legislation - Market Overview: Insight into the experience, capabilities and potential capacities of relevant providers - Basis for Future Planning: Use of the information to further develop detailed requirements and possible tender documents Partial Response Partial response to our questions are explicitly encouraged. Please note that submissions will be considered even if they do not cover the full scope of requirements, as we highly value specialized insights and expertise in your specific area. Process Short summary of the process in advance -Register via E-Mail -Receive an NDA to sign -Sign the NDA and send it to us -Get access to the strictly confidential information Process in detail To participate in the RFI process interested parties are required to follow the following procedure. To gain access to further information and documentation, please register (follow section 'Registration' in chapter 'Communication Channels'). In your registration e-mail, please specify a contact and e-mail-address(es) to be used to communicate with your company on this matter. Once this step is complete, we will provide you a Non-Disclosure Agreement (NDA). Please note that, due to the strictly confidential nature of the information involved, all participant parties must sign the NDA as a prerequisite to receive additional documents. Schedule - RFI Release: 2026-03-20 - Submission of signed NDA (Prerequisite and mandatory for RFI participation): 2026-04-07 - 09:00 CET - Send-out of RFI documents (Only for participants who signed an NDA): 2026-04-08 - Deadline for Clarification Questions: 2026-04-27 - 09:00 CEST - Submission Deadline for RFI Responses: 48 calendar days after receiving the RFI documents, but at the latest: 2026-05-25 - 09:00 CEST supplies 48100000 DE111 DEU PAR-0002 ORG-0001 ORG-0001 true MSHIP Market Survey for Kubernetes Cluster Lifecycle Management MSHIP Market Survey for Kubernetes Cluster Lifecycle Management MSHIP Market Survey for Kubernetes Cluster Lifecycle Management siehe englische Beschreibung Official name: TransnetBW GmbH Email: mship-pbps-procurement@transnetbw.de Legal type of the buyer: Public undertaking Activity of the contracting entity: Electricity-related activities Procedure RFI - Kubernetes Cluster Lifecycle Management Title: MSHIP Market Survey for Kubernetes Cluster Lifecycle Management General Information: The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self-hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Context Kubernetes Cluster Lifecycle Management: For MSHIPs Platform, Kubernetes Cluster Lifecycle Management plays a central role — orchestrating the assembly of Kubernetes clusters from provisioned nodes using a chosen distribution. The solution must cover the full cluster lifecycle: design, bootstrap, configuration, scaling, upgrades, node replacement, and decommissioning - across dozens of clusters and hundreds of nodes. Kubernetes Cluster Lifecycle Management sits between bare-metal provisioning (which delivers ready nodes), network automation (which provides connectivity), and the Kubernetes distribution (which hosts business applications). Where responsibilities overlap or require coordination, integration contracts and authority boundaries are central focus points. The solution will be designed to maximize automation through Infrastructure as Code-based workflows while preserving deliberate control over cluster changes. It must support fleet-wide operations across multiple sites and failure domains, operate fully air-gapped, and remain distribution-agnostic to allow flexibility in Kubernetes distribution choices. We aim to leverage the positive developments from the Kubernetes ecosystem in recent years, aligning as closely as possible with industry trends around declarative configuration, GitOps workflows, and modular lifecycle tooling. At the same time, the solution must adhere to industry security standards and be suitable for use in a KRITIS environment. Purpose of this RFI: The purpose of this RFI is to identify potential providers and solutions that can meet the requirements of MSHIP - Platform Base and Platform Services. 1) The RFI is intended to provide an initial market overview and to evaluate possible technological approaches and their ability to integrate into the existing MSHIP architecture. 2) The aim is not to commit to a specific system, an architecture or provider in advance. Openness to different approaches remains the main guiding principle. The information gathered will serve as a basis for future decisions and possible tenders. Participation in this market exploration will not result in any advantages or disadvantages for the participants as potential bidders in a future - not yet binding - tender procedure. Expectations: - Solutions and Technologies: Overview of available products and technical approaches tailored to the technical platform and technical enablement service and assessment of security, flexibility and technology standards - Integration and Compatibility: Guidelines for interoperability with existing MSHIP components and compliance with relevant standards/legislation - Market Overview: Insight into the experience, capabilities and potential capacities of relevant providers - Basis for Future Planning: Use of the information to further develop detailed requirements and possible tender documents Partial Response Partial response to our questions are explicitly encouraged. Please note that submissions will be considered even if they do not cover the full scope of requirements, as we highly value specialized insights and expertise in your specific area. Process Short summary of the process in advance -Register via E-Mail -Receive an NDA to sign -Sign the NDA and send it to us -Get access to the strictly confidential information Process in detail To participate in the RFI process interested parties are required to follow the following procedure. To gain access to further information and documentation, please register (follow section 'Registration' in chapter 'Communication Channels'). In your registration e-mail, please specify a contact and e-mail-address(es) to be used to communicate with your company on this matter. Once this step is complete, we will provide you a Non-Disclosure Agreement (NDA). Please note that, due to the strictly confidential nature of the information involved, all participant parties must sign the NDA as a prerequisite to receive additional documents. Schedule - RFI Release: 2026-03-20 - Submission of signed NDA (Prerequisite and mandatory for RFI participation): 2026-04-07 - 09:00 CET - Send-out of RFI documents (Only for participants who signed an NDA): 2026-04-08 - Deadline for Clarification Questions: 2026-04-27 - 09:00 CEST - Submission Deadline for RFI Responses: 48 calendar days after receiving the RFI documents, but at the latest: 2026-05-25 - 09:00 CEST supplies 48100000 DE111 DEU PAR-0003 ORG-0001 ORG-0001 true MSHIP Market Survey for Kubernetes Distribution MSHIP Market Survey for Kubernetes Distribution MSHIP Market Survey for Kubernetes Distribution siehe englische Beschreibung Official name: TransnetBW GmbH Email: mship-pbps-procurement@transnetbw.de Legal type of the buyer: Public undertaking Activity of the contracting entity: Electricity-related activities Procedure RFI - Kubernetes Distribution Title: MSHIP Market Survey for Kubernetes Distribution General Information: The MSHIP Program is an initiative by TransnetBW aimed at supporting Germany's energy transition by developing a sustainable, scalable, and efficient grid management system. It focuses on modularity, automation, and simplicity to enhance operational security and reduce costs. The architecture is based on a self-hosted, cloud-native platform specifically designed for secure and data-driven operations. MSHIP - Platforms goal is to use designs, selection, implementation, and system integration of all infrastructure components to provide the IaaS (Infrastructure as a Services) and PaaS (Platform as a Service) components of the MSHIP OT/IT Secure Realtime Platform using IaC (Infrastructure as Code) so that additional non-functional and functional MSHIP Macro Services can be built on top of it. Context Kubernetes Distribution: For MSHIPs Platform, Kubernetes distributions - the software artifacts, binaries, and default configurations that constitute a deployable Kubernetes system - are a distinct concern. The term "distribution" is used broadly in the market and may refer to pure upstream Kubernetes repackaged for ease of installation, modified distributions with vendor-specific changes, or enhanced distributions bundling additional components. We intentionally separate the distribution from Kubernetes Cluster Lifecycle Management tooling. This allows flexibility in combining distributions with different solutions, supports replaceability, and avoids vendor lock-in. The distribution must be deployable and operable in a fully air-gapped environment and meet security standards suitable for KRITIS. Purpose of this RFI: The purpose of this RFI is to identify potential providers and solutions that can meet the requirements of MSHIP - Platform Base and Platform Services. 1) The RFI is intended to provide an initial market overview and to evaluate possible technological approaches and their ability to integrate into the existing MSHIP architecture. 2) The aim is not to commit to a specific system, an architecture or provider in advance. Openness to different approaches remains the main guiding principle. The information gathered will serve as a basis for future decisions and possible tenders. Participation in this market exploration will not result in any advantages or disadvantages for the participants as potential bidders in a future - not yet binding - tender procedure. Expectations: - Solutions and Technologies: Overview of available products and technical approaches tailored to the technical platform and technical enablement service and assessment of security, flexibility and technology standards - Integration and Compatibility: Guidelines for interoperability with existing MSHIP components and compliance with relevant standards/legislation - Market Overview: Insight into the experience, capabilities and potential capacities of relevant providers - Basis for Future Planning: Use of the information to further develop detailed requirements and possible tender documents Partial Response Partial response to our questions are explicitly encouraged. Please note that submissions will be considered even if they do not cover the full scope of requirements, as we highly value specialized insights and expertise in your specific area. Process Short summary of the process in advance -Register via E-Mail -Receive an NDA to sign -Sign the NDA and send it to us -Get access to the strictly confidential information Process in detail To participate in the RFI process interested parties are required to follow the following procedure. To gain access to further information and documentation, please register (follow section 'Registration' in chapter 'Communication Channels'). In your registration e-mail, please specify a contact and e-mail-address(es) to be used to communicate with your company on this matter. Once this step is complete, we will provide you a Non-Disclosure Agreement (NDA). Please note that, due to the strictly confidential nature of the information involved, all participant parties must sign the NDA as a prerequisite to receive additional documents. Schedule - RFI Release: 2026-03-20 - Submission of signed NDA (Prerequisite and mandatory for RFI participation): 2026-04-07 - 09:00 CET - Send-out of RFI documents (Only for participants who signed an NDA): 2026-04-08 - Deadline for Clarification Questions: 2026-04-27 - 09:00 CEST - Submission Deadline for RFI Responses: 48 calendar days after receiving the RFI documents, but at the latest: 2026-05-25 - 09:00 CEST supplies 48100000 DE111 DEU