Data Modelling Products
ATCCIS baseline 2.0 includes several Data Modelling Products . Most of the Data Modelling Products are related to the LC2IEDM.
Some data modelling concepts are explained in the side notes.
WP
5-5
Land C2 Information Exchange Data Model, edition 5.0. It has a
main
body file, an annexes
file, a PDF
file capturing the
Erwin
model, and the ATCCIS Information Resource
Dictionary (AIRD)
database.
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.
The ATCCIS Information Resource Dictionary contains the essential and pertinent information from the ATCCIS information modelling efforts plus such additional information that is deemed to be important to ATCCIS
conformance. As such, the AIRD itself is a database with its own conceptual schema defining the structure and the content of the
LC2IEDM and ARM Management Data Model.
WP 3-6
ATCCIS Key Management, edition 5.0, consisting of one file.
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).
WP 3-1 DATA Naming Procedures for the LC2IEDM Data Model,
edition 5.0, consisting of one file
(see Data Naming in the side notes).
The ATCCIS End of Phase Documents have several Data Modelling Products:
LC2IEDM Change Proposals (CP),
edition 5.0 . As part of WP 5-5, it consists of a set of documents described in the
Readme
file. The Phase 2000 CPs are in an Microsoft
Access@
Database. Also the Change Proposals for Phase III, IV and V in
MS Word zipped files are available
(see Change
proposal in the right-side notes).
ATCCIS Data Subgroup Phase V
Information Exchange Requirements (IER) Databases, edition 5.0.
As part of WP 5-5, it
has one Readme
file and three databases, one for Article
V IER, one for Combined Joint Task Force (CJTF)
IER and one for Crisis Response Operations (CRO)
IER.
Databases of Article 5, CRO & CJTF IERs. The requirements were generated from the Ops subgroup and developed further for Data Group purposes.
WP 5-14 ATCCIS 2000 Phase V Work
for the Record, edition 5.0, consisting of one
file.
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.
You may wish to read these WPs in order to get a concise view of ATCCIS:
ATCCIS Phase V Final Report, edition 5.0, consisting of one
file.
WP 3-13 Guide to Change proposal for ATCCIS Data
specifications, edition 5.0, consisting of one
file.
WP 31-1 ATCCIS Filtering Proposals,
draft 5.0, consisting of one
file.
Use the Document Navigator to find quickly the documents relevant to you.
LC2IEDM
The aim is to provide the following:
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.
A base document
that can be used as a reference for future amendments to the model.
A core model upon
which nations can base their own modelling efforts of chosen areas and
onto which specialised area models can be attached or “hung.”
A basic document
that nations can use to present and validate functional data model views
with their own specialist organisations.
A specification
of the physical schema required for database implementation.
The LC2IEDM is modelled using IDEF1x notation.
This
methodology describes the rules to model the problem's domain as described in Thomas Bruce’s textbook on IDEF1X.
Links to
IDEF1X:
NATO is currently conducting data modelling activities under
the lead of the NATO Data Administration Group (NDAG).
One
task in the work schedule for the development of the “NATO
Corporate Data Model” has been the specification of a
Reference Model, and this Partnership continues.
The development of the present NATO Reference Model
was heavily influenced by previous versions of the ATCCIS Data Model.
Data Managing Activities (Phase V)
LC2IEDM Edition 2
model and its documentation was completed in March 2000
at the end of Phase IV. The model was submitted to NDAG
to serve as the basis for NATO Reference Model as part of
the NATO Corporate DM, and was accepted.
At the Phase V start, a number of Article
V requirements remained unsatisfied by the data model.
In addition, there were a number of outstanding proposals for
model improvements that did not necessarily address a formal
requirement. Two papers that had
been under development in Phase IV were presented to the HoDs for
further consideration. These were the Optimisation Paper
that dealt with data model de-normalisation issues and a paper
that outlined management procedures for processing model change
proposals.
Data and
Operational Groups reviewed and prioritised 172 requirements
remaining from Phase IV work.
The primary goal in
data modelling was to extend the model to incorporate remaining
Article V requirements and the new requirements that were to
be produced by the Operational Group to support aspects of
joint operations and crisis response operations.
Work on Article V
requirements continued during Phase V. In addition, the
Operational Group issued in September 2000 an additional set of
requirements for Crisis Response Operations
(CRO).
In recognition of
changing realities of potential NATO military operations, ATCCIS
Heads of Delegation enlarged the scope in Phase V by adding
requirements for joint interfaces that are needed to support
land operations. The Operational Group issued formal
requirements in March 2001.
Data Group was
engaged throughout the entire phase in attempting to satisfy the
three sets of outstanding requirements, responding to critiques of
the model by NDAG, and processing further proposals for technical
improvements in the model.
The group considered
nearly 200 change proposals of which about 150 were accepted.
A new version of the model that features considerably broadened
functionality was produced. At the end of the phase, 95%
of Article V requirements were satisfied (vice 70% at phase
start). Furthermore, 92% of CRO and 95% of joint
interface requirements had been satisfied.
A small number of
requirements remain unsatisfied. In addition, WP
5-14 lists issues to be considered in the future.
These range in scope from suggestions for improving existing
definitions to substantive changes in the model structure.
The ATCCIS data model, the LC2IEDM, is a rich and powerful model capable of supporting a wide spectrum of military requirements. But it is not a static model. Information requirements evolve and new requirements emerge as the application of military force adapts to new threats. Responsibility for the continued evolution of the LC2IEDM now rests with MIP, which now has custody of the model.
The naming conventions proposed in WP 3-1
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.
In WP 3-1, 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 the 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 apply to logical data modelling only.
The information contained within the validated Data Models
will need to be captured in a data dictionary. The term Data
Dictionary is used within this paper in the context of an ISO Information
Resource Dictionary (IRD). The definition of the information to
be stored in the ATCCIS Information Resource Dictionary (AIRD)
is defined in ATCCIS Working
Paper 4-1. This includes information relating to the entities,
attributes and relationships contained in the IDEF1X data model diagrams
as well as supporting information such as range of attribute values,
entity and attribute descriptions. Both the ERwin tool and the AIRD
must be capable of supporting the proposed naming convention.
Best viewed at 1024 * 768
Choose the appropriate text size in menu-view.
Remarks
Formats remark:
All the hyperlinks
point to the Adobe Acrobat version of each document. In order
to get the Microsoft Word@, Microsoft Access 98@,
Microsoft Excel@ or Erwin 3.5.2@ you will
need to navigate through the Web Site (using for example MS Explorer@
or any FTP client).
Copyrights
are detailed in Home
Page.
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.