CN111142558B - Method and device for capturing system requirements - Google Patents
Method and device for capturing system requirements Download PDFInfo
- Publication number
- CN111142558B CN111142558B CN201911346725.5A CN201911346725A CN111142558B CN 111142558 B CN111142558 B CN 111142558B CN 201911346725 A CN201911346725 A CN 201911346725A CN 111142558 B CN111142558 B CN 111142558B
- Authority
- CN
- China
- Prior art keywords
- interface
- party
- target system
- relationship
- requirements
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 16
- 230000001502 supplementing effect Effects 0.000 claims abstract description 10
- 238000010586 diagram Methods 0.000 claims abstract description 8
- 238000009423 ventilation Methods 0.000 claims description 8
- 238000001816 cooling Methods 0.000 claims description 7
- 238000006243 chemical reaction Methods 0.000 claims description 2
- FGUUSXIOTUKUDN-IBGZPJMESA-N C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 Chemical compound C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 FGUUSXIOTUKUDN-IBGZPJMESA-N 0.000 description 4
- GNFTZDOKVXKIBK-UHFFFAOYSA-N 3-(2-methoxyethoxy)benzohydrazide Chemical compound COCCOC1=CC=CC(C(=O)NN)=C1 GNFTZDOKVXKIBK-UHFFFAOYSA-N 0.000 description 2
- 238000002054 transplantation Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/10—Simultaneous control of position or course in three dimensions
- G05D1/101—Simultaneous control of position or course in three dimensions specially adapted for aircraft
Landscapes
- Engineering & Computer Science (AREA)
- Aviation & Aerospace Engineering (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of aviation, and relates to a method and a device for capturing system requirements. The method comprises the following steps: according to a traditional input/output interface mesh structure diagram, all input/output interfaces of each system are gathered in detail; determining and supplementing the relation of corresponding interfaces according to the type of each interface, and determining the role of each interface corresponding to the system and the roles of other related systems connected with the system; and converting the input/output interface mesh structure chart into a requirement management V-shaped structure according to the relationship of all the interfaces, the roles of the interfaces corresponding to the system and the roles of other related systems connected with the system.
Description
Technical Field
The invention belongs to the technical field of aviation, and relates to a method and a device for capturing system requirements.
Background
The traditional flow chart is in a mesh structure, the interface relationship is complex, although the input/output interface relationship between the system and other related systems can be described more completely, the following aspects are obviously considered: each output interface of the system only considers the 'satisfaction' relationship and does not consider the 'distribution' relationship; for each input relationship of the system, only the allocation relationship is considered, and the satisfaction relationship is not considered.
The emerging demand management technology adopts a V-shaped structure, and can comprehensively consider the two relations of distribution and satisfaction at the same time, but the required capture amount is obviously insufficient, and the workload is huge if the demand capture is carried out from zero.
Disclosure of Invention
The purpose of the invention is: the method and the device for capturing the system requirements comprehensively consider the advantages and the disadvantages of the new technology and the old technology, perform requirement capture from the traditional mesh structure chart, and make up the deficiency of the requirement capture amount in the requirement management V-shaped structure by transplanting all input and output interfaces in the traditional mesh structure chart into the emerging requirement management V-shaped structure.
The technical scheme of the invention is as follows:
the invention provides a system requirement capturing method, which comprises the following steps:
according to a traditional input and output interface mesh structure chart 1, all input and output interfaces 2 of each system are gathered in detail;
determining and supplementing the relation of corresponding interfaces according to the type of each interface, and determining the role of each interface corresponding to the system and the roles of other related systems connected with the system;
and converting the input/output interface mesh structure chart 1 into a requirement management V-shaped structure according to the relationship of all the interfaces, the roles of the interfaces corresponding to the system and the roles of other related systems connected with the system.
Further, the type of the interface comprises an input interface and an output interface; roles include a satisfying party and an allocating party; the relationship includes: "satisfy" relationships and "assign" relationships.
Further, for the ith interface of the target system, i is a positive integer, the relationship of the corresponding interface is determined and supplemented according to the type of each interface, and the role of the system corresponding to each interface and the roles of other related systems connected with the system are determined, including:
taking the ith interface of the target system to perform input/output discrimination 3;
if the interface of the target system is an output interface 4, the relationship of the interface of the target system is a 'satisfaction' relationship, a corresponding 'distribution' relationship 5 is analyzed according to the 'satisfaction' relationship, meanwhile, the target system is set as a satisfaction party 9, and other related systems corresponding to the 'distribution' relationship are set as a proposing party of the target system;
if the interface of the target system is an input interface 6, when the relationship of the interface of the target system is an allocation relationship, analyzing a corresponding 'satisfaction' relationship 7 according to the allocation relationship, and simultaneously carrying out extraction/satisfaction identification 8 on the target system;
when the "distribution" relationship of the target system indicates that the target system puts forward requirements for other corresponding related systems, the target system is set as the proposing party 10; setting other related systems as the satisfaction parties of the target system;
when the distribution relation of the target system indicates that other corresponding related systems put forward requirements for the target system, setting the other related systems as a proposing party; the target system is set to satisfy party 9.
Further, according to the type of each interface, determining and supplementing the relationship of the corresponding interface, determining the role of the system corresponding to each interface and the roles of other related systems connected with the system, and further comprising:
the target system is classified into the top-level system requirement 11 as the requirement of the satisfying party 9; the target system's own requirements for the proposing party 10 are relegated to the system's underlying requirements 12.
Furthermore, the requirements of the target system are classified into top layer requirements and bottom layer requirements, when the top layer requirements are defined as self as the satisfying parties, the requirements of the proposing party corresponding to the satisfying parties on the target system are proposed, and the bottom layer requirements are defined as self as the proposing parties and the requirements of the satisfying parties corresponding to the proposing parties are proposed.
The invention provides a system requirement capturing device, which comprises:
the summarizing module is used for summarizing all input/output interfaces 2 of each system in detail according to a traditional input/output interface mesh structure chart 1;
the determining and supplementing module is used for determining and supplementing the relation of the corresponding interface according to the type of each interface, and determining the role of the system corresponding to each interface and the roles of other related systems connected with the system;
and the conversion module is used for converting the input/output interface mesh structure chart 1 into a requirement management V-shaped structure according to the relationship among all the interfaces, the roles of the interfaces corresponding to the system and the roles of other related systems connected with the system.
Further, the type of the interface comprises an input interface and an output interface; roles include a satisfying party and an allocating party; the relationship includes: "satisfy" relationships and "assign" relationships.
Further, for the ith interface of the target system, where i is a positive integer, determining the supplementary module includes:
a discrimination unit, which is used for taking the ith interface of the target system to perform input/output discrimination 3;
the setting unit is used for analyzing a corresponding distribution relation 5 according to the satisfaction relation if the interface of the target system is an output interface 4, setting the target system as a satisfaction party 9, and setting other related systems corresponding to the distribution relation as a proposing party of the target system; if the interface of the target system is the input interface 6, when the relationship of the interface of the target system is the distribution relationship, analyzing a corresponding satisfaction relationship 7 according to the distribution relationship, and simultaneously distinguishing a provider/a satisfaction provider of the target system 8; and is also used for setting the target system as the proposing party 10 when the "distribution" relationship of the target system indicates that the target system proposes requirements for other corresponding related systems; setting other related systems as the satisfaction parties of the target system; the system is also used for setting other related systems as a proposing party when the distribution relation of the target system indicates that the corresponding other related systems propose requirements for the target system; the target system is set to satisfy party 9.
The invention has the advantages and beneficial effects that: according to the method for capturing the system requirements, the transplantation from the traditional mesh structure chart to the emerging requirement management V-shaped structure is realized by supplementing the 'distribution' or 'meeting' relationship to each input/output interface of the system, the integrity of the requirements is ensured, and the loss and omission of the requirements are avoided; the method for capturing the system requirements is applied to certain airplanes in our hospital.
Drawings
FIG. 1 is a flow chart of the present invention. Wherein: 1 is a traditional input and output interface mesh structure diagram; 2, all input and output interfaces of each system are provided; 3 is input/output discrimination; 4 is an output interface; 5 is an "assignment" relationship; 6 is an input interface; 7 is the "satisfy" relationship; 8 is the presenter/satisfer discrimination; 9, the system is a satisfaction party; 10, the system is a proposing party; 11 is the top requirement of the system; 12 is the system bottom layer requirements; 13 to identify whether the input/output interface between the system and other related systems has been fully analyzed.
FIG. 2a is a schematic diagram of a conventional I/O interface network for a nacelle ventilation cooling system of the type illustrated in the example, wherein: 14 is a nacelle ventilation cooling system; 15 aircraft gross weight specialty; 16 is aircraft general performance specialty; 17 is an exhaust system; 18 is a fire prevention and extinguishing system; 19 is a nacelle drainage system; 20 is an in-cabin accessory system (a heating accessory; 21 is an in-cabin accessory system (a heated accessory; 22 is a nacelle structure system; 23 is an input interface 'the weight of a ventilation cooling system should be less than or equal to 10 kg'; 24 is an input interface 'the highest ambient temperature in the cabin should be less than or equal to 120 ℃'; '25 is an input interface' the maximum radial clearance of an inner exhaust pipe and an outer exhaust pipe should be less than or equal to 20mm ';' 26 is an output interface 'the true value of the total envelope of the cabin ventilation volume is 4.5 kg/s'; '27 is an output interface' the true value of the mixture ratio of oil and gas in the nacelle is 0.02 '; 28 is an input interface' the maximum calorific value of the in-cabin accessory should be less than or equal to 80W ';' 29 is an output interface 'the true value of the ambient temperature in the cabin is 110 ℃'; 30 is an input interface 'the maximum area of the air inlet port surface of the nacelle should be less than or equal to 30cm 2'; and '31 is an output interface' the skin value of the pressure difference between the inside and the outside of the nacelle is 1750 Pa.).
FIG. 2b is the end result of demand capture for a nacelle ventilation cooling system of the type of engine in the example.
Detailed Description
The method for capturing system requirements of the invention is shown in fig. 1, fig. 2 and fig. 2b, and realizes the transplantation from the traditional mesh structure diagram to the emerging requirement management V-shaped structure by supplementing the 'distribution' or 'satisfaction' relationship to each input/output interface of the system; the top-level requirement is defined as the requirement of other related systems to the system (the system is a satisfying party, the bottom-level requirement is defined as the requirement of the system to other related systems (the system is a proposing party; by dividing the requirement into two large categories of the top-level requirement and the bottom-level requirement, each system of the whole machine, regardless of the level and the size, is divided into independent individuals, the interface between the system and the system is clear, please refer to fig. 1, fig. 2 and fig. 2b, which shows a method for capturing the system requirement, and specifically comprises the following steps:
a, step a: aiming at any specific system, according to a traditional input/output interface mesh structure chart 1, summarizing all input/output interfaces 2 between the system and other related systems in detail;
step b: taking any one of all input/output interfaces 2 to perform input/output discrimination 3;
step c: if the output interface is 4, the interface is in a 'satisfy' relationship, at this time, a corresponding 'distribution' relationship 5 needs to be supplemented according to a known 'satisfy' relationship, meanwhile, the system is a satisfying party 9, and other related systems are proposing parties;
step d: if the input interface is 6, the interface is in a distribution relation, at this time, a corresponding 'satisfaction' relation 7 needs to be supplemented according to a known distribution relation, and meanwhile, the system needs to be further subjected to a presenter/satisformer identification 8;
step e: if the system is the satisfying party 9, other related systems are the proposing parties;
step f: if the system itself is the proposing party 10, the other related systems are satisfying parties;
step g: c, classifying the system in the step c and the step e as the system meeting the requirements of the party 9 into a system top requirement 11; the requirements of the system which is the proposing party 10 in the step f are classified into the system bottom layer requirements 12;
step h: and c, judging whether the input and output interfaces of the system are completely analyzed 13, if the interfaces between the system and other related systems are not completely analyzed, returning to the step b, and repeating the steps b to h until the input and output interfaces between the system and other related systems are completely analyzed.
Example (b):
the following describes a method for capturing the demand of a certain type of engine nacelle ventilation cooling system in detail by taking the system as a typical example and combining fig. 1, fig. 2a, fig. 2b and table 1, and comprises the following specific steps:
a, step a: for the nacelle ventilation cooling system 14, all the input/output interfaces 2 between the system 14 and other related systems 15-22 are summarized in detail according to the conventional input/output interface mesh structure diagram shown in fig. 2 a;
step b: taking any one of all input/output interfaces 2 to perform input/output discrimination 3;
step c: if the output interface is 4, the interface is in a 'satisfy' relationship, at this time, a corresponding 'distribution' relationship 5 needs to be supplemented according to a known 'satisfy' relationship, meanwhile, the system is a satisfying party 9, and other related systems are proposing parties;
step d: if the input interface is 6, the interface is in an 'allocation' relationship, at this time, a corresponding 'satisfaction' relationship 7 needs to be supplemented according to the known 'allocation' relationship, and meanwhile, the system itself needs to be further subjected to a presenter/satisformer identification 8;
step e: if the system is the satisfying party 9, other related systems are the proposing parties;
step f: if the system itself is the proposing party 10, the other related systems are satisfying parties;
step g: c, classifying the system in the step c and the step e as the system meeting the requirements of the party 9 into a system top requirement 11; the requirements of the system for the proposing party 10 in the step f are classified into system bottom layer requirements 12;
step h: and (4) judging whether the input and output interfaces of the system are completely analyzed or not 13, if the interfaces between the system and other related systems are not completely analyzed, returning to the step b, and repeating the steps b to h until the input and output interfaces between the system and other related systems are completely analyzed.
TABLE 1
Claims (4)
1. A method for system demand capture, comprising:
aiming at an engine nacelle ventilation cooling system, according to a traditional input and output interface mesh structure diagram (1), summarizing all input and output interfaces (2) of each system in detail;
determining and supplementing the relation of corresponding interfaces according to the type of each interface, and determining the role of each interface corresponding to the system and the roles of other related systems connected with the system;
converting the mesh structure diagram of the input and output interface into a V-shaped structure for demand management as shown in table 1 according to the relationship among all the interfaces, the roles of the interfaces corresponding to the system and the roles of other related systems connected with the system;
TABLE 1
The type of the interface comprises an input interface and an output interface; roles include a satisfying party and an allocating party; the relationship includes: "satisfy" and "assign" relationships;
the method for capturing the system requirement is described in detail in conjunction with table 1 as follows:
taking the ith interface of the target system for input/output identification (3);
if the interface of the target system is an output interface (4), the interface of the target system is in a 'satisfying' relationship, a corresponding 'distribution' relationship (5) is analyzed according to the 'satisfying' relationship, meanwhile, the system is set as a satisfying party (9), and other related systems corresponding to the 'distribution' relationship are set as a proposing party of the target system;
if the interface of the target system is an input interface (6), when the interface of the target system is in an allocation relation, analyzing a corresponding 'satisfaction' relation (7) according to the allocation relation, and simultaneously distinguishing a provider/a provider of the target system (8);
when the 'distribution' relation of the target system indicates that the target system puts forward requirements for other corresponding related systems, the system is set as a pull-out party (10); setting other related systems as the satisfaction parties of the target system;
when the distribution relation of the target system indicates that other corresponding related systems put forward requirements for the target system, setting the other related systems as a proposing party; the system itself is set to the satisfactory party (9).
2. The method of claim 1, wherein the relationship between the corresponding interfaces is determined and supplemented according to the type of each interface, and the role of the corresponding system of each interface and the roles of other related systems connected with the system are determined, further comprising:
the requirements of the system for satisfying the party (9) are classified into the top-level requirements (11) of the system; the requirements of the system itself for the presenter (10) are placed into the system's underlying requirements (12).
3. The method of claim 2, wherein the requirements of the target system are categorized into top requirements and bottom requirements, the top requirements are defined as requirements that a proposing party corresponding to a satisfying party proposes to the target system when the top requirements are defined as the satisfying party, and the bottom requirements are defined as requirements that a proposing party is defined as the proposing party and that the satisfying party corresponding to the proposing party proposes.
4. An apparatus for system demand capture, comprising:
the system comprises a summarizing module, a network interface module and a network interface module, wherein the summarizing module is used for summarizing all input and output interfaces (2) of each system in detail according to a traditional input and output interface mesh structure diagram (1);
the determining and supplementing module is used for determining and supplementing the relation of the corresponding interface according to the type of each interface, and determining the role of the system corresponding to each interface and the roles of other related systems connected with the system;
the conversion module is used for converting the input/output interface mesh structure chart (1) into a demand management V-shaped structure as shown in a table 1 according to the relationship among all the interfaces, the roles of the interfaces corresponding to the system and the roles of other related systems connected with the system;
TABLE 1
The type of the interface comprises an input interface and an output interface; roles include a satisfying party and an allocating party; the relationship includes: "satisfy" and "assign" relationships;
for the ith interface of the target system, i is a positive integer, and with reference to table 1, determining the supplementary module includes:
the judging unit is used for taking the ith interface of the target system to carry out input/output identification (3);
a setting unit, which is used for taking the ith interface of the target system to carry out input/output identification (3); if the interface of the target system is an output interface (4), the relationship of the interface of the target system is a 'satisfaction' relationship, a corresponding 'distribution' relationship (5) is analyzed according to the 'satisfaction' relationship, meanwhile, the system is set as a satisfaction party (9), and other related systems corresponding to the 'distribution' relationship are set as a proposing party of the target system; if the interface of the target system is an input interface (6), when the interface of the target system is in an allocation relation, analyzing a corresponding 'satisfaction' relation (7) according to the allocation relation, and simultaneously distinguishing a provider/a provider of the target system (8); when the 'distribution' relation of the target system indicates that the target system puts forward requirements for other corresponding related systems, the system is set as a pull-out party (10); setting other related systems as the satisfaction parties of the target system; when the distribution relation of the target system indicates that other corresponding related systems put forward requirements for the target system, setting the other related systems as a proposing party; the system itself is set to the satisfactory party (9).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911346725.5A CN111142558B (en) | 2019-12-24 | 2019-12-24 | Method and device for capturing system requirements |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911346725.5A CN111142558B (en) | 2019-12-24 | 2019-12-24 | Method and device for capturing system requirements |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111142558A CN111142558A (en) | 2020-05-12 |
| CN111142558B true CN111142558B (en) | 2023-03-14 |
Family
ID=70520082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911346725.5A Active CN111142558B (en) | 2019-12-24 | 2019-12-24 | Method and device for capturing system requirements |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142558B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106950980A (en) * | 2017-04-18 | 2017-07-14 | 南京航空航天大学 | A kind of small-sized fixed-wing unmanned plane guidance computer and method of guidance |
| CN108594715A (en) * | 2018-05-18 | 2018-09-28 | 赫星科技有限公司 | Unmanned plane master control borad |
| CN108628335A (en) * | 2016-03-02 | 2018-10-09 | 成都飞机工业（集团）有限责任公司 | A kind of course heading control method of all-wing aircraft unmanned plane |
| CN109871635A (en) * | 2019-03-05 | 2019-06-11 | 中国航空综合技术研究所 | Run-time scenario modeling method towards the capture of civil aircraft top-level demands |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2990529B1 (en) * | 2012-05-11 | 2021-09-10 | Thales Sa | PROCESS AND DEVICE FOR CAPTURING THE NEED FOR A CENTRALIZED MAINTENANCE SYSTEM FOR AIRCRAFT |
| US9678506B2 (en) * | 2014-06-19 | 2017-06-13 | Skydio, Inc. | Magic wand interface and other user interaction paradigms for a flying digital assistant |
| WO2016100601A2 (en) * | 2014-12-17 | 2016-06-23 | Picpocket, Inc. | Drone based systems and methodologies for capturing images |
| CA3012049A1 (en) * | 2016-01-20 | 2017-07-27 | Ez3D, Llc | System and method for structural inspection and construction estimation using an unmanned aerial vehicle |
| CN110032200A (en) * | 2019-04-19 | 2019-07-19 | 成都飞机工业（集团）有限责任公司 | A kind of modeling method for Capability Maturity Model of taking a flight test |
-
2019
- 2019-12-24 CN CN201911346725.5A patent/CN111142558B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108628335A (en) * | 2016-03-02 | 2018-10-09 | 成都飞机工业（集团）有限责任公司 | A kind of course heading control method of all-wing aircraft unmanned plane |
| CN106950980A (en) * | 2017-04-18 | 2017-07-14 | 南京航空航天大学 | A kind of small-sized fixed-wing unmanned plane guidance computer and method of guidance |
| CN108594715A (en) * | 2018-05-18 | 2018-09-28 | 赫星科技有限公司 | Unmanned plane master control borad |
| CN109871635A (en) * | 2019-03-05 | 2019-06-11 | 中国航空综合技术研究所 | Run-time scenario modeling method towards the capture of civil aircraft top-level demands |
Non-Patent Citations (2)
| Title |
|---|
| 基于 MBSE 的舰载无人机飞控系统架构研究;尧伟文;《中国优秀博硕士学位论文全文数据库 工程科技Ⅱ辑》;20180315;正文第1-51页 * |
| 面向行业的商品化管理信息系统框架构建与方法研究;吴士亮;《中国优秀博硕士学位论文全文数据库 社会科学I辑》;20051115;正文第1-148页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111142558A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108229015B (en) | Variable working condition matching design method for high-altitude two-stage turbocharger | |
| CA2785327A1 (en) | System and method for automated building services design | |
| CN111142558B (en) | Method and device for capturing system requirements | |
| CN106446325B (en) | Design method of aircraft fuel system | |
| CN104299068B (en) | Aobvious control information management system and the method for cockpit based on ARINC661 | |
| CN109582702B (en) | Post-hoc data processing system and method based on aircraft measurement and control | |
| CN107391550A (en) | A kind of report form generation method and system based on big data mould plate technique | |
| CN107220780A (en) | Heterogeneous task Perform sequence optimization method in mass-rent system | |
| CN110043484B (en) | Two-stage high-load fan design method based on circumferential vorticity through-flow design | |
| CN114547877A (en) | Extreme boundary-based ultra-large bypass ratio turbofan engine optimization design method | |
| CN111163149A (en) | Intelligent contract platform method based on block chain | |
| CN113343494B (en) | Aircraft engine bearing cavity thermal performance simulation calculation model correction method | |
| CN114221983A (en) | Method and device for determining key path of energy Internet of things physical and information system | |
| CN115600436A (en) | Automatic response method for natural gas pipeline operation scheme | |
| CN116151755B (en) | Personnel information intelligent evaluation analysis system | |
| CN105426481A (en) | Data processing method and device | |
| CN203052035U (en) | Connection hoop flange structure with plane metal ring seal | |
| CN102546809A (en) | Unified control method of large-scale server cluster | |
| CN116176842A (en) | Cooperative use method and device for airplane cold source | |
| CN106364663B (en) | Aircraft air condition component cabin | |
| CN112304107B (en) | Operating system for intelligent lifting engineering of roasting furnace | |
| CN106095476B (en) | A kind of newly-increased Component service method based on heat | |
| CN108225779B (en) | Diesel engine standard air inlet air conditioner comprehensive utilization system | |
| CN204880740U (en) | Online air exhaust device of vacuum hot water condensing vapour gas separation for unit | |
| CN111429040A (en) | Optimized deployment method for metering equipment of building energy consumption detection system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |