# IT infrastructure in the mid-market: plan network, servers, sites and capacity > Infrastructure that carries: plan capacity and replacement ahead, size network and sites, make dependencies visible, set maintenance windows and keep outages manageable. URL: https://techport.ai/en/it-beratung/betrieb-und-support/it-infrastruktur --- 1. [IT Consulting](/en/it-beratung)/ 2. [Operations and Support](/en/it-beratung/betrieb-und-support)/ 3. Planning IT infrastructure [Operations and Support](/en/it-beratung/betrieb-und-support) # Planning IT infrastructure By Redaktion techport.ai, IT-Beratung · Last updated on 21 August 2026 Infrastructure only gets noticed when it is missing. It is the network production reports over, the server the ERP runs on, the link to the second site and the power supply in the technical room. As long as everything runs there is no reason to talk about it, and that is precisely why it usually gets renewed only when it fails or when a project hits its limits. Infrastructure planning in the mid-market does not mean buying the newest equipment. It means knowing what has to be replaced when, where the limits are, and what happens when a part fails. ## How you notice it * Devices run considerably longer than intended because no replacement was budgeted. * Systems get slow under peak load and nobody can say where the constraint sits. * The technical room has grown over the years, cabling and labelling are out of date. * There is no overview of which application runs on which machine and what depends on it. ## Why this happens Infrastructure gets bought project by project. One initiative needs a server, another more storage, a third a faster link. Each purchase solves its problem, but nobody assembles the parts into an overall picture and nobody plans the replacement, because the purchase sat in a project budget and the replacement sits in none. After five to seven years several replacements then fall due at once, usually unplanned. ## How we go about it 1. **Record inventory and life cycle.** We capture which components exist, how old they are, how long they will be supported and which applications run on them. From that comes a multi-year replacement plan that feeds into budget planning. 2. **Make dependencies visible.** We document which application depends on which component, including network, directory service, name resolution and power supply. That chain is the most important information during an incident and the least known in daily work. 3. **Check capacity in the right place.** We measure where bottlenecks arise rather than everywhere: storage, throughput, response times of the central systems and the links between sites. On that basis growth can be planned rather than reacted to. 4. **Secure operations.** We set maintenance windows, arrange spare parts or contracts with response times for critical components, and check how long an outage would last per component. That figure belongs in the emergency plan. ## What you gain * Replacements that appear in the budget as planned rather than as a surprise. * Incidents narrowed down faster because dependencies are documented. * A solid basis for deciding what stays in house and what is operated externally. ## From our projects The most frequently underestimated dependency is the directory service. When it is unavailable, practically nothing works any more, including systems that appear to have nothing to do with it. In many companies it runs on a machine whose failure scenario has never been thought through. The second most common surprise is the power supply: uninterruptible supplies exist, but their batteries are older than intended and have not been tested for years, which in an emergency means the protection does not take effect. Both are small checks with large effect. ## Häufige Fragen Should we keep our own servers or outsource everything? That is decided per system, not across the board. For standard applications external operation is usually more economical. For systems with tight response time requirements, for production control or where the external connection is itself a risk, running your own remains sensible. What matters is that the remaining infrastructure is then small enough to operate properly. How long should servers and network components run? As orientation, five years for servers and up to seven for network components, but vendor support is what decides. Once there are no more security updates, age is irrelevant and the component has to be replaced. That is why the end of support belongs in the inventory list, not the purchase date alone. ## Let us talk about Planning IT infrastructure In a thirty minute first call we work out where your biggest lever sits and whether we are the right people for it. [Arrange an initial call](/en/kontakt)[Our software](/en/loesungen) ## Further reading [Architecture and ApplicationsSettling the cloud questionCloud decisions per system rather than across the board: cost over the term, operations and specialists, legal requirements, vendor dependency and a defined way back.](/en/it-beratung/architektur-und-anwendungen/cloud-strategie)[Operations and SupportMonitoring and availabilityMonitoring that helps instead of adding noise: choose the right measuring points, set sensible thresholds, tie alerts to people, measure availability and be able to hold commitments.](/en/it-beratung/betrieb-und-support/monitoring-und-verfuegbarkeit)[Security and ResilienceEmergency management and recoveryWhat happens when IT stops: determine critical processes and time targets, write the emergency plan, rehearse recovery, settle crisis communication and learn from exercises.](/en/it-beratung/sicherheit-und-resilienz/notfallmanagement)[KnowledgeIT metricsDefinitions and formulas read the same way across the company.](/en/it-beratung/kennzahlen)[KnowledgeIT glossaryTerms from IT, software and security, briefly explained.](/en/it-beratung/glossar) Back to the field [Operations and Support](/en/it-beratung/betrieb-und-support) Rt Written by [Redaktion techport.ai](/ueber-uns), IT-Beratung Mehr als 15 Jahre Erfahrung in IT-Projekten des Mittelstands, Auswahl und Einführung von Unternehmenssoftware, Aufbau von IT-Betrieb und Informationssicherheit in wachsenden Organisationen. [More about us](/en/ueber-uns) More from techport.ai [ Software Custom process software for mid-sized companies. ](/en/loesungen)[ HR consulting People processes and the systems behind them. ](/en/hr-beratung)[ IT maturity check Ten minutes to a clear position. ](/en/it-beratung/reifegrad-check)[ HR maturity check 24 statements, a result per field. ](/en/hr-beratung/reifegrad-check)[ Funding BAFA grant plus more than 50 programmes for delivery. ](/en/foerderung)[ Process in practice How workflows become reliable software. ](/en/sop-praxis)[ Data and AI Analysis, forecasts and assistance systems. ](/en/daten-ki)[ About us The people behind techport.ai. ](/en/ueber-uns)