Engineering toolchain integration
Requirements, test, PLM and simulation data connected through open standards. Nine years of production experience.
Systems and processI connect requirements, tests, product data and simulation into one traceable digital thread: standards-based, fast to deploy, and documented. And I add AI that runs on your own servers, so your data never leaves your network.
Available for projects from December 2026 · Dresden, remote and on-site in DACH and the EU.
Requirements, test, PLM and simulation data connected through open standards. Nine years of production experience.
Systems and processE-invoicing, Cyber Resilience Act, Data Act and battery passport: fixed scope, typical delivery in 2–10 weeks.
Compliance offersOpen-weight language models, retrieval over your documents and agents that propose while a person decides. No data leaves your network.
How local AI worksThe failures are rarely dramatic. They accumulate, and each one makes the next more likely.
Connections between these systems exist, but they are rarely good.
Performance collapses with large data volumes; old technology hides behind a newer interface.
Every customer configuration is hand-made and must be re-checked at every update.
A change to one requirement silently invalidates tests and simulations that nobody re-runs.
When something breaks, the fix takes months because the escalation path is long.
I have spent nine years on the other side of these failures: building the connectors, and diagnosing them in live customer environments when a release was blocked.
A map of the systems and standards I work with, as text rather than logos. What matters in PLM integration is which interfaces, object types and versions are involved, and how links behave when a baseline changes.
Typical work: DOORS Next integration with ETM and PLM, OSLC integration across vendor boundaries, ReqIF exchange with suppliers, an Ansys Minerva integration that feeds results back to requirements, and Aras Innovator connectors.
Recommended first step
System landscape, data models, processes, a mapping concept and a reliable effort estimate. You receive a written result that any implementer can work from, including me.
Installation, configuration, attribute and object mapping, workflows, permissions, testing, go-live and hypercare.
Integration capacity under your project lead and, if you wish, under your branding. Second- and third-level support. Feasibility checks and effort estimates for pre-sales.
Day rates and fixed-price assessments on request.
Five phases in a fixed order. The bars show the typical range of each phase in working days.
Typical total: 18–38 days
Small and mid-sized firms buy software when a law puts a date on it. These are the dates; each has a fixed-scope offer behind it.
AI-literacy duties apply to every company that uses AI.
CRA reporting of exploited vulnerabilities starts; new connected products must give users access to their data.
Companies above €800,000 turnover must issue XRechnung or ZUGFeRD invoices.
EV, LMT and industrial batteries above 2 kWh need a digital battery passport.
All CRA obligations apply to products with digital elements.
Every German business must issue e-invoices.
Saxon SMEs can apply for SAB digitalisation grants covering part of the cost; I help prepare the application.
All offers with scope and timelinesCurrent open-weight language models are good enough for real engineering and back-office work, and they run on a single server you own. I set them up so the assistant can read your documents and systems, while nothing goes out.
services:
llm:
image: ollama/ollama
networks: [internal]
index:
image: pgvector/pgvector:pg17
networks: [internal]
assistant:
image: registry.local/assistant:1.0
environment:
LLM_URL: http://llm:11434
SIGN_OFF: required
ports: ["8080:8080"] # reachable from your LAN
networks: [internal, lan]
networks:
internal:
internal: true # model and index: no route out
lan: {}
I work from a machine-readable specification. AI coding agents draft implementation, tests and documentation against it; I review, test and sign off architecture and correctness myself. That shortens delivery from months to weeks without handing judgement to a model.
Everything ships as containers with one Compose file and a CI pipeline, so installation is a single command and every update is repeatable. Your project data is not sent to external AI services unless you agree to it in writing.
In development
Synapse is my own product. It is built for the part of coordination work that connectors cannot do.
The language model runs on your infrastructure. No requirement, test or simulation text leaves your company.
Specification complete, implementation under way, pilot customers from Q2 2027.
Interested in a pilot?For a reference programme of 40 people working with DOORS Next, ETM and a PLM/SPDM system, I estimate about 2,076 hours of coordination work per year.
Transport · ≈ 644 h
Moving data between tools. Today's connectors already handle this.
Judgement · ≈ 1,432 h
Judgement, drafting, searching and providing evidence. This is where Synapse works.
The industries differ; the question an auditor asks is always the same: show me, for this requirement, what verified it and in which baseline.
Projects run across Germany and the EU, remotely and on site. In Saxony, I am a day trip away from:

I'm Waheed Ghumman, an integration architect based in Dresden. For nine years I worked as Principal Software Engineer and Solutions Architect for enterprise PLM/ALM integrations, from requirements analysis to production support, for customers in automotive, aerospace and semiconductors.
My work sits where the hard part is not the API call but semantics, versioning and failure behaviour. Root-cause analysis under pressure is what I am most often called in for. From December 2026 I work as an independent consultant.
Yes. Most of the work runs remotely. I come on site in DACH and the EU when workshops, cut-overs or your security rules call for it.
Yes. I work under your project lead and, if you wish, under your name towards the end customer. Confidentiality agreements are a matter of course.
In line with the GDPR; a data processing agreement is available on request. Data stays in your systems: I work in your environment or with test data. Export-control requirements are respected.
A written report covering your system landscape and data models, the processes that touch them, a mapping concept, the risks, and a reliable effort estimate for implementation. It takes 3–5 days at a fixed price and stands on its own, whoever implements afterwards.
Not yet. The specification is complete and implementation is under way; pilot customers from Q2 2027. If you would like to be one of them, I would be glad to talk.
Compliance offers typically take 2–10 weeks after a one-day deadline check, a local AI pilot 4–6 weeks, and an engineering integration 18–38 working days. Speed comes from a fixed scope, specification-driven work with AI coding agents, and containerised deployment.
Yes. Current open-weight models run on a server inside your network. The model, the search index and the logs stay on your hardware, and outbound traffic can be blocked entirely.
Small and mid-sized companies in Saxony can apply for SAB digitalisation grants for external services and software. The application must be filed before the project starts; I help prepare it, and SAB decides on eligibility.
Tell me which systems are involved, which versions, and where it hurts.
First a call, then a fixed-scope assessment, before anyone commits to implementation.