Software that fits
the plant you have
Line-of-business applications with SAP integration, geo-redundant infrastructure and NIS2-compliant ISMS for manufacturing, logistics and maritime. Precise cuts into existing landscapes rather than greenfield rebuilds.
References in this industry
SAP-Integrated Web Tools for Estimation and Shop-Floor Planning
minutes not hoursEstimation Time
ERP Integration for Digital Equipment Management
eliminatedDuplicate Data Entry
Maritime AI Platform - Hull Inspection & Maintenance
-60%Inspection Time
ISO 27001 Process Documentation for Logistics
CompliantISO 27001
NIS2 Security Implementation
AchievedNIS2 Compliance
Real-Time IoT Monitoring Platform
3 monthsTime to POC
What we build for this industry
Applications with ERP integration
Calculation, estimation and scheduling as their own application, connected to SAP rather than maintained alongside it.
- SAP integration
- Material estimation & calculation
- Shop-floor staff scheduling
- Customer-facing PDF output
Infrastructure & high availability
Geo-redundant Windows, Linux and MSSQL landscapes with a backup design and automated operation.
- Geo-redundancy & failover
- Backup & recovery design
- PowerShell & Ansible
- Documented maintenance windows
NIS2 & ISO 27001
ISMS structures built to fit actual operations rather than an ideal, with hardening along BSI baseline protection.
- ISMS along NIS2
- BSI baseline hardening
- Vulnerability & patch management
- Incident, change & release processes
Data pipelines & image recognition
Sensor and image data evaluated automatically, as in maritime hull inspection, instead of reviewed by hand.
- Data pipelines
- Image recognition in inspection
- ERP & asset management integration
- Visible rather than silent failures
What actually gets in the way
The problems we hear in this field, before anyone mentions a technology.
No greenfield project
The ERP has run for years and the processes work. Just with manual transcription in between.
The knowledge sits in spreadsheets
Which parameter feeds into a calculation and how is rarely documented anywhere.
Downtime is money directly
A system built elegantly but behaving unclearly during a fault is the worse system.
NIS2 has reached mid-sized industry
For many the first structured engagement with security beyond individual measures.
What obstructs operations
Gets bypassed. A security concept people work around protects no one.
Silent failures cost the most
A transfer that fails unnoticed only surfaces once the numbers stop adding up.
What we have built here
SAP-Integrated Web Tools for Estimation and Shop-Floor Planning
Two line-of-business applications for a polymer processor - material estimation for underfloor heating and browser-based shop-floor scheduling.
ERP Integration for Digital Equipment Management
Bidirectional integration between a trades ERP and a SaaS platform for tool and equipment management.
Maritime AI Platform - Hull Inspection & Maintenance
AI-powered hull inspection and maintenance platform for the maritime industry. 60% faster inspections, 40% lower costs.
ISO 27001 Process Documentation for Logistics
Comprehensive ISO 27001 security process documentation and cross-departmental alignment for a national logistics provider.
NIS2 Security Implementation
NIS2 compliance implementation for an industrial manufacturer, including ISMS setup, risk management, and security monitoring.
Real-Time IoT Monitoring Platform
Full-stack IoT platform with real-time sensor data pipelines, event-driven architecture, and live monitoring dashboards.
Have a project in mind?
Tobias
Let's Talk →Frequently Asked Questions
No, and as a rule that would be the wrong path anyway. We build applications alongside the ERP and connect them rather than replacing it. At an international polymer processor two applications ran with SAP integration, material estimation and shop-floor staff scheduling. The ERP stays authoritative for its data; the application covers what cannot be modelled there.
At the start we do not, and that is the actual effort in the project. The work consists of reconstructing it: which parameters feed into a calculation and how, which rules govern shift staffing, which system is authoritative for which data field. That knowledge usually sits in spreadsheets and in people, not in a specification, and surfacing it is part of the job.
We ask that question during design, not during operation. Failed transfers are retried and stay visible instead of being silently lost. Alongside that come recovery times, failover behaviour and maintenance windows as part of the design. In manufacturing, downtime is directly measurable in money, which shifts priorities considerably against software projects in other industries.
That depends on sector and company size, and we work through the classification together at the start. What is clear is that NIS2 has brought requirements into mid-sized industry that previously concerned mainly critical infrastructure operators. For many companies this is the first structured engagement with information security beyond individual technical measures.
If it is designed against an ideal rather than against operations, yes. That is exactly why we build ISMS structures along actual workflows: hardening along BSI baseline protection, vulnerability and patch management, documented incident, change and release processes that fit your shifts and maintenance windows. A security concept that obstructs operations gets bypassed, and then protects no one.
Yes, and with infrastructure projects that is the norm rather than the exception. For a machine tool manufacturer we own the architecture and operation of a geo-redundant Windows, Linux and MSSQL landscape including high availability, backup design and automation via PowerShell and Ansible. Where you want to run it yourself, we build for handover accordingly.