Engineering management system control method based on model

Abstract

The invention provides a model-based engineering management system control method. The model-based engineering management system control method comprises the following steps: proposing design task information in a problem mode according to a first user operation; changing a design model according to the design task information; and sending a notification after the design model is changed to a preset position. The modification process is constructed in a questioning mode, and the technical problem that an overall efficient system for three-dimensional modeling modification of drawings is lacked in the prior art is solved.

Description

Technical Field:

[0001] The present invention relates to the technical field of management control, and in particular to a control method for a model-based engineering management system. Background Art:

[0002] The characteristics of long design cycle, multi-disciplinary and multi-professional, complex structure and complex functions of ships determine that frequent changes are required during the ship design process and production and construction process. The impacts brought by engineering changes will directly reflect on the quality, cost and delivery date of the ships.

[0003] Therefore, it is necessary to establish an engineering change control system during the ship life cycle to effectively discover problems in the design process, solve and trace the problems, solidify the scope of change impacts and the change status before and after, form a complete closed-loop control, and improve the technical traceability of the ship throughout its life cycle.

[0004] For traditional one-shipyard-multiple-factory engineering changes based on drawings and documents, restricted by the construction progress of the general assembly construction unit, etc., it is usually the on-site work team (general design unit) that modifies the drawings at the construction site. The internal drawing modification of the general design unit is often relatively lagged. In addition, the information that two-dimensional drawings and documents can carry is relatively limited. The discovery of design problems and the judgment of modification content rely more on the experience of designers, and it is easy to miss when involving modifications of multiple specialties. Therefore, it is necessary to establish an engineering change control system with a three-dimensional model as the technical responsibility carrier, timely and quickly feedback the modification results to the construction site, ensure the synchronization of the product technical status, further reduce design changes, and effectively improve the design quality.

[0005] There is an urgent need for a control method for a model-based engineering management system, which helps to solve the technical problem in the prior art of lacking an overall efficient system for modifying the three-dimensional modeling of drawings. Summary of the Invention:

[0006] In one embodiment, the present invention provides a control method for a model-based engineering management system, which constructs a modification process by means of asking questions, and helps to solve the technical problem in the prior art of lacking an overall efficient system for modifying the three-dimensional modeling of drawings.

[0007] The control method for the model-based engineering management system includes:

[0008] Proposing design task information in the form of questions according to the first user operation;

[0009] Making design model changes according to the design task information;

[0010] Sending the notice after the design model changes to a predetermined location.

[0011] In one embodiment, presenting the design task information in the form of a question according to the first user operation includes:

[0012] The team leader client creates a question through a second user operation and describes the question;

[0013] The team leader client designates the contracting information of the contracting unit;

[0014] The question is presented according to the contracting information to form design task information.

[0015] In one embodiment, the design model is submitted to the system through the contracting unit client in the form of a delivery package.

[0016] In one embodiment, after the step of sending the notice of the changed design model to a predetermined location, the method further includes:

[0017] The general section leader client analyzes and modifies the delivery package, and adds and modifies the model delivery package of personnel through a third user operation.

[0018] In one embodiment, after the step that the general section leader client analyzes and modifies the delivery package, and adds and modifies the model delivery package of personnel through a third user operation, the method further includes:

[0019] The designer client receives the model modification task;

[0020] After modifying the model according to the modification task, it is fed back to the general section leader client so that the general section leader client can review the modified model through a fourth user operation.

[0021] In one embodiment, after the step that after modifying the model according to the modification task, it is fed back to the general section leader client so that the general section leader client can review the modified model through a fourth user operation, the method further includes:

[0022] Prepare a modification notice and send back the change task.

[0023] In one embodiment, the contracting unit client and the co - sponsoring professional client respectively proofread the modification notice and countersign the modification notice.

[0024] In one embodiment, after the step that the contracting unit client and the co - sponsoring professional client respectively proofread the modification notice and countersign the modification notice, the method further includes:

[0025] Approve the modification notice.

[0026] In one embodiment, after the step of approving the modification notice, the method further includes:

[0027] The client of the contracting unit executes the filing process and the distribution process.

[0028] In one embodiment, before the step of presenting the design task information in the form of a question according to the first user operation, the method further includes:

[0029] Define the main data types in the engineering change, divide the types according to different services, and clarify the responsibilities of the data types. Description of the drawings:

[0030] Figure 1 Schematic diagram of the engineering change data model definition architecture in an embodiment of the present invention;

[0031] Figure 2 Schematic diagram of the architecture for defining the main attributes in another embodiment of the present invention;

[0032] Figure 3 Schematic diagram of the problem type attribute information architecture in another embodiment of the present invention;

[0033] Figure 4 Schematic diagram of the modification notice type attribute information in another embodiment of the present invention;

[0034] Figure 5 Schematic diagram of the data status definition in the engineering change in another embodiment of the present invention;

[0035] Figure 6 Schematic diagram of the user role definition in the engineering change in another embodiment of the present invention;

[0036] Figure 7 Schematic diagram of the process of the model-based engineering change management method in another embodiment of the present invention;

[0037] Figure 8 Schematic diagram of the data flow of the model-based engineering change management in another embodiment of the present invention;

[0038] Figure 9 Use case diagram for change request management in another embodiment of the present invention;

[0039] Figure 10 Use case diagram for the more request management in another embodiment of the present invention;

[0040] Figure 11 Use case diagram for change notice management in another embodiment of the present invention. Specific embodiments:

[0041] To enable those skilled in the art to better understand the technical solutions of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0042] To solve the problems such as asynchronous data modification and ineffective change impact analysis in engineering changes based on drawing documents, reduce the total amount of engineering changes, and improve design quality, the present invention provides a model-based engineering change management method.

[0043] This patent provides a model-based engineering change management method, which runs through the entire life cycle of engineering changes in a multi-plant under one institute. Through data model definition, the change management infrastructure is determined. Through role definition, personnel and responsibilities are determined. By introducing an integrated process management mode, online management of engineering change data is realized, and management efficiency is improved. Real-time monitoring is carried out on the three major stages of requests, instructions, and notifications during the change process, forming a complete closed-loop control for engineering changes, improving the traceability of the technical status of ship products throughout the life cycle, and providing a strong guarantee for digital collaborative design.

[0044] Figure 1 It is a schematic diagram of the engineering change data model definition architecture in an embodiment of the present invention; Figure 2 It is a schematic diagram of the definition architecture of main attributes in another embodiment of the present invention; Figure 3 It is a schematic diagram of the problem type attribute information architecture in another embodiment of the present invention;

[0045] Figure 4 It is a schematic diagram of the modification notice type attribute information in another embodiment of the present invention; Figure 5 It is a schematic diagram of the data status definition in engineering changes in another embodiment of the present invention; Figure 6 It is a schematic diagram of the user role definition in engineering changes in another embodiment of the present invention;

[0046] Figure 7 It is a schematic diagram of the process of the model-based engineering change management method in another embodiment of the present invention; Figure 8 It is a schematic diagram of the data flow of the model-based engineering change management in another embodiment of the present invention; Figure 9 It is a use case diagram for change request management in another embodiment of the present invention; Figure 10 It is a use case diagram for change request management in another embodiment of the present invention; Figure 11 It is a use case diagram for change notice management in another embodiment of the present invention.

[0047] As Figures 1 to 11 shown, in one embodiment, the present invention provides a control method for a model-based engineering management system, and the control method for the model-based engineering management system includes:

[0048] S101, propose design task information in the form of a problem according to the first user operation.

[0049] In this step, specific steps for proposing design task information in the form of a problem according to the first user operation are provided.

[0050] S102. Modify the design model according to the design task information.

[0051] In this step, a specific step for modifying the design model according to the design task information is provided.

[0052] S103. Send the notice after the design model is modified to a predetermined location.

[0053] In this step, a specific step for sending the notice after the design model is modified to a predetermined location is provided.

[0054] In this embodiment, a specific implementation manner of the model-based engineering management system control method is provided. The previous project establishment method generally adopted the project method. Since there was too much design information and it was not direct, the efficiency was relatively low. Therefore, we adopted the method of information interaction by raising questions. Here, the predetermined location can be different clients or the server, which helps to solve the technical problem of the lack of an overall efficient system for modifying the three-dimensional modeling of drawings in the prior art.

[0055] In one embodiment, the design task information proposed in the form of a question according to the first user operation includes:

[0056] The team leader client creates a question through a second user operation and describes the question.

[0057] The team leader client designates the undertaking information of the undertaking unit.

[0058] The question is proposed according to the undertaking information to form design task information.

[0059] In this embodiment, a specific information interaction method of the team leader client is mainly provided. It should be noted that the clients above and below mainly refer to the different positions of the operators' identities, corresponding to different positions in the system framework.

[0060] In one embodiment, the design model is submitted to the system in the form of a delivery package through the undertaking unit client.

[0061] In one embodiment, after the step of sending the notice after the design model is modified to a predetermined location, the method further includes:

[0062] The general section leader client analyzes and modifies the delivery package, and adds and modifies the model delivery package of personnel through a third user operation.

[0063] In one embodiment, after the step that the general section leader client analyzes and modifies the delivery package and adds and modifies the model delivery package of personnel through a third user operation, the method further includes:

[0064] The designer client receives a model modification task;

[0065] After modifying the model according to the modification task, it is fed back to the general section chief client, so that the general section chief client can review the modified model through a fourth user operation.

[0066] In one embodiment, after the step of modifying the model according to the modification task and feeding it back to the general section chief client, so that the general section chief client can review the modified model through a fourth user operation, the method further includes:

[0067] Prepare a modification notice and send back the change task.

[0068] In one embodiment, the contractor client and the co - sponsoring professional client respectively proofread the modification notice and countersign the modification notice.

[0069] In one embodiment, after the step that the contractor client and the co - sponsoring professional client respectively proofread the modification notice and countersign the modification notice, the method further includes:

[0070] Approve the modification notice.

[0071] In one embodiment, after the step of approving the modification notice, the method further includes:

[0072] The contractor client executes the archiving process and the distribution process.

[0073] In one embodiment, before the step of presenting design task information in the form of a question according to the first user operation, the method further includes:

[0074] Define the main data types in the engineering change, divide the types according to different businesses, and clarify the responsibilities of the data types.

[0075] (1) Data model definition

[0076] Define the basic types and relationships in the engineering change, and determine the basic data architecture for the entire change management.

[0077] Define the main data types in the engineering change, divide the types according to different businesses, and clarify the responsibilities of the data types.

[0078] Define the main attributes of the types in the engineering change management, which are used to store specific information during the implementation of the engineering change.

[0079] Define the status of the types in the engineering change management, which is used to clarify the current business status during the implementation of the engineering change and facilitate subsequent operations.

[0080] (2) Role Definition

[0081] Define the main roles in the engineering change, and determine the personnel and responsibilities for the entire change management.

[0082] (3) Business Process

[0083] A model-based engineering change management method includes the following main steps:

[0084] Step 1: The team leader creates a problem and briefly describes it.

[0085] Step 2: The team leader designates the main unit and co-organizing unit of the overall department.

[0086] Step 3: The person in charge of the main unit designates the person in charge of the problem.

[0087] Step 4: The person in charge, the personnel of the co-organizing unit and the designer coordinate offline. After summarizing to form a complete modification plan, the person in charge uploads the modification plan and adds the model delivery package that needs to be modified for this change.

[0088] Step 5: The section leader receives the modification plan and assigns personnel for model modification and proofreading. If the model delivery package added by the person in charge is incomplete, the section leader can supplement and add it. If it is found that the co-organizing unit is incomplete in the modification plan, the section leader will roll back the process to the person in charge.

[0089] Step 8: The model proofreader proofreads the model.

[0090] Step 9: The section leader reviews the model.

[0091] Step 10: The section leader prepares and uploads the modification notice.

[0092] If the model delivery package is incomplete, the section leader can supplement and add it. If it is found that the co-organizing unit is incomplete in the modification plan, the section leader will roll back the process to the person in charge.

[0093] Step 6: The model modifier receives the model modification task.

[0094] Step 7: After the model modification is completed, the model modifier uploads the modified model delivery package and the modification description.

[0095] Step 11: After all model modification tasks are completed, the section leader forwards the change tasks back according to the specialty. The modification tasks of the main specialty are forwarded back to the person in charge, and the modification tasks of the co-organizing specialty are forwarded back to the co-organizer.

[0096] Step 12: The main and co-organizing units modify the modification notice and the model modification tasks of their respective specialties. After proofreading, the person in charge signs the proofreading of the modification notice, and the relevant personnel of the co-organizing unit sign the joint signature.

[0097] Step 13: The team leader approves the modification notice.

[0098] Step 14: Archive and distribute the modified model.

[0099] From the perspective of the application layer, the model-based engineering management system control method, the model-based engineering management system, the system includes business process and problem status management, as well as ECN status management and model status management;

[0100] The functional modules of the business process include problem creation, problem evaluation and assignment, ECN creation and assignment, ECN initiation review, ECN execution and change task submission, ECN release approval, ECN archiving, ECN sending;

[0101] The functional modules of the problem status management include creation, assignment, activity, review, closure;

[0102] The functional modules of the ECN status management include preliminary, work, review, release, archiving, sending;

[0103] The functional modules of the model status management include model original version, new version, freeze, release;

[0104] The module interactions between layers include:

[0105] The problem creation realizes problem creation for the creation functional module;

[0106] The problem evaluation assigns problem tasks to the assignment;

[0107] The ECN initiation review realizes information re-interaction of the work module with the activity module for the work, and the work module conducts information interaction with the model original version and the new version;

[0108] The ECN execution and change task submission conducts information interaction with the review, the review conducts information interaction with the freeze, and the ECN release approval conducts information interaction with the release and then with the review.

[0109] The ECN archiving conducts information interaction with the archiving and the release;

[0110] The ECN sending conducts information interaction with the sending and the subsequent closure.

[0111] Beneficial effects:

[0112] This patent proposes a model-based engineering change data management method. During the engineering application of a certain product, a model-based change management mechanism for one institute with multiple factories is established, and change impact analysis is fully carried out to improve the change linkage of various specialties. For the first time, the single-specialty change based on drawings and documents is transformed into a multi-specialty comprehensive change based on models, ensuring the consistency of the change technical state. Compared with the previous product, the total number of engineering changes is reduced by nearly 70%, effectively improving the design quality.

[0113] Explanation of the data flow and state transition in the business process of model-based engineering change management.

[0114] Step 1: Change request management. The change request is recorded online in the form of a problem, which is the starting point of the engineering change.

[0115] 1) The general assembly construction unit issues a technical contact form to record the design and engineering changes required during the on-site construction of the hull.

[0116] 2) Record and confirm the problem in the system. The problem includes specific ship product codes, contact form numbers, names, sources, and contact form contents, etc.

[0117] 3) The professional supervisor creates a change request form. The problem, technical contact form, and technical coordination form are used as the input of the change request, and then change impact analysis is carried out. After being approved by the relevant personnel in the change management process, the change is made.

[0118] ) Quick change: As Figure 10 shown within the red dotted line, for quick changes to problems spontaneously raised within the unit or by designers, no other input or drive is required. At this time, only the change notice change control process is followed (the review and approval nodes of the simplified process can also be distinguished from the formal change);

[0119] 2) Formal change: As Figure 10 shown in full, for changes with greater impacts such as affecting cost and quality, they are driven by the change request. Formal changes must have complete change requests and change instructions (modification notices). At this time, the change application form control process and the change instruction control approval process need to be followed.

[0120] Step 3: Change notice management. From the input of the change (problem, technical contact / coordination form, review, or spontaneous) to the submission of the change request to the driving of the change instruction (change notice); then after the change instruction is completed, it is issued to the relevant departments and units for execution. After the relevant departments and units complete the change notice, the execution situation is fed back to drive the change instruction to complete, the change instruction drives the change request to complete, and after the change request is completed, it drives the problem to be closed for closed-loop management.

[0121] The above embodiments are only exemplary embodiments of the present invention and are not intended to limit the present invention. The protection scope of the present invention is defined by the claims. Those skilled in the art can make various modifications or equivalent substitutions within the essence and protection scope of the present invention, and such modifications or equivalent substitutions should also be regarded as falling within the protection scope of the present invention.

Claims

1. A control method for a model-based engineering management system, characterized in that, The model-based engineering management system control method includes: Proposing design task information in the form of a question according to the first user operation; Making changes to the design model according to the design task information; Sending the notice after the design model is changed to a predetermined location.

2. The control method of the model-based engineering management system according to claim 1, wherein The step of proposing design task information in the form of a question according to the first user operation includes: The team leader client creates a question through the second user operation and describes the question; The team leader client designates the contracting information of the contracting unit; Proposing the question according to the contracting information to form design task information.

3. The control method of the model-based engineering management system according to claim 2, wherein The design model is submitted to the system in the form of a delivery package through the contracting unit client.

4. The control method of the model-based engineering management system according to claim 3, characterized in that After the step of sending the notice after the design model is changed to a predetermined location, the method further includes: The general section leader client analyzes and modifies the delivery package, and supplements and adds modified model delivery packages for personnel through the third user operation.

5. The method for controlling a model-based engineering management system according to claim 3, wherein After the step that the general section leader client analyzes and modifies the delivery package, and supplements and adds modified model delivery packages for personnel through the third user operation, the method further includes: The designer client receives the model modification task; After modifying the model according to the modification task, feedback it to the general section leader client, so that the general section leader client can review the modified model through the fourth user operation.

6. The control method of the model-based engineering management system according to claim 5, wherein, After the step of modifying the model according to the modification task and then feedbacking it to the general section leader client so that the general section leader client can review the modified model through the fourth user operation, the method further includes: Compiling a modification notice and sending back the change task.

7. The control method of the model-based engineering management system according to claim 6, characterized in that, The contracting unit client and the co-organizing professional client respectively proofread the modification notice and countersign the modification notice.

8. The control method of the model-based engineering management system according to claim 7, characterized in that After the step that the contracting unit client and the co-organizing professional client respectively proofread the modification notice and countersign the modification notice, the method further includes: Approving the modification notice.

9. The control method of the model-based engineering management system according to claim 8, wherein After the step of approving the modification notice, the method further includes: The contracting unit client executes the filing process and the distribution process.

10. The control method of the model-based engineering management system according to claim 9, characterized in that, Before the step of proposing design task information in the form of a question according to the first user operation, the method further includes: Defining the main data types in the engineering change, dividing the types according to different businesses, and clarifying the responsibilities of the data types.

Images