Showing papers on "Concept of operations published in 1997"
TL;DR: The role of a Concept of Operations (ConOps) document in specification and development of a software‐intensive system and its use and benefits, who should develop it, and when it should be developed are described.
Abstract: This paper describes the role of a Concept of Operations (ConOps) document in specification and development of a softwaredintensive system. It also describes the process of developing a ConOps, its use and benefits, who should develop it, and when it should be developed. The ConOps described in this paper is compared to other forms of operational concept documents. A detailed outline for ConOps documents is provided in an appendix to the paper.
37 citations
01 Dec 1997
TL;DR: This paper describes the Integrated Supportability Analysis and Cost System (ISACS+) and the features which will be demonstrated and describes the architecture used to distribute the ISACS+ software over multiple computing tiers in support of the concept of operations.
Abstract: This paper describes the Integrated Supportability Analysis and Cost System (ISACS+) and the features which will be demonstrated. ISACS+ is a distributed, client/server system for evaluating operation and support characteristics of weapon systems and, in future builds, commercial aircraft systems. This tutorial briefly describes the ISACS+ Concept of Operations and how Operation and Support studies are conducted using the ISACS+ tool. This tutorial also describes the architecture used to distribute the ISACS+ software over multiple computing tiers in support of the concept of operations.
5 citations
22 May 1997
TL;DR: It is argued that the idea of nested concepts is an inviolate principle which will be even more critical on the future battlefield.
Abstract: : This monograph argues that the idea of nested concepts is an inviolate principle which will be even more critical on the future battlefield. The primary research question is: will the future battlefield's environment still require nested concepts to enable subordinates at all levels to make sound, timely decisions? This monograph examines past trends in weapons and information technology. These trends are applied to the future to envision the future battlefield environment. Tempo will continue to increase and soldiers will have to make decisions in a time-compressed environment. With smaller and more isolated units, it will be imperative for soldiers to analyze situations, use judgment and take initiative. Even though Force XXI technology will improve situational awareness, a commander's vision is still required to provide the common goal and framework for the organization. Shared vision allows subordinates to exploit opportunities. Nested concepts is a vehicle to communicate the vision throughout an organization. By insuring that the assigned purposes in the concept of operations support the commander's intent, nested concepts secures unity of effort. Nested concepts controls a subordinate's relationship both vertically with his commander and horizontally with his fellow commanders. But it does not control his actions. Implementing the commander's vision through nested concepts will enable subordinates to use their judgment and take the initiative when required to accomplish the common goal.
4 citations
01 Oct 1997
TL;DR: This report provides a description of requirements analysis, state-of-the-art review, technology trends, concurrent virtual machine, cost benefit analysis and case study undertaken and demonstrates the applicability of the proposed concurrentvirtual machine for the design of a terrain masking program.
Abstract: : This final technical report summarizes research accomplished by Bagrodia and Chandy Associates. This 12-month research endeavor, entitled "Concept of Operations for a Virtual Machine for C31 Applications," examined issues in using a concurrent virtual machine for the design of C31 applications, where a concurrent virtual machine is an abstraction of a parallel machine. These issues were evaluated and defined for the purposes of handling concurrency in the design of parallel programs and to facilitate porting a parallel program to multiple architectures. This report provides a description of requirements analysis, state-of-the-art review, technology trends, concurrent virtual machine, cost benefit analysis and case study undertaken. One of the recommendations proposed demonstrates the applicability of the proposed concurrent virtual machine for the design of a terrain masking program.
3 citations
01 Aug 1997
TL;DR: In this paper, a qualitative examination of media access to military operations in light of the new Department of Defense Instruction 5400.14.4, 'Procedures for Joint Public Affairs Operations' is presented.
Abstract: : This study is a qualitative examination of media access to military operations in light of the new Department of Defense Instruction 5400.14.4, 'Procedures for Joint Public Affairs Operations' Based on a review of literature on media access to military operations, an examination of current policies and procedures, as well as a comparative analysis of views presented by media and military representatives, the researcher assesses the efficacy of the new DoD Instruction. The researcher concludes that while the new Instruction is a vast improvement on previous policies that prohibited or severely restricted media access to military operations, there are areas it neglects to address in an adequate manner. These oversights may lead to a recurrence of tensions between the media and the military that existed prior to the implementation of the new Instruction. Media and military members should be apprised of the key concepts of the new DoD Instruction to ensure negation of tensions in the media-military relationship. Members of those institutions should engage in a continuing, proactive dialogue to address future concerns and enhance understanding of each other's requirements and limitations. The military and media should agree on mutually acceptable numerical limitations to future military operations. The DoD should consider using a centralized funding source for equipping joint information bureaus.
1 citations
01 Aug 1997
TL;DR: The requirements which an integrated tool suite will have to meet to provide user's with the desired capabilities are discussed and the technological needs and feasibility of developing an ISEE are addressed.
Abstract: The Tools Integration and Interoperability Working Group (TIWG) is developing a Concept of Operations and a Specification for an Integrated Systems Engineering Environment (ISEE). Last year's TIWG Report (Reference 1) focused on the development of an initial set of scenarios leading toward the development of the full Concepts of Operations. This paper collects the next set of three scenarios which have been developed. The scenarios presented address: (1) the process of defining an organizational systems engineering process; (2) the set of processes associated with administration of an ISEE as part of an organization's information infrastructure; and (3) the process of assessing an organization's systems engineering capability. Based on these process oriented scenarios, we discuss the requirements which an integrated tool suite will have to meet to provide user's with the desired capabilities. The discussion also addresses the technological needs and feasibility of developing an ISEE.
19 May 1997
TL;DR: In this article, the fundamental principles to guide the use of nuclear powered submarines in warfare are outlined, and the operational commander must rely on doctrine to incorporate these tasks into his concept of operations.
Abstract: : How can nuclear powered submarines (SSNs) contribute to joint force protection? Are these submarines essential to a joint force commander's concept of operations? Would their absence significantly alter his branch and sequel plans? Although SSNs represent a significant combat capability, do they possess the necessary range of capabilities to enhance operational protection in a given theater? SSNs can be a force multiplier in the right scenario. 'The modern attack submarine is a versatile multi-mission warship that is more survivable than any other naval vessel in history.' However, just as the special operating forces complement ground troops, SSNs complement the naval forces. SSNs can not accomplish all tasks all the time, but the capabilities they bring to joint force operations can free other forces to act in contributing areas to accomplish the overall mission. This is their forte. The principle missions submarines can perform have grown tremendously from the pre-World War II tasks. These tasks included covert strike warfare, surface warfare, undersea warfare, intelligence collection and surveillance, covert indication and warning, electronic warfare, special warfare, covert mine warfare, and battlegroup support. With so many capabilities available, the operational commander must rely on doctrine to incorporate these tasks into his concept of operations. This paper will attempt to articulate the fundamental principles to guide the use of SSNs in warfare. Just as air superiority against an adversary requires phasing of operations, so does undersea superiority. Submarines can best combine time and space with stealth to help prepare the littoral battlespace for future operations.
07 Feb 1997
TL;DR: In this paper, the authors focus on the sea-based Joint Force Air Component Commander (JFACC) and explore the problems, limitations, and considerations that are faced by seabased JFACC.
Abstract: : The Joint Force Air Component Commander's (JFACC) mission is to command joint air operations based on the Joint Force Commander's (JFC) concept of operations and air apportionment decisions. This is accomplished by planning, coordination, allocation, and tasking of assets. The basic components of the JFACC organization are Combat Plans, Combat Operations, Intelligence, and Communications. The Combat Plans Division includes a Guidance, Apportionment and Targeting (GAT) Cell, an Air Task Order (ATO) Production Cell, and an Air Strategy Cell. The Combat Operations Division includes Current Operations, an Airspace Cell, and an Air Defense Cell. The preceding JFACC organizational functions and relationships have been captured in joint doctrine. The JFACC charter is flexible. It could find itself operating as a part of a naval enabling force conducting presence operations. On the other end of the spectrum, it might participate in a major regional conflict. The following discussion will focus on the sea-based JFACC. It will explore the problems, limitations and considerations that are faced by sea-based JFACC. This will be done illustrating the sea-based JFACC variations that have been developed. Once a picture has been developed of the afloat JFACC executing its mission, the following question will be presented and analyzed: once a crisis matures, how do you smoothly accomplish a transition to the next higher or lower echelon of joint air operations? The discussion will attempt to show that joint doctrine has not completely addressed this question.
01 Dec 1997
TL;DR: A research project identified and prototyped critical elements of an automated development system for interactive courseware (ICW) for job training that incorporated a multimedia database that contained all completed, planned, and partially completed media elements.
Abstract: A research project identified and prototyped critical elements of an automated development system for interactive courseware (ICW) for job training The prototype system incorporated a multimedia database that contained all completed, planned, and partially completed media elements A web-based approach was taken to overcome the problems of platform dependence The system consisted of the following elements: an electronic storyboard that allowed designers to enter data elements as they performed preproduction design and development activities; a media production tool that provided access to and reports from the multimedia database; and a project management tool that provided information to ICW development managers The system definition involved the following steps: (1) capture the concept of operations; (2) document a concise set of requirements; (3) develop a preliminary database architecture; (4) select appropriate system hardware; (5) design the network architecture; and (6) select commercial off-the-shelf software Preliminary use of the system identified additional features that would make the system more useful for ICW development such as a distributed media repository to replace the current database structure; a full-text search capability; an encryption capability; and teaming tools A comparison of the time required to develop one hour of ICW using the automated approach and the traditional approach showed the time was reduced by approximately 30 percent when the automated system was used (YLB) ******************************************************************************** Reproductions supplied by EDRS are the best that can be made from the original document ******************************************************************************** AN APPROACH TO AUTOMATING DEVELOPMENT OF INTERACTIVE COURSEWARE US DEPARTMENT OF EDUCATION Ofti of Educational Research and Improvement ED AT1ONAL RESOURCES INFORMATION CENTER (ERIC) This document has been reproduced as received from the person or organization originating it Minor changes have been made to improve reproduction quality Points of view or opinions stated in this document do not necessarily represent official OERI position or policy Claire S Bartoli Katharine C Goias, PhD Southwest Research Institute San Antonio, Texas ABSTRACT PERMISSION TO REPRODUCE AND DISSEMINATE THIS MATERIAL HAS BEEN GRANTED BY PERMISSION TO REPRODUCE AND DISSEMINATE THIS MATERIAL HAS BEEN GRANTED BY TO THE ATIONAL RESOURCES INFORMATION CENTER (ERIC) Since the early 1970s, the computer-based training industry has grown to the point where most American government agencies and private organizations, and a significant number of international organizations, implement some type of interactive courseware (ICW) in their training programs Some organizations rely solely on ICW to deliver training, while others combine ICW with other delivery methods, such as classroom instruction, on-the-job training, and simulator-based training Historically, the process of developing ICW has been viewed as complicated and risky There are as many documented cases of cost overruns and poor-quality products as there are successful programs However, even with the risks and high costs associated with ICW, it has emerged as the most popular training delivery system within the last 30 years With more powerful computing technologies now available at lower cost, and the emergence of digitial multimedia, the popularity of ICW is increasing It has long been accepted by those who develop multimedia ICW that it is necessary to automate critical aspects of the ICW development process There is less agreement on which aspects should be automated and the approach that should be taken to automation This paper will describe a research project in which critical elements of an automated development system were identified and prototyped The prototype system incorporates a multimedia database which contains all completed, planned, and partially completed media elements A Web-based approach was taken to overcome the problems of platform dependence The system consists of an electronic storyboard tool which allows designers to enter data elements as they perform preproduction design and development activities; a media production tool which provides access to and reports from the multimedia database; and a project management tool which provides information to ICW development managers A comparison of ICW development using the traditional approach and the automated approach with the prototype system was performed The result was a reduction in labor hours of approximately 30 percent using the automated approach