Method and apparatus for aligning interactions of users in a green technology project

Abstract

A computer system for controlling exchange of data between users sharing data of a green technology project on a digital platform may include a platform device, which may store profiles of the users in a platform structure that may include layers to which the user profiles may be assigned depending on a user type. The platform device may be configured to receive project data, project criteria and basic criteria of a user having a user profile assigned to a first layer from a first terminal device, transmit the received project criteria to terminal devices, receive, from a second terminal device, a request of another user to access the project data and permit said user to access the project data if a set of project criteria and basic criteria of said user match with a set of project criteria and basic criteria of the user assigned to the first layer.

Claims

1. A computer system for controlling the exchange of data between different users of a project sharing data on a digital platform, the computer system comprising a plurality of terminal devices (6a, 6b, 6c) connected to at least one system server (1) configured to receive input data from a user and to display output data to the user, the system server (1) including a plurality of databases (3, 4, 5) comprising at least one project database (5) configured to store project data of a plurality of projects, at least one project criteria database (4) configured to store project criteria of a plurality of users, at least one basic criteria database (5) configured to store basic criteria of the plurality of users, and a platform device (2) connected to the plurality of databases (3, 4, 5) storing profiles of users in a platform structure (21), the platform structure (21) including different layers (21-1, 21-2, 21-n) which are arranged in hierarchical order from a top layer to a bottom layer, wherein the user profiles are assigned to the different layers (21-1, 21-2, 21-n) depending on a type of a user, and user profiles representing the project are assigned to a first layer (21-1, 21-2, 21-n) of the platform structure (21), the platform device (2) configured to receive project data, project criteria and basic criteria of a user assigned to the first layer (21-1, 21-2, 21-n) from a first terminal device (6a, 6b, 6c), transmit the received project criteria to the plurality of terminal devices (6a, 6b, 6c), receive, from a second terminal device (6a, 6b, 6c), in response to the transmitted project criteria, a request of a user having a user profile assigned to a second layer (21-1, 21-2, 21-n) of the platform structure (21) to access the project data, wherein the request includes at least one set of project criteria and at least one set of basic criteria of the user, compare the received sets of basic criteria and project criteria of the user assigned to the second layer (21-1, 21-2, 21-3) with the project criteria and the basic criteria of the user assigned to the first layer (21-1, 21-2, 21-n), permit the user of the second layer (21-1, 21-2, 21-n) to access the project data if the set of project criteria and the set of basic criteria of the user assigned to the second layer (21-1, 21-2, 21-n) match with a set of project criteria and a set of basic criteria of the user assigned to the first layer (21-1, 21-2, 21-n).

2. The computer system according to claim 1, wherein a set of project criteria includes a first predetermined number of user requirements directed to a project, and a set of basic criteria includes a first predetermined number of project requirements directed to a user.

3. The computer system according to claim 1, wherein each time a request to access the project data of a user having a user profile assigned to a second layer (21-1, 21-2, 21-n) is received by the platform device (2), the platform device (2) is configured to store project criteria included in the request in the project criteria database (4) and basic criteria included in the request in the basic criteria database (5).

4. The computer system according to claim 1, wherein the platform device (2) is configured to compare a set of project criteria of a user assigned to the top layer (21-1) of the platform structure (21) with sets of project criteria of users assigned to one or more subsequent lower layers (21-2, 21-n), and if a match is found between the set of project criteria of the user assigned to the top layer (21-1) and a set of project criteria of a user assigned to the one or more subsequent lower layers (21-2, 21-n), compare the set of project criteria of the user assigned to the one or more subsequent lower layers (21-2, 21-n) with sets of user criteria of users assigned to one or more further subsequent lower layers (21-2, 21-n) until the bottom layer is reached, and compare a set of basic criteria of a user assigned to the bottom layer (21-n) with sets of basic criteria of users assigned to one or more subsequent upper layers (21-1, 21-2), and if a match is found between the set of basic criteria of the user assigned to the bottom layer (21-n) and a set of basic criteria of a user assigned to the one or more subsequent upper layers (21-1, 21-2), compare the set of basic criteria of the user assigned to the one or more subsequent upper layers (21-1, 21-2) with sets of basic criteria of users assigned to one or more further subsequent upper layers (21-1, 21-2) until the top layer is reached, and if users matching the project criteria are equal to users matching the basic criteria, permit access to the project data for said users.

5. The computer system according to claim 2, wherein the platform device (2) is configured to determine a match of two sets of project criteria if a second predetermined number of user requirements of both sets are equal, wherein the second predetermined number of user requirements is less or equal to the first predetermined number of user requirements.

6. The computer system according to claim 2, wherein the platform device (2) is configured to determine a match of two sets of basic criteria if a second predetermined number of project requirements of both sets are equal, wherein the second predetermined number of project requirements is less or equal to the first predetermined number of project requirements.

7. The computer system according to claim 1, wherein the platform device (2) is configured to determine a match between two sets of project criteria if a value of a third predetermined number of the user requirements included in the two sets of project criteria corresponds in a predetermined range.

8. The computer system according to claim 1, wherein the platform device (2) is configured to determine a match between two sets of basic criteria if a value of a third predetermined number of the project requirements included in the two sets of project criteria corresponds in a predetermined range.

9. The computer system according to claim 1, wherein the platform device (2) is configured to store a plurality of sets of project criteria of each user in the project criteria database (4) and a plurality of sets of basic criteria of each user in the basic criteria database (5), arrange the sets of project criteria and basic criteria in the respective database in different layers (4-1-4-n, 5-1-5-n) depending on the type of the user in hierarchical order from a top layer to a bottom layer according to the platform structure (21).

10. The computer system according to claim 1, wherein the platform device (2) is configured to store a plurality of sets of project data of each project in the project database (3), arrange the sets of project data in the project database in different layers (3-1, 3-2, 3-n) according to the type of users requesting access to the project data in hierarchical order from a top layer to a bottom layer according to the platform structure (21).

11. The computer system according to claim 1, wherein the platform device (2) is configured to transmit at least one predetermined set of project data to a terminal device (6a, 6b, 6c) of a user when access to the project data is permitted, wherein the predetermined set of project data corresponds to the type of the user.

12. The computer system according to claim 11, wherein the platform device (2) is configured to transmit an updated set of the project data to the terminal device (6a, 6b, 6c) of the user when updated project data corresponding to the predetermined set of project data has been entered to the project database (3).

13. The computer system according to claim 1, wherein the system server (1) comprising the platform device (2) and the plurality of terminal devices (6a, 6b, 6c) are connected via a network (N) to a blockchain network (7) and wherein the data transmission between the platform device (2) and the terminal devices (6a, 6b, 6c) via the network (N) to the blockchain network (7) is encrypted.

14. The computer system according to claim 1, comprising: one or more computation units, and one or more data storage units, wherein the data storage units store one or more computer-program products which are configured to perform functions of the platform device (2).

15. A method for controlling the exchange of data between different users of a project sharing data on a digital platform, wherein a platform device (2) comprises a platform structure (21) including different layers (21-1, 21-2, 21-n) which are arranged in hierarchical order from a top layer to a bottom layer, wherein profiles of the users are assigned to the different layers (21-1, 21-2, 21-n) depending on a type of a user and user profiles representing the project are assigned to a first layer (21-1, 21-2, 21-n) of the platform structure (21), the method comprising the following steps: receiving project data, project criteria and basic criteria of a user having a user profile assigned to the first layer (21-1, 21-2, 21-n) from a first terminal device (6a, 6b, 6c), transmitting the received project criteria to a plurality of terminal devices (6a, 6b, 6c), receiving, from a second terminal device (6a, 6b, 6c), in response to the transmitted project criteria, a request of a user having a user profile assigned to a second layer (21-1, 21-2, 21-n) of the profile structure (21) to access the project data, wherein the request includes a set of project criteria and a set of basic criteria of the user, comparing the received sets of basic criteria and project criteria of the user assigned to the second layer (21-1, 21-2, 21-n) with the project criteria and the basic criteria of the user assigned to the first layer (21-1, 21-2, 21-n), permitting the user assigned to the second layer (21-1, 21-2, 21-n) to access the project data if the set of project criteria and the set of basic criteria of the user assigned to the second layer (21-1, 21-2, 21-n) match with a set of project criteria and a set of basic criteria of the user assigned to the first layer (21-1, 21-2, 21-n).

16. The method according to claim 15, comprising the further steps: comparing a set of project criteria of a user assigned to the top layer (21-1) with sets of project criteria of users assigned to one or more subsequent lower layers (21-2, 21-n), and if a match is found between the set of project criteria of the user assigned to the top layer (21-1) and a set of project criteria of a user assigned to the one or more subsequent lower layers (21-2, 21-n), comparing the set of project criteria of the user assigned to the one or more subsequent lower layers (21-2, 21-n) with sets of user criteria of users assigned to one or more further subsequent lower layers (21-2, 21-n) until the bottom layer is reached, and comparing a set of basic criteria of a user assigned to the bottom layer (21-n) with sets of basic criteria of users assigned to one or more subsequent upper layers (21-1, 21-2), and if a match is found between the set of basic criteria of the user assigned to the bottom layer (21-n) and a set of basic criteria of a user assigned to the one or more subsequent upper layers (21-1, 21-2), comparing the set of basic criteria of the user assigned to the one or more subsequent upper layers (21-1, 21-2) with sets of basic criteria of users assigned to one or more further subsequent upper layers (21-1, 21-2) until the top layer (21-1) is reached, and if users matching the project criteria are equal to users matching the basic criteria, permit access to the project data for said users.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0058] FIG. 1 shows schematically an overview of a digital platform in which the computer system described herein may be implemented.

[0059] FIG. 2 shows schematically the components of the computer system.

[0060] FIG. 3 shows schematically the exchange of information between users assigned to different layers of the project structure included in the platform device.

[0061] FIG. 4 shows schematically the platform structure with regard to the matching of the project criteria.

[0062] FIG. 5 shows schematically the platform structure with regard to the matching of the basic criteria.

[0063] FIG. 6 shows schematically the platform structure with regard to the provision of access to the project data.

[0064] FIG. 7 shows an example of sharing project information between different users according to the herein described subject matter.

DETAILED DESCRIPTION OF EXEMPLARY ASPECTS

[0065] In the following, preferred aspects and examples will be described in more detail with reference to the accompanying figures. Same or similar features in different drawings and examples are referred to by similar reference numerals. It is to be understood that the detailed description below relating to various preferred aspects and preferred examples are not to be meant as limiting the scope of the present disclosure.

[0066] FIG. 1 shows schematically an overview (“big picture”) of the interactions between different users of a digital platform in which the computer system described herein may be implemented. The following describes numbered items 1a through 11 and A through C, which represent interactions among various stakeholders in a green technology project where matching of requirements is needed. At first (1a), in case of a new project, an issuer of a green loan or bond may have an idea of the desired project. In a next step (1b′), the issuer may consider projects based on city or site level systemic change advisory. If an existing project matches the expectations of the issuer (matching between 1a and 1b), historical data of an existing project, which may be based on existing assets, may be received, and analyzed by a service provider (item 1c). As a result, a project proposal may be presented to the issuer (item 1d) and alignment between the issuer's demands and the offered proposal has to be achieved (matching between 1c and 1d).

[0067] In case a matching is achieved (item 2), the issuer may submit to the digital platform the project details (“Proposal”) based on the actions carried out at items 1a or 1d. Framework means including a description of the organisational strategy and the reasoning to select the project may highlight its contribution to achieve the transition goals.

[0068] At item 3, the data exchange according to the present invention may be started. The project may be made visible to the investor or lender to consider getting in touch with the issuer and begin negotiations. The issuer may get contacts from one or multiple investors or lenders interested in the project.

[0069] Outside the digital platform the lending agreement may take place, which may include a so called “Promise” regarding the use of proceeds and the outcome in terms of environmental and/or social impact in exchange of better terms. Loan/bond contract may need some level of innovation to include a new clause (item 4). Furthermore, the money transaction may take place outside the digital platform (item 5).

[0070] In a next step (item 6), use of proceeds may be allocated to the necessary internal and external parties to implement the project. Subsequently, project implementation may be carried out (item 7). Depending on the type and scale of the project, this step may take time.

[0071] After project implementation, the project may start to generate operational data of the green facilities, which may be monitored by Internet of Things (IoT) devices and communicated as project data to the digital platform (item 8). Furthermore, by using blockchain, the project data may be securely stored and converted into Key Performance Indicators (KPI) (item 9). The type and complexity of the KPI may depend on the project. Based on the knowledge of the system provider KPIs and their standardisation may be implemented. The KPIs and monitored data may become visible to the investor or lender corresponding to the evidence of the issuer's compliance to the promise (“Delivery”) (item 10). As a result, the investor or lender may provide better terms e.g. lower interest rate as the “Delivery” of their promise (item 11).

[0072] The items A to C are related to projects in which no IoT is included, such as projects related to human rights, money laundering, ESG rating and the like. At item A, a service matching from the digital platform to a third-party auditor/reviewer/certifier may take place. In a next step (item B), similar evidence as in item 10 can be used to show to insurers the increased greening of a site e.g., a building potentially resulting in benefits such as lower insurance fees. The insurer can offer a new derivative type of insurance related to the risk exposure of item 11. For example, if the weather is bad, the expected solar energy generation is lower resulting in not “Delivering” the “Promise” potentially causing a penalty. This consideration is quite early stage. Based on the evidence, the insurer may provide benefits such as lower insurance fees (item C).

[0073] FIG. 2 shows schematically the components of the computer system described herein which may be part of the digital platform described above. For example, the computer system may comprise a system server 1 which may include a plurality of databases 3, 4, 5 and a platform device 2 exchanging data with the plurality of databases 3, 4, 5. The plurality of databases 3, 4, 5 may comprise a project database 3, a project criteria database 4 and a basic criteria database 5. It may also possible that the databases 3, 4, 5 are located on remote individual servers and in this case be connected to the system server 1 via a network (not depicted). The platform device 1 may be at least one hardware device or may be a software-based program product which may be stored in one or more data storage units (not depicted). A platform structure 21 may be integrated into the platform device 2, e.g., by software, which may comprise a plurality of layers 21-1, 21-2, 21-n. The layers 21-1, 21-2, 21-n may be arranged in hierarchical order from a top layer 21-1 to a bottom layer 21-n, wherein user profiles of different users of the digital platform may be assigned to the different layers 21-1, 21-2, 21-n depending on the type of user. For example, user profiles of project owners may be assigned to the bottom layer 21-n, user profiles of investors or lenders may be assigned to the top layer, and user profiles of other project supporters, such as external reviewers and project developers may be assigned to the layers in between.

[0074] Each of the databases 3, 4, 5 may include a data storage structure corresponding to the platform structure 21. The project database 3 may comprise the layers 3-1 to 3-n for storing entire project data of various projects as well as individual project data sets transmitted to the users after matching the respective project and basic criteria. For example, the project data of each project may be stored in the bottom layer 3-n, wherein individual sets of project data transmitted to different project supporters after matching may be stored in the upper layers 3-1, 3-2. Instead of storing complete project data sets in the upper layers, it may also be possible that the upper layers include only access data sets pointing to the respective set of project data stored in the bottom layer.

[0075] The project criteria database 4 may comprise the layers 4-1 to 4-n for storing project criteria of the different types of user. For example, the project criteria of the project owners may be stored in the bottom layer 4-n, the project criteria of the investors or lenders may be stored in the top layer 4-1, and the project criteria of the other project supporters, such as external reviewers and project developers, may be stored in the in the layers 4-1, 4-2, 4-n in between.

[0076] Accordingly, the basic criteria database 5 may comprise the layers 5-1 to 5-n for storing basic criteria of the different types of user. For example, the basic criteria of the project owners may be stored in the bottom layer 5-n, the basic criteria of the investors or lenders may be stored in the top layer 5-1, and the basic criteria of the other project supporters, such as external reviewers and project developers, may be stored in the in the layers 5-1, 5-2, 5-n in between.

[0077] The system server 1 may be connected to a plurality of terminal devices 6a, 6b, 6c which may be configured to receive input data from a user and to transmit output data to a user. The terminal devices 6a, 6b, 6c may be mobile devices, such as smartphones or tablet computers, or any other type of computer connectable to the system server. It may also be possible that the terminal devices 6a, 6b, 6c may be IoT devices monitoring operational data of the green facilities and providing said operational data to the system server 1.

[0078] In the example depicted in FIG. 2, the terminal devices 6a, 6b, 6c exchange data with the platform device 2 of the system server 1 via a single or multiple networks N, preferably the internet. In order to increase data security, the communication between the terminal devices and the system server may preferably be end-to-end encrypted and a verification for log in to the system server 1 may be required. Thus, the system server 1 may be connected to a blockchain network 7, in which the project data, such as the KPIs of the green facilities, as well as project and basis criteria and any other relevant data of the project may be stored.

[0079] FIG. 3 shows schematically the data exchange between users assigned to different layers included in the project structure of the platform device. On the right side the top-down matching of project criteria starting from users assigned to the top layer (layer 1) to users assigned to the bottom layer (layer N) and the bottom up matching of basic criteria starting from users assigned to the bottom layer (layer N) to users assigned to the top layer is shown. As a result, users who meet both criteria are allowed access to the project data and the project information is made available to the respective users. For example, user profiles of project owners may be assigned to the bottom layer (layer N), user profiles of investors or lenders may be assigned to the top layer (layer 1), and user profiles of other project supporters, such as external reviewers and project developers may be assigned to the layers in between (layer 2 to layer N−1).

[0080] On the left side the data exchange between users of different layers is described in the depicted arrows. Arrows pointing away from a layer include information which are sent by a user of that layer and arrows pointing to the layer include information received by said user.

[0081] The flow of interactions among users of different layers can begin from the top layer (layer 1) or the bottom layer (layer N). For example, a new top layer user such as a new investor or lender may send a criteria set and a request information to a project owner (“to downstream”) and the project owner may provide updated information access settings “from downstream” if the project and basic criteria provided in the criteria set of the investor match his expectations. After the top and bottom layers begin the flow of interactions, intermediate layers can begin interacting.

[0082] On the other hand, for example, a project owner assigned to layer N may provide information to the project database and may send a criteria set “to upstream”, which means the project owner may provide project criteria to all users assigned to the upper layers. In response to the transmitted project criteria, the project owner may receive a criteria set and a request for information from one or more users assigned to an upper layer (“from upstream”) and may update the information access settings of users assigned to upper layers (“to upstream”) if they match the project criteria and the basic criteria.

[0083] The described data exchange may also be carried out between users of upper layers. For example, a new intermediate layer user such as a new external reviewer or a new project developer (e.g., assigned to layer 2 and layer N−1) may provide project information to the project database, send a criteria set “to upstream” and receive a request for information “from upstream”. At the same time, the intermediate layer user may send a criteria set and a request for information “to downstream” for getting access to project data of users assigned to lower layers.

[0084] The types of data in each database may include proprietary or public data, dynamic data, static data, qualitative data, quantitative data, and the like. Furthermore, e.g., users in upper layers can carry out project aggregation from users in lower layers. For example, aggregating various single projects into a bundle of projects that can be structured into a green bond for investors. Investors may expect a large sized financial instrument, but single projects might be too small. By aggregating multiple projects, the desired size by investors can be achieved. The number of necessary layers for interaction, depends on the project and the preferences of the users. In the following FIGS. 4 to 6, which show interactions between users of the platform structure in terms of matching project and basic criteria and providing information, cases are shown in which users of all layers are involved but also cases in which not all types of users are required to set up a project.

[0085] FIGS. 4 and 5 shows schematically the platform structure with regard to the matching of project and basic criteria. As obvious from these figures, there are multiple paths to achieve a connection between users assigned to different layers from the top layer to the bottom layer (“end-to-end connection”). For each path, the project and basic criteria of the various users, which may be stored in the project and basic criteria database, may be compared to match users of different types required to complete a green technology project. Based on both databases, for the matching and filtering purposes, ranking of users of upper and lower layers may be visible to prioritise the selection. In some cases, the end-to-end connection may not be achieved, which may represent projects that could not be funded because of misalignment between the different types of users assigned to the layers. For these cases, the respective users can make actions to fulfil missing expectation, reach alignment and ensure the end-to-end connection across layers. Recommendations about required or preferred data inputs to fulfil criteria for the users in each layer may be provided in the project and basic criteria databases resulting in dynamic guidance of the users based on dynamic criteria settings.

[0086] As a result of the filtering and matching of project and basic criteria, the path for sharing project information is shown in FIG. 6. The cases where there is end-to-end connection in the three databases are projects that have the highest possibilities of being financed and implemented as there is fulfilment of criteria and sharing of project information. The above results in access and visibility of project information if there is matching across users in project and basic criteria.

[0087] FIG. 7 shows an example of access to information by concrete users of the digital platform according to the herein described subject matter. The bold arrows and the content of the text fields above the arrows show the development of a project information database on the path from project owner to lender or investor. The matching of project and basic criteria described earlier can be applied at different levels of the project, namely between project owners/green bond issuers and project developers/underwriters to select a promising project from a pool of candidates, between project developers/underwriters and external reviewers to review projects from a pool of candidates that are already in progress, and between external reviewers and investors/lenders regarding investment-ready green bonds/loans. This allows for providing an effective and transparent data exchange throughout the entire process from project idea to completion.

[0088] Summarizing, the herein described subject matter provide a computer system and a method that enables users in a project to access information in an automated manner. The described standardized approach performed by the platform device allows investors to communicate expectations as well as targets and goals across different levels to ultimately reach project owners. At the same time, it enables project owners and users in lower layers to communicate expectations to upper layers. From the end-to-end matching across layers, steps, and users, emerges a mutual alignment achieving clarity and transparency, which results in lower cost of capital.

[0089] As will be appreciated by one of skill in the art, the present disclosure, as described hereinabove and the accompanying figures, may be embodied as a method (e.g., a computer-implemented process or any other process), apparatus (including a device, machine, system, computer program product, and/or any other apparatus), or a combination of the foregoing.

[0090] Aspects/Examples of the present disclosure may be a software entirely (including firmware, resident software, micro-code, etc.), or a combination of software and hardware aspects that may be referred to as a “system”. Furthermore, the present disclosure may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium.

[0091] It should be noted that arrows may be used in drawings to represent communication, transfer, or other activity involving two or more entities. Double-ended arrows generally indicate that activity may occur in both directions (e.g., a command/request in one direction with a corresponding reply back in the other direction, or peer-to-peer communications initiated by either entity), although in some situations, activity may not necessarily occur in both directions.

[0092] Single-ended arrows generally indicate activity exclusively or predominantly in one direction, although it should be noted that, in certain situations, such directional activity actually may involve activities in both directions (e.g., a message from a sender to a receiver and an acknowledgement back from the receiver to the sender, or establishment of a connection prior to a transfer and termination of the connection following the transfer). Thus, the type of arrow used in a particular drawing to represent a particular activity is exemplary and should not be seen as limiting.

[0093] The present disclosure may be described with reference to flowchart illustrations and/or block diagrams of methods and apparatuses, and with reference to a number of sample views of a graphical user interface generated by the methods and/or apparatuses. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, as well as the graphical user interface, can be implemented by computer-executable program code.

[0094] The computer-executable program code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the program code, which executes via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts/outputs specified in the flowchart, block diagram block or blocks, figures, and/or written description.

[0095] The computer-executable program code may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the program code stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act/output specified in the flowchart, block diagram block(s), figures, and/or written description.

[0096] The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the program code which executes on the computer or other programmable apparatus provides steps for implementing the functions/acts/outputs specified in the flowchart, block diagram block(s), figures, and/or written description. Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the disclosure.

[0097] It should be noted that terms such as “server” and “processor” may be used herein to describe devices that may be used in certain aspects of the present disclosure and should not be construed to limit the present disclosure to any particular device type unless the context otherwise requires. Thus, a device may include, without limitation, a bridge, router, bridge-router (brouter), switch, node, server, computer, appliance, or other type of device. Such devices typically include one or more network interfaces for communicating over a communication network and a processor (e.g., a microprocessor with memory and other peripherals and/or application-specific hardware) configured accordingly to perform device functions.

[0098] Communication networks generally may include public and/or private networks; may include local-area, wide-area, metropolitan-area, storage, and/or other types of networks; and may employ communication technologies including, but in no way limited to, analog technologies, digital technologies, optical technologies, wireless technologies (e.g., Bluetooth), networking technologies, and internetworking technologies.

[0099] It should also be noted that devices may use communication protocols and messages (e.g., messages created, transmitted, received, stored, and/or processed by the device), and such messages may be conveyed by a communication network or medium.

[0100] Unless the context otherwise requires, the present disclosure should not be construed as being limited to any particular communication message type, communication message format, or communication protocol. Thus, a communication message generally may include, without limitation, a frame, packet, datagram, user datagram, cell, or other type of communication message.

[0101] Unless the context requires otherwise, references to specific communication protocols are exemplary, and it should be understood that alternatives may, as appropriate, employ variations of such communication protocols (e.g., modifications or extensions of the protocol that may be made from time-to-time) or other protocols either known or developed in the future.

[0102] It should also be noted that logic flows may be described herein to demonstrate various aspects of the disclosure, and should not be construed to limit the present disclosure to any particular logic flow or logic implementation. The described logic may be partitioned into different logic blocks (e.g., programs, modules, functions, or subroutines) without changing the overall results or otherwise departing from the true scope of the disclosure.

[0103] Often, logic elements may be added, modified, omitted, performed in a different order, or implemented using different logic constructs (e.g., logic gates, looping primitives, conditional logic, and other logic constructs) without changing the overall results or otherwise departing from the scope of the disclosure.

[0104] The present disclosure may be embodied in many different forms, including, but in no way limited to, a graphical processing unit as well as computer program logic for use with a processor (e.g., a microprocessor, microcontroller, digital signal processor, or general purpose computer), programmable logic for use with a programmable logic device (e.g., a Field Programmable Gate Array (FPGA) or other PLD), discrete components, integrated circuitry (e.g., an Application Specific Integrated Circuit (ASIC)), or any other means including any combination thereof Computer program logic implementing some or all of the described functionality is typically implemented as a set of computer program instructions that is converted into a computer executable form, stored as such in a computer readable medium, and executed by a microprocessor under the control of an operating system. Hardware-based logic implementing some or all of the described functionality may be implemented using one or more appropriately configured FPGAs.

[0105] Computer program logic implementing all or part of the functionality previously described herein may be embodied in various forms, including, but in no way limited to, a source code form, a computer executable form, and various intermediate forms (e.g., forms generated by an assembler, compiler, linker, or locator).

[0106] Source code may include a series of computer program instructions implemented in any of various programming languages (e.g., an object code, an assembly language, or a high-level language such as Fortran, python, C, C++, JAVA, JavaScript or HTML) for use with various operating systems or operating environments. The source code may define and use various data structures and communication messages. The source code may be in a computer executable form (e.g., via an interpreter), or the source code maybe converted (e.g., via a translator, assembler, or compiler) into a computer executable form.

[0107] Computer-executable program code for carrying out operations of embodiments of the present disclosure may be written in an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++, or the like. However, the computer program code for carrying out operations of aspects of the present disclosure may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages.

[0108] Computer program logic implementing all or part of the functionality previously described herein may be executed at different times on a single processor (e.g., concurrently) or may be executed at the same or different times on multiple processors and may run under a single operating system process/thread or under different operating system processes/threads.

[0109] Thus, the term “computer process” refers generally to the execution of a set of computer program instructions regardless of whether different computer processes are executed on the same or different processors and regardless of whether different computer processes run under the same operating system process/thread or different operating system processes/threads.

[0110] The computer program may be fixed in any form (e.g., source code form, computer executable form, or an intermediate form) either permanently or transitorily in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), a PC card (e.g., PCMCIA card), or other memory device.

[0111] The computer program may be fixed in any form in a signal that is transmittable to a computer using any of various communication technologies, including, but in no way limited to, analog technologies, digital technologies, optical technologies, wireless technologies (e.g., Bluetooth), networking technologies, and internetworking technologies.

[0112] The computer program may be distributed in any form as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).

[0113] Hardware logic (including programmable logic for use with a programmable logic device) implementing all or part of the functionality previously described herein may be designed using traditional manual methods, or may be designed, captured, simulated, or documented electronically using various tools, such as Computer Aided Design (CAD), a hardware description language (e.g., VHDL or AHDL), or a PLD programming language (e.g., PALASM, ABEL, or CUPL).

[0114] Any suitable computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or medium.

[0115] More specific examples of the computer readable medium include, but are not limited to, an electrical connection having one or more wires or other tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device.

[0116] Programmable logic may be fixed either permanently or transitorily in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), or other memory device.

[0117] The programmable logic may be fixed in a signal that is transmittable to a computer using any of various communication technologies, including, but in no way limited to, analog technologies, digital technologies, optical technologies, wireless technologies (e.g., Bluetooth), networking technologies, and internetworking technologies.

[0118] The programmable logic may be distributed as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web). Of course, some embodiments of the disclosure may be implemented as a combination of both software (e.g., a computer program product) and hardware. Still other aspects of the present disclosure are implemented as entirely hardware, or entirely software.

[0119] While certain exemplary aspects have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and are not restrictive on the broad disclosure, and that the aspects of the present disclosure are not limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible.

[0120] Those skilled in the art will appreciate that various adaptations, modifications, and/or combination of the just described aspects and examples can be configured. Therefore, it is to be understood that, within the scope of the appended claims, the disclosure may be practiced other than as specifically described herein. For example, unless expressly stated otherwise, the steps of processes described herein may be performed in orders different from those described herein and one or more steps may be combined, split, or performed simultaneously. Those skilled in the art will also appreciate, in view of this disclosure, that different aspects or examples of the disclosure described herein may be combined to form other aspects or examples of the disclosure.

REFERENCE SIGN LIST

[0121] 1 system server [0122] 2 platform device [0123] 21 platform structure [0124] 21-1, 21-2, 21-n layers of the platform structure [0125] 3 project database [0126] 3-1, 3-2, 3-n layers of the project database [0127] 4 project criteria database [0128] 4-1, 4-2, 4-n layers of the project criteria database [0129] 5 basic criteria database [0130] 5-1, 5-2, 5-n layers of the basic criteria database [0131] 6a, 6b, 6c terminal devices [0132] 7 blockchain network [0133] N network