| Sector | Automotive, Logistics |
|---|---|
| My Role | Support Lead, Team Lead |
| Team Size | 13 |
| Budget | High five-figure range |
| Duration | 1,5 Years |
| Technologies | Angular JS, Azure, Chat GPT, DDD (Domain Driven Design), Docker, Kubernetes, SAP |
Description
Project Overview
This project was delivered for a large automotive supplier with very strict requirements around information security governance and source control processes. The client outsourced internal logistics operations to an external provider and needed a reliable integration interface between the client’s SAP landscape and the external provider’s logistics software — supporting JIS (Just-in-Sequence) and JIT (Just-in-Time) logistics.
Our solution was based on the D4S platform and leveraged core PST-style integration and application capabilities. We integrated SAP, transformed SAP messages into the external provider’s message format, and ensured stable interoperability. To enable the project, multiple improvements were also required inside the client’s SAP processes and integration points.
The client operated 24/7 production, so availability and support were non-negotiable requirements.
Business Value
The solution enabled a stable, auditable, and scalable interface between SAP and an external logistics provider while maintaining continuous operations.
Key outcomes:
-
Reliable interoperability between SAP and third-party logistics systems for JIS/JIT flows
-
Reduced operational risk through monitoring, retrigger workflows, and transparent error handling
-
Scalable architecture to handle 1M+ transactions per year
-
24/7 production support model with clear responsibilities and operational tooling
-
Long-term stability through a 5-year support commitment
What We Built / Solution
SAP Integration and Message Transformation
-
Integrated the client SAP landscape via D4S interfaces
-
Transformed SAP messages into the external provider’s message structure to ensure interoperability
-
Supported SAP-side improvements required for consistent end-to-end integration
Reliability Tooling and Operational Workflows
-
Monitoring and health checks for the interface layer
-
Tools for the client’s IT team to validate that message flows were working
-
Workflows to retrigger failed messages safely and traceably
-
Clear operational visibility for incident handling and escalation
24/7 Support Setup
-
Designed for continuous operations in a 24/7 production environment
-
External company handled technical support operations
-
Defined processes and tooling to ensure predictable handover and troubleshooting
Architecture Highlights
-
Deployed on Azure AKS (Kubernetes) for scalability and operational resilience
-
Built for high throughput and long-running stability
-
Designed with robust error handling and recoverability as first-class features
My Role
In this project I worked as:
-
Technical Lead
-
Team Lead
-
Responsible for support and infrastructure
I owned the technical direction, ensured delivery quality and operability, and took responsibility for the support model and infrastructure setup.
Technologies
-
C# / .NET (ASP.NET Core)
-
Java
-
SQL Server
-
Angular
-
React
-
SAP integration
-
D4S integration interfaces
-
Azure
-
Azure AKS (Kubernetes)
-
Docker
-
Microservices architecture
-
Event-driven architecture (messaging / asynchronous integration)
-
Machine / IoT integration
-
User management / Identity & access control
-
WYSIWYG workflow & app editor (CMS / process modeling)
-
Monitoring, alerting, and operational tooling
-
Workflows for retry / reprocessing
Additional information
| Budget | High five-figure range |
|---|---|
| Duration | 1,5 Years |
| My Role | Support Lead, Team Lead |
| Sector | Automotive, Logistics |
| Team Size | 13 |
| Technologies | Angular JS, Azure, Chat GPT, DDD (Domain Driven Design), Docker, Kubernetes, SAP |





