Software
IT Support for Manufacturers and Machine Shops: Networks and Software
IT support for manufacturers starts on the shop floor: a network sized for the machines and the CAD files, a file server only the right people can reach, and a plan for the morning something fails. After that comes the software, usually the one job your ERP or your spreadsheets can’t do. Both are quoted in writing after a free audit.
A plant’s office runs like any office. The shop floor doesn’t. It has CNC programmers moving large files, machines and computers that can’t go down mid-shift, and people who share a handful of terminals rather than owning a laptop each. IT that treats the plant like an office tends to fail in the same few places.
Networks on a shop floor
The most common thing we find is a network that grew without a plan: equipment bought for a business half the size, carrying far more than it was built for. What a shop floor network needs:
- Business-grade network equipment sized for the load, not the router the internet provider handed over.
- The office, the shop floor and any guest Wi-Fi kept apart, so a visitor’s phone and the CAD workstations aren’t on the same network.
- A file server with access set by role, so the people who need the 3D models and programs can reach them and nobody else can.
- Protection against malware and ransomware on every machine that can reach those files.
- Backups that have been restore-tested, and a written plan for a critical failure.
- Documentation of all of it, so the next person who works on it isn’t guessing.
When the ERP cannot do the one thing you need
Most of the machine shop software we see in Ohio plants is an ERP, an accounting package, spreadsheets, or some of each. ERP support for a small manufacturer is often less about the ERP than about the one job it doesn’t do: a quote that needs part-level costs, an engineering change that has to reach the floor, an order flow your customers expect online. There are three ways to handle that gap:
- Configure what you have, if the system can do the job and nobody has set it up.
- Build a small tool beside it that reads from it and writes back, so the ERP stays the record and the tool does the one job.
- Replace it, when the workarounds have become the system.
Grimm Scientific Industries in Marietta ran on spreadsheets until we built an ERP from scratch around the way the company already worked. It covers cost accounting down to the individual part, engineering change orders and a live dashboard of orders and alerts. The company has quadrupled in size on it since, and we still support and extend it.
Not every gap is inside the plant. When Medlining Machine Works lost its only online sales channel, it needed a store that could sell product bundles and let buyers pick a barrel thread as they added an assembly to the cart. We built it, and they now run it themselves; the Medlining Machine Works case study covers how. Our custom software page covers how we scope this kind of work, and our post on build vs buy covers when not to.
Support pricing for a 40-person plant
We don’t publish a per-seat price, because two plants of the same size can need very different support. Every engagement is quoted in writing after a free audit. What sets the number for a plant with around 40 people:
- How users are counted. Per-user pricing suits an office where everyone has a laptop. On a shop floor where several people share one terminal, per-device pricing is often fairer. Ask how each quote counts a shared machine.
- What sits behind the people: servers, the firewall, the wireless and the machine-side computers, and whether they are in the fee or priced per device on top.
- Projects, such as rebuilding the network, which are scoped and priced on their own.
- Trips on site. Most support is remote. Anything more than three hours from our office in Marietta is planned as a full on-site day.
Our post on what managed IT support costs per user shows how to compare quotes line by line, and our IT support page covers the help desk, monitoring and backups.
What we found at Athens Mold and Machine
Athens Mold and Machine machines tire molds, and its CNC programmers build the 3D models the molds are cut from. It had no IT department, no disaster plan and patchy network security. The audit found that age was only part of the problem. A small router from the internet provider was carrying several powerful computers and systems.
We rebuilt the network from the ground up as a fresh, fully documented setup, specified and installed managed equipment sized for the business, and took over as its IT team. The result was finer control over who can reach the file server, protection against malware and ransomware, and a disaster recovery plan where there had been none. The full write-up is in the Athens Mold and Machine case study.