Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
TECHNIQUES FOR MANAGING DATA THROUGHOUT VARYING DATA SYSTEMS
Document Type and Number:
WIPO Patent Application WO/2022/006355
Kind Code:
A1
Abstract:
Systems, devices and methods for managing data throughout a plurality of business, government and other widely-varied data systems are provided. According to some aspects of the invention, a data integration device comprised within or comprising a specialized hardware- and software-based control system performs new techniques for creating and integrating asset- and resource-related data in a complex economic environment. In some embodiments, data related to a product or other asset is managed throughout a product or asset lifecycle across varied data systems, and the data integration device negotiates the creation of new forms of electronic data interchange ("EDI") between an Enterprise Resource Planning ("ERP") system and other data systems. Techniques provided include a new form of applicator and tracking device applying a structure over and into product parts. Over the product lifecycle, use and maintenance physically alters the structure in ways associated with product status, which is then recorded.

Inventors:
MITCH ELEANOR (US)
Application Number:
PCT/US2021/040016
Publication Date:
January 06, 2022
Filing Date:
June 30, 2021
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
MITCH ELEANOR (US)
International Classes:
G06F16/27; G06F16/23; G06Q20/40; G06Q40/04; H04L9/32
Foreign References:
US20200175600A12020-06-04
US20180302417A12018-10-18
US20170075877A12017-03-16
US20180002055A12018-01-04
US20160154939A12016-06-02
US20140263674A12014-09-18
Attorney, Agent or Firm:
BECKMAN, Christopher (US)
Download PDF:
Claims:
CLAIMS

We claim:

1. A system for managing product and/or service-related data on differing data systems [101], comprising: an ERP system [117], owned and managed by a superuser and accessible by other user(s); and an electronic data interchange device [103], comprising: a control system [400] comprising computer hardware and software and a network connection communicatively connecting said control system with one or more blockchain(s) [105, 409], wherein said control system is configured to: authorize and facilitate a plurality of data systems, other than said ERP system or said electronic data interchange device, to receive and produce data related to a product throughout a product lifecycle; and create and accept parameters, requests and functions related to said electronic data exchanged between said electronic data interchange device and each data system of said plurality of data systems.

2. The system for managing product and/or service-related data of Claim 1, wherein said parameters, requests and functions are created by an algorithm applied by the electronic data interchange device.

3. The system for managing product and/or service-related data of Claim 1, wherein said parameters, requests and functions are created by an algorithm applied by an additional control system, owned by another user.

4. The system for managing product and/or service-related data of Claim 3, wherein the algorithm applied by an additional control system implements a matching of search terms and parameters related to said product lifecycle, and related to a request for EDI by said electronic data interchange device, with terms stored in data within the additional control system.

5. The system for managing product and/or service-related data of Claim 4, wherein the search terms and parameters are so searched by Boolean logic.

6. The system for managing product and/or service-related data of Claim 4, wherein the search terms and parameters are so searched with the aid of fuzzy logic.

7. The system for managing product and/or service-related data of Claim 4, wherein the search terms and parameters are so searched within metadata stored on said additional control system.

8. The system for managing product and/or service-related data of Claim 1, wherein said additional control system generates additional, suggested search terms and/or parameters, in reaction to said search terms and parameters.

9. The system for managing product and/or service-related data of Claim 8, wherein said electronic data interchange device accepts or rejects said additional, suggested search terms and/or parameters, and implements said additional, suggested search terms and/or parameters in subsequent data interchange with the additional control system and/or other control systems.

10. The system for managing product and/or service-related data of Claim 9, wherein the additional control system and/or other control systems with which said subsequent interchange takes place is said additional control system.

11. The system for managing product and/or service-related data of Claim 9, wherein the additional control system and/or other control systems with which said subsequent interchange takes place are said other control systems.

12. The system for managing product and/or service-related data of Claim 4, wherein the search terms and parameters are so searched by pattern matching and/or the application of a confidence interval.

13. The system for managing product and/or service-related data of Claim 1, wherein said control system comprises, or is communicatively connected with, an applicator device.

14. The system for managing product and/or service-related data of Claim 13, wherein the applicator device applies a surface-adhering, encoded structure over parts, sub-parts or other assets and components.

15. The system for managing product and/or service-related data of Claim 13, wherein the applicator device and/or the control system comprises a tracking device and/or a camera or other pattern sensor, configured to read changes in patterns in the surface-adhering, encoded structure.

16. The system for managing product and/or service-related data of Claim 15, wherein the applicator device and/or the control system associates said changes in patterns in the surface-adhering, encoded structure to changes in status of said product.

17. The system for managing product and/or service-related data of Claim 13, wherein the applicator device embeds an encoded structure into parts, subparts or other assets and components.

18. A method for managing product and/or service-related data on differing data systems [101], comprising the following steps: providing a system comprising: an ERP system [117], owned and managed by a superuser and accessible by other user(s); and an electronic data interchange device [103], comprising: a control system [400] comprising computer hardware and software and a network connection communicatively connecting said control system with one or more blockchain(s) [105, 409], wherein said control system is configured to: authorize and facilitate a plurality of data systems, other than said ERP system or said electronic data interchange device, to receive and produce data related to a product throughout a product lifecycle; and create and accept parameters, requests and functions related to said electronic data exchanged between said electronic data interchange device and each data system of said plurality of data systems.

Description:
TECHNIQUES FOR MANAGING DATA THROUGHOUT VARYING DATA SYSTEMS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is being filed on June 30, 2021, as a PCT International patent application, and claims priority to U.S. Provisional Application No. 63/046,608, filed June 30, 2020, titled “Techniques for Managing Data Throughout Varying Data Systems,” which is herein incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present invention relates to the fields of asset and resource management systems, and, more particularly, to data management devices, systems and methods for managing data throughout varied business systems, using decentralized computer networks, such as blockchains.

BACKGROUND

[0003] Since the dawn of civilization, different peoples have sought to share information and coordinate work efforts, in order to increase their productivity and achieve common goals. The very concept of civilization is closely tied to organized human collaboration, and its effects have been quite striking throughout history.

[0004] Beginning at least with ancient Sumer, systems of written collaboration developed, initially in the context of agricultural trade. Sumerians would drop symbolic tokens into clay envelopes, and then press the clay against them, creating a visible impression of the symbols on the outside. The earliest form of writing then developed.

[0005] In modern times, extremely sophisticated computer systems have been integrated into the fabric of society. Computer software has been developed, at least in part, to aid in collaborative writing and recordkeeping, among many other pursuits. [0006] In complex industrial manufacturing and maintenance processes such as those, for example, in the aerospace industry, the availability and provision of resources is integrated with the field of enterprise resource management (“ERM”). Modern ERM requires the development of integrated approaches to managing core business processes and the resources needed to support them, including the provision of inventory, parts, maintenance services, other services, and completed products. A plethora of ERM systems have emerged, and continue to emerge, as humanity’s varied, specialized industries manage their different resources, ranging from simple consumer products to complex industrial services and machinery.

[0007] There is a need for more effective resource management systems, and, more specifically, enterprise resource management systems, tailored to the dynamic needs of consumers and industries, incorporating ever-changing information and regulations, and yielding richer, more complete data regarding a wide variety of management factors.

[0008] It should be noted that some of the disclosures set forth as background, such as, but not limited to, the above language under the heading “Background,” do not relate exclusively to prior art and the state of the art in the field(s) of the invention, and should not be construed as an admission with respect thereto.

SUMMARY

[0009] Systems, devices and methods for managing data throughout a plurality of business, government and other widely-varied data systems are provided. According to some aspects of the invention, a data integration device comprised within or comprising a specialized hardware- and software-based control system performs new techniques for creating and integrating asset- and resource-related data in a complex economic environment. In some embodiments, such a device is comprised in an administrative system, such as an Enterprise Resource Planning system (“ERP”), and is, or includes, an electronic data interchange device. In some embodiments, data related to a product or other asset is managed throughout a product or asset lifecycle across varied data systems, and the data integration device negotiates the creation of new standardized forms of electronic data interchange (“EDI”) between the ERP and other data systems.

[0010] In some embodiments, new hardware and devices related to managing and tracking products and other resources are provided. For example, in some embodiments, a new form of applicator and tracking device that applies a new form of surface-adhering, scannable, encoded structure on or about products, and/or parts thereof, is provided. In some embodiments, such a scannable, encoded structure includes a unique, signature pattern associated only with the product and/or parts thereof. In some embodiments, such a structure is a thin instantly-formed film (e.g., in the form of interlaced thread(s), or “threading;” e.g., a net or net-like structure; e.g. a flat, transparent film less than 1 millimeter thick) forming a complex, unique, “signature pattern.” In some such embodiments, such a pattern is a visual pattern. In some embodiments, such a pattern is a pattern of resistance or other electric or magnetic profile. In some embodiments, such a film is a conductive threading. In some embodiments, such a film is a capacitive threading. In some such embodiments, such a pattern is an impedance of the conductive and/or capacitive film. In some embodiments, the applicator device also implants an electronic and/or wireless reading conduit device into such conductive and/or capacitive film, allowing the “reading” of the unique signature pattern. In some embodiments, the reading conduit device includes electrical contacts, conductively connected to conductor(s) comprised within the conductive and/or capacitive film. In some embodiments, such a film is a non-volatile medium. In some embodiments, the film is adhered to a surface of product packaging, or integrated with product packaging. In some embodiments, the film is non-toxic, biodegradable and/or edible.

[0011] In other embodiments, deliberate, unique machine-readable (but not human- readable) patterns are deliberately inflicted into product components during manufacturing, creating a unique identifier of that product, and other product-related information in conjunction with the control system (i.e., a signature pattern). In some embodiments, a new, unique data format is created during such manufacturing, in which particular sub-patterns are encoded by the control system to signify particular product- related information, which are then recorded by the control system. In some embodiments, projected erosion, wear-and-tear, and other alterations of those patterns are also a part of that new data format, and the control system records data related to such alterations upon detecting such alterations of those patterns in subsequent scanning (e.g., visual) of the part.

[0012] In some embodiments, such a creation of a unique signature pattern is made to one or more surfaces of a product, and/or its constituent parts, as the product is manufactured, sold, distributed, used, maintained, remanufactured, resold, retired, or subject to other steps in the product lifecycle.

[0013] In various embodiments, new systems, devices and methods for enhancing information transparency for persons and entities within a supply chain are provided. For example, in some embodiments, a device comprised within or comprising a specialized hardware- and software-based control system, such as any of the device(s) discussed in this application, produces and presents information related to a product, service or other asset within the supply chain to a user. For example, in some embodiments, a specialized graphical user interface (“GUI”) is presented on display hardware conveying such information to distributors, wholesalers, refurbishers, servicers and/or other persons or entities within the supply chain.

[0014] In some embodiments, such information, and transactions between such persons or entities, and other actions relevant to a product, service or other asset in the supply chain are recorded on a blockchain as one or more smart contract(s), executed and recorded through a transactional tool(s) implemented by the control system. In some such embodiments, such a transactional tool(s) includes a promissory note, between at least two contracting parties, and recorded by the control system. In some such embodiments, such a transactional tool includes a technique for issuing, signing, transmitting and recording (a.k.a. “issuing”) a cryptographic or other token, such as a “promissory token,” as will be set forth in greater detail below, executed with the aid of a decentralized network, included in, or including the control system. In some embodiments, tokens in various embodiments set forth in this application may record, or be, a virtual asset, which may have a value determined by the control system. In some embodiments, such tokens comprise a signed transaction, and related data structure, recorded on a blockchain. In some such embodiments, such a decentralized network includes at least one blockchain. In some embodiments, such a decentralized network includes a plurality of blockchains. In some embodiments, such a token includes restrictions on such tokens, as managed by the control system. For example, in some embodiments, such a restriction prevents transactions related to a particular classification(s), while permitting others.

[0015] Such a transactional tool may record data related to a wide variety of transactions related to a product, service or other asset within a supply chain. For example, in some such embodiments, the transactional tool creates and records data related to the delivery of a product, service or other asset to a recipient. In some embodiments, the transactional tool creates a record of data related to the receipt of the product, service or other asset by a recipient. In some embodiments, the transactional tool creates a record of data related to the use of a product, service or other asset by a recipient. In some embodiments, a transactional tool records other data, related to a transaction between persons or entities within the supply chain. For example, in some embodiments, such a transactional tool records data regarding the identity of a buyer and/or seller who are parties to such a transaction. As another example, in some embodiments, such a transactional tool records data regarding alterations to any of the unique patterns associated with products discussed above. In some such embodiments, particular types of alterations yield data regarding the condition of a product and/or service, or part thereof, which is recorded by the control system. Any such records may be made cryptographically and/or onto a blockchain, in some embodiments (e.g., with a smart contract, and/or cryptographic token, as discussed further herein).

[0016] In some embodiments, the smart contract(s) discussed above include a governance feature, and the control system implements an algorithm incorporating a plurality of variables related to the supply and demand for particular preferred types of transactions.

[0017] As discussed elsewhere in this application, in some embodiments, cryptographic tokens, promissory tokens or other tokens are issued by a control system including computer hardware and software connected to a network, such as the Internet and/or one or more blockchains, and carrying out any other aspects of the invention set forth in this application. In some embodiments, such promissory tokens are issued by one or more user(s) of the control system with privileges to issue such promissory tokens, such as a superuser. For example, in some embodiments, such users include manufacturers of a product or service providers (e.g., authorized manufacturers and/or service providers). In some such embodiments, one or more of such blockchain(s) are used to record product- or service-related transactions. In some such instances, such promissory tokens may be visible, or at least partially visible, to any party participating in a supply chain. For example, in some embodiments, such a party may be an authorized user of the blockchain(s) or member of a class of users of the blockchain(s).

[0018] In some embodiments, such a control system creates a digital signature based on data-bearing tag(s), which may be chemical, electromagnetic, visual-based or other tag(s) placed on, in or throughout an asset for use in a manufacturing, maintenance, conveyance, shipping, delivery, distribution, or another industrial process (“data-bearing tag”). A data-bearing tag may be a label, identifier, tag, particle, and/or any other device that contains information about an asset, in various embodiments. In some embodiments, a data-bearing tag is, or comprises or is comprised within, any of the unique pattern(s) and/or film(s), and/or reading conduit devices discussed in this Application. In some embodiments, at least part of such a tag, and/or the data held within them, are alterable by a user of the supply chain. In some embodiments, such a tag or data are so altered by virtue of actions of such a user related to a product, or use of a product fastened to that tag. For example, in some embodiments, any of the films bearing any of the types of unique patterns discussed in this application may be broken or worn based on corresponding wear-and-tear or replacement of product components covered by those patterns, and the control system interprets changes to those patterns, and the reading thereof, as corresponding with data signifying such wear-and-tear or replacement. In some embodiments, such a film may be altered by other changes to the product components, or changes in their relationship to one another or to external factors. For example, in some embodiments, movement of moving parts may cause changes in such tag which are pre-associated with such movements. In some such embodiments, such associated changes may then be presumed and recorded for the product, upon scanning and detecting such changes in the tag. For example, in some such embodiments a separation or other change in the relative proximity of sub-parts of the product (e.g., widening a seam between them), may break, stretch or otherwise alter some conductive connections of the film, which is a readable change in that tag. As another example, wear and tear associated with servicing and scanning the product and/or tag may be associated with a servicing event related to the product.

[0019] In some embodiments, the control system then combines any of the above changes and associated information about an asset with the digital signature into a new, combined data set, and inserts all or at least part of that set into a secure network and/or a blockchain, as a series of recorded values. Preferably, an insertion process into a blockchain is used, which creates a secure, encrypted identifier, separate from the digital signature, which is associated with the asset. This process creates a new identifier, for use on the blockchain, unique to the particular asset, and allows a user to trace any asset recorded by the control system, view important data related to it, and authenticate it, in real time, and to better manage the asset throughout its lifecycle within the control system. The enhanced security of the blockchain-implemented embodiment protects the asset from hacking and other security threats, making the control system substantially inviolable.

[0020] In some embodiments, the invention is implemented as a comprehensive, all- inclusive control system, managing an entire product- and/or service lifecycle and transactional process (including the issuance of tokens, promissory tokens and presenting transactional tools).

[0021] In some embodiments, the data management and product, service or other asset management techniques set forth in this application are carried out with the aid of an ERP or other administrative system, and may include both middleware, and hardware running it, as well as software directly interfacing with a user, distributor, manufacturer and/or servicing hardware and control systems. However, aspects of the invention are not limited to ERP contexts. [0022] In some embodiments, the control system includes specialized hardware and software to allow operation in a wide variety of network environments. For example, in some embodiments, the control system carries out any or all of the steps and other techniques set forth in this application despite intermittent network connections (e.g., temporary loss of connection to a centralized network and/or blockchain(s)). As another example, in some embodiments, the control system carries out any or all of the steps and other techniques set forth in this application in an efficient manner, during inconsistent and/or altered type(s) of network connections (e.g., any of satellite networks, local area networks, cellular networks, wired connections, etc., failing and being reestablished over time).

[0023] Further aspects of the invention will be set forth in greater detail, below, with reference to the particular figures.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The features and advantages of the example embodiments of the invention presented herein will become more apparent from the detailed description set forth below when taken in conjunction with the following drawings.

[0025] Fig. 1 is an example diagram of some elements of an electronic data interchange device, comprised in or comprising a control system (such as the example control system set forth below, in reference to Fig. 4) operating within an example commercial environment, and managing product- and/or service-related data throughout a plurality of data systems, in accordance with aspects of the present invention.

[0026] Fig. 2 is a diagram of aspects of example data transmissions between the example electronic data interchange device, discussed above, and product- and/or servicereceiving user entities, and illustrating aspects of an example electronic data interchange protocol, in accordance with some example embodiments of the invention. [0027] Fig. 3 is a diagram of additional aspects of additional example data transmissions between the example electronic data interchange device and any of the product- and/or service-receiving user entities set forth above, illustrating additional aspects of an example electronic data interchange protocol, in accordance with some example embodiments of the invention.

[0028] Fig. 4 is a schematic block diagram of some elements of a control system in accordance with some example embodiments of the invention.

[0029] Fig. 5 depicts aspects of a new type of asset management system for tracking and managing products, and parts and sub-parts thereof, over a product lifecycle in complex manufacturing, maintenance and/or usage environments, such as the example manufacturing environment provided.

DETAILED DESCRIPTION

[0030] The example embodiments of the invention presented herein are directed to methods, systems, devices and computer program products for managing a plurality of products, services, resources and other tangible or intangible assets, or aspects and subcomponents related thereto, and related information, in a complex economic environment, which are now described herein. This description is not intended to limit the application of the example embodiments presented herein. In fact, after reading the following description, it will be apparent to one skilled in the relevant art(s) how to implement the following example embodiments in alternative embodiments (e.g., involving a control system including specialized computer hardware and software implementing GUI tools for managing such products, services, resources and other assets, or aspects and subcomponents and related information). [0031] Fig. 1 is an example diagram of some elements of an electronic data interchange device 103, comprising computer hardware and software, and comprised in, and/or, in some embodiments, comprising, a control system (such as the example control system set forth below, in reference to Fig. 4) operating within an example commercial environment 101, and managing product and/or service-related data throughout a plurality of different data systems, in accordance with aspects of the present invention.

[0032] As discussed above, in some embodiments, product(s), service(s) and related data are managed by a control system, including computer hardware and software, connected to a network, such as the Internet and/or one or more blockchain(s) 105, and carrying out any other aspects of the invention set forth in this application. For example, in some embodiments, data related to events during a product and/or service lifecycle are recorded via transactions executed by the control system and/or user(s), and recorded on a blockchain(s). In some embodiments, other assets, in addition to, or instead of, or in addition to, such products or services may be so managed by the control system (e.g., a virtual asset).

[0033] In some embodiments, such a control system may be at least partially present on the premises or other use environment of any entity or individual (including human, computer-managed or other users) using the control, system (a “user”), such as any of user entities 107. As an overview, some such possible users, according to some embodiments, may include any of the following: A) product and/or service manufacturer(s) or provider(s), such as the pictured example product manufacturing entity(ies) 109; B) product and/or service distributor s), such as the pictured example product distributor entity(ies) 111; C) product and/or service wholesalers, such as the pictured example wholesale entity(ies) 113; and product and/or service retailers, such as example retailer entity(ies) 115.

[0034] In some embodiments, at least one of those entities, and preferably the initial manufacturer or another more significant stakeholder in or responsible party with respect to the product and/or service managed, also is an authorized administrator or other “superuser” of the electronic data interchange device 103, and, as such, has greater, special privileges granted by software and hardware of the control system of the data interchange device. For example, in some such embodiments, such a superuser may be provided with special privileges to create and record data related to the managed products and/or services. For example, in some such embodiments, the control system of the data interchange device is configured to allow a superuser to create, apply and associate product management tags, films, patterns and/or data related thereto, to a product, service and/or other asset, in accordance with those aspects set forth in this application. In some embodiments, such a manufacturer or other stakeholder entity is an owner of the data interchange device, or the software run on it, and also owns and/or manages an Enterprise Resource Planning system (“ERP”), which may include such a control system, such as example ERP 117, controlling at least initially available data created with respect to the product and/or service being managed by the data interchange device. In some embodiments, ERP 117 may include the control system, or be included within the control system, and thereby be managed and controlled by it. In some embodiments, ERP 117 is communicatively connected with the control system, either through a wired or wireless communications connection (a.k.a. “connected”). Such connections may be periodic and intermittent, in some embodiments. However, in other embodiments, such connections may be constant, or substantially constant. According to some embodiments, any control systems set forth in this application may be configured to continue carrying out any methodological steps set forth in this application, despite inconsistent or altered communications connections (e.g., network connections including a blockchain). Examples of such embodiments are provided in greater detail elsewhere in this application.

[0035] In accordance with some example method embodiments of the present invention, the superuser may first create a product or service to be managed by the ERP 117 and electronic data interchange device 103. In some embodiments, the control system may also create a unique, secure identifier for the product and/or service, and record it in a transaction on blockchain(s) 105, in accordance with aspects of the invention set forth in the present application. The control system may also create a unique, secure physical tag(s), film(s), sheet(s), mesh(es) and/or pattern(s) and data related to the product or service, its components, and other attributes, in accordance with aspects of the invention set forth in the present application. Some examples of such unique, secure physical tag(s), film(s), sheet(s), mesh(es) and/or pattern(s) and data within them, according to some embodiments, are discussed herein and elsewhere in this application. In some embodiments the control system may then place or create the unique, secure tag(s), film(s), sheet(s), mesh(es), and/or pattern(s) and/or data within them on, within, on or about the product and/or service or related items (e.g., product, service or sales-related literature or other items), before sending the product and/or service to other users 107 of the electronic data interchange device 103. In some embodiments, the control system may also record data of or related to such tag(s), film(s), sheet(s), mesh(es) and/or pattem(s) and data within them on blockchain(s) 105.

[0036] In some embodiments, any of users 107, instead of or in addition to the superuser (e.g., manufacturer or other stakeholder) owner of ERP 117, may be such a superuser. In other words, the instance of an ERP-owning manufacturer as such a superuser is preferred, but not an exclusive embodiment of the invention. For example, in some embodiments, example retailer entity(ies) 115 may, instead of or in addition to such a manufacturer/owner, be an owner of ERP 117 or the software run on it, and/or may be such a superuser.

[0037] As used in this application, “entities” means any business, government or other recognized party with the ability to act as a party to a business transaction, and/or to act upon its legal or other rights.

[0038] In some embodiments, other entities and users, other than the superuser (e.g., the manufacturer or other stakeholder owner of ERP 117), may engage in transactions with the superuser, recorded on the blockchain(s) 107. In some embodiments, various specialized tokens, dedicated to evidencing such particular transactions, the parties involved, the nature of the product(s) and/or services, and information related to the product(s) and/or service(s) may be recorded on blockchain(s) through the issuance of such tokens to an initiating party, along with confirmations of such tokens (e.g., via subsequently -issued and recorded tokens), recorded by an authorized counter-party. [0039] Fig. 2 is a diagram of aspects of additional example data transmissions 200 that may occur between the example electronic data interchange device 103 and any of the product- and/or service-receiving user entities 107 set forth above (not pictured in the present figure), and illustrating additional aspects of an example electronic data interchange protocol, in accordance with some example embodiments of the invention.

In some embodiments, data transmissions 201 may be initiated through data interchange device 103 by a user with administrative privileges (e.g., a superuser, as discussed above). For example, and as discussed above, such a superuser may be a manufacturer entity, or other party responsible for a product, service or other asset. In some such embodiments, such a superuser may be responsible for the creation, initial distribution and/or overall management of a product over its lifecycle (i.e., a “product lifecycle”). As also discussed above, in some embodiments, such a superuser may use example electronic data interchange device 103 to manage and control information related to the management and control of a product, service or other asset across a wide variety of other data systems. For example, in some embodiments, such other data systems are more directly maintained and used by a party owning those systems, such as any of user entities 107. In some embodiments, electronic data interchange device 103 may manage and control information related to the management of a product, service or other asset according to the following steps.

[0040] First in some embodiments, a superuser of electronic data interchange device 103 may initiate example data transmissions 200 by sending an initial data communication 201 to one of example user entities 107. In some embodiments, initial data communication 201 includes an initial aspect signaling a request for data related to the product (i.e., an individual produced item, good or unit) in response from a data system controlled by the example user entity. In some embodiments, initial data communication 201 includes initial product-related data, created and recorded by the superuser. For example, in some embodiments, such initial product-related data is created and recorded upon manufacturing and/or creating and attaching a unique identifier and/or signature pattern on, about or within the product, as set forth in this application. In some embodiments, the electronic data interchange device 103 requests that the user entity confirm receipt of those data (e.g., through a smart contract, and/or by issuing a token, as recorded on blockchain 105).

[0041] In addition, in some embodiments, such an initial communication also includes a request or parameter for the data requested from the user entity. For example, in some embodiments, such a parameter indicates to the user entity the type of data, potential file names, file types and/or metadata included with that type of data, requested from the user entity. For example, in some such parameter(s) so communicated within initial data communication 201, electronic data interchange device 103 may indicate a set or type of author(s), creator(s), subject(s), and/or other party(ies) related to the data requested and the product and that the data relate to the product (e.g., by indicating the product’s unique, secure identified s), signature pattem(s), and/or description). In some embodiments, such parameters may be more specific, in addition to or instead of more general parameters. For example, in some embodiments, the electronic data interchange device 103 may indicate to the user entity 107 that the request relates to data reflecting subsequent distribution, shipment, modifications and/or maintenance of the product. In some embodiments, such parameters may be even more specific, requesting information relating to potential counterfeiting, substitution of non-OEM parts, or potentially improper maintenance techniques. For example, as discussed in greater detail below, in some embodiments, the electronic data interchange device 103 may request data concerning changes in unique, identifying patterns of tag(s), sheet(s), mesh(es) and/or film(s) overlaid onto products and/or components thereof, in accordance with further aspects set forth in this application, and may record data indicated by, and associated with, such changes in patterns, in some embodiments. In some embodiments, such parameters may include a timeframe (i.e., data related to events concerning a product carried out in a particular timeframe(s)). In some embodiments, such parameters may include standard subsets or segments of an existing electronic data interchange transmission format. For example, in some embodiments, such parameters may include a request for such EDI subsets related to purchase orders for the product. As another example, in some embodiments, such parameters may include a request for an acknowledgement of, or other data related to, a product-related transaction. As another example, in some embodiments, such parameters may include a request for an invoice related to the product. As yet another example, in some embodiments, such parameters may include a shipment notice. In some embodiments, such parameters may include any EDI subset specified in a common EDI system, such as UN EDIFACT or ANSI ASC X12.

[0042] In some embodiments, electronic data interchange device 103 resides, or runs software that resides, at least in part on the local data system(s) of the user entity 107. In some embodiments, such software specifies and provides a link to functions, requests, and parameters as set forth herein configured to issue effective commands to the local data system(s) of that user entity 107, based on the operating system and all product- related software currently running, or scheduled to run, on that data system(s) of the user entity. In this sense, the electronic data interchange device 103 may act as a “translator” of EDI, creating, storing and requesting data related to the product in formats available from the data systems of the user entity 107, which is then supplied in the available format from the local data system(s). In some such embodiments, specialized data parameters, requests and functions (e.g., commands) related to the storage and communication of product-related data, may be included within the initial data communication 201. In some embodiments, any or all of such functions (and/or requests and parameters), and responses thereto, may be recorded and confirmed as transactions on a blockchain(s) (e.g., as smart contracts), as discussed in this application.

[0043] In some embodiments, parameters, requests and/or functions are pre-programmed into software included in the control system of the electronic data interchange device. In other embodiments, the parameters, requests and/or functions are created by an algorithm applied by the control system (or, in some embodiments, by an additional control system, owned by another user, other than the control system of the electronic data interchange device). In some embodiments, such an algorithm implements a search for and matching of 1) search terms and parameters, requests and/or functions related to the product and/or product lifecycle, and related to a request for EDI by the electronic data interchange device, with 2) terms stored in data, data types, metadata and/or data locations within the additional control system. In some embodiments, such an additional control system generates additional, suggested search terms and/or parameters, in reaction to the search terms, parameters, requests and/or functions in part 1, above, related to a request for EDI by the electronic data interchange device. In some embodiments, any of the search terms, parameters, requests and/or functions are so searched and matched with an algorithm including Boolean logic. In some embodiments, any of the search terms, parameters, requests and/or functions are searched and matched with an algorithm including fuzzy logic. In some embodiments, any of the search terms, parameters, requests and/or functions are searched and matched with an algorithm including pattern matching and/or the application of a confidence interval. In some embodiments, any of the search terms, parameters, requests and/or functions may be searched and matched with an algorithm including any other suitable technique, or combination of techniques, known in the art.

[0044] In reaction to the results of applying any such algorithm, set forth above, and determining suggested search terms, parameters, requests and/or functions, which may be communicated to the control system of the electronic data interchange device, in some embodiments, the electronic data interchange device accepts or rejects or accepts any of the suggested search terms, parameters, and implements additional, suggested search terms and/or parameters in subsequent data interchange (e.g., based on the application of additional algorithms) with the additional control system.

[0045] Although initial data communication 201 may comprise a set of discrete functions, requests and parameters, in some embodiments, it is preferred that initial data communication 201 be sent as a single, substantially contemporaneous communication, which is received in one instance by example user entity 107.

[0046] Following transmission of the initial data communication 201 from the electronic data interchange device 103 to the user entity 107, the data system(s) of the user entity may next communicate a series of discrete data packets - such as example data packet 209, example data packet 211, example data packet 213 and example data packet 215 - in response, back to the electronic data interchange device 103. Unlike initial data communication 201, preferably, example data packet 209, example data packet 211, example data packet 213 and example data packet 215 are sent in response, individually, when the local data system(s) of the user entity has prepared the component of that particular data packet. Although the example of four data packets is provided, fewer or more such data packets, including a single such data packet, or an unlimited number of data packets, may be transmitted, instead of the example four (4) data packets. Some example components of such data packets, and subsequent dynamic communications in response there to, are provided in the following figure.

[0047] Fig. 3 is a diagram of additional aspects of additional example data transmissions 301 between the example electronic data interchange device 103 and any of the product- and/or service-receiving user entities 107 set forth above, also illustrating aspects of an example electronic data interchange protocol, in accordance with some example embodiments of the invention. Although the parties are not pictured in the present figure, for simplicity, it should be understood that, as in Fig. 2, above, communications shown as transmitted in the downward direction (vertically, or the negative y axis, in the two- dimensional layout of the figure) represent communications from the electronic data interchange device 103 to an example user entity 107, and vice versa. Thus, and as discussed above, in some embodiments, data systems of user entity 107 may communicate a number of data packets, each in response to an individual component parameter, request and/or function sent in the initial data communication 201 from the electronic data interchange device 103. In some embodiments, communication 201 may contain a number of sub-components, such as example requested data types, parameters, requests and subjects, shown as subcomponents 203 through 208. Preferably, each such packet comprises an initial code, identifying which such parameter, request and/or function of the initial data communication 201 it is responding to. In some embodiments, such as initial data packet 209 or initial data packet 317, may include such an initial code signifying that it relates to a type of data requested, followed by a code indicating the types of data requested that are available from the data system(s) related to the product. As another example, another, subsequently sent data packet, such as data packet 211 or data packet 319, may include an initial code indicating that it also includes a “main” or other substantive data component, of the type of data requested by the electronic data interchange device 103 in the initial data communication 201. As another example, in some embodiments, a third packet, such as example data packet 321, may contain an initial code indicating that it relates to a time, or timeframe, in which the data, or related product-related activities, was created, followed by (also included in data packet 321) data related to those timeframes. In some embodiments, based on reading such initial codes, the electronic data interchange device 103 routes and/or differently processes the different data packets, reading only the initial codes prior to further routing to subsystems of the control system of the electronic data interchange device, which subsystems are specialized for management of (acting upon) those particular data types.

[0048] In some embodiments, more open-ended data packets, requesting a response from the electronic data interchange device 103, may be issued by the user entity 107. For example, in some embodiments, data systems of the local user (e.g., using locally installed EDI software) may determine a level of deviation from parameters, requests and/or functions requested and the local user’s response, and communicate data indicating such deviations in additional data packets, such as example data packet 323 or example data packet 215. Such additional data packets may also include a suggested substitution of different parameters, requests and/or functions, based on their relationships, correlations, or matching subcomponents, relative to the parameters, requests and/or functions requested within the initial data communication 201.

[0049] Finally, in response to the data packets issued by the user entity 107 to the electronic data interchange device 103, the electronic data interchange device 103 may respond with its own set of discrete data packets, such as example data packets 325. As with other data packets set forth above, data packets 317 may also each include an initial code, indicating the type of data contained in each data packet. In some embodiments, data packets 317 may complete, or attempt to complete, the negotiation of a new EDI format, by accepting or rejecting (a.k.a., “answering”) the user entity-suggested substitutions of different parameters, requests and/or functions, discussed above, which then become, or do not become, respectively, components of future EDI transmittals between the two parties. In some embodiments, the electronic data interchange device 103 may accept such substitutions, which are then provided in response to such acceptance, or, alternatively, may request additional, different parameters, requests and/or functions, in reaction to those suggestions, in a new initial communication, with similar steps as set forth therefore, above, and the negotiation of the EDI format may continue, accordingly.

[0050] The steps set forth above, in reference to Figs. 2 and 3, and in other methods and techniques set forth in the present application, are non-exclusive, and non-limiting.

Many other steps may be added, and some may be removed, in keeping with aspects of the present invention. In addition, the steps set forth above are not exhaustive of the many various different order(s), number(s) and arrangements of steps falling within the scope of the invention, as will be readily apparent to those of skill in the art.

[0051] Fig. 4 is a schematic block diagram of some elements of a control system (hereinafter, the “system” or “control system”) 400, in accordance with some example embodiments of the present invention. In some example embodiments, the control system incorporates a non-transitory machine-readable medium storing instructions that, when executed by one or more processors, execute various aspects of the present invention described herein. The generic and other components and aspects described herein are not exhaustive of the many different systems and variations, including a number of possible hardware aspects that might be used, in accordance with the example embodiments of the invention. Rather, the control system 400 is an example embodiment.

[0052] Control system 400 includes an input/output device 401, a memory device 403, long-term data storage device 405, and processor(s) 407. The processor(s) 407 is (are) capable of receiving, interpreting, processing and manipulating signals and executing instructions for further processing and for output, pre-output and/or storage in and outside of the system. The processor(s) 407 may be general or multipurpose, single- or multithreaded, and may have a single core or several processor cores, including microprocessors. Among other things, the processor(s) 407 is/are capable of processing signals and instructions for the input/output device 401, to cause a user interface to be provided or modified for use by a user on hardware, such as, but not limited to, computer system peripheral devices, such as a mouse, keyboard, touchscreen and/or other display 419, with specialized tools (e.g., for facilitating EDI with an electronic data interchange device, as set forth in this application) and/or presentation and input-facilitating software (as in a graphical user interface, a.k.a. a “GUI”) (e.g., on local machine(s) 411, display 419 or smartphone 420).

[0053] For example, user interface aspects, such as graphical “windows,” “buttons” and data entry fields, may present via, for example, a display, any number of selectable options and/or data entry fields. When the option and/or data entry field is selected, such selection causes aspects of the control system to command other aspects of the control system to track, access and modify data related to products, services and other assets within a supply chain, and record additional data based thereon throughout a product and/or service lifecycle, in accordance with aspects of the invention. In some embodiments, some of such aspects are managed by an ERP, or superuser, which may be included within, or in communication with, the control system, to create, scan and store information, tags and/or films and patterns, in relation to those data, and to provide digital signatures, identification codes or information, and record them in a secure manner on a network (e.g., the Internet and/or another network incorporating a blockchain). For example, and as explained in greater detail elsewhere in this application, the control system may provide standard EDI components, and negotiated new EDI components, generated by algorithms and/or artificial intelligence subsystems of the control system, and, in response to data interchanged, facilitate the creation of a smart contract and/or token on a blockchain, related to any of those data. In some embodiments, the control system may record and label promissory tokens and other parameters for the management of a product and/or service by the control system and other data systems, and provide secure identifiers and/or other data related to the asset to the control system, where it is stored (e.g., on long-term data storage device 405, or server(s) and/or on blockchain(s) 409). A promissory token label is a label, identifier, tag, particle, or any other tool that contains information about energy generation or distribution service by an entity and/or for an energy consumer. In some embodiments, the control system may also facilitate the creation of, recordation of, encryption of, and other actions with respect to promissory tokens, governance variables, or any other asset or virtual asset set forth in this application. The processor(s) 407 may execute instructions stored in memory device 403 and/or long-term data storage device 405, and may communicate via system bus(ses) 475. Input/output device 401 is capable of input/output operations for the system, and may include and communicate through input and/or output hardware, and instances thereof, such as a computer mouse, scanning device or other sensors, actuator(s), communications antenna(ae), keyboard(s), smartphone(s) and/or PDA(s), networked or connected additional computer(s), camera(s) or microphone(s), a mixing board(s), real-to-real tape recorder(s), external hard disk recorder(s), additional movie and/or sound editing system(s) or gear, speaker(s), external filter(s), amp(s), preamp(s), equalizer(s), computer display screen(s) or touch screen(s). Such input/output hardware could implement a program or user interface created, in part, by software, permitting the system and user to carry out the user settings and input discussed in this application. Input/output device 401, memory device 403, data storage device 405, and processor(s) 407 are connected and able to send and receive communications, transmissions and instructions via system bus(ses) 475. Data storage device 405 is capable of providing mass storage for the system, and may be or incorporate a computer-readable medium, may be a connected mass storage device (e.g., flash drive or other drive connected to a Universal Serial Bus (USB) port or Wi-Fi), may use back-end (with or without middle-ware) or cloud storage over a network (e.g., the Internet) as either a memory backup for an internal mass storage device or as a primary memory storage means, or may simply be an internal mass storage device, such as a computer hard drive or optical drive. Generally speaking, the system may be implemented as a client/server arrangement, where features of the system are performed on a remote server, networked to the client and made a client and server by software on both the client computer and server computer. Also generally speaking, the system may be implemented as middleware, whereby it provides output and other services to an external system. In any event, the system may include, or include network connections (e.g, wired, WAN, LAN, 5G, ethernet, satellite, and/or Internet connections) with, any of the example devices or auxiliary devices and/or systems, shown as Internet server(s) and blockchain(s) 409, local machine(s) 411, cameras and microphones 413, sensor(s) 414, internet of things or other ubiquitous computing devices 415, ERP 417, scanner 419 and smartphone 420. Similarly, the control system 400 is capable of accepting input from any of those auxiliary devices and systems, and modifying stored data within them and within itself, based on any input or output sent through input/output device 401.

[0054] Input and output devices may deliver their input and receive output by any known means, including, but not limited to, any of the hardware and/or software examples shown as internet server(s) and blockchain(s) 409, local machine(s) 411, cameras and microphones 413, sensor(s) 414, internet of things or other ubiquitous computing devices 415, ERP 417, display 419 and smartphone 420.

[0055] While the illustrated example of a control system 400 in accordance with the present invention may be helpful to understand the implementation of aspects of the invention, any suitable form of computer system known in the art may be used - for example, in some embodiments, a simpler computer system containing just a processor for executing instructions from a memory or transmission source. The aspects or features set forth may be implemented with, and in any combination of, digital electronic circuitry, hardware, software, firmware, middleware or any other computing technology known in the art, any of which may be aided with external data from external hardware and software, optionally, by networked connection, such as by LAN, WAN, satellite communications networks, 5G or other cellular networks, and/or any of the many connections forming the Internet. The system can be embodied in a tangibly-stored computer program, as by a machine-readable medium and propagated signal, for execution by a programmable processor. The many possible method steps of the example embodiments presented herein may be performed by such a programmable processor, executing a program of instructions, operating on input and output, and generating output and stored data. A computer program includes instructions for a computer to carry out a particular activity to bring about a particular result, and may be written in any programming language, including compiled and uncompiled and interpreted languages and machine language, and can be deployed in any form, including a complete program, module, component, subroutine, or other suitable routine for a computer program. [0056] In some embodiments, the control system includes specialized hardware and software to allow operation in a wide variety of network environments. For example, in some embodiments, the control system carries out any or all of the steps and other techniques set forth in this application despite intermittent network connections. For example, in some such embodiments, if the control system experiences a temporary or other loss of connection to a network server, local intranet server, other network and/or blockchain(s), any data recordation and communications steps may be paused and/or queued until such time as the connection(s) are restored, at which time those steps may be executed. In some such embodiments, despite such a loss of such a connection, subsequent steps after any step including data recording through such a network, on a blockchain, set forth in any method set forth in this application, may still be carried out, and the control system may utilize data recorded in an alternative format, in a nearby, local data storage device, such as long-term data storage device 405 or a data storage device included in ERP 417, instead of data recorded through such a network, on a blockchain. For example, in some such embodiments, such data recorded in an alternative format, in a nearby, local data storage device includes a record signifying that a blockchain record will be made, along with a record of the data to be recorded on the blockchain. In some such embodiments, in which data recordation through such a network, on a blockchain is a prerequisite to such a subsequent step, such data recorded in an alternative format, in a nearby, local data storage device substitutes as the prerequisite for actual recordation on the blockchain, for such subsequent steps.

[0057] As another example, in some embodiments, the control system continues to carry out any or all of the steps and other techniques set forth in this application in an efficient manner, during inconsistent network performance and/or altered type(s) of network connections (e.g., any of the control system’s satellite network, local area network, cellular network, and/or wired network connections, etc., failing, slowing and being reestablished over time). For example, in some such embodiments, if the control system experiences a temporary or other loss of availability, or reduced performance, of a network server, local intranet server, other network and/or blockchain(s), but other networks remain or become available, any data recordation and communications steps may be queued, re-attempted and/or rerouted through such available, alternative networks, until such time as the connection(s) are restored, at which time those steps may be executed. In some such embodiments, despite such a loss of availability or reduced performance of such a server or network, subsequent steps after any step including data recording through such a network, on a blockchain, set forth in any method set forth in this application, may still be carried out, and the control system may utilize data recorded in an alternative format, in a nearby, local data storage device, such as long-term data storage device 405 or a data storage device included in ERP 417, instead of data recorded through such a network, on a blockchain. For example, in some such embodiments, such data recorded in an alternative format, in a nearby, local data storage device includes a record signifying that a blockchain record will be made, along with a record of the data to be recorded on the blockchain. In some such embodiments, in which data recordation through such a network, on a blockchain is a prerequisite to such a subsequent step, such data recorded in an alternative format, in a nearby, local data storage device substitutes as the prerequisite for actual recordation on the blockchain, for such subsequent steps.

[0058] In some embodiments, the control system may divide network communications and execute them in different parts over different networks. In some such embodiments, such a division of network communications may be made to improve the encryption of such communications, e.g., by segmenting independently illegible aspects of the communication, across each network.

[0059] Fig. 5 depicts aspects of a new type of asset management system 501 for tracking and managing products, and parts and sub-parts thereof, over a product lifecycle in complex manufacturing, maintenance and/or usage environments, such as example manufacturing environment 500.

[0060] Within the depicted example environment 500, a complex industrial product and/or product part, namely, example electronic vehicle (“EV”) battery pack 503, is shown in an assembly line work area 505. Example EV battery pack 503 comprises a variety of sub-part components, including example interchangeable battery modules 507 and 509, example electrical wiring 511, an example semiconductor board 513 including conductive leads, such example integral conductive wiring lead 515, and electrical interface ports, such as example snap fastener / electrical connector 517, on which battery modules 505 and 507, and other battery modules, may be variably mounted and electrically connected to power management hardware, such as example electrical power controller 519. In some embodiments, some or all of such sub-parts or other components may be mounted on a structural scaffold, such as example structural mounting sled 521, allowing all of battery pack 503 to be mounted onto or otherwise physically connected to other products or product parts (e.g., an EV and/or EV battery compartment, in a later use environment (not pictured)), e.g., via fasteners (also not pictured).

[0061] In some embodiments of a system and/or method in accordance with aspects of the invention, a user of the system, such as example assembly line worker 523, applies a new form of surface-adhering, encoded structure over, on or about (a.k.a., “covering”) assets, such as parts and sub-parts of a manufactured product (e.g., battery pack 503). Thus, as pictured, in some embodiments, assembly line worker 503 applies such a surface-adhering, encoded structure - namely, example insulated conductive threading 525, integrated with an example adhesive material 527. In some embodiments, such a surface-adhering, encoded structure includes a unique pattern, such as conductive threads, leads, or wires, bearing a unique electronic, electromagnetic, visual and/or capacitive pattern. In some embodiments, such a surface-adhering, encoded structure, with such a unique pattern, serves as a tracking device, aiding in the identification and location of parts and/or sub-parts covered by the surface-adhering, encoded structure, as well as the status of such parts and/or sub-parts, and products in which they are integrated. Further methods in accordance with some such embodiments will be discussed in greater detail below.

[0062] In some embodiments, a user, such as assembly line worker 523, uses a new form of applicator to place such a surface-adhering, encoded structure over, on or about parts and sub-parts of a product. For example, in some embodiments, as pictured, a user may use a spraying, squirting or other applicator device 529, which, in some embodiments, sends a sheet or mesh comprising such a surface-adhering, encoded structure out and away from a sprayer exit end 531, which the user aims away from himself and at the product (i.e., covering battery pack 503). In some embodiments, such a sheet or mesh comprises a non-volatile medium. In some embodiments, such a sheet or mesh is transparent, or translucent. In some embodiments, such a sheet or mesh is otherwise invisible or substantially invisible. For example, in some such embodiments, such a sheet or mesh is too thin to be perceived by the human eye. In some embodiments, such a sheet or mesh is durable and undisturbed by ordinary or other wear-and-tear in authorized use of the part, sub-part or product. In other embodiments, such a sheet or mesh is worn in pre-determined pattern types by such wear-and-tear, and such changes in patterns may be sensed and recorded by the control system, along with data signifying that such wear and tear has occurred, and/or events or product status(es) associated with such wear and tear. In some embodiments, the sheet or mesh is adhered to a surface of product packaging, or integrated with product packaging, holding the part, sub-part and/or product. In some such embodiments, such a sheet or mesh may, alternatively or in addition to covering them, be embedded, or partially embedded, into the parts and subparts of a product (e.g., within the housing, or deeper within the part and/or sub-part). In such embodiments, however, such a sheet or mesh preferably includes partially exposed conductive connections for connection to a scanning device, or includes a remotely scannable component (e.g., antenna or chip) operatively connected to the unique pattem(s) set forth above (e.g., conductive connections to the threads, leads, or wires discussed herein). In some embodiments, such a sheet or mesh is non-toxic, biodegradable and/or edible. In some embodiments, such a sheet or mesh comprises an adhesive film. In some such embodiments, such a sheet comprises an adhesive on only one side, facing the part, sub-part or product. In some embodiments, such a sheet or mesh comprises is formed from a liquid released from applicator device 529 (e.g., by a propellant) that solidifies upon, or shortly after, exposure to air, upon or on or about the time it adheres with an outer surface of the part, sub-part and/or product. In some embodiments, conductive threads are generated and mixed with an adhesive, forming the sheet or mesh. In some such embodiments, such conductive threads generate a random physical pattern as they are so mixed, and propelled onto a part, sub-part and/or product (e.g., by complex, interactive forces from such mixing and propulsion.) In other embodiments, such a pattern may be or include a section fixed by a pattern generator (e.g., prior to loading the pattern into a compartment of the applicator device 529). In some such embodiments, such a section may be placed by the applicator on, about or within moving parts, and/or parts that, if physically changed (e.g., worn), indicate a change in status of the product or part over which it is placed. In some embodiments, such threads overlap with one another, forming an interlaced pattern, generating a unique, “signature” appearance and/or electrical, capacitive and/or electromagnetic characteristics. In some such embodiments, sensors at the assembly line work area 505 may be omitted. However, in some embodiments, such sensors are included, as will be discussed immediately below.

[0063] In some embodiments, applicator device 529 comprises a camera or other pattern sensor 533. In some such embodiments, pattern sensor 533 includes an aimable optical component, such as lens 535. In some such embodiments, lens 535 is trained on the parts, sub-parts or product being applied with the surface-adhering, encoded structure (e.g., by mounting or other orientation in the direction of squirting example adhesive material 527). In some embodiments, the pattern sensor 533 includes, or is connected with computer hardware and software of a control system (such as control unit 537, which may be a control system set forth in reference to Fig. 4), which records data related to a pattern within the surface-adhering, encoded structure. In some embodiments, the control system records other product-related and/or identifying data, and associates those data with the data related to the pattern. In some such embodiments, these data are recorded on a blockchain within or connected to the control system. As such, in some embodiments, the unique pattern generated and sprayed onto parts, sub-parts and a product is permanently recorded in an immutable, distributed manner, and the status of the part, sub-part and/or product can be later scanned, by the same pattern sensor 533, or another pattern scanner, connected for communications with that blockchain (and/or the control system.) In this sense, applicator device 529 is both a code applicator, and a part and sub-part tracking device.

[0064] In some embodiments, the “signature” appearance and/or electrical, capacitive and/or electromagnetic characteristics of sheet or mesh may be detected by physical contact with a testing device. For example, in some embodiments, a pattern sensing and reading electrical conduit device, such as an electrical probe 539, with segmented conductors capable of applying electrical charges, may be included, and also comprised within or connected for communications with, the control system. In some embodiments, a specific location on or about the sheet or mesh may be touched by the electrical probe 539, and, by applying a charge to the sheet or mesh through the probe, and sensing and recording the resistance, capacitance or other characteristics of the sheet or mesh and its unique pattern of threading, the identity of the part, sub-part and or product can be recorded.

[0065] Furthermore, in some embodiments, changes to such unique patterns, and characteristics, are used as a basis for assessing changes to a product, at a later time. For example, as discussed above, in some embodiments, such a sheet or mesh is worn down in pre-determined pattern types by such ordinary wear-and-tear, and such changes in patterns may be sensed and recorded by the control system, along with data signifying that such wear and tear has occurred. In other embodiments, such a sheet or mesh is damaged or missing when a sub-part is removed or replaced, and due to the unique nature of each pattern, cannot be easily replicated or counterfeited. In such embodiments, such changes to the pattern are sensed and recorded by the control system, along with data signifying that such changes in parts and/or counterfeiting have or may have occurred. In some such embodiments, such changes must be authorized by the control system or a super-user of the control system, or else the change is recorded as a “fault.” In some such embodiments, the provenance of the product may be negatively impacted by such a fault. In some embodiments, the control system will not issue a certificate with respect to the part, sub-part and/or product when such a fault is detected, or will record and/or report caveat(s) regarding the provenance of the product. As mentioned above, any of the above changes and statuses may be recorded over a network, onto a blockchain, in some embodiments (e.g., as a smart contract).

[0066] In some embodiments, an electronic and/or wireless reading conduit device 541 is placed into, or otherwise connected with the sheet or mesh, allowing the “reading” of the unique signature pattern. In some embodiments, the reading conduit device includes electrical contacts 543, conductively connected to conductor(s) comprised within the conductive and/or capacitive film, which are complementary in form to, and able to interface conductively with, electrical contacts 545 of electrical probe 539

[0067] As mentioned above, in some embodiments, instead or in addition to such films and/or sheets, unique machine-readable (but not human-readable) patterns are deliberately inflicted into product components during manufacturing, creating a unique identifier of that product, and other product-related information in conjunction with the control system. In some embodiments, a new, unique data format is created during such manufacturing, in which particular sub-patterns are encoded by the control system to signify particular product-related information, which are then recorded by the control system. In some embodiments, projected erosion, wear-and-tear, and other alterations of those patterns are also a part of that new data format, and the control system records data related to such alterations upon detecting such alterations of those patterns in subsequent scanning (e.g., visual) of the part.

[0068] In some embodiments, such a creation of a unique signature pattern is made to one or more surfaces of a product, and/or its constituent parts, as the product is manufactured, sold, distributed, used, maintained, remanufactured, resold, retired, or subject to other steps in the product lifecycle.

[0069] In various embodiments, new systems, devices and methods for enhancing information transparency for persons and entities within a supply chain are provided. For example, in some embodiments, a device comprised within or comprising a specialized hardware- and software-based control system, such as any of the device(s) discussed in this application, produces and presents information related to a product, service or other asset within the supply chain to a user. For example, in some embodiments, a specialized graphical user interface (“GUI”) is presented on display hardware conveying such information to distributors, wholesalers, refurbishers, servicers and/or other persons or entities within the supply chain.

[0070] In some embodiments, such information, and transactions between such persons or entities, and other actions relevant to a product, service or other asset in the supply chain are recorded on a blockchain as a smart contract, executed and recorded through a transactional tool(s) implemented by the control system. In some such embodiments, such a transactional tool(s) includes a promissory note, between at least two contracting parties, and recorded by the control system. In some such embodiments, such a transactional tool includes a technique for issuing, signing, transmitting and recording (a.k.a. “issuing”) a token, such as a “promissory token,” executed with the aid of a decentralized network, included in, or including the control system. In some embodiments, such a promissory token may record, or be, a virtual asset, which may have a value determined by the control system. In some embodiments, tokens comprise a signed transaction data structure, recorded on a blockchain. In some such embodiments, such a decentralized network includes at least one blockchain. In some embodiments, such a decentralized network includes a plurality of blockchains. In some embodiments, such a promissory token includes restrictions on such promissory tokens, as managed by the control system. For example, in some embodiments, such a restriction prevents transactions related to a particular classification(s), while permitting others.

[0071] Such a transactional tool may record data related to a wide variety of transactions related to a product, service or other asset within a supply chain. For example, in some such embodiments, the transactional tool creates and records data related to the delivery of a product, service or other asset to a recipient. In some embodiments, the transactional tool creates a record of data related to the receipt of the product, service or other asset by a recipient. In some embodiments, the transactional tool creates a record of data related to the use of a product, service or other asset by a recipient. In some embodiments, a transactional tool records other data, related to a transaction between persons or entities within the supply chain. For example, in some embodiments, such a transactional tool records data regarding the identity of a buyer and/or seller who are parties to such a transaction. As another example, in some embodiments, such a transactional tool records data regarding alterations to any of the unique patterns associated with products discussed above. In some such embodiments, particular types of alterations yield data regarding the condition of a product and/or service, or part thereof, which is recorded by the control system. [0072] In some embodiments, the smart contracts discussed above include a governance feature, and the control system implements an algorithm incorporating a plurality of variables related to the supply and demand for particular preferred types of transactions.

[0073] In some embodiments, promissory tokens are issued by a control system including computer hardware and software connected to a network, such as the Internet and/or one or more blockchains, and carrying out any other aspects of the invention set forth in this application. In some embodiments, such promissory tokens are issued by one or more user(s) of the control system with privileges to issue such promissory tokens. For example, in some embodiments, such users include manufacturers of a product or service providers. In some such embodiments, one or more of such blockchain(s) are used to record product- or service-related transactions. In some such instances, such promissory tokens may be visible, or at least partially visible, to any party participating in a supply chain.

[0074] In some embodiments, such a control system creates a digital signature based on data-bearing tag(s), which may be chemical, electromagnetic, visual-based or other tag(s) placed on, in or throughout an asset for use in a manufacturing, maintenance, conveyance, shipping, delivery, distribution, or another industrial process (“data-bearing tag”). A data-bearing tag may be a label, identifier, tag, particle, or any other device that contains information about an asset, in various embodiments. In some embodiments, a data-bearing tag is, or comprises or is comprised within, any of the unique pattem(s) and/or film(s), and/or reading conduit devices discussed in this Application. In some embodiments, at least part of such a tag, and/or the data held within them, are alterable by a user of the supply chain. In some embodiments, such a tag or data are so altered by virtue of actions of such a user related to a product, or use of a product fastened to that tag. For example, in some embodiments, any of the films bearing any of the types of unique patterns discussed in this application may be broken or worn based on corresponding wear-and-tear or replacement of product components covered by those patterns, and the control system interprets changes to those patterns, and the reading thereof, as corresponding with data signifying such wear-and-tear or replacement. [0075] In some embodiments, the control system then combines that information about an asset with the digital signature into a new, combined data set, and inserts all or at least part of that set into a secure network and/or a blockchain, as a series of recorded values. Preferably, an insertion process into a blockchain is used, which creates a secure, encrypted identifier, separate from the digital signature, which is associated with the asset. This process creates a new identifier, for use on the blockchain, unique to the particular asset, and allows a user to trace any asset recorded by the control system, view important data related to it, and authenticate it, in real time, and to better manage the asset throughout its lifecycle within the control system. The enhanced security of the blockchain-implemented embodiment protects the asset from hacking and other security threats, making the control system substantially inviolable.