Objectives  In order to give full play to role of "operational concepts" in the engineering process of military equipment development, it is necessary to understand and form standardized operational concept documents (OCD), and study the modeling design of OCD in order to implement the transformation of the system engineering process from document-centric to model-centric.

  Methods  This study analyzes the US military's definition of operational concepts and introduces its hierarchical operational concepts, especially the bottom level ConOps or OpsCon, usually as a part of equipment acquisition and requirement engineering. Lessons are then drawn from the relevant theories and standards such as IEEE 29148:2018 and ANSI/AIAA G-043B-2018 of the operational concepts document outline in order to design the specifications of the OCD. Finally, key technologies are studied, including SysML-based OpsCon modeling, UML Profile-based OpsCon framework design and MSDL/C-BML-based operational scenario development.

  Result  The results indicate the effectiveness of implementing the modeling design of OCDs.

  Conclusions  In the process of equipment requirement engineering, the results of this study can help to improve the efficiency of equipment requirement demonstration through an ambiguous operational concept model and an engineering environment for all stakeholders of the system.