Petra · Joining Catena-X without an IT team
A small-supplier operations manager receives a Catena-X mandate from her largest customer and has no IT team. She needs a managed connector path that does not assume infrastructure knowledge, gets her live in time, and stays invisible afterwards.
Scenario
Petra is Operations Manager at a family-owned automotive components manufacturer in Pilsen with 85 employees. On a Tuesday morning she receives an email from the procurement team at her company’s largest customer, a tier-1 supplier accounting for 40% of the firm’s revenue, requiring Catena-X participation by a date four months away. The email contains a link to a technical onboarding guide and a note that non-participating suppliers may be deprioritised in future sourcing decisions. Petra reads the email three times. She clicks the link. She closes the tab.
She is the person at the company who handles anything involving external digital systems, not because she sought the role, but because she is the most capable person available and the firm cannot afford a dedicated IT team. She has managed the ERP implementation and two EDI integrations with customers. Those took longer than anyone expected and required external consultants both times. Her CEO is supportive but will ask how much this costs and whether it is strictly necessary. The answer to the second question is yes, and Petra knows it. She cannot afford to lose 40% of revenue over a technology requirement.
Storyline
sequenceDiagram actor P as Petra participant C as Customer (tier-1) participant K as Kaphera (web + support) participant DS as Tractus-X authority C->>P: Catena-X mandate (deadline) P->>K: search, read site, email enquiry K-->>P: plain-language reply + supplier guide P->>K: create account, set up org (22 min) P->>K: initiate Tractus-X onboarding K->>DS: identity establishment, credential request DS-->>K: validation pending (3-10 days) DS-->>K: validated K-->>P: connector active P->>C: first data exchange C-->>P: confirmation received
Step 1: The mandate arrives and the first search begins
Action
Petra forwards the email to herself with the subject line “action required, Catena-X.” She opens the technical onboarding guide from the customer and reads as far as the section on Eclipse Dataspace Components before stopping. She searches “Catena-X onboarding supplier” and reads three results. She searches “Catena-X connector what is it.” She reads a forum post from another supplier who describes the process as “technically complex but manageable with the right provider.” She saves the forum post. She searches “Catena-X managed connector service” and finds four providers. She looks at each one’s website. Two of them lead with Kubernetes. She does not know what Kubernetes is. She closes both tabs.
Thoughts
“The customer email says this is straightforward. The documentation says it requires a Kubernetes cluster. One of these is wrong and I suspect it is the customer email.”
Emotions
Anxious and mildly overwhelmed. Petra is not afraid of new technology, she has handled complex implementations before, but she has learned that implementations described as straightforward in customer communications are rarely straightforward in practice. She is allocating more mental space to this problem than the email suggested she would need to.
Step 2: Finding a provider that speaks her language
Action
Petra returns to the search results and opens Kaphera Cloud’s website. The first paragraph describes the platform as a way to join a dataspace without needing to operate infrastructure. The pricing page shows a managed shared tier with a fixed monthly cost. She reads the setup process description: create an organisation, establish a digital identity, join a dataspace in a single step. She reads it again. She finds the FAQ section and reads the answer to “What does the setup process look like?” She reads the answer to “Is Kaphera Cloud production-ready?” She notes the reference to 150-plus active MDS connectors. She does not know what MDS is, but the number is reassuring. She sends an email to the contact address asking one question: does this work for a small supplier who needs to connect to Catena-X and has no IT team?
Thoughts
“If the answer to my email is a sales call I don’t understand, I’m going to find a consultant and add that to the budget. If the answer actually addresses my question, I’ll keep reading.”
Emotions
Cautiously hopeful. The website is the first thing she has read in two days that does not assume she already knows what a Kubernetes cluster is. She is not ready to trust it yet, but she is willing to ask a direct question and see what comes back.
Step 3: The response that earns the next step
Action
Petra receives a reply within four hours. It is written in plain language, addresses her exact question (yes, this works for small suppliers without IT teams, the setup takes under an hour on the platform side, and the connector runs in the background without requiring ongoing attention), and includes a one-page guide titled “Connecting to Catena-X as a small supplier.” The guide has six steps. Step one is “Create an account.” Petra reads all six steps. She understands all six steps. She forwards the email and the guide to her CEO with a note: “This is what we need to do. Monthly cost is X. I can handle it.” The CEO replies: “If you’re sure it’s the right thing, go ahead.”
Thoughts
“Six steps I can explain to my CEO. That’s the bar I was applying without knowing I was applying it.”
Emotions
Relieved and decisive. The response converted Petra from an uncertain evaluator into a customer in a single email. She is not comparing providers anymore. She is creating an account.
Step 4: Account creation and organisational setup
Action
Petra creates an account on Kaphera Cloud and follows the onboarding flow to create her company’s organisation. The flow asks for the company name, legal registration number, and a contact email. It does not ask about Kubernetes, cloud providers, or infrastructure preferences. She uploads the company’s registration document when prompted. A status indicator shows her where she is in the process. She completes the organisation setup in twenty-two minutes. She receives a confirmation email. She saves the login details in the company’s password manager.
Thoughts
“Twenty-two minutes. The ERP onboarding took four months and a consultant who billed by the hour. I am aware that this is not the same scale of implementation, but still.”
Emotions
Pleasantly surprised. Petra had allocated a full afternoon to the account setup based on prior experience with similar processes. She now has the rest of the afternoon back, which she spends on a production scheduling problem that has been waiting.
Step 5: Digital identity establishment and Catena-X onboarding initiation
Action
Petra returns to the platform the following morning to complete the identity establishment step. The platform prompts her to initiate onboarding into the Tractus-X dataspace profile. She clicks the button. A status tracker appears showing the steps the platform is completing on her behalf: identity establishment, credential request, connector provisioning. Three of the five steps complete immediately. Two show a status of “pending validation” with an explanation that the Catena-X onboarding process includes a validation step managed by the dataspace that typically takes three to ten business days. Petra reads the explanation. She notes the timeline. She sets a calendar reminder for ten business days from now.
Thoughts
“The three to ten days is not something the platform controls. The explanation makes that clear. I would rather know it is pending and why than see a spinner with no information.”
Emotions
Patient and informed. The status tracker and the explanation of the pending step have managed Petra’s expectations without requiring her to chase anyone. She is not anxious about the delay because she understands what is happening.
Step 6: Validation completes, connector activated
Action
Seven business days later Petra receives an email: her connector is active and her company is now a participant in the Tractus-X dataspace. She logs into the platform and sees her connector’s status: active, no issues. She sees the data exchange policy her customer’s dataspace profile requires, the specific data types she is expected to be able to provide. She reads the list. She identifies one data type she is not sure her company’s ERP can export in the required format. She sends an email to her ERP vendor asking about the export capability.
Thoughts
“The connector is active. The question now is whether our ERP can produce the data in the format the customer needs. That is a separate problem, and it is a more familiar one.”
Emotions
Calm and reoriented. The infrastructure problem is solved. What remains is a data format question, an operational problem Petra is more comfortable with than a platform implementation. She is not anxious about the ERP question in the same way she was anxious about the connector setup.
Step 7: First data exchange with the customer
Action
Petra’s ERP vendor confirms that the required export format is supported with a configuration change. Petra makes the configuration change. She initiates the first data exchange through the Kaphera Cloud console, a product specification dataset for a component family the customer has requested. The exchange completes. She receives a confirmation from the customer’s procurement team that the data has been received. She forwards the confirmation to her CEO. The CEO’s reply is two words: “Well done.”
Thoughts
“The customer received the data. That is the outcome the original email required. Everything between that email and this confirmation was the implementation I had to get through to arrive here.”
Emotions
Satisfied and, for the first time since the original mandate email arrived, finished with the problem. The connector is active, the first exchange has completed, and the customer requirement is met. Petra closes the browser tab and returns to her production schedule.
Step 8: The connector becomes invisible
Action
Over the following three months Petra logs into the Kaphera Cloud console four times, twice to check the status of a data exchange her customer’s team asked about, once to update the company’s contact details after a staff change, and once to forward a certificate renewal notification to nobody in particular because the platform handled the renewal automatically and the notification was purely informational. The connector runs. No one at the company thinks about it. It has become infrastructure in the same way the internet connection is infrastructure, present, functional, and invisible until it is not.
Thoughts
“I have logged in four times in three months. At the rate I was expecting to be involved in this, that is significantly better than I planned for.”
Emotions
Untroubled. The invisibility of the connector is the product delivering exactly what Petra needed. She is not delighted by features she does not use. She is satisfied by the absence of problems she was expecting to have.
Step 9: A second mandate arrives
Action
Six months after the first connector went live, Petra receives a similar email from a second customer, a different tier-1 supplier, requiring MDS participation by a date three months away. Petra opens Kaphera Cloud, navigates to the dataspace discovery section, finds the MDS profile, and initiates onboarding. The flow is identical to the Tractus-X onboarding she completed six months ago. She completes the initiation in eleven minutes. She sends an email to the second customer confirming that onboarding has been initiated and providing the expected activation timeline. She does not forward anything to her CEO. She does not consult a consultant. She does not search the internet for an explanation of what MDS is.
Thoughts
“The second mandate took eleven minutes to initiate. The first one took two weeks of anxiety and a full afternoon of reading before I found the right provider. That difference is entirely the product of having done it once and knowing what I was doing.”
Emotions
Quietly confident. The second mandate is not a problem. It is a task. The platform’s consistent onboarding flow across dataspace profiles has made the second participation something Petra handles between two other items on her morning task list.
Step 10: Petra becomes an informal reference
Action
At a regional automotive suppliers association meeting, Petra mentions to two other operations managers that her company completed Catena-X onboarding without a consultant and without an IT team. Both of them are facing the same mandate from the same tier-1 customer and are in the early stages of anxiety Petra recognises from six months ago. She sends them both the one-page supplier guide Kaphera sent her in Step 3. One of them signs up the following week.
Thoughts
“I am not a technology expert. But I am someone who did this and it worked. That is the only qualification needed to recommend it to someone who is where I was six months ago.”
Emotions
Generous and genuinely helpful. Petra is not an advocate in any formal sense. She is not posting reviews or attending conferences. She is an operations manager who solved a problem and will tell other operations managers how she solved it when it comes up. That is the referral that travels furthest in her network.
Key features
📋 Mandate-to-onboarding plain language flow: every step of the account creation, identity establishment, and dataspace onboarding process written in language that does not assume infrastructure knowledge
⏱ Real-time status tracker with explained pending states: onboarding progress visible at all times, with clear explanations of steps that depend on the dataspace rather than the platform, so waiting feels informed rather than abandoned
📄 Small supplier onboarding guide: a single-page, non-technical document covering the full setup process in supplier language, suitable for forwarding to a CEO or a cautious operations manager
💶 Fixed, predictable monthly pricing: a single line item that can be presented to a CEO without qualification and approved without a capital investment conversation
🔔 Automated certificate and credential lifecycle management: renewals handled by the platform without requiring the participant’s action, with informational notifications that confirm the renewal happened rather than requesting intervention
🗺 Consistent onboarding flow across dataspace profiles: the second and subsequent participations follow the same steps as the first, making expansion a task rather than a new implementation project
📊 Participant-facing connector status in plain language: active, inactive, and error states described in operational terms rather than infrastructure terms, with clear guidance on what action is required if any
📬 Direct, human-response support for initial enquiries: first contact with the platform answered by a person who addresses the specific question asked, in language that matches the enquirer’s context
Related
- petra-novak: the protagonist: operations manager at a small automotive supplier, the named human carrying this scenario
- participant: the archetype: dataspace participants whose primary need is to satisfy a customer mandate without operating infrastructure
- kaphera-cloud-managed-server: the managed shared-tier server that runs Petra’s connector
- kaphera-cloud-console: the web console she uses for onboarding, dataspace discovery, and connector status
- participant-playbook: sales motion for the participant archetype