STATEMENT OF WORK AND TECHNICAL ... - eportal.nspa.nato.int · The following is a non‐exhaustive list of documents which, in their most current version/revision, are relevant in

NATO UNCLASSIFIED Statement of Work dated 1 March 2019 (Version 2)

NATO UNCLASSIFIED

COMMUNICATIONS, AIR AND MISSILE DEFENCE PROGRAMME PROGRAMME DE COMMUNICATIONS, DÉFENSE AÉRIENNE & ANTIMISSILE

STATEMENT OF WORK

AND TECHNICAL REQUIREMENTS

FOR

MARTELLO ELECTRONIC SHELTER RESTORATION ‐ S723

1 March 2019 (Version 2)


NATO UNCLASSIFIED

TABLE OF CONTENTS

0. NOTATION CONVENTIONS ................................................................................................ 5

1. OBJECTIVE AND SCOPE ..................................................................................................... 1

2. REFERENCE DOCUMENTS .................................................................................................. 1

2.1. NATO STANDARDS AND PUBLICATIONS ......................................................................................... 1

2.2. INTERNATIONAL STANDARDS AND SPECIFICATIONS ........................................................................... 2

2.3. EQUIPMENT TECHNICAL MANUALS ............................................................................................... 2

3. CURRENT RADAR SYSTEM ................................................................................................. 2

4. OVERVIEW OF PROJECT DEVELOPMENT AND CONTRACTOR’S TASKS ............................... 2

5. PROJECT MANAGEMENT .................................................................................................. 3

5.1. MASTER SCHEDULE .................................................................................................................... 3

5.2. PROJECT CONTROLS ................................................................................................................... 4

6. TECHNICAL AND INTEGRATION REQUIREMENTS ............................................................... 4

6.1. GENERIC.................................................................................................................................. 4

6.2. PERFORMANCE SPECIFICATIONS (SEE CONFIDENTIAL ANNEX 0) ......................................... 6

6.3. INTERFACE REQUIREMENTS ......................................................................................................... 6

6.3.1. DEMARCATION PANEL ................................................................................................................ 7

6.3.2. COMMUNICATION FUNCTION BETWEEN RRH AND CRC ..................................................................... 7

6.3.3. COMMUNICATION FUNCTION WITH ADP NETWORK INTERFACE ........................................................... 7

6.3.4. ACCS NETWORK INTERFACE ........................................................................................................ 8

6.4. SYSTEM TIMING AND WAVEFORM GENERATOR (OFF‐MOUNT RECEIVER) .............................................. 8

6.5. SIGNAL PROCESSOR ................................................................................................................... 8

6.6. EXTRACTOR (PRIMARY RADAR) .................................................................................................... 9

6.7. SSR DECODER AND PLOT EXTRACTOR ............................................................................................ 9

6.8. JAMMING ANALYSIS RECEIVER ................................................................................................... 10

6.9. SYSTEM CLOCK ....................................................................................................................... 10

6.10. RCDSS: DATA PROCESSING AND COMMUNICATION ....................................................................... 11

6.11. RCDSS: MONITORING AND CONTROL ......................................................................................... 13

6.12. RCDSS: BITE REPORTING ......................................................................................................... 17

6.13. RCDSS: DATA BUFFER ............................................................................................................. 18

6.14. RCDSS: PRIORITY FILTER .......................................................................................................... 19

6.15. RCDSS: PERFORMANCE EVALUATION COMPUTER (PEC) ................................................................. 19

6.16. REMOTE DISPLAY SYSTEM (RDS) ................................................................................................ 19

6.17. PERFORMANCE EVALUATION TOOL (PET) ..................................................................................... 21

6.17.1. Radar Raw Data Files ............................................................................................................... 22

6.17.2. Data Analysis and Display ....................................................................................................... 23

6.17.3. Output Data File ...................................................................................................................... 24

6.17.4. PET Environment ...................................................................................................................... 25

6.17.5. Test Points ............................................................................................................................... 25

6.17.6. Radar Environment Simulator (RES) ........................................................................................ 25


NATO UNCLASSIFIED

6.17.7. Installation ............................................................................................................................... 27

6.18. RELIABILITY, MAINTAINABILITY AND TESTABILITY ........................................................................... 28

6.18.1. Reliability ................................................................................................................................. 28

6.18.2. Maintainability ........................................................................................................................ 28

6.18.3. Testability ................................................................................................................................ 28

7. PROJECT DEVELOPMENT AND MAJOR TECHNICAL MILESTONES ..................................... 29

7.1. GENERIC................................................................................................................................ 29

7.2. SYSTEM REQUIREMENTS REVIEW (SRR) ....................................................................................... 29

7.3. CRITICAL DESIGN REVIEW (CDR) ................................................................................................ 29

7.4. PRODUCTION AND FACTORY ACCEPTANCE TEST (FAT) .................................................................... 30

7.5. DELIVERY, INSTALLATION, INTEGRATION AND SITE ACCEPTANCE TESTING (SAT) ................................... 31

7.6. RELIABILITY TEST (RT) .............................................................................................................. 33

8. VERIFICATION AND ACCEPTANCE ................................................................................... 33

8.1. VERIFICATION AND ACCEPTANCE TEST (V&A‐T) PLAN .................................................................... 33

8.2. ACCEPTANCE MILESTONES ........................................................................................................ 35

8.2.1. Factory Acceptance of the Integrated Prototype Solution....................................................... 35

8.2.2. Provisional Site Acceptance (PSA) ............................................................................................ 35

8.2.3. Final Acceptance: (FA) ............................................................................................................. 36

9. LOGISTIC SUPPORT DELIVERABLES .................................................................................. 36

9.1. DOCUMENTATION ................................................................................................................... 36

9.2. CONFIGURATION ..................................................................................................................... 37

9.3. TRAINING .............................................................................................................................. 37

9.4. SPARE PARTS ......................................................................................................................... 39

9.4.1. Installation & Check Out (INCO) Spares ................................................................................... 39

9.4.2. Reliability and Provisioning Data ............................................................................................ 39

10. QUALITY ASSURANCE ..................................................................................................... 40

11. OPTIONS (EVALUATED) ................................................................................................... 40

APPENDIX 1: SUMMARY OF DELIVERABLE DATA, PRODUCTS AND SERVICES ......................... 41

APPENDIX 2: ENVIRONMENTAL REQUIREMENTS WITHIN THE DISPLAY SHELTER ................... 43

APPENDIX 3: ABBREVIATIONS AND ACRONYMS .................................................................... 45

ANNEXES:

ANNEX 0: MARTELLO S723 REQUIREMENTS

ANNEX 1: MARTELLO S723 SYSTEM DESCRIPTION

ANNEX 2: MARTELLO S723 SCHEMATICS

ANNEX 3: MARTELLO S723 TECHNICAL DOCUMENTATION

ANNEX 4A: S723 INTERFACE BETWEEN RCDSS AND RDS

ANNEX 4B: S723 INTERFACE BETWEEN LSD AND RIS&MASE


NATO UNCLASSIFIED

AMENDMENT RECORD

REVISION/AMENDMENT PAGES DATE OF ISSUE REMARKS Version 1 52 Pages and

Annexes below: Annex O Annex 1 Annex 2 Annex 3 Annex 4A Annex 4B

23 JULY 2018 NONE

Version 2 52 Pages

Annex 1

1 March 2019


NATO UNCLASSIFIED

0. NOTATION CONVENTIONS

This document contains both a statement of work and a set of technical requirements. Paragraphs stating deliverables and specifying requirements are preceded by an alphanumeric code in brackets with the following meaning:

(Rx): States a generic requirement affecting all deliverables, where “x” is a serial number.

(R.Tx): Specifies a technical requirement for the system, where “x” is a serial number. Technical requirements are given at Section 6 of this document.

(Dx): States a requirement for the Contractor to deliver certain a product (including data products) or service, where “x” is a serial number.

(R.Dx.y): Defines specific requirements related to the deliverable “Dx”, where “y” is a serial number.

Deliverables and their associated requirements are stated in Sections 5, 7 and 9 of this document.

(R.Qx): Specifies quality assurance requirements, where “x” is a serial number. Quality assurance requirements are given in Section 8 of this document.

(O.Tx): State options for additional technical scope.

Options are given in Section 11 of this document.

Tables and bulleted lists following paragraphs stating deliverables or specifying requirements are part of the definition of the deliverable or requirement.

Paragraphs not preceded by any of the codes listed above do not state outright deliverables or associated requirements, but contain essential information or may complete the definition of work and acceptance. They may also reflect actions which NSPA will perform.

Acronyms and abbreviations are normally spelled out when they are used for the first time in the document, except when referring a commonly used term (e.g. NATO). Appendix 3 contains a list of acronyms and abbreviations used.

Where the “Host Nation” is mentioned, it is to be understood as “Denmark”.

“Customer” is to be understood as “NSPA” in its role as Procurement Agent and Contract Manager and “Denmark” as the End User for the equipment and responsible for the operations of the radar.

Statement of Work dated 1 March 2019 (Version 2)

NATO UNCLASSIFIED MARTELLO S723 Electronic Shelter Restoration

NATO UNCLASSIFIED p.1

1. OBJECTIVE AND SCOPE

This document defines requirements for services and products to be provided by the Contractor to the NATO Support and Procurement Agency (NSPA) for the upgrade of the Signal Processor (SP), Data Processor (DP), Data Handling (DH) and IFF Processor (Option) in the current configuration of the NATO Martello S723 Air Defense System in Denmark. This upgrade will be referred hereafter as the Martello S723 Electronic Shelter Restoration (MESR).

The main objective of the MESR is to extend the system life cycle through a technology refresh to mitigate system obsolescence and improve system supportability. As such NSPA, is not aiming for improved technical system performance, but to guarantee the original system performance with improved supportability for the remaining planned operational life.

The services and supplies covered by this SOW are applicable to the equipment at one MARTELLO S723 radar site, Radar Head Solution (RHS), and at two Remote Operations Center (ROC) as described in Table 1.

Country Site name System Function Location Mod kit

Denmark BORNHOLM S723 Radar head BORNHOLM RHS

Denmark Karup ROC CRC + CARS KARUP RS

Denmark Mobile CRC ROC D‐CRC KARUP RS

Table 1: sites concerned by the MARTELLO S723 Electronic Shelter Restoration

2. REFERENCE DOCUMENTS

The following is a non‐exhaustive list of documents which, in their most current version/revision, are relevant in whole or in part to the object of this SoW. They do not in principle constitute requirements unless explicitly referred in other parts of this SoW. If there is a conflict between the requirements of this SoW and any of the listed reference documents, the SoW shall prevail.

(R1) The Contractor shall be responsible for ensuring that the new equipment complies with all national and international applicable legal requirements.

2.1. NATO Standards and Publications

a. AQAP‐2110 (NATO Quality Assurance Requirements for Design, Development and Production)

b. AQAP‐2210 (NATO Supplementary Software QA Requirements to AQAP 2110) c. ACMP 1‐7 Allied Configuration Management Publications (Edition 2) d. STANAG 4193 Ed 3: Technical Characteristics of IFF Mk XA and Mk XII Interrogators

and Transponders




e. 3885.10/SHCCC/382/98, AIR COMMAND AND CONTROL SYSTEM CRITERIA AND STANDARDS (3rd edition, final), NATO CONFIDENTIAL (available only after contract award)

f. STANAG 4370 (Environmental Testing) g. STANAG 4236 (Lightning environmental conditions, affecting the design of material

for use by NATO forces) h. STANAG 4327 (Lightning test procedures) i. STANAG 5535 Ed 2/ADatP‐35 Ed 2 (NATO Standard Document for Air Surveillance

and Ground Based Sensors Information Exchange).

2.2. International Standards and Specifications

j. ISO 9001:2000 (Quality Management Systems – Requirements) k. MIL‐HDBK‐61A Configuration Management Guide l. MIL‐STD‐100, Engineering Drawings m. MIL‐DTL‐31000, Technical Data Packages n. MIL‐STD 1250, Corrosion control o. ICAO, International Civil Aviation Organization ‐ Technical Characteristics of IFF MK

XA and MK XII Interrogators and Transponders p. Recommendation CCIT V29

2.3. Equipment Technical Manuals

q. MARTELLO S723 TMEs are listed in Annex 3, available and maintained at NSPA

3. CURRENT RADAR SYSTEM

The description, performance and technical characteristics of the current radar system and support equipment are reflected in Annexes 0 to 3.

4. OVERVIEW OF PROJECT DEVELOPMENT AND CONTRACTOR’s TASKS

Through this contract, the Contractor will replace the Signal Processor and the Radar Control and Display Subsystem (RCDSS) equipment for the MARTELLO S723 radars used in NATO’s Air Defense System. Annex 2 presents a schematic containing the affected parts of the radar system.

NSPA is seeking a low risk and fast implementation solution, ideally non‐developmental, i.e. an existing design needing limited adaptation for specific requirements of this application. Contractors able to propose such solution are to interpret the design & development tasks outlined below as comprising only this adaptation.

The Contractor will undertake the following tasks:

a. Establish the engineering design that will ensure that all current system performance are met, including existing system & operational control capabilities (Local & Remote);

b. Establish the engineering design of the R‐SPC Performance Evaluation Tool (PET); c. Develop the new equipment Human Machine Interface and output interfaces;




d. From a Work Breakdown perspective, due to the estimated duration of the project, the solution will be developed, tested, implemented and validated in the following main technical phases:

i. Development, to include HW Design updates and SW scripts updates and documentation development.

ii. Factory Testing. iii. Installation, Integration and Site Testing. iv. Reliability Testing.

e. Upon contract award the Contractor will perform a System Requirements Review (SRR) and the design and development activities leading to Critical Design Review (CDR).

f. Following CDR approval by the NSPA, the Contractor will conduct factory testing for the solution proposed, before proceeding with site installation and integration of the Modification kit (Modkit) for the radar site, and two Mod kits for the CRC sites. For each complete installation, the Contractor shall perform Site Acceptance Test (SAT) followed by a phase of reliability testing starting after Provisional Site Acceptance (PSA).

g. Provisional Site Acceptance (PSA) will be achieved for each site, after the technical solution has been tested and accepted at that site and management and logistics products have been delivered and accepted.

h. The last milestone of the project is Final Acceptance (FA) which will be performed simultaneously for all sites once all validation and verification activities are successfully completed and any observations cleared.

i. The project also includes logistics support deliverables, i.e. training, documentation, special tools and test equipment and recommended spares lists.

5. PROJECT MANAGEMENT

(D1) The Contractor shall assign a Project Manager to be the main Point of Contact (POC) for NSPA in all aspects related with the project.

5.1. Master Schedule

(D2) Not later than 4 weeks after Contract Award, the Contractor shall deliver and maintain through the execution of the contract, a Master Schedule for the delivery of all products and services in this contract. Within 2 weeks of reception, NSPA shall approve the Master Schedule or provide requirements for change or clarification. The Contractor shall implement the changes required by NSPA for final agreement.

By agreeing on the schedule, NSPA considers the plan to be a logical and satisfactory approach to the management of the required activities, based upon the information provided. The requirements in this SoW take precedence over the Master Schedule in the case of conflict, ambiguity or omission.

(R.D2.1) The Master Schedule shall indicate the planned dates for all events and intermediate milestones described in this SoW in order to achieve the Final Acceptance not later than 18 months after Contract Award. The Master Schedule is included as an Annex to the Contract.




(R.D2.2) The dates for site installation and testing shall provide for the consecutive implementation of the upgrade on all sites in order to minimize contractor’s personnel travel and subsistence cost. The site installation schedule shall be considered tentative until it is confirmed by the Host Nation. NSPA shall provide confirmation of these dates at least 60 days before the planned operation.

(R.D2.3) In case of project changes, the Contractor shall update the Master Schedule accordingly and submit it for NSPA approval.

(D3) 90 days before any intervention on site, the Contractor shall communicate to NSPA the bio and security clearance data of all the personnel (to include backup personnel) involved in the activities on all sites.

5.2. Project Controls

(R2) Generally, the Contractor shall keep the NSPA Project Manager informed of any issue

or risk affecting the schedule or the scope of the project.

(D4) If at any point during the execution of the Contract, the Contractor foresees any significant risk to the schedule or circumstance creating a risk to any of the requirements in this document, he shall inform NSPA immediately in writing and will seek agreement by Contract Amendment.

(D5) Other than the main technical events in the contract described in Section 7, NSPA may call for an ad‐hoc Project Review and/or a Technical Interchange Meeting at any point during the execution of the contract.

(R.D5.1) Ad‐hoc meetings called by NSPA will be exceptional and, unless otherwise agreed, will take place at the contractor facility to minimize the contractor’s cost. If NSPA requires contractor personnel to travel for this type of meeting, cost incurred by the contractor shall be considered as a modification to this contract.

(R.D5.2) The Contractor shall record the minutes of all formal meetings and provide them to NSPA for agreement, in general within 2 weeks of the meeting.

(R.D5.3) Meeting minutes shall be considered final only once they have been signed by the Contractor, NSPA and, if in attendance, the Host Nation. The Contractor shall not consider the minutes as the basis for changes to any of the terms and conditions of the Contract in the Absence of a formal Contract Amendment.

6. TECHNICAL AND INTEGRATION REQUIREMENTS

6.1. Generic

(R.T1) There shall not be any degradation to any of the current radar operation and maintenance functions or its technical characteristics as a consequence of the MARTELLO S723 Shelter Restoration.

(R.T2) The Contractor shall provide the services, equipment, and facilities necessary to design, produce, integrate, deliver, install on the radar and CRC sites, and test; to the extent defined herein, the MESR Modkits.




(R.T3) The Contractor shall make maximum use of existing designs, documentation, and processes; to the extent such use is economically beneficial.

(R.T4) The MARTELLO S723 Shelter Restoration Mod kits will utilize commercial off‐the‐shelf (COTS) components and assemblies to the maximum possible extent and shall:

Extend the life of the MARTELLO S723 system by at least 10 years, by introducing technologies that eliminate current and foreseeable obsolescence.

Reduce or maintain the Life Cycle cost by improving the system reliability and availability, and enhance the maintenance features of the radar system;

(R.T5) All the equipment delivered and installed as part of this contract shall be new, not refurbished.

(R.T6) The COTS hardware and software to be supplied both for the Radar and the CRCs, shall be of the latest production in the Contractor product line at the time of the order. The Contractor shall provide any applicable software (on CD/DVD‐ROM) and related User Licenses associated to the COTS hardware and software to be supplied;

(R.T7) The entire system shall be contained within a 19’’ cabinet and shall use common hardware platforms based on industry hardware/software standards for both the processing and I/O sub‐systems. The subsystems shall be contained within industry‐standard and rack‐mountable electronic enclosures.

(R.T8) The upgraded Hardware (HW) and Software (SW) shall be integrated in a modular architecture. The following HW shall be replaced:

Off‐Mount Receiver (OMR): pulse expander, pulse compression units;

Signal Processor (SP): Multibeam IF subsystem (Master Control Unit (MCU) + Beam Processing Units (BPU)), Plot Forming Unit (PFU), Jamming Strobe Extractor (JSE) and SLB Detection and Logic;

RCDSS: Radar Management Processor, Plot Processor, Display Processors and Work Station;

SSR Decoder and Plot Extractor

Radar output data converter and modems

Maintenance Control Facility

Performance Evaluation Tool (PET).

System Clock

Remote Dispaly System (RDS);

Radar Environment Simulator (RES)

(R.T9) The new equipment shall produce the same type of interface impedances, control, timing and data signal levels as the original equipment in order to make a proper interface.

(R.T10) The Human Machine Interface (HMI) of the RCDSS shall be upgraded, consistently with the technological upgrade.

(R.T11) The upgraded radar system shall provide at least all existing radar operational modes and waveforms (there is no requirement but no limitation to add new operational




modes and implement new type of waveforms as long as all those shall remain compatible with the existing antenna and transmitter configuration);

(R.T12) The new Radar Data Processor shall not exceed 50% of the available capabilities under maximum workload conditions.

(R.T13) The Contractor shall deliver and install all the relevant updated application and mission software and the related user licenses, where applicable (see also (D32)).

(R.T14) The mission and application software shall:

Interface the radar network to the external Automatic Data Processing

Execute Performance Monitoring and Fault Isolation (PMFL) both on the radar and on the CRC sites;

(R.T15) For any custom developed assemblies, the Contractor shall place all related design specification, development files, manufacturing drawings and VHDL source code (if any) in escrow for future access for the expected life of the system. Therefore, should the Contractor no longer be available to support the product, the escrowed VHDL code, drawings, etc., shall be available to NSPA to support the further manufacture of the product by another source. The escrow process shall be set up before FSA.

6.2. Performance Specifications (See Confidential Annex 0)

(R.T16) The modified radar shall provide equivalent or improved:

Detection capability in the clear, in ground clutter, in atmospheric propagation and extended range clutter for the full detection range of the radar;

Target angle centered accuracy;

Range resolution;

Signal processor dynamic range;

ECCM capabilities, (e.g. Strobe, in Chaff, Advanced SLB signal processing);

Digital waveform generation capabilities and pulse compression gain;

Plot handling capability.

(R.T17) Equivalent or reduced false alarm rate in clutter and jamming conditions for the full detection range of the radar;

6.3. Interface Requirements

(R.T18) The Mod kits shall be compatible, but not limited in function, with the existing equipment and must accept the input/output protocols, control signals, triggers and data of the existing interfaces of other subassemblies such as the BITE and the Transmitter Sub‐system.

(R.T19) The radar shall provide accurate plot time stamping. The time of detection shall be provided, with an error of no greater than 10 msec. Time of detection is defined as the time that the center of the beam scans over the reported target’s azimuth.




6.3.1. Demarcation Panel

(R.T20) The Contractor shall develop and install at the Radar Head a physical “Demarcation Panel”, which will be the connection interface between the original system and the RHS/RS Mod kit. This Panel is intended to facilitate the connection to the radar for all evaluation purposes. In practice the original radar equipment will have to be kept in the as is condition within the Electronics shelter during the whole evolution period.

(R.T21) The Panel separates the cables, connectors and interfaces that are outgoing / incoming to the Shelter from cables, connectors and interfaces that are required for new equipment installation.

(R.T22) The Demarcation panel is also intended to facilitate at any time the swapping between the original system and the RHS/RS Mod kit for operational reasons and in case of discrepancies encountered with the modification. It shall be possible to perform the swapping between the two systems in less than 15 min.

6.3.2. Communication function between RRH and CRC

(R.T23) The existing radar data interface functionality to the respective CRC shall be preserved, i.e.:

Distribution of the air picture to the CRC sites;

Remotely display the status, and control the radar (SR & SSR) from the CRC site;

Redundancy in the sense that the radar and can be monitored and controlled from at least two CRCs.

(R.T24) All the communications equipment necessary for the data exchange between the Radar systems and the CRCs shall be fully compatible with the existing communications lines between the remote entities and the radar site.

(R.T25) It shall be possible to establish simultaneous connection from two distinct CRCs to a given radar head with master or monitoring capabilities. The radar control selection shall follow a master/slave concept.

6.3.3. Communication function with ADP network interface

(R.T26) Radar messages shall be provided to CRCs for display and tracking purposes. CRCs will be equipped with specific Remote Display System (RDS) and interfaces to the existing Automatic Data Processing (ADP) network environment.

(R.T27) The format for integration in the ADP network is the NATO RSRP Standard Format. The types and format of messages to be delivered to the remote ADP are specified in annex 4B.

(R.T28) The CRC RDSs shall display the information available in the RRH RDSs and be able to execute the same level of radar control.




6.3.4. ACCS Network Interface

(R.T29) The Contractor shall implement a UDP/IP interface on the radar site for transmission through ACCS Network interface of radar data. The respective network equipment and user interfaces in ACCS Network interface shall be a Customer responsibility.

(R.T30) Option (See Option O.T1.)

6.4. System Timing and Waveform Generator (Off‐Mount Receiver)

(R.T31) The SP shall also include the Receiver/Exciter functionality and replace the existing up/down converter stages, oscillator and timing controls.

6.5. Signal Processor

(R.T32) Pulse Compression for all receive beams. The Bidder shall propose and describe in his bid the methods/techniques to compensate (reduce) the unwanted signal modulations and time side lobes caused by transmitter/receiver chain nonlinearities and during propagation.

(R.T33) The Bidder shall propose and describe in his bid the chosen methods/techniques used in the Signal Processor in order for NSPA to evaluate the expected system clutter performance with the modification.

(R.T34) Signal processing parameters shall be adjustable through a HMI in compliance with at least the original system capabilities detailed in the relevant MARTELLO S723 system documentation.

(R.T35) Each beam shall have logic to the maximization of the signal‐noise‐ratio in different environmental (clear, clutter, ECM etc.) and Radar Cross Section (RCS) situations. The best beam processing from target detection point of view shall be based on an automatic selection or combination of the available channel logics.

(R.T36) Independent beam signal processing. Each channel shall contain, Pulse Compression, MTI/MTD, Clutter maps, CFAR and SLB Logic as in the original system.

(R.T37) Clutter map. The radar shall automatically generate and maintain clutter outline data consisting of the height, the strength and the type of clutter, i.e. ground, weather or chaff within the radar coverage. The clutter map shall provide a resolution of at least 2 km in range, the azimuth 3dB beam width in azimuth and the elevation 3 dB beam width in height. Active ECM shall not influence the clutter outline data. The range of the strength shall be consistent with the actual clutter environment at the radar site.

(R.T38) CFAR control by clutter map. The ground clutter map shall have a sufficiently small cell size to control the detection thresholds and false alarm rate in strong ground clutter areas consistent with the detection requirements. Ground clutter shall be considered up to 300 km.

(R.T39) The Signal Processor shall encompass a spare processing channel that can be used in case of failure of one of the 8 receive beams channels. The reconfiguration can be managed either manually by site technicians or automatically by the system (the automatic switch function can be either enabled or disabled by the operator).




6.6. Extractor (Primary Radar)

(R.T40) The new system shall, at least, contain and perform all the functions offered by the original primary plot extractor. Among those:

Range azimuth and elevation bias error correction via site‐dependent and user‐ adaptable data;

Height error correction;

The jamming strobes and plot extraction parameters shall be controllable though a HMI with adaptive and manual set up. The total number of false jamming strobes (including jamming strobes resulting from jamming in the side lobe) shall not exceed 1 per scan for any of the jamming types.

(R.T41) The 3D primary height calculation technique shall provide at least the same information and accuracy as the original system.

6.7. SSR Decoder and Plot Extractor

(R.T42) The secondary extractor shall, at least, contain and perform all the functions offered by the original secondary extractor. Among those:

(R.T43) Real time code extraction shall be provided to detect the presence of valid SSR reply pulses and to reject invalid pulses in accordance with the specifications in STANAG 4193.

(R.T44) A reply in a triple interlaced interrogation mode is properly decoded with at least a probability of 80% at the output of the extractor.

(R.T45) Associate transponder replies with primary Surveillance Radar (SR) plots by position correlation and use of SSR altitude and ADSB information when available. Associated replies shall be reported together with the SR plot or, if association is not successful (e.g.; no radar detection), as an SSR plot.

(R.T46) Means shall be provided to detect all reply codes, in all modes as output by the transmitter/ receiver equipment for the purpose of producing range, azimuth, code and height data for each plot. Decoded height must be available in increments of 100 feet. Selection of target for active decoding should be done by rolling ball or similar. Correlation and garbling shall be indicated as part of the plot code information. Time of detection has also to be part of the SSR plot information.

(R.T47) SSR plots shall be extracted with a range resolution and a range accuracy matching that of the primary radar. The azimuth resolution shall be equal to the effective antenna beamwidth. Means shall be provided for minimizing the probability of generating plots from asynchronous signals (as defruiting for instance).

(R.T48) The equipment shall detect automatically military emergency, identification of position (I/P), all classes of civil emergency and Special Position Indicator (SPI) transponder replies.

(R.T49) Audible and visual alarms shall be provided in order to inform the operator when an SSR emergency signal is received.

(R.T50) The plot extraction system shall be capable of processing up to 1500 SSR plots per scan without any loss of plots, or degradation in system performance due to processing




overload. The system shall also be capable of processing 64 SSR plots per antenna beamwidth without any loss of plots. Under normal plot load (up to 1500 SSR plots per scan), the plot processing delay through the extractor shall not exceed 30° except under conditions of plot overload.

(R.T51) Means shall be provided for reducing the number of false bracket decodes from closely‐spaced or overlapping replies.

(R.T52) Defruiting. Fruit and non‐synchronous replies shall be effectively removed such that, out of 10 000 fruits per second, less than 2 false plots per second appear in the plot output. Means must be provided to reduce the asynchronous replies and other interference with an effectiveness of 0.998 meaning that out of 1000 fruit replies/sec only 2 fruits replies/sec will be at the output. Defruiting can be part of the IFF extractor.

(R.T53) Means shall be provided to reduce the probability of failing to declare a real plot and of reporting a false plot.

(R.T54) deleted

(R.T55) SR/SSR Plot Association criteria:

Means shall be provided to associate transponder replies to the primary radar plots;

In any mode of operation an SR plot report and an SSR plot report of the same target shall be automatically associated;

When both SR and SSR detections are available for a single plot report, the range, azimuth data and time data included in the SR/SSR plot report shall be those from the SR report;

SR/SSR plot correlation shall be tested during in site test using dedicated flights.

Means for sectorised power reduction or general inhibition of radiation shall be provided (from local control and remote control);

Range and azimuth bias error correction via a site‐dependent and used‐adaptable data, (e.g. from lookup table).

6.8. Jamming Analysis Receiver

(R.T56) The new system shall interface with the original Jamming Analysis Receiver and provide at least the same control and jamming information as the original system.

6.9. System Clock

(R.T57) The System Clock (SC) shall provide an accurate time reference for the tagging of system data and synchronization of communication equipment. It shall include a Global Positioning System (GPS) receiver, an external interface for synchronization and an accurate oscillator to allow extended operation without external synchronization. Battery support shall allow the clock to continue running in the event of mains failure. The system clock shall include an indication of current time in hours (0‐24), minutes and seconds in digital form.




(R.T58) The system clock shall encompass the following equipment:

• rack mounted units, including batteries, receiver and interconnecting cables;

• external antenna; • antenna/shelter cable;

(R.T59) The system clock shall provide a time data output with status data to the RCDSS. The external synchronization shall conform to IRIG 104‐70, format B. Time required to achieve initial synchronization shall be less than 10 minutes (assuming a GPS satellite is in view). Synchronization shall subsequently be checked and adjusted automatically. Receivers and antenna required for this purpose shall be supplied as part of the SC.

(R.T60) The receiver shall accept the GPS satellite signals.

(R.T61) The equipment shall operate from the available mains power.

(R.T62) In terms of accuracy and stability, the timing source shall be such that timing data contained in messages represent the true GMT at least to the nearest 1/64 second at all times other than during periods of initial synchronization. In the event of loss of time coded transmissions the accuracy shall be maintained for a period of at least 30 days.

(R.T63) deleted

(R.T64) Antenna feeder. The clock system design shall allow the clock antenna to be located up to 80 meter from the receiver with 30 meter of cable within a Shelter and 50 meter of external cable between the Shelter and the Antenna.

6.10. RCDSS: Data Processing and Communication

(R.T65) The new system shall, at least, contain and perform all the Data Processing and Communication functions as the ones offered by the original RCDSS equipment. Amongst those:

(R.T66) The 3D primary height calculation technique shall provide at least the same information and accuracy as the original system (if the function is not already performed by the Signal Processor).

(R.T67) Association of primary and secondary plots to form a combined plot.

(R.T68) A Multi Scan Correlator function to reduce false plot production significantly in case of heavy clutter or jammer condition.

(R.T69) The effects of moving clutter that may be caused by surface vehicles, ground objects and birds shall be suppressed by the Multi Scan Correlator. It shall be possible to setup individual parameters in 7 different user defined special processing areas and for the background.

(R.T70) In each special processing area it shall be possible to set the individual clutter filter parameters:

Minimum Velocity

Maximum Velocity




The tracking parameters

Track Initiation criteria

Maximum Turn Rate

Track Coasting

(R.T71) Setting start range of a tracker special processing area to zero shall disable the special processing area.

(R.T72) If special processing areas overlap the lowest number special processing area shall take priority.

(R.T73) A function enabling to perform the North alignment of the primary radar (e.g. SUN strobe or ADS‐B) in coordination with the PET.

(R.T74) Management of the Built In Test Equipment (BITE) with information display.

(R.T75) System Control commands. At least the original system control commands are required.

(R.T76) A communication function to:

Format and pass the messages listed in annexes 4A and 4B to the ROCs (Remote Display System, RDS). It should be noted that up to two distinct ROCs can be simultaneously connected to a given radar head.

Receive primary and secondary radar systems control messages from the ROCs as described in annex 4A.

(R.T77) Each radar output shall be connected to modems, and the modems outputs shall be connected to crypto devices which will be provided and installed as PFE. The modems to be used by the manufacturer shall be compatible with crypto equipment. The mechanical and electrical specifications of the crypto equipment will be provided to the contractor in due time. Suitable place for crypto devices shall be provided at the same rack with modems.

(R.T78) A module to maintain and display time and date information received from System Clock – GPS, in manual (if the GPS signals are missing) and automatic mode. The system clock will be used for plot time stamping.

(R.T79) Information Time Delay. The time delay shall be measured between the time of detection and the ADP interface at the Line Sharing Device (LSD) assuming a sufficient line capacity.

(R.T80) Integration within the existing Automatic Data Processing environment. The radar system will be integrated into the existing NADGE system. The radar system shall be designed in such a way that the integration into the ACCS Network interface will be easily achievable (see also 6.3.4). This shall be achieved by implementing a Data Buffer and a Priority Filter.

(R.T81) All information produced by, or fed into, the radar system shall be stored in a Data Buffer (DB). The radar system shall derive subsets of this information to be sent to a




connected user (ROC). Different users may require different subsets of the Data Buffer's contents.

(R.T82) In addition, by remote controlling the Priority Filter (PF), a remote user may assign priorities to types of data. The radar system shall then assemble the information to be sent in the required order.

(R.T83) Information derived by the radar system shall be kept present in the Data Buffer for 30 days and for easy access at a later time.

(R.T84) The DB and PF structures shall be realized with software and shall be well documented.

(R.T85) Control Commands from Automatic Data Processing (ADP). The commands received from the ADP system shall control the users Priority Filter with the mode 4 interrogation, the radar silence function and the area outlines requests.

(R.T86) Line Sharing. Existing lines shall be used for integration with ADP, i.e. communications between:

the radar terminals and the radar head

ADP and the radar head

(R.T87) It is foreseen that the various interfaces to the LSD are subject to changes. Therefore, the functions of the LSD shall be provided by software.

6.11. RCDSS: Monitoring and Control

(R.T88) The new System shall, at least, contain and perform all the CONTROL and DISPLAY functions offered by the original RCDSS display equipment (Maintenance Work Station and Performance Evaluation Computer) in order to:

Monitor and control all functions and the performance of the radar at the maintenance work station of the radar set

Monitor and control operational functions and performance of the radar at the TPO (see hereafter) position in the operations center

Monitor and analyze the ECM, chaff and clutter environment and to control the ECM and clutter reduction facilities of the radar at the ECCMO position in the operations center

Track Production Officer mode (TPO) enabling monitoring and control of the peacetime radar facilities

Electronic Counter‐Counter Measures Officer mode (ECCMO) offering all the capabilities of the TPO mode plus monitoring and control of the wartime facilities

(R.T89) The monitoring and control facility at the Maintenance Work Station shall include all capabilities specified for the facilities at the TPO and ECCMO positions.

(R.T90) Information displayed at the terminals shall be easily readable. Graphic, alphanumeric and combined graphic/alphanumeric presentations shall be provided to




accomplish this. Control actions entered by the operator shall be indicated on the display. The acknowledgement of such control actions shall also be indicated on the display.

(R.T91) Control of the radar shall be possible from two local positions (maintenance work station at the radar head and a position in the bunker) and two remote positions, where the remote positions shall have primary control as default, but the local position can take over in an orderly manner.

Among those:

(R.T92) Maintenance Work Station. The radar head shall be provided with a means to continuously supervise equipment operation, to operate the radar and to support maintenance actions. These means shall be centralized at one position which will be referred to as the maintenance work station. The new maintenance work station shall include at least the following elements:

A plan position indicator displaying

PSR videos

SSR videos

PSR plots

SSR plots

Associated PSR/SSR plots

Jamming Strobes

Radar height upon request

SSR mode/code information on selected plots (only)

Mode 4 target status information upon request

Clutter areas outlines

A monitoring and control facility to cover the TPO and ECCMO functions and the mass raid assessment function.

Some monitoring devices to display the more detailed equipment status to include among others the BITE check results.

A Remote Control & Display to display relevant equipment status data of the radar system.

Some control devices to operate the radar head as far as not covered by the monitoring and control facility to include all control functions.

(R.T93) Monitoring and Control Facility (TPO). The terminal at the TPO position shall consist of a general purpose, alphanumeric and graphic display (or PPI) and a keyboard. It shall be possible to select display of video‐status information. An audible alert and force attention display capability shall be provided to indicate changes of certain status information. It shall be possible to execute control functions to two (2) Radars with a growth capability to four (4).

(R.T94) TPO Video‐Status Information

For the TPO the following status information shall be available for display:

Electrical power source go/no go

PSR overall status go/no go (**)




PSR limited operation e.g. (**)

PSR‐TX/RX modules out,

processor failure,

Spine temperature

PSR TX radiate/not radiate

PSR detection performance in clear environment

Radar in maintenance mode

PSR plot/strobe processing capacity occupied (*) (**)

Data Buffer processing capacity occupied (*) (**)

SSR go/no go (**)

SSR TX radiate/not radiate (**)

SSR Extractor processing capacity occupied (*) (**)

PSR Battleshort

Frequency Mode

Selected Peacetime Frequency

PSR Search Mode

SSR Interlace

SSR ECM Warning (**)

Number of PSR and SSR plots per scan for transmission

Processing channel

Manual ECM

Mass raid

Area outlines for modes of operation, priority filter settings, and clutter filter

Activated inhibit (PSR, SSR or both): sectors (from azimuth to azimuth)

Connected users conspicuously indicating the ops center having control over the radar

Fire detection (**)

Notes:

(*) Warning threshold shall be selectable, status and overflow shall be indicated.

(**) Audible, alert and force attention display.

(R.T95) Also the following video shall be available for display for the TPO:

PSR video (co‐located site only)

SSR video (co‐located site only)

PSR plots

SSR plots

Associated PSR/SSR plots

Strobes

SSR mode/code information

Mode 4 plots upon request

Clutter outline data

Synchronization data (co‐located site only)

Area outline data




(R.T96) TPO Radar Control Functions. It shall be possible for the TPO to execute at least the following control functions:

PSR Inhibit

SSR Inhibit

PSR/SSR Inhibit

SSR Interlace

Radar Silence

Fixed frequency selection (to be set anywhere in the required operating frequency bandwidth)

Filter Setting

PSR Operating Modes (as applicable)

Warning threshold control

PSR processing channel

(R.T97) Monitoring and Control Facility (ECCMO). The terminal at the ECCMO position shall consist of a general purpose, alphanumeric and graphic display and a keyboard. It shall be possible to select display of status information. An audible alert and force attention display capability shall be provided to indicate changes of status information. It shall be possible to execute control functions.

(R.T98) ECCMO Jamming Information. The status information as specified in (R.T99) shall be available for display for the ECCMO. This shall be accomplished by selecting the TPO‐Mode.

(R.T99) In the ECCMO‐Mode the following jamming status information shall be available for display:

Bearing and intensity of all jamming strobes in a geographic form (update per antenna scan)

Quantity of jamming strobes per antenna scan and changes thereto

Frequency, intensity and type of jamming over the entire radar bandwidth in one display (update per antenna scan)

Azimuth, intensity, width, elevation, and type of jamming of selected strobes on request (update per antenna scan)

Equipment status to include selected frequency (band), selected frequency, mode, activated ECCM, selected search modes, SSR ECM warning, radar silence for PSR and SSR (update cycle 1 min)

(R.T100) ECCMO Radar Control Functions. It shall be possible for the ECCMO to execute at least the following control functions:

PSR Battleshort

Frequency Modes of operation

Search Modes of operation

Activate ECCM's o SLB




o High PRF o Stagger PRF

Warning Threshold Control

(R.T101) Terminals. TPO and ECCMO terminals can be combined in one workstation.

(R.T102) Capability to display information from the original Jamming Analysis Receiver installed within the SPINE.

(R.T103) Capability to control the radar. The full radar system should be made available fully operational after reboot in not more than 6 minutes. However this time requirement might be readjusted depending on the specific SPINE booting process but, shall be minimized.

(R.T104) Capability to present the radar video signals echoes/plots/strobes in different presentation forms (at least Plan Position Indicator and Range Height Indicator).

(R.T105) The possibility to display overlays and grids when displaying radar signals, including at least geographic maps, range rings and lines of constant latitude and longitude.

(R.T106) The possibility to display, record and playback information.

(R.T107) A capability to maintain and display time and date information.

(R.T108) All display monitors shall be Flat Screen displays having at least 21” of useful area for information display.

(R.T109) The load status of HW and SW components shall be reflected in status data of the radar terminals. In case of critical SW or HW load conditions operations personnel shall be alerted prior to the occurrence of an overload situation. The operator may then take corrective actions to avoid functional degradation of the system. A capability shall be provided which allows the operator to individually set the load threshold for the alert. Nevertheless, should any overload condition occur, system functions of high operational priority shall be preserved as long as possible while low priority functions shall be degraded first.

6.12. RCDSS: Bite Reporting

(R.T110) BITE reporting is originally made through the RCDSS. The new BITE processor and display shall provide the same status messages as the original system regarding the original subsystems. The new BITE shall interact with the SPINE which is to remain untouched.

(R.T111) The BITE reports shall also be sent to a Remote Display System (RDS) located up to 100 meters from the radar. The RDS will be the same display as the one located within the Electronics Shelter.

(R.T112) The original BITE architecture and associated message structure is available at NSPA in the relevant system documentation (list of available documents in Annex 3).




6.13. RCDSS: Data Buffer

(R.T113) The radar system shall have a function which is referred to as Data Buffer (DB).

(R.T114) The DB represents a database in which all data available in the radar is stored. This comprises target data as well as the actual radar modes of operation and data from the built‐in test equipment (BITE). In addition, selection, sorting and association of various data have to be performed, usually under control of the user of the DB.

(R.T115) The DB structure shall be realized with software and shall be well documented.

(R.T116) The functions of the DB shall be as follows:

(R.T117) Data generated by the extractor or other sources shall be fed into the buffer independent of the source of the data. This data is then available for transmission to the different operating centers or other users or for use by the radar system.

(R.T118) The DB shall be the only interface between the radar head and its environment. Therefore the DB has to maintain radar generated data (e.g. plot data) as well as user received data (e.g. control commands).

(R.T119) The setting of a certain mode of operation shall be accomplished by storing the appropriate control data into the DB, regardless of the source of the data (radar terminals, manually entered on user's DP system).

(R.T120) A capability shall be provided to automatically count all PSR and SSR plots per scan in the data buffer for transmission to a user.

(R.T121) An audible and visual warning shall be provided if the numbers of plots between two consecutive scans increase or decrease by a percentage figure which shall be selectable in steps of 5, 10 and 30.

(R.T122) A copy of the clutter map shall be part of the DB. The map may be transmitted to the user as a set of points which represent the outline contour formed from those sample strengths which exceed a threshold (the ISO clutter level) set by the operator.

(R.T123) It is a task of the PF to transform the clutter map into the format required by the user. It must be possible to send the whole map as well as only a set of points, which represent the outline contour formed from those sample strengths which exceed a threshold (the ISO clutter level) set by the operator. The transformation of the clutter map performed by the PF may also comprise a reduction of the resolution of the map.

The set of points (ISO Clutter Line) is sent to the RDS ‐ and then to the NADGE ADP.

NOTE: A reduction in resolution of the clutter map is controlled by the Remote User(s).

(R.T124) The clutter map is for interaction with the Remote Site only and not for interaction with remote radar integration network.




6.14. RCDSS: Priority Filter

(R.T125) The selection of data to be transmitted to a user shall be performed by a function called Priority Filter (PF). The PF structure shall be realized with software and shall be well documented.

(R.T126) Each user shall have his own PF that can be set to best fit operational needs at any time.

(R.T127) The PF shall be capable of performing the selection of data as well as a prioritization of the sorting of data.

(R.T128) The setting of the PF for a user shall also be part of the DB. The user may set his PF by assigning priorities to types of data.

A typical assignment may be (in order to decreasing priorities):

Strobes from a specified sector or cone

Plots from a specified volume

Other strobes

Other plots

Other data (amplifying data, status data)

The PF then has to search the available data in the DB and to decide about transmission according to the priority level and free line capacity.

(R.T129) Time Tag. Data with low priorities may be delayed and shall be kept in the DB for a certain time. This time shall be user‐selectable and shall be part of the PF setting. Due to possible delays all data in the DB shall be tagged with the time of detection. For this purpose the radar system shall be equipped with a highly accurate real time clock.

(R.T130) Formatting of Outgoing Data, Realization of the DB and PF Structures. The PF also shall format the outgoing data into the required message types. The DB and PF structures shall be realized with software and shall be well documented. A change to the message formats or to the logic of the PF shall be possible by software change only.

6.15. RCDSS: Performance Evaluation Computer (PEC)

(R.T131) A computer called Performance Evaluation Computer for the evaluation of radar performances in day to day operation as well as for special radar evaluation mission shall be a part of the RCDSS environment. This computer enables the operator to record radar plots and off‐line checks of the system alignment. The PEC shall also offer a North alignment capability using Sun strobes or ADS‐B. A new evaluation tool (PET) running on a PC shall be proposed at least with the same test/recording functionalities as the original PEC.

6.16. Remote Display System (RDS)

(R.T132) Two types of RDS sites are to be considered:

• co‐located with a S723 radar head as in Bornholm

• non co‐located with a S723 radar head as in KARUP




Co‐located and non‐co‐located RDSs are identical except for the fact that the co‐located RDS shall additionally provide the operators (TPO and ECCMO) with the primary and secondary video signals upon selection.

(R.T133) The new RDS shall, at least, contain and perform all the functions offered by the original RDS equipment in terms of display, data processing and remote control capabilities.

(R.T134) The RDS shall perform the Line Sharing Device Functions and shall be a single computer subsystem of the same form as used in the RCDSS (i.e. uses identical elements of hardware as well as sub‐sets of software elements). The Remote Processor (RP) shall support at least the following equipment:

PPI display and control console

TPO radar terminal

ECCMO radar terminal

EC RES terminal

ADP interface

Radar interface

(R.T135) Like for the RCDSS at the radar head, TPO, ECCMO and EC terminals can be regrouped in one. The RP shall be designed to accommodate all necessary interface processors for communications with the above equipment as integral parts of the computer. These processors shall be connected directly to the internal bus and where necessary have autonomous access to random access memory. The RP shall include the line sharing functions to allow the same set of lines to be used for all communications with the radar head.

(R.T136) The RP shall route the data associated with the radar being controlled to and from the ADP (RIS/MASE network, annex 4B). The RP shall route the data associated with the radar being controlled/monitored to the PPI display and the radar terminals as fitted (annex 4A).

(R.T137) Capability to display radar reports as listed in paragraph 6.10 and 6.11.

(R.T138) The RDS shall provide a TPO and an ECCMO terminal for the control and monitoring of the radar, together with a single PPI display. The PPI shall display data relating to the radar which is being controlled by the RDS.

(R.T139) All terminals in an RDS shall be of identical type to those used in the RCDSS, and shall consist of a display and keyboard. The terminals shall incorporate alphanumeric and graphics displays. Control actions entered by the operator at an RDS terminal shall be indicated on the display, normally on a single line at the bottom of the display, and acknowledgement that the input command has been actioned shall be indicated on the same display. All data entry at the RDS radar terminals shall be validated. Invalid entry shall result in the data being aborted and data entry (i.e. control) then may be recommenced again.




(R.T140) The RDS shall have the capability to operate at the required link rates without any data degradation or reduction of operational facilities and capabilities.

(R.T141) RDS/RADAR ‐ PPI Data (when co‐located at radar). When a ROC and a radar head are co‐located, the radar head shall provide the following signals for the RDS PPI display:

Delayed Display Trigger

ACP and delayed NM (NRP)

The "delayed" signals are timed to match the processing delays within the Signal Processor

Videos 2 PSR and 2 SSR

(R.T142) Capability to present the radar plots/tracks/strobes in different presentation forms at least Plan Position Indicator and Range Height Indicator.

(R.T143) The possibility to display overlays and grids when displaying radar signals, including at least geographic maps, range rings and lines of constant latitude and longitude.

(R.T144) The possibility to display, record and playback information.

(R.T145) A module to maintain and display time and date information

(R.T146) All display monitors shall be Flat Screen displays having at least 21” of useful area for information display.

(R.T147) ADP. Direct conversion of the radar data into RSRP format for transmission to radar integration network (serial line although Ethernet TCP/IP is acceptable). Refer to annex 4B for a description of the messages format.

(R.T148) Loop test function to check and measure the status and capabilities of the communication lines.

(R.T149) The communication functions shall be compatible with the crypto devices installed by the Host Nation to decrypt radar head messages.

6.17. Performance Evaluation Tool (PET)

(R.T150) A new Performance Evaluation Tool (PET) running on the PEC shall be proposed at least with the same test/recording functionalities as the original PEC. This includes Data Analysis and Display, Output Data File and PET Environment.

(R.T151) A dedicated Computer with specific interfaces shall be installed for hosting PET software. This tool will be used at least:

by the site technicians for standard system maintenance

during periodic site visits by NSPA R‐SPC engineers

for OSM

for system acceptance tests

It shall be possible to check the alignment of the surveillance radar and the secondary surveillance radar to true north by using solar radiation and to evaluate radar performance by using flight data




These facilities shall record, store, process, analyze and display radar target data as well as manual input data if necessary and shall be interfaced with the radar head in an appropriate manner (refer to the PET requirements)

(R.T152) At least the following additional capabilities are required:

verification of the good working state of the beam calibration loop with manual adjustment capabilities

verification of the beam alignment for the height calculation

verification of the stability and performance of the Tx pulse expander and pulse compression units

verification of the good working state of the SLB logic

verification of the good working state of the target detection logic in different clutter/ECM etc conditions

verification of the antijamming capabilities

verification of the correct removal of “n”‐th‐time (n≥2) around echo for targets of large RCS

(R.T153) The SPINE shall remain untouched by the system upgrade: none of the equipment/sensors implemented by the contractor and necessary to apply the different tests shall be installed inside the SPINE.

(R.T154) deleted

(R.T155) The PET shall have a specific analysis software package and contain a Graphical User Interface for operator controls and display. The PET shall allow for specific analysis of data recorded from the radar for evaluation of radar operations and performance as the original PEC. Only the types of analysis offered by the PEC are to be retained but not the way they are displayed. The data recorded by the PET in real‐time shall include upon selection by the operator:

All incoming plots and jamming strobes

All radar status messages

(R.T156) The PET shall be able to record all measured information in real time mode and the input/output data of the DSP sub‐software module analyses result shall also be processed and displayed in real time. (The plot output time delay with regard to real time is determined by Contractors but shall be better than or equal to the original as indicated in Table 1 in Annex 3).

6.17.1. Radar Raw Data Files

(R.T157) The radar RAW data is related to the radar settings in any operation mode. The radar RAW data recordable by the new system shall, at least, cover the type of data recorded by the original RCDSS equipment. In addition at least the following information shall be recordable in order to be further analyzed and displayed:




Incoming (receive beams) and outgoing (expanded pulse) IF signals of the Electronics Shelter,

Raw video for each beam before and after pulse compression

Raw video before and after CFAR

Data of all beam channels before automatic selection on combination of the best channel(s) logic of the signal channels and after it

clutter/chaff map built by the new system

Jamming information from the original Jamming Analysis Receiver (JAR) and from the Signal Processor

Mass Raid

Beam alignment information

(R.T158) The RAW data files and PLOT files are to be analyzed and results are displayed to the operator. The results of the analysis of the RAW data are also to be transferred into an OUTPUT data file readable and transportable on platforms external to the site.

6.17.2. Data Analysis and Display

(R.T159) The RAW data and PLOT analysis is at least to be displayed as follows:

Maps:

DTM (Digital Terrain)

Radar coverage

Clutter

SR/SSR plot association and alignment

SR/SSR plot accuracy

SSR decoding statistics

Sun position/strobe calculation

Azimuth Accuracy /Jammer strobe resolution Accuracy

Plots:

PSR Plots

SSR Plots

Combined Plots

Jamming Strobes/Sectors

Mass Raid Analysis

Jamming Analysis

Radar System Status

Azimuth Status messages

(R.T160) Range performance worksheet (Preferably Blake Chart type)




(R.T161) Pd (Probability of detection)

(R.T162) Pfa (Probability of false alarm) analysis

(R.T163) Automatic Rx. Gain Equalization and alignment analysis

(R.T164) Shape of the Expander Output IF waveform with visual indication of compliance with specifications.

(R.T165) Shape of the Compressed Pulses with visual indication of compliance with specifications (for all beams and SLB channel).

(R.T166) Clutter map performance analysis: PPI representation of the Improvement Factor (IF), with visual indication of compliance with specifications. The IF evaluation shall be user selectable to be performed using real clutter or a CFP Radar Target Generator.

(R.T167) PPI representation of Jamming Strobes.

(R.T168) PPI representation of the Jamming information of the JAR and the SP

(R.T169) PPI Mass raid representation can be filtered for position, beam messages, and frequency.

(R.T170) The Digital Signal Processing (DSP) Performance check function can calculate the amplitude or phase for the selected data. Analysis results can be displayed in the form of tabular lists and 2‐D graphs.

(R.T171) DSP Performance. This analysis task shall use, at least, two types of data files recorded from the DSP prior to plot extraction to evaluate DSP performance:

DSP DDM (Digital Demodulation) files: These files contain “raw” I & Q (In‐phase and Quadrature) data for the 8 Main and SLB channels. DDM files can be filtered for beam messages, short/long range and frequency.

DSP envelope files: These files contain data already processed by the DSP. Envelope files can be filtered for position, beam messages, short/long range and frequency. The DSP Performance function can calculate the amplitude or phase for the selected data for the 8 receive channels and the SLB channel. Analysis results can be displayed in the form of tabular lists and 2‐D graphs.

(R.T172) Plot loading statistics represented per beam as a function of time (scan): combined plots, SR plots, SSR plots, false alarms.

(R.T173) SR/SSR alignment (range, azimuth and height).

The display environment shall offer the capability to print the displayed results and to save them as a picture file (at least in JPEG format).

6.17.3. Output Data File

(R.T174) The output file compiles the results of the analysis. At least two types of output files shall be considered: the output radar data file and the output plot data file.

(R.T175) Those files are to be produced in ASCII (text).




(R.T176) The OUTPUT radar data file is to present the results of the analysis; its structure shall be suggested by the contractor and approved by NSPA at the end of design phase.

(R.T177) The OUTPUT plot data file shall present at least the following plot information:

For each PSR,SSR combined plot: range, azimuth, elevation angle, detection time

For each combined/primary plot: Beam number

For each combined/primary plot: Mass raid flag

For each combined/primary plot: calculated height

For combined/secondary plots: IFF codes for each interrogation mode

For jamming strobes: azimuth, elevation, frequency

6.17.4. PET Environment

(R.T178) The PET shall be developed and run under a high level programming environment (like MATLAB or NATIONAL INSTRUMENTS/LABVIEW for instance) in order to facilitate the migration to other analysis tools external to the radar.

6.17.5. Test Points

(R.T179) A number of tests and monitoring points shall be made available on a front plate within the Display Shelter for maintenance and verification purposes.

(R.T180) The following Radar Timing Signals test points shall be made available mounted as a female BNC connector:

NRP true

NRP corrected

ACP

Trigger

(R.T181) The monitoring of the Expander Output IF and compressed pulses for all beams shall be made available on SMA front plate connectors.

(R.T182) Separate Analogue Radar logarithmic video for each of the 8 beams and SLB channel (one distinct test point for each of the 8 beams and SLB channel).

(R.T183) One or several external connection points to the RRH LAN(s).

6.17.6. Radar Environment Simulator (RES)

(R.T184) The RES shall produce a fully realistic simulation of primary radar signals received by the S723 under normal and hostile (ECM) conditions in order to;

Train the site personnel in the optimization of the radar system settings for detection within a predefined environment,




Provide a realistic ECM environment with compromising the radar system’s active ECCM capabilities to hostile ELINT/SIGINT observations,

Assess the radar’s effectiveness under EW conditions.

(R.T185) The RES shall generate simulated signals to be mixed with live signals of the primary radar.

(R.T186) These signals shall include a range of different types of targets, which shall have a target identity tag hidden from the operator, together with simulated jamming and chaff to be reproduced over the complete operating frequency band of the radar.

(R.T187) The RES target identity tag shall be included in all associated output messages (i.e.; plot, strobe and chaff).

(R.T188) The RES shall simulate all radar processes prior to the point of signal injection (e.g. Transmitter frequency, power and waveform, antenna gain patterns, propagation, etc.) and respond to all radar controls.

(R.T189) RES shall be capable to accept both pre‐programmed scenarios and online commands for processing.

(R.T190) RES control shall be both local and remote from any CE and/or RRH.

(R.T191) Targets and any associated ECM effects (e.g.; jamming and chaff dispensing) shall automatically cease when the target is declared killed by any CE. However, already shown chaff will continue blooming in accordance with the established parameters.

(R.T192) The radar performance shall not be degraded by the addition of the RES.

(R.T193) The RES shall be used also for testing purposes, therefore should contain validated target models to assure that the test results which are generated using the RES are indicative of system performance.

(R.T194) Exercise duration: At least two hours with maximum simulation load.

(R.T195) Target Capability:

(1) Up to 60 targets of which 12 are controllable in real time, the rest being pre‐

programmed,

(2) Up to 12 jamming aircraft of which 4 are controllable in real time, the rest being

pre‐programmed,

(3) Three aircraft may overlap in azimuth on any bearing, two may be active

jammers, and one may be a chaff dispenser.

(R.T196) Active Jamming Simulation Capability

(1) Twelve active jamming aircraft per scan of which up to four can be controlled,

the rest being pre‐programmed,




(2) It shall be possible to simulate synchronous repeater jamming together with at

least two other types of active jamming from any source in the entire frequency

band.

(R.T197) Jamming power levels: 1 to 70 dB above radar system noise level.

(R.T198) Chaff Simulation Capability

(1) Four of the 12 active jammers can also be chaff dispensers, each being able to

drop three legs of chaff of total mass one ton distributed in the appropriate

wavebands,

(2) Chaff parameters will be controllable (horizontal and vertical speed blooming

rates, spread, density, turbulence),

(3) Up to 12 chaff legs per scan and up to eight chaff legs to be positioned

simultaneously,

(4) The bloomed chaff velocity spectrum shall be consistent with the radial velocity

spectrum of any collocated live weather.

(R.T199) The RES shall provide the following capabilities:

(1) Start/stop RES simulation,

(2) Setting the sectors in which the RES shall be active,

(3) Choose up to 16 exercise programs,

(4) Interrupt a simulation program at any point during the exercise and subsequently

restart the program at any point in time in the scenario,

(5) Initiate up to 4 targets and modify their track and jamming parameters at any

point during an exercise or during normal day‐to‐day operation (controllable

jamming targets).

6.17.7. Installation

(R.T200) The S723 RHS Modkit shall be contained in one 19 inch cabinet to be installed outside the Electronics shelter (in an equipment room next to the shelter room) and shall accept the mains available in the equipment room.

(R.T201) The cabinet shall not make use of the S723 original air conditioning system and shall therefore contain a cabinet ventilation and cooling system.

(R.T202) The cabinet shall include a UPS in order to supply all software‐based equipment for a minimum period of 15 minutes. This is applicable for both Radar Head Solution (RHS) and Remote Solution (RS).




6.18. Reliability, Maintainability and Testability

6.18.1. Reliability

(R.T203) The system shall have the following reliability characteristics:

Minimum MTBF = 1400 hrs

Minimum MTBCF = 6000 hrs

where failures shall include all hardware faults within the installed equipment as well as software faults that degrade the performance of the system with respect to its specification. Critical failures are those failures which result in a cessation of the system capability to perform its mission and require immediate corrective action.

6.18.2. Maintainability

The system shall have the following maintainability characteristics:

(R.T204) At least 95% of all maintenance tasks (HW and SW) shall require skills, tools and test equipment such that they can be carried out at Organizational Level1.

(R.T205) Maximum MTTR(O‐level) = 20 minutes.

(R.T206) The system shall not require organizational level preventive maintenance other than visual checks and start‐up self‐calibration and/or test.

6.18.3. Testability

The system shall have the following Built‐in‐Test (BIT) capability:

(R.T207) The radar shall provide BIT capabilities to meet the maintainability requirement using On‐Line & Off‐Line diagnostics.

(R.T208) The new BIT equipment (BITE) shall be compatible with the existing BITE.

(R.T209) Start‐up BITE shall be initiated at system/equipment power‐up and it shall be able to diagnose the respective LRU in less than 5 minutes.

(R.T210) On‐line BIT shall be able to detect 98% of the LRU failures. On‐line BIT isolation capability shall be as follow:

100% of the failures within a group of not more than 3 LRUs; 95% of the failures within a group of not more than 2 LRUs; 90% of the failures to 1 LRU.

1 Organizational Level Maintenance includes fault monitoring by BITE and/or visual inspection, removal and replacement of LRUs, system functional testing and preventive maintenance tasks. The maintainers use simple test equipment (standard and special‐to‐type) in addition to BITE for on and off line diagnostics. O‐level support for SW includes all those tasks that are within the capabilities of a system manager, i.e. on and off line diagnostics, manual restart, upload of SW upgrades and patches, etc.




7. PROJECT DEVELOPMENT AND MAJOR TECHNICAL MILESTONES

7.1. Generic

(D6) The Contractor shall develop the design of the equipment integration and any Non Developmental Item (NDI) adaptation required to adapt the equipment to the particularities of this project.

7.2. System Requirements Review (SRR)

(D7) Within 4 weeks of Contract Award, the Contractor shall organize a SRR meeting to be attended by NSPA at his facility

(R.D7.1) During the SRR the Contractor and NSPA shall conduct a joint review of the requirements in this Statement of Work to ensure a mutual understanding. The Contractor shall present and justify in detail all technical and programmatic aspects of his proposal, including:

i. Requirements functional allocation to subsystems (Modkit functional block diagram)

ii. Implementation of System Interfaces

iii. Initial assessment of reliability, testability and maintainability requirements

iv. Verification strategy

v. Assumed contributions/support from NSPA and Host Nation

vi. Schedule details, including required downtime.

(D8) Within 1 week of the completion of SRR the Contractor shall prepare and deliver the SRR meeting record, including any issues, agreed actions and closure plans and shall submit it for acceptance to NSPA.

7.3. Critical Design Review (CDR)

(D9) The Contractor shall organize a CDR meeting to be attended by NSPA at his facility.

(R.D9.1) The Contractor shall obtain from NSPA the authorization to call the CDR meeting, which shall be in principle granted.

Since the starting point of the design will be based in an existing and tested solution, NSPA doesn’t require the execution of a Preliminary Design Review.

(R.D9.2) At CDR, the initial Product Baseline (PBL) shall be established and the Contractor shall provide evidence that the stable design meets the requirements in this SoW. In particular, the Contractor shall:

a. Provide the final identification list of legacy HW and SW to be removed.

b. Provide evidence that the design meets the requirements in Section 6, to include:




• detailed review of the initial HW and SW PBL to meet the requirements in

Section 6, including a HW Configuration Tree (D32)

• fully developed RM&T prediction. The Contractor is not bound to use any particular methodology for RM&T modelling, but NSPA may require a justification of the methodology used, which must have a sound engineering approach.

• detailed assessment on obsolescence mitigation and supportability improvement achieved by the new design;

• assessment of the impact of the new design on system basic power requirement.

c. Review the RSPL.

d. Provide an initial Special Tools and Test Equipment (STTE) list (if applicable).

e. Brief on production planning and risks related to production of the prototype or production units.

f. Present the Baseline Assessment (BA) procedures for NSPA acceptance (see D16);

g. Present the final Verification and Acceptance Test Plan, including a Verification Requirements Traceability Matrix for NSPA acceptance (see Section 8.1).

h. Present relevant elements of logistics support related with the requirements of this contract.

i. Provide a full analysis of required documentation changes (see D27).

j. Review the status of technical risks.

k. Review the Master Schedule.

(D10) The Contractor shall submit the information package for review at CDR at least 4 weeks ahead of the meeting.

(D11) Within 1 week of the completion of CDR the Contractor shall prepare and deliver the CDR meeting record, including any issues, agreed actions and closure plans and shall submit it for acceptance to NSPA.

7.4. Production and Factory Acceptance Test (FAT)

(D12) Following CDR, the Contractor shall complete the physical production of all the new equipment and software required for the modification as per the design approved at CDR.

(R.D12.1) The Contractor shall be responsible for the procurement of all material required for production of the Modkits.

(R.D12.2) The equipment shall comprise one Modkit for the Remote Radar Head site and two Modkits for the CRC sites

(D13) Upon completion of the production, the Contractor shall perform FAT on every Mod kit and within 2 weeks of the completion of FAT shall submit to NSPA the respective Certificate of Completion and Factory Acceptance Test Report. Within ten (10) calendar days, NSPA will review the Certificate and the Report and provide any comments. In the absence of comments in this period, the Certificate of Completion and the Test Report will be deemed accepted.




(R.D13.1) The Contractor shall provide NSPA with 30 days notice of the exact scheduled FAT date and NSPA shall have the option to nominate staff to witness the tests. If NSPA decides not to provide a witness, the FAT shall be conducted by the Contractor as scheduled, and the Contractor’s Quality Assurance organization will observe the testing on behalf of Customer.

(R.D13.2) The FAT Report shall contain the following information:

P/N and S/N of the kits tested;

P/N of the sub‐assemblies tested;

List of performed system sub‐tests;

Recorded test results with a note “Passed” or “Failed” IAW the V&A‐T Plan, where applicable;

Recommended course(s) of action with respect to each of the failed sub‐tests;

Overall Pass/Fail conclusion. A conclusion of “Pass” shall entail the Contractor’s assessment that the design is mature for implementation in operational systems;

Any other, as appropriate (data recording and analysis files, printouts, pictures, records).

7.5. Delivery, Installation, Integration and Site Acceptance Testing (SAT)

(D14) Upon completion of FAT, the Contractor shall pack and deliver under his responsibility; install and integrate the developed HW and SW (Modkits) in the radar site and 2 CRCs (see Table 1) in accordance with the Master Schedule (see (D2)).

(D15) The Contractor shall also be responsible for the shipment to the sites of the INCO spares (see 9.4.1), tools and test equipment property of the Contractor required for the installation, integration and testing.

(D16) Before the removal of the currently installed equipment and installation of the Mod kit on each site, the Contractor, the NSPA representative and a representative of the Host Nation shall jointly perform a Baseline Assessment (BA) to evaluate the status of the radar system. The Contractor shall reflect the result of this evaluation in a Baseline Assessment Report, which shall be signed by the three parties.

(R.D16.1) The purpose of this BA is to assess and document the radar operational and technical performance status by using the available on‐line and off‐line tests and performance checks. The Contractor may also use their own test sets and special tools and test equipment.

(R.D16.2) The BA tests to be performed shall be described in the V&A‐T Plan.

(R.D16.3) The Baseline Assessment Report shall detail the system status and all relevant system faults or conditions prior to the implementation of the modification. For each condition, this report shall also state the assessment and way ahead agreed by the three parties; for example:

An assessment that the condition may affect or be affected by the implementation of the modification or the subsequent test activities, and corrective action must be taken prior to the implementation;




The acknowledgement that the condition will persist after the implementation of the modification, but it is unrelated to the requirements of the new equipment and the system operation and testing can be conducted in the presence of this condition;

Any other agreement reached with respect to each condition.

(R.D16.4) This Baseline Assessment shall be repeated, after the completion of the modification activities as part of the SAT, to verify that no technical or operational degradation has been introduced.

(D17) Prior to each Mod kit installation the Contractor shall, in case the space is needed for the Mod kits, remove all hardware and software being replaced or no longer needed.

NSPA and the Host Nation shall be responsible for the storage and disposal of the removed equipment, no longer required.

(D18) Upon removal of the equipment being replaced or no longer needed, the Contractor shall proceed with the installation and integration activities.

The Host Nation shall make the MARTELLO S723 Radar System available for use by the Contractor in accordance with the Master Schedule (see (D2)).

(D19) deleted

(R.D19.1) The Contractor shall be responsible for the Modkit installation and all checkout activities, including the verification activities in accordance with the requirements of this SoW.

(D20) The Contractor shall be responsible to bring the modified radar performance up to the MARTELLO S723 Specification (see Annex 0), except where limited by the performance recorded during the BA.

(D21) Upon completion of each installation and integration, the Contractor shall conduct SAT in accordance with the V&A‐T Plan and in the presence of NSPA and Host Nation staff, who will follow the progress of the SAT activities.

(D22) Within 1 week of completion of the SAT, the Contractor shall provide a SAT test report and Certificate of Completion in Contractor’s format. The mutually agreed SAT Report will be signed by NSPA, Host Nation and Contractor representatives. The SAT Report will be the main element providing evidence for Provisional Site Acceptance (see Section 8.2.2).

(R.D22.1) The SAT Report shall contain the following information:

P/N and S/N of the items tested (at LRU level)

List of performed system sub‐tests;

Recorded test results with a note “Passed” or “Failed” IAW the V&A‐T Plan;

Recommended course(s) of action with respect to each of the failed sub‐tests;

Overall Pass/Fail conclusion;

Any other, as appropriate (data recording and analysis files, printouts, pictures, records).




(R.D22.2) In case of test failure or other issues related to the test results, NSPA will have fifteen (15) calendar days to provide comments. In the absence of comments in this period, the Certificate of Completion and the Test Report will be deemed accepted.

(R.D22.3) In case of test failure or NSPA raised issues with respect to test results, the Contractor and NSPA will agree on appropriate corrective/recovery actions. The Contractor shall be responsible to put in place all the actions agreed (including the Modkit retrofit if necessary) to be compliant with the required performance at no additional cost for NSPA. After implementation of the corrective actions agreed and repetition of the corresponding tests, the Contractor shall submit a new SAT Report to NSPA.

7.6. Reliability Test (RT)

(D23) Upon confirmation of successful SAT, the Contractor and NSPA shall agree on the exact date of commencement of the Reliability Test (RT) periods.

(R.D23.1) The observation period and failure tolerances shall be such that the probability of acceptance in case of the system not meeting the reliability requirements is less than 20%.

(R.D23.2) The duration of the RT for the radar site shall be such that reliability testing finishes simultaneously in all 3 sites.

(R.D23.3) During the RT period, NSPA shall report to the Contractor all relevant events regarding the Reliability Test in accordance with the V&A‐T Plan. The Contractor shall either acknowledge that the event is to be considered as a failure to be counted in the RT, or provide rationale for rejecting the event as related to the RT.

(R.D23.4) In the event of failure of the Reliability Test, and after implementation of the corrective actions, a new monitoring period will be observed.

(D24) Within 2 weeks of the completion of the Reliability Test period, the Contractor shall submit to NSPA the Reliability Test Report including an analysis comparing the results achieved with the requirements specified in Section 6.

8. VERIFICATION AND ACCEPTANCE

(D25) The Contractor shall conduct a verification program reflected in the V&A‐T Plan (see also Section 8.1) with the ultimate objective to demonstrate to the satisfaction of NSPA that all requirements in this SoW have been met, as well as intermediate objectives to ensure that the different stages of technical maturity of the developed HW and SW are achieved.

(D26) The Contractor shall grant NSPA representatives unrestricted access to all testing activities in the V&A‐T Plan and to the resulting data collected.

8.1. Verification and Acceptance Test (V&A‐T) Plan

(D27) Not later than 8 weeks prior to the commencement of the first Factory Acceptance Test the Contractor shall deliver the final Verification and Acceptance Test (V&A‐T) Plan to NSPA for approval. Within 2 weeks of reception of the V&A‐T Plan, NSPA shall approve the Plan or provide motivated requirements for change or clarification. The Contractor shall




either (a) accept and implement NSPA change requirements or (b) propose an alternative. The V&A‐T will have as ultimate objective to demonstrate that the technical requirements in Section 6 have been achieved.

NSPA will reject proposals for the V&A‐T Plan that do not appropriately address the verification of all requirements in this SoW.

(R.D27.1) The Contractor shall propose a V&A‐T Plan which comprises as a minimum the following major formal verification activities:

a. Factory Acceptance Test (FAT) This test shall have the objective to ensure that the developed/purchased HW and SW will respond as expected when integrated into the radar system and thus the design is mature for implementation in the field. It shall be conducted by the Contractor at his facility on all prototype HW and SW (normally using a radar emulator). Prototype HW and SW having successfully passed FAT will become 1st production units. The Contractor may propose FAT in several phases to deal with independent and integrated testing of different modification kits, but there shall be at least one FAT phase testing the complete solution.

b. Site Acceptance Test (SAT): Shall be conducted by the Contractor on operational systems following all installations to demonstrate that the full scope of Technical Requirements stated in Section 6 have been met, including all radar performance characteristics.

For the 2nd CRC SAT the Contractor shall develop a verification program sub‐set, not including the TR associated with the SW design, unless additional changes were applied after the first production units SAT.

The Contractor shall conduct SAT in the presence of NSPA and Host Nation (HN) representatives, who will countersign the SAT Test Reports.

c. Reliability Test (RT): Shall be conducted following successful SAT at each site under

the conditions in the agreed V&A‐T Plan. The RT shall have the objective to

demonstrate that the system is reliable and stable.

d. Validation and Verification of Documentation: Shall be conducted by NSPA on all

documentation provided as part of the contract (see section 9.1). The planning for

validation of documentation may include partial documentation deliveries.

(R.D27.2) The Contractor shall propose for the verification of each of the requirements in this SoW the most efficient method (analysis, test, demonstration or inspection) providing adequate confidence.

(R.D27.3) The V&A‐T Plan shall include a Verification Requirements Traceability Matrix, depicting for each requirement the formal verification stage(s) in which it will be verified and the verification methodology (analysis, inspection, demonstration or test)

(R.D27.4) The V&A‐T Plan shall include for all testing and verification activities at least the following:

List of proposed sub‐tests and requirements verified;

Detailed description of the test procedures for each sub‐test;




Test equipment or any requirement for NSPA or Host Nation furnished property, information, or manpower support;

Pass/fail criteria and tolerances, where applicable;

Reference documents and standards.

(R.D27.5) The Contractor shall propose for the verification of each of the requirements in this SoW the most efficient method (analysis, test, demonstration or inspection) providing adequate confidence.

(R.D27.6) The Contractor shall ensure that verification approach and procedures consider any site specific factor that may affect implementation and compliance of the solution developed under this contract.

8.2. Acceptance Milestones

There shall be three major acceptance milestones: (1) Factory Acceptance of the Integrated Prototype Solution, (2) Provisional Site Acceptance (PSA) for Radar and CRC sites, and (3) Final Acceptance.

8.2.1. Factory Acceptance of the Integrated Prototype Solution (FAT)

Acceptance of the Integrated Prototype Solution is the act whereby NSPA formally

acknowledges that the integrated solution as design and built is mature for implementation

in the field.

This milestone will be achieved upon successful completion of FAT for the complete

integrated solution. Subsequently, NSPA will issue a notification to the Contractor

containing confirmation of Acceptance of the Integrated Prototype Solution.

8.2.2. Provisional Site Acceptance (PSA)

PSA is the act whereby NSPA will formally acknowledge for each installation that the

technical requirements for the system and requirements for the logistics deliverables have

been achieved, though there may be minor discrepancies, which the Contractor shall

commit to resolve to achieve FA.

PSA will be achieved for each installation upon successful completion of the SAT, a minimum

of 3 months of successful RT and acceptance of logistics deliverables.

PSA for each site may be achieved with minor discrepancies, after approval by NSPA of a

Discrepancies Clearance Plan (DCP), which implementation schedule shall be incorporated in

the Master Schedule.

Once all conditions for PSA have been achieved, NSPA will issue a PSA Protocol, to be

countersigned by the Contractor, containing confirmation of PSA for the specific site. NSPA

may require to convene a meeting with the Contractor to complete each PSA Protocol.




After PSA, the Contractor shall keep NSPA informed of the progress on the implementation

of the DCP.

8.2.3. Final Acceptance: (FA)

FA is the act whereby NSPA will definitively accept all delivered products and services in this

SoW, for all sites, as complying with the contractual requirements, determining the start of

the warranty period for all sites and INCO Spares.

FA will be achieved for the complete scope of this contract once PSA of the last site is

achieved, the observations/discrepanies from PSA for all sites are cleared, Reliability Tests

are successful for all sites and INCO spares and all logistics products are delivered.

Once all conditions for FA have been achieved, NSPA will issue a Final Acceptance

Certificate.

9. LOGISTIC SUPPORT DELIVERABLES

9.1. Documentation

(D28) The contractor shall analyze the TMEs included in Annex 3 that are affected by this upgrade.

(D29) Technical Manual Updates (in preliminary version) shall be made available in paper copies by the Contractor to support the Operation and Maintenance (O&M) training courses (1 per each student) 4 weeks prior to training starting date.

(D30) Final Technical Manual Updates that incorporate the MARTELLO S723 Shelter Restoration Mod kits into the standard MARTELLO S723 Radar baseline manuals shall be supplied by the Contractor 4 weeks after the completion of the training program.

(R.D30.1) NSPA will conduct documentation validation activities concurrently with the installation periods or upon receipt of documentation deliverables, and will notify the Contractor of any discrepancies identified. The Contractor shall rectify all recognized documentation discrepancies in order to achieve Final Acceptance (See Section 8).

(R.D30.2) Documentation updates shall be provided only for the pages that have been changed (Change Pages) from the original versions and shall provide organizational/intermediate operations and maintenance instructions for the Radar System after incorporation of the MARTELLO S723 Shelter Restoration Modkit. Where applicable, new manuals shall be provided.

(R.D30.3) The updates shall be provided in a non‐proprietary2 editable electronic format (i.e. editable pdf for text/tables and SVG for schematics or drawings).

2 For the purpose of this requirement, MS Word is accepted as a non‐proprietary format.




(R.D30.4) For COTS equipment, existing operation and maintenance manuals presented in the manufacturer's format shall be supplied. Appropriate references to these OEM manuals will be made, as required, in the applicable system Technical Manuals.

(R.D30.5) All manuals shall be written in English language.

(D31) Within 4 weeks from the First Kit Installation date, the Contractor shall deliver to NSPA the update to the System Specification and System Interface Control Documentation (ICD) under the new configuration.

(R.D31.1) The ICD shall include all interfaces of the “Radar Head Solution”, both to the rest of the radar system and the ROC.

(D32) After SAT for each installation, the Contractor shall deliver all Software installed during the implementation of the upgrade (including COTS Software) on CD/DVD‐ROM support: 1 copy for NSPA, 1 copy for the Danish Air Force, 1 copy per site where the software is installed.

9.2. Configuration

(D33) As part of CDR, the Contractor shall provide the configuration identification data in the form of a hierarchical tree representation of the ModKits up to component level listing:

ModKits’ P/N;

ModKits’ main subassembly P/N;

ModKits’ LRU P/N.

9.3. Training

(D34) The Contractor shall prepare a Training Plan and shall submit it to NSPA (Contractor Format) at least three (3) months before the scheduled training start date. Within four (4) weeks of reception NSPA shall provide any written feedback.

(R.D34.1) The Training Plan shall provide the definition of all specific training implementation elements to meet the training requirements below (R.D34.x). In particular, the Training Plan shall contain at least the following:

Duration proposed for the operators and maintainers course, such that the training objectives are met;

Outline of the operators and maintainers course (training syllabus) and class plan;

Description and methodology of planned induced failures;

Recommended class schedule and starting date;

RADAR downtime schedule;

Location of training (for operators course);

List of training devices/aids/equipment required to support each course (if any);

List of test equipment and tools required (if any);

List of documentation required for the course (i.e. Technical manuals and other related technical data, specific training documentation to be provided by the contractor);




(D35) Upon completion of the SAT activities on the site(s), the Contractor shall deliver training to designated personnel according to the Training Plan.

(R.D35.1) Two types of training courses shall be provided:

Site Maintenance Training course – to site radar technicians and maintenance personnel;

Operators’ Training course – to operators from the Radar and CRC sites.

(R.D35.2) The Site Maintenance Training course shall be performed at the radar site. It shall provide an overview of the new hardware/software configuration of the upgraded radar system and the necessary knowledge for the operation and maintenance at site level (HL1 and HL2). This training will provide classroom and hands‐on equipment training of operation, maintenance procedures, fault isolation and repairs to the upgraded equipment (through induced faults). The duration of the course shall be a maximum of 10 working days.

(R.D35.3) The training course documentation will be provided in accordance with the requirements listed at Paragraph 9.1

(R.D35.4) The Operator’s Training course shall be performed at one of the CRC sites, to be defined in accordance with the installation sequence. It shall provide an overview of the new hardware/software configuration of the upgraded radar system and the RCDSS. This training will provide classroom and hands‐on equipment training on the RCDSS. The duration of the course shall be a maximum of 5 working days.

(R.D35.5) The maximum number of students to be trained in each course is six (6).

(R.D35.6) Training shall be conducted based on a 5‐day week and 8‐hour day, including periodic breaks and lunch breaks.

(R.D35.7) In the event that the Upgraded portion of the Radar System fails during the training period, the course(s) shall be continued at such time as the repair or replacement is completed and at such time the course(s) shall be resumed for the period of time that was remaining in the course at the time of failure.

(R.D35.8) All Host Nation and Contractor holidays will be considered in the determination of the training schedule.

(R.D35.9) The Upgrade Training shall be designed for students who have a basic understanding and familiarity with the current MARTELLO S723 Radar System.

(R.D35.10) All courses shall be taught in English language. Students will be assumed to possess sufficient English language skills.

(R.D35.11) At the completion of each Training Course the Contractor and the Training Senior Attendee shall sign a “Training Completion Certificate” certifying the training course completion in accordance with the requirements of this SoW. The Contractor shall also provide each trainee with a Certificate of Training Completion.

NSPA and the Host Nation shall be responsible for the provision of the following in‐country:

A classroom facility on site to enable the proper instruction; the Training Plan shall provide details of those facilities and equipment necessary for training;

Office space for the Contractor’s Instructors, including a desk and phone;




An operational Radar System for the duration of the training period.

The Host Nation shall provide the appropriate radar downtime for the Upgraded System in order to support the training activities, in accordance with the Master Schedule (see (D2)).

9.4. Spare Parts

9.4.1. Installation & Check Out (INCO) Spares

(D36) The Martello Electronic Shelter Restoration specified in this SoW shall be considered as spares inclusive service. The contractor shall therefore be responsible for defining and then providing a set of spares to be used during all phases of production, installation and testing to ensure immediate replacement of failed parts. These spares shall be known as Installation & Check Out (INCO) Spares.

(R.D36.1) The INCO spares will be procured by NSPA under this SoW and retained by the contractor during the execution of the contract.

(R.D36.2) The shipment of the INCO spares to the customer sites to be used during installation and testing activities shall be performed by the contractor together with the modification kits.

(R.D36.3) The contractor shall return the full set of INCO spares to NSPA in a serviceable condition before the Final Acceptance3.

(R.D36.4) The contractor shall provide a list of INCO spares to NSPA.

9.4.2. Reliability and Provisioning Data

(D37) As part of CDR (see D9) the Contractor shall deliver a Recommended Spare Parts Lists (RSPL).

(R.D37.1) The RSPL will contain the proposed spares required to support the upgraded system for a period of 2 years with 90% confidence. Those items to be part of the INCO Spares as defined in 9.4.1 will be identified as such within the RSPL.

(R.D37.2) The RSPL shall identify critical LRUs (i.e. equipment at the LRU level, which failure renders the system non‐operational).

(R.D37.3) Part in the RSPL shall be identified by manufacturer part number and cage code. If existing, alternative part numbers, alternative cage codes and NATO Stock Numbers shall also be included.

(D38) As part of CDR (see D9) the Contractor shall deliver a Reliability Data List (RDL) containing MTBCF data for all hardware LRUs in the new system configuration and the associated equipment susceptible of being replaced at organizational level.

3 Items to be returned to NSPA as part of the INCO Spares Set, which are being repaired under warranty will be returned upon completion of repair and will not be a reason for NSPA to not issue a notification to the Contractor with the confirmation of Final Acceptance.




(R.D38.1) Part in the RDL shall be identified by manufacturer part number and cage code. If existing, alternative part numbers, alternative cage codes and NATO Stock Numbers shall also be included.

(R.D38.2) Both RDL and RSPL shall be delivered in an editable electronic format (e.g. MS Excel).

10. QUALITY ASSURANCE

(R.Q1) The Contractor shall conduct quality management activities in this project in accordance with an internationally recognized standard for quality management systems (e.g. AQAP 2110, ISO 9001, AS9100).

11. OPTIONS (EVALUATED)

The following requirements reflect optional technical scope. If the options are exercised, they shall be considered as technical requirements under Section 6 of the SoW and all service and data deliverables defined in Sections 5, 7, 8, 9 and 10 shall be applicable to these requirement.

(O.T1) For integration into the ACCS Network (see 6.3.4), the radar system shall support the

following AWCIES (ACCS‐Wide Communication Information Exchange Standard)/Mil‐

ASTERIX message categories compliant with ADatP‐35 Ed. 2 (NATO STANAG 5535 Ed. 2).

‐ 155 – Sensor Monitoring;

‐ 156 – Radar Control;

‐ 157 – Service Data;

‐ 158 – Strobe Report;

‐ 159 – Target Report;

‐ 180 – Sensor Track.

(R.OT1.1) The contractor shall implement in the ACCS interface (6.3.3) all RDS control and

monitoring functions admissible by the Mil‐ASTERIX Data Item Catalogue.

(O.T2) The contractor shall integrate an IFF Interrogator compliant with NATO STANAG

4193 Ed. 3 with the aim of extending the system capability to IFF Mode 5, Level 1 and Level

2.

(R.OT2.1) The RCDSS and RDS shall include the necessary functionality to perform all control

and monitoring messages enabling Mode 5 Level 1 and Level 2 operations.

(R.OT2.2) The ACCS Network Interface shall include all Mode 5 control and monitoring

messages defined in ADatP‐35 Ed 2.




APPENDIX 1: SUMMARY OF DELIVERABLE DATA, PRODUCTS AND SERVICES

The Table below lists the deliverable products and services under this contract. It is provided as a quick reference for convenience.

In case of any inconsistency between this table and the Text in the SoW document body, the text in the document body shall prevail.

Serial Deliverable Type When

D1 Nominate a Project Manager (PM)

Service Contract Award

D2 Master Schedule Data First Delivery with Proposal

4 weeks after Contract Award

D3 Contractor Staff Personal Data + Sec Clearance

Data 90 days before site installations

D4 Risk Updates Data When required

D5 Attend Ad‐Hoc PMR/TIM Service When required

D6 SP/Exc Design Service Per Contractor Schedule (Complete by CDR)

D7 SRR Service 4 weeks after CA

D8 SRR Meeting Record Data 1 week after SRR

D9 CDR Service Per Master Schedule

D10 CDR Information Package Data 4 Weeks ahead of CDR

D11 CDR meeting record Data 1 week after CDR

D12 Production Service Per Contractor Schedule

D13 FAT & FAT Report & FAT CoC Service /

Data

Per Master Schedule (upon completion of production for each kit)

‐ Notify 30 days ahead ‐ FAT Report & CoC within 2 weeks of FAT

D14

D15 Packaging, Delivery and Installation (Modkits, T&TE)

Service/

Material After completion of FAT

D16 Baseline Assessment Service /

Data Per Master Schedule (With legacy configuration)

D17 Remove and/or disconnect legay HW&SW

Service Per Master Schedule (Before installation)

D18 Installation of Mod kits Service Per Master Schedule

D19 Ensure Pre‐BA Radar Performance

Service Per Master Schedule

D20 SAT Service Per Master Schedule

D21 SAT Test Report Data 1 week after completion of SAT

D22 Reliability Test (RT) Service Per Master Schedule

D23 Reliability Test Report Data 2 Weeks after completed RT

D24, D25

Conduct of V&AT Programme Service V&AT activities as per master schedule

D26 V&A‐T Plan Data SRR (v1), CDR (v2)




8 weeks before 1st FAT (Final)

D27 Analysis of documentation changes

Data 4 weeks ahead of CDR (Part of CDR Information Package)

D28,

D29 Technical Manual Updates Data

‐ 4 weeks ahead of Training start (prelim) ‐ 4 weeks after Training completion (final)

D30 System Spec and ICD Data 4 weeks after first site installation

D31 SW delivery Data After SAT

D32 Configuration Tree Data 4 weeks ahead of CDR (Part of CDR Information Package)

D33 Training Plan Data 3 months before Training start

D34 Training Services Start following SAT and as per Master Schedule

D35 INCO Spares Material At the start of first installation

D36 RSPL Data 4 weeks ahead of CDR (Part of CDR Information Package)

D37 RDL Data 4 weeks ahead of CDR (Part of CDR Information Package)

Note A1: All the deliverables that require delivery of certain documents are noted in the column “Type” with mentioning “Data”.

Note A2: Whilst timing for some of the intermediate milestones is not specified in this SoW, the Master Schedule shall be such that FA is achieved not later than 18 months after Contract Award.




APPENDIX 2: ENVIRONMENTAL REQUIREMENTS WITHIN THE DISPLAY SHELTER

These specifications are based on standards and Allied Environmental Conditions and Test

Publication (AECTP), which are accepted and approved by NATO. If there are contradictions

in terms of the requirements listed below and requirements stated in STANAG 4370, the

specification below supersedes.

They are applicable for the equipment installed WITHIN the Display Shelter.

Temperature and Humidity

Requirement

MinInside/Outside

Typ.

Max

Unit

Notes

TemperatureOperatingWITHINtheDisplayShelter

0° +20° +40° Celsius

TemperatureNon‐OperatingWITHINtheDisplayShelter

10° N/A 65°

HumidityOperating 40% 55% 80% Condensationmust

notbeallowedtodHumidityOperating

forGPSSystemClockAntennasystem

5% 55% 90% Withpossiblecondensation

AirSaltContent 0.75 (1)* Micro‐grams/m3

*forGPSSystemClockAntennasystem(gram/m3)

AirOzonContent 220 (1)* Micro‐grams/m3

*forGPSSystemClockAntennasystem(gram/m3)

HumidityNon‐Operating 95% Noncondensingwhenpacked

AtmosphericPressure 500 1050 mb

AltitudeOperating

10,000 Feet

AltitudeNon‐Operating

40,000 FeetDuringairbornetransport

Table 4 ‐ Standards Environmental Conditions ‐ Temperature and Humidity

Shock and Vibration (Operating)

The assembly shall be designed to withstand:

Shock: Half sine shock pulse 6 G peak (±1 G) for 10 ms (±3 ms), applied once in all three axis.




Vibration test as indicated here below:

1.5 G (± 6 mm max displacement)

5 to 22 Hz, 0.010 in Double Amplitude

22 ‐ 500 Hz, 0.025 peak

500 ‐ 22 Hz, 0.025 peak

22 to 5 Hz, 0.010 in Double Amplitude

Shock and Vibration (Not Operating)

The assembly shall be designed to withstand

Shock: MIL‐STD‐810C1, Method 516.2, Procedure 1, Figure 516.2‐2.

Half sine shock

Pulse for ground equipment, 30 g peak, 11 ms duration.

Vibration test as below indicated:

MIL‐STD‐810C, Method 514.2, Category G (equipment transported as cargo), Procedure X,

table 514.2‐VII (rail, air, semi‐trailer), Figure 514.2‐7, Curve AA is to be used for vibration

isolated items

These requirements will be demonstrated by analysis of operating characteristics of the

used equipment during the FAT.

EMI Radiation Emitted

There are no EMI related specific requirements, which have to be applied in new equipment

of the MARTELLO S723 radar, but the EMI/RFI emanating from the new equipment shall not

cause any trouble to the other electronic circuits of the radar systems.

However a Lightning protection system is required, for which the STANAG 4236 and STANAG

4327 shall be applied.




APPENDIX 3: ABBREVIATIONS AND ACRONYMS

ADatP Allied Data Publication

ADS‐B Automatic Dependent Surveillance – Broadcast

AQAP Allied Quality Assurance Publication

ASTERIX All‐purpose Structured EUROCONTROL Radar Information Exchange

AWCIES ACCS‐Wide Communication Information Exchange Standard

BA Baseline Assessment

CFP Customer Furnished Property

CNIF Clutter to Noise Improvement Factor

COTS commercial off‐the‐shelf

CRC Control and Reporting Centre

DP Data Processor

EC Exercise Controller

EUROCONTROL European Organization for the Safety of Air Navigation

FA Final Acceptance

FAT Factory Acceptance Test

FT Factory Test

HL Hardware Level (maintenance)

HMI Human Machine Interface

HW Hardware

I&CO (or INCO) Installation and Check‐Out

IAW In Accordance With

ICD Interface Control Document

IF Improvement Factor or Intermediate frequency (clear through context)

IFF Identification Friend or Foe

ITU International Telecommunications Union

LRU Line Replaceable Unit

MFI Monitoring and Fault Isolation

Modkit Modification kit

MSSR Mono pulse Secondary Surveillance Radar

MTBCF Mean Time between Critical Failures

MTBF Mean Time between Failures

NATO North Atlantic Treaty Organization

NDI Non Developmental Item

NLT Not Later Than

NRP North Reference Pulse

NSPA NATO Support and Procurement Agency

O&M Operation and Maintenance

ODAS Offline Detection Analysis Software

OEM Original Equipment Manufacturer

P/N Part Number

PDF Portable Document Format

PMFL Performance Monitoring and Fault Isolation




PMR/TIM Program Management Review / Technical Interchange Meeting

PRF Pulse Repetition Frequency

PSA Provisional Site Acceptance

PSR Primary Surveillance Radar

RADNET Radar Network

RCDSS Radar Control and Display Sub‐System

RDS Remote Display System

RES Radar Environment Simulator

RF Radio Frequency

RP Remote Processor

R‐SPC Radar – System Performance Check

RSPL Recommended Spare Parts List

S/N Serial Number

SAT Site Acceptance Test

SGS Scenario Generator Software

SLB Sidelobe Lobe Blanking

SoW Statement of Work

SPT&A System Performance Test and Alignment

SSR Secondary Surveillance Radar

STANAG Standardization Agreement

STC Sensitivity Time Control

SW Software

TIM Technical Interchange Meeting

TME Technical Manual Equipment

TMs Technical Manuals

UDP/IP User Datagram Protocol/Internet Protocol

UPS Uninterruptible Power Supply

V&A‐T Verification and Acceptance Test (Plan)

Documents

STATEMENT OF WORK AND TECHNICAL ... - eportal.nspa.nato.int · The following is a non‐exhaustive list of documents which, in their most current version/revision, are relevant in