JP2014146213A - Constituent management device and constituent management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To achieve a controlling method of a constituent of a product using a tree structure, for smooth and simultaneous progress of design of a high order constituent and design of a low order constituent, or for smoothly designing the low order constituent prior to the high order constituent.SOLUTION: A constituent management device 10 includes: a node management part 11 which manages a node which has an attribute part showing a constituent attribute for each constituent, and a link part showing a constituent which is the child of the constituent; and an access permission grant part 13 which grants an access permission to a node of the constituent for each constituent, and which independently grants the access permission to the attribute part and the link part.

Description

  The present invention relates to a technique for managing product components using a tree structure.

  The tree structure is a data structure represented by vertices and branches connecting the vertices. Except for the lowest vertex, one or more lower vertices (child vertices) are connected to the vertex by a branch. Also, except for the highest vertex, only one upper vertex (parent vertex) is connected to the vertex by a branch.

  When managing product components using a tree structure, for each component, a node is prepared in which the vertices for which the attributes of the component are set and the branches connecting the vertices and child vertices are integrated. Is done. And since the user who designs for every structure differs, an access authority is set for every structure. That is, the access authority is set for each node in which the vertex and the branch connecting the vertex and the child vertex are integrated.

  Each vertex is version controlled and a new version is created each time it is changed. The specific version of the parent vertex and the specific version of the child vertex are connected by a branch.

JP-A-9-171510 JP-A-6-35914

When revising a child vertex or adding / deleting a child vertex, it is necessary to edit a branch connecting the parent vertex and its child vertex. As described above, the branch connecting the parent vertex and the child vertex is prepared as one body with the parent vertex. Therefore, it is necessary to revise the parent vertex.
That is, there is a restriction that when a child vertex is revised or when a child vertex is added or deleted, the parent vertex needs to be revised.

When designing product components, in order to shorten the lead time of the design, when the design of the upper component and the design of the lower component proceed simultaneously, or when the design of the lower component is the upper component It may be performed prior to the design of the object.
Therefore, before the designer of the upper component starts the design change, the designer of the lower component applies the design corresponding to the change made in the next version of the upper component to the lower component. Need to be done.

However, due to the above-mentioned restrictions, (a) when editing and revising the attributes (child vertices) of lower components, the attributes of the upper components (parent vertices) are changed to the designers of the upper components It is necessary to revise regardless of the intention. (B) Since the designer of the lower component needs to have an access right to revise the attribute (parent vertex) of the upper component, the design of the upper component is not possible during the design of the lower component. If done in parallel, the designer of the lower component will see the attribute (parent vertex) of the upper component being edited.
For this reason, the design of the upper component and the design of the lower component can proceed smoothly simultaneously, and the design of the lower component cannot be performed smoothly prior to the design of the upper component. .

  According to the present invention, it is possible to smoothly advance the design of the upper component and the design of the lower component, and to smoothly design the lower component prior to the design of the upper component. Another object of the present invention is to realize a method for managing product components using a tree structure.

The component management apparatus according to the present invention is:
A component management device that manages each component of a product composed of a plurality of components having a parent-child relationship in a tree structure,
For each constituent, a node management unit that manages a node having an attribute part indicating an attribute of the constituent and a link part indicating a constituent corresponding to a child of the constituent;
An access authority granting unit that grants access authority to a node of each constituent for each constituent, the access authority granting unit separately granting access authority to the attribute part and the link part And

The node management unit is, for each constituent, a working state in which both the attribute part and the link part of the constituent node can be edited, and an active state in which the link part of the constituent node can be edited. And an editing state indicating either a fixed state in which both the attribute part and the link part of the node of the component cannot be edited,
The access authority granting unit grants access authority to the attribute part and the link part of each node according to the editing state of the node of each constituent.

The component management apparatus further includes:
For each composition, an editor indicating a user who edits both the attribute part and the link part of the node of the composition, and a user who edits the link part of the node of the composition A user management unit that manages user information indicating a constituent member,
The access authority granting unit, for each component and user, depends on the editing state of the node of the component and user information about the user for the component, and the attribute unit and the link unit of the node The access authority with respect to is granted.

The node management unit creates a new revision of the attribute part when the attribute part becomes editable, and a new revision of the link part when the link part becomes editable. Make a plate,
The access authority granting unit
When the editing state is a working state and the user information is an editor, the right to edit the latest revision of the attribute part of the node of the component and the latest revision of the link part are displayed. Give the user editable permissions,
When the editing state is a working state and the user information is a composer, the authority to refer to the revised version of the attribute part immediately before the node of the constituent, and the latest of the link part Give the user the ability to edit the revised version,
When the editing state is active and the user information is an editor or a constituent, the authority to refer to the latest revised version of the attribute part of the node of the constituent and the latest of the link part The user is given the authority to edit the revised version.

The access authority granting unit changes the editing state of the node according to the editing state of the node of the constituent and the user information about the user of the constituent for each constituent and user. It is characterized by granting rights.

The access authority granting unit
When the editing state is a working state and the user information is an editor, a state transition right that can make a transition to a confirmed state is granted,
When the editing state is an active state and the user information is an editor, a state transition right that can be changed to a working state is given,
When the editing state is a fixed state and the user information is an editor or a composer, a state transition right that can make a transition to an active state is given.

The node management unit
For each of the attribute part and the link part, a new revised version is created when it is in an editable state, and a link is provided for each component corresponding to the child and each revised part of the attribute part indicating the attribute of the constituent. Manage the link part
When the link unit has links for a plurality of revised versions of the same component, a top flag indicating a link for the latest revised version among the plurality of links of the link unit is managed.

The node management unit is characterized in that links for a plurality of revised versions of the same component included in the link unit are associated and managed in order from the link of the latest revised version to the link of the old revised version.

The component management apparatus further includes:
It is characterized by comprising a simultaneous transition unit for transitioning the edit state of all nodes whose edit state is a definite state among the nodes of the product components to the active state.

The component management apparatus further includes:
By sequentially tracing the parent node connected by the link part from the specified node, the node corresponding to the upper level of the specified node is extracted, and the child node connected by the link part is sequentially traced from the specified node. A node extracting unit for extracting a node corresponding to a lower level of the designated node is provided.

The composition management program according to the present invention is:
A component management program for managing each component of a product composed of a plurality of components having a parent-child relationship in a tree structure,
A node management process for managing a node having an attribute part indicating an attribute of the constituent for each constituent and a link part indicating a constituent corresponding to a child of the constituent;
An access authority granting process for granting access authority to a node of each constituent for each constituent, and causing the computer to execute an access authority granting process for separately granting access authority to the attribute part and the link part It is characterized by that.

  In the component management apparatus according to the present invention, since the access authority is separately given to the attribute portion (vertex) and the link portion (branch), the design of the upper component and the design of the lower component are smoothly performed simultaneously. It is possible to proceed and to smoothly design the lower constituents prior to the design of the upper constituents.

1 is a configuration diagram of a configuration management apparatus 10 according to Embodiment 1. FIG. Explanatory drawing of the management structure of the node 20 by the node management part 11. FIG. Explanatory drawing of version management of the node 20 by the node management part 11. FIG. Explanatory drawing of the state management of the node 20 which the node management part 11 manages. Explanatory drawing of the user information which the user management part 12 manages. Explanatory drawing of the access authority grant logic by the access authority grant part 13. FIG. Explanatory drawing of the access right given to a user when the edit state of the node 20 is a working state. Explanatory drawing of the access right given to a user when the edit state of the node 20 is an active state. Transition diagram of edit state. Transition diagram of edit state. Transition diagram of edit state. Explanatory drawing of the top flag 23 and the list | wrist 24. FIG. The figure which shows an example of the table in the relational database which the node management part 11 manages. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the child node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the parent node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the parent node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the parent node 20 changes. The figure which shows the change of the link part 22 of the parent node 20 when the edit state of the parent node 20 changes. The figure which shows an example of the structure which the structure management apparatus 10 manages. The figure which shows an example of the structure which the structure management apparatus 10 manages. The figure which shows an example of the hardware constitutions of the structure management apparatus 10 which concerns on the said embodiment.

Embodiment 1 FIG.
In the first embodiment, a component management apparatus 10 that manages a component of a product using a tree structure will be described.
Here, the product is a product such as a home appliance or a software product, or a facility such as a factory. In the case of home appliances and software products, the component is a part or the like constituting the product, and in the case of a facility such as a factory, the component is equipment or the like constituting the facility. In other words, the substance of products and parts is in the real world.
The component management apparatus 10 logically expresses and manages attributes and files representing the substance of products and parts, assembling methods and structures of products and parts on a computer.

  In the following description, the terms “higher-order component” and “lower-order component” are used. For example, the higher-order component is formed by assembling a plurality of lower-order components.

FIG. 1 is a configuration diagram of a configuration management apparatus 10 according to the first embodiment.
The constituent management apparatus 10 includes a node management unit 11, a user management unit 12, and an access authority giving unit 13.
The node management unit 11 manages the node 20 assigned to each product component.
The user management unit 12 manages user information indicating a user who performs editing for each component.
The access authority granting unit 13 grants access authority to the node 20 based on user information and the like managed by the user management unit 12.

FIG. 2 is an explanatory diagram of the management configuration of the node 20 by the node management unit 11.
The node management unit 11 manages the nodes 20 (each part surrounded by a broken line in FIG. 2) assigned to each constituent. Each node 20 has an attribute part 21 (each part represented by a solid square in FIG. 2) and a link part 22 (each part represented by an arrow in FIG. 2). The attribute part 21 shows the attribute of the composition to which the node 20 is assigned. The link unit 22 indicates a constituent corresponding to a child of the constituent to which the node 20 is assigned. The link unit 22 is a name that collectively refers to the arrows that are output from one attribute unit 21 in FIG. 2, and each arrow is referred to as a link. That is, the link unit 22 includes one or a plurality of links.
That is, the node management unit 11 manages information on product components in a tree structure with the attribute unit 21 as a vertex and the link unit 22 as a branch.
In FIG. 2, the product A is the highest-order component, the components A and B are the child components of the product A, the child components a1 and a2 are the child components of the component A, and the child of the component B is As components, there are child parts b1 and b2.

FIG. 3 is an explanatory diagram of version management of the node 20 by the node management unit 11. FIG. 3 shows a case where the attribute part 21 of the child component b2 shown in FIG. 2 is revised.
The node management unit 11 manages the version of each component. The node 20 is revised every time the component is changed, and a new version is generated. Since the node 20 includes the attribute part 21 and the link part 22, a new version of the node 20 means that a new version of the attribute part 21 and the link part 22 are generated.
When a certain node 20 is revised, it is necessary to connect the attribute section 21 of the new version node 20 and the attribute section 21 of the parent node 20 of the node 20 by the link section 22 of the parent node 20. Therefore, it is necessary to update the link part 22 of the parent node 20. That is, the parent node 20 also needs to be revised. If the parent node 20 also has a parent node 20, the parent node 20 also needs to be revised.
In FIG. 3, since the attribute part 21 of the child part b2 is revised to the second version, the part B corresponding to the parent of the child part b2 is also revised to the second version, and the product A corresponding to the parent of the part B is also revised to the second version. It is a version. In the second version of the component B, the first version of the child component b1 and the second version of the child component b2 are connected by the link portion 22. In the second version of the product A, the first version of the part A and the second version of the part B are connected by the link portion 22.

FIG. 4 is an explanatory diagram of the state management of the node 20 managed by the node management unit 11.
The node 20 is assigned one of three editing states, that is, a working state, an active state, and a confirmed state, for each version. In the following description, the work state may be indicated as W, the active state as A, and the confirmed state as S.
The working state is a state where both the attribute part 21 and the link part 22 of the node 20 can be edited. In the active state, only the link part 22 of the node 20 can be edited, and the attribute part 21 cannot be edited. The confirmed state is a state where both the attribute part 21 and the link part 22 of the node 20 cannot be edited.
Note that the working state and the active state are states in which only the latest version of each node 20 can be obtained, and all old versions that are not the latest are in a definite state.

FIG. 5 is an explanatory diagram of user information managed by the user management unit 12. FIG. 5 shows user information about the product shown in FIG.
The user information is assigned to each constituent, and an editor who can edit both the attribute part 21 and the link part 22 of the node 20 assigned to the constituent, and the attribute part of the node 20 assigned to the constituent. 21 is set, and a constituent who can edit the link unit 22 and a reference who can refer to both the attribute unit 21 and the link unit 22 of the node 20 assigned to the constituent are set.
When the node 20 is newly created, the user information is assigned according to an instruction from the user or the like who created the node 20. In addition, when the node 20 is newly created, the user information may be assigned a predetermined default value and may be changed later according to a user instruction.

FIG. 6 is an explanatory diagram of an access authority granting logic performed by the access authority assigning unit 13.
The access authority granting unit 13 grants an access right to each node 20 to the user based on the editing state of the node 20 managed by the node management unit 11 and the user information managed by the user management unit 12. In particular, the access authority granting unit 13 separately grants access rights to the attribute unit 21 and the link unit 22 for each node 20.
The access right granted by the access right granting unit 13 includes an edit right that can be edited and referred to, and a reference right that cannot be edited but can be referred to.

The access authority granting unit 13 grants an access right to each node 20 to the user according to the following rules.
When the editing state of the node 20 is the working state, the following access rights W1 to W3 are given according to the user information. The user who is an editor is given the editing right to the latest version attribute section 21 and the editing right to the latest version link section 22 (W1). The user who is a constituent is given a reference right to the attribute part 21 of the latest previous version and an edit right to the link part 22 of the latest version (W2). The user who is a reference is given the reference right to the attribute part 21 of the latest previous version and the reference right to the link part 22 of the latest previous version (W3).
When the editing state of the node 20 is active, the following access rights A1 to A3 are given according to user information. The user who is an editor or a constituent member has a right to refer to the latest version attribute section 21 and an edit right to the latest version link section 22 (link section 22 for the next version of the latest attribute section 21). Is given (A1, A2). For the user who is a referrer, the right to refer to the latest attribute section 21 and the right to refer to the latest previous link section 22 (the link section 22 for the latest version of the attribute section 21) Is given (A3).
When the editing state of the node 20 is the finalized state, each user is given a reference right to the latest version attribute section 21 and link section 22 (S1, S2, S3).

Further, as shown in FIG. 6, the access authority assigning unit 13 assigns a state transition right that is an authority to change the state of each node 20 based on the editing state of the node 20 and the user information.
When the editing state is the working state, the access authority giving unit 13 gives the user who is the editor the right to transition to the confirmed state. Further, when the editing state is the active state, the access authority giving unit 13 gives the user who is the editor the right to transition to the working state. Further, when the editing state is the finalized state, the right of transition to the active state is given to the user who is the editor or the constituent member.

FIG. 7 is an explanatory diagram of the access right given to the user when the editing state of the node 20 is the working state. FIG. 8 is an explanatory diagram of access rights given to the user when the editing state of the node 20 is active.
7 and 8, the hatched attribute part 21 and the link part 22 can be edited, and those without hatching can only be referred to. The part enclosed by a broken line indicates the access right given to the editor, the part enclosed by a one-dot chain line shows the access right given to the composer, and the part enclosed by a two-dot chain line gives the access right given to the reference person Indicates.

By giving the access right as described above, when the editing state of the node 20 in FIG. 7 is the working state, the attribute unit 21 of the latest version can be edited only by the editor, and others such as the composer can edit and I can't refer to it. Therefore, the contents of the latest version attribute section 21 being edited by the editor cannot be seen by others. Further, when the editing state of the node 20 is the working state, the composer can refer to the attribute unit 21 of the previous version. Therefore, even when the editor is editing the node 20, the composer can edit the child node 20 while referring to the attribute unit 21 of the previous version. The composer can edit the latest version of the link unit 22. Therefore, the composer can add or delete the child node 20 even when the editor is editing the node 20.
Further, in FIG. 8, when the editing state of the node 20 is active, the composer can edit the latest version link unit 22 (the link unit 22 for the next version of the latest version attribute unit 21). Therefore, before the editor starts editing the node 20, the child node 20 can be edited, added, or deleted.

FIG. 9 is a transition diagram of the editing state. In FIG. 9, only one node 20 (parent node 20) is shown for simplicity. In FIG. 9, the attribute part 21 and the link part 22 with hatching can be edited, and those without hatching can only be referred to.
When a new node 20 (which is referred to as a parent node 20) is created, a first version of the working state is generated. When the editing is completed, the first version is in a finalized state. Here, for simplicity of explanation, it is assumed that “when the editing is completed, the first version is in a definite state”. However, to be exact, when editing is completed, the editing state of the first version transitions to the finalized state according to the instruction of the user having the state transition right (identifier W1 in FIG. 6). Also in the following description, for the sake of simplicity of explanation, it may be omitted that the edit state transition is based on an instruction of a user who has a state transition right.
Thereafter, when editing of the child node 20 connected by the link unit 22 is started in advance, the active state is entered, and only the link unit 22 generates the second version. When editing of the parent node 20 is started, the working state is entered, and the second version of the attribute unit 21 is also generated. When the editing is completed, the second version is in a definite state.
Thereafter, when editing of the child node 20 is started again in advance, the active state is entered, and the third version is generated only for the link unit 22. When editing of the parent node 20 is started, the working state is entered, and the third version of the attribute unit 21 is also generated. When the editing is completed, the third version is in a definite state.
As described above, when the design of the child node 20 (lower component) is performed prior to the design of the parent node 20 (upper component), the final state, the active state, and the working state are repeated in order. The design is recommended. In addition, when the design of the upper structure is performed prior to the design of the lower structure, the active state is skipped and the transition is made from the confirmed state to the working state.

FIG. 10 is a transition diagram of the editing state. FIG. 10 shows two nodes 20, a parent node 20 and a child node 20. In FIG. 10, the attribute portion 21 and the link portion 22 that are hatched are editable, and those that are not hatched can only be referred to.
First, when a parent node 20 is newly created, a first version of the working parent node 20 is generated. Subsequently, when a new child node 20 is created, a working child node 20 first version is generated. When the editing of the parent node 20 and the child node 20 is completed, the first version of the parent node 20 and the child node 20 is in a finalized state.
Thereafter, when editing of the child node 20 is started in advance, the child node 20 is in a working state, and the second version is generated. At this time, the parent node 20 is activated, and the second version is generated only for the link unit 22. When editing of the parent node 20 is started, the parent node 20 is also in a working state, and the second version of the attribute unit 21 is also generated. When the editing of the parent node 20 and the child node 20 is completed, the second version is in a finalized state.

FIG. 11 is a transition diagram of the editing state. FIG. 11 shows two nodes 20, a parent node 20 and a child node 20, as in FIG. 10. In particular, FIG. 11 shows a case where the child node 20 is revised a plurality of times under one version of the parent node 20. In FIG. 11, the attribute portion 21 and the link portion 22 that are hatched are editable, and those that are not hatched can only be referred to.
It is assumed that the first version of the parent node 20 and the child node 20 is in a finalized state. Thereafter, when the editing of the child node 20 is started, the child node 20 is in a working state, and the second version is generated. At this time, the parent node 20 is activated, and the second version is generated only for the link unit 22. When the editing of the child node 20 is completed, the second version of the child node 20 is in a finalized state.
Thereafter, when the editing of the child node 20 is started again, the child node 20 is in a working state, and the third version is generated. At this time, the parent node 20 is in an active state, and the second version of the link unit 22 can be edited. When the editing of the child node 20 is completed, the third version of the child node 20 is in a finalized state.
Thereafter, when the editing of the child node 20 is started again, the child node 20 is in a working state, and the fourth version is generated. At this time, the parent node 20 is in an active state, and the second version of the link unit 22 can be edited. When editing of the parent node 20 is started, the parent node 20 is also in a working state, and the second version of the attribute unit 21 is also generated. When the editing of the parent node 20 and the child node 20 is completed, the second version of the parent node 20 and the fourth version of the child node 20 are in a definite state.

FIG. 12 is an explanatory diagram of the top flag 23 and the list 24. FIG. 12 shows the structure of the parent node 20 and the child node 20 shown in FIG.
As described based on FIG. 11, the child node 20 may be revised several times under one version of the parent node 20. In this case, as shown in FIG. 12, one version of the parent node 20 (second version in FIG. 12) is linked to a plurality of versions of the same child node 20 (second to fourth versions in FIG. 12). Will be stretched.
Among the same child nodes 20 linked from one version of the parent node 20, a top flag 23 is set in the latest version (top flag 23 = ON). As a result, the latest version of the same child node 20 linked from a version of the parent node 20 can be identified at high speed.
In addition, the same child node 20 linked from one version of the parent node 20 is associated with the list 24 in order from the new version to the old version. Thereby, for example, all the versions of the same child node 20 linked from one version of the parent node 20 can be identified at high speed. Therefore, for example, when a certain child node 20 is disconnected from the parent node 20, the link to be disconnected can be specified at high speed.

FIG. 13 is a diagram illustrating an example of a table in a relational database managed by the node management unit 11.
The node management unit 11 manages information regarding the node 20 as a table in a relational database. The node management unit 11 manages information about the node 20 using an attribute table that manages information about the attribute unit 21 and a link table that manages information about the link unit 22.

The attribute table has items such as attribute ID, version number, version status, name, specification, date / time information, charge information, access right, and the like, and the attribute ID and version number are keys.
The attribute ID is identification information of the attribute unit 21. The version number is version identification information in the attribute section 21. The version state is an editing state of the version of the attribute section 21. The name is a name given to the version of the attribute section 21. The specification is the specification of the version of the attribute section 21. The date / time information is a date such as a creation date, a revision date, or a confirmation date. The charge information is information indicating workers such as a creator, a revised person, and a finalizer. The access right is an access right of each user for the version of the attribute section 21.

The link table has items such as link ID, parent attribute ID, parent attribute version number, child attribute ID, child attribute version number, top flag, link list, active version flag, specification, number of children, access right, etc. The link ID is a key.
The link ID is identification information of the link. The parent attribute ID is the attribute ID of the parent attribute part 21. The parent attribute version number is the version number of the attribute section 21 of the parent. The child attribute ID is an attribute ID of the child attribute part 21. The child attribute version number is the version number of the child attribute portion 21. The top flag is the above-described top flag 23, which is ON in the latest version, and is OFF otherwise. The link list is the list 24 described above, and is the link ID of the previous (old) version. The active version flag is ON if the editing state of the parent attribute section 21 is active, and this link is the latest next version, and is OFF otherwise. The specification is a specification of how to assemble the version of the link. The number of children is the number of child attribute portions 21 connected to the parent attribute portion 21. Access rights are each user's access rights to that version of the link.

14 to 20 are diagrams illustrating changes in the link unit 22 of the parent node 20 when the editing state of the child node 20 changes. 14 to 20, only some items are shown for the link table.
FIG. 14 shows that when the first version of the parent node 20 (attribute ID “A”) is in the finalized state, the child node 20 (attribute ID “B”) is newly created. 20 is activated, and the second version is generated only for the link unit 22. The child node 20 generates a first version of the working state. Then, the first version attribute section 21 of the child node 20 is connected by the second version link section 22 of the parent node 20.
At this time, in the link table for the link unit 22 of the parent node 20, a record in which “1” is assigned to the link ID is generated. The record includes a parent attribute ID “A”, a parent attribute version number “first version”, a child attribute ID “B”, a child attribute version number “first version”, a top flag “ON”, and a link list “none”. ", The active version flag" ON "is set.

  Subsequently, as shown in FIG. 15, when the first version of the child node 20 is confirmed, the child node 20 is in a confirmed state. At this time, the link part 22 of the parent node 20 is not changed.

  Subsequently, as shown in FIG. 16, when the grandchild node 20 is created below the child node 20, the child node 20 becomes active and the second version link unit 22 is generated. At this time, the link part 22 of the parent node 20 is not changed.

Subsequently, as shown in FIG. 17, when the child node 20 is revised, the child node 20 enters a working state, and the second-version attribute unit 21 is generated. Then, the second version attribute section 21 of the child node 20 is connected by the second version link section 22 of the parent node 20.
At this time, in the link table for the link unit 22 of the parent node 20, the record with the link ID “1” is updated to the top flag “OFF”. In addition, a record in which “2” is assigned to the link ID is generated. In the record, parent attribute ID “A”, parent attribute version number “first version”, child attribute ID “B”, child attribute version number “second version”, top flag “ON”, link list “1” ", The active version flag" ON "is set.

  Subsequently, as shown in FIG. 18, when the second version of the child node 20 is confirmed, the child node 20 is in a confirmed state. At this time, the link part 22 of the parent node 20 is not changed.

  Subsequently, as shown in FIG. 19, when the grandchild node 20 is created below the child node 20, the child node 20 becomes active, and a third version link unit 22 is generated. At this time, the link part 22 of the parent node 20 is not changed.

Subsequently, as shown in FIG. 20, when the child node 20 is revised, the child node 20 enters a working state and a third version is generated. Then, the third version attribute section 21 of the child node 20 is connected by the second version link section 22 of the parent node 20.
At this time, in the link table for the link unit 22 of the parent node 20, the record with the link ID “2” is updated to the top flag “OFF”. In addition, a record in which “3” is assigned to the link ID is generated. The record includes a parent attribute ID “A”, a parent attribute version number “first version”, a child attribute ID “B”, a child attribute version number “third version”, a top flag “ON”, and a link list “2”. ", The active version flag" ON "is set.

21 to 24 are diagrams illustrating changes in the link unit 22 of the parent node 20 when the editing state of the parent node 20 changes. In FIG. 21 to FIG. 24, only some items are shown for the link table.
As shown in FIG. 21, the first version of the parent node 20 (assumed to be attribute ID “A”) is in a definite state, and the first version of the parent node 20 has the attribute ID “B” as the child node 20. It is assumed that the first version to the third version are connected to the first version with the attribute ID “C”.

As shown in FIG. 22, when the parent node 20 becomes active, a second version link unit 22 is generated. Then, the second version link unit 22 connects the child node 20 from the first version of the attribute ID “B” to the third version and the first version of the attribute ID “C”.
At this time, a copy (link ID “5” to “8”) of each record (link ID “1” to “4”) for the first version link unit 22 of the parent node 20 is created. Then, the activated version flag of the copied records with the link IDs “5” to “8” is set to “ON”, and the link list of the records with the link IDs “5” to “8” is also changed from the link IDs “5” to “8”. Is changed to point to the corresponding link ID in 8 ″.

  As shown in FIG. 23, when the parent node 20 is in a working state, the second version of the attribute unit 21 is generated. At this time, since the attribute part 21 of the second version of the parent node 20 is generated, the parent attribute version number of the record with the link ID “5” is changed to “second version”, and the active version flag is set to “2”. “OFF”. In FIG. 23, records with link IDs “1” to “4” are omitted.

  As shown in FIG. 24, when the parent node 20 is in a finalized state, the link part 22 of the parent node 20 is not changed.

As described above, in the component management apparatus 10 according to the first embodiment, access rights are separately assigned to the attribute unit 21 and the link unit 22 when managing product components using a tree structure. In particular, in the constituent management apparatus 10 according to the first embodiment, an access right is given to each user based on the editing state of the node 20 and user information. In addition, the component management apparatus 10 according to the first embodiment prepares only the new version link unit 22 without causing a new version of the attribute unit 21 (that is, without creating the attribute unit 21).
As a result, the design of the upper component and the design of the lower component can proceed smoothly and simultaneously, and the lower component can be designed prior to the design of the upper component. .

In the above description, when a product is configured by assembling a plurality of parts, the node is assigned to the product and each part, with the product as an upper component and each part as a lower component. However, the higher-order component may be a component designed and manufactured in a process before the lower-level component.
FIG. 25 is a diagram illustrating an example of a configuration managed by the configuration management apparatus 10.
FIG. 25 shows an example of industrial product design. In the design of industrial products, there is a manufacturing preparation process for designing a manufacturing method for parts and the like as a downstream process of a design process for designing parts and the like. In this case, a part or the like designed in the design process may be used as the parent node 20, and manufacturing method data designed in the manufacturing preparation process may be used as the child node 20.
FIG. 26 is a diagram illustrating another example of a component managed by the component management apparatus 10.
FIG. 26 shows an example of facility maintenance. In equipment maintenance, there is a maintenance inspection process for recording inspection and accident data as a downstream process of the design process for designing equipment. In this case, the equipment or the like designed in the design process may be the parent node 20, and the data recorded in the maintenance / inspection process may be the child node 20.

In addition, the composition management apparatus 10 (simultaneous transition unit) transitions all the nodes 20 that are in the finalized editing state among the nodes 20 connected to one tree structure to the active state all at once based on a user instruction. It is also possible to make it. This instruction can be given by the editor or the composer of the top node of the tree structure.
By transitioning all the nodes 20 to the active state all at once, each user can obtain an access right corresponding to the user information that the user has. The link unit 22 can be edited by the node 20 while referring to the connection relation of the entire tree structure, or the attribute unit 21 can be edited by making a transition to a working state.
Then, after the editing is completed, the configuration management apparatus 10 (simultaneous transition unit) can also transition all the nodes 20 to the confirmed state all at once based on a user instruction. This instruction can be given by the editor of the highest node in the tree structure.

In addition, when a constituent is designated by the user, the constituent management apparatus 10 (node extraction unit) traces the link unit 22 from the constituent, extracts the constituent corresponding to the upper or lower order of the constituent, and displays the constituent It can also be displayed on the device.
For example, when a product is recalled, a target component can be extracted using this function.

FIG. 27 is a diagram illustrating an example of a hardware configuration of the configuration management apparatus 10 according to the above embodiment.
As shown in FIG. 27, the configuration management apparatus 10 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program. . The CPU 911 is connected to the ROM 913, the RAM 914, the LCD 901 (Liquid Crystal Display), the keyboard 902 (K / B), the communication board 915, and the magnetic disk device 920 via the bus 912, and controls these hardware devices. Instead of the magnetic disk device 920 (fixed disk device), a storage device such as an optical disk device or a memory card read / write device may be used. The magnetic disk device 920 is connected via a predetermined fixed disk interface.

  An operating system 921 (OS), a window system 922, a program group 923, and a file group 924 are stored in the magnetic disk device 920 or the ROM 913. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 stores software, programs, and other programs that execute the functions described as “node management unit 11”, “user management unit 12”, “access authority granting unit 13”, etc. in the above description. Yes. The program is read and executed by the CPU 911.
In the file group 924, information, data, signal values, variable values, and parameters stored in the “attribute table” and “link table” in the above description are stored as items of the “database”. The “database” is stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for the operation of the CPU 911 such as calculation / processing / output / printing / display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the operation of the CPU 911 for extraction, search, reference, comparison, calculation, calculation, processing, output, printing, and display. Is remembered.

In the above description, the arrows in the flowchart mainly indicate input / output of data and signals, and the data and signal values are recorded in a memory of the RAM 914, other recording media such as an optical disk, and an IC chip. Data and signals are transmitted online by a bus 912, signal lines, cables, other transmission media, and radio waves.
In addition, what is described as “to part” in the above description may be “to circuit”, “to device”, “to device”, “to means”, and “to function”. It may be “step”, “˜procedure”, “˜processing”. In addition, what is described as “˜device” may be “˜circuit”, “˜device”, “˜means”, “˜function”, and “˜step”, “˜procedure”, “ ~ Process ". That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, only software, hardware such as elements, devices, substrates, and wirings, a combination of software and hardware, or a combination of firmware may be used. Firmware and software are stored in a recording medium such as ROM 913 as a program. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes a computer or the like to function as the “˜unit” described above. Alternatively, the computer or the like is caused to execute the procedures and methods of “to part” described above.

  DESCRIPTION OF SYMBOLS 10 Structure management apparatus, 11 Node management part, 12 User management part, 13 Access authority provision part, 20 Node, 21 Attribute part, 22 Link part, 23 Top flag, 24 Lists.

Claims (11)

A component management device that manages each component of a product composed of a plurality of components having a parent-child relationship in a tree structure,
For each constituent, a node management unit that manages a node having an attribute part indicating an attribute of the constituent and a link part indicating a constituent corresponding to a child of the constituent;
An access authority granting unit that grants access authority to a node of each constituent for each constituent, the access authority granting unit separately granting access authority to the attribute part and the link part The composition management device. The node management unit is, for each constituent, a working state in which both the attribute part and the link part of the constituent node can be edited, and an active state in which the link part of the constituent node can be edited. And an editing state indicating either a fixed state in which both the attribute part and the link part of the node of the component cannot be edited,
The access authority granting unit grants, for each constituent, an access authority to the attribute part and the link part of the node according to an editing state of the node of the constituent. The component management apparatus described in 1. The component management apparatus further includes:
For each composition, an editor indicating a user who edits both the attribute part and the link part of the node of the composition, and a user who edits the link part of the node of the composition A user management unit that manages user information indicating a constituent member,
The access authority granting unit, for each component and user, depends on the editing state of the node of the component and user information about the user for the component, and the attribute unit and the link unit of the node The component management apparatus according to claim 2, wherein an access right is given to. The node management unit creates a new revision of the attribute part when the attribute part becomes editable, and a new revision of the link part when the link part becomes editable. Make a plate,
The access authority granting unit
When the editing state is a working state and the user information is an editor, the right to edit the latest revision of the attribute part of the node of the component and the latest revision of the link part are displayed. Give the user editable permissions,
When the editing state is a working state and the user information is a composer, the authority to refer to the revised version of the attribute part immediately before the node of the constituent, and the latest of the link part Give the user the ability to edit the revised version,
When the editing state is active and the user information is an editor or a constituent, the authority to refer to the latest revised version of the attribute part of the node of the constituent and the latest of the link part The composition management apparatus according to claim 3, wherein the user is given an authority to edit the revised version. The access authority granting unit changes the editing state of the node according to the editing state of the node of the constituent and the user information about the user of the constituent for each constituent and user. 4. The component management apparatus according to claim 3, wherein a right is given. The access authority granting unit
When the editing state is a working state and the user information is an editor, a state transition right that can make a transition to a confirmed state is granted,
When the editing state is an active state and the user information is an editor, a state transition right that can be changed to a working state is given,
6. The state transition right that can make a transition to an active state is given when the editing state is a fixed state and the user information is an editor or a composer. Component management device. The node management unit
For each of the attribute part and the link part, a new revised version is created when it is in an editable state, and a link is provided for each component corresponding to the child and each revised part of the attribute part indicating the attribute of the constituent. Manage the link part
When the link part has links for a plurality of revised versions of the same component, a top flag indicating a link for the latest revised version among a plurality of links of the link part is managed. Item 7. The component management apparatus according to any one of Items 1 to 6. The node management unit manages, in order, the links of a plurality of revised versions of the same component included in the link unit in association with the links of the latest revised version to the old revised version of the link. Item 8. The component management apparatus according to Item 7. The component management apparatus further includes:
7. The system according to claim 2, further comprising: a simultaneous transition unit that transitions an editing state of all nodes whose editing state is a definite state among the nodes of the component of the product to an active state. Composition management device. The component management apparatus further includes:
By sequentially tracing the parent node connected by the link part from the specified node, the node corresponding to the upper level of the specified node is extracted, and the child node connected by the link part is sequentially traced from the specified node. The component management apparatus according to claim 1, further comprising a node extraction unit that extracts a node corresponding to a lower level of the designated node. A component management program for managing each component of a product composed of a plurality of components having a parent-child relationship in a tree structure,
A node management process for managing a node having an attribute part indicating an attribute of the constituent for each constituent and a link part indicating a constituent corresponding to a child of the constituent;
An access authority granting process for granting access authority to a node of each constituent for each constituent, and causing the computer to execute an access authority granting process for separately granting access authority to the attribute part and the link part A composition management program characterized by that.

Images