Auldenfire Sweden - News
Enterprise Systems Architecture Laboratory

NAS Information Architecture Committee (NIAC)
(January 24, 2002)
Dynamic Metadata Support in Air Traffic Environments
Technical Briefing

Auldenfire Sweden AB (Stockholm, Sweden) presented an architectural framework approach for metadata designed for Dynamic Metadata Support in Air Traffic Environments before the National Airspace System Architecture Committee on January 24th, 2002. The presentation was provided by Chris de Vaney, Chief Architect for Auldenfire Sweden AB, with responsibility for the Enterprise Systems Architecture Laboratory (ESAL).

Chris de Vaney played a major role in remodeling the Eurocontrol Environment (ENV) Database from a networked to an object-oriented model with constraint logic. He is currently a member of the OMG Analysis & Design task force, working on the Model-Driven Architecture definition, finalization of the Real-Time UML specification, and the next version of the Meta-Object Facility (MOF) for UML. Previous involvement with the OMG included membership and active participation on the OMG's Common Warehouse Metadata Interchange specification team.

Mr. de Vaney began by describing the ESAL project, which basically provides all the services - central repository and directory, messaging, security, workflow, transformations, etc. - and tools needed to let users experiment with different application frameworks and configurations. ESAL has four enterprise architecture frameworks under development now:

  • Financial Management Services, which involves heavy transaction volume and security (and which is being used in the banking industry today)

  • Telecommunications Framework for any telecommunication-type business

  • Data Warehousing, which is a project to look at secure upload of data with publish/subscribe (this uses OMG's data warehouse standards)

  • Air traffic Management, which is being used as a test bed for proving ESAL functionality in information management and security areas and for ATC simulation projects.

The classic notion of metadata, which is "data about data" and pretty much restricted to entity-attribute modeling (e.g. a relational model can produce a static data dictionary), is not sufficient for developing enterprise frameworks like those described above. Different user communities are struggling with this and consequently have produced a number of specialized views and standards for metadata, such as Dublin Core metadata for social sciences, FIXML for financial services, UDDI and SOAP for e-business, etc. Mr. de Vaney contends that a better definition for metadata is that it describes the knowledge, structure, processes and organization of the systems and their content. An enterprise architecture, including an architecture for air traffic management, requires that metadata be established at five levels:

  1. Ontology level - the vocabulary, concepts, definitions and relationships of the subject matter area; the "thesaurus" view. An example of this metadata is an ATC thesaurus and glossary of terms.

  2. Conceptual level - the business environment, its processes, flows, etc. An example is a policy for handling a rejected air traffic message.

  3. Logical level - the application-independent schemas, object library interfaces, functional specifications, component families, infrastructure requirements. This includes defining the way data is stored and how it is processed.

  4. Physical level - the actual databases, components, applications, networks, directories, etc. that will be used in the applications. For instance, the logical level might specify the SQL database and the physical level might specify its implementation in Oracle 9i.

  5. Configuration level - the configuration metadata used in the runtime environment, e.g. load balancing, exception management, object broker configurations, message structures, etc.

As opposed to static informative data dictionaries, this is dynamic metadata. Its artifacts are used not only as models for systems development or for generating code or databases, but also to control information for system configurations (e.g. what to do if a network node is dropped) and runtime support (e.g. directory schemas). Slide #9 is a high-level use case model showing the roles involved in defining each of the above levels, and slides #15-21 show how the ATM Framework is implemented in the ESAL framework, including examples of ontological, conceptual, logical, and physical metadata from this framework. Mr. de Vaney went on to describe and demonstrate examples of how this metadata is being managed and used at the ESAL facility in Stockholm, Sweden (Farsta).

Auldenfire Sweden's ESAL team under the leadership of Chris de Vaney, Chief Architect, has developed detailed metadata describing the generic Air Traffic Environment (over 95 object classes like flight, aircraft, etc. and 1000 attributes, modeled in UML) and from them created views of real-world environments such as the metadata objects describing the Dallas-Fort Worth airport's runways, radars, communications systems, routes, and approach/departure procedures. Other tools such as simulators then use these objects. The ESAL team has implemented platform-independent models developed by Chris de Vaney of core air traffic environment systems and used these to generate platform-specific code - an application of the OMG's model-driven architecture (MDA) approach; see the MDA website at

Auldenfire Sweden's ESAL team is also building a message library in XML based on the ATC business objects and developing a virtual private network between Sweden and New Zealand so that they can link ATC simulation environments. This capability should go into production in March. Mr. de Vaney concluded that the complexity, security, and performance requirements of ATC make it the most challenging of the frameworks developed at ESAL. Future activities include collaboration with the OMG Air Transport Committee (

You can view the slide show presentation here.



Events Calendar
Seminars & Workshops
January 24 2002
Technical Briefing
National Airspace System Information Architecture Committee
Dynamic Metadata Support in Air Traffic Environments
September 19 2001
Legion MDA Software Atelier Workshop Stockholm
September 2001
OMG Technical Meeting Toronto
Auldenfire presents MDA repository whitepaper and architecture overview
August 2001
Legion MDA Software Atelier Pilot Roll-Out
July 2001
OMG Technical Meeting Boston
Auldenfire responsible for content description design models and requirements for platform independent MDA repository

Close Window


Copyright © 2001 - 2007 Aurenav LLC - e-mail: