During the initial setup of OneView360° the Standardization component conforms data sources to a Canonical Model (XML), a common definition and name for data. Conforming the inbound data to this model is a critical step in OneView360°.

The Canonical Model provides several key benefits:

• Common definition of data at an attribute level
• Interoperability of loosely coupled services
• Efficient tracking of data lineage
  • New data elements
  • New transaction type
  • New data sources
  • New enhancement services

To prepare the inbound data for downstream processing, OneView360° standardizes each data element by tagging based on a master dictionary of data. Once tagged, the data is known by the solution for all future processing. This standardization is the key to the overall flexibility of the solution.

The Reference Data Management (RDM) service within OneView360° was developed to centralize the storage, maintenance and access to code values. Managing and maintaining code values is important because they provide the basis for the evaluation of the data when making business decisions. Some examples of codes are:

RDM (Reference Data Management)

• Associations
• Lists
• Usages
• Relationships

IRD (Internal Reference Data)

• Status Code Values
• Transaction Type Values

Once the source data has been conformed, it can be recognized and processed throughout OneView360°. The file profile established for each data source will associate each source file with one or more standardization routines to generate expected OneView360° output.

Many times, the standardization will be more than just conforming the source data to the Canonical Model. Data mapping may also be needed. To support this function, OneView360° maintains a central repository of code values, code variations and code-mapping relationships.

The standardization for each source will be unique. The implementation can take a number of forms; however, this function is typically implemented by leveraging an off-the-shelf ETL tool.

Return to top of page