Research on Command Information System Architecture for Human-Computer Fusion

Architecture frameworks continue to evolve. The Unified Profile for the Department of Defense (DoD) Architecture Framework (DoDAF) and the UK's Ministry of Defence Architecture Framework (MODAF) (UPDM) provides a standard means of representing DoDAF, MODAF, and NATO Architecture Framework (NAF) conformant architectures using the Unified Modeling Language (UML), and Systems Modeling Language (SysML). Since the UPDM V2.0 publication, further information has emerged such as the June 2011 NATO study entitled: “Development of The AMN (Afghanistan Mission Network) Architecture In 2010 – Lessons Learned,” by Torsten Graeber of the NATO C3 Agency. This report identified the following in section 4.1‐ARCHITECTURE FRAMEWORKS, sub‐section 4.1.2 Observations (Need for a Unified Architecture Framework) and stated that:• differences in DoDAF, MODAF, and NAF make it difficult to match the metamodel one to one.• some of the concepts in the frameworks have the same name but different definitions, i.e. different semantics.• difficult to cross‐walk the concepts between the different frameworks leads to miscommunication between architects using different frameworks.Based on the above, the NATO Architecture Capability Team (Architecture CaT) meeting on Sept. 10‐11, 2012 committed to move to a single world‐wide Architecture Framework. Consequently, a new architecture framework profile supporting a unified framework is needed. It is intended that this framework bring the different architecture frameworks together. The UPDM V3.0 domain metamodel shall be derived from MODEM (the MODAF metamodel) and the DoDAF 2.0 metamodel (DM2), both of which are based upon the International Defence Enterprise Architecture Specification Foundation [IDEAS]. This paper will document the rationale behind the UPDM 3.0 as well as its new name of the Unified Architecture Framework (UAF).

The Department of Defense Architectural Framework (DoDAF) is the DoD's mandated method to document system architectures. The current version of DoDAF i.e. v2.02 advocates a data-centric process focused on eliciting data to facilitate decision support. It prescribes a domain ontology i.e. the DoDAF Meta-Model (DM2) aimed at ensuring conformance and interoperability of architecture models. Although DoDAF currently does not prescribe or proscribe specific methodologies or tools, the mismatch between DoDAF's underlying modeling approach and mainstream methodologies and supporting technology in Systems Engineering (SE) has been alluded to in the literature [1-3]. This paper proposes a process for architecting of systems in line with the DoDAF, aimed at bridging this gap. Additionally it offers a discussion of supporting tools in this regard.

The method of architecture is an effective way to analyze the requirements of weapons and equipment. DODAF (U.S. Department of Defense Architecture Framework) is a standard specification issued by the U.S. Department of Defense in 2004 to guide the generation of military equipment requirements. DODAF has been widely recognized as the standard of weapon equipment requirement description. This paper introduces the concepts of DODAF, analyze DoDAF function, structure and problems of DoDAF, and discusses the basic process of weapon loading requirement analysis based on DODAF method, providing a new scientific method for the analysis and research of weapons and equipment requirements.

This paper describes the structure of a concept of the land brigade command information system that is a product of the research work of numerous experts throughout the years done in the then-Yugoslav Army, Army of Serbia and Montenegro and today's Army of the Republic of Serbia. The institution formed for this purpose is the Centre for Command Information Systems and Information Support where command information systems are studied continuously and systematically. Today the KIS represents a primary source needed to obtain an efficient military command management system and an instrument for multiplying combat power without increasing the number of units and combat resources. The KIS is a complex multidisciplinary system requiring the implementation of prototype evolution methodology. Due to its complexity, importance end sensitivity, the KIS has to be realized in one's own military R&D institutions belonging to the Ministry of defense, because only these institutions have adequate knowledge and facilities. Fast and ad-hoc solutions in this area are unacceptable from the military, specialized and economic point of view. The primary KIS br KoV structure concept relies on six types of KIS, five technical subsystems and a number of adequate information systems. The key segment are technical systems that represent one open technical and technological (hardware and software) platform in the realization of any KIS type. The KIS is a dynamic permanent system following the users' needs and technical technology changes. It is not, therefore, a closed and finally defined system, it is the system in continuous evolution, under construction and implementations. Introduction The concept described in this paper is the result of work of numerous people, authors included, engaged in the last twenty years of KIS research. The real balance of forces in combat does not depend so much on the potentials of warring parties but rather on the efficiency of command of combat units as well as of the speed of collecting, analyzing and using information with the main goal to make the optimal decision and make the most of one's own potentials, terrain features and enemy's weaknesses. Command and information systems A general definition of command and information systems is that they are the collection of hardware and software solutions used for real-time integration of all organizational structures, military doctrines, technical and technology systems, information flows and processes aiming at the realization of efficient and rational functioning of the military (units, headquarters, etc.). Basic elements in analyzing command management and command information systems A command information system is an element of the land brigade command system intended for the support of command management in securing and leading complex combat operations. The basic principles of the KIS architecture evolution The key factor is the fact that the KIS is a very complex multidisciplinary system requiring the application of the methodology of prototype evolution together with encompassing human and material resources for better effectiveness. Concept of the land brigade command information system On the basis of long-term research and the obtained experiences with practical solutions, the concept of the KIS br KoV is based on the decomposition model of the military command management system which is decomposed onto functional parts (macro-functions) and command unit operations in real time during combat. Conclusion Command information systems (KIS) today represent the basic instrument for efficient military command management systems rather than an instrument for the multiplication of combat power without increasing the number of units and combat resources. The KIS is a complex multidisciplinary system requiring the application of the prototype evolution methodology.

With the deterioration of battlefield environment, joint combat will become an important mode of operation in the future. In this paper, the Department of Defense Architecture Framework (DoDAF) is studied, the architecture framework design ideas and specific architecture design steps of DoDAF are given, the architecture views involved are described. This paper presents a DoDAF-based modeling method for air-sea joint combat system architecture, which can better describe the operational tasks, information relations among constituent nodes and sub-systems of the complex integrated air-sea joint operation system. This method is often used in the early development stage of complex systems, and enhances consistency understanding between application personnel and system designers and developers.

This chapter focuses on developing system functions from previously defined system capabilities and activities, and how these functions lead to requirements for the system specification. Using the example of a satellite ground system, we demonstrate how the Department of Defense Architecture Framework (DoDAF) system view (SV) aids in defining the requirements necessary for functions such as command and telemetry operations. We also highlight the similarities between the SV and SysML Activity views, showing how these can be useful in transitioning from DoDAF to SysML as part of the overall program/project progression from architecture to system design.

This paper describes a research effort to develop the requirements for a micro-UAV defense system using the Department of Defense Architectural Framework (DoDAF). The goal is to define the system requirements for a security system against a single intruder UAV. The analysis begins with the definition of a potential scenario that is based on an analysis of relevant performance characteristics of commercially available micro UAS. The statement of need finalizes the first step of the requirements process. Based on this the Stakeholder and the system requirements are developed using the DoDAF.

The United States Air Force (USAF) is implementing an integrated net-centric system of systems for airborne operations in support of the global war on terror (GWOT). The GWOT demands that a successful architecture framework transforms and delivers net-centric assets to the war-fighter in a timely manner. A critical component of this implementation is the transformation of legacy strategic air platforms into net-centric air power assets operating within a system of systems. The System Architectural (SA) framework, and the Department of Defense Architectural Framework (DoDAF) are ways of managing complexity and organizing information within a system of systems network. This paper will explore and compare these architectural frameworks; show examples used in a system of systems network; and illustrate how the DoDAF can successfully define the transformation of a legacy weapon system into a net-centric asset.

Modeling Resilience in System of Systems Architecture

One of the ways to capture enterprise knowledge is Enterprise Architecture (EA). EA allows indentifying the majority of software "to-be" requirements for information systems (IS) engineering. However, the transition between enterprise architecture model and IT resource design still lacks a clear approach and tools for implementing it in practice. The paper presents an approach for the enterprise knowledge based software requirements elicitation. The suggested approach is based on the Unified profile for Ministry of Defence Architecture Framework (MODAF) and Department of Defense Architecture Framework (DoDAF), System Modeling Language (SysML) requirements model, and a Semantics of Business Vocabulary and Business Rules (SBVR) standard as a formal background for elicited software requirements. A real world example is presented to validate the suitability of the approach.http://dx.doi.org/10.5755/j01.itc.40.3.626

Properly aligned business and Information Technology (IT) can provide competitive edge to an organization. In order to align business with IT, IT should fully support business operations. Enterprise Architecture (EA) can be used to support business and IT alignment. To help design such systems using EA, Enterprise Architecture Frameworks (EAF) may be used. There are frameworks to support EA, such as Zachman Framework, the Department of Defense Architecture Framework (DoDAF), and The Open Group Architecture Framework (TOGAF). They help to design, evaluate, and build the right architecture and reduce the costs of planning, designing, and implementing [8]. ArchiMate is an open and independent architecture modeling language that complements EAF for modeling and visualizing EA. Regardless of chosen EAF, conversion processes from requirements to EA using ArchiMate are not well-defined to the best of our knowledge. Goal-oriented approach is a requirement analysis technique that supports early requirements analysis, which can be used to define a process for bridging EA requirements to ArchiMate. Therefore,we propose guidelines using goal-oriented approach and then apply them to the interoperability of prescriptions in a healthcare system.KeywordsBusiness ProcessBusiness ServiceEnterprise ArchitectureBusiness ObjectBusiness FunctionThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Chapter 3 - Meeting Industry Standards

Organizational lifecycle (OLC) management encompasses the creation, modification, and exchange of information throughout all phases of production. Although this effort has historically relied on project management (PM), the incorporation of technical personnel promises to increase the accuracy and reliability of the required tasks and deliverables. As organizations rapidly scale their digital footprint, an opportunity to enhance cross-disciplinary communication and collaboration is presented. Leveraging an enterprise architecture (EA) is a relatively new technique that provides a framework across domains including, but not limited to, operations, personnel, resources, and security. In respect to personnel, capturing all relevant information in an accessible repository assists PM with resource allocation based on factors such as the competencies, roles, and responsibilities of individual team members. This paper will evaluate implementation of the Unified Architecture Framework (UAF) for a small company as a real-world case study assessing the potential benefits. The UAF builds on the Department of Defense Architecture Framework (DoDAF) with the intent to include additional domains and viewpoints. In parallel with current trends, the UAF is amenable to model-based systems engineering (MBSE) which supports traceability and re-usability throughout the solution architecture lifecycle phases. Transferring document-based procedures into a virtual environment is not expected to demonstrate significant value. However, the traceability between entities enabled by MBSE will provide insights regarding the human aspect of the OLC so that operational decisions consider the entire organization and downstream effects. Leveraging the UAF to define the internal structure and processes of an organization while acknowledging personnel, the individual needs of employees, and their distinct capabilities demonstrates a progressive approach to human resource management (HRM) by integrating these facets into the holistic architecture.

At present, the configuration of combat system-of-systems (SoS) equipment is highly complex, and the dynamic changes in the states of individual equipment during operations are difficult to predict. Traditional SoS effectiveness evaluation methods are not capable to keep up with these challenges. This study focuses on the OODA (Observation, Orientation, Decision, and Action) operational process, covering different stages such as reconnaissance, intelligence, planning and attacking. First, based on the DoDAF (Department of Defense Architecture Framework), a SoS architecture model is constructed to qualitatively describe the SoS's operational process from multiple perspectives. Second, the ADC (Availability-Dependability-Capability) model is used to calculate the effectiveness of individual equipment. Third, in combination with the Graphical Evaluation and Review Technique (GERT), quantitative calculations are performed to analyze the SoS 's effectiveness. Finally, the contribution of equipment to SoS effectiveness is calculated, as well as the impact of different network architecture in the kill chain on the SoS 's effectiveness, providing guidance for SoS optimization.

In order to satisfy the capability generation requirement of command information system, a load balancing method for service scheduling is studied. Considering that a work which will be finished by command information system based on service-oriented architecture is composed of several jobs, the paper analyzes the work completion process in detail. Then, a method to measure the load on a service which is scheduled to participate in a work is designed. On that basis, a load balancing mathematical model for service scheduling is established and a model solving algorithm that is based on greedy strategy and has polynomial time is put forward. Simulated experimental results show that the method proposed in this paper can allocate load to the services of command information system in a balanced way.