Manufacturing ERP IT Requirements: What SAP, Oracle, Epicor, and Infor Need From Your Infrastructure

The Manufacturing ERP Landscape

Manufacturing ERP systems differ from generic business ERP in one critical way: they must integrate with shop floor systems — MES, SCADA, machine interfaces, quality systems, and production scheduling. This integration requirement means IT infrastructure decisions in manufacturing affect both office operations and production.

The major platforms by deployment model:

• Large enterprise: SAP S/4HANA (cloud or on-premise), Oracle Cloud ERP / Oracle E-Business Suite, Infor LN, Infor M3
• Mid-market: Epicor Kinetic, SYSPRO, Sage X3, IFS Applications
• Small to mid-market: JobBOSS², E2 Shop, Macola, NetSuite for Manufacturing

SAP S/4HANA IT Requirements

SAP S/4HANA is available in three deployment models with dramatically different IT requirements:

• SAP S/4HANA Cloud (Public Edition): Cloud-native SaaS. IT requirements: reliable internet, standard endpoint management, Azure AD or SAP BTP identity management. SAP manages all infrastructure.
• SAP S/4HANA Cloud (Private Edition): Hosted on AWS or Azure but managed by SAP. More customization allowed. IT requirements: similar to public cloud, but integration middleware (SAP Integration Suite or third-party) needs configuration.
• SAP S/4HANA On-Premise: Runs on customer hardware or IaaS. Requires SAP-certified hardware configurations, HANA-optimized servers (in-memory database with significant RAM requirements — typically 512GB–4TB RAM for production systems), Linux OS expertise, SAP Basis administration, and Oracle-like DBA skills for HANA database administration.

SAP ECC (the predecessor to S/4HANA) installations still running on-premise require: SAP Basis administrators, Oracle or MS SQL database administration, ABAP development environment for customizations, and a scheduled migration plan to S/4HANA before SAP's mainstream maintenance end date (2027 for standard, 2030 for extended maintenance).

Oracle ERP (Cloud and E-Business Suite) IT Requirements

• Oracle Cloud ERP (Fusion): Cloud-native SaaS. Reliable internet, current browser, Oracle Identity Cloud Service for SSO. Oracle manages infrastructure.
• Oracle E-Business Suite (EBS) 12.2: On-premise. Requires Oracle Linux (supported) or Red Hat Enterprise Linux, Oracle Database 19c, Oracle Application Server. Oracle DBA expertise is essential — EBS 12.2 has specific Oracle Database configuration requirements. Oracle extended support ends in 2025 (Premier Support ended in 2023).
• JD Edwards EnterpriseOne: Common in discrete manufacturing. Available cloud-hosted via Oracle Cloud Infrastructure or on-premise. On-premise requires Oracle Database and WebLogic Server administration.

Epicor Kinetic IT Requirements

Epicor Kinetic (formerly Epicor ERP) is the most common ERP in mid-market manufacturing and has both cloud and on-premise options:

• Epicor Kinetic Cloud: SaaS hosted on Epicor's cloud infrastructure. IT requirements: reliable internet (50Mbps+ for multi-user environments), current browsers, and integration configuration for shop floor connections.
• Epicor Kinetic On-Premise: Windows Server 2019+, SQL Server 2019+, IIS for web services, dedicated server hardware. Epicor-specific SQL Server configurations (filegroups, maintenance plans) differ from standard SQL Server setups.
• Integration with Epicor MES (Advanced MES): Requires network connectivity between shop floor devices and the Epicor server — this is where OT/IT boundary considerations become relevant.

Shop Floor Integration: The Unique Manufacturing IT Challenge

Every manufacturing ERP eventually needs to connect to the shop floor:

• MES integration: Manufacturing Execution Systems (Epicor Advanced MES, Plex, Apriso) collect production data from machines and workers. They need real-time connectivity to the ERP for job scheduling, material consumption, and quality data.
• Machine connectivity: Modern CNC machines, injection molders, and assembly equipment can send production data via OPC-UA, MQTT, or proprietary protocols. Connecting this data to your ERP requires an IoT platform or middleware.
• Barcode and RFID systems: Warehouse and shop floor barcode scanning requires server-side inventory integration, network coverage throughout the facility, and hardware (scanners, printers) that IT must support.

This integration complexity is why manufacturing IT support is fundamentally different from generic business IT support. See our guide on industrial IoT security for the security considerations around shop floor connectivity.

Common ERP IT Failures in Manufacturing

• Insufficient server RAM: ERP performance is RAM-limited. Undersized servers create slowdowns that get worse as databases grow — not better.
• No SQL Server maintenance: ERP databases require weekly index maintenance. Without it, query performance degrades significantly over 12–18 months.
• Backup not including ERP database: The ERP database is often excluded from standard backup jobs or backed up inconsistently. Test restoration quarterly.
• No integration monitoring: ERP-to-shop-floor integrations fail silently. Without monitoring, you discover an integration has been broken for two weeks only when inventory numbers are wildly wrong.

Frequently Asked Questions

How often does manufacturing ERP software need to be upgraded?

Major ERP versions are typically supported for 5–10 years. The real driver is vendor support — when your ERP vendor ends mainstream support, you're running without security patches, which creates both cybersecurity and business risk. Plan for major upgrades every 3–5 years, with annual maintenance releases in between.

What is the IT cost of running SAP versus Epicor?

SAP S/4HANA on-premise requires SAP Basis administrators (typically $90–$130/hour for skilled consultants), HANA-certified hardware ($150K–$500K for a production system), and Oracle-level database expertise. Epicor on-premise is significantly lower — standard SQL Server administration, Windows Server hardware, and Epicor-certified IT providers. Cloud versions of both eliminate infrastructure costs but add subscription fees.

Can a generalist MSP support our manufacturing ERP?

For the server and network infrastructure underneath the ERP, yes — a qualified MSP can handle Windows Server, SQL Server, networking, and backup. For ERP-specific application support (Epicor configuration, SAP Basis, Oracle DBA), you need ERP-specific expertise that most generalist MSPs don't have. Many manufacturers use their MSP for infrastructure and a separate ERP consultant for application support.