CN112508500A - Product development process data integration management method considering multiple technical states - Google Patents
Product development process data integration management method considering multiple technical states Download PDFInfo
- Publication number
- CN112508500A CN112508500A CN202011167163.0A CN202011167163A CN112508500A CN 112508500 A CN112508500 A CN 112508500A CN 202011167163 A CN202011167163 A CN 202011167163A CN 112508500 A CN112508500 A CN 112508500A
- Authority
- CN
- China
- Prior art keywords
- design
- batch
- ebom
- pbom
- baseline
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 238
- 230000008569 process Effects 0.000 title claims abstract description 227
- 238000007726 management method Methods 0.000 title claims abstract description 67
- 238000012356 Product development Methods 0.000 title claims abstract description 17
- 230000010354 integration Effects 0.000 title claims abstract description 17
- 238000013461 design Methods 0.000 claims abstract description 148
- 238000005516 engineering process Methods 0.000 claims abstract description 22
- 238000011161 development Methods 0.000 claims abstract description 12
- 238000013070 change management Methods 0.000 claims abstract description 5
- 238000013500 data storage Methods 0.000 claims abstract description 5
- 238000004519 manufacturing process Methods 0.000 claims description 30
- 230000008859 change Effects 0.000 claims description 24
- 238000010276 construction Methods 0.000 claims description 19
- 238000005266 casting Methods 0.000 claims description 13
- 238000005457 optimization Methods 0.000 claims description 6
- 238000010923 batch production Methods 0.000 claims description 5
- 238000012938 design process Methods 0.000 claims description 5
- 230000008676 import Effects 0.000 claims description 4
- 238000012550 audit Methods 0.000 claims description 3
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 238000005242 forging Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 3
- 238000011084 recovery Methods 0.000 claims description 2
- 238000012986 modification Methods 0.000 claims 1
- 230000004048 modification Effects 0.000 claims 1
- 230000006872 improvement Effects 0.000 abstract description 2
- 230000001737 promoting effect Effects 0.000 abstract description 2
- 239000000047 product Substances 0.000 description 18
- 238000013523 data management Methods 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000007711 solidification Methods 0.000 description 1
- 230000008023 solidification Effects 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Manufacturing & Machinery (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a product development process data integration management method considering multiple technical states, which is characterized by comprising the following steps of: s1, managing and optimizing the design technology state; s2, managing and optimizing the technical state of the process; s3, optimizing the technical state management of the batch; s4, tool design management, including tool design, tool design data storage, tool EBOM management, tool design document management and tool design change management; and S5, managing model technical file codes. The invention has the advantages of improving the technical state management capacity of design, process and batch and promoting the improvement of model development efficiency.
Description
Technical Field
The invention relates to the technical field of data integration management, in particular to a product development process data integration management method considering multiple technical states.
Background
By 2019, the factory experiences seven-stage projects, the PDM system is built and transformed, the product data technical state management capability and the collaborative development capability of the factory are deepened continuously, and the aim of improving the service efficiency is always achieved. At present, the PDM system has the capabilities of basic management capability of product data, design data management capability, process data management capability, development stage, production system integration and the like. Meanwhile, the PDM of our factory is used as an important component of a Federal PDM system of the second institute, so that task cooperation and design process cooperation of the same design unit can be realized, and the technical state management capability of the second institute is supported. With the continuous deepening of business, the following problems are found in the actual business process of our factory:
1) design inputs given by design units are scattered and not standardized. Only a few parts of the data given by the design unit are in the form of EBOM, and all the data is given. Usually, only paper design files or electronic three-dimensional models and design files are sent with design data scattered and changed, so that the state of the design technology is difficult to trace under the condition of multiple states and multiple batches.
2) There are problems with process technology state management. Under the condition of lacking the EBOM, the technological process of our factory is difficult to control, the related process files are organized according to workshops instead of PBOM forms, the process is troublesome, and the states of different batches are difficult to control in the batch production process.
Disclosure of Invention
The invention aims to provide a product development process data integration management method considering multiple technical states, which has the advantages of improving the technical state management capacity of design, process and batch and promoting the improvement of model development efficiency, and solves the problems that 1) the design input given by a design unit is scattered and not standard. Only a few parts of the data given by the design unit are in the form of EBOM, and all the data is given. Usually, only paper design files or electronic three-dimensional models and design files are sent with design data scattered and changed, so that the state of the design technology is difficult to trace under the condition of multiple states and multiple batches. 2) There are problems with process technology state management. Under the condition of lacking the EBOM, the process of our factory is difficult to control, the related process files are organized according to workshops instead of PBOM, and besides troubles are brought to the process, the states of different batches are difficult to control in the batch production process.
In order to achieve the purpose, the invention provides the following technical scheme:
a product development process data integration management method considering multiple technical states is characterized by comprising the following steps:
s1, design technology state management optimization, including EBOM construction, EBOM audit, design base library management, design technology state baseline and EBOM construction business scene;
s2, optimizing process technology state management, including process technology state management, PBOM construction and batch baseline determination, secondary process task division, PBOM reconstruction, process documentation, process file approval and batch baseline investment, PBOM approval and process change and closed-loop identification;
s3, batch technical state management optimization, wherein each production is driven by a production approval process, a craft searches parts needing to be produced, then the PBOM structure of the parts is displayed based on a batch base line, then the production is started, the system automatically puts the PBOM of the current parts and a process procedure file associated with each part into a production sheet (the batch information of the production sheet is taken from the base line selected by the current part), and after approval, the PDM system sends the PBOM and a process route (structured data, node information of a lower-level casting blank is added to the casting) to the ERP by using an integrated interface of the ERP, wherein the file only provides a link and does not provide an entity file;
s4, tool design management, including tool design, tool design data storage, tool EBOM management, tool design document management and tool design change management;
and S5, managing the model technical file code number, including a system management module, a code application module and code use.
Preferably, the EBOM construction comprises a manual EBOM construction mode, an Excel import EBOM generation mode and a Creo integration EBOM generation mode.
Preferably, the system management module includes managing coding categories, managing coding rules, modifying coding rules, disabling coding rules, and browsing coding rules.
Preferably, the code application module comprises code application, view code, approval code, invalidation code and recovery code.
Preferably, in S1, a plurality of states of the external unit product may exist at a certain development stage in the design process, and need to be managed, such as a sample projectile and a formal projectile, or a plurality of batches, the design data versions of each state are different, and data that need to realize different states can be identified and traceable, after a craftsman receives or constructs the design data, the craftsman manually puts the design data into the state baseline of the corresponding state design technology, and defines an identifier for each state, such as identification uniformly by batch, such as P01, P02, and the like, and the numbering rule of the design baseline is defined as: the method comprises the steps of SJJX + model number + development phase identification + state identification, wherein a design baseline is designated for selected data when a task is initiated each time, the state of a craft worker is defaulted to be approved after the baseline is created, the EBOM state is automatically put into the baseline after being approved, and after the EBOM is updated, the baseline content is automatically updated through flow driving, namely the baseline of the design technology state.
Preferably, in the operation menu of the detailed information interface of the top node of the EBOM in S2, the first-level process responsible person may convert the EBOM into a process PBOM view by using the "convert to process BOM" operation, and after the conversion is completed, process attribute information, such as identifying a casting and forging, is added, the first-level process responsible person puts the PBOM into a batch baseline, and determines the basis for developing process design work, the first-level process responsible person compiles a route list and associates the route list with the top node of the PBOM, and the route list needs to identify the batch information, and after approval, the route list is automatically put into the batch baseline together with the associated top node.
Preferably, in S2, according to the division of the secondary process tasks, it is determined which parts are responsible for maintenance of each department, and a process worker determines whether to reconfigure the PBOM according to the process design requirements, such as adding virtual parts, splitting parts, merging parts, etc., in the same manner as the manual construction manner of the EBOM, and then determines whether to update the process attributes of a single node of the PBOM, such as whether to buy or outsource, or to update the process attributes in batch in an excel table based on the existing export BOM, and then imports the update BOM.
Preferably, after the process file is approved in S2, the system puts the process file and its associated Part into the batch baseline according to the batch information identified by the approved process file, and when the batch baseline does not exist, the system upgrade must create the baseline first.
Preferably, in the process of designing the process in S2, a work order object is added to record which data are sent to the ERP each time, a product is traced back to complete work in several times, no matter in the development stage or in the batch production stage, each work is driven by a work approval process, a craftsman finds a part to be worked on, then displays the PBOM structure of the part based on a batch baseline, then starts work, and the system automatically puts the PBOM of the current part and a process procedure file associated with each part into the work order (the work order batch information is taken from the baseline selected by the current part), and after approval, the PDM system sends the PBOM and the process route (structured data, node information of a next-level casting blank is added to the casting) to the ERP by using an integrated interface of the ERP, wherein the file only provides a link and does not provide an entity file.
Compared with the prior art, the invention has the beneficial effects that: the product technical state management stage generates and issues an EBOM and a PBOM, and data preparation is made for commissioning; the commissioning phase sends the lot PBOM to ERP based on the lot baseline, updates the baseline if a change occurs affecting production and resends to ERP.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that the terms "upper", "lower", "inner", "outer", "front", "rear", "both ends", "one end", "the other end", and the like indicate orientations or positional relationships only for convenience in describing the present invention and simplifying the description, but do not indicate or imply that the referred device or element must have a specific orientation, be constructed in a specific orientation, and be operated, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it is to be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "disposed," "connected," and the like are to be construed broadly, such as "connected," which may be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
The invention provides a technical scheme of a product development process data integration management method considering multiple technical states
A product development process data integration management method considering multiple technical states is characterized by comprising the following steps:
s1, design technology state management optimization, including EBOM construction, EBOM audit, design base library management, design technology state baseline and EBOM construction business scene;
and (3) building an EBOM: when a first-level process worker needs to construct a PBOM according to the production requirement and compile a process file, whether the needed EBOM exists in the PDM system needs to be checked, and if the needed EBOM does not exist, how to construct the EBOM needs to be determined according to the condition of design input; after the EBOM is built, the EBOM is put into a design baseline by a first-level process staff, if the design input is changed, the EBOM and the design baseline need to be updated, when the design input is imported into a PDM system through an integration mode, the EBOM is directly updated through the integration mode, when the design input is still transmitted through mails, optical disks and paper files, the EBOM is manually updated by the first-level process staff, the updating mode adopts manual construction, excel table import or Creo integration according to specific data conditions, and when the design baseline is determined, batch baselines are constructed for PBOM and process file state solidification. After PBOM is created, a process file is compiled based on PBOM and a specified batch baseline is entered. After the EBOM is updated, updating the PBOM and the batch baseline as required;
and E, EBOM auditing: establishing an approval process according to 1714B standard for in-plant self-researched products, performing a simple approval process for a manually-built EBOM (electronic book management) of an external unit design product, wherein in a planning link, a process worker needs to specify a design technical state baseline number to be put in by the EBOM, after the approval process, the manually-built EBOM is changed into an approved state which can be used for PBOM reconstruction, and the EBOM is automatically put into the specified design technical state baseline;
designing basic library management: because the standard parts or components used by the design unit are only the internal basic resources of the design unit, but not the unified basic resources of the whole institute, when the EBOM of a product to be produced by the design unit is manually built, if the EBOM lacks design basic resource data, a design basic library of the design unit needs to be built, the design basic resource data is manually maintained and signed along with the simple process, and after subsequent design data is distributed, the PDM is automatically updated after receiving the design basic resource data, so that the design basic resource data of the design unit are ensured to be consistent;
designing a technical state baseline: in a certain development stage of a design process of an external unit product, a plurality of states may exist, which need to be managed, such as a sample projectile and a formal projectile, or a plurality of batches, the design data version of each state is different, and data which need to realize different states can be identified and traced, after a craftsman receives or constructs the design data, the design data is manually input into a state baseline of a corresponding state design technology, an identifier is defined for each state, for example, the identifiers are identified uniformly according to batches, such as P01, P02 and the like, and the numbering rule of the design baseline is defined as: SJJX + model number + development phase identifier + state identifier, assigning a design baseline for the selected data when initiating a task each time, defaulting the state of a craft worker to be approved after creating the baseline, automatically putting the EBOM into the baseline after the EBOM state is approved, and automatically updating the baseline content through flow driving after the EBOM is updated;
the EBOM builds a service scene: and describing a service scene: and when the design station does not send the EBOM across the system during process design, the EBOM is automatically constructed, and the EBOM is automatically updated after the design station formally sends the EBOM. When the system receives the EBOM transmitted by the design, the generated process data is not influenced.
S2, optimizing process technology state management, including process technology state management, PBOM construction and batch baseline determination, secondary process task division, PBOM reconstruction, process documentation, process file approval and batch baseline investment, PBOM approval and process change and closed-loop identification;
managing the technical state of the process: the first-level process responsible person changes PBOM based on the issued EBOM; the method comprises the steps that a primary process responsible person puts PBOM into a batch baseline, the primary process responsible person compiles a route table and uploads the route table to a PDM system and associates the PBOM, a primary process complex person compiles a secondary process task division list based on the PBOM, the secondary process task division list determines process files needed to be compiled by each Part, division is performed according to the secondary process, a process person determines whether to reconstruct the PBOM according to needs and comprises adding virtual parts, splitting parts, combining parts and the like, the virtual parts are similar to folders and comprise primary files, main materials and auxiliary materials, a lower node is acquiescent after the virtual parts are created, a model master technologist has authority of adding, modifying and deleting, the process person compiles various process files and associates the process files to the PBOM, the process files identify batch information, the process files need to be compiled by the aid of batch cards and are associated with the borrowed process files, the process person submits the process files to examine and approve the process files, and the system associates the process files with the Part associated with the process Putting in a batch baseline, and updating the process baseline again after a process worker changes the PBOM and the process file, wherein the process change source can be a design or a process;
PBOM construction and batch baseline determination: in an operation menu of a detailed information interface of a top node of the EBOM, a first-level process responsible person can convert the EBOM into a process PBOM view by using the operation of converting into the process BOM, after the conversion is finished, process attribute information such as identifying a casting and forging part is added, the first-level process responsible person puts the PBOM into a batch baseline and determines the basis for developing process design work, the first-level process responsible person compiles a route table and associates the route table with the PBOM top node, the route table needs to identify batch information, and the route table and the associated top node are automatically put into the batch baseline after approval;
the secondary process task is divided into work: the second-level process task list is managed in a structured mode, information such as task names, task contents, task sources, construction units, completion dates, production quantities, drawing quantities and the like is filled in on line when the second-level process task list is created, a reference relation is established between the process task list and related process files and stored under a process task list folder of a product library, the process task list also identifies batch information but is not related to product structures, the second-level process task list is based on electronic issuing in the future, the second-level process task list file is still reserved within a certain time period issued by an electronic process, so that the second-level process task list file (xls format) is automatically generated by a system during the approval of the second-level process task list, the second-level process task list is submitted to the approval independently, wherein the second-level process task list is subjected to the approval by a specific person and the process group length is designated when the second-level process task is not, the group leader transfers the task, designated personnel need to confirm after receiving the second-level work allocation task, and can inquire and count whether to receive the task, and the approved second-level process task list is put into the batch base line;
PBOM reconstruction: according to the division of the secondary process tasks, which parts are taken by each department for maintenance is determined, a process worker determines whether to reconstruct PBOM according to the process design requirements, such as adding virtual parts, splitting parts, combining parts and the like, the operation mode is the same as the EBOM manual construction mode, then, whether to update the process attribute of a single node of the PBOM is determined according to the requirement, such as whether to purchase or outsource, or update the process attribute in batch in an Excel form based on the existing export BOM, then, the update BOM is imported, when the quantity of the parts needing to be maintained on the PBOM is very large, the Part attribute can be maintained in batch based on Excel, the PBOM in an Excel format is generally exported based on the PBOM, then, the Excel file is edited to supplement the process attribute information, and finally, the Excel file is imported to update the PBOM, and the operation mode is the same as that of the EB;
and (3) process documentation: the process personnel divides the labor according to the secondary process task, uses a CAPP tool to compile files such as process procedures and the like, the process files identify batch information, and the compiling result is associated to the Part corresponding to the PBOM through the CAPP integrated function;
process file approval and batch investment baseline: the process files are individually approved, the process links are executed according to the current system setting, only the process files and the rules related to the Part input batch baselines are added to the project in the period, after the process files are approved, the system inputs the process files and the related parts into the batch baselines according to the batch information marked by the approved process files, and when the batch baselines do not exist, the system is promoted and the baselines are established firstly;
PBOM approval: the PBOM is submitted and approved once after the integrity and the maturity (the process files required by batch production are published) are confirmed by a first-level process responsible person, and other process persons are only responsible for submitting the process files and are not required to submit the PBOM for approval;
process change and closed-loop identification: according to different sources of process changes, the revision modes of the process view Part are different, if only the process proposed by the process itself is changed (irrelevant to design), the process view Part and the relevant process files are directly revised, if the process change caused by the design change exists, the process view Part needs to be reconstructed based on the new version of the design view Part, the function is called as 'reconstructed PBOM', after the 'reconstructed PBOM' operation is executed, the process view is converted based on the new version of the design view Part (including newly added sub-pieces), meanwhile, the process files related to the process view Part already exist are hung on the new version of the process view Part, AA3.003.1234 is changed in design, after the PBOM is reconstructed, the AA3.003.1234 process view automatically displays the increasing and decreasing results when the design change occurs, meanwhile, the process files related to the AA3.003.1234 process view B.3 version are automatically related to C.1, and the process personnel execute the revision operation of the process files according to needs, in the PBOM reconstruction process, when the process file of the previous edition needs to be hung on the PART of the new edition, the process is confirmed, namely the PBOM simple approval process is initiated to confirm the reconstruction result after reconstruction; the method comprises the following steps that a plurality of process files are possibly unavailable any more during process change, at this time, a function of 'invalidation' of the process files is required, the process files are automatically removed from all batch baselines after invalidation, in addition, if the condition of detaching the graphs by a process worker exists, the process worker associates the detached graphs to a PBOM (basic programmable controller object model), in order to realize a business closed loop with design change, a 'design change order number' attribute is added to a process change order, a process notice and a technical notice, and data preparation is made for change closed loop information fed back by the design in the future;
s3, batch technical state management optimization, each production is driven by a production approval process, a craftsman finds parts needing to be produced, then the PBOM structure of the parts is displayed based on a batch base line, then the production is started, the system automatically puts the PBOM of the current parts and a process procedure file related to each part into a production sheet (the batch information of the production sheet is taken from the base line selected by the current part), after the approval, the PDM system sends the PBOM and a process route (structured data, node information of a lower-level casting blank is added for a casting) to the ERP by utilizing an integrated interface with the ERP, wherein the files only provide links and do not provide entity files, the production finished by a model product through a plurality of production sheets can be checked through the PBOM for retrospective comparison with the data received by the ERP, the process change process is modified and deviated from a single process, and a 'designated affected batch' link is added, the affected batch can be set. For the process change flow, if the affected batch is designated, after the process change is released, the modified version is directly put into the batch baseline and the production flow is automatically started. Aiming at the deviation process, if the affected batch is designated, directly putting the deviation list into the baseline of the modified related batch and starting the production process after the deviation is issued;
s4, tool design management, including tool design, tool design data storage, tool EBOM management, tool design document management and tool design change management;
tool design: the tool design process based on the PDM comprises three stages of scheme design, detailed design and design change, wherein various design files are compiled in the scheme stage, a serial number is applied before the files are compiled, then the files are uploaded to a PDM system, the detailed design in work is started after the schemes are approved and issued, drawing is mainly performed on drawings and models in the detailed design stage, part serial numbers are also applied before the files are uploaded to the PDM system, an automatic CAD drawing adopts a manual EBOM building mode, a Creo model adopts an integrated EBOM building mode, the drawing models are issued along with the examination and the approval of the EBOM, when the tool needs to be changed, a design change program is executed, when the tool is converted into the stage, a marking link is needed in the shaping stage, according to the actual situation, the tool design is generally simplified compared with a research and development design mode, and the scheme design stage is an optional link;
tool design data storage: the tool design data comprises drawings, models and design files, the data type defined by the current PDM system can be used, the tool is mainly a special tool, special folder management tool data is proposed to be arranged under a model product library and is named as a tool, the tool design data is stored in the tool folder, namely whether the tool design data is the tool data or not is distinguished through a storage position, if the tool is a general tool, the tool library is established to be independent of the product library management general tool data, the product library is named as a general tool, the folder under the product library of the general tool comprises a design file and a process file, the state tool data to be planned is open to all members of the product library for reading and modifying, and all members of other state special tool data have reading rights but can not be modified;
tool EBOM management: the tool is designed in two dimensions by using AutoCAD and in three dimensions by using Creo, the tool design result is suggested and also managed by using EBOM organization, the AutoCAD two-dimensional design tool adopts a manual EBOM building mode, the Creo three-dimensional design work adopts a Creo integration mode to build the EBOM, each node of the tool EBOM has a corresponding pattern or model, an AutoCAD two-dimensional design drawing needs to be manually converted into a pdf format before being uploaded to a PDM system, a dwg format file is used as the main content of the pattern file, the pdf format file is used as an accessory of the pattern file, the Creo three-dimensional design result has a three-dimensional model and also has a drw format two-dimensional drawing, the three-dimensional design result needs to be converted into a lightweight file through a visualization server, wherein the drw format file is converted into PDF format, the tooling drawing or model is checked in batch along with EBOM, after the checking process is finished, the system automatically generates a signature file (pdf format), and the electronic signature of the tool design file is configured based on the existing functions of the PDM system;
tool design document management: after the tool design documents of other characters and forms are compiled outside the system (doc or pdf format), uploading the tool design documents to a PDM (product data management) for filing, wherein the uploaded documents are in a 'quasi' state, the system automatically calls a visual server to generate a visual file (pdf format), after uploading, an examination and approval process is started based on the document 'submitting and reviewing', so that the documents are controlled, non-pattern and model tool design documents are not associated with EBOM (electronic design document) by mandatory requirements, the examination and approval process of the tool design documents is the same as the examination and approval process of the tool EBOM, after the examination and approval process is finished, the system automatically generates a signature file (pdf format), and the electronic signature of the tool design file is configured based on the existing functions of the PDM system;
tool design change management: after the EBOM or the tool design file is approved, the tool designer must complete the tool design change process if the tool designer wants to modify the EBOM or the tool design file. The method comprises the following steps that a tool designer creates a tool design change list based on a data object needing to be changed, the tool designer needs to revise data when creating the change list, the revised data is upgraded to a large version (for example, the data is upgraded from an A.3 version to a B.1 version), the data is changed into a 'simulation' state, the tool designer can revise based on the data, a tool design change flow is submitted after the revision is completed, and the tool design change flow and the tool data needing to be changed are examined and approved;
and S5, managing the model technical file code number, including a system management module, a code application module and code use.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Claims (9)
1. A product development process data integration management method considering multiple technical states is characterized by comprising the following steps:
s1, design technology state management optimization, including EBOM construction, EBOM audit, design base library management, design technology state baseline and EBOM construction business scene;
s2, optimizing process technology state management, including process technology state management, PBOM construction and batch baseline determination, secondary process task division, PBOM reconstruction, process documentation, process file approval and batch baseline investment, PBOM approval and process change and closed-loop identification;
s3, batch technical state management optimization, wherein each production is driven by a production approval process, a craft searches parts needing to be produced, then the PBOM structure of the parts is displayed based on a batch base line, then the production is started, the system automatically puts the PBOM of the current parts and a process procedure file associated with each part into a production sheet (the batch information of the production sheet is taken from the base line selected by the current part), and after approval, the PDM system sends the PBOM and a process route (structured data, node information of a lower-level casting blank is added to the casting) to the ERP by using an integrated interface of the ERP, wherein the file only provides a link and does not provide an entity file;
s4, tool design management, including tool design, tool design data storage, tool EBOM management, tool design document management and tool design change management;
and S5, managing the model technical file code number, including a system management module, a code application module and code use.
2. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: the EBOM construction comprises a manual EBOM construction mode, an Excel importing EBOM generation mode and a Creo integration EBOM generation mode.
3. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: the system management module comprises a management coding category, a management coding rule, a modification coding rule, a forbidding coding rule and a browsing coding rule.
4. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: the code application module comprises code application, check codes, approval codes, revocation codes and recovery codes.
5. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: in S1, there may be multiple states that need to be managed in a certain development stage of the product in the design process, such as a sample projectile and a formal projectile, or multiple batches, where the design data versions of each state are different, and data that need to realize different states can be identified and traced, after receiving or constructing the design data, a craftsman manually puts the design data into the state baseline of the corresponding state design technology, and defines an identifier for each state, such as identification by batch, for example, P01, P02, and the numbering rule of the design baseline is defined as: the method comprises the steps of SJJX + model number + development phase identification + state identification, wherein a design baseline is designated for selected data when a task is initiated each time, the state of a craft worker is defaulted to be approved after the baseline is created, the EBOM state is automatically put into the baseline after being approved, and after the EBOM is updated, the baseline content is automatically updated through flow driving, namely the baseline of the design technology state.
6. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: in an operation menu of a detailed information interface of a top node of the EBOM in the S2, a first-level process responsible person can convert the EBOM into a process PBOM view by using the operation of converting into a process BOM, process attribute information such as identifying a casting and forging part is added after the conversion is finished, the first-level process responsible person puts the PBOM into a batch baseline and determines the basis for developing process design work, the first-level process responsible person compiles a route list and associates the route list with the PBOM top node, the route list needs to identify the batch information, and the route list and the associated top node automatically put into the batch baseline after approval.
7. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: in S2, according to the division of work of the secondary process task, it is determined which parts are responsible for maintenance of each department, and the process personnel determines whether to reconstruct the PBOM according to the process design requirements, such as adding virtual parts, splitting parts, merging parts, etc., the operation mode is the same as the manual EBOM construction mode, and then determines whether to update the process attributes of the single node of the PBOM according to the needs, such as whether to buy or outsource, or update the process attributes in batch in an excel table based on the existing export BOM, and then import the update BOM.
8. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: after the process file is approved in the S2, the system puts the process file and the associated Part into the batch baseline according to the batch information identified by the approved process file, and when the batch baseline does not exist, the system is promoted and the baseline must be created first.
9. The integrated management method for product development process data considering multiple technical states as claimed in claim 1, wherein: in the process of process design in S2, adding a production sheet object to record data sent to ERP each time, tracing a product to complete production in several times, wherein in a development stage or a batch production stage, each production is driven by a production approval process, a technologist finds a part to be produced, then displays a PBOM structure of the part based on a batch base line, starts production, and automatically puts a PBOM of the current part and a process procedure file associated with each part into the production sheet (the batch information of the production sheet is taken from the base line selected by the current part), after approval, a PDM system sends the PBOM and a process route (structured data, node information of a lower-level casting blank is added to the casting) to the ERP by using an integrated interface with the ERP, wherein the file only provides a link and does not provide an entity file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011167163.0A CN112508500B (en) | 2020-10-27 | Product development process data integrated management method considering multiple technical states |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011167163.0A CN112508500B (en) | 2020-10-27 | Product development process data integrated management method considering multiple technical states |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112508500A true CN112508500A (en) | 2021-03-16 |
| CN112508500B CN112508500B (en) | 2024-09-24 |
Family
ID=
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113240231A (en) * | 2021-03-31 | 2021-08-10 | 成都飞机工业（集团）有限责任公司 | Finished product technical state management system |
| CN113656987A (en) * | 2021-10-12 | 2021-11-16 | 南京国睿信维软件有限公司 | Multiple manufacturing process design method based on single design drawing |
| CN114239246A (en) * | 2021-12-01 | 2022-03-25 | 中国电子科技集团公司第二十九研究所 | Production method of PBOM (peripheral component interconnect express) process assembly for complex scene |
| CN115048734A (en) * | 2022-05-18 | 2022-09-13 | 中国电子科技集团公司第二十九研究所 | Cross-layer cascade dynamic structured process compiling, production executing and changing method |
| CN116450666A (en) * | 2023-06-19 | 2023-07-18 | 北京天圣华信息技术有限责任公司 | PBOM updating method, device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20080004061A (en) * | 2006-07-04 | 2008-01-09 | Stx조선주식회사 | A method of managing technical change for a ship design |
| CN108614891A (en) * | 2018-05-09 | 2018-10-02 | 上海航天精密机械研究所 | Space product data packet is built and consistency desired result method |
| CN110659866A (en) * | 2019-04-15 | 2020-01-07 | 南京依维柯汽车有限公司 | Method for releasing BOM from PDM system to ERP system |
| CN111738607A (en) * | 2020-06-28 | 2020-10-02 | 中国电子科技集团公司第五十四研究所 | Electronic equipment process documentation method based on PBOM baseline |
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20080004061A (en) * | 2006-07-04 | 2008-01-09 | Stx조선주식회사 | A method of managing technical change for a ship design |
| CN108614891A (en) * | 2018-05-09 | 2018-10-02 | 上海航天精密机械研究所 | Space product data packet is built and consistency desired result method |
| CN110659866A (en) * | 2019-04-15 | 2020-01-07 | 南京依维柯汽车有限公司 | Method for releasing BOM from PDM system to ERP system |
| CN111738607A (en) * | 2020-06-28 | 2020-10-02 | 中国电子科技集团公司第五十四研究所 | Electronic equipment process documentation method based on PBOM baseline |
Non-Patent Citations (7)
| Title |
|---|
| 吴欣;: "一体化三维工艺设计在复杂电子装备中的应用", 电子机械工程, no. 01 * |
| 御云|清软英泰: "航天三维设计过程管理PDM解决方案", Retrieved from the Internet <URL:http://www.pdm.so/information/201910281144.html> * |
| 李玮 等: "基于 PDM 系统的设计制造一体化应用研究", 信息化技术, no. 4 * |
| 白书清 等: "基于Windchill的多物料清单管理技术研究", 计算机集成制造系统, no. 01 * |
| 秦坤 等: "基于PDM基线的研究与实施", 航空精密制造技术, vol. 50, no. 3 * |
| 赵鹏 等: "基于PDM的三维工艺设计与管理", 智能制造, no. 1 * |
| 钱勇: "基于系统的基线管理研究", 中国优秀硕士学位论文全文数据库 (信息科技辑), no. 6 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113240231A (en) * | 2021-03-31 | 2021-08-10 | 成都飞机工业（集团）有限责任公司 | Finished product technical state management system |
| CN113656987A (en) * | 2021-10-12 | 2021-11-16 | 南京国睿信维软件有限公司 | Multiple manufacturing process design method based on single design drawing |
| CN114239246A (en) * | 2021-12-01 | 2022-03-25 | 中国电子科技集团公司第二十九研究所 | Production method of PBOM (peripheral component interconnect express) process assembly for complex scene |
| CN114239246B (en) * | 2021-12-01 | 2023-04-25 | 中国电子科技集团公司第二十九研究所 | Production method of complex scene-oriented PBOM (private branch exchange) process assembly |
| CN115048734A (en) * | 2022-05-18 | 2022-09-13 | 中国电子科技集团公司第二十九研究所 | Cross-layer cascade dynamic structured process compiling, production executing and changing method |
| CN116450666A (en) * | 2023-06-19 | 2023-07-18 | 北京天圣华信息技术有限责任公司 | PBOM updating method, device and storage medium |
| CN116450666B (en) * | 2023-06-19 | 2023-09-05 | 北京天圣华信息技术有限责任公司 | PBOM updating method, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20060129462A1 (en) | Automated planning and manufacturing systems | |
| CN106774170B (en) | A kind of generation system of three-dimensional mechanical processing technique | |
| KR20030081675A (en) | System for designing wiring harness using database for vehicle and method for the same | |
| CN107729668A (en) | Technological design coordination management system and its method based on threedimensional model | |
| WO2021228118A1 (en) | Central air conditioner intelligent design method, system and device | |
| CN102243495A (en) | Electronic work instruction designed for isa-95 standard | |
| US20060129461A1 (en) | Data entry and system for automated order, design, and manufacture of ordered parts | |
| CN116796498A (en) | Model-based system research and development flow method and management system | |
| CN103164573A (en) | Product data management (PDM) design system | |
| CN111241675B (en) | Complex product collaborative design management method and system based on data driving | |
| CN115169011A (en) | Editing system and application system of airplane assembly outline | |
| KR20090124059A (en) | Total dimensional accuracy control system and method for block assembly | |
| US20060129270A1 (en) | Processes and systems for creation of machine control for specialty machines requiring manual input | |
| CN112508500A (en) | Product development process data integration management method considering multiple technical states | |
| CN112288150A (en) | Boats and ships industry pipe fitting processing management and control integrated system | |
| CN112508500B (en) | Product development process data integrated management method considering multiple technical states | |
| CN111914417A (en) | Plan and budget simulation analysis system | |
| CN116562784A (en) | Method and system management platform for implementing modification and monitoring of aircraft assembly engineering | |
| CN110717976A (en) | Technical state linkage method in product manufacturing process | |
| CN111222793A (en) | Data interaction method and system | |
| Jeon et al. | Information Delivery Manual (IDM) Configurator: Previous Efforts and Future Work | |
| CN114881601A (en) | Multi-process route transmission method based on PLM system | |
| CN114115843A (en) | Low code production method of index data and visualized data processing system thereof | |
| CN113256080B (en) | Teamcenter-based multi-beat process file development system and file development method | |
| JP3229811U (en) | BOM creation system based on design specifications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |