Main Page

From imde.io

Revision as of 17:00, 10 November 2022 by HansdG (talk | contribs) (→‎Data Containers)

What is IMDE

Interoperable Modular Data Exchange (IMDE) is a framework that will enable machine-2-machine exchange data across the entire value network. Minimizing the cost for collecting, using and distributing data. IMDE can overcome a number of the challenges faced by organizations, solution providers and data processors like datapools in terms of improving simplification of data exchange while at the same time improving data quality (consistency, relevance, completeness, accuracy and timeliness). The biggest benefits are in exchanging data with both upstream and downstream business partners. The beneficiaries are machines!, so not humans. The whole framework is designed for fully autonomous communication between machines.

Why Interoperable and Modular?

Many of the initiatives in the past focussed on creating standards for specific use cases, or in specific industries. These standards often covered all three layers of data exchange:

  • Information Model, this covers taxonomy and data definitions, focussing on what do we mean with what data point. Examples of information models are: ETIM, GTS-Global Textile Scheme and GS1-Global Data Model)
  • Data Format. This layer covers the technical way the data message or file is constructed and the related file/message type. For example, an Excel template for file-based data exchange or a XML-XSD for message-based data exchange.
  • Data Exchange: The technical way the data is exchanged between usually two systems, but can also be between systems and humans. Examples are APIs (Rest / Soap), DataPorts, file transfer (FTP, sFTP, FTPs, AS2, Dropbox, Box) and email. Data Exchange can be peer-to-peer (DataPorts) or via Data Pools/Networks (2BA, PS in Food service, GTS, GS1-GDSN)

The challenge in this approach is that the world is big, so there a many standards, for different territories, industries and use cases. Which has resulted in the fact that data exchange is still a technical and organizational nightmare. Example: A Food manufacturer sourcing raw materials and components from multiple suppliers and selling both A-Brand and Private Label products can be dealing with dozens of different ways to exchange origin and allergen data. While the type of data is a 100% the same in all situations: Allergens information has the same data points for raw materials, semifinished goods and finished goods, and allergens data is not different for A-Brands or Private label brands. But still, from a technical standpoint, organizations need to deal with many ways to export or import this kind of data.

The solution is to move away from all-in-one standards, where all standards had the strategy to become THE standard. And where every standard covers all 3 layers: the exchange technology, the message structure and the information model. This new approach is based on the idea of allowing modular standards with independent solutions for all 3 layers.

The key principle is to model for multiple interoperable modular standards in any part of the framework. In this way, industries, organizations and solutions providers can choose the standard per part of the data exchange that suits them best.

IMDE Standard and versioning

IMDE goal is to support multiple standards and standard versioning (backwards and forwards) for all data points relevant to manufacture, distribute and commercialize discrete products (e.g. food, beverages, fashion, electronics, powertools, adhesives, pet food, personal care, home care, et cetera).

The IMDE framework does not included the Data Exchange layer so that IMDE can be implemented in any DataPool (Like 2BA), Data Network (like GS1-GDSN) or Digital Catalog (like FABDIS or BMECAT). Data Exchange which can run on the IMDE DataFormat are for example: FTP, RestAPI, SOAP-API, DataPorts. Multiple IMDE DataFormats can be define per DataTopic, so DataTopics can be implemented in Excel, XML and Json based datasets.

IMDE base principle is to use existing information standards per data topic, like for example:

  • ETIM, the international classification standard for technical products
  • FAO for Fish farming and Fishery related information standards
  • ISO (e.g. for languages, countries and units)

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.

  • Material: Use to exchange data related to physical items, in most cases items Materials can be transported by car, truck, plane or boat. There are multiple typs of materials:
    • Raw materials (e.g. eggs, porkbelly, salt, oil, tree trunk)
    • Production materials (e.g packaging components like foil & cans and food components like herb-mix or

electronic components)

    • Semi-finished goods (e.g. bottled beer without labels, frozen fries not yet packaged), usually produced by the brandowner/product manufacturer).
    • Finished goods (e.g. TV, mobile phone, bottle of shampoo, ready to eat salad, smoothie in plastic bottle)
    • Handling units (e.g. crates, cases, displays and pallets). Easy check: Materials can be transported by car, truck, plane or boat.
  • Organisation: Legal entity like companies, NGOs and government bodies. Easy check: Organisations can be sued in court
  • Brand: Covers both product and organizational brands.
  • 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.
  • Person: Individuals/humans like employees and consumers)
  • Transaction: Transactions between persons, locations or organisations like orders, invoices, shipments, payments.

Every entity will have a defined DataContainer within IMDE framework to exchange data related to this entity (e.g. product information for materials)

Data Topics

The core principles of the IMDE framework are interoperable and modular. That also applies to data messages and files. 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 can contain one or more DataTopics, depending on the needs in that part of the supply chain. For example

  • Packaging Component Supplier will include the Packaging Materials DataTopic
  • Herb Mix Supplier will include the Allergen topic
  • The Manufacturers that combines that into a consumer product will include both topics in the data message that is send to the retailer.

This covers the modular part, the frame 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).

IMDE will support multiple DataFormats per DataTopic (e.g allegens) 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.

Identifiers

Identifiers are essential to accomplish autonomouse communication between machines across the entire value network. But just like with data standards there are also multiple identifiers per entity. That is why IMDE will also support multiple identifiers per entity. Depending on the industry or territory different identifiers can be used to exchange data. Just some examples:

  • Material Identifier:
    • GTIN standard by GS1 for Trade Items
    • UMID (Unique Material Identifier, based on UUID)
  • Location Identifier:
  • Brand Identifier:
    • GBIN standard for identifying brands.
Retrieved from "http://imde.io/index.php?title=Main_Page&oldid=98"