G1111 VTS 시스템·장비 기능 성능 요건 수립 (요약·한영 대역)

IALA GUIDELINE G1111
ESTABLISHING FUNCTIONAL AND PERFORMANCE REQUIREMENTS FOR VTS SYSTEMS AND EQUIPMENT

Edition 2.0, December 2022
urn:mrn:iala:pub:g1111:ed2.0

International Association of Marine Aids to Navigation and Lighthouse Authorities
Association Internationale de Signalisation Maritime
10, rue des Gaudines, 78100 Saint Germaine en Laye, France

Revisions to this document are to be noted in the table prior to the issue of a revised document.

1. Introduction
  1.1 Purpose
  1.2 G1111 guideline series
2. Establishing the functional and performance requirements for a VTS system and equipment
  2.1 Project planning
    2.1.1 Project management steps
  2.2 Security requirements
  2.3 Operational requirements
  2.4 Deriving functional and performance requirements
3. Implementation considerations
  3.1 Availability and reliability
  3.2 Recording, archiving and replay
  3.3 Other considerations
    3.3.1 Environmental considerations
    3.3.2 Equipment shelters
    3.3.3 Lightning protection
    3.3.4 Site and equipment access
    3.3.5 Electrical power
    3.3.6 Safety and security precautions
    3.3.7 Equipment preservation and monitoring
    3.3.8 Marking and identification
    3.3.9 Documentation
    3.3.10 Equipment standards and approvals
4. Definitions
5. Abbreviations
6. References

List of Tables: Table 1 Relationship between downtime and availability
List of Figures: Figure 1 Project management steps in establishing VTS systems

This Guideline presents a common source of information to assist competent authorities and VTS providers in the preparation and establishment of functional and performance requirements for VTS systems. Tailoring is required to capture the specific and relevant performance requirements from the generic information included within this document. The Guideline should not be used as a specification without such tailoring.

References and definitions applicable to the separate sections are included in the sections where appropriate.

This Guideline is associated with Recommendation R0128 VTS Systems and Equipment [1], a normative provision of IALA Standard S1040 Vessel Traffic Services (VTS). To demonstrate compliance with the Recommendation, the provisions of this Guideline should be taken into account.

This Guideline is one of the G1111 series of guideline documents. The purpose of the G1111 series is to assist the competent authority for VTS and the VTS provider in preparing the definition, specification, establishment, technical operation and upgrades of a VTS system. The documents address the relationship between the functional requirements and VTS system performance (technical) requirements and how these reflect into system design and sub system requirements.

The G1111 series of guideline documents present system design, sensors, communications, processing, and acceptance, without inferring priority. New sub-guidelines can be introduced to the G1111 series in future. The guideline documents are numbered and titled as follows:

• G1111 Establishing Functional and Performance Requirements for VTS Systems and Equipment
• G1111-1 Producing Requirements for the Core VTS System
• G1111-2 Producing Requirements for Voice Communications
• G1111-3 Producing Requirements for RADAR
• G1111-4 Producing Requirements for AIS
• G1111-5 Producing Requirements for Environment Monitoring Systems
• G1111-6 Producing Requirements for Electro Optical Systems
• G1111-7 Producing Requirements for Radio Direction Finders
• G1111-8 Producing Requirements for Long Range Sensors
• G1111-9 Framework for Acceptance of VTS Systems and Equipment

IALA Guideline G1150 Establishing, Planning and Implementing VTS [2] advises on the planning and implementation of a VTS related to the definition of operational, functional, performance and acceptance requirements of a VTS system. These requirements should be:

• derived from a business case and feasibility study in the initiating phase; and
• defined in the planning phase of the overall VTS project before the procurement of the VTS system.

The competent authority for VTS and/or the VTS provider should establish operational, functional and performance requirements and acceptance plan for a VTS system at the same time as they establish their procurement plan. These requirements should form the basis for the entire system lifecycle, its definition and its acceptance following implementation.

The G1111 Guideline Series provide generic guidance for all potential equipment and sensors that may be used in designing a VTS system. The guidance is not prescriptive, and the capabilities required may vary between VTS, VTS area and VTS sectors or even specific parts of a VTS area or sector. VTS capability should be linked to a risk assessment which will identify the degree of mitigation expected of a VTS, together with other mitigation measures, in addressing a specific hazard or hazards. The extent of risk mitigation will be determined by a number of factors that include the equipment fit, equipment capability, local geography and operator authorization/training. This Guideline focuses on an overview of the key areas for consideration related to the establishment of a VTS system.

IALA sub-guidelines G1111-1 to G1111-8 provide specific guidance on initiating and planning functional and performance requirements and implementing VTS systems and equipment, based on operational requirements.

Acceptance steps are typically conducted on the proposed or implemented VTS to ensure compliance with the requirements. These acceptance steps are discussed in G1111-9 Framework for Acceptance of VTS Systems and Equipment.

IALA Guideline G1150 recommends a project management approach to ensure that major deliverables, assumptions and constraints are clearly documented when planning and implementing a VTS. This will assist in defining the scope of the VTS, its goals and objectives that need to be met. Project management is considered as a discipline with the purpose to achieve specific goals and objectives by planning, organizing, motivating, and controlling resources.

Relevant international guidance prepared and published by appropriate international organizations regarding project management should be considered, or, where there are national requirements for project management, these should be used.

Project management is undertaken in different steps in order to improve control and quality. Guideline G1150 provides an overview of the five project management phases and the key areas for consideration as they relate to VTS:

• Initiating
• Planning
• Implementing
• Controlling
• Closing

It is noted that before completing each stage to define functional and performance requirements, these results could be re-evaluated by risk assessment and cost benefit analysis. The core practice in the planning phase is finalising the requirements. This involves combining the relevant operational requirements with the functional and performance requirements, without unintentionally restricting flexibility in the implementation.

It is important to write well-structured, individual requirement statements within the published requirements documentation.

Note that, for the implementation phase, several possible technical solutions may be identified to achieve the defined requirements and each of these solutions may have different strengths and weaknesses. Scoring systems to address the most critical aspects of the operational requirements may need to be considered when preparing a procurement plan.

The security requirements needed to derive the functional and performance requirements should include, but not be limited to:

• Physical security of the VTS Centre and remote sites
• Cyber security
• Business continuity, availability, reliability and disaster recovery

The operational requirements needed to derive the functional and performance requirements should include, but not be limited to:

• Delineating the VTS area and, if appropriate, VTS sub-areas or sectors
• Types and sizes of ships required or expected to participate in the VTS
• Navigational hazards and traffic patterns
• Human/machine interface and human factors, including health and safety issues
• Tasks to be performed by VTS operators and/or supervisors
• Operational procedures, including communication, staffing level and operating hours of the VTS
• Information sharing and co-operation with external stakeholders
• Legal framework

The functional and performance requirements for a VTS system should be derived from the operational requirements. This may be an iterative process, which can be aligned with the phases of Guideline G1150.

In order to define functional and performance requirements, the operational requirements may be grouped into:

• communications
• situational awareness
• recording and playback
• reliability and availability

The grouping of operational requirements facilitates the creation of functional and performance requirements, for example, divided into:

• voice and data communication
• the VTS Centre, sites, sensors and processing
• recording and replay, including post situational analysis
• redundancy and resilience

Deriving system concepts may involve various mathematical, functional and simulation models to visualize different characteristics of the system. Models to consider might include, but not be limited to:

• Radio communications coverage
• Sensor coverage
• Communications network infrastructure
• Data architecture and interfaces
• Reliability and availability, including any redundancy options
• Lifecycle costs

The models could assist in establishing the relationship between the system concepts, associated functional and performance requirements and operational requirements. Feasibility studies (site surveys, equipment trials etc.) may also be appropriate to reduce technical risks which may otherwise not be apparent until implementation.

Additional functional and performance requirements may come from, but not be limited to:

• Environmental considerations
• Legal obligations
• Ergonomic issues
• Safety (other than navigational safety)
• Security requirements, e.g., physical security, personnel security, cyber security incl. software updates during operation
• Operational business rules or operational procedures

VTS system implementations may require consideration of the following:

• VTS system function and performance including, but not limited to:
  • Off-the-shelf solution or customized solution
  • Sensor and radio coverage, including overlapping coverage
  • Equipment redundancy
  • Communications routes
  • External Interfaces
  • Electromagnetic issues (EMI/EMC)
• VTS system sustainability including, but not limited to:
  • Lifecycle planning, including environmental impact and sustainability in the choice of materials, power consumptions etc.
  • Maintenance of the VTS system and equipment
  • Environmental constraints and impacts such as wind, influence from the sea, precipitation and possibly ice
• Locational and infrastructure design should include but not be limited to:
  • VTS Centre location(s)
  • Available land and suitability of sensor sites
  • Existing infrastructure such as power and data lines
  • Selection of installation sites with due respect to neighbours
  • Security and site access
• Rules and regulations, for example:
  • Applicable rules and regulations, i.e. required licenses (transmission, building etc.)
  • Business rules
• Organization, for example:
  • Administrative functions and roles
  • Authorization levels

Any VTS system should, as a minimum, be equipped with means to build a VTS traffic image as well as providing reliable communications.

The system architecture of a VTS system should carefully consider issues such as, but not be limited to:

• Network requirements (bandwidth, latency etc.)
• Redundant data paths
• Data integrity
• Security requirements, e.g., physical security, cyber security
• Data storage
• Reporting and recording requirements
• Maintenance of the VTS System and its equipment

In addition, the system architecture should have built-in flexibility for future upgrades and have the capability to be maintained without impacting routine VTS operations.

During the development of the system architecture, comprehensive site surveys should be performed, including but not limited to the above considerations. Involvement of relevant stakeholders in the site survey early in the process adds value and ensures awareness of the potential risks (e.g., design and performance).

The VTS provider should define an overall availability and reliability target for the VTS system, including the elements to be considered based on the risk assessment results. The relationship between downtime and availability figures is given by Table 1.

The VTS provider can decide whether individual sub-systems are critical or non-critical. Non-critical sub-systems may be excluded from the overall system availability requirement.

Note that multiple means of communications and overlapping sensor coverage will increase overall availability. Such a solution may result in reduced requirements for the availability of each item of equipment individually.

Scheduled maintenance activities may be included in availability figures.

Also note that required spare parts should be readily available, to ensure the shortest time to repair. Therefore, VTS providers should plan for sufficient spare parts and service arrangements, or business continuation plans in order to meet the availability criteria.

The VTS system availability may be improved by the following redundancy measures:

• by duplicating hardware and/or by using externally hosted VTS system and equipment - in duplicated hardware systems, hand-over procedures from active to stand-by equipment should be considered;
• by siting sensors such as radio and radar aerials to provide partial overlapping coverage; and
• by facilitating gradual reduction of capabilities in individual VTS Equipment.

Within legal limitations, provision should be made for secure storage, retrieval and presentation of VTS data so the relevant historical data can be easily recalled and played back.

The data retention period should allow for the full retrieval of data post-incident/accident, in compliance with national requirements and those of the investigation procedures.

Stored and archived data should include, but not be limited to:

• VTS traffic image
• Sensor data
• Voice communication
• Other relevant information

It may also include (within legal limitations):

• Internal VTS personnel conversations inside the VTS centre
• VTS personnel activities
• Technical and maintenance requirements, e.g., logging, failure tracking, long term failure statistics and analysis, system performance monitoring and improvement

The data should be recorded automatically and be capable of replay without impact to on-going VTS operations. Synchronization of information is recommended for replay.

Data security should always be considered especially when providing online storage. Long term archiving may be considered for traffic statistics, risks evaluation, strategic planning etc.

The VTS provider should specify the local environmental conditions for VTS system performance, design and outdoor installations.

A shelter can provide a protective environment with characteristics that depend on the location and design of the shelter. In situations where contained equipment is reliant on the environment created by the shelter, the shelter facilities (e.g., cooling or heating) may become critical to the achieved availability of the equipment.

Lightning protection is often subject to national or local legislation taking into account local conditions, severity, earth conductivity, power grid constraints etc. The guidance from country to country differs depending on lightning strike frequency and severity. As a consequence, requirements for the number and type of lightning arrestors, the number of earthing points and the minimum cross sectional area of conductors vary to suit local conditions.

The general principles include:

• Lightning arrestors and/or conductors should be positioned higher than other equipment and be designed to protect the entire installation.
• Separate down conductor(s) on the exterior of buildings should not be connected to metal parts of buildings such as steel reinforcements, handrails and antenna masts.
• Safety grounding of equipment should be kept separate from lightning protection.
• Potential equalization should be achieved in earth and never at the top of the equipment. See Guideline G1012 The Protection of Lighthouses and Other Aids to Navigation against Damage from Lightning for further information.
• Warning lights.

High structures, such as RADAR towers, may require warning lights for air traffic. Some light arrangements may also be disturbing to both vessel traffic, the general public and to birds and animals. It is therefore recommended to consult local authorities for specific requirements or restrictions in the area.

As part of the selection of a VTS system location, the VTS provider should analyse the need for site access for installation and maintenance. Fencing and other protective means against illegal intrusion may also be needed in many cases.

The VTS system could require a reliable source of electrical power, which could include a backup power source such as an Uninterruptable Power Supply (UPS) and/or generator.

Renewable sources should be used where appropriate.

For each location, the VTS provider should implement safety and security requirements in accordance with relevant legislation.

Safety requirements should, at least, consider but are not limited to:

• safety procedures, such as instructions to personnel performing maintenance;
• personnel protection equipment for working at heights;
• lone working on remote sites;
• safety switches to isolate equipment and to stop rotating antennas;
• precautions regarding electromagnetic radiation, rotating machinery and electrical shock, railings on masts etc.; and
• protection of the general public.

Security requirements should, at least, consider:

• physical restrictions, e.g., fences, locks, motion sensors, monitoring (CCTV); and
• access procedures, i.e., restrictions imposed by ISPS.

The VTS provider should also consider the following:

• fire detection and (remote) alarms;
• automated fire extinguishers;
• remote monitoring of site status (power, fuel, temperature, site environmental conditions etc.); and
• remote monitoring of equipment status.

VTS equipment should be marked with manufacturer name, type and serial number.

Legislation may require additional marking or identification, signposts etc.

The VTS provider should specify deliverable documentation to accompany the VTS equipment, which should be available for appropriate personnel. As a minimum, documentation should include:

• operating instructions;
• maintenance instructions (preventive and corrective) inclusive of procedures and spare parts catalogue;
• safety information (e.g., regarding radiation, electrical safety and rotating machinery);
• certificates and permissions as required by relevant legislation;
• test procedures, test certificates; and
• "As built" documentation comprising drawings, equipment configurations, software versions, etc.

Legal requirements for equipment standards and approval (or statements of conformity) vary from country to country. It is the responsibility of the VTS provider to ensure compliance to local, regional and international standards. The VTS Provider should state any applicable standards as part of the acquisition process.

VTS providers should ensure that all appropriate standards and approvals for their VTS area have been considered. Typical standards and approvals may include the following:

• Electrical Safety
• Mechanical Safety
• Radiation Safety
• Electromagnetic Compatibility
• Radio Spectrum licensing
• Hazardous / Chemical Substances

The following definitions apply within this document and in all the G1111 series of guideline documents:

VTS system: the VTS system is the VTS software, hardware, communications and sensors. This excludes personnel and procedures.

VTS equipment: VTS equipment refers to the individual items of software, hardware, communications and sensors, which make up the VTS system.

VTS user: VTS user is defined as someone with either an operational, technical, or administrative need to use or access the VTS system.

The other definitions of terms used in this Guideline can be found in the International Dictionary of Marine Aids to Navigation (IALA Dictionary) and were checked as correct at the time of going to print. Where conflict arises, the IALA Dictionary should be considered as the authoritative source of definitions used in IALA documents.

1. IALA. Recommendation R0128 VTS Systems and Equipment (V-128).
2. IALA. Guideline G1150 Establishing, Planning and Implementing a VTS.
3. IALA. Guideline G1012 The Protection of Lighthouses and Other Aids to Navigation against Damage from Lightning.