AIRM Consolidated Logical Data Model Description
Describing the AIRMCLDM
Executive Summary / 03 August 2011
Edition 00.00.01
Project ID 08.01.03.
The AIRM Consolidated Logical Data Model Description provides a textual and illustrative description of the AIRM Consolidated Logical Data Model for modellers and users of AIRM.
Project ID 08.01.03. AIRM Consolidated Logical Data Model Description
Table of Contents
1Introduction
1.1Scope and application
1.2Intended readership
1.3Acronyms and terminology
1.4Adoption
1.4.1Normative
1.4.2Informative
1.5Reading instructions
2AIRM Consolidated Logical Data Model
2.1Introduction
2.2AIRM Consolidated Logical Data Model
3AIRM Consolidated Logical Data Model Description
4References
List of tables
Error! No table of figures entries found.
List of figures
Figure 1 – AIRM Consolidated Logical Data Model
1Introduction
1.1Scope and application
The AIRM Consolidated Logical Data Model Description provides a textual and illustrative description of the AIRM Consolidated Logical Data Model.
1.2Intended readership
The target audience is:
- Modellers contributing to the AIRM
- Users of the AIRM
1.3Acronyms and terminology
Term / DefinitionAIRM / ATM Information Reference Model
ATM / Air Traffic Management
NAF / NATO Architecture Framework
UML / Unified Modelling Language
1.4Adoption
This section describes external documents and other artefacts that, through reference in this text, provide provisions that are considered as normative of this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For each publication a description how it has been adopted/used in this set of documents is also provided.
Note: If a reference is expressed with a date then only that version, of the reference, is valid since it is not possible to guarantee that newer versions, of referenced document, does not adversely impact this document.
1.4.1Normative
The following publications, documents and artefacts are considered as normative:
- SESAR P08.01.03 Project Initiation Report
- NATO Architecture Framework (NAF), v3
- OMG Unified Modelling Language (UML), v2.1
- CONOPS, B4.2 (to be published)
- EAEA Structure and Guidance, B4.1, v00.00.03
1.4.2Informative
There are no informative references.
1.5Reading instructions
There are no specific reading instructions.
2AIRM Consolidated Logical Data Model
2.1Introduction
The AIRM Consolidated Logical Data Model provides a reference model of the SESAR data concepts for service architects and system implementers. It contains the information elements necessary to model the shared information of ATM. This is outlined in Principle 3 of the AIRM Foundation Rulebook:
The AIRM Consolidated Logical Data Model contains definitions of entities that are exchanged by ATM actors. The entities are defined without the consideration of solution, system and implementation aspects.
It can be used in order to construct “derived” logical data models and, indeed, exchange models or physical data models. As such, it can be used to create a model that can be used to build services and operations.
It is best to think of the AIRM Consolidated Logical Data Model in groupings:
- DataTypes
- Abstract
- Subject Fields
The following figure illustrates the relationship between these groupings.
Figure 1 – AIRM Consolidated Logical Data Model
2.2Is this the right model for me?
The AIRM has been structured to satisfy the needs of several different audiences. It is therefore important to look at the parts of the AIRM most suited to the needs at hand.
The following table helps with the decision-making process.
AIRM Information Model / AIRM Consolidated Logical Data ModelPurpose / Operational discourse / Logical interoperability
Audience / Operational experts / Service architects
System implementers
Scope / ATM wide / Information that is exchanged
Tracing / Operational information requirements / AIRM Information Model
NAF v3 notation / NOV-7 Information Model / “of-type” NSV-11a Logical Data Model
Table 1 – Model and Use Matrix
3AIRM Consolidated Logical Data Model Description
3.1Colour coding
The modelis colour coded. Each subject field uses a different colour. The colour codinghas two main goals:
- to help the reader understand which entities belongs to which subject field,
- to highlight dependencies between subject fields where entities have been associated or sub-typed
<to be completed>
To be developed.
4References
Title / Location1 / ATM Lexicon Guidelines /
2 / AIRM Foundation Rulebook / SJU extranet: Project 08.01.03 > Project Execution
3 / AIRMTechnical Standards Profile / SJU extranet: Project 08.01.03 > Project Execution
4 / AIRM Primer / SJU extranet: Project 08.01.03 > Project Execution
31-Aug-2011 16:11 00.00.01
1of 8