Björn Klinger, T-Mobile Austria & Thorsten Guggenberger, CEO J-IT Wir geben einen kurzen Überblick über die Evaluierung der BPM Engines und allgemeine Informationen weshalb die Entscheidung letztendlich auf Camunda gefallen ist. Die ersten Schritte bis zum Einsatz in der Produktion & darüber hinaus die fortwährende schrittweise Ablösung der Legacy Systeme im Einklang mit dem Daily Business.

1. Replacement of Legacy
workflow engine at
T-Mobile Austria GmbH
www.j-it.at

2. … a journey from Oracle
Workflow (OWF)
to Camunda BPM
… Q&A at the end of the presentation
www.j-it.at

3. 3
• Björn Klinger
T-Mobile Austria GmbH (TMA)
IT Technical Order Execution & Middleware
Senior Manager
• Thorsten Guggenberger
”J-IT” IT-Dienstleistungs GesmbH (JIT)
CEO & founder of JIT
Who we are?
www.j-it.at

4. 4
• JIT’s role at TMA
• TMA’s middleware
• Reasons for replacement of OWF
• Mission statement
• Evaluation process
• Daily life with Camunda BPM
Overview
www.j-it.at

5. 5
• Supported TMA during bpm engine evaluation
- Cover technical aspects regarding specific solutions
- Evaluate development process, tools
- Participate in PoC workshop & validate result
• Get pilot ready for production
• Daily work
- Integrate new business processes
- Stepwise replacement of legacy workflow system
JIT’s role at TMA
www.j-it.at

6. The middleware at
TMA - architecture
System ..
System 4
System 3
System 2
System 1
DB ...
DB 4
DB 3
DB 2
DB 1
Middleware
Direct
Procedure
SOAP
www.j-it.at

7. 7
• Runtime is Oracle DB
• Execute PL/SQL and Java
• Process definitions in proprietary format (wft files)
• Oracle Workflow Builder
- Tool for process design and deployment
• Good support for error handling
- e.g. batch retries, skip, jump, etc.
The middleware at TMA - Oracle
Workflow
www.j-it.at

8. 8
Oracle Workflow Builder
www.j-it.at

9. 9
• Latest supported database: 10.2
• End of life: 2010/2013
• Difficult setup for local development
• Only Java 6 supported
• wft files hard to maintain
• Ancient look-and-feel of tools
• Code collaboration not supported
Reasons for replacement of OWF
www.j-it.at

10. 10
• Replace OWF with state-of-the-art business process solution
• Embed new solution in existing system landscape
- Parallel operation with existing solution
- Step-by-step replacement
• Focus on operational needs
- e.g. batch retries, skip, jump, etc.
Mission statement
www.j-it.at

11. 11
• Requirements document
- approx. 140 funct. and non-funct. Req.
• Two-days workshop at TMA
- presentation of working sample
- discuss technical details and concrete implementations
• Evaluation of workshop
• Optional follow-up: PoC workshop
Setup of RFT
www.j-it.at

12. First candidates
www.j-it.at

13. 13
• Supports process and case management
• Proprietary solution
- Non-standard notation
- Own tool set
• Why scrapped?
- Despite T-Mobile discount very costly
First candidates: Oracle BPM Suite
www.j-it.at

14. 14
• Broader scope
- Replacement for workflow engine and product catalogue
• Closed source turnkey solution
• PoC implemented
• Why scrapped?
- No own or third-party developers allowed to develop on that stack
First candidates: Netcracker
www.j-it.at

15. The candidates 2014
www.j-it.at

16. 16
• Working sample presented
• Clearly structured documentation
• Mature product, but missing features
• Deep technical insights
• Focused on TMA’s needs
- possible product extensions
- solutions for specific req. of TMA
The candidates: Camunda
www.j-it.at

17. 17
• No working sample presented
• Huge amount of documentation
• Mature solution
- Several products required
- Still missing features
• Superficial technical insights
• Focused on own products
The candidates: RedHat
www.j-it.at

18. 18
• Working sample presented
• Structured documentation
• Product with many missing features
- Clear gap between requirements and feature set
• No container deployment
• No experience with high throughput project at that time
The candidates: Activity
www.j-it.at

19. And the winner is...

20. 20
• Working sample at RFT workshop
• Deep technical insights
• Mature product
• Commitment to extend product
- roadmap for implementation of missing features required by TMA
• Easy setup of dev environments
• Easy to learn for java developers
And the winner is... Camunda
www.j-it.at

21. 21
• Interworking between legacy (OWF) & Camunda works very well
• High perception from business & IT
• Reduced development costs (approx. 30%)
• Given promises in 2014 have been kept
• Housekeeping features delivered
- Token manipulation (jump to arbitrary activity)
- Process instance restart (for finished or canceled instances
- Batch restarts
• Operational safety provided
Camunda BPM since 2015
www.j-it.at

22. 22
• Stable product & excellent performance
• Supports state of the art development & delivery tool chain
• Operational business process issues per month less than < 1%
• Camunda BPM framework handles technical challenges and helps
business to take care of the real challenge, i.e. focusing on
organization & business know how
• Look forward: Camunda candidate for Microservices collaboration
Camunda since 2015
www.j-it.at

23. 23
Thanks
Any questions?
www.j-it.at