Decentralized ledger supply chain planning interchange

1 . A non-transitory computer readable medium that when executed by one or more first processors generates a data structure for a decentralized ledger interchange object comprising:

a single data structure within the decentralized ledger interchange object comprising a first data field, a set of second data fields, a set of third data fields and a set of fourth data fields;

the first data field containing an identifier for an item;

the set of second data fields linked to the first data field, wherein the set of second data fields comprises two or more second data fields and each second data field containing one of a set of time periods;

the set of third data fields, each third data field linked to a corresponding second data field, wherein the set of third data fields comprises two or more third data fields and each third data field containing a requested quantity of the item for a corresponding time period;

the set of fourth data fields, each fourth data field linked to the corresponding second data field, wherein the set of fourth data fields comprises two or more fourth data fields and each fourth data field containing a committed quantity of the item for the corresponding time period;

wherein the decentralized ledger interchange object is configured to be synchronized and replicated through nodes on a decentralized network;

wherein the one or more first processors further (a) fill in the first data field, the set of second data fields, and the set of third data fields to create a first decentralized ledger object, (b) generate a first block for the first decentralized ledger interchange object, (c) insert the first block onto the decentralized network, and (d) make the first block visible to the one or more second processors; and

wherein the one or more second processors (a) access the first decentralized ledger interchange object in the first block in the decentralized network, (b) generate a second decentralized ledger interchange object based on the first decentralized ledger interchange object by filling in one or more of the fourth data fields, (c) generate a second block for the second decentralized ledger object, (d) insert the second block onto the decentralized network, and (e) make the second block visible to the one or more first processors.

2 . The data structure of claim 1 , further comprising a set of fifth data fields within the single data structure, each fifth data field linked to the corresponding second data field, wherein the set of fifth data fields comprises two or more fifth data fields and each fifth data field containing a price for the corresponding time period.

3 . The data structure of claim 1 , further comprising one or more sixth data fields linked to the first data field, each sixth data field containing one or more terms and conditions, one or more specifications for the item, a shipping and handling price, a tax amount, a link to other data or information stored remotely, or a link to other decentralized ledger interchange objects.

4 . The data structure of claim 1 , wherein the first data field, the set of second data fields and the set of third data fields, and the set of fourth data fields are configured for automatic input into or export from a sales and operations planning system.

5 . The data structure of claim 1 , wherein the first data field, the set of second data fields and the set of third data fields, and the set of fourth data fields are configured for automatic input into or export from a sales plan, an inventory plan, a customer lead time plan, a new product development plan, a strategic initiative plan, or a financial plan.

6 . The data structure of claim 1 , wherein the first data field, the set of second data fields and the set of third data fields, and the set of fourth data fields are configured for automatically updating an electronic commerce application.

7 . The data structure of claim 1 , wherein the identifier for the item comprises a stock keeping unit number, a production unit number, a part number, or a model number.

8 . The data structure of claim 1 , wherein the decentralized ledger interchange object is configured for use in a decentralized ledger.

9 . The data structure of claim 8 , wherein the decentralized ledger comprises hyper ledger, blockchain or quorum.

10 . The data structure of claim 8 , wherein the decentralized ledger interchange object is detachable from the decentralized ledger.

11 . The data structure of claim 10 , wherein the detachable decentralized ledger interchange object is reconcilable back to a source of the decentralized ledger interchange object.

12 . The data structure of claim 10 , wherein the detachable decentralized ledger interchange object is synchronized with other information without a link to the source of the decentralized ledger interchange object.

13 . The data structure of claim 1 , wherein the decentralized ledger interchange object is an asynchronous data object that is self-reconciling.

14 . A computer system that uses a decentralized ledger, the computer system comprising:

a first computer system comprising one or more first processors;

one or more second computer systems, each second computer system comprising one or more second processors;

the one or more first processors (a) create a first decentralized ledger interchange object, (b) generate a first block for the first decentralized ledger interchange object, (c) insert the first block onto the decentralized ledger, and (d) make the first block visible to the one or more second computer systems;

the one or more second processors (a) access the first decentralized ledger interchange object in the first block of decentralized ledger, (b) generate a second decentralized ledger interchange object based on the first decentralized ledger interchange object, (c) generate a second block for the second decentralized ledger object, (d) insert the second block onto the decentralized ledger, and (e) make the second block visible to the first computer system; and the first and second decentralized ledger interchange objects each comprise a single data structure comprising a first data field containing an identifier for an item, a set of second data fields linked to the first data field, wherein the set of second data fields comprises two or more second data fields and each second data field containing one of a set of time periods, a set of third data fields, each third data field linked to a corresponding second data field, wherein the set of third data fields comprises two or more third data fields and each third data field containing a requested quantity of the item for a corresponding time period, and a set of fourth data fields, each fourth data field linked to the corresponding second data field, wherein the set of fourth data fields comprises two or more fourth data fields and each fourth data field containing a committed quantity of the item for the corresponding time period;

wherein the creating the first decentralized ledger interchange object further comprises the one or more first processors filling in the first data field, the set of second data fields, and the set of third data fields, and wherein the generating the second decentralized ledger interchange object further comprises the one or more second processors filling in the one or more of the fourth data fields;

wherein the decentralized ledger interchange objects are configured to be synchronized and replicated through nodes on a decentralized network.

15 . The computer system of claim 14 , wherein each single data structure further comprises a set of fifth data fields, each fifth data field linked to the corresponding second data field, wherein the set of fifth data fields comprises two or more fifth data fields and each fifth data field containing a price for the corresponding time period.

16 . The computer system of claim 14 , wherein the first and second decentralized ledger objects further comprise one or more sixth data fields linked to the first data field, each sixth data field containing one or more terms and conditions, one or more specifications for the item, a shipping and handling price, a tax amount, a link to other data or information stored remotely, or a link to other decentralized ledger interchange objects.

17 . The computer system of claim 14 , wherein: the one or more first processors generate at least one cryptographic key for the second computer system, and encrypt the first block using the cryptographic key; and the cryptographic key enables the one or more second processors to view blocks on the distributed ledger and to insert blocks onto the distributed ledger.

18 . The computer system of claim 14 , wherein: the one or more first processors input the identifier for the item, the set of time periods, and the requested quantity of the item for each time period into the first decentralized ledger interchange object; and the one or more second processors input the committed quantity of the item for each time period into the second decentralized ledger interchange object.

19 . The computer system of claim 14 , wherein the one or more first processors generate the first decentralized ledger interchange object using data from a sales and operations planning system, and update the sales and operations planning system using data from the second decentralized ledger interchange object.

20 . The computer system of claim 14 , wherein the one or more first processors reconcile and synchronize the second decentralized ledger object received from multiple second computer systems.

21 . The computer system of claim 14 , wherein the first decentralized ledger object and the second decentralized ledger object are automatically input into or exported from a sales plan, an inventory plan, a customer lead time plan, a new product development plan, a strategic initiative plan, or a financial plan.

22 . The computer system of claim 14 , wherein the first decentralized ledger object and the second decentralized ledger object a exported to a static non-network production system or supply chain system as a direct data feed to synchronize future inventory requirements from another party, source, block, node or location.

23 . The computer system of claim 14 , wherein the second decentralized ledger object is used to automatically update an electronic commerce application.

24 . The computer system of claim 14 , wherein the decentralized ledger is used as a source of data in a manufacturing process, a supply chain, a sales and operations planning time series plan, or a schedule.