scispace - formally typeset
Search or ask a question
Topic

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.


Papers
More filters
Proceedings ArticleDOI
01 Dec 2002
TL;DR: In this paper, the authors proposed a solution to the problem of microwave bandwidth allocation for a mobile, adaptive communication network for the U.S. Army, which is based on a survivable, adaptable network.
Abstract: The Army's objective is to design, develop and demonstrate its 'ability to distribute information around the battlefield.' Future Army systems will be based on a survivable, adaptable network capable of integrating commercial services and securely utilizing bandwidth for voice, data, and video applications. However, microwave bandwidth allocation has been a serious problem (given crosstalk, interference and frequency management) for a mobile, adaptive communication network. Because of the inherent advantages of the high data rate, crosstalk independence, jam - resistance, covertness and quick system setup time, the Army is looking into optical wireless communication as a means to address this communications requirement. However, development of a fielded laser communication system requires the development of enabling technologies, the understanding of physical limits and performance, and concept of operations (CONOPS).

3 citations

Journal ArticleDOI
15 Jul 2017
TL;DR: Owens et al. as mentioned in this paper tailor the format and content that goes into these various aerospace industry ConOps and tailor them into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.
Abstract: An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

3 citations

Book
30 May 2014
TL;DR: In this paper, the authors analyzed the operational effectiveness of three RPA design concepts, plus the MQ-9 as a baseline, on a hunter-killer mission: to find and destroy a specific moving vehicle.
Abstract: : Remotely piloted aircraft (RPAs) notably the medium-altitude MQ-1 Predator and MQ-9 Reaper have provided crucial support to counterinsurgency and counterterrorism operations over the past decade. As these operations come to a close, the Air Force has begun to evaluate additional RPA concepts to meet future needs. In this report, we analyze the operational effectiveness of three RPA design concepts, plus the MQ-9 as a baseline, on a hunter-killer mission: to find and destroy a specific moving vehicle. All the findings in this report are based on the modeling results for a particular scenario (with variants) and should be understood within that context. Although our scenario is representative of many hunter-killer missions as they are executed today, it is not representative of others. It also relies on several crucial assumptions. Most important, the threat environment we modeled is permissive, meaning that there is negligible threat to the aircraft. This permits the use of concepts of operations (CONOPS) untempered by survivability concerns. In the particular scenario we considered, the initial cue for the target vehicle is urgent but imprecise, allowing only that the enemy is expected to emerge from hiding somewhere in a five nmi2 area within 15 minutes. Its ultimate destination is believed to be outside this area but is otherwise unknown. Finding the target vehicle before it leaves the area therefore necessitates a rapid, brute-force search. Because the area is not especially large, the search is not difficult but is complicated by environmental factors. The cued area is an urban environment, which constrains line of sight to steep viewing angles. Moreover, in many of the variants we considered, the RPA sensor operator is forced to contend with other effects detrimental to establishing and maintaining line of sight, including fog and clouds.

3 citations

Proceedings ArticleDOI
TL;DR: An overview of the Model Based Systems Engineering (MBSE) language, tool, and methodology being used in the development of the Operational Plan for Large Synoptic Survey Telescope (LSST) operations is provided.
Abstract: We† provide an overview of the Model Based Systems Engineering (MBSE) language, tool, and methodology being used in our development of the Operational Plan for Large Synoptic Survey Telescope (LSST) operations. LSST’s Systems Engineering (SE) team is using a model-based approach to operational plan development to: 1) capture the topdown stakeholders’ needs and functional allocations defining the scope, required tasks, and personnel needed for operations, and 2) capture the bottom-up operations and maintenance activities required to conduct the LSST survey across its distributed operations sites for the full ten year survey duration. To accomplish these complimentary goals and ensure that they result in self-consistent results, we have developed a holistic approach using the Sparx Enterprise Architect modeling tool and Systems Modeling Language (SysML). This approach utilizes SysML Use Cases, Actors, associated relationships, and Activity Diagrams to document and refine all of the major operations and maintenance activities that will be required to successfully operate the observatory and meet stakeholder expectations. We have developed several customized extensions of the SysML language including the creation of a custom stereotyped Use Case element with unique tagged values, as well as unique association connectors and Actor stereotypes. We demonstrate this customized MBSE methodology enables us to define: 1) the rolls each human Actor must take on to successfully carry out the activities associated with the Use Cases; 2) the skills each Actor must possess; 3) the functional allocation of all required stakeholder activities and Use Cases to organizational entities tasked with carrying them out; and 4) the organization structure required to successfully execute the operational survey. Our approach allows for continual refinement utilizing the systems engineering spiral method to expose finer levels of detail as necessary. For example, the bottom-up, Use Case-driven approach will be deployed in the future to develop the detailed work procedures required to successfully execute each operational activity.

3 citations

Proceedings ArticleDOI
20 Apr 2021
TL;DR: In this article, the conceptual description of the Tactical Separation System (TSS) which design is ongoing in the EU funded project COAST (Cost Optimized Avionics System), under the Clean Sky 2 research and development programme, is presented.
Abstract: This paper provides the conceptual description of the Tactical Separation System (TSS) which design is ongoing in the EU funded project COAST (Cost Optimized Avionics System), under the Clean Sky 2 research and development programme. The TSS is an ADS-B-based advanced self-separation system aimed to extend the traffic situational awareness and to provide the pilot with suggested manoeuvres aimed to maintain the required separation minima. It constitutes not only an enabler for single-pilot operations in SAT vehicles and for the implementation of the separation responsibility delegation to the flight segment in the future SESAR environment, but it also constitutes a step-forward in the framework of the development of Airborne Separation Assurance Systems (ASAS) for Small Aircraft. The TSS receives consolidated traffic picture (position and velocity of all tracks) from the ADS-B receiver and its own position and velocity from the GNSS receiver, all consolidated by dedicated traffic data processing application. Based on this overall information, the TSS perform its main assigned functions, i.e. Conflict Detection and Conflict Resolution. In the paper, a description is first reported of the overall TSS architecture and of its concept of operations. Based on that, an overview of each functionality implemented in the TSS is reported, namely with reference to: Coarse Filtering, Conflict Detection, Severity Assignment, Conflict Resolution and overall TSS Logic. Finally, the design process that is ongoing is outlined and the future developments are indicated.

3 citations


Network Information
Related Topics (5)
Communications system
88.1K papers, 1M citations
69% related
Software
130.5K papers, 2M citations
69% related
Robustness (computer science)
94.7K papers, 1.6M citations
68% related
Radar
91.6K papers, 1M citations
68% related
Control system
129K papers, 1.5M citations
67% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202133
202025
201940
201830
201743
201647