Glimpact philosophy
Use Glimpact
Technical configuration
Sectorial documentation
What’s new ?
In Glimpact, the terms ‘Entity’ and ‘Analysis Case’ are frequently used. It is essential to understand what they mean and to differentiate them in order to make full use of the platform.
<aside>
</aside>
The analysis case corresponds to the most granular level of object in Glimpact and is always linked to an impact. This means that an analysis case always has an impact.
An analysis case can represent an impact in different categories, such as components, apparel, furniture, etc. *To learn more about category section click here.*
The analysis case will provide results through the score ranking, and explanatory factors pages once you input enough activity data in it. The following scheme represents that logic below:
Analysis case’s logic
It's important to understand that your activity data is contained in a specific analysis case, not the entity. This means that information is stored and processed at the level of the analysis case, and not at a more global level such as the entity.
<aside>
</aside>
An entity can be viewed as a global object. It's not directly related to an impact, but rather serves as a container for one or more other analysis cases. For example, consider Europe as an entity, which contains several countries, each representing an analysis case.
<aside> ℹ️ However, note that an entity is never empty; it always contains at least one analysis case. This means when you create a new entity, Glimpact automatically creates a new analysis case within it.
</aside>
This concept enables you to establish a global entity for a finished good, under which you can classify different impacts according to a parameter of your choice, for example the year of production or a material or manufacturing process that changes.
For instance, the below scheme illustrates how you could assess the impacts of the same finished good over several years, such as a t-shirt : there is the overall entity, a white T-shirt knitted from 100% polyester, and each analysis case representing a specific year (for example, 2022, 2023, 2024).
Entity’s logic
As for Analysis cases, Entity can belong to various categories. For instance, you could create an entity to evaluate a t-shirt, a chocolate, or even an entire organization.
Glimpact’s concept
<aside>
</aside>
For your information, when you create a new entity or a new analysis case, they are assigned a unique ID, which makes it easier to identify them later.
This feature is particularly useful for features such as export or integration through mass import or API.