doc.mod.gov.lvdoc.mod.gov.lv/iepirkumi_upload/TECHNICAL_REQUIREM… · Web viewContinuous...

Request for proposal

TECHNICAL REQUIREMENTS SPECIFICATION

TABLE OF CONTENTS

1. INTRODUCTION 3

2. SYSTEM OVERVIEW 4

2.1 LIELVARDE AFB TOTAL SYSTEMS CONCEPT 42.1.1 GENERAL 42.1.2 SYSTEMS FOR LIELVARDE 4

2.2 SYSTEM CONCEPT BASIC REQUIREMENTS 52.2.1 NAVIGATION SYSTEM 52.2.2 COMMUNICATIONS SYSTEM 5

3. SERVICES 13

3.1 INSTALLATIONS AND TRANSITION OPERATIONAL IMPACT 133.1.1 General 13

3.2 TRAINING 133.2.1 Introduction 133.2.2 General 143.2.3 Training Documentation 143.2.4 Training Facilities and Equipment 153.2.5 Training of Operational Personnel 153.2.6 Training of Maintenance Personnel 153.2.7 Proposal from the Bidder 16

3.3 QUALITY ASSURANCE 173.3.1 General Requirements 173.3.2 Quality Control and Verification 17

3.4 ACCEPTANCE TESTING 193.4.1 Factory Acceptance Test (FAT) 193.4.2 Site Acceptance Test (SAT) 193.4.3 Factory Acceptance Test (FAT) 193.4.4 Site Acceptance Test (SAT) 20

3.5 WARRANTY 223.5.1 General 22

3.6 SPARES 233.6.1 Initial Spares 233.6.2 Sparing Level 233.6.3 Description of Spares 233.6.4 Spares List 233.6.5 Guarantees 23

3.7 DOCUMENTATION 233.7.1 General 233.7.2 Hardware documentation 24

document.doc 20.05.23



3.7.3 Software documentation 253.7.4 Miscellaneous documentation 25

3.8 HARDWARE AND SOFTWARE REQUIREMENTS 263.8.1 Software Requirements 263.8.2 Hardware Requirements 26

3.9 CIVIL WORKS 283.9.1 General Requirements 28

3.10 MAINTENANCE REQUIREMENTS 283.10.1 General 283.10.2 System design Consideration 283.10.3 Maintenance Operation 293.10.4 Preventive Maintenance 303.10.5 Corrective Maintenance 303.10.6 Maintenance Support 31




1. INTRODUCTION

This document sets forth the operational and technical requirement specifications for a national Communications, Navigation, and Air Traffic Management (CNS/ATM) system for the modernization of Lielvarde Air Force Base (AFB) project. These requirements are mandatory and must be adhered to by the Bidder. Any significant noncompliance with this fundamental requirement would result in disqualification from further consideration.

The overall objective of the Lielvarde AFB CNS/ATM/MET system is to provide the Latvian Air Force (LAF) inter-operability with NATO. Therefore, compliance with applicable ICAO and NATO standards is mandatory.

The systems proposed must be of modern design, demonstrable and whose operation has been field-proven in a NATO-member country in Europe. The Bidder must have upgraded at least three airports in NATO-member countries essentially to the level specified in this document.

Where possible, the total system will be based on modern, high quality, commercial off-the-shelf (COTS) technology.

The Bidder will provide a detailed compliance matrix identifying full compliance, partial compliance (with explanation) or non-compliance based on requirements identified within this tender document and the attached specifications.




2. SYSTEM OVERVIEW

2.1 LIELVARDE AFB TOTAL SYSTEMS CONCEPT

2.1.1 GENERAL

2.1.1.1 The following diagram shows the total CNS/MET System concept for the modernization of Lielvarde AFB project.

AWOS Workstation AWOS Workstation

Radio COM RCMS

AWOS DisplayVCCSPrinter

GPS Clock

AWOSSystem

RecorderSystem

VCCSSystem

Field EquipmentRCMS(s)

RCMS

MaintenanceWSMaintenance

WS

TOWER

MET OFFICE

TECHNICAL HALL

AWOS

TransmittersSite

D-VORTAC

ReceiversSite

ILS

Lielvarde AFB – Total CNS/ATM/MET System Concept Block Diagram

2.1.1.2 The overall concept for Lielvarde as depicted in the Overall System Diagram above is based on a requirement for a fully integrated military Communications, Navigation, Meteorological, such that Lielvarde can operate autonomously as well as in harmony with adjacent military and civil aviation authorities.

2.1.2 SYSTEMS FOR LIELVARDE

2.1.2.1 The overall Lielvarde systems concept is as follows:

2.1.2.1.1 The Navigation System will consist of ICAO and NATO compliant Instrument Landing System, and area navigation systems such as military Tactical Air Navigation (D-VORTAC);

2.1.2.1.2 The Communications System will consist of HF, VHF and UHF air-ground and ground-ground radios, voice communications and control system (VCCS) and




ground-ground communications systems to inter-link all the CNS assets to the Command and Control Center offices in Lielvarde AFB;

2.1.2.1.3 The Meteorological System will consist of an Automatic Weather Observation System, which will provide current weather observation parameters in automatic mode, including: wind direction and wind speed, aeronautical visibility and Runway Visual Range (RVR), height of the cloud base and cloud amount, some present weather phenomena, atmospheric pressure (QNH, QFE), temperature and relative humidity (dew point temperature). It will allow incorporating of visual observations into automated reports, to provide system operator with complete weather observation data set.

2.2 SYSTEM CONCEPT BASIC REQUIREMENTS

2.2.1 NAVIGATION SYSTEM

2.2.1.1 The Lielvarde AFB navigation system will consist of the following subsystems:

2.2.1.1.1 Cat III ILS Localizer;

2.2.1.1.2 Cat III ILS Glidepath;

2.2.1.1.3 DME;

2.2.1.1.4 Tactical Air Navigation (D-VORTAC).

Refer to Attachment 2 for the detailed Requirement Specifications for the ILS System.Refer to Attachment 3 for the detailed Requirement Specifications for the DME System.Refer to Attachment 8 for the detailed Requirement Specifications for the D-VORTAC System.

2.2.2 COMMUNICATIONS SYSTEM

2.2.2.1 The Communication System shall include the following two subsystems:

2.2.2.1.1 Air Traffic Control Tower Communications System

2.2.2.1.2 Communications Information System (CIS)

2.2.2.2 2.2.2.2 Air Traffic Control Tower Communications System

2.2.2.2.1 2.2.2.2.1 The Air Traffic Control Tower (ATC-T) Communications System shall consist of the following subsystems:

2.2.2.2.1.1 Voice Communication Control System (VCCS);

2.2.2.2.1.2 VHF/UHF Radios (transceivers and receivers);

2.2.2.2.1.3 Voice Logging Recorder System;

2.2.2.2.1.4 GPS Clock System;

2.2.2.2.1.5 Airfield Remote Control and Monitoring System.

The Requirement Specifications for the VCCS are detailed in the Attachment 4

2.2.2.2.2 The following operator workplaces shall be designed and provided:

2.2.2.2.2.1 ATC-T Tower Control




2.2.2.2.2.2 ATC-T Ground Control

2.2.2.2.2.3 ATC-T Auxiliary Position

2.2.2.2.2.4 Approach Control Operator 1

2.2.2.2.2.5 Approach Control Operator 2 (combined with Supervisor)

2.2.2.2.2.6 Technical Maintenance

2.2.2.2.3 The Bidder shall provide three (3) ATC consoles, two (2) APP consoles and one (1) Technical Maintenance console.

2.2.2.2.4 The design of the consoles shall provide flexible, ergonomic and efficient operation that eliminate distractions and allow controllers to focus strictly on the decisions of the moment. For the ATC-T, the consoles shall be designed to provide the best possible view from a working position towards the outside of the airfield.

2.2.2.2.5 The consoles shall be provided with the following features:

2.2.2.2.5.1 Internal 19”rack cabinets for mounting equipment

2.2.2.2.5.2 Aluminum rail systems for mounting displays on flexible arms

2.2.2.2.5.3 Vent panels

2.2.2.2.5.4 Removable panels

2.2.2.2.5.5 Individual power distribution system for each cabinet

2.2.2.2.6 Under table rails shall permit mounting of the following equipment accessories:

2.2.2.2.6.1 Jack panels

2.2.2.2.6.2 Microphones

2.2.2.2.6.3 Handsets

2.2.2.2.6.4 Headset plugs

2.2.2.2.6.5 Flight strip tray holders

The Requirement Specifications for the VHF/UHF Radios are detailed in the Attachment 5

2.2.2.2.7 The following radios are requested for the ATC-T:

2.2.2.2.7.1 Five (5) main/standby VHF-UHF transmitters

2.2.2.2.7.2 Five (5) main/standby VHF-UHF receivers

2.2.2.2.7.3 One (1) emergency VHF-UHF transceiver with independent power backup.

2.2.2.2.8 The requested RF filters, antenna, lightning protection, feeders, antenna towers, and installation materials shall be provided, as a turn-key solution.

2.2.2.2.9 The VHF-UHF transmitters and receivers shall be provided with remote control and maintenance monitoring system and network management system.

2.2.2.2.10 The detailed Requirement Specifications for the Voice Logging Recorder System are as follows:




2.2.2.2.10.1 The Voice Logging Recorder shall have the capability to cover all the radio, telephone and inter operator communications. The recording capability shall be redundant.

2.2.2.2.10.2 The minimum number of channels installed at the VCCS site shall be forty-eight (48). Additional recorders with minimum 16 channels shall be available for other locations upon request.

2.2.2.2.10.3 As a minimum the following features shall be provided:

2.2.2.2.10.3.1 Accurate recording and archiving of calls / radio communications

2.2.2.2.10.3.2 Quick and easy call retrieval

2.2.2.2.10.3.3 Immediate reproduction and availability of the last recorded call

2.2.2.2.10.3.4 Playback without interruption of ongoing recording

2.2.2.2.10.3.5 Reliable archiving of calls on a variety of storage media (HD, DVD, etc.)

2.2.2.2.10.3.6 On-line monitoring

2.2.2.2.10.3.7 Networking capability

2.2.2.2.10.3.8 ExpandabilityThe Requirement Specifications for the Recorder system are detailed in the Attachment 7.

2.2.2.2.11 The detailed Requirement Specifications for the GPS Clock System are as follows:

2.2.2.2.11.1 The GPS Clock System shall be designed and built to meet or exceed all specifications recommended in the NENA (National Emergency Number Association) PSAP (Public Safety Answering Point) Master Clock Standard (NENA-04-002).

2.2.2.2.11.2 GPS Clock System shall allow other equipment designed to meet NENA specifications to be synchronized to the time information as received from the GPS satellites.

2.2.2.2.11.3 The Master Clock shall receive legally traceable time and date information from Global Positioning System satellites and shall supply UTC (Coordinated Universal Time) synchronized data to the ATC-T systems in a variety of forms. A twelve-channel receiver shall be employed, which is capable of tracking up to twelve (12) satellites simultaneously, although reception of only one is required for accurate time data to be output.

2.2.2.2.11.4 The Bidder shall be responsible for the provision of the required interfaces for the following systems:

2.2.2.2.11.4.1 VCCS

2.2.2.2.11.4.2 Voice Logging Recorder

2.2.2.2.11.4.3 RDPS/FDPS

2.2.2.2.11.4.4 Analogue/Digital clocks (minimum 10 interfaces)




2.2.2.2.12 The Requirement Specifications for the Airfield Remote Control and Monitoring System are as follows:

2.2.2.2.12.1 The RCMS shall provide the remote monitoring and control of the entire CNS/MET system assets at Lielvarde. The Bidder shall propose his concept such that the total system can be monitored from a central location.

2.2.2.2.12.2 Both equipment (CNS/MET) and site (Localizer, Glide Path, D-VORTAC, MET) control and maintenance monitoring information shall be included.

2.2.2.2.12.3 The site monitoring shall consist of, but not limited to the following features:

2.2.2.2.12.3.1 Temperature monitoring

2.2.2.2.12.3.2 Smoke alarm monitoring

2.2.2.2.12.3.3 AC power availability

2.2.2.2.12.3.4 Backup generator on

2.2.2.2.12.3.5 Backup generator alarm

2.2.2.2.12.3.6 Backup generator low fuel

2.2.2.2.12.3.7 Open door alarm

2.2.2.2.12.4 The RCMS shall have the capability of central supervision of the operational status of all the ground based aviation system elements used by the facility. Its main purpose is to provide the Air Traffic Management operators with a comprehensive graphic representation of the equipment interfacing the system’s alarm conditions.

2.2.2.2.12.5 The RCMS shall be specifically customized for the equipment installed at a given location. The Graphical User Interface (GUI) shall make the operation of the software intuitive and interactive.

2.2.2.3 Communications Information System (CIS)

2.2.2.3.1 General Description

2.2.2.3.1.1 The configuration of the Communication Information System is specific for each type of operational environment. Basically the CIS shall provide:

2.2.2.3.1.1.1 Continuous communication-information service to the airport personnel;

2.2.2.3.1.1.2 Links to the communication-information networks of the civilian/military aviation infrastructure;

2.2.2.3.1.1.3 Technical support for the Automated Information System;

2.2.2.3.1.2 The Communication Information System consists of the following subsystems:

2.2.2.3.1.2.1 Communications Information Center (CIC)

2.2.2.3.1.2.2 Automated Information System (AIS)




2.2.2.3.1.2.3 Telephone Centre (PABX network)

2.2.2.3.1.2.4 Ground – Air – Ground Communications, including

2.2.2.3.1.2.4.1 HF-VHF-UHF Transmitting Center

2.2.2.3.1.2.4.2 HF-VHF-UHF Receiving Center

2.2.2.3.1.2.5 Remote Ground – Air VHF Radio Communications

2.2.2.3.1.2.6 Network equipment (modems, …) to transmit signals from field equipment over redundant Fiber Optic communications backbone (main) and copper communication backbone (standby)

2.2.2.3.1.2.7 Local Area Network (LAN) for connecting the CIC and AIS workstations to public and/or private networks

2.2.2.3.1.2.8 Fiber Optic / Copper Cable / Wireless infrastructure for interconnecting different sites of the airport to the backbone (e.g. Radio Navigation and Surveillance sites to the backbone, Radio Transmitting Center and/or Receiving Center to the backbone, Meteorological System sites to the backbone, local telephone extensions to the PABX, internal interconnections of the systems at control tower)

2.2.2.3.2 Prerequisites

2.2.2.3.2.1 The CIS will be the responsibility of the bidder to describe in detail in his proposal after conducting a mandatory site survey. During the site survey, the Buyer will provide the bidders the opportunity to visit all the locations involved in this project and their roles. The Buyer will advise all the bidders about the dates for the Site Surveys.

The Requirement Specifications for the Site Surveys detailed in the Attachment 1.

2.2.2.3.2.2 The Communications Information Center (CIC) shall be equipped with top of the line Commercial-On-The-Shelf (COTS) workstations, based on specificē operational configuration.

2.2.2.3.2.3 The standard software shall consist exclusively of the following items:

2.2.2.3.2.3.1 MS Windows Professional (latest edition)

2.2.2.3.2.3.2 MS Office Standard (latest edition)

2.2.2.3.2.3.3 Antivirus software (latest edition)

2.2.2.3.2.4 The Automated Information System (AIS) is an infrastructure that provides access to information, and means for information processing, storing, displaying, transferring, and broadcasting. The AIS is structured so that two different types of networks are available, and completely independent:

2.2.2.3.2.4.1 Private Network (Intranet)

2.2.2.3.2.4.2 Public Network (internet)




2.2.2.3.2.5 AIS shall be equipped with top of the line COTS servers, workstations, switching and routing equipment based on specific operational configuration.

2.2.2.3.2.6 The standard software shall consist exclusively of the following items:

2.2.2.3.2.6.1 MS Windows Professional (latest edition)

2.2.2.3.2.6.2 MS Office Standard (latest edition)

2.2.2.3.2.6.3 Antivirus software (latest edition)

2.2.2.3.2.7 The Telephone Center consists of a PABX network and corresponding infrastructure.

2.2.2.3.2.8 The PABX specifications shall be based on the end user provided information regarding the type and number of trunks, type and number of telephone sets for extensions, type and number of attendants, number of the nodes within the network.

2.2.2.3.2.9 The PABX shall be provided with administration terminal(s) based on the specific project configuration.

2.2.2.3.2.10 The Ground – Air – Ground Communication System is installed in the HF-VHFUHF Transmitting Center and HF-VHF-UHF Receiving Center.

2.2.2.3.2.11 The following radios are requested for the Transmitting Center:

2.2.2.3.2.11.1 Two (2) HF Transmitters 125W

2.2.2.3.2.11.2 Two (2) HF Transmitters 500W

2.2.2.3.2.11.3 Five (5) VHF-UHF Transmitters

2.2.2.3.2.12 The following radios are requested for the Receiving Center:

2.2.2.3.2.12.1 Four (4) HF Receivers

2.2.2.3.2.12.2 Five (5) VHF-UHF Receivers

2.2.2.3.2.13 The requested RF filters, antennae, lightning protection, feeders, antena towers, and installation materials shall be provided, as a turn-key solution.

2.2.2.3.2.14 The VHF-UHF transmitters and receivers shall be provided with remote control and maintenance monitoring system and network management system.

2.2.2.3.2.15 The radios shall be operated from the VCCS installed in the ATC-T.

The Requirement Specifications for the VHF/UHF Radios are detailed in the Attachment 5.The Requirement Specifications for the HF Radios are detailed in the Attachment 6.

2.2.2.3.2.16 The Remote Ground – Air Communications (also known as Extended Range VHF Radio System) is subject of separate specifications.

2.2.2.3.2.17 High capacity communications backbone shall provide the requested links to the communication-information networks of the civilian/military aviation infrastructure (e.g. other airports, aviation headquarters, Command and




Control Center, remote ground – air communication system, Air Sovereignty Operative Center – ASOC, etc.).

2.2.2.3.2.18 A communication backbone to be interconnect all the CNS/MET system together using modern, high capacity data links (fiber optic, microwave, etc.).

2.2.2.3.2.19 The Bidder shall propose a total communication backbone after conducting a detailed site survey.

2.2.2.3.2.20 The Fiber Optic infrastructure shall be built with sufficient number of SM (Single Mode) fiber cables, installed underground in HDPE pipes (one spare pipe to be included for further development).

2.2.2.3.2.21 The precise number of FO cables shall be determined during the site surveys.

2.2.2.3.2.22 The spare FO cables shall be installed.

2.2.2.3.2.23 The fiber optical cable shall be terminated in Optical Distribution Frames (ODF). The distribution to the fiber optic line units shall be made with fiber-optic patch cords.

2.2.2.3.2.24 Each no systems defined above (MW communications, FO terminals and multiplexors) shall be equipped with remote control terminals, which are necessary for system administration and remote monitoring.

2.2.2.3.2.25 The Local Area Network (LAN) shall be based on the Ethernet protocol (IEEE 802.X). The network topology shall be star, with number of nodes and ports for each node (be defined during the site survey). The central node shall be assigned to the CIC building.

2.2.2.3.2.26 The links between the nodes shall be provided with fiber optic cables. The fiber optic infrastructure shall be built with fiber cables, installed underground in HDPE pipes (one spare pipe to be included for further development).

2.2.2.3.2.27 The fiber optical cable shall be terminated in Optical Distribution Frames (ODF). The distribution to the fiber optic line units shall be made with fiber-optic patch cords.

2.2.2.3.2.28 The proper LAN routing equipment shall be used based on the network size.

2.2.2.3.2.29 The Fiber Optic / Copper Cable / Wireless infrastructure consists of the required cables, distribution frames, and/or communications equipment.

2.2.2.3.2.30 The technology for the PABX distribution network shall be copper pair cables.

2.2.2.3.2.31 The copper pair cables shall be terminated in Main Distribution Frames (MDF) installed at the entrance in each building. The entrance in the building shall be properly protected against lightning. The internal distribution to the central equipment and extension sets shall be made with copper-pair patch cords.

2.2.2.3.2.32 All the other communications between different sites of the airport shall be made with either fiber optic cables, or wireless transceivers.

2.2.2.3.2.33 In case of fiber optic cables, the fiber optic infrastructure shall be built with fiber cables, installed underground in HDPE pipes (one spare pipe to be included for further development). The fiber optical cable shall be terminated in Optical Distribution Frames (ODF). The distribution to the fiber optic equipment shall be made with fiber-optic patch cords.




2.2.2.3.2.34 In case of wireless communications between sites, the equipment shall consist of spread spectrum transceivers, using the frequency hopping spread technology.

2.2.2.3.2.35 The transceivers shall be capable of uncompressed data rates at high speed over distances of 20 miles or more.

2.2.2.3.2.36 The transceivers shall be able to operate point to point or point to multipoint, mode selectable using an asynchronous terminal program. Up to two repeaters may be used to extend the range by programming the transceiver to operate as a store and forward unit, in order to reach distances of 60 miles, or more.




3. SERVICES

3.1 INSTALLATIONS AND TRANSITION OPERATIONAL IMPACT

3.1.1 General

3.1.1.1 Within about 2(two) weeks of the issuing of the Tender, the Contracting Authority shall hold a Bidder’s Meeting in Latvia at which time the Buyer shall brief the Bidder on the LAF Communication concept.

3.1.1.2 Visits of their approximate locations all the relevant LAF CNS assets associated the Lielvarde project will be facilitated, where the Bidders can conduct detailed site survey.

3.1.1.3 The Bidders shall submit as a part of their proposals, detailed communication system to interconnect all the CNS assets within the AirForce Base and to with other agencies.

3.1.1.4 The Bidder shall perform an in-depth Site Survey within thirty days of Contract award. Detail drawings along with engineering reports of each site will be given to the Buyer within 60 days.

3.1.1.5 The Bidder shall propose a Detailed Site Installation Plan that will identify detailed equipment configuration for each system and describe in details all areas of work needed to fully install the total system and recommend transition hardware placement and configuration.

Refer to Attachment 1 for the detailed Requirement Specifications for the Site Surveys.

3.2 TRAINING

3.2.1 Introduction

3.2.1.1 The Bidder shall propose a comprehensive training package as described below:

3.2.1.1.1 System Maintenance (hardware/software) training for 10 electronic technicians for Navigation and Communication systems and associated subsystems.

3.2.1.1.2 Supervisory training for 10 senior supervisory staff.




3.2.1.2 Training documentation requirements are included here.

3.2.1.3 Detailed training programs for the technical personnel shall be negotiated

3.2.2 General

3.2.2.1 Syllabus, lesson’s plans and lecture notes (handouts) shall be provided for the each training course.

3.2.2.2 The Training shall be provided separately for every system/equipment, if it was not specially defined.

3.2.2.3 To ensure efficient training, it is essential that a high standard of documentation is provided.

3.2.2.4 The documentation shall be in the English (or Latvian) language, provide all information required, and be presented in a clear, and concise format.

3.2.2.5 All training courses shall:

3.2.2.5.1 be conducted in the English (or Latvian) language;

3.2.2.5.2 involve theoretical and practical training;

3.2.2.5.3 provide simulation of faults;

3.2.2.5.4 use documentation provided for the each system.

3.2.2.6 After training course the Bidder shall give a document (Certificate) which confirms training completion.

3.2.3 Training Documentation

3.2.3.1 In case final training documentation is not available at the beginning of the training, preliminary versions of both the information and instructional documents shall be provided.

3.2.3.2 Descriptions and detailed data included in the documentation shall comply with the characteristics of the delivered equipment as closely as possible.

3.2.3.3 Any advertising or sales promoting material shall not be included in the training material.

3.2.3.4 The Bidder shall:

3.2.3.4.1 deliver to the Buyer detailed course programs and documentation at least 1 month before the beginning of the course;

3.2.3.4.2 provide each participant with a complete set of course material at the beginning of the course;

3.2.3.4.3 at the end of the course deliver a complete set of instructor's training material (presentations, transparences, films, video tapes etc.) to the Buyer.




3.2.4 Training Facilities and Equipment

3.2.4.1 When training takes place at the Bidder´s factory/training center suitable classrooms and laboratory facilities shall be provided.

3.2.4.2 Students shall have access to rest areas, and the Bidder shall arrange for accommodation, transportation, first aid service, etc.

3.2.4.3 All test equipment used under training shall be of the same kind as Contracted.

3.2.4.4 Maintenance of training test equipment is the Bidder´s responsibility.

3.2.5 Training of Operational Personnel

3.2.5.1 Under the Contract, system-related training for operational personnel shall be provided.

3.2.5.2 The Bidder shall provide the training after the project has been defined and documented in the Product Specification and prior to, but as close as possible to the FAT starting date

3.2.5.3 The training course shall include:

3.2.5.3.1 general course on system hardware;

3.2.5.3.2 detailed course on rules of the system operating;

3.2.5.3.3 documentation on the system operation.

3.2.5.4 At the completion of the course each participant shall have:

3.2.5.4.1 clear overview of the system;

3.2.5.4.2 knowledge of the functional design and operation of the system;

3.2.5.4.3 detailed knowledge of operational functions, input functions and their results, etc. enabling to operate the work station equipment in accordance with the designer's requirements.

3.2.5.5 This shall include to:

3.2.5.5.1 carry out all the functional operations envisaged by the specifications;

3.2.5.5.2 select any configuration of the system and to be able to accomplish reconfiguration of the system;

3.2.5.5.3 to operate the workstation equipment in accordance with the designer's requirements.

3.2.6 Training of Maintenance Personnel

3.2.6.1 Under the Contract, system-related training shall be provided for maintenance personnel and system engineers.

3.2.6.2 The Bidder shall provide the training after the project has been defined and documented in the Product Specification and prior to, but as close as possible to the FAT starting date

3.2.6.3 The training course shall include:

3.2.6.3.1 detailed system hardware course;




3.2.6.3.2 system operating course;

3.2.6.3.3 installation, maintenance and technical parameter changes.

3.2.6.4 At the completion of the course each participant shall have:

3.2.6.4.1 clear overview of the complete system;

3.2.6.4.2 a sound understanding of individual sub-systems;

3.2.6.4.3 knowledge of the functional design and operation of the system down to board level;

3.2.6.4.4 detailed knowledge of operational functions, input functions and their results, etc. enabling the operation of all sub-systems and work station equipment;

3.2.6.4.5 detailed knowledge of how to perform preventive and corrective maintenance.

3.2.6.5 This shall include to:

3.2.6.5.1 check performance parameters;

3.2.6.5.2 interpret fault conditions;

3.2.6.5.3 select and apply maintenance aids such as fault finding procedures, test programs, control and monitoring test equipment;

3.2.6.5.4 carry out adjustments allowable for maintenance personnel;

3.2.6.5.5 perform necessary restoration of service.

3.2.7 Proposal from the Bidder

3.2.7.1 The Bidder shall, based on the guidelines given above, compose an adapted technical training course program.

3.2.7.2 Each course shall have a description, duration, location and an allowed maximum number of participants.

3.2.7.3 The Bidder shall state the price for each of the courses in his proposal which shall also form a part of the Contract.

3.2.7.4 When training takes place at the Contractor´s factory/training center travel cost, accommodation and daily expenses for trainees shall be provided by the Contractor.




3.3 QUALITY ASSURANCE

3.3.1 General Requirements

3.3.1.1 The Bidder shall provide its Quality Assurance Plan to the Buyer. The QAP shall conform to the following guidelines

3.3.1.2 Quality System Requirements

3.3.1.2.1 To prevent nonconformity at all stages of the project, Bidder shall have established a quality system in accordance with the requirements in the document: STANDARD ISO 9000 SERIES (the latest version available, but not lower than ISO9001:2008).

3.3.1.2.2 If the Bidder uses a standard other than stated above compliance with it shall be stated in the compliance table and a correspondence with the ISO 9000 series standards shall be stated.

3.3.1.2.3 All of the offered equipment shall be produced in accordance with the European Union Directives to obtain the CE symbol (including the standards for electromagnetic compliance (EMC) as well as the safety regulations, which ensure the protection of personnel and equipment).

3.3.2 Quality Control and Verification

3.3.2.1 Introduction

3.3.2.1.1 Although the objective of the prescribed quality system is to prevent nonconformity to materialize, verification shall be an important activity.

3.3.2.1.2 The verification activities shall be an on-going process that extends from the conception of the system up to and including its acceptance by the Buyer.

3.3.2.1.3 The verification process shall include design reviews, inspections, and relevant tests. As the realization of the system progresses, tests shall be performed at increasingly higher levels of items. Test procedures shall be worked out for assemblies, units, sub-systems and other equipment.

3.3.2.2 Design Reviews

3.3.2.2.1 Design reviews shall be held at appropriate points in the design and development phase in order to verify compliance with the requirements in the Specification.

3.3.2.2.2 Completion of the design reviews shall result in the release of preliminary acceptance test procedures.

3.3.2.2.3 Design reviews shall be performed by the Bidders own organization.

3.3.2.2.4 Preliminary acceptance test procedures shall be made available to the Buyer.

3.3.2.3 Quality Inspection

3.3.2.3.1 The Bidder shall have the full responsibility for a proper and thorough supervision of the manufacturing process.




3.3.2.3.2 The Bidder shall have full responsibility for quality of the equipment under the Contract even if the Buyer has made use of his right to verify the manufacturing process through inspection activities.

3.3.2.3.3 The Buyer's representative shall be given complete insight in the Bidder's and any Sub-Supplier's manufacturing and QA activities.

3.3.2.3.4 Should the Buyer's representative so wish, he shall be entitled to carry out his own verification tests and reviews. In such cases he shall be given full assistance from the Bidder's staff.

3.3.2.3.5 All approvals shall be in written form and signed by the Buyer's Project Manager or his authorized representative.

3.3.2.4 Testing

3.3.2.4.1 A formal stability verification test before commissioning of the contracted equipment is part of the Buyer's requirements.

3.3.2.4.2 The objective of the Buyer's testing requirements is a full verification that the equipment, when completed and installed on site, meets the contractual specifications, as laid down in the Specification.

3.3.2.4.3 Tests are divided into two categories:

3.3.2.4.3.1 production tests, which shall be performed by the Bidder in order to verify compliance to specifications of items at lower levels;

3.3.2.4.3.2 acceptance tests, which shall be performed by the Bidder in order to verify compliance to specifications of items at lower levels.

3.3.2.4.4 Acceptance tests shall be performed on items at sub-system level and higher, in order to demonstrate that the item concerned meets the specified functional performance.

3.3.2.4.5 The Buyer shall be prepared to accept such tests being applied to units if the performance or capabilities of such units cannot be demonstrated properly under higher level tests, or if testing of units will give a better verification of compliance.

3.3.2.4.6 Acceptance tests are of important significance for the Buyer. Every acceptance test shall be performed in the presence of the Buyer, who will sign the acceptance documentation upon successful completion of the tests.

3.3.2.4.7 All Acceptance tests shall be further divided into 2 categories:

3.3.2.4.7.1 Factory Acceptance Tests (FAT)

3.3.2.4.7.2 Site Acceptance Tests (SAT).




3.4 ACCEPTANCE TESTING

3.4.1 Factory Acceptance Test (FAT)

3.4.1.1 Before the actual Factory Acceptance test a full-scale internal preliminary test shall be arranged according to the specification. The Buyer reserves the right to attend this test as an observer. The Bidder shall notice in due time the start of this preliminary test, however not later than one month in advance.

3.4.1.2 FAT is a test in the Bidder's facilities, which is conducted in accordance with the agreed FAT specification.

3.4.1.3 The Buyer shall be entitled to witness the test and shall be notified about the FAT in due time (at least 3 months in advance). Upon successful completion of the FAT the Buyer will sign the test protocol.

3.4.2 Site Acceptance Test (SAT)

3.4.2.1 A test at the Buyer's premises which is conducted in accordance with the agreed SAT specification. The Buyer shall witness the test and will sign the test protocol upon successful completion of the test.

3.4.3 Factory Acceptance Test (FAT)

3.4.3.1 A selection of the required documentation shall be approved by the Buyer, as indicated below. The following documentation is relevant for the FAT:

3.4.3.1.1 TEST PLAN, which shall contain the general conditions and definitions, a test work flow which defines the test sequence and identifies the related test specifications and test procedures, and a general description of the tests. The Test Plan shall be worked out by the Bidder and shall be made available for the Buyer for review and approval latest three months prior to the expected start of the FAT.

3.4.3.1.2 TEST SPECIFICATION, which shall include detailed descriptions of the various tests and also include criteria for acceptance/rejection, conditions and interfaces. In addition, requirements for test provisions such as test tools, test equipment and test software shall be included. The Test Specification shall be worked out by the Bidder and sent, together with the Test Plan, to the Buyer for review latest two months prior to the expected start of the FAT.

3.4.3.1.3 CERTIFICATION RECORD, which shall indicate the type of test, the items tested and test result, including possible remarks. After completion of each acceptance test an equipment certification record shall be filled in. Remarks may include agreed deviations from the test procedure. The Certification Record shall be the formal document for recording of approval of the relevant test. Both the Employer and the Supplier shall sign the Certification Record.

3.4.3.1.4 LIST OF DELIVERY. The list of delivery shall contain information about the configuration of the equipment down to sub-assembly level.




3.4.3.2 The Bidder shall accomplish the agreed Factory Acceptance Test (FAT) program in the presence of the Buyer's appointed representatives.

3.4.3.3 The FAT shall be run to verify whether the equipment, before delivery, satisfies the functional requirements and technical specifications defined in the Contract.

3.4.3.4 It is accepted that factory acceptance tests are performed under the environmental conditions that prevail in the Bidder's test department at the time of the test.

3.4.3.5 The FAT shall be performed following the Test Plan, successively checking the items for compliance with the Test Specification.

3.4.3.6 The Bidder shall provide all instruments, equipment, materials, facilities and services required for an appropriate realization of the FAT.

3.4.3.7 During the FAT the Certification Record shall be completed. The configuration of the equipment during the FAT shall correspond to the one requested by the Buyer.

3.4.3.8 Should problems arise during the FAT or should the FAT test results be deemed unsatisfactory in any major way by the Buyer, the problems shall be corrected and the status shall be mutually verified and agreed. The Bidder shall take full economic responsibility for any required re-testing program.

3.4.3.9 The following set of documentation shall be handed over to the Buyer as evidence of a successfully completed FAT:

3.4.3.9.1 the Certification Record, signed by the Buyer or their representatives upon completion of the test,

3.4.3.9.2 the List of Delivery

3.4.3.10 These Factory Acceptance Test documents, properly signed by the Bidder and the Buyer, shall imply that the equipment is accepted by the Buyer for delivery to the site.

3.4.4 Site Acceptance Test (SAT)

3.4.4.1 A selection of the required documentation shall be approved by the Buyer, as indicated below. Upon approval by the Buyer these documents shall be binding on both parties. The following documentation is relevant for the SAT:

3.4.4.1.1 TEST PLAN, which shall contain the general conditions and definitions, a test work flow which defines the test sequence and identifies the related test specifications and test procedures, and a general description of the tests. The Test Plan shall be worked out by the Bidder and shall be made available for the Buyer for review and approval latest three month prior to the expected start of the SAT or after completion of the FAT, whichever is the latest.

3.4.4.1.2 TEST SPECIFICATION, which shall include detailed descriptions of the various tests and also include criteria for acceptance/rejection, conditions and interfaces. In addition, requirements for test provisions such as test tools, test equipment and test software shall be included. The Test Specification shall be worked out by the Bidder and sent, together with the Test Plan, to the Buyer




for review latest two months prior to the expected start of the SAT or after completion of the FAT, whichever is the latest.

3.4.4.1.3 CERTIFICATION RECORD, which shall indicate the type of test, the item tested and the test result, including possible remarks. After completion of each acceptance test, an equipment certification record shall be filled in. Remarks may include agreed deviations from the test procedure. The Certification Record shall be the formal document for recording the approval of the relevant test. Both the Buyer and the Bidder shall sign the Certification Record.

3.4.4.1.4 LIST OF DELIVERY. The list of delivery shall contain information about the configuration of the equipment down to sub-assembly level.

3.4.4.2 The objective of the Site Acceptance Test is to confirm that the system, after installation on site, is compliant with all the specifications.

3.4.4.3 A complete Site Acceptance Test shall include verification of all items delivered in accordance with the Bidder including training and documentation

3.4.4.4 The Site Acceptance Tests will be performed under the environmental conditions that will exist under normal operation for the equipment contracted.

3.4.4.5 It shall be the responsibility of the Bidder to provide required documentation, test equipment, measuring instruments, tools etc. prior to the start of the SAT.

3.4.4.6 The SAT shall be performed following the Test Plan and the Test Specification.

3.4.4.7 Flight Inspection (Check) for navigation systems (ILS and D-VORTAC) shall be considered as a part of SAT and shall be the responsibility of Bidder to order necessary Installation and Commissioning Flight Check from neutral Provider.

3.4.4.8 Equipment under SAT shall consist of the complete system in accordance with the Contract.

3.4.4.9 The final phase of the SAT shall include a long term STABILITY TEST, lasting for minimum 30 days, during which the system shall run under continuous relevant operation without any signs of anomalous function. The procedures of the stability test and the criteria and conditions to be granted acceptance shall be mutually agreed.

3.4.4.10 The configuration of the equipment, as it is during the SAT shall be laid down in the List of Delivery.

3.4.4.11 Should problems arise during the SAT or should the SAT test results be deemed unsatisfactory in any major way by the Buyer, the problems shall be corrected and the status shall be mutually verified and agreed.

3.4.4.12 The following set of documentation shall be handed over to the Buyer as evidence of a successfully completed SAT:

3.4.4.12.1 the certification record, signed by the Buyer or their representative upon completion of the test,

3.4.4.12.2 the list of delivery.




3.5 WARRANTY

3.5.1 General

3.5.1.1 The warranty period for the entire system shall commence after Buyer acceptance and last for 2 year.

3.5.1.2 The Bidder shall be responsible to provide system maintenance support during the warranty period.

3.5.1.3 The Bidder shall propose a maintenance concept for the on-going management of the installed systems after acceptance.

3.5.1.4 A fully covered contractor maintenance proposal shall be provided within 4 months after contract award.




3.6 SPARES

3.6.1 Initial Spares

3.6.1.1 Initial spare parts shall be provided by the Bidder and shall be sufficient for maintaining all hardware items for a three-year period, including the warranty period.

3.6.1.2 The spare parts will be for all delivered systems and equipment including test and ancillary equipment.

3.6.2 Sparing Level

3.6.2.1 The recommended sparing level shall be based upon the Bidder’s reliability data for the system being provided and reflect the reliability expected in the Buyer’s operational environment.

3.6.2.2 The Bidder shall provide these reliability data as part of the response to this tender.

3.6.3 Description of Spares

3.6.3.1 Spares will consist of LRM and LRU spares, as well as consumable items required for system operation, including, but not limited to, fuses, lamps, printer supplies, and specialized print medium.

3.6.4 Spares List

3.6.4.1 The recommended spares list shall be fully itemized and individually priced and shall be included as part of the tender documentation.

3.6.5 Guarantees

3.6.5.1 The Bidder shall guarantee the availability of all spare parts and modules for the COTS equipment offered for a period of at least 5 years.

3.6.5.2 The Bidder shall guarantee the availability of all spare parts and modules for the special equipment offered for a period of at least 10 years.

3.6.5.3 The equipment vendor shall, for a period of 20 years, monitor the availability of repair parts, and shall provide the Buyer at least 3 months’ notice in writing of supplier(s) intending to terminate their manufacture and the date by which the Buyer may place orders for the final production run.

3.7 DOCUMENTATION

3.7.1 General

3.7.1.1 The documentation shall make it possible to the Buyer to:

3.7.1.1.1 Perform fault detection and repairing on a routine basis

3.7.1.1.2 Estimate how functions in hardware may be changed and completed without tedious studying of details




3.7.1.2 The design of documentation shall be such that the Buyer's staff in appropriate length of time and by themselves shall be able to:

3.7.1.2.1 Reach good knowledge of principles of hardware structure and way of operation

3.7.1.2.2 Understand how certain hardware parts cooperate to perform certain functions

3.7.1.2.3 Understand interfaces between different units

3.7.1.2.4 Locate erroneous units and make corrections

3.7.1.3 The system documentation shall include complete technical manuals for each equipment and part of the system consisting at least the System description and Software description

3.7.1.4 Documentation data must be recorded to the CD/DVD media in common software like (Excel, Word, Acrobat, Auto-Cad, etc.)

3.7.1.5 The Buyer shall have the right up to mutually agreed level to copy and use delivered documentation.

3.7.1.6 To assist any further modification and use of the documentation it should be available also in electronic data form with suitable media.

3.7.1.7 The Bidder shall provide 3 complete sets of system operations and maintenance manuals for each subsystem

3.7.2 Hardware documentation

The documentation of hardware shall include:

3.7.2.1 Technical manuals:

3.7.2.1.1 General description

3.7.2.1.2 Technical functions

3.7.2.1.3 Mechanical lay-out

3.7.2.1.4 Maintenance instructions

3.7.2.2 Technical data:

3.7.2.2.1 Parts lists (List of used components with serial numbers)

3.7.2.2.2 Communication settings

3.7.2.2.3 Logic and circuit schematics

3.7.2.2.4 Cabling documentation

3.7.2.3 Installation description:

3.7.2.3.1 Distribution plan

3.7.2.3.2 Cable runs

3.7.2.3.3 Interconnection schematics




3.7.3 Software documentation

3.7.3.1 The documentation shall make it possible for the Buyer to:

3.7.3.1.1 To find out easily version of software

3.7.3.1.2 Perform fault detection and repairing on a routine basis

3.7.3.1.3 Estimate how functions and software may be changed and completed without tedious studying of the details and making excessive summaries

3.7.3.2 The design of the documentation shall be such that the members of the Buyer's staff in appropriate length of time and by themselves shall be able to:

3.7.3.2.1 Reach good knowledge of the principles of software structures and way of operation

3.7.3.2.2 Understand how certain software parts cooperate to perform certain functions

3.7.3.2.3 Understand interfaces between different programs and interfaces between hardware and software

3.7.3.2.4 Understand how every single program and program module operate

3.7.3.2.5 Understand organization and meaning of data in the system

3.7.3.2.6 Understand all error signals from the system

3.7.3.2.7 Estimate computer capacity, how it is used and determine reserve capacity

3.7.3.3 The documentation of the software shall at least include:

3.7.3.3.1 An overall system description

3.7.3.3.2 All necessary manuals to meet the requirements of software production and maintenance

3.7.3.3.3 The complete linked system, including the bootstrap loader for initial system loading, stored on media acceptable to the Buyer.

3.7.3.3.4 It shall be possible to restore the system from scratch using the provided installation media.

3.7.3.3.5 System and workstation images on a CD/DVD media

3.7.4 Miscellaneous documentation

3.7.4.1 Test procedure and test report documentation for Factory Acceptance Test.

3.7.4.2 Test procedure and test report documentation for Site Acceptance Test

3.7.4.3 Training documentation

3.7.4.4 Reliability analysis

3.7.4.5 Maintenance plan

3.7.4.6 Risk analysis




3.8 HARDWARE AND SOFTWARE REQUIREMENTSIn case if it is not specially defined in the current document or its attachments, the Bidder should provide the hardware and software, which fulfils the following requirements:

3.8.1 Software Requirements

3.8.1.1 System-level software for servers shall be one of the commercially available multi-tasking, multi-user Operating System (OS). One of the OS UNIX™ versions or their clones (such as Linux), which supports Intel® hardware platform are preferred.

3.8.1.2 System-level software for Working Positions shall be one of the commercially available multi-tasking, multi-user Operating System (OS). One of the OS UNIX™ versions or their clones (such as Linux), which supports Intel® hardware platform are preferred, however Microsoft® Windows™ 7 or later version will be considered as a suitable OS

3.8.1.3 Off-the-shelf (COTS) database software shall be provided for servers.

3.8.1.4 System and application software shall support dual server architecture and allow automatic and manual switching of the primary/standby server, in case of failure or for the maintenance purposes.

3.8.2 Hardware Requirements

3.8.2.1 Off-the-shelf (COTS) equipment shall be provided for server and workstations equipment. Solutions, based on Intel® Pentium™ platform (Dell, HP, FUJITSU) are preferred.

3.8.2.2 The server and communication equipment should reside in standard 19” rack (the dimension should be at least: 2000mm height, 600mm width, 1000mm depth). Rack shall be equipped with rack-mounted console including LCD monitor, keyboard and mouse.

3.8.2.3 All the server equipment, including computers, display, keyboard, etc., should be rack-mounted.

3.8.2.4 In case of several servers, it shall be necessary to provide an Off-the-shelf (COTS) KVM switch with correspondent number of KVM ports.

3.8.2.5 Each server should have the configuration, not worse that:

3.8.2.5.1 Processor: X86 architecture with 4 cores (64 bit support). 2 processors with 8 cores total. Min. 185 point benchmark by SPECint_rate2006 test (http://www.spec.org);

3.8.2.5.2 Memory: At least 32 GB DDR3 with Advanced ECC with possibility to extend till 128 Gb;

3.8.2.5.3 HDD: 4x300 GB 15000 RPM, Hot Swap(SAS or SCSI interface);

3.8.2.5.4 Optical equipment: CD-RW/DVD-RW drive (EIDE or SCSI interface);

3.8.2.5.5 Network Interface Card(s), Base-T Dual Gigabit Ethernet with RJ-45 socket;

3.8.2.5.6 Rack-mount (19”) case with the redundant power supply of sufficient characteristics and appropriate cooling;




3.8.2.5.7 USB 2.0: 2 USB 2.0

3.8.2.5.8 Video card, which supports resolution of 1280x1024,

3.8.2.5.9 17” High Resolution LCD display;

3.8.2.5.10 Additional components, like multi-port serial interfaces, magneto optical or tape

3.8.2.5.11 storage device for long-term data archiving or DVD/CD-writer, modems, etc., shall be provided.

3.8.2.6 The servers shall be provided with embedded redundancy functionality including dual power supplies, mirrored hard drives (RAID 0/1/5), etc.

3.8.2.7 Each CWP should have the configuration, not worse that:

3.8.2.7.1 Processor: Processor: X86 architecture with min. 2550 point benchmark by PassMark CPU test (http://www.cpubenchmark.net) with possibility extend for 2 processors;

3.8.2.7.2 Memory: At least 4 GB DDR3 expandable till 8 GB;

3.8.2.7.3 HDD: 160 GB (PATA/SATA or SCSI interface);

3.8.2.7.4 CD/DVD drive (PATA/SATA or SCSI interface);

3.8.2.7.5 Network Interface Card(s), Ethernet 10/100/1000 Base-T with RJ-45 socket;

3.8.2.7.6 Video card, which supports resolution of 1920x1080 min (for Tower positions 2K x 2K);

3.8.2.7.7 24” LCD display (for Tower positions with daylight settings). The other displays could have another parameters, but not worse than described above

3.8.2.7.8 Additional components, like multi-port serial interfaces, magneto optical storage device for long-term data archiving or DVD/CD-writer, modems, etc., shall be provided as necessary.

3.8.2.8 The workstations shall be provided with mirrored hard drives (RAID 0/1/5)

3.8.2.9 Every workstation shall be equipped with all necessary power cables, communication cables, input\output devices (mouse/trackball, keyboard, etc.).

3.8.2.10 Sufficient number of short-range modems shall be provided for the systems, which requires serial asynchronous connection.

3.8.2.11 The system should be equipped with one or more network packet switches to allow network communication between system components (servers, workstations) and external equipment.

3.8.2.12 Network switches should allow connection of the equipment by means of 1000BaseT Category 6 twisted pair cabling or higher.

3.8.2.13 The system should be equipped with number of printers. It should be network or local printers depending on the configuration.

3.8.2.14 The laser printers are preferable, however in special cases and for special purposes the matrix printers will be considered as suitable solution.




3.9 CIVIL WORKS

3.9.1 General Requirements

3.9.1.1 The Bidder shall evaluate existing situation at the Lielvarde AFB as well as the works performed during the reconstruction and review all available information (design, surveys of performed works etc.).

3.9.1.2 If the information is insufficient the Bidder shall obtain additional data that is required for installation of proposed equipment (topographical survey, geological survey etc.).

3.9.1.3 The Bidder shall provide all the required construction works for installation of proposed equipment including construction of foundations, access roads, communication networks and providing the water drainage.

3.9.1.4 The Bidder shall provide development of appropriate design to perform the civil works.

3.10 MAINTENANCE REQUIREMENTS

3.10.1 General

3.10.1.1 The ILS/DME and DVORTAC systems shall include maintenance features, which provide system operators and maintenance personnel with full information about system status all the time. Moreover, to satisfy availability requirements, outage time shall be minimised by functions and facilities, which enable rapid diagnosis of malfunction, identification and replacement of the failed unit.

3.10.1.2 The Bidder shall present complete set of maintenance documentation include list of all required maintenance procedures and all measurement equipment’s and tools required to carry out those maintenance.

3.10.1.3 The maintenance philosophy and planned operations herein after are the basis for the Contract, but however, if the Bidder thinks he can evaluate and state a corresponding or better solution, he shall do so.

3.10.1.4 Following items are considered:

system design considerations;

maintenance concept;

system management;

preventive maintenance;

corrective maintenance;

maintenance supports;

technical monitoring and control.

3.10.2 System design Consideration

3.10.2.1 Design considerations shall include at least, but not be limited to:

maximum reliability of equipment;




maximum availability of equipment;

redundancy of equipment and/or modules.

3.10.2.2 Features that will allow internal on-line diagnostics for isolating failed modules and effect system restoration by reconfiguring the system by using redundant modules.

3.10.2.3 Modular design that permits an easy access to and simple replacement of defective modules and subassemblies.

3.10.2.4 Standardisation of modules or units, to the extent practicable, to reduce life cycle costs including training, spare-keeping, etc.

3.10.2.5 The maintenance design features shall include on-line and off-line diagnostics, which together with built-in test equipment, test points and fault indicators, should quickly detect the existence of pinpoint and the source of a failure.

3.10.2.6 Diagnostics, status information and control of system are required to be handled via terminals, which should be located in the Technical Monitoring & Control (TMC) facility.

3.10.2.7 Special tools to remove, repair, replace and adjust units shall be minimum for using.

3.10.2.8 All Lowest Replaceable Modules (LRM), subassemblies, parts, test points and terminals shall be readily accessible for adjustment and maintenance. Each unit shall be so mounted as to permit its replacement without the partial or complete removal of any other.

3.10.2.9 The Bidders shall describe the method of the main LRM replacement. The hot swap of LRM is preferable.

3.10.2.10 Adjustments and routine servicing such as lubrication, screwdriver adjustments, etc., for rack mounted equipment, shall be possible without removing the equipment from the rack in which it is installed.

3.10.2.11 The hardware shall be designed to minimise the effects of individual part failures. The design shall prevent the propagation of the effects of an error.

3.10.2.12 The Bidders shall present to the Buyer the equipment failure detection ratio and MTBF for DVORTAC, ILS, DME and it components.

3.10.3 Maintenance Operation

3.10.3.1 General

3.10.3.1.1 The maintenance operation is based on the premise of a highly reliable hardware design with a reasonable amount of redundancy at the system level. Therefore necessary design features to keep maintenance requirements to a minimum shall be incorporated.

3.10.3.1.2 Maintenance activities are classified into five items:

system management;

certification;

preventive maintenance;




corrective maintenance;

technical support.

3.10.3.1.3 The Bidder shall present to the Buyer the list off all measurement devices, accessories, tools and etc., required for site survey, installation, commissioning and all kind of maintenance. All items of this list shall be included to offer as separate items, but the list of units, which cost presented shall be present inside proposal. All delivered measurement devices shall be calibrated and include calibration certificate (valid at least 1 year at the delivery date) with list and data of performed tests, as well as with list of devices utilised during calibration and it calibration dates. All required sets of cables, adapters, connectors and etc. shall be delivered together with DVORTAC and ILS/DME beacons.

3.10.3.1.4 All supplied tool, measurement instruments, as well as extension boards shall be delivered with manufactures calibration certificates and within hard cases (metallic cases are preferable) for safety transportation and storage. The well-known device manufacture such as Tektronix, Rochde&Schwarz, Agilent, IFR, Radial, Spinner or equivalents shall be preferred.

3.10.3.2 Spares

3.10.3.2.1 The Bidder shall suggest the two lists of LRM: first one based on own experience and second – one of each unique board for DVORTAC, ILS, DME and RCMS. The Bidder offer shall include cost for both spares sets as separate items. The list of both spares set shall be specified within technical specification. The Buyer could extend this list after Bidder offer analysis and later during of warranty time.

3.10.3.2.2 The Bidder shall propose routines for repairing the LRM.

3.10.3.2.3 The Bidder shall guarantee the correct operation of delivered spares.

3.10.3.2.4 Each delivered lowest replaceable module (LRM) spares shall be supplied inside separate protection packing for successful transportation and storage.

3.10.4 Preventive Maintenance

3.10.4.1 The Bidder shall propose a program and detailed instructions for preventive maintenance, taking into account this chapter and operational as well as reliability and availability requirements.

3.10.4.2 The Bidder shall propose all necessary resources to be needed to carry out the proposed preventive maintenance.

3.10.5 Corrective Maintenance

3.10.5.1 Level 1

3.10.5.1.1 The redundancy of the equipment together with the on-line diagnostic capability shall permit automatic reconfiguration of a defective unit to a redundant one.

3.10.5.1.2 Fault isolation to the defective lowest replaceable module (LRM) will be accomplished using built-in test equipment (BITE) and/or off-line diagnostic programs.




3.10.5.1.3 The time consumption of removal and replacement to accomplish of an LRM shall be determined by the Bidder and presented within offer.

3.10.5.1.4 The Bidder is requested to submit predicted Mean Time To Repair (MTTR) on maintenance level 1 for all the LRM-units contained in the proposed system and to calculate on this basis and on the Contract previous experience the MTTR.

3.10.5.1.5 Compliance with the predicted MTTR figures will be evaluated during the equipment guarantee period.

3.10.5.1.6 Considerable negative deviations from predicted values affecting the expected magnitude of the life cycle cost of the equipment should be considered as an acceptable guarantee claim.

3.10.6 Maintenance Support

3.10.6.1 On-line Diagnostics

3.10.6.1.1 General

3.10.6.1.1.1 The purpose of the on-line diagnostic task is to check the system hardware for correct operation and to initiate a malfunction report when an error occurs.

3.10.6.1.1.2 On-line diagnostics should provide a very high level of confidence for operational use of the system, a sound basis for automatic and manual reconfiguration decisions, and an indication to maintenance personnel of the nature and location of the malfunction.

3.10.6.1.2 Design Considerations

3.10.6.1.2.1 Design emphasis should be placed on fault detection primarily and on fault location secondly. The design should take advantage of all available supplementary and status information which is to be included in the malfunction report.

3.10.6.1.2.2 In addition, this information should be easily accessible from different system blocks by maintenance personnel.

3.10.6.1.2.3 The on-line diagnostic tasks should form an integral part of the system design, and should be executed on a regular basis by means of a clock call.

3.10.6.1.2.4 Diagnostic routines should be repeated within adjusted time depending upon the criticality of the individual equipment. Diagnostic routines should be provided for each hardware functional element, such as processing elements, memory/storage elements, interfaces, communication links and user interfaces and should be properly tailored to the hardware architecture and interface configurations.

3.10.6.1.3 Hardware Error Detection

3.10.6.1.3.1 All features for hardware error detection should be exercised by the on-line diagnostics to the extent that they do not degrade the operational system integrity.

3.10.6.1.4 Watch-dog-function

3.10.6.1.4.1 The design should include the capability of verifying that the diagnostic and operative routines have been executed at the specified rate.




3.10.6.1.5 Documentation

3.10.6.1.5.1 Explanatory documentation for on-line diagnostic programs should be supplied.

3.10.6.1.6 Built-in test equipment (BITE)

3.10.6.1.6.1 BITE should be designed for rapid assessment of test results and isolation of faults down to LRM or component level.

3.10.6.1.6.2 Built-in test equipment or diagnostic programs should be utilised also in peripheral equipment to localise faults down to LRM level. Facilities for calibration, fault detection, fault location and performance monitoring functions should be included where applicable.

3.10.6.1.6.3 BITE should not cause system failures or false alarms and should be extensively self-tested to ensure the validity of the BITE output. There should be a possibility to block off the BITE function.

3.10.6.1.6.4 A local summary signal for pass/fail should be indicated, for instance by an LED on the front edge of each major unit or PWB.

3.10.6.1.6.5 A subset of the internal diagnostic routines should be activated automatically on power up. In this case the execution time of diagnostics should be stated for each major unit. The associated routines should include a check of all LRM's in the chassis and present the results in a manner similar to that described in the previous paragraph.

3.10.6.1.6.6 When BITE is activated, reports should be output to the corresponding display and log file.

3.10.6.1.7 Off-line Diagnostics

3.10.6.1.7.1 Off-line diagnostics should be available for downloading to the defective equipment.

3.10.6.1.7.2 It should be possible to run the diagnostics either in a chained mode with default parameter values or by individual selection to permit detailed fault analysis in specific areas. Parameter values should be easily modified and diagnostic loops easily inserted.


doc.mod.gov.lvdoc.mod.gov.lv/iepirkumi_upload/TECHNICAL_REQUIREM… · Web viewContinuous...

Documents

Transcript of doc.mod.gov.lvdoc.mod.gov.lv/iepirkumi_upload/TECHNICAL_REQUIREM… · Web viewContinuous...