“As I would not be a slave, so I would not be a master. This expresses my idea of democracy.”
One of the keys to data integrity is to understand the data flows between your various systems and which is the data master and which are the data slaves for any given transaction.
In general, the network is the true source of truth, so it should always be the data master, pushing information up through EMS, NMS then up to OSS. The perfect example here is in the case of alarm or performance data.
However, there are other situations where the OSS is the data master, pushing information down to the network. Examples of this include the provisioning of a customer service based on data on their order form. Another example includes the global enforcement of naming conventions for devices, customer services, etc, as well as managing work-force activities, etc.
Where possible, it is important to use feedback paths to provide reconciliation reports, such as cross-referencing the data in the OSS database with the data from the EMS or the device itself. The feedback path of a carefully planned reconciliation is key to continual monitoring and improvement of your data integrity.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email