Industrial · Legacy Infrastructure Manufacturers, fabricators, service shops, warehouses, and oilfield operators west of the river and through the legacy corridor. Shop floors that can’t stop, OT/IT separation that has to actually work, and backup strategies sized for the real downtime cost.
Free IT Risk Assessment
(918) 270-6600
IT Support for Tulsa’s Industrial & Legacy-Infrastructure Businesses.
20 min
Avg. resolution time
~4 mi
Avg. drive to client site
Since 2008
Serving Tulsa businesses
3
Neighborhoods in this cluster
The IT Reality Here West Tulsa, Red Fork, and Owen Park are the oldest continuously industrial parts of the city. West 21st, Southwest Boulevard, Gilcrease Museum Road, the corridor along I-244 — this is fabrication shops, HVAC wholesalers, machine shops, precision manufacturing, distribution yards, and oilfield service companies. Buildings that were industrial in 1955 and are still industrial now, with the cabling history to match. The IT reality is different from the office-tower cluster in three specific ways. First, there’s almost always a shop floor. CNC machines, ERP terminals on the line, barcode scanners, time clocks, and a handful of Windows 7 PCs controlling equipment nobody wants to touch. That’s OT — operational technology — and it has to be separated from office IT without getting in the way of how the floor actually runs. Second, the cost of a bad day is counted in shifts, not hours. A server down on Tuesday morning means a production run that doesn’t go out Tuesday night, which means penalties with the customer and overtime on Wednesday. Backup and disaster recovery aren’t an optional line item — they’re the difference between a bad morning and a bad quarter. Third, there’s rarely an in-house IT person. The owner or plant manager handles it, sometimes with a nephew who’s “good with computers,” until the day a ransomware email comes through and everything stops.
Older infrastructure, higher stakes, fewer IT people.
Cluster-Wide IT Challenges Individual pages cover what’s specific to each block. These are the patterns we see everywhere inside this cluster.
Six problems on every shop floor in this cluster.
OT on the same flat network as office IT
CNC controllers, PLCs, and shop-floor Windows machines sharing a subnet with payroll. One compromised office laptop, one ransomware event, entire floor is down. We separate OT and IT with firewalled VLANs and documented allowlists.
Legacy servers carrying the business
ERP on Server 2012, file shares on a SAN that’s been “about to fail” for five years, tribal knowledge about which service starts first on reboot. We migrate or virtualize on a real schedule — never cold-turkey — and document the rebuild procedure before we touch it.
Backup that’s never been tested
Backup software is running. Nobody’s actually restored from it in three years. Tapes rotate, drives fill up, notifications get ignored. We run quarterly test restores on every critical server so the first time you restore isn’t the first time you find out it doesn’t work.
Ransomware exposure without an IR plan
Industrial targets are prime for ransomware — attackers know downtime costs scale with production. Most shops in this cluster have no written incident response plan. We build one and practice the disconnect-and-restore procedure before it’s needed.
Cabling that dates to the Clinton administration
Cat3 in conduit, gigabit switches starved by 100Mb links they don’t know about, mystery runs between buildings over copper that should have been fiber. We survey, label, and rerun where it actually matters — not a top-to-bottom rebuild.
Warehouse and yard WiFi that drops mid-scan
Metal racking, concrete tilt-walls, scanners dropping between aisles. We design APs for the actual building — ceiling heights, metal surfaces, outdoor yard coverage — on Cisco Meraki or Fortinet, and we document the heatmap so the next change has a baseline.
Stack Composition More on-prem and more legacy than any other cluster we cover — because ERP, CNC, and production control still largely run there. Typical vendors: Microsoft Server, Hyper-V / VMware, Veeam / Datto backup, Fortinet and Cisco Meraki firewalls, Microsoft 365 email, ERP platforms like Global Shop, E2 Shop, Sage 100, and Epicor.
Stack composition across Tulsa’s industrial corridor.
Services Mapped to This Cluster Built around uptime-per-shift, OT separation, and recovery you can actually execute. Backup & DR, OT/IT separation, legacy server migration, and managed IT — in that order.
What we deploy on shop floors and industrial sites.
Managed IT for manufacturers
Flat-rate monitoring, patching, and on-call support sized for shops with 10–100 users. Starts at $200 per user per month for managed IT and cybersecurity. Includes documented runbooks for your ERP and production systems. Learn more
OT/IT separation
Shop-floor equipment, CNC, PLCs, and Windows 7 holdouts separated from office IT with firewalled VLANs and allowlisted flows. Designed so the line keeps running when the office network doesn’t. Learn more
Legacy server migration & virtualization
Incremental migration off Server 2012/2016, virtualization of legacy ERP on Hyper-V or VMware, and clean cut-over procedures that don’t depend on the one person who knows how to boot the thing. Learn more
Backup & disaster recovery
Datto or Veeam with off-site replication, RPO and RTO you can actually cite, and quarterly test restores documented. A ransomware-isolated immutable tier so the backup survives even when the primary environment doesn’t. Learn more
Services we deploy most in this cluster
Inside This Cluster Each one has its own infrastructure quirks. Click through for the neighborhood-level detail. The largest industrial footprint across the Arkansas River — fabrication, warehousing, oilfield services, and distribution running through older single-story metal buildings with mixed-era infrastructure. Southwest Boulevard and the historic Red Fork strip — smaller shops, auto-related trades, wholesalers, and mixed commercial with building stock going back to the oil-boom era. Just north of downtown along I-244 — trades, light industrial, and small service companies in rehabbed pre-war commercial buildings with the cabling history to match.
The neighborhoods we cover across the industrial corridor.
West Tulsa
Red Fork
Owen Park
Cluster FAQ Yes, and we do it as a phased project rather than a weekend rebuild. We start by documenting every flow into and out of the shop floor — which office machine prints to which label printer, which ERP screen talks to which CNC, which service account the scheduling app uses. Then we build the VLAN boundary with explicit allow rules for every flow we’ve documented, and cut over during a planned window. Production never stops because we’ve mapped it first. We don’t rip-and-replace. We audit the workload, virtualize it on modern Hyper-V or VMware with backup immediately in place, test restore into a sandbox before anyone trusts the migration, and then decommission the old hardware once the new environment has proved itself over a few cycles. For ERP platforms like Global Shop, E2, Sage 100, or Epicor we coordinate with the vendor directly on supported upgrade paths. Tiered. Immutable local backup (Datto or Veeam) with short RPO for fast restore of a corrupted file or VM. Off-site replication to our cloud or yours for site-loss scenarios. A documented RTO per system so you know production ERP comes back in four hours and accounting in twelve, not “we’ll figure it out.” And we test-restore every quarter and send you the log. That last step is the one most shops in this cluster have never had. Very common. You isolate them. They go on an OT VLAN with no internet access and a narrow allowlist back to the ERP server. No email, no browser, no file share beyond what the machine actually needs. They’re still Windows 7, but they can’t be reached from anywhere that matters. We also image the drive so that when the hardware eventually dies, you don’t lose the only working install. Yes. Our office is at 51st & Lewis — West Tulsa is roughly fifteen minutes across the river outside of rush. Red Fork and Owen Park are closer. Most issues we close remotely inside a 20-minute average, and when on-site is required we’re not routing a ticket to a call center in another state.
Questions we get from industrial operators.
Can you actually separate shop-floor OT from office IT without breaking production?
How do you handle legacy server migration — Server 2012, Hyper-V, old SANs?
What does your disaster recovery plan actually look like for a manufacturer?
We have Windows 7 machines running a CNC we can’t replace. What do we do?
We’re in West Tulsa. Are you actually going to drive out here?
Start With A Walkthrough An on-site visit, a real look at the server room and the shop floor, and an honest assessment of what needs to happen first. If the answer is “you’re in better shape than you think,” that’s what we’ll say. Month-to-month · No hard sell · Local Tulsa team since 2008
Let’s walk your shop before we propose anything.
Book a Call
(918) 270-6600
