JP2012118711A - Data management system, data management method and data management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress deterioration in mass data processing performance while implementing past data utilization in a production management job system at low costs.SOLUTION: A computer retrieves a target which does not have any reverse target and of which the production status indicates completion, and a target which does not have any reserve target and of which the production status indicates any other status than completion, extracts a succession of targets in a reserve relationship with each target as an origin, and stores records in a memory. A first flag is set to the record of the target of which the production status indicates completion, and a second flag is set to the record of the target of which the production status indicates any other status than completion. The records to which the first flag and the second flag have been set are collated, and a reserve relationship is extracted for a target indicated by a record to which the second flag has been set but has the same production number in the records to which the first flag has been set. In the case where the first flag is set, it is changed into the second flag and the record to which the first flag has been set is registered in a storage section as history information in addition to reserve information.

Description

  The present invention relates to a data management system, a data management method, and a data management program, and more specifically, deterioration of mass data processing performance while realizing the use of past data in a business system for production management at a low cost. It is related with the technology which controls.

  There is a business that formulates a production plan for a product based on order information, etc., and performs production of parts and semi-finished products constituting the product, instructions for provisioning, collection / management of production results, and the like. If a business system for production management that manages such work is continuously used, a large amount of performance data is accumulated. For this reason, there is a problem that the load on the system increases during execution of a large amount of data processing (such as MRP), and the processing speed becomes slow.

  Therefore, for example, for the purpose of providing an entry / exit history record management device that can efficiently collect and aggregate entry / exit data without imposing a heavy load on the system, it is recorded in a database that is not recorded in character strings. The character string data converted by converting the entry / exit history into a text character string or a binary data string corresponding to the text character string is defined as a file whose file name is the management time corresponding to the converted entry / exit history A first data conversion means for storing in the area, a first database in which data of the past entry / exit history in the past for a predetermined short period from the present to the present is recorded, and at least recorded in the first database A second database in which data of the past entry / exit history for a period that has not been recorded is recorded, and a file stored in the predetermined area The second data converting means for converting the data of the exit history into the data of the entrance / exit history of the second database and storing the data in the second database; and all the periods of the entrance / exit history requested from the outside If the data storage periods of the first and second databases do not match and are not included, the second data conversion means converts the entry / exit history data for a period that is insufficient as the data storage period. The data management means for converting from the file entry / exit history data to the second database and supplementing the second database entry / exit history data with reference to the outside, An entry / exit history record management device in which the file is substantially stored in the predetermined area over the entire operational period longer than the first database (see, for example, Patent Document 1). Etc. has been proposed.

JP 2004-145787 A

  However, in order to cope with the situation of performance degradation due to an increase in load, if past past performance data is simply deleted or archived, the corresponding data cannot be used when necessary. On the other hand, in order to be able to refer to archived past performance data, it is necessary to separately construct a mechanism for referring to past output slips, resulting in an increase in cost. On the other hand, if nothing is done, there is a concern that the operation of the business system may be interrupted or stagnated due to performance degradation due to increased load.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a technique for suppressing deterioration of mass data processing performance while realizing the use of past data in a production management business system at a low cost.

  A data management system of the present invention that solves the above-described problems includes a storage unit that stores allocation information that includes at least information on an allocation relationship between objects, a production number, and a production status regarding an object of production management, and the allocation A process of referring to the allocation relationship and production status information of information, and searching for an object having no allocation object and indicating that the production status is complete, and an object having no allocation object and indicating a status other than completion, and Starting from each target object identified by the search, a series of targets in the allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted target object is read from the allocation information and stored in the memory And in the memory, in the target object group that continues from the target that indicates that there is no allocation target and the production status is complete, The first flag is set in the record of the target object whose production status indicates completion, and the status other than the production status among the target object groups starting from the target object indicating the status other than the completion of the provisioning status and the production status The process of setting the second flag in the record of the object indicating the above, the record in which the first flag is set, and the record in which the second flag is set are collated, and the record in which the second flag is set There is a record having the same production number in the record in which the first flag is set, and for the object indicated by the specified record, a series of objects in the allocation relationship is extracted in the allocation information, When the first flag is set in the extracted record, the process of changing to the second flag, and the record in which the first flag is set are separated from the allocation information An arithmetic unit that executes a process of registering in the storage unit as the gravel information, characterized in that it comprises a.

  In addition, the data management method of the present invention includes a storage unit that stores allocation information including at least information on allocation relations between objects, production numbers, and production status relating to production management objects, and a calculation unit. The computer refers to the allocation relationship and the production status information of the allocation information, and selects an object that does not have an allocation object and indicates that the production status is complete, and an object that does not have an allocation object and indicates a status other than completion. Starting from each object identified by the search and the object identified by the retrieval, a series of objects in an allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted object is allocated to the allocation information Read from and stored in the memory, and in the memory, the starting point is an object for which there is no allocation target and the production status indicates completion The first flag is set in the record of the object whose production status indicates completion among the object groups, and the production among the object groups connected from the target object indicating the status other than the completion that has no allocation target A process for setting a second flag in a record of an object indicating a status other than completion, a record in which the first flag is set, and a record in which the second flag is set are collated, and a second flag Is set, but the record with the same production number is specified in the record in which the first flag is set, and the object indicated by the specified record is the object of the allocation relationship in the allocation information. A process of extracting a series and changing to a second flag when the first flag is set in the extracted record; and a record in which the first flag is set And executes a processing for separately registered in the storage unit as history information from the person information.

  The data management program according to the present invention further includes a storage unit that stores allocation information that includes at least information on allocation relations between objects, production numbers, and production status related to production management objects, and a calculation unit. With reference to the allocation relationship and production status information of the allocation information, an object indicating that there is no allocation object and the production status is complete and an object indicating that there is no allocation object and the production status is other than completion are displayed on the computer. Starting from each object identified by the search and the object identified by the retrieval, a series of objects in an allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted object is allocated to the allocation information Starting from an object for which there is no allocation object and the production status is completed in the memory. Among the target object group, the first flag is set in the record of the target object indicating that the production status is complete, and among the target object group that is linked from the target object indicating the status other than the completion target and the production status, A process for setting a second flag in a record of an object whose production status indicates a status other than completion, a record in which the first flag is set, and a record in which the second flag is set are collated, A record in which the flag is set, but the record having the same production number is specified in the record in which the first flag is set, and the object indicated by the specified record is in an allocation relationship in the allocation information If the first flag is set in the extracted record, a process for changing to the second flag and the record in which the first flag is set are extracted. Characterized in that to execute a process of separately registered in the storage unit as history information and the provision information.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to suppress degradation of mass data processing performance, implement | achieving the past data utilization in the business system for production management at low cost.

It is a network block diagram containing the data management system of this embodiment. It is a figure which shows the structural example of the data management system of this embodiment. It is a figure which shows each data structural example of the production schedule information part and provision information part of this embodiment. It is a figure which shows each data structural example of the plan information part of this embodiment, an instruction information part, and a track record information part. It is a figure which shows the process flow example 1 of this embodiment. It is a figure which shows the process flow example 2 of this embodiment. It is a figure which shows the process flow example 3 of this embodiment. It is a figure which shows the process flow example 4 of this embodiment. It is a figure which shows the example 1 of a concept of the information processing of this embodiment. It is a figure which shows the conceptual example 2 of the information processing of this embodiment. It is a figure which shows the example 3 of a concept of the information processing of this embodiment. It is a figure which shows the example 4 of a concept of the information processing of this embodiment. It is a figure which shows the determination concept of the historical information of this embodiment. It is a figure which shows the example 5 of a concept of the information processing of this embodiment. It is a figure which shows the conceptual example 6 of the information processing of this embodiment. It is a figure which shows the conceptual example 7 of the information processing of this embodiment. It is a figure which shows the conceptual example 8 of the information processing of this embodiment. It is a figure which shows each data structure example of the allocation history information part of this embodiment, a plan history information part, an instruction | indication history information part, and a performance history information part. It is a figure which shows the process flow example 5 of this embodiment. It is a figure which shows the process flow example 6 of this embodiment. It is a figure which shows the process flow example 7 of this embodiment. It is a figure which shows the example 1 of a screen of this embodiment. It is a figure which shows the example 2 of a screen of this embodiment. It is a figure which shows the example 3 of a screen of this embodiment. It is a figure which shows the example 4 of a screen of this embodiment. It is a figure which shows the example 5 of a screen of this embodiment.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a network configuration diagram including the data management system of this embodiment. A data management system 100 (hereinafter, system 100) shown in FIG. 1 is a computer system that suppresses deterioration of mass data processing performance while realizing past data use in a production management business system at low cost. As an example of the data management system 100 of the present embodiment, a server device that processes and returns data in response to requests from various terminals, for example, can be assumed. The network 140 in this embodiment includes computer terminals such as the design department terminal 200, the production management department terminal 210, the material management department terminal 220, the ordering terminal 230, the subcontractor terminal 240, and the purchaser terminal 250, in addition to the system 100. Is connected.

  In the example shown in FIG. 1, among the above, the system 100, the design department terminal 200, the production management department terminal 210, and the material management department terminal 220 are computers such as computers involved in production management work in the same company on an intranet or the like. It is tied so that it can communicate. Further, a terminal used by another business operator who orders an article to be a production management work, that is, a product to be produced, is the ordering source terminal 230. In addition to producing the object of production management in-house, there are cases where a part is outsourced, but the terminal used by the subcontractor company is the subcontractor terminal 240. In addition to producing the object of production management in-house as well as purchasing from outside, the terminal used by the purchaser company is the purchaser terminal 250.

  In the general flow of production management work, it is likely that product ordering instruction information enters the system 100 from the ordering source terminal 230 first. In response to the system 100, the design department terminal 200 acquires the content of the product order and displays it on a display or the like. A person in charge of the design department browses the content information of the displayed product order and executes product design. The design content input at the design department terminal 200 is registered in the system 100. A person in charge of the production management department browses the design contents using the production management department terminal 210, creates information for actual production management, and registers it in the system 100. The person in charge of the material management department browses the information for production management using the material management department terminal 220, and the materials and parts necessary for the subcontractor terminal 240, the supplier terminal 250, etc. as well as in-house. The arrangement instruction will be executed.

  Next, the configuration of the system 100 of this embodiment will be described. FIG. 2 is a diagram showing a configuration example of the data management system of the present embodiment. The system 100 naturally includes a configuration that a normal computer should have, and includes a storage unit 101 configured by a nonvolatile storage device such as a hard disk drive, a memory 103 such as a nonvolatile storage device such as a RAM, and the storage unit 101. An arithmetic unit 104 such as a CPU that reads and executes the program 102 stored in the computer and implements necessary functions, a keyboard, a mouse, a touch panel or other user interface such as a touch panel, and displays processing results And an output unit 106 such as a display, and a communication unit 107 such as a NIC (Network Interface Card) for communicating with other devices. Screen data 110 to be displayed on the output unit 106 according to the situation in the business flow is prepared in the storage unit 101 in advance. Further, the storage unit 101 includes a production schedule information unit 125, an allocation information unit 126, a plan information unit 127, and an instruction information unit 128 as databases used by the system 100 to execute the data management method of the present embodiment. , A performance information part 129, and history information 130-133 are stored. Details of such information will be described later.

  Next, functions implemented by the calculation unit 104 of the system 100 executing the program 102 will be described. The system 100 refers to the information on the allocation relationship (in the example of FIG. 3, “allocation number”, “destination allocation number” in the example of FIG. 3) and the production status (“state” in the example of FIG. 3) of the allocation information unit 126, It has a function of searching for an object that has no allocation object and indicates that the production status is complete, and an object that has no allocation object and whose production status indicates a status other than completion.

  In addition, the system 100 extracts a series of objects in the allocation relationship from the allocation information in the allocation information unit 126, starting from each of the objects identified by the search, and extracts each of the extracted objects. It has a function of reading a record from the allocation information unit 126 and storing it in the memory 103.

  In addition, the system 100 includes a first flag (see FIG. 5) in a record of an object whose production status indicates completion among a group of objects that start from an object whose production status indicates completion in the memory 103. In the example of 11, the “target” flag in the “target flag” column is set, and the production status is other than completion in the target object group starting from an object that has no provision object and has a status other than completion. The second flag (in the example of FIG. 11, the “non-target” flag in the “target flag” column) is set in the record of the target object that indicates the status.

  Further, the system 100 collates the record in which the first flag is set with the record in which the second flag is set, and is a record in which the second flag is set, but the first flag is set. In the record, the same production number is specified, and for the object indicated by the specified record, the allocation information unit 126 extracts a series of objects in the allocation relationship, and the extracted flag includes the first flag. Has a function of changing to the second flag.

  Further, the system 100 has a function of registering the record in which the first flag is set in the storage unit 101 as history information (in the example of FIG. 2, the allocation history information unit 130) separately from the allocation information unit 126. Have.

  The system 100 extracts the corresponding records in the plan information unit 127, the instruction information unit 128, and the performance information unit 129 from the storage unit 101 for each object indicated by the record included in the history information, If it has a function of registering the extracted information in the storage unit 101 as history information about the target object (in the example of FIG. 2, the plan history information unit 131, the instruction history information unit 132, and the result history information unit 133). Is preferred.

  In addition, the system 100 receives information requests from various terminals such as the design department terminal 200, the production management department terminal 210, and the material management department terminal 220 via the communication unit 107, and an object corresponding to the information request. As the information regarding the target object, the plan information, the instruction information, the actual information, and the history information are stored in the storage unit 101. The plan information unit 127, the instruction information unit 128, the actual information unit 129, the allocation history It has a function of extracting from the information unit 130, the plan history information unit 131, the instruction history information unit 132, and the result history information unit 133, respectively, and returning them to the terminal.

--- Data structure example ---
Next, an example of the data structure of information used by the data management system 100 of this embodiment will be described. The information may be managed in a nonvolatile storage device such as a hard disk drive that can be used via a network, in addition to the storage unit 101 provided in the system 100 itself. The history information such as the allocation history information unit 130, the plan history information unit 131, the instruction history information unit 132, and the result history information unit 133 will be described later.

  FIG. 3 is a diagram showing a data configuration example of the production schedule information unit 125 and the allocation information unit 126 of the present embodiment. The production schedule information unit 125 allows each person in charge, such as the design department, the production management department, and the material management department, to select the target product and its components, according to the order data received by the system 100 from the orderer terminal 230. This is a database that stores information on the production, and the information determined for each product, that is, the production quantity and delivery date of the object in the present embodiment. In the example of FIG. 1, the record number is associated with data such as the item of the object, the quantity to be produced, and the delivery date, using the schedule number uniquely determined for each production event and the production number as a key.

  The allocation information unit 126 is a database that stores allocation information that includes at least information on allocation relations between objects, production numbers, and production status regarding the objects of production management. This information is information that combines information for production management into a bill of materials that shows how semi-finished products and parts are allocated to each other in order to produce the ordered product. It can also be said.

  In the example of the allocation information part 126 shown in the figure, the allocation number is used as a key, and a record in which each data of the allocation number, the production number, the plan number, the instruction number, the actual number, the item, the allocation quantity, and the state is associated with each other. It is an aggregate. In this example, the “provision number” is an identification number that is uniquely assigned to each of the above-mentioned objects that are the targets of production management. Usually, the final product and the half that constitutes the product are arranged in ascending order. It is set for each part of the product and semi-finished product. Further, the “advance allocation number” is an allocation number of an object that is an allocation destination of the corresponding object. The “production number” corresponds to the production number of the record established by the production schedule information unit 125 regarding the production of the target object. The “plan number” is a plan number of a record corresponding to the production number in the plan information unit 127 described later. Similarly, the “instruction number” becomes the instruction number of the record corresponding to the production number in the instruction information unit 128 described later, and the “result number” is the record number of the record corresponding to the production number in the result information unit 129 described later. Number. The “item” is an item corresponding to the production number of the record established in the production schedule information unit 125 regarding the production of the target object. “Allocated quantity” indicates the quantity that the target object is allocated to the object specified by the prior allocation number. The “state” is information indicating the production status of the target object. Among the information described above, for example, a series of allocation numbers and prior allocation numbers corresponds to information regarding allocation relations between objects.

  Then, each data structural example of the plan information part 127, the instruction information part 128, and the performance information part 129 is demonstrated. FIG. 4 is a diagram illustrating a data configuration example of the plan information unit 127, the instruction information unit 128, and the result information unit 129 of the present embodiment. The plan information unit 127 is a collection of information in which a plan number is assigned to each record of the production schedule information unit 125, and a production start date and an end date are set.

  The instruction information unit 128 is a database that stores instruction information for the production department or the procurement department based on the plan information relating to the production of the target object, and uses the instruction number associated with the production number for the target object as a key. , A collection of records in which data such as production numbers, items, and quantities are associated with each other.

  The actual result information part 129 is a database in which information on production results actually made based on the information of the above-described plan information part 127 and instruction information part 128 is stored, and the actual result number associated with the production number. Is a set of records in which data such as production number, item, and quantity are associated with each other.

--- Example of pretreatment ---
FIG. 5 is a diagram showing a processing flow example 1 of the present embodiment. First, an outline of the process before the execution of the data management method of this embodiment will be given. In this case, in step s101, the system 100 receives the order information transmitted from the ordering source terminal 230, and provides this information to the production management department terminal 210 upon request. In the production management department terminal 210, the person in charge reads the information and determines the production schedule. The production management department terminal 210 registers the production schedule information thus determined in the production schedule information section 125 of the system 100. FIG. 22 shows an example of an input screen for production schedule information in the present embodiment.

  Next, in step s102, the system 100 receives various information obtained in step s101 and information on the item configuration and inventory of products and parts prepared in advance in the storage unit 101, for example, in response to a request. To various terminals 200-220. Using these information, the person in charge performs the production of material requirements and executes production planning, and uses the terminals 200 to 220 and the like to obtain the planning results, and the allocation information section 126 and the planning information of the system 100. Registered in the unit 127.

  Subsequently, in step s103, the system 100 extracts a record to be a production instruction target based on, for example, the start date information in the plan information unit 127 registered in the step s102, and stores it in the storage unit 101. Register in the instruction information unit 128.

  In step s104, the system 100 registers actual production record information related to the object indicated by the record in the instruction information unit 128 registered in step s103 in the record information unit 129 as a record record. The production result information is received and acquired by the system 100 from the production management department terminal 210, for example. FIG. 25 shows an example of a record information input screen in the present embodiment.

  Next, in step s105, the system 100 receives an instruction from the terminals 200 to 220 and the like, and if re-planning is necessary (s105: YES), the process returns to the step s101, and re-planning is unnecessary. (S105: NO), this flow is terminated.

  In any case, the above processing flow is merely an example, and when executing the data management method of the present embodiment, the production schedule information section 125, the allocation information section 126, the plan information section 127, the instruction information section 128, the actual result The information unit 129 and the like need only store necessary information in advance, and the acquisition route, method, and the like are not limited to the above flow.

--- Processing procedure example 2 ---
Hereinafter, the actual procedure of the data management method in the present embodiment will be described with reference to the drawings. Various operations corresponding to the data management method described below are realized by a program 102 that is read into the memory 103 of the system 100 and executed. And this program 102 is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 6 is a diagram showing a processing flow example 2 of the present embodiment. In this case, the system 100 stores information on the allocation relationship (“allocation number” and “destination allocation number” in the example of FIG. 3) and production status (“state” in the example of FIG. 3) of the allocation information unit 126. Extracted and registered in the memory 103 (s201). FIG. 9 shows an example of the processing concept.

  Subsequently, the system 100 refers to the information registered in the memory 103 in the step s201, and “there is no provisioning number or a provisioning number that is in the provisioning number and not in the provisioning number”, that is, there is no provisioning object. , A record whose “state” is “completed” is extracted as an expansion start point to be reflected in the history information and registered in the memory 103 (s202).

  Similarly, referring to the information registered in the memory 103 in the step s201, “the provisioning number is not present or the provisioning number is in the provisioning number and not in the provisioning number”, that is, there is no provisioning target, ”Is extracted as a development start point that is not a reflection target in the history information and registered in the memory 103 (s203). FIG. 10 shows an example of the processing concept. In this case, the record with the allocation number “01” is specified as the starting point of the reflection target in the history information, and the record with the allocation number “02” is specified as the starting point that is not the reflection target in the history information.

  The flow from here is based on FIG. Subsequently, the system 100 starts from the record registered in the memory 103 in step s202 as the development start point, and the information of the allocation information unit 126 registered in the memory 103 in step s201 indicates the object in the allocation relationship. The series is extracted, and the corresponding records are registered in the memory 103 in order from the higher order to the lower order of the allocation relationship (s204). Further, the system 100 sets a “target” flag in the item “target flag” in the record registered in the memory 103 in step s204 (s205).

  FIG. 11 shows a conceptual example of these processes. In the example of FIG. 11, starting from the record with the allocation number “01”, each record with the allocation numbers “03” and “04” having the “01” in the destination allocation number and “03” to “ “04”, the allocation numbers “06”, “07”, “08”, and the allocation numbers “11”, “08” having any of the allocation numbers “06”, “07”, “08”. Each record of “12” and “13” is extracted as a series of objects having an allocation relationship. In this case, the corresponding records are registered in the memory 103 in order from the upper order of the allocation relationship, that is, from the record of the allocation number “01” to the lower record of “13”.

  Subsequently, the system 100 starts from the record registered in the memory 103 in step s203 as the starting point of development, and in the information of the allocation information unit 126 registered in the memory 103 in step s201, the system 100 The series is extracted, and the corresponding records are registered in the memory 103 in order from the upper level to the lower level of the allocation relationship (s206). Further, the system 100 sets a “non-target” flag in the “target flag” item in the record registered in the memory 103 in step s206 (s207).

  FIG. 12 shows a conceptual example of these processes. In the example of FIG. 12, starting from the record of the allocation number “02”, the allocation number “09” having the allocation number “05” having the allocation number “02” and the allocation number “09” having the allocation number “05”. ”,“ 10 ”records, and the allocation numbers“ 14 ”and“ 15 ”having either“ 09 ”or“ 10 ”in the pre-assignment number are extracted as a series of objects having an allocation relationship. Has been. In this case, the corresponding records are registered in the memory 103 in order from the upper order of the allocation relationship, that is, from the record of the allocation number “02” to the lower record of “15”.

  The system 100 in step s207 collates the record with the “target” flag set with the record with the “non-target” flag set, and records the “non-target” flag set. There is a record with the same “production number” in the record in which the “target” flag is set. In the example shown in FIG. 11, the record of the allocation number “08” in which the “target” flag is set and the record of the allocation number “09” in which the “non-target” flag is set in the example shown in FIG. The “production number” is the same as “007”, and the system 100 identifies the record having the allocation number “08”. Further, the system 100 extracts the record with the allocation number “13” from the information in the allocation information unit 126 developed in the memory 103 as a series of the objects having the allocation number and the allocation number “08”. Yes. Then, the system 100 changes the “target” flag to the “non-target” flag for the “target flag” in the records of the allocation number “08” and the allocation number “13”.

  As shown in FIG. 13, the concept of such flag change processing is based on a series in the provision relation of articles allocated to a product or the like starting from a product or the like whose production status is “completed”, and the production status is “ Compared with the series in the provisioning relationship of articles allocated to the product, etc. starting from the product other than "completed", articles with the same production number are used between these series It is characterized by identifying the situation. In addition, it is possible to consider the case where the grant target of the “subject” flag, which has been determined to be treated as history information, is actually composed of articles that are subject to the “exclude” flag. The allocation relationship is also double-checked from the viewpoint of production number, and only the information that may be handled as history information is allocated history information section 130, plan history information section 131, instruction history information section 132, record history information. It is stored in the unit 133 and the like.

  In the example illustrated in FIG. 13, for example, an object having a production number “C” is allocated with respect to an object having a production number “B”, but the object having the production number “B” is “object”, “ It is included in any provisioning relationship series that is not eligible. That is, among the objects with the production number “C”, one individual product is assigned to the production number “B” to which the “target” flag is assigned, and another individual product is produced with the “out of target” flag. It is assigned to the number “B”, and it can be said that brother-related articles are divided into the history information target and the non-target. Alternatively, if there is an article that is excluded from the historical information in the article that goes back to the upper level, that is, the ancestor in the allocation relationship, the possibility that the data is also used for the lower level corresponding article remains. I do not.

  The flow from here is based on FIG. Subsequently, as shown in FIG. 14, the system 100 records a record in which the “target” flag is set in the information of the allocation information unit 126 copied to the memory 103, with the allocation information unit 126 of the storage unit 101. Otherwise, it is registered in the allocation history information section 130 as history information (s208).

  Similarly, as shown in FIG. 15, the system 100 stores the record corresponding to the plan number indicated by the corresponding record registered in the allocation history information unit 130 as the history information in the step s 208 as the plan information in the storage unit 101. The information is extracted from the unit 127 and registered in the plan history information unit 131 (s209). Further, as shown in FIG. 16, the system 100 records a record corresponding to the instruction number indicated by the corresponding record registered in the allocation history information unit 130 as history information in the step s 208, in the instruction information unit 128 of the storage unit 101. And is registered in the instruction history information unit 132 (s210). Further, as shown in FIG. 17, the system 100 records a record corresponding to the record number indicated by the corresponding record registered in the allocation history information unit 130 as history information in the step s 208, in the record information unit 129 of the storage unit 101. And is registered in the history record information section 133 (s211). An example of the allocation history information unit 130, the plan history information unit 131, the instruction history information unit 132, and the result history information unit 133 generated in this way is illustrated in FIG.

--- Processing procedure example 3 ---
Next, information input / output processing in the system 100 will be described. FIG. 19 shows a processing flow example 5 of this embodiment, FIG. 20 shows a processing flow example 6 of this embodiment, and FIG. 21 shows a processing flow example 7 of this embodiment. In this case, the system 100 receives information requests from various terminals such as the design department terminal 200, the production management department terminal 210, and the material management department terminal 220 via the communication unit 107, and targets corresponding to the information requests As information about the object, a record of the target object is extracted from the plan information unit 127 in the storage unit 101 and returned to the terminal (s301). FIG. 23 shows an example of the plan information output screen in this embodiment.

  Alternatively, the system 100 receives information requests from various terminals such as the design department terminal 200, the production management department terminal 210, and the material management department terminal 220 via the communication unit 107, and an object corresponding to the information request. As information on the relevant object, a record of the target object is extracted from the instruction information unit 128 in the storage unit 101 and returned to the terminal (s302). FIG. 24 shows an example of an instruction information output screen in the present embodiment.

  Alternatively, the system 100 receives information requests from various terminals such as the design department terminal 200, the production management department terminal 210, and the material management department terminal 220 via the communication unit 107, and an object corresponding to the information request. As the information regarding, the record of the target object is extracted from the record information unit 129 in the storage unit 101 and returned to the terminal (s302). FIG. 26 shows an example of an output screen for performance information in the present embodiment.

  Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

  According to the present embodiment, in the production management business flow, the status in production management is completed, and information that cannot be used for rewriting / updating in relation to other articles to be allocated, and other information Information (information that remains available for rewriting, updating, etc.) is managed, and information that does not use rewriting / updating is managed separately as history information. For example, only for output requests It can be handled as information provided correspondingly. In other words, the targets for receiving processing such as input and update in the business system are limited to information that can be used for update and the like, and the data processing load on the business system can be effectively suppressed. Moreover, in order to realize such a mechanism, it is not necessary to introduce special new hardware, etc., so it can be realized at low cost by combining the effective use of history information (= past data) and the suppression of the above data processing load. It becomes possible to do.

  Accordingly, it is possible to suppress the deterioration of the mass data processing performance while realizing the use of the past data in the production management business system at a low cost.

  At least the following will be clarified by the description of the present specification. That is, in the data management system, the storage unit further stores plan information related to the production of the target object, instruction information to a production department or a procurement department based on the plan, and production performance information. The unit extracts the plan information, the instruction information, and the performance information from the storage unit for each object indicated by the record included in the history information, and stores the extracted information as history information regarding the target object in the storage unit. The registration process may be executed.

  In addition, the data management system includes a communication unit that communicates with an external device, the calculation unit receives an information request from a terminal via the communication unit, and as information about the object corresponding to the information request, It is good also as what performs the process which extracts the plan information, instruction | indication information, performance information, and the said historical information of an applicable target object from the memory | storage part, and returns to the said terminal.

DESCRIPTION OF SYMBOLS 100 Data management system 101 Memory | storage part 102 Program 103 Memory 104 Operation part 105 Input part 106 Output part 107 Communication part 110 Screen data 125 Production schedule information part 126 Allocation information part 127 Plan information part 128 Instruction information part 129 Performance information part 130 Allocation history Information section 131 Plan history information section 132 Instruction history information section 133 Results history information section 140 Network 200 Design department terminal 210 Production management department terminal 220 Material management department terminal 230 Ordering source terminal 240 Subcontractor terminal 250 Supplier terminal

Claims (5)

A storage unit for storing provision information including at least information on provision relations between the objects, production numbers, and production statuses regarding the objects of production management;
A process of referring to the allocation relationship and the production status information of the allocation information, and searching for an object having no allocation object and indicating that the production status is complete, and an object having no allocation object and indicating a status other than completion. ,
Starting from each object identified by the search, a series of objects in an allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted object is read from the allocation information and stored in the memory. Processing to store,
In the memory, the first flag is set in the record of the target object whose production status indicates completion among the target object groups starting from the target object indicating that there is no allocation target and the production status is complete. Processing for setting a second flag in a record of a target object indicating a status other than completion among target object groups starting from an object indicating a status other than completed,
The record in which the first flag is set is collated with the record in which the second flag is set, and the record in which the second flag is set. When the same thing is specified, a series of objects having an allocation relationship is extracted in the allocation information for the object indicated by the specified record, and the first flag is set in the extracted record Processing to change to 2 flags,
A calculation unit that executes a process of registering the record in which the first flag is set in the storage unit as history information separately from the allocation information;
A data management system comprising: The storage unit further stores plan information relating to the production of the object, instruction information to a production department or a procurement department based on the plan, and production performance information,
The calculation unit extracts the plan information, the instruction information, and the performance information from the storage unit for each object indicated by the record included in the history information, and stores the extracted information as history information about the target object. To execute the process of registering in the copy,
The data management system according to claim 1. A communication unit that communicates with an external device;
The arithmetic unit receives an information request from a terminal via the communication unit, and information on the target corresponding to the information request includes plan information, instruction information, and actual information of the target object, and the history information. Are extracted from the storage unit and returned to the terminal.
The data management system according to claim 2. A computer comprising a storage unit for storing allocation information including at least each information of an allocation relationship between production objects, a production number, and a production status regarding an object of production management, and a calculation unit,
A process of referring to the allocation relationship and the production status information of the allocation information, and searching for an object having no allocation object and indicating that the production status is complete, and an object having no allocation object and indicating a status other than completion. ,
Starting from each object identified by the search, a series of objects in an allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted object is read from the allocation information and stored in the memory. Processing to store,
In the memory, the first flag is set in the record of the target object whose production status indicates completion among the target object groups starting from the target object indicating that there is no allocation target and the production status is complete. Processing for setting a second flag in a record of a target object indicating a status other than completion among target object groups starting from an object indicating a status other than completed,
The record in which the first flag is set is collated with the record in which the second flag is set, and the record in which the second flag is set. When the same thing is specified, a series of objects having an allocation relationship is extracted in the allocation information for the object indicated by the specified record, and the first flag is set in the extracted record Processing to change to 2 flags,
A process of registering the record in which the first flag is set in the storage unit as history information separately from the allocation information;
The data management method characterized by performing. In a computer comprising a storage unit for storing provision information including at least information on provision relations between objects, production numbers, and production status, and a calculation unit, regarding production management objects,
A process of referring to the allocation relationship and the production status information of the allocation information, and searching for an object having no allocation object and indicating that the production status is complete, and an object having no allocation object and indicating a status other than completion. ,
Starting from each object identified by the search, a series of objects in an allocation relationship is extracted from the allocation information in the allocation information, and each record of the extracted object is read from the allocation information and stored in the memory. Processing to store,
In the memory, the first flag is set in the record of the target object whose production status indicates completion among the target object groups starting from the target object indicating that there is no allocation target and the production status is complete. Processing for setting a second flag in a record of a target object indicating a status other than completion among target object groups starting from an object indicating a status other than completed,
The record in which the first flag is set is collated with the record in which the second flag is set, and the record in which the second flag is set. When the same thing is specified, a series of objects having an allocation relationship is extracted in the allocation information for the object indicated by the specified record, and the first flag is set in the extracted record Processing to change to 2 flags,
A process of registering the record in which the first flag is set in the storage unit as history information separately from the allocation information;
A data management program characterized in that

Images