DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Introduction
The following is a non-final Office Action in response to Applicant’s communications received on November 26, 2025. Claims 1, 14 and 25 has been amended, and claims 4, 10, 13, 17, 20, 24 and 28 have been cancelled.
Currently claims 1-3, 5-9, 11-12, 14-16, 18-19, 21-23, 25-27 and 29-30 are pending. Claims 1, 14 and 25 are independent.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submissions filed on November 26, 2025 has been entered.
Response to Amendments
Applicant’s amendments to claims 1, 14 and 25 are NOT sufficient to overcome the 35 U.S.C. § 101 rejection as set forth in the previous Office Action. Therefore, the 35 U.S.C. § 101 rejection to claims 1-3, 5-9, 11-16, 18-19, 21-23, 25-27 and 29-30 has been maintained.
Response to Arguments
Applicant’s arguments filed on 11/26/2025 have been fully considered but they are not persuasive.
In the Remarks on page 17, Applicant’s arguments regarding the 35 U.S.C. § 101 rejection that the claims recite additional elements that integrate the judicial exception into a practical application… since the Specification discloses particular problems when enterprises are using both CRM and ERP system (see page 18), and paragraph [0018]-[0038] disclose a solution to these problems by using microcomponents that act as integration links between CRM and ERP system. They allow real-time, multi-directional data exchange without needing complex middleware or third-party APIs..
In response to Applicant’s argument, the Examiner respectfully disagrees. In order for a claim to integrate the exception into a practical application, the additional claimed elements must, for example, improve the functioning of a computer or any other technology or technical field (see MPEP § 2106.05(a)), apply the judicial exception with a particular machine (see MPEP § 2106.05(b)), affect a transformation or reduction of a particular article to a different state or thing (see MPEP § 2106.05(c)), or apply or use the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment (see MPEP § 2106.05(e)). See Revised 2019 Guidance.
Here, claim 1 recites the additional elements of “a customer relationship management (CRM) system”, “an enterprise resource planning (ERP) system”, “one or more computing devices”, “a memory”, and “one or more processor of the one or more computing devices” for executing instructions to perform the method” including installing a framework of microcomponents into the CRM system (storing an application program as data in the CRM system), receiving a request, retrieving information from the ERP system, providing (sending, transmitting) in real-time the information retrieved from the ERP system to the CRM system, retrieving additional information from the ERP system, and providing in-time the additional information retrieved from the ERP system to the CRM system, providing (sending, transmitting) bi-directional data exchange between the CRM system and the ERP system. The additional elements are recited at a high level of generality and are merely invoked as tools to perform the generic computer functions including receiving, manipulation and transmitting information over a network. Using generic computer components to implement an abstract idea does not integrate the abstract idea into a practical application. See, e.g., Alice, 573 U.S. at 223–24; see also Revised Guidance, 84 Fed. Reg. at 55 (explaining that courts have identified merely using a computer as a tool to perform an abstract idea as an example of when a judicial exception has not been integrated into a practical application).
Further, the claims here are unlike the claims in Enfish either. In Enfish, the claims at issue focused on a specific type of data structure, i.e., a self-referential table for a computer database, designed to improve the way a computer carries out its basic functions of storing and retrieving data, and not merely on asserted advances in the uses to which existing computer capabilities could be put. Enfish, 822 F.3d at 1335–36. In contrast, the improvement that Applicant concerns is an entrepreneurial problem rather than a technological problem. For example, “improving workflows and productivity” (see Spec [0002]); and “improve revenue-generating business processes through the bridging of legacy ERP and CRM systems.”(see Spec [0017]).
In the Remarks on page 20, Applicant’s arguments regarding the 35 U.S.C. § 101 rejection that if Examiner disagree with Applicant that their claimed invention is not an abstract idea, Applicant can still traverse this under Step 2B of the Alice inquiry.
In response to Applicant’s argument, the Examiner respectfully disagrees. Step 2B of the Alice inquiry is to search for an ‘inventive concept’—i.e., an element or combination of elements that is ‘sufficient to ensure the claims in practice amounts to significantly more than a patent on the ineligible concept itself. Alice Corp. Pty. v. CLS Bankint'l, 573 U.S. 208,217-18 (2014). Here, the amended claims recite the additional elements of “by processors” and “memory devices” for performing the steps. The Specification discloses these additional elements at a high level of generality, nothing more than any generic computer component that capable performs generic computer functions including receiving, storing, and transmitting data over a network. The processor and memory in this case, at best, may perform the steps of receiving, storing, and retrieving data stored on memory. However, using the processors and memory for receiving, storing and retrieving data have been recognized by the courts as merely well-understood, routine, and conventional functions of generic computers. See MPEP 2106.05 (d) (II) (Receiving or transmitting data over a network, e.g., using the Internet to gather data, buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network); Storing and retrieving information in memory, Versate Dev. Group, Inc. v. SAP Am., Inc., 793 F.3d 1306, 1334, 115 USPQ2d 1681, 1701 (Fed. Cir. 2015); OIP Techs., 788 F.3d at 1383, 115 USPQ2d at 1092-93.). The courts have repeatedly held that conventional computer components operating to collect, manipulate, and display data are well understood, routine, and conventional to a skilled artisan. See Mortg. Grader, Inc. v. First Choice Loan Servs. Inc., 811 F.3d 1314, 1324–25 (Fed. Cir. 2016) (generic computer components, such as an “interface,” “network,” and “database,” fail to satisfy the inventive concept requirement); Alice, 573 U.S. at 226 (“Nearly every computer will include a ‘communications controller’ and [a] ‘data storage unit’ capable of performing the basic calculation, storage, and transmission functions required by the method claims.”); Intellectual Ventures I LLC v. Erie Indem. Co., 850 F.3d 1315, 1327 (Fed. Cir. 2017) (explaining that receiving a request to execute a database search and delivering records are routine computer functions that can only be described as generic or conventional). Therefore, simply implementing the abstract idea on a generic computer for performing generic computer functions are not enough to qualify as a practical application, and the combination of the claimed elements do not provide significantly more to an abstract idea (MPEP 2106.05(f) & (h)).
In the Remarks on page 22, Applicant’s arguments regarding the 35 U.S.C. § 101 rejection that like Speed Track, Intellectual Ventures, and DDR Holding, Applicant’s claimed invention is rooted in computer, enterprise software systems, and business process automation technology. Also, Applicant’s claimed invention solves a technological problem arising from such by enabling real-time, bi-directional integration without relying on complex middleware or third-party APIs. Applicant’s claimed invention streamlines business workflows—such as quoting and pricing—by using modular microcomponents that allow seamless communications and configuration across enterprise platforms.
In response to Applicant’s argument, the Examiner respectfully disagrees. As discussed above, Applicant’s invention aims to solve an entrepreneurial problem—improve revenue-generating business processes through the bridging of legacy ERP and CRM systems. Nothing in the claims similar to the claims in Speed Track, Intellectual Ventures and DDR Holding that “rooted in computer and communication networks and solving a technological problem arising out of such networks.” Which the network itself operated was changed to improve network operations. However, for the instant application, even the claimed solution may improve the workflow and productivity for the enterprise, the improvement is not made to the functioning of the computer or other technology or technical field.
In the Remarks on page 22-23, Applicant argues that Gil, Wilkins, Kemmer, and Charlton, either alone or in combination, do not disclose the claimed combination including at least the above features; neither do they render obvious the claimed invention. Gil focuses on middleware/EAI and SCM integration using protocols like EDI and flat files—not CRM-installed microcomponents. Wilkins deals with AI/ML predictive analytics for CPQ, not real-time ERP data exchange. Desai addresses cloud application management and low-code scripting, not synchronous CRM—ERP integration. Kemmer simulates pricing but does not teach microcomponents or ERP-native conversion. Last, Charlton concerns healthcare embedded systems and firmware upgrades, completely outside enterprise software integration.
In response to Applicant’s arguments against the references individually, one cannot show nonobviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986).
Claim Objections
Claim 1 is objected to because of the following informalities. Claim 1 recites “enable a user to modify to modify a configuration” which appears to be a typography error. Examiner interpreted the claim to read “enable a user to modify a configuration” for the purpose of examination.
Claim Rejections – 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(B) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-3, 5-9, 11-12, 14-16, 18-19, 21-23, 25-27 and 29-30 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which applicant regards as the invention.
Regarding claims 1, 14 and 25, claim 1 recites “the method performed by one or more computing systems, comprising processing devices and memory devices”, “executed by one or more processors of the one or more computing systems”, “cause the one or more processing devices to perform”, and the steps performed “by processors”; claims 14 and 25 recite “a computing system”, “the computing system comprising processing devices and memory devices coupled to the processing devices, with one or more memory devices”, “executed by one or more processors”, and the steps performed “by processors”, render the claims indefinite because scope of such claim cannot be reasonable ascertained by one of ordinary skill in the art. It is unclear to the Examiner as to whether the “one or more computing systems” equal the “processing devices” equal the “one or more processors” and equal the “processors”; and unclear whether the steps are performed/executed “by one or more computing systems”, “by one or more processors” or “by processors”, or all together. However, the Specification only describes that “the present embodiments may be executed by programmable equipment, such as computers” (see ¶ 37).
Further, each step is performed “by processors” can be interpreted as each step is performed by a different processor or a different set of processors.
Applicant is required to particularly point out and distinctly claim the subject matter which applicant regards as the invention.
Dependent claims 2-3, 5-9, 11-12, 15-16, 18-19, 21-23, 26-27 and 29-30 are also rejected for the same reasons as each depended on the rejected claims.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-3, 5-9, 11-12, 14-16, 18-19, 21-23, 25-27 and 29-30 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
As per Step 1 of the subject matter eligibility analysis, it is to determine whether the claim is directed to one of the four statutory categories of invention, i.e., process, machine, manufacture, or composition of matter.
In this case, claims 1-3, 5-9 and 11-12 are directed to a method for providing information retrieved from the ERP system to the CRM system for use in the workflow of the CRM transaction, which falls within the statutory category of a process; claims 14-16, 18-19 and 21-23 are directed to a system comprising processing devices and memory devices, which falls within the statutory category of a machine; and claims 25-27 and 29-30 are directed to a system comprising processing devices and memory devices, which falls within the statutory category of a machine. Step 1 is satisfied.
In Step 2A of the subject matter eligibility analysis, it is to “determine whether the claim at issue is directed to a judicial exception (i.e., an abstract idea, a law of nature, or a natural phenomenon). Under this step, a two-prong inquiry will be performed to determine if the claim recites a judicial exception (an abstract idea enumerated in the 2019 Guidance), then determine if the claim recites additional elements that integrate the exception into a practical application of the exception. See 2019 Revised Patent Subject Matter Eligibility Guidance (2019 Guidance), 84 Fed. Reg. 50, 54-55 (January 7, 2019).
In Prong One, it is to determine if the claim recites a judicial exception (an abstract idea enumerated in the 2019 Guidance, a law of nature, or a natural phenomenon).
Taking the method as representative, claim 1 recites “a method of integrating information [stored in a CRM and an ERP] on behalf of an enterprise…,” installing a framework of microcomponents into the CRM, receiving a request to initiate a CRM transaction, determining, based on the CRM transaction, the sales organization picker microcomponent is associated with the workflow of the CRM transaction, retrieving information from the ERP system, providing the information retrieved from the EPR system to the CRM system, determining the plant picker microcomponents is associated with the workflow of the CRM transaction, retrieving additional information from the ERP system, providing the additional information retrieved from the ERP system by the plant picker microcomponents to the CRM system, providing a user interface to enable a user to modify a configuration, performing a price simulation process…, receiving a web service call…, retrieving pricing data from the ERP system, providing the pricing data in XML format to the CRM system, and upgrading the sales organization picker microcomponent; the dependent claims further recite the similar limitations. Each of these steps involves observation, evaluation, judgment, or opinion. For example, “observing the CRM transaction and determining whether a sales organization picker microcomponent associated with the workflow of the CRM transaction” requires evaluation of the CRM transaction and judgment to determine whether a sales organization picker /plant picker microcomponent associated with the workflow of the CRM transaction. The Specification provided an example supports the view of mental process, such as “The sale area picker uses the SAP customer number that is attached to the CPQ quote to determine the SAP customer ID associated with the account.” (Spec, ¶ 28). None of the limitations recites technological implementation details for any of these steps, but instead recite only results desired by any and all possible means. The limitations, as drafted, are directed to methods, allowing a user to manage CRM transactions, managing commercial interactions, and managing interactions between people, which fall within the certain methods of organizing human activity grouping. See Under the 2019 Guidance, 84 Fed. Reg. 52. The mere nominal recitation of generic computer components including “by one or more processors”, “by processors”, “memory devices” and “a user interface” for performing no more than generic computer functions do not take the claims out of the certain methods of organizing human activity grouping because they do not provide meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment or field of use. See MPEP § 2106.05(h). Thus, claims fall in the mental processes grouping, and therefore, the claim recite an abstract idea.
In Prong Two, it is to determine if the claim recites additional elements that integrate the exception into a practical application of the exception.
Beyond the abstract idea, the claims recite the additional elements of by one or more processors”, “by processors”, “memory devices” and “a user interface” for executing instructions to perform the steps. These additional elements are recited at a high level of generality and merely invoked as tools to perform the generic computer functions including receiving, storing, manipulating, and transmitting information over a network. Thus, merely adding a generic computer, generic computer components, or programmed computer to perform generic computer functions does not automatically overcome an eligibility rejection. Alice Corp. Pty. Ltd. V. CLS Bank Int’l, 134 S. Ct. 2347, 2358-59, 110 USPQ2d 1976, 1983-84 (2014). Again, automating an abstract process does not convert it into a practical application. See Credit Acceptance v. Westlake Servs., 859 F.3d 1044, 1055 (Fed. Cir. 2017) (“Our prior cases have made clear that mere automation of manual processes using generic computers does not constitute a patentable improvement in computer technology.”). However, simply implementing the abstract idea on a generic computer does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea, and nothing in the claims that reflects an improvement to the functioning of a computer itself or another technology. Therefore, the claims are directed to an abstract idea, and the analysis is proceeding to Step 2B.
In Step 2B of Alice, it is "a search for an ‘inventive concept’—i.e., an element or combination of elements that is ‘sufficient to ensure that the patent in practice amounts to significantly more than a patent upon the [ineligible concept’ itself.’” Id. (alternation in original) (quoting Mayo Collaborative Servs. v. Prometheus Labs., Inc., 132 S. Ct. 1289, 1294 (2012)).
The claim as described in Prong Two above, nothing in the claims that integrates the abstract idea into a practical application. The same analysis applies here in Step 2B.
Beyond the abstract idea, the claims recite the additional elements of by one or more processors”, “by processors”, “memory devices” and “a user interface” for executing instructions to perform the steps. These computer components are recited at a high level of generality, nothing more than any generic computer that capable performs generic computer functions including receiving, storing, and transmitting data over a network. In the present case, at best, the one or more processors/processors may perform the steps of receiving, storing, and transmitting (providing) data over a network. However, the functions of receiving, storing and transmitting data over a network have been recognized by the courts as merely well-understood, routine, and conventional functions of generic computers. See MPEP 2106.05 (d) (II) (Receiving or transmitting data over a network, e.g., using the Internet to gather data, buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network); Storing and retrieving information in memory, Versate Dev. Group, Inc. v. SAP Am., Inc., 793 F.3d 1306, 1334, 115 USPQ2d 1681, 1701 (Fed. Cir. 2015); OIP Techs., 788 F.3d at 1383, 115 USPQ2d at 1092-93.). Simply implementing the abstract idea on a generic computer for performing generic computer functions are not enough to qualify as a practical application, and the combination of the claimed elements do not provide significantly more to an abstract idea (MPEP 2106.05(f) & (h)).
For the foregoing reasons, claims 1-3, 5-9 and 11-12 cover subject matter that is judicially-excepted from patent eligibility under § 101 as discussed above, the other claims 14-16, 18-19, 21-23, 25-27 and 29-30 parallel claims 1-3, 5-9 and 11-12—similarly cover claimed subject matter that is judicially excepted from patent eligibility under § 101.
Therefore, the claims as a whole, viewed individually and as a combination, do not provide meaningful limitations to transform the abstract idea into a patent eligible application of the abstract idea such that the claims amount to significantly more than the abstract idea itself. The claims are not patent eligible.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 1-3, 5-9, 11-12, 14-16, 18-19, 21-23, 25-27 and 29-30 are rejected under 35 U.S.C. 103 as being unpatentable over Gil et al., (US 2002/0188513, hereinafter: Gil), and in view of Wilkins et al., (US 2020/0005123, hereinafter: Wilkins), and further in view of Desai et al., (US 2014/0208266, hereinafter: Desai), and Kemmer et al., (US 20160162920, hereinafter: Kemmer), and Charlton et al., (US 10176888 B2, hereinafter: Charlton).
Regarding claim 1, Gil discloses a computer-based method of integrating information stored in multiple database systems on behalf of an enterprise in real-time without the need for data synchronization or complex application programming interface (API) integration via a third party, wherein the multiple database systems comprise a customer relationship management (CRM) system of the enterprise and an enterprise resource planning (ERP) system of the enterprise (see Fig. 5-6, ¶ 50, ¶ 70, ¶ 100-101), the method performed by one or more computing systems, comprising processing devices and memory devices coupled to the processing devices, with one or more memory devices having microcomponent instructions stored thereon that, when executed by one or more processors of the one or more computing system is configured to (see ¶ 36), cause the one or more processing devices to perform the method comprising:
wherein at least one of the microcomponents is configured to receive extensible markup language (XML) based service calls from the CRM system (see ¶ 78-79, ¶ 92-92, ¶ 113, ¶ 121), convert the XML format into ERP-native API calls and retrieve validated data from the ERP system (see Fig. 18; ¶ 84, ¶ 180, ¶ 198).
Receiving, by processors, with instructions stored on coupled memory devices (see ¶ 36), a request to initiate a CRM transaction (see Abstract: a request from a network system for access real-time data is received; ¶ 7-9, ¶ 11, ¶ 56, ¶ 64, ¶ 69, ¶ 80-81, ¶ 89, ¶ 120: a customer or partner initiates a transaction directly to the execution subsystem), wherein the CRM transaction is a configure, price, quote (CPQ) process for a selected product have a workflow that is to be executed by the CRM system, wherein the ERP system of the enterprise maintains information relevant to the CRM transaction (see ¶ 8, ¶ 70: describes the system includes application or subsystems for enterprise resource planning (ERP) and customer relationship management (CRM) may provide or support functionality and maintain customer information in a database);
Determining, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), based on the CRM transaction, the sales organization picker microcomponent is associated with the workflow of the CRM transaction (see ¶ 78-80, ¶ 82 and ¶ 90);
Retrieving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the sales organization picker microcomponent, retrieving information from the ERP system, wherein the information is associated with the workflow for the CRM transaction (see ¶ 79, ¶ 96, ¶ 122 and ¶ 128-129);
providing, by processors, with microcomponent instructions stored on coupled memory devices, in real-time the information retrieved from the ERP system by the sales organization picker microcomponent to the CRM system for use in the workflow of the CRM transaction (see ¶ 10, ¶ 62, ¶ 70-72, and ¶ 123-126);
determining, by processors, from microcomponent instructions stored on coupled memory devices (see ¶ 36), the plant picker microcomponent is associated with the workflow of the CRM transaction (see ¶ 78-80, ¶ 127, ¶ 137).
Retrieving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the plant picker microcomponent, additional information from the ERP system, wherein the additional information is associated with the workflow for the CRM transaction (see ¶ 88, ¶ 90, ¶ 96 and ¶ 149);
17providing, by processors, from microcomponent instructions stored on coupled memory devices (see ¶ 36), in real-time the additional information retrieved from the ERP system by the second microcomponent to the CRM system for use in the workflow of the CRMby the plant picker microcomponent to the CRM system for use in the workflow of the CRM transaction (see ¶ 10, ¶ 62-64, ¶ 72, and claim 1);
Providing a user interface to enable a user to modify to modify a configuration of said selected product (see Fig. 15; ¶ 73, ¶ 78, ¶ 177); and wherein subsequent to receiving a request to configure a product associated with the CPQ process (see ¶ 9-10, ¶ 78, ¶ 90, ¶ 200), retrieving rule-based configuration options from the ERP system using a fourth microcomponent (see ¶ 86-88, ¶ 128-129, ¶ 172-173);
receiving, by processors, with microcomponent instructions stored on coupled memory devices, on behalf of the microcomponent, a web service call from the CRM system to the pricing and order simulation microcomponent using an (XML) format structure (see ¶ 7-10, ¶ 162-163); and
retrieving, by processors, with microcomponent instructions stored on coupled memory devices, pricing data from the ERP system, and in response, providing, by processors, with microcomponent instructions stored on coupled memory devices, the pricing data in XML format to the CRM system (see ¶ 96, ¶ 124, ¶ 129).
Gil disclose the process execution component may include software or application for initiating business workflow by a transaction, a request, or a demand from a partner system, generating and maintaining the context of the transaction in real-time (see ¶ 79-80); and setting up unit price for a particular product (see ¶ 126).
Gil does not explicitly disclose wherein the CRM transaction is a configure, price, quote (CPQ) process have a workflow that is to be executed by the CRM system of the enterprise; however, Wilkins in an analogous art for generating product quotes discloses
wherein the CRM transaction is a configure, price, quote (CPQ) process for a selected product having a workflow that is to be executed by the CRM system of the enterprise (see Abstract, ¶ 2-4, ¶ 7: configurator the generate a quote for a product or service, the quote including a quote workflow and quote attributes; ¶ 32: the CPQ systems are processed through a customer defined workflow).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil to include teaching of Wilkins in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more accurate pricing solution, enabling better decision making. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses an integrated network application designed and architected as a complete closed-loop system, it incorporate all of the features in one package required to execute and coordinate transactions accurately in the network and be able to monitor the performance of any given partner. It offers partners multiple connection options to minimize IT investment, reduce overhead, and increase adoption rates among partners. It supports direct, real-time connections to a number of enterprise resource planning (ERP), material requirement planning (MRP), supply chain management (SCM), customer relationship management (CRM), warehouse management systems (WMS), and enterprise application integration (EAI) applications or subsystems for direct back-end system integration. Communication with any existing system is possible using multiple electronic connection protocols, including enterprise application integration (EAI), electronic data interchange (EDI) files, flat file, and application connectors, so it does not require users to install and run software from their system (see ¶ 56-57); The enterprise component represents the enterprise and is integrated into the existing system of the enterprise. The enterprise component is operable to generate real-time data relevant to one or more transactions in which the enterprise is involved in the supply chain, and the partner component represent a partner and is integrated into the existing system of the partner; and the functionality of these components can be performed with suitable data processing facility running appropriate software and operating under the control of any suitable operating system (see ¶ 76).
Gil and Wilkins do not explicitly disclose the following limitations; however, Desai in an analogous art for managing applications discloses
Installing, by processors, from coupled memory devices with stored microcomponent instructions, a framework of microcomponents into the CRM system of the enterprise, further wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system (see ¶ 20, ¶ 39, ¶ 72-75, ¶ 83, ¶ 93, ¶ 96: VBScript is one of the low code programming techniques).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins to include teaching of Desai in order to gain the commonly understood benefit of such adaption, such as providing the benefit of enhancing computation efficiency, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses a plurality of enterprise components for accessing real-time data of partner systems and retrieving data relevant to one or more transactions in which the partner is involved in the supply chain; and a network system of network may be implemented at least in part at each of enterprise domain. The network domain may be linked through a gateway to another network domain such as the service network may be linked to the supplier network through the respective network domains to route transaction between the networks (see ¶ 11-13, ¶ 45, and ¶ 126).
Gil, Wilkins and Desai do not explicitly disclose performing a price simulation process, however, Kemmer in an analogous art for simulating the cost of goods and services discloses
Performing, by processors, with microcomponent instructions stored on coupled memory devices, based on the information retrieved from the ERP system, using the sales organization picker microcomponent and the additional information retrieved from the ERP system using the plant picker microcomponent, a price simulation process using the pricing and order simulation microcomponent by (see ¶ 18-20 and ¶ 34).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins and Desai to include teaching of Kemmer in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more optimal solution, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses the real-time information within the supply chain can be used to modify or update the respective contexts for the transactions, and the partner coordinator may independently push out the real-time data to the network domain by cooperating with one or more existing legacy system at the customer domain (see ¶ 87).
Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton in an analogous art for software upgrading management discloses
upgrading, by processors, with microcomponent instructions stored on coupled memory devices, the sales organization picker microcomponent, wherein upgrading the sales organization picker microcomponent does not affect the operation of the plant picker microcomponent (see col. 15, lines 18-55, claim 20).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
In addition, the phrases “wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system” are merely characterizing the type of the framework of microcomponents is directed to nonfunctional descriptive material because they cannot exhibit any functional interrelationship with the way the steps are performed. Therefore, it has been held that nonfunctional descriptive material will not distinguish the invention from prior art in term of patentability. (In re Gulack, 217 USPQ 401 (Fed. Cir. 1983), In re Ngai, 70 USPQ2d (Fed. Cir. 2004), In re Lowry, 32 USPQ2d 1031 (Fed. Cir. 1994); MPEP 2111.05).
Regarding claim 2, Gil discloses the computer-based method of claim 1, wherein at least one of the sales organization picker microcomponent and plant picker microcomponent are configurable (see ¶ 131).
Regarding claim 3, Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton discloses the computer-based method of claim 2, wherein each of the sales organization picker microcomponent and plant picker microcomponent are separately upgradable (see claim 6, claim 11).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Regarding claim 5, Gil discloses the computer-based method of claim 1, further comprising:
providing, by at least one of the sales organization picker microcomponent and plant picker microcomponents, bi-directional data exchange between the CRM system and the ERP system (see ¶ 100: exchanges and management of data between the components of the network; ¶ 126).
Regarding claim 6, Gil discloses the computer-based method of claim 5 wherein the bi-directional data exchange is in real time (see ¶ 8, ¶ 41, ¶ 86, ¶ 100, and ¶ 126).
Regarding claim 7, Gil discloses the computer-based method of claim 1, further comprising:
periodically executing a batch routine to synchronize data between the CRM system and the ERP system (see ¶ 62, ¶ 176-177 and claim 7).
Regarding claim 8, Gil discloses the computer-based method of claim 7, further comprising:
retrieving information from the ERP system using the sales organization picker microcomponent and plant picker microcomponent in between the execution of successive batch routines (see ¶ 33, ¶ 66 and ¶ 96).
Regarding claim 9, Gil discloses the computer-based method of claim 8, wherein the batch routine is executed daily (see ¶ 176-177).
Regarding claim 11, Gil discloses the computer-based method of claim 1, wherein the sales organization picker microcomponent is a real time function to fetch sales organization data from the ERP system (see ¶ 11-12, ¶ 80 and ¶ 200).
Regarding claim 12, Gil discloses the computer-based method of claim 1 1, wherein the plant picker microcomponent is a real time function to fetch plant availability data from the ERP system (see ¶ 10, ¶ 149 and ¶ 200).
Regarding claim 14, Gil discloses a computing system to integrate information stored in multiple database systems on behalf of an enterprise in real-time without the need for data synchronization or complex application programming interface (API) integration via a third party, wherein the multiple database systems comprise a customer relationship management (CRM) system of the enterprise and an enterprise resource planning (ERP) system of the enterprise (see Fig. 5-6, ¶ 50, ¶ 70, ¶ 100-101), processing devices and memory devices coupled to the processing devices, with one or more memory devices having microcomponent instructions stored thereon that, when executed by one or more processors of the one or more computing system is configured to (see ¶ 36), cause the one or more processing devices to:
wherein at least one of the microcomponents is configured to receive extensible markup language (XML) based service calls from the CRM system (see ¶ 78-79, ¶ 92-92, ¶ 113, ¶ 121), convert the XML format into ERP-native API calls and retrieve validated data from the ERP system (see ¶ 84, ¶ 180, ¶ 198).
Receive, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), a request to initiate a CRM transaction (see Abstract: a request from a network system for access real-time data is received; ¶ 7-9, ¶ 11, ¶ 56, ¶ 64, ¶ 69, ¶ 80-81, ¶ 89 and ¶ 120: a customer or partner initiates a transaction directly to the execution subsystem), wherein the CRM transaction is a configure, price, quote (CPQ) process having a workflow that is to be executed by the CRM system of an enterprise, wherein the ERP system maintains information relevant to the CRM transaction (see ¶ 8, ¶ 70: describes the system includes application or subsystems for enterprise resource planning (ERP) and customer relationship management (CRM) may provide or support functionality and maintain customer information in a database);
Determine, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), based on the CRM transaction, the sales organization picker microcomponent is associated with the workflow of the CRM transaction (see ¶ 78-80, ¶ 82 and ¶ 90);
Retrieve, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the sales organization picker microcomponent, information associated with the workflow of the CRM transaction from the ERP system (see ¶ 79, ¶ 96, ¶ 122 and ¶ 128-129);
providing, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), on behalf of the microcomponent, in real-time the information retrieved from the ERP system by the sales organization picker microcomponent to the CRM system in the first data format for use in the workflow of the CRM transaction (see ¶ 10, ¶ 62, ¶ 70-72, and ¶ 123-126);
determine, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the plant picker microcomponent is associated with the workflow of the CRM transaction (see ¶ 78-80, ¶ 127, ¶ 137).
Retrieve, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the plant picker microcomponent, retrieve additional information from the ERP system, wherein the additional information is associated with the workflow for the CRM transaction (see ¶ 88, ¶ 90, ¶ 96 and ¶ 149);
receiving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), a service call from the CRM system in a first data format (see ¶ 7-9);
converting, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the service call from the first data format to a second data format (see ¶ 93, ¶ 126, ¶ 202);
retrieving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the information associated with the workflow of the CRM transaction from the ERP system using the second data format (see ¶ 96, ¶ 129);
17providing, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), on behalf of the microcomponent, in real-time the additional information retrieved from the ERP system by the plant picker microcomponent to the CRM system for use in the workflow of the CRMby the second microcomponent to the CRM system for use in the workflow of the CRM transaction (see ¶ 10, ¶ 62-64, ¶ 72, and claim 1);
Receiving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), a web service call from the CRM system to the pricing and order simulation microcomponent using an XML format structure (see ¶ 7-10, ¶ 113, ¶ 162-163); and
Retrieving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), pricing data from the ERP system, and in response (see ¶ 96, ¶ 126), providing, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the pricing data in XML format to the CRM system (see ¶ 96, ¶ 124, ¶ 129).
Gil disclose the process execution component may include software or application for initiating business workflow by a transaction, a request, or a demand from a partner system, generating and maintaining the context of the transaction in real-time (see ¶ 79-80); and setting up unit price for a particular product (see ¶ 126).
Gil does not explicitly disclose wherein the CRM transaction is a configure, price, quote (CPQ) process have a workflow that is to be executed by the CRM system of the enterprise; however, Wilkins in an analogous art for generating product quotes discloses
wherein the CRM transaction is a configure, price, quote (CPQ) process having a workflow that is to be executed by the CRM system of an enterprise (see Abstract, ¶ 2-4, ¶ 7: configurator the generate a quote for a product or service, the quote including a quote workflow and quote attributes; ¶ 32: the CPQ systems are processed through a customer defined workflow). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil to include teaching of Wilkins in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more accurate pricing solution, enabling better decision making. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses an integrated network application designed and architected as a complete closed-loop system, it incorporate all of the features in one package required to execute and coordinate transactions accurately in the network and be able to monitor the performance of any given partner. It offers partners multiple connection options to minimize IT investment, reduce overhead, and increase adoption rates among partners. It supports direct, real-time connections to a number of enterprise resource planning (ERP), material requirement planning (MRP), supply chain management (SCM), customer relationship management (CRM), warehouse management systems (WMS), and enterprise application integration (EAI) applications or subsystems for direct back-end system integration. Communication with any existing system is possible using multiple electronic connection protocols, including enterprise application integration (EAI), electronic data interchange (EDI) files, flat file, and application connectors, so it does not require users to install and run software from their system (see ¶ 56-57); The enterprise component represents the enterprise and is integrated into the existing system of the enterprise. The enterprise component is operable to generate real-time data relevant to one or more transactions in which the enterprise is involved in the supply chain, and the partner component represent a partner and is integrated into the existing system of the partner; and the functionality of these components can be performed with suitable data processing facility running appropriate software and operating under the control of any suitable operating system (see ¶ 76).
Gil and Wilkins do not explicitly disclose the following limitations; however, Desai in an analogous art for managing applications discloses
install, by processors, from coupled memory devices with stored microcomponent instructions, a framework of microcomponents into the CRM system of the enterprise, further wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system (see ¶ 39, ¶ 72-75, ¶ 83, ¶ 93, ¶ 96: VBScript is one of the low code programming techniques).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins to include teaching of Desai in order to gain the commonly understood benefit of such adaption, such as providing the benefit of enhancing computation efficiency, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses a plurality of enterprise components for accessing real-time data of partner systems and retrieving data relevant to one or more transactions in which the partner is involved in the supply chain; and a network system of network may be implemented at least in part at each of enterprise domain. The network domain may be linked through a gateway to another network domain such as the service network may be linked to the supplier network through the respective network domains to route transaction between the networks (see ¶ 11-13, ¶ 45, and ¶ 126).
Gil, Wilkins and Desai do not explicitly disclose performing a price simulation process, however, Kemmer in an analogous art for simulating the cost of goods and services discloses
Perform, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), based on the information retrieved from the ERP system, using the sales organization picker microcomponent and the additional information retrieved from the ERP system using the plant picker microcomponent, performing a price simulation process using a pricing and order simulation microcomponent by (see ¶ 18-20 and ¶ 34). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins and Desai to include teaching of Kemmer in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more optimal solution, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses the real-time information within the supply chain can be used to modify or update the respective contexts for the transactions, and the partner coordinator may independently push out the real-time data to the network domain by cooperating with one or more existing legacy system at the customer domain (see ¶ 87).
Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton in an analogous art for software upgrading management discloses
upgrade, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the sales organization picker microcomponent, wherein upgrading the sales organization picker microcomponent does not affect the operation of the plant picker microcomponent (see col. 15, lines 18-55, claim 20).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
In addition, the phrases “wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system” are merely characterizing the type of the framework of microcomponents is directed to nonfunctional descriptive material because they cannot exhibit any functional interrelationship with the way the steps are performed. Therefore, it has been held that nonfunctional descriptive material will not distinguish the invention from prior art in term of patentability. (In re Gulack, 217 USPQ 401 (Fed. Cir. 1983), In re Ngai, 70 USPQ2d (Fed. Cir. 2004), In re Lowry, 32 USPQ2d 1031 (Fed. Cir. 1994); MPEP 2111.05).
Regarding claim 15, Gil discloses the computing system of claim 14, wherein at least one of the sales organization picker microcomponent and plant picker microcomponent are configurable (see ¶ 131).
Regarding claim 16, Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton discloses the computing system of claim 15, wherein each of the sales organization picker microcomponent and plant picker microcomponent are separately upgradable (see claim 6, claim 11).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Regarding claim 18, Gil discloses the computing system of claim 14, further comprising:
provide, by at least one of the sales organization picker microcomponent and plant picker microcomponent, bi-directional data exchange between the CRM system and the ERP system (see ¶ 100: exchanges and management of data between the components of the network; ¶ 126).
Regarding claim 19, Gil discloses the computing system of claim 18, wherein the bi-directional data exchange is in real time (see ¶ 8, ¶ 41, ¶ 86, ¶ 100, and ¶ 126).
Regarding claim 21, Gil discloses the computing system of claim 14, wherein the sales organization picker microcomponent is a real time function to fetch sales organization data from the ERP system (see ¶ 11-12, ¶ 80 and ¶ 200).
Regarding claim 22, Gil discloses the computing of claim 21, wherein the plant picker microcomponent is a real time function to fetch plant availability data from the ERP system (see ¶ 10, ¶ 149 and ¶ 200).
Regarding claim 23, Gil discloses the computing system of claim 22, further comprising:
subsequent to receiving a request to configure a product associated with the CPQ process, retrieve rule-based configuration options from the EPR system using a configuration microcomponent (see ¶ 90, ¶ 126-129 and ¶ 173).
Regarding claim 25, Gil discloses a computing system to integrate information stored in multiple data systems on behalf of an enterprise in real-time without the need for data synchronization or complex application programming interface (API) integration via a third party, wherein the multiple database systems comprise a configure, price, quote (CPQ) system of the enterprise and an enterprise resource planning (ERP) system of the enterprise (see Fig. 5-6, ¶ 50, ¶ 70, ¶ 100-101), the computing system comprising processing devices and memory devices coupled to the processing devices, with one or more memory devices having microcomponent instructions stored thereon that, when executed by one or more processors cause the one or more processors to:
wherein at least one of the microcomponents is configured to receive extensible markup language (XML) based service calls from the CRM system (see ¶ 78-79, ¶ 92-92, ¶ 113, ¶ 121), convert the XML format into ERP-native API calls and retrieve validated data from the ERP system (see ¶ 84, ¶ 180, ¶ 198).
Receive, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), a request to initiate a CRM transaction (see Abstract: a request from a network system for access real-time data is received; ¶ 7-9, ¶ 11, ¶ 56, ¶ 64, ¶ 69, ¶ 80-81, ¶ 89 and ¶ 120: a customer or partner initiates a transaction directly to the execution subsystem), wherein the CPQ transaction has a workflow that is to be executed by the CPQ system, wherein the ERP system of the enterprise maintains information relevant to the CPQ transaction, wherein the ERP system of the enterprise maintains information relevant to the CRM transaction (see ¶ 8, ¶ 70: describes the system includes application or subsystems for enterprise resource planning (ERP) and customer relationship management (CRM) may provide or support functionality and maintain customer information in a database);
Determine, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), based on the CPQ transaction, the sales organization picker microcomponent is associated with the workflow of the CPQ transaction (see ¶ 56, ¶ 78-80, ¶ 124-125 and ¶ 128);
Retrieve, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the sales organization picker microcomponent, information from the ERP system, wherein the information is associated with the workflow for the CPQ transaction (see ¶ 96 and ¶ 129);
P22PProvide, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), in real-time the information retrieved from the ERP system by the sales organization picker microcomponent to the CPQ system for use in the workflow of the CPQ transaction (see ¶ 10, ¶ 62, ¶ 70-72, and ¶ 123-126);
Determine, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), the plant picker microcomponent is associated with the workflow of the CPQ transaction (see ¶ 56, ¶ 69, ¶ 80-81, ¶ 129, and ¶ 188);
Retrieve, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), using the plant picker microcomponent, retrieve additional information from the ERP system, wherein the additional information is associated with the workflow for the CPQ transaction (see ¶ 88, ¶ 96 and ¶ 129);
provide, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), in real-time the additional information retrieved from the ERP system by the plant picker microcomponent to the CPQ system for use in the workflow of the CPQ transaction (see ¶ 10, ¶ 62-64, ¶ 72, and claim 1);
receiving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), a web service call from the CRM system to the pricing and order simulation microcomponent using an (XML) format structure (see ¶ 7-10, ¶ 162-163); and
retrieving, by processors, with microcomponent instructions stored on coupled memory devices (see ¶ 36), pricing data from the ERP system, and in response, providing the pricing data in XML format to the CRM system (see ¶ 96, ¶ 124, ¶ 129).
Gil disclose the process execution component may include software or application for initiating business workflow by a transaction, a request, or a demand from a partner system, generating and maintaining the context of the transaction in real-time (see ¶ 79-80); and setting up unit price for a particular product (see ¶ 126).
Gil does not explicitly disclose wherein the CRM transaction is a configure, price, quote (CPQ) process have a workflow that is to be executed by the CRM system of the enterprise; however, Wilkins in an analogous art for generating product quotes discloses
wherein the CRM transaction is a configure, price, quote (CPQ) process have a workflow that is to be executed by the CRM system of the enterprise (see Abstract, ¶ 2-4, ¶ 7: configurator the generate a quote for a product or service, the quote including a quote workflow and quote attributes; ¶ 32: the CPQ systems are processed through a customer defined workflow).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil to include teaching of Wilkins in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more accurate pricing solution, enabling better decision making. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses an integrated network application designed and architected as a complete closed-loop system, it incorporate all of the features in one package required to execute and coordinate transactions accurately in the network and be able to monitor the performance of any given partner. It offers partners multiple connection options to minimize IT investment, reduce overhead, and increase adoption rates among partners. It supports direct, real-time connections to a number of enterprise resource planning (ERP), material requirement planning (MRP), supply chain management (SCM), customer relationship management (CRM), warehouse management systems (WMS), and enterprise application integration (EAI) applications or subsystems for direct back-end system integration. Communication with any existing system is possible using multiple electronic connection protocols, including enterprise application integration (EAI), electronic data interchange (EDI) files, flat file, and application connectors, so it does not require users to install and run software from their system (see ¶ 56-57); The enterprise component represents the enterprise and is integrated into the existing system of the enterprise. The enterprise component is operable to generate real-time data relevant to one or more transactions in which the enterprise is involved in the supply chain, and the partner component represent a partner and is integrated into the existing system of the partner; and the functionality of these components can be performed with suitable data processing facility running appropriate software and operating under the control of any suitable operating system (see ¶ 76).
Gil and Wilkins do not explicitly disclose the following limitations; however, Desai in an analogous art for managing applications discloses
install, by processors, from coupled memory devices with stored microcomponent instructions, a framework of microcomponents into the CRM system of the enterprise, further wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system (see ¶ 39, ¶ 72-75, ¶ 83, ¶ 93, ¶ 96: VBScript is one of the low code programming techniques).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins to include teaching of Desai in order to gain the commonly understood benefit of such adaption, such as providing the benefit of enhancing computation efficiency, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses a plurality of enterprise components for accessing real-time data of partner systems and retrieving data relevant to one or more transactions in which the partner is involved in the supply chain; and a network system of network may be implemented at least in part at each of enterprise domain. The network domain may be linked through a gateway to another network domain such as the service network may be linked to the supplier network through the respective network domains to route transaction between the networks (see ¶ 11-13, ¶ 45, and ¶ 126).
Gil, Wilkins and Desai do not explicitly disclose performing a price simulation process, however, Kemmer in an analogous art for simulating the cost of goods and services discloses
Preform, by processors, with microcomponent instructions stored on coupled memory devices, based on the information retrieved from the ERP system using the sales organization picker microcomponent and the additional information retrieved from the ERP system using the plant picker microcomponent, a price simulation process using a pricing and order simulation microcomponent by (see ¶ 18-20 and ¶ 34). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins and Desai to include teaching of Kemmer in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more optimal solution, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Gil discloses the real-time information within the supply chain can be used to modify or update the respective contexts for the transactions, and the partner coordinator may independently push out the real-time data to the network domain by cooperating with one or more existing legacy system at the customer domain (see ¶ 87).
Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton in an analogous art for software upgrading management discloses
upgrade, by processors, with microcomponent instructions stored on coupled memory devices, the sales organization picker microcomponent, wherein upgrading the sales organization picker microcomponent does not affect the operation of the plant picker microcomponent (see col. 15, lines 18-55, claim 20).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
In addition, the phrases “wherein the framework of microcomponents comprises a sales organization picker microcomponent, a plant picker microcomponent, and a pricing and order simulation microcomponent, wherein the sales organization picker microcomponent is a first low-code integration link to the ERP system of the enterprise, wherein the plant picker microcomponent is a second low-code integration link to the ERP system, and wherein the pricing and order simulation microcomponent is a third low-code integration link to the ERP system” are merely characterizing the type of the framework of microcomponents is directed to nonfunctional descriptive material because they cannot exhibit any functional interrelationship with the way the steps are performed. Therefore, it has been held that nonfunctional descriptive material will not distinguish the invention from prior art in term of patentability. (In re Gulack, 217 USPQ 401 (Fed. Cir. 1983), In re Ngai, 70 USPQ2d (Fed. Cir. 2004), In re Lowry, 32 USPQ2d 1031 (Fed. Cir. 1994); MPEP 2111.05).
Regarding claim 26, Gil discloses the computing system of claim 25, wherein at least one of the sales organization picker microcomponent and plant picker microcomponent are configurable (see ¶ 131).
Regarding claim 27, Gil, Wilkins, Desai and Kemmer do not explicitly disclose the following limitations, however, Charlton discloses the computing system of claim 26, wherein at least one of the sales organization picker microcomponent and plant picker microcomponent are upgradable (see claim 6, claim 11).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Gil and in view of Wilkins, Desai and Kemmer to include teaching of Charlton in order to gain the commonly understood benefit of such adaption, such as providing the benefit of a more flexible solution for software management, in turn of operational efficiency. Since the combination of each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Regarding claim 29, Gil discloses the computing system of claim 25, further comprising: provide, by at least one of the sales organization picker microcomponent and plant picker microcomponent, bi-directional data exchange between the CPQ system and the ERP system (see ¶ 100: exchanges and management of data between the components of the network; ¶ 126).
Regarding claim 30, Gil discloses the computing system of claim 29, wherein the bi-directional data exchange is in real time (see ¶ 8, ¶ 41, ¶ 86, ¶ 100, and ¶ 126).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Underwood (WO 01/10082 A2) discloses a method for managing business objects in a system that includes a plurality of sub-activities and sub-activity logic adapted to generate an output based on an input received from user upon execution.
Battas et al., (US 2002/0107864) discloses a method for enabling an enterprise to run zero latency enterprise and allowing the enterprise to integrate its services, applications and data in real time.
Underwood (US 6601233 B1) discloses a method for generating software based on business components to carry out the capabilities of the logical business components and the functional interrelationship between the logical business components.
Sullivan et al., (US 2017/0330121) discloses a system for creating and accounting ERP frameworks for handling the multiple types of operational workflows that an ERP system may implement.
Beckerle et al., (CN 101076793) disclose system for constructing and managing data integration process comprises user interface, programming interface, service, and component, running engine and outer connector.
Misovski et al., (US 8938734 B2) discloses a method for providing user-driven configuration of application content package for installation on the client device and for integration with an application running on a client device.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PAN CHOY whose telephone number is (571)270-7038. The examiner can normally be reached 5/4/9 compressed work schedule.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jerry O'Connor can be reached on 571-272-6787. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/PAN G CHOY/Primary Examiner, Art Unit 3624