|
|
|
Generating database or data structure (e.g., via user interface) |
Man-hour management system7010541
Abstract
A man-hour management system (1 in FIG. 2) which manages man-hours for producing a product, comprising a walk man-hour conversion table (12) for performing registration management of standardized man-hours for walks; a work constituent condition table (10) for performing registration management of constituent work CW (element work), and conditions for each of the constituent work CW (element work); a standardized man-hour table (11) for performing registration management of standardized man-hour analysis contents and standardized man-hours for the constituent work CW (element work) or the constituent work CW (element work) conditions; a main man-hour management table (18) for performing registration management/reorganization management of constituent work CW (element work) items in units of processes, data being assigned to the constituent work CW (element work) items from the tables (10, 11, 12), or data being inputted and set to the constituent work CW (element work) items; a process name table (19) for performing registration management/reorganization management of names of the processes; and man-hour output means (OS) for outputting man-hour information. The man-hour management system can analyze man-hours in each individual process unit and for a state between the processes.
Claims
What is claimed is:
1. A man-hour management system which manages man-hours for producing automobiles, comprising:
a server, a database, connection terminals, and an Ethernet;
said database comprising:
a walk man-hour conversion table for performing registration management of standardized man-hours for walks which are generated by works;
a work constituent condition table for performing registration management of constituent works for use in managing the man-hours, end having conditions for each of the constituent works;
a standardized man-hour table for performing registration management of standardized man-hour analysis contents and standardized man-hours for the constituent works or the constituent work conditions which are under the registration management of said work constituent condition table;
a main man-hour management table for managing item data for constituent works in process units and for performing registration management and/or reorganization management of constituent work items in the units of processes, data being assigned to the constituent work items from said walk awn-hour conversion table, said work constituent condition table and said standardized man-hour table, or data being inputted and set to the constituent work items; and
a process name table for performing registration management and/or reorganization management of names of the processes; and
said man-hour management system further including man-hour output means including a man-hour output system program, a timing graph output program, a process balancing table output program, a net & loss aggregation table output program, an individual-process specification aggregation table output program, a history management table output program, and a main man-hour management output program, for outputting man-hour information by being assigned data from said main man-hour management table and said process name table.
2. A man-hour management system according to claim 1, comprising a change history table for performing save management of work change contents in units of the processes;
wherein said man-hour output means outputs the man-hour information by being assigned data also from said change history table.
3. A man-hour management system according to claim 1, comprising a timing graph data table for performing registration management of data of a timing graph, data being assigned to said timing graph data table from said main man-hour management table;
wherein said man-hour output means outputs the man-hour information by being assigned data also from said timing graph data table.
4. A man-hour management system according to claim 1, comprising a line name table for performing registration management of modes of lines which implement works;
wherein said main man-hour management table is assigned data also from said line name table.
5. A man-hour management system according to claim 1, comprising a series table for performing registration management of series and types associated with the series;
wherein said main man-hour management table is assigned data also from said series table.
6. A man-hour management system according to claim 1, comprising a derivation table for performing registration management of derivatives associated with each of the series and types;
wherein said main man-hour management table is assigned data also from said derivation table.
7. A man-hour management system according to claim 1, comprising:
a database in which the tables are stored; and
series data backup means for extracting the data of said tables in series units as have become unnecessary, from said database, and for re-storing said data of said tables extracted in series units, in said database.
8. A man-hour management system according to claim 1, wherein the constituent work has its each movement classified into one of a main movement, an auxiliary movement and a quasi movement, and standardized man-hours analyzed are set for said each movement.
Description
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a man-hour management system which manages man-hours for producing a product, and more particularly to a man-hour management system which offers man-hour information effective to diminish the numbers of man-hours in each individual process unit and between processes.
2. Description of the Related Art
In case of producing a product, processes and works or jobs in each process are managed in terms of man-hours in order to grasp how much labor is required for the production of the product. Besides, how a production cost is curtailed becomes important in the case of producing the product, and diminution in the number of man-hours is very effective for curtailing the production cost. Therefore, techniques for calculating the man-hours and managing them become very important for judging the degrees to which the arrangement of workers or operators, diminution in the number of wasteful man-hours, process organization, etc. in a production line contribute to the curtailment of the production cost and the achievement of a target production cost. In each manufacturer, accordingly, man-hours are managed by a man-hour management system utilizing various techniques, and they are analyzed on the basis of man-hour information delivered from the man-hour management system.
A man-hour analysis in the prior art is such that a process is separated into personal works and equipmental works, and that net man-hours are respectively cumulated for the works by persons and the works by equipment so as to be compared. By way of example, FIG. 44 shows a graph of net man-hours for respective works in one process as is utilized in the prior-art man-hour analysis. In the graph 100, the works of personal man-hours 101 and equipmental man-hours 102 are listed in a vertical direction, while the net man-hours for the respective works are cumulated in a horizontal direction. In the man-hour analysis based on the graph 100, the magnitudes of the net man-hours extending horizontally are compared, and works of large net man-hours (for example, a work by a welding robot 1 and a component preparing work) are narrowed down as works which are subjects for diminutions in the numbers of man-hours. Besides, automation, the enhancement of an equipment precision, the reconsideration of a personal work procedure, or the like is promoted for such a work narrowed down, so as to attain diminution in the number of net man-hours, in turn, curtailment in a production cost.
Since, however, the prior-art man-hour analysis is made for the individual works, it is alien to an analysis for overall man-hours required for one cycle in each actual process (the total man-hours of net man-hours and loss man-hours in each process in one cycle of product production). Therefore, the prior-art man-hour analysis cannot analyze man-hours in each individual process unit, between processes or in view of the whole production line. More specifically, it cannot analyze man-hours in the case where a certain work is transferred to the next work, or where a certain process is transferred to the next process. Further, it cannot analyze man-hours for the state between works proceeding concurrently or for the state between processes proceeding concurrently. Accordingly, a man-hour management system in the prior art is difficult to make a man-hour analysis for determining process organization, the arrangement of equipment within a factory, the arrangement of workers in a production line, or the like, in each individual process unit or in consideration of the state between processes. Consequently, it is difficult to efficiently curtail a production cost.
SUMMARY OF THE INVENTION
An object of the present invention is to provide a man-hour management system which can analyze man-hours in each individual process unit and between processes.
A man-hour management system according to the present invention having accomplished the above object is a man-hour management system which manages man-hours for producing a product, characterized by comprising a walk man-hour conversion table for performing registration management of standardized man-hours for walks which are generated by works; a work constituent condition table for performing registration management of constituent work CW (element work) for use in managing the man-hours, and conditions for each of the constituent work CW (element work); a standardized man-hour table for performing registration management of standardized man-hour analysis contents and standardized man-hours for the constituent work CW (element work) or the constituent work CW (element work) conditions which are under the registration management of said work constituent condition table; a main man-hour management table for performing registration management/reorganization management of constituent work CW (element work) items in units of processes, data being assigned to the constituent work CW (element work) items from said walk man-hour conversion table, said work constituent condition table and said standardized man-hour table, or data being inputted to and set as the constituent work CW (element work) items; a process name table for performing registration management/reorganization management of names of the processes; and man-hour output means for outputting man-hour information by being assigned data from said main man-hour management table and said process name table.
According to this man-hour management system, the standardized man-hours are set for the constituent work CW (element work) or the conditions of each of the constituent work CW (element work), and the constituent work CW (element work) items are managed in process units, so that a man-hour analysis can be made between the constituent work CW (element work) within each process or between the processes. Therefore, a process organization loss, etc. can be readily detected, and a plant capability loss, etc. can be relieved in a short time. Moreover, at a model change or at the development of a new car type, a man-hour analysis can be made on the basis of the data of a close car type under the registration management, so that process organization of little loss can be performed in a short term.
By the way, the "constituent work CW (element work)" is a simple work in each process. The "process" is a unit in which one work can be completed. The "standardized man-hours" are standard (reference) man-hours (work done) in the constituent work CW (element work) or in each of conditions having been set for the constituent work CW (element work). The "man-hour information" is information about man-hours as has been obtained in such a way that the data of the standardized man-hours or the likes managed in each individual process unit are converted into a form (such as table or graph) effective for analyzing man-hours. The information can be outputted by various means such as screen display, file output and paper sheet output.
Besides, the man-hour management system is characterized by comprising a change history table for performing save management of work change contents in units of the processes;
so that said man-hour output means outputs the man-hour information by being assigned data also from said change history table.
According to this man-hour management system, each time man-hours are changed by the alteration of a shape, the curtailment of a cost, or the like, the change of work contents on that occasion is managed along with the changed man-hours, and hence, the course in which the man-hours have been changed can be readily grasped. In a man-hour analysis at the development of a new car type, a model change, or the like, therefore, data can be diverted to a similar alteration in shape, a similar place of curtailed cost, or the like.
Further, the man-hour management system is characterized by comprising a timing graph data table for performing registration management of data of a timing graph, data being assigned to said timing graph data table from said main man-hour management table; so that said man-hour output means outputs the man-hour information by being assigned data also from said timing graph data table.
According to this man-hour management system, the wait time and working time of each constituent work CW (element work) and the start time of each constituent work CW (element work) are managed as timing graph data, so that the wait time of the constituent work CW (element work) can be readily detected. Therefore, a wasteful wait time can be shortened in a short time.
Alternatively, the man-hour management system is characterized by comprising a line name table for performing registration management of modes of lines which implement works; so that said main man-hour management table is assigned data also from said line name table.
According to this man-hour management system, the lines for implementing processes or constituent work CW (element work) are registered and managed, so that the line which is implementing the process or the constituent work CW (element work) can be readily referred to.
Further, the man-hour management system is characterized by comprising a series table for performing registration management of series and types associated with the series; so that said main man-hour management table is assigned data also from said series table.
According to this man-hour management system, the series and types are registered and managed, so that the series or type for which the process or constituent work CW (element work) is proceeding can be readily referred to.
Moreover, the man-hour management system is characterized by comprising a derivation table for performing registration management of derivatives associated with each of the series and the types; so that said main man-hour management table is assigned data also from said derivation table.
According to this man-hour management system, the derivatives associated with the series are registered and managed, so that the series to which any of the derivatives being handled belongs can readily referred to.
Besides, the man-hour management system is characterized by comprising a database in which the tables are stored; and series data backup means for extracting the data of said tables in series units as have become unnecessary, from said database, and for re-storing said data of said tables extracted in series units, in said database.
According to this man-hour management system, the data having become unnecessary can be extracted from the database, and the extracted data can be stored in the database again, so that the database can be efficiently utilized.
In addition, the man-hour management system is characterized in that the constituent work CW (element work) has its each movement classified into one of a main action, a supplemental action and a quasi action, and that standardized man-hours analyzed are set for said each movement.
According to this man-hour management system, the standardized man-hours are set on the basis of each of the movements refined from the constituent work CW (element work), so that the set standardized man-hours differ very little from real man-hours of the constituent work CW (element work) by individual workers.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram showing the general construction of a man-hour management system according to an embodiment of the present invention;
FIG. 2 is a diagram showing the system architecture of the man-hour management system according to the embodiment;
FIG. 3 is a diagram showing the relations of a main man-hour management table with various other tables in the embodiment;
FIG. 4 is a diagram showing the data hierarchical structure of the man-hour management system in the embodiment;
FIG. 5 shows the menu screen of a standardized man-hour management system in the embodiment;
FIG. 6 shows the registration screen of walk man-hour management in the embodiment;
FIGS. 7A through 7C are diagrams for explaining constituent work CW (element work) condition management in the embodiment, in which FIG. 7A shows the relationship between a classification table for constituent work CW (element work) and conditions and a work constituent condition table, FIG. 7B shows a screen for setting a constituent work CW (element work) name, and FIG. 7C shows a screen for registering conditions in a constituent work CW (element work);
FIG. 8 is a diagram showing the relationship between the main man-hour management table and the work constituent condition table as well as a standardized man-hour table in the embodiment;
FIGS. 9A and 9B are diagrams for explaining standardized man-hour registration in the embodiment, in which FIG. 9A shows the relationship between the classification table for constituent work CW (element work) and conditions and the standardized man-hour table, while FIG. 9B shows a screen for registering standardized man-hour analysis contents and standardized man-hours;
FIGS. 10A and 10B are diagrams for explaining constituent name condition item maintenance in the embodiment, in which FIG. 10A shows the relationship between the classification table for constituent work CW (element work) and conditions and the work constituent condition table as well as the standardized man-hour table, while FIG. 10B shows a screen for editing constituent name condition items;
FIG. 11 shows the menu screen of a derivation management system in the embodiment;
FIGS. 12A and 12B are diagrams for explaining line name management in the embodiment, in which FIG. 12A shows the relationship between the registration screen and line name table of the line name management and the main screen of main man-hour management, while FIG. 12B shows the data hierarchical structure of an automobile production line;
FIG. 13 is a diagram showing the relationship between the registration screen and series table of series registration management and the main screen of the main man-hour management in the embodiment;
FIG. 14 is a diagram showing the relationship between the registration screen and derivation table of derivation classification registration management and the main screen of the main man-hour management in the embodiment;
FIG. 15 shows the registration screen of derivation format registration management in the embodiment;
FIG. 16 shows the registration screen of derivation code table management in the embodiment;
FIGS. 17A and 17B are diagrams for explaining a main man-hour management system (main man-hour management) in the embodiment, in which FIG. 17A shows the main screen of the main man-hour management system (main man-hour management), while FIG. 17B is a diagram for explaining the sheet invoking screen of the main man-hour management;
FIGS. 18A through 18F are diagrams for explaining the derivation setting of the main man-hour management in the embodiment, in which FIG. 18A shows the main screen of the main man-hour management, FIG. 18B shows Example 1 of a derivation display selection screen, FIG. 18C shows Example 2 of the derivation display selection screen, FIG. 18D shows Example 3 of the derivation display selection screen, FIG. 18E is a diagram for explaining the display level of constituent work CW (element work) items for the setting of the derivation display selection screen, and FIG. 18F shows the priority level of the displays of the constituent work CW (element work) items;
FIG. 19 is a diagram for explaining the setting of the constituent work CW (element work) items in the main screen of the main man-hour management in the embodiment;
FIG. 20 is a diagram for explaining the condition setting and standardized man-hour setting of a constituent work CW (element work) in the main screen of the main man-hour management in the embodiment;
FIG. 21 is a diagram for explaining wait man-hour setting in the main screen of the main man-hour management in the embodiment;
FIG. 22 is a diagram for explaining walk man-hour setting in the main screen of the main man-hour management in the embodiment;
FIG. 23 is a diagram for explaining man-hour subtotal and total (in the presence of values added) setting in the main screen of the main man-hour management in the embodiment;
FIG. 24 is a diagram for explaining man-hour subtotal and total (in the absence of values added) setting and total man-hour setting in the main screen of the main man-hour management in the embodiment;
FIG. 25 shows the registration screen of process name management in the embodiment;
FIG. 26 shows the alteration screen of the process name management in the embodiment;
FIG. 27 shows the input screen of change history management in the embodiment;
FIG. 28 shows the display screen of the change history management in the embodiment;
FIGS. 29A and 29B are diagrams for explaining timing graph management in the embodiment, in which FIG. 29A shows a timing graph screen, while FIG. 29B shows an input screen for timing graph data;
FIG. 30 is a diagram for explaining working man-hour setting in the timing graph management in the embodiment;
FIG. 31 is a diagram for explaining start time setting in the timing graph management in the embodiment;
FIG. 32 is a diagram showing a procedure for creating a timing graph in the timing graph management in the embodiment;
FIGS. 33A and 33B are diagrams for explaining a series data backup system in the embodiment, in which FIG. 33A shows the relations between a database and data to-be-backed-up, while FIG. 33B shows the classification of series data;
FIG. 34 shows the main screen of the series data backup system in the embodiment;
FIG. 35 shows the menu screen of a man-hour output system in the embodiment;
FIG. 36 shows the condition setting screen of the man-hour output system in the embodiment;
FIGS. 37A and 37B are diagrams for explaining timing graph outputs in the embodiment, in which FIG. 37A shows a main man-hour management screen, while FIG. 37B shows a timing graph screen;
FIG. 38 shows an output screen for process balancing table outputs in the embodiment;
FIG. 39 shows an output screen for net & loss man-hour aggregation table outputs in the embodiment;
FIG. 40 shows an output screen for individual-process specification aggregation table outputs in the embodiment;
FIG. 41 shows an output screen for history management table outputs in the embodiment;
FIG. 42A is a diagram showing losses involved within a basic time (man-hours), while FIG. 42B is a diagram showing the relationship between a process organization loss as well as a man-hour difference loss and car types of different man-hours;
FIG. 43 is a diagram for explaining the refinement of a constituent work CW (element work) based on an improved MOST according to the embodiment; and
FIG. 44 is a graph showing net man-hours for respective works in a prior-art analysis.
PREFERRED EMBODIMENT OF THE INVENTION
An embodiment of a man-hour management system according to the present invention will be described below with reference to the drawings.
With the man-hour management system according to the present invention, standardized man-hours for the walk of a worker are managed by a walk man-hour conversion table, a constituent work CW (element work) serving as a reference for managing standardized man-hours and conditions in the constituent work CW (element work) are managed by a work constituent condition table, and standardized man-hours for the constituent work CW (element work) or the respective conditions in the constituent work CW (element work) are managed by a standardized man-hour table. Besides, with the man-hour management system, in order to manage item data for the constituent work CW (element work) in each individual process unit, the standardized man-hours of every constituent work CW (element work) or every condition of the constituent work CW (element work) are managed by a main man-hour management table in each individual process unit on the basis of the walk man-hour conversion table, work constituent condition table and standardized man-hour table, while the names of processes are managed by a process name table. Further, with the man-hour management system, man-hour information can be outputted in each individual process unit on the basis of the main man-hour management table and process name table. In addition, with the man-hour management system, a plurality of production lines are managed by a line name table, a plurality of series are managed by a series table, and derivatives within the series are managed by a derivation table, while the data of the three tables are managed in each individual process unit by the main man-hour management table. Moreover, with the man-hour management system, the alteration history of the main man-hour management table is managed by a change history table, and the standardized man-hour information of the main man-hour management table is managed as time-series data by a timing graph data table. Therefore, the man-hour management system according to the present invention can analyze man-hours in each individual process unit.
In this embodiment, the man-hour management system according to the present invention shall be applied to a man-hour management system in automobile production. Further, in this embodiment, the field of welding will be mentioned as an example from within the automobile production. In case of automobiles, sorts of cars correspond to series, and each of the sorts of cars includes types of cars, such as sedan type, wagon type and hardtop type. Further, the same type of cars includes cars of 4WD and 2WD, AT and MT, right steering wheel and left steering wheel, etc., which correspond to derivatives. Besides, a large-scale automobile production factory is furnished with a plurality of production lines such as a first line and a second line, and line names are given in each individual work unit within the production lines.
Besides, in this embodiment, a unit which is the minimum unit of self-completion and in which a cost constitution can be grasped shall be defined as a "cost center". Besides, in this embodiment, work contents based on the cost center are set as a unit for managing man-hours. In the case of, for example, the welding in the automobile production, the cost center can be sorted into a front floor, a rear floor, a dashboard, a roof, a side panel, a floor subassembly, a roof subassembly, a front door, a rear door, a trunk tailgate, etc. That is, the cost center can be regarded as one line. Besides, the line is constructed of the aggregate of a plurality of processes being units in each of which one work can be completed. Further, each of the processes is constructed of the aggregate of a plurality of constituent work CW (element work) each of which is a simple work. Also, in this embodiment, man-hours in the case where a predetermined basic time is entirely expended on works shall be defined as "net man-hours", whereas those man-hours not expended on works which can occur within the basic time shall be defined as "loss man-hours". Incidentally, the "basic time" is a time period for which workers must work, and which is obtained by subtracting fixed idle times (such as a mealtime, a breathing time, a time for morning meeting, and a time for closing meeting) from compulsory hours (working hours) stipulated by a company.
By the way, in a case where the cost center is considered as one product, a line including a plurality of processes exists in order to finish up the product. The cost constitution is an index for ascertaining the appropriateness of a current production cost or finding out a clue to the realization of a still lower production cost, and it is obtained in such a way that line characteristics are grasped by calculating net man-hours and loss man-hours throughout the processes in the line.
Here, the kinds of losses occurring within a basic time will be described with reference to FIGS. 42A and 42B. In FIG. 42A, the time (man-hours) is represented in a vertical direction, while the kinds of losses are listed in a lateral direction. In case of producing a product, a working loss WL, a quality yield loss YFL, a process organization loss PL and a man-hour difference loss ML occur relative to the basic time BT, and a real working time RWT, a working time WT, a maximum whole time (man-hours) MWT and a substantial whole time RWT are obtained by reducing the respective loss components from the basic time BT.
The real working time RWT is a time period based on the number of cars to-be-produced, that is, a time period required for really producing a set number of cars. More concretely, the real working time RWT is a time period (line tact set time) obtained in such a way that predicted idle times for a line trouble, the changeover of car types, the changeover and preparation of components, work starting safety checking, etc. are subtracted from the basic time BT. The working time WT is a time period based on the number of cars to-be-handed-over, that is, a time period required for producing the number of cars which are handed over to the next process as conforming articles among the cars produced in the real working time RWT. The maximum whole time MWT is a time period based on maximum man-hours, that is, a time period (work done) required in a case where only the car type (component) of the maximum man-hours is produced in a line of multiple car types. By the way, in a line of single car type, the maximum whole time MWT is a time period required for the production of the specific car type which is produced in this line. The substantial whole time RWT is a time period based on substantial whole man-hours, that is, a time period required for production in the case where a plurality of car types or a plurality of derivatives coexist in the set number of cars to-be-produced.
The working loss WL is a time period obtained by subtracting the real working time RWT from the basic time BT, and is a predicted idle time period within the basic time BT. The quality yield loss YFL is a time period obtained by subtracting the working time WT from the real working time RWT, that is, a time period required for producing the number of cars which are not handed over to the next process as nonconforming articles among the cars produced in the real working time RWT. The process organization loss PL is a time period obtained by subtracting the maximum whole time MWT from the working time WT. This loss PL occurs when car type and component man-hours are allocated to the tact set number of processes, and it especially signifies the difference between the tact and the man-hours of the maximum man-hour car type (component). The man-hour difference loss ML is a time period obtained by subtracting the substantial whole time RWT from the maximum whole time MWT, and it is the difference of man-hours between car types or between derivatives as occurs in case of producing at least two car types (or/and at least two derivatives) in one line. Incidentally, the process organization loss PL and the man-hour difference loss ML are termed a "plant capability loss PCL" when added up. The plant capability loss PCL is a time period which corresponds to a difference in the number of cars as occurs in case of producing the number of cars less than the production capability of a plant.
Incidentally, the "tact" is a production time period (man-hours) required for producing one car in anticipation of nonconforming articles. By way of example, in a case where 500 conforming cars are to be produced in 8 hours in anticipation of a nonconformity percentage of 5%, 525 cars must be produced in 8 hours. The tact in this case is about 55 seconds (=8×3600÷525), and processes are organized so that one car can be produced in about 55 seconds.
Here, the relationship between car types of different man-hours and the process organization loss PL as well as the man-hour difference loss ML will be described with reference to FIG. 42B. In FIG. 42B, the time (man-hours) is represented in a vertical direction, while the car types of different man-hours are listed in a lateral direction. Car type A is a car type of maximum man-hours, and man-hours required for production decrease in the order of car type B, car type C and car type D. The process organization loss PL is the difference between a practice tact PT and type-A man-hours MA. Besides, the man-hour difference loss ML is the differences between the type-A man-hours MA and type-B man-hours MB, type-C man-hours MC and type-D man-hours MD. Incidentally, the man-hour management system according to this embodiment is a system which is effective to analyze the process organization loss PL as well as the man-hour difference loss ML (plant capability loss PCL), and to relieve the losses.
Besides, in this embodiment, the magnitudes of standard (reference) man-hours (works done) are analyzed and grasped for respective constituent work CW (element work) in a cost center by employing a unified technique (for example, MOST [Maynard Operation Sequence Technique], thereby to set standardized times (man-hours). Incidentally, the analysis may well be made by employing any expedient other than the MOST, for example, an MTM [Method-time Measurement] technique or a stopwatch.
Incidentally, the "unified technique" is a technique for setting the standard times (man-hours) of works, and it includes the MTM technique, and the MOST evolved from the MTM technique. Since the MTM technique divides operations or movements finely (into, for example, "stretch", "grip", "carry" and "unhand"), it requires a long time for an analysis or measurement, and it requires a large number of man-hours for calculating the standard time of one work (for example, taking and positioning). With the MOST, a standard time is preset every constituent work CW (element work) (for example, the sum between "stretch an arm" and "grip" for a movement "take up", or the sum between "carry" and "unhand" for a movement "put"), and one simple work (for example, taking and positioning) can be easily evaluated by the sum between the standard times of constituent work CW (element work).
Further, in this embodiment, a constituent work CW (element work) is refined and analyzed because reference man-hours cannot be satisfactorily analyzed and grasped with the unified technique. More specifically, in this embodiment as shown in FIG. 43, a constituent work CW (element work) is sorted into a main work MW or a supplementary movement SM in a work classification, and each of the main work MW and supplementary movement SM is refined into a main action MA, a supplemental action SA or a quasi action QA in a movement classification. Besides, the main action MA, supplemental action SA and quasi action QA are analyzed, and standardized man-hours are set for the respective movements. When, in this manner, the constituent work CW (element work) is classified into the movements so as to set the standardized man-hours therefore, the man-hours conform to the real movements by a worker and are highly reliable as standard (reference) man-hours (work done). Here in this embodiment, the technique by which the constituent work CW (element work) is refined and analyzed shall be called the "improved MOST". In the man-hour management system of this embodiment, the standardized man-hours obtained for the refined main action MA, supplemental action SA or quasi action QA by the work analysis of a car type to-be-mass-produced based on the improved MOST are stored as data.
The main work MW is one in the constituent work CW (element work). The supplementary movement SM is one which assists in the main work MW.
The main action MA is the basic movement in the main work MW or the supplementary movement SM. By way of example, it is a movement which recurs 100%, and which includes attachment, tightening, pasting, coupling, check and carrying. The supplemental action SA is one for establishing the main work MW or the supplementary movement SM, and it includes, for example, walk, moving, fluctuation and a body turn. The quasi action QA is a preparatory or rearrangement movement for the main action MA in a series of movements, and it includes, for example, taking, returning, opening or closing, putting, pressing, sending, tearing off, rotating and pushing a button.
Now, the general construction of a man-hour management system 1 will be described with reference to FIG. 1. The man-hour management system 1 is chiefly constructed of a server 2, a database 3, connection terminals 4, 4, 4, . . . , and an Ethernet 5.
The server 2 is one for sharing the database 3, and it is connected to the connection terminals 4, 4, 4, . . . through the Ethernet 5. Herein, the server 2 permits the connection terminals 4, 4, 4, . . . to read and write the data of various tables 10-21 stored in the database 3.
The database 3 includes a storage device such as hard disk, and stores therein the tables 10-21 which are utilized in the man-hour management system 1. Incidentally, the database 3 is managed by the server 2 and can be accessed through the Ethernet 5 by the connection terminals 4, 4, 4, . . . . The tables stored in the database 3 are the work constituent condition table 10, standardized man-hour table 11 and walk man-hour conversion table 12 for a standardized man-hour management system, the series table 13, line name table 14, derivation table 15, derivation format table 16 and derivation application table 17 for a derivation management system, and the main man-hour management table 18, process name table 19, change history table 20 and timing graph data table 21 for a main man-hour management system.
By the way, in this embodiment, the work constituent condition table 10 corresponds to a "work constituent condition table" mentioned in the appended claims, the standardized man-hour table 11 corresponds to a "standardized man-hour table" mentioned in the same, the walk man-hour conversion table 12 corresponds to a "walk man-hour conversion table" mentioned in the same, the series table 13 corresponds to a "series table" mentioned in the same, the line name table 14 corresponds to a "line name table" mentioned in the same, the derivation table 15 corresponds to a "derivation table" mentioned in the same, the derivation format table 16 corresponds to a "derivation format table" mentioned in the same, the derivation application table 17 corresponds to a "derivation application table" mentioned in the same, the main man-hour management table 18 corresponds to a "main man-hour management table" mentioned in the same, the process name table 19 corresponds to a "process name table" mentioned in the same, the change history table 20 corresponds to a "change history table" mentioned in the same, and the timing graph data table 21 corresponds to a "timing graph data table" mentioned in the same.
Each of the connection terminals 4, 4, 4, . . . is a terminal for executing the applications of the man-hour management system 1, and an electronic computer such as personal computer is employed therefor. Although not shown in detail, each of the connection terminals 4, 4, 4, . . . includes the computer proper, a display, a keyboard and a hard disk drive. If necessary, it includes a compact disk drive, a floppy disk drive, an audio output device, a printer etc. Further, each of the connection terminals 4, 4, 4, . . . stores in its hard disk, application programs for executing the applications of the man-hour management system 1. In addition, each of the connection terminals 4, 4, 4, . . . shall have a multiwindow environment as an OS [Operating System]. Besides, each of the connection terminals 4, 4, 4, . . . executes the applications of the man-hour management system 1 in accordance with the operations of a user, thereby to register/reorganize data in the tables 10-21 or to output man-hour information on the basis of the data of the tables 10-21.
The Ethernet 5 is a local area network of bus type laid in an automobile production factory. The server 2 is connected to the Ethernet 5, and the database 3, the connection terminals 4, 4, 4, . . . , etc. are connected thereto through the server 2.
Next, the system architecture of the man-hour management system 1 will be described with reference to FIG. 2. The man-hour management system 1 includes a standardized man-hour management system SS, a derivation management system DS, a main man-hour management system MS, a series data backup system BS and a man-hour output system OS. The standardized man-hour management system SS and the derivation management system DS are systems for pre-registering/pre-reorganizing information necessary for a man-hour analysis. The main man-hour management system MS is a system for performing the operational management of the pre-registered information about man-hours. The series data backup system BS and the man-hour output system OS are systems for making the most of data about man-hours, that is, for outputting the data for the man-hour analysis, backing up the data, utilizing the man-hour information for a minor change or a model change, and so forth.
The standardized man-hour management system SS is a system which performs the registration management of the basic data of the preceding information of the man-hour management system 1 concerning man-hours, and which includes walk man-hour management SS1, constituent work CW (element work) condition management SS2, standardized man-hour registration SS3 and constituent name condition item maintenance SS4. The application programs of the standardized man-hour management system SS include a standardized man-hour management system program as a main program, and a walk man-hour management program, a constituent work CW (element work) condition management program, a standardized man-hour registration program and a constituent name condition item maintenance program as subprograms. Incidentally, these programs are stored in each of the hard disks of the server 2 and connection terminals 4, 4, 4, . . . . Besides, the applications of the standardized man-hour management system SS are executed in such a way that the respectively corresponding programs are loaded into each of the connection terminals 4, 4, 4, . . . in accordance with the user's operation. Further, the standardized man-hour management system SS registers data in the work constituent condition table 10, standardized man-hour table 11 and walk man-hour conversion table 12 through the server 2 in accordance with the executions of the applications. By the way, the standardized man-hour management system SS is constructed of the standardized man-hour management system program, walk man-hour management program, constituent work CW (element work) condition management program, standardized man-hour registration program and constituent name condition item maintenance program; the server 2 and connection terminals 4, 4, 4, . . . ; the work constituent condition table 10, standardized man-hour table 11 and walk man-hour conversion table 12; and so forth.
The derivation management system DS is a system which performs the registration management/reorganization management of data corresponding to multifarious variations (such as the data of a plurality of production lines, those of a plurality of series, those of a plurality of car types, and those of a plurality of derivatives), as the preceding information of the man-hour management system 1 concerning man-hours, and which includes line name management DS1, series registration management DS2, derivation classification registration management DS3, derivation format registration management DS4 and derivation code table management DS5. The application programs of the derivation management system DS include a derivation management system program as a main program, and a line name management program, a series registration management program, a derivation classification registration management program, a derivation format registration management program and a derivation code table management program as subprograms. Incidentally, these programs are stored in each of the hard disks of the server 2 and connection terminals 4, 4, 4, . . . . Besides, the applications of the derivation management system DS are executed in such a way that the respectively corresponding programs are loaded into each of the connection terminals 4, 4, 4, . . . in accordance with the user's operation. Further, the derivation management system DS registers/reorganizes data in the series table 13, line name table 14, derivation table 15, derivation format table 16 and derivation application table 17 through the server 2 in accordance with the executions of the applications. By the way, the derivation management system DS is constructed of the derivation management system program, line name management program, series registration management program, derivation classification registration management program, derivation format registration management program and derivation code table management program; the server 2 and connection terminals 4, 4, 4, . . . ; and the series table 13, line name table 14, derivation table 15, derivation format table 16 and derivation application table 17.
The main man-hour management system MS is a system which performs the management, aggregation, display management, etc. of man-hours on the basis of the preceding information of the man-hour management system 1 concerning man-hours, and which includes main man-hour management MS1, process name management MS2, change history management MS3 and timing graph management MS4. The application programs of the main man-hour management system MS include a main man-hour management system program as a main program, and a main man-hour management program, a process name management program, a change history management program and a timing graph management program as subprograms. Incidentally, these programs are stored in each of the hard disks of the server 2 and connection terminals 4, 4, 4, . . . . Besides, the applications of the main man-hour management system MS are executed in such a way that the respectively corresponding programs are loaded into each of the connection terminals 4, 4, 4, . . . in accordance with the user's operation. Further, the main man-hour management system MS registers/reorganizes data in the main man-hour management table 18, process name table 19, change history table 20 and timing graph data table 21 through the server 2 in accordance with the executions of the applications. By the way, the main man-hour management system MS is constructed of the main man-hour management system program, main man-hour management program, process name management program, change history management program and timing graph management program; the server 2 and connection terminals 4, 4, 4, . . . ; the main man-hour management table 18, process name table 19, change history table 20 and timing graph data table 21;and so forth.
The series data backup system BS is a system by which the tables 10-21 stored in the database 3 are backed up in each individual series unit. This series data backup system BS includes a series data backup system program as its application program. Incidentally, this program is stored in each of the hard disks of the server 2 and connection terminals 4, 4, 4, . . . . Besides, the application of the series data backup system BS is executed in such a way that the program is loaded into each of the connection terminals 4, 4, 4, . . . in accordance with the user's operation. Further, in accordance with the execution of the application, the series data backup system BS stores the data of the tables 10-21 from the database 3 in a floppy disk, a hard disk or the like through the server 2 in each individual series unit, and it also restores in the database 3 data in each individual series unit backed up in a floppy disk, a hard disk or the like. The series data backup system BS is constructed of the series data backup system program; the server 2 and connection terminals 4, 4, 4, . . . ; and so forth.
By the way, in this embodiment, the series data backup system BS corresponds to "series data backup means" mentioned in the appended claims.
The man-hour output system OS is a system which outputs the man-hour information of the man-hour management system 1 for making a man-hour analysis, and which includes timing graph output OS1, process balancing table output OS2, net & loss aggregation table output OS3, individual-process specification aggregation table output OS4, history management table output OS5 and main man-hour management output OS6. The application programs of the man-hour output system OS include a man-hour output system program as a main program, and a timing graph output program, a process balancing table output program, a net & loss aggregation table output program, an individual-process specification aggregation table output program, a history management table output program and a main man-hour management output program as subprograms. Incidentally, these programs are stored in each of the hard disks of the server 2 and connection terminals 4, 4, 4, . . . . Besides, the applications of the man-hour output system OS are executed in such a way that the respectively corresponding programs are loaded into each of the connection terminals 4, 4, 4, . . . in accordance with the user's operation. Further, in accordance with the executions of the applications, the man-hour output system OS converts output data on the basis of the data of the tables 10-21 of the database 3, thereby to deliver a display output to the display of each of the connection terminals 4, 4, 4, . . . , a paper sheet output to a printer, a file output to a floppy disk or the like, and so forth. Such output data are utilized for finding a clue to diminution in the number of man-hours on the basis of the clarification of a working time as well as a wait time and the clarification of net man-hours as well as loss man-hours, for organizing processes for a minor change, a full model change or a new model change, for verifying the balance of the process organization as well as a process capability, and so forth. By the way, the man-hour output system OS is constructed of the man-hour output system program, timing graph output program, process balancing table output program, net & loss aggregation table output program, individual-process specification aggregation table output program, history management table output program and main man-hour management output program; the server 2 and connection terminals 4, 4, 4, . . . ; and so forth.
In this embodiment, the man-hour output system OS corresponds to "man-hour output means" mentioned in the appended claims.
Here, the main man-hour management table 18 will be described with reference to FIG. 3. This table 18 is a basic table in the case of making a man-hour analysis by the man-hour management system 1, and it manages item data for constituent work CW (element work) in process units.
The main man-hour management table 18 is selectively assigned or automatically assigned the pre-registered data of the work constituent condition table 10, standardized man-hour table 11, walk man-hour conversion table 12, series table 13, line name table 14, derivation table 15, derivation format table 16 and derivation application table 17, and the data of the process name table 19, whereby data are registered/reorganized. Besides, the main man-hour management table 18 manages information about man-hours which are necessary for making a man-hour analysis in process units managed by the process name table 19. Further, the main man-hour management table 18 offers man-hour information to the man-hour output system OS in order to output the man-hour information necessary for the man-hour analysis.
The data which are under registration management/reorganization management by the main man-hour management table 18 include series [A], line No [B], line name [C], cost center [D], process name [E], derivation display selection [F], total man-hours [G], aggregation of man-hours having values added [H] and aggregation of man-hours having no values added [I]; derivation [1], procedure [2], constituent work CW (element work) (what) [3], constituent work CW (element work) (where) [4], constituent work CW (element work) (how) [5], frequency [6], SPOT [7] indicating the number of dots, and MIG [8] and sealer [9]; number of steps [10], time of steps in seconds [11], waist [12], taking and putting [13], setting [14], pushing a button [15], fluctuating time [16], positioning [17], personal work [18], equipmental work [19], carrying [20] and subtotal [21] in the presence of the value-added of man-hours; number of steps [22], time of steps in seconds [23], waist [24], taking and putting [25], fluctuating time [26], positioning [27], personal work [28], wait [29], carrying [20] and subtotal [30] in the absence of the value-added of man-hours; total of the man-hours [31]; and TARGET part No [32], DWG No [33], remarks [34], standard walk [35], standard work [36] and standard work [37]. The data in the main man-hour management table 18 are stored in process units, and the stored data corresponding to each process shall be called a "worksheet". Incidentally, since a plurality of constituent work CW (element work) are included in one process, constituent work CW (element work) items [1]-[37] are respectively set for each constituent work CW (element work) in one worksheet. By the way, the data of the main man-hour management table 18 explained in this embodiment are ones in the field of welding, and the contents of data are different in the other fields of assemblage, painting etc.
Here, the hierarchical structure of the data of the man-hour management system 1 will be described with reference to FIG. 4. The man-hour management system 1 forms the hierarchical structure with an apex at a plurality of or a single series (car type) [A]. Besides, since a plurality of production lines exist in an automobile production factory, a plurality of line Nos [B] are constructed as the lower layer of the series [A]. Incidentally, in case of a single production line, there is only one line No [B]. Further, since each production line is constructed of a plurality of lines each corresponding to a cost center, a plurality of line names [C] (cost centers [D]) are constructed as the lower layer of the line No [B]. Incidentally, in a case where the production line has only one cost center, there is only one line name [C]. Subsequently, since each cost center is constructed of a plurality of processes, a plurality of process names [E] are constructed as the lower layer of the line No [C]. Incidentally, in a case where the cost center has only one process, there is only one process name [E]. By the way, the main man-hour management table 18 has each worksheet invoked using the series [A], line No [B], line name [C] (cost center [D]) and process name [E] as keys.
Further, since each process is constructed of a plurality of constituent work CW (element work), item data [1]-[37] are respectively registered and managed for the plurality of constituent work CW (element work) as the lower layer of the process name. By the way, since the timing graph data table 21 is set on the basis of the main man-hour management table 18, timing graph data [41]-[51] are respectively registered and managed for the constituent work CW (element work) items [1]-[37]. Besides, a timing graph screen 57 (FIG. 29A), etc. are outputted on the basis of the timing graph data [41]-[51].
A series for which work man-hours are managed, is set as the series [A]. The name/names of series registered in the series table 13 (for example, a name "JM" or "AR", or names "JM-S03" and "JM-S13" in the presence of a plurality of car types) is/are selected and set as the series [A].
A production line for which work man-hours are managed, is set as the line No [B]. A line No registered in the line name table 14 (for example, "line 1" or "line 2") is selected and set as the line No [B].
The name of a line in which a work implemented, is set as the line name [C].
A line name registered in the line name table 14 (for example, "FRDOOR" or "RRDOOR") is selected and set as the line name [C].
A cost center as to which a work is proceeding, is set as the cost center [D]. A cost center No registered in the line name table 14 (for example, "211001" or "211002") is selected and set as the cost center [D].
The name of a process for which a work is proceeding, is set as the process name [E]. A process name registered in the process name table 19 is selected and set as the process name [E].
A code for effecting display selection in order to assign a derivation code to the derivation [1], is set as the derivation display selection [F]. The code name of a derivative registered in the derivation table 15 (for example, "A11", "RH", "LH", "2WD" or "4WD") is selected and set as the derivation display selection [F].
The total of standardized man-hours in worksheet (process) units is set as the total man-hours [G]. The total man-hours [G] is the total of the aggregation of man-hours having values added [H] and the aggregation of man-hours having no values added [I]. By the way, in a case where the aggregation of man-hours having values added [H] or/and the aggregation of man-hours having no values added [I] have been altered, the total man-hours [G] is re-computed in real time.
The total of the subtotals [21] in worksheet (process) units is set as the aggregation of man-hours having values added [H]. By the way, the subtotals [21] exist in the number of constituent work CW (element work) within one worksheet. Incidentally, the "man-hours having values added" are man-hours which are directly contributive to the production of a product.
The total of the subtotals [30] in worksheet (process) units is set as the aggregation of man-hours having no values added [I]. By the way, the subtotals [30] exist in the number of constituent work CW (element work) within one worksheet. Incidentally, the "man-hours having no values added" are man-hours for rearrangement and wait, and they include wait man-hours and loss man-hours.
Any of classified derivatives for which constituent work CW (element work) occur, is set as the derivation [1]. Any of code names registered in the derivation table (for example, "RH", "LH", "AT", "MT", "2WD", "4WD", "normal roof" or "sunroof") is selected and set as the derivation [1]. By the way, the derivation code selected by the derivation selection [F] is assigned to the derivation [1].
The sequence of works in a process is set as the procedure [2].
The name of a component and the name of a work forming a constituent work CW (element work), are set as the constituent work CW (element work) (what) [3].
The name of a place in which a work is implemented, is set as the constituent work CW (element work) (where) [4].
A constituent work CW (element work) name for an individual work item is set as the constituent work CW (element work) (how) [5]. Any of constituent work CW (element work) names registered in the work constituent condition table 10 (for example, "spot welding" or "mig welding") is selected and registered as the constituent work CW (element work) (how) [5].
The number of times which the same work is repeated, is set as the frequency [6].
The number of spots is set as the SPOT [7]. The size (welding length) of a mig is set as the MIG [8]. The size of a sealer is set as the sealer [9]. By the way, since most of works in welding are spot welding, mig welding and sealer coating, the number of dots is important for analyzing man-hours in the field of welding, and it is therefore set. Incidentally, "one dot" signifies that the spot welding is implemented one time.
Set as the number of steps [10] is the number of steps which a worker requires since his/her start of walk or moving to a destination till his/her arrival thereat in order to implement a work. The standardized man-hours (time value) of the walk is set as the time of steps in seconds [11]. The time of steps in seconds [11] is automatically set by being assigned standardized man-hours registered in the walk man-hour conversion table 12, with the number of steps [10] as a key.
The standardized man-hours (time value) of the movement of bending and turning a worker's waist are set as the waist [12]. Set as the taking and putting [13] are the standardized man-hours (time value) of the work of taking and putting a workpiece, a portable spot welding machine or a clamping tool. Set as the setting [14] are the standardized man-hours (time value) of the work of clamping the workpiece or confronting the workpiece to the portable spot welding machine or the clamping tool. The standardized man-hours (time value) of the work of pushing a switch are set as the pushing a button [15]. Set as the fluctuating time [16] are standardized man-hours (time value) which correspond to a welding time based on spot welding or mig welding, the coating time of a sealer, and a clamping time for a bolt and a nut. The standardized man-hours (time value) of the work of positioning the workpiece are set as the positioning [17]. The standardized man-hours (time value) of a personal work are set as the personal work [18]. The standardized man-hours (time value) of an equipmental (robot) work are set as the equipmental work [19]. The standardized man-hours (time value) of the work of carrying the workpiece are set as the carrying [20]. Incidentally, the items [12]-[20] in the "man-hours having values added" are automatically set by being assigned standardized man-hours registered in the standardized man-hour table 11, with keys being the constituent work CW (element work) or the conditions thereof in the case of the constituent work CW (element work) name setting of the constituent work CW (element work) (how) [5].
The total of the standardized man-hours of the works having values added is set in constituent work CW (element work) units as the subtotal [21]. This subtotal [21] is the total of the standardized man-hours of the items [11]-[20] in the "man-hours having values added". By the way, in a case where the standardized man-hours of the items [11]-[20] in the "man-hours having values added" have been altered, the subtotal [21] is re-computed in real time.
Set as the number of steps [22] is the number of steps which a worker requires since his/her start of walk or moving to a destination till his/her arrival thereat in order to implement a work. The standardized man-hours (time value) of the walk is set as the time of steps in seconds [23]. The time of steps in seconds [23] is automatically set by being assigned standardized man-hours registered in the walk man-hour conversion table 12, with the number of steps [22] as a key.
The standardized man-hours (time value) of the movement of bending and turning a worker's waist are set as the waist [24]. Set as the taking and putting [25] are the standardized man-hours (time value) of the work of taking and putting a workpiece, a portable spot welding machine or a clamping tool. Set as the fluctuating time [26] are standardized man-hours (time value) which correspond to a welding time based on spot welding or mig welding, the coating time of a sealer, and a clamping time for a bolt and a nut. The standardized man-hours (time value) of the work of positioning the workpiece are set as the positioning [27]. The standardized man-hours (time value) of a personal work are set as the personal work [28]. Standardized man-hours (time value) corresponding to a personal or equipmental standby time are set as the wait [29]. Incidentally, the items [24]-[29] in the "man-hours having no values added" are automatically set by being assigned standardized man-hours registered in the standardized man-hour table 11, with keys being the constituent work CW (element work) or the conditions thereof in the case of the constituent work CW (element work) name setting of the constituent work CW (element work) (how) [5].
The total of the standardized man-hours of the works having no values added is set in constituent work CW (element work) units as the subtotal [30]. This subtotal [30] is the total of the standardized man-hours of the items [23]-[29] in the "man-hours having no values added". By the way, in a case where the standardized man-hours of the items [23]-[29] in the "man-hours having no values added" have been altered, the subtotal [30] is re-computed in real time.
The total of standardized man-hours in constituent work CW (element work) units is set as the total [31]. This total [31] is the sum between the subtotal [21] of the man-hours having values added and the subtotal [30] of the man-hours having no values added. By the way, in a case where the value/values of the subtotal [21] of the man-hours having values added or/and the subtotal [30] of the man-hours having no values added has/have been altered, the total [31] is recomputed in real time.
A part No (main, type, class) is inputted to and set as the TARGET part No [32].
The main No of the part of each constituent work CW (element work) is inputted to and set as the DWG No [33].
Remarks on each constituent work CW (element work) are inputted to and set as the remarks [34].
Set as the standard walk [35] is a standardized material No which is assigned the standardized man-hours set in the time of steps in seconds [11] or the time of steps in seconds [23]. The standard walk [35] is automatically set by being assigned the standardized material No registered in the walk man-hour conversion table 12, with the time of steps in seconds [11] or the time of steps in seconds [23] as a key.
Set as the standard work [36] is a standardized material No which is assigned the standardized man-hours set in the items [12]-[20] in the "man-hours having values added". Set as the standard work [37] is a standardized material No which is assigned the standardized man-hours set in the items [24]-[29] in the "man-hours having no values added". The standard work [36] or [37] is automatically set by being assigned the standardized material No registered in the standardized man-hour table 11, with a key being the constituent work CW (element work) or the conditions thereof in the case of the constituent work CW (element work) name setting of the constituent work CW (element work) (how) [5].
Also, there will be described the timing graph data table 21 which is set on the basis of the main man-hour management table 18. Data which are set in the timing graph data table 21 are S. T [41], wait 1 [42], working or operation 1 [43], wait 2 [44], working 2 [45], wait 3 [46], working 3 [47], wait 4 [48], working 4 [49], wait 5 [50], working 5 [51] and total [52].
The start time of a timing graph for each constituent work CW (element work) is set as the S. T [41]. This S. T [41] is automatically set by being assigned the total [52] of an upper line.
If wait times are involved in the works of the items [11]-[20] of the "man-hours having values added" in the constituent work CW (element work), they are respectively set as the wait 1 [42]-wait 5 [50]. Accordingly, although only the five setting columns of the wait 1 [42]-wait 5 [50] are indicated as the wait times, setting columns increase as wait 6, . . . in the presence of six or more wait times. Besides, in the presence of four or less wait times, "0" (blank) is set in one or more of the setting columns of the wait 1 [42]-wait 5 [50]. These waits 1 [42]-5 [50] are respectively set by measuring wait times in the movements of the items [11]-[20]. Incidentally, the wait [29] of the main man-hour management table 18 corresponds to the total of the wait 1 [42]-wait 5 [50].
The working times of the items [11]-[20] of the "man-hours having values added" in the constituent work CW (element work) are respectively set as the working 1 [43]-working 5 [51]. Accordingly, although only the five setting columns of the working 1 [43]-working 5 [51] are indicated as the working times, setting columns increase as working 6, . . . in the presence of six or more working times. Besides, in the presence of four or less working times, "0" (blank) is set in one or more of the setting columns of the working 1 [43]-working 5 [51]. These workings 1 [43]-5 [51] are automatically set by being assigned the working times of the items [11]-[20].
Set as the total [52] is the total of the start time and the working times, including the wait times, of the "works having values added" of the constituent work CW (element work). That is, it is the total of the S. T [41], the wait 1 [42]-wait 5 [50] and the working 1 [43]-working 5 [51]. By the way, in a case where the value/values of the S. T [41], wait 1 [42]-wait 5 [50] or/and working 1 [43]-working 5 [51] have been altered, the total [52] is re-computed in real time.
Next, the standardized man-hour management system SS will be described with reference to FIG. 5 through FIG. 10B. Using the improved MOST, the standardized man-hour management system SS refines each of the constituent work CW (element work) and sets standardized man-hours for the constituent work CW (element work) so as to register them beforehand.
The standardized man-hour management system SS is such that, when a standardized man-hour management system starting icon (not shown) indicated on the display of the connection terminal 4 is clicked by a user, a standardized man-hour management system program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the menu screen 30 of the standardized man-hour management system SS as shown in FIG. 5 is indicated on the display of the connection terminal 4.
Displayed on the menu screen 30 are a selection button 30a for the walk man-hour management SS1, a selection button 30b for the constituent work CW (element work) condition management SS2, a selection button 30c for the standardized man-hour registration SS3, a selection button 30d for the constituent name condition item maintenance SS4, and a quit button 30e. Herein, when the user clicks any of the selection buttons 30a-30d, a corresponding application is executed, and when he/she clicks the quit button 30e, the application of the standardized man-hour management system SS is ended to erase the menu screen 30 from the display of the connection terminal 4.
Next, the walk man-hour management SS1 will be described with reference to FIG. 5 and FIG. 6. The walk man-hour management SS1 registers and manages the standardized man-hours (walk man-hours or walk time) of a walk region generated by a work, and it registers and manages data by the walk man-hour conversion table 12. Walk data for use in the main man-hour management system MS are registered in the walk man-hour conversion table 12 beforehand, whereby the automatic assignment of the standardized man-hours of walk is permitted. The data which are registered and managed correspond to the numbers of steps [10], [22] and the times of steps in seconds [11], [23] in the main man-hour management table 18. The numbers of steps [10], [22] and the times of steps in seconds [11], [23] are previously measured using the improved MOST, and are registered in the walk man-hour conversion table 12. Incidentally, the numbers of steps [10], [22] and the times of steps in seconds [11], [23] correspond to the supplemental actions of main works.
The walk man-hour management SS1 is such that, when the selection button 30a of the menu screen 30 indicated on the display of the connection terminal 4 is clicked by the user, a walk man-hour management program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the registration screen 31 of the walk man-hour management SS1 as shown in FIG. 6 is indicated on the display of the connection terminal 4. At the start-up of the registration screen 31, data already registered in the walk man-hour conversion table 12 are read out and are displayed on the registration screen 31. Herein, the data of the walk man-hour conversion table 12 are the numbers of steps, the times of steps in seconds, and the standardized material Nos. Incidentally, the standardized material No is obtained by encoding the number of seconds expended per number of steps measured using the improved MOST. On the registration screen 31, accordingly, a data No column 31a, a number-of-steps column 31b, a number-of-seconds column 31c and a standardized material No column 31d are arrayed and displayed in correspondence with the data of the walk man-hour conversion table 12.
In case of registering the number of steps, the time of steps in seconds, and the standardized material No, the user inputs numerical values to the data No column 31a, number-of-steps column 31b, number-of-seconds column 31c and standardized material No column 31d of the registration screen 31. Besides, when the user clicks the registration button 31f of the registration screen 31, the inputted numerical values are registered in the walk man-hour conversion table 12. By the way, in case of registering no data, or in case of returning to the menu screen 30 of the standardized man-hour management system SS, the user clicks the previous screen button 31e of the registration screen 31. Then, the registration screen 31 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
Next, the constituent work CW (element work) condition management SS2 will be described with reference to FIG. 5 and FIGS. 7A-7C. The constituent work CW (element work) condition management SS2 registers and manages constituent work CW (element work) names for use in man-hour management and also registers and manages conditions correspondent to constituent work CW (element work) for assigning standardized man-hours correspondent to the constituent work CW (element work), and it registers and manages data by the work constituent condition table 10. Item data for use in the main man-hour management system MS are registered in the work constituent condition table 10 beforehand, whereby the selective assignment of the constituent work CW (element work) name and the standardized man-hours is permitted. The data which are registered and managed are the constituent work CW (element work) name and the conditions thereof classified by the improved MOST as correspond to the constituent work CW (element work) (how) [5] of the main man-hour management table 18.
The constituent work CW (element work) condition management SS2 is such that, when the selection button 30b of the menu screen 30 indicated on the display of the connection terminal 4 is clicked by the user, a constituent work CW (element work) condition management program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the setting screen 32 of the constituent work CW (element work) condition management SS2 as shown in FIG. 7B is indicated on the display of the connection terminal 4. At the start-up of the setting screen 32, data already registered in the constituent work CW (element work) condition table 10 are read out and are displayed on the setting screen 32. Herein, the data of the constituent work CW (element work) condition table 10 are concretely the class (field) of the constituent work CW (element work), the constituent work CW (element work) name, and the conditions correspondent to the constituent work CW (element work). By the way, the setting screen 32 is a screen for setting the class and name of the constituent work CW (element work), and a class column 32a and a constituent work CW (element work) name column 32b are arrayed and displayed on this screen 32. Incidentally, the class column 32a includes a plurality of text boxes 32a1, . . . for setting and registering the classes of the constituent work CW (element work), and check columns 32a2, . . . corresponding to the respective text boxes 32a1, . . . . Besides, the constituent work CW (element work) name column 32b includes a plurality of text boxes 32b1, 32b2, 32b3, . . . for setting and registering the constituent work CW (element work) names, and check columns 32b4, 32b5, 32b6 . . . corresponding to the respective text boxes 32b1, 32b2, 32b3, . . . .
Here in the example, as shown in FIG. 7A, the class (field) of the constituent work CW (element work) is "welding", the constituent work CW (element work) names are "mig welding", "spot welding" and "T-stud welding", and the conditions for the constituent work CW (element work) are the "length of welding" and the "number of dots of welding". Incidentally, standardized man-hours are respectively set for the conditions of each constituent work CW (element work). By the way, in a case where no conditions are set for the constituent work CW (element work), standardized man-hours are respectively set for the constituent work CW (element work) themselves.
First, in case of setting and registering the class of the constituent work CW (element work), the user moves a cursor to that one of the text boxes 32a1, . . . of the class column 32a of the setting screen 32 for which the class is to be set. Subsequently, the user inputs the class of the constituent work CW (element work) to the specified text box 32a1. By way of example, "welding" is inputted to the text box 32a1 as shown in FIG. 7B. Otherwise, "painting", "assemblage" etc. are inputted. Further, in case of setting and registering the constituent work CW (element work) names for the class of each constituent work CW (element work), the user selects that one of the check columns 32a2, . . . in the class column 32a which corresponds to the class for inputting the constituent work CW (element work) names. Then, the constituent work CW (element work) names for the selected class can be inputted to the constituent work CW (element work) name column 32b. By way of example, the check column 32a2 is selected as shown in FIG. 7B, and the constituent work CW (element work) names for the class "welding" can be inputted in this state. Subsequently, the user moves the cursor to those of the text boxes 32b1, 32b2, 32b3, . . . of the constituent work CW (element work) name column 32b on the setting screen 32 for which the constituent work CW (element work) names are to be set. Besides, the user inputs the constituent work CW (element work) names to the specified ones of the text boxes 32b1, 32b2, 32b3, . . . . By way of example, the "spot welding" is inputted to the text box 32b1, the "mig welding" to the text box 32b2 and the "T-stud welding" to the text box 32b3 as shown in FIG. 7B. Besides, in case of registering the inputted class and names of the constituent work CW (element work), the user clicks the registration/previous screen button 32d of the setting screen 32, whereby the inputs are registered in the work constituent condition table 10. By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the cancel/previous screen button 32e of the setting screen 32. Then, the setting screen 32 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
Further, in case of registering the conditions for each constituent work CW (element work), the user selects that one of the check columns 32b4, 32b5, 32b6, . . . of the constituent work CW (element work) in the constituent work CW (element work) name column 32b of the setting screen 32 which corresponds to the constituent work CW (element work) for inputting the conditions. By way of example, let's consider a case as shown in FIG. 7B where the check column 32a2 is highlighted so as to select the "welding" in the class column 32a, and where the check column 32b5 is highlighted so as to select the "mig welding" in the constituent work CW (element work) name column 32b. In this case, a registration screen 33 (refer to FIG. 7C) for the conditions corresponding to the selected constituent work CW (element work) is displayed, and the conditions corresponding to the selected constituent work CW (element work) can be inputted to the condition column 33b of the registration screen 33. At the start-up of the registration screen 33, data already registered in the constituent work CW (element work) condition table 10 are read out and are displayed on the registration screen 33. By the way, the registration screen 33 is a screen for setting the conditions of each constituent work CW (element work), and the condition column 33b is arranged and displayed on this screen 33. This condition column 33b includes a header column 33c for registering the conditions of the corresponding constituent work CW (element work); an item 1 column 33d, item 2 column 33e, item 3 column 33f, item 4 column 33g and item 5 column 33h for registering data for the conditions; and a grouping column 33i for grouping the conditional data. Herein, the data of the conditional items are registered in the item 1-5 columns 33d-33h. In the presence of six or more conditions to-be-registered, the conditions are registered in a plurality of stages of the item 1-5 columns 33d-33h. Besides, the grouping column 33i includes check columns in correspondence with the positions of the text boxes of the item 1 column 33d, item 2 column 33e, item 3 column 33f, item 4 column 33g and item 5 column 33h. Incidentally, the class and the constituent work CW (element work) name selected on the setting screen 32 are displayed in the work condition item column 33a of the registration screen 33. By way of example, the "welding/mig welding" are displayed as shown in FIG. 7C.
In case of inputting the conditions, the user moves the cursor to the text boxes 33c1, 33c2, . . . of the header column 33c. Besides, he/she inputs the conditional items to the specified text boxes 33c1, 33c2, . . . . By way of example, as shown in FIG. 7C, a "length" is inputted to the text box 33c1, and the "number of dots" to the text box 33c2. Subsequently, in case of inputting the conditional data to the conditional item "length", the user moves the cursor to the text box 33d1 of the item 1 column 33d, etc. Besides, he/she inputs the conditional data to the specified text box 33d1, etc. In the presence of a plurality of conditional data for each conditional item, the conditional data are successively inputted to the text box 33e1 of the item 2 column 33e, the text box 33f1 of the item 3 column 33f, . . . . By way of example, in the presence of three conditional data for the conditional item "length", data "at most 6 mm", "at most 12 mm" and "at most 18 mm" are successively inputted to the text boxes 33d1, 33e1 and 33f1 as shown in FIG. 7C. Further, in case of inputting the conditional data to the conditional item "number of dots", the user moves the cursor to the text box 33d2 of the item 1 column 33d, etc. Besides, he/she inputs the conditional data to the specified text box 33d2, etc. In the presence of a plurality of conditional data for each conditional item, the conditional data are successively inputted to the text box 33e2 of the item 2 column 33e, the text box 33f2 of the item 3 column 33f, . . . . By way of example, in the presence of six conditional data for the conditional item "number of dots", the data are inputted to two stages such as the text boxes 33d2 and 33d3 of the item 1 column 33d for the "number of dots", as shown in FIG. 7C. More specifically, the data "1 dot", "2 dots", "3 dots", "4 dots", "5 dots" and "6 dots" are successively inputted to text boxes 33d2, 33e2, 33f2, 33g1, 33d3 and 33e3. Lastly, in case of registering the conditional data for each constituent condition, the user selects the check column 33i1, etc. of the grouping column 33i in order to group the conditional data of the constituent condition. By way of example, in order to group the conditional data "at most 6 mm" as the "length" and the conditional data "2 dots" as the "number of dots" of the constituent condition "mig welding", the check columns 33i1 and 33i2 of the grouping column 33i corresponding respectively to the data "at most 6 mm" as the "length" and the data "2 dots" as the "number of dots" are selected as shown in FIG. 7C. Besides, the user clicks the registration/previous screen button 33j of the registration screen 33, whereby the conditional data are registered in the work constituent condition table 10. By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the cancel/previous screen button 33k of the registration screen 33. Then, the registration screen 33 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
Next, the standardized man-hour registration SS3 will be described with reference to FIG. 5, FIG. 8 and FIGS. 9A-9B. The standardized man-hour registration SS3 registers and manages standardized man-hour analysis contents and standardized man-hours for the conditions of each constituent work CW (element work), and it registers and manages data by the standardized man-hour table 11. With the standardized man-hour registration SS3, the standardized man-hours are respectively registered in the standardized man-hour table 11, as to the conditions of the constituent work CW (element work) registered in the work constituent condition table 10 (refer to FIG. 8). Incidentally, the standardized man-hour analysis contents to be registered in the standardized man-hour table 11 are data corresponding to the conditions of the constituent work CW (element work), and they are concretely the class (field) of the constituent work CW (element work), the names thereof and the conditions thereof. The standardized man-hour data for use in the main man-hour management system MS are registered in the standardized man-hour table 11 beforehand, whereby the automatic assignment of the standardized man-hours is permitted. The data to be registered and managed are standardized man-hours measured by the improved MOST, corresponding to the items [12]-[20] of the "man-hours having values added" and the items [24]-[29] of the "man-hours having no values added" in the main man-hour management table 18, and the standardized material Nos corresponding to the standard works [36], [37] (refer to FIG. 8). Incidentally, the "man-hours having values added" are man-hours which are directly contributive to the production of a product. Besides, the "man-hours having no values added" are man-hours which are not directly contributive to the production of the product, and which are man-hours for rearrangement, wait, etc.
The standardized man-hour registration SS3 is such that, when the selection button 30c of the menu screen 30 indicated on the display of the connection terminal 4 is clicked by the user, a standardized man-hour registration program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the registration screen 34 of the standardized man-hour registration SS3 as shown in FIG. 9B is indicated on the display of the connection terminal 4. At the start-up of the registration screen 34, data already registered in the work constituent condition table 10 and standardized man-hour table 11 are read out and are displayed on the registration screen 34. Herein, the data of the standardized man-hour table 11 are concretely the class (field) of the constituent work CW (element work), the names of the constituent work CW (element work) and the conditions correspondent to each of the constituent work CW (element work) as the standardized man-hour analysis contents, and the standardized man-hours of the items [12]-[20] of the "man-hours having values added" and the items [24]-[29] of the "man-hours having no values added", as well as the standardized material Nos of the standard works [36], [37]. By the way, a standardized man-hour analysis content column 34a and a standardized man-hour column 34b are displayed on the registration screen 34. Incidentally, in order to select the class, the constituent work CW (element work) name and the conditions for each constituent work CW (element work) as are registered in the work constituent condition table 10, the standardized man-hour analysis content column 34a includes a class selection column 34c, a constituent work CW (element work) name selection column 34d and a condition selection column 34e, and the respective selection columns 34c, 34d and 34e include check columns 34c1, 34d1 and 34e1, . . . . The standardized man-hour column 34b includes text boxes 34b1-34b17 in correspondence with the standardized man-hours of the items [12]-[20] of the "man-hours having values added" and the items [24]-[29] of the "man-hours having no values added", and the standard works [36], [37].
In the example shown in FIGS. 9A and 9B, the standardized man-hours are set for "welding" being the class of the constituent work CW (element work), "mig welding" being the constituent work CW (element work) name, and "at most 6 mm as the length of welding" and "one dot as the number of dots of welding" being the conditions of the constituent work CW (element work).
First, in case of selecting standardized man-hour analysis contents (that is, in case of selecting the class of a constituent work CW (element work) for which standardized man-hours are to be registered, the name of the constituent work CW (element work), and conditions correspondent to the constituent work CW (element work)), the user selects the class of a subject for the registration of the standardized man-hours, from among the check columns 34c1, . . . of the class selection column 34c. Then, constituent work CW (element work) names registered in the work constituent condition table 10 are displayed on the constituent work CW (element work) name selection column 34d in correspondence with the selected class. Besides, the user selects the constituent work CW (element work) name of the subject for the registration of the standardized man-hours, from among the check columns 34d1, . . . of the constituent work CW (element work) name selection column 34d. Then, conditions registered in the work constituent condition table 10 in correspondence with the selected constituent work CW (element work) name are displayed in the condition selection column 34e. Therefore, the user selects the conditions for which the standardized man-hours are to be registered, from among the check columns 34e1, . . . of the condition selection column 34e. When the class, name and conditions of the constituent work CW (element work) have been all selected, the items of pertinent works, movements, etc. are displayed in the standardized man-hour column 34b. By way of example, check columns 34c1, 34d1, 34e1 and 34e2 are selected as shown in FIG. 9B in order to select the class "welding", the constituent work CW (element work) name "mig welding" and the conditions "at most 6 mm as the length of welding" and "one dot as the number of dots for welding". By the way, in a case where data are already registered in the standardized man-hour table 11 in correspondence with the class, name and conditions of the selected constituent work CW (element work), they are read out and displayed in the text boxes 34b1-34b17 of the standardized man-hour column 34b. On the other hand, in a case where no data are registered in the standardized man-hour table 11 in correspondence with the class, name and conditions of the selected constituent work CW (element work), the text boxes 34b1-34b17 of the standardized man-hour column 34b become blank.
Subsequently, in case of inputting the standardized man-hours for the class of the selected constituent work CW (element work), the name thereof and the conditions thereof, the user inputs the numerical values of the standardized man-hours to the text boxes 34b1-34b15 for the items [12]-[20] of the "man-hours having values added" and the items [24]-[29] of the "man-hours having no values added", respectively. Further, the user inputs the numerical values of the standardized material Nos to the text boxes 34b16-34b17 of the standard works [36]-[37], respectively. Besides, he/she inputs remarks to the remarks column 34b18 of the registration screen 34. Incidentally, when the call button 34h of the registration screen 34 is clicked, the total of the standardized man-hours is displayed in the man-hour column 34i of this screen. Subsequently, in case of registering the selected standardized man-hour analysis contents and the inputted standardized man-hours, the user clicks the registration button 34f of the registration screen 34, whereby the contents and the man-hours are registered in the standardized man-hour table 11. By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the previous screen button 34g of the registration screen 34. Then, the registration screen 34 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
Next, the constituent name work condition item maintenance SS4 will be described with reference to FIG. 5 and FIG. 10A-10B. The constituent name work condition item maintenance SS4 performs maintenance (registration position alteration, copying, deletion, etc.) for the registered contents of the work conditions and the standardized man-hours in constituent work CW (element work) units, regarding the constituent work CW (element work) items registered by the constituent work CW (element work) condition management SS2, and it registers and manages data by the work constituent condition table 10 and the standardized man-hour table 11. By way of example, the registration position alteration collectively alters the set positions of registered constituent work CW (element work) item data and standardized man-hour data. More specifically, when the position of the class of a constituent work CW (element work) is altered (the position of "welding" is altered in FIG. 10A), the data of a constituent work CW (element work) name, work conditions and standardized man-hours which are constructed at the lower layers of the class are simultaneously altered. Also, when the position of the constituent work CW (element work) name is altered (the position of "mig welding" is altered in FIG. 10A), the data of the work conditions and standardized man-hours which are constructed at the lower layers of the constituent work CW (element work) name are simultaneously altered. That is, the constituent name work condition item maintenance SS4 can collectively perform the maintenance (registration position alteration [move], "copy" and "delete") without individually altering the constituent work CW (element work) item data constructed at the lower layers of each class.
The constituent name condition item maintenance SS4 is such that, when the selection button 30d of the menu screen 30 indicated on the display of the connection terminal 4 is clicked by the user, a constituent name condition item maintenance program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the editing screen 35 of the constituent name condition item maintenance SS4 as shown in FIG. 10B is indicated on the display of the connection terminal 4. At the start-up of the editing screen 35, data already registered in the work constituent condition table 10 are read out and are displayed on the editing screen 35. By the way, a class column 35a and a constituent work CW (element work) name column 35b are displayed on the editing screen 35. The class column 35a includes check columns 35a2, . . . corresponding to respective text boxes 35a1, . . . . Besides, the constituent work CW (element work) name column 35b includes check columns 35b4, . . . corresponding to respective text boxes 35b1, . . . .
In case of moving constituent work CW (element work) item data, the user selects any of the check columns 35a2, . . . or check columns 35b4, . . . corresponding to a class or constituent work CW (element work) name to-be-moved, and he/she clicks the validate button 35c of the editing screen 35. Besides, in case of the selection of the class, the user selects any of the text boxes 35a1, . . . as a moving goal by the cursor, or in case of the selection of the constituent work CW (element work) name, he/she selects any of the text boxes 35b1, . . . as a moving goal by the cursor. Further, when the user clicks the move button 35d of the editing screen 35, the selected class is displayed in one of the text boxes 35a1, . . . selected as the moving goal, in the case of the selection of the class, or the selected constituent work CW (element work) name is displayed in one of the text boxes 35b1, . . . selected as the moving goal, in the case of the selection of the constituent work CW (element work) name. Still further, a move completion validating screen 35i is indicated on the display of the connection terminal 4. Herein, the user clicks the OK button 35i1 of the move completion validating screen 35i, whereby the constituent work CW (element work) item data and the standardized man-hour data are moved to the moving goal. Subsequently, in case of registering the moved contents in the work constituent condition table 10 and standardized man-hour table 11, the user clicks the registration/previous screen button 35g of the editing screen 35, thereby to register the moved data in the work constituent condition table 10 and standardized man-hour table 11. By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the cancel/previous screen button 35h of the editing screen 35. Then, the editing screen 35 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
In case of copying constituent work CW (element work) item data, the user selects any of the check columns 35a2, . . . or check columns 35b4, . . . corresponding to a class or constituent work CW (element work) name to-be-copied, and he/she clicks the validate button 35c. Besides, in case of the selection of the class, the user selects any of the text boxes 35a1, . . . as a copying goal by the cursor, or in case of the selection of the constituent work CW (element work) name, he/she selects any of the text boxes 35b1, . . . as a copying goal by the cursor. Further, when the user clicks the copy button 35e of the editing screen 35, the selected class is displayed in one of the text boxes 35a1, . . . selected as the copying goal, in the case of the selection of the class, or the selected constituent work CW (element work) name is displayed in one of the text boxes 35b1, . . . selected as the copying goal, in the case of the selection of the constituent work CW (element work) name. Still further, a copy completion validating screen 35j is indicated on the display of the connection terminal 4. Herein, the user clicks the OK button 35j1 of the copy completion validating screen 35j, whereby the constituent work CW (element work) item data and the standardized man-hour data are copied to the copying goal. Subsequently, in case of registering the copied contents in the work constituent condition table 10 and standardized man-hour table 11, the user clicks the registration/previous screen button 35g of the editing screen 35, thereby to register the copied data in the work constituent condition table 10 and standardized man-hour table 11. By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the cancel/previous screen button 35h of the editing screen 35. Then, the editing screen 35 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
In case of deleting constituent work CW (element work) item data, the user selects any of the check columns 35a2, . . . or check columns 35b4, . . . corresponding to a class or constituent work CW (element work) name to-be-deleted, and he/she clicks the validate button 35c. Besides, when the user clicks the delete button 35f of the editing screen 35, a delete completion validating screen 35k is indicated on the display of the connection terminal 4. Herein, when the user clicks the YES button 35k1 of the delete completion validating screen 35k, the deletion of the constituent work CW (element work) item data and standardized man-hour data is executed, or when he/she clicks the NO button 35k2 of the delete completion validating screen 35k, the deletion of the constituent work CW (element work) item data and standardized man-hour data is cancelled. Further, in the case of the click of the YES button 35k1, a delete completion validating screen 35l is indicated on the display of the connection terminal 4. Herein, the user clicks the OK button 35l1 of the delete completion validating screen 35l, thereby to delete the constituent work CW (element work) item data and the standardized man-hour data. Subsequently, in case of registering the deleted contents in the work constituent condition table 10 and standardized man-hour table 11, the user clicks the registration/previous screen button 35g of the editing screen 35, whereby the deleted contents are registered in the work constituent condition table 10 and standardized man-hour table 11 (that is, the constituent work CW (element work) item data and the standardized man-hour data are deleted). By the way, in case of registering no data, or in case of returning to the menu screen 30, the user clicks the cancel/previous screen button 35h of the editing screen 35. Then, the editing screen 35 is erased from the display of the connection terminal 4, and the menu screen 30 is displayed.
Next, the derivation management system DS will be described with reference to FIG. 11 through FIG. 16. The derivation management system DS previously registers car sort (car type) data, production line data, and derivation data set for individual car types, such as 2 doors, 3 doors, 4 doors, for domestic use, for export to U.S., for export to Europe, for use in a cold district, grade, right steering wheel, left steering wheel, and with or without a sunroof.
The derivation management system DS is such that, when a derivation management system starting icon (not shown) indicated on the display of the connection terminal 4 is clicked by the user, a derivation management system program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the menu screen 40 of the derivation management system DS as shown in FIG. 11 is indicated on the display of the connection terminal 4.
Displayed on the menu screen 40 are a selection button 40a for the line name management DS1, a selection button 40b for the series registration management DS2, a selection button 40c for the derivation classification registration management DS3, a selection button 40d for the derivation format registration management DS4, a selection button 40e for the derivation code table management DS5, and a quit button 40f. Herein, when the user clicks any of the selection buttons 40a-40e, a corresponding application is executed, and when he/she clicks the quit button 40f; the application of the derivation management system DS is ended to erase the menu screen 40 from the display of the connection terminal 4.
First, the line name management DS1 will be described with reference to FIG. 11 and FIGS. 12A and 12B. The line name management DS1 registers and manages the modes of production lines which are implementing works, and it registers and manages data by the line name table 14. Item data for use in the main man-hour management system MS are registered in the line name table 14 beforehand, whereby the selective assignment of a line name and a cost center No is permitted. The data which are registered and managed are the line name [C] and cost center [D] in the line No [B] of the main man-hour management table 18.
The line name management DS1 is such that, when the selection button 40a of the menu screen 40 indicated on the display of the connection terminal 4 is clicked by the user, a line name management program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the registration screen 41 of the line name management DS1 as shown in FIG. 12A is indicated on the display of the connection terminal 4. At the start-up of the registration screen 41, data already registered in the line name table 14 are read out and are displayed on the registration screen 41. Herein, the data of the line name table 14 are concretely line names and cost center Nos at individual line Nos. Incidentally, the registration screen 41 is a screen for registering the line names and cost center Nos included in the respective line Nos. On the registration screen 41, accordingly, a line No column 41a is displayed, and a line name column 41b and a cost center No column 41c are arrayed and displayed. In addition, the line No column 41a includes a selection box 41a1 for registering the line No, the line name column 41b includes a plurality of text boxes 41b1, . . . for registering the line names, and the cost center No column 41c includes a plurality of text boxes 41c1, . . . for registering the cost center Nos, in correspondence with the text boxes 41b1, . . . .
By the way, as shown in FIG. 12B, automobiles in a plurality of series (of a plurality of car types) are produced in an automobile production factory, and they are assigned series [A], [A], . . . . Besides, a plurality of production lines are arranged in the factory, and they are assigned line Nos [B], [B], . . . . Further, a plurality of cost centers exist in each of the production lines, and they are assigned line names [C], [C], (cost centers [D], [D], . . . ). Still further, a plurality of processes exist in each of the cost centers, and they are assigned process names [E], [E], . . . .
First, in case of inputting the line No, the user moves the cursor to the selection box 41a1 of the line No column 41a of the registration screen 41. Besides, he/she inputs the line No to the selection box 41a1. Subsequently, in case of inputting the line name, the user moves the cursor to any of the text boxes 41b1, . . . of the line name column 41b of the registration screen 41. Besides, he/she inputs the line name to the specified text box 41b1. Further, in case of inputting the cost center No in correspondence with the line name, the user moves the cursor to that one of the text boxes 41c1, . . . of the cost center No column 41c of the registration screen 41 which corresponds to the line name. Besides, he/she inputs the cost center No to the specified text box 41c1. By the way, in the presence of a plurality of line names and cost center Nos, the above input processing is iterated a plurality of number of times. Subsequently, in case of registering the line name and cost center No for the inputted line No, the user clicks the registration button 41 e of the registration screen 41, whereby the data are registered in the line name table 14 (that is, data about the selected line No are deleted). By the way, in case of registering no data, or in case of returning to the menu screen 40, the user clicks the previous screen button 41d of the registration screen 41. Then, the registration screen 41 is erased from the display of the connection terminal 4, and the menu screen 40 is displayed.
Also, in case of deleting the data of the registered line No, the user moves the cursor to the selection box 41 a1 of the line No column 41a of the registration screen 41. Besides, he/she selects the line No to-be-deleted from within the selection box 41a1. Then, the data of the line name and cost center No corresponding to the selected line No are read out of the line name table 14 and are respectively displayed in the line name column 41b and cost center No column 41c. Therefore, the user clicks the delete button 41f of the registration screen 41. Then, a delete validating screen 41g is indicated on the display of the connection terminal 4. Herein, when the user clicks the YES button 41g1 of the delete validating screen 41g, the deletion of the data about the selected line No is executed, or when he/she clicks the NO button 41g2 of the delete validating screen 41g, the deletion of the data about the selected line No is cancelled. Subsequently, in case of registering the deleted contents in the line name table 14, he user clicks the registration button 41e of the registration screen 41, whereby the deleted contents are registered in the line name table 14. By the way, in case of registering no data, or in case of returning to the menu screen 40, the user clicks the previous screen button 41d of the registration screen 41. Then, the registration screen 41 is erased from the display of the connection terminal 4, and the menu screen 40 is displayed.
Incidentally, the data registered in the line name table 14 can be selected in the line No column 51b and line name column 51c of the sheet invoking screen 51 of the main screen 50 of the main man-hour management MS1. Besides, the selected data are displayed in the line name column 50c and cost center column 50d of the main screen 50.
Next, the series registration management DS2 will be described with reference to FIG. 11 and FIG. 13. The series registration management DS2 performs the registration management of the files of new series (car sorts) and the registration management of car types for the individual series, and it registers and manages data by the series table 13. Item data for use in the main man-hour management system MS are registered in the series table 13 beforehand, whereby the selective assignment of a series is permitted. The data which are registered are the series [A] and the car types for the series [A] in the main man-hour management table 18.
The series registration management DS2 is such that, when the selection button 40b of the menu screen 40 indicated on the display of the connection terminal 4 is clicked by the user, a series registration management program is loaded into the RAM of the connection terminal 4 and is run by the CPU thereof. Then, the registration screen 42 of the series registration management DS2 as shown in FIG. 13 is indicated on the display of the connection terminal 4. At the start-up of the registration screen 42, data already registered in the series table 13 are read out and are displayed on the registration screen 42. Herein, the data of the series table 13 are concretely car types in individual series. Incidentally, the registration screen 42 is a screen for registering the car types included in the respective series. On the registration screen 42, accordingly, a series column 42a and an identifier column 42b are arrayed and displayed, and a car type column 42c is displayed. In addition, the series column 42a includes a selection box 42a1 for registering the series, the identifier column 42b includes a text box 42b1 for registering an identifier, and the car type column 42c includes a plurality of text boxes 42c1, . . . for registering the car types.
First, in case of inputting the new series, the user moves the cursor to the selection box 42a1 of the series column 42a of the registration screen 42. Besides, he/she inputs the series to the selection box 42a1. Subsequently, in case of inputting the identifier for the new series, the user moves the cursor to the text box 42b1 of the identifier column 42b of the registration screen 42. Besides, he/she inputs the identifier to the above text box 42b1. Further, in case of inputting the car type in correspondence with the new series, the user moves the cursor to any of the text boxes 42c1, . . . of the car type column 42c of the registration screen 42. Besides, he/she inputs the car type to the specified text box 42c1. By the way, in the presence of a plurality of car types, the above input processing is iterated a plurality of number of times. Subsequently, in case of registering the data of the inputted new series, the user clicks the registration button 42d of the registration screen 42, whereby the data are registered in the series table 13. By the way, in case of registering no data, or in case of returning to the menu screen 40, the user clicks the previous screen button 42e of the registration screen 42. Then, the registration screen 42 is erased from the display of the connection terminal 4, and the menu screen 40 is displayed.
Next, in case of altering the data of the car type, the user moves the cursor to the selection box 42a1 of the series column 42a of the registration screen 42. Besides, he/she selects the series to-be-altered from within the selection box 42a1. Then, the data of the car type corresponding to the selected series are read out of the series table 13 and are displayed in the car type column 42c. Therefore, the user moves the cursor to that one of the text boxes 42c1, . . . which corresponds to the car type to-be-altered. Besides, he/she rewrites the car type of the specified text box 42c1 or inputs the car type anew. By the way, in the presence of a plurality of car types to-be-altered, the above alteration processing is iterated a plurality of number of times. Subsequently, in case of registering the data of the altered car type, the user clicks the registration button 42d of the registration screen 42, whereby the data are registered in the series table 13. By the way, in case of registering no data, or in case of returning to the menu screen 40, the user clicks the previous screen button 42e of the registration screen 42. Then, the registration screen 42 is erased from the display of the connection terminal 4, and the menu screen 40 is displayed.
Next, in case of deleting the data of the series, the user moves the cursor to the selection box 42a1 of the series column 42a of the registration screen 42. Besides, he/she selects the series to-be-deleted from within the selection box 42a1. Then, the data of the car type corresponding to the selected series are read out of the series table 13 and are displayed in the car type column 42c. Therefore, the user clicks the delete button 42f of the registration screen 42. Then, a delete validating screen 42h is indicated on the display of the connection terminal 4. Herein, when the user clicks the YES button 42h1 of the delete validating screen 42h< |
