Decentralized Architecture
quiMSI employs a thin service-layer with plugin abstraction, enabling update-friendly design and autonomous operation.
MES/PAS-X
Manufacturing Execution System
quiMSI
Service Layer
DeltaV Plugin
InBatch Plugin
OPC UA Plugin
Custom Plugin
Each plugin handles protocol-specific communication, translating to standardized MSI messages
The quiMSI Difference
| Integration Aspect | Without quiMSI | With quiMSI |
|---|---|---|
| Integration Time | 3-6 months per equipment | Hours to days with certified plugins |
| Custom Code | Extensive custom development for each vendor | Zero custom code with plugin library |
| Updates & Maintenance | Production downtime for updates | Hot-swappable plugins, zero downtime |
| Vendor Lock-in | Proprietary protocols & dependencies | MSI standardization, vendor independent |
| Failure Isolation | Cascading failures across equipment | Autonomous instances, isolated failures |
| GxP Compliance | Complex validation per integration | Pre-validated plugins, 21 CFR Part 11 ready |
| Message Reliability | Message loss risk during disruptions | Guaranteed delivery with retry & queuing |
Resilience & Reliability
Autonomous Instances
Each plugin operates independently with its own thread and failure isolation.
Guaranteed Delivery
Persistent queuing and automatic retry ensure messages always reach their destination.
Parallel Handling
Process multiple MSI queries concurrently without blocking operations.
Update-Friendly
Hot-swap plugins and update components without disrupting production.
OPC UA Method-Based Communication
Unlike REST-based approaches, quiMSI leverages OPC UA methods for bi-directional communication, reducing certificate management overhead and ensuring shop-floor compatibility.
- Method-based message transfers (MSI-in, MSI-out)
- Reduced certificate operations vs REST APIs
- Native integration with existing OPC infrastructure
- Standards-compliant communication layer