Sectors
Seven environments, seven dominant constraints.
What decides a system’s architecture is not the list of services, it is the environment the system has to hold up in. Each sector imposes its own constraint; that constraint governs design, partners, equipment and method.
Your environment
Find yours.
Each page sets out what the environment imposes, what applies in it, what we have delivered there, and the questions to settle internally before committing.
A public service is validated on the worst-connected position, never on the one at head office.
Government
Areas covered : Government and public administration · Customs, borders and territorial management
The same data may fall under several regimes depending on where it is processed.
Diplomacy
Areas covered : International organisations
A system is judged when the link fails, not under nominal conditions.
Defence and security
Areas covered : National security and civil protection · Enterprise and sensitive-site security
On an isolated site, the public grid is an assumption, not a given.
Mining and industry
Areas covered : Energy and critical infrastructure
On a legacy network, the field survey costs three months and saves twelve.
Telecommunications
Areas covered : Telecommunications
A flag that cannot be explained cannot be contested, and therefore cannot be used.
Banking and essential services
Areas covered : Finance and fraud prevention · Health and essential services
A coordination system is judged on the day one link is missing.
Transport and logistics
Areas covered : Transport and logistics
The five divisions the group runs in these environments are presented separately: see the five divisions.
Areas of work
Responses shaped around each environment.
A business area describes what the group executes; an area of work describes the environment in which it executes. Each has a dominant constraint, and that constraint governs architecture, partners, equipment and method more than any list of services does.
- 01
Government and public administration
Dominant constraint : Continuity of registries and equality of access
A public digital service is judged on how reachable it is for those who depend on it most, and on the consistency of the registries underneath it. The binding constraint is not peak load: it is keeping civil-status records and reference data coherent over several decades.
- 02
National security and civil protection
Dominant constraint : Separation and degraded-mode operation
These systems must keep working when communications are lost, and must absorb the compromise of a single position without letting it spread. Separation by level of sensitivity takes precedence over convenience of use.
- 03
Customs, borders and territorial management
Dominant constraint : Traceability of controls and interoperability
Flows cross several authorities that share neither systems nor procedures. Interoperability here is a legal requirement as much as a technical one, and every control must remain traceable.
- 04
Finance and fraud prevention
Dominant constraint : Data quality and contestability of results
An analytical alert must be explainable, contestable and correctable. The quality of the input data governs the value of the system more than the sophistication of the analysis does.
- 05
Telecommunications
Dominant constraint : Availability and control of the supply chain
Availability rests on equipment whose origin and update cycle must be known. Software supply-chain security is part of network security, not an adjacent concern.
- 06
Construction and secure buildings
Dominant constraint : Security integrated from the design stage
Structure, circulation, sensitive zones, backup power and technical networks must be designed as one system. Konect coordinates studies, construction, technical trades and commissioning so that security is not added too late.
- 07
Enterprise and sensitive-site security
Dominant constraint : Detection, control and verified response
Video surveillance, access control, intrusion, fire, supervision and human procedures are integrated around real threat scenarios. The goal is a traceable response, not an accumulation of equipment.
- 08
IT equipment supply and installation
Dominant constraint : Compatibility, deployment and lifecycle support
Workstations, servers, storage, networking and peripherals are selected around actual use, prepared, inventoried and deployed with secure configurations, documentation and a support model.
- 09
Custom software development
Dominant constraint : Operational adoption and product ownership
Business applications, portals, mobile tools, APIs and automations are designed from real processes. Code, documentation, tests and maintenance plans remain usable beyond the initial project.
- 10
Energy and critical infrastructure
Dominant constraint : Separation of industrial and corporate systems
The separation between industrial control systems and corporate systems is the first line of defence. Every gateway between the two must be justified, documented and monitored.
- 11
Health and essential services
Dominant constraint : Data minimisation and continuity of care
Health data calls for the strictest minimisation and for separation by purpose. Continuity of care takes precedence over any consideration of administrative convenience.
- 12
Transport and logistics
Dominant constraint : Resilience of routes and multi-party coordination
Coordination brings together public and private operators whose systems were never designed to communicate. The arrangement must stay usable when one link becomes unavailable.
- 13
International organisations
Dominant constraint : Multiple legal regimes and controlled transfers
The same data may fall under several legal regimes depending on where it is processed. Transfer controls and traceability of access govern whether the arrangement is feasible at all.
Engagement confidentiality
Evidence is shared within a controlled process.
Client references, detailed architectures and information concerning sensitive sites are never published without authorisation. Material required for pre-qualification is shared with an identified organisation once the enquiry has been qualified.
Consultations · Pre-qualifications · Partnerships
Let’s discuss your project.
Describe your priority, its operating context and the intended outcome. We will route the enquiry to the right person.