Generation and execution of custom requests for quote
A request for quote (RFQ) engine ( 10 ) includes a data and metrics designer ( 22 ) that generates, in response to input from a user, a data and metrics model ( 42 ) for an RFQ template using a data and metrics meta-model ( 32 ). The RFQ engine ( 10 ) also includes a state transition designer ( 24 ) that generates, in response to input from the user, a state transition model ( 44 ) for the RFQ template using a state transition meta-model ( 34 ). Furthermore, the RFQ engine ( 10 ) includes a workflow designer ( 26 ) that generates, in response to input from the user, a user interface workflow ( 46 ) for the RFQ template using a workflow meta-model ( 36 ). In addition, the RFQ engine includes an execution engine ( 40 ) that executes the RFQ template that includes the data and metrics model ( 42 ) generated by the data and metrics designer ( 22 ), the state transition model ( 44 ) generated by the state transition designer ( 24 ), and the user interface workflow ( 46 ) generated by the workflow designer ( 26 ). The RFQ template is executed to generate an RFQ.
1. A system, comprising:
a supply chain network comprising one or more suppliers that provide one or more products or services, an originating entity, and a request for quote (RFQ) engine, the RFQ engine comprising one or more processors and one or more memory units;
the originating entity configured to initiate a request for quote (RFQ) for the one or more products or services provided by the one or more suppliers by initiating use of and sending parameter values over a computer network to the RFQ engine;
the RFQ engine, in response to the initiating use by and received parameter values over the computer network from the originating entity, configured to:
generate a data and metrics model for a custom request for quote (RFQ) template using a data and metrics meta-model by a data and metrics logical tier, the data and metrics model comprising rules;
generate a state transition model for the custom RFQ template using a state transition meta-model by a state transition logical tier, the state transition model comprising a state transition sequence based on the rules of the data and metrics model;
generate a user interface workflow for the custom RFQ template using a workflow meta-model by a workflow logical tier; and
an execution engine that executes the custom RFQ template comprising the data and metrics model generated by the data and metrics logical tier, the state transition model generated by the state transition logical tier, and the user interface workflow generated by the workflow logical tier, the custom RFQ template executed to generate an RFQ based on the received parameter values and according to the rules of the data and metrics model, the RFQ communicated over the computer network to the one or more suppliers, and the RFQ processed based on the state transition sequence of the state transition model; and
the one or more suppliers configured to receive the RFQ and process the RFQ based on the state transition sequence of the state transition model.
2. The system of claim 1 , wherein the data and metrics model defines data to be collected in association with the RFQ generated by the execution engine.
3. The system of claim 2 , wherein the data is collected over the computer network from the originating entity and the one or more suppliers responding to the RFQ.
4. The system of claim 2 , wherein the data and metrics model defines one or more metrics used to evaluate at least a portion of the collected data.
5. The system of claim 1 , wherein the user interface workflow defines a sequence of user interfaces presented to the one or more suppliers in association with the generation of and response to the RFQ.
6. The system of claim 1 , wherein the execution engine is further configured to:
receive a request over the computer network from the originating entity to generate an RFQ;
identify one or more custom RFQ templates that may be used to generate the RFQ;
receive a selection of a custom RFQ template over the computer network from the originating entity; and
execute the selected custom RFQ template in response to the selection.
7. The system of claim 6 , wherein executing the selected custom RFQ template initiates the communication of one or more user interfaces over the computer network to the originating entity that allow the originating entity to input information to generate the RFQ, the one or more user interfaces defined in the user interface workflow associated with the selected custom RFQ template.
8. A method, comprising:
generating, by a request for quote (RFQ) engine comprising one or more processors and one or more memory units, a data and metrics model comprising rules for a custom request for quote (RFQ) template using a data and metrics meta-model and parameter values received over a computer network from an originating entity, the originating entity configured to initiate a request for quote (RFQ) for one or more products or services from one or more suppliers of one or more products or services;
generating, by the RFQ engine, a state transition model for the custom RFQ template using a state transition meta-model by a state transition logical tier, the state transition model comprising a state transition sequence based on the rules of the data and metrics model;
generating, by the RFQ engine, a user interface workflow for the custom RFQ template using a workflow meta-model by a workflow logical tier;
executing, by an execution engine, the custom RFQ template comprising the data and metrics model, the state transition model, and the user interface workflow, the custom RFQ template executed to generate an RFQ based on the received parameter values and according to the rules of the data and metrics model, the RFQ communicated over the computer network to the one or more suppliers, and the RFQ processed based on the state transition sequence of the state transition model; and
receiving and processing, by the one or more suppliers, the RFQ based on the state transition sequence of the state transition model.
9. The method of claim 8 , wherein the data and metrics model defines data to be collected in association with the RFQ generated by the execution engine.
10. The method of claim 9 , wherein the data is collected over the computer network from the originating entity and the one or more suppliers responding to the RFQ.
11. The method of claim 9 , wherein the data and metrics model defines one or more metrics used to evaluate at least a portion of the collected data.
12. The method of claim 8 , wherein the user interface workflow defines a sequence of user interfaces presented to the one or more suppliers in association with the generation of and response to the RFQ.
13. The method of claim 8 , further comprising:
receiving a request over the computer network from the originating entity to generate an RFQ;
identifying one or more custom RFQ templates that may be used to generate the RFQ;
receiving a selection of a custom RFQ template over the computer network from the originating entity; and
executing the selected custom RFQ template in response to the selection.
14. The method of claim 13 , wherein executing the selected custom RFQ template initiates the communication of one or more user interfaces over the computer network to the originating entity that allow the originating entity to input information to generate the RFQ, the one or more user interfaces defined in the user interface workflow associated with the selected custom RFQ template.
15. A non-transitory computer-readable medium embodied with software, the software when executed using a computer is configured to:
generate a data and metrics model comprising rules for a custom request for quote (RFQ) template using a data and metrics meta-model and parameter values received over a computer network from an originating entity, the originating entity configured to initiate a request for quote (RFQ) for one or more products or services from a supplier of one or more products or services;
generate a state transition model comprising a state transition sequence based on the rules of the data and metrics model for the custom RFQ template using a state transition meta-model by a state transition logical tier;
generate a user interface workflow for the custom RFQ template using a workflow meta-model by a workflow logical tier;
execute the custom RFQ template comprising the data and metrics model, the state transition model, and the user interface workflow, the custom RFQ template executed to generate an RFQ based on the received parameter values and according to the rules of the data and metrics model, the RFQ communicated over the computer network to the supplier, and the RFQ processed based on the state transition sequence of the state transition model; and
receive and process the RFQ based on the state transition sequence of the state transition model.
16. The non-transitory computer-readable medium of claim 15 , wherein the data and metrics model defines data to be collected in association with the generated RFQ.
17. The non-transitory computer-readable medium of claim 16 , wherein the data is collected over the computer network from the originating entity and the one or more suppliers responding to the RFQ.
18. The non-transitory computer-readable medium of claim 16 , wherein the data and metrics model defines one or more metrics used to evaluate at least a portion of the collected data.
19. The non-transitory computer-readable medium of claim 15 , wherein the user interface workflow defines a sequence of user interfaces presented to the one or more suppliers in association with the generation of and response to the RFQ.
20. The non-transitory computer-readable medium of claim 15 , wherein the software is further configured to:
receive a request over the computer network from the originating entity to generate an RFQ;
identify one or more custom RFQ templates that may be used to generate the RFQ;
receive a selection of a custom RFQ template over the computer network from the originating entity; and
execute the selected custom RFQ template in response to the selection.
21. The non-transitory computer-readable medium of claim 20 , wherein executing the selected custom RFQ template initiates the communication of one or more user interfaces over the computer network to the originating entity that allow the originating entity to input information to generate the RFQ, the one or more user interfaces defined in the user interface workflow associated with the selected custom RFQ template.