None
None
This invention is related to manufacturing execution systems and in particular to the control and tracking of engineering changes made to a product while units of the product are in the manufacturing process. An engineering change is a change to the specification of a product that results in a change in the manufactured product units.
In the present invention, a product is manufactured in a manufacturing process controlled and tracked using a manufacturing execution system or MES. An engineering change is made to the product specification while units of the product are in the manufacturing process. The product unit is reworked to match the changed specification. The engineering change implementation function of the manufacturing execution system identifies the products units to be reworked, provides instructions for the rework, and tracks that all affected product units are reworked to the changed specification.
Once a product is designed and manufactured, it may under go modifications that are implemented in subsequent units that are manufactured. Changes are made to make the product safer, lower cost, add functions, etc. to meet changes in the market. These changes are called Engineering Changes because the change usually requires a change in the design specification by engineering. A change to the product usually changes the manufacturing process that produces the product. To assure that changes to designed functions of the product are reflected in the manufactured product, most organizations use an engineering change control process that requires that the manufacturing process changes are in effect before the changed product is manufactured. Each manufactured product may be tracked by a designation of the engineering change to which the product was manufactured. The item identifier, called a part number may be changed or a secondary identifier called a revision or engineering change level may be changed to signify that the product has been changed from the previous design of the product. Many processes and systems have been developed to assure that the manufacturing process changes are made to reflect the engineering change before the product is manufactured.
Many of these changes are unanticipated and there may be units of the product in the manufacturing process when an engineering change is contemplated or implemented. The product units may be allowed to complete the manufacturing process and shipped at the original design. However, it may be economically feasible to modify (rework) units in the manufacturing process so that these units meet the changed requirements. The prior art describes for some products, especially semiconductor products, where the product design, with in limits, can accommodate engineering changes without major reprocessing of the product.
However, the implementation of the engineering change to product units in the manufacturing process have been controlled and tracked manually. With a manual process, there are “escapes” where product units that should have been reworked are not, product units that were thought to have been reworked are not, and product units that should not be reworked are reworked. With a manual process, the wrong rework processes may used to rework product units. The rework process may be dependent on the state of unit in the manufacturing process. A unit that has just started may require just a change in a component in the bin used to assemble the product. A unit later in the process may require a component to be removed and another assembled in its place. A unit near completion, for example after encapsulation, may not be reworked. A unit may continue in the original manufacturing process to a specified point, then reworked to the engineering change specification. After a unit is reworked, the unit may require a different manufacturing process than before rework. For example, a test to validate the rework is executed.
The part identifier of a unit is associated with the engineering specification to which it was manufactured. The part identifier is usually called a part number and may also include a secondary identifier called Engineering Change level (E/C level) or revision level. When a unit built to a first engineering specification is reworked to a second engineering specification, the part identifier for the unit is changed to that associated with the second engineering specification.
The MES uses work order to associate a part identifier and quantity with units to be manufactured. The MES also associates a route, a step-by-step sequence of manufacturing process steps, to a work order as the operational description of the manufacturing process. The MES uses the route to control and track the units in the manufacturing process.
When an engineering change is contemplated and designed, product units may continue to be manufactured. These units may not be useable or may require more rework than if stopped when the engineering change was contemplated. Stopping the manufacturing process will provide the opportunity to assess the quantity of product in the manufacturing process and the state of the units in the process. An economic decision can be made as to if and when the engineering change can be implemented. It may be desirable to permit units to proceed to a specified point in the manufacturing process before stopping.
The product is controlled and tracked in the manufacturing process using a manufacturing execution system, MES, or shopfloor system. The present invention is a function of an MES to assure accurate implementation of an engineering change by:
A manufacturing execution system (MES) uses a route, a step-by-step sequence that defines a manufacturing process. A step in the route defines a manufacturing process step and the work center at which the step is executed. The step provides operator instructions, parameters or programs for process equipment used at the work center, etc. to execute the process step. At the completion of a process step, the MES provides direction to perform the next process step. The next process step may include an instruction to move the unit to the next work center in the route. A unit is identified by a barcode or other machine-readable identifier or by other means such as a paper traveler with identifying information. Reading the unit's barcode or entering the identifying information selects the unit in the MES. The MES tracks units by the step in the route at which the unit is selected and can determine if the unit is executing the process steps in the proper sequence. The MES can notify if a unit is not following the sequence. The completion of a step can also be tracked. Most MES provide a real time view of the “Work in process” or WIP by product or by work order for a product. A route can be diagrammed as a directed graph where a node represents a step in the route and the arrow designates the next node and step in the route.
The Engineering Change Implementation function of the MES provides:
It is noted that the first route and second route need not be different; the first route can be used as the route after reworking the unit.
The Engineering Change Implementation function assures that only the product units to be reworked are reworked; that the proper rework instructions were provided; units that have been reworked are tracked using the second route with the process to follow rework and the units that have not been reworked are tracked using the original route. The quantity of units for the second work order tracks the number of units reworked and the quantity of units for the original work order tracks the number of units that have not been reworked.
The route that describes the step-by-step manufacturing process can be implemented as a linked list in a relational database system as illustrated in Table 1.
A row in the Route Table includes a Route Identifier field to distinguish rows for different routes. A Current Step field that identifies the step in the route, a Work Center field that identifies the work center associated with the process step, a Next Step field that identifies the next step in the route, and an Instructions field that identifies the instructions that describes the process step to be executed at the work center. The beginning of the route is identified by “Start” and the end of the route is identified by “End” in the Current Step field.
The current position for a product unit is maintained in a Product Unit Route Position Table.
The Product Unit Route Position Table includes a Unit Identifier field with the barcode or other identifier for a product unit; a Route Identifier field to indicate the route used for the product unit and a Current Step field that indicates the position of the unit in the route. The manufacture of a unit begins with a row created in the Product Unit Route Position Table where the unit barcode is entered into the Unit Identifier field, the route for the process is entered into the Route Identifier field, and the Current Step field is initialized to “Start” to begin the route. In the example, when the unit with Barcode 1 is selected, the MES program selects the row from the Product Unit Route Position Table with Unit Identifier Barcode 1. The MES program selects the row in the Route Table for Route Identifier Route 1 and Current Step Start. The MES program can validate that the unit with identifier Barcode 1 is at Work Center 1. Instruction 1 is provided to the work center. When the process step is completed, the Current Step field in the Product Unit Route Position row for Barcode 1 is updated to the contents of the Next Step field: Step 2 and the work center is the work center for the row with the Current Step field Step 2: Work Center 2. Work Center 1 is directed to move Barcode 1 to Work Center 2.
Adding a field to the rows in the Product Unit Route Position Table enables the Engineering Change Implementation function. Table 3 illustrates the augmented column called E/C Implementation.
The E/C Implementation field can contain either a “Stop” flag or a key to a row in the E/C Rework Table. If the E/C Implementation field is blank, the MES program processes the unit as described earlier without Engineering Change Implementation. If the E/C Implementation field is set to “Stop”, the MES program displays a message at the work center to stop operations on the unit. This field may be used to stop the manufacturing process for a set of units for other than hold for an Engineering Change assessment and planning. For example, the “Stop” could also be used to stop the line due to a quality problem or a work center not operational. The “Stop” can be applied selectively so that only a specified set of units is affected.
When not blank or set to “Stop”, the E/C Rework field is used to select a row in the E/C Rework Table, illustrated as Table 4. A row in the E/C Rework Table provides the Route and process step for a unit when the rework instructions have been completed and the Rework Instructions. The MES program selects the row corresponding to the barcode or identifier of a unit. If the E/C Implementation field is not blank or set to “Stop”, then the MES program uses the value to select a row in the E/C Rework Table to present the Rework instructions and when completed, to transfer the unit to the route and step of the receiving route by inserting the values in the E/C Rework Table E/C Route and E/C Step fields into the Route Identifier and Current Step fields of the Product Unit Route Position with Engineering Change Implementation for the row corresponding to the barcode, Unit Identifier field. The E/C Implementation is set to blank to indicate that the E/C Implementation process for the unit has been completed.
The work order associates the part identifier (part number and E/C level) of a product, the route to manufacture the product and quantity. As a unit is reworked the quantity for the work order for the original part identifier is decreased by one and the quantity for the work order for the reworked part identifier is increased by one.
In the example, Barcode 1 is selected. The MES program selects the row with Barcode 1 in the Unit Identifier field. The MES program detects that the E/C Implementation filed is E/C Rework 1. The MES program selects from the E/C Rework Table the row where E/C Rework 1 is in the E/C Rework field. The MES program provides Rework 1 as the rework instruction. When the work center indicates that the rework instructions are completed, the MES program inserts Route 2 and Step 2′ into the Route Identifier and Current Step fields, clears the E/C Implementation filed for the row with Barcode 1 in the Unit Identifier field and decrements the Quantity field for Work Order 1 to N−1 and increments the Quantity field for Work Order 2 to M+1. This indicates a decrease in quantity for Part Number 1 E/C Level 1 by one and an increase for Part Number 2 E/C Level 2 by one.
It may be desirable for a unit to proceed on the first route to a specified process step before stopping or implementing the Engineering Change. The Product Unit Route Position with Engineering Change Implementation Table, Table 3, is augmented with the Implementation Step field with the route step to either stop or implement the engineering change. Table 6 is the Augmented Product Unit Route Position with Engineering Change Implementation Table.
With the contents of Table 6, each unit will be processed using Route 1 until it reaches the process step designated in the Implement Step field: End. When a unit reaches the End process step, Rework 3 instructions are displayed. When the Rework 3 Instructions are completed, the unit is transferred to Route 2 at Step 3′. The next process step is End′ in Route 2.
As a process example, when Barcode 1 is selected, the MES program selects the row with the Unit Identifier matching Barcode 1. The unit is at Route 1 Start process step. The Implement Step is End. Since the Current Step does not match the Implement Step, the MES processes the unit without any Engineering Change process and the Current Step field is updated to Step 2. When selected again, MES program determines that the Current Step does not equal the value in the Implement Step field and the unit is again processed without any Engineering Change process and the Current Step field is updated to End. When selected again, the MES program detects that the Current Step field matches the Implement Step field. The MES program selects the E/C Implementation field for the row. If the value were Stop, the MES program would display a message to stop processing the unit. In the example, a link to E/C Rework 3 in Table 4 is provided and the MES program displays the Rework 3 instruction. After Rework 3 instruction is completed, the MES program updates the Route Identifier field with Route 2 and the Current Step filed with Step 3′, and decrements the Quantity field for Work Order 1 to N−1 and increments the Quantity field for Work Order 2 to M+1.
The relational database can be a commercial relational database from Oracle, IBM, Microsoft and other providers. The MES program can be written in a wide variety of languages such as C, C++, Java, or Visual Basic. The MES program and relational database may execute on commercial hardware such as Intel based computers, SUN, IBM, or HP computers. The work centers are connected to the computers with the MES program and relational database using a LAN, a WAN, a wireless LAN, the Internet, or other electronic interconnection. One skilled in the art may find other alternative means of implementing the MES program such that it provides the functions to control and track Engineering Change Implementation in a manufacturing process.
Number | Name | Date | Kind |
---|---|---|---|
3971000 | Cromwell | Jul 1976 | A |
4303973 | Williamson et al. | Dec 1981 | A |
4443861 | Slater | Apr 1984 | A |
4489364 | Chance et al. | Dec 1984 | A |
4546413 | Feinberg et al. | Oct 1985 | A |
4652974 | Ryan | Mar 1987 | A |
4706165 | Takenaka et al. | Nov 1987 | A |
4746815 | Bhatia et al. | May 1988 | A |
4803595 | Kraus et al. | Feb 1989 | A |
4887206 | Natarajan | Dec 1989 | A |
4922377 | Matsumoto et al. | May 1990 | A |
5060116 | Grobman et al. | Oct 1991 | A |
5181317 | Nishihara et al. | Jan 1993 | A |
5184284 | Ashelin et al. | Feb 1993 | A |
5191534 | Orr et al. | Mar 1993 | A |
5243140 | Bhatia et al. | Sep 1993 | A |
5294754 | Wu | Mar 1994 | A |
5307261 | Maki et al. | Apr 1994 | A |
5315509 | Natarajan | May 1994 | A |
5761079 | Drumm | Jun 1998 | A |
5864875 | Van Huben et al. | Jan 1999 | A |
5953236 | Hossain et al. | Sep 1999 | A |
5970503 | Eisenberg | Oct 1999 | A |
6014506 | Hossain et al. | Jan 2000 | A |
6112130 | Fukuda et al. | Aug 2000 | A |
6167401 | Csipkes et al. | Dec 2000 | A |
6243717 | Gordon et al. | Jun 2001 | B1 |
6272665 | Johnson et al. | Aug 2001 | B1 |
6651239 | Nikitin et al. | Nov 2003 | B1 |
6684121 | Lu et al. | Jan 2004 | B1 |
6845280 | Rives et al. | Jan 2005 | B1 |
7069100 | Monette et al. | Jun 2006 | B2 |
20030063447 | Cwik et al. | Apr 2003 | A1 |
20030078975 | Ouchi | Apr 2003 | A1 |
20030102367 | Monette et al. | Jun 2003 | A1 |
20030105541 | Hsu et al. | Jun 2003 | A1 |
20040039665 | Ouchi | Feb 2004 | A1 |
20040225390 | Keller et al. | Nov 2004 | A1 |
Number | Date | Country | |
---|---|---|---|
20060122721 A1 | Jun 2006 | US |