5 min read

Sophie Renard

What she needs: A single integrated governance interface covering profile registration, identity, onboarding, and credentials. What she will not do: Assemble the governance stack from separately maintained components. Why she buys: Participant confidence requires auditable, source-available infrastructure she can inspect.

Head of digital infrastructure at a mobility sector industry consortium, technically literate but not an engineer, accountable to a board for the dataspace’s operation, compliance posture, and participant onboarding. She needs a single integrated governance interface covering profile registration, identity, onboarding, and credentials, with source-availability so she can audit what runs the consortium’s dataspace.

Role: Head of Digital Infrastructure, mobility sector industry consortium

Background

Sophie studied information systems at Sciences Po Paris and spent her early career in public sector digital transformation, first at a French government agency and then at the European Commission’s DG CONNECT, where she worked on data governance policy. She moved into the private sector a decade ago, joining a mobility sector consortium where she has since taken on increasing responsibility for the technical infrastructure underpinning the organisation’s data exchange initiatives. She is not an engineer, she does not write code and does not need to, but she is technically literate enough to evaluate infrastructure decisions critically and to hold engineering partners accountable. She understands how identity systems work, what a credential specification requires, and why an audit trail matters. She reads the IDSA and Gaia-X working group outputs and participates in Catena-X governance forums.

Responsibilities

Sophie is responsible for the technical infrastructure and operational governance of the consortium’s dataspace: defining the identity model participants must satisfy, overseeing the onboarding process, managing relationships with infrastructure providers, and ensuring that the dataspace operates in a way that satisfies both the consortium’s internal governance requirements and any external regulatory obligations. She represents the technical infrastructure function to the consortium’s board and is accountable when participant onboarding fails, when a compliance question surfaces, or when the infrastructure layer falls short of what the consortium has committed to its members. She also manages the vendor relationships that underpin the dataspace, including contracts, SLAs, and escalation paths.

Challenges

Sophie’s primary operational challenge is maintaining participant confidence in an infrastructure that most participants do not understand and cannot inspect themselves. When something goes wrong, an onboarding failure, a credential issue, an outage, the consortium’s members expect an explanation and a resolution, and Sophie is the person who has to provide both. She has assembled the current infrastructure from components that were not designed to work together, which makes auditing difficult and changes slow. Onboarding new participants is more manual than it should be, which limits the dataspace’s growth rate and concentrates operational burden on her small team. She is also watching the regulatory environment closely: TISAX, the EU Data Act, and evolving IDSA specifications all create compliance obligations that her current infrastructure was not built to handle cleanly.

Goals

Sophie wants a single, integrated governance interface that covers the full lifecycle of dataspace operation, profile registration, identity model configuration, participant onboarding, credential management, discoverability, without requiring her team to maintain custom integrations between components. She wants an infrastructure layer that is auditable, both for her own compliance processes and for the external assessors who periodically review the consortium’s operations. She wants participant onboarding to be fast and self-service wherever possible, so that growth does not require proportional growth in her team’s operational workload. And she wants a provider relationship built on transparency, one where she can inspect what is managing her infrastructure and is not dependent on a vendor’s goodwill to understand what her dataspace is actually doing.

Technology use

Sophie works primarily at the level of governance interfaces, documentation, and vendor relationships rather than directly with infrastructure tooling. She uses the consortium’s administrative systems, reviews audit logs and compliance reports, and manages the configuration of identity and onboarding rules through whatever interface the infrastructure provider exposes. She evaluates infrastructure providers by their compliance certifications, their source availability (she insists on being able to audit what runs the consortium’s dataspace), and their production track record with comparable deployments. She has learned, through one painful experience with a previous provider, that a proprietary platform introduces a dependency that is very difficult to unwind once participants are onboarded.

Needs from Kaphera Cloud

Sophie needs a complete governance interface that covers dataspace profile registration, identity model configuration, onboarding rule management, credential issuance, and discoverability control in a single operational surface, not assembled from separately maintained components. She needs the platform to be auditable: source-available licensing that allows her and her technical partners to inspect what manages the consortium’s dataspace is a hard procurement requirement. She needs compliance certification coverage, TISAX Level 2 and ISO 27001 as a baseline, that she can present to external assessors without qualification. She needs a provider with a verifiable production track record at the scale the consortium requires, not a reference deployment assembled for the sales process. She needs the infrastructure to run on EU-sovereign cloud providers, both for regulatory reasons and because the consortium’s members expect it. And she needs a governance structure that gives her confidence the provider cannot be acquired and repurposed against the consortium’s interests, which is why Kaphera’s steward-ownership model is a material consideration in the evaluation, not a marketing detail.

Quote “Our members trust us to run infrastructure they cannot see. That means I need to be able to see everything, and explain it to a board that will not accept ‘the vendor handles it’ as an answer.”

Graph View

Backlinks