Layer - Data Format
IMDE Data Formats
IMDE goal is to support multiple versioned DataFormats (backwards and forwards compatible) for all data points relevant to manufacture, distribute, commercialize and re-cycle discrete products (e.g. food, beverages, fashion, electronics, power tools, adhesives, pet food, personal care, home care, et cetera).
The IMDE DataFormat layer is implementation agnostic so that the defined DataFormats can be implemented in DataPools, Data Networks or Digital Catalog standards (like FABDIS or BMECAT).
Data Format and Data Containers
IMDE supports the exchange of data related to the following entities via so called DataContainers. A data container contains a message or file related to one or more entities of the same type.
- Item: Use to exchange data related to physical items. Items can be transported by car, truck, plane or boat. There are multiple types of items:
- Handling unit (e.g. a physical package or container that is used to transport, store or handle goods. It could be a pallet, a box, a crate or a bundle, and it is often used to group items together to facilitate handling, storage and transport. A cases, cartons, display)
- Finished goods (e.g. TV, mobile phone, bottle of shampoo, ready to eat salad, smoothie in plastic bottle)
- Parts/Components
- Semi-finished good / Sub-assemblies (e.g. bottled beer without labels, frozen fries not yet packaged), usually produced by the brandowner/product manufacturer).
- Components (e.g packaging components like foil & cans and food components like herb-mixes or electronic components)
- Raw material (e.g. eggs, raw milk, salt, oil, tree trunk, grain, iron)
- Bill of materials: Hierarchies of physical items, for example full trade hierarchy (Pallet, case, finished good) or manufacturing BOMs (Finished Good, Components/Parts, Raw Materials)
- Trade hierarchies: In the IMDE format, trade hierarchies are modelled as part of the Bill of materials
- Party/Legal Entity: Organizations and corporations like Manufacturers, Retailers, NGOs and government bodies. Easy check: Legal entities can be sued in court
- Location: Any place on earth where activities take place, like farms, forests, production facilities, distribution centers and retail stores). Easy check: Locations can be found on Google Maps.
- Brand: Covers both product and organizational brands.
- Person: Individuals/humans like employees and consumers)
- Transactions: Production Runs, Orders, Shipments
Every entity will have a defined DataContainer within IMDE framework to exchange data related to this entity (e.g. product information for materials). Every DataContainer will have a header which includes an identifier which will enable machines to process the data in a fully automatic way.
One or more Data Topics per container
The core principles of the IMDE framework are interoperable and modular. That also applies to data formats (data messages and templates). Within the IMDE framework industry groups will work on defining DataTopics. A DataTopic will contain all datapoints covering a specific topic. Examples are: Packaging Materials, Allergens, Marks or Claims. Any data message or template can contain one or more DataTopics, depending on the needs in that part of the supply chain. For example
- A Packaging Component Supplier will include the Packaging Material Datatopic in a data message that is send to a CPG brand owner.
- A Herb Mix Supplier will include all Food recipe related DataTopics like Allergens, Ingredients and Nutrients
- A Adhesive supplier will include all Formula related DataTopics like Reach
- A CPG/FMCG in Food will data related to the "consumer product" which will Food and Packaging related DataTopics in the data message that is sent to heir business partners (retailers, wholesales, logistic service providers)
This covers the modular part, the framework becomes interoperable by allowing multiple formats per DataTopic, with defined transformations between the formats. This allows every party (both data senders and receivers) to work in the format they prefer (no longer deliver multiple formats to all different data receivers).
The IMDE framework will support multiple DataFormats per DataTopic (e.g allergens) and related data points, making sure all industries and all territories can join IMDE. IMDE will also support multiple DataFormats per Data topic. Example: allergen exchange Excel template and Allergen Exchange XSD/XML. IMDE will also support existing information & taxonomy standards, like for example:
