A method for managing the internal and external interfaces of a target object boundary
By deconstructing the target object and related objects and managing the interface matrix, the problem of poor compatibility in component assembly was solved, and efficient production and quality assurance of the equipment were achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GUOKE SOFT (SUZHOU) TECH CO LTD
- Filing Date
- 2023-11-15
- Publication Date
- 2026-05-26
Smart Images
Figure CN117473002B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of interface management technology, and in particular to a method for managing interfaces inside and outside the boundary of a target object. Background Technology
[0002] In the existing technology, the components of the equipment come from different suppliers. When the suppliers produce the components according to the functional requirements, the manufacturer assembles the components received from different suppliers into finished equipment.
[0003] Since different components are manufactured according to functional requirements, a single component can meet the required functional requirements. However, assembling components from suppliers in different fields can easily lead to poor assembly compatibility, resulting in errors after assembly or poor assembly performance.
[0004] Therefore, it is necessary to supervise the production and processing of components, especially the relationships between related interfaces of interconnected components, to ensure that the interfaces are compatible and that the assembled parts function properly. Therefore, this invention provides an object interface management method to solve the problems existing in the prior art. Summary of the Invention
[0005] The purpose of this invention is to provide an object interface management method to solve the technical problem in the prior art where suppliers from different fields produce individual parts on demand, which can meet the needs of individual parts, but due to professional barriers, the compatibility of the parts when assembled together cannot meet the overall quality requirements of the equipment.
[0006] The technical solution of this invention is: a method for managing the internal and external interfaces of a target object boundary, comprising:
[0007] S1: Determine the target object and the associated objects that are assembled with the target object;
[0008] S2: Deconstruct the target object and the associated object to obtain the internal structural components of the target object and the external structural components of the associated object;
[0009] S3: Structural code management is performed based on the structural decomposition into the internal structural components and the external structural components;
[0010] S4: Based on the structural relationships between the internal structural components and the structural relationships between the internal structural components and the external structural components, set interfaces to represent the structural relationships and construct an interface matrix;
[0011] S5: Transmit the interface matrix information to the production operation terminals of the inner structural component and the outer structural component to synchronize the interface information;
[0012] S6: Perform interface library management and interface failure risk management based on the interface matrix.
[0013] Preferably, the process of constructing the interface matrix includes:
[0014] S31: Analyze the structural relationships between the internal structural components and the structural relationships between the internal structural components and the external structural components;
[0015] S32: Construct an interface for the inner structural component and the outer structural component that have a structural relationship;
[0016] S33: Set interface numbers for the internal structural components and the external structural components, and add interface function descriptions to the interface numbers;
[0017] S34: Based on the internal structural components, the external structural components, and the structural relationships, the interface matrix is generated.
[0018] Preferably, the interface matrix is set as a table, and the row headers or column headers of the table have "structure name" and "internal / external components" respectively;
[0019] When managing interfaces, the row and column filtering rules are as follows: filter by one of the following: structure name, interface matrix type, or interface type.
[0020] The content in the nth row and mth column of the table (n>1, m>1, where n and m are both positive integers) contains the interface code and the corresponding structural relationship between the structures in the nth row and mth column.
[0021] Preferably, the structural relationship is an assembly connection and functional relationship, and one interface corresponds to and uniquely identifies two structural components;
[0022] The structural relationships include: physical contact, energy transfer, information exchange, material transfer, and human-machine interaction.
[0023] Preferably, the physical contact connection methods in the structural relationship include welding, bonding, fastening, snap-fitting, plugging, bolting, lubrication, and interference fit;
[0024] The connection methods for information exchange in the structural relationship include: circuit signal connection, probe signal connection, and pulse signal connection.
[0025] Preferably, interface management is performed on the target object or the associated object based on the interface matrix, and all the identified interfaces are summarized and displayed to form an interface library;
[0026] The interface library displays content including classifying and encoding the interface numbers according to the type of the structural relationship, constructing the interface code, and the interface number corresponding to the structural relationship to which it belongs;
[0027] Based on the functional relationships identified and displayed in the interface library management, interface failure risk management is performed on the interface.
[0028] Preferably, the interface library construction and management includes:
[0029] Filter the interface codes and interface function descriptions to construct an interface library matrix, where each interface code corresponds one-to-one with the interface function description.
[0030] The operation options allow you to edit the interface code and its corresponding function description. The operation categories include modification and deletion.
[0031] The system automatically saves any edits made to the interface matrix or the interface library matrix and synchronizes the saved changes to all associated interfaces to display the latest interface relationship information.
[0032] Preferably, the structural and interface information of the target object or the associated object is transmitted to the FMEA system, where failure analysis of the interface is performed and control measures are taken to reduce the design risks caused by the interface.
[0033] The process of performing interface failure analysis and management includes:
[0034] F1: Perform interface function analysis based on the interface function description of the target interface;
[0035] F2: Perform functional failure analysis on the target interface;
[0036] F3: Set control measures for the failure of the target interface function, and verify the given control measures;
[0037] F4: Determine the risk level of taking the control measures in F3 for the failure of the target interface function; the risk level is divided into: H-high risk, M-medium risk and L-low risk, and when the risk is H, a red prompt indicates that the risk needs to be reduced;
[0038] F5: Implement new control measures for the high risks in F4 and verify the given new control measures;
[0039] F6: Determine the risk level of taking the new control measures in F5 for the failure of the target interface function. It is acceptable when the risk level is L or M.
[0040] Preferably, the structure code management includes:
[0041] Structural code encoding is set for the internal structural components and the external structural components according to the structural disassembly level of the target object, and a structural code disabling flag is set for the structural code encoding. The structural code encoding uniquely identifies the internal structural component of the target object or the external structural component of the associated object.
[0042] Preferably, the structure and interface information are bound through structure code management; when the structure code encoding is disabled, the corresponding structure code becomes invalid, and the structure and interface information is unbound.
[0043] Compared with the prior art, the advantages of the present invention are:
[0044] (1) This invention performs boundary / interface analysis on the target object and the associated objects that are assembled with the target object. By setting boundaries, interfaces are constructed inside and outside the boundaries. An interface matrix (form) is constructed according to the interface relationship to manage the component interfaces. Interface information is transmitted at the component production operation end of the target object and the associated objects to maintain information interaction and ensure the functionality and assembly compatibility between components.
[0045] (2) By setting an interface matrix for the target object and associated objects and setting structural code management for the structure, this invention can prevent code misuse, reduce code coupling, and improve code management efficiency when the structural code is no longer applicable to the current situation by disabling it.
[0046] (3) This invention brings together related structural components through an interface for unified management, breaking down the design and production barriers between structures in the traditional production model. Furthermore, based on unified interface management, risk analysis and management are carried out, taking into account more comprehensive risk factors. In the design stage, risk control measures can be better designed to improve product quality. Attached Figure Description
[0047] The present invention will be further described below with reference to the accompanying drawings and embodiments:
[0048] Figure 1 This is a flowchart of the method for managing the internal and external interfaces of the target object boundary as described in this invention;
[0049] Figure 2 This is a flowchart illustrating the process of constructing the interface matrix as described in this invention.
[0050] Figure 3 This is a schematic diagram illustrating the boundary / interface analysis relationship of the associated objects described in this invention;
[0051] Figure 4 This is a schematic diagram of the interface management form for the associated objects described in this invention;
[0052] Figure 5This is a schematic diagram of the boundary / interface analysis relationship of the target object described in this invention;
[0053] Figure 6 This is a schematic diagram of the interface management form for the target object described in this invention;
[0054] Figure 7 This is a schematic diagram of the interface library management form described in this invention;
[0055] Figure 8 This is a schematic diagram of the structure code management form described in this invention;
[0056] Figure 9 This is a schematic diagram illustrating information transmission based on interface analysis for modular management in this invention.
[0057] Figure 10 This is a flowchart illustrating the risk analysis and management process based on boundary / interface analysis, as described in this invention.
[0058] Figure 11 This is a flowchart illustrating the steps of risk analysis and management in the FMEA system according to the present invention. Detailed Implementation
[0059] The present invention will be further described in detail below with reference to specific embodiments:
[0060] like Figure 1 As shown, a method for managing the internal and external interfaces of a target object includes the following steps:
[0061] S1: Identify the target object and the associated objects that are assembled with the target object;
[0062] S2: Deconstruct the target object and its associated objects to obtain the internal structural components of the target object and the external structural components of the associated objects;
[0063] S3: Structural code management is based on structural decomposition into internal and external structural components;
[0064] S4: Based on the structural relationships between internal structural components and between internal and external structural components, set up interfaces to represent the structural relationships and construct an interface matrix;
[0065] S5: Transmit the interface matrix information to the production operation terminals of the internal and external structural components to synchronize the interface information;
[0066] S6: Manage the interface library and interface failure risk based on the interface matrix.
[0067] Identify the target object, and based on the target object, find related objects that are connected to the target object. Understand the structural relationship between the target object and related objects, and set up interfaces for structural components that are related to assembly.
[0068] Define the boundaries for the target object. The components within the boundaries are the lower-level structural parts of the target object. Based on the structural relationships between the components, construct an interface matrix for the target object.
[0069] "Target object" and "related object" are relative concepts. Therefore, a related object of the target object is used as the target object, and a boundary is defined. The area within the boundary is the interface matrix of the related objects. The constructed interface matrix is then edited to implement interface management.
[0070] By identifying the interface relationships between systems / components within and outside the target object's boundary through boundary analysis, an interface matrix is generated, enabling unified management of interfaces within and outside the target object's boundary, and allowing the export of an interface matrix list.
[0071] Boundary analysis identifies the interface relationships between internal / external systems / components within the design object's boundary and transfers this information to the FMEA (Failure Prevention and Analysis System). The FMEA allows for direct failure analysis of these interfaces and the implementation of control measures to mitigate design risks associated with them. (See attached document.) Figure 9 A flowchart illustrating the information transfer process during interface (library) management and risk analysis management based on boundary / interface analysis is provided.
[0072] Among them, refer to the appendix Figure 2 The process of constructing the interface matrix includes:
[0073] S31: Analyze the structural relationships between internal structural components and the structural relationships between internal and external structural components.
[0074] The structural relationships are assembly connections and functional relationships, with one interface corresponding to and uniquely identifying two structural components;
[0075] Structural relationships include: physical contact, energy transfer, information exchange, material transfer, and human-machine interaction.
[0076] Interfaces represent structural relationships; therefore, the interface type should be consistent with the category of the structural relationship.
[0077] For example, structure A and structure B are connected by threads (a type of physical contact), and the corresponding interface relationship is P1. The threaded connection has an interface P1 on both structure A and structure B. The threaded connection uniquely identifies the threaded connection between structure A and structure B. During assembly, they are assembled and paired through the interface. When designing and manufacturing components of structure A / B, structure B / A needs to be considered so that structure A and structure B can be assembled and adapted and operate in accordance with requirements.
[0078] Different structural relationships correspond to different interface names, and in this embodiment, "assembly" refers not only to a direct physical connection.
[0079] The physical contact connection methods in structural relationships include welding, bonding, fastening, snap-fitting, plugging, bolting, lubrication, and interference fit; the information exchange connection methods in structural relationships include: circuit signal connection, probe signal connection, and pulse signal connection.
[0080] It also includes the transfer of matter and energy. For example, the ink in a ballpoint pen refill is used to ensure smooth ink flow after the refill is assembled with the pen tip and the ball bearing. In addition to the physical connection and contact during assembly, this also includes the transfer of matter, that is, the delivery of ink.
[0081] S32: Creates interfaces for internal and external structural components that have structural relationships.
[0082] Establish assembly links for related structural components, that is, determine the two target endpoints of the interface and generate the structural code storage space (address) for the interface.
[0083] S33: Set interface numbers for internal and external structural components, and add interface function descriptions to the interface numbers;
[0084] S34: Generate an interface matrix based on internal structural components, external structural components, and structural relationships.
[0085] By setting boundaries and interfaces, the interface relationships between structures can be analyzed.
[0086] The boundary diagram (graphical relationship) format is clear and easy to view. However, with large amounts of data, the ability to quickly and conveniently export files based on the identified interface relationships is not ideal for efficient data management, and it is very inconvenient for data reuse.
[0087] Therefore, this embodiment uses an interface matrix for management, and the interface matrix is presented in tabular form, which can clearly analyze, display and view the relationship between interfaces. Compared with directly using a boundary diagram (graphical relationship) for display and viewing, it is more convenient and effective.
[0088] The row headers of the management table in the interface matrix are "Structure Name" and "Internal / External Components", and the column headers are "Structure Name" and "Internal / External Components".
[0089] The content in the nth row and mth column of the table (n>1, m>1, where n and m are both positive integers) contains the interface code and the corresponding structural relationship between the structures in the nth row and mth column.
[0090] When managing interfaces, the target interfaces to be managed and related interface information can be obtained by filtering rows or columns.
[0091] The row and column filtering rules are as follows: filtering is performed according to one of the following criteria: structure name, interface matrix type (internal interface matrix, external interface matrix), or interface type (material contact, energy transfer, information interaction, material transfer, human-computer interaction).
[0092] Taking a ballpoint pen as an example, the target object is the pen refill, and the associated object is the telescopic mechanism, as shown in the attached figure. Figure 3 Appendix Figure 4 Appendix Figure 5 and attached Figure 6 The diagram shows the boundary / interface analysis diagram of the target object and its associated objects, along with the corresponding interface management form.
[0093] Telescopic structure---pen refill, the overall assembly interface relationship between the pen refill and the telescopic mechanism is P11: sliding fit.
[0094] In the appendix Figure 3 In the boundary diagram, the telescopic structure includes structural components: a push rod, a ratchet, and a spring. The assembly interface relationship between the push rod and the ratchet is P9: rotation, and the assembly interface relationship between the push rod and the spring is P15: pressing.
[0095] In the interface management form, the header is "Internal and External". The row and column headers of the table should include the name of the target object or related object and the name of the internal structural component of the target object or related object.
[0096] For example, in the appendix Figure 4 The document provides an interface management form for associated objects (telescopic mechanisms), with the table header being "Internal and External," column headings being "Push Rod, Ratchet, and Telescopic Mechanism," and row headings being "Pen Refill, Push Rod, and Flip Spring."
[0097] In the table (4×2) corresponding to the telescopic mechanism and the pen refill, mark the interface relationship between the telescopic mechanism and the pen refill as "P11: sliding fit". In the table (2×4) corresponding to the push rod and the lifting spring, mark the interface relationship between the push rod and the lifting spring as "P15: pressing". In the table (3×3) corresponding to the ratchet and the push rod, mark the interface relationship between the push rod and the ratchet as "P9: rotation".
[0098] Similarly, attached Figure 5 The diagram provides a boundary / interface analysis of the target object, "pen refill". The diagram shows the interface relationships between the structural components disassembled within the boundary. The structural components within the boundary of the pen refill include the pen tip, ink, and ink tube. The interface relationship between the pen tip and ink is M1: pneumatic fluid; the interface relationship between the pen tip and ink tube is P9: rotation; and the interface relationship between the ink tube and ink tube is P8: lubrication.
[0099] Appendix Figure 6The document provides a form diagram for the "pen refill" interface management.
[0100] The table title is "Interface Management (Pen Lead)", the table header is "Internal and External", the row headers are "Oil Tube", "Pen Tip" and "Pen Lead", the column headers are "Telescopic Mechanism", "Oil Tube" and "Ink", the corresponding table for telescopic mechanism and pen lead (2×4) is marked "P11: Sliding Fit", the corresponding table for oil tube and pen tip (3×3) is marked "P9: Rotation", the corresponding table for ink and oil tube (4×2) is marked "P8: Lubrication", and the corresponding table for ink and pen tip (4×3) is marked "M1: Pneumatic Fluid".
[0101] The management forms all have "row filter" and "column filter" function filter boxes, as well as function filter buttons for interface relationship types, providing multiple filtering methods and convenient querying and viewing.
[0102] Based on the above statements and appendices Figure 3 - Appendix Figure 6 The comparison of the charts shows that setting it up as an interface matrix (table) makes it easier to view and manage. Unifying the management of target objects and related objects can break down the barriers in traditional production management methods, ensuring that interfaces are compatible with each other and that assembled structural components function properly and meet requirements.
[0103] The interface matrix / management form of the target object and the interface matrix / management form of the associated object are aggregated, and the interfaces are identified. All identified interfaces and their information (interface function descriptions) are then compiled together to form an interface library matrix, which is presented in tabular form. In other words, interface (library) management is the knowledge management of interface relationships, enabling the unification, standardization, and reuse of interface relationships.
[0104] The interface library (table) displays the interface code and interface information / structural relationships / interface function descriptions.
[0105] Interface numbers are categorized and coded according to the type of structural relationship, with each interface number corresponding to its respective structural relationship.
[0106] See attached document Figure 7 The document provides the interface numbers and corresponding connection methods for interfaces of type "Physical Contact" in the interface library management form. Interfaces are categorized and coded, with their corresponding connection methods listed, making the document concise, clear, and easy to view and manage.
[0107] The interface (library) matrix displays the structural and functional relationships. It transmits the structural and interface information of the target object or related object to the FMEA system. In the FMEA system, failure analysis is performed on the interface and control measures are taken to reduce the design risks brought by the interface, thereby managing the interface failure risk.
[0108] Appendix Figure 11 The document provides a flowchart outlining the steps involved in interface failure analysis and management within an FMEA system, including:
[0109] F1: Perform interface function analysis based on the interface function description of the target interface;
[0110] F2: Perform functional failure analysis on the target interface;
[0111] F3: Set control measures for the failure of the target interface function, and verify the given control measures;
[0112] F4: Determine the risk level of taking control measures in F3 for the failure of the target interface function; the risk level is divided into: H - high risk, M - medium risk and L - low risk; when the risk is H, a red prompt indicates that the risk needs to be reduced.
[0113] F5: Implement new control measures for the high-risk components in F4 and verify the new control measures.
[0114] F6: Assess the risk level of implementing the new control measures in F5 for target interface function failure. Risk levels are divided into: H - High Risk, M - Medium Risk, and L - Low Risk. A green risk (L) is acceptable, and a yellow risk (M) is acceptable.
[0115] As attached Figure 10 The flowchart shown in the figure illustrates the process from boundary / interface analysis of the target object and related objects to risk management in the FMEA system. By combining related structures through interfaces for unified management, the barriers between structures in traditional design and production models are broken down. Interface failure risk management involves further risk analysis and control management of the identified interfaces.
[0116] During the design phase, relevant information can be directly obtained through the interface matrix, making it more convenient to build FME analysis. Furthermore, when managing failure risks through FMEA, multiple related factors can be considered to reduce failure risks.
[0117] Structural code management involves setting structural code codes for internal and external structural components according to the structural disassembly level of the target object, and setting a structural code disabling flag for the structural code codes. The structural code code uniquely identifies the internal structural component of the target object or the external structural component of an associated object.
[0118] As attached Figure 8 The diagram shows a form illustrating structure code management. Structure code management binds structure and interface information; when structure code encoding is disabled, the corresponding structure code becomes invalid, and the structure and interface information is unbound.
[0119] During enterprise operation, structural codes may become unsuitable for the current situation, and new structural codes are usually used. To prevent the old structural codes from being used again (mostly due to misuse) and to facilitate the maintenance of data related to the old structural codes, a disable flag is set to disable the structural codes instead of completely deleting them. This simplifies the operation process, facilitates traceability, and makes management easier.
[0120] The above embodiments are merely illustrative of the technical concept and features of the present invention, intended to enable those skilled in the art to understand the content of the present invention and implement it accordingly, and should not be construed as limiting the scope of protection of the present invention. It will be apparent to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects. The scope of the present invention is defined by the appended claims rather than the foregoing description, and thus all changes falling within the meaning and scope of the equivalents of the claims are intended to be included within the present invention.
Claims
1. A method of managing interfaces inside and outside a boundary of a target object, characterized by, include: S1: Determine the target object and the associated objects that are assembled with the target object; S2: Deconstruct the target object and the associated object to obtain the internal structural components of the target object and the external structural components of the associated object; S3: Structural code management is performed based on the structural decomposition into the internal structural components and the external structural components; S4: Based on the structural relationships between the internal structural components and the structural relationships between the internal structural components and the external structural components, set interfaces to represent the structural relationships and construct an interface matrix; S5: Transmit the interface matrix information to the production operation terminals of the inner structural component and the outer structural component to synchronize the interface information; S6: Perform interface library management and interface failure risk management based on the interface matrix.
2. The method of claim 1, wherein, The process of constructing the interface matrix includes: S31: Analyze the structural relationships between the internal structural components and the structural relationships between the internal structural components and the external structural components; S32: Construct an interface for the inner structural component and the outer structural component that have a structural relationship; S33: Set interface numbers for the internal structural components and the external structural components, and add interface function descriptions to the interface numbers; S34: Based on the internal structural components, the external structural components, and the structural relationships, the interface matrix is generated.
3. The method for managing the internal and external interfaces of a target object boundary according to claim 2, characterized in that, The interface matrix is set as a table, and the row headers or column headers of the table have "structure name" and "internal / external components" respectively; When managing interfaces, the row and column filtering rules are as follows: filter by one of the following: structure name, interface matrix type, or interface type. The content in the nth row and mth column of the table (n>1, m>1, where n and m are both positive integers) contains the interface code and the corresponding structural relationship between the structures in the nth row and mth column.
4. The method for managing the internal and external interfaces of a target object according to claim 2, characterized in that, The structural relationship refers to the assembly connection and functional relationship, and one interface corresponds to and uniquely identifies two structural components. The structural relationships include: physical contact, energy transfer, information exchange, material transfer, and human-machine interaction.
5. The method for managing the internal and external interfaces of a target object boundary according to claim 4, characterized in that, The physical contact connection methods in the structural relationship include welding, bonding, fastening, snap-fitting, plugging, bolting, lubrication, and interference fit; The connection methods for information exchange in the structural relationship include: circuit signal connection, probe signal connection, and pulse signal connection.
6. The method for managing the internal and external interfaces of a target object according to claim 3, characterized in that, Based on the interface matrix, interface management is performed on the target object or the associated object, and all the identified interfaces are summarized and displayed to form an interface library; The interface library displays content including classifying and encoding the interface numbers according to the type of the structural relationship, constructing the interface code, and the interface number corresponding to the structural relationship to which it belongs; Based on the functional relationships identified and displayed in the interface library management, interface failure risk management is performed on the interface.
7. The method for managing the internal and external interfaces of a target object according to claim 6, characterized in that, The interface library construction and management includes: Filter the interface codes and interface function descriptions to construct an interface library matrix, where each interface code corresponds one-to-one with the interface function description. The operation options allow you to edit the interface code and its corresponding function description. The operation categories include modification and deletion. The system automatically saves any edits made to the interface matrix or the interface library matrix and synchronizes the saved changes to all associated interfaces to display the latest interface relationship information.
8. The method for managing the internal and external interfaces of a target object according to claim 6, characterized in that, The structural and interface information of the target object or the associated object is transmitted to the FMEA system. In the FMEA system, failure analysis of the interface is performed and control measures are taken to reduce the design risks caused by the interface. The process of performing interface failure analysis and management includes: F1: Perform interface function analysis based on the interface function description of the target interface; F2: Perform functional failure analysis on the target interface; F3: Set control measures for the failure of the target interface function, and verify the given control measures; F4: Determine the risk level of taking the control measures in F3 for the failure of the target interface function; the risk level is divided into: H-high risk, M-medium risk and L-low risk, and when the risk is H, a red prompt indicates that the risk needs to be reduced; F5: Implement new control measures for the high risks in F4 and verify the given new control measures; F6: Determine the risk level of taking the new control measures in F5 for the failure of the target interface function. It is acceptable when the risk level is L or M.
9. The method for managing the internal and external interfaces of a target object according to claim 1, characterized in that, The structure code management includes: Structural code encoding is set for the internal structural components and the external structural components according to the structural disassembly level of the target object, and a structural code disabling flag is set for the structural code encoding. The structural code encoding uniquely identifies the internal structural component of the target object or the external structural component of the associated object.
10. The method for managing the internal and external interfaces of a target object according to claim 9, characterized in that, Structure code management binds structure and interface information; when the structure code encoding is disabled, the corresponding structure code becomes invalid, and the structure and interface information is unbound.