COMOS Consulting — delivery depth, not buzzwords.

Ongoing operations, permissions, maintenance — so your COMOS environment stays stable and no one on your team has to divert time from core work.

Object library, rules, VBScript and .NET automations — tailored to your processes instead of the factory default. On request, I train your team directly in your own environment instead of on generic demo data — for teams who want to truly master COMOS.

Connections to SAP PM/MM, maintenance tools and Autodesk/AVEVA E3D — including the cross-department alignment that comes with it.

New rollout or an assessment of a grown environment — with a clear priority list of what to tackle first.

Knowledge transfer to your team, so you're independent once the project ends — that's the goal from day one of any engagement.

On a slide, a migration like that sounds like a weekend job. After the first test run I knew: it would take three. That's exactly what test runs are for — since then I plan migrations so the surprises happen in the test system, and the production cutover lands on a pleasantly boring Tuesday.

SAP, maintenance tools, Autodesk — I've built plenty of connections into COMOS. The key insight: the technology is rarely the problem. The problem is that two departments have filled the same field differently for years. There are solutions for that too — they start with listening.

Building the Autodesk connection taught me: CAD people and database people agree that the other side is the problem. My job was translating — in the end the data exchange ran automatically, and both sides were convinced they'd won.