Manufacturing System Software Version Management

• US 20080295089A1
• Filed: 09/24/2007
• Published: 11/27/2008
• Est. Priority Date: 10/04/2000
• Status: Active Grant

• Current Assignee: ASM Assembly Systems GmbH & Co. KG (Partnertec BV)
• Original Assignee: ASM Assembly Systems GmbH & Co. KG (Partnertec BV)
• Inventors: Huber, Robert
• Granted Patent: US 8,037,470 B2
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Version management for manufacturing system software involves a two-part data structure, having two identifiers that are separately and automatically modified, depending upon the changes or modifications that are made, respectively, to top-level and lower-level subsets of manufacturing system programs. According to various other aspects of the present invention, methods for managing revisions involve automatically assigning a version designator under preselected conditions, automatically notifying personnel having a need to know of the change, and managing revisions by way of a revision compare function.

Claims

1. In a computer-operated system for programming a manufacturing system, wherein a version of a program is downloaded to the manufacturing system and is associated with a version designator, a method for managing revisions to versions of the program, the method comprising the steps of:

running the program on the manufacturing system, the program including subsets organized with respect to one another in a hierarchical fashion, the subsets comprising a top-level subset and a plurality of lower-level subsets related hierarchically to the top-level subsets and to each other, each of the subsets identifying a main object and a sub-object, a version designator being associated with each of the subsets, each version designator including a first version identifier associated with the main object and a second version identifier associated the sub-object;

revising the first version designator identifier of a certain lower-level subset when the certain lower-level subset is modified;

if the modification of the certain lower-level subset affects other subsets, revising the second version identifier of the other affected subsets, and

identifying a status of the program as one of released or validated.

4. The method according to claim 1, wherein each of the first and second version identifiers comprises a number and the step of revising the first and second version identifiers comprises the step of incrementing the version identifier.

5. The method according to claim 1, wherein the status identifier comprises a validation indicator.

6. The method according to claim 5, wherein the manufacturing system comprises at least one line, the method further including activating the validation indicator after the program runs satisfactorily on the line.

7. The method according to claim 6, wherein the validation indicator is checked as a condition to running the program on the line without manual intervention.

8. The method according to claim 1, wherein the step of identifying a status includes providing a status identifier comprises a release indicator in the form of the letter R or V.

9. The method according to claim 8, wherein the manufacturing system comprises a plurality of lines, and the release indicator identifies the program as released for use on the plurality of lines after the program runs satisfactorily on the lines.

10. The method according to claim 8, wherein the release indicator is checked as a condition to running the program on any lines of the manufacturing system without manual intervention.

11. The method according to claim 1, wherein the manufacturing system comprises an electronics assembly system.

2. (canceled)

3. (canceled)

12-28. -28. (canceled)