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 .
Continued Examination Under 37 CFR 1.114
A request for continued examination (RCE) 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 submission has been entered.
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-2, 4-10, 12-20 rejected under 35 U.S.C. § 101 are directed to an abstract idea without significantly more.
The claims do not provide significantly more than the judicial exception under the subject matter eligibility two-part statutory analysis, as provided below.
Regarding Step 1,
Step 1 addresses whether the claims are directed to one of the four statutory categories of invention, i.e., process, machine, manufacture, or composition of matter according to MPEP §2106.03. The claims fall within the four statutory categories.
Regarding Step 2A [prong 1],
The claimed invention recites an abstract idea according to MPEP §2106.04. Independent claims for the same abstract features, is provided below for the following claim limitations, as an abstract idea.
Claims 1, 6, 14 & 15:
A process for sharing task related information between different parties of a project comprising:
extracting task dependency data for a first task in a first proprietary data format;
translating the extracted task dependency data into a common data structure to enable computational interoperability;
maintaining, for the construction project, at least shared model information of an end result of the construction project, shared information of responsible parties involved, and a shared workflow, wherein the shared model information comprises at least, per a part, a part identifier, which is unique within the construction project, said part representing a piece for the end result of the construction project in a model of the end result; the shared workflow comprises a plurality of tasks, a task representing a piece of work to be done or undertaken for the construction project, the task having a task identifier, which is unique within the construction project, and comprising at least an indication of a party responsible for the task, and dependency information indicating one or more dependent tasks, a dependent task being either a preceding task or a following task, wherein the tasks are in the shared workflow in an order in which a preceding task has to be completed before the piece of work the task represents can start, and wherein the shared workflow associates tasks, per a task, at least with one of a part identifier, a shared resource in the construction project and a shared location; and providing, per a pair of a first task and a dependent task of the first task, a responsible party of the dependent task with access rights to task related information of a responsible party of the first task; and providing, per the pair of a first task and the dependent task, the responsible party of the first task with access rights to task related information of the responsible party of the dependent task;
wherein the read-only access rights to the task related information of the first task are granted automatically to the responsible party of the dependent task, and all other task related information for other tasks of the responsible party of the first task remains inaccessible to the responsible party of the dependent task, and wherein the read-only access rights to the task related information of the dependent task are granted automatically to the responsible party of the first task, and all other task related information for other tasks of the responsible party of the dependent task remains inaccessible to the responsible party of the first task; determining, in response to completing a piece of work of the first task, end result information of the piece of work; and updating the task related information of the first task by adding the end result information to the task related information of the first task, such that the responsible party of the dependent task is made aware of the end result information.
The claim limitations above, under its broadest reasonable interpretation, fall under “Certain Methods of Organizing Human Activities” grouping of abstract ideas, and includes at least managing personal behavior or relationships or interactions between people (including social activities, teaching, and following rules or instructions). See MPEP §2106.04(a)(2)(II).
But for the recitation of generic implementation of computer system components, the claimed invention merely recites a process for managing personal behavior/relationships or interactions between people because the claimed steps recite managing a construction project and workflow of shared tasks for responsible parties working on the project. Accordingly, since the claimed invention describes a process that falls under “Certain Methods of Organizing Human Activities” grouping, the claimed invention recites an abstract idea.
Regarding Step 2A [prong 2],
The judicial exception is not integrated into a practical application according to MPEP §2106.04(d). Claims 1, 6, 14 & 15 include the following additional elements:
A computer-implemented method, non-transitory computer-readable and system comprising:
computer instructions to carry out a first and second process,
at least one data storage comprising;
at least one access right apparatus/device;
a first planning application executing in a first proprietary data format;
a common data structure;
a second disparately programmed planning application;
In particular, the additional elements cited above beyond the abstract idea are recited at a high-level of generality and simply equivalent to a generic recitation and basic functionality that amount to no more than mere instructions to apply the judicial exception using generic computer technology components.
The claimed invention merely provides an abstract-idea-based-solution implemented with generic computer processes and components recited at a high-level of generality (receiving, storing, determining, and comparing data) using computer instructions to implement the abstract idea on a computer, and merely “apply it” without any meaningful technological limits or any improvement to technology, technical field or improvement to the functioning of the computer itself.
Therefore, the additional elements fail to integrate the recited abstract idea into any practical application since they do not impose any non-generic meaningful limits on practicing the abstract idea. Thus, the claimed invention is directed to an abstract idea.
Regarding Step 2B,
The claimed invention does not include additional elements that are sufficient to amount to significantly more than the judicial exception. See MPEP §2106.05.
As discussed above, the claimed additional elements recited above amounts to no more than mere instructions to implement the abstract idea by adding the words “apply it” using generic computer components and functionality. See MPEP §2106.05(h). Mere instructions to apply the judicial exception using generic computer components are insufficient to provide an inventive concept. Furthermore, the claimed additional elements merely limit the abstract idea to be executed in a computer environment, thus do nothing more than generally linking the use of a judicial exception to a particular technological environment or field of use. See MPEP §2106.05(h).
Considered as an ordered combination, the additional elements are claimed at a high-level of generality and add nothing that is not already present when the steps are considered separately. The sequence of the claimed limitations is equally generic and otherwise held to be abstract since the combination of these additional elements is no more than mere instructions to apply the judicial exception using generic computer components operating in their ordinary and generic capacities of what is typically expected of computers storing and updating data, and receiving and transmitting data between generic computer devices. The claimed invention is not patent eligible because the additional elements are merely invoked as tools to execute the abstract idea and thus are insufficient to amount to an inventive concept significantly more than the judicial exception.
As for dependent claims 2-5, 7-13 and 16-20, they merely further narrow and reiterate the same abstract ideas for storing and updating data, and receiving and transmitting data using generic data storage and transmittal techniques with the same additional elements as recited above which provide nothing more than applying the abstract idea using generic computer technology components. Furthermore the dependent claims 2-5, 7-13 and 16-20 contain the following additional elements: a plurality of devices, memory for storing information, at least one interface.
These additional elements do not provide any improvement to technology, technical field or improvement to the functioning of the computer itself, and at best simply applying the abstract idea executed in a general-purpose computer environment. Therefore the dependent claims are also directed to ineligible subject matter since they do not provide significantly more than the abstract idea itself.
Thus, after considering all claim elements in Claims 1-22 both individually and as an ordered combination, it has been determined that the claimed invention as a whole, is not enough to transform the abstract idea into a patent-eligible invention since nothing in the claim limitations provide significantly more than the abstract idea under 35 U.S.C. § 101.
Response to Amendment and Arguments
Regarding 101, Applicant argues that the technical improvements include:
- Machine-based translation of proprietary data into a common interoperable format.
- Automated, event-driven updating and propagation of task status and results.
- Enforcement of mutual, fine-grained access rights at the system level, eliminating
manual permission management and reducing security risks.
The practical application is evidenced in the context of construction project management, where these mechanisms prevent delays, miscommunication,
Examiner respectfully disagrees. Machine-based translation of one type of data format into another type of data format, and updating task data status and enforcing data access rights using existing machine-based data processing and data access technology is not a technical improvement just because a computer system is being used as a tool to do the translation, updating and enforcing of existing generic data formatting and data access implementation. At best, the invention is solving an abstract idea problem in project management and improvement to the abstract idea itself utilizing generic computing systems to manage information sharing among users collaborating on a project based on shared and dependent tasks of the project. Sharing or granting access to task data by tracking dependent tasks that are data related, is not a technological improvement to a technological problem. Automatically and mutually granting data access rights to task-related information is a data sharing issue being solved with existing generic data computing network systems in distributed computing network systems that are expected to grant data access to users with certain user access rights. These additional elements do not provide any improvement to technology, technical field or improvement to the functioning of the computer itself, and at best simply applying the abstract idea executed in a general-purpose computer environment. Therefore the dependent claims are also directed to ineligible subject matter since they do not provide significantly more than the abstract idea itself.
Conclusion
The relevant prior art made of record not relied upon but considered pertinent to applicant's disclosure can be found in the current and/or previous PTO-892 Notice of References Cited. Any inquiry concerning this communication or earlier communications from the Examiner should be directed to LAURA YESILDAG whose direct telephone number is (571) 270-5066 and work schedule is generally Monday-Friday, from 9:00 AM - 5:00 PM ET.
In order to receive any email communication from the Examiner, filing for official authorization for Internet Communication is required. The authorization form can be accessed at https://www.uspto.gov/sites/default/files/documents/sb0439.pdf.
Examiner interviews can be requested by telephone or are available using the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the Examiner are unsuccessful, the Examiner’s Supervisor, LYNDA JASMIN, can be reached at (571) 272-6782 for any urgent matter that needs immediate attention. Additional information regarding the status of an application may be obtained from the USPTO Patent Center. For more information about the USPTO Patent Center, please access https://patentcenter.uspto.gov/ The Patent Center is available to all users for electronic filing and management of patent applications and can be contacted for questions at 1-866-217-9197 or 571-272-4100.
/LAURA YESILDAG/Primary Examiner, Art Unit 3629