Source: http://www.google.com/patents/US8069074?dq=5,222,134
Timestamp: 2014-07-30 08:21:50
Document Index: 10252485

Matched Legal Cases: ['art 121', 'art 122', 'art 121', 'art 122', 'art 121', 'art 121', 'art 122', 'art 122', 'art 122']

Patent US8069074 - Information processing terminal and server for supporting quality ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsAn information processing terminal for supporting quality improvement concerning product manufacture includes a workflow arrangement part acquiring row information indicating a first arrangement location of each of a plurality of workflows being arranged in an area for arranging the plurality of workflows...http://www.google.com/patents/US8069074?utm_source=gb-gplus-sharePatent US8069074 - Information processing terminal and server for supporting quality improvement concerning product manufactureAdvanced Patent SearchPublication numberUS8069074 B2Publication typeGrantApplication numberUS 11/638,692Publication dateNov 29, 2011Filing dateDec 14, 2006Priority dateDec 15, 2005Also published asUS20070192153Publication number11638692, 638692, US 8069074 B2, US 8069074B2, US-B2-8069074, US8069074 B2, US8069074B2InventorsTsuyoshi Toyofuku, Tsunehiro Kosaka, Hideki FujimuraOriginal AssigneeFujitsu Semiconductor LimitedExport CitationBiBTeX, EndNote, RefManPatent Citations (54), Non-Patent Citations (3), Classifications (22), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetInformation processing terminal and server for supporting quality improvement concerning product manufactureUS 8069074 B2Abstract An information processing terminal for supporting quality improvement concerning product manufacture includes a workflow arrangement part acquiring row information indicating a first arrangement location of each of a plurality of workflows being arranged in an area for arranging the plurality of workflows for verifying the quality improvement, and displaying the plurality of workflows based on the row information; a process component arrangement part acquiring matrix information indicating a second arrangement location of each of a plurality of process components being arranged in each of the plurality of workflows, and displaying the plurality of process components based on the matrix information; and a data association part performing a data association among the plurality of process components in accordance with data link lines within each of the plurality of workflows or the data link lines crossing from one workflow to another workflow with respect to the plurality of process components arranged and displayed in the plurality of workflows.
SUMMARY OF THE INVENTION An embodiment of the present invention solves one or more of the above problems.
DESCRIPTION OF THE PREFERRED EMBODIMENT An embodiment according to the present invention will be described with reference to the accompanying drawings.
Each of the clients PC 10 a implements a Java� environment, and creates, edits, and executes a business flow on a browser by activating a workflow creation program which is automatically downloaded from the quality improvement support server 100. When each user such as an engineer creates or edits the business flow while considering the business flow in his or her mind, computer resources of the client PC 10 a is used for processes concerning the business flow. Accordingly, a workload of the quality improvement support server 100 can be distributed to each client PC 10 a connected to the quality improvement system 1000 via the Intranet 5.
The workflow creation program 163 is a latest program file available for the client PCs 10 a. For example, the workflow creation program 163 is a Java� application program or a like. The problem DB 164 accumulates problem information concerning a problem for which an overcoming method is defined and stored in a database, from problems informed from the client PCs 10 a. When a recording medium 20 storing a program realizing the process conducted by the quality improvement support server 100 is set to a driver, the installer 19 reads out the program from the recording medium 20, and installs into the storage unit. The CPU reads out and executes the program installed in the storage unit, so that the process is performed in the quality improvement support server 100. The recording medium is a computer-readable medium. For example, the recording medium may be a CD-ROM (Compact Disc Read-Only Memory) or a like. Alternatively, the program may be downloaded via a network, and installed in the storage unit.
The Web client 120 communicates with the quality improvement support server 100 in accordance with the HTTP (HyperText Transfer Protocol), and further includes a workflow edit part 121, a workflow execution part 122, and a Java� VM (Virtual Machine) 123. For example, the workflow edit part 121 and the workflow execution part 122 are processing parts which are developed in a virtual storage area when the workflow creation program 163 is executed and becomes executable on the Java� VM 123.
On the matrix 50 f, a start of the business flow is indicated by a start mark 50 d. An engine selection area 50 c of the screen 50 shows engines which are classified for each category. For example, �ENGINES� listing all engines, �DATA EXTRACTION ENGINE�, �DATA PROCESS ENGINE�, and �RESULT ENGINE�.
The user arranges the engine in the workflow 50 e in accordance with a user's cognitive thought process, and flexibly sets a flow of data among engines being arranged. The flow of data is set in a direction from left to right and can be set from an upper left engine to a lower right engine in one workflow 50 e. Moreover, it is possible to set the flow of data from an upper left engine to a lower right engine so as to straddle from one workflow 50 e to another workflow 50 e in the matrix 50 f. The workflow edit part 121 of the client PC 10 a maintains the location of each of the workflows 50 e which are arranged by the user, with a variable �fposy� (integer equal to or greater than zero). Also, the workflow edit part 121 maintains the location of each of the engines which are arranged in each of the workflows 50 e, with a location coordinate (posx, posy) (integers equal to or greater than zero). The workflow 50 e is sectioned into a plurality of cells in one row and multiple rows such as two rows, three rows . . . may be formed in the workflow 50 e. A size of the workflow 50 e is maintained by a variable �rows� and a variable �cols�. A matrix configuration for each business flow will be described later with reference to description examples shown in FIG. 14 through FIG. 17.
In the workflow 1, lots and wafers having an outer circumferential defect are automatically classified by a �CSV IMPORT� engine, a �Bin-SSA� engine, a �CSV EXPORT� engine. In the workflow 2, the lots and wafers having the outer circumferential defect are verified by a �CSV IMPORT� engine and a �TREND� engine. In the workflow 3, defect factors of the lots and wafers having the outer circumferential defect are analyzed by device commonality by a �PROGRESS SHEET� engine, a �Commonality� engine, and a �CSV EXPORT� engine. In the workflow 4, a device causing common defect factors among the lots and the wafers having the outer circumferential defect are verified by a �CSV IMPORT� engine, a �MERGE� engine, a �TREND� engine, and a �CSV IMPORT� engine.
A �AGGREGATION� engine in the workflow 21 is associated with a �MERGE� engine in the workflow 23 by a data link line L28 crossing over the workflow 22. Moreover, a �LOT� engine in the workflow 22 is associated with a �PROCESS� engine by a data link line L31, and the �MERGE� engine in the workflow 22 is associated with a �MERGE� engine in the workflow 23 by a data link line L27.
The �PROCESS� engine in the workflow 23 is associated with the �MERGE� engine in the workflow 24 by the data link line L33. The �MERGE� engine in the workflow 23 is further associated with another �MERGE� engine in the workflow 24 by a data link line L34.
Moreover, a �MONITOR� engine in the workflow 22 is associated with the �MERGE� engine in the same workflow 22 by a data link line L24.
Furthermore, items for the �MERGE� engine in the workflow 23 are determined items acquired by the data link line L23 from the �AGGREGATION� engine in the workflow 21 and items acquired by the data link line L27 from the �MERGE� engine in the workflow 22. The items for the �MERGE� engine in the workflow 23 realizes the data associations toward a �TREND� engine in the workflow 23 by a data link line L29, a �CORRELATION CHART� engine in the workflow 23 by a data link line L30, and further the �MERGE� engine in the workflow 24 by the data link line L34.
In the workflows 21 through 24 arranged in the matrix 50 f, the user select a category �ENGINES� from an engine selection area 50 c, and places a program icon 512 showing �WORKFLOW� being classified to the category �ENGINES� to an arrangement location which the user determines based on the cognitive thought process, by the drag and drop operation.
Moreover, data link line L11 through L34 set in the matrix 50 f are placed when the user selects the category �ENGINES� from the engine selection area 50 c and places a program icon 511 showing �DATA LINK LINE� classified to the category �ENGINES� to arrangement locations which the user determines based on the cognitive thought process, by the drag and drop operation.
By selecting each program icon of engines, the user can add or delete items of a selected engine. Accordingly, in a case of an associated engine (for example, the �MERGE� engine of the sequential number 13) being associated from two or more engines, an item inconsistency may occur. In order to execute the business flow shown in FIG. 11, the item inconsistency is eliminated as shown in FIG. 12A and FIG. 12B.
FIG. 12A is a conceptual diagram showing items set to the engine when the workflow is designed, according to the embodiment of the present invention. In FIG. 12A, for example, when the workflows 21 through 24 are arranged, an item A and an item B are set for an extraction engine of the sequential number 1 (as the �CSV IMPORT� engine), an item C and an item D are set for an extraction engine of the sequential number 6 (as the �MONITOR� engine), and an item E and an item F are set for an extraction engine of the sequential number 9 (as the �CSV IMPORT� engine). Also, the item A, the item B, the item C, the item D, the item E, and the item F are set for the associated engine (as the �MERGE� engine).
In this case, the user deletes the item A of the extraction engine (as the �CSV IMPORT� engine) of the sequential number 1, and adds an item G to the extraction engine (as the �CSV IMPORT� engine) of the sequential number 1. In this state, the item A, the item B, the item C, the item D, the item E, and the item F are described in the XML in the workflow design data 171. Thus, since the item A is deleted and the item G is added, the item inconsistency occurs due to the items of the association engine (as the �MERGE� engine) of the sequential number 13 when the association engine (as the �MERGE� engine) of the sequential number 13 is executed.
The workflow execution part 122 refers to the workflow design data 171 in order to execute the association engine (as the �MERGE� engine) of the sequential number 13, and checks whether or not the item A, the item B, the item C, the item D, the item E, and the item F exist in the workflow design data 171. In accordance with the data link lines defined in the workflow design data 171, the workflow execution part 122 tracks back to an original upper engine extracting data in an order of the data link lines L28, L11, and L13, in an order of the data link lines L27 and L24, and by the data link line L25 (refer to FIG. 11).
After that, the workflow execution part 122 acquires items again, and automatically updates XML descriptions to change current items of the association engine (as the �MERGE� engine) of the sequential number 13 to be the item B, the item C, the item D, the item E, the item F and the item G, so as to eliminate the item inconsistency.
FIG. 12B is a conceptual diagram showing a state in which the item inconsistency is eliminated, according to the embodiment of the present invention. In FIG. 12B, since the item A and the item B of the extraction engine (as the �MERGE� engine) of the sequential number 1 are changed to the item B and the item G, the item B, the item C, the item D, the item E, the item F, and the item G are set with respect to the extraction engine (as the �MERGE� engine) of the sequential number 13.
In FIG. 14 through FIG. 17, information concerning the business flow shown in FIG. 11 is defined by a description 301. A tag <businessflow> is used to define a group name and a maximum number of rows (rows=�5�) of the matrix 50 f used for this business flow. The maximum number of rows indicates the number of the workflows. A tag <information> is used to define information concerning a creation of this business flow.
A description 320 defines information concerning the workflow 21. By a tag <workflow>, a maximum number columns (cols=�4�), identification information (id=�workflow.1�) of the workflow 21, a name (name=�WORKFLOW 21�) of the workflow 21, an arrangement location (fposy=�0�) of the workflow 21 in the matrix 50 f, the maximum number of rows (rows=�1�) in the workflow 21, the execution time (runtime=�00:00:13�), and a like.
Subsequently, a description 322 defines the engine set as the �AGGREGATION� engine of the sequential number 3 in the workflow 21 by using a tag <engine>. Setting information concerning this �AGGREGATION� engine of the sequential number 3 is defined by using a plurality of tags <setting> as shown in a description 322 a and a description 322 b. Similarly, a description 323 defines the engine set as the �TREND� engine of the sequential number 4 in the workflow 21. Setting information concerning this �TREND� engine of the sequential number 4 is defined by using a plurality of tags <setting> as shown in a description 323 a, a description 323 b, a description 323 c, a description 323 d, a description 323 e, and a description 323 f. Similarly, a description 324 defines the engine set as the �AREA DIVISION� engine of the sequential number 2 in the workflow 21. Setting information concerning this �AREA DIVISION� engine of the sequential number 2 is defined by using a plurality of tags <setting> as shown in a description 324 a and a description 324 b. Similarly, a description 324 defines the engine set as the �CSV IMPORT� engine of the sequential number 1 in the workflow 21. Setting information concerning this �CSV IMPORT� engine of the sequential number 1 is defined by using a plurality of tags <setting> as shown in a description 325 a and a description 325 b. Next, a description 330 defines information concerning the workflow 22. By the tag <workflow>, the maximum number columns (cols=�4�), the identification information (id=�workflow.2�) of the workflow 22, a name (name=�WORKFLOW 22�) of the workflow 22, an arrangement location (fposy=�1�) of the workflow 22 in the matrix 50 f, the maximum number of rows (rows=�2�) in the workflow 22, the execution time (runtime=�00:00:06�), and a like.
Subsequently, a description 332 defines the engine set as the �MONITOR� engine of the sequential number 6 in the workflow 22 by using a tag <engine>. Setting information concerning this �MONITOR� engine of the sequential number 6 is defined as shown in a description 332 a. Next, a description 340 defines information concerning the workflow 23. By the tag <workflow>, the maximum number columns (cols=�5�), the identification information (id=�workflow.3�) of the workflow 23, a name (name=�WORKFLOW 23�) of the workflow 23, an arrangement location (fposy=�2�) of the workflow 23 in the matrix 50 f, the maximum number of rows (rows=�2�) in the workflow 23, the execution time (runtime=�00:00:01�), and a like.
Subsequently, a description 342 defines the engine set as the �MERGE� engine of the sequential number 16 in the workflow 24 by using the tag <engine>. Setting information concerning this �MERGE� engine of the sequential number 16 is defined as shown in a description 342 a. Next, a description 350 defines information concerning the workflow 24. By the tag <workflow>, the maximum number columns (cols=�5�), the identification information (id=�workflow.4�) of the workflow 24, a name (name=�WORKFLOW 24�) of the workflow 24, an arrangement location (fposy=�3�) of the workflow 24 in the matrix 50 f, the maximum number of rows (rows=�2�) in the workflow 24, the execution time (runtime=�00:00:01�), and a like.
Subsequently, a description 352 defines the engine set as the �CORRELATION CHART� engine of the sequential number 17 in the workflow 24 by using the tag <engine>. Setting information concerning this �CORRELATION CHART� engine of the sequential number 17 is defined as shown in a description 352 a. A description 501 using a tag <link-set> defines the data link lines L11 through L34 arranged by the user shown in FIG. 11.
A description 511 using a tag <link> defines the data link line L11, and describes the data association from �workflow.21/process.areadivide.1� (�AREA DIVISION� engine of the sequential number 2 in the workflow 21) to �workflow.21/process.calculate.1� (�AGGERATION� engine of the sequential number 3 in the workflow 21) by using a tag <from> and a tag <to>.
A description 512 using the tag <link> defines the data link line L12, and describes the data association from �workflow.21/process.calculate.1� (�AGGERATION� engine of the sequential number 3 in the workflow 21) to �workflow.21/result.trend.1� (�TREND� engine of the sequential number 4 in the workflow 21) by using the tag <from> and the tag <to>.
A description 513 using the tag <link> defines the data link line L13, and describes the data association from �workflow.21/extract.import.1� (�CSV IMPORT� engine of the sequential number 1 in the workflow 21) to �workflow.21/process.areadivide.1� (�AREA DIVISION� engine of the sequential number 2 in the workflow 21) by using the tag <from> and the tag <to>.
A description 521 using the tag <link> defines the data link line L14, and describes the data association from �workflow.22/extract.lot.1� (�LOT� engine of the sequential number 5 in the workflow 22) to �workflow.22/extract.monitordata.2� (�MONITOR� engine of the sequential number 6 in the workflow 22) by using the tag <from> and the tag <to>.
A description 522 using the tag <link> defines the data link line L22, and describes the data association from �workflow.22/process.merge.3� (�MERGE� engine of the sequential number 10 in the workflow 22) to �workflow.22/result.trend.2� (�TREND� engine of the sequential number 6 in the workflow 22) by using the tag <from> and the tag <to>.
A description 523 using the tag <link> defines the data link line L23, and describes the data association from �workflow.22/result.trend.1� (�TREND� engine of the sequential number 7 in the workflow 22) to �workflow.22/result.export.1� (�CSV EXPORT� engine of the sequential number 8 in the workflow 22) by using the tag <from> and the tag <to>.
A description 524 using the tag <link> defines the data link line L24, and describes the data association from �workflow.22/extract.monitordata.2� (�MONITOR� engine of the sequential number 6 in the workflow 22) to �workflow.22/process.merge.3� (�MERGE� engine of the sequential number 10 in the workflow 22) by using the tag <from> and the tag <to>.
A description 525 using the tag <link> defines the data link line L25, and describes the data association from �workflow.22/extract.import.4� (�CSV IMPORT� engine of the sequential number 9 in the workflow 22) to �workflow.22/process.merge.3� (�MERGE� engine of the sequential number 10 in the workflow 22) by using the tag <from> and the tag <to>.
A description 526 using the tag <link> defines the data link line L26, and describes the data association from �workflow.22/extract.monitordata.2� (�MONITOR� engine of the sequential number 6 in the workflow 22) to �workflow.22/result.trend.1� (�TREND� engine of the sequential number 7 in the workflow 22) by using the tag <from> and the tag <to>.
A description 527 using the tag <link> defines the data link line L27, and describes the data association from �workflow.22/process.merge.3� (�MERGE� engine of the sequential number 10 in the workflow 22) to �workflow.23/process.merge.2� (�MERGE� engine of the sequential number 13 in the workflow 23) by using the tag <from> and the tag <to>. The description 527 of the data link line L27 defines the data association toward another workflow 23.
A description 528 using the tag <link> defines the data link line L28, and describes the data association from �workflow.21/process.calculate.1� (�AGGREGATION� engine of the sequential number 3 in the workflow 22) to �workflow.23/process.merge.2� (�MERGE� engine of the sequential number 13 in the workflow 23) by using the tag <from> and the tag <to>. The description 528 of the data link line L28 defines the data association toward another workflow 23.
A description 529 using the tag <link> defines the data link line L29, and describes the data association from �workflow.23/process.merge.2� (�MERGE� engine of the sequential number 10 in the workflow 22) to �workflow.23/result.trend.2� (�TREND� engine of the sequential number 14 in the workflow 23) by using the tag <from> and the tag <to>.
A description 530 using the tag <link> defines the data link line L30, and describes the data association from �workflow.23/process.merge.2� (�MERGE� engine of the sequential number 14 in the workflow 23) to �workflow.23/result.xyplot.1� (�CORRELATION CHART� engine of the sequential number 15 in the workflow 23) by using the tag <from> and the tag <to>.
A description 531 using the tag <link> defines the data link line L31, and describes the data association from �workflow.22/extract.lot.1� (�LOT� of the sequential number 5 in the workflow 23) to �workflow.23/extract.processdata.1� (�PROCESS� engine of the sequential number 12 in the workflow 23) by using the tag <from> and the tag <to>. The description 531 of the data link line L31 defines the data association toward another workflow 23.
A description 532 using the tag <link> defines the data link line L32, and describes the data association from �workflow.24/process.merge.1� (�MERGE� engine of the sequential number 16 in the workflow 24) to �workflow.24/result.xyplot.1� (�CORRELATION CHART� engine of the sequential number 17 in the workflow 24) by using the tag <from> and the tag <to>.
A description 533 using the tag <link> defines the data link line L33, and describes the data association from �workflow.23/extract.processdata.1� (�PROCESS� engine of the sequential number 12 in the workflow 23) to �workflow.24/process.merge.1� (�MERGE� engine of the sequential number 16 in the workflow 24) by using the tag <from> and the tag <to>. The description 533 of the data link line L33 defines the data association toward another workflow 24.
A description 534 using the tag <link> defines the data link line L34, and describes the data association from �workflow.23/process.merge.2� (�MERGE� engine of the sequential number 13 in the workflow 23) to �workflow.24/process.merge.1� (�MERGE� engine of the sequential number 16 in the workflow 24) by using the tag <from> and the tag <to>. The description 534 of the data link line L34 defines the data association toward another workflow 24.
In the workflow 21, the engines are arranged in an order of the �CSV IMPORT� engine, the �AREA DIVISION� engine, the �AGGREGATION� engine, and the �TREND� engine. However, since the user flexibly places those engines in accordance with the cognitive thought process of the user, a setting order in which the user places the engines may not be the same as an arrangement order. Also, in the workflow 22 through the workflow 24, the setting orders by the user may not be the same as the arrangement orders.
In the workflow 131, the data associations are set from a �PRIMARY TEST� engine to a plurality of engines: a �TREND� engine, a �AGGREGATION� engine, and an �AREA DIVISION� engine. In addition, the data association is set from the �PRIMARY TEST� engine in the workflow 131 to a �FILTER� engine in the workflow 132.
In the third example in FIG. 18, a single data extraction result of the �PRIMARY TEST� engine is associated with one graph process and three types of processes. One of the three processes further conducts a process, and produces a graph indicating a final result. By associating a process result among the engines being the program icon to be processed for a next engine being the program icon, it is possible to realize data process in accordance with the cognitive though process of the user.
A plurality of setting information are automatically modified in the workflow design data by corresponding to requirements of the �TREND� engine, the �AGGREGATION� engine, the �AREA DIVISION� engine, and the �FILTER� engine. Therefore, it is possible to flexibly execute the business flow and the workflow in response to the cognitive thought process of the user.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4802094 *Jun 27, 1986Jan 31, 1989Hitachi, Ltd.Process monitoring apparatus for process management in production and assembly linesUS5418945 *May 18, 1992May 23, 1995Motorola, Inc.File based and highly available hybrid databaseUS5455903 *May 31, 1991Oct 3, 1995Edify Corp.Object oriented customer information exchange system and methodUS5628112 *Mar 3, 1995May 13, 1997Ford Motor CompanyCircuit board assembly system and methodUS5630069 *Jan 15, 1993May 13, 1997Action Technologies, Inc.Computer based systemUS5768506 *May 20, 1997Jun 16, 1998Hewlett-Packard Co.Method and apparatus for distributed workflow building blocks of process definition, initialization and executionUS5774661 *Apr 18, 1995Jun 30, 1998Network Imaging CorporationComputer-implemented method of automatically generating/controlling workflowUS5819270 *Aug 27, 1997Oct 6, 1998Massachusetts Institute Of TechnologyComputer system for displaying representations of processesUS5822585 *May 30, 1997Oct 13, 1998Compuware CorporationIn a computer networkUS5930512 *Oct 18, 1996Jul 27, 1999International Business Machines CorporationMethod and apparatus for building and running workflow process models using a hypertext markup languageUS5937388 *Mar 21, 1997Aug 10, 1999Hewlett-Packard CompanySystem and method for performing scalable distribution of process flow activities in a distributed workflow management systemUS6026365 *Aug 18, 1997Feb 15, 2000Fuji Xerox Co., Ltd.Workflow support system and method of the sameUS6073109 *Dec 12, 1996Jun 6, 2000Action Technologies, Inc.Computerized method and system for managing business processes using linked workflowsUS6225998 *Dec 2, 1997May 1, 2001Aspect CommunicationsVisual design of workflows for transaction processingUS6243092 *Dec 2, 1997Jun 5, 2001Aspect CommunicationsTransaction flow editing toolUS6397192 *Sep 18, 1998May 28, 2002I2 Technologies Us, Inc.Synchronizing one or more workflows using one or more synchronization-join activities that include synchronization logicUS6697784 *Jun 5, 2001Feb 24, 2004EnterworksWorkflow management system, method, and medium with personal subflowsUS6810294 *Aug 16, 2002Oct 26, 2004Asyst Technologies, Inc.Method and apparatus for automating a microelectronic manufacturing processUS6853974 *Aug 20, 1999Feb 8, 2005Hitachi, Ltd.Workflow system, workflow control method and storage mediumUS6859676 *Apr 9, 2001Feb 22, 2005Ciena CorporationMethod of improving quality of manufactured modulesUS6889375 *Nov 17, 2000May 3, 2005Cisco Technology, Inc.Method and system for application developmentUS6986138 *Apr 6, 2000Jan 10, 2006Hitachi, Ltd.Virtual work flow management methodUS7065493 *Apr 6, 2001Jun 20, 2006International Business Machines CorporationWorkflow system and methodUS7069101 *Jul 29, 1999Jun 27, 2006Applied Materials, Inc.Computer integrated manufacturing techniquesUS7130709 *Nov 18, 2002Oct 31, 2006Kimberly-Clark Worldwide, Inc.Manufacturing information and alarming system and methodUS7221377 *Apr 24, 2000May 22, 2007Aspect CommunicationsApparatus and method for collecting and displaying information in a workflow systemUS7242991 *Apr 15, 2003Jul 10, 2007Invensys Systems, Inc.Workflow control configurator for use with process, factory-floor, environmental, computer aided manufacturing-based or other control systemUS7296103 *Oct 5, 2004Nov 13, 2007Advanced Micro Devices, Inc.Method and system for dynamically selecting wafer lots for metrology processingUS7433801 *Dec 5, 2005Oct 7, 2008Ford Motor CompanyIdentifying and visualizing faults in PLC-based manufacturing systemsUS7698013 *Jul 25, 2007Apr 13, 2010Honda Motor Co., Ltd.Parts production management system and parts production management methodUS7844910 *Sep 22, 2003Nov 30, 2010Fuji Xerox Co., Ltd.Linking information making device, linking information making method, recording medium having recorded a linking information making program, and document processing system therewithUS20010038708 *Jun 29, 2001Nov 8, 2001Seiji IshikawaInspection data analyzing systemUS20030061266 *Sep 27, 2001Mar 27, 2003Norman Ken OuchiProject workflow systemUS20030150908 *Nov 27, 2002Aug 14, 2003Kimberly-Clark Worldwide, Inc.User interface for reporting event-based production information in product manufacturingUS20030181991 *Dec 16, 2002Sep 25, 2003Agile Software CorporationSystem and method for managing and monitoring multiple workflowsUS20030195762 *Oct 15, 2002Oct 16, 2003David GleasonAutomated workflowUS20030220707 *Apr 15, 2003Nov 27, 2003Budinger Bruce D.Workflow control configurator for use with process, factory-floor, environmental, computer aided manufacturing-based or other control systemUS20040078373 *May 14, 2003Apr 22, 2004Adel GhoneimyWorkflow system and methodUS20040083448 *Jul 29, 2003Apr 29, 2004Karsten SchulzWorkflow management architectureUS20040230941 *Dec 23, 2003Nov 18, 2004Marin Mike A.Component integratorUS20050066304 *Sep 10, 2004Mar 24, 2005Captaris, Inc.Custom and customizable components, such as for workflow applicationsUS20050246215 *Jul 8, 2005Nov 3, 2005Rackham Guy J JSystem and method for alignment of an enterprise to a component business modelUS20060074736 *Feb 23, 2005Apr 6, 2006Microsoft CorporationProgramming interface for a componentized and extensible workflow modelUS20060173724 *Jan 28, 2005Aug 3, 2006Pegasystems, Inc.Methods and apparatus for work management and routingUS20070008584 *Jul 5, 2006Jan 11, 2007Konica Minolta Business Technologies, Inc.Method and apparatus for displaying workflowUS20070061358 *Sep 13, 2005Mar 15, 2007Brooks Patrick JWorkflow application having linked workflow componentsUS20070088583 *Oct 14, 2005Apr 19, 2007Synergy Business Solutions Inc.Autonomic workflow application program generator and method thereofUS20070120736 *Nov 29, 2005May 31, 2007General Electric CompanyMethod and system for discrete location triggering for enhanced asset management and trackingEP1065618A2Aug 27, 1999Jan 3, 2001Hitachi Software Engineering Co., Ltd.Workflow system with business process definitionJP2001014389A Title not availableJP2002074253A Title not availableJP2002245215A Title not availableJP2002259643A Title not availableJP2005182635A Title not available* Cited by examinerNon-Patent CitationsReference1 *Goff et al. "From design to Production Control Through the Integration of Engineering Data Management and Workflow Management Systems" CMS Note 1997.2 *Sun, Sherry; Zhao, Leon; and Sheng, Olivia, "Data Flow Modeling and Verification in Business Process Management" (2004). AMCIS 2004 Proceedings. Paper 508.3 *Tyson R. Browning "Process Integration Using the Design Structure Matrix" Systems Engineering, vol. 5, No. 3, 2002 Wiley Periodicals, Inc.* Cited by examinerClassifications U.S. Classification705/7.27, 705/7.26, 705/7.11, 705/7.12, 700/97International ClassificationG06Q50/04, G05B19/418, G06Q10/06, G06Q10/00, G06Q50/00Cooperative ClassificationG06Q10/06316, G06Q10/06395, G06Q10/0631, G06Q10/0633, G06Q10/063, G06Q10/06European ClassificationG06Q10/06, G06Q10/063, G06Q10/06316, G06Q10/0631, G06Q10/06395, G06Q10/0633Legal EventsDateCodeEventDescriptionJul 22, 2010ASAssignmentEffective date: 20100401Free format text: CHANGE OF NAME;ASSIGNOR:FUJITSU MICROELECTRONICS LIMITED;REEL/FRAME:24748/328Owner name: FUJITSU SEMICONDUCTOR LIMITED,JAPANOwner name: FUJITSU SEMICONDUCTOR LIMITED, JAPANFree format text: CHANGE OF NAME;ASSIGNOR:FUJITSU MICROELECTRONICS LIMITED;REEL/FRAME:024748/0328Dec 11, 2008ASAssignmentOwner name: FUJITSU MICROELECTRONICS LIMITED, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;REEL/FRAME:021977/0219Effective date: 20081104Owner name: FUJITSU MICROELECTRONICS LIMITED,JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100209;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100216;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100223;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100225;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100302;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100309;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100316;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100323;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100329;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100420;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100427;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:21977/219Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;REEL/FRAME:21977/219Apr 13, 2007ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TOYOFUKU, TSUYOSHI;KOSAKA, TSUNEHIRO;FUJIMURA, HIDEKI;REEL/FRAME:019186/0192;SIGNING DATES FROM 20061214 TO 20061227Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TOYOFUKU, TSUYOSHI;KOSAKA, TSUNEHIRO;FUJIMURA, HIDEKI;SIGNING DATES FROM 20061214 TO 20061227;REEL/FRAME:019186/0192RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google