The basis for unified data is data provenanceand a model of how data propagates to the processes that consume the data. Because “Like DNA, data has provenance”. Though it may seem strange to speak about DNA in a discussion about data. Yet, it is especially in regard to data that provenance is extremely important. And common sense tells us that everything we know of has provenance and everything has a purpose.
And data is no different. Transposing this reality to software means that system applications need to preserve data provenance. And at the same time track how data propagates to all processes that require the data. For example, spare parts are identified by manufacturers, spare part providers and buyers, in different type of processes, from planned maintenance, to requisitioning, vendor selection, despatch up to deliveries onboard vessels.
Provenance
When one thinks that components are originally sourced from their manufacturers, and it is manufacturers who define the ways in which we identify parts, then provenance becomes imperative. Since everything that happens to a component once it enters the real world are data instances of that original component data. Consequently, Technical data, to retain its cognitive value five and ten years down the line, requires technology that upholds data integrity by design.
No matter where and how diversely data propagates, with Task Assistant® Central Component Library, data integrity persists. This can be simply explained by the fact that data provenance is retained.