Industrial controller automation interface

1. A non-transitory computer-readable medium having instructions stored thereon that, in response to execution, cause a computer communicatively coupled to an industrial controller through a first network to perform operations comprising:

establishing one or more classes of objects, including defining at least one attribute or method for each object;

assigning a project object to the industrial controller, the project object being associated with at least one program file object residing on the industrial controller and at least one data file object residing on the industrial controller;

executing an automation interface exposed to a client application located on a remote device communicatively coupled to the computer through a second network, wherein the automation interface is resident on the computer;

receiving, via the automation interface from the client application, a data request to upload control process data from a data file object of the at least one data file object residing on the industrial controller, the data request specifying the control process data as an attribute of the project object or an object associated with the project object;

based on the specified control process data attribute in the received data request, executing, via the automation interface, the data request with the industrial controller associated with the project object associated with the specified control process data attribute;

receiving, via the automation interface from the client application, an additional data request specifying an edited version of the control process data to download to the industrial controller associated with the data file object; and

based on the edited version of the control process data, executing, via the automation interface, the additional request with the associated industrial controller.

2. The non-transitory computer-readable medium of claim 1 , the operations further comprising:

receiving and processing, via the automation interface, a client request from the client application according to a first communication protocol; and

invoking, via the automation interface, one or more communications classes or functions of the one or more classes of objects to execute the client request with the industrial controller via a second communication protocol that is different from the first communication protocol.

3. The non-transitory computer-readable medium of claim 1 , wherein the first network is different from the second network.

4. The non-transitory computer-readable medium of claim 1 , the operations further comprising generating, based on the one or more classes of objects, the automation interface.

5. The non-transitory computer-readable medium of claim 1 , wherein the operations further comprising:

receiving, via the automation interface, another data request from the client application which specifies an attribute of an object associated with the project object;

identifying, via the automation interface, the project object based on the attribute and the industrial controller associated with the project object;

issuing, via the automation interface, a request to the industrial controller for data associated with the attribute of the object specified in the other data request;

receiving, via the automation interface, the requested data from the industrial controller; and

transmitting, via the automation interface, the requested data to the client application.

6. The non-transitory computer-readable medium of claim 5 , wherein the other data request is received according to a first communication protocol, the requested data is transmitting according to the first communication protocol, the request is issued according to a second communication protocol that is different from the first communication protocol, and the requested data is received according to the second communication protocol.

7. A non-transitory computer-readable medium having instructions stored thereon that, in response to execution, cause a computer communicatively coupled to an industrial controller through a first network to perform operations comprising:

establishing one or more classes of objects, including defining at least one attribute or method for each object;

assigning a project object to the industrial controller, the project object being associated with at least one program file object residing on the industrial controller and at least one data file object residing on the industrial controller;

executing an automation interface exposed to a client application located on a remote device communicatively coupled to the computer through a second network, wherein the automation interface is resident on the computer;

receiving, via the automation interface from the client application, a request specifying the project object to upload from the industrial controller associated with the project object;

based on the project object specified in the received request, executing, via the automation interface, the request with the industrial controller;

receiving, via the automation interface, another request from the client application specifying an edited version of the project object to download to the industrial controller associated with the project object; and

based on the edited version of the project object specified in the other request, executing, via the automation interface, the other request with the associated industrial controller.

8. The non-transitory computer-readable medium of claim 7 , the operations further comprising:

receiving and processing, via the automation interface, a client request from the client application according to a first communication protocol; and

invoking, via the automation interface, one or more communications classes or functions of the one or more classes of objects to execute the client request with the industrial controller via a second communication protocol that is different from the first communication protocol.

9. The non-transitory computer-readable medium of claim 7 , wherein the first network is different from the second network.

10. A computer, comprising:

a processor; and

a memory communicatively coupled to the processor, the memory having stored therein computer-executable instructions, comprising:

an automation interface exposed to a client application residing on a remote device that is connected to the computer through a first network, wherein the automation interface is in communication with an industrial controller through a second network and comprises one or more classes of objects, including at least one attribute or method defined for each object, wherein the automation interface is configured to:

assign a project object to the industrial controller, the project object being associated with at least one program file object residing on the industrial controller and at least one data file object residing on the industrial controller;

receive, from the client application, a data request to upload control process data from a data file object of the at least one data file object residing on the industrial controller, the data request specifying the control process data as an attribute of the project object or an object associated with the project object;

based on the specified control process data attribute in the received data request, execute the data request with the industrial controller associated with the project object associated with the specified control process data attribute;

receive, from the client application, an additional data request specifying an edited version of the control process data to download to the industrial controller associated with the data file object; and

based on the edited version of the control process data, execute the additional request with the associated industrial controller.

11. The computer of claim 10 , wherein the automation interface is further configured to:

receive and process a client request from the client application according to a first communication protocol; and

invoke one or more communications classes or functions of the one or more classes of objects to execute the client request with the industrial controller via a second communication protocol that is different from the first communication protocol.

12. The computer of claim 10 , wherein the first network is different from the second network.

13. The computer of claim 10 , further comprising a component configured to generate the automation interface based on the one or more classes of objects.

14. The computer of claim 10 , wherein the automation interface is further configured to:

receive another data request from the client application which specifies an attribute of an object associated with the project object;

identify the project object based on the attribute and the industrial controller associated with the project object;

issue a request to the industrial controller for data associated with the attribute of the object specified in the data request;

receive the requested data from the industrial controller; and

transmit the requested data to the client application.

15. The computer of claim 14 , wherein the other data request is received according to a first communication protocol, the requested data is transmitting according to the first communication protocol, the request is issued according to a second communication protocol that is different from the first communication protocol, and the requested data is received according to the second communication protocol.

16. A computer, comprising:

a processor; and

a memory communicatively coupled to the processor, the memory having stored therein computer-executable instructions, comprising:

an automation interface exposed to a client application residing on a remote device that is connected to the computer through a first network, wherein the automation interface is in communication with an industrial controller through a second network and comprises one or more classes of objects, including at least one attribute or method defined for each object, wherein the automation interface is configured to:

assign a project object to the industrial controller, the project object being associated with at least one program file object residing on the industrial controller and at least one data file object residing on the industrial controller;

receive, from the client application, a request specifying the project object to upload from the industrial controller associated with the project object;

based on the project object specified in the received request, execute the request with the industrial controller;

receive another request from the client application specifying an edited version of the project object to download to the industrial controller associated with the project object; and

based on the edited version of the project object specified in the other request, execute the other request with the associated industrial controller.

17. The computer of claim 16 , the operations further comprising:

receive and process a client request from the client application according to a first communication protocol; and

invoke one or more communications classes or functions of the one or more classes of objects to execute the client request with the industrial controller via a second communication protocol that is different from the first communication protocol.

18. The computer of claim 16 , wherein the first network is different from the second network.