Mining site — server room and backup power
Construction of a secure technical room and its power chain, on an isolated site with no reliable public grid.
- Weeks of measurement before sizing
- 4
- Load tests per year
- 12
Reference KP-2024-008
Technology · Telecoms · Security · Power · Construction
We build what must endure.
Software, telecommunications, security, power and critical buildings: designed, deployed and operated under one accountable lead.
- 01Technology
- 02Telecoms
- 03Security
- 04Construction
- 05Energy
Divisions
Five divisions, one point of contact.
One command across five divisions. Responsibilities are settled before execution, not at the first snag.
Six stacked layers, and a seventh that cuts across them.
Each can be bought separately, and each is simple taken on its own. Faults almost never appear inside a layer: they appear between two.
Layers of an infrastructure
Building
What it carriesPlant rooms, circulation, service risers, restricted zones.
What falls with itEverything above it, with nowhere to sit and no route to run.
DivisionConstruction
Power
What it carriesIncomer, generator, transfer switch, UPS, fuel autonomy.
What falls with itThe five layers above, in the order of their own autonomy.
DivisionEnergy
Network
What it carriesCabling, fibre, switching, physically separate routes.
What falls with itVoice, security and applications, together and without warning.
DivisionTelecoms
Telecoms
What it carriesTelephony, inter-site links, reachability of remote sites.
What falls with itThe ability to report the incident and coordinate the response.
DivisionTelecoms
Security
What it carriesAccess control, video, detection, screening of what comes in.
What falls with itThe evidence of what happened, including for the other layers.
DivisionSecurity
Applications
What it carriesLine-of-business software, data, exchanges with existing systems.
What falls with itThe service delivered, the only thing the end user measures.
DivisionTechnology
Monitoring
What it carriesThresholds, alerts, on-call, response, a record of what was done.
What falls with itThe difference between an incident closed within the hour and found on Monday.
DivisionTechnology
A site that stops rarely has a single cause. It has one failing layer and one interface nobody had signed for.
Solutions
What you buy, under a single accountability.
Each solution assembles several divisions into a result that can be accepted.
The online counter is the visible part; processing is what decides the service delivered.
Digital government
Taking an administrative procedure online end to end, from submission to notification, without leaving the processing behind.
A site’s security never decays through its hardware; it decays through its interfaces.
Secure sites
Protecting a site by treating the fabric, access, detection, supervision and the power that holds them as one.
Every component is available; it is their assembly that is not.
Critical infrastructure
Building and operating the base everything else rests on: technical room, power, links, and the continuity that ties them together.
What costs in a branch network is not bandwidth, it is heterogeneity.
Connected enterprise
Linking sites, workstations and voice under one configuration, operable remotely and documented.
The question is not package versus bespoke, but where the specificity sits.
Business software
Supporting the process that sets you apart, integrating it with what exists, and leaving it maintainable by your teams.
Contracted supply describes a contract; a load study describes a need.
Backup power
Holding a site when the grid fails: load study, uninterruptible supply, generator set, and the tests that prove it.
Delegating operations is legitimate; losing the ability to take them back is not.
Monitoring and maintenance
Keeping what was delivered in service: useful monitoring, committed response times, traced access, and the ability to take control back.
The group in figures
Experience built in the field.
- 58+Projects deliveredTechnology and infrastructure projects taken from design through to commissioning.
- 94+Sites deployedBuildings, technical infrastructure and remote sites equipped and commissioned.
- 24/7SupervisionMonitoring and operational continuity of the systems covered by our maintenance contracts.
- 5Integrated disciplinesTechnology, telecommunications, security, power and infrastructure under a single accountable lead.
Projects
What we have built, operated and brought back into service.
One real engagement per record: the operating problem, the architecture chosen, the result. The client is named only where written authorisation allows.
Regional operator — core network modernisation
Replacement of the core network and backup power at fourteen points of presence, with no commercial service outage.
- Points of presence migrated
- 14
- Longest outage window observed
- 4 min
Reference KP-2023-021
European diplomatic mission — multi-system security
Complete overhaul of access control, video surveillance and backup power for a chancery in service.
- Systems merged
- 3
- Service interruptions
- 0
Reference KP-2022-014
References
Organisations that have entrusted us with a mission
Each entry links to the record of the mission delivered: the technical scope, what was handed over and what was measured. An organisation served is demonstrated by work described, not by a logo displayed.
None of these organisations is named here. Naming a client requires their written agreement, and that agreement states what may be published: the name, the mark, the figures. References are provided, by name, to an identified organisation. Open the pre-qualification centre
Control and continuity
Three questions settled before design begins.
Where the system runs, where the data resides, who holds the keys. The answers are yours, and they govern the architecture.
Deployment modes
Encryption keys held by the client organisation
Konect keeps no copy, whichever mode is chosen.
National infrastructure
- AccessPublic network
- ProcessingPublic network
- DataSegregated
Execution and data residency within the organisation’s own territory.
Hybrid environment
- AccessPublic network
- ProcessingSegregated
- DataSegregated
Sensitive processing stays local; the rest may be shared.
Isolated environment
- AccessSegregated
- ProcessingSegregated
- DataSegregated
No link to the public network. Exchanges pass through a controlled transfer.
Control safeguards
What we commit to before we begin.
- 01
Ownership of data
Data produced in the course of an engagement remains the property of the client organisation, with no exception and no derived use.
- 02
Place of deployment
The organisation chooses where its systems run and where its data resides, including in environments isolated from the public network.
- 03
Open standards
Interfaces and formats are documented and published, so that another supplier can take the work over.
- 04
Reversibility
The exit plan is defined before go-live, not at the point where the relationship breaks down.
- 05
Transfer of skills
The engagement ends when the organisation’s own teams run the system without outside assistance.
A transparent relationship
You know what is public, available on request and protected.
- 01 · Public
Public on this site
Legal identity, capabilities, method, locations and official channels.
- 02 · Due diligence
Available on request
Capability statements, compliance evidence, authorised references and contractual terms.
- 03 · Restricted
Protected by principle
Products, internal architectures, operational data and sensitive clients.
Insights
What we learned by building it.
A trade-off, a common mistake, what it costs. Nothing to buy for it to be useful.
Operational presence
Two locations, four areas of operation.
The operational headquarters leads engagements. The North American location carries software engineering and private hosting.
- West Africa
- Delivery and maintenance across the sub-region, from the operational headquarters.
- Central Africa
- Individual engagements and programmes delivered with qualified local partners.
- Europe
- Relations with diplomatic missions and international organisations.
- North America
- Software engineering and private hosting infrastructure.
- Bamako
- Operational headquarters12° 39′ N · 8° 00′ W
- Montréal
- North American relay45° 30′ N · 73° 34′ W
- Separation
- Great-circle distance7,110 km
Consultations · Pre-qualifications · Partnerships
Let’s discuss your project.
Modernisation, cybersecurity, integration, infrastructure or partnership: tell us about your priority and its operating context.