Technical documentation
Design data, bills of materials and standards in – operating manual, conformity documentation and multilingual versions out.
Documentation in parallel with design, not after it
Your designs.
Your knowledge.
Your agent.
AI for technical documentation, service and quotations – from an on-demand assistant to an agent with its own area of responsibility. Running in your plant or in a German data center. Not a single drawing leaves the building.
Three use cases that save time from day one
Service & spare parts
Service report, error message and machine history in – a diagnostic proposal, spare parts list and customer reply out.
First-level service in minutes
Quotations & requirement specs
The customer's requirement specification in – a comparison against your scope of supply, deviations and a draft quotation out.
No requirement overlooked in the quote
0
design data outside the building – technically ruled out
2
operating models: in your own server room or hosted in Germany
8
weeks from first conversation to an evaluated pilot
Why sovereign – and why in machinery this is not an option but self-protection
Design data is your capital – drawings, bills of materials and parameters do not belong on servers third parties can access. On-premise makes the question moot.
Export control and dual-use – technical data stays in-house; no unintended disclosure through cloud services.
NIS2 for production – local inference with no internet connection on the shop floor; runs even in an air-gapped production network.
Never used to train third-party models – technically ruled out, not just contractually promised; every query logged.
The platform – two operating models, one software
On-premise · NN-Forge appliance
A pre-configured inference server in your own server room – no internet connection needed in operation.
Hosted EU · data center in Germany
Operated by Neuronetz; connected to PLM, ERP or your service portal with permission-aware access.
OpenAI-compatible interface · open-weight models only · switch from hosted to on-premise at any time, with no data migration.
From assistant to agent – automation in three stages
STAGE 1 · ASSISTANT
The human asks, the AI answers
Draft documentation, diagnostic proposals, quotation comparison – on demand, with sources.
STAGE 2 · AUTOMATION
The AI prepares the work, the human signs off
Service requests pre-sorted, spare parts inquiries answered, draft quotations prepared – ready for sign-off.
STAGE 3 · AGENT
Its own role, its own mailbox
A service agent with its own mailbox handles first-level support; technicians review spot checks and escalations.
Each stage builds on the previous one. You set the pace – trust is built on results, not promises.
A pilot in 8 weeks – no investment decision required
WEEK 1
Scoping
Half a day: use case, machine type, 3–5 users.
WEEKS 2–3
Setup
Platform, connection to your document store, permissions, onboarding.
WEEKS 4–7
Operation
Daily use in real work, weekly check-ins.
WEEK 8
Evaluation
Time saved, quality, adoption – roll out or stop.
You provide: one contact person from the business side and the documents of one machine type. We deliver: platform, setup, support and a final report. We discuss terms in the first conversation.
Let's talk about your machines.
Stephan Kasdorf · Managing Director · Neuronetz UG (haftungsbeschränkt)
Exposé as PDF