100 SOW (Acquisition) Annex A - Part B - Operational and ...



operational and support concept document

(self propelled howitzer (sph))

Table of Contents

1 Introduction 1

2 mission overview 5

3 mission essential functions 8

4 mission system Organisation 8

5 common mission system Scenario attributes 12

6 generic mission SYSTEM scenarios 13

7 system constraints 16

8 system solution description 18

9 Support Concepts 19

Introduction

1 Aim

1 The aim of the Operational and Support Concept Document (OSCD) is to provide a basis for common understandings by all stakeholders and system developers. It details the following in relation to the Mission System and Support System:

1 Describes the characteristics from and operational perspective,

2 Facilitates an understanding of the overall system goals, and

3 Details missions and scenarios associated with operation and support of the Indirect Fire System (IFS).

2 Mission System. The Mission System is that element of the capability that directly performs the operational function. For LAND 17 the Mission System is considered to consist of Battle Management System-Fires (BMS-F), Delivery Platforms and modular charge systems. The delivery platforms shall be based on the two platform capabilities as endorsed at Government First Pass, that is, SPH and lightweight towed howitzers.

3 Support System. The Support System is the organisation of hardware, software, material, facilities, personnel, technical data, processes and services required to enable the Mission System and the Support System to be effectively supported so that the Mission System can meet its operational requirements. The Support System embraces the Commonwealth, In-Service contractors and In-Service subcontractors.

2 Purpose

1 LAND 17, Artillery Replacement Project, seeks to enhance the indirect fire support capability of the ADF. The project will replace and enhance Army’s Indirect Fire System (IFS). Specifically, the LAND 17 Mission System will address the tactical joint fires artillery command and control system (BMS-F) and delivery platforms requirements of the IFS. The project will also meet the various integrated logistic support (ILS) requirements including training support, facilities and all aspects of Through Life Support (TLS).

3 System Boundary.

1 The five sub-systems of the IFS are:

1 Ammunition,

2 Target Acquisition,

3 Command and Control,

4 Delivery Platforms, and

5 Combat Service Support.

2 Each of these subsystems is applicable to the IFS although the extent to which they are impacted by LAND 17 will vary. LAND 17 will seek enhanced performance by either replacement or enhancement of each sub-system (or elements within it). Specifically for the ammunition sub system enhancement will be through increased range provided by increased calibre and chamber capacity in the delivery platform and its associated modular charge system. For the Target Acquisition sub system; Joint Offensive Support Team (JOST) target location, designation and digital terminal control devices will be acquired, however, other Target Acquisition devices such as the Weapon Locating Radar (ANTQP 36), Ground Surveillance Radar (AMSTAR) will not be acquired.

4 Acquisition Boundary

1 LAND 17 is to interface with existing and planned enhancements to ADF capability. These are detailed below. In particular, LAND 17 will not seek to acquire:

1 General natures of artillery ammunition (these will be acquired under the Medium Artillery Replacement Ammunition Project (MARAP)).

2 New target acquisition systems (except for Forward Observer target location and designation devised and digital terminal devices as outlined above), although it is accepted that the legacy or planned target acquisition systems will be integrated into the capability to be delivered by LAND 17 (as applicable).

3 New communication systems, noting that an improved artillery command and fire control system must inevitably rely on the underlying communications links established using existing and planned tactical communications capabilities (e.g. JP2072 Tactical Communications System). Provision may need to be made for the acquisition of additional quantities of communications equipment should the LAND 17 solution require additional radios above the numbers currently provided to the artillery organisation. Additional communication equipment may be acquired as part of subordinate target acquisition equipment.

4 New logistic systems beyond the level of the artillery regiment, although improvement to logistics capabilities within the regimental structure (notably munitions handling, reporting and tracking systems) may be considered a viable enhancement option.

2 LAND 17 will seek to acquire 52 calibre modular charge systems and enhanced performance munitions (such as Artillery Delivered High Precision Munitions (ADHPM) in the form of Course Correcting Fuses (CCF)). The enhanced performance munitions will be acquired at a later phase of the project. Other forms of ADHPM such as Trajectory Corrected Munitions (TCM) and Sensor Fused Munitions (SFM) will be purchased under other Major Capital Projects.

5 Contract Boundary

1 It is likely that the acquisition will seek to achieve a range of contract deliverables including:

1 Provision of an enhanced BMS-F able to coordinate all forms of joint fires and integrating all components of the system into an efficient, networked structure. This will include the integration of land based offensive fire support assets with Offensive Air Support (OAS) and Naval Surface Fire Support (NSFS). The Advanced Field Artillery Tactical Data System (AFATDS) has been selected as the LAND 17 BMS-F (C2).

2 Provision of upgraded or new delivery platforms, able to deliver indirect fire support to ADF manoeuvre units at greater ranges, and with enhanced efficiency, protection (self-propelled platforms only) effectiveness and responsiveness.

3 Integration of the munitions, the delivery platforms, and the BMS-F which involves the interfacing fire control system with the target acquisition system and the tactical command, control and communications systems.

2 Figure 1 describes the project scope as detailed above.

[pic]

Figure 1: Land 17 Project Scope Diagram

6 Existing Assets to be integrated into the IFS

1 The following existing (and planned) assets are to either interface with, or be integrated into; the IFS are detailed in Table 1 below.

|Existing (or Planned) Asset |Function/Relationship with IFS |

|Medium Artillery Replacement Ammunition |MARAP proposes the acquisition of a new family of 155mm ammunition. Project MINCS (L) |

|Project (MARAP) |40.10 seeks to deliver this ammunition to the ADF. |

|AN/TPQ-36 Weapon Locating radar (WLR) |The WLR is a ground-based, weapons locating radar, designed to acquire and locate |

| |threat indirect fire systems. Project LAND 58 Phase 3 seeks to upgrade and extend the |

| |life of type of this system |

|Tactical Unmanned Aerial Vehicle (TUAV) |The TUAV is an airborne sensor to provide real time imagery for surveillance and |

| |target acquisition. Project JP129 seeks to deliver this equipment to the ADF. |

|M113A1 Armoured Personnel Carrier (APC) |The APC is used by mounted manoeuvre units, and by some JOST, within the land |

| |battlespace. Under Project LAND 106, quantities of the current fleet will be upgraded |

| |to M113A3 standard. |

|Battlefield Command Support System (BCSS) |BCSS is a computer based command support system employed in support of manoeuvre |

| |commanders at certain levels (generally unit and above). It is primarily an |

| |operational planning tool, providing a level of situational awareness. Currently being|

| |delivered under Project LAND 75, the system is still evolving with the intent of |

| |providing a vehicle mounted BMS capability in the future. |

|Combat Net Radio (CNR) |CNR is a tactical communications bearer. It provides the primary communications links |

| |used to transfer targeting data and all other command and administrative information |

| |within the indirect fire support system. Project JP2072 seeks to deliver an enhanced |

| |tactical communications capability, including new CNR. |

|Artillery Orienting System (AOS) |AOS is a secondary inertial navigation system used to orientate and fixate delivery |

| |platforms and WLR. Project MINCS (L) 42.15 seeks to deliver this equipment to |

| |nominated artillery units. |

|Marwin Meteorology system |Marwin provides meteorological data used in the computation of ballistic firing data. |

|Lightweight Utility Vehicle (LR110) Fitted |These vehicles are used by manoeuvre units, and by artillery command elements, within |

|For Radio |the land battlespace. Project LAND 121 Overlander seeks to deliver a new fleet of |

| |vehicles. |

|Utility Vehicles (Medium and Heavy) |These vehicles are used by manoeuvre units, and by artillery elements (for the purpose|

| |of towing firing platforms and logistics), within the land battlespace. Project LAND |

| |121 Overlander seeks to deliver a new fleet of vehicles. |

|Australian Light Armoured Vehicle (ASLAV) |The ASLAV is used by manoeuvre units, and by some JOST, within the land battlespace. |

|CH-47D Chinook |The CH-47D is a rotary wing aircraft used by the army to transport cargo and |

| |personnel. It may also be used to transport elements of the IFS during operational and|

| |tactical deployments, subject to load restrictions. An operational requirement will |

| |introduce a Ballistic Protection capability to the CH-47D that will result in a |

| |reduction of the cargo capacity of the airframe. |

|C-130 Cargo Aircraft |The C-130 is used by the RAAF to transport cargo and personnel. It may also be used to|

| |transport elements of the IFS during strategic, operational and tactical deployments, |

| |subject to load restrictions. |

|C17 Globemaster Aircraft |AIR8000 Ph2 will acquire a heavy battlefield aircraft suitable for carrying payloads |

| |(up to 60 tonne) well in excess of the current C-130 fleet. The C17 Globemaster may |

| |also be used to transport elements of the IFS during strategic, operational and |

| |tactical deployments subject to load restrictions. |

Table 1: Assets to be integrated into IFS

7 Context

1 The IFS capability will function within, and interface to, a wide range of existing and planned Army, joint and coalition capabilities. It will also be influenced, both during acquisition and during in service employment, by a variety of factors and constraints.

2 A context diagram, illustrating the relationship of the IFS to other capabilities and projects is at Figure 2 below. It shows:

1 The sources of Strategic Guidance that impact on the definition of the capability to be acquired;

2 The Fundamental Inputs to Capability (FIC) to be addressed during the capability assessment process;

3 The Coalition environment in which the IFS must operated; and

4 Projects with which the IFS must interface. These include Land, Sea, Air Force and Joint projects.

[pic]

Figure 2: LAND 17 Context Diagram

mission overview

1 Tasks

1 The mission for the IFS is to establish such fire supremacy in the battlespace that threats can neither interfere with friendly operations nor effectively develop their own. To achieve this mission, the system must complete two essential tasks. Those tasks are to:

1 Coordinate joint fires and provide indirect fire to support the close battle.

2 Coordinate and employ joint fires and indirect fire to shape the battlespace.

2 The Operational Concept Graphic for the IFS is illustrated in Figure 3 below:

[pic]

Figure 3: IFS Operational Concept Graphic

3 The Graphic illustrates the manner in which all elements of the IFS are linked across a Fire Control Data Grid and through it to the common operating picture. Coalition and ADF joint assets are able to interface with the IFS through data gateways into this Data Grid.

4 The Graphic also illustrates the proposed fire planning functional structure represented by JOST positioned well forward with the supported manoeuvre elements, and Joint Offensive Support Coordination Centre (JOSCC) located at unit and formation headquarters.

2 Support the Close Battle

1 The IFS is required to suppress neutralise and destroy enemy targets in support of the land forces in close battle. These are tactical engagements that will occur at close ranges and with little warning. In these cases, the generation of fire supremacy will need to be responsive. Essential to these engagements is the coordination and delivery of Joint and Coalition lethal and non-lethal effects in both time and space against targets that are often in close proximity to ground forces and of immediate concern.

2 The IFS supporting the close battle must possess either; similar mobility and protection as the supported force, and/or sufficient range to obviate the need for redeployment in order to support ground forces, thus supporting the commander’s ability to create tempo.

3 Shape the Battle Space

1 In shaping the battlespace, IFS must be able to destroy point targets such as air defence systems and headquarters, and area targets such as massed forces, individual armoured vehicles and hostile indirect fire units. This task requires the coordination and delivery of precise and discriminate Joint and Coalition lethal and non-lethal effects that can be generated beyond the immediate battle.

4 Operational Policies and Constraints.

1 Ottawa Agreement. The Ottawa Agreement seeks a global ban on the use of anti-personnel land mines. Signatories of the agreement were to stop production and use of anti-personnel land mines. Australia is a signatory of this agreement and thus declares it will not use anti-personnel land mines.

2 For the purposes of this agreement an anti-personnel land mine is a “munition placed under, on or near the ground or other surface and is designed to be exploded by the presence, proximity or contact of a person”.

3 The impact of the agreement is that the IFS cannot plan or support missions that use anti-personnel land mines to deny ground to adversaries and non-combatants such as the Field Artillery Scatter-Able Minefield (FASCAM).

5 Personnel Interfaces to System

1 The IFS will interface with personnel across the following:

1 Joint Task Force (JTF). The JTF staffs provide high-level operational management of the IFS. This includes coordination of IFS assets and the creation and distribution of joint fire plans. The staff require interfaces to ADF and coalition target acquisition, fire support and command support systems employed across the JTF organisation, as well as timely situational awareness, fire planning tools, and weapon system availability information in order to manage the IFS at the operational level. The essential outcome is coordinated and networked joint and coalition fires to support the commander’s operational plan;

2 Ground Elements. The IFS must interface with those ground forces so that requests for fire support can be passed efficiently to the IFS, together with the necessary situational awareness, to ensure that the fires are delivered in a coordinated manner at the required time and place and in the required fashion. The practical interface between the ground forces and the IFS is detailed below:

i) Artillery Organisation HQ. Artillery command groups will normally be co-located with the JTF, Battle Group and formation level HQ in order to establish JOSCCs. In addition to providing formal fire planning and coordination activities, these personnel also provide advice on indirect fire capabilities and employment of all forms of joint and coalition fires that are available to the respective ground commanders. They require timely situational awareness, fire mission planning tools and system availability information in order to provide tactical coordination of joint and coalition fires.

ii) JOST. JOST (FO Parties) will be detached from artillery organisations and allocated to elements of the supported ground force. In addition to providing formal fire planning and coordination activities, these personnel also acquire targets, provide advice on the capabilities and employment of all forms of joint and coalition fires that are available to the ground commander. They require local situational awareness and fire mission planning tools in order to efficiently and accurately coordinate and call for fire as well as the tools to reduce Target Location Error and designate targets for laser spot trackers or laser guided precision weapons. The JOST will enable the conduct of All Arms Call For Fire (AACFF) missions by virtue of its communications suite and situational awareness through collocation with the manoeuvre force. JOSTs will monitor the AACFF mission and assume control (by request) if the mission exceeds the complexity threshold (for the AACFF observer) that sees continued terminal control by the manoeuvre asset as detracting from its ability to concentrate on its tactical responsibilities and prosecution of the close battle.

3 Delivery Platform Positions. The delivery platforms (guns) may be located individually or grouped (usually in troops of two guns each), and may be in isolation or within established positions occupied by elements of the ground force. The delivery platform’s site will also typically include the immediate logistics element and local C2 nodes. The crews will be required to deploy, survey, re-supply and then operate the delivery platforms while providing their own protected areas. Where possible local protection for the delivery platform should be provided from under protection with a remotely operated weapon station with a day and night sighting mechanism.

4 Logistic Elements. Indirect fire and target acquisition units and sub-units require substantial logistic support (specifically ammunition and maintenance). Support logistic staff will require situational awareness and automated system status information in order to provide pro-active and efficient support.

mission essential functions

1 The Mission Essential Functions (MEF) have been derived from the Operational Concept Document (OCD) and Function and Performance Specification (FPS). They do not negate performance requirements.

2 Any malfunction that would result in the inability of the IFS to perform one or more of the MEF to the level described below will be assessed as a mission failure.

3 At all times throughout the specified Mission Profiles, the IFS shall be able to:

2 Deploy Strategically

1 The IFS must be capable of deployment from the National Support Base (NSB)[1], in a barracks environment, to the Area of Operations.

3 Plan Offensive Support

1 The IFS must be capable of planning the delivery of Offensive Support in support of the operational requirements of the land force commander.

4 Manage Target Data

1 The IFS must be capable of providing a connection to surveillance and target acquisition capability for managing target data in support of the operational requirements of the land force commander.

5 Deploy Tactically

1 The IFS must be capable of tactical deployment and redeployment in support of the operational requirements of the land force commander.

6 Execute Joint Fire

1 The IFS must be capable of delivering the required joint fires to meet the operational requirements of the land force commander.

7 Protect the IFS

1 The IFS must be capable of protecting the deployed elements of the system, so the system is positioned and able to deliver the required indirect fire effect to meet the operational requirements of the land force commander without interference from the enemy.

8 Maintain and Sustain the IFS

1 The IFS must be capable of being maintained and sustained so the system is able to deliver the required indirect fire effects to meet the operational requirements of the land force commander.

mission system Organisation

1 Generic IFS Organisation

1 The generic IFS organisation for the LAND 17 Mission System is based on an artillery regimental structure. This IFS organisation is to be embedded within an Australian Army manoeuvre brigade. The regimental structure contains multiple gun batteries each with an integral coordination and manoeuvre liaison function; an Operational Support battery with its integral brigade level fire support coordination, fire direction and Joint Fires Forward Observation teams (JFO); and a Combat Service Support (CSS[2]) battery providing the required logistic support. An outline of the regimental structure for a generic IFS organisation is shown in Figure 4: Generic IFS Organisation with the operational elements highlighted.

[pic]

Figure 4: Generic IFS Organisation

2 Gun Battery

1 The Gun Battery structure is shown in Figure 5: Gun Battery with the operational elements highlighted.

[pic]

Figure 5: Gun Battery

2 The key functions of the each Gun Bty operational element are listed in Table 2 below.

|Element |Function |

|BG JOSCC |Provide joint and coalition fires advice to supported Battle Group |

| |(BG) commander. |

| |Coordinate all forms of joint and coalition fires and effects in |

| |support of the manoeuvre plan. |

| |Validate calls for fire from unauthorized observers and allocate |

| |fire missions to the Bty Fire Direction Centre (FDC) or Tp FDC |

| |should the Bty FDC not be deployed. |

| |For a BG operation, run the Supporting Arms Coordination Centre |

| |(SACC) aboard the Landing Platform Amphibious (LPA) or Landing |

| |Helicopter Dock Ship (LHD). |

|Bty Recon |Conduct sub-unit level recon. |

| |Command the gun group. |

| |Coordinate battery resupply. |

| |Provide technical expertise on gun-line. |

|BG JOST |Coordinate and terminally control all forms of joint and coalition |

| |fires and effects in support of the manoeuvre plan. |

| |Provide joint and coalition fires and effects fires advice to the |

| |Combined Arms Team (CAT) commander. |

| |Deploy on patrols (e.g. BG recon patrols), either individually or |

| |with a CAT, to provide liaison and observation capability, and |

| |maintain a full suite of insertion, extraction and survivability |

| |skills. |

|Bty FDC |Part of Bty Recon element. |

|(The activation of the Bty FDC will depend on the type of mission |Allocate fire missions to bty gun troops in accordance with plans |

|and regimental/battery structure adopted for the operation) |and priorities advised by JOSCC (both Bde and BG) and JOST. |

| |Predict firing data and transmit it to individual guns if firing |

| |data prediction is unavailable on the gun platforms. |

| |Manage target records and meteorological data for the bty. |

|Gun Tp |Command two gun detachments, a Tp FDC and an ammunition vehicle. |

| |A troop is considered to be the minimum deployable capability brick|

| |to provide indirect fire (the term gun detachments and gun crew are|

| |interchangeable) as two guns ensures that one gun is always |

| |available. |

Table 2: Gun Bty Key Functions

3 RHQ and CSS

1 The Operational Support Battery is shown in Figure 6 below.

[pic]

Figure 6: Operational Support Bty[3]

2 The key functions of each Operational Support Bty element are listed in Table 3 below.

|Element |Function |

|Bde JOSCC |Coordinate all forms of joint and coalition fires and effects |

| |through Bde HQ and assist in planning and execution of Bde plans |

| |and orders. |

| |Provide joint and coalition fires and effects liaison to air and |

| |maritime elements attached to the Bde HQ. |

| |Validate calls for fire from unauthorized observers and allocate |

| |fire missions to the Regt and Bty FDC |

| |Command and control of the Bde JOST Tp |

|Bde JOST |Coordinate and terminally control joint and coalition fires in |

| |advanced operations (ISR and shaping) in direct support of the Bde |

| |Commanders scheme of manoeuvre. |

| |Deploy on advanced operations patrols (e.g. Bde early entry |

| |airborne and amphibious operations), either independently or as |

| |part of CAT, ahead of the main force to provide liaison and |

| |observation capability and conduct handover from SF. |

| |Possesses the full suite of insertion, extraction and survivability|

| |skills. |

| |Validate and transmit joint and coalition fires target data to the |

| |Bde JOSCC via a line of sight or SATCOM communication bearers. |

|Regt Recon |Conduct broad-area unit level recon. |

|Regt FDC |Allocate fire missions to Bty FDC in accordance with plans and |

| |priorities advised by the Bde JOSCC. |

| |Predict firing data and transmit it to individual guns if firing |

| |data prediction is unavailable on the gun platforms. |

| |Manage target records and meteorological data for the Regt. |

|RTX Det |Facilitate radio communications within Regt. |

Table 3: Operational Support Battery Key Functions

3 Combat Service Support (CSS) Battery is shown in Figure 7 below.

[pic]

Figure 7: CSS Bty

4 Basis of Provisioning (BOP)

1 The proposed BOP for two, three or four bty of SPH is shown below in Table 4. Land 17 will seek, as minimum two bty of SPH with an option for a third or fourth bty.

|Location |Two SPH Bty |Three SPH Bty |Four SPH Bty |

|8/12 Mdm Regt, Darwin NT |6 |6 |6 |

|8/12 Mdm Regt, Adelaide SA |6 |6 |6 |

|1 Fd Regt, Brisbane QLD | |6 |12 |

|School of Artillery, Puckapunyal VIC |2 |2 |2 |

|Army Logistics Training Centre, Bonegilla VIC |1 |1 |1 |

|Logistic Unit (To Be Determined) |3 |3 |3 |

|TOTAL |18 |24 |30 |

Table 4: Proposed Basis of Provisioning (BOP)

common mission system Scenario attributes

1 Definitions

1 Deployment Mode. The two modes of deployment are:

1 Strategic. Movement to the Area of Operations[4] (AO).

2 Tactical. Movement within an AO.

2 System State. The various system states are:

1 Transit. Transit is moving without firing.

2 Inactive. Stationary (available for maintenance areas).

3 Firing. Into and out of action and firing.

3 Tempo. Tempo is the rate of rhythm of military activity relative to the enemy within tactical engagements and battles and between major operations.

4 Intensity. Intensity refers to the overall tempo, degree of violence and technological sophistication of the violence employed. The rate of consumption of resources is also a measure of intensity. The intensity will be high when the violence occurs frequently of when encounters between combatants are particularly violent.

5 Ammunition Expenditure Rates (AER). The AER is the average quantity of ammunition that is expected to be expended per day, per gun at a given intensity of fighting.

2 Mission Environment

1 General Description. .

2 The terrain, in which the IFS is expected to operate, varies from mountainous to heavily vegetated areas to sparsely vegetated scrubland to flat areas with little vegetation and sandy dry soil to densely populated coastal areas. Jagged ranges rising to 4600m above sea level typify the mountainous terrain. This terrain constrains both ground and rotary wing aviation operations. Off road vehicle movement, while unrestricted due to vegetation, can be restricted due to soft loose ground. Vehicle movement in mountainous areas is very restricted due to terrain and the availability of suitable roads. The urbanised terrain creates difficulty in locating and identifying combatants and non-combatants. The terrain represents a diverse and dynamic environment.

3 Environmental Requirements. The IFS must be capable of operating in the following environments, as specified in DEF (AUST) 5168A:

1 A1 – Hot Dry: Areas that experience very high temperatures accompanied by high levels of solar radiation, i.e. hot dry deserts of North Africa, parts of the Middle East, northern India, south western USA and desert areas of the Australian continent;

2 A2 – Intermediate Hot Dry: Areas that experience high temperature accompanied by high levels of solar radiation and moderately low relative humidity, i.e. southern Europe, the Australian continent, south central Asia, northern and eastern Africa, coastal regions of North Africa, high plains of North America, and most of Mexico;

3 B1A – Wet Warm (Australia): Areas that experience moderately high temperatures accompanied by continuous very high humidity. These conditions are found in rain forests and other tropical regions during periods of continuous cloud cover, where direct solar radiation is not a significant factor. Geographical regions covered include the northern coast of Australia;

4 B2 – Wet Hot: Areas that experience moderately high temperatures accompanied by high humidity and high direct solar radiation. These conditions occur in exposed areas of the wet tropical regions named in category B1;

5 B3 – Humid Hot Coastal Desert: Areas that experience moderately high temperature accompanied by high humidity and high direct solar radiation. These conditions occur in hot areas near large expanses of water such as the Arabian Gulf and the Red Sea;

6 C0 – Mild Cold: Areas that experience mildly low temperatures such as the coastal areas of Western Europe under a prevailing maritime influence, and parts of New Zealand; and

7 C2 – Cold: colder areas which include northern Norway, prairie provinces of Canada, Tibet and parts of Siberia but excluding the coldest areas of the North American continent, Greenland and Siberia.

generic mission SYSTEM scenarios

1 General. The Generic Mission Profiles have been developed in order to provide a breakdown of the functions performed by the LAND 17 Mission System in its expected operating profile.

2 The five mission profiles defined in this document are grouped under generic operational and training missions and are detailed below.

2 Mission Profiles

1 Generic Operational Mission Profile – Scenario 1. The Generic Operational Mission Profile is based upon the following:

1 An operation against an adversary with low-medium capabilities.

2 This is a protracted long-term operation with long range warning time.

3 Mission duration of six months.

4 A mission of low-intensity tempo with ‘round the clock’ operation (24 hours a day).

5 It is expected to occur at least once during the in-service life of the SPH.

2 Generic Operational Mission Profile – Scenario 2. The Generic Operational Mission Profile – Scenario 2 is based upon the following:

1 An operation against an unconventional adversary.

2 This is a protracted long-term operation with a short warning time.

3 Mission duration of 12 months.

4 A mission of low-intensity tempo with ‘round the clock’ operation (24 hours a day).

5 It is expected to occur at least once during the in-service life of the SPH.

3 Generic Operational Mission Profile – Scenario 3. The Generic Operational Mission Profile – Scenario 3 is based upon the following:

1 An operation within an asymmetric threat environment against a medium to highly capable adversary.

2 This is a protracted long-term operation with a short warning time.

3 Mission duration of six months.

4 A mission of high-intensity tempo with ‘round the clock’ operation (24 hours a day).

5 It is expected to occur at least once during the in-service life of the SPH.

4 Generic Training Mission Profile – Land Command. The Generic Training Mission Profile – Land Command is based upon the following:

1 A mission to meet the collective training requirements for employment of the SPH.

2 A mission duration of 18 days.

3 Each mission entails ‘round the clock’ operation (24 hours a day).

4 It is expected to occur five times annually during the in-service life of the SPH.

5 Generic Training Mission Profile – Training Command. The Generic Training Mission Profile – Training Command is based upon the following:

1 A mission to meet the individual training requirements for employment of the SPH.

2 A mission duration of 12 hours.

3 It is expected to occur 96 times annually during the in-service life of the SPH.

6 Generic Mission Profile Summary. A summary of the Generic Mission Profiles is detailed in Table 5 below.

| |Generic Mission Profile[5] |

|Characteristic |Operational Scenario 1|Operational Scenario 2|Operational Scenario 3|Training Scenario – |Training Scenario – |

| | | | |Land Comd |Trg Comd |

|Environment |A1/B1A |B2 |A1/A2/C0 |A1/B1A |A1 |

|Deployment | | | | | |

|Strategic |Rail/Road |Sea/Air |Sea/Air |Rail/Road[6] | |

|Tactical |Self-deploy |Self-deploy |Self-deploy |Self-deploy |Self-deploy[7] |

|Duration |6 months |12 months |6 months |18 days |9 hrs |

|Intensity |Low |Low |High | | |

|System State[8] | | | | | |

|Transit |3% | |25% |20% |10% |

|Inactive |85% |70% |10% |40% |10% |

|Firing |12% |30% |65% |40% |80% |

|AER[9] |50 |50 |200 |9 |16 |

|Total Rds[10] |1300 |5200 |36000 |405 |1500[11] |

|EFC[12] |425 |1690 |12600 |130 |490 |

|Area of Operations |400 x 400 |200 x 120 |350 x 150 |1050 – 3700 sq km |30 x 50 |

|(AO)[13] | | | | | |

|Distance (within |2200 |800 |2700 |1400 |28 |

|AO)[14] | | | | | |

Table 5: Generic Mission Profile Summary mission system architecture

3 Operational Nodes vs System Nodes

1 The Operational View, as portrayed in Figure 3, has identified a series of operational nodes required to facilitate the IFS capability. Table 6 below identifies the IFS system node within each of the operational nodes. It is the system nodes that are required to interface with each other to provide the information flows within the IFS system.

|Operational Node |IFS System Node |

|HQ Joint Operations Command (JOC) |Battlefield Coordination Detachment (CO 1 GL Gp) |

|Deployable Joint Force HQ (DJFHQ)/HQ 1st Div |Land Component Commander JOSCC |

|Brigade Headquarters |Brigade JOSCC |

|Battle Group Headquarters (Supported) |Battle Group JOSCC |

|Battle Group JOST |Battle Group JOST |

|Brigade JOST |Brigade JOST |

|Battery FDC |Battery FDC |

|Regimental FDC |Regimental FDC |

| |Meteorology Section |

|Gun Platform |Gun Platform |

|Combat Service Support |IFS CSS |

|Strategic ISTAR |Joint Intelligence Staff |

|Air Tactical ISTAREW |AEW&C |

| |Maritime Patrol Aircraft |

| |Joint Strike Fighter |

|Land Tactical ISTAREW |Weapon Location |

| |Ground Surveillance |

| |Unattended Ground Sensors |

| |TUAV (Ground Station) |

| |TUAV (Air Vehicle) |

| |ARH (Ground Station) |

| |ARH (Air Vehicle) |

|Offensive Air Support (OAS) |Aircrew, TACP, Joint Staff (RAAF) |

|Coalition Joint Fires |ADF Joint Fires Liaison Officer & Coalition FSCCs |

Table 6: Mapping of Operational Nodes to IFS System Nodes

4 System Entities

1 Within each of the system nodes identified above, there are a number of system entities pertaining to the IFS. Table 7 below, maps the system entities to their parent system node.

|System Node |System Entities |

|Brigade JOSCC |Battlefield Command Support System (BCSS) |

| |BMS-D |

| |BMS-M |

| |Joint Command Support System |

| |Air Command Support System (TBMCS) |

| |Maritime Command Support System |

| |Other Component Command Support System |

| |Coalition Terminal |

| |Combat Net Radio |

| |BMS-F |

| |TADIL Client |

|Battle Group JOSCC |BCSS |

| |Combat Net Radio |

| |BMS-F |

| |BMS-D |

| |BMS-M |

| |Remote Sensors (e.g. GSR, UGS) |

| |Organic Weapons (e.g. Mortars, SFMG) |

| |TADIL Client |

|Battle Group and Brigade JOST |BMS-D/BMS-F/DTCD |

| |Combat Net Radio |

| |Remote Sensors (e.g. Laser Range Finder, TI/II, GSR) |

| |TUAV remote Video Terminal/TADIL Client |

| |TADIL Client |

|Battery FDC |BMS-M |

| |Combat Net Radio |

| |BMS-F |

| |TADIL Client |

| |AOS |

|Regimental FDC |BMS-M |

| |Combat Net Radio |

| |BMS-F |

| |TADIL Client |

|Gun Platform |Combat Net Radio |

| |Weapon Platform with integrated FCS |

| |BMS-F |

|IFS CSS |BMS-M |

| |Combat Net Radio |

| |BMS-F |

|TUAV (Ground Station) |BMS-M |

| |Combat Net Radio |

| |TADIL Client |

|TUAV (Air Vehicle) |TADIL Client |

|ARH (Ground Station) |BMS-M |

| |Combat Net Radio |

| |TADIL Client |

|ARH (Air Vehicle) |TADIL Client |

| |Combat Net Radio |

|Weapon Location |BMS-M |

| |Weapon Locating Radar Operating System |

| |Combat Net Radio |

| |TADIL Client |

|Ground Surveillance |BMS-D/M |

| |Ground Surveillance Radar |

| |Combat Net Radio |

| |TADIL Client |

|Strategic ISR |Joint Command Support System |

|Met Section |BMS-D |

| |TADIL Client |

| |Met Terminal |

Table 7: IFS System Entities with System Nodes

system constraints

1 System constraints provide a framework for the design of the future system. The constraints pertaining to the IFS have been divided into ‘internal’ and ‘external’ types. Internal constraints are those that influence the system when seen in a ‘stand-alone’ scenario, whilst external constraints take into account entities that the IFS must work to/with in an Army, Joint or Coalition environment.

2 Internal Constraints

1 The internal system constraints were identified by the internal system needs and constraints. These constraints are grouped as internal because they are, to varying degrees, optional. The IFS could be developed and fielded successfully even when ignoring some or all of the internal constraints. The internal constraints are shown in Table 8 below.

|Internal System Need/Constraint |Remarks |

|ABCA agreements (QSTAGS) |Adoption of and compliance with QSTAG is ongoing |

|Insensitive munitions |ADF Policy is detailed in Defence Instruction (General) LOG 7-10 |

|Environmental Requirements |Full environmental control is limited with current equipment |

|NATO JBMOU |Adoption of and compliance with JBMOU is limited with current |

| |equipment |

|JTIEE |The Tactical Information Exchange System (TIES) standard for the |

| |Joint Fires system has been set as the Variable Message Format |

| |(VMF) |

|NBC |NBC protection is limited to IPE for operating a towed howitzer |

|Rules Of Engagement |ROE dictate how, when and where a weapon is to be used for a given |

| |operation. They may constrain the use of the IFS for a particular |

| |operation, but past ROE should not be used to influence the design |

| |of the future system. Improvements in precision, TA and C2 may |

| |assist in operating within defined ROE. |

| |The BMS-F will require a targeting policy construct to be developed|

| |by HQ JOC to support its employment within ROE. |

|OH&S |The requirement to operate within the bounds of Commonwealth |

| |legislation on OH&S is a constraint on the operation of the IFS |

|Tactics |The ability to quickly re-deploy with support ‘Shoot and scoot’ |

| |tactics. |

Table 8: System Internal Constraints

3 External Constraints

1 There are additional constraints that may be applied to the future system design that come about through Government policy or the need to interface the IFS to external entities. These ‘external’ constraints must be incorporated in the system if it is to interface to, and interoperate with, the relevant external entities. The external constraints are shown in Table 9 below.

|External System Need/Constraint |Remarks |

|Policy |Ottawa Agreement. |

|Deploy (Strategic) |IFS elements must be transportable by: C17 Globemaster, LPA, rail, |

| |ADF & civil road lift. The system must be able to self deploy by |

| |road. |

|Deploy (Tactical) |The system must be able to self deploy on Class 1, 2 and 3 roads. |

|Procedures |Adherence to Joint and Coalition procedures will aid |

| |interoperability. |

|Communications |Must interface with CNR, BMS-D/BMS-M (messaging) and TADIL to |

| |communicate externally (Army, Joint and Coalition). |

| |Must interface with RAAF’s TBMCS and the RAN’s future naval fires |

| |system onboard the AWD, ANZAC FFHs and FFGs. |

|Munitions |The IFS must be able to fire the in-service and known future (e.g. |

| |Excalibur and Smart155) 155mm munitions. |

|Threat Weapon Systems |IFS must have the range and effects to counter enemy weapon issues.|

|Simulation |IFS elements are to interface to existing simulation assets to aid |

| |training and mission rehearsal. |

Table 9: System External Constraints

system solution description

1 System Description

1 The IFS provides close support and shaping artillery to the land force. Its mission, as stated at 2.1.1, can be simply expressed as to establish overwhelming fire supremacy in the battlespace, and in doing so needs to complete the essential tasks of supporting the close battle and shape the battlespace.

2 The proposed system must remain closely coordinated with the fire of other weapons, including joint and coalition fires, and the scheme of manoeuvre[15]. These coordination requirements dictate that the indirect fire system must be capable of being task organised to support sub-unit, unit and task force size groupings. The indirect fire system remains an integral component of the combined arms team.

2 Proposed Sub Systems

1 The proposed capability, of the five sub systems, of the IFS are outlined below.

2 Ammunition. The ammunition is the weapon within the proposed system. The new family of ammunition (provided under Army minor project MARAP) will provide the variety of lethal and non-lethal effects and the range required to support the scheme of manoeuvre. It will also provide a level of munition commonality that allows for increased supportability and interoperability during allied and coalition operations. This ammunition is to be capable of being fired from the LAND 17 SPH. JP2085 will introduce ADHPM to the ADF in the form of precision Excalibur and Smart 155. These ADHPM must be capable of being ballistically calculated and fired from the LAND 17 SPH. The charge system used for the projectiles must be of a modular configuration and optimised for the SPH.

3 Target Acquisition. The target acquisition sub system will provide the timeliness, discrimination and accuracy required in order to plan and execute joint and coalition fires, and the ability to assess the battle damage at the completion of the firing engagement. It will also provide the sensor array that can be effectively integrated into an automated and digitised BMS-F network.

4 Command and Control. The C2 sub system (termed the BMS-F (C2)) is key in integrating the effects of joint/coalition fires with the scheme of manoeuvre and comprises two elements:

1 AFATDS; and

2 the communications network to transmit those plans and orders.

5 The digitised communications network will enable orders and reports to be generated and disseminated in a timely and accurate manner throughout the IFS without overloading the communications infrastructure.

6 Delivery Platform. The solution shall be based on a protected self-propelled howitzer. The SPH will have mobility commensurate with the ground forces being supported and possesses a degree of protection to survive likely threats. The SPH is to be capable of laying, loading, ramming and firing in degraded modes, preferably without degradation in the level of protection afforded to the detachment.

7 All SPH must be capable of automated independent fixation and orientation with data capable communication for all tactical firing solutions. Each SPH must possess the capability to independently determine its own firing solution for selected and approved targets, and be compatible with all ammunitions introduced under JP2085 and preferable under MARAP.

8 Automated loading is required, as is assisted replenishment of the magazine. This will reduce the workload of the detachment, risk of injury to personnel and enable more responsive and longer duration fires. The minimum amount of ammunition to be carried on any platform is 40 rounds with at least half of this ammunition ready for immediate firing.

9 The SPH must be capable of using the main armament for self protection against soft and hardened (non tank) targets. The SPH must also be able to remotely employ self protection weapons for local area engagements.

10 Combat Service Support. The combat service support sub system will provide the supply, distribution and maintenance of the other indirect fire support sub systems. Supply involves the handling of combat supplies and parts to ensure the IFS are available to ground commanders. Distribution is the transportation and asset tracking of supplies, in particular ammunition, for the IFS. Maintenance ensures reliability, availability and sustainability of the IFS. The CSS functions up to unit level will be optimised with insertions of automation technologies to enhance both procedural and physical requirements, eg replenishment of ammunition on the platform.

Support Concepts

1 General. This section describes the required support environment in terms of the support necessary to operate the deployed system. The description applies generically across the entire system, noting there may be variations in supporting some of the various sub systems.

2 The successful contractor will be expected to provide a level of through life support for the equipment liability introduced by LAND 17. The Life of Type (LOT) of the LAND 17 Mission System is 20 years with the initial term of the Contract (Support) expected to be five years from the Operative Date. The project will seek opportunities for innovative cost-effective options, for maintenance and supply support, through the establishment of a Support Contract, utilising a Performance Based Contract framework with the Contractor (Acquisition) or an approved agent (Contractor (Support)). The Contractor (Support) will provide the required spares support and maintenance to sustain availability of specified systems in specified locations including any SPH trainers acquired through the Acquisition Contract. This will also include the responsibility for developing, and managing, the SPH rotation policy. Annex G to the Contract (Support) will detail the Mission System Rate of Effort (ROE). This annex is derived from the Operational and Support Concept Document.

3 Performance measurements, for the Mission System, will be based on availability, reliability and supportability measures eg platform availability at specific times and locations, demand satisfaction, etc.

2 Reliability, Availability and Maintainability Considerations

1 Reliability. The inherent reliability of a system is primarily determined by its design. However, in-service reliability is determined by the way in which the equipment is designed, manufactured, operated and maintained. The Contractor (Support) will not be able to influence the operating and maintaining. They will only be able to influence reliability through the quality of the maintenance actions they are responsible for.

2 Maintainability. The time that weapon systems and equipment are not available for operational use because of preventative (planned) or corrective (unplanned) maintenance. The Contractor (Support) can only influence maintainability through the efficiency of the planned and unplanned maintenance actions they are responsible for.

3 Availability. This is a measure of the degree to which the equipment is in an operable state at the start of a mission, where the mission is called for at an unknown (random) time. It encompasses the elements of reliability, maintainability and the performance of the supporting logistic system. The Contractor (Support) can only influence availability through the performance of the elements of the Support System they are responsible (contracted) for i.e. maintenance and supply support.

3 Engineering Support

1 Engineering Support provides a range of engineering services to sustain and modify the IFS. This includes engineering analysis, technical regulation and the development and/or approval of modifications and other configuration changes. Engineering Support includes the organisation of processes and resources to enable general engineering, specialty engineering, Systems Engineering, Configuration Management, Software Engineering and other engineering services to be provided in-service.

2 Support Contract responsibilities. Maximum support will be sought from Contractor (Support) for Engineering Support, particularly with regards to Configuration Management and Technical Data management.

3 Configuration Management. It is anticipated that the IFS will be subjected to Grade A Configuration Management (CM) requirements. Grade A is the highest level of CM and involves the detailed management of the Actual Build State. Typically, a dedicated CM information system would be used to provide control and access to CM information and technical data for all organisations and individuals involved in the CM process. It is not envisaged that Defence will carry out modifications to the equipment, unless they are part of normal manufacturer upgrades.

4 Maintenance Support

1 Maintenance Support includes preventative and corrective maintenance services performed by qualified maintainers, operators and other support personnel. Maintenance is normally defined in terms of restoring an item to, or retaining it in, a near original operating condition. Software “maintenance” changes the software’s original design (even if it is only a small change); hence, software maintenance is included as part of Engineering Support, not Maintenance Support. The primary objective of materiel maintenance is to maintain the level of system availability required by operational commanders while using resources effectively and efficiently. Maintenance for the IFS will be conducted as far as forward as possible with maximum use made of Line Replaceable unit (LRU) at unit level.

2 It is intended to maximise the use of Interactive Electronic Technical Manuals (IETM) for maintenance.

3 Support Contract responsibilities. The Contract (Support) will seek maintenance support for the Mission System and, any acquired SPH simulators, for all lines of maintenance except for 1st Line and all grades of repair except for Operator and Light Grade Repair.

4 Lines of Maintenance Support. The maintenance system consists of four lines of maintenance support which describe from where the maintenance support is being provided. The lines of support are:

1 First Line. Maintenance support provided by unit maintenance personnel and technical support sub-units, under the command of the unit commander; to equipment operated by the unit.

2 Second Line. Maintenance support provided by brigade maintenance assets, normally part of Combat Service Support Battalions (CSSB), to perform maintenance tasks that are beyond the capability and/or capacity of first line maintenance support elements.

3 Third Line. Maintenance support provided within the area of operations to the force and force stocks of equipment.

4 Fourth Line/National Support Base. Maintenance support provided by organisations not allocated to the deployed force to equipment that is back loaded from the deployed force.

5 Grades of Repair. Grades of repair classify repair tasks according to a combination of frequency of occurrence, difficulty, skills required, repair time and the range of repair parts and facilities required. Each maintenance support element is allocated responsibility for performing specific grades of repair on each equipment type. This enables specialist tools, test equipment, repair parts and maintenance personnel to be allocated to those units best placed to perform particular grades of repair. The grades of repair are:

1 Operator Maintenance. Operator maintenance is that maintenance carried out by equipment operators. Operator maintenance does not need supervision by technical tradespersons but must be supervised by the chain of command to ensure it has been completed to an acceptable standard. Operator maintenance includes minor repair part replacement, minor adjustments, parade servicing, scheduled servicing and non-technical instructions.

2 Light Grade Repair. Light grade repairs are those maintenance tasks that can be carried out in the unit by maintenance personnel organic to the unit, using portable tools and a limited range of fast moving repair parts. In the main, this grade is restricted to common minor repairs involving adjustment and quick replacement of repair parts and minor assemblies.

3 Medium Grade Repair. Medium grade repairs are those maintenance tasks that require greater engineering capacity than can be provided by unit maintenance personnel and technical support sub-units. In the main, these tasks are limited to assembly and module replacement. Medium grade repairs may include some repairs to assemblies and modules including those repair operations which need light machine tool support and a wider range of repair parts and specialised facilities.

4 Heavy Grade Repair. Heavy grade repairs are those maintenance tasks that require extensive engineering facilities. These range from repairs to individual components and overhaul of assemblies and modules, to overhauls and the rebuild of major items of equipment. Heavy grade repairs are generally time consuming and require the use of extensive machine tools, test equipment and facilities. They require a comprehensive range of repair parts.

5 Supply Support

1 Supply Support provides services for acquiring distributing, accounting for, managing, and disposing of stores. These stores include Mission System spares equipment, components, fuels, munitions, and materials needed to operate, maintain, and sustain the IFS.

2 Support Contract responsibilities. The Contract (Support) will seek to maximise contractor supply support responsibilities. The Commonwealth may not own any Stock items with the Contractor (Support) responsible for Repairable Item (RI) and non-RI pipeline management to meet Mission System availability requirements.

6 Training Support

1 Training Support provides for the delivery of training services to personnel. Training services can include a range of methods for delivery (eg classroom training, computer based training, on the job training, and self-paced study), each of which requires different support arrangements. Training support also includes the resources and processes to define, develop and maintain training materials; processes to administer students, courses, and trainers; and the requirements for managing training resources.

2 Land 17 will seek to acquire, through the Acquisition Contract, both driver, crew and maintainer trainers for the SPH. The expected types and locations of SPH trainers are detailed in Table 10 below:

|Location |Type |Function |Qty |

|8/12 Mdm Regt, Darwin NT |Gun Trainer |Gun Crew training |1 |

|8/12 Mdm Regt, Adelaide SA |Gun Trainer |Gun Crew training |1 |

|1 Fd Regt, Brisbane QLD[16] |Gun Trainer |Gun Crew training |1 |

|School of Artillery, Puckapunyal VIC |Gun Trainer |Gun Crew individual training |2 |

|School of Artillery, Puckapunyal VIC |Driver Trainer |SPH Driver individual training |2 |

|Army Logistics Training Centre, Bonegilla VIC |Maintainer Trainer |SPH Maintainer individual training |1 |

Table 10: Land 17 Simulation Equipment

3 Contractor (Support) responsibilities. The Commonwealth will retain responsibility for the sustainment training of both operators and maintainers. In addition to the responsibility for maintenance for any simulation equipment acquired, through the Acquisition contract, the Contractor (Support) may have some responsibility for the operation of simulation equipment.

4 Individual training. The individual training regime supporting the IFS is directed by Training Command and comprises:

1 Joint training at ADF Warfare Centre;

2 Special-to-Corps officer and soldier trade and promotion courses;

3 Operator and maintainer training;

4 Trade management, including trade structures; and

5 Training management and support.

5 Collective training. Collective training is directed by LHQ and is conducted by units within Land Command. Units conduct a range of collective training activities to maintain operational capability. Activities include:

1 Dry firing crew, sub-unit and unit training in ADF training areas; and

2 Live firing crew, sub-unit and unit training at ADF training areas.

6 The anticipated IFS operational functions that would need to be addressed by the training system are shown in Figure 8 below.

[pic]

Figure 8: IFS Operational Functions

7 The potential requirements for training support to the SPH include the need to support:

1 day and night training.

2 week day and weekend training.

3 a consistent level of training throughout the year (reduces the effect of climatic or environmental conditions on both training, e.g. wet season).

4 a range of training delivery requirements:

5 gun crew training,

6 driver training,

7 maintenance training, and

8 command and fire control systems training.

8 Simulation. There are a number of areas of individual training that may benefit from greater use of simulation. The potential future use of simulation by IFS, together with an indication of the current baseline is shown in Figure 9 below.

[pic]

Figure 9: Current and potential simulation support for individual training

9 A number of systems identified at the individual level have potential to provide ‘collective training’ of crews or personnel at a sub-system level. For instance an entire gun crew can be trained using a gun trainer simulator.

10 Where these individual simulation systems are networked, they can provide collective training involving two or more sub-systems, such as:

1 The gun platform and command and control sub-systems;

2 The gun platform and targeting sub-systems; and

3 The gun platform, command and control and targeting sub-systems.

11 The benefits that can be accrued at this level are significant in that networked simulations providing collective training between sub-systems introduces the potential to reduce the amount of ‘live’ training and maintain a consistent training level throughout the year.[17] The potential future use of simulation at the collective level, together with an indication of the current baseline is shown in Figure 10 below.

[pic]

Figure 10: Current and potential future use of simulation in collective training

-----------------------

[1] In geographic (physical) terms, the National Support Base refers to the Australian nation

[2] The support provided to combat forces, primarily in the fields of administration and logistics

[3] In an Australian Artillery regiment, the Battery Commander of Operational Support Battery doubles as the Regimental S3 (Operations Officer)

[4] That portion of an area of war necessary for military operations and for the administration of such military operations

[5] The Mission Profile is for an individual gun, however, the fleet will be rotated, during their service, in order to spread usage evenly across the total fleet

[6] Distance travelled from unit barracks to Training Area is approximately two round trips of 6000km each and three round trips of approximately 300km each

[7] Self-deploy to Training Area from school of Artillery is approximately 10km round trip

[8] Expressed in percentage terms of the total mission duration within the AO

[9] Total rounds fired per gun per day

[10] Total rounds fired per mission duration per gun

[11] Total rounds fired per training year per gun

[12] Equivalent Full Charge per gun

[13] All distances expressed in kilometres

[14] Distance per mission

[15] The scheme of a manoeuvre can include land, air and maritime forces

[16] Subject to acquisition of 3rd or 4th bty of SPH

[17] For instance, simulation may enable a more consistent training regime compared to high training levels in the dry season and low training levels in the wet season for units based in the Northern Territory or north Queensland

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download