Skip to content
comercial@henicom.com+244 956 419 040
HENICOM
PTEN
Talk to an engineer
HENICOM · Angola

Network engineering for organisations that cannot stop.

We train engineers, design and deploy critical networks and run our own wireless network. What we learn on one front makes the others better.

Meet HENICOMTalk to an engineer
Three businesses, one engineering team

Train. Design. Operate.

Each business solves a different problem, but they all share the same engineering team and the same standards.

01 · TrainHENICOM IT ACADEMY

Hands-on courses in networks, systems and security, taught by people who work in the field.

See courses 02 · Design and deployHENICOM IT SOLUTIONS

Networks, security and continuity to help businesses of every size go digital.

See capabilities 03 · OperateHENICOM NAVEGA

Our own wireless network in Luanda, for homes and businesses, and managed Wi-Fi for hotels and restaurants.

See packages and coverage

What NAVEGA learns from operating a network every day feeds back into IT SOLUTIONS projects and IT ACADEMY classes.

A network is only worth something if it keeps working when it is needed most. That is why we design for failure, measure everything we operate and stay responsible for the result after installation.

HENICOM
How we think

Four principles we do not compromise on

  1. 01

    Measure before you change

    No change starts without a baseline: what is happening, where and how often. Then we measure again to prove the result.

  2. 02

    Design for failure

    All equipment breaks and all links go down. The right question is not «if» but «what happens next» — and the answer has to be written down and tested.

  3. 03

    Automate what repeats

    Configurations, backups and checks are code. Anything done by hand over and over ends up being done differently.

  4. 04

    Security from the start

    Separate networks, grant the least access needed and log what matters. Adding security at the end costs more and protects less.

What we measure

A network is described with numbers, not adjectives

On every network we operate we track objective indicators. These are what appear in our reports to clients.

AvailabilityThe share of time the service is actually usable, measured from the outside in.
Latency and lossDelay and lost packets at peak times, not just the daily average.
Signal on the groundSignal strength and quality measured on site, to confirm what planning predicted.
Time to restoreHow long it takes from a failure to service restored — and how long the failure went unnoticed.
Contact

Talk to an engineer, not a salesperson

Tell us the problem. The first conversation is about understanding what is going on and whether we can help.