HPE and Dell Server Procurement in Bosnia and Herzegovina: A Buyer’s Guide

Buying enterprise server hardware in Bosnia and Herzegovina is rarely a simple transaction. Whether you represent a public institution bound by the Law on Public Procurement, a bank working through a structured capital expenditure process, or a municipal authority preparing your first formal tender for IT infrastructure, the path from recognizing a need to deploying a functioning server environment involves layers of technical, legal, and commercial complexity that can quietly undermine even well-intentioned projects.

This guide is written for procurement managers, IT administrators, finance officers, and project leads at organizations in BiH who are evaluating HPE or Dell server hardware, either through an open tender process or through direct commercial procurement. It covers what to specify, what to watch for in warranty and SLA terms, how the public procurement framework shapes the process, and what distinguishes a sound procurement from one that creates problems after delivery.

Why HPE and Dell Dominate Enterprise Server Procurement in BiH

When BiH public institutions and private sector organizations tender for server infrastructure, two vendor families account for the overwhelming majority of specifications: Hewlett Packard Enterprise (HPE) and Dell Technologies (formerly Dell EMC). This is not accidental.

Both vendors maintain extensive authorized reseller and service partner networks in the Western Balkans region. Both offer product lines that map well to the scale and budget parameters typical of BiH public sector projects, from entry-level rack servers for small municipal deployments through to dense blade infrastructure for banking data centers. Both carry active warranty and support structures that can be verified, extended, and contractually anchored within a public tender.

For procurement purposes, the key distinction is that these are vendor ecosystems, not just product lines. When you procure an HPE ProLiant server, you are also procuring access to HPE’s support infrastructure: Pointnext services, parts availability, certified engineers, and escalation paths that extend across the region. The same applies to Dell’s ProSupport framework. Specifying the hardware without anchoring the support terms is one of the most common and costly mistakes organizations make in this region.

Public Procurement Framework: What the ZJN Requires

For public sector buyers (state institutions, cantonal authorities, municipalities, public enterprises, and state-owned companies) server procurement in Bosnia and Herzegovina is governed by the Law on Public Procurement of Bosnia and Herzegovina (Zakon o javnim nabavkama, ZJN). The law aligns substantially with EU procurement directives and establishes thresholds, procedure types, and documentation requirements that shape every aspect of how an HPE or Dell server tender must be structured.

Key Thresholds to Know

The ZJN establishes value thresholds that determine which procurement procedure applies. For goods and services contracts, the direct agreement procedure applies below approximately 6,000 BAM, while competitive procurement procedures (restricted, open, or negotiated depending on justification) apply above this threshold. Server infrastructure almost invariably falls into competitive procedure territory, meaning a formal public tender with defined technical specifications, evaluation criteria, and publication obligations.

For contracts above EU threshold values, additional obligations apply, including publication in the Official Gazette of BiH and compliance with stricter documentation and standstill requirements.

Writing the Technical Specification

This is where many public procurement processes for server hardware go wrong. The ZJN explicitly prohibits technical specifications that reference a specific brand, trademark, patent, or origin — the intent being to prevent specifications written around a preferred vendor’s model numbers. In practice, this means your tender documentation must specify performance parameters, technical characteristics, and compatibility requirements rather than simply listing “HPE ProLiant DL380 Gen11” as the required item.

A well-written technical specification for a rack server might include:

  • Processor type and minimum performance benchmark (e.g., minimum two-socket configuration, a defined number of cores per processor, minimum clock speed or benchmark score)
  • Memory capacity and type (e.g., minimum 64 GB DDR5 ECC RAM, expandable to defined maximum)
  • Storage configuration (e.g., minimum four 2.5″ drive bays, support for NVMe and SAS/SATA, defined RAID controller capability)
  • Network interface requirements (e.g., minimum dual-port 10GbE on-board, with specific form factor for expansion)
  • Management interface (out-of-band, dedicated, IPMI 2.0 compatible or equivalent)
  • Rack form factor (e.g., 2U or 1U, standard 19″ rack-mount)
  • Operating system compatibility certification for the organization’s existing or planned environment
  • Warranty and support terms (see below)

The specification should be written to be technically neutral while being specific enough that only hardware genuinely meeting the organization’s needs will qualify. Authorized partners of both HPE and Dell, including Zerick, regularly assist clients in drafting compliant technical specifications that protect the organization’s actual requirements while remaining legally defensible under ZJN.

Evaluation Criteria

Under ZJN, the most commonly applied evaluation criterion for goods procurement is the lowest price among technically compliant bids. This is a meaningful constraint: it means that if your technical specification is not precise enough, a bidder offering technically inferior hardware at a lower price may win, and the contracting authority has limited recourse if the specification was vague.

Some contracting authorities are beginning to apply the “most economically advantageous tender” (MEAT) criterion, which allows quality and lifecycle cost factors to be weighted alongside price. For server hardware, this approach creates space to score warranty depth, local service response time, and total cost of ownership are factors that have real operational consequences but are invisible in a lowest-price evaluation.

Warranty: What HPE and Dell Actually Offer, and What to Specify

Both HPE and Dell ship enterprise server hardware with base warranty terms that are often inadequate for the operational environments in which they are deployed in BiH. Understanding the difference between base warranty and extended/upgraded support, and specifying the right level in your procurement, is one of the highest-value decisions a procurement manager can make.

HPE Warranty Structure

HPE ships most ProLiant servers with a standard three-year warranty that includes parts and labor coverage, but defaults to a 9x5xNBD response standard: coverage during business hours, next-business-day parts delivery. For a server in a production data center environment (banking systems, public registry databases, municipal infrastructure) next-business-day response is almost never acceptable.

HPE’s Pointnext support portfolio allows this base warranty to be upgraded to:

  • HPE Foundation Care: Extended coverage with defined response windows (4-hour response, same-day, or 24×7 depending on tier). Available in 3, 4, and 5-year terms.
  • HPE Proactive Care: Adds proactive monitoring and account-level support management to the reactive support coverage.
  • HPE Datacenter Care: Higher-tier service for complex environments, including dedicated account engineers and environment-level support.

For BiH deployments, the practical choice for most production environments is HPE Foundation Care at the 4-hour hardware call-to-repair or 24×7 coverage level. When procuring through an authorized partner, these support contracts are attached to the hardware at point of sale and registered with HPE.

Dell Support Structure

Dell Technologies ships enterprise servers (PowerEdge line) with base ProSupport or Basic Hardware coverage. The meaningful service levels for BiH deployments are:

  • ProSupport: Access to Dell’s expert technical support teams (not consumer-level triage), with next-business-day onsite response as baseline.
  • ProSupport Plus: Adds predictive issue detection and automated support case creation based on system telemetry.
  • ProSupport Mission Critical: 4-hour or 2-hour response options, 24×7 coverage, defined resolution targets. The appropriate tier for data center and production workloads.

Dell also offers Keep Your Hard Drive and Accidental Damage add-ons that are relevant for specific deployment contexts, the former is particularly relevant for public sector clients who may have data residency or destruction obligations under BiH data protection law.

What to Specify in a Tender

When writing warranty and support requirements into a public tender, avoid generic language like “standard manufacturer warranty.” Instead, specify:

  • Warranty duration (e.g., minimum 3 years, or 5 years for critical infrastructure)
  • Coverage window (e.g., 24x7x365 support access)
  • On-site response time (e.g., maximum 4 hours from case escalation to engineer on-site)
  • Parts replacement standard (e.g., on-site parts replacement, not depot return)
  • Coverage geography (on-site response within BiH, not routed through regional hub)
  • Documentation requirement (e.g., warranty certificate issued in the organization’s name, not the reseller’s)

The last point deserves emphasis. It is common for hardware to be delivered with warranty registered in the reseller’s name, meaning the end customer cannot access vendor support directly. For public sector clients, this creates a dependency that should be contractually avoided, the warranty certificate must name the contracting authority as the beneficiary.

SLA Considerations: Connecting Hardware Support to Operational Requirements

A hardware warranty is a vendor commitment about the hardware. A Service Level Agreement (SLA) in the context of a managed services or support contract is a commitment about the service, the response, the resolution process, and the consequences of failure to meet defined targets. These are different documents, and confusing them is a common source of post-procurement disputes.

For organizations procuring servers in BiH, the relevant SLA question is: who is responsible for maintaining operational continuity of the hardware environment after delivery and installation?

When You Have an Internal IT Team

If the organization has internal IT staff capable of managing the server environment, the SLA question becomes: what level of vendor support will they call on when they cannot resolve an issue? In this scenario, the hardware warranty terms described above effectively function as the SLA and ensuring the warranty is registered correctly and at the right service level is the critical procurement task.

When You Are Procuring Managed Support

Many organizations in BiH and particularly municipalities, smaller public enterprises, and sector organizations without large internal IT departments procure server hardware as part of a broader managed services or maintenance contract. In this model, the supplier (or a separate managed services provider like Zerick) commits to maintaining the environment against defined operational parameters.

Key SLA elements to define in this context:

  • Response time: Maximum time from fault notification to first meaningful response (e.g., 2 hours for critical systems, 4 hours for standard)
  • Resolution time: Maximum time to restore full functionality (e.g., 8 hours for critical, next business day for standard) distinct from response time, and often omitted from poorly drafted contracts
  • Escalation path: Defined process for issues the first-line team cannot resolve, including timescales for each escalation level
  • Reporting obligations: Monthly or quarterly reporting on availability, incidents, and maintenance activities
  • Planned maintenance windows: Agreed periods during which work may affect availability, with notification requirements
  • Exclusions and force majeure: Clearly defined circumstances under which SLA targets do not apply

Under BiH public procurement law, SLA terms attached to a service contract are legally binding commitments and, if structured correctly, can include financial consequences (penalty clauses, service credits) for failures. This is an area where legal counsel familiar with ZJN and contracting practice is valuable.

Practical Buying Considerations: HPE vs Dell for BiH Deployments

Beyond the procurement process, the question of which vendor platform is right for a given deployment has operational and long-term implications.

Service Availability in BiH

Both HPE and Dell maintain authorized service partner coverage in Bosnia and Herzegovina. However, the depth and responsiveness of that coverage varies depending on the partner and the region. For deployments outside of Sarajevo and major urban centers, verifying actual on-site service capability, not just vendor authorization, is important before committing to a support tier that depends on local presence.

Parts Availability

For mission-critical deployments, spare parts availability is a real operational variable. HPE’s parts logistics in the Western Balkans region typically routes through the EU distribution network, meaning guaranteed same-day or next-day parts availability depends on what is stocked at regional hubs. Dell operates similarly. Authorized partners who maintain local spare parts inventory, even a limited set of common failure items such as drives, memory, and power supplies can meaningfully improve real-world resolution times relative to published SLAs.

Compatibility with Existing Environments

BiH public sector environments frequently combine hardware generations spanning a decade or more, often as a result of procurement cycles that did not maintain architectural continuity. Before specifying new server hardware, confirming compatibility with existing storage, networking, virtualization, and management infrastructure avoids integration problems that the warranty and SLA structure will not cover, because they are design problems.

Total Cost of Ownership

In a lowest-price procurement environment, total cost of ownership arguments are difficult to make formally. But internally, the calculation matters. A server procured at the lowest price with inadequate support coverage, requiring two unplanned maintenance events in its first three years, typically costs more in staff time, operational disruption, and potential third-party intervention than a correctly specified procurement would have.

How Zerick Supports Server Procurement in BiH

Zerick d.o.o. is an authorized partner for HPE, Dell EMC, and Ubiquiti in Bosnia and Herzegovina, serving clients across government, banking, automotive, and municipal sectors since 2017.

Our involvement in server procurement projects typically spans the full procurement lifecycle:

  • Pre-tender advisory: Helping clients develop technically precise, legally compliant specifications that protect their actual requirements
  • Supply: Direct hardware supply as an authorized vendor partner, with warranty registered in the client’s name
  • Deployment: Physical installation, rack integration, OS configuration, and handover documentation
  • Support and maintenance: Ongoing managed services, break-fix support, and vendor SLA fulfilment for HPE and Dell environments
  • Documentation: Handover certificates, maintenance records, and warranty registration documentation for audit and compliance purposes

We work with public institutions, private sector clients, and international organizations operating in BiH. If you are preparing a tender specification, evaluating a vendor proposal, or looking for support on an existing HPE or Dell environment, we are available to advise.

Summary: What to Get Right in HPE and Dell Server Procurement

The following checklist captures the highest-impact decisions in a server procurement process for BiH buyers:

Technical specification

  • Specify performance parameters, not brand model numbers, to comply with ZJN
  • Define interface, expansion, and management requirements precisely
  • Confirm compatibility with existing infrastructure before specifying

Warranty

  • Do not accept base warranty defaults for production environments
  • Specify coverage window, response time, and on-site resolution standard explicitly
  • Require warranty certificate in the contracting authority’s name, not the reseller’s

SLA

  • Distinguish between warranty (vendor commitment) and SLA (supplier commitment)
  • Define both response time and resolution time, they are not the same
  • Include escalation paths, reporting obligations, and maintenance windows

Procurement process

  • Understand which ZJN procedure applies based on contract value
  • Consider MEAT evaluation criteria if the contracting authority has flexibility
  • Verify the bidder’s authorized partner status and actual local service capability

Total cost

  • Calculate 3-to-5-year total cost including support, not just acquisition price
  • Factor in risk cost of unplanned downtime for the specific operational environment