Technical Specification 1.0

8/11/2019 Technical Specification 1.0

1/82


2/82


3/82

SWEDISH DEFENCE MATERIEL ADMINISTRATION SPECIFICATION: xWDM

C3I Systems Procurement Command, Network Office 10FMV2552-2:1

SE-115 88 STOCKHOLM, SWEDEN Date: 2010-04-26

7 AVAILABILITY, PERFORMANCE AND MAINTENANCE 387.1 General................................................................................................................... 38

7.2 Logistic Support Analysis (LSA) .......................................................................... 38

7.3 Life expectancy and operating profile ................................................................... 38

7.4 Maintenance system design ................................................................................... 39

7.5 Test, alarms and supervisory functions.................................................................. 39

7.6 Availability performance requirements ................................................................. 39

7.7 Evaluation of availability performance, maintenance and LSC ............................ 397.8 Spare parts.............................................................................................................. 41

7.9 Technical support................................................................................................... 42

7.10 Repair service ........................................................................................................ 42

7.11 Software support .................................................................................................... 42

7.12 Tenderers Maintenance system ............................................................................ 42

8 DOCUMENTATION 43

8.1 General................................................................................................................... 43

8.2 Types of documentation......................................................................................... 438.3 Manuals.................................................................................................................. 44

8.4 Basis for Registration of Necessities ..................................................................... 45

9 INSTALLATION AND COMMISSIONING 46

9.1 Security approval ................................................................................................... 46

10 TRAINING 47

10.1 General................................................................................................................... 47

10.2 System Overview Course....................................................................................... 48

10.3 Technical Maintenance Course.............................................................................. 48

10.4 Technical Operation and Management Course...................................................... 49

10.5 System Course, FAT.............................................................................................. 50

10.6 Network planning course ....................................................................................... 50

11 QUALITY ASSURANCE 52

11.1 General................................................................................................................... 52

11.2 Requirements on the Contractor's general quality assurance................................. 52

11.3 Requirements on the Contractor's quality plan...................................................... 5211.4 First Article Test .................................................................................................... 53

11.5 Delivery Inspection................................................................................................ 55

11.6 Delivery ................................................................................................................. 55

12 PROJECT MANAGEMENT 58

12.1 General................................................................................................................... 58


4/82




1 SYSTEM OVERVIEW

1.1 Introduction1.1.1 The Swedish Defence Materiel Administration will purchase a Wavelength

Division Multiplex System (xWDM), preferably COTS equipment (Commercial

Of The Shelf), to be used in the fixed Swedish Defence Telecommunication

Network (FTN).

1.1.2 The xWDM System asked for in this specification shall be capable of bridging a

variety of fibre lengths in Long Haul, Regional as well as in Metro applications.

Optical amplifiers may be used when required.

1.1.3 The xWDM System shall be able to handle CWDM as well as DWDM. The

required initial number of wavelengths is only few and must be possible to expand

when needed without affecting the traffic.

1.2 Swedish Defence Telecommunication Network1.2.1 The Swedish Defence Telecommunication Network is a nation-wide fixed

network built for the joint Armed Forces telecommunication services.

1.2.2 The network structure is mesh-shaped and the transmission is based on fibre optic

cables and microwave radio relay equipment. Transmission resources may be

equipped with bulk encryption devices (not part of this purchase).

1.2.3 Network sites are of various designs. In all types of sites, the indoor equipment isinstalled in shelters that have controlled environment. The network sites are

operated unmanned. The network operation profile is 24 hours a day all days.

1.2.4 The network operation organization consists of two network operation centres

during office hours. During non-office hours, national network operation is

carried out from anyone of these.

1.2.5 The on-site maintenance is managed by the operation centres. Field technicians

carry out the field maintenance. The maintenance consists mainly of restoringfunctions by replacing malfunctioning Line Replaceable Units (lru).

1.3 Nomenclature1.3.1 The Swedish Defence Materiel Administration is hereafter referred to as FMV.

1 3 2 Th f l T d i h ft f d t th C t t


5/82




1.4 Response1.4.1 The response to this specification shall be provided in a word document, with

reference to the related paragraphs stated in this document. The answers shall be

clearly identified and shall be written after the corresponding questions.

1.4.2 The Tenderer shall identify every answer in accordance with the levels of

compliance provided in Table 1.

Table 1. Levels of Compliance

Nomenclature Meaning

Understood The Tenderer shall respond with Understood to

paragraphs that are provided for information purposes,

meaning that the Tenderer understands and accepts the

information so marked. This response is used only in

respect of paragraphs that are clearly providing

information to the Tenderer and that cannot reasonablybe considered to constitute a requirement.

Compliant The Tenderer shall answer with Compliant when the

required functionality is supported by the system release

that is available at the moment of answering this

proposal.

Partially Compliant The Tenderer shall answer with Partially Compliant

when the required functionality is partially supported bythe system release that is available at the moment of

answering this proposal.

The Tenderer shall clearly describe the level of

compliance and if the system shall be fully compliant in

a future release.

Alternative solutions may also be offered.

Will Comply The Tenderer shall answer with Will Comply when the

required functionality is not compliant at the current

time, but will be fully compliant at a later date.

The Tenderer shall provide date and release of future

li


6/82




1.4.3 Additional information shall be provided after the level of compliance and inannexed documents.

1.4.4 All information included in this document shall be handled confidentially.

1.5 References

1.5.1 Swedish, European or other well established international standards must be used

where applicable.

Examples on utilized standard bodies:

MIL-STD US Defence Standard

DEF-STAN Brittish Defence Standard

ETSI European Telecommunications Standards Institute

FSD Swedish Defence Standards (http://www.fsd-online.se)

IEC International Electrotechnical Commission

ISO International Organization for Standardization

ITU International Telecommunication Union

ITU-T ITU Telecommunication recommendations

MIL-HDBK US Military Handbook

1.5.2 The Tenderer shall specify all standards and recommendations used including the

date of issue or revision.

1.5.3 The Tenderer shall in detail comment paragraphs in applicable standards and

recommendation that:

The Tenderer does not comply to

Are optional

Have options

Have values to be given Have paragraphs under study (e g the Tenderers solution/value shall be

given)

Have other deviations


7/82




2 TECHNICAL REQUIREMENTS

2.1 General2.1.1 This document specifies a Wavelength Division Multiplex System (xWDM) that

shall be used in the fixed Swedish Defence Telecommunication Network (FTN).

Commercial of the Shelf (COTS) equipment is preferred.

2.1.2 The xWDM System will be mounted in fixed sites with controlled environment as

per chapter 5.

2.2 Wavelength Division Multiplex System Definition2.2.1 The xWDM System will be regarded and referred to as a system including all

parts and components necessary for a complete operative system.

2.2.2 Fibres and optical distribution frames are not part of this purchase.

2.3 Composition2.3.1 Depending on the network requirements, the xWDM System shall be able to

handle CWDM and DWDM and shall be flexible and scalable with regards to

interfaces, capacity and fibre lengths.

2.3.2 The xWDM System shall be used with a variety of fibre lengths in Long Haul,

Regional as well as in Metro applications. Optical amplifiers may be used when

required.

2.3.3 The xWDM system shall support OTM (Optical Terminal Multiplexer) as well as

OADM (Optical Add Drop Multiplexer) configurations.

2.3.4 The offer may consist of different equipment types; however a common platform

and a common management system shall be used.

2.3.5 In case of different equipment types a common set of spare units is preferred.

2.3.6 The Tenderer shall thoroughly state the equipment composition for CWDM,

DWDM and hybrid CWDM and DWDM use in OTM and OADM configurations.

2.4 References2.4.1 The xWDM System shall conform to the following standards and

recommendations. The Tenderer shall separately state deviations, if any, in

i ith th l t bli ti


8/82




ITU-T rec. G.694.2 Spectral grids for WDM applications: CWDM frequencygrid.

ITU-T rec. G.695 Optical interfaces for coarse wavelength division

multiplexing applications.

ITU-T rec. G.697 Optical monitoring for DWDM systems.

ITU-T rec. G.698.1 Amplified multichannel DWDM applications with single

channel optical interface.ITU-T rec. G.698.2 Amplified multichannel DWDM applications with single

channel optical interfaces.

ITU-T rec. G.703 Physical/electrical interfaces of hierarchical digital

interfaces.

ITU-T rec. G.707 Network node interface for the synchronous digital

hierarchy (SDH).ITU-T rec. G.709 Interfaces for the Optical Transport Network (OTN).

ITU-T rec. G.774 Synchronous digital hierarch (SDH) Management of

transmission systems.

ITU-T rec. G.872 Architecture of optical transport networks.

ITU-T rec. G.874 Management aspects of the optical transport network

element.ITU-T rec. G.957 Optical interfaces for equipments and systems related to

the synchronous digital hierarchy.

ITU-T rec. G.983 series PON.

ITU-T rec. G.984 series G-PON.

ITU-T rec. M.3010 Principles for a telecommunications management network.

IEEE 802.3 series Ethernet, Fast Ethernet, 1GB Ethernet, 10GB Ethernet.

ANSI X3.230 Fibre Channel, Physical and Signalling Interface (Fc-Ph).

ETSI EN300 132-2 Environmental Engineering (EE); Power supply interface

at the input to telecommunications equipment; Part 2:

Operated by direct current (DC)


9/82




telecommunications equipment; Part 1-3: Classification ofenvironmental conditions; Stationary use at

weatherprotected locations.

ETSI EN 300 386 Electromagnetic compatibility and Radio spectrum

Matters (ERM); Telecommunication network equipment;

ElectroMagnetic Compatibility (EMC) requirements.

EN 60950-1 Information technology equipment. Safety. General

requirements.

EN 41003 Particular safety requirements for equipment to be

connected to telecommunications networks.

ISO 14001:2004 Environmental management systems - Requirements with

guidance for use.

ISO 14004:2004 Environmental management systems - General guidelines

on principles, systems and support techniques.

SFS:1998:808 The Swedish laws Miljbalken (The Environmental

Code) and its ordinances.

Directive 2002/95/EC European Parliament and the Council; The restriction of

the use of hazardous substances in electrical and electronic

equipment (RoHS).

Directive 2002/96/EC European Parliament and the Council; waste of electricaland electronic equipment (WEEE).

MIL-HDBK-217F Reliability Prediction of Electronic Equipment, US DoD.

RFC 3411RFC 3418 SNMP V3

RFC 1305 NTP V3 and NTP V4

2.4.2 Deviations and additions that FMV requires are stated in this specification.

2.5 Main requirements

2.5.1 Network topology2.5.1.1 The xWDM System shall be possible to configure in any kind of network

topology for example point-to-point chain ring and meshed networks


10/82




2.5.2 Services2.5.2.1 The xWDM System shall support any mixture of services and data rates without

any restrictions up to the system maximum capacity. The Tenderer shall state the

maximum capacity.

2.5.2.2 The services transported by the xWDM System shall use interfaces according to

chapter 4.

2.5.2.3 The traffic cards must be possible to change without disturbing the services in

another part of the equipment (i.e. hot swappable).

2.5.2.4 The xWDM System shall be able to handle the services according to sections

2.5.2.5to 2.5.2.9.

2.5.2.5 SDH

STM-1

STM-4

STM-16

STM-64

2.5.2.6 OTN (G.709) Optional

OTU-1

OTU-2

2.5.2.7 SAN

Fiber Channel 1G

Fiber Channel 2G

Fiber Channel 4G

Fiber Channel 8 G (optional)

Fiber Channel 10G (optional)

2.5.2.8 LAN and WAN

Fast Ethernet

Gigabit Ethernet

10 GB Ethernet


11/82




2.5.3.3 The grooming function shall support add and drop of services to and from the linesignals (ADM). To be stated.

2.5.4 Transparency2.5.4.1 The xWDM System shall be transparent for any service protocol, and maintain

data integrity.

2.5.4.2 The xWDM system shall be able to handle optical wavelengths that are originated

in any external client systems.

2.5.5 Number of wavelengths2.5.5.1 Initially eight wavelengths are required at each fibre network port. However for

future needs it shall be possible to expand the number of wavelengths to at least

forty in each fibre network port (build as you grow). The estimated expansion

rate is 4 wavelengths per year.

2.5.5.2 The expansion procedure must not disturb the ongoing telecom traffic in another

part of the equipment.

2.5.6 Frequency gridsFrequency grids according the following recommendations shall be used:

2.5.6.1 ITU-T rec. G.694.1 (DWDM frequency grid). The Tenderer shall state how many

wavelengths are supported.

2.5.6.2 ITU-T rec. G.694.2 (CWDM frequency grid). The Tenderer shall state how manywavelengths are supported.

2.5.6.3 The xWDM system shall support hybrid CWDM and DWDM multiplexing.

Number of wavelengths and other details shall be stated by the Tenderer.

2.5.7 Flexibility2.5.7.1 The specific applications at the sites call for various interface requirements at the

different nodes. The capacity need may also change over time. Hence a flexible

and scalable xWDM System is required, that can be adapted by means of insertion

or removal of interface units and insertion and removal of pluggable interfaces.

This procedure must not disturb the ongoing telecom traffic in another part of the

equipment.

2.5.7.2 ROADMs shall be direction less and colour less.


12/82




Maintenance function for example test and loop back, optical powerindications

2.5.9 Management2.5.9.1 Local management of the xWDM System shall be made by means of a local

element manager, for example a PC with application software.

2.5.9.2 Remote management of the xWDM System shall be made by means of a remote

management system from the network operation centres according to chapter 3.

2.5.10 Optical Line Interfaces2.5.10.1 The xWDM System shall be possible to equip with optical line interfaces for short

haul, regional haul as well as long haul. Standard optical fibres according ITU-T

rec. G.652 is mostly used.

2.5.10.2 It shall be possible to change interface type without disturbing the services in

another part of the system (hot swappable). Optical Line Interfaces based onpluggable modules are preferred.

2.5.11 Optical Amplifiers2.5.11.1 For long haul applications the xWDM System shall be possible to equip with

optical amplifiers to compensate for fibre attenuation up to 44 dB. Such amplifiers

shall be offered as an option.

2.5.11.2 It shall be possible to mount optical amplifiers as integrated in the network

elements.

2.5.11.3 Type of amplifiers (e.g. EDFA, RAMAN etc.) and their amplification range shall

be stated.

2.5.12 Dispersion compensation2.5.12.1 Dispersion compensation functions shall be included.

2.5.12.2 It should be possible to mount integrated dispersion compensating modules in the

network elements.

2.5.12.3 FMV prefers dispersion compensation device of FBG type (Fibre Bragg Grating)

for zero latency.

2.5.12.4 The Tenderer shall thoroughly describe the dispersion compensation functions,

f d i d l i d i l d d


13/82




2.5.15 Automatic optical power management2.5.15.1 Function for automatic optical power management and equalization shall be

included in the network elements to automatically compensate power and gain for

capacity change, ageing effects or other changes of the operating conditions.

2.5.15.2 It shall be possible to monitor every provisioned optical channel by for example a

graphical view of the input and output power levels for each wavelength.

2.5.15.3 The Tenderer shall thoroughly describe the automatic optical power management

functions.

2.5.16 Cross connections2.5.16.1 It shall be possible to cross connect optical signals in the xWDM System. The set

up of the cross connections shall be possible locally by means of the element

manager and remotely by the management system.

2.5.16.2 The Tenderer shall thoroughly describe the cross connect function.

2.5.17 Layer 2 switching2.5.17.1 Layer 2 switching should be offered as an option.

2.5.17.2 Layer 2 switching shall be managed by the same management system as the

xWDM System itself.

2.5.17.3 The Tenderer shall thoroughly describe the Layer 2 switching function.

2.5.18 Encryption2.5.18.1 The xWDM system should have optional functions to encrypt the traffic

information.

2.5.18.2 The Tenderer shall thoroughly describe the encryption function (encrypted service

types, encrypted layer, encryption algorithm, key changes, encryption latency etc.)

2.5.19 Protection

2.5.19.1 Functions in the network elements shall be protected by for example duplicatedcards and power supplies. To be described by the Tenderer.

2.5.19.2 Channels for transportation of the services shall be possible to protect. Protection

switching time shall be less than 50 ms. To be described by the Tenderer.

2.5.19.3 At this point of time line protection not considered. However the Tenderer shall


14/82




2.5.20.4 Functions for automatic discovery and provisioning should be included tosimplify future changes of the network, for example new network elements and

change of the network elements configuration.

2.5.20.5 Functions for end-to-end provisioning of services should be included.

2.5.20.6 The xWDM System shall have built in test (BIT) to verify the equipment

functioning before and during the deployment and during the operation.

Malfunctions in the equipment shall be identified and faulty units pinpointed.

2.5.20.7 Alarms and status shall be indicated locally by means of light emitting diodes, an

alphanumeric display or similar device. Alarms shall also be indicated in the

remote equipment.

2.5.20.8 Detailed alarms and status shall be indicated by means of the local element

manager as well as by the management system.

2.5.20.9 The xWDM System should have functions integrated for detection of cut,

degradation and intrusion of the optical fibre. The function shall be thoroughlydescribed by the Tenderer.

2.5.20.10 The xWDM System shall have functions for measuring the attenuation of the

optical lines. The function shall be thoroughly described by the Tenderer.

2.5.20.11 The Tenderer shall thoroughly describe built in test, loop back functions and

alarm and status indications.

2.5.20.12 The xWDM System shall accumulate historic performance information.2.5.20.13 The system should support performance calculations according to ITU-T G.826.

2.5.20.14 Collection periods supported should be n*24 hours and n*15 minutes The

Tenderer shall state the number of performance collection periods.

2.5.20.15 The performance results shall at any time be possible to access locally and

remotely.

2.5.21 Management Channel and Embedded Communication Channel2.5.21.1 The xWDM System shall contain a management channel that is used for the

management of the xWDM System. The management channel function shall be

thoroughly described.

2.5.21.2 The management channel function shall be independent of the other transmission


15/82




Figure 1. Management Channel and ECC Channel

2.5.22 EMC/EMI2.5.22.1 The xWDM System shall be co-located with other types of equipment in the same

shelter; hence it is important that the xWDM System meets all stipulated

EMC/EMI requirements according to chapter 5.

2.6 Type Nodes

2.6.1 General2.6.1.1 In the first deployment phase the xWDM System shall be used in a network with a

topology layout according to Appendix 1. Type Nodes according the sections

2.6.2to 2.6.7shall be used to describe the network. A list of suggested Type

Nodes for each site shall be supplied in the tender.2.6.1.2 To facilitate the installation and commissioning in the first deployment phase, the

nodes shall be pre-commissioned with IP addressed and the relevant path

attenuation. The delivery shall be complete with all necessary cards and patch

cables mounted.


16/82




A medium configuration with the initial number of wavelengths, 16 expandable to 40 and with two cases of fibre attenuation for the xWDM

interfaces.

A maximum configuration with 40 and with two cases of fibre attenuationfor the xWDM interfaces.

A number of interfaces as indicated shall be included.

A grooming function shall be included for just any services.

2.6.1.6 Wavelengths not terminated shall be cross connected between any of the xWDM

interfaces.

2.6.1.7 ROADMs shall be included in type node B to E.


17/82




2.6.2 Type Node A2.6.2.1 The type Node A shall have one xWDM interface. Services shall be terminated in

interfaces. The general configuration shall be as in Figure 2.

2.6.2.2 The Type Node A minimum configuration shall also be offered in a low shelf

that is maximum 3 Height Units (HU).

Figure 2. Type Node A

2.6.2.3 The Type Node A shall have expandable configurations according to Table 2.

Table 2. Type Node A, configuration

Expandable

Configuration

xWDM interface,

No. of ,fibre attenuation, CWDM,

DWDM

Number of Interfaces

Minimum 8 , 15-25 dB, CWDM,

DWDM

4

8 , 30-35 dB, DWDM 4

Medium 16 , 15-25 dB, CWDM,

DWDM

16

16 , 30-35 dB, DWDM 16

Maximum 40 , 15-25 dB, DWDM 40

40 , 30-35 dB, DWDM 40


18/82




2.6.3 Type Node B2.6.3.1 The Type Node B shall have two xWDM interfaces; East and West. Any services

shall be terminated from any xWDM interface. Services not terminated shall be

possible to cross connect between any xWDM interfaces without restrictions. The

general configuration shall be as in Figure 3.

2.6.3.2 The Type Node B minimum configuration shall also be offered in a low shelf

that is maximum 3 Height Units (HU).

Figure 3. Type Node B

2.6.3.3 The Type Node B shall have expandable configurations according to Table 3.

Table 3. Type Node B, configuration

Expandable

Configuration

xWDM interface,

No. of ,

fibre attenuation, CWDM,

DWDM


Minimum 8 , 15-25 dB, CWDM, DWDM 4

8 , 30-35 dB, DWDM 4

Medium 16 , 15-25 dB, CWDM, DWDM 8

16 , 30-35 dB, DWDM 8


19/82




2.6.4 Type Node C2.6.4.1 The Type Node C shall have two xWDM interfaces; East and West. An integrated

Service Grooming Function shall be included. Any services, groomed services

included, shall be terminated from any xWDM interface. Services not terminated

shall be possible to cross connect between any xWDM interfaces without

restrictions. The general configuration shall be as in Figure 4.

xWDM

West

Grooming

Sevice interfaces

xWDM

East

Through

connection

Figure 4. Type Node C

2.6.4.2 The Type Node C shall have expandable configurations according to Table 4.

Table 4. Type Node C, configuration

Expandable

Configuration

xWDM interface,

No. of ,


DWDM


Minimum 8 , 15-25 dB, CWDM, DWDM 2 + 4 groomed services

8 , 30-35 dB, DWDM 2 + 4 groomed services

Medium 16 , 15-25 dB, CWDM,

DWDM

4 +4 groomed services


Maximum 40 , 15-25 dB, DWDM 16 + 8 groomed services



20/82




2.6.5 Type Node D2.6.5.1 The Type Node D shall have four xWDM interfaces; East, West, South and North

An integrated Service Grooming Function shall be included. Any services,

groomed services included, shall be terminated from any xWDM interface.

Services not terminated shall be possible to cross connect between any xWDM

interfaces without restrictions. The general configuration shall be as in Figure 5.

Figure 5. Type Node D

2.6.5.2 The Type Node D shall have expandable configurations according to Table 5.

Table 5. Type Node D, configuration

ExpandableConfiguration

xWDM interface,No. of ,


DWDM




Medium 16 , 15-25 dB, CWDM, DWDM 4 +4 groomed services





21/82




2.6.6 Type Node E2.6.6.1 The Type Node E shall have five xWDM interfaces; East, West, South, North and

Northeast. An integrated Service Grooming Function shall be included. Any

services, groomed services included, shall be terminated from any xWDM

interface. Services not terminated shall be possible to cross connect between any

xWDM interfaces without restrictions. The general configuration shall be as in

Figure 6.

Grooming

Sevice interfaces

Through

connectionxWDM

West

xWDM

South

xWDM

North

xWDM

East

xWDM

Northeast

Figure 6. Type Node E

2.6.6.2 The Type Node E shall have expandable configurations according to Table 6.

Table 6. Type Node E, configuration

Expandable

Configuration

xWDM interface,

No. of ,


DWDM




Medium 16 , 15-25 dB, CWDM, DWDM 8 + 8 groomed services





22/82




2.6.7 Type Node F2.6.7.1 The Type Node F shall connect existing access equipment by means of a Passive

Optical Network (PON), optical filters included. The general configuration of

Type Node F shall be as in Figure 7.

2.6.7.2 It should support CWDM or DWDM and forwarding of individual wavelengths to

the access equipment (the access equipment will be fitted with suitable coloured

interfaces).2.6.7.3 The Tender shall thoroughly describe the function and capabilities, technical data,

management and surveillance included.

Figure 7. Type Node F


23/82




2.6.8 Type Node G2.6.8.1 The Type Node G shall consist of at least two independent Network Elements

according Type Nodes A to F that share the services for redundancy reasons. The

distance between the Network Elements may be up to 10 km (5 dB).

2.6.8.2 The Tender shall thoroughly describe the function and capabilities, technical data,

management and surveillance included.

2.7 Reference System2.7.1 The Tenderer shall offer reference equipment to be used at the FMV Maintenance

Centre Lab. The purpose of the reference system is to be able to perform system

tests with other already existing equipment, testing and evaluation of new

software releases etc.

2.7.2 The reference equipment shall as a minimum contain the following:

Two chassis of the standard type provided in the delivery. In case of additionalchassis types different from the standard type, one of each additional type

shall be provided.

All chassis shall be equipped with basic cards such as power supply cards,control cards for the system as well as local and remote management and other

common cards if any.

Two sets of traffic carrying cards of each type, to be able to performmeasurements from client interface to client interface, short haul optical

interfaces included.

A separate management system for the reference equipment with functionsaccording to Chapter 3, but for a limited number of network elements.


24/82




3 NETWORK MANAGEMENT SYSTEM

3.1 General3.1.1 The management shall be done by means of Network Management System

(NMS).

3.2 Overview

3.2.1 The NMS shall be based on internationally accepted standards for open systemsand management functions.

3.2.2 The tender shall specify which standards the NMS complies with.

3.2.3 The network operation organization includes two geographically separated

network operation centres. During office hours both are used. During non-office

hours, national network operation is carried out from anyone of these.

3.2.4 A redundant NMS solution with two servers and related databases are required.

The general overview of the NMS shall be as indicated in Figure 8.

3.2.5 The necessary communication between the different parts of the NMS and the

Network Elements is accomplished by means of an existing Data Communication

Network (DCN).

3.2.6 It shall be possible to connect the NMS to a Superior Management System. See

Figure 8.

3.2.7 A NMS system for test purposes is required for the transmission test centre. Thelayout and the function shall be equal to the main NMS.


25/82




3.2.8 The NMS shall contain the following quantities:3.2.9 Two main servers with the related databases, placed at geographical separated

locations:

Server I is the main server of the NMS

Server II is used as a hot or warm standby redundancy to Server I

Clients with the related databases for the regional management. It must also bepossible to manage the complete network from just any of the Clients.

3.2.10 Management applications for Network Management and Network Element

management (ref. to ITU-T rec. M.3010):

Fault Management

Configuration Management

Accounting Management (Optional)

Performance Management

Security Management

3.3 Capacity3.3.1 Initially the NMS shall have the capacity to manage minimum 100 network

elements and 5 clients used simultaneously.

3.3.2 The Tenderer shall as an option offer an upgrade to 200 network elements and 10

clients used simultaneously. The upgrade procedure shall be described.

3.3.3 The network is military, and it must be operable in a war situation. This implies,

specifically, that the management system shall not be choked when large parts of

the network reports failure events. Also the routing and restoration algorithms

must be designed for this situation.

3.4 DCN Transmission Capacity3.4.1 The Tenderer shall state the minimum DCN transmission capacity needed for the

necessary communication between:

Server I and Server II

The different servers and the databases

The different servers and the network elements

The different servers and the clients


26/82




Communication protocols Man Machine Interface

3.5.1.2 The Tender shall include a graphical description of the NMS and all relevant

system components.

3.5.1.3 The Tenderer shall specify the relation between the OS, the applications, the

databases and additional requirements such as mandatory software (for example

MSExcel etc).

3.5.2 Management System Platform, Hardware3.5.2.1 This system component shall include computer hardware for servers that are

available as standard products on the market. HP ProLiant DL380 G5 is preferred.

3.5.2.2 Client system hardware technical requirements shall be stated by the Tenderer.

3.5.2.3 As en option the Tenderer shall offer Client system hardware.

3.5.3 Management System Platform, Software (OS) and general IT Security3.5.3.1 This system component includes what is traditionally considered to be included in

an operating system, such as CPU-sharing, process-handling, inter process

communication (internally), memory management, file management, I/O

handling, user authentication, resource/information access control, etc.

3.5.3.2 The operating system used for the servers shall be described by the Tenderer and

the Security Templates possibilities (Security Hardening) shall be thoroughly

described. An MS Windows Server 2003 based platform is preferred due to IT

Security reasons.

3.5.3.3 The server should include a tool for control, monitor and management of the

server (HP System Insight Manager is preferred) and a tool for monitoring of

services (MonitorWare Agent is preferred).

3.5.3.4 The server shall include an antivirus and intrusion protection program. McAfee is

preferred.3.5.3.5 It shall be possible to automatically synchronize the time of the management

system to an external NTP time source and forward correct time to the network

elements.

3 5 3 6 The operating system used for the client shall be described by the Tenderer and


27/82




3.5.4.1 The Tenderer shall thoroughly describe: The internal structure of the manager application

The management protocol used

Multi user access functions

Start up time for the warm or hot standby management back-up system

Synchronization, database update and take over procedures between theoperating managers and the backup managers

The information exchange with the superior management systems(northbound)

3.5.5 Database system3.5.5.1 The database system constitutes the database manager used by the management

application.

3.5.5.2 The Tenderer shall thoroughly describe the system and its capabilities, access

rights as well as back-up and restore functions.3.5.5.3 A database of the type MS SQL Server 2005 for Windows based systems is

preferred.

3.5.6 System ManagementThis paragraph is valid for the OS and the Applications of the Servers and the

Clients.

3.5.6.1 The Tenderer shall thoroughly specify the security, identification andauthentication functions.

3.5.6.2 The user identity shall always be verified. Individual operator passwords shall be

used to gain system access.

3.5.6.3 All security related functions must be saved in a data log.

3.5.6.4 The logging functions shall be described in detail.

3.5.6.5 The NMS shall support different user classes for the access control with differentaccess rights to the system set by the System Administrator.

3.5.6.6 Logging of operator identity shall be made when access privileges and IT Security

sensitive data are changed.

3 5 6 7 O t ith i l h ll diff t t f th t k

SWEDISH DEFENCE MATERIEL ADMINISTRATION SPECIFICATION WDM


28/82




The existing management systems consist of the following main parts. TNMS v12.0 (Nokia Siemens) over Windows Server 2003

EM-OS v6.7.3 (Ericsson Marconi) over HP UX v10.2

HP-OV NNM 6.2 (Hewlett Packard) over HP UX 11.0

HP-OV NNM 7.53 over MS Server 2003

Netviewer v7.0 SP5 (Nokia Siemens) over Windows Server 2003

ServiceOn/MiniLink Manager v7.1 (Ericsson Marconi) over Windows Server

2003 NetMaster (NERA) over Windows Server 2003

SyncView v3.1.1 over Windows Server 2003

IBM Tivoli NetCool

3.5.7.1 It is an advantage if any of the existing management systems can be used for

management of the xWDM system. To be stated by the Tenderer.

3.5.7.2 The Tenderer shall thoroughly describe the solution for interaction between theNMS as well as the xWDM System and higher level management systems.

3.5.8 Communication protocols3.5.8.1 The NMS shall use the communication protocol IPv4 shall for communication the

between the different servers and the network elements.

3.5.8.2 The NMS should be capable to use the communication protocol IPv6 for the

communication between the different servers and the network elements.3.5.8.3 SNMPv3 shall be used between the NMS and the superior management system.

3.5.8.4 The Tenderer shall state the communications port numbers used for setting of the

existing firewalls.

3.5.9 Man Machine InterfaceThe Man Machine Interface (MMI) for communication with the application

(manager) shall conform to the following requirements:3.5.9.1 All text-information appearing in the MMI shall be in Swedish or English

3.5.9.2 The MMI shall be graphical and window-oriented

3.5.9.3 The screen shall be a flat colour screen with the minimum size 21 inch and the

SWEDISH DEFENCE MATERIEL ADMINISTRATION SPECIFICATION WDM


29/82




3.6.1 General functionality3.6.1.1 The Tenderer shall thoroughly describe the Graphical User Interface (GUI) withrespect to customization, presentation layers and operators privilege profile.

3.6.1.2 Critical actions as delete, etc. shall be confirmed.

3.6.1.3 On-line help and "Undo" functions shall be supported.

3.6.1.4 The Tenderer shall thoroughly describe the Security Manager, i.e. the system

managers tool to control other operators access and privileges of the NMS.

3.6.1.5 The Tenderer shall thoroughly describe the event filter, i.e. the tool for

subscription to events based on different criteria and needs.

3.6.1.6 Functions shall be included in the NMS for export of different types of logs and

measurements to a common and widespread file format.

3.6.2 Network functionality

3.6.2.1 The Tenderer shall thoroughly describe the Network Editor, i.e. how the topologyof the xWDM System network is created, viewed and edited.

3.6.2.2 The Tenderer shall thoroughly describe the Node Manager, the tool to manage

routing tables and cross connects etc.

3.6.2.3 It shall be possible to download new software to the network elements via the

integrated element manager.

3.6.2.4 The Node Manager shall support consistency check between data stored in the

network element and corresponding data stored in the network database.

3.6.3 Supervision functionality3.6.3.1 The Tenderer shall thoroughly describe the Trouble Ticketing i.e. the tool to

administer complaints or problems indicated by the subscriber or the system.

3.6.3.2 The Tenderer shall thoroughly describe the Fault Manager, i.e. the tool to monitor

and report fault status and correlation in the xWDM System network.

3.6.3.3 The Tenderer shall thoroughly describe the Test Functions, i.e. the tool to test the

equipment and the paths to localise problems, fault interpretation included.

3.6.3.4 The Tenderer shall thoroughly describe the Performance Manager, i.e. the tool to

report and monitor the performance of objects in the transport network.



30/82




4 INTERFACE REQUIREMENTS

4.1 Mechanical Interface4.1.1 Type of mounting 19 inch racks or ETSI racks.

FMV prefers mounting in both types of

racks.

4.1.2 Installation particularities All terminating connectors must be easily

accessible for installation and maintenancewithout dismounting the equipment

4.1.3 Dimensions To be stated

4.1.4 Weight To be stated

4.2 Power Supply4.2.1 Characteristics Shall conform to ETSI EN 300 132-2,

48 V DC nominal

4.2.2 Input voltage polarity Positive to ground or floating

4.2.3 Power consumption Maximum 800W. To be stated for each

node type.

4.2.4 Connector type To be stated

4.2.5 Power supply disturbances After the end of any voltage variations and

power supply interruptions the equipment

shall automatically resume normal

operation (i.e. the same operation mode as

before the disturbance)

4.3 Equipment Protective Ground4.3.1 Protective ground connection The equipment shall have a stud screw or

equivalent for protective grounding,mounted directly on the chassis

4.4 Traffic Interfaces

4 4 1 Interface DWDM



31/82




4.4.2 Interfaces CWDM4.4.2.1 Characteristics According to ITU-T rec. G.695

4.4.2.2 Frequency grid According to ITU-T rec. G694.2

4.4.2.3 Reach Short-haul, Long-haul

4.4.2.4 Connector type To be stated, LC preferred

4.4.3 Interface SDH

4.4.3.1 Characteristics According to ITU-T rec. G.957 and G.691

4.4.3.2 Type STM-1 S-1.1, L-1.1 and L-1.2

Connector type to be stated. LC preferred

4.4.3.3 Type STM-4 S-4.1, L-4.1 and L-4.2


4.4.3.4 STM-16 S-16.1, L-16.1 and L-16.2


4.4.3.5 STM-64 S-64.1, L-64.1 and L-64.2


4.4.4 Interface 10GBE LAN PHY and WAN PHY4.4.4.1 Characteristics According to IEEE.802.3ae

4.4.4.2 Types 10GBase-SR

10GBase-SW10GBase-LR

10GBase-LW

10GBase-ER 10GBase-EW

10GBase-ZR

10GBase-ZW

4.4.4.3 Connector type To be stated. LC preferred

4.4.5 Optical Interface OTU4.4.5.1 Characteristics According to ITU-T rec. G.709

4.4.5.2 Types OTU1

OTU2



32/82




4.4.6 Optical Interface 1GBE4.4.6.1 Characteristics According to IEEE 802.3z

4.4.6.2 Types 1000Base-SX

1000Base-LX

1000Base-ZX


4.4.7 Electrical Interface 1GBE4.4.7.1 Characteristics According to IEEE 802.3ab

4.4.7.2 Types 1000Base-T

4.4.7.3 Connector type RJ-45

4.4.8 Optical Interface Fast Ethernet4.4.8.1 Characteristics According to IEEE 802.3u

4.4.8.2 Types 100Base-SX

100Base-FX


4.4.9 Electrical Interface Fast Ethernet4.4.9.1 Characteristics According to IEEE 802.3

4.4.9.2 Interface type Ethernet 10/100BaseT4.4.9.3 Connector type RJ-45

4.4.10 Interface Fibre Channel4.4.10.1 Characteristics According to ANSI X3.230

4.4.10.2 Types 10GFC

8GFC

4GFC2GFC

1GFC

4.4.10.3 Reach Long, Intermediate, Short

4 4 10 4 Fibre Type Single Mode



33/82



4.6 Remote Management Interface [Q]The optional remote manager shall be connected to the xWDM System by meansof an existing Data Communication Network.

4.6.1 Interface type Ethernet 10/100BaseT

4.6.2 Connector type RJ-45

4.7 Service Channel Interface

4.7.1 Ethernet4.7.1.1 Characteristics According to IEEE 802.3

4.7.1.2 Interface type Ethernet 10/100BaseT


4.7.2 E1

4.7.2.1 Characteristics ITU-T rec. G.703

4.7.2.2 Interface type E1




34/82



5 ENVIRONMENTAL REQUIREMENTS

5.1 General5.1.1 The equipment shall be able to operate and be maintained in the physical and

electrical environment specified in this chapter.

5.1.2 Test reports and results verifying the fulfilment of the environmental requirements

shall be provided to FMV during the First Article Test.

5.2 Climatic EnvironmentThe xWDM System shall meet climatic environmental conditions according to

ETS 300 019

5.2.1 Indoor equipment Stationary use in weather-protected location

(indoor installation) as per ETSI EN 300

019-1-3, class 3.1

5.2.2 Transport conditions Public transportation as perETSI EN 300 019-1-2, class 2.3

5.2.3 Storage conditions Weather protected, not temperature

controlled as per

ETSI EN 300 019-1-1, class 1.2

5.3 Electrical Environment

5.3.1 EMC5.3.1.1 The xWDM System shall meet EMC requirements according ETSI EN 300 386

V1.4.1; Immunity, Emission and Testing Conditions. Transmission Equipment

Specific Requirements shall apply.

5.4 Safety5.4.1 The xWDM System shall meet the safety requirements of

EN 60950-1, Information technology equipment. Safety. General requirements

EN 41003, Particular safety requirements for equipment to be connected totelecommunications networks

5 5 H t S f



35/82



6 DESIGN REQUIREMENTS

6.1 General6.1.1 The Tenderer shall guarantee that used materials meet all requirements stipulated

in specifications, drawings or any other document referred to in the quotation.

6.2 Environmental protection

6.2.1 Green telecom6.2.1.1 The Tenderer shall submit his policies for Green Telecom, i.e. preventing

contribution directly to climate change; in particular to the production of

greenhouse gases due to for example power consumption, concentration of

information and communication technology devices, recycling of material, etc.

6.2.1.2 The following international regulations on environmental protection should be

used:

ISO 14001:2004, Environmental management systems -- Requirements withguidance for use

ISO 14004:2004, Environmental management systems -- General guidelineson principles, systems and support techniques

6.2.2 Environmental Codes and Directives6.2.2.1 In regard to minimize the environmental effects the following Environmental

Codes and Directives shall be applicable:

The Swedish laws Miljbalken (The Environmental Code) SFS:1998:808and its ordinances in all parts

Directive 2002/95/EC of the European Parliament and of the Council on therestriction of the use of hazardous substances in electrical and electronic

equipment (RoHS)

Directive 2002/96/EC of the European Parliament and of the Council on waste

of electrical and electronic equipment (WEEE)

6.2.3 CE approval6.2.3.1 The xWDM System shall conform to European Directives regarding safety, health

and environmental requirements. This shall be ascertained by affixed CE

f i ki li bl


d k ffi


36/82



6.4.2 The equipment shall be designed with easily exchangeable spare units that havecomplete mechanical and electrical exchangeability.

6.4.3 It must be possible to change a spare unit without switching off the power supply.

6.4.4 The exchange of a spare unit should not require special tools. After exchange no

subsequent adjustment shall be necessary.

6.4.5 The equipment shall be properly marked to make it easy to locate different items,

e.g. test points. See 6.6.

6.5 Changes, Upgrades and Modifications6.5.1 All items of the same type shall be identical in relation to each other to preserve

the exchangeability of lrus. This also applies to software and firmware.

6.5.2 When production has started no modifications affecting the interfaces or functions

are allowed unless approved by FMV.

6.6 Labelling and Marking6.6.1 The equipment and included units down to lru shall be given serial numbers.

6.6.2 All switches, test points, etc. related to installation and maintenance shall have

clear and legible markings. All markings must correspond exactly to the

documentation designation.

6.6.3 Patch cables shall be marked in a clear and consistent way, identifying the

connection points in the xWDM System. The marking shall comprise shelfnumber, slot number and port number. Example of the patch cable markings shall

be included in the Tender.

6.6.4 The equipment and subunits shall be equipped with FMV identification labels.

The size and appearance of the identification labels will be discussed during order

negotiation or during the first progress meeting.

6.6.5 FMV will provide FMV identification labels.

6.7 Packing6.7.1 The equipment shall be designed and packed to permit transportation by air, sea or

truck without risk of damage.

6.7.2 Reusable packaging is preferred.


C3I S t P t C d N t k Offi 10FMV2552 2 1


37/82



6.10 Use of commercially available software6.10.1 The Tenderer shall explain how FMV will be assured maintenance and anysubsequent modifications of commercial software.

6.10.2 A description of how the Tenderer will ensure the quality of commercial software

shall be included.

6.10.3 Clearly define which rights FMV will receive to commercial software.


C3I Systems Procurement Command Network Office 10FMV2552 2:1


38/82



7 AVAILABILITY, PERFORMANCE AND MAINTENANCE

7.1 General7.1.1 This chapter specifies the qualitative and quantitative requirements on the

availability, performance and maintenance of the xWDM System.

7.1.2 The hardware of the xWDM System is expected to consist of commercially

available equipment. This will influence the system design, the maintenance

system, the procurement of spare parts and, consequently, the availabilityperformance of the xWDM System.

7.2 Logistic Support Analysis (LSA)

7.2.1 LSA Management7.2.1.1 The Contractor shall, with advice and assistance from FMV, undertake the LSA

management activities, in accordance with DEF STAN 00-60 or similar.

7.2.1.2 The Contractor shall provide all of the necessary logistic information to FMV

consistent with the proposed maintenance strategy.

7.2.2 LSA Tasks7.2.2.1 FMV has developed a LSA strategy as follows:

7.2.2.2 The Swedish Defence shall be able to perform functional recovery comprising

fault finding down to lru (Line Replaceable Unit) and/or psp (Primary Spare Part

unit) at the installation site. The LSA process shall define the lru or psp and mayinclude modules and circuit boards. Faulty lrus can be shipped to the Contractor

or any other service facility that FMV may choose, for repair. The Contractor

shall be obliged to repair faulty units within an agreed Turn Around Time.

7.2.2.3 The Tenderer shall provide a LSA plan according to DEF-STAN 00-60 Task 102

or similar and be prepared to carry out recommended activities during the project.

7.3 Life expectancy and operating profile

7.3.1 Life expectancy7.3.1.1 Life expectancy shall be stated by the Tenderer.

7 3 1 2 Expected nominal lifetime shall be minimum 10 years


C3I Systems Procurement Command Network Office 10FMV2552 2:1


39/82



7.4 Maintenance system design7.4.1 The maintenance system design shall be based on field repair by exchange offaulty lrus (line replaceable units) carried out by the Swedish Defence

Maintenance Organization.

7.4.2 The Contractor shall carry out repairs of lrus on agreed turn around times and give

technical support during the equipment lifetime.

7.5 Test, alarms and supervisory functions7.5.1 The xWDM System shall have test, alarms and supervisory functions for trouble-shooting and continuous technical and quality monitoring.

7.5.2 The maintenance philosophy according to ITU-T M.20 and other relevant

recommendations should be applied.

7.5.3 The Tenderer shall thoroughly describe all test, alarms and supervisory functions.

7.6 Availability performance requirements

7.6.1 Reliability requirements7.6.1.1 The minimum reliability requirement is 100 000 hours for a complete xWDM

System terminal.

7.6.1.2 The Tenderer shall state guaranteed values corresponding to the requirements to

which availability performance parameters are assigned.

7.6.1.3 The reliability requirements include all types of failures, in hardware as well as insoftware.

7.6.1.4 The MTBF for each type of lru and for the complete xWDM System as well as for

the management platform workstations shall be stated in the tender.

7.6.1.5 It shall be possible to deduce and calculate the hardware reliability parameters on

the basis of MIL-HDBK-217F or some other well-established standard. The used

calculation method shall be stated by the Tenderer.

7.6.2 Maintainability requirements7.6.2.1 The xWDM System shall be of modular design and shall consist of units that are

replaceable on site.

7 6 2 2 R l t h ll b ibl ith th t d


C3I Systems Procurement Command Network Office 10FMV2552-2:1


40/82

C3I Systems Procurement Command, Network Office 10FMV2552 2:1


7.7.1.1 The Tenderer shall estimate and submit the initial LSC including:

Training Costs

Documentation Costs

Spares Costs

Support Equipment Costs

7.7.1.2 The Tenderer shall estimate and submit the annual and long term LSC including:

Corrective maintenance Preventive maintenance costs

lru repair costs

Spares costs

Technical support costs

7.7.2 Reliability block diagram7.7.2.1 A reliability block diagram shall be submitted in the tender. The diagram shall be

broken down to at least lru/psp-level. If one block consists of several lru/psp, each

lru/psp in the block shall be shown separately. Relevant redundancies shall be

specified.

MTBF for each individual block

MTBFtot for each individual block

MTTR for each individual block

The number of lrus for each individual block

7.7.3 Maintainability information7.7.3.1 The Tender shall describe the self-test and monitoring functions on site.

7.7.3.2 The Tender shall give examples of error messages from the system.

7.7.3.3 The Tender shall describe how the system control functions can be used, e.g. for

switching over between redundant units, if any.

7.7.3.4 The Tender shall describe the start-up and restart procedures (manual orautomatically initiated) of the xWDM System. The start-up and restart time shall

also be stated.

7.7.4 Preventive maintenance




41/82

C3 Syste s ocu e e t Co a d, Netwo O ce 0 V 55 :


7.7.5.3 The following information is required:

Item and original code

Recommended number per maintenance level

Price per unit

Its not necessary to include standard transmission instruments and standardtools

7.7.6 Software releases, service bulletins, etc.7.7.6.1 The Tenderer shall state his procedures for subscription to software releases,

service bulletins, etc.

7.7.6.2 The Tenderer shall specify the contents of the subscription.

7.7.7 Suggestion for training facilities7.7.7.1 The Tenderer shall give a proposal on equipment suitable for one autonomous

training facility.

7.8 Spare parts7.8.1 The Contractor shall provide a spare parts price list and undertake to deliver, spare

parts necessary for the expected lifetime of the xWDM System. Spare parts will

be ordered separately.

7.8.2 FMV reserves the right to purchase spare parts from other suppliers.

7.8.3 The Contractor shall inform FMV, in good time, of his and his sub-contractors

intentions to discontinue the production of any equipment and component that has

been delivered, in order to enable FMV to purchase spare parts for the remaining

lifetime.

7.8.4 The following data shall be submitted (in tabular form, appendix 2) for each

replaceable spare part in the system:

Item and original code

Denomination/designation ID-tag for superior unit

Category (lru, psp, spec-lru, spec-psp)

Number per superior system (item of equipment)

Expected failure rate when in operation (for psp = 1/guaranteed operating




42/82

y ,


7.9 Technical support7.9.1 The Contractor shall undertake technical support and offer a technical supportsolution the entire lifetime of the delivered equipment. A Technical Support

agreement proposal shall be enclosed in the tender.

7.9.2 Technical support means that the Contractor shall provide trained personnel,

equipment, etc. in order to:

Carry out maintenance in relation to complex faults of a systematic or

intermittent nature Modify delivered system functions and add new functions and software to the

system

Solve interface problems between the xWDM System and the interactingequipment

7.9.3 Technical telephone support in connection with the initial deployment of the first

10 network elements shall be included.

7.9.4 Technical support on the site shall be offered separately based on an hourly fee.

7.10 Repair service7.10.1 The Contractor shall undertake to offer and carry out, against separate orders,

repair services of the delivered xWDM System. A draft example on a repair

agreement shall be enclosed in the tender.

7.11 Software support7.11.1 The Contractor shall establish all software licenses and other Imaginary Property

Rights (IPR) issues that would be needed to operate, maintain and support the

delivered system.

7.12 Tenderers Maintenance system7.12.1 For evaluation of the Tenderer's suitability as a maintenance resource, the tender

shall describe the maintenance organisation, geographical location, personnel,maintenance equipment etc.




43/82


8 DOCUMENTATION8.1 General8.1.1 The term documentation, in this chapter, refers to all publications, drawings and

other written documents that provide the necessary information for the operation,

installation, commissioning, maintenance, verification and training of personnel.

8.1.2 The documentation shall be prepared, designed and submitted according to FMV

information requirements during acquisition, project development and operation.8.1.3 The Contractor shall be responsible for compliance with the requirements,

specified herein, concerning all documentation, including the documentation from

his sub-contractors

8.2 Types of documentation

8.2.1 Contents8.2.1.1 The documentation shall contain only descriptions and data sheets that are

pertinent to the system and its functionality.

8.2.1.2 The documentation should be standard documentation adjusted to the delivered

equipment.

8.2.1.3 Documents intended for PR or sales promotion shall not be included.

8.2.2 Language8.2.2.1 All documentation shall be written in Swedish or English.

8.2.2.2 Recognized technical rules and concepts shall be employed.

8.2.3 Form8.2.3.1 The Tender shall be able to deliver the documentation as printed on paper and on

CD-ROM.

8.2.3.2 The file format on the CD-ROM shall be well established, for example AdobePDF.

8.2.4 Standards8.2.4.1 Units of measurement shall be in accordance with the international SI system.




44/82


8.2.5.4 In case the xWDM System is modified or updated, the documentation shall be

updated. The Tenderer shall specify if there is a subscription service for the

supplied documentation, the scope and the annual cost.

8.3 ManualsThe minimum contents of the manuals shall be as stated in chapters 8.3.1- 8.3.5.

8.3.1 Description of equipment

8.3.1.1 This description shall: Include technical data and technical descriptions

Constitute an adequate basis for fault tracing down to line replaceable units(lru)

Form the basis for future modifications

Include block schematics down to lru and psp level

Include assembly drawings

8.3.2 Descriptions of operation8.3.2.1 The description of operation shall:

Describe the operation, design and use of the equipment

Describe local management

Describe the interfaces and interaction with external equipment

Provide the user with sufficient knowledge of the equipment

Constitute an adequate basis for maintenance work and fault tracing Be suitable for the training of maintenance personnel

8.3.3 Description of Installation and Commissioning8.3.3.1 The Contractor shall provide detailed instructions for installation and start-up in

such form and detail that installation and start-up can be carried out.

8.3.3.2 The design and contents of the installation documentation shall be decided in

consultation with FMV and shall comprise drawings, cable connection diagramsand tables, e.g. In addition to installation and start-up instructions, the instructions

shall also include the following information for the planning of premises:

Documents for assembly and securing to floors and walls, as well as locationsof vents and inlets/outlets for cabling



SE 115 88 STOCKHOLM SWEDEN D 2010 04 26


45/82


8.3.4 Description of maintenance8.3.4.1 This description shall:

Provide the maintenance personnel with knowledge of the maintenance pro-cedures of the equipment

Constitute instructions for the management of maintenance equipment and testprograms if any

8.3.4.2 The documents shall include information concerning:

The necessary instruments, special test equipment, test programs, etc.

Fault finding instructions

Repair instructions

Preventive maintenance instructions

8.3.5 Description of Software8.3.5.1 This documentation shall contain all necessary information needed for local

operation management as well as remote management. The required managementfunctions are described in chapter 3.

8.3.5.2 The Contractor shall deliver original descriptions for the operating system.

8.4 Basis for Registration of Necessities

8.4.1 General

8.4.1.1 All equipment and materiel within the Swedish defence that are utilised, kept instorage, shown and handled in the information system of the Swedish defence, is

registered in FMVs material registration system FREJ88.

8.4.1.2 FMV will perform computerized registration of units and components included in

the equipment in FREJ88 by engagement of contractor or the equipment

contractor.

8.4.2 Basis for registration in FREJ888.4.2.1 The Tenderer shall supply information for the FMV basic registration of storagedesignations (M- and F-numbers) according to Appendix 4. All parts pertinent to

the order shall be included. The information shall be presented at the first progress

meeting.



SE 115 88 STOCKHOLM SWEDEN D t 2010 04 26


46/82


9 INSTALLATION AND COMMISSIONING

Installation of the xWDM System will be performed by FMV.

The Contractor shall assist and shall provide technical assistance in the planning

of installation and commissioning.

Technical Support during the commissioning shall be offered as an option.

9.1 Security approvalFor planning and commissioning on the sites it is necessary to hold a Swedish

citizenship ant to be security approved by the Swedish Defence.



SE 115 88 STOCKHOLM SWEDEN Date: 2010 04 26


47/82


10 TRAINING10.1 General

Training shall be carried out as outlined in this chapter. The contents and dates of

the training courses will be agreed on at the progress meetings.

10.1.1 Extent and guide-lines10.1.1.1 The following courses shall be included:

System overview course for network planners

Technical maintenance course for field engineers

Technical operations and management course for NOC personnel

System course FAT (first article test)

Network planning course

10.1.1.2 The objectives of each course are specified in 10.2-10.6.

10.1.1.3 The Contractor shall be responsible for all training, including equipment and

software, supplied by sub-contractors.

10.1.2 Training course10.1.2.1 The Contractor shall establish a detailed training time schedule in co-operation

with FMV. The time schedule must be agreed upon as soon as possible after the

order.

10.1.2.2 A draft training contents list shall be submitted in the Tender.

10.1.3 Training course material10.1.3.1 Training shall be performed on systems, HW and SW, according to this

specification. Any deviations must be agreed on with FMV.

10.1.3.2 The Contractor shall:

Submit to FMV a detailed (hour by hour) course programme, not later thanthree months before the beginning of a course

Supply each of the trainees with a complete set of the required coursedocumentation, well in advance before the beginning of the course

After the course has been completed, submit to FMV a complete set of thefi l i i f th d t ti ( ft fil id t t )



SE-115 88 STOCKHOLM SWEDEN Date: 2010-04-26


48/82


10.1.4 Contents and language10.1.4.1 The content of each course document shall be clear and easily readable.

10.1.4.2 The documentation shall contain necessary descriptions, drawings and data sheets

etc. PR and sales documentation must not be used as reference material during the

training.

10.1.4.3 The courses shall be held in Swedish or English.

10.1.4.4 All documents used for the training shall be written in Swedish or English.

10.2 System Overview Course

10.2.1 Objective10.2.1.1 After completing the course, the trainees shall have overview knowledge of the

design and the functions of the xWDM System, its use, installation, maintenance

requirements, performance possibilities and documentation.

10.2.2 Contents10.2.2.1 Presentation of the xWDM System software and hardware including a practical

demonstration.

10.2.2.2 Installation particulars shall be included as well as a functional overview based on

illustrations and block diagrams.

10.2.2.3 Control and test functions shall be described.

10.2.2.4 The course may also serve as an introduction for the "Technical MaintenanceCourse and the Technical Operation and Management Course"

10.2.3 Target group10.2.3.1 The course is intended for participants, with a general technical education holding

management positions, and who need a general knowledge of the system and its

functions.

10.2.4 Number of trainees10.2.4.1 Maximum 15.

10.2.5 Course duration10.2.5.1 Approximately 1-2 working days.





49/82

SE 115 88 STOCKHOLM, SWEDEN Date: 2010 04 26

10.3.2 Contents10.3.2.1 The technical maintenance course shall include a functional overview based on

illustrations and block diagrams.

10.3.2.2 To be able to find faults down to sub unit level, the equipment must be described

in sufficient detail.

10.3.2.3 Detailed descriptions of the input and output functions, maintenance test points

etc shall be included.

10.3.2.4 Practical "hands-on" training shall be emphasized, concentrated to fault location,by using the test equipment and test programs included and restoration by

replacement of sub units.

10.3.3 Target group10.3.3.1 Instructors and field-maintenance engineers with good theoretical and practical

knowledge of transmission equipment.

10.3.4 Number of trainees10.3.4.1 Maximum 8 peoples.

10.3.5 Course duration10.3.5.1 Approximately 3 - 5 working days.

10.3.6 Location of training courses10.3.6.1 The training shall be held at the Contractor's training centre or in Sweden.

10.3.6.2 For training in Sweden the premises and classroom equipment will be made

available by FMV. The location will be chosen by FMV

10.4 Technical Operation and Management Course

10.4.1 Objective10.4.1.1 The objective of the course is to give the participants a good knowledge of the

software functions. After completion the participants must be capable to carry outthe daily operation and supervision, of the network.

10.4.2 Contents10.4.2.1 The content shall comprise a presentation of the xWDM System and the





50/82

,

10.4.4.1 5 10 trainees at a time.

10.4.5 Course duration10.4.5.1 Maximum 5 working days.

10.4.6 Location of training courses10.4.6.1 The training shall be held at the Contractor's training centre or in Sweden.

For training in Sweden the premises and classroom equipment will be made

available by FMV. The location will be chosen by FMV.

10.5 System Course, FAT

10.5.1 Objective10.5.1.1 The objective of the course is to give the participants a good knowledge of the

xWDM System functions and handling. After completion the participants must be

capable to carry out the FAT.

10.5.2 Contents10.5.2.1 Technical and operational information to give personnel, involved in the FAT,

such overall insight of the system and documentation, that they will be able to

perform the FAT together with the Contractor's personnel.

10.5.2.2 A description with block schematics to sub-unit level and description of software

functions.

10.5.3 Target group10.5.3.1 The course is intended for personnel carrying out FAT.


10.5.5 Course duration

10.5.5.1 Approximately 3-5 working days.10.5.5.2 The course shall be held before and in conjunction with the first article test (FAT).

10.5.6 Location of training courses10.5.6.1 The training shall be held at the Contractor's factory or training centre.





51/82

10.6.2.1 Technical and operational information to give personnel, involved in the planning,

such overall insight of the system and planning tools, that they will be able toperform the network planning

10.6.2.2 A description of planning procedures and planning tools and a point by point

planning guide.

10.6.3 Target group10.6.3.1 The course is intended for network planning engineers.


10.6.5 Course duration10.6.5.1 Approximately 2-4 working days.

10.6.6 Location of training courses

10.6.6.1 The training shall be held at the Contractor's training centre or in Sweden.For training in Sweden the premises and classroom equipment will be made

available by FMV. The location will be chosen by FMV.





52/82

11 QUALITY ASSURANCE11.1 General11.1.1 The requirements stated in this chapter are applicable to the Contractor and for his

quality control of sub-contractors and vendors.

11.1.2 The Contractor shall deliver the goods or services at the agreed price and time

schedule.

11.1.3 The Contractor shall present objective facts which show that the Contractor hasmaintained control of his activities and carried out the inspections/verifications,

whose results show that the product fulfils all the requirements.

11.1.4 The project shall during the entire contract performance be supervised and

inspected in accordance with the quality plan, to ensure that the requirements are

met.

11.2 Requirements on the Contractor's general quality assurance

11.2.1 Quality Management System11.2.1.1 The Contractors quality management system should be based on ISO 10007,

Quality Management Systems - Guidelines for configuration management. The

quality management system shall take the following main management processes

into account;

Identification Configuration Control

Status Accounting

Configuration Audit

11.2.2 Quality Systems11.2.2.1 The Contractor shall be able to establish his ability to deliver a product that meets

the specified requirements. The Contractor shall have a quality system that fulfils

the requirements of EN-ISO 9001.

11.2.3 Contractor assessment11.2.3.1 FMV shall, if it so desires (even before the contract has been signed), be given the

opportunity to evaluate the efficiency and compliance of the Contractor's quality





53/82

subsequent rejections, nor preclude FMV from doing subsequent reviews of the

quality plan.

11.3.2 Scope11.3.2.1 The quality plan shall cover all phases of contract performance. Inspection and

testing procedures, methods and work instructions to be applied, suitable testing,

inspection, examination and audit programmes at appropriate stages (design,

development, etc.) and associated records are often more conveniently managed

as separate documents but shall, as such, be referred to in the quality plan.

11.3.3 Contents11.3.3.1 The quality plan shall contain the following chapters:

Organization of the quality functions within the project

The quality objectives to be attained

The specific allocation of responsibilities and authorities during the differentphases of the project

Method for changes and modifications in the quality plan as the projectproceeds

List of consultants, vendors and sub-contractors who are of significantimportance for the project and to whom the Contractor intends to apply for

contract performance

Reference to a project flow chart (including software -if any) that clearly andwith information of phases (time events) shows major activities including

design, tests, inspections and verifications performed during the design andproduction phases

References to the specific procedures, methods, work instructions and formsfor the verification of tests, inspections, examinations and audits at appropriate

stages

Reference to a cross reference list between specified requirements and theactivities that confirm that the requirements are fulfilled

11.3.4 Updating11.3.4.1 The Contractor shall keep the quality plan and referenced documents continuously

updated.

11.3.4.2 Changes shall be reported to FMV before they are applied.





54/82

11.4.1.3 The FAT procedure shall describe how all te

Date post:	02-Jun-2018
Category:	Documents
Upload:	otoniel-rodriguez-g
View:	230 times
Download:	0 times