1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T L.55TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2003) SERIES L: CONSTRUCTION, INSTALLATION AND PROTECTION OF CABLES AND OTHER ELEMENTS OF OUTSIDE PLANT Digital database for marine cables and pipelinesITU-T Recommendation L.55 ITU-T Rec. L.55 (11/2
2、003) i ITU-T Recommendation L.55 Digital database for marine cables and pipelines Summary This Recommendation describes the nature of the information regarding marine cables and pipelines that should be maintained by National or Regional government agencies which are responsible for marine shoreline
3、s, and the cable or pipeline installations that may either be present or added. Information about marine cable and pipeline installations can affect the cost of future installations or maintenance, including their environmental impact. At present, there is no global authority to maintain such inform
4、ation and the responsibility rests with individual countries. Given that information from multiple shoreline databases is necessary in designing new cable links, a standardization of the information that should be maintained will assist all participating parties. Such information is also useful in m
5、anaging shoreline infrastructure when cables and pipelines are decommissioned, thereby allowing the possibility of reusing the space. Source ITU-T Recommendation L.55 was approved on 28 November 2003 by ITU-T Study Group 6 (2001-2004) under the WTSA Resolution 1. Keywords Database, marinized terrest
6、rial cable, submarine cable, survey. ii ITU-T Rec. L.55 (11/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is respo
7、nsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the I
8、TU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborati
9、ve basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain man
10、datory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. Th
11、e use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU take
12、s no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual proper
13、ty, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may
14、be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. L.55 (11/2003) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and Definitions 1 4 Abbreviations 2 5 Overview 2 5.1 Regulating body 2 5.2 Owner/Operators 2 5.3 Installers . 3 5.4 Other commercial enti
15、ties. 3 6 Database contents . 3 6.1 Primary record 3 6.2 Activity record 6 7 Database initiation 6 7.1 Charts 6 7.2 Reports and logs . 6 7.3 Software 6 7.4 Security. 6 7.5 Infrastructure owners 7 7.6 Initial data. 7 7.7 Field survey 7 8 Maintenance 7 8.1 Charts and reports. 7 8.2 Contact point 7 App
16、endix I More information and justification on the need for marine infrastructure digital databases 8 BIBLIOGRAPHY 15 ITU-T Rec. L.55 (11/2003) 1 ITU-T Recommendation L.55 Digital database for marine cables and pipelines 1 Scope This Recommendation covers the reasons for maintaining a digital databas
17、e for marine cables and pipelines. It outlines the minimum contents of such a database and recommends procedures by which such databases can be initiated, maintained, and used. This Recommendation assumes that the creation and maintenance of these digital databases are under the responsibility of Na
18、tional or Regional government agencies that are responsible for the shorelines where marine cables or pipelines are terminated. This Recommendation does not mandate National or Regional regulations on data collection and dissemination, but does offer the possibility of determining a minimum set of d
19、ata needed. This Recommendation is applicable for the creation of digital databases to be implemented after it enters into force. This Recommendation is originated and maintained by ITU-T Study Group 6, “Outside plant“, which normally has within its scope construction, installation, and maintenance
20、of marinized terrestrial communication cables. The recommended database applies, however to the following, which are normally not in the scope of SG 6: Submarine telecommunication cables (ITU-T Rec. G.972); Submarine electrical power cables; Submarine pipelines. 2 References The following ITU-T Reco
21、mmendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are t
22、herefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a s
23、tand-alone document, the status of a Recommendation. ITU-T Recommendation L.28 (2002), External additional protection for marinized terrestrial cables. ITU-T Recommendation L.29 (2002), As-laid report and maintenance/repair log for marinized terrestrial cable installation. 3 Terms and Definitions Th
24、is Recommendation defines the following terms: 3.1 regulating body (RB): The National or Regional government agency that is responsible for maintaining records of a given portion of shoreline and the associated waters. 3.2 shoreline region: The shores and associated waters under the authority of a g
25、iven regulating body. 3.3 cable awareness charts (CAC): Detailed maps of the shorelines including the waters in the vicinity. These maps may or may not be digital, but should be numbered in a manner consistent with accessing them, based on a pointer. 2 ITU-T Rec. L.55 (11/2003) 3.4 transport infrast
26、ructure: The cable or pipeline that is deployed undersea with a shore termination. 3.5 terminating infrastructure: Buildings and protections at the interface of land and sea that are not part of the transport infrastructure, but which are part of the overall installation. 3.6 owner/operator: The ent
27、ity that holds the legal ownership of the transport and terminating infrastructure and the associated rights of way or real property. 3.7 installer: The entity that completes the actual installation. 3.8 local termination: The point within the shoreline region where a transport infrastructure termin
28、ates. 3.9 distant termination: The point outside the shoreline region where the transport infrastructure terminates. NOTE When a given transport infrastructure is terminated at both ends in the same shoreline region, there should appear two records in the database of the RB, one for each. For each,
29、the distant termination will be a reference to the other end. 4 Abbreviations This Recommendation uses the following abbreviations: CAC Cable Awareness Chart ITU International Telecommunication Union RB Regulating Body 5 Overview Information on the benefits of maintaining databases is given in Appen
30、dix I. It is assumed that one database is maintained by the RB of a given shoreline region. In many cases, the databases of multiple RBs may need to be researched before a complete new link design can be completed. While the position and condition of transport infrastructure that passes under the op
31、en sea may be available, this information is included only as an optional map pointer. The database for a given shoreline region can only be initiated and maintained with the cooperation of several parties, each with different responsibilities. The following outlines the roles of these parties: NOTE
32、 This Recommendation is applicable for the creation of digital databases to be implemented after it enters into force. 5.1 Regulating body Initiate the database (see clause 7). Communicate the requirements to owner/operators and installers. Maintain the CACs. Add new data to the database. Establish
33、database security policies and access requirements. Publish guidelines on sea surface transportation (shipping, etc.) and water use (fisheries) to prevent damage to transport infrastructure. 5.2 Owner/Operators Review the database before planning a new installation to avoid damaging existing infrast
34、ructure. ITU-T Rec. L.55 (11/2003) 3 Include the requirements of the RB in contracts with the installers. Require installers to conform to the requirements of ITU-T Rec. L.29. Conform to the requirements of ITU-T Rec. L.29 for maintenance. Inform the RB when the transport infrastructure is no longer
35、 in use. 5.3 Installers Check the database before proceeding with new installations. Conform to the requirements of the RB and ITU-T Rec. L.29. 5.4 Other commercial entities These include: Fishing authorities; Vessel owners and captains; Military authorities; Offshore oil operators; Port authorities
36、; Hydrographic offices. All these entities are responsible for reviewing and publicly following available guidelines from the RB. Those entities that may have database access are responsible for reviewing the database before engaging in any new programs that may cause infrastructure damage, or befor
37、e changing existing infrastructure. 6 Database contents The overall database consists of four primary elements, the first two of which can be digital. The others, which may exist only in paper copy, should be organised with identification numbers which can be referenced. These are: Primary records;
38、Activity records; Cable awareness charts; Installation and maintenance logs and reports. The primary records are for the retention of information that does not change much with time. They include a primary ID defined with the longitude and latitude of the termination point, along with a serial numbe
39、r for possible multiple items at a given location. They also contain information on the owner, installer, distant termination, charts, and other descriptors. They also contain pointers to the first and last activity records, which form a linked list. Every activity, including that of primary record
40、initiation is reflected by an activity record. These records indicate time dependent material such as record initiation, and pointers to various reports that may occur during installation, maintenance or decommissioning. The dates and identification of the person authorizing the data entry are among
41、 the items included in these records. NOTE This Recommendation is applicable for the creation of digital databases to be implemented after it enters into force. 6.1 Primary record Table 1 contains the recommended fields for the primary records. 4 ITU-T Rec. L.55 (11/2003) Table 1/L.55 Primary record
42、 fields Description Field Data type Notes Primary ID Longitude number This is the unique identification for each item of infrastructure Latitude number It is positional to allow the addition of future installations between current ones Serial number The serial number is used to distinguish between i
43、tems that are so close (they have the same location) Cable type Primary code 0 power line, 1 oil pipe, 2 gas pipe, 3 electrical telecom, 4 optical telecom with electricity, 5 all optical telecom Secondary code This secondary code is for local use to further differentiate types of infrastructure Perm
44、its Right of Way text These fields are provided to allow a pointer to local legal permits Property ID Construction text Owner Name text If the owner is not known, enter Unknown Address text Telephone number Fax number email text Status InUse binary This is to record whether the infrastructure is out
45、 of use Replaced binary This is to record whether the infrastructure has been replaced with new Replacement ID longitude number This is a pointer to the replacement infrastructure latitude number Serial number Installer Name text If the installer is not know, enter Unknown Address text Telephone num
46、ber Fax number email text ITU-T Rec. L.55 (11/2003) 5 Table 1/L.55 Primary record fields Description Field Data type Notes Termination description Legal address text Used to find the termination from the terrestrial side Description of the shoreline text Building present binary Description of additi
47、onal protections (see ITU-T Rec. L.28) text Other text This can be used to document items such as close presence of other infrastructures Cable Awareness Charts Number referenced number More than one chart might be referenced Chart1 text Chart2 text Chart3 text Chart4 text Chart5 text Chart6 text Ch
48、art7 text Distant Termination Distant RB name text If the distant RB is not known, enter Unknown Name text Address text Telephone number Fax number email text Distant RB primary ID Longitude number These can be used to identify the details associated with the distant termination point Latitude numbe
49、r Serial number Activity Record First record ID number This points to the first activity record Last record ID number This points to the last activity record 6 ITU-T Rec. L.55 (11/2003) 6.2 Activity record Table 2 contains the recommended fields for the activity records. Table 2/L.55 Activity record fields Description Field Data type Notes Source primary ID longitude number All activity records need pointer to “owner“ latitude number serial number Activity pointers Prior number Negative if first Next number Negative if la
