The Big Picture
No single system runs a modern manufacturing operation. It takes an ecosystem of interconnected systems — each handling a different aspect of the business — all sharing data to keep planning, execution, and analysis in sync. Understanding how these systems fit together is what separates people who use software from people who can improve how an operation works.
This is the knowledge that comes from working in complex manufacturing environments like aerospace and defense, where a single product can involve hundreds of thousands of parts, dozens of work centers, and multiple systems all talking to each other.
Interactive: Explore the Ecosystem
The Five Layers of Manufacturing Systems
Manufacturing systems are organized in layers, roughly following the ISA-95 standard. Each layer operates at a different time scale and serves different users:
| Layer | Systems | Time scale | Key users |
|---|---|---|---|
| Engineering | PLM, CAD/CAM/CAE | Months to years | Design engineers, configuration managers |
| Business Planning | ERP, S&OP, demand planning | Weeks to months | Planners, buyers, finance, management |
| Scheduling | APS, finite scheduling | Days to weeks | Production schedulers, planners |
| Execution | MES, SCADA, quality systems | Minutes to hours | Operators, supervisors, quality techs |
| Analytics | BI, dashboards, reporting | Real-time to monthly | All levels — adapted to role |
Critical Data Flows
The ecosystem only works when data flows correctly between systems. Here are the most critical connections:
Downward flows (plan → execute)
Upward flows (actual → plan)
Integration Challenges
In reality, getting these systems to talk to each other is one of the hardest problems in manufacturing IT:
Common integration failures
- PLM BOM doesn't match ERP BOM — different structures, different part numbers
- ERP lead times are months out of date — scheduling is fiction
- MES data never flows back to ERP — actuals and plan diverge
- BI dashboards show stale data — decisions based on last week's numbers
- "Islands of automation" — each system works alone
Integration best practices
- Single source of truth per data type (BOM owns PLM, inventory owns ERP)
- Automated bidirectional interfaces with error handling and monitoring
- Master data governance — who owns each data element and keeps it current
- Near-real-time data feeds (not nightly batch jobs) for execution systems
- Integration middleware (MuleSoft, Boomi, Informatica) for complex landscapes
Where SymplProcess Fits
SymplProcess operates at the execution and analytics layers — providing structured shift-level data capture (like a lightweight MES) and trend analysis (like purpose-built BI) for operations that need daily operational visibility without the complexity and cost of full enterprise system deployments. It complements rather than replaces ERP and MES, and for many mid-size operations, it's the most practical way to bridge the gap between "we have an ERP" and "we actually know what's happening on the floor."
Key Takeaway
Remember This
A production system is an ecosystem, not a single tool. PLM defines the product, ERP plans the production, APS optimizes the schedule, MES executes on the floor, and BI turns it all into intelligence. The magic happens in the connections between them — data flowing down from plan to execution and flowing back up from reality to plan. Understanding this ecosystem is what allows you to see the whole picture and improve the system, not just your corner of it.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.