Components¶
The components schema contains information regarding the individual components that are used to create complete packages. These maybe created from a single material or a combination of materials from the materials schema.
Table¶
Column | Status |
Format | Notes |
---|---|---|---|
identifier | mandatory |
UUID | A globally unique identifier. See identifiers section for information on how to construct this identifier |
name | optional |
String | The name of this component. |
description | optional |
String | A brief description of this component. |
externalIdentifiers | optional |
Dictionary | A dictionary of identifiers that might be used to identify the component in other systems. For example: manufacturer’s own internal identifier, bar codes or global trade item number (gtin). To provide external identifiers please follow this format. {'externalIdentifierName1': 'identifier1', 'externalIdentifierName2': 'identifier2'} |
imageURLs | optional |
List | A list of URLs that links to a picture of the component. Please see the guidelines below on how to capture the image and name the URL. |
LOWcode | optional |
String | The list of waste code for only the component, by itself. LOW code is synonymous with European Waste Catalogue Code (EWC). For example: an empty bottle would have a LOWcode of 15 01 02 . Please use Dsposal or legislation.gov to find the LOWcode. Note: The LOWcode can based on its combination with other components and the actual product contained in the completePackaging. Be sure to only include the component LOWcode. If you cannot find the code or are uncertain please enter Uncertain . |
componentConstituents | mandatory |
List | The information regarding the consituents that are combined to create this component. The entries should be from the Component Constituents Relationship List identifier. |
height | optional |
Decimal | The height of the component. Please see the guidelines below on how to properly measure and report the height. |
heightDate | optional |
Date | The date that the height was last verified/measured. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
width | optional |
Decimal | The width of the component. Please see the guidelines below on how to properly measure and report the width. |
widthDate | optional |
Date | The date that the width was last verified/measured. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
depth | optional |
Decimal | The depth of the component. Please see the guidelines below on how to properly measure and report the depth. |
depthDate | optional |
Date | The date that the depth was last verified/measured. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
volume | optional |
Decimal | The amount of space the component takes up. Note: this is related to the size of the component and is different to capacity. Using the height, width, and depth found using the measurement guidelines, calculate the component’s volume using: height x width x depth . |
volumeDate | optional |
Date | The date that the volume was last verified/measured. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
weight | mandatory |
Decimal | The weight of the component. Please see the guidelines below on how to properly measure and report the weight. |
weightTolerance | mandatory |
Decimal | The threshold of weight that a component can vary by. This can be given in grams or percentage. |
weightToleranceType | mandatory |
String | Either grams or percentage based on the value provided in weightTolerance |
weightDate | optional |
Date | The date that the weight was last verified/measured. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
shape | optional |
String | What is the shape of the component? The entry should contain the shape controlled list identifier for the component. |
function | optional |
String | What is the function of the component? The entry should contain the function controlled list identifier for the component. |
flexibility | optional |
String | Whether the component is considered flexible or rigid. The entry should be the flexibility controlled list identifier. |
branding | mandatory |
Boolean | Does the component contain your own brand (logo, trademark, or any distinctive mark)? Answer as: TRUE for yes and FALSE for no. |
componentEndOfLifeRoutes | optional |
List | The information regarding this component’s proposed end of life routes. The entries should be the component end of life routes identifiers. |
colour | optional |
String | The actual colour of the component at point of production using CMYK (Cyan-Magenta-Yellow-blacK) values. The format is specified according to cmyk(C%, M%, Y%, K%), where C, M, Y, and K are the percent values for the cyan, magenta, yellow, and black values of the color. For example: black is cmyk(0%,0%,0%,100%) . If there are multiple colours input decorative . |
opacity | optional |
String | The transparency of the colours. The entry should be the opacity controlled list identifier. |
loaned | mandatory |
Boolean | Is the component hired or loaned out as reusable packaging? Answer as: TRUE for yes and FALSE for no. |
reuseSystems | optional |
List | The system(s) that facilitates the reuse of the component e.g., Loop . The entries should be the reuse system controlled list identifier(s). |
partOfMultipack | mandatory |
Boolean | Is the component part of a multipack? Answer as: TRUE for yes and FALSE for no. |
recycledContent | optional |
Decimal | Positive decimal only, maximum value is 100.00. Value should equated to a percentage (e.g. 30 = 30%) The minimum allowable percent of how much recycled content is included in the makeup of the component. It is ‘required’ for plastic packaging where for the purposes of this standard we refer to UK’s HM Revenue & Customs definition of recycled content. “Recycled plastic is plastic that has been reprocessed from recovered material by using a chemical or manufacturing process. This is so it can be used either for its original purpose or for other purposes. This does not include organic recycling. Recovered material is pre-consumer plastic or post-consumer plastic that both: a) is no longer suitable to be used in the process from which it was generated and would otherwise have been used for energy recovery (for example, by incineration) or disposed of as waste (for example, by being sent to landfill); b) has been collected and recovered for use as a material input for a recycling or manufacturing process, instead of new primary material” |
recycledContentClaims | optional |
List | The information regarding the recycled contents. The entries should be the recycled content claims relationship list indentifiers. |
recyclability | optional |
Boolean | Is the component recyclable (as determined by a reputable source)? Answer as: TRUE for yes and FALSE for no. |
recyclabilityClaims | optional |
List | The information regarding this recyclability claims. The entries should be the recyclability claims relationship list identifiers. |
certification | optional |
Boolean | Does the component have a certificate (e.g. FSC, REACH, FSA etc.)? Answer as: TRUE for yes and FALSE for no. |
certificationClaims | optional |
List | The information regarding the certifications. The entries should be the certification claims relationship list identifiers. |
manufacturers | optional |
List | The information regarding the manufacturer(s). The entries should be the Organisations Relationship List identifiers. |
manufacturedCountry | optional |
String | The country the component was manufactured in. Use the country numeric ISO codes as described in the ISO 3166 international standard. |
updateDate | mandatory |
Date | The date that the component was provided/last updated. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
releaseDate | optional |
Date | The date that the component will be available to use. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
discontinueDate | optional |
Date | The date that the component will no longer be available to use. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard. |
Diagram¶
erDiagram
MATERIALS }o--o{ COMPONENTS : component_constituents
COMPONENTS {
identifier UUID "*"
name String
description String
externalIdentifiers Dictionary
imageURLs List
LOWcode String
componentConstituents List "*"
height Decimal
heightDate Date
width Decimal
widthDate Date
depth Decimal
depthDate Date
volume Decimal
volumeDate Date
weight Decimal "*"
weightTolerance Decimal "*"
weightToleranceType String "*"
weightDate Date
shape String
function String
flexibility String
branding Boolean "*"
componentEndOfLifeRoutes List
colour String
opacity String
loaned Boolean "*"
reuseSystems List
manufacturers List
manufacturedCountry String
recycledContent Decimal
recycledContentClaims List
recyclability Boolean
recyclabilityClaims List
partOfMultipack Boolean "*"
certification Boolean
certificationClaims List
updateDate Date "*"
releaseDate Date
discontinueDate Date
}
COMPONENTS }o..o{ CONTROLLED_LISTS : attributes
COMPONENTS }o..o{ RELATIONSHIP_LISTS : attributes
COMPONENTS }o--o{ COMPLETE_PACKAGING : complete_packaging_constituents
COMPONENTS }o..o{ MULTIPACK : multipack_constituents
MULTIPACK }o..o{ LOADS : load_constituents
COMPLETE_PACKAGING }o..o{ MULTIPACK : multipack_constituents
COMPLETE_PACKAGING }o..o{ LOADS : load_constituents
COMPONENTS }o..o{ LOADS : load_constituents
CONTROLLED_LISTS {
shape optional
function optional
flexibility optional
opacity optional
reuseSystem optional
}
RELATIONSHIP_LISTS {
componentEndOfLifeRoutes optional
recycledContentClaims optional
recyclabilityClaims optional
certificationClaims optional
organisations optional
}
Example¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
|
Data flow¶
flowchart LR
subgraph baseMaterials[Base Materials]
bm_example["example base materials"]
end
subgraph materials[Materials]
ma_cardboard["Cardboard
-
16f41cca-1a77-4e31-8b0f-2723f752317b"]
ma_glass["Glass
-
b050ab75-4bcb-4c7f-b8f5-8a1f9e5ba7d3"]
end
subgraph components["`**Components**`"]
co_cardboardBox["`**Cardboard box
-
9dad67b0-d5a2-4afb-9287-e712fd1ea3e6**`"]
co_wineBottle["`**Wine bottle
-
94108707-b914-43f3-bed5-93adbbd208c1**`"]
end
subgraph completePackages[Complete Packages]
cp_example["example complete pakages"]
end
baseMaterials --> materials
ma_cardboard --> co_cardboardBox
ma_glass --> co_wineBottle
co_cardboardBox --> completePackages
co_wineBottle --> completePackages
Guide for how to take measurements¶
Units¶
All measurements should be given using the metric system.
- Height: millimetre (mm)
- Width: millimetre (mm)
- Length: millimetre (mm)
- Volume: cubic metre (m3)
- Weight: grams (g)
- Weight Tolerance: percent (%)
Numbers should be entered with a decimal place. Use the decimal / full stop / period character as a separator. Do not exceed 3 decimal places. When rounding, use convential rounding methods: for 5 and above round up, 4 and below round down. For example: volume = 0.67952 rounded to 0.68.
Important: When converting between systems of measurement, perform the conversion first and then apply the convential rounding. This will give more accuracy and consistency.
Default Front of a component¶
Prior caputuring measurements, first determine the default front of the component, this is similar to GS1 (Note: GS1 rules are specified only for complete packaging and not components. Therefore, there are subtle differences to convert from taking a measurement for the complete packaging versus a component). In this standard, as with GS1, the default front is the face with the largest surface area, where area is equal to the width
times the height
.
Important: Determining of default front provides a consistent, repeatable process to find measurements for a given component.
width
X height
)Some components have the same surface area, thus more than one possible front. These components can be presented both vertically and horizontally. If a component has more than one possible front, the highest side is considered to be the default front.
Note: Calculating the area for a rectangular component is simple. However, for non-rectangular components (for example, components with a cylindrical or irregular form), the method to calculate the area is:
- First break the component into multiple sides. Then, for:
- a round component: do not use (=pi*r^2) to calculate the area. Instead, draw “two dimensional” rectangles around the round component’s sides and then calculate the area for each side.
- any other shape component: draw a “two dimensional” rectangle around the sides of the component, and then calculate the area for each side.
- The side with the maximum area then becomes the default front of that component.
width
X height
)Measuring the height, width, and depth of a component¶
After the default front has been determined, as with GS1, it is possible to determine the height, width, and depth of a component.
- For rectangular components:
- Height: from the base to the top
- Width: from the left to the right
- Depth: from the front to the back
Note: If there are two different measurements for the height, width, or depth, always report the maximum measurement.
-
For irregular shaped components: Similar to finding the default front of an irregularly shaped component, draw a “three dimensional” rectangle around the component.
- Height: from the base to the top
- Width: from the left to the right
- Depth: from the front to the back
-
For unformed, flexible components:
- Take the measurements as if the component was fully formed and filled.
-
For standing components:
- Height: from the flat surface to the top most point
- Width: from the left-most point to the right-most point
- Depth: from the default front to the farthest opposite surface
-
For components with leaning or irregular verticlas:
- Height: from the flat surface to the top most point (parallel to the vertex)
- Width: from the left most point to the right most point
- Depth: from the default front to the farthest opposite surface
-
For components that are cylindrical:
- For cylindrical items two dimensions will be nominally equal. Which dimensions are equal is determined by the result of determination of the default front.
Guide for component images¶
As with providing measurements, please first find the default front of the component. The image capturing process and naming convention is similar to GS1. As with measurements, we altered the gs1 standard for capturing the component.
Type of Image¶
For the purposes of this standard, we define the differences between photographic and rendered images. Note: both types are accepted but the naming convention will differ based on image type so that images have unique names and do not having naming conflicts.
- Photographic image: the result of the electronic or chemical capture of a likeness of a physical object with the use of a camera.
- Rendered image: the result of the creation of a digital likeness of a physical object with the use of a computer and software.
Image Recommendations¶
- Provide coloured images. However, do not provide colour casts. Colour should be as rich, vibrant and eye-catching as possible
- Contrast and exposure should be balanced; avoid high contrast effects and “blown-out” highlights
- Images should not be overly sharpened
- Components should be centred in Margins to cover 95% on the canvas.
- Graphic rendering of a component should be realistic.
- Do not provide layers, guides or rulers in the images.
- Background layer should be white (RGB 255,255,255).
- Remove signatures, “finger printing” or visible watermarks. No compression artifacts. No interpolation (“resizing up”).
File size¶
- 900x900 to 2400x2400 pixels
Component faces¶
After determining the default front, the possible faces, in relation to the default front, are: 1. Default Front 2. Left 3. Top 7. Back 8. Right 9. Bottom
Naming convention for URL¶
Please follow this naming convention:
- component identifier
- underscore _
- type of image (photographic
or rendered
)
- underscore _
- component face (1
: Default front, 2
: Left, 3
: Top, 7
: Back, 8
: Right, 9
: Bottom)
- orientation (C
: Centre, L
: left, R
: right, N
: No plunge angle)
Example: An image for a component that is rendered with a default front facing image and centred orientation. identifier123_rendered_1C.jpg