DIDO Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 2.2 Existing Issues ======
[[dido:public:s_cli:05_contents:02_prt:supply:02_existing:start| Existing Simplified System without DIDO ]]

==== Issues ====
[[dido:public:s_cli:05_contents:02_prt:supply:start| Return to Top ]]

Although this scenario is about strawberries which may not be considered as a critical food resource, it does represent many agricultural issues for commodities such as grain, meat or dairy. It can also be reflective of non-

  - [[dido:public:ra:xapend:xapend.a_glossary:s:supplychain|Supply chain]] records are spread across many individuals and companies covering wide geographic areas crossing numerous international borders covered by international law, trade unions and treaties.
  - [[dido:public:ra:xapend:xapend.a_glossary:p:pedigree|Pedigree]] and [[dido:public:ra:xapend:xapend.a_glossary:p:provenance|Provenance]] have different levels of granularity. For example, wanting to know the source of food may be 
    - strictly geopolitical (i.e., embargoes), 
    - it may religious (i.e., Halal and Kosher)
    - it may be medical (i.e., nut allergies)
  - The breadth and depth of the supply chain may vary according to product classifications. For example, Organic can reach back to before the product is harvested and cover the source of the seeds, the number of years the fields has had no pesticides or inorganic fertilizers added to it. Another example would be Genetically Modified Organisms (GMO) might even extend to neighboring fields because the Non-GMO products might be inadvertently pollinated by crops in neighboring fields
  - This scenario does not cover ancillary information such as insurance, bonding, customs, import/export regulations or signed receipts for products
  - This scenario does not cover the data sharing aspects of the Supply Chain. In [[dido:public:ra:xapend:xapend.a_glossary:v:valuechain|Value Chain]] there is often a single company with single key responsibility for the data (i.e., Walmart or Amazon)
  - This scenario represents most of the components within the Supply Chain as a federation, and consequently there can be problems with inconsistent:
    - Security enforcement
    - Automated signatures
    - Data Models or versions of models (e.g., version 1.0 of definition of a field versus version 2.0)
    - Supply Chain nomenclature ( what is a field, truck, crate, warehouse, etc.)
    - Domain specific nomenclature ( what is a strawberry, box of strawberries, flat of strawberries, organic, non-GMO, etc).
  - This scenario has a lot of "parts" and flows. Each part and each flow introduce risk to the success of the Supply Chain
  - Any centralized or even decentralized data stores also represent a risk to the data from hacking, breaches or to ransomware

/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~
DIDO Wiki

User Tools

Site Tools

Page Tools
