Systems and Methods for Assurance Management

Abstract

The present invention will process and combine data from transaction information and create a verifiable data record of the transaction with accompanying terms, conditions, provisions, and parties and perform operational ratings, rankings, probabilities, assignments, and tokenization in various distributed ledger storage systems. The present invention improves the operation of assurances by identifying complementary components that may be integrated, combined, extended, or transformed and thus provide consolidated holistic benefits for the user.

Claims

1. A method for use in an assurance management system, said method employing computer means having processing means, data storage means, network communications means, and communication means with a distributed ledger of a distributed ledger network and comprising the steps of: (a) a Subscriber, as a person, group, organization, human, legal, virtual, or contrived entity, creating an account record with requested information; (b) a Provider, creating an account record with requested information, as an entity originating an Assurance Policy, specifying the terms of performance and one or more Assurance Element, as an individual object that includes one or more provision, feature, attribute, or specification, as designated by a Provider and to be conferred to a Subscriber or Beneficiary in operation with a Transaction Master, as a transaction envelope or wrapper for the Assurance Policy and Assurance Element to be recorded in the distributed ledger and being instantiated by one or more Provider; (c) receiving a Transaction Master record containing an Assurance Policy and Assurance Element as originated from a Provider; (d) identifying any Transaction Supplement, as one or more Provider being associated with the Transaction Master and offering supplemental Assurance Policy and Assurance Element, and integrating by means of chaining any supplementary Assurance Policy and Assurance Element to provide enhancement, extension, or continuity of any Assurance Policy or Assurance Element; (e) creating a Tokenization, involving the process of converting data into a fungible or non-fungible encoded structure (token) and stored in a verifiable arrangement as developed in such compatible distributed ledger technologies, of the Transaction Master and storing a digital representation of the Transaction Master on a distributed ledger of a distributed ledger network storage; and (f) providing access to the Transaction Master distributed ledger network storage for management, amendment, and query.

2. The method of claim 1 comprising the further step of Dynamic Assurance, the process of adjusting an established Assurance Policy or Assurance Element, by discovering, evaluating, and determining if additional Provider Assurance Policy or Assurance Element may be applied to a Transaction Master.

3. The method of claim 1 comprising the further step of analyzing the Transaction Master distributed ledger network storage to produce correlated Subscriber cohorts that may petition Provider for enhanced Assurance Policy or Assurance Element in dynamic fashion for inclusion and amendment to a Transaction Master.

4. The method of claim 1 comprising the further step of providing access to the Transaction Master distributed ledger network storage for Subscriber and Provider management.

5. The method of claim 1 comprising the further step of evaluating performance factors that may be computed by the assurance management system using historical and available data sources to provide statistical, probability, and projection assessments of the Provider, Subscriber, Beneficiary, Assurance Policy, and Assurance Element.

6. The method of claim 1 comprising the further step of monitoring Transaction Master Assurance Policy or Assurance Element and communicating notices, alerts, requirements, actions, expirations, and instructions as may be contained in the Transaction Master.

7. The method of claim 1 comprising the further step of assigning one or more Subscriber, and none or more Beneficiary, at the time of storing a Transaction Master, or at a time post-storage amending a Transaction Master.

8. The method of claim 7 comprising the further step whereby the Transaction Master, in whole or in part, may be assigned or reassigned to none or more Subscriber or Beneficiary with appropriate tokenization.

9. The method of claim 7 comprising the further step whereby Subscriber or Beneficiary assignments or amendments are stored on a distributed ledger of a distributed ledger network storage.

10. A computerized system of one or more processors, and one or more memories as adapted to store a plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the system to provide: assignment, analysis, authentication, encryption, tokenization, notification, storage, and management operations all as configured to process Transaction Master information; produce analysis, rating, and probability results of parties, Transaction Master, and Assurance Element; record available and related transaction information, rating, ranking, and probability results; the creation, authentication, and transfer of various token protocol objects; assignment of Transaction Master records to the designated Provider, Subscriber, Beneficiary; storage of Transaction Master records on a distributed ledger of a distributed ledger network storage; verifiably pairing a Transaction Master record with a digital representation comprising: a computer system in communication with a distributed ledger of a distributed ledger network; a first data capture device in communications with the computer system; a second device in communication with the computer system; a set of computer readable instructions included in the computer system configured for: creating a first Transaction Master record from the first data capture device including, a first Provider, a first Subscriber, a first time, a first Assurance Policy, one or more first Assurance Element, none or more Beneficiary, and a first set of performance factors wherein the first Transaction Master record includes a first digital representation of a first Transaction Master record captured by the first data capture device, and, storing the first Transaction Master record on the distributed ledger of a distributed ledger network storage for access by a second device in communication with the computer system.

11. The computerized system of claim 10 wherein the set of computer readable instructions include instructions for receiving the Transaction Master data that includes any of portrayals of goods, services, information, terms, conditions, limitations, effective time periods, covenants, restrictions, policies, instructions, procedures, and associated data that relates to the nature of the Assurance Policy or Assurance Element.

12. The computerized system of claim 10 wherein the set of computer readable instructions include instructions for receiving external data from an external data source associated with sources from the group consisting of public records, enterprise software, a local computer device, distributed ledger network, and remote computer device and any combination thereof in communication with the computer system.

13. The computerized system of claim 12 wherein the external data includes scores, ratings, commentary, performance evaluations, personal information, and financial information as related to the parties associated with a Transaction Master record.

14. The computerized system of claim 10 wherein the set of computer readable instructions include instructions for calculating a rating and a probability spectrum for the parties associated with a Transaction Master using available data, assigning such rating and probability spectrum to the parties associated with a Transaction Master and assigning such rating and probability spectrum to the Transaction Master record, and storing the results on the distributed ledger of a distributed ledger network storage.

15. The computerized system of claim 10 wherein the set of computer readable instructions include: (a) means for recording data of users, transactions, analysis results, and commentary; (b) means for receiving requests to process transactions; (c) means for enabling user access to information; (d) means for producing Transaction Master records on a distributed ledger of a distributed ledger network storage; (e) means for processing notices, alerts, requirements, actions, expirations, and instructions as may be contained in the Transaction Master record; (f) means for transmitting information to users by any available modality; (g) means for consummating transactions; and, (h) means for receiving, recording, and storing user information and transaction activity.

Description

DESCRIPTION OF THE DRAWINGS

[0116] These and other advantages will become more apparent from the detailed description of the various embodiments of the present specification with reference to the drawings wherein:

[0117] FIG. 1 is a block diagram of an assurance management system, in accordance with the embodiments of the present specification that illustrates establishing and executing data connections, communication, display, delivery, processing, transactions, settlements, analysis, combinations, encryption, ratings, assignment, tokenization, monitoring, and storage functions.

[0118] FIG. 2 illustrates a screen display of information related to a Provider account in accordance with the embodiments of the present disclosure.

[0119] FIG. 3 illustrates a screen display of information related to a Host account in accordance with the embodiments of the present disclosure.

[0120] FIG. 4 illustrates a screen display of information related to a Subscriber account in accordance with the embodiments of the present disclosure.

[0121] FIG. 5 illustrates a screen display of information related to a Beneficiary account in accordance with the embodiments of the present disclosure.

[0122] FIG. 6 illustrates a screen display of information related to a Transaction Master framework in accordance with the embodiments of the present disclosure.

[0123] FIG. 7 illustrates a screen display of information related to a transaction in accordance with the embodiments of the present disclosure.

[0124] FIG. 8 illustrates a screen display of information related to an assignment of a Beneficiary in accordance with the embodiments of the present disclosure.

[0125] FIG. 9A is a block diagram of an assurance management server processing system that illustrates a flow-diagram of the present invention.

[0126] FIG. 9B depicts further steps carried out by the process started in FIG. 9A.

[0127] FIG. 10 illustrates a screen display of information related to a Transaction Master communication framework in accordance with the embodiments of the present disclosure.

[0128] FIG. 11 is a block diagram of a flow chart displaying the processing of a Provider creating and transmitting a Transaction Master.

[0129] FIG. 12 is a block diagram of a flow chart displaying the processing of a Beneficiary receiving a Transaction Master.

[0130] FIG. 13 illustrates a screen display of information related to the analysis of a Transaction Master.

[0131] FIG. 14 illustrates a screen display of information related to the entry of rating and feedback information from Subscriber to Provider.

[0132] FIG. 15 is a block diagram of a flow chart displaying the processing of a Beneficiary providing rating and feedback to a Provider.

[0133] FIG. 16 illustrates a screen display of information related to the entry of rating and feedback information from Provider to Subscriber.

[0134] FIG. 17 is a block diagram of a flow chart displaying the processing of a Provider providing rating and feedback to Beneficiary.

[0135] FIG. 18 illustrates a screen display of information related to a listing of Transaction Masters.

[0136] FIG. 19 illustrates a screen display of information related to a Provider listing of reliability ratings for Transaction Masters.

[0137] FIG. 20 illustrates a screen display of information related to the entry of rating and feedback information for a selected account.

[0138] FIG. 21 is a block diagram of a flow chart displaying the processing of a Subscriber providing rating and feedback to a selected account.

[0139] FIG. 22 is a stacked Venn diagram illustrating the conceptual arrangement of processing components.

[0140] FIG. 23 illustrates an example of a product purchase flow-diagram with transformed integrated and combined assurance policies.

[0141] FIG. 24 illustrates a visual display of the one or more assurance metric aspects as combined and monitored.

DETAILED DESCRIPTION AND MODE OF IMPLEMENTATION

[0142] The present system and methods provide means to manage in a convenient and combinatorial manner transactions related to one or more Provider and Assurance Element and construct a registry of agreements, assignments, assurance terms, combinations, tokens, ratings, projections, and feedback for Subscribers.

[0143] Subscribers and Beneficiaries can be associated with any type of transaction, communication, or assigned instrument including, but not limited to, association or group instances including assurance terms and any one or more of grants that bestow, confer, contract with, present title or rights, declare requirements, make available, or convey an assignment to a Subscriber or Beneficiary that assures and warrants the Subscriber or Beneficiary the ability to any of privileges or rights to assert, demand, obtain standing, gain possession, exercise, review, and invoke claim and entitlement to one or more assurance terms.

DETAILED DESCRIPTION

[0144] The embodiments of the present specification pertain to an invention that is designed for individual, group, and entity users. The embodiments provide a system and methods for transactions and communications involving assurances to be recorded, processed, and reviewed, thus enabling methods of combination, authentication, preservation, analysis, and production of documentation and results. The Transaction Master and Assurance Element, along with their respective Assurance Policy, are the core functional components enabling assurance terms to be managed for the benefit of a Subscriber. No inferences should be drawn that the account structures (logically or physically) as described or displayed are intended to limit the structure that is implemented.

[0145] The assurance system processes and extracts data from a transaction or communication and creates a data record of the transaction or communication and performs operational assignments in various storage systems including distributed-ledger systems.

[0146] Access to the assurance service is accomplished through online hosted servers using application software that processes the transaction or communication information, extracts data, combines, authenticates and tokenizes data, and produces ratings and projections. Further embodiments of the present specification may be embedded in other applications, such as digital wallets and social media systems. Subscribers may pay a periodic fee to use the software application.

[0147] In the event that a Subscriber needs to generate a claim for assurance performance (e.g., free repair of a device), a Subscriber can access their account on the system server and retrieve information such as their assigned rights of assurance performance, guarantees, time periods, obligations, and be able to present to the repairing authority authentic documentation (e.g., tokens) for confirmation of device purchase and ownership.

[0148] At various times, the Subscriber is notified and informed of their assurance rights still in force and advised of such assurance terms as being available and actively conferred to the Subscriber. The service can also provide lists of transaction parties as originally involved in the assignment of any Transaction Master or Assurance Element. Consequently, the present invention combines a number of electronic and digital capabilities to make Subscriber assignment and assurance management more convenient, accurate, efficient, trustworthy, and persistent. These features and aspects will become better understood with regard to the following descriptions of the embodiments.

[0149] The following presents the general operation of the present invention with processing features that may be accomplished by a person skilled in the art of data communication, computer programming, databases, encryption, distributed ledgers, and related system infrastructures.

[0150] A Provider optionally connects to the present invention system server using a device with communication and data network means and creates a Provider account record in a connected database. The Provider database record comprises data fields such as, for example and not limitation, name, identification code(s), contact information, default settlement options, default assurance terms and policies, premiums, operating conditions, environmental metrics, and public and private encryption codes.

[0151] A Provider account record is not required for a Provider to have a Transaction Master received by a Subscriber account and entered into the present invention. A Transaction Master can be created external to the present invention service in various forms and formats and designations, and then received by a Subscriber and entered into the assurance service server by automatic or manual means on the selection, reception, connection, or acquisition of a Transaction Master (e.g., purchase of a product at a retail outlet and the manual entry of the merchant's printed sales receipt data).

[0152] To create or enter a Transaction Master or Assurance Element, a Provider having an account record will connect to the present invention service server using a device with communication and data network means to create or enter one or more Transaction Master or Assurance Element record in a connected database. The Transaction Master or Assurance Element database record comprises one or more of data fields such as, for example and not limitation, Provider identification, contact information, statement, category, item description, item identification, Assurance Policy with assurance terms, conditions, valid dates and times when the Transaction Master or Assurance Element in whole and/or individual assurance terms in part may be active, environmental metrics, settlement or acceptance options, and ratings. Once constructed, the Transaction Master or Assurance Element may be transmitted, using appropriate means, to a Provider, Host, or Subscriber.

[0153] An Assurance Policy in a Transaction Master or Assurance Element may include provision of actionable items or services, as example and not limitation, advantages, awards, benefits, claims, contracts, dates, disbursements, donations, duties, valid time periods, events, features, items, pledges, powers, prizes, privileges, profits, promises, receipts, reimbursements, repairs, replacements, reservations, rights, services, titles, vows, winnings, in any single or combination thereof.

[0154] An example of an Assurance Policy is a home insurance policy that pledges to pay $250,000.00 upon certain damage conditions occurring. Another example of an Assurance Policy is a theatre guaranteeing the reservation of a specific seat at a concert. A further example of an Assurance Policy is a lawn maintenance service promising to cut a homeowner's lawn bi-weekly. In all instances, the present invention service processes and extracts data from transaction or communication information and creates a data record of the transaction or communication, parses the assurance provisions, combines available features, enters Transaction Master and Assurance Element records, and performs Subscriber assignments in various storage systems as described in this specification.

[0155] A Provider having created, transmitted, or entered a Transaction Master or Assurance Element may then exhibit or deliver it, with collateral materials as appropriate, by using one or more display or transmission channels. The Transaction Master or Assurance Element could be exhibited, as example, by use of a direct communication channel (e.g., e-Mail, telemarketing), or by a public display channel (e.g., placement of a product on a Walmart store shelf, Internet website), or combinations of display channels. The use of an intermediary by the Provider to exhibit a Transaction Master to prospective Subscribers, such as exhibiting a product on a Walmart shelf, constitutes the use of a Host (e.g., Walmart) and such Host may append their own supplementary Assurance Policy (i.e. Transaction Supplement) to the Provider's Transaction Master. As an example, Walmart may provide assurance terms of a refund or exchange within thirty days of purchase in addition to any Provider Assurance Policy, e.g., free defect repairs for one year. As an example, Milwaukee Tool Company, as a Provider, creates an Assurance Element record in their account for an M18 drill. Milwaukee then contracts with Walmart, as Host, to display their M18 drill on the store shelf. Walmart sells the drill to a consumer (i.e., Subscriber) with Walmart creating a Transaction Master and including Milwaukee's Assurance Element in the sales receipt.

[0156] Information related to the Provider Transaction Master will be presented in a fashion appropriate for the particular display or communication channel. The present invention service will process and extract data from the transaction or communication information and create a data record of the transaction or communication and perform operational analysis, combinations, ratings, rankings, projections, and Subscriber assignments in various storage systems as described in this specification.

[0157] The Provider, Subscriber, and Host account interfaces and database would have multiple action options available as one skilled in the art of member account management would readily understand to provide, e.g., profile maintenance, data entry, feedback, search, and display.

[0158] The fields and columns not specifically mentioned in accounts, yet deemed appropriate as conditions evolve, will be readily apparent to those skilled in the art of user interface and database design and implementation. It should be understood that the field and column structure displayed in screen templates is merely representative and not intended to restrict the present invention. Those skilled in the art of database management system design and implementation may make changes, including the addition or deletion of fields to effectuate system functionality.

[0159] The user and system display configuration presented is simplified here for purposes of brevity. In actual implementations, many more fields may be used to facilitate other account data and related information and to incorporate additional system parameters related to the evolving nature of transactions and information. The display layouts will be readily appreciated by those skilled in the art of database management system design and implementation. It should be noted that the fields and their apparent arrangement in displays are merely representative to enable one skilled in the art to make and use the present invention. No inferences should be drawn that the account structures (logically or physically) as described or displayed are intended to limit the structure that is implemented.

[0160] FIG. 1 illustrates an assurance management system in accordance with the embodiments of the present specification. The system 100 includes a Beneficiary computing and communication device 110, a Subscriber computing and communication device 120, a Provider computing and communication device 130, a Host computing and communication device 140, network and data connections 150, external data source servers 160, assurance management servers 170, one or more modules 180, a data processing module 184, a data extraction, combination, and tokenizing module 186, a data tracking module 188, a storage device 190, and one or more database 192.

[0161] The computing and communication devices 110, 120, 130, and 140 illustrate methods of inputting and receiving information for transmission using network and data connections 150 with server 170. Computing and communication devices would include, without limitation, mobile devices, telephones, beacons, tags, virtual assistants, and personal computers. It is contemplated that any type of computing and data communication device may be used for transmission and reception with the server 170.

[0162] The computing and communication devices 110, 120, 130, and 140 may communicate with server 170 through any transmission network 150 (e.g., Internet, telephone) having operative communication and data transfer connections.

[0163] The server 170 is a server for performing services for connected clients. The server 170 is in operative communication with the one or more modules 180. In the embodiments of the present disclosure there are three modules. These include the data processing module 184, the data extraction, combination, and tokenizing module 186, and the data tracking module 188. However, a number of other modules are contemplated to provide system services and capabilities as technologies evolve.

[0164] The data processing module 184 processes internal and external data received and transmitted through network connections 150. The data extraction module 186 is used for extracting specific processed data from the data processed by module 184. The data to be extracted and employed may be pre-programmed by software or may be manually performed by the Subscriber. The extracted data will be reviewed for combination of related assurance terms and compiled into tokens by module 186 as appropriate according to the present invention. The data tracking module 188 is used for tracking and monitoring the data processed by the data processing module 184, and the data extracted by the data extraction, combination, and tokenizing module 186. The data tracking module 188 tracks and monitors the processed and extracted data for review, changes, and notification purposes.

[0165] The data that is processed by the one or more modules 180 is stored in the storage device 190. The storage device 190 may contain one or more databases 192. The data stored in the database 192 can contain, without limitation, one or more of names and addresses, accounts, Transaction Master, Assurance Element, tokens, ratings, and item or service information.

[0166] In addition, information can be determined by the system employing available data, as example: Subscriber rating and projection factors integrating internal and external information such as social media. Furthermore, content management software or distributed ledger systems can be used to trigger events based on events or conditions. Such trigger allows Subscribers to be informed during predetermined or projected events or time periods that an Assurance Element requires action or is nearing an exceptional situation or conclusion of one or more assurance terms.

[0167] Referring now to FIG. 2, therein depicted is a Provider's information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 200 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and ratings 210, preferences and policies, rules and conditions, settlement options, and notices 220, and assignments 230 data in the form of system information and correspondingly printed on screen 200 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 200 is a visual display form that is generated in a conventional manner by or on behalf of assurance management server 170 and is usually presented via a computer display terminal or any such visual, audio, or tactile display device.

[0168] In all screen and visual display instances, the present invention certainly envisions Subscribers employing other means of entering and receiving information beyond visual displays, such as, without limitation, audio, system-to-system communications, tactile, along with robotic and evolving automaton means.

[0169] Referring now to FIG. 3, therein depicted is a Host's information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 300 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and ratings 310, preferences and policies, rules and conditions, settlement options, and notices 320, and assignments 330 data in the form of system information and correspondingly printed on screen 300 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 300 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0170] Referring to FIG. 4, therein depicted is a Subscriber's information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 400 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and ratings 410, preferences and policies, rules and conditions, settlement options, and notices 420, and assignments 430 data in the form of system information and correspondingly printed on screen 400 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 400 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0171] Referring now to FIG. 5, therein depicted is a Beneficiary's information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 500 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and ratings 510, preferences and disclosures, rules and conditions, and messages 520, and assignments 530 data in the form of system information and correspondingly printed on screen 500 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 500 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0172] Referring to FIG. 6, therein depicted is a Transaction Master's transaction information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 600 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and item description and Transaction Master and Assurance Element attributes 610, assurance terms, settlement acceptance options, rules and conditions, and notes and messages 620 data in the form of system information and correspondingly printed on screen 600 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 600 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0173] Referring now to FIG. 7, therein depicted is a transaction's information record as Transaction Master delivered to a Subscriber or Beneficiary illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 700 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and item description and attributes 710, assurance terms, settlement acceptance options, rules and conditions, and notes and messages 720, Subscriber information and transaction details and options 730, and Beneficiary information and details 740 data in the form of system information and correspondingly printed on screen 700 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 700 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0174] Referring to FIG. 8, therein depicted is a Beneficiary's assignment information record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 800 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and Transaction Master and Assurance Element description and attributes 810, Transaction Master and Assurance Element assurance terms, rules and conditions, and notes and messages 820, selected Beneficiary information and assurance details and options 830, Subscriber information and Transaction Master description and options 840, and present and past history of assigned Beneficiary information and details 850 data in the form of system information and correspondingly printed on screen 800 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 800 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0175] FIGS. 9A and 9B illustrate an assurance management flow-diagram in accordance with the embodiments of the present specification. The method 900 includes the following steps. In step 905, a Provider creates an Assurance Policy describing statements, items, assurance terms, and other declaratory information. In step 910, the Provider may use a Host to exhibit or deliver the Assurance Element Assurance Policy and a supplementary Assurance Policy may be created and appended by the Host. In step 915, the Assurance Policy(s) are exhibited or delivered to Subscriber. In step 920, Subscriber(s) are able to review Assurance Policy(s) and may provide comment. In step 925, a Subscriber can select, accept, enter, or acquire Assurance Policy(s). In step 930, a Subscriber provides settlement or acceptance. In step 935, Subscriber becomes default Beneficiary or makes a Beneficiary assignment(s) to the one or more Assurance Element(s). In step 940, one or more portions of the transaction information are transferred to an assurance service server device. In step 945, the transferred information is processed and data extracted for analysis and combination. In step 950, Subscriber assignments are determined from the processed data. In step 955, internal and external data may be used, captured, and transferred to the assurance service server device for analysis and production of ratings, rankings, and projections. In step 960, transaction information, processed data, assignment(s), supplemental information, tokenization, and the results of analysis and combinations are stored in one or more databases of a storage device. In step 965, transaction information, processed data, assignment(s), supplemental information, and the results of analysis and combination may be processed, transferred, and posted to a distributed ledger system. In step 970, Providers, Subscribers, Beneficiaries, and Transaction Master and Assurance Element terms, conditions, and ratings will be monitored and notifications sent to appropriate parties. In step 975, feedback can be provided regarding transaction, Transaction Masters, Assurance Elements, and parties to a transaction.

[0176] The flow-diagram described in FIGS. 9A and 9B allows a Subscriber to access data located in a server and stored in one or more databases in order to update, access, research, verify, and/or modify information, as performed by the Subscriber. In the embodiments, Subscribers may access other assurance management services offered by the present invention service. To wit, a Subscriber may have access to user-defined analytic tools for data analysis to complement the ratings, rankings, and projections produced by the assurance management service server. Additional functions that may be available to the Subscriber include: automatically being notified of Transaction Master amendments, track ratings against user-defined parameters, and asynchronously or interactively share feedback and messages regarding Providers, Subscribers, Beneficiaries, or events which may impact the performance or ratings of a Transaction Master, Assurance Element, or associated parties.

[0177] Referring now to FIG. 10, therein depicted is a Transaction Master's statement information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1000 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and item description and Transaction Master Assurance Element attributes 1010, statement of assurance terms, acceptance options, rules and conditions 1020, events and times of notifications 1030, methods of transmission and communication 1040 data in the form of system information and correspondingly printed on screen 1000 to indicate the guidelines of operation to be carried out or executed by assurance management server 170. Screen 1000 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0178] Referring to FIG. 11 therein illustrates an assurance management flow-diagram in accordance with the embodiments of the present specification. The method 1100 includes the following steps. In step 1110, a Provider creates a Transaction Master describing one or more of statements, items, Assurance Elements, and other declaratory information. In step 1120, the Provider may use one or more means of making the Transaction Master Assurance Element statement available for exhibition or delivery. In step 1130, the Transaction Master statement is transmitted to or entered by one or more Subscriber.

[0179] The flow-diagram described in FIG. 11 allows a Provider or Subscriber to access data located in a server and stored in one or more databases in order to create, update, access, receive, research, verify, or modify information, as performed by the Provider or Subscriber. Additional functions that may be available to the Provider and Subscriber include: automatically being notified of Transaction Master amendments, track ratings against user-defined parameters, and asynchronously or interactively sharing feedback and messages regarding the one or more Provider and Subscriber, or events which may impact the performance, fidelity, or ratings of a Transaction Master or associated parties.

[0180] Referring now to FIG. 12 therein illustrates an assurance management Transaction Master processing flow-diagram in accordance with the embodiments of the present specification. The method 1200 includes the following steps. In step 1210, a Subscriber receives or enters a Transaction Master describing one or more statements, items, Assurance Element, Assurance Policy, and other declaratory information. In step 1220, the Transaction Master is automatically entered or manually entered 1230 in Subscriber account. In step 1240, Transaction Master data is processed in accordance with the embodiments of the present specification. In step 1250, extraction of statement information data is processed in accordance with the embodiments of the present specification. In step 1260, statement information, processed data, extracted data, assignment(s), supplemental information, and the results of analysis are combined, tokenized, and stored in one or more databases of a storage device 190. In step 1270, statement information, processed data, extracted data, combinations, assignment(s), supplemental information, and the results of analysis are monitored. In step 1280, process notifications are transmitted to appropriate parties.

[0181] The flow-diagram described in FIG. 12 allows a Subscriber to access data located in a server and stored in one or more databases in order to create, update, access, receive, research, verify, or modify information, as performed by the Subscriber. Additional functions may be available to the Subscriber in accordance with the embodiments of the present specification.

[0182] Referring to FIG. 13, therein depicted is a Transaction Master and Provider analysis of assurance account information illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1300 resembles a typical computer system screen display as a representation of details including, without limitation, personal information, item description and Transaction Master assurance terms and attributes 1310, constructed analysis results of rankings, ratings, and projections 1320, and comments and feedback 1330 data in the form of system information and correspondingly printed on screen 1300 to indicate the factors as executed and produced by assurance management server 170. Screen 1300 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0183] Referring now to FIG. 14, therein depicted is Subscriber rating and feedback account information record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1400 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and item description and Transaction Master attributes 1410, statement of assurance terms, acceptance options, rules and conditions 1420, events and times of notifications 1430, feedback and performance elements 1440 data in the form of system information and correspondingly printed on screen 1400 to indicate the utility and performance of a Provider and Transaction Master and Assurance Element. Screen 1400 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0184] Referring to FIG. 15 therein illustrates an assurance management rating and feedback flow-diagram in accordance with the embodiments of the present specification. The method 1500 includes the following steps. In step 1510, a Subscriber selects a Transaction Master describing statements, items, Assurance Element, assurance terms, and other declaratory information. In step 1520, the Subscriber enters utility and performance ratings and feedback for a Provider and Transaction Master Assurance Element. In step 1530, the ratings and feedback information is processed and integrated with information of the Provider and Transaction Master. In step 1540, ratings and feedback information, updated accounts, and statistical data are stored in one or more databases of a storage device.

[0185] The flow-diagram described in FIG. 15 allows a Subscriber to access data located in a server and stored in one or more databases in order to create, update, access, receive, research, verify, or modify information, as performed by the Subscriber. Additional functions that may be available to the Subscriber include: automatically being notified of Transaction Master amendments and updates, tracking ratings against user-defined parameters, and asynchronously or interactively sharing feedback and messages regarding Providers and Subscribers or events which may impact the performance or ratings of a Transaction Master or associated parties.

[0186] Referring now to FIG. 16, therein depicted is a Provider's rating and feedback information account record illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1600 resembles a typical computer system screen display as a representation of details including, without limitation, personal information and item description and Transaction Master attributes 1610, statement of assurance terms, Assurance Element, acceptance options, rules and conditions 1620, events and times of notifications 1630, feedback and performance elements 1640 data in the form of system information and correspondingly printed on screen 1600 to indicate the utility and performance of a Subscriber and Transaction Master and Assurance Element. Screen 1600 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0187] Referring to FIG. 17 therein illustrates an assurance management rating and feedback flow-diagram in accordance with the embodiments of the present specification. The method 1700 includes the following steps. In step 1710, a Provider selects a Transaction Master Assurance Element describing statements, items, assurance terms, and other declaratory information. In step 1720, the Provider enters utility and performance ratings and feedback of a Subscriber and Transaction Master. In step 1730, the ratings and feedback information is processed and integrated with information of the Subscriber and Transaction Master. In step 1740, ratings and feedback information, updated accounts, and statistical data are stored in one or more databases of a storage device.

[0188] The flow-diagram described in FIG. 17 allows a Provider to access data located in a server and stored in one or more databases in order to create, update, access, receive, research, verify, or modify information, as performed by the Provider. Additional functions that may be available to the Provider include: automatically being notified of Transaction Master amendments and updates, tracking ratings against user-defined parameters, and asynchronously or interactively sharing feedback and messages regarding Providers and Subscribers or events which may impact the performance or ratings of a Transaction Master or associated parties.

[0189] Referring now to FIG. 18, therein depicted is an Assurance Policy master listing of account record information illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1800 resembles a typical computer system screen display as a representation of details including, without limitation, Provider name, item description, and Assurance Element attributes 1810 in the form of system information and correspondingly printed on screen 1800 to list the available Assurance Policy. An Assurance Policy as displayed on screen 1800 may be selected by a Subscriber for display of further detailed information. Screen 1800 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170. Other forms of presentation (e.g., audio) are considered for use in all venues by the present invention.

[0190] Referring to FIG. 19, therein depicted is a rating and analysis listing of account record information illustrated as a database computer system screen entry and display according to the present invention. In particular, screen 1900 resembles a typical computer system screen display as a representation of details including, without limitation, account selection of Provider, Subscriber, Host, or Beneficiary with related personal information, ratings, and projections 1910, listing of corresponding category, descriptions, and Transaction Master or Assurance Element attributes 1920 data in the form of system information and printed on screen 1900 to indicate the account's stored analysis, ratings, reviews, and performance factors. A category or Transaction Master or Assurance Element as displayed on screen 1900 may be selected by a user for further display of detailed information. Screen 1900 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0191] Referring now to FIG. 20, therein depicted is universal Subscriber rating and feedback account record information illustrated as a database computer system screen entry and display according to the present invention. A Subscriber can search and select any available account, with or without a related Transaction Master assignment, to provide feedback and ratings depending on privacy and association settings. In particular, screen 2000 resembles a typical computer system screen display as a representation of details including, without limitation, personal information, rating, ranking, and projection factors 2010, feedback and performance elements 2020 data in the form of system information and correspondingly printed on screen 2000 to indicate utility and performance. Screen 2000 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

[0192] Referring to FIG. 21 therein illustrates an assurance management rating and feedback flow-diagram in accordance with the embodiments of the present specification. The method 2100 includes the following steps. In step 2110, a Subscriber selects a user account. In step 2120, the Subscriber enters utility and performance ratings and feedback for the selected user account. In step 2130, the ratings and feedback information is processed and integrated with existing information of the selected account. In step 2140, ratings and feedback information, updated account, and statistical data are stored in one or more databases of a storage device.

[0193] The flow-diagram described in FIG. 21 allows a Subscriber to access data located in a server and stored in one or more databases in order to create, update, access, receive, research, verify, or modify information, as performed by the Subscriber. Additional functions that may be available to the Subscriber include: asynchronously or interactively sharing feedback and messages regarding Subscribers or events which may impact the performance or ratings of a Transaction Master or associated parties.

[0194] Referring now to FIG. 22 therein illustrates an assurance management system conceptual arrangement of the components in the present specification. The stacked Venn diagram illustrates how the encompassed features of the present invention are organized in a hierarchical order. A Subscriber or Beneficiary can be involved with one or more Provider. A Provider can produce one or more Transaction Master. A Transaction Master can include one or more Transaction Supplement. A Transaction Master or Transaction Supplement can include one or more Assurance Element. An Assurance Element can include one or more Assurance Policy and other details as conveyed by a Provider or Transaction Supplement, whether in isolation or combination of assurance terms. Variations of the arrangement are considered and evolving revisions may be performed by one skilled in the art of computer programming and database management systems.

[0195] Referring to FIG. 23 therein illustrates an example of a product purchase flow-diagram as gift with integrated, combined, and extended assurance policies in accordance with the embodiments of the present specification. The method 2300 includes the following steps. In step 2310, a Subscriber proceeds to a HomeDepot store on 1 Jan. 2021 to purchase a Sawzall saw as a gift. In step 2320, the Subscriber buys a Milwaukee Sawzall saw at Home Depot paying with a MasterCard credit card. Home Depot provides a merchandise policy of a refund or exchange within 90 days from purchase date. In step 2330, the Milwaukee Sawzall saw manufacturer provides an assurance policy of free repairs for 2 years from the date of purchase. In step 2340, MasterCard provides an extension of a manufacturer warranty for up to 24 months matching the manufacturer warranty. In step 2350, a Milwaukee rebate is identified and processed for remittance. In step 2360, the system analyzes, determines combinable terms and options, then processes and transforms the combinable features and attributes into a newly formed and consolidated tokenized assurance chain structure as depicted in 2370. The token is recorded in the Subscriber's account and the Beneficiary appropriately notified. The state of transformation is novel since there is a conversion from one state of individual assurance elements to a newly formed tokenized structure of integrated holistic benefits. Just as different chemicals when combined create a new compound, so too does this present invention combine different term elements to create a new assurance structure.

[0196] The example of FIG. 23 displays the advancement, integration, and combination of dates while no such limitation of the present invention should be inferred. Any of features or attributes that may add, extend, encourage, or complement the one or more assurance terms, as may be offered by one or more Provider, are encompassed by the present invention. As example and not limitation, the use of various integration features and attributes, as well as dates, include advancement, integration, combination, complement, and extension options such as: added mileage allowance of a leased automobile; extended minutes awarded for game play; supplementary gigabytes of download allowance; bonus cloud-based storage capacity; extra transmission speed for data transfers; increased movie channel options; increased discount percentage rate; additional rebate amount; adjusted seating classification, such as advancing from coach to first class; extra paper clips; loyalty points; square-feet of storage space; awarding pounds of grass seed; or, adding size, color, or flavor to an object.

[0197] As further example, diverse product assurance metrics can be integrated with the present invention. Resperate.com offers a product to reduce a person's blood pressure. If blood pressure (i.e., the conditional assurance metric) is not reduced in 60 days, a consumer can get a full refund. The product also comes with a one year warranty. If a consumer pays for the product with a MasterCard credit card, then MasterCard will extend the manufacture warranty for one year. The present invention will coordinate and combine the conditional 60 day refund, one year manufacturer warranty, and one year MasterCard warranty to produce a combined assurance structure. Should this product be purchased as a gift, then the Beneficiary will be appended to the newly formed assurance structure for complete tracking and performance. It is evident that FIG. 23 could be recast as providing an assurance structure with the Resperate.com product and an activation condition of lowered blood pressure as an Oracle trigger. Monitoring data could be received by, as example, an IoT or Apple Watch sensor. There is no prior art that aligns such diverse metrics (i.e., blood pressure) with refunds or other actions.

[0198] The present invention identifies and distinguishes all assurance policy terms and supplements, and then aligns them with the appropriate combination of relatable assurance factors and features (e.g., points, power cycles, dates, classifications, discounts). When an action is required to claim an assurance term (e.g., refund of payment, monetary claim for damage), then the present invention will produce credentials as required indicating the combined assurance structure and elements.

[0199] Referring to FIG. 24 therein depicted, as example, is one of many alternative assurance structure depictions for the one or more assurance metric. In particular, screen 2400 resembles a typical computer system screen display as a representation of Transaction Master logical and illustrative details including, without limitation, transaction and item information 2410, assurance options 2420 for Time metric, assurance options 2430 for Power-On Cycles metric, and action links. This example shows the variable indicators 2440 of Time and Power-On Cycles. There is an indication 2440 of who can make claim to which assurance element and from whom in accordance with the present invention. The system arranges and manages one or more metrics as prescribed by Assurance Providers. Additional metrics would likewise display to accommodate assurance specifications. Screen 2400 is a visual display form that is generated in a conventional way by or on behalf of assurance management server 170.

Use Cases

Promise—Will Sell by

[0200] As example and not limitation of an invention embodiment is a promise made between two people, such as a real estate broker and a house seller.

[0201] After a Monday lunch date, Alpha tells Baker “I'll sell your house by Friday for an 8% commission, or thereafter for a 3% commission.” Baker, wanting a fast sale, asks Alpha to enter the promise information into the present invention, or Baker may choose to enter such promise information with Alpha authentication (e.g., encryption code). By using analysis that integrates internal and external historical and current data sources, the present invention determines factors such as, without limitation, that such promises have a category rating of 72% failure rate, an 8% “sold within promised by date” success rate, and a 20% “sold after promised by date” delayed rate.

[0202] The present invention also may use internal and external historical and current data sources to calculate and produce a trustworthy factor of Alpha indicating that 92% of promises made by this person are fulfilled, 6% of promises are fulfilled late, and 2% or promises are unfulfilled. The present invention also may produce success projection rates indicating that on Monday there is a 97% probability Alpha will sell the house, by Tuesday it may be 82% getting a buyer, by Wednesday it may be 58% getting a buyer, by Thursday it may be 26%, and by Friday it may be 4%, with Saturday, the day after the “promised by date”, being 11% since Alpha has a 20% “sold after promised by date” probability ranking. Reference FIG. 13 as illustration of such factors.

[0203] Specific items that are extracted from promise information and submitted for processing would include, without limitation: date of assurance (e.g., when was a promise made); assurance item product, service, or action; item assurance terms, as appropriate; effective time periods; Host, as may be involved; settlement or acceptance method; party authentication; transmission method of Transaction Master; and, Provider and Subscriber identification.

[0204] Based on promise information entered, specific results of data processing would produce as appropriate, and without limitation, analysis factors of: current assurance item probability of success, failure, or delayed action (e.g., will a promise be fulfilled); Provider reliability factor for issuing and fulfilling assurances; projected assurance item probability of success, failure, or delayed action; and, integrated quality rating of Provider and Assurance Element.

[0205] A component of the present invention would allow Baker to provide feedback on Alpha as to when, or if, they sold the house. Alpha also would have an option to provide feedback on Baker as to whether they accepted a sale, declined a sale, and delayed a sale, among other actions or activities.

[0206] The present invention service will process and extract data from the promise information and create a data record of the communication and execute ratings, rankings, projections, and operational assignments in various storage systems as described in this specification. The communication information of the promise will be analyzed and transformed into ratings, rankings, and projections that will assist in the determination and development of planned and contingency actions by Subscriber.

[0207] The processing of communication information results in outputs that produce ratings, rankings, and projections that also may be used to establish trigger points for action.

[0208] A trigger point may include, without limitation, statistical probability levels which are used as a basis for action notifications. For example, an insurance policy expiration date could be processed into a statistical probability level indicating that a Subscriber should be notified of the expiration starting 8 days before the expiration date since that would be sufficient time to submit and have processed a policy renewal application, introduce amendments, or find a new Provider.

[0209] As another example, a washing machine warranty expiration date may be processed into a statistical probability level that triggers a notification to a Subscriber at 23 days before the warranty expiration date since that would be sufficient time to examine the washing machine for possible defects and request warranty-covered repairs. This transformation of information to proactive projection delivers something significantly beneficial to a Subscriber by revealing ratings, rankings, patterns, trends, and action features that increases the utility of Assurance Elements.

[0210] The processed trigger points could be used with internal, external, computed, or Subscriber-stated comparison factors such that when a processed trigger point was matched to a comparison factor the present invention system will generate and transmit a notification to appropriate parties or engage pre-programmed instructions.

Insurance Policy—Smart Contract

[0211] An example, and not as limitation, of another invention embodiment is the application of an insurance contract as a “smart” contract. In this situation, an insurance policy issuer serves as Provider, a consumer serves as both Subscriber and Beneficiary.

[0212] A Provider creates a Transaction Master for an insurance policy that covers damage to an automobile. The Transaction Master designates the Subscriber as the assigned Beneficiary along with the grant of, among other assurances, a commitment assurance term to pay for repairs if the automobile is damaged. Settlement terms require a premium payment on the first of each month. The Subscriber agrees to and accepts the Transaction Master. The Transaction Master is transmitted to the present invention service which extracts and processes data from the transaction information and creates an assurance structure record as described in this specification.

[0213] The insurance policy Transaction Master is entered as a smart contract into one or more distributed-ledger system for monitoring, compliance, and actions. The distributed-ledger system includes an Oracle trigger which monitors for compliance of payment submission to the policy issuer. It is possible for preprogrammed Oracle instructions to be included that automatically makes payment prior to a default date, or notifies the Subscriber of an upcoming payment due. In the event of a Subscriber making a manual payment, if the Oracle trigger determines on the second day of a month that a manual payment has not been made, then programmed smart contract instructions that were entered into the distributed-ledger system would notify the Subscriber of the default or perform other programmed actions. The operations, processing, and logic of said smart contract provisions will be readily apparent to those skilled in the art of computer programming, distributed-ledger technologies, and database management systems.

Product

[0214] An example, and not as limitation, of another invention embodiment is a product purchase. In this situation, a merchant serves as Host, a manufacturer serves as Provider (i.e., Transaction Supplement, Assurance Element), a re-assignable generic Beneficiary placeholder of “Buyer” serves as a pre-designated re-assignable Beneficiary, and a consumer serves as Subscriber. A Host creates a Transaction Master for a product (e.g., Walmart offering a microwave oven) for general distribution in the marketplace. The merchant offers a refund and exchange policy with the Transaction Master. The Transaction Master includes an assurance warranty statement indicating a pre-designated re-assignable Beneficiary (e.g., the Buyer).

[0215] The product, with Transaction Master, is exhibited to the public using, as example, the merchant Walmart as Host for display of the product in the merchant's establishment or website. Subscribers review the product and Transaction Master, and if agreed to, will accept the product and the Transaction Master in a settlement action. As assistance in a purchase, a Subscriber will have available the ratings of the Provider, Host, and, based on available information, the microwave oven product (i.e., Assurance Element) ratings.

[0216] At any time during the transaction process when the Host has exhibited the product and Transaction Master, either the Host, or a Subscriber considering the product and Transaction Master, may assign one or more Beneficiary to the Transaction Master as amendment, or as a right of making a Beneficiary designation (e.g., a gift purchase). A Subscriber that accepts the Transaction Master may assign all or part of the Transaction Master Assurance Element to one or more Beneficiary.

[0217] The present invention system and methods will execute a series of processes on the Transaction Master. Using an example of time periods, the Transaction Master will be parsed to identify the primary Provider (e.g., the Host) and determine any time periods related to an Assurance Policy (e.g., refund or exchange within 90 days). Further warranty options beyond time periods may include, as example and not limitation, power cycles, torque load, and environmental conditions as a sample of issues that may be conditional assurance topics.

[0218] To continue, the system will identify the Assurance Element (i.e., the microwave oven) for any related Assurance Policy (e.g., free repairs for 2 years). The system will continue to identify any Transaction Supplements (e.g., payment by MasterCard) and determine any related Assurance Policy related to the Assurance Element (i.e., microwave oven) and combine in chain-fashion any extension of benefits (e.g., manufacturer warranty time period extended by MasterCard up to 2 years). Processing continues to evaluate any further Transaction Supplements in a similar manner for warranty terms that may be applied or combined. The present invention will incorporate all such related benefits for the Assurance Element into a holistic assurance structure. All related components of the Transaction Master will be compiled according to this specification's processing system and appropriately tokenized and stored.

[0219] In the event of a defective product, a Subscriber or Beneficiary will be availed of the Transaction Master assurance terms as assigned. In this instance, the Subscriber or Beneficiary would be able to claim, as example, a refund, the exchange of product, a manufacturer warranty of service to repair or replace the product, or such other advantages as bestowed on the Subscriber or Beneficiary by the Transaction Master.

[0220] The present invention service will extract, process, and combine data from the transaction information and create a data record of the transaction and perform operational ratings, rankings, projections, assignments, and tokenization in various storage systems as described in this specification.

PLEDGES AND STATEMENTS

[0221] An example, and not as limitation, of another invention embodiment is in the application of services related to a statement of undertaking or event occurrence. To wit, a created and presented Provider Transaction Master of a statement claiming “The sky is falling” (Sky) with an assurance benefit of the Provider paying $50 if the sky does fall and having a Subscriber pay the Provider $20 if the sky does not fall. In this example, a Provider creates and exhibits the Sky Transaction Master including a time period and other conditions for the occurrence of such event. When an interested one or more Subscriber chooses to accept and acquire the Sky Transaction Master, the Subscriber then settles and enters the Sky Transaction Master into their account and becomes an assigned Beneficiary with the Provider advised and linked to the Subscriber/Beneficiary account.

[0222] The Sky Transaction Master will be monitored as to the occurrence of the Sky falling event. One or more Beneficiaries will be availed of the ability, as provided by the present invention, to provide feedback on the accuracy, veracity, occurrence, and adherence to the Sky Transaction Master. A Provider may connect in order to provide feedback to any Subscriber account. Such a Sky Transaction Master example may be expanded to include instances of, for example, communications of politicians and their campaign pledges.

[0223] Should the Sky falling event occur, then the Provider will remit a $50 payment to a Subscriber/Beneficiary. If it does not occur, then the Subscriber/Beneficiary will remit a $20 payment to the Provider. The present invention integrates distributed ledger blockchain technology and, as such technology allows, provides a digital wallet that offers storage and processing of items encompassing, without limitation, currencies, objects, attributes and such components and features as accepted by a distributed ledger system.

[0224] The present invention service will extract, process, and combine data from the transaction information and create a data record of the transaction and perform operational ratings, rankings, projections, assignments, and tokenization in various storage systems as described in this specification.