IT infrastructure for multi-site companies

How it is deployed

1. 1Inventory per site: network, servers, lines and contracts.
2. 2Design of the central architecture and access model.
3. 3Pilot at a representative branch.
4. 4Progressive site-by-site rollout.
5. 5Centralised operation with per-location reporting.

What gets standardised

A per-site standard is defined: addressing scheme, network hardware, security policies, workstation build, application access and the user onboarding procedure. That standard is documented and applied to existing sites as well as new ones. Seintec operates what has been agreed and monitors links and equipment. Carrier lines can be contracted by the company or arranged by Seintec, as agreed, but the technical specification is always defined before signing to avoid lines that do not match the intended use.

What is at stake if it is left unaddressed

• A different configuration at every site

  Inherited network equipment with no common standard means every incident is solved by hand and improvements cannot be replicated.

• A single link with no alternative

  If a branch depends on one line, an outage at the carrier stops that site's activity completely.

• Decentralised user management

  Accounts created and closed locally leave active credentials belonging to people who have already left the company.

Frequently asked questions

Do we still need a server at each site?

Usually not, although some applications or production systems may require local equipment. This is decided during the inventory.

How is an incident handled at a distant branch?

First-line support is remote. On-site visits follow the coverage and terms agreed in the contract.

Can we keep our current lines?

Yes, if they meet bandwidth and stability requirements. If not, replacement or a backup link is proposed.

What about sites outside Catalonia?

Remote management covers the whole Iberian Peninsula. On-site attendance depends on the coverage contracted in each case.

Is a server at each site better than centralising?

In most cases centralising simplifies operations, backups and security, leaving only network equipment and workstations at each site. Something stays local when a process cannot tolerate latency or depends on machinery. The decision is made by measuring how the applications behave over the available link.

How is an incident handled at a distant branch?

Most support is resolved remotely, which is also the fastest route. Anything requiring a physical presence is planned in advance and supported by a named contact at the site. On-site coverage and service hours are agreed contractually according to each company's needs.

Can telephony and file access be unified across sites?

Yes, and it is usually one of the first visible benefits: a single numbering plan, transfers between sites and a shared folder structure with permissions by team. The preparatory work is tidying up existing permissions, which in multi-site companies have usually grown without any clear rule.

Can we start with a single site?

Yes, and it is usually the most sensible route: one site is tidied up, the resulting standard is documented and then replicated at the others on their own schedule. Investment is staged and each site is tackled with a configuration already proven in production.

How are sites connected to each other?

Through an encrypted link between each site and the central infrastructure, sized for the applications in use rather than for the headline speed of the line. Where a site cannot tolerate an outage, a second connection from a different carrier is added and traffic switches automatically. The design is documented so that any later change to a line or a router follows the same pattern.