JPH08137938A - Document change history management device - Google Patents

Abstract

(57) [Summary] [Purpose] To realize a document change history management device in which a configuration history table is automatically created using the data of the issued issuance / change notice. [Structure] A notification creation unit that has the function of creating a document issuance / change notification, which is the unit for issuing documents, and a document creation / creation created by this notification
From the drawing approval unit that has the function to generate a trigger to create the configuration history table when printing the change notification, the part information creation unit that has the function to create information that depends on the part number, and the drawing approval unit In response to the trigger of, the function to extract the information required for creating the configuration history table from the information input in the notification creation section and the information created in the parts information creation section and rearrange it arbitrarily to create the configuration history table The history table creating unit is provided.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a device for managing a technical document in a design engineering business, and more particularly to a document change history management device for managing change history data such as a design drawing in which a history of changes is important. .

[0002]

2. Description of the Related Art Conventionally, in order to manage a change history of a technical document such as a drawing, it is necessary to maintain the next document in addition to the drawing to be changed. Issuance / change notice ... What kind of drawing was changed and what time it was shown Configuration history table ... What kind of change history a certain drawing group had undergone

Although the issuance / change notice and the configuration history table have almost the same contents of description, the issuance / change notice is generated every time a change event occurs. One is generated for each drawing group. For complex system products, etc., one document may be manufactured using many documents.
A configuration history table is essential.

[0004]

As described above, when a technical document is modified, two documents having almost the same description content are created, so it takes time to create the document. There was a problem such as occurrence.

An object of the present invention is to eliminate such a point, and a document change history management device capable of automatically creating a "configuration history table" using the data of the created "issue / change notice". To provide.

[0006]

In order to achieve such an object, according to the present invention, a notice forming section having a function of producing a document issue / change notice as a document issuing unit, and a notice creating section Part issuing function that has a function to generate a trigger to create the configuration history table when printing the document issuance / change notice created by the department and part information that has the function to create information that depends on the part number Section and the trigger from the drawing approval section, extract the information necessary for creating the configuration history table from the information input by the notification creating section and the information created by the part information creating section, and optionally It is characterized by including a history table creation unit having a function of creating a configuration history table by rearranging to.

[0007]

[Operation] In the history table creation section, necessary information is extracted from the information of the document issuance / change notification created in the notification creation section and the information depending on the parts created in the parts information creation section Automatically create a configuration history table by rearranging. The configuration history table does not need to be handled as a document, and is created each time the need arises.

[0008]

The present invention will be described in detail below with reference to the drawings.
FIG. 1 is a configuration block diagram showing an embodiment of a system for realizing a document change history management device according to the present invention. The document creation device 10 includes a key input unit and a display unit (neither of which is shown), and a work including a notice creation unit 11, a drawing approval unit 12, a history table creation unit 13, and a parts information creation unit 14. It is a station. Documents (also called manufacturing standards) issued by product design departments to related departments such as manufacturing departments include the quality to be incorporated into products at the manufacturing stage, manufacturing processes, work methods and procedures, and manufacturing know-how possessed by the design departments. And technical matters to be communicated are described. In this embodiment, change history data management for such a document will be described.

The notification forming unit 11 issues a document issuance / change notification (this is the FZ2
Abbreviated) is created as follows. Common information (header portion) of the FZ2 is created by calling a menu screen as shown in FIG. 2 and inputting information in necessary items. Enter the data on the menu screen as shown in FIG.
Create a list of drawings to be output in Z2.

The drawing approval unit 12 creates a configuration history table (referred to as FA1) to the history table creating unit 13 when the FZ2 created by the notice creating unit 11 is provisionally formalized (printing for drawing). It has the function of generating a trigger. History table creation unit 13
Has a function of receiving the trigger from the drawing approval unit 12 and extracting the information necessary for creating the configuration history table from the information input by the notification creating unit 11 to generate a printed matter. The part information creation unit 14 has a function of creating information depending on the part number.

The operation of such a configuration will be described below. FIG. 4 shows a format example of the document issuance / change notice, and FIG. 5 shows a format example of the configuration history table. When necessary information is entered in the document issuance / change notice in the notice creating unit 11, and provisional formalization is carried out in the drawing approval unit 12, the history table creating unit 13 uses the part number (or product model name) as a key to perform FZ2. Also, necessary information is extracted from the information created by the component information creating unit 14, and the information is rearranged appropriately to automatically generate the configuration history table as shown in FIG.

The items of the main part in FZ2 and the entry method are shown in Table 1, and the items of the main part in FA1 and the entry method are shown in Table 2. (Blank until the next page)

[0013]

[0014]

The part information creating section 14 creates information depending on the part number. The information is, for example, the items shown in Table 3 below. (Blank until the next page)

[0016]

The format of the input information and the output information in the device of the present invention is not limited to the embodiment.
The information managed by the document creation device and depending on the revision can be rearranged and provided as information. For example, a drawing list as shown in FIG.
It is possible to create based on the information of 2.

[0018]

As described above, according to the present invention, it is possible to obtain useful information represented by a configuration history table in any format by creating a document issuance / change notice. The following effects are produced. Time for document creation can be shortened. Eliminates inconsistencies between documents. Further, since the data obtained by rearranging the data in the document can be created at any time, the configuration history table and the like are not treated as a document but are created each time, so that the following effects can be obtained. Eliminates the time required for document creation. Fewer documents to manage.

[Brief description of drawings]

FIG. 1 is a configuration block diagram showing an embodiment of a system for realizing a document change history management device according to the present invention.

FIG. 2 is a diagram showing an example of an input screen used when issuing an FZ2.

FIG. 3 is a diagram showing an example of an input screen for inputting details of FZ2.

FIG. 4 is a diagram showing an example of an output format of FZ2.

FIG. 5 is a diagram showing an example of an output format of FA1.

FIG. 6 is a diagram showing an output example of a drawing list.

[Explanation of symbols]

 10 Document Creation Device 11 Notification Form Creation Section 12 Drawing Approval Section 13 History Table Creation Section 14 Parts Information Creation Section

Claims (1)

[Claims] 1. A device for managing a document, which has a function of creating a document issuance / change notice which is a unit for issuing a document, and a document issuance / preparation document created by the notice creation unit. A drawing approval unit having a function of generating a trigger for creating a configuration history table when printing a change notice, a parts information creation unit having a function of creating information dependent on a part number, and the drawing approval unit In response to the trigger from, the information necessary for creating the configuration history table is extracted from the information input in the notification creating unit and the information created in the component information creating unit, and the configuration history table is created by arbitrarily rearranging it. A document change history management device having a history table creation unit having a function to perform.