Operational Working Papers 

ATCCIS Baseline 2 does not include any working papers from the Operational Requirements Sub-Group. Operational working papers formed the operational input to the programme and they are incorporated into the technical specifications. Therefore, they are part of the End of Phase Documents.

  WP 18-1 Information Exchange Requirements, edition 5.0, consisting of one file and one Microsoft Access^@ database:

  The purpose is to preserve the work that has been done to date for use or reference in the future. The treatment of the topics that are covered in this paper may serve as a starting point or basis for future development of ATCCIS specifications.

  This paper is a compendium of work produced by the Operational Working Group and a cover paper for the IER database. The paper contains material that gives a global overview of the more detailed contents of the Baseline 2 papers.

  WP 18-2 Flexible Contracting, draft 5.0, consisting of one file:

  A paper by OPS to describe the requirement and benefit of dynamic flexible contracting.

  The ARM referred to previously automatically replicates new or changed data between LC2IEDM nodes. There are two generic options to do that: 1) replicate everything (contract ALL) or 2) define criteria to set the limits of the data to be replicated (contracting and filtering).

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 5-7 Overview of the LC2IEDM, edition 5.0, consisting of one file. 

Use the Document Navigator to find quickly the documents relevant to you.

Sources

   The Operational Working Group is responsible to establish the right source documents in order to accomplish the ATCCIS objectives, and then to extract the minimun information exchange requirements to satisfy the ATCCIS objective.

   The main sources for these objectives were:

    AJP 3.4.1 Peace support operations.

    APP 6 (a) Military symbols for Land based systems.

    APP 9 Compendium for Allied Forces Messages.

    STANAG 2939 Medical requirement for blood, blood donors an associated equipments.

    STANAG 2982 Essential field sanitary requirements.

    STANAG 2399 Battlefield recovery/evacuation operations.

    STANAG 2418 Battle damage repair policy.

Information Exchange Requirements...

Operational Requirement Activities (Phase V)

  The main work for the Operational Requirements Sub-Group (OWG) in Phase IV was the preparing and conducting of  the “Final Field Test” of ATCCIS Phase IV. This work is captured in the  WP 17- 1. 

  For the preparation and conduct of Army-led combined/joint operations, only the requirements for the support of information exchange necessary between HQs (this includes command posts, units, organisations, etc.) of different nations was to be considered in ATCCIS Phase V.

For a description of the "functional" operational requirements go to the right-side notes.

  During Phase V, based on the scope and the operational requirements, the OWG focused on 3 major tasks:

  Develop new Information Exchange Requirements (IER) to support operational requirements for CRO and Army led Combined Joint Task Forces (CJTF) to support operational requirement.

  Participate in the Contract Task Force to investigate the use of flexible contracting in support of operational requirements.

  Participate in the Filter Task Force to investigate the use of filters in support of operational requirement.

  At the end of Phase V the following was achieved:

  New IER’s developed to support CRO and CJTF operations.  All IER’s are captured in WP 18-1 Ed 5.0. 

  The Contract Task Force was cancelled at AWG 3/2000. The OWG was tasked to continue investigating the possibility of doing information management operationally by using flexible contracting. The results are captured in WP 18-2 Draft Ed 5.

  The filter task force work and results are captured in WP 31-1 Draft Ed 5.0.

  The aspiration to incorporate dynamic contracting into replication remains unfulfilled.  The two papers , above, were produced to consider this issue and future work must decide an appropriate response to this lively issue.

  A concept of use for ATCCIS enabled systems is required in order that operational staff can immediately see how best to exploit the power of such systems

The amount of information available for commanders will be growing. To avoid information overload on systems and staffs, tools for effective information management are needed. The concept of Network Centric Warfare is relevant to this.

Requirements

   It is required to support the exchange of operational information between HQs (Command Posts, units, organisations, etc.) independent of command structures.

   It is required to be able to trace the ATCCIS-originator-node of information, in order to avoid the risk of misinterpretation at a receiver HQ as if it were coming from more than one source.

   It is required to support the information exchange necessary for the establishment of situational awareness at HQs involved in Army-led combined/joint operations in War fighting (WF)/ Crises Response Operations (CRO).

   It is required to support the information exchange necessary for the build-up of plans and orders at HQs involved in Army-led combined/joint operations in WF/CRO.

   It is required for the provider and receiver to agree, before and during an ongoing operation, on their information exchange by using a set of predefined information exchange requirements.

   It is required to allow the prioritisation of information exchange between distinct HQs (ATCCIS nodes).

   It is required to support the necessary adaptations in the information exchange pattern ("ATCCIS Network") when a command function moves from one HQ to another (SUCOC).

   It is required to support the exchange of information using only the minimum bandwidth possible.

  14 IERs were provided to support Crisis Response Operations (CRO) and a limited set of 18 IERs to support Combined Joint Task Force (CJTF) operations. 

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. 

Exercises

SHAPE COFS attended to the ATCCIS Final Field Test in EDE (NL in 1999)