Industry Guide Technology
Plants often run on servers and network gear long past their support dates. Build an inventory, rank risk by production impact, and plan refreshes around shutdowns and budgets.
Manufacturing sites are good at maintaining machines. They are often less consistent about the servers, switches, firewalls and PCs that keep those machines scheduled, monitored and connected to the business. A server under a desk in the plant office runs the label printing. A ten-year-old switch connects the production floor to the ERP system. A workstation that runs the quality inspection software cannot be updated because nobody is sure the software will still work.
None of this is unusual, and much of it runs reliably for years. The risk arrives quietly: a vendor stops issuing security updates, a disk fails with no spare available, or a cyber incident spreads through equipment nobody remembered to patch. IT asset lifecycle management is the discipline of knowing what you have, how long it will remain supported and when it needs replacing, so that upgrades happen on your schedule rather than in an emergency.
This guide shows manufacturers how to build an infrastructure inventory, rank risk by production impact, plan refreshes around shutdowns and budgets, and measure whether the program is working.
End-of-support dates are fixed and published, which makes them one of the few IT risks you can see coming. A current example: Microsoft has stated that Windows Server 2016 reaches the end of extended support on January 12, 2027. After that date it no longer receives standard security updates unless the organization has an eligible Extended Security Updates arrangement. Eligibility, delivery options and costs need to be checked for the actual deployment. The Microsoft lifecycle page for Windows Server 2016 sets out the product's fixed-lifecycle dates.
Servers of that generation are common in plants because they were installed alongside production systems around the time the operating system was current. If you have any, the decision about whether to upgrade, migrate, isolate or buy extended updates needs to be made in the next few months, not after the date passes.
Operating systems are only one category. Network equipment, firewalls, storage, virtualization platforms, databases and industrial software all have their own support lifecycles, often controlled by different vendors.
You cannot plan a lifecycle for equipment you do not know about. Start with a single inventory covering every server, network device, storage system and business-critical workstation across all sites.
| Field | Why it matters |
|---|---|
| Asset and location | Plant, line, room or rack, so people can find it |
| Function | What it does, such as ERP database, label printing, historian, file shares |
| Business owner | The person who can say what happens if it stops |
| Hardware model and age | Warranty status, spare parts availability |
| Operating system and version | End-of-support date |
| Key applications and their vendors | Whether those vendors support newer platforms |
| Network zone | Office network, production network, or both |
| Backup status | Whether it is backed up and when a restore was last tested |
| Support contract | Hardware maintenance, software subscription, renewal date |
| End-of-support date | For hardware, operating system and key software |
Gather the data from several sources: network and endpoint management tools where they exist, vendor portals, purchase records and, unavoidably, walking the plant. Equipment in production areas is often missing from central records because it was bought by engineering or a machine supplier rather than IT.
Keep the inventory in one place with a named owner. A spreadsheet is acceptable to start; what matters is that it is maintained.
Not every out-of-date asset needs the same urgency. Score each one on two dimensions.
Likelihood of a problem: age and warranty status, whether security updates are still available, known reliability issues, spare parts availability and how exposed it is on the network.
Impact if it fails: whether production stops, slows or continues; how long recovery would take; whether quality, safety or compliance records depend on it; and how many sites or lines it affects.
A simple matrix helps:
| Low impact | High impact | |
|---|---|---|
| High likelihood | Plan replacement this year | Act now: replace, isolate or add protection |
| Low likelihood | Monitor; replace at normal end of life | Plan replacement and test recovery |
High-impact assets on the production side deserve particular care. Changes near production control systems can affect equipment and safety, so involve controls or operational technology engineers in any change there. NIST's Guide to Operational Technology Security (SP 800-82 Rev. 3) is a useful reference for the security side of connecting business and production networks.
For each high-priority asset, choose one of five actions:
The application vendor usually decides which options are available. Contact vendors early: some quality, labeling and machine-interface software is certified only on specific operating system versions, and getting a supported upgrade path can take months. If the software itself is the obstacle, our guide to legacy software modernization for manufacturers covers the application side.
Lifecycle work fails when it competes with production. Build the plan around the plant's calendar.
The following example is invented for illustration.
A manufacturer with two plants finds 46 servers and network devices in its inventory, 11 more than its IT records showed. Six servers run an operating system approaching end of support, including the server hosting its label printing and shipping software. Two core switches on the production network are past the manufacturer's end-of-sale date, with spare parts becoming hard to find.
Ranking by impact puts the label printing server and the core switches first, because both would stop shipments. The company confirms that the label software vendor supports a newer operating system, schedules the server replacement for the December shutdown, and orders replacement switches for the same window, with the old switches kept as spares. Four lower-impact servers are virtualized over the following quarter, and the remaining end-of-support server, which runs an unsupported test application, is isolated on its own network segment while the quality team evaluates replacements.
Some assets will stay in service past their support dates because a machine, a certified process or a vendor depends on them. Reduce the risk deliberately rather than hoping nothing happens:
A predictable refresh program is easier to fund than a series of emergencies. Group assets by expected replacement year, attach an estimated cost from current quotes, and present finance with a three- to five-year schedule. Separate capital items, such as servers and switches, from operating items, such as support contracts, subscriptions and extended security updates. Review the schedule annually: some assets will last longer than planned, while vendor announcements may bring others forward.
| Role | Responsibility |
|---|---|
| IT lead or managed provider | Inventory, monitoring, patching, refresh planning and execution |
| Plant or operations manager | Change windows, production priorities, acceptance |
| Controls or OT engineering | Any change touching production equipment or networks |
| Application owners | Vendor contact, testing and sign-off |
| Finance | Capital planning and support contract renewals |
Dependencies to track include vendor certification of software on new platforms, hardware lead times, shutdown calendars and support contract renewal dates.
IT asset lifecycle management is the practice of tracking every server, network device, storage system and critical workstation from purchase to retirement: what it runs, who owns it, when support ends and when it should be upgraded, replaced or retired. Its purpose is to replace emergencies with planned, budgeted refreshes.
A common way to describe it is plan and procure, deploy, operate and maintain, upgrade or refresh, and retire and dispose. In manufacturing, the operate and refresh stages need extra care because changes near production systems must fit around shutdowns and involve controls engineers.
Microsoft has stated that Windows Server 2016 reaches the end of extended support on January 12, 2027. After that date, systems still running it need an upgrade, replacement, migration, isolation or a paid extended security update arrangement.
Reduce the risk deliberately: segment the network so the system reaches only what it needs, remove internet access and unnecessary remote tools, restrict accounts, keep tested backups and spares, and record the decision with an owner and a review date.
Start the inventory this month, beginning with servers and network devices that production depends on, and check every operating system against its vendor's lifecycle page. If any business-critical systems run Windows Server 2016 or older, put a decision on them on the agenda before the end of the year.
Growix's IT Infrastructure Management service administers servers and technology assets across their full lifecycle, from provisioning through upgrades to retirement. If you want an independent view of where your risks are before committing to a plan, our IT Consulting & Audits team reviews your environment and produces a prioritized plan.
Lower the cost of serving each customer, not just the monthly bill. A four-step method for SaaS teams on AWS, Azure or Google Cloud, with a worked example.
Migration fixes platform limits; optimization fixes waste and performance. Diagnose which constraint you have, then sequence the work so you never migrate what you should retire.
Manufacturers rarely need a big-bang replacement. Audit the interfaces between ERP, inventory and production, then modernize one boundary at a time without stopping the plant.
