Shared repository of simulation models

• US 10,521,521 B2
• Filed: 03/31/2014
• Issued: 12/31/2019
• Est. Priority Date: 10/14/2013
• Status: Active Grant

• Current Assignee: Aveva Software LLC (Schneider Electric SE)
• Original Assignee: Aveva Software LLC (Schneider Electric SE)
• Inventors: Boys, Ian H., Kane, Douglas Paul, Jerome, David H., Depew, Cal
• Primary Examiner(s): Ochoa, Juan C
• Application Number:
  US14/231,341
• Publication Number:
  US 20150106073A1
• Time in Patent Office: 2,101 Days
• Field of Search: 703 2, 703 6, 703 9
• CPC Class Codes: G06F 30/20 Design optimisation, verification or simulation optimisation, verification or simulation of circuit designs G06F30/30

Abstract

A system simulates a process entity. Software instructions stored on a memory device and executable by a processor create a plurality of entity type objects that generically represents a type of process entity. Instructions store the plurality of entity type objects in a shared repository. Additionally, instructions enable a plurality of users to access the plurality of entity type objects in the shared repository simultaneously.

Claims

1. A system for simulating a process entity in an industrial process, the system comprising:

a processor;

a memory device coupled to the processor;

software instructions stored on the memory device and executable by the processor, said instructions comprising;

instructions for presenting a plurality of model editors on a respective plurality of remote processing devices, wherein the remote processing devices are coupled to the system via a communications network, and wherein each of the remote processing devices is associated with a user;

instructions for creating, via the model editors, a plurality of standard entity type objects in response to user input from one or more of the remote processing devices, said standard entity type objects each generically representing a type of process entity in the industrial process, wherein one or more of the standard entity type objects are customizable;

instructions for creating, via the model editors, a plurality of custom entity type objects in response to user input from one or more of the remote processing devices, wherein the custom entity type objects are specific to the users associated with the remote processing devices;

instructions for storing the standard entity type objects in a pre-existing default model library of a shared repository stored on a shared server;

instructions for creating a custom model library in the shared repository;

instructions for storing the custom entity type objects in the custom model library;

instructions for enabling the remote processing devices to access the standard entity type objects in the default model library of the shared repository simultaneously;

instructions for enabling the remote processing devices to access the custom entity type objects in the custom model library of the shared repository simultaneously;

instructions for changing, via the model editors, at least one of the custom entity objects in response to user input from one or more of the remote processing devices; and

instructions for persisting, in the custom model library of the shared repository, changes made to the custom entity type objects by any of the users associated with the remote processing devices.

2. The system of claim 1, wherein the remote processing devices are enabled to access the custom entity type objects from a plurality of geographical locations, wherein at least one of the remote processing devices is located at a first geographical location of the plurality of geographical locations and at least one of the remote processing devices is located at a second geographical location of the plurality of geographical locations that is different from the first geographical location.

3. The system of claim 1, further comprising instructions for storing the changes made to the custom entity type objects in the custom model library of the shared repository for use by the users associated with the remote processing devices, wherein the changes are made in response to user input from one or more of the remote processing devices.

4. The system of claim 1, wherein storing the custom entity type objects comprises importing an externally created custom entity type object into the custom model library of the shared repository.

5. The system of claim 1, further comprising instructions for storing one or more simulations in the shared repository, said simulations comprising flowsheets and one or more instances of the standard entity type objects and custom entity type objects, wherein the simulations are stored separately from the default model library and the custom model library in the shared repository.

6. The system of claim 5, further comprising instructions for saving a snapshot of a simulation stored in the shared repository, said snapshot representing an archive of a simulation.

7. The system of claim 5, wherein each simulation includes an internal model library stored in the shared repository, wherein each internal model library includes custom entity type objects private to the simulation.

8. The system of claim 5, wherein changes made to instances of the standard entity type objects in one simulation are propagated to instances of the standard entity type objects in other simulations.

9. One or more tangible, non-transitory computer-readable media having executable instructions stored thereon that, when executed, perform a method of simulating a process entity in an industrial process, the method comprising:

presenting a plurality of model editors on a respective plurality of remote processing devices, wherein the remote processing devices are coupled to the system via a communications network, and wherein each of the remote processing devices is associated with a user;

creating, via the model editors, a plurality of standard entity type objects in response to user input from one or more of the remote processing devices, said standard entity type objects generically representing a type of process entity in the industrial process, wherein one or more of the standard entity type objects are customizable;

creating, via the model editors, a plurality of custom entity type objects in response to user input from one or more of the remote processing devices, wherein the custom entity type objects are specific to the users associated with the subset of remote processing devices;

storing the standard entity type objects in a pre-existing default model library of a shared repository stored on a shared server;

creating a custom model library in the shared repository;

storing the custom entity type objects in the custom model library;

enabling the remote processing devices to access the standard entity type objects in the default model library of the shared repository simultaneously;

enabling the remote processing devices to access the custom entity type objects in the custom model library of the shared repository simultaneously;

changing, via the model editors, at least one of the custom entity objects in response to user input from one or more of the remote processing devices; and

persisting, in the custom model library of the shared repository, changes made to the custom entity type objects by any of the users associated with the remote processing devices.

10. The computer-readable media of claim 9, wherein the remote processing devices are enabled to access the custom entity type objects from a plurality of locations.

11. The computer-readable media of claim 9, wherein the method further comprises storing the changes made to the custom entity type objects in the custom model library of the shared repository for use by another of the users associated with the remote processing devices.

12. The computer-readable media of claim 9, wherein storing the custom entity type objects comprises importing an externally created custom entity type object into the custom model library of the shared repository.

13. The computer-readable media of claim 9, further comprising storing one or more simulations in the shared repository, said simulations comprising flowsheets and one or more instances of the standard entity type objects and custom entity type objects, wherein the simulations are stored separately from the default model library and the custom model library in the shared repository.

14. The computer-readable media of claim 13, wherein the method further comprises saving a snapshot of a simulation stored in the shared repository, said snapshot representing an archive of a simulation.

15. A processor executable method of simulating a process entity in an industrial process, the method comprising:

presenting a plurality of model editors on a respective plurality of remote processing devices, wherein the remote processing devices are coupled to the system via a communications network, and wherein each of the remote processing devices is associated with a user;

creating, via the model editors, a plurality of standard entity type objects in response to user input from one or more of the remote processing devices, said standard entity type objects generically representing a type of process entity in the industrial process, wherein one or more of the standard entity type objects are customizable;

creating, via the model editors, a plurality of custom entity type objects in response to user input from one or more of the remote processing devices, wherein the custom entity type objects are specific to the users associated with the remote processing devices;

storing the standard entity type objects in a pre-existing default model library of a shared repository stored on a shared server;

creating a custom model library in the shared repository;

storing the custom entity type objects in the custom model library;

enabling the remote processing devices to access the standard entity type objects in the default model library of the shared repository simultaneously;

enabling the remote processing devices to access the custom entity type objects in the custom model library of the shared repository simultaneously;

changing, via the model editors, at least one of the custom entity objects in response to user input from one or more of the remote processing devices; and

persisting, in the custom model library of the shared repository, changes made to the custom entity type objects by any of the users associated with the remote processing devices.

16. The method of claim 15, wherein the remote processing devices are enabled to access the custom entity type objects from a plurality of locations.

17. The method of claim 15, further comprising storing the changes made to the custom entity type objects in the custom model library of the shared repository for use by another of the users associated with the remote processing devices.

18. The method of claim 15, wherein storing the one or more custom entity type objects comprises importing an externally created custom entity type object into the custom model library of the shared repository.

19. The method of claim 15, further comprising storing one or more simulations in the shared repository, said simulations comprising flowsheets and one or more instances of the standard entity type objects and custom entity type objects, wherein the simulations are stored separately from the default model library and the custom model library in the shared repository.

20. The method of claim 19, further comprising saving a snapshot of a simulation stored in the shared repository, said snapshot representing an archive of a simulation.