| IAW Annex A to ATCCIS WORKING GROUP (AWG) 2000-7 Minutes | ||||||||||
| BASELINE 2.0 | ||||||||||
| No. | Class | Title | Edition | Date | Status hardcopy | Status softcopy | Intended Audience | Remarks | Purpose | Overview/Scope |
| WP 5-5 | NU | LC2IEDM | 5.0 | Mar-02 | FC | OK | -Data Modellers -Implemen. |
The aim is
to provide the following: 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. c. A core upon which nations can base their own modelling efforts of chosen areas and onto which specialised area models can be attached or “hung.” d. A basic document that nations can use to present and validate functional 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 LC2IEDM is principally directed at producing a corporate view of the data that reflects the multinational information exchange requirements for multiple echelons in land-based wartime operations and crisis response operations (CRO) to include joint interfaces that support land operations. The data model is focused primarily on the information requirements that support the operations planning and execution activities of a military headquarters or a command post. | |
| WP5-5 DM | NU | LC2IEDM (ERwin Model) | 5.0 | Mar-02 | FC | OK | -Data Modellers -Implemen. |
The tool
based representation of the LC2IEDM data specification. In case of differences, this will take precedence over WP 5-5. |
ER1 file, created with ErWin 3.5.2. | |
| WP5-5 AIRD | NU | ATCCIS Information Resource Dictionary (AIRD) | 5.0 | Mar-02 | FC | OK | -Data managers -Data Modellers |
Access database that contains definitions, domains, data-types, and other specifications for ATCCIS data models. It supports the LC2IEDM (which is also known as the ATCCIS Data Exchange Schema) and ARM Management Data Model. | 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. | |
| WP3-1 | NU | DATA Naming Procedures for the LC2IEDM Data Model | 5.0 | Mar-02 | 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. |
|
| WP3-6 | NU | ATCCIS Key Management | 5.0 | Mar-02 | FC | OK | -Data
managers -Data Modellers -Implement |
This paper
describes a set of rules, which are to lead to unambiguous worldwide 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 new record
key is assigned must not have yet been used elsewhere already, these rules will ensure that this occurs. In general, ATCCIS key management is based upon the principle of assigning limited sets of allowed values to all key generating organisations (e.g., nations, units, ATCCIS nodes). When these sets have no overlap (and the organisations again apply key management on their own sets), uniqueness of key values is assured. In many aspects this approach is similar to already existing NATO standards, for example, the assignment of unique NATO stock numbers. It must be noted that the ATCCIS key management rules have only one objective, namely making keys unique. The rules are definitely not intended to make the key values traceable by means of possible hidden information inside. |
This ATCCIS Working Paper defines the common
agreement about the initial strategy for the management of data
identification keys in ATCCIS. The present version served as the guide for key management during the ATCCIS Demonstration in 1997 and the ATCCIS Phase IV Command Post Exercise in 1999. It also proved to be a reasonable basis for national development teams building ATCCIS-based systems. The paper is still subject to future investigation on key management. Readers are invited to return any comments they have to the originator. One proposed alternative is included as Annex C. Although applicable to ATCCIS in the first place, the paper is also considered as a possible solution for key management issues in general. It may therefore be used by other (interoperability) programmes as well. |
|
| WP 5-7 | NU | Overview of LC2IEDM | 5.0 | Mar-02 | FC | OK | -Data Modellers -Implement. -General |
The aim is
to provide the following: 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. c. A core upon which nations can base their own modelling efforts of chosen areas and onto which specialised area models can be attached or “hung.” d. A basic document that nations can use to present and validate functional 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 LC2IEDM is principally directed at producing a corporate view of the data that reflects the multinational information exchange requirements for multiple echelons in land-based wartime operations and crisis response operations (CRO) to include joint interfaces that support land operations. The data model is focused primarily on the information requirements that support the operations planning and execution activities of a military headquarters or a command post. | |
| WP 14-3 | NU | ARM Consolidated Specification | 5.0 | Mar-02 | FC | OK | -Technical -Implement. |
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). For ATCCIS 2000 the paper is transformed into a consolidated specification that can be used as Baseline 2.0 document. | This
document 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 for automatic data exchange within the ATCCIS concept. 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. |
|
| WP 14-3 DM | NU | ARM Management Data Model (Erwin Model | 5.0 | Mar-02 | FC | OK | -Technical -Implement. |
The tool
based on representation of the ARM Management Data Model specification In case of differences, this will take precedence over WP 14-3. |
ER1 file, created with ErWin 3.5.2. | |
| WP 14-6 | NU | ARM Management Data-fill | 5.0 | Mar-02 | FC | OK | -Technical -Implement. |
The
purpose of this paper is to provide a detailed description of, and reference
to, a database (known as a data fill) of ARM management data. This database is provided separately as a
Microsoft Access 2000™ file in WP 5-5 AIRD, and the SQL scripts are provided
in Annex B. The document also describes the All Data Contract whose replication domain is the entire LC2IEDM. In case of differences, this will take precedence over AIRD |
This paper will include data instances for all entities contained in the Data Model View of the ARM Management Data Model and the reference data portions of the Replication View of the ARM Management Data Model | |
| ATCCIS END OF PHASE DOCUMENTS | ||||||||||
| No. | Class | Title | Edition | Date | Status hardcopy | Status softcopy | Intended Audience | Remarks | Purpose | Overview/Scope |
| WP 5-5 CP | UN | LC2IEDM Change Proposals (consisting of CP descriptions and a database) | 5.0 | Mar-02 | FC | OK | -Data modelers | Database of all Change Proposals and decisions. It also includes copies of all Approved CPs. | The Change Proposal Data Base contains all change proposals for all modelling issues since January 1997. This period covers Phase III, Phase IV, and Phase V (ATCCIS 2000.) An ACCESS database is used to capture the information about all proposals. Documents describing the proposals, where available, are also attached. In a few cases, there are separate decision documents. | |
| WP 3-13 | UN | Guide to Change Proposal for ATCCIS DATA Specifications | 5.0 | Mar-02 | FC | OK | -Data managers -Data Modellers |
The purpose of this paper is to outline the process of handling proposals to change ATCCIS data specifications that are under configuration control and to stipulate the standards to be followed in documenting the proposals. The procedures followed in the previous phases to evolve the Generic Hub data model varied from informal verbal suggestions to formally documented full-scale change proposals. The procedures worked reasonably well, but experience showed that ad hoc approaches sometimes led to less than optimum results. As the ATCCIS product acceptability and implementation expands and the participant community grows, it is necessary to embrace more formal and rigorous procedures to ensure that the Data Group provides an effective forum for deliberation by all delegates and that operational user requirements result in technically sound data specifications. | The process for managing change proposals involves a two-phase system. The first phase is referred to as the concept phase. It entails an initial suggestion whose acceptability is uncertain. The concept phase permits the Data Group to decide whether a proposed concept for changing model specifications merits further investigation that leads to a specific proposal. The second phase requires a specific proposal that is fully documented for consideration by the Data Group. The two-phase system is intended to avoid expenditure of possibly considerable effort by national delegates to develop a detailed proposal only to see the proposal rejected. | |
| WP 5-14 | UN | Work for the record Phase 5 | 5.0 | Mar-02 | FC | OK | -Data managers -Data Modellers |
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. | This paper is a compendium of work produced by the Data Group during ATCCIS 2000 Phase V. 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 constitutes proposals that were not accepted; still other material deals with original ideas about topics that the ATCCIS community must yet face. | |
| WP 5-5 IER | UN | ATCCIS Data Subgroup Phase 5 IER Databases. | 5.0 | Mar-02 | FC | OK | -Data managers -Data Modellers |
Databases of Article 5, CRO & CJTF IERs. The requirements were generated from the Ops subgroup and developed further for Data Group purposes. | See WP 5-14 Chapter 2. | |
| WP 14-3 CP | UN | ARM open issues (Library) | 5.0 | Mar-02 | FC | OK | -Technical | CPs submitted by Nations to improve ARM Specification but not incorporated in Phase 5. For future consideration. This is a library of Change Proposals (CPs) in Word format supported by an Excel Spreadsheet that tracks progress. | The directory contains all the change proposals (CP) submitted in the Architecture WG during ATCCIS Phase V. The CPs has been divided into four subdirectories according to their status; Approved, In Progress, Proposed and Rejected. | |
| WP 18-1 | UN | ATCCIS Ops Subgroup Information Exchange Requirement. | 5.0 | Mar-02 | FC | OK | -Operat -Engineer |
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. | This paper is a compendium of work produced by the Operational Working Group and a coverpaper for the IER database. The paper contains material that gives a global overview of the more detailed contents of the 5-series (= baseline 2) papers. | |
| WP 18-2 | UN | Dynamic Flexible Contracting | 5.0 | Mar-02 | FC | OK | -Operat -Engineer |
DRAFT | A paper by OPS to describe the requirement and benefit of dynamic flexible contracting. | The ARM referred to previously automatically replicates new or changed data between LC2IEDM nodes. There are two generic options to do that: 1) replicate everything (contract ALL) or 2) define criteria to set the limits of the data to be replicated (contracting and filtering). |
| WP 31-1 | UN | ATCCIS Filtering Proposals | 5.0 | Mar-02 | FC | OK | -Operat -Engineer |
DRAFT | The purpose of this paper is to document the findings of the filter task group and serve as the basis for further development of ATCCIS specifications. | This document presents the approach to analysis, postulates general criteria to be applied to filtering, states what the minimum filter specifications should be, defines data sets for filtering, and provides an overview of the filter types. These include area, time, combination area and time, ORBAT, and combined area and ORBAT. |
| UN | ATCCIS Phase 5 Final Report | 5.0 | Mar-02 | FC | OK | -All | ATCCIS final report and the end of Phase 5 report. | |||