MIP Public Home

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

Members' Area

Home

History

Organization

Documents

Contact

Miscellaneous

You are at:

Organization > MIP Operational Working Group

Best viewed at
1024 * 768

Membership

Membership of the MIP may be as Full Members or Associate Members.

Only nations are eligible to become Full Members of the MIP.

Full Members are nations that commit to support the collaborative development of succeeding versions of the MIP interoperability solution suitable for fielding. To be a Full Member, a nation must agree to meet the requirements listed in the MIP Programme Management Plan. In addition a Full Member must express an intention to field the MIP solution.

Full Members undertake to be represented in all WGs and must be prepared to expend the resources required. Full Members have voting and access rights at all meetings.

Associate Members include nations and non-nation entities showing an interest in this programme that have been granted Associate Member status by the MSG. Associate Members are entitled to have the same rights and privileges as Full Members but do not have the right to vote on decisions within the Programme.

Application

The official request to become a member shall be made by formal written proposal that must be endorsed by a current MIP Full Member.

This Full Member becomes the sponsoring member and assumes the responsibility for forwarding the endorsed application to all other Full Member MSG HoDs.

The application must include a statement on the status of involvement in a C2IS, the nature of interest in the MIP, and an agreement to abide by MSG/PMG decisions.

The PMG as an empowered body will, at the next available opportunity consider the application for membership as presented by the sponsoring member. On unanimous agreement, the PMG will issue direction to the host member to extend an invitation to the applicant to attend the next MSG.

MIP & NATO

NATO Force Goals (EL2802, Land & ER2802, Marine Forces) calls for the implementation of the MIP solution by NATO Nations.

The JC3IEDM is already the STANAG 5525 currently under ratification. The NATO Corporate Data Model (STANAG 5523 / ADatP-32) does not exist any longer.
*STANAG (Standard Agreement)

MIP liaises closely with NATO, and NATO has a Policy on MIP that allows MIP to easily conveys its specifications into NATO.

The MIP specification is included in the NATO C3 Technical Architecture.

The NATO Military Criteria for High Readiness Forces (Land) Headquarters requires the use of an MIP (ATCCIS) conformant land information system.

Many national C2 information systems implement MIP specifications.

The Bi-SC Automated Information System will use the MIP solution in its Land Functional Services to interface to national C2IS, either in HRF/LRF, CJTF, NRF or other crisis response operation or exercise.

MIP Integrated Operational Test & Evaluation (Sep 03)

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

MIP Operation Working Group (OWG)

The OWG represents the "operational" layer of MIP. It gathers the experience of multiple international SMEs in military operational matters from MIP Member Nations and Organizations. This page tells its main features.

Features.

Aim, Responsibilities & Activities. What is the OWG purpose and mission?

Members & Decision Procedures. OWG gathers Operational SMEs from Members.

Meetings & Chairmanship. How many OWG meetings are held?

Main products. Documents produced by OWG.

Aim, Responsibilities & Activities.

The OWG is the working group performing in MIP the operational modelling discipline with support from the Systems Engineering and Architecture Working Group (SEAWG) and the Data Modelling Working Group (DMWG). The purpose of that discipline is to model the relevant aspects of the C2IS (operational level) to the MIP solution.

The OWG identifies and model the operational information needs, specifies the operational requirements and develops the MIP solution’s operational structure, behaviour and performance.

The OWG also develops the operational test cases that will be used to validate the MIP solution as well as defines elements of risk and risk mitigation alternatives.

Most important OWG tasks regarding Operational Requirements are:

		To identify user/operational requirements to support C2IS interoperability at the levels of command from Corps to Battalion, or lowest appropriate level, in order to support multinational, combined and joint operations.
		To identify and prioritise IERs in order to achieve both horizontal and vertical exchange of information as well as recommend change proposals on existing IERs
		To define business rules for horizontal and vertical information exchange.
		To define the concept of use for the developed fieldable solutions.
		To identify and take heed of lessons learned from other interoperability initiatives and deployments.
		To provide user and operational guidance to other MIP WGs through the PMG in the development/ execution of the MIP work plan and ensure that the C2IS Solution Package meets operational requirements.

Most important OWG tasks regarding Operational Validation are:

		To define Measures of Success (effectiveness and performance) for operational tests and validation (OLT).
		To define operational test cases and scenarios for operational tests and validation (Operational Level Test, OLT for short)

OWG establishes and maintains liaison with relevant doctrinal and operational organisations such as LOWG, SLIERP, Symbology Panel, APP-9/APP-6A Harmonization Sub-Panel.

* More comprehensive list may be found in MPMP, Annex C (OWG ToRs).

Top

Members & Decision Procedures.

Each Full Member use to send at least one representative to the OWG. In addition, representation from interested organisations participating, or interested in deploying a MIP solution package (HQ ARRC, HQ EUROCORPS, EUROFOR, etc) and otherwise not an Associate Member, may be invited to attend. The MSG takes the decision on this regard.

Decisions and Action Items are made by unanimous agreement, of all national representatives or their empowered representatives. Where unanimity is not achieved, the OWG Chair may raise the issue to the PMG for resolution. Decisions are made among equals.

Top

Meetings & chairmanship.

The OWG normally meets four times per year, concurrently with the other MIP WGs. Other meetings may be called at the request of any Member of the OWG.

The MSG designates a member to provide the OWG Chairman following a review of nominations. The MSG also designates a Deputy Chairman from a different Nation. If a member is unable to provide a chairman, the MSG asks another member to provide one.

The WG meeting forecast is included in the MIPS.

Top

OWG main products.

The OWG devotes most of its effort basically to produce official MIP documents such as:

		MTIR (MIP Tactical C2IS Interoperability Requirements) which analyse in deep the Operational and IE requirements. The most important OWG product.
		MOH (MIP Operational Handbook) which specifies how the MIP solution must be used operationally.
		MOP (MIP Operational Procedures) which specifies the procedures to set up, run and keep the MIP solution working.

A close cooperation with the DMWG assures a correct interpretation of IERs when they are modelled.

Have a look at mentioned documents in "Documents" page

* Not all MIP documents are published in MIP Public Area.

Top

MIP Operation Working Group (OWG)
Aim, Responsibilities & Activities. Members & Decision Procedures.
Meetings & Chairmanship. Main products.