Concept of operations

About: Concept of operations is a research topic. Over the lifetime, 964 publications have been published within this topic receiving 6845 citations. The topic is also known as: CONOPS.

SOS Enterprise, SOSE CONOPS, SOSE Architecture Design Approach: A Perspective on Space and Airborne Systems

Abstract: The objective of this chapter is to (i) define System-of-Systems Enterprise (SOSE), SOSE Concept of Operations (CONOPS), and SOSE Architecture (SOSEA) CONOPS assessment, and (ii) discuss their differences using examples from existing space and airborne systems. The chapter also describes the SOS design challenges and presents an SOSE Architecture design approach addressing these challenges. In addition, DOD Architecture Framework Version 2.02 (DODAF-v2.02) views will be discussed along with a recommendation for a set of key DODAF views to capture system architecture artifacts with practical examples involving SOS Enterprise architectures for notional space-based communications system and manned airborne Intelligence, Surveillance, and Reconnaissance (ISR) platform.

Recent advances in the design of distributed embedded systems

Abstract: The network-centric 'system-of-systems' concept popular in current defense programs has been viewed from a very functional perspective. However, the heart of such a system is going to be an embedded software infrastructure of unprecedented complexity, and the technology for developing and testing this software needs as much if not more immediate attention than the concept of operations for the envisioned applications. Such an embedded software system will need to be infinitely scalable, modular, verifiable, and distributed, yet satisfy the myriad hard real-time performance constraints imposed by each of perhaps many different device types and service demands. It is suggested here that the only path to a robust design methodology for such systems is with model-based design. Model-based embedded system design is the focus of the Model-Based Integration of Embedded Software (MoBIES) program, currently underway at the Defense Advanced Research Projects Agency (DARPA), managed by the author. This paper will motivate the model-based approach to large-scale embedded software design and explain how projects funded under MoBIES are contributing to the development of interoperable model-based design tool components. An application for such technology is provided in the context of digital flight control systems for aggressive aircraft maneuvers, which is the subject of another DARPA sponsored program, Software-Enabled Control (SEC).

A method for evaluating power generation concepts considering the optimal concept of operations

Abstract: ...........................................................................................................................v LIST OF TABLES ................................................................................................................. xii LIST OF FIGURES ............................................................................................................... xiv LIST OF ABBREVIATIONS ................................................................................................. xviii CHAPTER

The Buck Stops Here: Systems Engineering Is Responsible for System Security

Abstract: Who is responsible for systems security? As shown in figure 1, the acquirer (Acq) thinks it is the supplier, the supplier (Sup) delegates that responsibility to systems engineering, who pass it on to system security engineering (SSE), who meet requirements originating with the acquirer. This arrangement results in a finger-pointing circle when security fails. New revisions to the INCOSE Systems Engineering Handbook are integrating responsibility for system security into the systems engineering processes. Placing responsibility on systems engineering is only a first step. A second step requires mutual engagement between systems engineering and security engineering, an engagement that can only be enabled by systems engineering. Systems engineers and program or project managers will be expected to engage effectively throughout the systems engineering processes and activities—beginning with requirements analysis and the concept of operations, and proceeding through the full lifecycle of development, operations, and disposal. The theme articles in this issue of INSIGHT focus on the nature and problems of effective security engineering engagement in critical systems engineering processes. In the end, the acquirer and the supplier must also engage, in a shared responsibility that recognizes and deals with an unpredictable future of security threats. But that is another story, one that cannot be effective until systems and security engineering engagement is achieved.

Examining concept of operations in future plants.

Abstract: This paper will examine the results of this research that focus on future concepts of operations. Our approach was to look at current technological developments in the areas of reactor technology, I&C technology, and human-system integration technology and to make projections into the near and longer-term future concerning their potential impact on human performance. The results were discussed in terms of three aspects of concepts of operations: functional staffing models, plant automation, and training and qualifications. Significant changes to each are anticipated and discussed. Research will be needed to address these changes in order to provide for confidence that changes to concepts of operations are accomplished in ways that maintain public safety.