Case studyGovernment & Public Sector — Health Supply Chain

Connecting and protecting eight branches of a national pharmaceutical supply agency

Routers, switches, and perimeter firewalls supplied and implemented across eight regional branches of a national pharmaceutical supply agency — delivered on time, “with great efficacy,” and formally recommended by the delivery partner.

Delivered2019project completed
ClientA national pharmaceutical supply agency (eight branches), delivered through a pharmaceutical distribution partner
Solution areasNetworking & Connectivity · Cybersecurity
TimelineSix months, on time
01 — Challenge

The challenge

A national pharmaceutical supply agency does something the public rarely sees and always depends on: it moves medicines and medical supplies from central stores to the regions, and it does so on information — stock levels, orders, distribution schedules, cold-chain records. That information lives on a network. In 2019, that network needed rebuilding across eight regional branches.

The problems were the classic ones of a distributed public organization:

01Inconsistent, aging branch infrastructure Each branch had grown its own way; equipment was heterogeneous, undocumented, and past its useful life. Reliability varied by site.
02Weak perimeter security Branches connected to central systems and to the internet with little or no modern inspection at the edge — an exposure for an agency handling regulated supply-chain and health data.
03No standardization Without a common design, every fault was a bespoke problem, and every change had to be re-thought per site.
04Geography Eight branches spread across the country meant logistics, coordination, and on-site work at scale — with a hard timeline.

The delivery partner — a pharmaceutical distribution company that held the contract — needed an integrator that could design a standard branch architecture, source and stage the equipment, and implement it across all eight sites within the schedule. On the recommendation of a US-based technology partner, it selected eSafe.

02 — Approach

Our approach

  1. 01

    One design, eight times

    Rather than eight custom projects, eSafe designed a standard branch architecture — routing, switching, and perimeter firewalling in a repeatable configuration — that could be built, staged, and deployed identically at every site. Standardization is what makes a distributed network supportable.

  2. 02

    Stage centrally, deploy locally

    Equipment was configured and tested centrally from the standard design, then deployed to each branch by eSafe’s engineers — reducing on-site time, eliminating per-site configuration errors, and making each branch cutover fast and predictable.

  3. 03

    Site by site, on schedule

    Deployment was sequenced across the eight branches against a schedule agreed with the partner, with each site tested and handed over before the team moved on. The whole program completed within its six-month window.

  4. 04

    Document for the long term

    Every branch was delivered with the documentation the agency’s IT staff need to support it — a direct answer to the “undocumented, bespoke” problem the program set out to fix.

03 — Solution

The solution

Standardized branch network

  • Branch routers providing resilient connectivity from each site to the agency’s central systems and services.
  • Access and distribution switching to connect branch users, workstations, and systems on a clean, consistent design.
  • A common configuration baseline across all eight branches, so the network behaves identically everywhere and can be supported from one runbook.

Perimeter security at every branch

  • Perimeter firewalls at each site, bringing modern edge inspection to every branch rather than only to headquarters — so each regional office is a controlled boundary, not an unguarded door into central systems.
  • Consistent security policy applied across the branch estate.

Delivered end to end

  • Design, supply, staging, implementation across eight sites, testing, documentation, and handover — one team, one standard, on one schedule.
04 — Result

The result

The program was delivered on time. The partner’s leadership wrote that eSafe completed the “supply and implementation of routers, switches and perimeter firewalls for eight branches… on time and that too with great efficacy” — praising the “professionalism by which they have completed the project” and noting that eSafe’s technical and managerial team “has some of the best technical expertise in Ethiopia.”

Supply and implementation of routers, switches and perimeter firewalls for eight branches… on time and that too with great efficacy
From the client’s letter

The letter closed with the partner’s — and its international partner’s — “highest recommendation for eSafe IT Solution PLC.” Three years later, the same partner returned to eSafe for its own ERP security program: a second engagement, and the clearest verdict on the first.

The agency gained what a distributed public organization needs most: a standardized, secured, documented network across its regional footprint — the reliable foundation under a supply chain the country’s health system depends on.

05 — Why it worked

Why it worked

Standardize, then replicate

One repeatable branch design turned eight projects into one program — and made the result supportable.

Stage centrally

Building and testing configurations before shipping to site is why eight cutovers were fast and error-free.

Security at every edge

Perimeter protection at each branch, not just at headquarters, closed the exposure a distributed agency actually has.

Client identity withheld under our confidentiality commitments. Details, quotations, and outcomes are drawn from the client’s formal project acceptance and recommendation letters, held on file.

More case studies

Other engagements, same discipline

Next step

Have a project like this one?

Tell us your infrastructure reality and your constraints — we’ll show you how we’d approach it.

Talk to a pro