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 .
Response to Amendment
Applicant’s Remarks, filed June 1st, 2026, has been fully considered and entered. Accordingly, claims 1-4, 6-11, 13-18, and 20-21 are pending in the case. Claims 5, 12, and 19 were cancelled. Claims 1, 8, and 15 were amended. Claims 1, 8, and 15 are the independent claims.
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.
Claims 1-4, 6-11, 13-18, and 20-21 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 the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Regarding claim 1, the claim recites, in part, “transmitting, by the EBN and without conversion, the electronic SFR to an aircraft operator” (emphasis added), which renders the claim indefinite as it is unclear how the electronic SFR is transmitted by the EBN to an aircraft operator without conversion. As such, the claim is indefinite, and the Examiner requests clarification from Applicant as the Specification (Paragraph [0017]) does not provide sufficient support to discern the metes and bounds of the claim.
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-4, 6-11, 13-18, and 20-21 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Regarding claim 1,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim recites the following limitations directed to an abstract idea:
“populating, by a service seller, an electronics shop findings report (SFR) in a common message structure,” as drafted this recites a mentally performable process as an evaluation or judgement. One can mentally evaluate or judge populating a report.
“performing, by the airport operator, analysis on data retrieved from the electronic SFR,” as drafted this recites a mentally performable process as an evaluation or judgement. One can mentally evaluate or judge performing analysis on data.
At Step 2A, Prong Two:
The claim recites the following additional elements:
“transmitting, by the service seller, the electronic SFR to an electronic business network (EBN),” which is insignificant extra-solution activity as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
“receiving, by the EBN, the electronic SFR,” which is insignificant extra-solution activity as receiving of data (i.e. mere data gathering) such as 'obtaining information' and the particulars of the retrieved data are merely “selecting information … for collection, analysis, and display” as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
“transmitting, by the EBN an without conversion, the electronic SFR to an aircraft operator,” which is insignificant extra-solution activity as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
“directly ingesting and processing, within internal computer systems of the aircraft operator, the electronic SFR” which is insignificant extra-solution activity as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
With respect to the “receiving,” “transmitting,” “ingesting,” and “processing,” identified as insignificant extra-solution activity above when re-evaluated this element is well-understood, routine, and conventional as evidenced by the court cases in MPEP 2106.05(d)(II), “i. Receiving or transmitting data over a network, e.g., using the Internet to gather data, Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362 (utilizing an intermediary computer to forward information); … OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015) (sending messages over a network); 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);” and thus remains insignificant extra-solution activity that does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Regarding claim 2,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim further recites limitations corresponding to the judicial exception recited in parent claim 1.
At Step 2A, Prong Two:
The claim recites the following additional elements:
“wherein the electronic SFR is formatted in Extensible markup language (XML),” which is insignificant extra-solution activity as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Regarding claim 3,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim recites the following limitations directed to an abstract idea:
“wherein the analysis is statistical analysis,” as drafted this recites a mentally performable process as an evaluation or judgement. One can mentally evaluate or judge performing statistical analysis.
At Step 2A, Prong Two:
The claim does not recite any additional elements.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Regarding claim 4,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim recites the following limitations directed to an abstract idea:
“wherein the analysis is performed by artificial intelligence (AI),” as drafted this recites a mentally performable process as an evaluation or judgement. One can mentally evaluate or judge performing analysis on data by using artificial intelligence.
At Step 2A, Prong Two:
The claim does not recite any additional elements.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Regarding claim 6,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim recites the following limitations directed to an abstract idea:
“performing, by the EBN and as EBN analysis, analysis on data retrieved from the electronic SFR,” as drafted this recites a mentally performable process as an evaluation or judgement. One can mentally evaluate or judge performing analysis on data.
At Step 2A, Prong Two:
The claim does not recite any additional elements.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Regarding claim 7,
At Step 1:
The claim is directed to a “method” and thus directed to a statutory category.
At Step 2A, Prong One:
The claim further recites limitations corresponding to the judicial exception recited in parent claim 6.
At Step 2A, Prong Two:
The claim recites the following additional elements:
“transmitting, by the EBN and to the aircraft operator, a result of the EBN analysis,” which is insignificant extra-solution activity as identified in MPEP 2106.05(g) and does not provide integration into a practical application.
Viewing the additional limitations together and the claim as a whole, nothing provides integration into a practical application.
At Step 2B:
The conclusions for the mere implementation using a computer are carried over and does not provide significantly more.
Looking at the claim as a whole does not change this conclusion and the claim is ineligible.
Independent claims 8 and 15 and dependent claims 9-11, 13-14, 16-18, and 20-21 correspond to and recite the same judicial exception as claims 1-4, and 6-7, except that in claim 8 at Step 1, the claim is directed to a “non-transitory computer-readable medium” and thus directed to the statutory category of machine, and in claim 15 at Step 1, the claim is directed to a “system” and thus directed to the statutory category of machine. Therefore, claims 8-11, 13-18, and 20-21 are rejected accordingly.
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, 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.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1-4, 6-11, 13-18, and 20-21 are rejected under 35 U.S.C. 103 as being unpatentable over Papa et al. (US 2019/0026964 A1) in view of O’Malley et al. (US 2022/0237959 A1).
Regarding claim 1, Papa teaches a computer-implemented method, comprising:
populating, by a service seller, an electronic shop findings report (SFR) in a common message structure (see Papa, Paragraph [0035], “Data from multiple sources such as shop findings, cost analytics, and invoices are scanned and received by input component 106.” [Data from multiple sources such as shop findings may be scanned (i.e., populating an electronic shop findings report by a service seller).]);
However, Papa does not explicitly teach:
populating, by a service seller, an electronic shop findings report (SFR) in a common message structure;
O’Malley teaches:
populating, by a service seller, an electronic shop findings report (SFR) in a common message structure (see O’Malley, Paragraph [0035], “The device 120 may be further configured to process the image(s) of the label information to extract the engine module data and/or the LRU data. The device 120 is also configured to transmit the engine module data and/or the LRU data, once obtained, to the data acquisition and transmission unit 114 via a communication path 124. … the device 120 is configured to enforce that a proper data format is used to enter the data to the memory 116.” Paragraph [0036], “The data may be stored in the memory 116 using any suitable format including, but not limited to, in an Extensible Markup Language (XML) file.” [The engine module data and LRU data may be processed in a proper data format, which may be stored in an Extensible markup language (XML) file (i.e., common message structure).]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have combined Papa (teaching analytics system for aircraft line-replaceable unit maintenance optimization) in view of O’Malley (teaching system and method for tracking engine and aircraft component data), and arrived at a method that incorporates Extensible markup language. One of ordinary skill in the art would have been motivated to make such a combination for the purposes of improving tracking engine and aircraft component data (see O’Malley, Paragraph [0003]). In addition, both the references (Papa and O’Malley) teach features that are directed to analogous art and they are directed to the same field of endeavor, such as aircrafts. The close relation between both the references highly suggests an expectation of success.
The combination of Papa, and O’Malley further teaches:
transmitting, by the service seller, the electronic SFR to an electronic business network (EBN); receiving, by the EBN, the electronic SFR (see Papa, Paragraph [0039], “FIG. 3 illustrates an artificial intelligence based system 100 that includes a data conversion component 302 which can convert unstructured archived data to structured data that can be analyzed by the machine learning component through employment of optical character recognition (OCR) component 402, as illustrated in FIG. 4.” [The image files (i.e., electronic SFR) are transmitted and received by the data conversion component of the artificial intelligence system (i.e., electronic business network).] Also, see O’Malley, Paragraph [0034], “one or more client devices 120 are adapted to communicate with the data acquisition and transmission unit 114. … Each device 120 is configured to connect to the data acquisition and transmission unit 114 via a communication path 124,” Paragraph [0035], “Each device 120 is configured to read the labels 108 a, 108 b to obtain the label information associated therewith. The device 120 is then configured to extract the engine module data and/or the LRU data from the label information. … The device 120 is also configured to transmit the engine module data and/or the LRU data, once obtained, to the data acquisition and transmission unit 114 via a communication path 124. … The data acquisition and transmission unit 114 may in turn store the received data in the memory 116.” [The device is configured to transmit the engine module data and LRU data to the data acquisition and transmission unit, and the data acquisition and transmission unit is configured to receive the engine module data and LRU data.]);
transmitting, by the EBN and without conversion, the electronic SFR to an aircraft operator; directly ingesting and processing, within internal computer systems of the aircraft operator, the electronic SFR and performing, by the aircraft operator, analysis on data retrieved from the electronic SFR (see Papa, Paragraphs [0042]-[0045], “Users can actively identify which words or phrases are important or are synonyms to complement machine learning. FIG. 7 illustrates an example, non-limiting method 700 for building dynamic and interactive wordcloud that has drag and drop functionality. … FIG. 9 illustrates graph 900 for workscope clustering to identify cost errors. Graph 900 has three different cost levels and one data point that is misplaced but is difficult to identify without applying workscope clustering. LRU 902 depicts an improperly applied workscope only visible by manually reading and recognizing the issues,” [The user (i.e., aircraft operator) has access to the data, thus, indicating the electronic SFR was transmitted, by the EBN and without conversion. The user (i.e., aircraft operator) may interact with the data regarding the shop findings, thus, indicating the electronic SFR is directly ingested and processed within the internal computer systems of the aircraft operator.]).
Regarding claim 2, Papa in view of O’Malley teaches all the limitations of claim 1. O’Malley further teaches:
wherein the electronic SFR is formatted in Extensible markup language (XML) (see O’Malley, Paragraph [0036], “The data may be stored in the memory 116 using any suitable format including, but not limited to, in an Extensible Markup Language (XML) file.” [The data may be stored in an Extensible markup language (XML) file.]).
Regarding claim 3, Papa in view of O’Malley teaches all the limitations of claim 1. Papa further teaches:
wherein the analysis is statistical analysis (see Papa, Paragraph [0034], “Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determinate an action to be automatically performed.” [Statistical analysis may be implemented.]).
Regarding claim 4, Papa in view of O’Malley teaches all the limitations of claim 1. Papa further teaches:
wherein the analysis is performed by artificial intelligence (AI) (see Papa, Paragraph [0034], “A support vector machine (SVM) is an example of a classifier that can be employed. … Other directed and undirected model classification approaches include, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed.” [The analysis may be performed by a support vector machine, as well as other classification approaches (i.e., artificial intelligence).]).
Regarding claim 6, Papa in view of O’Malley teaches all the limitations of claim 1. Papa further teaches:
performing, by the EBN and as EBN analysis, analysis on data retrieved from the electronic SFR (see Papa, Paragraph [0041], “Text analytic and clustering algorithms are employed to determine causality between workscope, shop findings, applied service bulletins, costs, etc.” [Text analytics and clustering algorithms (i.e., analysis) may be performed on the converted data.]).
Regarding claim 7, Papa in view of O’Malley teaches all the limitations of claim 6. Papa further teaches:
transmitting, by the EBN and to the aircraft operator, a result of the EBN analysis (see Papa, Paragraph [0045], “an avatar component 1102, as illustrated in FIG. 11, can generate an avatar that interfaces with a user and provide suggestions to the user based on outputs of the AI model. For example, the avatar can remind the user that a set of LRU needs to be replaced and ask whether the user want the avatar to order replacements.” [The suggestions (i.e., a result of the EBN analysis) may be provided to the user (i.e., aircraft operator).]).
Regarding claims 8-11, 13-18, and 20-21, Papa teaches all of the limitations of claims 1-4, and 6-7, in method form rather than in computer-readable medium form and system form. Papa also discloses a computer-readable medium [0056] and system [0056]. Therefore, the supporting rationale of the rejection to claims 1-4, and 6-7, applies equally as well to those limitations of claims 8-11, 13-18, and 20-21.
Response to Arguments
Applicant’s Arguments, filed June 1st, 2026, have been fully considered, but are not persuasive.
Applicant argues on pages 7-8 of Applicant's Remarks that the amended claims are integrated into a practical application, and amount to significantly more than the abstract idea. The Examiner respectfully disagrees.
The abstract idea is not integrated into a practical application because the invention merely uses the computer such as a “non-transitory, machine-readable media,” and “memory” to facilitate performance of the abstract idea, and the specification (paragraphs [0017] and [0019], as cited by the Applicant) does not provide sufficient details such that one of ordinary skill in the art would recognize that the invention as claimed is an improvement, thus, it does not improve the functioning of the computer in any way (see MPEP 2106.04(d)(1)).
The limitations as claimed do not include limitations that are sufficient to amount to significantly more than the judicial exception because the limitations as claimed are recited at a high-level of generality and amounts to no more than mere instructions to apply the abstract idea to a computer environment (see MPEP 2106.05(f)).
Applicant argues on page 9 of Applicant's Remarks that the cited references do not teach or suggest “an electronic shop findings report (SFR) in a common message structure that is transmitted by an electronic business network (EBN) and without conversion to an aircraft operator and directly ingest[ed] and process[ed], within internal computer systems of the aircraft operator.” (emphasis added). The Examiner respectfully disagrees.
Applicant’s specification discloses in paragraph [0018], “the described approach generates an electronic SFR by a service seller in a common message structure (e.g., Extensible Markup Language (XML)).” As shown, a common message structure is an Extensible Markup Language (XML). Accordingly, O’Malley discloses in paragraph [0036], “The data may be stored in the memory 116 using any suitable format including, but not limited to, in an Extensible Markup Language (XML) file.” As shown, O’Malley discloses storing data in an Extensible Markup Language (XML) file (i.e., a common message structure).
Accordingly, in addition to the cited portions above, Papa discloses in paragraphs [0042]-[0044], “Users can actively identify which words or phrases are important or are synonyms to complement machine learning. FIG. 7 illustrates an example, non-limiting method 700 for building dynamic and interactive wordcloud that has drag and drop functionality. … FIG. 9 illustrates graph 900 for workscope clustering to identify cost errors. Graph 900 has three different cost levels and one data point that is misplaced but is difficult to identify without applying workscope clustering. LRU 902 depicts an improperly applied workscope only visible by manually reading and recognizing the issues.” As shown, the AI system (i.e., Electronic Business network) may allow the user (i.e., aircraft operator) to interact with the information that was received such as the shop findings mentioned above in paragraph [0035] of Papa. Accordingly, the user (i.e., aircraft operator) has access to the data, thus, indicating the electronic SFR was transmitted, by the EBN and without conversion. Lastly, the user may interact with information regarding the shop findings, which indicates the data is directly ingested and processed within the internal computer systems of the aircraft operator.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Avery et al. (US 2007/0124222 A1), which discloses integrated materials management for commercial aircraft fleets including access to real-time on-board systems information.
Foxford et al. (US 2004/0138792 A1), which discloses a system and method that efficiently captures, stores, and reports aerospace maintenance, repair, and overhaul data.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HUSAM TURKI SAMARA whose telephone number is (571)272-6803. The examiner can normally be reached on Monday - Thursday, Alternate Fridays.
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, Apu Mofiz can be reached on (571)-272-4080. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/HUSAM TURKI SAMARA/Examiner, Art Unit 2161
/APU M MOFIZ/Supervisory Patent Examiner, Art Unit 2161