1. 0 What to include in your IT infrastructure project: from business case to delivery Walter Hannemann

2. TORM 1 Offices in Denmark, India, Singapore, Philippines and USA. Approx. 70 vessels, mostly product tankers. All equipped with a state-of-the-art Vessel IT infrastructure Dedicated Vessel IT team

3. What to include in your IT infrastructure project: from business case to delivery Global infrastructure – nothing like on shore Business case: focus on business benefits. IT benefits are just not enough Requirements – not IT but business – what is the business strategy? 5 year strategy? Design and architecture: do not leave anything as an afterthought. Do not retrofit your design. Include IT security from the start. Include disaster recovery. Vendor lock-in. Good or evil? Data communication: how much are you in control? Rollout to vessels: Where? When? How to reduce uncertainty and failure risk – staging part How to deal with needed competencies – or the lack of them Documentation How to report and communicate Change management Measure the results as you go 2

4. Global infrastructure – nothing like on shore 3 Is 2Mbps really broadband? 50Mbps? What about latency? And price? Not all current technologies apply directly

5. Business case: focus on business benefits. IT benefits are just not enough Avoid variable OPEX costs What is the biggest benefit? The bridge itself or everything that benefits from it? Map the indirect benefits. OPEX and the variable costs? Select as many fixed cost solutions as possible. 4

6. Requirements – not IT but business What is the business strategy? Where do you want to be in 5 years? 5 Requirements should be tied to an overall strategy You can only deliver to the business case if aligned to the strategy Remember the Triple Constraint and work in the scope/quality balance – but you still can pick only two!

7. Design and architecture Do not leave anything as an afterthought Do not retrofit your design Think about the longer term Consider changes – the ones you know and the other ones Be ready for new technologies Include IT security from the start Include active monitoring and disaster recovery 6

8. Vendor lock-in. Good or evil? Can you ensure a common vendor for all vessels? What if you have vessel take-overs? What about short-time assignments? Can your infrastructure live with any present and future changes? Would your vendor(s) agree with a more diverse solution landscape? 7

9. Data communication: How much are you in control? Do you measure yourself? Do you administer capacity directly? How are the reports made and with which objectives? Who and what is using what? Is it all or there are leaks? 8

10. Rollout to vessels: Where? When? How? Logistics of sending equipment – how fast, how expensive Installation teams: How many? What competencies? Tools and insurance Visas HRA Sailing or not with the vessel Hidden or unprecise position information 9

11. How to reduce uncertainty and failure risk Hardware fails; software fails Processes fail Deal with failures close to home and resources Test and verify Update everything on “real” broadband Use the [expensive] experts on shore 10

12. Include everything you need You can’t go to the shop next-door 11

13. How to deal with needed competencies – or the lack of them 12 Installation is more than only IT How many technicians do you have available? Are they also running operations and support?

14. Documentation Who is reading it? Technical, at what level? Stakeholder management and project documents 13 Interpretation

15. Documentation Who is reading it? Technical, at what level? Stakeholder management and project documents 14 No need for interpretation

16. How to report and communicate Focus on the different stakeholders: users onboard (officers and crew), shore staff, management. Focus more on the practical i.e. write informational articles about the changes and how to use them Write practical user guides Send user guides several times Be ready to answer the same questions over and over again 15

17. Change management 16

18. Measure the results as you go – and report What did you promise? Are you delivering? Evaluate concrete (IT) and soft benefits 17

19. What’s next? Use it! Develop new services. Gather and utilize data. That’s how you realize the benefits. 18

20. 19 Walter Hannemann Head of Systems, Technical Division wah@torm.com Thank you!