A common question is if you should record historical data in the historian for the ERP Layer.
Jeremy Theocharis from United Manufacturing Hub (UMH), has answered this excellently:
A historian or time-series database is mainly used for recording data points over time, handling high-frequency data, and capturing all the detailed fluctuations in a system. On the other hand, an ERP system generally logs high-level information at a much lower frequency (like noting down the completion time of a certain order).
Duplicate data with Unified Namespace (UNS)?
Regarding your question about data duplication between the UNS and the ERP system: yes, there can be overlapping data, but this is not necessarily a negative aspect. It is actually considered a best practice in the industry. > The ERP system remains the primary and trusted source for the data, and the UNS essentially mirrors the updates happening in the ERP system. The purpose of having this “duplicated” data is to facilitate real-time responses and actions on the shop floor (like changing the color of a traffic light to signal the start of an order) and to enable cloud-based data analyses which can be essential for optimizing various processes.