DevOps at De Lijn: Automating manual processes for 85% faster deployments
Robust corporate applications and faster time-to-market with IBM Cloud Pak solutions
15 December 2020
Kilian Niemegeerts
- Reduced deployment time from 2 weeks to 2 days through automation
- Decreased weekend deployment team from 5 FTEs to 2 FTEs
- Successfully migrated 65 applications to a container-based platform
- Eliminated manual procedures through automated deployment pipelines
Buried in deployment documentation? Multiple departments needed for each release? De Lijn faced these challenges with their corporate applications platform, where each deployment required extensive manual procedures and large weekend teams.
The Challenge: When manual becomes unmanageable
De Lijn’s application landscape needed modernization. Their business-critical applications ran on out-of-support Java versions, and deployments relied heavily on manual processes. Each release required detailed documentation, multiple team members, and precious weekend hours. With five full-time employees needed for weekend deployments, the process was both resource-intensive and time-consuming.
Breaking free from traditional IBM WebSphere
The first step was clear: move away from traditional IBM WebSphere ND servers. We implemented IBM Cloud Pak for Applications with Red Hat OpenShift as the foundation. This modern container platform provided the perfect base for integrating their 65 existing applications.
The combination of IBM WebSphere Liberty and IBM Cloud Pak for MultiCloud Management created a lightweight, modular solution. This new setup didn’t just modernize their infrastructure – it transformed how teams worked together.
Automating the development lifecycle
Where previously developers and operations worked in silos, automated pipelines now bridge the gap. Development teams gained clarity about deployment outcomes, while operations teams could easily identify and communicate issues.
The proces went beyond tools:
- Manual deployment procedures reduced to a few essential actions
- Automated testing ensures consistent quality
- Clear feedback channels between development and operations
- Containerization making application failures easier to handle
The impact: Faster deployments, better collaboration
The numbers tell a great story. Deployment cycles dropped from two weeks to just two days. Weekend deployments now need only two team members instead of five. But the real victory lies in the improved collaboration between departments.
Development teams now have clear visibility into the deployment process. When issues arise, operations can quickly pinpoint and communicate problems, leading to faster resolutions. The automated pipelines ensure that what works in development makes it successfully to production.
Looking ahead, De Lijn’s modernized platform isn’t just about faster deployments – it’s about building better applications. This project has created stronger inter-departmental collaboration, setting the foundation for continued innovation.
Want to learn how your team could achieve similar results? Let’s talk about modernizing your application platform and transforming your deployment process.
Sorry, the comment form is closed at this time.