System and method for live update of a manufacturing system

• US 6,711,593 B1
• Filed: 06/26/2001
• Issued: 03/23/2004
• Est. Priority Date: 06/26/2000
• Status: Expired due to Fees

• Current Assignee: Camstar Systems, Inc. (Siemens AG)
• Original Assignee: Camstar Systems, Inc. (Siemens AG)
• Inventors: Quantz, Dale C., Gordon, Brian S., Preston, David R.
• Primary Examiner(s): Shah, Sanjiv
• Application Number:
  US09/892,873
• Time in Patent Office: 1,001 Days
• Field of Search: 707/204, 707/203, 707/202, 707/201, 707/200, 707/10, 707/1, 700/95, 713/100, 709/224
• US Class Current: 707/615
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method and system for performing a live update of a manufacturing database. The user can automatically change database tables, add files, executable programs, and new modeling schema at remote sites from a central location. Manufacturing processes can be modified or changed entirely to introduce a new product line. Clients at the remote sites receive notification that a change in the database will occur so that works in progress can be completed. Clients complete their transactions but connections to the application server are maintained to facilitate resuming production. No new transactions are allowed at the remote site while the update is in progress. Downtime is minimal as the system is always running and the user can schedule the update at the most convenient time for individual sites. A rollback copy of the data is maintained to allow users to return to a version utilized prior to the last update.

Claims

1. A method for performing an automatic configuration of a remote manufacturing database comprising the steps of:

a) preparing centralized update information;

b) presenting said update information for export to a remote location;

c) making remote preparations for an update;

d) updating a remote database in a server at said remote location, wherein said updating includes providing said centralized update information; and

e) running a database compare process;

f) waiting for a hold state confirmation; and

g) creating new instance tables.

2. The method of claim 1, wherein transactions continue between said remote server and its clients while said remote preparations for an update are made.

3. The method of claim 1, wherein transaction between said remote server and said clients are suspended while said remote database is updated and a network connection between said client and said server is maintained.

4. The method of claim 1, wherein a copy of a previous configuration is retained at said remote site.

5. The method of claim 1, wherein a time-stamped record is kept, said record detailing the success or failure of completing said updating of said remote database.

6. The method of claim 1, wherein said centralized update information includes configuration information which is an update to a previous configuration.

7. The method of claim 6, wherein said configuration is a new configuration.

8. A computer-usable medium having computer-readable program code embodied therein for causing a computer system to perform the steps of:

a) preparing centralized update information;

b) presenting said update information for export to a remote location;

c) making remote preparations for an update;

d) updating a remote database in a server at said remote location, wherein said updating includes providing said centralized update information; and

e) running a database compare process;

f) waiting for a hold state confirmation; and

g) creating new instance tables.

9. The computer-usable medium of claim 8, wherein the computer readable program directs the computer system to make remote preparations for an update while existing transactions continue between said remote server and its clients.

10. The computer-usable medium of claim 8, wherein the computer readable program directs the computer system to suspend transactions between said remote server and said clients while said remote database is updated and directs a network to maintain a connection between said client and said server during said update.

11. The computer-usable medium of claim 8, wherein the computer readable program directs the computer system to retain a copy of a previous configuration at said remote site.

12. The computer-usable medium of claim 8, wherein the computer readable program directs the computer system to keep a time-stamped record, said record detailing the success or failure of completing said updating of said remote database.

13. The computer-usable medium of claim 8, wherein said centralized update information includes configuration information which is an update to a previous configuration.

14. The computer-usable medium of claim 8, wherein said configuration is a new configuration.

15. A computer system comprising:

a bus for communicating information;

a computer storage medium coupled to said bus, said computer storage medium operable to store digital information and computer-readable program code, wherein said computer-readable program code causes a computer system to perform the steps of;

a) preparing centralized update information,

b) presenting said update information for export to a remote location,

c) making remote preparations for an update, and

d) updating a remote database in a server at said remote location,

wherein said updating includes providing said centralized update information; and

a central processor unit coupled to said bus operable to process digital information and instructions, including performance of a database synchronization process comprising;

running a database compare process;

waiting for a hold state confirmation; and

creating new instance tables.

16. The computer system of claim 15 wherein a backup copy of a previous version of said remote database is maintained.

17. The computer system of claim 16 wherein said synchronization process includes the steps of:

backing up unchanged versions of metadata tables scheduled to be changed in the current update;

deleting the metadata tables that are to be changed from the site production database by a database delete program; and

copying the new metadata tables from the source directory to the site production database.

18. The computer system of claim 16 wherein said synchronization process includes the steps of:

waiting for notification of the suspend state;

backing up changed instance tables to the site backup database;

deleting the changed instance tables from the site production database by the database delete program; and

copying the new instance tables from the source directory to the site production database.