Prosecution Insights
Last updated: October 04, 2026
Application No. 18/941,681

FLEET VEHICLE WITH MONITORING SYSTEM

Final Rejection §112
Filed
Nov 08, 2024
Priority
Dec 13, 2012 — provisional 61/736,999 +4 more
Examiner
SWEENEY, BRIAN P
Art Unit
3668
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
The Heil Co.
OA Round
2 (Final)
93%
Grant Probability
Favorable
3-4
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 93% — above average
93%
Career Allowance Rate
737 granted / 789 resolved
+41.4% vs TC avg
Moderate +8% lift
Without
With
+7.6%
Interview Lift
resolved cases with interview
Fast prosecutor
1y 11m
Avg Prosecution
10 currently pending
Career history
802
Total Applications
across all art units

Statute-Specific Performance

§101
20.4%
-19.6% vs TC avg
§103
20.0%
-20.0% vs TC avg
§102
20.0%
-20.0% vs TC avg
§112
34.1%
-5.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 789 resolved cases

Office Action

§112
Notice of Pre-AIA or AIA Status The present application is being examined under the pre-AIA first to invent provisions. DETAILED ACTION Status of the Claims This action is in response to applicant’s filing on July 22, 2026. Claims 1, 3, 5-10 and 12-22 are pending. Response to Arguments Applicant’s arguments, see page 2, filed July 22, 2026, with respect to 35 U.S.C. 101 have been fully considered and are persuasive. The rejection of claims 1-19 has been withdrawn. Applicant’s arguments, see page 2, filed July 22, 2026, with respect to 35 U.S.C. 112 have been fully considered and are persuasive. The rejection of claims 1-19 with regard to “vehicle monitoring apparatus” has been withdrawn in view of applicant’s amendments. Applicant’s arguments, see page 2, filed July 22, 2026, with respect to 35 U.S.C. 102 and 35 U.S.C. 103 have been fully considered and are persuasive. The rejection of claims 1, 7-9 and13-19 has been withdrawn. Applicants’ arguments filed July 22, 2026, have been fully considered but they are not persuasive. With respect to 35 U.S.C. 112, the examiner still finds that the cited paragraph does not support the claim limitations. In addition, applicant’s amendments have caused new 35 U.S.C. 112 rejections. Claim Interpretation The following is a quotation of 35 U.S.C. 112(f): (f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph: An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked. As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph: (A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function; (B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and (C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function. Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function. Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function. Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “a vehicle activity information system configured to” in claims 1 and 19. A review of the specification yields the following: “vehicle activity information system configured to”; ¶ [0011] states “A vehicle activity information system is disclosed. In an embodiment, the system includes a processor; a data bus coupled to the processor; and a non-transitory computer-usable tangible storage device storing computer program code, the computer program code comprising program instructions executable by the processor. The computer program instructions comprise of instructions to: collect driver and vehicular information; analyze the collected vehicular and driver information; and configure parameters for displaying the collected driver and vehicular parameters to improve driving behavior.” Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof. If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. Claim Rejections - 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112: The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention. Claims 1, 3, 5-10 and 12-22 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention. Regarding claim 1, the claim recites the phrase “selecting, from a plurality of computing devices that are remote from the vehicle, a particular computing device based on the vehicle being within a geofence associated with the particular computing device” The claim limitation is not supported by the specification as the specification merely describes a way to “create a geofence for a fleet group, wherein the geofence comprises at least one person or entity for email notification of an event.” The specification does not clearly define entity, but it would not be a computing device as an entity is notified via email and not selected dynamically. In addition, the specification is silent as to “selecting, from a plurality of computing devices that are remote from the vehicle, a particular computing device”. The examiner can find no mention of this in the specification to describe how such is done. Therefore, the claim as drafted not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor had possession of the claimed invention. Claims 3, 5-10, 12-18 and 20 are rejected as being dependent on a rejected base claim. Regarding claim 19, the claim recites the phrase “selecting, from a plurality of computing devices that are remote from the vehicle, a particular computing device based on the vehicle being within a geofence associated with the particular computing device” The claim limitation is not supported by the specification as the specification merely describes a way to “create a geofence for a fleet group, wherein the geofence comprises at least one person or entity for email notification of an event.” The specification does not clearly define entity, but it would not be a computing device as an entity is notified via email and not selected dynamically. In addition, the specification is silent as to “selecting, from a plurality of computing devices that are remote from the vehicle, a particular computing device”. The examiner can find no mention of this in the specification to describe how such is done. Therefore, the claim as drafted not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor had possession of the claimed invention. Claims 21-22 are rejected as being dependent on a rejected base claim. Conclusion Applicants’ 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 nonprovisional extension fee (37 CFR 1.17(a)) 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 mailing date of this final action. Inquire Any inquiry concerning this communication or earlier communications from the examiner should be directed to BRIAN P SWEENEY whose telephone number is (313)446-4906. The examiner can normally be reached on Monday-Thursday from 7:30AM to 5:00PM. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, James J. Lee, can be reached at telephone number 571-270-5965. 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 Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center to authorized users only. Should you have questions about access to the USPTO patent electronic filing system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). Examiner interviews are available via a variety of formats. See MPEP § 713.01. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) Form at https://www.uspto.gov/InterviewPractice. /BRIAN P SWEENEY/Primary Examiner, Art Unit 3668
Read full office action

Prosecution Timeline

Nov 08, 2024
Application Filed
Apr 22, 2026
Non-Final Rejection mailed — §112
Jul 06, 2026
Interview Requested
Jul 13, 2026
Applicant Interview (Telephonic)
Jul 14, 2026
Examiner Interview Summary
Jul 22, 2026
Response Filed
Sep 18, 2026
Final Rejection mailed — §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12746924
ROAD VEHICLE IMPLEMENTING A LAUNCH CONTROL PROCEDURE AND CORRESPONDING CONTROL METHOD
1y 6m to grant Granted Sep 29, 2026
Patent 12731482
Systems and Methods for Improved Traffic Conditions Visualization
2y 1m to grant Granted Sep 08, 2026
Patent 12722673
SYSTEMS AND METHODS FOR MONITORING AND VALIDATING STATUS OF WHEEL DETECTOR DEVICES IN A CLASSIFICATION YARD
2y 3m to grant Granted Sep 01, 2026
Patent 12715457
VEHICLE CONTROL SYSTEM AND METHOD, AND VEHICLE
2y 1m to grant Granted Aug 25, 2026
Patent 12703456
Method for Operating a Drive Unit of an Electric Bicycle
3y 4m to grant Granted Aug 11, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
93%
Grant Probability
99%
With Interview (+7.6%)
1y 11m (~0m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 789 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month