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 .
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-20 are rejected under 35 U.S.C. 101 because the claimed invention is -directed to non-statutory subject matter. Claims 1-20 are directed to a judicial exception (i.e., a law of nature, natural phenomenon, or abstract idea) without significantly more.
Part I. 2A-prong one (Identify the Abstract Ideas)
The Alice framework, step 2A-Prong One (part 1 of Mayo test), here, the claims are analyzed to determine if the claims are directed to a judicial exception. MPEP §2106.04(a). In determining, whether the claims are directed to a judicial exception, the claims are analyzed to evaluate whether the claims recite a judicial exception (Prong One of Step 2A), and whether the claims recite additional elements that integrate the judicial exception into a practical application (Prong Two of Step 2A). See 2019 Revised Patent Subject Matter Eligibility Guidance (“PEG” 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50-57 (Jan. 7, 2019)).
Independent claims 1, 11, and 17 are directed to identifying anomalies and generating configuration files/workflows to eliminate the anomalies.
Under step 2A-Prong One (part 1 of Mayo test), here, the claimed invention in claim 1, 11, and 17 are directed to non-statutory subject matter because the claim(s) as a whole, considering all claim elements both individually and in combination, do not amount to significantly more than an abstract idea.
The above limitation falls within a mental process
Part II. 2A-prong two (additional elements that integrate the judicial exception into a practical application)
Under step 2A-Prong two (part 1 of Mayo test), this judicial exception is not integrated into a practical application under the second prong of Step 2A. In particular, the claims recite the additional elements beyond the recited abstract idea. Such as, “… processing system…hardware device…historical file…industrial system…workflow file…summary generation file…workflow update engine…non transitory computer readable medium”
The courts have recognized the following computer functions as a merely generic manner (e.g., at a high level of generality) and as insignificant extra-solution activity (i.e., "receiving, processing, storing, transmitting/notifying/displaying/presenting data" (MPEP 2106.05(d))
Accordingly, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. The claims are directed to an abstract idea with no significantly more elements.
As a result, Examiner asserts that claims 2-10, 12-16, 18-20 are similarly directed to the abstract idea. Since these claims are directed to an abstract idea, the Office must determine whether the remaining limitations “do significantly more” than describe the abstract idea.
Part III. Determine whether any Element, or Combination, Amounts to“Significantly More” than the Abstract Idea itself
The Alice framework, we turn to step 2B (Part 2 of Mayo) to determine if the claim is sufficient to ensure that the claim amounts to “significantly more" than the abstract idea itself.
Claim 1, 11, and 17 do not include any limitations amounting to significantly more than the abstract idea, alone. Claim 1, 11, and 17 do include various elements that are not directed to the abstract idea. These elements include“… processing system…hardware device…historical file…industrial system…workflow file…summary generation file…workflow update engine…non transitory computer readable medium” these amounts to generic computing elements performing generic computing functions.
In addition, Fig. 1 of the Applicant’s specifications detail any combination of a generic computer system program to perform the method (i.e., commercially available processors). Generically recited computer elements do not add a meaningful limitation to the abstract idea because the Alice decision noted that generic structures that merely apply abstract ideas are not significantly more than the abstract ideas.
The dependent claims of 2-10, 12-16, and 18-20 further limit the abstract idea without adding significantly more. Accordingly, the Examiner concludes that there are no meaningful limitations in the claims that transform the judicial exception into a patent eligible application such that the claim amounts to significantly more than the judicial exception itself.
Further, Examiner notes that the additional limitations, when considered as an ordered combination, add nothing that is not already present when looking at the additional elements individually.
Therefore, the dependent claims are rejected as ineligible subject matter under 35 U.S.C. 101 based on a rationale similar to independent claim 1, 11, and 17.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-8, 10, 17-19 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Eryurke et al. (US Pub. No. 2005/0197806) (hereinafter, Eryurke).
As per claim 1,
Eryurke teaches,
A method comprising:
receiving a configuration data update file having new configuration data corresponding to each of a plurality of assets operating in an industrial environment;
(paragraph 168, noting “… the rules development application 298 enables a user to create other rules based on experiences within the process plant being monitored. For example, if a user knows that a certain combination of SPM abnormal conditions or events indicates a certain problem in the process, the user can use the rules development application 298 to create an appropriate rule to detect this condition and, if desired, to generate an alarm or alert or to take some other action based on the detected existence of this condition…” Examiner noting: the new rules development application that the user generated is functioning as the “configuration data update file” of the current application)
generating a configuration change summary indicating change in existing configuration of at least one asset from among the plurality of assets, based on analysis of the new configuration data;
(Fig. 39 and paragraph 59, showing a summary of rules (i.e. configuration change))
processing an operational workflow file corresponding to the at least one asset, to determine any anomaly in historic operational data of the at least one asset due to the change in existing configuration of the at least one asset, wherein the operational workflow file comprises historic operational data of the at least one asset; and
(Fig. 13 and corresponding paragraphs, including 116,117, 118; noting on paragraph 117, “…In any event, a trend window, such as that of FIG. 13, enables a user to view the historical behavior for any SPM parameter. Depending upon the process, it is possible to characterize abnormal conditions, based upon the trend of different process variables…”)
updating the historic operational data of the at least one asset in accordance to the new configuration data to correct the anomaly
(paragraphs 167-171 and paragraphs 172-175 for clarity and examples).
As per claim 2,
Eureka teaches,
the method as claimed in claim 1, wherein the method comprises updating the existing configuration with the new configuration data in configuration data files of each of the plurality of assets
(Fig. 39 and paragraph 59, showing a summary of rules (i.e. configuration change))
As per claim 3,
Eureka teaches,
the method as claimed in claim 2, wherein the updating comprises rewriting the existing configuration with the new configuration data in the configuration data file of the at least one asset
(Fig. 39 and paragraph 59, showing a summary of rules (i.e. configuration change))
As per claim 4,
Eureka teaches,
the method as claimed in claim 1, wherein the anomaly indicates one or more instances in the historic operation where the asset was correctly executed in accordance to the existing configuration, but the asset is determined to have been incorrectly operated in view of the new configuration data
(paragraph 111 in its entirety and surrounding paragraphs)
As per claim 5,
Eureka teaches,
the method as claimed in claim 1, wherein the generating a configuration change summary comprises comparing the new configuration data of the at least one asset with the existing configuration of the at least one asset to determine the change in existing configuration of the at least one asset
(paragraphs 117-119)
As per claim 6,
Eureka teaches,
the method as claimed in claim 1, wherein the method comprises validating the configuration data update file to determine compatibility of the configuration data file
(paragraphs 178, 181-183)
As per claim 7,
Eureka teaches,
the method as claimed in claim 6, wherein the validating comprises a preliminary check to verify that the configuration data update file is in a predefined format
(paragraphs 176-178)
As per claim 8,
Eureka teaches,
The method as claimed in claim 7, wherein the validating comprises:
determining if the configuration data update file includes minimum predefined parameters of configuration data of each of the plurality of assets; and
(claims 16 and 17)
upon determining that the configuration data update file does not include the minimum predefined parameters, the method comprises generating a diagnostic report indicating missing predefined parameters of configuration data
(claim 29)
As per claim 10,
Eureka teaches,
the method as claimed in claim 1, wherein the method comprises generating a report based on the new configuration data of the at least one asset
(paragraphs 117-119)
As per claim 17,
Eureka teaches,
determining a change in existing operational control data of at least one process from among a plurality of processes operating in an industrial environment, based on analysis of a new operational control data of the at least one process;
(paragraph 168)
processing an operational workflow file associated with the at least one process, to determine any anomaly in historic operational data of the at least one process due to the change in existing operational control data of the at least one process, wherein the operational workflow file comprises historic operational data of the at least one process when executed according to the existing operational control data;
(Fig. 13 and corresponding paragraphs, including 116,117, 118; noting on paragraph 117, “…In any event, a trend window, such as that of FIG. 13, enables a user to view the historical behavior for any SPM parameter. Depending upon the process, it is possible to characterize abnormal conditions, based upon the trend of different process variables…”)
updating the historic operational data of the at least one process in accordance with the new operational control data to correct the anomaly; and
(paragraphs 167-171 and paragraphs 172-175 for clarity and examples).
updating the existing operational control data with the new operational control data in an operational control data file of the at least one process
(Paragraph 111 in its entirety).
As per claim 18,
Eureka teaches,
the non-transitory computer readable medium as claimed in claim 17, wherein the analysis comprises comparing the new operational control data of the at least one process with the existing operational control data of the at least one process to determine the change in existing operational control data of at least one process
(paragraphs 117-119).
As per claim 19,
Eureka teaches,
the non-transitory computer readable medium as claimed in claim 17, wherein the anomaly indicates one or more instances in the historic operation where an asset was correctly executed in accordance to the existing operational control data, but the asset is determined to have been incorrectly operated in view of the new operational control data
(paragraph 111 in its entirety and surrounding paragraphs)
Claim Rejections - 35 USC § 103
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, 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 9, 11-16, and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Eryuke as applied to claims 1-8, 10, 17-19 above, and further in view of Nixon et. Al. (US Pub. No. 2017/0115648) (hereinafter, Nixon).
As per claim 9,
Eryuke does not explicitly teach; however, Nixon does teach,
the method as claimed in claim 1, wherein the generating a configuration change summary comprises:
determining an upload setting of the configuration data update file, the upload setting being one of a manual upload setting and an auto-upload setting;
(Abstract)
for the upload setting being the manual upload setting, generating the configuration change summary on receiving a first prompt from a user; and
for the upload setting being the auto-upload setting, auto generate the configuration change summary
(paragraph 15, noting “…Based on the analyses, the process control system big data system may be able to automatically provide in-depth knowledge discovery, and may suggest changes to or additional entities for the process control system. Additionally, or alternatively, the process control system big data system may perform actions (e.g., prescriptive, predictive, or both) based on the knowledge discovery. The process control system big data system may also enable and assist users in performing manual knowledge discovery, and in planning, configuring, operating, maintaining, and optimizing the process plant and resources associated therewith…”)
Therefore, it would have been obvious to one of ordinary skill in the art at the time of filing to incorporate the teachings of Nixon within the invention of Eryuke with the motivation of optimizing the process control system or plant. (see, Nixon Abstract)
As per claim 11,
Eureka teaches,
A system comprising:
a summary generation engine to receive a configuration data update file having new configuration data corresponding to each of a plurality of assets operating in an environment;
(paragraph 168, noting “… the rules development application 298 enables a user to create other rules based on experiences within the process plant being monitored. For example, if a user knows that a certain combination of SPM abnormal conditions or events indicates a certain problem in the process, the user can use the rules development application 298 to create an appropriate rule to detect this condition and, if desired, to generate an alarm or alert or to take some other action based on the detected existence of this condition…” Examiner noting: the new rules development application that the user generated is functioning as the “configuration data update file” of the current application)
Eureka does not explicitly teach; however, Nixon does teach,
determine an upload setting of the configuration data update file, the upload setting being one of a manual upload setting and an auto-upload setting;
(Abstract)
for the upload setting being the manual upload setting,
generate a configuration change summary on receiving a first prompt from a user, wherein the configuration change summary indicates change in existing configuration of at least one asset from among the plurality of assets, based on analysis of the new configuration data;
and
for the upload setting being the auto-upload setting,
auto generate the configuration change summary;
(paragraph 15, noting “…Based on the analyses, the process control system big data system may be able to automatically provide in-depth knowledge discovery, and may suggest changes to or additional entities for the process control system. Additionally, or alternatively, the process control system big data system may perform actions (e.g., prescriptive, predictive, or both) based on the knowledge discovery. The process control system big data system may also enable and assist users in performing manual knowledge discovery, and in planning, configuring, operating, maintaining, and optimizing the process plant and resources associated therewith…”)
Therefore, it would have been obvious to one of ordinary skill in the art at the time of filing to incorporate the teachings of Nixon within the invention of Eryuke with the motivation of optimizing the process control system or plant. (see, Nixon Abstract)
Eureka teaches,
a workflow update engine to
update the existing configuration of the at least one asset with the new configuration data in a configuration data file of the at least one asset, wherein the configuration data file comprises existing configuration data of the at least one asset.
(Paragraph 111 in its entirety)
As per claim 12,
Eureka teaches,
the system as claimed in claim 11, wherein the workflow update engine is to:
analyze an operational workflow file corresponding to the at least one asset, to determine any anomaly in historic operational data of the at least one asset due to the change in existing configuration of the at least one asset, wherein the operational workflow file comprises historic operational data of the at least one asset; and
(Fig. 13 and corresponding paragraphs, including 116,117, 118; noting on paragraph 117, “…In any event, a trend window, such as that of FIG. 13, enables a user to view the historical behavior for any SPM parameter. Depending upon the process, it is possible to characterize abnormal conditions, based upon the trend of different process variables…”)
update the historic operational data of the at least one asset in accordance to the new configuration data to correct the anomaly.
(paragraphs 167-171 and paragraphs 172-175 for clarity and examples).
As per claim 13,
Eureka does not teach; however, Nixon does teach,
the system as claimed in claim 11, wherein for the upload setting being the manual upload setting, the workflow update engine is to perform the analysis of the operational workflow file corresponding to the at least one asset upon receiving a second prompt from the user
(Paragraph 15, see claim 11 notations for clarity)
Therefore, it would have been obvious to one of ordinary skill in the art at the time of filing to incorporate the teachings of Nixon within the invention of Eryuke with the motivation of optimizing the process control system or plant. (see, Nixon Abstract)
As per claim 14,
Eureka does not explicitly teach; however, Nixon does teach,
the system as claimed in claim 11, wherein for the upload setting being the manual upload setting, the workflow update engine is to update the historic operational data of the at least one asset in accordance to the new configuration data to correct the anomaly in response to receiving a third prompt from the user
(Paragraph 15, see claim 11 notations for clarity)
Therefore, it would have been obvious to one of ordinary skill in the art at the time of filing to incorporate the teachings of Nixon within the invention of Eryuke with the motivation of optimizing the process control system or plant. (see, Nixon Abstract)
As per claim 15,
Eureka teaches,
the system as claimed in claim 11, wherein the system comprises a display engine to display the configuration change summary of the at least one asset on a display unit coupled to the display engine
(Fig. 39 and paragraph 59, showing a summary of rules (i.e. configuration change))
As per claim 16,
Eureka teaches,
the system as claimed in claim 11, wherein the system comprises a download engine to download the configuration data update file in a prespecified format
(Fig. 39)
As per claim 20,
Eureka does not explicitly teach; however, Nixon does teach,
the non-transitory computer readable medium as claimed in claim 17, wherein the instructions, when executed by the processor, cause the processor to perform operations comprising:
receiving a user input to initiate the processing of the operational workflow file associated to the at least one process
(paragraph 15).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of filing to incorporate the teachings of Nixon within the invention of Eryuke with the motivation of optimizing the process control system or plant. (see, Nixon Abstract)
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ZAHRA ELKASSABGI whose telephone number is (571)270-7943. The examiner can normally be reached Monday through Friday 11:30 to 8:00.
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, Rob Wu can be reached at 571.272.6045. 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.
ZAHRA . ELKASSABGI
Examiner
Art Unit 3623
/RUTAO WU/Supervisory Patent Examiner, Art Unit 3623
Prosecution Insights