Cloud MES Architecture for Real-Time Pharma Process Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current manufacturing systems in pharmaceutical and biopharmaceutical industries face challenges in integrating cloud computing for efficient process control, leading to high drug costs and inconsistent quality, with a need for a global approach to enhance production efficiency and consistency.

Innovation Solution

A cloud-based manufacturing execution system (MES) is integrated into pharmaceutical and biopharmaceutical manufacturing processes, using software programs for continuous monitoring and control of active and inactive ingredients, with real-time data analytics and endpoint protocols to ensure purity and consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud-based MES is integrated into pharmaceutical manufacturing processes, then production efficiency and quality consistency are improved, but system complexity and integration challenges increase

Engineering Contradiction:
Improveproduction efficiencyVSAvoidsystem integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based MES platform as an intermediary layer between manufacturing execution systems and cloud computing infrastructure. This mediator handles data translation, protocol conversion, and integration logic, allowing legacy manufacturing systems to connect with cloud services without requiring complete system replacement or complex point-to-point integrations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system architecture is divided into modular components: edge computing devices for local data processing, cloud-based analytics engines, and distributed manufacturing execution modules. This segmentation allows incremental implementation and reduces integration complexity by enabling independent deployment and scaling of specific functional modules.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If real-time monitoring and control is implemented across global manufacturing sites, then quality consistency is improved, but data transmission latency and network dependency increase

Engineering Contradiction:
Improvequality consistencyVSAvoiddata transmission latency
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system pre-processes and validates data at edge computing devices before transmission to the cloud, performing preliminary quality checks and filtering operations locally. This preliminary action reduces the amount of data requiring transmission and ensures critical quality parameters are captured immediately, minimizing latency impacts on quality decision-making.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Each manufacturing site operates with localized edge computing capabilities that maintain autonomous quality monitoring and control functions. This local quality assurance ensures that critical manufacturing processes continue with minimal disruption even when network connectivity is degraded or latency occurs, while still contributing to global quality consistency.

Inventive Principle:
Principle #3Local quality

3Ease of manufacture

If cloud computing is used for manufacturing process control, then operational costs are reduced, but reliability and security concerns increase

Engineering Contradiction:
Improveoperational costVSAvoidsystem reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The architecture incorporates redundant cloud service providers and failover mechanisms that are pre-configured to activate automatically upon detecting service degradation or security incidents. Data is replicated across multiple geographic locations before failures occur, ensuring business continuity and maintaining reliability while leveraging cost-effective cloud infrastructure.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Adaptability or versatility

If distributed control systems are replaced with cloud-based centralized control, then system flexibility is improved, but control loop response time may be affected

Engineering Contradiction:
Improvesystem flexibilityVSAvoidcontrol loop response time
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The system transitions from traditional hierarchical control architecture to a multi-dimensional control model where control functions are distributed across edge devices, local controllers, and cloud-based optimization engines operating simultaneously at different temporal and spatial scales. This allows fast local responses for critical control loops while cloud systems handle slower strategic optimization and adaptability functions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP3701704B1Cloud-controlled manufacturing execution system (clo-cmes) for use in pharmaceutical manufacturing process control, methods, and systems thereof
Publication Date: 2025.10.22 SMP LOGIC SYST
  • EP3701704B1 patent drawingFigure 1
  • EP3701704B1 patent drawingFigure 2
  • EP3701704B1 patent drawingFigure 3(A)~3(C)

AI summary

"Cloud" based manufacturing execution systems ("MES") and methods thereof used to control, execute, and monitor pharmaceutical or biopharmaceutical production processes and systems are disclosed herein. Consequently, the methods and systems provide a means to quality manufacturing on an integrated level whereby drug or biologic manufacturers can achieve data and product integrity and ultimately minimize cost.