JP2007072580A - Design support system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a design support system or the like that is capable of enhancing design quality and design efficiency. <P>SOLUTION: Information about the process of element development/product development is unified by means of a product specification/technical issue database 20 or the like. Based on this unified information, a design management server 40 creates product specifications, technical issues and the like, and also obtains achievement status and manages progress. Furthermore, accumulation and reuse of technologies and information sharing are achieved. In this way, it is made possible to enhance the efficiency of product development and product quality. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a design support system and the like that can further improve design quality and design efficiency.

Conventionally, technical information related to design has been stored in paper, or digitized data has been distributed and managed in a personal computer or a plurality of databases.
For example, there is a system that collectively records the operation of each application for design support (Patent Document 1).
Japanese Patent Laid-Open No. 9-171523 (page 3, FIG. 2)

In the system as described above, in order to obtain technical information necessary for the design work of the engineer (designer), whether or not the necessary technical information is stored by accessing a large number of DBs, etc. Judgment had to be made, and the search operation took a long time.
In addition, technical information is managed in a distributed manner, and information sharing and standardization are not performed at all. Therefore, specification omissions are likely to occur at the time of design, which hinders improvement in product quality and development efficiency. It was.

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a design support system and the like that can further improve design quality and design efficiency.

In order to achieve the above object, a design support system according to a first aspect of the present invention provides:
Specification storage means for storing information related to specifications that are standardized in common across models for each product field, divided into specifications to be achieved by the entire product and specifications of components constituting the product,
Specification acquisition means for acquiring specifications according to the product field and model of the new product to be developed from the specifications stored in the specification storage means;
A specification sheet generating means for generating a specification sheet of a new product with the specification acquired by the specification acquiring means as an initial state;
A specification sheet editing means for editing the specification sheet generated by the specification sheet generating means and adding a specific specification;
It is characterized by providing.

  According to the present invention, the specification storage means is divided into specifications to be achieved by the entire product (for example, specification items) and specifications of components constituting the product, and specifications standardized in common for each product field. The information about is memorized. The specification acquisition unit acquires a specification according to the product field and model of the new product to be developed from the specifications stored in the specification storage unit. The specification sheet generation unit generates a specification sheet for a new product with the specification acquired by the specification acquisition unit as an initial state. Then, the specification sheet editing unit edits the specification sheet generated by the specification sheet generation unit and adds a unique specification. As a result, design quality and design efficiency can be further improved.

The design support system further includes verification method storage means for storing information on a verification method standardized for all models for verifying specifications,
The specification storage means stores a specification previously associated with the verification method stored in the verification method storage means,
The specification acquisition unit may acquire a specification of a new product and further acquire a verification method associated with the specification from the verification method storage unit.

  The specification sheet generation means is divided into specifications to be achieved by the entire new product and specifications of the components constituting the new product, and the specifications of the entire product and specifications of the components and / or specifications between the components. A specification sheet associated with each other may be generated.

  The design support system may further include comparison information generating means for generating comparison information in which specifications of other products similar to the new product and specifications of the new product are arranged for each item.

The design support system includes: a technical problem selecting unit that selects a technical problem to be solved from a specification sheet generated by the specification sheet generating unit or a specification included in a specification sheet edited by the specification sheet editing unit; ,
The technical problem selected by the technical problem selection means is divided into a technical problem to be achieved by the entire new product and a technical problem of the component constituting the new product. And / or an assignment sheet generating means for generating an assignment sheet that associates technical issues between components;
And a task sheet editing unit for editing the task sheet generated by the task sheet generating unit.

  The design support system includes a problem sheet generated by the problem sheet generation means, or a technical problem of the problem sheet edited by the problem sheet editing means, importance, difficulty, management level, achievement means, achievement means. You may further provide the subject expansion | deployment means expand | deployed to the detailed subject information containing at least any one of a difficulty, an effect degree, feasibility, a control factor, and an error factor.

  The design support system acquires a degree of achievement for the technical sheet of the problem sheet generated by the problem sheet generation unit or the problem sheet edited by the problem sheet editing unit, and the entire new product and / or component It may further comprise progress management means for generating information relating to progress management.

A program according to the second aspect of the present invention is
A specification storage means for storing information on specifications standardized for all models in each product field, wherein the computer is divided into specifications to be achieved by the entire product and specifications of components constituting the product;
Specification acquisition means for acquiring a specification according to the product field and model of the new product to be developed from the specifications stored in the specification storage means,
Specification sheet generating means for generating a specification sheet for a new product with the specifications acquired by the specification acquiring means as an initial state,
A specification sheet editing means for editing the specification sheet generated by the specification sheet generating means and adding a unique specification;
To function as.

  According to the present invention, design quality and design efficiency can be further improved.

Hereinafter, a design support system according to an embodiment of the present invention will be described with reference to the drawings.
A configuration example of this system is shown in FIG. The design support system 1 includes a master database 10, a product specification / technical issue database 20, a document / drawing database 30, a design management server 40, and a user terminal 50.

The master database 10 stores information on specification items of products and components constituting the products, information on verification methods of the specification items, and the like.
Specifically, the master database 10 stores a specification master for managing specification items and a verification method master for managing verification methods.

The specification master standardizes and manages the specification items. For example, for each product category (color machine / monochrome machine, etc.), the entire product and the specification items of the components are standardized and managed in common for all models. This makes it possible to prevent leakage of specification items to be verified and evaluated for each model.
On the other hand, the verification method master standardizes and manages the verification method for each specification item. In other words, it manages know-how information such as guides, tools, etc. for verification / evaluation methods / design methods used in common with products.

Details of the specification master and the verification method master will be described with reference to FIG. FIG. 2 is a schematic diagram showing an example of a master maintenance screen displayed on the user terminal 50 or a management terminal (not shown).
First, the specification master manages the entire product and the specification items of the components for each product classification, and can be revised at any time, such as addition / deletion and correction, as shown on the screen G1. In addition, it is possible to select whether to reflect the revised contents in the specification items of the entire product / component of each model, and to determine whether to reflect according to the development status of the model.
Further, the contents of the revision history remain for each specification item, and the change contents (addition, deletion, change) can be referred to. For example, in the case of an item change, as shown on the screen G2, it is possible to refer to the item name before and after the change, the updater, the update date, and the like.
Then, the entire product / component is selected, and the corresponding specification item is added / deleted / modified. For example, when “component 1” is selected on the screen G1, revisions such as addition / deletion / correction can be performed for each specification item, as shown on the screen G3. At that time, the last updater and the last update date are managed in specification item units.

On the other hand, in the verification method master, a link to the document of the verification method, classification (guide, measuring instrument name, etc.), verification method name, and document number can be registered. For example, when a specification item verification method is selected on the screen G3, as shown on the screen G4, a link, classification, verification method name, document No. Can be added / deleted / modified. Any revisions such as additions, deletions, and modifications are immediately reflected in the verification method for each model.
Further, when the link guide or the like of the verification method master is revised, the link is pasted to the latest revised document by periodic automatic update. As a result, the latest verification method is maintained.

Returning to FIG. 1, the product specification / technical issue database 20 stores specifications and technical issues related to products. That is, the specification information of the entire product and the specification information of the component are stored, and the problem information of the entire product and the problem information of the component are stored.
As an example, the specification information includes specification items, specification values (values to be achieved), current ability values, verification methods, evaluation progress (achievement levels), part numbers, related information (documents, diagrams), change history, and the like. .
The problem information is a technical problem for achieving the specification item, and is, for example, a target value. Note that specification items that are particularly difficult to achieve may be picked up as technical issues, registered, and managed.

  The document / drawing database 30 stores related information (files such as documents and drawings, applications such as browsers and groupware) related to specification items and the like. Note that files such as documents and drawings are linked or attached in accordance with specification items.

The design management server 40 includes a general-purpose computer that includes a control unit, a storage unit, a communication control unit, and the like. Then, necessary information is transmitted to the user terminal 50, and product design or the like is performed according to the instruction information transmitted from the user terminal 50.
More specifically, a control unit configured by a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like reads and executes a program stored in the storage unit, Sheet creation / management unit 41, product specification management unit 42, technical problem management unit 43, history management unit 44, progress status management unit 45, examination / approval management unit 46, development process management unit 47, and master management unit 48 Realize logically.

The sheet creation / management unit 41 creates and manages a sheet for setting specification items (specification values and verification methods for the specification items) when designing a new model (model to be developed). At this time, when the previous model (original existing model) is specified from the user terminal 50, the seat of the new model that inherits the specification items of the previous model as an initial state is referred to the seat of the previous model. Create
For example, when the model α (predecessor model) is specified and the model β (new model) is designed, the sheet creation / management unit 41, as shown in FIG. 3, the specification master SMT and the sheet STα of the model α. From this, a sheet STβ of model β is created. That is, a sheet for the entire product and a sheet for each component for the model β are created.
The sheet STβ (each sheet) is generated from the specification items of the specification master SMT and the specification items added to the model α in the sheet STα. At that time, the specification value of the sheet STα is generated by copying the specification value of the predecessor of the sheet STβ (specification value of the previous model).
If the predecessor model is not designated, the sheet STβ is generated only from the specification items of the specification master SMT.

When the design is advanced by the user and a specification item specific to the model β is added to the sheet STβ (when a specification item not managed by the specification master SMT is approved), the added specification item / The verification method is notified to the master administrator or the like.
As described above, the added specification item / verification method is appropriately examined by the master administrator or the like, and is added to the specification master / verification method master (master database 10) by the master management unit 48 described later as necessary. The Through this series of steps, the specification master / verification method master is reinforced, and more appropriate specification items / verification methods can be applied to subsequent new models.

Returning to FIG. 1, the product specification management unit 42 displays and edits product specifications. For example, depending on the product model and component name, information related to the product specifications is appropriately read from the product specification / technical issue database 20 and displayed on the user terminal 50 so that the user can edit the specification items. At that time, a new model to be designed may be compared with a similar previous model.
For example, a specification editing screen (screen G5) as shown in FIG. 4 is displayed on the user terminal 50 so that the previous model and the new model can be compared for each specification item side by side. Editing or the like may be performed.

As shown in the drawing, the product specification items are divided into hierarchies on the screen G5. In addition to the specification master items, device-specific specification items can be added, and the added device-specific specification items can be distinguished from the specification master specification items by different display colors.
More specifically, the specification values of an existing model (predecessor model) similar to the new model to be designed are arranged horizontally for each specification item as shown in screen G5 by the user specifying the model name. Displayed for comparison. At that time, the same item is displayed as “←” so that the difference from the previous model can be clearly identified. In the figure, it is represented by “←”, but it has a value internally, and can be displayed by switching to an actual value.
In addition, in the figure, the specification value (value to be achieved) and the current ability value are displayed side by side, so that it is possible to clearly determine how much ability is present against the achievement target. .
Also, the part number corresponding to (or related to) the specification item can be input / edited, etc. By specifying the part number on this screen G5, the relationship between the CAD data, the part drawing, etc. of the part is specified. It is also possible to display design information to be displayed.

Furthermore, since the related information of the specification item is linked or attached, the user can recognize the presence / absence of the related information and the number of cases on the screen G5. The attached file is stored in the document / drawing database 30.
Then, by specifying the related information on the screen G5, for example, as shown in FIG. 5, detailed information such as the classification, title, and number of each related information, documents stored in the document / drawing database 30, etc. Can be displayed.

  Further, on the screen G5 shown in FIG. 4, the presence / absence of the specification change is also managed, and the specification item with the change is indicated by a mark (◯ mark). When this mark is designated and a reference to change of specification is instructed, a change history for each specification item can be displayed based on information managed by the history management unit 44 described later.

The product specification management unit 42 also manages a verification method for evaluating the achievement level and the evaluation contents for each specification item.
Specifically, as shown in FIG. 6, the product specification management unit 42 manages a verification method and evaluation contents for each specification item.
The verification method is set based on verification method guides / standards that are known technologies, legal information to be observed, and the like. In other words, the verification method stored in the verification method master (master database 10) can be selected as appropriate. In the case of a new technique (verification method), the designer himself can input.
On the other hand, as the evaluation contents, standard evaluation types (basic evaluation, upper / lower limit evaluation, environmental evaluation, durability evaluation, etc.) can be set. Then, for each evaluation content, a plan indicating whether or not to carry out, a mark indicating the evaluation results (such as ● or ○ in the figure), which development step (step 1 or step 2 in the figure), etc., and In what units (aaaaaaaaaa, bbbbbbbbbb, etc. in the figure) are set and managed.

  Such a product specification management unit 42 distributes specifications prior to product development. In other words, when developing a new product, first, the specifications of the entire product, such as what kind of product is to be created, are defined, and the values to be achieved are allocated to each component when the development proceeds.

Specifically, the product specification management unit 42 distributes specifications as shown in FIG. 7 based on an instruction from the user terminal 50. That is, in the figure, when an attempt is made to realize a specification value of 100 for the specification item X (specification item X) in the specification information of the entire product, 50 in the specification item x1 of component 1, The value to be achieved is allocated to each component, such as 30 for the specification item x2 and 20 for the specification item x3 of the component 3.
It is also possible to have a relationship between the component specifications. For example, when the value (output) of the specification item y1 of the component 1 is the input value of the specification item y2 of the component 2, the association is performed between y1 and y2, as illustrated.
In this way, the relationship between specifications is clarified by distributing and associating specifications. In addition, the specification information of the allocation source / destination and association source / destination can be displayed immediately, so that the scope of influence and the progress status can be quickly grasped when the specification value is determined (or changed). And it can be performed without leakage.

In addition to this, the product specification management unit 42 can compare the specification values of the products side by side.
Specifically, the product specification management unit 42 compares the specification values by arranging the models side by side as shown in FIG. 8A based on an instruction from the user terminal 50. In other words, in FIG. 8 (a), the product field and component narrowing conditions can be set, and the comparison target model is selected from the models that meet the set conditions, and the model that is the basis for comparison Can be specified. The set comparison conditions can be saved individually, and the comparison conditions saved when calling for comparison can be called and compared based on the latest specification information.
For example, when the machine B and the machine C are selected as the models to be compared and the machine A is specified as the model to be compared, a side-by-side comparison execution is instructed, as shown in FIG. Thus, the comparison execution result is displayed.
More specifically, as shown in FIG. 8B, the specification master stored in the master database 10 and the product specifications (the specification information of the entire product and the specification information of the components) of the product specification / technical issue database 20 ) To generate a comparison execution result in which the specification values of each product are arranged side by side.
With such a specification side-by-side comparison function performed by the product specification management unit 42, other similar product specifications can be acquired as the latest information at that time, and the validity of the specifications can be confirmed each time.

Returning to FIG. 1, the technical problem management unit 43 manages the problem of the entire product (technical problem) and the problem of each component.
The problem to be managed (technical problem) is a technical problem for achieving the specification item, and is, for example, a target value. Note that specification items that are particularly difficult to achieve may be picked up as technical issues, registered, and managed.
And the technical problem management part 43 manages a technical problem (problem item) in association with a specification item, as shown in FIG.

  Such a technical problem management unit 43 distributes problems prior to management of technical problems. That is, when solving the problem of the model, the problem of the entire product is first defined, but this is also a problem that spans each component. Therefore, issues to be achieved are allocated to each component. Note that the way of distributing the target values differs depending on the characteristics of each task item.

Specifically, the technical problem management unit 43 develops (distributes) problems as shown in FIG. 10 based on an instruction from the user terminal 50. That is, in the figure, when trying to realize a target value of 100 for the task item X (task item X) in the task information of the entire product, the task x1 of the component 1 is 50, and the task of the component 2 The target value is developed for each component, such as 30 for x2, 20 for the task x3 of component 3, and so on.
And it enables it to link with the subject of the whole product also from the subject side of a component. By this development (distribution) and association, the relationship and structure of the issues are clarified, and the range of influence of the issues and the issues that should be reflected as the implementation results can be determined.

The technical problem management unit 43 develops a problem. In other words, the issues distributed from the entire product and the issues specific to the components are further hierarchized, and the structure of the issues to be implemented and the goal achievement level of each issue are clearly defined.
Specifically, the technical problem management unit 43 stratifies the problems based on an instruction from the user terminal 50 as shown in the problem screen (such as the problem screen K1) in FIG. Set. When there are a plurality of achievement means, a plurality are set.
First, when the assignment screen K1 is displayed on the user terminal 50, the user sets a management level for each assignment. This management level is set based on the relationship between importance and difficulty (for example, importance × difficulty).
Further, the user sets the difficulty level for each achievement means. This difficulty level is set based on the relationship between the degree of effect and the feasibility (for example, the degree of effect × feasibility). If there are multiple achievement means depending on the problem, the difficulty level of the achievement means is set taking into consideration the difficulty of each achievement means, the contribution ratio of each achievement means to the problem, and whether the achievement means are promising achievement means. .
The user sets a control factor and an error factor for each achievement means. In other words, by clarifying the factors at the planning stage, it becomes possible to easily cope with the problem based on the output image obtained as an evaluation result.

Next, as shown in the specification / characteristic item screen K2, a problem that is preliminarily expanded from the specification item and associated can be reflected in the specification value column by a control factor (characteristic value) obtained as a result of the execution of the problem. It has become. As a result, it is possible to determine in which specification the implementation result of the task is reflected.
In addition, in the related information item on the assignment screen K1, the presence / absence of the link / attachment information and the number of cases that are the basis for achievement of the assignment are set. When the related information is designated, detailed information including a document name, a document number, a classification, and the like is displayed as shown in a detailed screen K3. Further, when detailed information in the detail screen K3 is designated, a related information screen K4 is displayed.

Returning to FIG. 1, the history management unit 44 manages the change history of the specification information and the like.
Specifically, the history management unit 44 manages the change history for each change item, as shown in FIG.
As shown in the figure, when each value of the specification information is changed, date and time, development step, value before change, value after change, reason for change, etc. are recorded in the change history. From such a change history, the transition of the specification information can be determined.
In addition, if there is a specification item that is distributed or associated with the changed specification item, the details are automatically notified to the person in charge in charge of the design of the component of the other party (influence range). You may be made to do. In this case, according to the specification change, the change contents are automatically notified to the affected range, and the person in charge of each component can respond to the original specification change without omission, mistakes, rework, etc. Is prevented.

Returning to FIG. 1, the progress management unit 45 manages the progress in product design. For example, the task achievement status, specification evaluation status, overall product schedule, and individual schedule are managed.
Specifically, the progress status management unit 45 displays progress information as shown in FIG. 13 based on an instruction from the user terminal 50. As shown in the figure, the achievement status of the technical problem is displayed in the achievement graph of the problem. Also, the evaluation progress is displayed in a graph.
The progress information is associated with information on higher specifications such as product planning, product concept, and design concept in determining the specifications of the entire product / components. For example, if it is specified by the related information in the figure, the higher specification can be referred to.

In addition to such progress information, more detailed evaluation progress can be referred to.
For example, detailed evaluation progress as shown in FIG. 14 can be referred to. This evaluation progress is aggregated as comprehensive information for each development step, and the preliminary performance management is possible. In addition, the technical issues of the model (the entire product and the constituent elements) are associated and displayed in a hierarchical manner.
The task achievement status can be easily grasped by classification for each management level.

  Returning to FIG. 1, the examination / approval management unit 46 manages the history of examination / approval. For example, when an examination / approval processing request is issued from the user terminal 50, the examination / approval management unit 46 generates and manages history information including information such as the contents of examination / approval, examination results, and approval results. To do.

The development process management unit 47 manages process information (time point information) for each development step or each approval.
Specifically, when a component and a time point are selected based on an instruction from the user terminal 50, the development process management unit 47 displays development process data at that time point, as shown in FIG.

Returning to FIG. 1, the master management unit 48 manages the specification master and the verification method master of the master database 10 in accordance with an instruction from the master administrator or the like.
For example, when the design is advanced by the user and the specification item specific to the device is added to the above-mentioned sheet or the like, the master administrator or the like examines the content, and if necessary, sends the specification item to the master management unit 48. Etc. are instructed. Then, the master management unit 48 adds specification items and the like to the specification master / verification method master (master database 10).

The user terminal 50 includes a computer terminal or the like used by a user (designer or the like) who performs design. The user terminal 50 is connected to the design management server 40 via a network (not shown).
The user terminal 50 accesses the design management server 40 in accordance with a user operation instruction, and instructs the above-described sheet creation, specification distribution, specification side-by-side comparison, problem development, history display, progress display, development process display, and the like. .

  Hereinafter, the design support operation of the above configuration will be described with reference to FIG. FIG. 16 is a flowchart illustrating an example of design support processing executed by the design management server 40. This design support process is started in response to an access from the user terminal 50, for example.

  First, the design management server 40 creates a new model sheet (step S11). That is, the design management server 40 creates a new model sheet based on the master database 10 (specification master) or the like. When the previous model is designated, the sheet of the previous model is referred to, and a new model sheet that inherits the specification items of the previous model is created as an initial state. For example, as shown in FIG. 3 described above, a new model sheet is created.

  The design management server 40 determines whether or not distribution of specification items has been instructed (step S12). If the design management server 40 determines that the distribution of the specification items is not instructed, the design management server 40 advances the processing to step S14 described later.

  On the other hand, when it is determined that the distribution of the specification items is instructed, the design management server 40 distributes the specification items (specification values, etc.) of the entire product to the specification items of the constituent elements (step S13). For example, the specification items are distributed as shown in FIG.

  The design management server 40 determines whether or not a side-by-side comparison of specification items has been instructed (step S14). If the design management server 40 determines that the side-by-side comparison of the specification items is not instructed, the design management server 40 advances the processing to step S16 described later.

  On the other hand, when it is determined that the side-by-side comparison of the specification items is instructed, the design management server 40 generates comparison information (specification editing screen) in which the specified previous model and the new model are arranged for each specification item ( Step S15). For example, the specification editing screen as shown in FIG. 4 described above is generated.

  The design management server 40 determines whether or not assignment of assignment items has been instructed (step S16). If the design management server 40 determines that the assignment of assignment items has not been instructed, the process proceeds to step S18 described later.

  On the other hand, when it is determined that assignment of assignment items has been instructed, the design management server 40 distributes assignment items (target values, etc.) of the entire product to assignment items of the constituent elements (step S17). For example, task items are distributed as shown in FIG.

  The design management server 40 determines whether or not an expansion of the task item has been instructed (step S18). If the design management server 40 determines that the assignment of the task item has not been instructed, the design management server 40 advances the processing to step S20 described later.

  On the other hand, when it is determined that the expansion of the task item has been instructed, the design management server 40 assigns the importance, difficulty, management level, achievement means, achievement means difficulty, effectiveness, effectiveness, control factor to the problem item. And error factors and the like are set (step S19). For example, the task items are expanded as shown in FIG.

  The design management server 40 determines whether the specification item or the like has been changed (step S20). When the design management server 40 determines that the specification item or the like has not been changed, the design management server 40 advances the processing to step S22 described later.

  On the other hand, when it is determined that the specification item or the like has been changed, the design management server 40 updates the sheet according to the change, and adds the change content or the like to the update history (step S21). In addition, if there is a specification item that has been allocated or associated with the changed specification item, the details are automatically sent to the person in charge who is responsible for the design of the components of the other party (influence range). May be notified.

The design management server 40 determines whether the specification or the like has been confirmed (step S22). If the design management server 40 determines that the specification or the like is not finalized, it returns the process to step S12 described above.
On the other hand, when it is determined that the specification or the like has been confirmed, the design management server 40 ends the design support process.

  As described above, according to the present invention, since specification items are standardized and managed, it is possible to prevent leakage of specification items to be verified and evaluated in each model. In addition, it is possible to clearly distinguish the differences from the previous model by comparing the specification items side by side.

The system of the present invention can be realized using a normal computer system, not a dedicated system. For example, a program for executing the above operation is stored in a computer-readable recording medium (FD, CD-ROM, DVD, etc.) and distributed, and the program is installed in the computer to execute the above processing. A design support system or the like may be configured. Alternatively, it may be stored in a disk device of a server device on a network such as the Internet and downloaded to a computer, for example.
In addition, when the OS realizes the above functions by sharing the OS or jointly with the OS and the application, etc., only the part other than the OS may be stored and distributed in the medium, or may be downloaded to the computer. Good.

It is a block diagram which illustrates the composition of the design support management system concerning the embodiment of the present invention. It is a schematic diagram which shows an example of a master maintenance screen. It is a schematic diagram for demonstrating preparation of a sheet | seat. It is a schematic diagram which shows an example of a specification edit screen. It is a schematic diagram which shows an example of detailed information. It is a schematic diagram for demonstrating the verification method managed for every specification item, and evaluation content. It is a schematic diagram for demonstrating distribution of a specification. (A), (b) is a schematic diagram for demonstrating comparison of a specification value. It is a schematic diagram for demonstrating correlation with a specification item and a task item. It is a schematic diagram for demonstrating distribution of a subject. It is a schematic diagram for demonstrating expansion | deployment of a subject. It is a schematic diagram which shows an example of a change log | history. It is a schematic diagram which shows an example of progress information. It is a schematic diagram which shows an example of evaluation progress. It is a schematic diagram for demonstrating the outline until it displays a development process. It is a flowchart for demonstrating the design assistance process which concerns on embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Design support system 10 Master database 20 Product specification and technical problem database 30 Document and drawing database 40 Design management server 41 Sheet creation and management part 42 Product specification management part 43 Technical problem management part 44 History management part 45 Progress management part 46 Examination・ Approval Management Department 47 Development Process Management Department 48 Master Management Department 50 User Terminal

Claims (8)

Specification storage means for storing information related to specifications that are standardized in common across models for each product field, divided into specifications to be achieved by the entire product and specifications of components constituting the product,
Specification acquisition means for acquiring specifications according to the product field and model of the new product to be developed from the specifications stored in the specification storage means;
A specification sheet generating means for generating a specification sheet of a new product with the specification acquired by the specification acquiring means as an initial state;
A specification sheet editing means for editing the specification sheet generated by the specification sheet generating means and adding a specific specification;
A design support system comprising: A verification method storage means for storing information on a verification method standardized for all models for verifying specifications;
The specification storage means stores a specification previously associated with the verification method stored in the verification method storage means,
The specification acquisition unit acquires a specification of a new product, and further acquires a verification method associated with the specification from the verification method storage unit.
The design support system according to claim 1, wherein: The specification sheet generation means is divided into specifications to be achieved by the entire new product and specifications of the components constituting the new product, and the specifications of the entire product and specifications of the components and / or specifications between the components. Generate specification sheets that are associated with each other,
The design support system according to claim 1, wherein the system is a design support system. A comparison information generating means for generating comparison information in which specifications of other products similar to the new product and specifications of the new product are arranged for each item;
The design support system according to claim 1, wherein the system is a design support system. A technical problem selecting means for selecting a technical problem to be solved from a specification sheet generated by the specification sheet generating means or a specification included in the specification sheet edited by the specification sheet editing means;
The technical problem selected by the technical problem selection means is divided into a technical problem to be achieved by the entire new product and a technical problem of the component constituting the new product. And / or an assignment sheet generating means for generating an assignment sheet that associates technical issues between components;
An assignment sheet editing means for editing the assignment sheet generated by the assignment sheet generation means,
The design support system according to claim 1, wherein the system is a design support system. The assignment sheet generated by the assignment sheet generation means, or the technical assignment of the assignment sheet edited by the assignment sheet editing means, importance, difficulty, management level, achievement means, achievement means difficulty, effectiveness, A problem expansion means for expanding into problem detailed information including at least one of feasibility, control factor, and error factor is further provided.
The design support system according to claim 5, wherein: Acquire the achievement level of the technical sheet of the problem sheet generated by the problem sheet generation means or the problem sheet edited by the problem sheet editing means, and generate information on the progress management of the entire new product and / or component And a progress management means for
The design support system according to claim 5 or 6, wherein Computer
Specification storage means for storing information on specifications that are standardized in common across models for each product field, divided into specifications to be achieved by the entire product and specifications of components constituting the product,
Specification acquisition means for acquiring a specification according to the product field and model of the new product to be developed from the specifications stored in the specification storage means,
Specification sheet generating means for generating a specification sheet for a new product with the specifications acquired by the specification acquiring means as an initial state,
A specification sheet editing means for editing the specification sheet generated by the specification sheet generating means and adding a unique specification;
Program to function as.

Images