Document Title
MANUFACTURING DATA HUB
FAQ’s
#1
Is an MDH like a kind of middleware?
It certainly does sit between source and consuming systems and it does transform data moving between them much like middleware.
An MDH though has a few more tricks up it’s sleeve:
- manufacturing native data model
- flexibility to respond to any request from a subscriber
- supports both real time and historic data
- complex multi-source payloads in a single transaction
#2
Is an MDH cloud hosted or on-premise?
The Rhize MDH has been designed and developed from the ground up to support global manufacturing. And that means one thing above all else.
Flexibility is paramount.
- ✓ Public or private cloud? Sure thing
- ✓ On-premise, even behind a DMZ? Of course
- ✓ Hybrid model to support multi-site deployments? Absolutely
#3
What existing systems does an MDH replace?
The primary functions of an MDH are as a data hub - a central, semantic, context rich operations history; and as an orchestrator - moving data between systems automatically on event.
In performing these functions, all existing systems are retained and connected to the MDH as sources and/or consumers.
The MDH also supports application development, in which case existing applications may be augmented or replaced entirely.