Infrastructure change without shortcuts

ILS Networks designs, manages and delivers infrastructure projects end to end: mapping what exists, architecture, staged delivery with a defined way back, and operation after handover.

Illustration: infrastructure project delivery — planning, maintenance windows, acceptance testing and documented handover

Overview

Most infrastructure projects do not fail during delivery

They fail before it — when nobody mapped what is actually connected to what, when no one defined what happens if a stage does not work, or when a dependency between suppliers surfaced on cutover day. Execution is usually the easy part.

So we run the same four stages on every project, whether it is a virtualization migration, a storage migration or building network infrastructure at a new plant. The method does not change with the size of the project, only its scope.

How it works

Four stages, on every project

Map and design

  • Systems, service dependencies, risks and load
  • Business requirements gathered, not only technical ones
  • Architecture designed with alternatives and budget
  • A defined way back from every material change

Deliver

  • A pilot before any organization-wide rollout
  • Maintenance windows agreed in advance
  • Acceptance testing defined per stage
  • Coordination with external suppliers and contractors

Hand over and operate

  • Documentation of what exists and how it is configured
  • Knowledge transfer to the internal team
  • Ongoing monitoring and fault handling
  • Adapting the environment as needs change

Proof

Projects we have run end to end

Ariston Group

Staged infrastructure change in a live environment

A virtualization migration, storage migration, switch deployment and security build — as a staged process with a way back at every step, across ten branches.

  • Proxmox
  • IBM Storage 5300
  • Aruba
  • Sophos

Combe

Infrastructure built at new plants

Network infrastructure designed and built from the ground up at plants added to the group, alongside dozens of projects over more than 15 years.

  • Network infrastructure
  • Sophos
  • Arista Networks

CooperVision

A full network estate end to end

Design and build of backbone, campus and wireless, alongside a storage migration and an NDR deployment.

  • Arista Networks
  • Dell PowerStore
  • NDR

The projects shown here are based on work delivered by the ILS team in customer environments.

FAQ

Frequently asked questions

What does infrastructure project management cover with you?

Four stages: map what exists, design the architecture and the alternatives, deliver in stages with acceptance testing, then run and support after handover. Each stage ends with documentation of what was actually delivered, not with a checklist that got ticked.

Do you manage projects that involve other suppliers?

Yes. Most infrastructure projects involve more than one party — a telecoms provider, a vendor, an electrical contractor or a software supplier. Part of the work is synchronising them and managing the dependencies between them, rather than each side waiting on the other.

What happens if a stage fails midway?

Every material change has a defined way back, agreed in advance. That principle runs through all our work — virtualization migrations, storage migrations and network upgrades — because an infrastructure change without a rollback plan is a gamble, not a project.

Do you work alongside an internal IT team?

Yes, and that is the common case. At some clients we supplement an existing team on a specific project; at others we run the whole estate over years. Both models work; what matters is agreeing who owns what before starting.

What does documentation look like at the end of a project?

Documentation of what actually exists: what was installed, how it is configured, why those settings were chosen and what someone needs to know to maintain them. The simple test is whether a person who was not on the project can resolve a fault from the document.

Do you serve organizations in Israel?

Yes. ILS Networks is an Israeli IT infrastructure company.

How does an infrastructure project with ILS run?

In four stages: mapping the existing environment and its dependencies, designing the architecture with options and budget, staged delivery in agreed maintenance windows with a rollback plan for each stage, and after handover, documentation and ongoing operation. Every material change has a defined way back, so production never depends on everything going to plan.

What does an infrastructure project cost and how is it priced?

Pricing follows the scope established after the mapping stage rather than a fixed price list, because the same request in two different environments is two different projects. We start with a conversation and a review of the environment, then provide a detailed proposal separating hardware, implementation work and ongoing operation, so it is visible what is being paid for.

Got an infrastructure project on the table?

A short technical call with the team: what is planned, where the risks are, and what it takes to deliver without surprises — no commitment.

Your details are used to respond to your inquiry, as described in our privacy notice.

Talk to us