Germany
Specialist engineering consulting, technical project support and calculation and documentation sets that hold up under review.
Load cases, strength and stability verification, FE models checked against hand calculation. Every result in the report can be followed back to the assumption it came from.
Calculation reports, drawing sets and revision trails prepared so that a reviewer, an auditor or the next engineer can read them years later without asking us what we meant.
We act as the engineering desk on your project for a defined phase: interface clarification, supplier documents, technical queries answered in writing instead of in a corridor.
A second opinion on a third-party design or calculation — what we agree with, what we would change, and which assumptions carry the result.
Our client app shows work packages, current revisions and open technical points on your phone, so the project status does not live in somebody's inbox.
Most technical problems that reach an outside specialist are not difficult because the physics is exotic. They are difficult because the question has never been written down precisely. A component cracks, a retrofit will not fit, a supplier's calculation arrives with four pages and no assumptions, a plant has to keep running while the modification is installed. In each case the first useful piece of engineering is a sentence: this is what we are verifying, under these loads, against this standard, with this result counting as pass.
That sentence is where we begin, and it is why the first thing we send back is never a price list. It is a scope — what we would examine, what we would deliberately leave out, which inputs we need from you, and what you would be holding at the end.
A number on its own has no shelf life. The same result is worth very little if nobody can reconstruct how it was obtained, and worth a great deal if the model, the load assumptions, the material data and the cross-check are all in one document with the revisions visible. So our calculation work ends in a report that a competent third party can audit without a phone call: assumptions listed before the maths, FE results compared against an independent hand estimate, deviations named rather than smoothed out.
This is also what makes the work survive personnel changes on your side. Projects outlive the people who started them. Documentation written for a reviewer, not for the author, is the only part of engineering that reliably transfers.
Industrial clients rarely have the luxury of an empty hall. Much of the specialist work is therefore planned around production: measurement campaigns in a shutdown window, modifications designed to be installed in stages, interim states checked as carefully as the final one. An interim state nobody calculated is the usual source of an unpleasant surprise.
Precision is less about complicated models than about honest boundaries. We would rather tell you a question is outside our scope than produce a document that looks complete and is not.
Four standard forms of mandate. Scope and effort are agreed in writing before anything starts.
A defined technical question, examined by a named engineer and answered in a written statement.
We carry the engineering desk through a project phase, from interface clarification to supplier document review.
The verification set for your file: models, hand cross-check and a report written to be audited.
A second opinion on an external design or calculation, with findings sorted by what actually affects the result.
Scope, deliverables and revision rounds are fixed in the written proposal. Drawings and specifications sent to us are treated as confidential; an NDA can be signed before the first file arrives.
What the work looks like between the enquiry and the handover.
You describe the component, system or project phase, and send whatever already exists — sketch, drawing, specification, a photograph of the problem.
A call with the engineer who would do the work. We settle the question, the applicable standard, the interfaces and what counts as a result.
Scope, deliverables, inputs we need from you, revision rounds and effort — on paper, before anything is started.
Work packages, current revisions and open technical points stay visible to you in the client app for the whole duration.
You receive the documentation set in your format, with the assumptions, the cross-checks and the remaining open points stated plainly.
Describe the problem in your own words. Precision helps, but a rough description is enough to start.
An engineer will read it and get in touch shortly, usually with a few clarifying questions before anything is quoted.
This page uses cookies for analytics and advertising measurement, but only after you give your consent. Learn More