| IAW Annex A to ATCCIS WORKING GROUP (AWG)2000-1 Minutes | ||||||||||
| BASELINE 1 | ||||||||||
| No. | Class | Title | Edition | Date | Status hardcopy | Status softcopy | Intended Audience | Remarks | Purpose | Overview/Scope |
| AWP ST2 | NU | The Land C2 Information Exchange Data Model | Ed. 2.0 | mar-00 | FC | OK | -Data Modellers -Implemen. |
a. A
description of the common data in an overall model that contains all relevant
data abstracted in a well-structured and normalised way, unambiguously
reflecting their semantic meaning. b. A base document that can be used as a reference for future amendments to the model. ADatP-32 is the configuration management tool for the data model. c. A core upon which nations can base their own modelling efforts of chosen areas and onto which specialized area models can be attached or “hung.” d. A basic document that nations can use to present and validate subfunctional data model views with their own specialist organisations. e. A specification of the physical schema required for database implementation |
The scope of the analysis carried out in the development of the Generic Hub Data Model is principally directed at producing a corporate view of the data that reflects the multinational information exchange requirements for multiple echelons in wartime operations and operations other than war (OOTW). The data model currently tends to focus its scope primarily on the information requirements that support the operations planning and execution activities of a military headquarters or a command post | |
| NU | Data Fill for for Evaluation Cycle 3 i.e. ‘Final-EC3-Data’ | Release 1.0 | mar-00 | UKN | OK | -Data managers -Implemen. |
A data fill to test the AWP ST through the ARM | It consist of 8 different datafill files | ||
| WP 3-1 | NU | Data Naming Procedures for ATCCIS Data Model. | Ed. 3.0 | mar-00 | FC | OK | -Data managers -Data Modellers |
The purpose of this paper is to describe the naming conventions that support the ATCCIS Data Modelling work. The paper is intended to be utilised by those involved in the ATCCIS Data Modelling exercise and assumes that the reader is familiar with the concepts of ATCCIS, data modelling, and IDEF1X in particular. | The naming
conventions proposed in this paper are aimed at supporting the requirements
of the ATCCIS programme. They are
based on the proposal already formulated in ATCCIS Phase II and documented in
Working Paper 7L [Ref. 1]. In this
paper, the fundamental principles of the Working Paper 7L proposal have been
revised to take account of the particular requirements of the current ATCCIS
programme, and experience gained within the nations of applying a structured
naming convention since the publication of Working Paper 7L. It is not the function or intention of
ATCCIS to review and rationalise the various naming proposals currently being
proposed by various external agencies throughout the nations. The ATCCIS naming conventions as specified in this paper apply to logical data modelling only. |
|
| WP 3-6 | NU | ATCCIS Key Management | Ed. 1.0 | mar-00 | FC | OK | -Data
managers -Data Modellers -Implement. |
This paper describes a set of rules, which are to lead to unambiguous world-wide usage of keys for all ATCCIS operational and meta data. Whenever a record is created, the key of that record, which consists of ‘id’ and ‘index’ attributes, must be globally unique. The value that the key of a new record gets must not have yet been used elsewhere already. The rules will ensure this. | This ATCCIS Working Paper defines the common agreement about the initial strategy for the management of data identification keys in ATCCIS | |
| WP 3-7 | NU | Management Guidance for ATCCIS Products | Draft 1.0 | mar-00 | FC | OK | -Data managers -Data Modellers |
In order
to ensure consistency over a longer period of time, data definitions, static
encyclopaedic data, architectural specifications, data exchange meta data and
associated products require adequate management by a competent authority.
The prime objective of this document is to define and describe all aspects related to ATCCIS long term management. Hence its name: ATCCIS Long Term Management Plan (ALTMP). |
The scope for this ATCCIS Long Term Management Plan is depicted in table 1 below. Product maintenance, configuration management, distribution and support are addressed in terms of organisational context, processes and procedures, support environment, technical standards and project guidance. | |
| WP 5-11 | NU | Phase IV Work for the Record | Ed. 1.0 | mar-00 | FC | OK | -Data managers -Data Modellers |
A brief
summary of the process in moving from Information Exchange Requirements
(IERs) to Information Exchange Contracts (IECs) provides the underlying
rationale for much of the contents of this paper.This paper also deals with
materiel that was not accepted or left for further discussion. These topics are: (a) Denormalisation for physical optimisation. (b) Issues of completeness criteria |
This paper
is a compendium of work produced by the Data Group during Phase IV. The paper contains material that does not
readily fit within the scope of other 5-series papers. Some of the material was used in support of
ATCCIS specification development; some of the material was developed to
support the Phase IV evaluation cycle but was not used when alternative
approaches were adopted; some of the material constitutes proposals that were
not accepted; still other material deals with original ideas about topics
that the ATCCIS community must yet face. The purpose is to preserve the work that has been done to date for use or reference in the future. The treatment of the topics that are covered in this paper may serve as a starting point or basis for future development of ATCCIS specifications. |
|
| WP 14-3 | NU | ATCCIS Replication Mechanism (ARM) Consolidated Specification | Ed. 3.0A | jun-00 | FC | OK | -Technical -Implement. |
WP 14
Series. The purpose of the WP 14-x
series of documents is to provide the specification of the ARM to a
sufficient level of detail, precision, and background material to allow
multiple implementations that are interoperable. WP 14-3. The purpose of this paper is to define the specification of the ARM, incorporating background and concepts from WP 14-1 and WP 14-2, and to provide the basis for guidance for implementation teams (e.g., in WP 14-4). |
The WP
14-x series of documents are not the final specification of the ARM for
ATCCIS conformance. The conformance
specification will take into account the lessons learned from development and
testing of prototype systems. Although the prototypes developed for evaluation are not intended to deliver operational systems, the capabilities of the architecture should provide an adequate basis for developing interoperable CCISs in the future. This document contains the specification of the ARM for ATCCIS proof-of-principle evaluations. The specification is a description of the agreement of the ATCCIS Working Group on what is required to be implemented when designing an ARM to guarantee interoperability on automatic data exchange within the ATCCIS concept. |
|
| WP 17-1 | NU | Final Field Test ATCCIS Phase IV | Ed. 1.0 | feb-00 | FC | OK | -Technical -Implement. -Test |
The Final Field Test (FFT) working paper gives guidance and directions for the conduct of the Evaluation Cycle 3 in EDE (NL) in the period of 29 November to 10 December. | The aim for the Evaluation Cycle 3 test is to evaluate the minimum essential operational requirements of the command and control part of the systems using a near operational scenario. | |
| NU | ATCCIS Phase IV Final Report | Draft 1.0 | may-00 | FC | OK | -All | The
primary purpose of this document is to identify the work completed in Phase
IV. This effort included improvements
to Phase III products. The crucial
areas of Phase IV focused on the development and integration of the ATCCIS
Battlefield Generic Hub Level 3 (GH3) Data Model (used to specify meanings
and relationships among data) and the ATCCIS Replication Mechanism (ARM, used
to supplement database management systems for exchanging data) into the
participating country prototypes. The
GH3 and ARM were subjected to interoperability testing and a series of
evaluations (based on an operational scenario), which culminated in a command
post exercise (CPX). In most cases,
details of the work completed in Phase IV are documented in a series of
working papers (WPs) that are referenced rather than excerpted for inclusion
herein. The secondary purpose of this document is to capture the important lessons learned during ATCCIS Phase IV. An additional function of this document is to identify possible areas of future work for the ATCCIS programme. |
The
participants in the Army Tactical Command and Control Information System
(ATCCIS) study are seeking to define the minimum agreements necessary for
nations to achieve Level 5 of System Interconnection of automated command and control
information systems (CCISs), one of the six forms of CCIS interoperability
defined by the Allied Data Systems Interoperability Agency (ADSIA). Interoperability is defined in NATO [Ref.
AAP-6 1993] as the ability of systems to provide services to, and accept
services from, other systems and to use the services so exchanged to enable
them to operate effectively together.
In ATCCIS, interoperability, as a minimum, requires the exchange of
information that preserves meaning and relationships of the information
exchanged. This paper is an overview of significant activities and accomplishments of the ATCCIS project in Phase IV. It highlights the main events in the phase and directs the reader to documentation produced in Phase IV or previous phases for further information. As such, it is not a summary of all technical activities, but an executive summary and tour guide through 2 ½ years of concentrated work by 12 nations and over a hundred people from doctrinal centres, research and development laboratories, and commercial contractor firms. |
||
| CURRENT ATCCIS PHASE III AND PHASE IV DOCUMENTATIO | ||||||||||
| No. | Class | Title | Edition | Date | Status hardcopy | Status softcopy | Intended Audience | Remarks | Purpose | Overview/Scope |
| WP 3-5 | NU | ATCCIS Data Management | 1.0 | Nov-97 | FC | OK | -Data managers -Data modellers |
The
purpose of this working paper is to describe the data management issues that
must be addressed if the ATCCIS concepts for Level 5 interconnection are to
live beyond the end of the ATCCIS study programme. The paper provides a high-level view of ATCCIS Data Management as part of the final ATCCIS Conformance Specification. |
There are
two distinct data management aspects which must be considered in terms of the
successful implementation of a data management policy in support of any
organisation or group of organisations. These are: a. the organisational framework to support data management in a multi-national context; b. the supporting technical procedures and capabilities. For the effective establishment and operation of a data management policy the technical aspects must be defined in terms of the Organisational Framework in which they will be operated. The Phase III data management work has defined a baseline of understanding in terms of: a. a structured naming convention for the attributes of the generic data model; b. the definition of a dictionary structure and supporting functionality to meet the shorter term requirements of the demonstration; c. the population and maintenance of the dictionary in support of the demonstration; d. management and allocation of Data Identification Keys; e. guidance for Physical Implementation of ATCCIS conformant databases. |
|
| WP 4-1 | NU | ATCCIS Information Resource Dictionary (AIRD). Definition of Structure and Contents | 2.0 | Jun-95 | In Phase III FC | OK | -Data managers -Data Modellers |
The purpose of this working paper is to define the structure of the ATCCIS Information Resource Dictionary (AIRD). The AIRD structure is specified in this paper through a logical data model known as a "metadata model" (also called "metamodel") for the information to be retained in the AIRD. The AIRD will serve as the data repository referenced in the ATCCIS Phase III Work Plan. | The ATCCIS
Information Resource Dictionary should contain the essential and pertinent
information from the ATCCIS information modelling efforts plus such
additional information that is deemed to be important to ATCCIS conformancy. As such, the AIRD itself will be a database
with its own conceptual schema defining the structure and the content of the
Information Resource Dictionary. The AIRD described in this paper is specified to the level necessary to support the forthcoming ATCCIS Phase III Demonstration |
|
| WP 4-2 | NU | AIRD Management Procedures | 2.0 | Jun-95 | In Phase III FC | OK | -Data managers -Data Modellers |
This Working Paper describes the procedures that should be followed when managing the AIRD. It describes how to populate and maintain the AIRD. This first chapter provides a global introduction to the AIRD. It concludes with an overview of the remaining document. | The ATCCIS Information Resource Dictionary (AIRD) is a repository of information about the data requirements and recommendations for common meanings and relationships that are deemed essential by the ATCCIS PWG for achieving NIPD Level 5 of System Interconnection among the future command and control information systems of the nations. As a minimum, such interconnection must ensure the exchange of information (with user-imposed constraints) that preserves meanings and relationships (a concept characterised in the ATCCIS Architecture as “basic interoperability”). | |
| WP 4-3 | NU | Data Repository User Manual | 1.0 | Sep-96 | In Phase III FC | In Final Draft jun-96 | -Data managers -Data Modellers |
The purpose of this working paper is to provide guidance to all possible users of the ATCCIS Information Resource Dictionary (AIRD). It is to explain how the AIRD meta database can be utilised by means of the tool ADEF (Automated Data Element Finder), which provides the functionality necessary for viewing and, in special cases, input of meta data about the ATCCIS information analysis results. | The ATCCIS Information Resource Dictionary (AIRD) contains the essential information from the ATCCIS information modelling efforts plus such additional information that is deemed to be important to ATCCIS conformancy. The AIRD itself is a database with its own conceptual schema. | |
| WP 5-5 | NU | ATCCIS Generic Hub 3 Data Model Specification | 3.0 | Jul-98 | In Phase III FC in draft 2.0 dated in nov-96 | OK | -Data Modellers -Implemen. |
WP 5-5
aims to document the Generic Hub 3 in order to provide the following: a. A description of the data that all subfunctional areas have in common. The overall ATCCIS data model contains all ATCCIS relevant data elements, abstracted in a well-structured and normalised way, unambiguously reflecting their semantic meaning. b. A base document against which amendments to the model can be referenced and around which discussions can be based. Working Paper 5-5 is the configuration management tool for the ATCCIS Data Model. c. Implementation of the naming conventions laid out and detailed in WP 3-1, Data Naming Procedures for the ATCCIS Data Model [Ref. ATCCIS WP 3-1 1995]. d. A core upon which nations can base their own modelling efforts of chosen subfunctional areas and onto which specific subfunctional area models can be attached or “hung.” e. A basic document that nations can use to present and validate subfunctional ATCCIS data model views with their own specialist organisations. |
The scope of the analysis carried out in the development of the Generic Hub 3 Data Model is principally directed at producing a corporate view of the data that reflects the multinational information exchange requirements of a multinational or national army headquarters at brigade, division, or corps levels. Furthermore, the data model tends to focus its scope primarily on the information requirements that support the operations planning and execution activities of a military headquarters. | |
| WP 5-6 | NU | Implementation Guidance for Physical Databases based on GH3 | 2.0 | Nov-98 | FC | OK | -Data Modellers -Implement. |
WP 5-6
aims to document the physical schemata for ATCCIS-conformant databases in
order to provide the following: a. Configuration control of the data specifications. b. The physical data model specified in accordance with the Integrated Definition (IDEF) for Information Modelling [Ref. 11]. c. Meta data for the physical schemata, which include for each attribute: (1) Generic data types: integer or real numeric (NUMBER), fixed-length alphanumeric (CHAR), and variable-length alphanumeric (VARCHAR) (2) Number of positions (i.e., length of each valid domain value) and, in the case of a real numeric data type, the number of decimal places (3) Whether a null value is permitted (NULL) or not (NOT NULL). d. Domain values (including physical abbreviations) for all coded (enumerated) domains. e. Rules and guidance for physical schemata to support consistent meaning of data. f. Traceability of the physical schemata to the baseline data model (WP 5-5). g. Reference to the AIRD for definitions and other meta data underlying the physical schemata. |
This
document is one of several specifications required to define the ATCCIS
database structures (schemata). It is
specifically aimed at supporting the implementation of ATCCIS-conformant
systems. The basis for the physical schemata is the ATCCIS Battlefield Generic Hub 3 Data Model (WP 5-5). |
|
| WP 5-7 | NU | ATCCIS Generic Hub Overview | 1.0 | Sep-97 | In Phase III FC | OK | -Data Modellers -Implement. -General |
WP 5-7 provides a broad overview of the model structure and functionality while omitting a significant part of the technical detail that is inherent in explicit data models and is needed for further evolution of the model and its application in systems development. | The scope of the development of the Generic Hub 3 Data Model is the multinational information exchange requirements of a multinational or national army headquarters at brigade, division, or corps levels for operations planning and execution. | |
| WP 5-10 | NU | ADatP-3 Mapping | 1.1 | Jan-99 | FC | OK | -Data Modellers -Procedur. -Implement. |
Draft | The
purpose of this document is to describe general and specific rules that will
have to be taken into consideration when mapping ATCCIS operational
(battlefield) information to ADatP-3 messages and vice versa. The proposed Mapping Rules are based on the comparison of the ATCCIS GH3 (Edition 3.0) [Ref. ATCCIS WP 5-5 1998] and ADatP-3, Baseline 8.1 [Ref. ADatP-3 1992]. |
Considering
the volume of ADatP-3, the spectrum of the mapping efforts has been reduced
to some significant messages. The
present document covers the following three ADatP-3 Message Text Formats
(MTFs): 1. Enemy Situation Report (ENEMY SITREP) 2. Own Land Forces Situation and Presence Report (OWN SITREP) 3. Commanders Logistic Report (CDRLOGREP) |
| WP 5-12 | NU | Data Population Guide for ATCCIS GH3 Data Model | 1.0 | Mar-00 | FC | OK | -Data Modellers -Procedur. -Implement. |
The initial data fill should be done centrally under the control of a data fill manager to assure consistency and uniform approach to data management. National representatives must be designated to participate in this data fill. Once the data has been compiled from available sources, it will have to be validated for completeness and accuracy. While the overall responsibility will be central, the individual Nations will be accountable for the accuracy of nation–specific item and type data. | The
process of generating data entails a number of mechanical steps, as outlined
below, and discussed in the following paragraphs: a. Building a database structure for the target repository b. Creating operational or user data c. Loading data into a database repository |
|
| WP 8-4 Vol. 1 | NU | ATCCIS Phase III Final Report | 1.0 | mar-98 | In Phase III FC | OK | -All | Without number WP 8-4 | ||
| WP 14-1 | NU | ARM Requirements (operational and high-level functional) | 1.0 | Sep-95 | In Phase III FC | OK | -Operat -Engineer |
The purpose of this paper is to specify the agreed operational requirements for the method (not the contents) of information exchange in an ATCCIS environment and to specify the high-level ARM requirements that relate directly to system interconnection. | The requirements in WP 14-1 and the forthcoming specification of WP 14-3 will, therefore, not cover all of the requirements of operational systems (e.g., robustness, availability, survivability, and security). They are aimed at supporting automatic database-to-database replication for the ATCCIS proof-of-concept demonstration in a laboratory environment, while taking into account some of the constraints that apply in an operational environment. | |
| WP 14-2 | NU | ARM Concepts and Models | 2.1 | Mar-98 | FC | OK | -Engineer -Technical |
Draft | The purpose of this paper is to define the concepts of the ARM and their relationships, and to discuss the models that will form the context for stating the specification. | This document contains material on both concepts and models that will ultimately be national implementation issues. This apparent redundancy is necessary to put the ARM in perspective, to define the relations, and to decide the exact boundaries and interfaces between national and international issues. When required, national functionality will be explicitly identified. |
| WP 14-4 | NU | ARM Implementation Guidance | 0.6 | Jul-97 | In Phase III FC in draft 0.57 | OK | -Technical -Implement. |
Draft | The purpose of this paper is to define common interpretations to the specification of the ARM in WP 14-3, with as background WP 14-1 and WP 14-2. | This document contains the implementation agreements associated with the concepts and specification of the ARM for ATCCIS proof-of-principle evaluation. The specification is a description of the agreements of the ATCCIS Permanent Working Group on what is required to be implemented when designing an ARM to guarantee interoperability on automatic data exchange within the ATCCIS concept. |
| WP 14-5 | NU | ARM Pre-Evaluation Test Specification | 1.4 | Nov-98 | FC | OK | -Technical -Test -Implement. |
Draft | The
purpose of this paper is to define the technical tests that will be run for
the ARM in order to prepare for the 1998-1999 period of experimentation and
evaluation for Phase IV. It is planned
to address the following points: a. Standard test installation b. Association Manager tests (1) Full protocol implementation tests (2) Point-to-point ARM connection tests (3) Full ARM network connection test (4) Stress tests c. Replication Manager tests d. ARM Management tests e. Application tests. |
This document contains the implementation agreements associated with testing the features of the ARM |
| WP 15-3 | NU | ATCCIS Phase III - Evaluation Reports | 1.0 | Feb-98 | FC | OK | -All | The purpose of this document is to provide the results of the three Evaluation Cycles that took place during ATCCIS Phase III. | This paper
contains the results of the Evaluation Program in an analysed fashion. The results of each of the three evaluation
cycles will not be individually addressed.
Only the analysed, consolidated results of each of the subsets of the
programme, i.e., the ATCCIS Replication Mechanism (ARM), the Generic Hub 3
data model, and data management rules) will be incorporated herein. a. Each of the three major subsets (ARM, data model and data management rules) will be covered in a separate chapter. b. Network load and bandwidth conservation techniques will be discussed in Chapter 6. c. The Nations were invited to document their lessons learned and recommendations in Chapter 9, if not accommodated elsewhere in the document. d. Forms used during the execution of Evaluation Program are contained in the annexes as a record of tools used. e. A matrix correlating evaluation requirements from WP 15-2 to those items actually evaluated in the program is contained in Annex E. |
|
| WP 16-1 | NU | ATCCIS Phase IV - Evaluation Programme | 0.6 | Feb-98 | UKN | OK | -Engineers -Test |
Draft | The purpose of this paper is to serve as the capstone document for Phase IV of the ATCCIS Programme testing and evaluation activities. | This paper deals with requirements, constraints and overviews testing activities. It is applicable to nations involved in specification activities and also to nations developing ATCCIS-conformant systems, either prototype or fielded. This paper draws requirements from the various disciplines involved in the ATCCIS work (data modelling, data management, replication mechanism, security) into one document. Traceability from these requirements to test events will be maintained in this document. |
| WP 16-2 | NU | ATCCIS Test Plan | 0.9 | Mar-99 | FC as Draft 0.8 | OK | -Test | Draft Title 'ATCCIS Evaluation cycle 1 specification' | The purpose of ATCCIS Working Paper 16-2 is to detail the testing activities that will be conducted in Evaluation Cycle 1 (EC1). | This paper will detail the events, the operator actions, the network topology and the metrics associated with EC1. |
| WP 16-3 | NU | Test Results in support Phase IV | 0.7 | May-99 | UKN | OK | -Test | Draft | This paper will highlight the test program for Phase IV and the first increment of tests for Phase IV. The results of the remote tests and the Interoperability Tests of will be detailed as will the results of Evaluation Cycle 1. | This paper
is produced as the test report for the remote and on-site test periods and
Evaluation Cycle 1 (EC1) in April 99.
As such, it will cover the following activities: - Remote Tests ; (January - February 1999 - Interoperability testing from 25 January to 5 February, 1999; - Remote tests 29 March - 2 April, 1999 - Evaluation Cycle 1 results from 12 April to 23 April, 1999 on-site tests |
| WP 16-4 | NU | Evaluation cycle 2 | 0.4 | Sep-99 | UKN | OK | -Test | Draft | The purpose of ATCCIS Working Paper 16-4 is to detail the testing activities that will be conducted in Evaluation Cycle 2 (EC2). This paper will detail the events, the operator actions, the network topology and the metrics associated with EC2. | The
structure of this paper is to overview the previous testing activities
leading up to this event, then to detail the actual events. Metrics and quality control / configuration
control procedures are also detailed. Requirements and constraints, as well as traceability are covered in WP 16-1. Test environment details are covered in AST/02. The results of this evaluation event will be covered in WP 16-5. |
| AST-01 | NU | ATCCIS Test Plan in support of Phase IV Evaluation cycles | 0.7 | Mar-99 | UKN | OK | -Engineers -Test |
Draft | This paper schedules remote tests, the international on-site Interoperability Test (January - February, 1999) and Evaluation Cycle (EC) 1 in Ede, NL. This paper describes the international test site in Ede, NL. This paper also describes the testing organisation and conduct of tests. | This paper
is produced as the Test Plan for the national, remote, and Interoperability
Test period (currently scheduled for January - February 1999) and Evaluation
Cycle 1 (EC1) in April 99. As such, it
will cover the following activities: a. National tests; b. Remote Tests ; c. Interoperability testing from 25 January to 5 February, 1999; d. Evaluation Cycle 1 environment from 12 April to 23 April, 1999. Note that the actual tests for EC1 are contained in ATCCIS Working Paper 16-2. |
| ACMP | NU | ATCCIS Configuration Management Plan | 4.0 | Mar-99 | FC as Edition 1.0 Jul 99 | OK | -All | |||
| NU | Phase IV ARM Datafill | Release 1.0 | mar-00 | UKN | OK | -Data managers -Implemen. |
A data fill to test the AWP ST through the ARM. | It consist of 3 different datafill files | ||
| NU | ARM Model Domain database | Release 1.0 | mar-00 | UKN | OK | -Data managers -Implemen. |
A reduce version of the AIRD. | Access database containing the ARM and GH4 entities, relationships, domain-values… | ||
| NU | Datagroup CPs & IER | Release 1.0 | mar-00 | UKN | OK | -Data modelers | A data base with the CP,s and IER for the Data S/G | |||