←

SaaS in Manufacturing: Definition, Benefits and MES Pricing

By Uwe Kobbert · Last updated: March 2026

What Is Software as a Service (SaaS)?

Software as a Service (SaaS) is a software delivery model in which the application is hosted by the provider, delivered over the internet, and paid for on a subscription basis. The customer does not purchase, install, or maintain the software on local servers. Instead, the provider is responsible for infrastructure, updates, security, and availability. The customer accesses the application through a web browser or a dedicated client.

In general business applications (CRM, ERP, email, project management), SaaS has been the default delivery model for over a decade. In manufacturing, the shift to SaaS is more recent and more consequential. A SaaS-based Manufacturing Execution System (MES) changes not only how the software is delivered but how fast a plant can start capturing real-time production data, how easily the system scales to additional plants, and how much internal IT capacity is required to operate it.

SaaS vs. On-Premise vs. Hybrid: Delivery Models Compared

Dimension	SaaS (Cloud-native)	On-Premise	Hybrid (Lift-and-Shift)
Infrastructure	Provided by the vendor. No local servers, no database management, no operating system maintenance.	Customer provides and maintains all infrastructure: servers, operating systems, databases, network, backups.	Software runs in a cloud VM but was designed for on-premise. Customer or vendor manages the VM infrastructure.
Upfront investment	Zero or minimal. No license fees, no server hardware, no infrastructure project. Monthly or annual subscription.	High. License fees (typically EUR 50,000 to 500,000+), server hardware, database licenses, implementation services.	Medium. Cloud VM costs replace server hardware, but license fees and implementation effort remain similar to on-premise.
Ongoing costs	Predictable monthly subscription. Updates, maintenance, and support included. No hidden IT costs.	Annual maintenance fees (typically 18 to 22% of license cost). Internal IT staff for server management, updates, backups. Upgrade projects every 3 to 5 years.	Cloud VM costs + maintenance fees. Updates still require planned downtime and testing. Internal IT effort reduced but not eliminated.
Updates	Automatic. All customers always run the latest version. No downtime, no update projects, no version fragmentation.	Manual. Updates require planning, testing, downtime, and often additional services from the vendor. Many customers run versions 2 to 5 years behind current.	Semi-automatic. Updates easier than on-premise but still require testing and planned downtime.
Time to first value	Hours to days. Account provisioned instantly. IoT gateways installed in 2 to 4 hours per machine. First dashboards live on day one.	Weeks to months. Server procurement, installation, network configuration, software installation, database setup before first machine connection.	Days to weeks. Faster than on-premise but VM provisioning, configuration, and testing still required.
Multi-plant scalability	Add a new plant by adding IoT gateways and configuring the plant in the same platform instance. Minutes to hours of configuration work.	Each plant typically requires its own server infrastructure. Cross-plant reporting requires additional integration projects.	Easier than on-premise but each plant may require its own cloud VM instance.
Global access	Any browser, any device, anywhere. Management dashboards accessible globally. No VPN required.	Local network access. Remote access requires VPN configuration, firewall rules, and additional security measures.	Accessible via internet but may require VPN for certain functions depending on architecture.

CAPEX vs. OPEX: The Financial Impact of SaaS

The shift from on-premise to SaaS is fundamentally a shift from capital expenditure (CAPEX) to operating expenditure (OPEX). For manufacturing companies, this has significant financial and organizational implications.

Financial dimension	On-Premise (CAPEX)	SaaS (OPEX)
Budget approval	Requires investment approval for EUR 100,000 to 500,000+ (license + infrastructure + implementation). Often requires board-level sign-off. Lead time: months.	Monthly subscription. Typically within operational budget authority of plant manager or COO. Lead time: days to weeks.
Cash flow	Large upfront payment before any value is delivered. Depreciation over 3 to 7 years. Cash flow impact concentrated in year one.	Small monthly payments that start when the system is productive. Cash flow impact distributed evenly over time.
Risk profile	High upfront investment risk. If the project fails or the vendor underperforms, the investment is largely lost. Switching costs are extreme.	Low risk. Cancel the subscription if the system does not deliver. No sunk cost in infrastructure. Switching costs are low.
Total cost of ownership (3 years)	License + infrastructure + implementation + 3 years maintenance + internal IT costs. Hidden costs: upgrade projects, server replacements, database license renewals.	36 months of subscription. All-inclusive: updates, support, infrastructure, security. No hidden costs. Predictable budget.
Scalability cost	Adding a new plant requires new server infrastructure, additional licenses, and implementation services. Significant incremental cost per plant.	Adding a new plant requires additional IoT gateways and configuration. Flat-rate per plant pricing. No infrastructure investment.

Why SaaS in Manufacturing Is Different from SaaS in the Office

SaaS for email, CRM, or project management runs entirely in the browser. The data originates from human input and lives exclusively in the cloud. SaaS for manufacturing is fundamentally different because the data originates from machines on the shop floor, not from keyboards.

Challenge	Why it is specific to manufacturing SaaS	How it is solved
Machine connectivity	Data must be captured from physical machines (PLCs, digital I/O signals, OPC UA servers) and transmitted to the cloud. This requires hardware at the edge.	IoT gateways installed at each machine or machine group. Digital signals, analog inputs (4-20 mA), OPC UA. Data transmitted via MQTT over LTE, Wi-Fi, or Ethernet.
Offline resilience	A factory cannot stop producing if the internet connection drops. A manufacturing SaaS system must handle connectivity interruptions without data loss.	IoT gateways buffer data locally during connectivity interruptions. When the connection is restored, buffered data is transmitted in order. No data loss, no production interruption.
Real-time data processing	Manufacturing decisions require real-time data: machine status, cycle counts, alarm states. Latency of minutes (acceptable for email) is unacceptable for production monitoring.	Edge-to-cloud pipeline optimized for low latency. Machine signals processed at the IoT gateway and transmitted in near real-time. Dashboard updates within seconds.
IT/OT convergence	Manufacturing IT departments are protective of the OT network (machines, PLCs, SCADA). A cloud system that requires inbound firewall rules is rejected immediately.	IoT gateways initiate outbound connections only. No inbound firewall ports required. IT/OT segmentation preserved. TLS encryption for all data in transit.
ERP integration	Manufacturing SaaS must exchange data bidirectionally with on-premise ERP systems (SAP, Infor, Navision). This is not a simple API call but a complex integration.	Bidirectional ERP connectors: SAP R3 (ABAP IDoc), InforCOM (file interface), Navision (file interface). Order data from ERP, production data back to ERP. REST API for custom integrations.
Brownfield machines	Most manufacturing plants have machines from 1990 to 2024. A cloud MES must connect to machines without modern interfaces, without modifying the PLC, and without stopping production.	Digital I/O gateways capture basic signals (running/stopped, cycle complete, alarm) from any machine with electrical outputs. No PLC modification. No production interruption. Installation in 2 to 4 hours per machine.

How SYMESTIC Delivers SaaS MES

SaaS characteristic	How SYMESTIC implements it
Cloud-native architecture	Built from scratch on Microsoft Azure. Microservice architecture, API-first design. Not a lift-and-shift of on-premise software. No legacy code, no monolithic architecture.
Flat-rate per plant pricing	One flat-rate subscription per plant. Unlimited users, unlimited dashboards, unlimited shopfloor clients included. No per-user fees, no per-machine fees, no per-dashboard fees.
Automatic updates	All customers always run the latest version. Updates deployed centrally by SYMESTIC. No downtime, no update projects, no version management by the customer.
Implementation speed	Production KPIs: under 1 month for 10 machines. Full MES: under 6 months. Klocke (pharmaceutical packaging): all lines connected in 3 weeks. Carcoustics: 500+ machines in 6 months across 7 countries.
Multi-plant, multi-country	Single platform instance for all plants worldwide. Carcoustics: Germany, Poland, Slovakia, Czech Republic, Mexico, USA, China. Meleghy: Germany, Czech Republic, Hungary. Brita: Germany, UK.
Self-service scalability	Modular building block system. Customers add machines, configure dashboards, and extend functionality independently after initial onboarding. Meleghy, Carcoustics, Klocke, Brita all scaled independently.
Security and compliance	Microsoft Azure infrastructure. TLS encryption for all data in transit. Per-device authentication. Azure Active Directory integration (Enterprise tier). Data retention: 12 months (Professional), regulatory-dependent (Enterprise).
No local IT dependency	No local servers. No database management. No operating system updates. No backup strategy. IoT gateways connect via LTE, no LAN infrastructure required. Klocke: "All lines connected without any LAN infrastructure."

SaaS MES vs. On-Premise MES: Implementation Comparison

Implementation phase	On-Premise MES	SaaS MES (SYMESTIC)
Infrastructure setup	2 to 6 weeks. Server procurement, OS installation, database setup, network configuration, firewall rules, VPN setup.	0 days. Account provisioned instantly. No local infrastructure.
Software installation	1 to 2 weeks. Software installation, configuration, license activation, initial testing.	0 days. Browser-based access. No installation.
Machine connectivity	2 to 8 weeks. PLC programming, network cabling to each machine, protocol configuration, signal mapping.	2 to 4 hours per machine. IoT gateway installation. Digital signals or OPC UA. No PLC modification. No network cabling (LTE).
Configuration and dashboards	2 to 4 weeks. Configuration by vendor consultants or trained internal staff. Often requires vendor services for changes.	Hours to days. Onboarding training (8 to 12 hours). Key users configure dashboards, KPIs, and reports independently.
ERP integration	4 to 12 weeks. Custom integration development. Testing. Often the longest phase of the project.	1 to 4 weeks. Standard ERP connectors (SAP R3 IDoc, InforCOM, Navision). Bidirectional. Tested interfaces, not custom development.
Total time to production	3 to 18 months. Average for mid-market: 6 to 12 months.	Production KPIs: under 1 month. Full MES with ERP integration: under 6 months.

Frequently Asked Questions About SaaS in Manufacturing

Is SaaS secure enough for manufacturing data?

Yes. Cloud providers like Microsoft Azure invest more in security than any individual manufacturing company can. Azure provides ISO 27001, SOC 2, and GDPR compliance. All data in transit is TLS-encrypted. Each IoT gateway authenticates with a unique device identity. No inbound firewall ports are required. Data residency can be configured to specific Azure regions (e.g., Europe).

What happens when the internet connection drops?

Production continues without interruption. IoT gateways buffer machine data locally during connectivity gaps. When the connection is restored, buffered data is transmitted to the cloud in order. No data is lost. Dashboards show historical data from before the outage and resume live data when connectivity returns. This is a fundamental architectural requirement for any manufacturing SaaS system.

Is SaaS more expensive than on-premise in the long run?

In most cases, SaaS is less expensive over a 3 to 5 year period when all costs are included. On-premise TCO must account for license fees, server hardware (replaced every 4 to 5 years), annual maintenance fees (18 to 22% of license), internal IT staff for server management, and upgrade project costs every 3 to 5 years. SaaS TCO is the subscription fee, and that fee includes everything: updates, infrastructure, support, security.

Can a SaaS MES integrate with our on-premise ERP?

Yes. Bidirectional ERP integration is a standard capability. SYMESTIC provides standard connectors for SAP R3 (ABAP IDoc), InforCOM (file interface), and Navision (file interface). Order data flows from ERP to MES, production data (quantities, times, statuses) flows back from MES to ERP. A REST API is available for custom integrations with other ERP systems.

What is the difference between cloud-native SaaS and a hosted on-premise system?

Cloud-native SaaS is built from the ground up for the cloud: microservice architecture, automatic scaling, continuous deployment, multi-tenant or single-tenant by design. A hosted on-premise system (lift-and-shift) is traditional software running in a cloud VM. It still requires manual updates, planned downtime, and often still needs per-server licensing. The user experience, update frequency, and scalability are fundamentally different.