Data model

Review the data dictionary to understand the objects that are managed in Envizi Supply Chain Intelligence. The data dictionary spreadsheet contains multiple tabs:

1. Data object summary

Defines the primary data objects in the master data, orders, and emission management categories of Envizi Supply Chain Intelligence.

2. Data object details

Defines the primary identifiers for each primary object in the Envizi Supply Chain Intelligence object model.

3. Dictionary - for import

Defines the minimum set of entities that you must configure to get started. These entities are marked as either required or recommended. You configure these entities in a CSV file and upload to the platform when you first onboard with Envizi Supply Chain Intelligence.

4. Dictionary - calculated

Defines the primary set of entities that you can configure to manage your scope 3 data in Envizi Supply Chain Intelligence. This tab includes optional entities for the objects you configure when you first onboard. The tab includes objects that you configure when you work with Envizi Supply Chain Intelligence, for example, a ComplianceRecord object, which is used to manage PCF data.

5. Dictionary - extension

Defines the secondary set of entities that you can configure to manage your supply chain data in Envizi Supply Chain Intelligence. This tab includes objects that you might configure to better track the supply chain, for example, the Shipment object.

Sample files are available to populate with your data when you first onboard with Envizi Supply Chain Intelligence. You must map source data from your ERP systems to the Envizi Supply Chain Intelligence object model. As you populate the CSV files with your data, you must identify which entities in your source data map to the Envizi Supply Chain Intelligence entities. Column data might be spread across several columns and tables in your source data. The process of normalizing your source data helps to:

• Focus on the primary entities.
• Reduce redundancy.
• Avoid inconsistencies.