Last updated on 26th October 2007                        
© 2005-2007 MIP                                     
You are the visitor number 
                          

Members' Area

Home History Organization Documents Contact

Miscellaneous

You are at:

  Documents > Library

Best viewed at 
1024 * 768

Configuration Control

Any time that changing or updating a particular MIP document is required, a CP must be issued, discussed and approved.

A MIP CP follows the process as depicted on the picture below (click on to enlarge).

CP flow chart.


MIP Glossary

Some definitions.

 Baseline.
A reviewed and approved release of artefacts that constitutes an agreed basis for further evolution or development and that can be changed only through a formal procedure, such as change management and configuration control

 Document.
A document is a collection of information that is intended to be represented on paper, or in a medium using a paper metaphor. The paper metaphor includes the concept of pages, and it has either an implicit or explicit sequence of contents. The information is in text or two-dimensional pictures. Examples of paper metaphors are word processor documents, spreadsheets, schedules, Gantt charts, web pages, or overhead slide presentations.

 Artifact.
Artefacts are either final or intermediate work products that are produced and used during a project. Artefacts are used to capture and convey project information. An artefact can be any of the following:
-. A document, such as Business Case or Software Architecture Document;
-. A model, such as the Use-Case Model or the Design Model;
-. A model element; that is, an element within a model, such as a class, or a subsystem; and
-. Plans, code, test cases, manuals.


Some acronyms.

 MCMP
MIP Configuration Management Plan
 MIP Doc Reg
MIP Document Register
 CMSR
Configuration Management Status  Report
 MOL
MIP Official Library
 CP
Change Proposal
 CN
Change Notice
 RFD
Request For Deviation
 RFW
Request For Waiver


Greding

 You must follow the admin instructions to get access to the WTD-81 and to accommodate in Greding.

 There are several hotels in Greding. Click on the hyperlink for details.

MIP_wtd81map.gif (25789 bytes)
WTD-81

MIP_Greding.jpg (278832 bytes)
Greding


 

Site Map       

Home

MIP News

MIP Concept

Nav & Caveats


History

ATCCIS

Block 1

IOT&E

Baseline 2


Organization

MSG

PMG

Operational

Data Model

Engineering

Test & Eval

Conf Control


Documents

XML 1

XML 2

XML 3

Library


Contact



 Download here

 Acrobat Reader

 

 Contact the

    Webmaster

 

 

 

 

 

 

 

 

 

 

 

 

Technical Articles.

If you are interested in publishing any article which might be of interest for the MIP Community or just for the general audience visiting the MIP pages, take into account the following:

 

Articles must be written in good English.

 
 

Submission of an article does not imply that the work described has not been previously published. It is allowed to publish your work in different forums.

 
 

Upon acceptance of an article, authors will retain the copyright but are authorised to publish it on this Web Site. MIP is not responsible for any further use of the article.

 
 

Authors are strongly encouraged to submit their pages electronically to the  Webmaster.

 
 

Send articles to MIP in electronic format. We accept most word processing format, but Word or PDF are preferred.

 
 

Please include a brief abstract of your paper and a brief biography.

 

* Submission does not imply always publication.

  Index.

 Main chapters of this page are as follows:

2004: "information Engineering.." & C2 Data Models,.."

2003: "Information Interoperability Domains.." & "..performance of military distributed information systems"

2002:"Node to node contracting".

Network Centric Warfare / Network Enable Capability. "Power to the edge" and more.

C2 Interoperability. "Cutting The Gordian Knot".

Technology. "..Multi-Agent System..".


 

 2004.

 

 "Information engineering in support of multilateral joint operational  interoperability "
by
Eric Dorion.

ABSTRACT: Broadly speaking, interoperability can be achieved for systems that sit on top of a single common ontology, or for systems that sit on top of distinct ontologies provided with a means of translation between the crossing domains. An example of the first approach is the Multilateral Interoperability Programme (MIP) that provides a common ontology-oriented solution consisting of the Command and Control Information Exchange Data Model (C2IEDM), supporting land-focused joint military operations. In the next 2-year phase, its focus will expand to full-blown joint military operations. This paper describes the information engineering process (ontological engineering) that must take place in order to successfully achieve both interoperability solutions.

"C2 Data Models, at a crossroads"
by Rafael de Solis.

ABSTRACT: Military C2 systems are at a crossroads where there is a need to decide between the “Global Information Grid” that develops the Network Centric Warfare/ Effect Based Operations concepts, in which the information is conceived as a corporate good available anytime and anywhere; and the traditional conception of the information as an integrating element of each one of the “functions” in which the combat is methodologically divided. In the field of information, the dichotomy comes down between having a common data model for all the battlespace functions, or leaving each one to develop its own model and then to use an exchange model to share the common data.

 

Top


 

 2003.

 

"Information Interoperability Domains"
by Eddie Lasschuyt.

ABSTRACT: Coalition-wide interoperability can be improved considerably by better harmonisation of all major information standardisation efforts within NATO. This notion is supported by the concept of dividing the NATO C3 information area into more or less independent “information interoperability domains”, collections of information systems that interact via a specific standardised exchange language. Since a single information standard (data model) for the entire NATO C3 area is unlikely to be ever achieved, we will inevitably have multiple domains, related to each other by means of some sort of structure. NATO has to play a co-ordinating role in defining the structure, setting the scope for the domains (and hence the information standards) — hereby minimising the overlap — and providing guidelines for the development of these standards in order to assure that translation between the resulting data models is feasible. Within these margins, specific communities of interest should be made responsible for developing these standards independently. This whole approach, including NATO’s intended role, differs from the current way of working, though migration in this direction is not unrealistic. It would be a significant step towards overall interoperability within (and maybe also outside) NATO.

"On the performance of the military distributed information systems"
by
Eric Dorion.

ABSTRACT: This thesis reflects on the problem of ensuring performance in military distributed applications. From the general problem, four sub-problems will be identified and explained. As many solutions to address these will be proposed. The sub-problems are: Military command and control measures of merit for system instrumentation, quality of service and related concepts for guaranteeing performance, CORBA architecture in support to performance and a UML-based methodology to encompass performance modelling efforts.

 

Top


 

 2002.

 

"White paper on node to node contracting"
by MIP Dutch Delegation.

ABSTRACT: The white-paper gives a global description about the way node-to-node contracts can be integrated in the MIP DEM solution in a relative easy yet extensible and flexible way. The goal is to implement node-to-node contract for the MIP IOT&E in 2003 and the tests to prepare for this event. If the white-paper is amended by all nations a Change Proposal (CP) has to be written in order to describe the exact impact on the current MIP specifications.

 

Top


 

 Network Centric Warfare / Network Enable Capability.

 

"Power to the Edge"
by Alberts and Hayes.

ABSTRACT: Power to the Edge articulates the principles being used to provide the ubiquitous, secure, wideband network that people will trust and use, populate with high quality information, and use to develop shared awareness, collaborate effectively, and synchronize their actions. Read Ray Ozzie's Review.

"Complexity Theory and Network Centric Warfare"
by Moffat.

ABSTRACT: Professor Moffat articulates the mathematical models and equations that clearly demonstrate the relationship between warfare and the emergent behaviour of complex natural systems, as well as a means to calculate and assess the likely outcomes.

"The Big Issue"
by Potts.

ABSTRACT: This Occasional considers command and combat in the Information Age. It is an issue that takes us into the realms of the unknown. Defence thinkers everywhere are searching forward for the science and alchemy that will deliver operational success.

"Effects Based Operations- Applying Network Centric Warfare to Peace, Crisis, and War"
by Smith.

ABSTRACT: This third book of the Information Age Transformation Series speaks directly to what we are trying to accomplish on the "fields of battle" and argues for changes in the way we decide what effects we want to achieve and what means we will use to achieve them.

 

Top


 

 C2 Interoperability.

 

"Cutting_The_Gordian_Knot"
by Hamilton.

 

Top


 

 Technology.

 

"Towards a Standardization of Multi-Agent System Frameworks"
by Roberto A. Flores-Mendez.

ABSTRACT: Agents are everywhere. People encounter intelligent agents, information agents, mobile agents, personal assistant agents, and other types of agents daily. One might wonder if it is possible to make some sense of this apparent anarchy: What is it that makes an agent? Is there something that agents have in common? How can one organize them to carry out tasks?

 

Top

 


Technical Articles.
2004. 2003. 2002. Network Centric Warfare / Network Enable Capability.
C2 Interoperability. Technology.


You are at:

  Documents > Library

Best viewed at 
1024 * 768

Members' Area

Home History Organization Documents Contact
Miscellaneous

       
     

 

 

Last updated on 26th October 2007                        
© 2005-2007 MIP                                     
You are the visitor number