This spreadsheet is provided as an optional means to verify the consistency of the

numbers provided in the Tender Form. Only the information in the Tender Form
has legal value. CERN does by no means guarantee the correctness of the formulae
in this spreadsheet.

Adjudication is based on this capacity measured in HEP-SPEC06 350.000

Prices in (currency) please specify currency

Estimate
ITE
DESCRIPTION Unit Price d PRICE (*)
M
Quantity
Price (FCA) of one fully equipped enclosure including assembly, testing, any other charges and 3 years 0,00
warranty.
1 NB: For a server enclosure with multiple mainboards (system units) quote the price for each fully
equipped enclosure.
For instance, for a 2U quad system, quote the price for the enclosure including the four system units.
Performance in HEP-SPEC06, as defined in the technical specification, of a fully equipped enclosure. 0,00
2 For instance, for a 2U quad system quote the sum of the performance of the four system units
Minimum number of fully equipped enclosures required to provide a total performance of 350.000,00 0,00
3 HEP-SPEC06: (3) = 350.000,00 HEP-SPEC06 / (2) rounded up to next higher integer
Price of initial stock of spare components for units to be shipped to CERN Meyrin (50% of the delivery 0,00
4,1 in Item 3), as defined in the warranty section of the technical specification, based on the bidder’s
estimates provided in the answer to the technical questionnaire.
Price of initial stock of spare components for units to be shipped to Wigner (50% of the delivery in Item 0,00
4,2 3), as defined in the warranty section of the technical specification, based on the bidder’s estimates
provided in the answer to the technical questionnaire.
Price for upgrading one system unit with two additional journaling SSDs as 0,00 48 0,00
5 defined in section 5.9 of the technical specification (please quote the price for
the two SSDs / system unit).
Price for upgrading one system unit with one LSI 9207-8e SAS Host Bus 0,00 108 0,00
6 Adapter as defined in section 5.10 of the technical specification.
TOTAL PRICE FREE CARRIER (FCA):(7) = [(3) x (1)] + [(4,1) + (4,2)] + [(5) + (6)] 0,00
7

Adjudication malus resulting from the cost incurred by CERN for hosting infrastructure for 4 years of 0,00
running of the proposed servers. The following parameters shall be used: - Electrical power: 0,0620
(CHF/kVAh) x 4(y) x 365(d/y) x 24(h/day) = 2172,48 CHF per kVA of total power consumption - 50
CHF per enclosure Power Supply inlets - 50 CHF per Gigabit Ethernet connections Please refer to
8 separate TCO table provided in the spreadsheet (Annex of the tender form).

Total cost for provided performance: 0,00

9
(9) = (7) + (8)
Total performance provided in HEP-SPEC06: 0,00
10
(10) = (3) x (2)
ADJUDICATION PRICE INCLUDING MALUS FOR 350.000 HEP-SPEC06: (11) = (9) x 0,00
11 350.000 / (10)
Cost of transport of 50% of delivery (50% of item 3 and 4.1) to CERN Meyrin and all-risk transport 0,00
12,1
insurance
Cost of transport of 50% of delivery (50% of item 3 and 4.2) to WIGNER and all-risk transport 0,00
12,2
insurance
TOTAL PRICE DELIVERY AT PLACE (DAP), CERN SITES: (13) = (7) + (12,1) + (12,2) 0,00
13

The shaded items are not Price Request/Information.

Options
Estimate
Item Unit price d TOTAL PRICE
DESIGNATION FCA Quantity FCA
Price for one fully equipped enclosure with an alternative Solid State Drive 0,00 0,00
model as defined in clause 5.6.12 of the technical specification, including
assembly, testing, any other charges and 3 years warranty assuming the same
A volume as in item 3.

For a server enclosure with multiple mainboards (system units) quote the price
for the fully equipped enclosure.
 This spreadsheet is provided to assiste the calculation of the
Total Cost of Ownership requested in Item (10) in the
Adjudication table. All input to this table is automatically taken
from Adjudication table and technical questionnaire. Please note
that only the information in the Tender Form has legal value.
CERN does by no means guarantee the correctness of the
formulae in this spreadsheet. CHF EUR GBP USD Other
0,0620 0,0620 0,0422 0,0657 0,0000
1,0 1,0 0,7 1,1 0,0
Electrical power cost in CHF / kVAh 0,0620 50,0 50,0 34,0 53,0 0,0
Adjudication is based on this capacity measured in HEPSPEC06 350.000 2.172,5 2.172,5 1.477,3 2.302,8 0,0
Prices in (currency) please specify currency

Cost incurred to CERN from hosting infrastructure for 4 years of running of the
supplied servers.
Electrical power
Weighted apparent power consumption in VA: 80% of automatically
apparent power consumption in VA under full load, 20% of calculated
1
apparent power consumption in VA when idle, of one
enclosure fully configured with proposed system units.
Minimum number of fully equipped enclosures required to 0
2 provide a total performance as specified in Item (3) in the
adjudication table
3 Number of system units in a fully configured enclosure 4
Total apparent power consumption in kVA: 0
4
(4) = (1) x (2) / 1000
Cost of electrical power (CHF/kVA) for 4 years of running: Please contact
(5) = 4(y) x 365(d/y) x 24 (h/d) x (0,0620) (CHF/kVAh) = CERN if
5
2172,48 CHF/kVAh specified currency
is not listed above
Total cost of electrical power for 4 years running: 0,00
6
(6) = (5) x (4)
Rack level power distribution
Number of C14 inlet power connectors on the power supply please enter
7
system value
Cost of rack level power distribution infrastructure 50 CHF per Please contact
outlet: CERN if
8
(8) = (2) * (7) x 50 CHF specified currency
is not listed above
Network connectivity
The cost of networking infrastructure is 50 CHF per Gigabit
Please contact
Ethernet port. Each system unit requires 2 ports to be
CERN if
9 connected: one for data and the second for IPMI. The total cost
specified currency
for connecting the proposed number of systems:
is not listed above
(9) = (2) x (3) x 2 x 50 CHF
Total cost of ownership for 4 years of running of supplied 0,00
servers:
10
(10) = (6) + (8) + (9)
Please enter this cost in Item (8) in the adjudication table
Bidder must specify below a complete cost breakdown of base unit in
components. CERN will use the information for potential upgrades and also for
determining insurance value when shipping parts. Please add rows for other
components if appropriate
Part number
Component type Manufacturer (manufacturer) Part number (vendor) Component price quantity
Chassis 0 0
Rails 0 0
Processor 0 0
Heat sink 0 0
Mother board 0 0
Power supply 0 0
Cooling fan 0 0
Memory 0 0
Storage drive 0 0
Backplane 0 0
 Questions unanswered #ERROR!
0 Company offer
0,1 Company name please enter value ¿?
If alternative proposal(s) submitted: Bid (Conforming bid or
0,2 please enter value
alternative proposal) ¿?
Model name and/or part number of proposed CPU server if
0,3 HNS2600KP
applicable
4 General Requirements
4,1 Hardware and Software Configurations
All enclosures and system units supplied in response to a
given purchase order have an identical hardware
4.1.1 yes
configuration, in particular the manufacturer, model, type,
revision number, firmware version, etc.
Each type of component inside the system unit is identical, in
particular all processors are identical, all memory modules
4.1.1 yes
are identical, all mainboards are identical, etc, between
system units as well as within each system unit
All hardware components are delivered with fixes for all
4.1.2 technical problems reported by their manufacturers at the yes
time of delivery
BIOS / UEFI, BMC and all other firmware versions and
4.1.2 revisions have the latest good compatible software versions yes/no
as specified by the manufacturers of each component ¿?
BIOS / UEFI, BMC and other firmware versions are not system
integrator specific (e.g.: the hardware component runs
4.1.3 yes
generic code provided by the manufacturer of that
component)
4,2 Certifications and Linux Tools Logs
4.2.1 CE compliance provided with the tender bid yes/no ¿?
Certification of the memory modules by the mainboard
4.2.2 manufacturer for use with the selected mainboard provided yes
with the tender bid
24 hours x 7 days certification on the Solid State Drives
4.2.3 yes/no
provided with the tender bid ¿?
A list of all available SMART counters for the Solid State
4.2.4 Drives, their meaning and interpretation provided with the yes/no
tender bid ¿?
If the processors require active fan(s), the certification of the
complete heat-sink fan (HSF) by the mainboard and chassis
4.2.5 yes/no/na
manufacturers for the proposed processors provided with the
tender bid ¿?
80 PLUS® certification on the power supply system provided
4.2.6 yes
with the tender bid
Detailed log output of a BIOS / UEFI update provided with
4.2.8 yes
tender bid
Detailed log output of a dump of the BIOS / UEFI
4.2.9 configuration (including resulting files) and of a restore yes/no
operation provided with tender bid ¿?
Detailed log output of a BMC firmware update operation
4.2.10 yes
provided with the tender bid
Detailed log output of a Solid State Drive firmware update
4.2.11 yes/no
provided with the tender bid ¿?
Detailed log output of the update of the "Product Asset Tag"
4.2.12 yes/no
and "Product Serial" FRU fields provided with tender bid ¿?
The bidder agrees to perform, upon request from CERN, a full
4.2.13 yes/no
Red Hat Enterprise Linux 6 certification of the systems ¿?
Detailed log output of all performance measurements
4.2.14 yes/no
required in section 9 provided with tender bid ¿?
5 Requirements on System Units
5,1 Mainboard
5,1 Manufacturer of mainboard Intel
Part number of mainboard (reference of the original
5.1 S2600KP
equipment manufacturer)
5,1 Chipset Intel® C612 Chipset (Intel® DH82029 PCH)
5,1 Total number of processor sockets on mainboard 2
5,1 Total number of memory slots on mainboard 8
Memory type(s) and speed(s) supported by mainboard and DDR4 ECC RDIMM 1600/1866/2133,
5,1
processor(s) DDR4 ECC LRDIMM 1600/1866/2133
The mainboard provides a single independent BMC compliant
5.1.1 with the Intelligent Platform Management Interface (IPMI) no
version 2.0 or above
5.1.2 The system supports PXE 2.0 or above for network booting yes
The BIOS / UEFI supports booting over the network via PXE
5.1.2 yes
before booting from the local storage drive(s)
The BIOS / UEFI provides the possibility to invoke a boot
5.1.3 device selection menu and to select the boot device at start- yes
up
The number and types of storage ports provided per system
5.1.4 10 SATA
unit
The mainboard provides connectivity for at least four ports of
5.1.4 yes
the SAS, SATA (AHCI or SCU) or NVMe type
In case SAS and SATA interfaces are provided, the version of
5.1.4 yes
the interface standard supported is at least 2.0
In cases where NVMe is being used, the corresponding
5.1.4 yes/no/na
connectors on the mid-plane are of the SFF-8639 type ¿?
5,2 Management Controller
5.2.1 The BMC is integrated on the mainboard yes
The status of the system unit does not affect the normal
5.2.1 yes/no
operation and network connectivity of the BMC ¿?
Status of the BMC does not affect the normal operation and
5.2.1 yes/no
network connectivity of the system unit ¿?
The BMC allows for the monitoring of mainboard, CPU and
5.2.2 yes
RAM temperatures, fans and power supplies
All required (analog) sensors are defined in the SDR
5.2.2 yes/no
repository of the BMC ¿?
It is possible to retrieve all SDR values through both in-band
5.2.2 yes/no
and out-of-band (remote management) interfaces
BMC records sensors events in a SEL providing at least 256
5.2.3 no
entries
5.2.3 The format of each event complies to the PET format yes/no ¿?
 The data of each event includes enhanced information
5.2.3 yes/no
allowing the identification of the event source ¿?
5.2.4 The BMC has FSC enabled yes
The BMC supports FSC configuration update through both in-
5.2.4 yes
band and out-of-band (remote management) interfaces
The FSC configuration updates take effect immediately
5.2.4 yes/no
without resetting the BMC or rebooting the system unit
The BMC supports the "last-state", "always on" and "always
5.2.5 yes/no
off" power policies
Power policy updates take effect without resetting the BMC
5.2.5 yes/no
or rebooting the system unit ¿?
The BMC supports power policy update(s) through both in-
5.2.5 yes
band and out-of-band (remote management) interfaces
The BMC supports the "power on", "power off", "hard reset",
5.2.6 "warm reboot" and "soft shutdown" power control yes
operations
The BMC supports power control operations through both in-
5.2.6 yes/no
band and out-of-band (remote management) interfaces ¿?
The BMC supports at least the "user", "operator" and
5.2.7 no
"administrator" level of authentication and authorization solo administrator y user
5.2.7 The default BMC user accounts are disabled yes
A CERN specific BMC user account will be configured using a
5.2.7 yes/no
non-standard password provided by CERN ¿?
BMC supports configuring usernames and passwords with a
5.2.8 no
length of at least 15 POSIX characters
The system supports redirecting the keyboard, video and
5.2.9 yes
mouse via virtual KVM over IP
All changes of BIOS / UEFI settings as well as the invocation of
5.2.9 the boot device selection menu and the selection of the boot yes
device are possible by using the virtual KVM over IP feature
The virtual KVM over IP feature is accessible via a web
5.2.9 yes
interface
The BMC supports encrypted access to the virtual KVM over
5.2.10 yes
IP via the network
All ports providing access to the BMC via clear-text, insecure
5.2.10protocols (such as, but not limited to, Telnet and HTTP) are no
disabled
In case the virtual KVM over IP functionality is provided via a
5.2.11Java web start application, the JAR file is digitally signed using yes/no
a certificate issued by a Certificate Authority ¿?
The validity of the certificate is of at least five years from the
date when the tender was dispatched or BMC firmware
5.2.11 yes/no
updates will be provided with a renewable certificate for a
period of at least five years ¿?
BMC supports programmatic updating of the HTTPS
5.2.12 yes/no
certificate used by its web interface via an API or shell script ¿?
BMC supports configuring users and network parameters
5.2.13 yes/no
from a command line application running locally under Linux ¿?
The BMC retains its settings, including network and access
configuration, even if the power to the system unit is cut, and
5.2.14 yes/no
is fully operational without any reconfiguration after power is
restored, regardless of the duration of the power cut ¿?
The BMC supports changing the order, at the next reboot, of
5.2.15boot devices through both in-band and out-of-band (remote yes
management) interfaces
BMC supports upgrading its firmware without requiring any
5.2.16 yes/no
physical input
BMC firmware upgrade does not affect the normal operation
5.2.17 yes/no
of the system unit ¿?
BMC firmware upgrade process does not require a reboot or
5.2.18 yes/no
power cycle of the system unit ¿?
BMC firmware upgrade process supports keeping existing
5.2.19 yes
configuration and settings
BMC firmware upgrade process does not imply any BMC MAC
5.2.20 yes/no
address change ¿?
At least one exclusively dedicated Ethernet port for the BMC,
5.2.21equipped with an RJ45 connector for copper cables (at least yes
100Base-T) is provided per system unit
The BMC interface of each system unit is directly accessible
over the network from outside of the system unit via a
standard web browser and by using the standard version of
5.2.22 yes
the ipmitool program as provided by a standard installation of
the 64-bit version of Red Hat Enterprise Linux 6 (update 6 or
later) and the 64-bit version of CentOS 7 (update 1 or later)
5,3 Processor(s)
5,3 Manufacturer of processors Intel
5,3 Part number of processors Intel® Xeon® E5-2600 V3 processors (2630L) http://ark.intel.com/es/products/64586/Intel-Xeon-Processor-E5-2630L-15M-Cache-2_00-GHz-7_20-GTs-Intel-QPI
5,3 Processor nominal frequency in MHz 2GHz ¿?
5,3 Processor turbo frequency in MHz 2.5 Ghz ¿?
5,3 Processors with integrated memory controllers yes ¿? http://www.cpu-world.com/Compare/151/Intel_Xeon_E5-2430L_vs_Intel_Xeon_E5-2630L.html
5.3.1 Number of installed processors per system unit 2 ¿?
5.3.1 At least two processors installed per system unit yes
Processors use the x86 architecture, with Intel 64 or AMD64
5.3.1 yes/no
extensions ¿?
5.3.2 Number of physical cores per processor 6 ¿?
5.3.2 Number of virtual processing units per processor 12 ¿'
5.3.2 Each processor has at least 8 physical cores no
5.3.2 Number of physical cores per system unit 12 Tiene 6
5.3.2 Number of virtual processing units per system unit 24
5.3.3 Thermal Design Power (TDP) per processor in Watts 60 ¿?
Thermal Design Power (TDP) per processor is lower or equal
5.3.3 yes
to 120 Watts
5.3.4 Total processor L2 + L3 cache size in MiB 15 ¿?
5.3.4 Processor L2 + L3 cache / physical core in MiB 2,5
Each processor has at least 2 MiB of L2 + L3 cache / physical
5.3.4 yes
core
Heat-sink fans (if any) are certified by mainboard and chassis
5.3.5 yes/no/na
manufacturers for the proposed processors ¿?
5.3.6 Processor installation instructions fully respected yes/no ¿?
5,4 Memory
5,4 Manufacturer of memory modules please enter value ¿?
5,4 Part number of memory modules please enter value ¿?
5,4 Capacity per memory module in GiB please enter value ¿?
5,4 Number of installed memory modules / system unit please enter value ¿?
5,4 Total capacity of installed RAM memory in GiB / system unit automatically calculated
Each system unit is equipped with at least 2 GiB of RAM per
5.4.1 automatically calculated
processing unit
5.4.2 Frequency at which memory is operated in MHz please enter value ¿?
5.4.2 Memory is operated at a frequency of at least 1600 MHz automatically calculated
5.4.2 RAM generation (DDR3 or DDR4) please enter value ¿?
5.4.2 Timing at which memory is operated (CAS latency) please enter value ¿?
5.4.2 Type of the memory modules (UDIMM / RDIMM / LRDIMM) please enter value ¿?
The memory modules, processors and the mainboard all
5.4.3 support the ECC technology, and ECC is fully configured and yes/no
operational ¿?
Memory modules are certified by the mainboard
5.4.4 yes/no
manufacturer for use with the selected mainboard ¿?
Memory modules report their respective serial number in the
5.4.5 yes/no
DMI fields ¿?
Interleaved memory access (at least 128 bit data) is
5.4.6 yes/no
supported and used ¿?
5.4.7 System supports NUMA yes/no ¿?
The number of memory modules installed is identical across
5.4.7 yes/no
all NUMA domains ¿?
5.4.7 At least one memory module installed per memory channel yes/no ¿?
5,5 Ethernet Network Interface(s)
5.5 Manufacturer of network interface(s) Intel
5.5 Part number of network interface(s) please enter value
5.5 Chipset of network interface(s) Intel I350
5.5.1 Number of network interface(s) 2
5.5.1 Type of network interface(s) (10GBase-T, SFP+, ...) 1000BASE-T
Network interface(s) support memory to network transfers at
5.5.1 yes/no
full Ethernet speed ¿?
Form factor of the network interface(s) (on-board,
5.5.2 on board
mezzanine, PCIe add-on, etc)
5.5.3 Network interface(s) support PXE 2.0 or above yes
All available 10 Gigabit network interfaces appear in the boot
5.5.3 yes/no
list order of the system unit's BIOS / UEFI
5,6 System Solid State Drives
5,6 Manufacturer of Solid State Drives please enter value ¿?
5,6 Part number of Solid State Drives please enter value ¿?
5.6 Manufacturer of the Solid State Drives controller please enter value ¿?
5.6 Unformatted capacity of a Solid State Drive in GB please enter value ¿?
Type and revision of the interface used by the Solid State
5.6 please enter value
Drives ¿?
5.6.1 Number of Solid State Drives installed per system unit please enter value ¿?
5.6.1 Each system unit is equipped with two Solid State Drives automatically calculated
The Solid State Drive controller and the Solid State Drive itself
5.6.2 automatically calculated
originate from the same manufacturer
Storage capacity provided by each of the Solid State Drives is
5.6.3 at least 160 GB plus an additional 20 GB per each processing automatically calculated
unit
Solid State Drives provide the same interface standard as the
5.6.4 yes/no
ports required in clause 5.1.4 ¿?
Solid State Drives are not connected to any hardware RAID
5.6.5 yes/no
dedicated controller ports ¿?
Solid State Drives are covered by a warranty of at least five
5.6.6 yes/no
years by the manufacturer ¿?
Solid State Drives are certified by the manufacturer for
5.6.7 yes/no
continuous (24 hours x 7 days) operation ¿?
Solid State Drives are equipped with a mechanism protecting
5.6.8 against data loss or data corruption during or after yes/no
unexpected power loss events ¿?
Solid State Drives provide support for SMART short and
5.6.9 yes/no
extended self-tests ¿?
Solid State Drives provide monitoring support through SMART
5.6.10 yes/no
testing, counters and error logging ¿?
Solid State Drives provide dedicated SMART counters for
monitoring at least the following attributes: the number of
reallocated sectors (retired blocks), the number of program
5.6.10 yes/no
and erase failures, number of unexpected power loss events,
the number of un-correctable errors, amount of host writes
and the overall flash wear level ¿?
The chosen combination of Solid State Drives and controllers
5.6.11provides support for upgrading the storage drive firmware in yes/no
place using a Linux binary ¿?
5.6.12Mandatory Option for an Alternative Solid State Drive Model
5.6.12Manufacturer of alternative Solid State Drives please enter value ¿?
5.6.12Part number of alternative Solid State Drives please enter value ¿?
5.6.12Manufacturer of the alternative Solid State Drives controller please enter value ¿?
5.6.12Unformatted capacity of an alternative Solid State Drive in GB please enter value ¿?
Type and revision of the interface used by the alternative
5.6.12 please enter value
Solid State Drives ¿?
5.6.12Number of alternative Solid State Drives per system unit please enter value ¿?
Each system unit is equipped with two alternative Solid State
5.6.12 automatically calculated
Drives ¿?
Storage capacity provided by each of the alternative Solid
5.6.12State Drives is at least 160 GB plus an additional 20 GB per automatically calculated
each processing unit ¿?
Alternative Solid State Drives provide the same interface
5.6.12 yes/no
standard as the ports required in clause 5.1.4 ¿?
Alternative Solid State Drives are not connected to any
5.6.12 yes/no
hardware RAID dedicated controller ports ¿?
Alternative Solid State Drives covered by a warranty of at
5.6.12 yes/no
least five years by the manufacturer ¿?
Alternative Solid State Drives are certified by the
5.6.12 yes/no
manufacturer for continuous (24 hours x 7 days) operation ¿?
Alternative Solid State Drives are equipped with a mechanism
5.6.12protecting against data loss or data corruption during or after yes/no
unexpected power loss events ¿?
 Alternative Solid State Drives provide support for SMART
5.6.12 yes/no
short and extended self-tests ¿?
Alternative Solid State Drives provide monitoring support
5.6.12 yes/no
through SMART testing, counters and error logging ¿?
Alternative Solid State Drives provide dedicated SMART
counters for monitoring at least the following attributes: the
number of reallocated sectors (retired blocks), the number of
5.6.12 yes/no
program and erase failures, number of unexpected power
loss events, the number of un-correctable errors, amount of
host writes and the overall flash wear level ¿?
The chosen combination of alternative Solid State Drives and
5.6.12controllers provides support for upgrading the storage drive yes/no
firmware in place using a Linux binary ¿?
5,7 PCIe Connectivity
Describe the PCIe connectivity:
<CPU Socket ID: PCIe Slot type: PCIe lanes: PCIe Gen>
5,7 Example: Use space below
CPU Socket #1: x16: x16: 3.0
CPU Socket #1: x16: x8: 3.0

CPU Socket #1: x16: x16: 3.0

CPU Socket #2:x 24: x24: 3.0
CPU Socket #3::x24 x24: 3.0
5.7.1 Total number of PCIe slots available per system unit 3
5.7.1 Number of electrical PCIe lanes available for each slot 16/24/24
5.7.1 Physical size of each PCIe slot (number of lanes) 16/24/24
5.7.1 Version of the PCIe bus per available slot 3.0
At least one PCIe 2.0 or later, x8 or x16 slot providing 8 or 16
5.7.1 yes
lanes is available per system unit
5.7.2 Riser card used for PCIe slot(s) yes
5.7.2 In case a riser card is used, it is of the passive type no
5.8 Miscellaneous Requirements on System Units
The CERN contract number is recorded in the "Product Asset
5.8.1 Tag" field of the FRU of the BMC of each system unit and in yes/no
the DMI fields of the BIOS / UEFI ¿?
The serial number of each system unit is recorded in the
5.8.2 "Product Serial" of the FRU of the BMC of each system unit yes/no
and in the DMI fields of the BIOS / UEFI ¿?
Each system unit is identified by a label displaying the
5.8.3 contract number and a unique serial number in a text and yes/no
barcode format ¿?
5,9 Upgrade with Journal Solid State Drives
5,9 Manufacturer of journal Solid State Drives please enter value ¿?
5,9 Part number of journal Solid State Drives please enter value ¿?
5,9 Manufacturer of the journal Solid State Drives controller please enter value ¿?
5,9 Unformatted capacity of a journal Solid State Drive in GB please enter value ¿?
Type and revision of the interface used by the journal Solid
5,9 please enter value
State Drives ¿?
Number of journal Solid State Drives per system unit requiring
5,9 please enter value
them ¿?
5.9 Two journal Solid State Drives per system unit requiring them automatically calculated
Journal Solid State Drives provide the same interface
5,9 yes/no
standard as the ports required in clause 5.1.4 ¿?
Journal Solid State Drives are not connected to any hardware
5,9 yes/no
RAID dedicated controller ports ¿?
Journal Solid State Drives covered by a warranty of at least
5,9 yes/no
five years by the manufacturer ¿?
Journal Solid State Drives are certified by the manufacturer
5,9 yes/no
for continuous (24 hours x 7 days) operation ¿?
Journal Solid State Drives are equipped with a mechanism
5,9 protecting against data loss or data corruption during or after yes/no
unexpected power loss events ¿?
Journal Solid State Drives provide support for SMART short
5,9 yes/no
and extended self-tests ¿?
Journal Solid State Drives provide monitoring support through
5,9 yes/no
SMART testing, counters and error logging ¿?
Journal Solid State Drives provide dedicated SMART counters
for monitoring at least the following attributes: the number
of reallocated sectors (retired blocks), the number of program
5,9 yes/no
and erase failures, number of unexpected power loss events,
the number of un-correctable errors, amount of host writes
and an indication of the overall flash wear level ¿?
The chosen combination of journal Solid State Drives and
5,9 controllers provides support for upgrading the storage drive yes/no
firmware in place using a Linux binary ¿?
The journal Solid State Drive controller and the Solid State
5.9.2 automatically calculated
Drive itself originate from the same manufacturer
The endurance of the journal Solid State Drives in terms of
5.9.3 please enter value
complete drive writes per day over a period of five years ¿?
The journal Solid State Drives provide an endurance of at
5.9.3 least three complete drive writes per day over a period of five automatically calculated
years
Storage capacity provided by each of the journal Solid State
5.9.4 automatically calculated
Drives is at least 200 GB
5.10 Upgrade with an LSI 9207-8e SAS Host Bus Adapter
5.10.1The SAS Host Bus Adapter is the LSI 9207-8e yes/no ¿?
Contractor will install the SAS Host Bus Adapters inside the
5.10.3 yes/no
system units as requested by CERN at order time ¿?
6 Requirements on Enclosures
6,1 Physical Requirements
6.1 Manufacturer of enclosure Intel
Part number of enclosure (reference of the original
6.1 please enter value
equipment manufacturer)
6.1 Width of enclosure in cm 43,8
6.1 Height of enclosure in cm 8,79
6.1 Depth of enclosure in cm 77,1
6.1.1 Enclosure is at most 79 cm deep yes
6.1.1 Enclosure is mountable in industry-standard 19-inch racks yes
6.1.2 Enclosure height in U sizes 2
6.1.2 Enclosure is at most 10U high yes
6.1.2 Weight in kg of a fully configured enclosure 21
 Weight of a fully configured enclosure is less or equal to 150
6.1.2 yes
kg
6.1.3 Number of system units in a fully configured enclosure 4
6.1.3 Enclosure contains at least 2 system units / U yes
System units and enclosures designed such that in case a
6.1.4 system unit needs to be removed or serviced, the operation yes
of no other system unit is affected
The enclosure is specified by its manufacturer for use with
6.1.5 yes
the type and size of system unit proposed
The bidder's proposal to achieve 350 000 HEP-SPEC06 fits in a
6.1.6 yes/no
power envelope of at most 350 000 Watts ¿?
6,2 Rails
6.2.1 Rails provided yes
6.2.1 Brand and model of rails please enter value
6.2.1 Length of rails in cm 76,2
6.2.1 The length of the rails does not exceed 81 cm yes
The weight rating of the proposed rails is larger than the
6.2.1 yes/no
weight of a fully equipped enclosure ¿?
Distance between front and rear screw poles of 19-inch rack
6.2.1 please enter value
supported by telescopic rails (minimum and maximum in cm) ¿?
To access system units the enclosure needs to be moved out
6.2.2 yes/no
of its place in a fully configured 19-inch rack ¿?
6.2.2 Rails are telescopic yes/no ¿?
In case the rails are telescopic, they are equipped with a
6.2.2 protection against accidentally pulling out entirely the inner yes/no/na
part of the rails ¿?
The rails support the weight of a fully populated and fully
6.2.2 yes/no
pulled out enclosure without bending ¿?
The rails remain in fully working state following at least 50
6.2.3 pull-out / push-in operations, using a fully configured yes/no
enclosure ¿?
6,3 Power Supplies and Cooling
6.3 Brand and model of power supply system please enter value ¿?
6.3 Power rating of power supply system in Watts 1200W and 1600W
The number and type of fans in enclosure other than the one
6.3.13 1+1 W 73.5mm x L 265.0mm x H 39/40mm.
(s) on processors and in power supplies
The power supply system meets the requirements specified
6.3.1 by the mainboard manufacturer and those specified for all yes
components within the enclosure
The power supply system is equipped with Active Power
6.3.2 Factor Compensation in compliance with International yes
Standard IEC 61000
6.3.3 Power supplies used are 80 PLUS® certified yes
6.3.4 For a fully loaded system the power factor is 0.9 or better automatically calculated
6.3.5 Redundant N + N power supplies used yes
6.3.6 The power supply modules are hot-swappable yes
The power supply system is designed such that neither the
failure nor the replacement of any single power supply
6.3.7 yes/no
module adversely affects the performance or operation of the
system when fully loaded ¿?
All system units are able to continue to boot and operate at
full performance even when the enclosure is experiencing a
6.3.8 failure on half of the power supply modules or when yes/no
experiencing a power feed problem to half of the power
supply modules ¿?
Number of C14 inlet power connectors on the power supply
6.3.9 please enter value
system ¿?
6.3.9 Even number of C14 inlet power connectors automatically calculated
6.3.10Enclosures delivered without any power cables yes/no ¿?
Cooling system designed for reliable operation of the
enclosure and all installed components when installed in a full
6.3.11 yes/no
rack in a machine room in which the inlet air temperature is
within the range 14˚ C - 35˚ C
6.3.11Hot air exhausted only through the rear of the enclosure yes/no
The power system is dimensioned such that when running
under full load the total power consumption for the enclosure
6.3.12 yes/no
and the system units does not exceed 95% of the combined
power rating of half of the power supply modules.
All fans in the enclosure are redundant except those for
6.3.13 yes/no
processors and power supplies
6,4 Connectivity
USB connector(s) for keyboard and mouse provided for each
6.4.1 yes
system unit
6.4.2 USB type A receptacle(s) provided for each system unit yes/no ¿?
Number of USB type A receptacles per system unit (be sure
6.4.2 not to include USB type A receptacles already counted for please enter value
keyboard and mouse connections) ¿?
6.4.2 Version of the USB standard supported 2,0
6.4.2 Support for USB version 2.0 or above yes
Booting from USB devices (such as, but not limited to, USB
6.4.2 yes
flash drives, CD-ROM drives) supported
6.4.3 Type of VGA connector(s) video out (DB-15)
6.4.3 Number of VGA connector(s) per system unit 1
At least one standard VGA connector provided per system
6.4.3 yes
unit
RJ45 connector(s) provided for 10 Gigabit Ethernet
6.4.4 no
connectivity
6.4.4 RJ45 connector(s) provided for dedicated IPMI connectivity yes/no
Total number of RJ45 connectors for 10 Gigabit Ethernet
6.4.4 3
connectivity per enclosure
Number of RJ45 connectors for 10 Gigabit Ethernet
6.4.4 0
connectivity per system unit
Total number of RJ45 connectors for dedicated IPMI
6.4.4 please enter value
connectivity per enclosure
Number of RJ45 connectors for dedicated IPMI connectivity
6.4.4 please enter value
per system unit
Enclosure contains any integrated Ethernet pass-thru or
6.4.4 yes/no
network switches
 Adapter required for any of the connections specified in this
6.4.5 yes/no
section
If adapters are required specify the number and type of
6.4.5 please enter value
provided adapters
6.4.5 Adapters provided for all connections that require one yes/no/na
6.4.6 All connectors at the rear of the enclosure yes/no
6.4.6 All connectors clearly marked at the rear of the enclosure yes
6,5 Buttons and Indicators
Per system unit at least one power on/off button is accessible
6.5.1 yes
from the front of the enclosure

Per system unit an indicator for the power state is provided

6.5.2 yes
on the front of the enclosure
Indicators for Solid State Drive activity provided on the front
6.5.2 yes/no
of the enclosure ¿?
Per system unit, indicator(s) for the identification and system
6.5.3 fault are provided and are visible from the front of the yes
enclosure
6,6 Storage Drive Trays
Number of fully functional and connected storage drive trays
6.6 16
per enclosure
Number of fully functional and connected storage drive trays
6.6 4
per system unit

6.6.1 All storage drive trays are hot-swappable yes

6.6.2 All storage drive trays provide activity indicators yes

6.6.3 All storage drive trays are of the 2.5" type yes
All storage drive trays are fitted inside the enclosure and all
non-populated storage drive trays are ready to accept drives
6.6.4 yes
(it is not permitted to have non-populated storage drive trays
replaced with blanks)
A total of at least four fully functional and connected storage
6.6.5 yes
drive trays per system unit
6.7 Mid-plane(s)
A mid-plane is used to provide power and data connections
6.7.1 yes/no
between the Solid State Drives and the mainboards ¿?
Mid-plane supports the interface standard defined in clause
6.7.1 yes/no/na
5.1.4 ¿?
6,8 Miscellaneous Requirements on Enclosures
Each enclosure has a label that's visible when the enclosure is
6.8.1 installed in a 19-inch rack, with the contract number and a yes/no
unique serial number in a text and barcode format ¿?
6.8.1 Any additional information on the label is written in English yes/no ¿?
The airflow efficiency is not reduced by the positioning of
6.8.2 yes/no
labels ¿?
7 Common Requirements on Enclosures and System Units
7.1 General Requirements
7.1.1 Internal cables are not pinched nor stretched yes/no ¿?
It is possible to disable or acknowledge any audible alarms of
7.1.2 yes/no
the enclosure and the system units ¿?
7.1.3 Installation instructions for all components are fully respected yes/no ¿?
In case of assembly from OEM parts, it complies with the
7.1.4 yes/no
specifications of each original manufacturer ¿?
All screws are tightened to an adequate torque, ensuring
7.1.5 yes/no
sufficient but not excessive tightening ¿?
8 Software and Documentation Requirements
8,1 Operating Systems
The system units and enclosures are guaranteed to operate
and to provide the full functionality required by the technical
specification under the 64-bit version of Red Hat Enterprise
8.1.1 yes
Linux 6 Server (update 6 or later) and the 64-bit version of
CentOS 7 (update 1 or later) without requiring any additional
driver or software, even at installation time
The systems are able to boot the 64-bit version of Red Hat
Enterprise Linux 6 Server (update 6 or later) and the 64-bit
8.1.2 yes
version of CentOS 7 (update 1 or later) without keyboard,
screen, mouse, or serial console attached
The systems are guaranteed to operate and to provide the
8.1.3 full functionality required by the technical specification under yes
the 64-bit version of Microsoft Windows Server 2012 R2
Additional drivers not included in the 64-bit version of
8.1.3 Microsoft Windows Server 2012 R2 are provided and are yes
Microsoft certified and digitally signed
The systems are able to boot the 64-bit version of Microsoft
8.1.4 Windows Server 2012 R2 without keyboard, screen, mouse, yes
or serial console attached
8,2 Settings
All equivalent components (system units, enclosures)
delivered with identical settings, in particular internal drive
8.2.1 yes/no
configurations, firmware (e.g. BIOS / UEFI, BMC) revision
levels, NVRAM settings and jumper settings are all the same
8.2.1 All settings configured as specified by CERN yes/no
The contractor will contact CERN for the desired settings prior
8.2.2 yes/no
to delivery
The contractor will provide CERN with remote access (SSH
8.2.3 and virtual KVM over IP) to the first fully configured system yes/no
prior to delivery
Remote access will be provided either on dedicated public IP
8.2.3 addresses or through a VPN connection, using a broadband yes/no
Internet connection
8,3 Linux Flash Tools and BIOS / Firmware Images
The BIOS / UEFI image file is provided with the evaluation
8.3.1 yes/no
samples and at delivery time
The CERN customized CMOS settings are provided with the
8.3.1 yes/no
evaluation samples and at delivery time
The BMC firmware file is provided with the evaluation
8.3.1 yes/no
samples and at delivery time
The firmware files for the storage drives are provided with
8.3.1 yes/no
the evaluation samples and at delivery time
 The firmware files for the SAS / SATA / NVMe internal
8.3.1 controller are provided with the evaluation samples and at yes/no
delivery time
A Linux flash tool for the BIOS / UEFI is provided with the
8.3.2 yes/no
evaluation samples and at delivery time
A Linux flash tool for the BMC is provided with the evaluation
8.3.2 yes/no
samples and at delivery time
A Linux flash tool for the storage drives is provided with the
8.3.2 yes/no
evaluation samples and at delivery time
A Linux flash tool for the SAS / SATA / NVMe internal
8.3.2 controller, if any, is provided with the evaluation samples and yes/no
at delivery time
All other firmware files used by the system and the associated
8.3.2 flash tools not explicitly mentioned above will be provided yes/no
with the evaluation samples and at delivery time
All command line tools are able to run in an automated
fashion locally under the 64-bit version of Red Hat Enterprise
8.3.2 Linux 6 and the 64-bit version of CentOS 7 (update 1 or later) yes/no
without requiring recompiling or specific drivers for different
kernel versions
The BIOS / UEFI command line tool allows exporting the BIOS
8.3.3 settings in a human readable format, including a detailed yes/no
value-meaning description for each setting
8.3.4 The BIOS / UEFI requires a license to run yes/no
The license is provided together with the evaluation samples
8.3.4 yes/no/na
and at delivery time, for each system unit
The license fee, if any, is included in the price of the system
8.3.4 yes/no/na
units
The BIOS / UEFI command line tool allows for BIOS / UEFI
8.3.5 yes/no
updates preserving the existing BIOS / UEFI settings
Linux tools allowing information to be written in the FRU
8.3.6 fields of the BMC and in the DMI fields of the BIOS / UEFI are yes/no
provided with the evaluation samples and at delivery time
The tool for writing into the FRU and DMI fields runs locally
under the 64-bit version of Red Hat Enterprise Linux 6 and the
8.3.6 64-bit version of CentOS 7 (update 1 or later) without yes/no
requiring any recompilation or specific drivers for different
kernel versions
8,4 Documentation
A complete set of documentation materials and manuals,
written in English, for the system units and enclosures, in PDF
8.4.1 yes/no
or HTML format, provided with the evaluation samples and at
delivery time
The contractor grants CERN the right to redistribute these
8.4.1 yes/no
manuals as required for operational purposes
The documentation includes full specifications with detailed
8.4.2 technical drawings of components and cabling required for yes/no
failure analysis performed by CERN
The documentation includes pictures of a fully configured
8.4.3 yes/no
enclosure (all external and internal sides / views)
The documentation includes pictures of a fully configured
8.4.4 yes/no
system unit
One electronic configuration sheet for the whole order
providing at least the serial number and Ethernet MAC
8.4.5 address(es) of each system unit, detailing the interface type yes/no
(Gigabit Ethernet, 10 Gigabit Ethernet, IPMI), using the
template provided by CERN
The order of system units on the configuration sheet matches
8.4.6 their order within the enclosure as specified and marked by yes/no
the manufacturer
All external packaging such as, but not limited to, cardboard
boxes and palette wrappings carry a label with the contract
8.4.7 yes/no
number and serial number(s) of the enclosure(s) and system
units(s) contained
The tools, firmware files and documentation will be uploaded
8.4.8 yes/no
to CERN servers using a file hosting service provided by CERN
The files will remain accessible online for CERN throughout
8.4.8 yes/no
the entire warranty period of the supply
9 Performance Measurements
9,1 General Requirements
Benchmark system(s) installed with the 64-bit version of
9.1.3 Scientific Linux CERN 6 (update 6 or later) as described at yes/no
http://cern.ch/it-procurements/IT-4137
All performance requirements met with the 64-bit version of
Scientific Linux CERN 6 (update 6 or later) as installed by
9.1.3 yes/no
default, without changing any kernel parameters, drivers,
library versions, etc.
The system compiler, gcc version 4.4.x installed by 64-bit
9.1.3 version of Scientific Linux CERN 6 (update 6 or later) used for yes/no
all benchmark compilations
Benchmark system(s) configured according to the settings
9.1.4 yes/no
specified in http://cern.ch/it-procurements/IT-4137/setup
9,2 Computing Performance
System performance measured using the SPEC CPU2006 v1.2
9.2.1 benchmark suite with the configuration file supplied by CERN, yes/no
as specified at http://cern.ch/it-procurements/IT-4137/spec
Number of SPEC CPU2006 benchmark processes executed in
9.2.2 please enter value
parallel
The SPEC CPU2006 benchmark executed in parallel as many
9.2.2 automatically calculated
times as there are virtual processing units on the system unit
Average system performance in HEP-SPEC06 for a single
9.2.3 system unit (i.e. a computing unit based on a single please enter value
mainboard).
Average system performance in HEP-SPEC06 for a single
system unit (i.e. a computing unit based on a single
9.2.3 please enter value
mainboard) while running with only half of the power
supplies connected.
The SPEC CPU2006 benchmark has been executed in parallel
9.2.3 across all system units inside the enclosure, using three yes/no
consecutive runs
The HEP-SPEC06 result provided above is the average of all
9.2.3 yes/no
runs, across all system units inside the enclosure
9,3 Storage Performance
Flexible IO tester (FIO) benchmark suite used for storage
performance benchmarking using the configuration file
9.3.1 yes/no
supplied by CERN, as specified in http://cern.ch/it-
procurements/IT-4137/fio
Benchmarked IOPS using 1 writer and a 4 KB block size for
9.3.1 please enter value
system SSD
System SSD provides at least 6000 IOPS using 1 writer and a 4
9.3.1 automatically calculated
KB block size
Benchmarked IOPS using 5 writers and a 4 KB block size for
9.3.1 please enter value
system SSD
System SSD provides at least 12000 IOPS using 5 writers and a
9.3.1 automatically calculated
4 KB block size
Benchmarked IOPS using 1 writers and a 512 KB block size for
9.3.1 please enter value
system SSD
System SSD provides at least 500 IOPS using 1 writer and a
9.3.1 automatically calculated
512 KB block size
Benchmarked IOPS using 1 writer and a 4 KB block size for
9.3.1 please enter value
alternative system SSD
Alternative system SSD provides at least 6000 IOPS using 1
9.3.1 automatically calculated
writer and a 4 KB block size
Benchmarked IOPS using 5 writers and a 4 KB block size for
9.3.1 please enter value
alternative system SSD
Alternative system SSD provides at least 12000 IOPS using 5
9.3.1 automatically calculated
writers and a 4 KB block size
Benchmarked IOPS using 1 writers and a 512 KB block size for
9.3.1 please enter value
alternative system SSD
Alternativev system SSD provides at least 500 IOPS using 1
9.3.1 automatically calculated
writer and a 512 KB block size
Benchmarked IOPS using 1 writer and a 4 KB block size for
9.3.1 please enter value
journal SSD
Journal SSD provides at least 6000 IOPS using 1 writer and a 4
9.3.1 automatically calculated
KB block size
Benchmarked IOPS using 5 writers and a 4 KB block size for
9.3.1 please enter value
journal SSD
Journal SSD provides at least 14000 IOPS using 5 writers and a
9.3.1 automatically calculated
4 KB block size
Benchmarked IOPS using 1 writers and a 512 KB block size for
9.3.1 please enter value
journal SSD
Journal SSD provides at least 670 IOPS using 1 writer and a
9.3.1 automatically calculated
512 KB block size
9,4 Power Consumption
Power consumption measured as described at http://cern.
9,4 yes/no
ch/it-procurements/IT-4137/power
Describe the measurement setup, in particular give details
9,4 Use space below
about the power meter

please enter value

Apparent power consumption in VA under full load of one
9,4 please enter value
enclosure fully configured with proposed system units
Active (real) power consumption in W under full load of one
9,4 please enter value
enclosure fully configured with proposed system units
Power factor under full load of one enclosure fully configured
9,4 please enter value
with proposed system units
Apparent power consumption in VA when idle of one
9,4 please enter value
enclosure fully configured with proposed system units
Active (real) power consumption in W when idle of one
9,4 please enter value
enclosure fully configured with proposed system units
Power factor when idle of one enclosure fully configured with
9,4 please enter value
proposed system units
Weighted apparent power consumption in VA: 80% of
apparent power consumption in VA under full load, 20% of
9,4 automatically calculated
apparent power consumption in VA when idle, of one
enclosure fully configured with proposed system units.
10 Delivery
10,1 Requirements on the Delivery of Bid Evaluation Sample Units
Upon the request of CERN, the bidder will provide, at no cost
for CERN, two samples of the bidding configuration (one
including the upgrades corresponding to sections 5.9 and 5.10
of the technical specification) that are identical in every
10.1.1respect to the configuration described in the technical yes/no
questionnaire and tender form and are set up according to
CERN’s specifications so that CERN will be able to evaluate
whether the systems are compliant with the tender
documents
If the proposed configuration foresees more than one system
unit per enclosure, enclosures fully equipped with system
10.1.2 yes/no
units will be made available to CERN on request within one
week of this request
Documentation for the samples provided according to the
10.1.3technical specification; in particular, configuration sheets will yes/no
be provided
The contractor will contact CERN for the desired settings prior
10.1.4to delivering the evaluation samples and will deliver the yes/no
evaluation samples according to CERN’s specifications
10,2 Requirements on Contract Delivery
The system units within the first production enclosure will be
installed with the 64-bit version of Scientific Linux CERN 6
10.2.1(update 6 or later) and will have a fully working virtual KVM yes/no
over IP and SSH connection. Remote access will be provided
for CERN to these first production systems.
The contractor will fulfil the instructions provided in the
"Delivery Instructions and Hardware Configuration"
10.2.2 yes/no
document provided by CERN and will supply the computing
equipment as requested in this document
 If CERN orders DAP (Delivered At Place), delivery of the
10.2.3complete enclosures will be done within ten weeks from the yes/no
date of dispatch of the contract
If CERN orders FCA (Free Carrier), the contractor will provide
all required information to, and arrange transport with the
transport agent nominated by CERN within eight weeks from
10.2.4 yes/no
the date of the contract, and will make the complete
enclosures available for shipment within nine weeks from the
date of the contract
The contractor will ensure that the enclosures and system
10.2.5 yes/no
units are delivered fully assembled
The outer parts (those to be mounted in the 19-inch rack) of
10.2.7the rails delivered, or their shipment arranged, as yes/no
appropriate, two weeks ahead of the CPU servers
The inner parts of the rails delivered already mounted to the
10.2.7 yes/no
enclosures
Contractor accepts that if outer parts of the rails are not
delivered, or their shipment arranged, as appropriate, two
10.2.8 yes/no
weeks ahead of the systems, the acceptance period will be
extended by two weeks
Contractor accepts that if inner parts of the rails are not
10.2.8delivered already mounted to the enclosures the acceptance yes/no
period will be extended by two weeks
The initial stock of spare parts will be part of the delivery of
10.2.9 yes/no
the complete systems
11 Acceptance
11,1 General Terms
Contractor accepts that if any of the acceptance tests carried
out establish that any of the systems concerned are not in
proper condition, do not perform properly or in any other
respect are not in conformity with the tender bid and the
11.1.3 yes/no
contract, the contractor must forthwith and at his own
expense take the necessary measures to ensure the proper
condition and performance of the CPU servers and their
conformity with the tender bid and the contract
Contractor accepts that the time between CERN notifying the
contractor of the non-conformity of the CPU servers and the
contractor notifying CERN of the successful completion of the
11.1.3corrective measures, may, at CERN’s discretion, be yes/no
considered as part of the delivery time (with potential
consequences on penalties for late delivery as described in
the tender form)
Contractor accepts that on CERN’s request, measures to
ensure full compliance of delivered systems with the tender
11.1.3 yes/no
bid and the contract must be performed by the contractor
rather than a subcontractor
Contractor accepts that if any of the acceptance tests carried
out establish that more than 10% of the CPU servers are not
in proper condition, do not perform properly or in any other
respect are not in conformity with the tender bid and the
11.1.4 yes/no
contract, CERN will have the right, at its discretion, either to
terminate the contract, or to require the contractor to
replace all systems of the faulty delivery by new ones at the
contractor’s expense
Contractor accepts that if any of the acceptance tests carried
out establish that the CPU servers provide lower performance
than the minimum required or consume more power than the
11.1.5bidder indicated in the tender bid, CERN will have the right, at yes/no
its discretion, either to terminate the contract, or to require
financial compensation from the contractor as described in
the tender form
12 Warranty
12,1 General Terms
How will warranty be guaranteed when the original
12.1.1 Use space below
equipment is no longer available due to obsolescence?

please enter value

If for any reason the manufacturing of the original equipment
12.1.2 yes/no
will be discontinued, the contractor will notify CERN in writing
Contractor accepts that if more than 10% of the system units
do not perform properly or in any other respect are not in
conformity with the contract during the three months after
acceptance, CERN reserves the right, at its discretion, either
12.1.3to return the systems and be reimbursed by the contractor, yes/no
or to require the contractor to replace all systems of the
faulty delivery by new systems at the contractor’s expense. In
the latter case, these new systems will be subjected to
acceptance tests.
Contractor accepts that if any system experiences hardware
failures more than twice during any period of six months
12.1.4within the warranty period, CERN is entitled to require that yes/no
system to be replaced by a new system at the contractor’s
expense
Contractor accepts that if 20% of systems fail due to a
systematic issue with the same component type during any
period of six months within the warranty period, CERN has
the right, at its discretion, either to return the servers and be
12.1.5 yes/no
reimbursed by the contractor or to require that all identical
components be replaced at the contractor’s expense. In the
latter case, these new components will be subjected to
acceptance tests.
Contractor accepts warranty responsibility, without any
additional charge to CERN, for the systems as delivered even
12.1.6if third-party devices have been added to the system units or yes/no
enclosures, without requiring these third-party devices to be
removed before commencing investigations or repair
 In addition to replacing non-functional or otherwise obviously
faulty drives, the contractor accepts replacements of drives
12.1.7under warranty upon any of the conditions described in yes/no
clause 12.1.7 of the technical specifications (SMART tests and
failures)
Contractor accepts that any server that has undergone a
repair or exchange must remain fully compliant with the
technical specification. In particular, the hardware
configuration will remain identical to the other system units
12.1.8 yes/no
and / or enclosures of the same delivery, and replacement
components will be equipped with the firmware revision
levels and NVRAM and jumper settings specified by CERN at
the time of the contract
Contractor accepts that deviations from hardware brands,
12.1.8types or revisions, or firmware revisions and NVRAM and yes/no
jumper settings require the written approval by CERN
12,2 Warranty Service
Contractor accepts that failure analysis and repairs will be
12.2.1 yes/no
performed by CERN without voiding the warranty
Contractor accepts that CERN's repair technicians can replace
12.2.1components on the supplied system units and enclosures yes/no
without voiding the warranty
The bid includes the cost for an initial stock of spare parts and
12.2.2 yes/no
fully configured standby replacement enclosures
Contractor’s estimated initial stock quantity of standby units,
storage drives, memory modules, power supply units, cooling
fans, processors, pluggable network interface cards, SAS
12.2.2cables, etc. The stock must be sized based on the number of Use space below
units or required capacity specified in the commercial tender
form and the price for this initial stock must be entered into
the adjudication table.

please enter value

The contractor accepts to cover all shipping cost of
12.2.3replacement parts and standby units to and from CERN yes/no
throughout the full warranty period
The size of the stock of spare parts detailed above is based on
12.2.3contractors estimates to cover expected failures of the yes/no
delivered hardware for a period of at least two months
The "Component breakdown" sheet has been filled in with
12.2.4 yes/no
the price of each component
The contractor accepts to provide warranty coverage for the
delivered hardware, replacement parts and standby
12.2.5 yes/no
replacement units for a period of three years, starting from
the date of acceptance
The contractor accepts to send replacement parts and
standby units, at the contractor’s expense, at a monthly
12.2.6 yes/no
frequency or at a higher frequency in case the initial stock
was insufficiently sized by the contractor
The contractor accepts that CERN reserves the right to carry
12.2.7out remedial measures to delay(s) on shipping replacement yes/no
parts
On-site destruction and / or non-return of failed hard disks
12.2.8 yes/no
invalidate the off-site warranty
If on-site destruction can be permitted under special
12.2.8conditions without invalidating the off-site warranty, specify Use space below
those conditions here

please enter value

13 Safety
13,1 Safety Requirements Concerning Design of Products
The supply complies with the Directive Restriction of
13.1.1 yes/no
Hazardous Substances Directive RoHS (Directive 2011/65/EU)
The supply complies with the Low Voltage Directive
13.1.1 yes/no
(2006/95/EC or 2014/35/EU)
The supply complies with European and host countries
13.1.2 yes/no
regulation
The supply complies with CERN Safety rules (available at the
link http://cern.ch/safety-rules), in particular with IS 23:
13.1.3Criteria and Standard Test Methods for the Selection of yes/no
Electric Cables and Wires with Respect to Fire Safety and
Radiation Resistance
End