DETAILED ACTION
Claims 1-20 are pending.
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 § 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 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-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Zhu, Jun, et al. "A collaborative virtual geographic environment for emergency dam-break simulation and risk analysis." Journal of spatial science 61.1 (2016): 133-155 (hereinafter Zhu).
Regarding claims 1-20, Zhu discloses all the claimed limitations, as outlined below:
1. A system, comprising: a memory that stores executable components; and a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising: a user interface component configured to render integrated development environment (IDE) interfaces on respective client devices and to receive, via interaction with the IDE interfaces, industrial design input that defines aspects of an industrial automation control project; a project generation component configured to generate system project data based on the industrial design input; and a collaboration management component configured to, in response to receipt of industrial design input from a first client device associated with a first user defining a modification to a first aspect of the industrial automation control project, determine whether the modification will affect one or more second aspects of the industrial automation control project, wherein the user interface component is further configured to, in response to a determination by the collaboration component that the modification will affect the one or more second aspects, deliver a notification to one or more second client devices associated with users assigned to develop the one or more second aspects of the industrial automation control project (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
2. The system of claim 1, wherein the collaboration component is configured to perform a regression analysis on the system project data to determine interdependencies between aspects of the industrial automation control project, and to determine whether the modification will affect the one or more second aspects based on the interdependencies learned by the regression analysis (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
3. The system of claim 2, wherein the regression analysis determines, as the interdependencies, at least one of a dependency between control code segments, a dependency between a control code segment and a visualization element, a dependency between a control code segment and an engineering drawing, or a hierarchical relationship between automation objects included in the system project data (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
4. The system of claim 1, wherein the notification comprises at least one of a description of the modification or a description of an effect that the modification will have on the one or more second aspects of the industrial automation control project (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
5. The system of claim 1, wherein the system project data comprises at least control programming that, in response to execution on one or more industrial devices, facilitates monitoring and control of an industrial automation system in accordance with the industrial design input (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
6. The system of claim 1, wherein the collaboration management component configured to perform brokering between multiple sets of the industrial design input submitted via different client devices of the client devices, and to integrate a selected subset of the sets of the industrial design input in the system project data based on results of the brokering (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
7. The system of claim 1, further comprising a simulation component configured to perform a risk analysis of the modification that identifies a potential negative impact on control performance of the industrial control and monitoring project due to the modification, wherein the user interface component is configured to render a notification of the potential negative impact on the first client device (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
8. The system of claim 7, wherein the risk analysis comprises a regression analysis on the system project data that identifies one or more aspects of the industrial automation control project that will be affected by the modification, and the simulation component is configured to perform a simulation to determine how the modification will affect performance of the one or more aspects (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
9. The system of claim 1, wherein the collaborative management component is further configured to generate and store records of modifications made to the control project data by respective users (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
10. The system of claim 1, wherein the collaboration management component is further configured to, in response to receipt of a development note submitted by a user and directed to a selected portion of the industrial automation control project, associate the development note with the selected portion, and the user interface component is further configured to, in response to a determination that the selected portion of the industrial control project is being rendered on a client device of another user, render the development note on the client device of the other user (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
11. A method, comprising: rendering, by a system comprising a processor, integrated development environment (IDE) interfaces on respective client devices; receiving, by the system via interaction with the IDE interfaces, industrial design input that defines aspects of an industrial control and monitoring project; in response to receiving industrial design input from a first client device associated with a first user defining a modification to a first aspect of the industrial control and monitoring project, determining, by the system, whether the modification will affect one or more second aspects of the industrial control and monitoring project; in response to determining that the modification will affect the one or more second aspects, rendering, by the system, a notification on one or more second client devices associated with users assigned to develop the one or more second aspects of the industrial control and monitoring project; and generating, by the system, system project data based on the industrial design input (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
12. The method of claim 11, wherein the determining comprises: performing a regression analysis on the system project data to determine interdependencies between aspects of the industrial control and monitoring project; and determining whether the modification will affect the one or more second aspects based on the interdependencies learned by the regression analysis (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
13. The method of claim 12, wherein the regression analysis determines, as the interdependencies, at least one of a dependency between control code segments, a dependency between a control code segment and a visualization element, a dependency between a control code segment and an engineering drawing, or a hierarchical relationship between automation objects included in the system project data (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
14. The method of claim 11, wherein the notification comprises at least one of a description of the modification or a description of an effect that the modification will have on the one or more second aspects of the industrial control and monitoring project (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
15. The method of claim 11, wherein the system project data comprises at least control programming that, in response to execution on one or more industrial devices, facilitates monitoring and control of an industrial automation system in accordance with the industrial design input (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
16. The method of claim 11, further comprising brokering, by the system, between multiple sets of the industrial design input submitted via different client devices of the client devices; and integrating, by the system, a selected subset of the sets of the industrial design input in the system project data based on results of the brokering (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
17. The method of claim 11, further comprising: performing, by the system, a risk analysis of the modification that identifies a potential negative impact on control performance of the industrial control and monitoring project due to the modification; and rendering, by the system on the first client device, a notification of the potential negative impact (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different functions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
18. The method of claim 17, wherein the performing of the risk analysis comprises: performing a regression analysis on the system project data that identifies one or more aspects of the industrial control and monitoring project that will be affected by the modification, and performing, by the system, a simulation to determine how the modification will affect performance of the one or more aspects (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
19. A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a system comprising a processor to perform operations, the operations comprising: rendering integrated development environment (IDE) interfaces on respective client devices; receiving, via interaction with the IDE interfaces, industrial design input that defines aspects of an industrial control and monitoring project; in response to receiving industrial design input from a first client device associated with a first user defining a modification to a first aspect of the industrial control and monitoring project, determining whether the modification will affect one or more second aspects of the industrial control and monitoring project; in response to determining that the modification will affect the one or more second aspects, rendering a notification on one or more second client devices associated with users assigned to develop the one or more second aspects of the industrial control and monitoring project; and generating system project data based on the industrial design input (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
20. The non-transitory computer-readable medium of claim 19, wherein the determining comprises: performing a regression analysis on the system project data to determine interdependencies between aspects of the industrial control and monitoring project; and determining whether the modification will affect the one or more second aspects based on the interdependencies learned by the regression analysis (Fig 1 and Pages 135-136 - - The CVGE framework was designed as shown in Figure 1, which mainly included server and clients. The system aimed not only to share geographically distributed data, programs and software in a dynamically changing network environment but also to support multiple users to facilitate exploration of complicated geo graphical phenomenon and the performance of collaborative risk assessment. Because of the adoption of an agent-oriented view of the distributed system, there may be both coop erative and selfish agents whose aims are, respectively, to optimise the overall perform ance of the system and to maximise their own individual return. The server was the core of the CVGE, and it ensured that the whole system was running correctly. On the server side, a series of management toolkits and protocol criteria were defined for sharing, integration and interoperation of all resources and data. By means of message mechanisms, agents in the service environment with different func tions could be organised to implement collaborative work or tasks. It was composed of four types of functional components: resource registration service, mobile agent computing service, collaborative workflow service and virtual scene service).
Citation of Pertinent Prior Art
The following prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Liteplo et al., US Patent No. 6,782,305 relates to – information sharing in a collaborative design environment.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CARLOS R ORTIZ RODRIGUEZ whose telephone number is (571)272-3766. The examiner can normally be reached on Mon-Fri 10:00 am- 6:30 pm.
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, Mohammad Ali can be reached on 571-272-4105. 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.
/CARLOS R ORTIZ RODRIGUEZ/ Primary Examiner, Art Unit 2119
Prosecution Insights