Skibsteknisk Selskab. Standard on Software Maintenance of Shipboard Equipment. Chief marine technical officer Aron Sørensen

Transcription

1 Skibsteknisk Selskab Standard on Software Maintenance of Shipboard Equipment Chief marine technical officer Aron Sørensen

2 Our Members - DWT of Owner Members

3 Our 2,300 Members by Category Owners Brokers Agents Clubs Associate members New Private Maritime Security Companies (require certification from ISO) Members 31 October % 8% 14% 34% 34% Owners Brokers Agents Clubs Associates

4 Example no 1 Ship, June 04 Good day, V/L is in the window period for surveys (3rd Apr to 3rd Oct) Personal preference would be for annuals Algeciras 14th July. Company, June 05 Good day, Ref below , please arrange annual radio service and VDR APT for XX Annuals due: Safety equipment, safety construction, safety radio, cert of class, loadline, iopp, doc imdg, app 4

5 Example no 1 continued Service provider, 16 June Good day, Please provide following details to arrange Annual Radio Survey & VDR APT at Algeciras on 14/07. Please revert with the status of all Navcom equipment working normal and if any deficiencies noted please advise accordingly to rectify. Please advise last gyro annual overhaul dates, magnetron running hours etc. Please advise expiry dates and battery renewal dates of below : EPIRB 1 (AUT) HRU For EPIRB 1 EPIRB 2 (MAN) SART 1: SART 2: Portable GMDSS VHF 1 Bat: Portable GMDSS VHF 2 Bat: Portable GMDSS VHF 3 Bat: Any additional equipment noted please add to above list. Please revert with make/model of VDR/SVDR also the status equipment working normal and if any deficiencies noted please advise accordingly to rectify. 1: Please check that there is no WARNING / ALARM for the system. 2: please advise VDR Capsule Beacon expire date 3: please advise VDR PSU battery expire date 4: please advise VDR serial number 5: please advise backup battery condition/last renewal date 5

6 Example no 1 continued Company, June 18 Good day, Please provide following details to arrange Annual Radio Survey & VDR APT at Algeciras on 14/07. Please revert with the status of all Navcom equipment working normal and if any deficiencies noted please advise accordingly to rectify. No defects noted. Please advise last gyro annual overhaul dates, magnetron running hours etc. Gyro 1&2 Last Overhaul 02 July 2014 S Band, On Time: H, TX Time: H, magnetron renewed Feb 2014 X Band, On Time: H, TX Time: H, magnetron renewed Feb 2014 Please advise expiry dates and battery renewal dates of below : EPIRB 1 (AUT) Batt Expires: Dec.2018 HRU For EPIRB 1 HRU: Jan.2017 EPIRB 2 (MAN) N/A SART 1: Expires: May 2017 SART 2: Expires: May 2017 Portable GMDSS VHF 1 Bat: Expires Jan.2017 Portable GMDSS VHF 2 Bat: Expires Jan.2017 Portable GMDSS VHF 3 Bat: Expires Jan.2017 Any additional equipment noted please add to above list. Nil Please revert with make/model of VDR/SVDR also the status equipment working normal and if any deficiencies noted please advise accordingly to rectify. Make: Furuno, Model: VR3000, 1: Please check that there is no WARNING / ALARM for the system. Nil alarms 2: please advise VDR Capsule Beacon expire date Expires: Sept : please advise VDR PSU battery expire date Batteries Built in DCU Expires: May : please advise VDR serial number S/N : XXXX-XXXX 5: please advise backup battery condition/last renewal date Unknown 6

7 Example no 1 continued Service provider, 22. juni (early morning) Good day, Please be informed that we are planning Annual Radio, VDR APT & both Gyro service at Algeciras on 14/07. Kindly confirm if same can be arranged & advise quotation. Company, 22 June (15 minutes later) Good day We confirm attending for radio survey and VDR APT in Algeciras 14 th of July. Best Regards 7

8 Example no 1 continued Company, 13 July //URGENT// Good day, As per attached message from Master it seems there is some confusion regarding service arrangement. Please note we had given PO & go ahead well in advance on 26/06 hence there is no reason of service not arranged. Please treat this as urgent & confirm attendance tomorrow on 14/07. Service Provider, 13 July (last mail) Good day, We confirm service arrangements is confirmed. A technician will attend onboard tomorrow morning. Kindly let us know the technician contact details. 8

9 Example 1 is illustrating that Details about hardware are readily available (make, batteries, replacements). We are moving from a hardware towards software regime. Would a ship be able to provide same detail for software in the mentioned systems? What do we need to get such information? It is a one way communication: Ship and company provides details to service provider and nothing comes back. The ships does not even know the name of the person who comes on board(security etc.). How can this be improved? 9

10 Example 2 After black out due to repair cooling water valve 19/2-10, we have got at problem with flexview. It keeps coming up with failure: Failure no 3633 (Cant Load DLL: MSJTER35.DLL Module frm Card Failure Procedure: add failure Line Choices are to press continue or exit program. If pressing continue the error comes back after some seconds/minutes. We have tried to restart a couple of times and same error comes back. Now the pc is blocked and we can not operate from pc in ECR. But the engine is running ok. 10

11 11

12 Example 2 is illustrating that This is quite serious! No readout from the engine. The ship was able to go to the next port, while trying to fix the problem by correspondence. This is one of many examples with software systems after a black out How can software testing procedures be improved before release? 12

13 Example 3 Antenna problem a service provider from another company than the original manufacturer comes on board The technician has problems, he cannot update the existing software, so he decides to install a new version of the software The problem is that the original manufacturer does not support the version that is being installed 13

14 15-17 October 2015 W Seoul Walkerhill Hotel, Seoul, Republic of Korea 14

15 Example 3 Good day, Please find service report attached - FBB has been checked and found OK. Good day Captain, Noted your below with thanks. Please note, Software has been upgraded to a version not accepted by XX. We believe instruction for downgrade might be available on board which was forwarded by XX During EVC migration. Can you please check if staff on board can do the downgrade to version 1.19? Only version accepted by XX is

16 Example 3 is illustrating that The software in the antenna tracking module (ATM) can lead to total failure of software, making it impossible to connect / communicate at service level! No body told the technician to replace software version. This is not aligned with the policies of the manufacturer. How can we ensure better co-operation between service provider, master, owner and manufacturer? How can we avoid that integration of software has a negative influence on other software? 16

17 To reply the answers we decide to develop software maintenance guidelines In 2013 BIMCO and CIRM decided to form a joint working group appropriate procedures to manage software updates Version 0.1 of a draft standard ready in March 2014 Version 1.0 ready in December will be used to try it in real life Next step submission to ISO/IEC 17

18 Objectives Need to address software maintenance systematically Create a generic model that can be applied in all circumstances Make sure all links in the chain of execution is included Focus on ship equipment not admin IT 18

19 Important features Testing should be robust when developing software Software must be designed with serviceability in mind Role-back to previous safe state in case of errors during update Cyber-security requirement are integrated in the standard Systems and integrations must be properly documented Updates to be documented for new features, fixes and training needs 19

20 Software maintenance process flow Event initiation Bug fix, Feature release, Compliance update Planning Where and when Best service engineer for the job Onboard software log Remote maintenance time slots Competent technician to be appointed Execution Execution and control Cyber security Prepare for role back Authorisation, Diagnostics After service Service report and onboard software log Evaluation and feedback The quality assurance and control 20

21 Table 1 - Software maintenance competency requirements Scope of job Competencies 1 Simple preventative and corrective maintenance activities such as operational inspection and execution of minor software updates. 2 Minor preventative and corrective maintenance activities such as adjusting configuration settings and conducting basic performance testing. Replacement of software to address bugs, add new features, maintain compliance with changing rules/regulations, etc. 3 General and emergency preventative and corrective maintenance activities such as trouble-shooting, advanced performance testing such as Annual Performance Tests, and advanced diagnosis of operational anomalies. 4 Major or complex preventative and corrective software maintenance activities such as major software upgrading that require knowledge beyond that held by the Service Role. +i When action performed may affect the functionality of equipment beyond the equipment undergoing the change (i.e. performed on integrated systems). Crew level -General basic technical knowledge Technician level -General basic technical knowledge -Specific technical product knowledge Senior Technician level -General basic technical knowledge -Specific product knowledge -Specific system knowledge Specialist level -General technical knowledge -Specific product knowledge -Specific system knowledge -Technical system specialization Integrator level -General basic technical knowledge -Specific product knowledge -Specific system knowledge -Multi-disciplinary system knowledge 21

22 Electronic service report Ship details (Shipowner; Ship name; IMO number; Maritime Mobile Service Identity MMSI; Last call). Service Role details (Name of company; Name of technician, Employee ID) Shipboard equipment details (Make; Type; Serial number; Model) Software details (Previous software version, Current software version, Last update applied, Last error generated) Status (Description of the equipment and software on arrival and after job completion) 22

23 Ship software log Ship details (Shipowner; Ship name; IMO number; Maritime Mobile Service Identity MMSI); Service Role details (Name of company; Name of technician, Employee ID); Shipboard equipment details (Make; Type; Serial number; Model); Software details (Previous software version, Current software version, Last update applied, Last error generated); Initiator (Producer/System Integrator/Service/Shipowner Role); Criticality (Rating); Status (Description of the equipment and software on arrival and after job completion). 23

24 Future work Modernisation of software used for equipment is needed (Windows XP is dead) Getting the guidence implemented with Shipowners, Manufacturers, Yards, Class and other stakeholders Seek to promote as ISO/IEC standard 24

25