Exploring Basic Concepts, Compliance Objects, and Processes

Objectives

After completing this lesson, you will be able to:
  • Name basic compliance objects and their relations.
  • Memorize the basic concepts of compliance requirements with compliance patterns.
  • Recall to make compliance requirements available for assessment using compliance purposes.
  • Outline the compliance view and how it is utilized in product compliance.

Compliance Data Foundation - Basic Compliance Objects

Compliance Data Foundation (CDF) on the one hand frames the conceptual basis of Product Compliance with its solution areas. On the other hand, CDF provides essential processes for

  • Managing Compliance Requirements and Compliance Purposes, which constitute regulations or policies as the basis for compliance assessments.
  • Managing Substances Compliance - Company substances linked to legal listed substances. Listed substances represent the chemical basis for compliance assessments of raw materials and products for substance related regulatory obligations.
  • Managing Basic Compliance Data - applicable for Products and underlying Raw Materials. This data sets the stage for assessments and compliance calculations specific per solution area. An important aspect here is the calculation of composition data along the product hierarchy, finally providing a substance-related perspective, which is key for almost any compliance subject.
Illustration showing the basic compliance objects compliance requirement, compliance purpose, company substance and compliance view with brief description.

Let us look at some major objects, we deal with in product compliance:

  • Compliance view - this is the focal point of product compliance. The compliance view comprises of basic compliance data and it relates to the compliance assessments, according to the assigned compliance requirements. To integrate with the value chain, the compliance view relates to products in product master.
  • Compliance Requirements - these are the digital representation of regulations, legal obligations, or policies. Compliance requirements can be specific for legal areas, means valid for dedicated countries/regions but can also be globally valid.
  • Compliance purposes combine compliance requirements for assignment to compliance views.
  • Company substances - are essential to image the chemical level of products, which is addressed by numerous regulations. Since affected substances are frequently published as lists, assigned to regulations, the term listed substance is used for any published chemical substance. Company substances are the representation of these substances, which are required to model raw materials and products. Business data coming with raw materials or products in product master does not reach this special level of detail. Such a breakdown is an important part of the basic compliance data of compliance views - for products as well as for raw materials.
Process overview diagram for Compliance Data Foundation.

Compliance data foundation provides basic processes to:

  • Create company substances, which are essential to represent the chemical level of raw materials and products in their analytical compositions. Substances are subject to marketability assessments when it comes to ensuring compliance with substance lists, for example restriction lists of prohibited substances.
  • Create compliance views of raw materials and products and edit basic compliance data. Major parts herein are:
    • Compositions and composition calculations
    • Properties, describing for example physical-chemical properties, ecological or toxicological hazards
  • Manage and activate compliance requirements and combine them in compliance purposes for assignment to compliance views, which makes related compliance assessments available.

Compliance Requirements and Compliance Patterns

Understand the concept of compliance requirements and compliance patterns being the digital representation of regulations or policies.

With the compliance view being the focal point of the data model for product compliance, a flexible concept for assignment of regulatory aspects to the compliance view is a key element in the concepts of product compliance.

Diagram showing the assignment of regulatory aspects to the compliance view.
Diagram showing the Regulations box pointed to Compliance Requirements and Compliance Pattern boxes. Listed Substances is the another box at the bottom, indicating the common foundation.

Compliance Requirements are the objects to flexibly assign regulatory aspects to the compliance view.

Compliance Requirements are the digitized versions of regulations or legal obligations but also industry or company-specific standards can be modeled, based on the available compliance patterns.

Compliance Patterns define data structures necessary for processing and documenting compliance assessments, which finally results in a compliance status. Beside the assessment logic, specific compliance patterns also include logic to calculate the compliance status.

Numerous compliance requirements relate to the chemical level of products. Listed substances represent this part of regulations or policies.

Illustration showing the Compliance Requirement Version with the version related details.

According to the fundamental model of Compliance Requirements, it comprises of at least the initial Compliance Requirement Version (CRV) with the following version-related details, keeping each compliance requirement version self-contained:

  • Header data and regulation details, supplemented with attributes specific for each solution area, for example product marketability;
  • The Compliance Requirement Pattern (CR-pattern) of the CRV, for example:
      • Substance List Check for Product Marketability or 
      • Dangerous Goods Assessment for unpackaged and packaged products;
    • Data structures - for example, data for assessing the compliance requirement version like a list of regulated substances or product information, which must be retrieved in the assessment. These data structures may also include for example
      • phrases
      • regulatory graphic collections
      • substance lists
    • Logic - for example, how to determine affected subordinate (intermediate) products, raw materials or substances along with compliance calculation or to calculate the compliance status;
    • The app to assess the Compliance Requirement.

Compliance Purpose and Compliance Assessment

Learn how you make compliance requirements available for assessment in a compliance view.

Diagram showing the assignment of regulatory aspects to the compliance view using compliance purposes with relation to the logistics roles and regional aspects like sell in Europe, transport in North America, produce in Asia.

The compliance purpose groups compliance requirements for assignment to compliance views of products or raw materials.

Grouping criteria can be:

  • Business processes, such as Sell In, Produce In, Transport In;
  • Regional or organizational aspects.

With the grouping of compliance requirement in compliance purposes, you can also prevent missing the assignment of an applicable compliance requirement.

With the assignment of a compliance purpose to a compliance view, the compliance requirements included in the compliance purpose become available for assessment.

Diagram showing the compliance objects interacting for processing of a compliance assessment.

The assessment of a product is processed against an active compliance requirement version. The compliance pattern specifies applicable data structures and assessment or calculation logic.

For example, the compliance status of an unpackaged product can be calculated from the following:

  • The compliance statuses of the underlying raw materials as given in the material-based composition (after production);
  • The substance level of the analytical composition (globally valid or legal-area-specific).

The Compliance View - Focal Point of Product Compliance

Understand, how the compliance view bridges from the product master to regulation-based compliance data.

The compliance view is the focal point of the data model for product compliance. The compliance view supplements the commercially based product master with the legal data.

Diagram showing the product master and the compliance view with the regulatory aspects.
Diagram showing product master and the compliance view providing compliance information for processing in the value chain.

The compliance view contains the compliance information for one or multiple products in product master.

The compliance view is the single source of compliance information for assigned products in product master.

Linking a product master to a compliance view, the product logically inherits the compliance information from the compliance view.

Differentiate Compliance View by Roles from Logistics

Logistic aspects in the compliance view

The integration of business and logistic data of the product master with the compliance view brings in two aspects, which are important for managing product compliance:

  • Is the product purchased, that is typically a raw material, is it produced, is it sold?
  • Does the product master represent the product "as such", means no packaging applied or is it a packaged product?

From the product compliance point of view, in general only packaged products are ready to be sold. Most product compliance assessments relate to the unpackaged product, except dangerous goods assessments. For dangerous goods, assignment of packaged products to the compliance view is mandatory. 

These two aspects are mirrored in the compliance view by

Logistics roles, which are assigned to the compliance view. The assigned logistics roles determine:

  • Assignment of detail data, which are specific for purchased products like raw materials or produced products;
  • Availability of the compliance view in respective apps to edit compliance data or navigate to compliance assessments.

Assignment of product master, distinct by

  • Related products in product master, which represent the unpackaged product in product master - most compliance data relates to this general level;
  • Compliance view for packaged product in product master - the assignment of a product master representing a packaged product automatically creates a specific compliance view for this packaged product.
Diagram showing the product master and logistics roles assigned to the compliance view.

Depending on the logistics role, the compliance view has specific objectives and details assigned:

  • Purchased: raw materials are typically purchased. The role purchased allows supplier information to be added to the compliance view. This role may also be applicable for trade goods.
  • Produced: products, or intermediates; the role produced allows to maintain a material-based composition for the compliance view. This role is typically assigned to the compliance view of an unpackaged product; it must not be assigned to the compliance view of a packaged product.
  • Sold: The role sold typically comes with the assignment of a packaged product to the compliance view of the unpackaged product.

    The assignment of the role Sold is vital when it comes to selling and shipping the product in sales and delivery.

  • Transported: This role cannot be assigned solely, there must be one of the other logistics roles assigned as prerequisite. Upon assignment of the role sold, the role transported is assigned automatically.

    The role transported is prerequisite for dangerous goods assessments.

Diagram showing the product master and compliance view, differentiated into unpackaged product and packaged products.

For product compliance, it is essential to differentiate the product master assigned to the compliance view into:

  • Unpackaged products, in general unpackaged products are not ready to be sold. To sell a product, it requires a packaging or another kind of enclosure. Assignment of product master for unpackaged products is optional - the compliance view "by itself" represents the unpackaged product.
  • Packaged products, which are ready to be sold. Assignment of product master for packaged products is mandatory - the compliance view of a packaged product is identified by the assigned product master.

When it comes to purchased goods, raw materials, or trade goods, the situation is quite similar - you purchase packaged raw materials or trade goods, but in product compliance, the primarily focus is on unpackaged products or raw materials.

If required, there can be more detailed compliance views for assigned packaged products. This is, for example, essential for dangerous goods.

On the left, illustration showing the overlapping logistics roles produced, purchased, sold, and transported. On the right, table giving examples for assignment of logistics roles related to business aspects like products to be sold to customers, intermediate products, not to the sold, or trade goods, which are not produced by the company.

Compliance View and Basic Compliance Data

The compliance view, being the focal point for product compliance, serves two objectives:

  • Provisioning of basic compliance data for products or raw materials, this comprises of, for example:
    • Logistics roles
    • Assignment of product master
    • Assignment of compliance purposes with compliance requirements to be assessed
    • Composition data, which is essential to drill down to the chemical level
    • Properties characterizing hazard potentials
  • Navigation to compliance assessments and market assessments, consolidating individual assessment results for product marketability, business processes Sell In and Produce In.

With the differentiation by assigned logistics roles, there are specific details available for

  • Products, being produced, which in first line makes the material-based composition available, which originates from the (production) bill of materials.
  • Raw Materials, being purchased, so supplier information is of importance. This includes managing supplier compliance information, supplier specific analytical composition and supplier status for the raw material. 
Illustration showing basic compliance data, differentiated for unpackaged products and raw materials.

Compliance View and Compositions

Definitions of Compliance Views

  • Raw Material - means a Compliance View with the logistic role Purchased. The compliance view with the logistic role Purchased has an analytical composition. This can be manually created or calculated from the underlying supplier raw materials, which also come with the logistic role Purchased.
  • Unpackaged Product - means a Compliance View with the logistic roles Produced and / or Sold and Transported.

    The compliance view with the logistic role Produced has a material-based composition. This is derived from the production bill of materials, stating the components used to produce the product. The material-based composition differentiates before production and after production, which is important in case of chemical reactions or physical changes - such as solvents being removed by drying or new substances being produced by chemical reactions. The analytical composition is derived from the material-based composition after production.

  • Packaged Product - means a Compliance View with the logistic roles Sold and Transported but not Produced. This Compliance View must be related to an unpackaged product (see previous item). It is automatically created upon assignment of a packaged product in product master to the compliance view of the unpackaged product.
Diagram showing the logistics roles of a compliance view and applicable compositions.

Compliance View and Properties

Property groups with properties are the representation of the nature, of hazards, or other characteristics, important for product compliance.

The following property groups are available:

  • Physical-chemical properties, like physical state, density, or viscosity
  • Safety-related properties, like flammability and flash point
  • Toxicological information, like toxicity for various exposure paths, carcinogenicity, or mutagenicity
  • Ecological information, like aquatic and terrestrial toxicology, or environmental fate and pathway

Each property group provides a variety of properties, as for example required for publication in a safety data sheet.

Upon creation of a new compliance view or a company substance, predefined property groups are assigned. You can manually assign additional property groups.

For more details, refer to the later section on properties.

Versioning Concept for Compliance Data

Versioning of compliance data is significant to have consistent documentation and is applicable for:

  • Compositions;
  • Properties;
  • Compliance assessments.

Upon creation of a new compliance view or a new company substance, initial versions with status in process are automatically created for:

  • Applicable compositions;
  • Default properties;
  • Assessments of assigned compliance requirements - these can originate from:
    • default compliance purposes;
    • purposes assigned by the product stewardship specialist when processing a request from logistics.

From time to time, compositions, properties or compliance assessments may need to be changed. To manage such changes and to safeguard consistent compliance data, the following status sequence ensures that only one dedicated set of compliance data is in status Released and is consumed for output on documents, checks or any other process.

Flow chart showing the version sequence for compliance data.

The access to a composition‘s history is a vital element for compliance management.

Screenshot showing the version history.

The above example shows the history of the material-based composition of a product.

The option to view version history is available for:

  • Compositions, as applicable for unpackaged products or raw materials;
    • Unpackaged product
      • Material-based composition for products
      • Analytical composition, also legal area specific analytical composition
      • Confidential business information
    • Raw materials
      • Analytical composition and
      • Supplier raw material analytical composition
  • Properties
  • Compliance assessments

Compliance View - Navigation to Compliance Assessments and Market Assessment

From the compliance view, you navigate to thecompliance assessments, where you process the assessment of compliance requirements being assigned

  • Using the assigned compliance purposes;
  • By propagation, for example from the unpackaged product to the related raw materials.

From the compliance assessment, navigation leads you to the market assessment, where you consolidate the individual assessment results for a market or production country/region and business processes Sell In or Produce In.

Diagram showing the navigation options from the compliance view to compliance assessments and market assessments.
Diagram showing the compliance objects interacting for processing of a compliance assessment.

The assessment of a product is processed against an active compliance requirement version. The compliance patterns specifies applicable data structures and assessment or calculation logic.

For example if the compliance status of an unpackaged product can be calculated from

  • the compliance statuses of the underlying raw materials as given in the material-based composition (after production);
  • the substance level of the analytical composition (globally valid or validity-area-specific).
Illustration showing the compliance assessment results for the solution areas product marketability, dangerous goods, and safety data sheets.

Log in to track your progress & complete quizzes