Electromagnetic lock system design method based on MBSE process
Through the electromagnetic lock system design method based on MBSE process, the lack of systematic demand analysis and design process in traditional design methods is solved, and higher design accuracy and reliability are achieved, product compliance is improved and maintenance costs are reduced. .
Patent Information
- Application Number
- CN202411518963.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-02-14
AI Technical Summary
The traditional electromagnetic lock design method lacks systematic demand analysis and design process, which leads to problems such as missing functions and under-compliance of performance in actual applications of the system, and it is difficult to fully consider the mutual influence of various factors.
The electromagnetic lock system design method based on MBSE process is adopted to improve the accuracy and controllability of the system design through refined demand analysis and system architecture design. Specific steps include user requirements analysis and definition, system-level requirements analysis, system architecture design, subsystem architecture extraction, mechanical structure and electronic and electrical analysis, simulation verification, etc.
Through systematic requirements analysis and design process, the accuracy and reliability of the design are improved, design deviations are reduced, the compliance of the final product is improved, and the costs of subsequent commissioning and maintenance are reduced.
Smart Images

Figure CN119442652A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of model-based system engineering, and in particular to a design method of an electromagnetic lock system based on an MBSE process. Background Art
[0002] MBSE, or "Model-Based Systems Engineering", is a specific practice and application of system engineering thinking. It emphasizes the use of modeling technology to describe, design, analyze, verify and confirm complex engineering systems throughout the system life cycle. The system development process is closely centered around requirements. The requirement model connects multiple engineering links such as design and verification in MBSE, playing a key central role.
[0003] With the development of intelligent technology, system engineering is increasingly used in various industries. Under the background of increasing security and controllability requirements, electromagnetic locks, as an important security device, are gradually being used in many fields such as access control systems, smart homes, and commercial facilities. The core function of electromagnetic locks on doors is to control the opening and closing of doors through electromagnetic principles to achieve safe and convenient access control. Therefore, ensuring that the design of electromagnetic locks not only meets user needs but also has high efficiency and reliability has become an urgent problem to be solved in system engineering.
[0004] Traditional electromagnetic lock design methods often rely on experience and simple functional descriptions, lacking a systematic demand analysis and design process. Usually, in the early stages of design, engineers will perform functional definition and preliminary structural design based on the user's verbal description or written requirements. After the design is completed, it often goes directly into the production stage, resulting in problems such as missing functions and substandard performance in actual applications. Traditional methods are particularly insufficient when faced with complex system requirements, and often fail to fully consider the mutual influence of various factors, resulting in designs that do not meet the user's real needs. In addition, traditional methods do not pay enough attention to the verification and simulation links of the design process, which can easily lead to design defects not being discovered in a timely manner, resulting in increased subsequent debugging and maintenance costs. Summary of the invention
[0005] In view of the defects in the prior art, the purpose of the present invention is to provide an electromagnetic lock system design method based on the MBSE process. The present invention is based on the MBSE framework, and through refined demand analysis and system architecture design, the accuracy and controllability of system design are improved to ensure the ultimate realization of the functions and performance expected by users.
[0006] To solve the above problems, the technical solution of the present invention is:
[0007] A design method for an electromagnetic lock system based on an MBSE process includes the following steps:
[0008] Analyze and define user needs, and convert the defined needs into product requirements;
[0009] Perform a thorough analysis of requirements at the system level to ensure that all functional and performance requirements are covered;
[0010] After completing the system requirements analysis, carry out system architecture design and refine the functional and performance requirements;
[0011] After refining the requirements, extract the subsystem architecture;
[0012] Allocate subsystem requirements and perform mechanical structure and electrical and electronic analysis;
[0013] Conduct mechanical structure design and simulation verification;
[0014] Allocate equipment requirements.
[0015] Preferably, the steps of analyzing and defining user requirements and converting the defined requirements into product requirements specifically include: when analyzing and defining requirements at the product level, user requirements must first be determined. After the requirements definition is completed, the defined requirements must be gradually converted into product requirements, and product requirements must be managed in layers, broken down to the system level, and the interface relationships and interaction methods between modules must be clarified so that subsequent system design can proceed smoothly.
[0016] Prioritize using the requirement tracking matrix to record the transformation process of requirements, ensure that each requirement has a clear responsibility module and design document, and ensure the traceability of requirements through the matrix to facilitate verification and modification in subsequent design stages.
[0017] Preferably, the step of comprehensively analyzing the requirements at the system level to ensure that all functional and performance requirements are covered specifically includes: when entering the system requirements analysis phase, it is first necessary to comprehensively analyze the requirements at the system level to ensure that all functional and performance requirements are covered, decompose the requirements into multiple levels by using the hierarchical requirements analysis method, and use the functional decomposition diagram to describe the system in layers, where each level represents a different functional module.
[0018] First, in order to achieve effective collaboration between modules, it is necessary to define the number of models and interface relationships, and use interface control documents to record interface information between modules to ensure smooth information flow.
[0019] Preferably, after completing the system requirement analysis, the system architecture design is carried out, and the steps of refining the functional and performance requirements are specifically included: after completing the system requirement analysis, the system architecture design is carried out to form a function tree and an architecture tree, clarify the functional division of each subsystem, and use the scenario analysis method to decompose the function and architecture to form a functional model and an architecture model, obtain more specific functional requirements through the function tree, and further derive the performance requirements, consider various constraint requirements, and form a complete requirement description of the system.
[0020] Preferably, the step of extracting the subsystem architecture after refining the requirements specifically includes: after refining the requirements, entering the subsystem architecture extraction stage, using the functional decomposition method to refine the system requirements into subsystems, using a hierarchical structure diagram to divide the system into main functional modules in a top-down manner, and further refine them into sub-modules.
[0021] Preferably, the steps of allocating subsystem requirements and performing mechanical structure and electronic and electrical analysis specifically include: after completing the conceptual design, entering the subsystem requirement allocation stage, allocating the obtained product requirements to each subsystem to form subsystem requirements, and after determining the subsystem requirements, it is necessary to determine whether the analysis object involves the mechanical structure or the electronic and electrical part. If it involves the mechanical structure part, a mechanical structure requirement analysis is required; for the electronic and electrical part, dual electrical requirement analysis and design are required to ensure that the system design meets the requirements of each subsystem.
[0022] Preferably, the steps of performing mechanical structure design and simulation verification specifically include: after completing the electronic and electrical requirements analysis, performing mechanical structure design, using the Modelica language to model and simulate the mechanical structure to ensure the rationality and feasibility of the structural design, and using the functional model interface format to perform simulation verification in the detailed stage to ensure the accuracy and feasibility of the design.
[0023] Preferably, the step of allocating equipment requirements specifically includes: allocating subsystem requirements to specific equipment to form equipment requirements, designing and simulating functions and controllers, optimizing models, and ensuring that the equipment can meet the requirements of the overall system.
[0024] Compared with the prior art, the present invention has the following beneficial effects:
[0025] 1. Improve demand accuracy: Through in-depth analysis of user needs, the systematic demand definition and conversion process enables the design team to clearly understand the user's expected functions and performance indicators, thereby reducing design deviations and improving the compliance of the final product.
[0026] 2. Optimize the design process: The present invention divides the system design process into multiple steps and clarifies the output document format in each step. This structured approach enhances the traceability and consistency of the design, ensuring that the design team has clear goals and standards at each stage.
[0027] 3. Enhance system collaboration: During the system architecture design phase, the functional division of labor and interface relationships of each subsystem are clarified through the construction of function trees and architecture trees. This process not only enhances the collaborative working capabilities between modules, but also reduces the potential risks caused by incompatibility between modules, thereby improving the overall reliability of the system.
[0028] 4. Improve verification effectiveness: Through simulation verification in the conceptual design phase, the system modeling language is used to calibrate and evaluate the model, effectively evaluating the feasibility of the design scheme; simulation verification in the detailed design phase further ensures the accuracy and feasibility of the design, identifies and solves potential problems early, and reduces the cost of subsequent debugging and maintenance.
[0029] 5. Flexible response to changes in requirements: Standardized document output and information management mechanisms make changes in requirements during the design process more flexible. During the project implementation, if there are changes in user requirements, the design team can respond quickly and make corresponding adjustments. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:
[0031] Figure 1 It is a flowchart of the electromagnetic lock system design method based on the MBSE process of the present invention;
[0032] Figure 2 It is a detailed flow chart of the electromagnetic lock system design method based on the MBSE process of the present invention;
[0033] Figure 3 A simulation verification flow chart is provided for the concept design of the present invention. DETAILED DESCRIPTION
[0034] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.
[0035] The present invention takes the access control system as a specific embodiment and provides an electromagnetic lock system design method based on the MBSE process. Figures 1 to 3 As shown, the method comprises the following steps:
[0036] S1: Analyze and define user needs, and convert the defined needs into product requirements;
[0037] Specifically, when performing demand analysis and definition at the product level, the user needs must be determined first, and user expectations and performance indicators of electromagnetic lock functions must be collected through questionnaires and interviews, such as the lock's opening and closing time, maximum load, and durability. After clarifying the basic needs, it is necessary to analyze the use scenarios of electromagnetic locks, including possible user operation methods, environmental conditions, and potential safety issues during use. At the same time, a ReqIf format document must be output to record the results of the analysis and provide a basis for subsequent design. In the process of defining requirements, it is crucial to pay attention to the system behavior model. The state transition diagram must be used to describe the changes in the working state of the electromagnetic lock. The formula can be expressed as:
[0038] S next =f(S current ,A)
[0039] Among them, S current is the current state, A is the input operation, S next is the next state. For example, if the current state is "locked" and the input operation is "unlocked", the formula can be used to transfer to the "unlocked" state. Ensure that the design goals are highly consistent with user needs, and ultimately form a clear and traceable requirements document to guide subsequent design and development.
[0040] After the requirements are defined, the product requirements conversion phase begins. In this phase, the requirements defined above are gradually converted into product requirements. The core of this process is to manage and refine the requirements in layers so that effective requirements analysis and architecture design can be performed at the system level. Specifically, the requirements need to be managed in layers, refined to the system level, and the interface relationships and interaction methods between modules need to be clarified so that the subsequent system design can proceed smoothly.
[0041] The interface relationship and interaction mode between modules can be clearly represented by a data flow diagram (DFD), where nodes represent modules and edges represent data flows. For example, the data generated by input module A can be transmitted to module B through interface I, which can be described as:
[0042] Data_A→I→DataB
[0043] This method can clearly demonstrate the relationship between the modules in the system, ensuring that the functions and interfaces of each module can be smoothly connected in the subsequent system design.
[0044] At this stage, the requirement tracking matrix (RTM) can also be used to record the transformation process of requirements to ensure that each requirement has a clear responsibility module and design document. Through this matrix, the traceability of requirements can be ensured, which is convenient for verification and modification in the subsequent design stage. In addition, in order to ensure the consistency and completeness of the design, a consistency check algorithm is used to evaluate each transformed requirement to ensure that it meets the system goals. Through this systematic approach, the risks in the design process can be effectively reduced and the accuracy and controllability of system design can be improved.
[0045] S2: Perform a comprehensive analysis of requirements at the system level to ensure that all functional and performance requirements are covered;
[0046] Specifically, when entering the system requirements analysis phase, it is necessary to first conduct a comprehensive analysis of the requirements at the system level to ensure that all functional and performance requirements are covered. At this point, choosing an appropriate model structure is a key step. The requirements can be decomposed into multiple levels using a hierarchical requirements analysis method to ensure that the complexity of the system can be managed. Specifically, a functional decomposition diagram (FDG) can be used to describe the system in layers, where each level represents a different functional module.
[0047] In order to achieve effective collaboration between modules, the number of models and interface relationships need to be defined. Interface control documents (ICDs) can be used to record interface information between modules to ensure smooth information flow. For example, if module A needs to transfer data to module B, the interface can be defined as:
[0048] Output-A → Input-B
[0049] When choosing a description form or simulation environment, you can rely on model simulation languages (such as SysML) to describe and ensure the visualization and understandability of the model. By setting the initial values of the model parameters and calibrating them, you can provide a reliable basis for subsequent design. The calibration process can optimize the parameters by the least squares method:
[0050] Minimize∑(y observed -y predicted ) 2
[0051] Among them, yobserved is the actual observed value, y predicted The value predicted by the model. By adjusting the model parameters, the predicted value is made as close to the observed value as possible, thereby improving the accuracy of the model.
[0052] Finally, the results of the system requirements analysis are organized into a ReqIf format document to facilitate the subsequent system architecture design and implementation. This document should include a detailed description of all functional and performance requirements, module interface definitions, and model parameters to ensure that all requirements can be effectively met in subsequent designs.
[0053] S3: After completing the system requirements analysis, carry out system architecture design and refine the functional and performance requirements;
[0054] Specifically, after completing the system requirements analysis, the system architecture design is carried out. The main task of this stage is to form a function tree and an architecture tree, clarify the functional division of each subsystem, and use the scenario analysis method to decompose the functions and architecture to form a functional model and an architecture model. In this way, the design team can more clearly understand the functions of each module and its role in the entire system, thereby reducing uncertainty in the design process.
[0055] The next step is to refine the functional and performance requirements. Obtain more specific functional requirements through the functional tree, and further derive performance requirements, consider various constraint requirements, and form a complete requirement description of the system. At this stage, it is very important to output XMI format documents, which can help the team maintain consistency in requirements during the design process and provide reference for subsequent verification work.
[0056] S4: After refining the requirements, extract the subsystem architecture;
[0057] Specifically, after the requirements are refined, the subsystem architecture extraction phase begins. In this phase, the system is divided into several interrelated subsystems to provide a structural basis for subsequent system design. This division not only helps manage the complexity of the system, but also ensures the collaboration and cooperation between the subsystems, thereby optimizing the overall system performance.
[0058] First, the functional decomposition method is used to refine the system requirements into subsystems. In this process, the Hierarchy Structure Diagram can be used to divide the system into main functional modules in a top-down manner, and further refine them into submodules. For example, the electromagnetic lock system can be divided into a control module, a sensor module, and a power module, and each module is further subdivided into specific functions. This hierarchical structure helps to clearly identify the functions and relationships of each module.
[0059] Secondly, in order to achieve effective collaboration between subsystems, the interface of each subsystem needs to be clarified. This can be done by recording the input and output of each subsystem through the interface control document (ICD). For example, the control module needs to receive data from the sensor module and send control signals to the execution module. The interface can be defined as:
[0060] Input_Sensor→Control_Module→Output_Actuator
[0061] At this stage, the performance of the interface needs to be evaluated, and the performance indicator formula can be used:
[0062]
[0063] Among them, P represents performance, W is the amount of work completed, and T is the time taken. By evaluating the response time and data transmission rate of the interface, it is ensured that each subsystem can meet the design requirements when collaborating.
[0064] The extraction of subsystem architecture will form a detailed architecture document, including subsystem division, functional description, interface definition and performance indicators. This document provides a clear blueprint for subsequent detailed design, ensuring the scalability and maintainability of the system, thereby effectively improving the overall efficiency and reliability of system design.
[0065] Finally, simulation verification is performed in the conceptual design phase. Simulation verification in the conceptual design phase is a key step to ensure the rationality of the system design. The simulation verification in the conceptual design phase is mainly based on SysML to obtain a verification model, which can not only be used to evaluate the feasibility of the design solution, but also provide an important basis for the subsequent detailed design. At this stage, the design team needs to conduct a comprehensive evaluation of the design solution to ensure that it can meet all user needs and technical requirements.
[0066] S5: Allocate subsystem requirements and perform mechanical structure and electrical and electronic analysis;
[0067] Specifically, after completing the conceptual design, the subsystem requirement allocation phase is entered, and the obtained product requirements are allocated to each subsystem to form subsystem requirements.
[0068] After determining the subsystem requirements, it is necessary to determine whether the analysis object involves mechanical structure or electrical and electronic parts. If it involves mechanical structure, it is necessary to conduct mechanical structure requirements analysis, first considering the size, parameters, functions and environment of the components. In this process, finite element analysis (FEA) can be used to predict the behavior of components under different load conditions, thereby ensuring the stability and safety of the design.
[0069] When analyzing the behavior under normal and abnormal operation, a probabilistic analysis model can be used to set the failure probability and impact. For example, if the failure probability of a component is P f , then the reliability R of the system can be expressed as:
[0070] R=1-P f
[0071] Through this formula, the design team can evaluate the reliability of the system under specific conditions and ensure the stability and safety of the system in various situations.
[0072] For the electronic and electrical parts, dual electrical requirements analysis and design are required to ensure that the design of the electronic and electrical system meets the overall requirements. This stage includes the detailed design of software and hardware. The software part mainly involves control algorithms, and SysML is used for requirements analysis to ensure that the functional logic is clear and traceable. The hardware part involves multiple disciplines and is described and modeled using the Modelica language. Through modeling, the dynamic behavior of the electrical system can be better understood, and the output model can be used for simulation analysis to verify the rationality of the design. In this process, it is also necessary to output XMI and FMI format files to ensure accurate information transmission during the design process.
[0073] S6: Conduct mechanical structure design and simulation verification;
[0074] Specifically, after completing the electronic and electrical requirements analysis, the mechanical structure design is carried out, and the Modelica language is used to model and simulate the mechanical structure to ensure the rationality and feasibility of the structural design. The output FMI format file provides a basis for subsequent verification.
[0075] After that, the detailed design simulation verification phase begins. The functional mockup interface (FMU) format is used for detailed phase simulation verification to ensure the accuracy and feasibility of the design. The simulation verification of the detailed design not only helps to discover potential problems in the design, but also provides an important basis for subsequent device-level design.
[0076] S7: Allocate equipment requirements.
[0077] Finally, the subsystem requirements are allocated to specific devices to form device requirements. At this time, function / controller design and simulation are carried out to optimize the model to ensure that the device can meet the requirements of the overall system. The goal of this stage is to maximize the function and performance of the device while ensuring the feasibility of the design.
[0078] In summary, the electromagnetic lock system design method based on the MBSE process of the present invention can effectively improve the accuracy and reliability of system design through systematic requirements analysis, design and verification processes, and can provide a solid foundation for subsequent system design through detailed steps and clear document output, ultimately achieving efficient and flexible system development.
[0079] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.
Claims
1. A design method for electromagnetic lock system based on MBSE process, characterized in that: The method comprises the following steps: Analyze and define user needs, and convert the defined needs into product requirements; Perform a thorough analysis of requirements at the system level to ensure that all functional and performance requirements are covered; After completing the system requirements analysis, carry out system architecture design and refine the functional and performance requirements; After refining the requirements, extract the subsystem architecture; Allocate subsystem requirements and perform mechanical structure and electrical and electronic analysis; Conduct mechanical structure design and simulation verification; Allocate equipment requirements.
2. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: The steps of analyzing and defining user requirements and converting the defined requirements into product requirements specifically include: when analyzing and defining requirements at the product level, first determine user requirements, and after the requirements definition is completed, gradually convert the defined requirements into product requirements, manage the product requirements in layers, refine them to the system level, and clarify the interface relationship and interaction method between each module so that subsequent system design can proceed smoothly.
3. The electromagnetic lock system design method based on MBSE process according to claim 2 is characterized in that: Use the requirement tracking matrix to record the transformation process of requirements, ensure that each requirement has a clear responsibility module and design document, and ensure the traceability of requirements through this matrix to facilitate verification and modification in subsequent design stages.
4. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: The steps of comprehensively analyzing requirements at the system level to ensure that all functional and performance requirements are covered specifically include: when entering the system requirements analysis phase, firstly, comprehensively analyzing requirements at the system level to ensure that all functional and performance requirements are covered, decomposing requirements into multiple levels by using a hierarchical requirements analysis method, and describing the system in layers using a functional decomposition diagram, where each level represents a different functional module.
5. The electromagnetic lock system design method based on MBSE process according to claim 4 is characterized in that: In order to achieve effective collaboration between modules, it is necessary to define the number of models and interface relationships, and use interface control documents to record interface information between modules to ensure smooth information flow.
6. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: After the system requirement analysis is completed, the system architecture design is carried out, and the steps of refining the functional and performance requirements are specifically included: after the system requirement analysis is completed, the system architecture design is carried out to form a functional tree and an architectural tree, the functional division of each subsystem is clarified, and the function and architecture are decomposed by using the scenario analysis method to form a functional model and an architectural model, more specific functional requirements are obtained through the functional tree, and performance requirements are further derived, various constraint requirements are considered, and a complete requirement description of the system is formed.
7. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: The step of extracting the subsystem architecture after refining the requirements specifically includes: after refining the requirements, entering the subsystem architecture extraction stage, using the functional decomposition method to refine the system requirements into subsystems, using a hierarchical structure diagram to divide the system into main functional modules in a top-down manner, and further refining them into sub-modules.
8. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: The steps of allocating subsystem requirements and performing mechanical structure and electronic and electrical analysis specifically include: after completing the conceptual design, entering the subsystem requirement allocation stage, allocating the obtained product requirements to each subsystem to form subsystem requirements, and after determining the subsystem requirements, it is necessary to determine whether the analysis object involves a mechanical structure or an electronic and electrical part. If it involves a mechanical structure part, a mechanical structure requirement analysis is required; for the electronic and electrical part, a dual electrical requirement analysis and design is required to ensure that the system design meets the requirements of each subsystem.
9. The electromagnetic lock system design method based on MBSE process according to claim 1 is characterized in that: The steps of mechanical structure design and simulation verification specifically include: after completing the electronic and electrical requirements analysis, mechanical structure design is carried out, modeling and simulation of the mechanical structure are carried out using the Modelica language to ensure the rationality and feasibility of the structural design, and simulation verification of the detailed stage is carried out using the functional model interface format to ensure the accuracy and feasibility of the design.
10. The electromagnetic lock system design method based on MBSE process according to claim 1, characterized in that: The step of allocating equipment requirements specifically includes: allocating subsystem requirements to specific equipment to form equipment requirements, designing and simulating functions and controllers, optimizing models, and ensuring that the equipment can meet the requirements of the overall system.