Technical Specification 1.0

SWEDISH DEFENCE MATERIEL ADMINISTRATION SPECIFICATION: xWDM
C3I Systems Procurement Command, Network Office 10FMV2552-2:1

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

Spec xWDM V1.5.doc
Page 2 of 82

TABLE OF CONTENTS 2
1 SYSTEM OVERVIEW 4
1.1 Introduction.............................................................................................................. 4
1.2 Swedish Defence Telecommunication Network...................................................... 4
1.3 Nomenclature........................................................................................................... 4
1.4 Response .................................................................................................................. 5
1.5 References................................................................................................................ 6
2 TECHNICAL REQUIREMENTS 7
2.1 General..................................................................................................................... 7
2.2 Wavelength Division Multiplex System Definition ................................................ 7
2.3 Composition............................................................................................................. 7
2.4 References................................................................................................................ 7
2.5 Main requirements ................................................................................................... 9
2.6 Type Nodes............................................................................................................ 15
2.7 Reference System.................................................................................................. 23
3 NETWORK MANAGEMENT SYSTEM 24
3.1 General................................................................................................................... 24
3.2 Overview................................................................................................................ 24
3.3 Capacity ................................................................................................................. 25
3.4 DCN Transmission Capacity ................................................................................. 25
3.5 System components ............................................................................................... 25
3.6 Management Application Function ....................................................................... 28
3.7 Licenses ................................................................................................................. 29
4 INTERFACE REQUIREMENTS 30
4.1 Mechanical Interface.............................................................................................. 30
4.2 Power Supply......................................................................................................... 30
4.3 Equipment Protective Ground ............................................................................... 30
4.4 Traffic Interfaces.................................................................................................... 30
4.5 Local Management Interface [F] ........................................................................... 32
4.6 Remote Management Interface [Q] ....................................................................... 33
4.7 Service Channel Interface...................................................................................... 33
5 ENVIRONMENTAL REQUIREMENTS 34
5.1 General................................................................................................................... 34
5.2 Climatic Environment............................................................................................ 34
5.3 Electrical Environment .......................................................................................... 34
5.4 Safety ..................................................................................................................... 34
5.5 Hot Surfaces........................................................................................................... 34
6 DESIGN REQUIREMENTS 35
6.1 General................................................................................................................... 35
6.2 Environmental protection ...................................................................................... 35
6.3 Standards................................................................................................................ 35
6.4 Mechanical and Electrical Construction Design.................................................... 35
6.5 Changes, Upgrades and Modifications .................................................................. 36
6.6 Labelling and Marking........................................................................................... 36
6.7 Packing................................................................................................................... 36
6.8 Software................................................................................................................. 36
6.9 Design of program system..................................................................................... 36
6.10 Use of commercially available software................................................................ 37

Spec xWDM V1.5.doc
Page 3 of 82

7 AVAILABILITY, PERFORMANCE AND MAINTENANCE 38
7.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............................ 39
7.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......................................................................................... 43
8.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...................................................... 52
11.4 First Article Test .................................................................................................... 53
11.5 Delivery Inspection................................................................................................ 55
11.6 Delivery ................................................................................................................. 55
12 PROJECT MANAGEMENT 58
12.1 General................................................................................................................... 58
12.2 Project Manager..................................................................................................... 58
12.3 Progress meetings .................................................................................................. 58
12.4 Progress reports...................................................................................................... 58
12.5 Informal meetings.................................................................................................. 58
12.6 Project Plan............................................................................................................ 58
13 APPENDICES 60


Spec xWDM V1.5.doc
Page 4 of 82

1 SYSTEM OVERVIEW
1.1 Introduction
1.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 Network
1.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 is
installed 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 restoring
functions by replacing malfunctioning Line Replaceable Units (lru).
1.3 Nomenclature
1.3.1 The Swedish Defence Materiel Administration is hereafter referred to as FMV.
1.3.2 The successful Tenderer is hereafter referred to as the Contractor.
1.3.3 Mandatory requirements in this specification are expressed with "shall", "must" or
explanatory text.
1.3.4 Preferred requirements in this specification are expressed by "should", optional
or explanatory text.
1.3.5 Requirements that cannot be identified as mandatory, prefer or preferred
according to the above shall be regarded as mandatory.
1.3.6 The expression To be stated means that the Tenderer shall provide the
information. Omitted information is evaluated as not fulfilled requirement.

Spec xWDM V1.5.doc
Page 5 of 82

1.4 Response
1.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 reasonably
be 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 by
the 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
compliance.
Non-Compliant The Tenderer shall answer Non-Compliant when the
required functionality is not supported by the system
release that is available at the point of time of answering
this proposal.
The Tenderer shall state if the functionality will be
supported in a future release.
Alternative solutions may also be offered.


Spec xWDM V1.5.doc
Page 6 of 82

1.4.3 Additional information shall be provided after the level of compliance and in
annexed 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

Spec xWDM V1.5.doc
Page 7 of 82

2 TECHNICAL REQUIREMENTS
2.1 General
2.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 Definition
2.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 Composition
2.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 References
2.4.1 The xWDM System shall conform to the following standards and
recommendations. The Tenderer shall separately state deviations, if any, in
comparison with the relevant publication.
ITU-T rec. G.664 Optical safety procedures and requirements for optical
transport systems.
ITU-T rec. G.671 Characteristics of optical components and subsystems.
ITU-T rec. G.680 Physical transfer functions of optical network elements.
ITU-T rec. G.692 Optical interfaces for multichannel systems with optical
amplifiers.
ITU-T rec. G.694.1 Spectral grids for WDM applications: DWDM frequency
grid.

Spec xWDM V1.5.doc
Page 8 of 82

ITU-T rec. G.694.2 Spectral grids for WDM applications: CWDM frequency
grid.
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).
ETSI EN 300 019-1-1 Environmental Engineering (EE); Environmental
conditions and environmental tests for
telecommunications equipment; Part 1-1: Classification of
environmental conditions; Storage.
environmental conditions; Transportation.

Spec xWDM V1.5.doc
Page 9 of 82

environmental 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 electrical
and 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 topology
2.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.
2.5.1.2 In the first deployment phase the xWDM System shall be used in a network with a
topology layout according to Appendix 1. The different nodes are interconnected
by means of existing black fibres.
2.5.1.3 In the forthcoming deployment phases (the plans are not yet finalized), the
network will be expanded; hence the xWDM System of first deployment phase
must be possible to supplement for the expansion. The Tenderer shall thoroughly
describe how to expand the system.
2.5.1.4 For forthcoming deployment phases, the Tenderer shall as option offer xWDM
equipment based on generic network elements (Type Nodes) that are described
in section 2.6.

Spec xWDM V1.5.doc
Page 10 of 82

2.5.2 Services
2.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.5 to 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
2.5.2.9 Additional Services
The Tenderer shall specify any additional services that are supported by the
xWDM System for example other SAN applications than Fiber Channel.
2.5.3 Service grooming
2.5.3.1 It shall be possible to groom different services to the same wavelength by means
of a multiplexing function and optical transport frames. The grooming
functionality shall be stated by the Tenderer
2.5.3.2 The service grooming function shall be achieved by a universal grooming card
with pluggable client interfaces. The Tenderer shall describe the grooming
function and the capacity.

Spec xWDM V1.5.doc
Page 11 of 82

2.5.3.3 The grooming function shall support add and drop of services to and from the line
signals (ADM). To be stated.
2.5.4 Transparency
2.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 wavelengths
2.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 grids
Frequency 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 many
wavelengths 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 Flexibility
2.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.
2.5.8 System Description
2.5.8.1 For the tender evaluation a detailed technical system description of the offered
xWDM System shall be included. The following information is expected:
Technical data of the network elements, cards, interfaces etc.
System functions description
Network Elements description
Main functions of available cards
Mechanical design
Basic information on planning, installation and commissioning
Network management overview (architecture, software, interfaces)

Spec xWDM V1.5.doc
Page 12 of 82

Maintenance function for example test and loop back, optical power
indications
2.5.9 Management
2.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 Interfaces
2.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 on
pluggable modules are preferred.
2.5.11 Optical Amplifiers
2.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 compensation
2.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,
type of device and latency imposed included.
2.5.13 Universal traffic cards
2.5.13.1 FMV prefers universal traffic cards that are software adjusted for the required
service and complemented with a suitable optical module.
2.5.14 Tuneable optical interfaces
2.5.14.1 FMV prefers tuneable optical interfaces to simplify the spare parts handling.
Tuneable optical interfaces should be offered as an option.

Spec xWDM V1.5.doc
Page 13 of 82

2.5.15 Automatic optical power management
2.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 connections
2.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 switching
2.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 Encryption
2.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 duplicated
cards 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
describe the line protection possibilities.
2.5.20 Operation and Maintenance functions
2.5.20.1 A network planning tool shall be included to simplify the network planning (for
example planning of the network topology, fibre and optical parameters,
equipment lists etc).
2.5.20.2 It should be possible to use the network planning tool also as a configuration tool
for the network elements.
2.5.20.3 The use of the network planning tool shall be described in detail.

Spec xWDM V1.5.doc
Page 14 of 82

2.5.20.4 Functions for automatic discovery and provisioning should be included to
simplify 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 thoroughly
described 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 Channel
2.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
functions in the network element and completely separated. Faults in the
management channel shall not be traffic affecting.
2.5.21.3 It shall be possible to encrypt the management channel by means of existing
external crypto equipment. The interface shall be Fast Ethernet according to IEEE
802.3 or E1 according to ITU-T rec G.703. Details to be stated by the Tenderer.
2.5.21.4 The xWDM System shall include an Embedded Data Communication Channel
that completely separates the management function from customer data. It shall be
possible to disable the ECC when it is not used. The ECC shall be thoroughly
described.
The Management Channel and the ECC Channel is explained in Figure 1.


Spec xWDM V1.5.doc
Page 15 of 82

Figure 1. Management Channel and ECC Channel
2.5.22 EMC/EMI
2.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 General
2.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.2 to 2.6.7 shall 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.
2.6.1.3 All nodes and their packing shall be clearly marked with the relevant site
designation. Detailed parameters shall be discussed during the first progress
meeting.
2.6.1.4 For future deployment phases the Tenderer shall offer xWDM network elements
as an option. The required network elements are described as a number of
different Type Nodes according the sections 2.6.2 to 2.6.7.
2.6.1.5 The offer shall include expandable variations for:
A minimum configuration with the initial number of wavelengths 8 ,
expandable to 40 and with two cases of fibre attenuation for the xWDM
interfaces.


Spec xWDM V1.5.doc
Page 16 of 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 attenuation
for 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.

Spec xWDM V1.5.doc
Page 17 of 82
2.6.2 Type Node A
2.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


Spec xWDM V1.5.doc
Page 18 of 82
2.6.3 Type Node B
2.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 ,
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
Maximum 40 , 15-25 dB, DWDM 16
40 , 30-35 dB, DWDM 16


Spec xWDM V1.5.doc
Page 19 of 82
2.6.4 Type Node C
2.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


Spec xWDM V1.5.doc
Page 20 of 82
2.6.5 Type Node D
2.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
Expandable
Configuration
xWDM interface,
No. of ,
DWDM
Medium 16 , 15-25 dB, CWDM, DWDM 4 +4 groomed services


Spec xWDM V1.5.doc
Page 21 of 82
2.6.6 Type Node E
2.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
connection
xWDM
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


Spec xWDM V1.5.doc
Page 22 of 82
2.6.7 Type Node F
2.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


Spec xWDM V1.5.doc
Page 23 of 82

2.6.8 Type Node G
2.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 System
2.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 additional
chassis 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 perform
measurements from client interface to client interface, short haul optical
interfaces included.
A separate management system for the reference equipment with functions
according to Chapter 3, but for a limited number of network elements.


Spec xWDM V1.5.doc
Page 24 of 82
3 NETWORK MANAGEMENT SYSTEM
3.1 General
3.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 systems
and 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. The
layout and the function shall be equal to the main NMS.

Figure 8. xWDM System Network Management System (NMS)


Spec xWDM V1.5.doc
Page 25 of 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 be
possible 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 Capacity
3.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 Capacity
3.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
3.5 System components
3.5.1 Overview
3.5.1.1 The NMS shall include the following main system components:
Management system platform, hardware
Management system platform, software (OS) and general IT security
Management application, Element Manager included
Database system
System management
Interaction with existing management systems

Spec xWDM V1.5.doc
Page 26 of 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, Hardware
3.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 Security
3.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
the Security Templates possibilities (Security Hardening) shall be thoroughly
described. An MS Windows Terminal Server based client platform is preferred
due to IT Security reasons.
3.5.3.7 The Tenderer shall state the IT security classes the OS complies with, according
to ISO/IEC 15408, Information technology Security techniques Evaluation
criteria for IT or other well known international standard.
3.5.4 Management application
This system component constitutes the end-user application for management of
the network aspects of the xWDM System (Network Management level) as well
as the network elements (Element Management level).

Spec xWDM V1.5.doc
Page 27 of 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 the
operating managers and the backup managers
The information exchange with the superior management systems
(northbound)
3.5.5 Database system
3.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 Management
This 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 and
authentication 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 different
access 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 Operators with various user classes shall manage different parts of the network.
3.5.6.8 The Tenderer shall thoroughly specify the resources that can be accessed for the
different user classes.
3.5.6.9 The Tenderer shall thoroughly describe the audit functions, for example log-ins,
log-outs, access right violations etc.
3.5.6.10 It shall be possible to export an audit report in a common file format.
3.5.6.11 The Tenderer shall thoroughly describe how data between processes, users and
objects are protected from loss or alteration.
3.5.6.12 Data loss or data alterations shall result in event logs.
3.5.7 Interaction with the Existing Management Systems

Spec xWDM V1.5.doc
Page 28 of 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 the
NMS as well as the xWDM System and higher level management systems.
3.5.8 Communication protocols
3.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 Interface
The 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
minimum resolution 1280x1024 dpi.
3.5.9.4 The screen should be TCO Certified.
3.5.9.5 The keyboard layout should be Swedish
3.5.10 Management of the NMS
3.5.10.1 The Tenderer shall thoroughly describe how systems management of the NMS is
supported, i.e. adding of new applications.
3.6 Management Application Function
The Management Application Function contains the user graphical tools for the
management of the xWDM System.

Spec xWDM V1.5.doc
Page 29 of 82

3.6.1 General functionality
3.6.1.1 The Tenderer shall thoroughly describe the Graphical User Interface (GUI) with
respect 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 topology
of 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 functionality
3.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.
3.6.4 Utility functionality
3.6.4.1 A Script Manager that replaces manual actions by a sequence of script commands
should be included. The Tenderer shall thoroughly describe the functions.
3.6.4.2 The NMS shall include functions for export of different logs and measurements to
a common file format.
3.7 Licenses
3.7.1 Required licenses shall be included in the offer and issued to Frsvarsmakten (The
Swedish Defence).


Spec xWDM V1.5.doc
Page 30 of 82

4 INTERFACE REQUIREMENTS
4.1 Mechanical Interface
4.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 maintenance
without dismounting the equipment
4.1.3 Dimensions To be stated
4.1.4 Weight To be stated
4.2 Power Supply
4.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 Ground
4.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
4.4.1.1 Characteristics According to ITU-T rec. G.692
4.4.1.2 Frequency grid According to ITU-T rec. G694.1
4.4.1.3 Reach Long-haul, Very long-haul, Ultra long-haul
4.4.1.4 Connector type To be stated, LC preferred

Spec xWDM V1.5.doc
Page 31 of 82

4.4.2 Interfaces CWDM
4.4.2.2 Frequency grid According to ITU-T rec. G694.2
4.4.2.3 Reach Short-haul, Long-haul
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 PHY
4.4.4.1 Characteristics According to IEEE.802.3ae
4.4.4.2 Types 10GBase-SR
10GBase-SW
10GBase-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 OTU
4.4.5.2 Types OTU1
OTU2
OTU1eOTU2e (LAN)

Spec xWDM V1.5.doc
Page 32 of 82

4.4.6 Optical Interface 1GBE
4.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 1GBE
4.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 Ethernet
4.4.8.1 Characteristics According to IEEE 802.3u
4.4.8.2 Types 100Base-SX
100Base-FX
4.4.9 Electrical Interface Fast Ethernet
4.4.9.1 Characteristics According to IEEE 802.3
4.4.9.2 Interface type Ethernet 10/100BaseT
4.4.10 Interface Fibre Channel
4.4.10.1 Characteristics According to ANSI X3.230
4.4.10.2 Types 10GFC
8GFC
4GFC
2GFC
1GFC
4.4.10.3 Reach Long, Intermediate, Short
4.4.10.4 Fibre Type Single Mode
4.5 Local Management Interface [F]
4.5.1 Interface Type To be stated
4.5.2 Connector Type To be stated

Spec xWDM V1.5.doc
Page 33 of 82

4.6 Remote Management Interface [Q]
The optional remote manager shall be connected to the xWDM System by means
of 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 Ethernet
4.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


Spec xWDM V1.5.doc
Page 34 of 82

5 ENVIRONMENTAL REQUIREMENTS
5.1 General
5.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 Environment
The 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 per
ETSI 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 EMC
5.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 Safety
5.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 to
telecommunications networks
5.5 Hot Surfaces
5.5.1 If operating temperature of cards or units represents a maintenance-handling
hazard, warning labels shall be furnished.


Spec xWDM V1.5.doc
Page 35 of 82

6 DESIGN REQUIREMENTS
6.1 General
6.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 telecom
6.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 with
guidance for use
ISO 14004:2004, Environmental management systems -- General guidelines
on principles, systems and support techniques
6.2.2 Environmental Codes and Directives
6.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:808
and its ordinances in all parts
Directive 2002/95/EC of the European Parliament and of the Council on the
restriction 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 approval
6.2.3.1 The xWDM System shall conform to European Directives regarding safety, health
and environmental requirements. This shall be ascertained by affixed CE
conformity markings to applicable parts.
6.2.3.2 The Tenderer shall provide Certificates of the CE approvals.
6.3 Standards
6.3.1 Components should as far as possible be standardized components in accordance
with international or Swedish standards.
6.4 Mechanical and Electrical Construction Design
6.4.1 The Tenderer's standards for electrical and mechanical joints shall be stated in the
tender. High quality industrial standards that are internationally recognized shall
be used.

Spec xWDM V1.5.doc
Page 36 of 82

6.4.2 The equipment shall be designed with easily exchangeable spare units that have
complete 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 Modifications
6.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 Marking
6.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 shelf
number, 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 Packing
6.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.
6.7.3 Marking of inside and outside (transport) packing shall be discussed during order
negotiation or during the first progress meeting.
6.8 Software
6.8.1 The Tenderer shall state the details of the software and firmware to be used.
6.9 Design of program system
6.9.1 The program system design and verification procedures shall be described by the
Tenderer.

Spec xWDM V1.5.doc
Page 37 of 82

6.10 Use of commercially available software
6.10.1 The Tenderer shall explain how FMV will be assured maintenance and any
subsequent 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.

Spec xWDM V1.5.doc
Page 38 of 82

7 AVAILABILITY, PERFORMANCE AND MAINTENANCE
7.1 General
7.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 availability
performance of the xWDM System.
7.2 Logistic Support Analysis (LSA)
7.2.1 LSA Management
7.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 Tasks
7.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 may
include 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 expectancy
7.3.1.1 Life expectancy shall be stated by the Tenderer.
7.3.1.2 Expected nominal lifetime shall be minimum 10 years.
7.3.1.3 Expected nominal lifetime should be at least 15 years.
7.3.2 Operating profile
7.3.2.1 The system will be in continuous operation 24 hours a day.
7.3.3 Life support cost
7.3.3.1 See 7.7.1.

Spec xWDM V1.5.doc
Page 39 of 82

7.4 Maintenance system design
7.4.1 The maintenance system design shall be based on field repair by exchange of
faulty 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 functions
7.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 requirements
7.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 in
software.
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 requirements
7.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 Replacement shall be possible with the power turned on.
7.6.2.3 The Tenderer shall state the procedures for loading new software releases, if and
how it may affect the hardware, PROM exchange etc.
7.7 Evaluation of availability performance, maintenance and LSC
7.7.1 Life support cost
The technical life expectancy will serve as the basis for calculating the Life
Support Cost (LSC). The life expectancy will be applicable from the date when
FMV has approved the final delivery.

Spec xWDM V1.5.doc
Page 40 of 82

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 diagram
7.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 information
7.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 or
automatically initiated) of the xWDM System. The start-up and restart time shall
also be stated.
7.7.4 Preventive maintenance
7.7.4.1 Preventive maintenance should not be required.
7.7.4.2 In case preventive maintenance is required, the details shall be stated in the tender.
7.7.5 Proposal for maintenance equipment
7.7.5.1 The Tender shall include a proposal for any maintenance equipment that may be
required.
7.7.5.2 The term maintenance equipment refers to:
Special tools and instruments
Test equipment, test benches, adapters, etc. needed for repair work in the
workshop, as well as diagnostic software, test programs, etc.

Spec xWDM V1.5.doc
Page 41 of 82

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 standard
tools
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 facilities
7.7.7.1 The Tenderer shall give a proposal on equipment suitable for one autonomous
training facility.
7.8 Spare parts
7.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
useful life in hours)
Guaranteed failure rate when in operation
Price per unit
Mean time to replace (MTTRp)
Mean time to repair lru (MTTRlru)
For lru: Fixed price per repair, at Tenderers factory, after expiry of the
guarantee period
For lru: Workshop turnaround time. For psp: Delivery time
If the unit has a limited life, this shall be stated together with the expected
useful life

Spec xWDM V1.5.doc
Page 42 of 82

7.9 Technical support
7.9.1 The Contractor shall undertake technical support and offer a technical support
solution 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 interacting
equipment
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 service
7.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 support
7.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 system
7.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.

Spec xWDM V1.5.doc
Page 43 of 82

8 DOCUMENTATION
8.1 General
8.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 Contents
8.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 Language
8.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 Form
8.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 Adobe
PDF.
8.2.4 Standards
8.2.4.1 Units of measurement shall be in accordance with the international SI system.
8.2.4.2 The nomenclature in documents shall follow IEC-standards.
8.2.4.3 Standards for data media shall be stated.
8.2.5 Verification and updates
8.2.5.1 All documents will be verified on delivery.
8.2.5.2 The required corrections and updates shall be accomplished without extra costs
for FMV, provided that they are not initiated by FMV.
8.2.5.3 Errors in the documentation, discovered during other activities than verification
on delivery, for example during installation or training, shall be corrected by the
Contractor free of charge during the warranty period.

Spec xWDM V1.5.doc
Page 44 of 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 Manuals
The 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 operation
8.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 Commissioning
8.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 diagrams
and 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 locations
of vents and inlets/outlets for cabling
Suitable types of cables and connectors
Requirements on cabling (length limits, separation from cables that may cause
interference, etc.)
Pin configurations
Physical measures e.g. length and weight

Spec xWDM V1.5.doc
Page 45 of 82

8.3.4 Description of maintenance
8.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 test
programs 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 Software
8.3.5.1 This documentation shall contain all necessary information needed for local
operation management as well as remote management. The required management
functions 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 in
storage, 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 FREJ88
8.4.2.1 The Tenderer shall supply information for the FMV basic registration of storage
designations (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.


Spec xWDM V1.5.doc
Page 46 of 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 approval
For planning and commissioning on the sites it is necessary to hold a Swedish
citizenship ant to be security approved by the Swedish Defence.

Spec xWDM V1.5.doc
Page 47 of 82

10 TRAINING
10.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-lines
10.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 course
10.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 material
10.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 than
three months before the beginning of a course
Supply each of the trainees with a complete set of the required course
documentation, well in advance before the beginning of the course
After the course has been completed, submit to FMV a complete set of the
final revision of the course documentation (software files, video tapes, etc.)
Restore the equipment to its original state if any special modifications have
been made for training purposes. (This requirement applies to equipment
owned by FMV)

Spec xWDM V1.5.doc
Page 48 of 82

10.1.4 Contents and language
10.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 Objective
10.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 Contents
10.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 Maintenance
Course and the Technical Operation and Management Course"
10.2.3 Target group
10.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 trainees
10.2.4.1 Maximum 15.
10.2.5 Course duration
10.2.5.1 Approximately 1-2 working days.
10.2.6 Location of training courses
10.2.6.1 The training shall be held in Sweden at a venue agreed upon during the contract
negotiations.
10.3 Technical Maintenance Course
10.3.1 Objective
10.3.1.1 After completing the course the trainees shall understand the interaction with
other systems, the design and operation. They shall be capable to perform local
management, field-maintenance down to subunits and know how to use the
maintenance equipment and test programs.

Spec xWDM V1.5.doc
Page 49 of 82

10.3.2 Contents
10.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 group
10.3.3.1 Instructors and field-maintenance engineers with good theoretical and practical
knowledge of transmission equipment.
10.3.4.1 Maximum 8 peoples.
10.3.5.1 Approximately 3 - 5 working days.
10.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 Objective
10.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 out
the daily operation and supervision, of the network.
10.4.2 Contents
10.4.2.1 The content shall comprise a presentation of the xWDM System and the
Management System. System-oriented description, build-up and function,
together with block diagrams and drawings, showing the signal paths between
various parts of the system shall be included.
10.4.2.2 User action for various operational modes must be given, e g performance,
security, configuration and fault.
10.4.2.3 All actions shall be "hands on".
10.4.3 Target group
10.4.3.1 Personnel working at the Network Operation Center.

Spec xWDM V1.5.doc
Page 50 of 82

10.4.4.1 5 10 trainees at a time.
10.4.5.1 Maximum 5 working days.
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 Objective
xWDM System functions and handling. After completion the participants must be
capable to carry out the FAT.
10.5.2 Contents
10.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 group
10.5.3.1 The course is intended for personnel carrying out FAT.
10.5.4.1 Maximum 6.
10.5.5.2 The course shall be held before and in conjunction with the first article test (FAT).
10.5.6.1 The training shall be held at the Contractor's factory or training centre.
10.6 Network planning course
10.6.1 Objective
network planning and planning tools. After completion the participants must be
capable to carry planning to create new networks and to expand existing
networks.
10.6.2 Contents

Spec xWDM V1.5.doc
Page 51 of 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 to
perform 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 group
10.6.3.1 The course is intended for network planning engineers.
10.6.4.1 Maximum 10.
For training in Sweden the premises and classroom equipment will be made
available by FMV. The location will be chosen by FMV.


Spec xWDM V1.5.doc
Page 52 of 82

11 QUALITY ASSURANCE
11.1 General
11.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 has
maintained 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 System
11.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 Systems
11.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 assessment
11.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
system at the Contractor's premises. These audits may concern the entire quality
system or be limited to certain processes or certain products.
11.2.3.2 FMV shall have the rights to access the results of the Contractor's internal quality
assessments (audits).
11.3 Requirements on the Contractor's quality plan
11.3.1 General
11.3.1.1 The Contractor shall within 2 months after contract submit to FMV the quality
plan for review and comment. The review by FMV does not relieve the Contractor
of his responsibility to provide conforming products, nor shall it preclude

Spec xWDM V1.5.doc
Page 53 of 82

subsequent rejections, nor preclude FMV from doing subsequent reviews of the
quality plan.
11.3.2 Scope
11.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 Contents
11.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 different
phases of the project
Method for changes and modifications in the quality plan as the project
proceeds
List of consultants, vendors and sub-contractors who are of significant
importance 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 and
with information of phases (time events) shows major activities including
design, tests, inspections and verifications performed during the design and
production phases
References to the specific procedures, methods, work instructions and forms
for the verification of tests, inspections, examinations and audits at appropriate
stages
Reference to a cross reference list between specified requirements and the
activities that confirm that the requirements are fulfilled
11.3.4 Updating
11.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.
11.4 First Article Test
11.3.4.1 The First Article Test (FAT) is the test that shall be carried out on the first
articles, on an agreed upon number of units, to ensure that the products fulfils all
requirements stated in the contract, specification and other relevant documents
such as progress reports and other agreements.
11.4.1 FAT procedure and records
11.4.1.1 A FAT procedure document with test records shall be delivered to FMV at least
one week before an agreed progress meeting.
11.4.1.2 The FAT procedure shall specify the methods for verification of conformity for
material, software and services etc. of the product.

Spec xWDM V1.5.doc
Page 54 of 82

11.4.1.3 The FAT procedure shall describe how all tests and verifications are to be carried
out in order to show that the product conforms to the requirements set in the
contract.
11.4.1.4 For every inspection point the FAT procedure shall contain information on
nominal data and tolerances according to the technical specification and other
requirement documents in the contract.
11.4.1.5 The presentation shall be legible and well organized in order to make it easy to
find the inspection chapter, that corresponds to a given function (requirement) in
the technical specification and other requirement documents in the contract.
11.4.1.6 The FAT shall conform to the objectives specified in 0 - 0.
11.4.1.7 General
List of contents
Designation and article number
Purpose of FAT procedures and principles for the documentation and usage of
results.
11.4.1.8 Inspection facilities
List of material and measuring instruments required at inspection
List of inspection and auxiliary programmes used for the inspection
Documentation and aid programmes shall be available to FMV prior to the
start of the inspection
Visual inspection
Configuration check in accordance with material lists
Inspection of modification/revision status of material, individual numbers,
software and documentation
Inspection of quality of manufacture in terms of conformity to standards and
work instructions
11.4.1.9 Functional inspection
The inspection shall show that the product fulfils all functional requirements
stipulated in the contract
All inspection points shall be listed and specified in detail
Methods of measurements used in functional inspection shall be described to
ensure reproducibility, with specification of the following:
Points of connection
Recommended measuring ranges for instruments used (range, bandwidth,
sensitivity, calibration requirements, etc)
Specified data with tolerances
Description of ambient conditions (electrical, mechanical, cleanness, etc.)
especially for outside measuring sites
11.4.1.10 Load check (software)
Definition of conditions and description of execution of inspection
Loads on CPU and I/O-channels

Spec xWDM V1.5.doc
Page 55 of 82

Memory loads
Response times
11.4.1.11 Personal and product safety
Instructions to prevent personal injury and material damages.
11.4.2 FAT records.
11.4.2.1 The FAT record shall be the document in which verification and inspection,
carried out in accordance with FAT procedure, are reported.
11.4.2.2 The record should be a separate document with references pertinent to paragraphs
in the FAT procedure.
11.4.2.3 The disposition of the record shall follow the FAT procedure document.
11.4.2.4 Each inspection action shall be signed by the inspector concerned.
11.4.3 Conditions for start of the FMV FAT inspection.
11.4.3.1 The Contractor shall have carried out complete FAT in accordance with the FAT
procedure and pertinent quality plan.
11.4.3.2 The FAT record and a written delivery notification (see paragraph "Delivery
notification") all have been received in, accordance with the time schedules, by
FMV.
11.4.3.3 Address:
Swedish Defence Materiel Administration
C3I Systems Procurement Command
Network Office
SE-115 88 STOCKHOLM
SWEDEN
11.5 Delivery Inspection
11.5.1 The procedures for a delivery inspection are considered to be chosen subsets of
the FAT test. Usually statistical sampling is applied to randomly choose the
objects for inspection.
11.6 Delivery
11.6.1 Conditions for start of FMV inspection
11.6.1.1 The following conditions must be met:
11.6.1.2 The Contractor has carried out complete inspection in accordance with the
pertinent quality plan. Deviations from specified requirements are not allowed
without a written agreement with FMV.
11.6.1.3 Delivery documents, as described below, are available.
11.6.1.4 Delivery notification, as described below, has been received by FMV.
11.6.2 Delivery notification

Spec xWDM V1.5.doc
Page 56 of 82

11.6.2.1 A written delivery notification, on products/services for delivery, shall have been
received by FMV no later than 10 working days prior to the scheduled delivery
date.
11.6.2.2 Address:
Swedish Defence Materiel Administration
C3I Systems Procurement Command
Network Office
SE-115 88 STOCKHOLM
SWEDEN
11.6.2.3 The delivery notification shall have the following content:
FMV order number
Date when the product is ready for FMV inspection
Scope of delivery, with item number and designation, in accordance with the
FMV order
11.6.3 Delivery Documentation
11.6.3.1 Delivery documentation specified below comprises the documents that identify
the delivery and show that specified requirements are fulfilled. Any
nonconformities and reasons for that shall be noted.
11.6.3.2 Certificate of Conformity that (FMV form) shall contain notice that the products
included in the delivery/sub-delivery have been inspected by the Contractor and
fulfils specified requirements. This certificate of conformity shall be signed by a
person responsible for the quality assurance in its entirety. The certificate shall
address:
Scope of delivery, with item number and designation, in accordance with the
FMV order
Individual numbers
Modification and revision status
11.6.3.3 Records
Final inspection record
Record from any special verifications
Appropriate diagrams, curves, material certificates, X-ray records etc. in
relation to the test
Descriptions and designations of material, included in the delivery, down to
line replaceable unit, lru
List of software and firmware
A digital file comprising serial numbers, firmware and software versions of all
equipment in the delivery

Spec xWDM V1.5.doc
Page 57 of 82

11.6.4 Acceptance/Rejection
11.6.4.1 The product will be accepted if the requirements in the contract are fulfilled and
the Contractor is able to provide evidences for this, i.e. that the Contractor can in a
satisfactory way demonstrate to FMV that all the requirements are fulfilled.
11.6.4.2 If an agreement of joint inspection is made, the Contractor shall notify FMV, at a
reasonable time in advance; stating a time and a place for such a joint inspection.
11.6.4.3 If the product has been rejected, the Contractor shall, in writing, describe to FMV
the corrective actions that have been taken and the subsequent results, before the
product is again notified for delivery.
11.6.5 Conditions for delivery.
11.6.5.1 The conditions for delivery are that FMV in writing has accepted the product.

Spec xWDM V1.5.doc
Page 58 of 82

12 PROJECT MANAGEMENT
12.1 General
12.1.1 The Contractor will be responsible for planning, follow-up and system
coordination including, when applicable, planning and follow-up of sub-
Contractors undertakings.
12.2 Project Manager
12.2.1 The Contractor shall appoint a Project Manager whose responsibilities shall
include liaison with FMV. This shall be done at the order negotiations.
12.3 Progress meetings
12.3.1 The Contractor shall arrange progress meetings to inform of the progress of work.
These meetings shall be held regularly from the date of order according to
separate agreement. The meetings shall constitute the formal contacts between the
Contractor and FMV.
12.3.2 A draft agenda shall be received by FMV at least one week before each meeting.
12.3.3 Minutes of the proceedings at those meetings shall be taken by the Contractor and
be verified by both parties immediately after the meetings.
12.4 Progress reports
12.4.1 Progress reports shall be received by FMV one week in advance of the progress
meetings.
12.4.2 The progress reports shall include:
Project status
Time schedule
Technical issues and problems
12.5 Informal meetings
12.5.1 In addition to the above mentioned progress meetings, informal meetings may be
held at any time, as requested by either the Contractor or FMV.
12.5.2 Minutes of such informal meetings that do not need verification shall be taken by
the Contractor and be available as a basis for decisions taken at regular progress
meetings.
12.6 Project Plan
12.6.1 The Project Plan will be required during the entire project period in order to
achieve maximum coordination of production efforts made by all parties involved.
12.6.2 The Project Plan shall be prepared by the Contractor. The schedules shall be
detailed enough to explain the structure of the project and its interfaces with
others concerned, and also to facilitate time related reviews of the project plan.
12.6.3 The project Plan shall include information on activities and events applicable to
Contractors undertakings with regards to:
Specification

Spec xWDM V1.5.doc
Page 59 of 82

Design
ILS activities
Manufacture
FAT
Final inspection
Delivery
Documentation
Training
Progress meetings
12.6.4 Events agreed upon in the order, so called key events, shall be specifically
identified in the Project Plan together with information on the interdependence
between FMV and the Contractor.
12.6.5 The Project Plan shall be submitted to FMV to serve as a basis for higher level
planning. Alternations and deviations shall be compiled and reported to FMV.
12.6.6 Deviations which affect key events shall immediately be reported to FMV without
awaiting the next regular report.

Spec xWDM V1.5.doc
Page 60 of 82

13 APPENDICES

Appendix 1 Network Layout

Appendix 2 Availability performance and maintenance. Definitions.

Appendix 3 Tabular layout of reliability information data.

Appendix 4 Basis for Registration in FREJ88.


Spec xWDM V1.5.doc
Page 61 of 82

Appendix 1

Network Layout

Wavelength Division Multiplex System (xWDM)


Spec xWDM V1.5.doc
Page 62 of 82

Existing service equipment interfaces
Existing service equipment has the following type of interfaces:
STM-N, Short Haul 1310 nm
GBE, 1000Base-SX
10GBE, C-band tunable, compatible with Cisco 10GE Tunable WDM-PHY
Shared Port Adapter
FC, Short Reach 1310 nm


Spec xWDM V1.5.doc
Page 63 of 82
Phase 1, Main
In Figure 9, Network layout for phase 1, Table 7, Attenuation and distances for phase
1 and Table 8, Services for phase 1 it is shown how phase 1 of the xWDM network
shall be built.
Figure 9, Network layout for phase 1
5
1
7
6
10 9
4 3
2 8 11
12 13
16
15
14
18
17 20
19 21
23 22
24 26
27 25
28
29
30
31
32 33 34
35
36 37 39 38
41 42
43
45
Phase 3
Site 46
Phase 2
Site 73
Phase 4
Site 52
Phase 2
Site 67
Phase 2
Site 62
Phase 4
Site 61
Phase 3
Site 76
78 77 40
79


Spec xWDM V1.5.doc
Page 64 of 82

Table 7, Attenuation and distances for phase 1
Site Site Distance
km
Attenuation
dB @1550 nm
1 3 10 4,5
1 4 3,2 3,5
1 5 32 11
1 46 107 19
2 5 10 5
5 6 80 20
6 7 76 35
7 8 10 4
7 9 99 25
7 73 85 23
7 77 103 29
9 10 105 30
10 11 11 5
10 12 94 24,5
12 13 128 30
13 14 10 5
13 15 60 19
13 16 105 24
16 17 25 15,5
16 18 49 19,5
16 19 95 24
19 20 45 16
19 21 80 18
19 67 80 18
21 22 10 4
21 23 32 11
21 24 78 17
26 27 30 12
26 28 25 10
26 52 65 15
26 43 51 20
28 29 85 20
29 30 58 19
29 31 79 19
30 31 35 10
31 45 33 11
31 39 77 22
32 33 26 7
32 62 82 19
33 34 37 9
34 35 55 14
35 36 61 13
36 37 45 16
37 79 26 12
37 38 20 6,5
38 39 15 8
38 79 10 5

Spec xWDM V1.5.doc
Page 65 of 82

Site Site Distance
km
Attenuation
dB @1550 nm
38 41 14 5
38 42 14 5
38 61 44 16
39 42 10 5
39 41 10 4
39 76 70 30
40 77 17 6
41 42 10 5
77 78 10 5

Table 8, Services for phase 1
Nr Function
Start - End point
Type of Service Via
1 31 - 24 4 GFC 29, 28, 26
2 31 - 24 4 GFC 35, 34, 33, 32
3 31 - 24 4 GFC 29, 28, 26
4 31 - 24 4 GFC 35, 34, 33, 32
5 31 - 24 4 GFC 29, 28, 26
6 31 - 24 4 GFC 35, 34, 33, 32
7 31 - 24 4 GFC 29, 28, 26
8 31 - 24 4 GFC 35, 34, 33, 32
9 31 - 24 4 GFC 29, 28, 26
10 31 - 24 4 GFC 35, 34, 33, 32
11 31 - 25 10 GBE 29, 28, 26
12 24 - 25 10 GBE -
13 31 - 24 10 GBE 35, 34, 33, 32
14 24 - 25 10 GBE 26
15 24 - 26 4 GFC -
16 24 - 26 4 GFC 25
17 24 - 26 10GBE -
18 25 - 26 10GBE -
19 27 - 24 10 GBE 25
20 27 - 28 10 GBE 26
21 28 - 31 10 GBE 29
22 35 - 31 10 GBE -
23 35 - 37 10 GBE 36
24 35 - 24 10 GBE 34, 33, 32
25 31 - 39 10 GBE -
26 38 - 39 10 GBE -
27 38 - 37 10 GBE -
28 8 - 31 10 GBE 7, 9, 10, 12, 13, 16, 19, 21, 24,
26, 28, 29
29 24 - 23 2 x GBE (10 GBE) 21
30 23 - 17 2 x GBE (10 GBE) 21, 19, 16
31 23 - 15 2 x GBE (10 GBE) 21, 19, 16, 13
32 17 - 15 2 x GBE (10 GBE) 16, 13
33 15 - 9 2 x GBE (10 GBE) 13, 12, 10
34 7 - 9 2 x GBE (10 GBE) -
35 7 - 4 2 x GBE (10 GBE) 6, 5, 1
36 7 - 78 2 x GBE (10 GBE) 77
37 9 - 78 2 x GBE (10 GBE) 7

Spec xWDM V1.5.doc
Page 66 of 82

Nr Function
Start - End point
Type of Service Via
38 41 - 38 STM-16 -
39 37 - 36 STM-16 -
40 36 - 35 STM-16 -
41 35 - 34 STM-16 -
42 34 - 33 STM-16 -
43 33 - 32 STM-16 -
44 32 - 24 STM-16 -
45 24 - 25 STM-16 -
46 25 - 26 STM-16 -
47 25 - 27 STM-16 -
48 27 - 26 STM-16 -
49 24 - 26 STM-16 -
50 26 - 43 STM-16 -
51 26 - 28 STM-16 -
52 28 - 29 STM-16 -
53 29 - 30 STM-16 -
54 29 - 31 STM-16 -
55 30 - 31 STM-16 -
56 31 - 39 STM-16 -
57 31 - 45 STM-16 -
58 31 - 35 STM-16 -
59 38 - 37 STM-16 -
60 38 - 42 STM-16 -
61 38 - 61 STM-16 -
62 39 - 42 STM-16 -
63 39 - 38 STM-16 -
64 40 - 77 STM-16 -
65 42 - 41 STM-16 -
66 22 - 21 STM-16 -
67 20 - 19 STM-16 -
68 14 - 13 STM-16 -
69 11 - 10 STM-16 -
70 8 - 7 STM-16 -
71 2 - 5 STM-16 -
72 3 - 1 STM-16 -
73 24 - 21 STM-16 -
74 21 - 23 STM-16 -
75 21 - 19 STM-16 -
76 19 - 16 STM-16 -
77 16 - 17 STM-16 -
78 16 - 13 STM-16 -
79 16 - 18 STM-16 -
80 13 - 15 STM-16 -
81 13 - 12 STM-16 -
82 12 - 10 STM-16 -
83 10 -9 STM-16 -
84 9 - 7 STM-16 -
85 7 - 5 STM-16 -
86 7 - 77 STM-16 -
87 77 - 78 STM-16 -
88 5 - 1 STM-16 -
89 1 - 4 STM-16 -
90 24 - 26 1 GBE -

Spec xWDM V1.5.doc
Page 67 of 82

Nr Function
Start - End point
Type of Service Via
91 24 - 26 1 GBE 25
92 26 - 31 1 GBE 28, 29
93 26 - 31 1 GBE 24, 32, 33, 34, 35
94 42 - 26 1 GBE 39, 31, 29, 28
95 42 - 26 1 GBE 38, 79, 37, 36, 35, 34, 33, 32, 24
96 41 - 26 1 GBE 38, 39, 31, 29, 28
97 41 - 26 1GBE 38, 79, 37, 36, 35, 34, 33, 32, 24
98 26 - 42 10 GBE 28, 29, 31, 39
99 41 - 24 10 GBE 38, 79, 37, 36, 35, 34, 33, 32
100 79 - 34 STM-16 37, 36, 35
101 34 - 29 STM-16 33, 32, 24, 26, 28
102 29 - 39 STM-16 31
103 79 - 34 10 GBE 37, 36, 35
104 33 - 39 10 GBE 32, 24, 26, 29, 31
105 24 - 31 1 GBE 26, 28, 29
106 24 - 31 1 GBE 32, 33, 34, 35
107 24 - 25 1 GBE -
108 24 - 25 1 GBE 26
109 30 - 31 1 GBE -
110 31 - 42 1 GBE 39
111 41 - 24 1 GBE 38, 79, 37, 36, 35, 34, 33, 32
112 24 - 25 1 GBE -
113 25 - 26 1 GBE -
114 26 - 30 1 GBE 28, 29
115 30 - 42 1 GBE 31, 39
116 42 - 41 1 GBE -
117 42 - 39 1 GBE -
118 42 - 38 1 GBE -
119 41 - 38 1 GBE -
120 41 - 39 1 GBE -
121 30 - 31 1 GBE -
122 30 - 28 1 GBE 29
123 45 - 31 1 GBE -
124 45 - 35 1 GBE 31
125 43 - 27 1 GBE 26
126 43 - 28 1 GBE 26
127 25 - 24 1 GBE -
128 25 - 27 1 GBE -
129 22 - 23 1 GBE 21
130 22 - 17 1 GBE 21, 19, 16
131 20 - 17 1 GBE 19, 16
132 14 - 17 1 GBE 13, 16
133 14 - 15 1 GBE 13
134 18 - 17 1 GBE 16
135 18 - 15 1 GBE 16, 13
136 11 - 15 1 GBE 10, 12, 13
137 11- 9 1 GBE 10
138 8 - 7 1 GBE -
139 8 - 9 1 GBE 7
140 2 - 7 1 GBE 5, 6
141 2 - 4 1 GBE 5, 1
142 3 - 4 1 GBE 1
143 40 - 7 1 GBE 77

Spec xWDM V1.5.doc
Page 68 of 82

Nr Function
Start - End point
Type of Service Via
144 40 - 78 1 GBE 77
145 42 - 43 2 x 1 GBE 39, 38, 31, 29, 28, 26
Table 9, Type Nodes for phase 1
Site Type Node 1) Site Type Node 1)
1 To be stated by the Tenderer 24 G
4 To be stated by the Tenderer 27 To be stated by the Tenderer

1) Type Nodes shall be A to G according to chapter 2.6.

Spec xWDM V1.5.doc
Page 69 of 82
Phase 2
In Figure 10, Network layout for phase 2, Table 10, Distances for phase 2 and Table
11, Services for phase 2 it is shown how phase 2 of the xWDM network shall be
built.

62
63
67 66
68
64
65
72
69
70
71
73
Phase 1
Site 32
Phase 3
Site 51
Phase 1
Site 7
Phase 1
Site 19
Phase 3
Site 47
74

Table 10, Distances for phase 2
Site Opposite site Distance
km
Attenuation dB
@1550 nm
62 32 see phase 1
62 51 see phase 3
62 63 15 4,5
62 64 67 17,5
64 65 10 4
64 66 95 25,5
66 67 60 15
67 19 see phase 1
67 68 82 30
67 74 50 12
67 69 45 12
69 70 96 23,5
69 73 110 23
70 71 47 12,5
70 72 10 4
70 47 67 20
73 7 see phase 1


Spec xWDM V1.5.doc
Page 70 of 82

Nr Function
Start - End point
Type of Service Via
1 63 - 35 2 x GBE (10 GBE) 62, 32, 33, 34
2 63 - 24 2 x GBE (10 GBE) 32
3 63 - 74 2 x GBE (10 GBE) 62, 64, 66, 67
4 74 - 23 2 x GBE (10 GBE) 67, 19, 21
5 15 - 74 2 x GBE (10 GBE) 13, 16, 19, 67
6 7 - 71 2 x GBE (10 GBE) 73, 69, 70
7 74 - 71 2 x GBE (10 GBE) 67, 69, 70
8 65 - 63 1 GBE 64, 62
9 8 - 31 10 GBE 7, 73, 69, 67, 66, 64,
62, 32, 33, 34, 35
10 65 - 74 1 GBE 64, 66, 67
11 68 - 74 1 GBE 67
12 68 - 17 1 GBE 69, 19, 16
13 68 - 67 STM-16 -
14 72 - 71 1 GBE 70
15 74 - 20 1 GBE 67, 19
16 72 - 70 STM-16 -
17 32 - 62 STM-16 -
18 62 -63 STM-16 -
19 62 - 64 STM-16 -
20 64 - 65 STM-16 -
21 64 - 67 STM-16 -
22 67 - 19 STM-16 -
23 67 - 74 STM-16 -
24 67 - 69 STM-16 -
25 69 - 70 STM-16 -
26 70 - 71 STM-16 -
27 69 - 7 STM-16 -

Site Type Node 1)
62 To be stated by the Tenderer



Spec xWDM V1.5.doc
Page 71 of 82
Phase 3
In Figure 11. Network layout for phase 3, Table 13, Distances for phase 3 and Table
built.

Figure 11. Network layout for phase 3

km
Attenuation
dB @1550 nm
1 46 see phase 1
44 49 140 31
44 75 40 12
46 47 53 14
46 48 79 22,5
47 70 67 20
48 49 86 18,5
49 50 54 14
49 51 99 25
51 62 73 16,5
75 76 177 41
76 77 see phase 1


Spec xWDM V1.5.doc
Page 72 of 82

Nr Function
Start - End point
Type of Service Via
1 50 - 47 2 x GBE (10 GBE) 49, 48, 46
2 50 - 63 2 x GBE (10 GBE) 49, 51, 62
3 47 - 71 2 x GBE (10 GBE) 70
4 47 - 4 2 x GBE (10 GBE) 46, 1
5 44 - 50 2 x GBE (10 GBE)
6 44 - 75 2 x GBE (10 GBE)
7 38 - 75 2 x GBE (10 GBE)
8 72 - 47 1 GBE 70
9 47 - 3 1 GBE 46
10 62 - 49 STM-16 -
11 49 - 50 STM-16 -
12 49 - 48 STM-16 -
13 48 - 46 STM-16 -
14 46 - 47 STM-16 -
15 46 - 1 STM-16 -
16 47 - 70 STM-16 -
17 40 - 49 STM-16 -
18 44 - 75 STM-16 -
19 75 - 76 STM-16 -
20 76 - 77 STM-16 -

Site Type Node 1)



Spec xWDM V1.5.doc
Page 73 of 82
Phase 4
In Figure 12, Network layout for phase 4, Table 16, Distances for phase 4 and Table
built.

km
Attenuation
dB @1550 nm
26 52 see phase 1
52 53 70 17
52 54 64 23
54 55 49 20
55 56 81 18
56 57 35 8
57 58 57 12
58 59 95 23,5
59 60 71 15,5
60 61 46 19
61 38 see phase 1

Nr Function
Start - End point
Type of Service Via
1 53 - 27 2 x GBE (10 GBE) 52, 26
2 53 - 28 2 x GBE (10 GBE) 52, 26
3 53 - 57 2 x GBE (10 GBE) 52, 54, 55, 56
4 57 - 61 2 x GBE (10 GBE) 58, 59, 60
5 61 - 38 2 x GBE (10 GBE) -
6 26 - 52 STM-16 -
7 52 - 53 STM-16 -
8 52 - 54 STM-16 -
9 54 - 55 STM-16 -
10 55 - 56 STM-16 -
11 56 - 57 STM-16 -
12 57 - 58 STM-16 -
13 58 - 59 STM-16 -
14 59 - 60 STM-16 -
15 60 - 61 STM-16 -


Spec xWDM V1.5.doc
Page 74 of 82

Nr Function
Start - End point
Type of Service Via
16 61 - 38 STM-16 -

Table 18, Type Node for phase 4
Site Type Node 1)



Spec xWDM V1.5.doc
Page 75 of 82

Appendix 2

Availability Performance and Maintenance.
Definitions



Spec xWDM V1.5.doc
Page 76 of 82

The terms in this appendix are defined by FMV as follows:

LCC, Life Cycle Cost
LCC is the total cost of acquisition of a material system and its operation and support
during its life.
LSC, Life Support Cost
The support cost during the life of a material system including initial and recurring
costs.
Quality of Service
QoS is the total picture of the system efficiency, according to ITU-T.

Availability performance
A qualitative characteristic of a material system that determines its ability to perform
as specified when faults, interferences and limited maintenance resources influence its
performance.

Availability performance is a function of

- Reliability
- Maintainability
- Supportability

and is usually measured in terms of availability.

Reliability
A qualitative characteristic of a material system that determines the probability and
distribution in time of faults and disturbances. Reliability is usually measured in terms
of failure rate, Mean Time Between Failures (MTBF).

Maintainability
A qualitative characteristic of a material system that determines the possibilities or
spending of resources when using a specified maintenance organization and specified
maintenance resources, provided these are available when required.

Maintainability is usually measured in terms of Mean Time To Restore (MTTR).

Supportability
A qualitative characteristic of the maintenance system that expresses its ability to
provide maintenance resources when so required.

Supportability is usually measured in terms of Mean Time Waiting (MTW), Mean
Logistic Down Time (MLDT), etc.

To achieve a certain level of supportability it is required that the skill of the personnel,
the maintenance equipment, and the spares are dimensioned for that level.


Spec xWDM V1.5.doc
Page 77 of 82

MTBF
Mean time between failures causing breakdown of the system, i.e., taking existing
redundancies into account.

MTBFtot
Mean time between any hardware and software failures requiring any form of
maintenance action.

MTTRp
Mean time to restore the function of the equipment in its operational environment by
replacement, adjustment, repair, etc. See "Restore" below.

MTTRlru
Mean time to restore the function of a line replaceable unit (lru) by repair, replacement
of a shop replaceable unit (sru) or readjustment, etc. See "Restore" below.

MTTRsru
Mean time to restore the function of a shop replaceable unit (sru) by replacement of
parts, readjustment, etc. See "Restore" below.

Restore
The term "restore" comprises all pertinent maintenance activities, e.g., trouble-
shooting, fault finding, replacement, readjustment, repair and the consequent function
test and restart. Waiting and transport times for maintenance support are not included
in MTTR as defined above.

Spares (generic term)
Spares is a generic term and is classified according to the following characteristics:

- Is the spare repairable or not?
- Is it replaceable in the equipment or not?

This implies the following main categories:

Repairable
Yes No
Replaceable in Yes Line replaceable unit, lru Primary spare part, psp
the equipment No Shop replaceable unit, sru Secondary spare part, ssp

Line replaceable unit, lru
Is replaced in the equipment and is repairable (in a workshop).

Shop replaceable unit, sru
Is replaced in an lru and is repairable (in a workshop).


Spec xWDM V1.5.doc
Page 78 of 82

Primary spare part, psp
Is replaced in the equipment and is not repairable.

Secondary spare part, ssp
Is replaced in an lru or an sru and is not repairable.

- expensive/not expensive, using a criterion specific to each occasion

- standard/special, where standard refers to spares obtainable in the open
market

- limited life/not limited life, where limited life refers to spares with a
substantial increase of the failure rate with the time of operation (e.g.,
crystals).

Spec xWDM V1.5.doc
Page 79 of 82

Appendix 3

Tabular Layout of Reliability Information Data



Spec xWDM V1.5.doc
Page 80 of 82

Availability and
LSC-data for:
Tender
given by:

Revise status: Date:
Item Denomination
code number
ID-tag for
sub unit
Category Number
per sub
unit
Expected
failure
rate
[E*-6]
Guaranteed
failure rate
[E*-6]
Unit price
[tend curr]
Mean time
to replace
MTTRp
[h]
Mean time
to repair
MTTRlru
[h]
Price for
repair at
tenderer
factory
[tend. curr]
Turnaround
time
[h]
Limited
life time
[year]
1 2 3 4 5 6 7 8 9 10 11


Spec xWDM V1.5.doc
Page 81 of 82

Appendix 4

Basis for Registration in Frej88



Spec xWDM V1.5.doc
Page 82 of 82
Part number Alternative
mark of origin
Part name / Abbreviation Description Battery
Y/N
Height
mm
Width
mm
Depth
mm
Weight
kg
61705805 X3TY-60 SFP/2G5U/1310S/SM
Pluggable client for 1310nm, standard
reach, up to 2.7G. Applications 100-
2666Mbit/s, LC connector N 13 14 58 0.02

E
x
a
m
p
l
e

Technical Specification 1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical Specification 1.0

Uploaded by

Copyright:

Available Formats

SWEDISH DEFENCE MATERIEL ADMINISTRATION SPECIFICATION: xWDM

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

You might also like