This page contains a Flash digital edition of a book.
Feature 4 | DECK EQUIPMENT AND MACHINERY


and Containers, in 2008, that the following amendments should also be applied to the current CSS Code. Te report to the MSC stated;


• 5.1 Te Sub-Committee recalled that DSC 12, having established the working group


• 1) noted the group’s views on the best way to disseminate information on local


on providing safe working conditions for securing of containers and the CSS Code and having considered the report of the working group (DSC 12/WP.4) in part relating to the item, took action as follows:


regulations, particularly the Russian Federation rules for safe carriage of cargoes by sea, form for cargo information and method of calculation of non-shiſt criterion for structuralising cargoes, relevant to specialised cargoes and regional trade, contained in document DSC 12/8 (Russian


• 2) agreed to the deletion of proposed amendments to the CSS Code contained


Federation), and that it could not reach an agreement on this issue and decided to request the Secretariat to consider the options suggested by the group and advise DSC 13 accordingly;


in the sections 7.2 (Container stowage) and 7.3 (Containership condition report) of the proposed amendments to the CSS Code contained in the annex to the report of the correspondence group (DSC 12/10/1). However, it also agreed that matters on container stowage should be taken into account when the Guidelines for the preparation of the cargo securing manual (MSC/Circ.745) is further considered for amendment. Additionally, the Sub-Committee noted the group’s opinion that the proposal on the Containership


Lloyd’s Register delivers software for safer operations


Lloyd’s Register has developed and released its latest container-securing rules and software that will provide a framework that is safer and more effective with the use of modern ships. The new rules have been developed along with the assistance of major container-shipping lines and manufacturers of lashing equipment. “These rules are the culmination of a great deal of detailed work with operators, builders, designers and port


operators,” said David Tozer, Lloyd’s Register’s global business manager for container ships. “Safety, as always, comes first. But ensuring flexibility in loading and discharging operations is vital for operators. So these new rules were created to combine safety and flexibility, allowing more sophisticated and varied container stows to save time and expense in port.” The rules and software follow last year’s release of Lloyd’s Register’s Guidance on Ergonomic Container Lashing (ECL), supported by the ECL notation. The main benefits of the latest set of rules from Lloyds Register are; • a reduced risk of losing containers overboard, with associated environmental risks and cost • a reduced risk of loss of life or serious injury to stevedores and crew engaged in container lashing • more effective lashing techniques for new, much larger, container ships • increased potential for innovative and flexible lashing designs and arrangements • increased flexibility in the allowable weight of containers in certain configurations. Lloyd’s Register’s LashRight software is the latest in the Group’s dedicated container-securing software. It calculates


the forces acting in lashed and unlashed stacks on deck and validates the results against the requirements contained in Part 3 of Lloyd’s Register’s Rules and Regulations for the Classification of Ships. LashRight can quickly identify areas which have failed the assessment, helping designers to make the required


changes to container arrangement, weight distribution or lashing equipment. This helps to ensure compliance with requirements and reduces the risk of containers being damaged or lost overboard.


Key features of the software include;


• step-by-step ‘wizards’ help designers to carry out analyses quickly and efficiently • calculations are performed in real time; changes are accommodated as they are made • results are calculated for pitching, rolling and combined conditions, in accordance with the Rules or user requirements • covers industry standard containers and lashing equipment, or users can add custom specifications to the software’s library.


126 The Naval Architect September 2010


• 3) noted the progress made on the draſt amendments to the new annex to the


condition report (document DSC 12/10/1, annex, section 7.3) had merit; and


• 5.2 Te Sub-Committee noted that there were three issues for consideration, namely


CSS Code, further noted that, due to time constraints, the group was not able to finalise the draſt amendments to the CSS Code and agreed to invite the Committee to extend the target completion date of this item to 2008.


means of dissemination of information on local regulations, information on the joint industry research project Lashing@Sea and the finalisation of the CSS Code.


Lashings@Sea is a joint industry research


project that aims to prevent lashing systems from failing and to increase safety and lashing


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164