BDNA Data Platform 5.5
Normalize gap-fill process refers to the process of reviewing 'Unknown' entries from the Normalize result and turning them into 'Known' entries (either 'Mapped' or 'Irrelevant').
Some definitions around the Normalize gap-fill:
| • | Known: Data that have been identified in Normalize (as represented by either the 'Mapped' or 'Irrelevant' signatures). |
| • | Mapped: Mapping signatures where the discovered data is mapped to Technopedia entries. This represents the 'Relevant' data, as well as raw data that has been deterministically identified and is aligned to Technopedia. |
| • | Irrelevant: This represents the signatures where the discovered data has been identified and deemed to be not relevant in order to identify the assets. While irrelevant data is not discarded, it's filtered out to remove the 'noise' created by all the extraneous data. |
| • | Unknown: This represents raw data that has not been processed by BDNA Normalize. It's either completely new data or existing data that has not been categorized as either 'relevant' (i.e. Mapped) or 'irrelevant' (i.e. marked as 'Irrelevant'). This is subject of the “gap-fill” process. Note that there may still be potentially entries that remain 'unknown' (typically customer developed custom software that can be identified and mapped using the BDNA Private Catalog capability) or it may be data that falls outside the SLA, which most of the time represents items that contribute little or nothing regarding the identification of an asset. |
BDNA Data Platform 5.5 Administration Help Library02 August 2016 |
Copyright Information | Flexera |