The Challenges of Change

Size: px

Start display at page:

Download "The Challenges of Change"

Samantha Powell
6 years ago
Views:

1 The Challenges of Change José Gisbert ICT Manager MSC Terminal Valencia S.A.U. 1 st International Workshop, November2014

2 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

3 The Challenges of Change Who we are TIL MSCTV A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

4 Who we are TIL Company Profile Terminal Investment Limited SA (TIL) invests in, develops and manages container terminals around the world. It was founded in 2000 to secure berths and terminal capacity in the major ports used by Mediterranean Shipping Company (MSC). Joint Ventures Most of TIL's terminal interests are in joint venture owned with one other international terminal operators (ITO). Clients MSC is our largest customer Others mainly thanks to the Joint Ventures

5 Who we are TIL Terminals 34 terminals in 25 world trade ports

6 Who we are TIL Terminals Top 10 terminal operators (2012)

coastline (8,000 km) VALENCIA Center of the Mediterranean for oceanic traffic Area near the

7 Who we are MSCTV Geographical Situation SPAIN Conveniently situated near major maritime trade routes Logistics platform for Southern Europe European country with the largest area of the coastline (8,000 km) VALENCIA Center of the Mediterranean for oceanic traffic Area near the Suez-Gibraltar axis Leader among Spanish and Mediterranean ports Logistics area network within 20 km

Who we are MSCTV Background and Objectives Start of construction in 2005 Start operating in October 2006 Fully operational in July 2007 Function as a

8 Who we are MSCTV Background and Objectives Start of construction in 2005 Start operating in October 2006 Fully operational in July 2007 Function as a dedicated terminal for ships and services operated by MSC in the Port of Valencia. The Port of Valencia is used by MSC as its main hub in the West Mediterranean.

9 Who we are MSCTV Terminal Data YARD LAYOUT Surface: m2 Quay Length: 770 m Number of berths: 2 TERMINAL CAPACITY Capacity full containers: Capacity empty containers: Reefer Connections: 488 CRANES 8 Ship to Shore Cranes, last generation Super Post-Panamax ROLLING EQUIPMENT 26 RTG s 7 ReachStackers 4 Empty Container Handlers 57 Tractors 58 Trailers 1st International Workshop, 14-15/10/2014

10 Who we are MSCTV Terminal Data GATES 4 entrance gates 3 exit gates Administrative check area with parking WORKFORCE 80 Blue collar (subcontracted for Maintenance, Gates and 5 IT Helpdesk) 81 White collar Up to 290 Dockers per day(4 shifts) depending on volumes

11 The Challenges of Change Who we are A TOS migration? Why? Next Steps Careful! Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

12 A TOS migration? Why? Cosmos WorldWide (PSA owned) stops its commercial activities in 2009 This is a high risk issue for TIL terminals (some of them working with COSMOS TOS) Next steps Look for its own corporate TOS (like PSA, Hutchison, APMT, DP World) TOS Study (2010) We compared 8 TOS suppliers (RBS, TSB, NAVIS, etc.) MSCTV s particular situation (NOATUM uses CATOS from TSB) MSC uses CASP from TSB for its fleet Plan a migration Project start in February 2011 First objective is to Go-Live in April 2012

13 A TOS migration? Careful! MARVALSA (NOATUM today) (From Own Software To CATOS) March 4 th 2006 TOS Change A lot of issues delivering containers through the gates March 27 th 2006 Strikes planned due to the failures of the new TOS DP World Australia (NAVIS Upgrade N4) April 2013 Truck queues at DP World in Melbourne MAHER Terminals NYC (NAVIS Upgrade N4) June 2013 TOS Change. Communication not working as designed between the TOS and the straddles Hundreds of containers stuck inside the terminal and hundreds of ships needed to deviate to other ports to deliver their containers

14 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

15 Main Goal Achieve a SEAMLESS migration

16 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result 1st International Workshop, 14-15/10/2014

17 The Team Multidisciplinary team Project Manager (Hired specifically for the project in December 2010) Operations Team 11 SuperUsers (2 years before Go-Live) Test Manager function executed by Operations Manager supervising all SuperUsers and preparations IT Team 1 additional Systems Expert 6 months before Go-Live to 4 months after 1 Developer Start working in Shifts from Go-Live to 2 months after Extended Helpdesk Team 5 extra for 24/7 on-site support (from 2 months before Go-Live to 5 months later) 6 extra for additional Go-Live support 1st International Workshop, 14-15/10/2014

18 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result 1st International Workshop, 14-15/10/2014

19 Side Projects Virtualization of old servers New UNIX Servers for Production environment ORACLE database servers Upgrade Wi-Fi infrastructure Install new 5.2GHz infrastructure Migrate RTGs and Quay Cranes to 5.2GHz technology Install new Access Point in RSs and ECHs Upgrade Quay Cranes PCs to make them touchable New PDS system for RSs and ECHs Install VMT on RSs and ECHs New Stress Testing Tool for CATOS RFID project cancelled a few months before Go-Live due to lack of time and set backs

20 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests SW and HW tests Go-Live rollout / rollback tests SQA Training Background Safety Net Go-Live The Result

21 Tests SW and HW tests SuperUsers We received a copy of CATOS software from PCT (proposed technological platform for MSCTV) Testing the software for 2 years and proposing new functionalities, discovering bugs, etc Real life testing of CATOS in parallel with Production Environment (COSMOS) 18 tests in all possible shifts IT Test HW and SW to make it robust and reliable Create a Disaster Recovery Plan and test it Test the throughput of the system by using a Stress testing tool and run it for every patch and upgrade made to the system to accept the patch or upgrade.

22 Tests Go-Live Roll-Out / Roll-Back tests Preliminary tests Unitary tests to control times of deployment of the solution in different PCs, VMTs, RTGs, QCs, Data Migration, etc. First half Roll-Out / Roll-Back test (March 19 th 2013) We chose a set of RTGs, PMs, QCs, RSs, ECHs, PCs to migrate them to the new system and then back Full Roll-Out / Roll-Back test (May 1 st 2013) We migrated all devices, cranes, PCs to the new system and back

23 Tests SQA (Software Quality Assurance) The Software had to be free of critical and high priority issues before going live This and all the customizations required by the SuperUsers delayed the project go-live two times MSCTV hired a specialized company in high volume stress testing (Hamburg Port Consulting) to assure the reliability and the correct performance of the whole system.

24 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

25 Training IT New Helpdesk team was trained in COSMOS Production environment and replaced our core Helpdesk team IT trained our core Helpdesk team in all new CATOS software and systems Core Helpdesk team trained Extended Helpdesk team in new CATOS environment SuperUsers SuperUsers trained all Operations users (45 internal staff) Dockers (178 from the labor pool, SEVASA) Other Subcontractors (16 in Gates and yard checkers)

26 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result 1st International Workshop, 14-15/10/2014

27 Background Safety Net An extra Helpdesk team was hired secretly to enter all moves created in CATOS into COSMOS just in case we had to Roll-Back. In this case the Roll-Back would only cost the time to Roll-Back all the devices, PCs, RTGs, QCs, etc. Once all Roll-Back would be finished, COSMOS would be up to date. 1st International Workshop, 14-15/10/2014

28 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result 1st International Workshop, 14-15/10/2014

29 Go-Live Postponed 3 times because the software did not comply with Operations necessities Stop date was Saturday June 1 st 2013 at 2 p.m. We stopped for 3 shifts Go-Live date Sunday June 2 nd 2013 at 8 a.m. Started with 85% of the operational capacity concentrating on the ship operations. If Go-Live would have failed, only ship operations would have been affected and no trucks nor Port Community would. Gates Go-Live was on Monday June 3 rd The Point Of No Return was set to the end of the Gates shift on Monday June 3 rd These dates were selected taking into account the impact on all stakeholders 1st International Workshop, 14-15/10/2014

30 The Challenges of Change Who we are A TOS migration? Main Goal The Team Side Projects Tests Training Background Safety Net Go-Live The Result

31 The Result Achievements A SEAMLESS Migration Zero impact on volumes Increased productivity

32 Keep Calm and Go Live IT Migration Team

33 Thank You Partner Logo José Gisbert Cano ICT MSCTV jgisbert@msctv.es

Optimization of Terminal Operations September 23, Navis, LLC. All other trademarks are the property of their respective owners.

Optimization of Terminal Operations September 23, 2016 A Quick Detour from Ports Vehicle Dispatching Systems Drivers Riders Match Technology Enablers & Mobile Devices Mapping Billing & Accountability Reporting