Case study
- Customer
- International Shipping and Logistics Conglomerate
- Industry
- Shipping and Logistics
- Technologies
- Microsoft Azure
- Docker
- MySQL
- Apache
- Beanstalkd
- Connected Vessels
- 100+
- Specialist Users in the System
- 30
- Months Project Duration
- 10
Contents
Initial Situation
The EDCenter (Engine Diagnostic Center) was running in single-server mode: one installation, all customers as tenants on it, with operations and data hosted by ATESO. The conglomerate wanted to operate the application in its own corporate cloud — in its own Azure tenant, with its own certificates and connected to the company-wide login.
Solution
The foundation is the containerized version of the EDCenter. It is not a special build for this customer, but the operational form of the product: the same image can be operated in a customer’s public cloud, in their data center, or continued to be hosted by ATESO. Between January and November 2024, ATESO deployed this version in the conglomerate’s Azure tenant, extracted the data from the shared system, and supported the rollout to the fleet.
| Work Package | Content |
|---|---|
| Containers and System Services | Web server, database (MySQL), Beanstalkd as queue manager, email delivery, Laravel configuration for standalone operation, cron jobs, backups on the same machine as daily, weekly, and monthly dumps |
| Data Migration | Extraction of data from the production multi-tenant system, preparation of metadata: parameters, curves, limit values, error cases |
| Customer-Specific Configuration | Recording fleets, vessels, engines, and cylinders; creating administrators, 80 DocSoft users, and manager roles; populating master data, limit values, and shop test curves |
| Single Sign-On | Integration of Microsoft Entra ID authentication into the EDCenter, mapping the Azure login to the local EDCenter user |
| Testing and Go-Live | Deploying containers in the customer’s public cloud, setting up production encryption certificates, distributing the adapted host URL to the data acquisition devices, verifying data transmission |
| Documentation | Handover of operational and configuration documentation |
From Single-Server Operation to Cloud-Ready Architecture
The migration shifts less the functional scope than the location and responsibility:
| Before | After | |
|---|---|---|
| Operation | One server, all customers shared | Containers per installation |
| Location | ATESO infrastructure | Customer’s corporate cloud (Microsoft Azure) |
| Login | Own user management in the EDCenter | Single sign-on via Microsoft Entra ID |
| Addressing | Shared certificates and host URL | Own certificates, own host URL on the data acquisition devices |
Result
Since mid-November 2024, the EDCenter has been running in the conglomerate’s Azure tenant. Over 100 vessels are sending their operational data to the dedicated instance, around 30 specialist users are working with it, and they log in via their existing Azure account.
Operation and Further Development
With the rollout, the project was not concluded. ATESO continues to support the installation and works closely with the conglomerate’s specialists: requirements from daily operations go directly into the further development of the EDCenter, instead of remaining in a backlog.
What matters is where they go — not into a fork for a single customer, but into the shared product base. What an operator triggers is available to all installations with the next release. This allows requirements from different fleets to flow into the same codebase, instead of getting lost in individual solutions that no one can maintain jointly anymore.
About the author
Engineering