A lot of the data that’s collected for our OSS / BSS are never used. Read about ETL data pedigree before and after landing on the OSS / BSS database!
Origin means traceability of the data, or in this case their etl data lineage
The origin of the data becomes an interesting concept in this context. In a typical sense, data origin means being able to register a source system or address (e.g. from a specific Element Management System [EMS]) and reference it to a data point loaded into an OSS or BSS database. This means tracing his lineage before reaching the OSS / BSS database. However, we like to think that his lineage should also be tracked after landing on the OSS / BSS database.
The origin of the initial load is important to the data engineer
Post-debit origin is more important to data analysts. We claim that it also has the potential to inform the data engineer and his projects, especially if you never use large amounts of data and only increase the ETL Data Lineage (and cure) costs. The broad coverage provided by the SunVizion package means that there is a large variety of data available to enrich other data points. It is compiled in a common format, making it well suited for cross-linking.
