Network fault fixing
Intermittent Wi‑Fi, roaming failures, unexplained congestion, broken topology, unstable uplinks and the problems that survive the first three “fixes”.
- Root-cause mapping
- On-site measurement
- Recovery plan
Network architecture · Field infrastructure · Bohinj
Networks that
have to work.
Independent planning, troubleshooting and delivery for hospitality, rural operations, events and places where generic IT answers stop being useful.
- 01Design before hardware
- 02Failure paths made visible
- 03Verified in the real environment
Editorial concept image · not client-site photography
What problem do you have?
Start with the failure mode.
Not the product catalogue.
AlpskiMedved starts where the system stops behaving. The technology comes after the constraints, dependencies and operational stakes are understood.
Network planning
New sites, renovations, expansions and inherited environments. Wired, wireless, fibre, segmentation, resilience and capacity planned as one system.
- Architecture
- Coverage and capacity
- Failure paths
Installation & rebuilds
Practical implementation with clean architecture, sensible hardware and verification in the real environment — not only on a dashboard.
- Direct implementation
- Specialist coordination
- Handover
Internet anywhere
Fibre, 5G, LTE, satellite, point‑to‑point and multi‑WAN designs for mountain, rural and operationally awkward locations.
- Path diversity
- Automatic failover
- Remote reach
Hospitality networks
Guest Wi‑Fi is only one workload. POS, staff devices, surveillance, access, reception, back office and Internet resilience all compete for the same infrastructure.
- Guest and operations separation
- Seasonal peak readiness
- Business continuity
Event & temporary networks
Temporary connectivity for events, seasonal sites and mobile operations where payments, production and staff systems still need to behave like permanent infrastructure.
- Rapid deployment
- Critical-workload priority
- Teardown-ready design
The whole operational path
One system.
Not six islands.
A network is useful only when the business workflows on top of it survive. Architecture connects the outside path, core, wireless edge and operational devices into one understandable system.
Upstream
Fibre · LTE/5G · Satellite · Radio
Core
Routing · Segmentation · Resilience
Field
Wi‑Fi · PtP · Outdoor coverage
Operations
POS · Staff · Guests · Cameras
The architecture is the product. Hardware is selected only after the system has a reason to exist.
The useful kind of difficult
Difficult is interesting.
A good network is not a pile of access points. It is a system of dependencies, constraints, failure paths and human operations.
The job is to remove fragility without replacing it with a different kind of complexity.
Field evidence · publication-safe method
Evidence before
adjectives.
A system is verified against the environment and operation it serves. Public claims come later—only when their source, scope and wording are ready.
01baseline the real operating condition
02make failure paths visible
03test under representative load
04state only the supported outcome
The public layer explains the method. Client identity, measurements and security-relevant detail remain outside the deployable package until publication is approved.
Evidence policy · Working cases held private
Real does not automatically mean public.
Public now
The verification method, operating principles and the kinds of acceptance tests a field system should survive.
Private until approved
Client identity, topology, measurements, commercial outcomes and any security-sensitive operational detail.
Release gate
Traceable evidence, bounded wording and a clear right to publish the resulting case material.
Case release standard
Publish only when the evidence can carry its own weight.
Evidence & scope Traceable
Client-safe wording Approved
How the work happens
Understand → Design → Build → Verify
One accountable line from the first symptom to a system that works in practice.
- 01Constraints before solutions
Understand
What are you actually trying to accomplish? Where does traffic, information and operational dependency really live? What happens when something breaks?
- 02Clarity before quantity
Design
Choose the smallest architecture that solves the real problem, fits the organisation and keeps failure paths visible.
- 03The right hands for the job
Build
Implement directly or coordinate trusted specialists where fibre, electrical, construction or other disciplines are needed.
- 04Reality is the dashboard
Verify
Test the system where it matters: on site, under load, across actual workflows — not only in configuration screens.
One architect. The right people when needed.
Small by design.
AlpskiMedved.solutions is built around specialist systems architecture rather than a generic helpdesk model. Network infrastructure stays front and centre; adjacent business systems are solved when they genuinely belong to the same operational problem.
When a project needs installation capacity or a discipline outside the core, trusted peers and contractors are brought in rather than pretending one company should do everything.
- Service area
- Bohinj · Bled · Kranjska Gora
- Model
- Independent specialist
- Bias
- Evidence over adjectives
Start here
Describe the problem.
We’ll start there.
A useful first message does not need a shopping list. It needs the place, the failure, the operational impact and what “working” should look like.
START A CONVERSATION
Marko Kolman is the public point of contact. Start by email, call directly, or prepare the project facts first.