Networks, routing & radio
Analyse, plan, and implement clearly bounded site networks, interconnections, routing transitions, radio networks, and microwave links.
Networks connect applications, sites, and people. When their dependencies are unclear or changes are made without a reliable fallback path, even a single transition can affect important functions. We primarily work with regulated, public-sector, social-service, and outage-sensitive organisations. We consider demanding private-client projects individually.
Typical starting situations and risks
- Site networks and interconnections have evolved over time or are only partly documented.
- Network segments serve different purposes, but their transitions and responsibilities are not clearly bounded.
- Static or dynamic routing decisions are difficult to trace, or changes can only be prepared with a high operational risk.
- Radio networks or microwave links need to be added, renewed, or integrated into an existing network.
- Dependencies on power, mounting locations, existing cabling, or external connections remain open before implementation.
- Fallback and recovery paths are not sufficiently documented or practically verifiable.
Analysis, planning, and implementation
The specific engagement is bounded by the affected functions, sites, and interfaces. Analysis, planning, and implementation can build on one another, but remain traceable work packages with their own prerequisites and approvals.
Analysis
We map the agreed environment, relevant network segments, interconnections, routing transitions, and radio links. We organise dependencies, known constraints, responsibilities, and available documentation. For radio and microwave projects, the agreed assessment may also consider site conditions, mounting paths, and integration with the wider network.
Planning
We develop an implementable target structure and describe the required transitions. This may include segmentation boundaries, routing behaviour, radio links, the sequence of changes, test conditions, and fallback and recovery paths. Decisions and open assumptions are documented so they can be reviewed before implementation.
Clearly bounded implementation
We carry out agreed configuration, integration, and commissioning work within the approved scope. Work on buildings, power, cabling, or external connections is only included when expressly agreed and covered by the necessary expertise. Changes take place in coordinated windows with the test and fallback points defined for the project.
Open router and firewall platforms in context
Depending on the task, OpenWrt, VyOS, OpenBSD, and OPNsense can be suitable examples of open router or firewall platforms. Requirements, existing interfaces, necessary functions, maintainability, and the intended operational handover determine the choice. These systems are neither a complete nor an exclusive technology list and imply no vendor or partner relationship.
Operational resilience, fallback, and recovery
Operational resilience is considered throughout the engagement: from traceable dependencies and coordinated changes to usable backups, fallback paths, and an orderly handover. Which tests or recovery exercises are useful and feasible depends on the agreed scope and operating environment.
Redundancy or alternative connection paths may form part of a plan. This does not provide a blanket guarantee of high availability, compliance, certification, availability, or outcomes.
Possible documentation and handover artefacts
Depending on the engagement, possible artefacts include:
- an as-is or target overview of relevant networks, segments, and interconnections;
- a traceable description of routing transitions and dependencies;
- route or mounting plans for agreed radio and microwave links;
- configuration, change, and test records;
- an overview of responsibilities, interfaces, and open points;
- a handover package covering backup, fallback, and recovery paths.
These are possible, engagement-dependent working artefacts, not generally promised outcomes. Their content, level of detail, and maintenance responsibility are defined for the specific project.
Client interfaces and contribution
The client team identifies the business and technical contacts, affected functions, operational priorities, and authorised approvers. It provides available documents and agreed access, coordinates change windows, and involves internal operations staff and external parties where needed.
For radio and microwave projects, site access, mounting approvals, power and cable paths, and any required coordination with property owners or other responsible parties must be clarified. Missing prerequisites and decisions are recorded as open client interfaces; they are not silently assumed to be part of the technical implementation.
Boundaries and exclusions
- support and maintenance only under a separate agreement; no blanket 24/7 operations;
- no guarantees concerning high availability, deadlines, availability, or outcomes;
- no product or licence sales and no reseller model;
- no general PC, printer, or small-ticket support;
- no automatically included penetration test, certification, or compliance audit;
- no implementation outside the agreed scope or without the necessary approvals.
The service overview places network work within the overall offer. The approved anonymised project profiles on more resilient network connectivity in a healthcare environment and decentralised connectivity for a care facility provide bounded practical examples without naming clients or disclosing confidential operational details.
Discuss your network project
Describe the affected functions and sites, the known environment, the intended change, and available operating windows. We can then determine which analysis, planning, or bounded implementation is appropriate and which prerequisites need to be addressed first.