DFC standard specifications
DFC Use Cases
DFC Use Cases
  • Introduction
  • Sources and licences
  • Contact and partners
  • Semantic specifications
    • Business ontology
    • Product ontology
    • Technical ontology
  • Technical specifications
    • Protocols specifications
    • Decentralized identifier matching reference system
    • Specifics API
    • Authentication strategy
    • Architecture representations
  • Prototype specifications
  • đźš§Solid client protocol
  • đźš§Connector
    • Model specifications
    • Semantizer specifications
    • Connector specifications
  • Use Cases
    • Enterprise Use Cases
    • Product Use Cases
      • Product Transformations
      • CSA Use Cases
    • Orders
    • Order Use Cases
      • Wholesale Order Processing
    • Glossary of terms
  • Appendixes
    • Appendix 1. General decisions
      • Federation vs Syndication
      • Stateless or stateful?
      • Service granularity
      • Directionality
      • Identification and authentication
      • Centralized or decentralized data storage
      • Metadata repository
    • Appendix 2. Technical decisions
      • Libraries to develop in semantic
      • Transition strategy fron current to ideal
      • Service standard
      • Serialization
      • Transport layer
      • Multi- or single-resource requests?
      • Right delegation between platforms and DFC
      • Data validity and inferences
    • Appendix 3. Practical Examples
      • Version 1.9
      • Version 1.8.2
      • version 1.7.4
      • version 1.7.3
      • version 1.7.1
      • version 1.7
      • version 1.6.2
      • version 1.6.1
      • version 1.6
      • version 1.5.1
      • version 1.5
      • version 1.3
      • version 1.2
  • Contributing
    • Procedures
      • Updates to the ontology
        • Patch releases procedure
        • Minor releases procedure
        • Major releases procedure
      • Taxonomy enrichment
        • Taxonomy updates
    • Platform Notifcations
  • Platform Register
    • Platform Register
Powered by GitBook
On this page
  • Transportation as a Transformation Flow
  • Product Transformation Use Cases

Was this helpful?

  1. Use Cases
  2. Product Use Cases

Product Transformations

PreviousProduct Use CasesNextCSA Use Cases

Last updated 7 months ago

Was this helpful?

Some products are “composed products”, they are made of other products, processed in some way to make a new product, like a tomato sauce for instance.

There is a theoretical transformation that plans a transformation process without any notion of where the products are located, the “recipe” that connects products with one another independently from where they could be. For instance as an artisan cookie maker I can tell that I put 100g flour, 20g chocolate, 2 eggs, etc. in my cookies. In that case I express the recipe in term of “functional products”, I need flour and chocolate.

I can be more precise and tell which type exactly of flour and chocolate I use and talk more in term of “technical products”, like wheat flour T110. And I can even tell exactly the farmer who's flour I used in my recipe, so express the recipe in terms of other “supplied products”. This is what we call the “as planned transformation flow”.

Then this recipe becomes something more like a “production workflow” that adds some notion of location. I have to move the tomato from “Awesome farm” to “TheKitchen”, the onions from “The Other Farm” to “TheKitchen”, etc. When all my components are in “TheKitchen” I can start the production process, cook, mix, bottle, etc. And get some jar of tomato sauce as output, which are located in “TheKitchen”.

This is still only a plan, a production map, I still don’t have the products, I’m just organising and planning the operations.

Then when physical products are concerned this flow becomes a “realized transformation flow”.

Transportation as a Transformation Flow

We realized when iterating that transforming the nature of a located product was exactly the same flow as transforming the place where this product is supposed to be located. As the Localized Product is a combination of an Product ID and an Place ID, one flow was transforming the Product ID, the other the Place ID. So we are treating transportation as a specific transformation flow. Input will be for instance 100 x potatoes 1kg located in “Awesome Farm” and output will be 100 x potatoes 1kg located in “The Great Town Shop”.

Product Transformation Use Cases

  1. As a Producer I need to be able to create Products by combining other Products so that I can create further Products

  2. As a Producer I need to be able to track the source of composed Products so that I can fulfill traceability requirements

  3. As a Producer I need to be able to plan my Product transformations so that I can ensure I have all the required source products available

  4. As a Producer I need to be able to request Products from suppliers in advance so that I can ensure my requirements are met.

  5. As a Supplier I need to be able to propose, in advance, a Product to meet a requested need so that I can match buyer requirements to my planned output.

  6. As a Supplier I need to be able to link my proposed Product to a Physical Product to ensure traceability of orders to deliveries/product batches.

Transformation Flow Portion of the Ontology