Prosecution Insights
Last updated: November 11, 2026
Application No. 18/882,576

METHOD AND DEVICE FOR TOOL DATA EXCHANGE

Non-Final OA §102
Filed
Sep 11, 2024
Priority
Sep 14, 2023 — DE 102023124850.2
Examiner
BROWN, MICHAEL J
Art Unit
2115
Tech Center
2100 — Computer Architecture & Software
Assignee
Dmg Mori Digital GmbH
OA Round
1 (Non-Final)
88%
Grant Probability
Favorable
1-2
OA Rounds
5m
Est. Remaining
97%
With Interview

Examiner Intelligence

Grants 88% — above average
88%
Career Allowance Rate
935 granted / 1063 resolved
+33.0% vs TC avg
Moderate +9% lift
Without
With
+8.7%
Interview Lift
resolved cases with interview
Typical timeline
2y 7m
Avg Prosecution
16 currently pending
Career history
1082
Total Applications
across all art units

Statute-Specific Performance

§101
10.3%
-29.7% vs TC avg
§103
46.4%
+6.4% vs TC avg
§102
26.3%
-13.7% vs TC avg
§112
2.0%
-38.0% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1063 resolved cases

Office Action

§102
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 . Information Disclosure Statement The information disclosure statement (IDS) submitted on 9/11/2024 was filed. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Claim Rejections - 35 USC § 102 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 (i.e., changing from AIA to pre-AIA ) 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 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. Claim(s) 1-4 and 7-21 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Lochbihler (US PGPub 2024/0061397). As to claim 1 Lochbihler discloses a method for processing tool data (tool data; see paragraph 0124, line 4) on a machine tool (machine tools 3a,3b; see Fig. 1) having a data interface (data interface device 2, see Fig. 1) for connection to a tool management system (tool data management device 1, see Fig. 1), wherein the method comprises the steps of: acquiring a unique tool identifier, WID (tool ID; see paragraph 0041, line 3), of a tool (tool 4, see Fig, 2) to be picked up (see paragraph 0152, lines 1-7 and paragraph 0162, lines 1-6); matching the acquired WID with previously known tool identification data of the machine tool (see paragraph 0152, lines 7-10); if it is determined that the tool to be picked up is not yet known and/or updated tool data for the WID are available (see paragraph 0152, lines 10-11): automatically, via the data interface, retrieving tool data directly from the tool management system based on the acquired WID or automatically retrieving the tool data directly from the tool to be picked up (see paragraph 0152, lines 10-15 and paragraph 0153, lines 1-5); determining a loading location (magazine slot) for the tool to be picked up based on the retrieved tool data and preferably, picking up the tool at the determined loading location (see paragraphs 0141-0143). As to claim 2 Lochbihler discloses the method according to claim 1, wherein acquiring the WID comprises scanning a tool identification identifier of the tool to be picked up (see paragraph 0152, lines 1-7). As to claim 3 Lochbihler discloses the method according to claim 1, wherein the tool management system is an external tool management system for providing data from the cloud and the data interface is a tool data interface which is connected to the external tool management system via a network connection (see paragraph 0065, lines 1-5 and paragraph 0066, lines 4-12). As to claim 4 Lochbihler discloses the method according to claim 1, wherein the tool data comprise measured values and/or setting values of the tool which have been determined by an external device, in particular a presetting, balancing or shrinking device (see paragraphs 0096-0100). As to claim 7 Lochbihler discloses the method according to claim 1, wherein a predetermined setup location for the tool to be replaced is determined (see paragraph 0045, lines 4-8 and paragraph 0141, lines 1-6). As to claim 8 Lochbihler discloses the method according to claim 1, wherein the method additionally determines a setup sequence of the tools depending on a machining assignment, so that the loading locations of the tools are determined according to the machining assignment (see paragraphs 0141 and 0142). As to claim 9 Lochbihler discloses the method according to claim 1, wherein the previously known tool identification data are stored on a memory (storage units 311a,311b; see Fig. 1) on the machine tool, in particular an internal memory of the machine tool or the machine tool controller (see paragraph 0139, lines 1-7). As to claim 10 Lochbihler discloses the method according to claim 1, wherein the WID and/or tool data are attached directly to the tool or tool holder (tool changing device 322, see Fig. 1) in a machine- readable manner in order to be retrieved by scanning (see paragraph 0152, lines 5-7). As to claim 11 Lochbihler discloses the method according to claim 1, wherein the tool data and/or the WID are stored in a database (storage unit 311); the tool data and/or the WID are permanently attached to the tool, in particular as an engraved code or printed 2D code; the tool data and/or the WID are temporarily stored on the tool, in particular as a printed sticker; and/or the tool data and/or the WID are stored on a data carrier associated with the tool, in particular an RFID chip (see paragraph 0090, lines 1-5 and paragraph 0152, lines 1-7). As to claim 12 Lochbihler discloses the method according to claim 1, wherein the 2D code is a data matrix code coding or a QR code coding (see paragraph 0090, lines 1-5). As to claim 13 Lochbihler discloses the method according to claim 1, wherein the tool data are retrieved via a direct data connection so that they arrive directly in the machine tool and are directly available there for further processing, wherein preferably the tool data are stored on the machine tool side after the retrieval and are used in the execution of a machining assignment (see paragraph 0142, lines 2-12). As to claim 14 Lochbihler discloses the method according to claim 1, wherein the data interface is a tool data interface which corresponds to the UPC UA, Open Platform Communications Unified Architecture, and wherein the interface comprises an OPC UA server (see paragraphs 0027-0029). As to claim 15 Lochbihler discloses the method according to claim 1, wherein the UPC UA, Open Platform Communications Unified Architecture, is used for the communication with the tool management system and in particular for retrieving the tool data (see paragraphs 0027-0029). As to claim 16 Lochbihler discloses the method according to claim 1, wherein the tool data are retrieved from an OPC UA server via an OPC UA client as an OPC UA service call (see paragraphs 0027-0029). As to claim 17 Lochbihler discloses the method according to claim 1, wherein the tool data are converted into an input format after the retrieval, said input format being predefined depending on the machine tool controller used (see paragraph 0101, lines 5-15). As to claim 18 Lochbihler discloses a non-transitory computer readable medium, storing instructions for processing tool data (tool data; see paragraph 0124, line 4) on a machine tool (machine tools 3a,3b; see Fig. 1) having a data interface (data interface device 2, see Fig. 1) for connection to a tool management system (tool data management device 1, see Fig. 1), wherein the instructions, when executed by a control device of a numerically controlled machine tool, cause said machine tool to carry out a process (see paragraph 0017, lines 1-10) comprising: acquiring a unique tool identifier, WID (tool ID; see paragraph 0041, line 3), of a tool (tool 4, see Fig, 2) to be picked up (see paragraph 0152, lines 1-7 and paragraph 0162, lines 1-6); matching the acquired WID with previously known tool identification data of the machine tool (see paragraph 0152, lines 7-10); if it is determined that the tool to be picked up is not yet known and/or updated tool data for the WID are available (see paragraph 0152, lines 10-11): automatically, via the data interface, retrieving tool data directly from the tool management system based on the acquired WID or automatically retrieving the tool data directly from the tool to be picked up (see paragraph 0152, lines 10-15 and paragraph 0153, lines 1-5); determining a loading location (magazine slot) for the tool to be picked up based on the retrieved tool data and preferably, picking up the tool at the determined loading location (see paragraphs 0141-0143). As to claim 19 Lochbihler discloses a control device (control devices 31a,31b; see Fig. 1) for a machine tool (machine tools 3a,3b; see Fig. 1) having a data interface (data interface device 2, see Fig. 1) for connection to a tool management system (tool data management device 1, see Fig. 1) and to an application-based control system (cloud-based tool data management device; see paragraph 0019, line 5), said control device being configured to: acquire a unique tool identifier, WID (tool ID; see paragraph 0041, line 3), of a tool (tool 4, see Fig, 2) to be picked up (see paragraph 0152, lines 1-7 and paragraph 0162, lines 1-6); match the acquired WID with previously known tool identification data of the machine tool (see paragraph 0152, lines 7-10); if it is determined that the tool to be picked up is not yet known and/or updated tool data (tool data; see paragraph 0124, line 4) for the WID are available (see paragraph 0152, lines 10-11): automatically, via the data interface, retrieving tool data directly from the tool management system based on the acquired WID or automatically retrieving the tool data directly from the tool to be picked up (see paragraph 0152, lines 10-15 and paragraph 0153, lines 1-5); determine a loading location (magazine slot) for the tool to be picked up based on the retrieved tool data and preferably, pick up the tool at the determined loading location (see paragraphs 0141-0143). As to claim 20 Lochbihler discloses the control device according to claim 19, wherein the data interface is a tool data interface which corresponds to the UPC UA, Open Platform Communications Unified Architecture, and wherein the interface comprises an OPC UA server (see paragraphs 0027-0029). As to claim 21 Lochbihler discloses the control device of claim 19, wherein the control device is part of the machine tool (see Fig. 1 and paragraph 0124, lines 7-8). Allowable Subject Matter Claims 5 and 6 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. The following is a statement of reasons for the indication of allowable subject matter: Lochbihler fails to specifically disclose the method wherein in order to create a difference list, the tools required for a machining assignment are compared with the tools already present, and wherein one or more tools to be replaced are determined on the basis of the difference list (in regards to dependent claim 5). Accordingly, dependent claim 5 includes allowable subject matter. Further, Lochbihler fails to specifically disclose the method wherein the method initially comprises the step of scanning an NC program for required tools and preferably creating a corresponding difference list (in regards to dependent claim 6). Accordingly, dependent claim 6 includes allowable subject matter. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to Michael J. Brown whose telephone number is (571)272-5932. The examiner can normally be reached Monday-Thursday from 5:30am-4:00pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kamini Shah can be reached at (571)272-2279. 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. /Michael J Brown/ Primary Examiner, Art Unit 2115
Read full office action

Prosecution Timeline

Sep 11, 2024
Application Filed
Oct 27, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12782897
SCADA WEB HMI SYSTEM
2y 9m to grant Granted Nov 03, 2026
Patent 12782919
METHODS AND APPARATUS FOR MANAGING THE COOLING OF A DISTRIBUTED COOLING SYSTEM
3y 6m to grant Granted Nov 03, 2026
Patent 12782978
FLUID DISPENSING SYSTEM
2y 11m to grant Granted Nov 03, 2026
Patent 12776658
ENERGY DISTRIBUTION SYSTEM INCLUDING SOURCE PRIORITIZATION
2y 8m to grant Granted Oct 27, 2026
Patent 12769273
Method, Devices, Computer Program and Computer-Readable Medium for Using Configurable Logic for Modular Setup of a Technical Installation
2y 10m to grant Granted Oct 20, 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

1-2
Expected OA Rounds
88%
Grant Probability
97%
With Interview (+8.7%)
2y 7m (~5m remaining)
Median Time to Grant
Low
PTA Risk
Based on 1063 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