During the Waikato campaign of 1863–64, the Imperial Commissariat employed field ovens manufactured by Vickery and Masefield of Auckland’s Albert Iron Foundry. Their double-cased iron oven offered a more robust alternative to the Aldershot and Curragh patterns supplied from Britain. By late October 1863, Commissariat ovens were operating in nearly every camp, reflecting the growing importance of forward bakeries in sustaining the British advance. Although the surviving manufacturer’s specification is dated 31 October 1864, the precise date on which the locally manufactured design first entered service remains to be established.
The double-cased field oven is probably the first piece of military field-cooking equipment designed and made in New Zealand.[1] It came almost fifty years before Lieutenant J. F. G. Roberts’ Salamander cooker of 1912. It also reflects a theme that runs through the earlier articles in this series. When imported equipment did not suit local conditions, New Zealand’s soldiers and suppliers designed their own.[2]
This article adds an 1860s chapter to three earlier RNZAOC articles. The Evolution of Army Catering in New Zealand (1845–1948) gives the organisational story. From Volunteer to Territorial covers field cooking from 1908 to 1915.[3]Feeding the Force traces field cooking systems from 1939 to the present.[4] None of them covers the New Zealand Wars, when the Imperial Commissariat ran the largest military catering effort New Zealand saw in the nineteenth century.
Feeding an army in the Waikato
Bread was the core of the soldier’s ration, and almost every ounce of it had to be baked in the theatre. The official daily scale was 1¼ lb of bread, 1 lb of meat, ¼ pint of rum, small amounts of tea, coffee and sugar, and a grain of pepper and salt. Biscuit replaced bread only when troops moved away from their bakeries.[5]
Responsibility was split. The Commissariat Staff Corps and its transport branch delivered the rations, ran the slaughter yards and ran the bakeries. The regiments turned raw meat and potatoes into meals in camp kettles over open fires. The Commissariat Transport Corps was formed in December 1861 and included butchers and bakers drawn from the Imperial garrison and the colonial militia. At its peak, the Commissariat Staff Corps had 41 officers, 125 NCOs and 1,341 men, with 1,516 horses and 729 bullocks.[6]
Although the Waikato was an established and productive agricultural region, the invading British force could not rely upon obtaining sufficient provisions locally. The campaign therefore depended heavily upon an organised supply system bringing flour, salt meat, biscuits, groceries and forage south from Auckland along the Great South Road and, increasingly, by river steamer. Local firewood was particularly important for operating the field bakeries.
Location plan of the Waikato Campaign, 1863–64, showing Auckland, the Great South Road, the Waikato and Waipā rivers, and principal military positions. The road and river networks were essential to the movement of Commissariat supplies and equipment as British forces advanced southwards.
At first, field bakeries at Drury and Ōtāhuhu baked bread four times a week and sent it to the south Auckland camps. As the advance went on, bakeries followed the depots forward to Rangiriri, Miranda, Ngāruawāhia and beyond.[7]
The Commissariat also improvised. At Ngāruawāhia, before the purpose-built ovens reached the front, Deputy Assistant Commissary-General Marshall supplied the staff with “very good bread” baked in holes in the ground.[8] Commissariat purchases in November 1863 listed dough troughs, boilers, ferment tubs, baskets and peels. Bakers were issued white kersey jackets, waistcoats, and drab moleskin trousers. Their ingredients were flour, potatoes, hops, malt, salt and yeast.[9]
A field oven and kneading trough illustrated in British military instructions of 1871. The design demonstrates how military personnel could construct baking facilities using locally available materials when manufactured ovens were unavailable. Source: Horse Guards, 1871, Plate 28.
The double-cased oven
The oven was a 7 ft 6 in iron tunnel with two skins, built in one piece to sit on a firebrick bed under a blanket of earth. Its design survives because the foundry documented it. Vickery and Masefield signed a Specification of Double-cased Field Oven at the Albert Iron Foundry on 31 October 1864. Deputy Assistant Commissary-General J. Leslie Robertson attached a certified copy, with a drawing, to his report on the Commissariat in the Waikato War. That report went to the War Office and is now held at The National Archives, Kew.[10]
The specification is an important surviving record of military equipment manufactured in New Zealand during the nineteenth century. It provides details of the oven’s construction, materials and intended use, although it does not establish how many were manufactured, their individual locations or their cost. Nor does the document, by itself, confirm whether the design had been modified between its initial development and the preparation of the October 1864 specification.
Specification of Double-cased Field Oven, Albert Iron Foundry, 31 October 1864, certified by DACG J. Leslie Robertson. WO 33/17A, No. 18, Inclosure 2, Appendix I, 73–74, as reproduced in Simmons, “Soldiers’ Foodways,” fig. 6.7.
The specification describes these features:
Two iron cases. An inner case of “full” ⅛ in sheet iron sat inside an outer case of ⅛ in sheet iron.[11]
Seven H-iron ribs. Between the cases sat seven ribs of H-section iron, bent to the oven’s arch on a template. Holes ran through both cases and each rib, and the whole was bolted or riveted together. The ribs projected below the cases to anchor the oven in the ground.
No floor. The oven had no bottom. It was set on a prepared bed of firebrick, which served as the baking hearth.
Front end. The single-cased front carried a wrought-iron door frame and door. The door had a sliding damper 6 in × 1¼ in, set about 2 in from the bottom. The front was joined to the outer case with a ring of angle iron.
Earth cover. The front plate stood 6 in higher than the oven to hold back the earth thrown over the oven once it was in place.
Back end. The single-cased back, also of ⅛ in plate, carried a chimney with a lid to regulate the draught.
One piece. Unlike the Aldershot oven, it was “not made in parts.” It was meant mainly for permanent stations, so it did not need to be portable. Even so, “it just fills a cart when complete.”[12]
The specification does not explicitly explain why the manufacturers adopted double-cased construction. However, the arrangement appears to have addressed weaknesses identified in the imported Aldershot and Curragh ovens, particularly their susceptibility to structural failure when the relatively thin iron casing was covered with earth and repeatedly heated.
The seven H-section iron ribs would have increased the arched structure’s rigidity, helping it resist deformation. The space between the two iron skins may also have influenced heat retention, although the extent of any thermal advantage cannot be established from the surviving specification. The principal documented distinction was therefore the oven’s more substantial construction rather than any proven improvement in fuel efficiency or baking performance.
The British Aldershot pattern field oven, showing its sectional iron construction and assembly. Unlike the Vickery and Masefield double-cased oven, which was transported as a complete structure, the Aldershot oven was assembled from separate components. Source: War Office, 1907, Plate 8, p. 15.
Feature
Vickery & Masefield double-cased oven
Aldershot pattern oven
Origin
Albert Iron Foundry, Auckland, 1863–64
British Army pattern, on the 1861 field-service list
Construction
Two ⅛ in iron skins on seven H-iron ribs, bolted or riveted
Single thin iron skin: two half-arches, one bottom, two ends, four bars
Floor
None; set on a firebrick bed
Iron bottom plate
Transport
Whole, on one cart
Knocked down into parts
Insulation
Earth thrown over the arch
About 6 in of compacted earth
Intended use
Semi-permanent station bakeries
Field and temporary camps
Known weakness
Weight and bulk
Thin iron that could collapse
Table 1. The New Zealand oven compared with the Aldershot pattern.[13]
Baking in the field
The new ovens made the difference between bread four times a week and bread every day. Taylor shows that the winter pause of 1863 gave the Commissariat time to build more ovens and move them forward. By late October 1863, ovens were in operation in nearly every camp. In February 1864, baking ovens, dough troughs and equipment were shipped up the Waikato from Meremere to Te Rore as the front moved south.[14]
The movement of baking equipment illustrates the practical relationship between mobility and sustained logistical support. Unlike the dismantled Aldershot oven, the Vickery and Masefield design was transported as a complete structure, occupying much of a cart. Its greater rigidity offered advantages for established or semi-permanent bakeries, but its size and weight may have limited its use where roads were poor or transport resources were limited. The selection and positioning of field bakeries therefore depended not only on oven availability, but also on suitable sites, transport capacity, and the ability to maintain supplies of flour, fuel, and other baking materials.
The local ovens did not replace the imported ones. Commissariat reports show Aldershot and Curragh pattern ovens in use alongside the New Zealand oven in both the Waikato and Taranaki. At Pātea in Taranaki, an oven made on the spot was added to the Aldershot and Curragh ovens at the bakery there. Setting up a bakery could be quick. At Alexandra in August 1865, the Daily Southern Cross reported that “in two days, ovens, &c were erected, and most excellent bread is now daily served out to all.”[15]
A Commissariat return for mid-1865 shows the bakery network after the fighting in the Waikato had ended. Fifteen stations had 38 bakers and 31 ovens: 2 brick ovens at Ōtāhuhu and 29 field ovens. The return does not say which pattern each field oven was.[16]
Station
Bakers
Ovens
Flour issued (lb)
Bread produced (lb)
Te Awamutu
6
6
40,600
55,720
Tauranga*
8
4
33,700
46,005
Ōtāhuhu
5
2 (brick)
19,675
25,643
Ngāruawāhia
4
2
12,953
17,390
Te Rore
3
3
12,450
14,889
Queen’s Redoubt
2
4
6,618
8,600
Thames
1
1
4,940
6,851
Maketū*
2
1
4,800
6,512
Rangiaowhia
1
1
5,200
6,509
Rangiriri
1
1
3,620
4,711
Raglan
1
2
3,300
4,300
Galloway’s Redoubt
1
1
3,070
3,990
Waikato Heads
1
1
2,600
3,446
Whatawhata
1
1
2,598
3,410
Ōhaupō
1
1
2,400
2,807
Total
38
31
158,524
210,783
Table 2. Commissariat bakeries, June 1865 (*Tauranga and Maketū, May 1865). Source: Jones, “Return.”
At the ration of 1¼ lb a day, 210,783 lb of bread is enough for about 5,600 men for 30 days. Te Awamutu alone produced enough for almost 1,500 men. Its six bakers and six ovens turned out about 1,860 lb of bread a day, roughly 310 lb per oven.[17]
Fuel was another important element of the bakery supply system. The surviving campaign records do not establish how much firewood the New Zealand-made ovens consumed. Later British instructions for the Aldershot pattern suggest approximately 300 lb (136 kg) of wood for the initial firing and 75 lb (34 kg) for subsequent bakes. Applying the latter figure to Te Awamutu’s six ovens gives an illustrative requirement of approximately 450 lb (204 kg) of firewood for one firing cycle across all six ovens. Actual consumption would have depended upon the number of firings, oven construction, operating conditions and the quantity of bread produced. Nevertheless, the calculation shows why fuel procurement and transport remained essential to military bakery operations.[18]
The makers
Vickery and Masefield was a young Auckland engineering partnership capable of making heavy ironwork. William Vickery (1824–1914) and Thomas Taylor Masefield (1842–1908) started the firm in 1862 at a foundry in Albert Street. By 1864 it built steam engines of 6 to 30 horsepower, made boilers, repaired harbour steamers, and cast pieces weighing 3 to 5 tons. The partnership was dissolved in 1867. Masefield carried on in Albert Street as T. T. Masefield and Company, and Vickery later set up a foundry at Thames.[19] Simmons gives the firm’s name as “Vickers and Masefield,” but the signed specification reads “Vickery Masefield.”[20]
Disposal and legacy
The withdrawal of Imperial forces from New Zealand during the later 1860s brought significant changes to the Commissariat’s bakery arrangements. In February 1866, the Commissariat offered ovens and baking equipment at half price to the successful bread contractor. Further tenders in 1867 for the supply of bread to Te Awamutu, Te Rore, Rangiaowhia, Kihikihi and Alexandra again offered existing ovens and implements to civilian contractors. Surplus baking equipment was also advertised for sale in Auckland. These arrangements reflected the progressive transfer of bread production from military bakeries to civilian suppliers, although the surviving evidence does not establish the fate of individual Vickery and Masefield ovens.[21]
Advertisements for the disposal of surplus Imperial Commissariat stores and government buildings, published in the Daily Southern Cross, 20 April 1867, p. 2. Such sales illustrate the redistribution and disposal of military infrastructure and supplies following the Waikato Campaign. The advertisements do not specifically identify double-cased field ovens.
No example is known to survive, and none has been found by archaeologists. Simmons found no physical trace of cookhouses, bread ovens or kitchen trenches at the Waikato sites she studied.[22] An earth-covered oven on a firebrick bed would leave only a scatter of firebrick and a patch of fire-reddened soil, easily lost to later building or ploughing. Excavators at redoubt and depot sites such as Te Awamutu, Ngāruawāhia or Queen’s Redoubt should look for exactly that near the Commissariat lines.
The experience of supplying British forces during the New Zealand Wars also contributed to wider discussions about military logistics. Richard Taylor identifies the Strathnairn Committee’s 1867 report as drawing upon New Zealand experience when considering the organisation and establishment of field bakeries. The locally manufactured double-cased oven formed part of a broader pattern of Commissariat improvisation, which also included constructing ambulances suited to local conditions. While the surviving evidence demonstrates that New Zealand experience informed discussions about British military supply arrangements, it does not establish that the Vickery and Masefield design directly influenced subsequent British oven construction.[23]
The double-cased oven also provides an early precedent for later New Zealand adaptations of military field-cooking equipment. The locally developed Salamander cooker of 1912 and modifications to British field-cooking systems during the Second World War reflected a continuing willingness to adapt imported equipment or develop local alternatives. Although separated by decades and very different operational circumstances, these examples illustrate the contribution of New Zealand engineering and manufacturing capability to military logistics.[24]
Conclusion
The double-cased field oven manufactured by Vickery and Masefield represents an early example of New Zealand industry responding to the practical requirements of military operations. Its construction reflected the limitations of imported British equipment and the need for durable baking facilities to support troops operating along extended lines of communication.
Although the number manufactured, their individual locations and their eventual fate remain uncertain, the surviving 1864 specification provides valuable evidence of local engineering capability and the Imperial Commissariat’s willingness to adopt equipment manufactured in New Zealand.
The oven also illustrates an enduring principle of military logistics: equipment cannot be considered in isolation from the system that sustains it. Flour, fuel, transport, trained bakers and suitable bakery sites were as important as the oven itself. By June 1865, the Commissariat maintained a substantial network of bakeries, demonstrating the organisation and resources required to provide a basic daily ration.
Nearly fifty years before the introduction of Lieutenant Roberts’ Salamander cooker, New Zealand engineers were already adapting military field-cooking equipment to meet local operational requirements. The double-cased oven therefore deserves recognition not simply as an unusual nineteenth-century engineering product, but as an early contribution to the development of military catering and logistics in New Zealand.
Notes
[1]Alexandra Lee Simmons, “Soldiers’ Foodways: Historical Archaeology of Military Comestibles in the Waikato Campaign of the New Zealand Wars” (PhD thesis, University of Otago, 2013), 174.
[2]Taylor, “British Logistics,” 157; Taylor notes that the Vickery and Masefield ovens “were regarded as being more robust than the Aldershot and Curragh military models used elsewhere by the British Army.”
[8]J. Leslie Robertson to H. S. Jones, 23 August 1864, Inclosure 1 in No. 18, WO 33/17A, 65, The National Archives, Kew, cited in Simmons, “Soldiers’ Foodways,” 174.
[9]Daily Southern Cross, 14 November 1863, 1, cited in Simmons, “Soldiers’ Foodways,” 173; Simmons, “Soldiers’ Foodways,” 121, 169.
[10]Vickery Masefield, “Specification of Double-cased Field Oven,” Albert Iron Foundry, Auckland, 31 October 1864, true copy certified by J. Leslie Robertson, Deputy Assistant Commissary-General, Inclosure 2 in No. 18, Appendix I, WO 33/17A, 73–74, The National Archives, Kew, reproduced in Simmons, “Soldiers’ Foodways,” 174, fig. 6.7.
[11]The printed specification gives both thicknesses as “1·8″”, which is almost certainly the typesetter’s rendering of ⅛ in. Sheet iron 1.8 in thick would have made an oven far too heavy to “just fill a cart.”
[12]Vickery Masefield, “Specification of Double-cased Field Oven,” 73–74.
[13]Simmons, “Soldiers’ Foodways,” 128–29, drawing on War Office, equipment for field service (1861), and later British cookery manuals of 1895 and 1907.
[14]Taylor, “British Logistics,” 157; Daily Southern Cross, 29 February 1864, 3, cited in Simmons, “Soldiers’ Foodways,” 327.
[15]Simmons, “Soldiers’ Foodways,” 175; Daily Southern Cross, 25 August 1865, 5, quoted in Simmons, “Soldiers’ Foodways,” 175.
[16]H. S. Jones, “Return Showing the Quantity of Flour Issued to, and Bread Produced at Commissariat Bakeries in New Zealand during the Month of June, 1865,” Inclosure 6 in No. 16, WO 33/17A, 52, The National Archives, Kew, reproduced in Simmons, “Soldiers’ Foodways,” 169, fig. 6.6.
[17]Author’s calculations from Jones, “Return,” at the field ration of 1¼ lb of bread a day. Simmons makes the same calculation for Te Awamutu; Simmons, “Soldiers’ Foodways,” 170.
[18]Simmons, “Soldiers’ Foodways,” 176 and n. 38, using the Aldershot oven figures in Army School of Cookery, Manual of Military Cooking (1895), 72, and War Office (1907), 20.
Recovering institutional knowledge, preserving the logic of military equipment entitlements, and building trust in future logistics systems
Long before computers, military organisations developed sophisticated systems to determine what was required to raise, equip, deploy, and sustain an army. These systems were recorded in War Establishments, equipment tables, scales of issue, entitlement schedules, ammunition allowances, repair parts lists and numerous other publications. Although maintained on paper and administered through manual accounting processes, they represented considerably more than inventories of military stores. Collectively, they captured generations of operational experience and provided a structured way to translate military organisation and operational requirements into personnel, equipment, and sustainment demands.
In many respects, these documents performed functions that modern information systems, including artificial intelligence (AI), are now being developed to undertake. They established relationships between military organisations, their authorised equipment, the resources required to maintain that equipment, and the consumable stores needed to sustain operations. By applying established rules and planning factors, logisticians could determine requirements, identify deficiencies and adjust support arrangements to suit particular circumstances.
It would be historically inaccurate to describe these paper-based systems as artificial intelligence in the modern technological sense. They did not learn independently, interpret unstructured information or generate new assessments. Nevertheless, they embodied a form of codified institutional intelligence in which accumulated knowledge was converted into rules, tables and procedures that could be applied consistently throughout the military organisation.
The transition from these systems to computerised logistics management has delivered substantial improvements in transactional efficiency, stock visibility and financial accountability. However, digitisation has not always preserved the relationships and underlying logic that made the earlier arrangements effective. In some instances, knowledge once contained within interconnected publications has had to be rediscovered, reconstructed or managed outside enterprise systems.
As artificial intelligence becomes increasingly capable of supporting military logistics planning and decision-making, this historical experience raises an important question: can the institutional knowledge previously captured in paper-based systems be recovered and incorporated into a trusted digital environment that can respond to changing operational requirements? This article argues that it can, and that artificial intelligence, built on a properly configured enterprise system and governed by authoritative data and human authority, should become a routine and progressively wider part of New Zealand Army logistics planning.
For more than 150 years, military logisticians have developed the knowledge, scales, tables and planning factors needed to calculate military support requirements. The next step is to make that accumulated knowledge executable within integrated enterprise systems, supported by automation and artificial intelligence, so that logisticians spend less time calculating what is required and more time ensuring that the necessary support is delivered. That knowledge must also record the risks accepted when established requirements are reduced, or delegated to allies, for political or practical reasons. Although the focus here is military, the same lessons apply to any organisation that must turn accumulated knowledge into the resources needed to sustain its people and assets.
Work to integrate AI into logistics and enterprise systems may well already be under way within the New Zealand Defence Force, including through the Future ERP programme. This article is not intended to critique or pre-empt that work. Rather, it approaches the subject from a different angle, drawing on the history of military scaling and the institutional knowledge embedded in it, to offer an additional perspective that may be useful to those designing and implementing these systems.
The Origins of Structured Military Equipment Scales
The practice of allocating equipment and supplies according to a military force’s size and composition predates the modern army. Military organisations have long recognised that a defined number of soldiers, animals, weapons or vehicles creates corresponding requirements for food, ammunition, transport, accommodation and maintenance. However, the nineteenth century saw a significant development in the formalisation of these relationships as armies expanded, military equipment became increasingly specialised, and governments sought greater consistency in providing and accounting for military stores.
The British War Office’s Army Equipment series of the 1860s was an early attempt to standardise the equipment requirements of military organisations. Its detailed tables recorded authorised stores, quantities, weights and other information needed for provisioning and transport planning. Source: Army Equipment, Part VI (1865)
A key example was the British War Office’s seven-part Army Equipment series, published during 1861–1866. The series was intended to provide comprehensive and standardised returns of the equipment authorised for the principal arms and services of the British Army. It covered cavalry, Royal Artillery, Royal Engineers, the Military Train, infantry, commissariat services and hospitals, with each volume addressing the particular equipment requirements of its respective organisation.[1]
The publications were considerably more detailed than simple inventories. They identified weapons, tools, personal equipment, saddlery, harness, camp equipment, specialist stores, and other resources needed to perform specific military functions. Where appropriate, they included quantities, weights, dimensions, and costs, allowing equipment requirements to be expressed as procurement, storage, and transportation demands. The volumes also reflected the increasingly specialised nature of military logistics, with separate provisions for the equipment required by engineers, artillerymen, transport personnel, medical services and the commissariat.
The 1865 Equipment of the Military Train, for example, addressed the resources required by the Army’s military transport organisation. Its preparation involved collecting and standardising equipment information, including determining weights and identifying costs. The compilers acknowledged possible errors and the need for later correction, showing that accurate equipment information and its maintenance were already recognised as important administrative responsibilities.[2]
The Commissariat Staff Corps’ Equipment, also published in 1865, provides an equally revealing example. In addition to describing specialist equipment used by bakers, butchers, carpenters, smiths and other trades, it included calculations for supporting an army in the field. One illustrative model considered a force comprising 10,000 infantry, 1,800 cavalry, 2,500 artillery, 600 engineers and 600 Military Train personnel, together with 400 horses. The calculations also considered the possibility of units being detached from the main force, showing an appreciation that logistics requirements could vary with the organisation and disposition of troops.[3]
Notably, some of the underlying calculations drew on experience gained during the Peninsular War. Operational knowledge accumulated decades earlier was therefore being incorporated into standardised planning arrangements that could be applied to subsequent military requirements.[4]
The Army Equipment series mattered not simply for the information in individual volumes, but for the broader principle it established. Once the composition and role of a military organisation were known, its equipment requirements could be determined by referring to an authoritative, standardised body of information. This allowed requirements to be calculated consistently, supported the preparation of stores for mobilisation, and provided a basis for assessing whether units had the resources needed to perform their assigned functions.
Although the calculations were undertaken manually and the information was maintained on paper, the underlying process was recognisably similar to modern requirements modelling. Organisational structures were linked to authorised resources, equipment characteristics supported transportation and storage calculations, and established rules enabled requirements to be adjusted according to the circumstances of the force being supported. These publications did not constitute a complete logistics information system in the modern sense, nor did they eliminate the need for professional judgement, but they demonstrate that structured data, standardised entitlements and the application of operational experience to logistics planning were well established before computers.
From Equipment Tables to Wartime Logistics Administration: The Ordnance Manuals of 1914 and 1939
By the beginning of the twentieth century, the British Army’s equipment administration had developed beyond preparing standardised equipment lists into a more comprehensive system governing the provision, issue, accounting, maintenance, and replenishment of military stores. This development is illustrated by the Ordnance Manual (War), 1914 and its later 1939 counterpart, which provide useful insights into the increasing sophistication of military logistics administration.
The Ordnance Manual (War), 1914 described the responsibilities and procedures of the Army Ordnance Department and Army Ordnance Corps during mobilisation and active service. It operated alongside the contemporary Equipment Regulations, which contained separate provisions for the equipment requirements of infantry, cavalry, artillery, engineers, the Army Service Corps, the Army Ordnance Corps and other specialist organisations. Together, these publications distinguished between the equipment a military organisation was authorised to hold and the administrative arrangements needed to provide and sustain it.[5]
The 1914 manual addressed the organisation of ordnance services in war, the maintenance of stocks, the preparation of demands and indents, the provision of ammunition and the arrangements for handling unserviceable equipment. These procedures ensured that equipment requirements could be translated into actual supplies and that the resulting transactions remained subject to administrative control. Determining an authorised requirement was only one part of logistics: the equipment also had to be available, transported to the appropriate location, issued to the correct organisation and subsequently maintained or replaced.
By the outbreak of the Second World War, the Ordnance Manual (War), 1939 reflected a further development of these principles. Its provisions addressed wartime provisioning, the supply of ordnance stores, repair and recovery arrangements, ammunition supply and the administration of the wider ordnance support system. Its detailed camp-equipment tables were particularly relevant. Table II, Camp Equipment for One Infantry Division (Manoeuvre Scale), differentiated between the arms and services forming the division, while Table III, Camp Equipment Required to Accommodate a Battalion at War Strength, provided a separate accommodation scale that expressly excluded equipment already included within the unit’s war equipment.[6]
The Ordnance Manual (War), 1939 distinguished between equipment carried as part of a unit’s war establishment and additional camp equipment required for accommodation and field operations. These distinctions enabled requirements to be calculated without unnecessary duplication.
This distinction showed that equipment requirements were not a single, fixed allocation. A unit had an authorised establishment and associated war equipment, but additional requirements could arise depending on its operating circumstances. Camp equipment, accommodation stores and other supporting resources could therefore be calculated separately from equipment necessary for the unit’s principal military role. The tables also included weights and measurements, allowing equipment quantities to be considered in relation to transportation and storage.
The progression from the nineteenth-century Army Equipment publications to the Ordnance Manuals of 1914 and 1939 illustrates a gradual development towards integrated resource management. The earlier publications standardised equipment requirements, while the later manuals described more comprehensive arrangements for administering those requirements during mobilisation and operations. New Zealand’s military administration inherited these principles and adapted them over time.
New Zealand’s Early Twentieth-Century Equipment Scales
By the beginning of the twentieth century, New Zealand’s military administration increasingly relied on formal establishments and equipment scales to support the organisation, training, and mobilisation of its forces. These arrangements became particularly important following the introduction of the Territorial Force in 1910, when the Army was required to equip and train larger numbers of personnel while maintaining effective control over limited resources.[7]
The annual training camps of the pre-war period provide useful examples. The 1913 brigade camps required accommodation, cooking equipment, camp furniture, tools, and other stores according to established scales. Temporary Ordnance Depots supported the issue and return of these items, with accounting procedures intended to ensure that equipment could be recovered, inspected and prepared for subsequent use. Once the number and composition of the participating units were known, requirements could be calculated against approved scales and the necessary holdings assembled.
The same principles applied to mobilisation. Expansion from a peacetime establishment to authorised wartime strength required corresponding increases in weapons, clothing, personal equipment, transport and supporting stores. Establishment tables identified the authorised organisation, while equipment schedules and other publications supplied the additional information needed to determine what that organisation required. Although undertaken manually, these calculations followed recognised structures and rules rather than being devised anew for every activity.
The Second World War: Establishments as Logistics Information
The rapid expansion of the New Zealand Army during the Second World War placed considerable demands upon its administrative and logistics systems. War Establishments and associated equipment tables became essential instruments for determining the personnel, vehicles, weapons, and supporting resources the expanding force required. A surviving collection of New Zealand Army Service Corps (NZASC) War Establishments for Home Defence, 1939–1945, offers a particularly useful illustration of the detail in these documents.[8]
The August 1940 War Establishment for a District Composite Company, NZASC, divided the organisation into headquarters, supply, ammunition and petrol sections, together with personnel permanently detached to support other formations and services. It recorded the authorised distribution of officers, warrant officers, non-commissioned officers, and other ranks, while separate tables identified the vehicles each element of the organisation required.[9]
An extract from the August 1940 War Establishment for a District Composite Company, NZASC. The establishment linked personnel, trades, vehicles and transport capacities to the organisation’s supply, ammunition and petrol distribution responsibilities, providing a structured basis for calculating its support requirements.
The transport schedules went beyond simply allocating vehicles. They distinguished between types and carrying capacities and identified their intended employment in transporting supplies, ammunition, petrol and other military stores. Individual subsections were assigned personnel and transport appropriate to their functions, and provision was made to support formations such as infantry brigades and medical units. The establishment therefore provided a structured description of logistics capability, linking authorised resources to the tasks the organisation was expected to perform.
It is important to distinguish the War Establishment from the equipment scales and stores entitlements that complemented it. The establishment defined the authorised organisation and its principal resources, while associated equipment documentation specified additional stores required to equip and sustain that organisation. Together, these publications provided a basis for determining requirements, assembling resources and assessing deficiencies. This distinction remains relevant to modern logistics information systems: organisational structures must connect to equipment configurations, actual holdings, consumption factors, and support arrangements before they can support a meaningful readiness assessment.
An earlier establishment shows the same logic applied to an expeditionary force. The September 1939 War Establishment for the Divisional Ammunition Company, NZASC (1st Echelon), was expressly based on British War Establishment II/1931/13/3 of August 1938, adapted for the Special Force. Its transport schedule allotted vehicles by ammunition nature (18-pounder, 4.5-inch howitzer, 2-pounder anti-tank, mortar, small-arms and anti-tank rifle ammunition, grenades and mines) as well as petrol, explosives, water and workshop loads. The establishment therefore embedded the division’s weapon systems within the company that sustained them. Its trade tables and notes went further, specifying workshop tradesmen, the numbers to be trained in first aid, water duties and anti-gas work, and dependencies on other units. Distribution lists prepared for the Ngaruawahia mobilisation camp then applied a 10 per cent reinforcement factor and carry annotations where duties were still being reconciled by hand.[10] The company was scaled to the equipment of the force it supported. As the Greek campaign would show, that alignment could not be assumed for every supporting organisation.
The Importance of Accurate Scaling: Greece, 1941
Even a well-established system’s limitations become apparent when the information used to determine requirements does not reflect the force being supported. The deployment of the New Zealand Division to Greece in 1941 provides an instructive example. The Scales Branch of the British Central Provisioning Organisation scaled Divisional Ordnance Field Parks centrally against a standard Middle East scale, set to represent 2.5 per cent of the supported division’s vehicles. The British Royal Army Ordnance Corps’ 1 Ordnance Field Park, attached to support the New Zealand workshops, held adequate Ford, 25-pounder and 2-pounder spares, but its vehicle spares had been scaled for Internationals and Crossleys. The New Zealand Division had no Internationals and only two Crossleys. A lack of consultation before the operation meant a sound scaling rule was applied to a fleet the Division did not hold.[11]
Consequently, part of the repair-parts holding was unsuitable for the vehicles requiring support. The problem was not the absence of a formal scaling system, but applying incorrect assumptions to the force being sustained. Transport capacity and storage space were committed to items of limited utility, while other requirements had to be met locally. After the withdrawal from Greece and Crete, the New Zealand Division formed its own Ordnance Field Park on 28 July 1941, initially with four officers, 81 other ranks and 27 three-ton lorries, holding fast-moving and essential motor-transport, weapon and signal spares for the Division’s own equipment. Its organisation was revised as the force changed: in November 1942 it was reorganised into holding, infantry and armoured sections to support the newly formed 4th Armoured Brigade.[12]
Alf Beale of the OFP sorting out his stock for the bin vehicle. Maadi Camp, October 1941. The New Zealand Divisional Ordnance Field Park was established in July 1941 to hold essential repair parts for the Division’s own vehicles, weapons and equipment. Its formation followed experience in Greece, where centrally determined spare-parts holdings did not adequately reflect the New Zealand Division’s vehicle fleet. Photo W.W Thomas.
This experience illustrates a principle fundamental to modern logistics management: a calculation can be mathematically correct, but its result operationally unsuitable if the information or assumptions on which it is based are inaccurate. Computers and AI do not remove this limitation; their speed may instead allow incorrect assumptions to be applied more widely and with greater apparent authority.
From Wartime Enumeration to Post-War Entitlement Control
After the Second World War, military equipment became increasingly complex, placing greater demands on the systems used to define and account for authorised holdings. Earlier War Equipment Tables, including the G1098 system, effectively established quantities against a unit’s authorised organisation, but were less suited to maintaining the integrity of increasingly complex equipment systems comprising components, accessories, tools, publications, and associated repair parts.[13]
By the late 1950s and early 1960s, the New Zealand Army was developing a more integrated approach to equipment entitlement and control. Drawing upon British and Commonwealth practices, the Army formalised a layered system incorporating New Zealand Entitlement Tables (NZET), New Zealand Complete Equipment Schedules (NZCES) and New Zealand Block Scales (NZBS). The NZET provided the authoritative record of a unit’s equipment entitlement, the NZCES defined components necessary to constitute complete equipment, and Block Scales enabled additional stores to be authorised according to particular roles or requirements.
A New Zealand Complete Equipment Schedule (NZCES) defined the components, accessories and associated items necessary to constitute a complete equipment system. Alongside entitlement tables and Block Scales, these schedules helped the New Zealand Army distinguish between possessing an item and holding the complete equipment necessary for its intended use.
Supporting maintenance and technical stores outfits, including First Aid Mechanical Transport Outfits (FAMTO) and First Aid Technical Stores Outfits (FATSO), further recognised that equipment possession alone did not constitute a sustainable capability. A vehicle’s usefulness depended on associated tools, documentation, and maintenance support, while changes to the authorised fleet could create corresponding requirements for repair parts and workshop resources. This marked an important shift from numerical allocation to managing complete, supportable equipment systems.
The 1965 Officers’ Handbook: Connecting Combat Formations and Logistics Support
An incomplete copy of a New Zealand Army Officers’ Handbook, dating from approximately 1965, further illustrates how these principles were applied to the organisation of a military force. The handbook describes a New Zealand Infantry Brigade Group and Logistic Support Group, supported by organisational diagrams and tables that identify personnel strengths, vehicles, and principal equipment. Because the surviving copy is incomplete, it should be read as evidence of the documented force model rather than proof that every organisation was established at full strength.[14]
Within the Infantry Brigade Group, combat and combat support units were accompanied by specialist logistics organisations, including an RNZASC Transport Company, an RNZAOC Ordnance Field Park, an RNZEME workshop and an RNZAMC Field Ambulance. The handbook’s entry for the RNZASC Transport Company describes four transport platoons, a composite platoon and workshop support, with an establishment of 11 officers and 307 other ranks, together with vehicle and trailer allocations.[15]
The Logistic Support Group extended beyond the brigade’s immediate requirements. Its organisation included transport companies, supply units, petrol distribution, air supply, cold storage, field bakery facilities, engineering support and medical services. The diagrams show that a force’s requirements could not be determined solely from its combat units: these generated corresponding demands for transport, fuel, ammunition, maintenance, medical support and numerous other services.[16]
The New Zealand Army’s Officers’ Handbook of approximately 1965 illustrated the relationship between combat formations and the organisations required to sustain them. The documented Logistic Support Group included transport, supply, petrol distribution, bakery, maintenance and other services, demonstrating how force structure generated corresponding logistics requirements.
The handbook therefore provides a useful example of an interconnected military information system. A formation’s organisational structure established the basis for personnel and principal equipment requirements, while associated entitlement schedules, technical publications, and planning factors supplied the information needed to calculate its wider support needs. Although recorded on paper, these relationships can now be represented in a digital information environment.
When Established Requirements Meet Political Constraints: Australia in Vietnam
The 1965 Officers’ Handbook records the documented model of a brigade group supported by its own Logistic Support Group. The Australian deployment to South Vietnam the following year shows what can happen when a deployed force departs from such a model. The existence of an established logistics organisation and its associated equipment scales does not mean that the resources needed to sustain a force will be authorised or deployed. Governments and commanders must reconcile military requirements with political commitments, personnel ceilings, funding and competing operational priorities. A critical distinction therefore exists between the doctrinal requirement, the approved establishment and the support capability actually available.
Ian R. Finlayson’s study of Australian Army logistics in South Vietnam illustrates the consequences. In planning the deployment of the 1st Australian Task Force (1ATF) in 1966, Australia established the 1st Australian Logistic Support Group (1ALSG), rather than deploying the supporting organisation already envisaged in earlier Army force structures. Planners assumed that American logistics could supply much of the support and consequently allocated 937 positions to 1ALSG from a deployed Army strength of 4,225. The decision favoured combat manpower but left the national logistics organisation constrained and dependent on external arrangements.[17]
The difficulties were not simply a question of supply quantities. American materiel was obtained through particular depots, agreements and liaison channels; the Australian organisation still had to request, collect, move and distribute it. Finlayson also describes restrictions on 1ALSG headquarters’ authority to direct technical logistics functions. Access to allied supply therefore did not remove national responsibilities for control, distribution, maintenance, or managing shortages.[18]
The lesson is not that coalition support should be avoided. For a smaller force, it is indispensable. Rather, reductions from an established logistics scale should be explicit, with the resulting shortfalls linked to confirmed arrangements, responsible providers, delivery capacity and contingency measures. A logistics system should show both the authorised force and the support it would require under the applicable doctrinal model, rather than treating the smaller approved establishment as proof that the requirement has disappeared.
The broader failure to avoid is losing institutional memory between deployments. If force-structure decisions, supply dependencies and operational lessons remain in disconnected reports or personal experience, future planners may have to reconstruct risks already encountered. An integrated enterprise system should compare doctrinal requirements with approved and actual establishments, identify deficiencies, record whether allied or contracted support is confirmed or merely assumed, and allow logisticians to explore the consequences of support failing or operational demands increasing.
These considerations were not confined to Vietnam. New Zealand’s commitments in Malaya, Borneo, Somalia and East Timor each required logistics organisations to reconcile national requirements with the support available through allied, multinational or host-nation arrangements. The operating environments, national responsibilities and degrees of reliance upon external support differed, but the underlying planning questions remained consistent: what support must New Zealand provide itself, what can reliably be obtained from others, and what risks arise when the approved support organisation falls short of the assessed requirement? The historical record of these deployments offers an opportunity to examine whether lessons about force scaling, national support responsibilities and dependency management were carried forward into subsequent planning.
Somalia, 1992–1994: When Operational Requirements Outgrow Equipment and Support Arrangements
New Zealand’s deployment to Somalia between 1992 and 1994 further illustrates the difference between equipping a military organisation according to established arrangements and ensuring its resources remain suitable for the circumstances in which it operates. Initially deployed as a 28-person Supply Detachment, the New Zealand contribution expanded in July 1993 into a 43-person Supply Platoon, incorporating an infantry section as the security situation deteriorated. The contingent’s responsibilities included managing general stores at Mogadishu Airport and supporting food distribution through the port, in conjunction with the United Nations-contracted catering organisation.[19]
New Zealand Army logisticians serving with the United Nations operation in Somalia, 1992–1994, worked in an environment where changing security conditions and multinational supply responsibilities placed demands on personnel, equipment and transport beyond those initially anticipated. The deployment illustrated the importance of adapting established support arrangements to operational realities.
Although established primarily to perform supply functions, the contingent operated in an increasingly hostile environment. Personnel carried standard New Zealand Army small arms and light fragmentation vests, while transport relied largely on commercially derived, unarmoured vehicles. As the threat increased, restrictions upon ground movement sometimes required the use of helicopters to maintain access to United Nations locations. These circumstances show how changes in operational conditions can create requirements beyond those anticipated when a force is initially equipped and deployed.[20]
The contingent’s personal equipment provides an equally instructive example. Standard load-carrying webbing proved impractical for many vehicle-based and supply duties, encouraging personnel to adopt alternative arrangements for carrying ammunition and essential equipment. The fragmentation vest offered limited protection against the threats encountered, while some New Zealand personnel serving at United Nations headquarters from 1994 gained access to more capable body armour. Such adaptations illustrated the difference between possessing authorised equipment and having equipment appropriately configured for the actual operating environment.[21]
The broader significance lies in the relationship between force structure, equipment entitlement, operational suitability and changing circumstances. A system that compares an approved establishment with actual holdings would provide only part of the picture. Effective logistics planning must also consider the tasks personnel undertake, the threats they face, the suitability of their equipment, and the changing resources required to sustain operations. An integrated ERP environment, supported by validated rules and AI-assisted analysis, could help identify these differences, flag emerging deficiencies, and preserve the operational lessons that should inform subsequent equipment scales and deployment planning.
Beyond Equipment Tables: The Wider Science of Logistics Planning
The examples examined so far represent only a snapshot of the military’s historical system of equipment establishments and entitlements. Over time, a much wider range of specialised tables, scales and planning factors was developed to address the increasingly complex requirements of military operations. Ammunition scales established initial holdings, expenditure assumptions, and replenishment requirements; repair parts scales identified components needed to maintain equipment; and fuel consumption tables enabled estimates based on vehicle types, operating conditions, distances travelled, and anticipated activity.
Other planning instruments addressed ration requirements, water consumption, transportation capacity, accommodation, medical support and casualty estimates. Although the publications served different purposes, the underlying principle remained consistent: a known military organisation, equipped for a particular task and operating under defined conditions, generated measurable requirements that could be calculated through established relationships and assumptions.
These requirements were not necessarily fixed. They could be adjusted according to the duration of an operation, terrain, climate, anticipated intensity of activity and transport availability. This was the science and art of scaling military logistics: the science lay in applying established quantities, rates, and relationships, while the art lay in exercising professional judgement to ensure the resulting requirements reflected operational realities. This combination offers considerable potential for future AI applications.
Project Convergence 2026: Scaling the Digitised Battlefield
The development of scales and planning factors is not complete. New equipment continues to create requirements for which established scales do not yet exist, as New Zealand’s participation in Project Convergence Capstone 6 (PCC6), a US-led programme of multinational experimentation conducted in 2026, demonstrated. Newly released New Zealand Defence Force (NZDF) briefings describe a battlefield increasingly characterised by persistent surveillance, uncrewed systems, autonomous sensor fusion, machine-assisted decision-making and connected communications. They also identify specialist technical skills as necessary to employ and sustain increasingly complex autonomous capabilities. The significance for military logistics is not simply the arrival of new equipment: each additional system creates new requirements for personnel, power, repair, replacement, data connectivity and distribution.[22]
Electrical power provides a particularly clear example. The NZDF findings identify power generation and energy resilience as increasingly important operational considerations, with battery consumption, replacement, charging cycles and sustainment requiring deliberate planning at tactical levels. An August 2026 US Army study similarly describes electrical power as an emerging fifth commodity, alongside ammunition, food, fuel and water. For a force deploying uncrewed aircraft, sensors, electronic warfare equipment and networked command systems, equipment entitlements alone are insufficient. A credible support calculation must also establish electrical loads, battery endurance, the number and compatibility of spare batteries, charging capacity, power-generation fuel, movement arrangements and safe storage and handling. These are modern equivalents of the weights, capacities, repair-parts allowances and consumption factors recorded in earlier equipment scales.[23]
PCC6 also highlighted the potential to forward-produce small uncrewed aircraft systems through additive manufacturing and commercial technologies. Such arrangements might shorten the route between damage, replacement and renewed operational availability, but do not remove the need for material stocks, suitable components, skilled personnel, quality assurance and safe power supplies. The same briefings emphasise that common data standards are fundamental to meaningful interoperability, regardless of the platforms employed, and note the close alignment observed between the New Zealand and Australian armies. For logistics information systems, this reinforces the importance of consistent item identification, equipment configurations, authoritative planning factors and exchangeable information across national and allied systems.[24]
New Zealand and United States personnel prepare an RQ-7 Shadow uncrewed aircraft during Exercise Wayfinder 24 at Waiouru in 2024. Systems of this type illustrate how modern military equipment creates additional logistics requirements for electrical power, batteries, specialist maintenance, technical personnel and supporting infrastructure. Source: NZDF, Exercise Wayfinder 24
These lessons also expose a practical distinction between acquiring a technological capability and sustaining it. The NZDF briefings recommend better alignment of robotic and autonomous-system initiatives to reduce duplication and improve supportability; they also show why experimentation should test the full support chain rather than equipment performance in isolation. The historical question remains recognisable: what resources does a specified force require, under particular operational conditions, for a defined period? The modern answer must include electricity, software-dependent systems and information exchange alongside the more familiar demands for fuel, ammunition, maintenance and transport.[25]
The same briefings also record more familiar support shortfalls. Accommodation was poorly coordinated; personnel had to buy their own cleaning materials to prepare equipment for Customs inspection on return; and the contingent lacked some of the technology needed to take full part in planned experimentation, reducing the opportunity to collect meaningful trial data. None of these requirements was novel. Cleaning stores for return inspection are precisely the kind of predictable, activity-specific need that a Block Scale or camp-equipment table was designed to capture, in the same way that the 1939 Ordnance Manual separated accommodation stores from a unit’s war equipment. The equipment, batteries, chargers and power generation needed to take part in a technology-focused exercise could likewise have been derived from the activity’s intended tasks. Had these requirements been held as an activity scale and checked against holdings before departure, with AI used to interpret the exercise plan, identify the applicable scales and flag items for which no entitlement or holding existed, many of these shortfalls could have been identified and resolved in New Zealand rather than discovered in the field. The NZDF’s own recommendation, that capabilities be tested in New Zealand before deployment, points in the same direction.[26]
Digitisation: What Was Gained and What Was Lost?
The introduction of computerised logistics systems fundamentally changed how military organisations recorded, processed and managed information. Electronic accounting systems were developed to reduce the considerable administrative burden of manual ledgers, requisitions, stock movements, and equipment reconciliation. These systems progressively evolved into enterprise resource planning (ERP) platforms, improving transaction processing, stock visibility, financial accountability and reporting.
However, the technological limitations of early systems meant that many established logistics functions were transferred into electronic form without fundamentally changing their operation. Equipment tables, entitlement schedules and accounting procedures often became electronic equivalents of their paper predecessors. Although information was easier to record and retrieve, relationships between establishments, equipment entitlements, operational requirements and sustainment calculations still required manual interpretation.
This distinction between computerisation and genuine digital transformation is important. A system might accurately record the quantity of equipment held by a unit without determining whether that equipment was complete, serviceable or sufficient for a particular mission. The information existed, but the functionality needed to turn it into an integrated assessment of operational capability was often missing.
Successive generations of ERP systems have improved database architecture, integration, workflows and reporting, enabling more dynamic relationships between inventory, procurement, maintenance and financial functions. Nevertheless, the full benefits of digitisation have not always been realised. Reports must still be downloaded, combined with other datasets and manipulated to meet mission-specific requirements, while resulting demands may require separate manual transactions.
Administrative effort has therefore been reduced, not eliminated. Tasks once performed by reconciling paper publications are now undertaken through electronic reports, spreadsheets and supplementary tools. Further integration, rules-based automation, and artificial intelligence offer the opportunity to move beyond recording and displaying information to dynamically calculating requirements, identifying deficiencies, and supporting operational decisions.
Working Around the System: The Excel Problem
A persistent feature of modern logistics information management is the reliance upon Microsoft Excel to supplement enterprise systems. Information is extracted from authoritative databases, reorganised, reconciled and manipulated in spreadsheets to produce reports and calculations suited to particular operational requirements. Spreadsheets remain valuable analytical tools, but routine extraction because the enterprise system cannot combine its own data may indicate incomplete digital integration.
For example, an ERP system may contain information on a unit’s equipment entitlements, actual holdings, serviceability, repair parts, ammunition allocations and consumption rates. Yet these datasets may be available only through separate reports rather than as a single assessment of the resources required for an exercise or deployment. Logisticians must retrieve the information, reconcile differences, apply planning factors and construct supplementary documents.
This process can create duplicate reports and standalone spreadsheets containing information already held within the enterprise environment. Locally maintained documents may incorporate assumptions and corrections that are not returned to the authoritative system. Changes in personnel strengths, equipment holdings or activity duration then require further manual reconciliation, increasing administrative effort and the possibility of inconsistencies.
The problem is not Excel itself, but the gap between information recorded in enterprise systems and the processes needed to convert it into operationally useful demands. A contemporary example is the New Zealand Army’s Catalogue Demand (CATDEM) process: its spreadsheet-based planning artefacts consolidate activity requirements, but the associated entitlement checks, demand interpretation and SAP transaction preparation remain substantially manual.[27]
AI, combined with conventional rules-based automation, could reduce repetitive data extraction, reconciliation and transaction preparation. The objective is not to eliminate spreadsheets, but to reserve them for genuine analysis rather than use them as essential workarounds for limitations in enterprise functionality.
Transferring the Burden of Logistics Calculation
The historical development of military equipment scales, entitlement tables and logistics planning factors reveals an important distinction between the knowledge contained within these publications and the effort required to apply it. The publications themselves represented accumulated institutional knowledge, progressively refined through operational experience and expressed as rules, relationships and calculations. However, the military logistician remained responsible for interpreting and applying that knowledge.
For generations, logisticians were required to consult multiple publications, establish the composition and equipment of a supported force, determine its entitlements, calculate consumption and maintenance requirements, identify deficiencies and translate the resulting information into demands for stores and services. The process required considerable professional knowledge, but much of the associated work was repetitive, administrative and computational.
In this respect, the paper-based system represented a form of institutional intelligence appropriate to its period. The rules and knowledge were already established; the human logistician supplied the processing capability necessary to apply them. As the preceding sections show, electronic accounting and ERP systems reduced this workload but did not remove it: many of the relationships between organisational structures, equipment entitlements, operational requirements and sustainment calculations still depend on manual interpretation and intervention.
The next stage in this evolution should be the progressive transfer of that computational and administrative burden to integrated enterprise systems, supported by rules-based automation and artificial intelligence. Authoritative establishments, equipment configurations, entitlement schedules, consumption factors and maintenance requirements should be maintained as connected information rather than isolated records requiring repeated manual reconciliation.
The objective should be to enable a logistician to establish the support requirements of a military activity or operation and receive a coherent assessment of the resources necessary to deliver that support. Such an assessment should identify what is authorised, what is required, what is available, what is serviceable, what remains deficient and what actions are necessary to close those deficiencies. It should also identify the transportation, maintenance, replenishment and other supporting arrangements required to sustain the force throughout the intended activity.
This does not remove the need for professional logistics judgement. Rather, it changes where that judgement is applied. Instead of spending substantial time assembling information and reconstructing established calculations, logisticians should focus on assessing the feasibility of support arrangements, resolving competing priorities, managing risk, and ensuring the required resources reach the right place at the right time.
The ultimate objective is not simply to provide more information to the logistician, but to make the full implications of an operational requirement visible, understandable and actionable.
Future ERP: Reconnecting Military Entitlements and Operational Logistics
The New Zealand Defence Force’s Future Enterprise Resource Planning (Future ERP) Programme provides a particularly relevant contemporary development in this longer history. The programme is intended to replace a fragmented ERP environment with an integrated enterprise-wide capability. In October 2026, NZDF procurement notices identified SAP S/4HANA and related SAP products as the intended solution, with separate procurement processes for systems integration, business integration and independent assurance. The transition is therefore more than a general aspiration to modernise accounting software; it is an opportunity to reconsider how information supports military readiness, deployment and sustainment.[28]
More significantly, a proactively released programme business case identifies “ERP for Defence, Paced for Success” as the preferred approach and explicitly favours SAP Defense & Security. It argues that this military-specific functionality provides operational planning, interoperability and readiness capabilities that a conventional corporate ERP solution cannot deliver. It also envisages rationalising numerous existing systems and ancillary tools. This shows a preferred programme direction, not that every module, workflow, or capability has been contracted, configured, or implemented.[29]
The distinction matters because SAP Defense & Security already contains functions closely related to the logic preserved in historical War Establishments and equipment scales. Its force-element model connects military organisational structures with authorised personnel and equipment, actual resources, maintenance, logistics and operational information. SAP’s published training materials describe authorised-versus-actual comparisons and the ability to initiate follow-on supply action from identified deficiencies. These are not speculative AI capabilities: they are established enterprise-system functions which, if properly configured and adopted, can provide much of the structured foundation on which more advanced decision support might operate.[30]
SAP S/4HANA Defense & Security provides military-specific functions for representing force structures, authorised personnel and equipment, and actual resources. Properly configured, these relationships can support readiness assessments and the identification of resource deficiencies. They also provide a structured foundation for automation and AI-supported logistics planning.
However, the existence of such functionality does not guarantee that the New Zealand Army’s entitlement policies, equipment configurations, activity-based demands, consumption factors, and deployment workflows will automatically operate as a coherent end-to-end process. Standard functionality must be mapped to national policy and military practice; master data must be corrected and governed; interfaces and workflows must be designed; and users must be trained to trust and employ the resulting system. Nor does an authorised-versus-actual equipment comparison, by itself, establish whether a force can sustain a specified operation for a given period. Serviceability, operational intensity, replenishment, maintenance capacity, transport constraints and the effects of disrupted communications must also be considered.
The system should also distinguish a doctrinal support requirement from the politically authorised establishment and the actual resources available. Allied, contracted and host-nation support should be represented as explicit dependencies, with the degree of assurance and consequences of failure visible to planners.
Future ERP therefore strengthens, rather than displaces, the argument advanced here. The rules-based foundation should be built first: the military-specific capabilities of SAP S/4HANA Defense & Security should be exploited rather than reproduced in separate applications or AI tools, so that AI can then be adopted with confidence on top of them. Artificial intelligence should be applied where it adds the most value: interpreting operational intent, retrieving relevant doctrine, exploring alternative scenarios, identifying anomalies, and explaining the consequences of changed assumptions. Approved entitlements, calculations, approvals and auditable transactions should remain under authoritative rules and human control. SAP also documents disconnected-operation capabilities, an important consideration for deployed forces, although the scope of any NZDF implementation remains to be established.[31]
Dividing Responsibilities Between ERP, Automation and AI
Realising the full potential of Future ERP will require a clear distinction between the functions performed by authoritative enterprise systems, conventional automation, artificial intelligence and military personnel. Not every logistics calculation or process requires AI. Many functions are better performed through established business rules, validated planning factors and integrated ERP workflows.
The following table illustrates how these responsibilities could be distributed within a future integrated military logistics environment.
Capability
Principal responsibility
Authorised force structures and equipment entitlements
SAP Defense & Security and approved policy
Actual holdings, maintenance and serviceability
ERP and integrated source systems
Consumption factors and scaling calculations
Governed planning rules and calculation engines
Identifying deficiencies and initiating demands
ERP workflows and automation
Interpreting operational intent and exploring alternatives
AI-supported decision tools
Prioritising resources and approving support arrangements
Commanders and logisticians
This division of responsibilities is important. Artificial intelligence should make the established logistics system easier to use, more responsive, and better able to support complex operational decisions. It should not become an alternative source of entitlement policy or an unaccountable calculation engine.
In this arrangement, calculation and administration increasingly shift from the individual logistician to the enterprise system, while professional judgement, prioritisation, and accountability remain firmly with military personnel.
Artificial intelligence offers an opportunity to reconsider how military logistics information is organised, connected and used. Its greatest potential in this context lies not simply in producing reports, but in reducing the manual effort required to convert authoritative information into operational requirements and decisions.
A future AI-enabled environment could draw upon approved establishments, equipment entitlements, complete equipment schedules, repair parts scales, maintenance information and current holdings to develop an integrated assessment of a proposed operation.
For example, a commander planning to deploy an infantry battalion could request an assessment of the equipment, ammunition, fuel, electrical power, battery charging, repair parts, transport and other resources required for a specified period. The system could compare authorised entitlements with actual holdings and serviceability, apply validated planning factors and identify deficiencies. Changes to duration, location, force composition or operational intensity could then be assessed without reconstructing each calculation in separate spreadsheets.
AI’s particular value lies in helping users express operational intent, interrogate information across systems, identify inconsistencies, explore alternative scenarios, and understand the resulting analysis.
Adoption should therefore be progressive, starting where the benefits are clearest and the risks easiest to control. Suitable first uses include interpreting activity requirements within the CATDEM process and preparing draft demands for human approval; testing how changes in duration, force composition, or operational intensity alter requirements; checking master data for inconsistent entitlements, missing configuration records, and unsuitable planning factors; and retrieving relevant doctrine, scales, and policy for planners. Each can be trialled against existing manual practice, including technical and logistics validation before deployment, measured, and widened as it proves reliable.
The New Zealand Army is comparatively well placed to test this approach. At 30 November 2025, it comprised 4,358 Regular Force personnel; an August 2025 audit population recorded 11,908 Regular Force and civilian personnel across the wider NZDF, excluding reservists.[32][33] These categories and reporting dates differ, but they indicate the organisation’s relatively modest scale. Its compact structure and interconnected logistics functions could allow integrated logistics processes to be developed, tested and refined through controlled trials and progressive integration at a manageable scale. A compact force is not automatically easier to transform, and resources, data quality, change management and implementation discipline remain real constraints. Nevertheless, with sustained investment, sound data governance and careful testing, a successful military-specific ERP implementation complemented by carefully governed AI could let the New Zealand Army demonstrate a digital logistics approach useful well beyond its size.
The opportunity is therefore not merely to recover institutional knowledge represented by historical paper systems, but to realise more fully the benefits that electronic accounting and ERP systems have long sought to deliver: accurate, connected and responsive logistics information with less repetitive administration and more time for professional judgement.
Accurate Data: The Essential Foundation
Wider use of AI depends upon the quality of the information available to it. A system operating with incorrect assumptions, outdated configurations, incomplete stock records or unsuitable consumption factors may produce convincing but operationally unreliable answers. The danger is particularly significant where results are presented without identifying their sources, assumptions or limitations.
Users must be able to distinguish between authorised requirements, verified holdings, calculated estimates and assumptions introduced because information is unavailable. Effective implementation requires disciplined management of organisational structures, entitlements, configuration records, item identification, maintenance information, and planning factors, along with clear responsibility for amendment, approval, and version control.
Historical equipment tables and scales required amendment to remain aligned with the organisations and equipment they described. The same principle applies to digital successors. AI can speed up and increase the flexibility of analysis, but it cannot compensate for the absence of an authoritative, well-maintained information foundation.
Data quality is not only a precondition for AI, however; it is also one of the areas where AI can help most. Checking entitlements against equipment configurations, identifying holdings with no corresponding entitlement and flagging planning factors that no longer match the equipment in service are laborious tasks when done manually, yet they are precisely the checks that would have exposed the mismatch between 1 Ordnance Field Park’s holdings and the New Zealand Division’s vehicle fleet in 1941. Used in this way, AI does not have to wait for a perfect information foundation; it helps to build one.
Building User Trust and Preserving Professional Judgement
Successful AI adoption will depend as much on organisational confidence as on technological capability. Users must understand where the information originated, how calculations were performed, and which assumptions shaped the results. When a system identifies deficiencies or recommends changes to a support plan, logisticians must be able to examine the evidence and assess its operational suitability.
Reducing manual intervention should not mean removing professional oversight. A system may identify the need for additional transport capacity, repair parts, or fuel reserves, but commanders and logisticians must decide how to meet, prioritise, or adjust those requirements. AI should improve decision support rather than transfer accountability from military personnel to a computer system.
The ultimate measure of success will be whether commanders and logisticians trust system outputs sufficiently to use them in planning and operations without routinely reconstructing the analysis in separate spreadsheets.
Lessons Beyond Defence
Although this article focuses on military logistics, the problems it describes are not unique to the armed forces. Any organisation that must equip, maintain and sustain people and assets for a defined activity faces the same task of turning institutional knowledge into requirements. Hospitals hold standard instrument sets and ward stock levels; airlines, transport operators and utilities hold recommended spares scaled to their fleets; humanitarian agencies plan against standard quantities of water, food and shelter per person. In civilian terms, a Complete Equipment Schedule is a bill of materials and a Block Scale a set of par levels.
Several of the lessons drawn here therefore apply more widely. First, a sound scaling rule applied to the wrong data produces a confident but unsuitable result: an operator that introduces a new bus, aircraft or medical-device fleet without revising its spares holdings repeats the experience of 1 Ordnance Field Park in Greece. Second, computerisation is not transformation; an ERP implementation that moves transactions without the logic that connects them leaves people to rebuild that logic in spreadsheets. Third, the persistence of spreadsheets alongside an enterprise system signals incomplete integration rather than user failure, and corrections made in those spreadsheets seldom return to the authoritative record.
Fourth, organisations adopting a standard ERP platform generally gain more by using its established functions than by reproducing them in custom applications and should build that rules-based foundation before layering AI on top of it. Fifth, the division of responsibility set out earlier between enterprise systems, governed rules, AI and people applies almost unchanged to a hospital, a port or an infrastructure operator: AI should make the established system easier to use without becoming an unaccountable source of policy or calculation. Finally, codified knowledge is vulnerable when the people who understand it retire and the systems that replace them record only transactions. Capturing the logic of scaling, not merely its outputs, matters as much to a civilian enterprise as to an army.
For New Zealand, this point is especially relevant. Many public agencies and businesses operate at a scale comparable to the NZDF, use similar enterprise platforms and face the same shortage of specialist staff. A Defence implementation that shows how institutional knowledge can be made executable, governed and trusted could offer a practical model well beyond the military.
Conclusion
The evolution of military establishments, entitlement tables and logistics planning factors demonstrates that the principles underpinning modern information systems have a long history. From nineteenth-century equipment publications and early mobilisation scales to detailed NZASC War Establishments and the layered entitlement arrangements developed during the 1960s, military organisations refined their ability to translate force structures and operational requirements into measurable logistics demands.
These arrangements were not artificial intelligence in the modern sense, but represented a substantial body of codified institutional knowledge. Their effectiveness depended on relationships among personnel, equipment, authorised holdings, consumption, maintenance, and transportation, along with professional judgement in applying those relationships to specific circumstances.
Electronic accounting systems and ERP platforms substantially improved the administration and visibility of military resources. Yet technological limitations meant that many functions were initially computerised rather than fully integrated or automated. Despite successive improvements, manual intervention remains necessary to turn enterprise information into mission-specific requirements, frequently through supplementary spreadsheets and standalone reports.
AI, combined with improved system integration and rules-based automation, offers the means to address these remaining limitations. By connecting authoritative data, established planning factors and approved business rules, future systems could reduce repetitive administrative work, dynamically calculate requirements, identify deficiencies and compare alternative support arrangements. For a comparatively small force such as the New Zealand Army, carefully governed experimentation could also demonstrate approaches transferable to larger military organisations and to civilian enterprises facing the same problems.
The underlying principle remains unchanged. Whether a requirement is calculated from a printed War Establishment, a Complete Equipment Schedule, a spreadsheet or an AI-enabled system, the result’s reliability depends on the accuracy of the information and assumptions used. The Australian experience in Vietnam adds a further requirement: institutional knowledge must preserve not only the calculation of what a force needs, but also the risks accepted when those requirements are reduced or delegated to others. The task is therefore not to invent a new method of determining support requirements, but to transfer the work of applying an established one from the individual logistician to integrated enterprise systems. The Future ERP programme makes this immediate rather than theoretical: its prospective adoption of SAP S/4HANA Defense & Security offers a practical means of rebuilding the connections between organisation, entitlement, holdings, readiness and sustainment that paper-based systems once expressed in separate but related publications. The New Zealand Army should therefore treat AI not as an optional addition to Future ERP, but as a planned layer within it: adopted progressively, under governed data and human authority, and widened as trust is earned. Success should be measured not by owning a modern ERP platform or an AI tool, but by whether logisticians can move from a validated operational requirement to a complete, intelligible, executable, and auditable logistics response without reconstructing the process outside the system.
Military logistics support knowledge has been developed and refined over generations. The challenge now is to make that knowledge accessible, connected and executable within modern information systems. The objective is not to replace the military logistician, but to remove much of the administrative and computational burden, allowing professional expertise to be directed towards what matters most: ensuring that military forces receive the support they require, when and where it is needed.
Notes
[1] War Office, Army Equipment, 7 parts (London: Her Majesty’s Stationery Office, 1861–66), especially parts 2–7. The surviving copies consulted include the volumes on artillery, engineers, Military Train, infantry, Commissariat and hospitals.
[2] War Office, Army Equipment, pt. 4, Equipment of the Military Train (London: Her Majesty’s Stationery Office, 1865), introductory material and equipment returns.
[3] War Office, Army Equipment, pt. 6, Equipment of the Commissariat Staff Corps (London: Her Majesty’s Stationery Office, 1865), illustrative field-force calculations.
[4] War Office, Equipment of the Commissariat Staff Corps, explanatory material accompanying the field-force estimates.
[5] War Office, Ordnance Manual (War), 1914 (London: His Majesty’s Stationery Office, 1914), provisions on ordnance organisation, demands, supply and accounting.
[8] New Zealand Military Forces, War Establishments, New Zealand Army Service Corps, Home Defence, 1939–1945, surviving compilation supplied for this study; archival identification on the compilation cover requires verification.
[9] New Zealand Military Forces, “A District Composite Company, N.Z. Army Service Corps: War Establishment, August 1940,” in War Establishments, NZASC, Home Defence, 1939–1945, summary of personnel and transport schedules.
[10] New Zealand Military Forces, “Divisional Ammunition Company, N.Z.A.S.C. (1st Echelon): War Establishment, September 1939,” Special Force, 1939, based on British War Establishment II/1931/13/3, 24 August 1938, parts (i) personnel, (ii) transport, (iii) distribution of rank and file by trades and duties, and notes; with “1st Echelon Divisional Ammunition Company: Distribution of Personnel,” Mobilisation Camp, Ngaruawahia.
[11] Robert McKie, “NZ Divisional Ordnance Field Park 1941–1945,” To the Warriors Their Arms, 10 December 2018, https://rnzaoc.com/2018/12/10/nz-divisional-ordnance-field-park-1941-1945/, drawing on A. H. Fernyhough, History of the Royal Army Ordnance Corps 1920–1945 (1965), and J. S. Bolton, A History of the Royal New Zealand Army Ordnance Corps (1992); see also McKie, “The Science and Art of Scaling.” The 1 OFP scaling details should be checked against Fernyhough and the underlying campaign and ordnance records before publication.
[12] McKie, “NZ Divisional Ordnance Field Park 1941–1945,” citing 2NZEF, Organisation and War Establishments – Ordnance – Field (Archives New Zealand, 1941), and Bolton, A History of the Royal New Zealand Army Ordnance Corps.
[14] New Zealand Army, Officers’ Handbook (undated, approximately 1965), incomplete copy supplied for this study, contents and parts 1–2. Publication date and status require verification.
[15] New Zealand Army, Officers’ Handbook, part 1, RNZASC Transport Company organisational and establishment tables.
[16] New Zealand Army, Officers’ Handbook, part 2, “NZ Logistic Support Group,” serial 31, organisation diagram and unit list.
[17] Ian R. Finlayson, Supporting the Commitment: Australian Army Logistics in South Vietnam, 1962–1973 (Cambridge: Cambridge University Press, 2026), 102–7.
[18] Finlayson, Supporting the Commitment, 153–65.
[23] New Zealand Defence Force, “OIA-2026-5916 Convergence Capstone,” findings on power generation, charging cycles and energy resilience; John Mabes, “Powering the Digitized Battlefield,” US Army Center for Army Lessons Learned, 28 August 2026, https://www.army.mil/article/294958/powering_the_digitized_battlefield.
[24] New Zealand Defence Force, “OIA-2026-5916 Convergence Capstone,” findings on common data standards, Australian interoperability and additive manufacturing for small uncrewed aircraft systems.
[25] New Zealand Defence Force, “OIA-2026-5916 Convergence Capstone,” institutional implications and recommendations concerning alignment of robotic and autonomous system initiatives and avoiding duplicated experimentation.
[26] New Zealand Defence Force, “OIA-2026-5916 Convergence Capstone,” findings and recommendations on accommodation, return-travel and Customs preparation, technology availability and pre-deployment testing; see also Phil Pennington, “Desert Wargames Tax Batteries, Feed Tech Wishlist,” RNZ, November 2026, https://www.rnz.co.nz/news/politics/2306252/desert-wargames-tax-batteries-feed-tech-wishlist.
[27] Robert McKie, Digitisation of CATDEM Within SAP to Enable Executable, Policy-Embedded Logistic Orchestration (unpublished concept paper, October 2026), secs. 3–6.
How the 1978 to 1979 Reorganisation Reshaped RNZAOC Supply.
Military logistics must adapt to new equipment, changing force structures, financial constraints and operational demands. The practical test of any change, however, is whether it sustains support to the force throughout. The 1978 to 1979 reorganisation of the Royal New Zealand Army Ordnance Corps (RNZAOC) is a clear New Zealand example. It changed the Corps’ responsibilities, units, establishments, stock accounts, and training role, while food, fuel, and stores still had to reach the Army.
The change made the RNZAOC the Army’s principal supply Corps. From 12 May 1979, it became responsible not only for ordnance stores, ammunition, and technical materiel, but also for foodstuffs, rations, and petroleum, oils and lubricants (POL).[1]
Change was already underway
The formal 1979 transfer was the second stage of a process already underway within the RNZAOC. In July 1978, Pataka described a proposed reorganisation intended to “rationalise the supply chain”. Central Ordnance Depots and Ordnance Field Parks were to be grouped into regional organisations, reducing duplicated stockholding and simplifying the movement of stores from demand to delivery.[2]
The proposal did not promise large Regular Force savings. Its main benefits were expected to be fewer stocking points, lower inventory and storage costs, simpler accounting and better use of people and infrastructure. In October 1978, former RNZASC supply organisations began coming under RNZAOC command for command purposes, and the February 1979 Pataka recorded the practical changes: new titles, altered establishments, repainted signs and the arrival of new personnel.[3]
Why the Army reorganised
The 1978 Defence Review required a rearrangement of Army logistic functions. New Zealand followed the broad direction already adopted in Australia: transport, movements and catering would be grouped in a Corps of Transport, while supply would sit with the RNZAOC.[4]
The date itself carried deliberate symbolism. Major W. Fraser recommended 12 May 1979 because it coincided with the anniversary of the 1910 New Zealand Gazette notice that established the Army Service Corps. The change was therefore both an organisational break and a carefully marked transition from a long-standing corps tradition.[5]
Organisation from 12 May 1979
Principal responsibilities
Royal New Zealand Corps of Transport
Transport, Defence movements, catering and postal functions.
Royal New Zealand Army Ordnance Corps
Supply, including food, rations, POL, ordnance stores, ammunition and related technical responsibilities.
This division did not separate supply from transport in the field. The RNZAOC held, managed and provided the stocks; the RNZCT provided transport and much of the distribution capability. The implementation order expressly allowed RNZAOC Combat Supplies Platoons to be placed under command of an RNZCT unit when operational circumstances required supplies to be distributed from second-line transport.[6]
What the RNZAOC gained
From 12 May 1979, responsibility for the provision and storage of all foodstuffs and POL, together with the development, evaluation and provision of ration packs, passed from the RNZASC to the RNZAOC. The accompanying equipment sponsorship was broad: refrigeration and air-conditioning equipment, packaging and packing materials, POL storage and quality-control equipment, water containers, agricultural supplies, and specialist camp and religious stores.[7][8]
The transfer also made clerk/storekeeper and butcher training an RNZAOC School responsibility. It affirmed that food, rations and fuel were technical supply functions requiring professional knowledge, not simply commodities to be bought and issued.
The RNZAOC after 12 May 1979
The new directorates at Headquarters New Zealand Land Force were implemented on 9 April 1979, before the field transfer on 12 May. This enabled the Director of Ordnance Services to assume the necessary policy, technical-control and force-management responsibilities before the new unit structure took effect.[9]
The RNZAOC Directorate controlled a national supply system comprising a base supply battalion, four regional Supply Companies, the New Zealand Advanced Ordnance Depot in Singapore and the RNZAOC School.
This table shows the principal RNZAOC supply organisation following the 1979 reorganisation. It does not attempt to list every RNZAOC technical, ammunition or workshop-stores appointment and element.
The structure combined static and regional supply, base-level bulk holdings and deployable field capability. It was therefore more than a renaming of RNZASC camp supply depots.
The units transferred to the Corps
Former RNZASC sub-unit
New RNZAOC sub-unit
Location
Composite Platoon, 1 Transport Company
13 Combat Supplies Platoon, 1 Supply Company
Papakura
Supply Section, Papakura Platoon, Northern Company
14 Supply Platoon, 1 Supply Company
Papakura
Headquarters 21 Supply Company
Headquarters 21 Supply Company, 4 Supply Company
Waiouru
4 Platoon, 21 Supply Company
43 Combat Supplies Platoon, 4 Supply Company
Waiouru
Supply Platoon, Waiouru Company
44 Supply Platoon, 4 Supply Company
Waiouru
7 Platoon, 21 Supply Company
47 Petroleum Platoon, 4 Supply Company
Waiouru
New sub-unit
23 Combat Supplies Platoon, 2 Supply Company
Linton
Supply Section, Linton Platoon, Central Company
24 Supply Platoon, 2 Supply Company
Linton
Wellington Supply Platoon, Central Company
54 Supply Platoon, 1 Base Supply Battalion
Trentham
Composite Platoon, 3 Transport Company
33 Combat Supplies Platoon, 3 Supply Company
Burnham
Burnham Supply Platoon, Southern Company
34 Supply Platoon, 3 Supply Company
Burnham
Supply Platoon, New Zealand Transport Company
New Zealand Supply Platoon, NZAOD
Singapore
The revised numbering made the national pattern clearer. The 14, 24, 34, 44 and 54 Supply Platoons corresponded to Papakura, Linton, Burnham, Waiouru and Trentham. The specialist exception was 47 Petroleum Platoon, which retained the petroleum function of former 7 Platoon, 21 Supply Company, while adopting the Waiouru prefix. Headquarters 21 Supply Company remained as a Territorial Force sub-unit of 4 Supply Company, capable of commanding up to five supply sub-units for training and exercises.[10]
People and capability transferred with the units
The establishment papers show that the reorganisation was not merely an exercise in moving existing posts. Eighty Regular Force supply posts and two civilian posts were transferred to the RNZAOC. There was no increase in the Regular Force establishment, but the Territorial Force supply establishment rose from 123 to 158 posts, a net gain of 35. The increase was required to establish 23 Combat Supplies Platoon at Linton, an entirely new sub-unit.[11]
This demonstrates that rationalisation and capability growth occurred together. Former RNZASC composite platoons became RNZAOC Combat Supplies Platoons; the existing combat-supply and petroleum capabilities of 21 Supply Company were retained, and a new platoon was raised for 2 Task Force Region.
Continuity of expertise was protected. RNZASC personnel employed in supply units were to remain in those units until the RNZAOC had sufficient trained personnel to replace them. They were also required to indicate whether they wished to join the RNZCT or RNZAOC.[12]
The transfer was also a lived transition, not merely an establishment change. Contemporary accounts suggest that some RNZASC and RNZAOC personnel expected difficulties, particularly in the continued supply of rations. In practice, the handover of tasks and the incorporation of transferees proceeded smoothly. The result supports the central lesson of the reorganisation: adaptation was judged not by creating new titles or badges, but by whether the Army continued to receive essential support without interruption.[13]
Accounts, responsibility and continuity
The change was embedded in the accounting system. Northern Company RNZASC’s supply-depot bulk-stock account became that of 1 Supply Company; Waiouru Company’s became 4 Supply Company; the Linton and Trentham Central Company accounts transferred to 2 Supply Company and 1 Base Supply Battalion; and Southern Company’s became 3 Supply Company.[14]
This mattered because stock accounts represented formal custody and accountability. New badges and unit titles could be introduced quickly; transferring account responsibility changed the organisation answerable for receipt, storage, demand, issue and reconciliation of the stores that sustained the Army.
Adaptation without interruption
The 1978 to 1979 reorganisation fundamentally widened the RNZAOC’s role. It placed food, fuel, rations and supply support alongside ordnance stores, ammunition and technical materiel. At the same time, it preserved the interdependence of supply and transport, retained specialist knowledge during the transfer and added a new Territorial Force combat-supply capability at Linton.
The contemporary details differ, but the lesson remains relevant. Logistics must adapt to new systems, new equipment and new operating demands while continuing to sustain the force. In 1979, the decisive measure was not whether the chart changed; it was whether the Army could still feed, fuel and equip its units. That remains the proper measure of logistic adaptation today.[15]
Notes
[1] Army General Staff, Army Reorganisation Instruction No. 11: RNZASC Reorganisation, Army 209/1/142/SD, 24 April 1979, paras. 1-5
[2] The RNZAOC Reorganisation,” Pataka, July 1978, 10-12.
[4] Julia Millen, Salute to Service: A History of the Royal New Zealand Corps of Transport and Its Predecessors, 1860-1996 (Wellington: Victoria University Press, 1997), 415-16
[5] Julia Millen, Salute to Service: A History of the Royal New Zealand Corps of Transport and Its Predecessors, 1860-1996 (Wellington: Victoria University Press, 1997), 415-16
[9] Headquarters New Zealand Defence Force, Army General Staff, Army Reorganisation Establishments, Volume 3, Army 1920/1, April 1979, paras. 3 and 10-15
[10] Army General Staff, Army Reorganisation Instruction No. 11, Annexes D and F, paras. 6-7.
[11] Headquarters New Zealand Defence Force, Army General Staff, Army Reorganisation Establishments, Volume 3, Annex F, “Supply Posts for RNZAOC.”
[12] Army General Staff, Army Reorganisation Instruction No. 11, para. 6c.
[13] Major J. S. Bolton, A History of the Royal New Zealand Army Ordnance Corps (Trentham: RNZAOC, 1992), 224-25
[14] Army General Staff, Army Reorganisation Instruction No. 11, Annex F, para. 8.
[15] Ministry of Defence, Defence Capability Plan 2025 (Wellington: Ministry of Defence, 2025), 39.
Building and Sustaining the Crown’s Parihaka Operation, 1879–1881
A note on scope
The terminology in this article is modern. The logistical problems were not. Every logistician who has sat through a briefing on the five Ds — destination, demand, distance, duration and dependency — or heard the principle of centralised control and decentralised execution, might assume these are recent inventions. Parihaka shows they are not: the same problems, solutions and trade-offs are visible in an operation conducted a century before they were formalised in doctrine manuals.
This article treats Parihaka as a logistics case study on how the Crown decided where supplies would enter the district, how a rapidly expanding force would be fed and equipped, how far men and matériel had to travel, how long the commitment might last, and how dependent it would be on shipping, contractors, roads, horses and weather. It does not attempt to retell the wider history of the occupation, or to reach a new judgement on it; that remains the proper work of historians and bodies such as the Waitangi Tribunal. But the analytical focus should not be mistaken for neutrality about what the system did. The roads, stores, transport and supply arrangements examined below were the means by which the Crown concentrated an armed force, occupied Parihaka, arrested its leaders, dispersed its people and dismantled the community’s ability to sustain itself. The logistics cannot be separated from the purpose they served.
Parihaka is well suited to this kind of analysis because it is comparatively well documented and involved a support system that can still be reconstructed from official reports, tenders and contemporary newspapers. Central direction came from Wellington; execution was delegated to district commanders, Defence Stores staff, camp officers, shipmasters, contractors and local non-commissioned officers.
This piece follows that system, not the men who directed it or the people it was directed against, but the roads, ships, stores and contracts that connected the two.
The occupation of Parihaka on 5 November 1881 is generally examined through the colonial government’s decisions, the leadership of Te Whiti-o-Rongomai and Tohu Kākahi, and the peaceful resistance of the people gathered at the settlement. Less attention has been given to the physical and administrative system that made the operation possible.
The force that entered Parihaka did not appear suddenly in November 1881. It was the culmination of more than two years of military preparation on the Taranaki coast. Between 1879 and 1881 the government enlarged the Armed Constabulary, transferred trained personnel into the district, accumulated weapons and ammunition, developed Opunake as a coastal supply point, constructed roads and telegraph lines, established a chain of camps, developed local forage resources and arranged contracts for provisions, transport, fuel and other support.
By November 1881 this system enabled 1,589 members of the Armed Constabulary and Volunteer Force to be assembled, equipped and sustained near Parihaka. It also enabled the government to arrest the settlement’s leaders, disperse much of its population and dismantle houses, fences and cultivations.
The visible event was the advance of 5 November. The less visible story was the logistical network built between Wellington, New Plymouth, Opunake, Rahotu, Pungarehu and the approaches to Parihaka.
Figure 1. Taranaki within New Zealand.
Figure 2. The Taranaki coast, plotted from surveyed coordinates.
Parihaka as a logistical operation
Although New Zealand officials did not employ the term “logistics” in its modern, comprehensive sense, the Parihaka operation required nearly all the functions now associated with military logistics. It involved the acquisition, storage, and issue of supplies; the movement of personnel and matériel; the construction and maintenance of roads and camps; medical support; contracted services; ammunition control; communications; and the recovery or disposal of stores after the operation.
Modern military doctrine defines logistics and sustainment as the planning and execution of support necessary to provide forces with freedom of action, operational reach and prolonged endurance. It encompasses supply, transportation, maintenance, personnel services, health support and associated field services.[1] These later definitions cannot be imposed directly upon an operation conducted in 1881, but they provide a useful framework for interpreting the surviving evidence.
Viewed in this way, the preparations for Parihaka were not a collection of unrelated administrative actions. Roads, camps, stores, ships, contractors, paddocks, telegraph lines and medical arrangements formed an interconnected support system.
The land dispute and the road through Parihaka
The logistical build-up cannot be separated from the dispute over confiscated land.
Parihaka had been established in the midst of the Taranaki confiscation area. Te Whiti and Tohu rejected the justice and legality of the confiscations and objected particularly to the failure to define and protect promised reserves. In 1878 the government began systematic surveys north of the Waingongoro River and advertised land for settlement.
Parihaka responded through peaceful civil disobedience. Survey pegs were removed and, from May 1879, parties began ploughing land claimed by settlers. Later protests included rebuilding fences across the projected coastal road after government parties removed them.
The road was therefore not neutral infrastructure. Its surveyed route cut through Parihaka’s cultivations, while proposed subdivisions between the road and the sea threatened to separate the promised reserve from coastal access. The fences across the road represented both physical boundaries and assertions of ownership.[2]
By April 1881 Parihaka’s population had grown to more than 1,300, making it one of New Zealand’s largest Māori communities. Its inhabitants included people from throughout Taranaki, upper Whanganui, Waikato, Ngāti Maniapoto and Tai Tokerau. The settlement was supported by fertile gardens, pastures and organised communal labour.[3]
The operation therefore brought two sustainment systems into conflict. One supported a colonial force through government stores, contractors, shipping, roads and military camps. The other supported a peaceful Māori community through cultivation, collective labour and regional networks.
Preparing for a West Coast emergency
The government’s logistical build-up began during the West Coast emergency of 1879, and as tensions increased, the Armed Constabulary Reserve was rapidly expanded. By July 1879 it consisted of 870 officers and men, of whom 600 were stationed on the West Coast and another 100 at Wellington. The men were armed with short Snider rifles and described as fully equipped for active service. Large reserves of ammunition and stores were accumulated at the principal stations.[4]
This concentration required considerably more than recruiting additional constables. Each man had to be selected, trained, clothed, armed and equipped before being sent to Taranaki. The Wellington Constabulary depot therefore became an important rear base, preparing personnel for service and issuing the equipment required in the field.
The scale of the preparations was also evident in the arms reserve. In June 1879 Colonel George Whitmore stated that 1,500 stand of arms were held in Wellington, packed in groups of fifty and ready for rapid despatch. Each group was reportedly accompanied by ammunition calculated at 100 rounds per weapon.[5]
This was effectively a pre-positioned mobilisation reserve. The weapons were not merely stored centrally; they had been packaged in quantities suitable for rapid issue or shipment.
The build-up also affected other commands. During June and July 1879 an officer, six non-commissioned officers and fifty-three constables were transferred from the Waikato to meet the demand for trained men on the West Coast. Their departure forced the Waikato command to recruit and train replacements.[6]
Preparation for Parihaka therefore extended beyond Taranaki. It affected recruiting, depot training and the distribution of experienced manpower throughout New Zealand.
Mobilising the Volunteer Force
The Volunteer Force provided a second source of manpower.
During the West Coast alarm of 1879, approximately 1,500 local Volunteers were under arms and training within ten days. Corps from Thames, Wellington, Christchurch, Timaru, Oamaru, Temuka, Picton, Cromwell and Queenstown offered to serve should an outbreak occur.[7]
The response demonstrated enthusiasm, but it exposed a fundamental logistical problem. The Volunteer Force consisted of separate corps scattered across New Zealand. Mobilising them required coordinating unit rolls, arms, ammunition, clothing, rail journeys, coastal shipping, accommodation, food, and baggage.
The colonial arms inventory was mixed. In 1879, 6,053 Snider rifles were already on issue, leaving only 866 in store, although another 3,400 were expected from Britain. At the same time, 9,642 older Enfield rifles remained in store, and another 1,788 were on issue.[8]
By April 1881 the position had improved. The Volunteer Force reported 6,883 Snider rifles on issue and 3,595 in store, with another 500 recently received from Britain. The ammunition reserve included 1,265,884 Snider cartridges and 204,592 rounds for Enfield rifles.[9]
The government therefore possessed sufficient arms and ammunition for a major mobilisation, but only because weapons had been accumulated, maintained and accounted for during the preceding years.
The permanent West Coast force
The Volunteer concentration of November 1881 was superimposed upon a substantial permanent Armed Constabulary presence.
On 31 March 1881 the Armed Constabulary Reserve numbered 717 officers and men throughout New Zealand. Of these, 522 were stationed in the Patea and Taranaki districts, principally at Pungarehu, Rahotu, Opunake, Manaia and other posts along the coast.[10]
The final mobilisation did not create a field organisation from nothing. It expanded an existing network of camps, roads, stores, paddocks and communications.
The permanent force also provided the skilled core needed to absorb the Volunteer contingents. Armed Constabulary personnel knew the roads, camp locations, landing arrangements and local terrain. They served as guides, guards, mounted orderlies, transport workers and store handlers.
Building the road to Parihaka
The military concentration could not be sustained without a reliable road along the Taranaki coast.
During 1879 and 1880 the Armed Constabulary was used extensively as a road-building force. Existing tracks were widened, gradients reduced, bridges and culverts repaired and sections gravelled. The objective was not simply to provide a path for infantry to march. The road had to carry drays, wagons, construction materials, provisions, baggage and ammunition.
Between the Waingongoro River and the western side of the Warmate Plains, approximately fifteen miles of existing road were repaired and widened. Bridges and culverts were substantially improved, nearly three miles were gravelled, and additional contracts were arranged for further gravelling.
On the Stony River–Opunake section, portions of the old road were repaired and new formation constructed. Sections were specifically prepared for dray traffic. The Public Works Statement of 1880 reported that road parties advancing from opposite directions across the Waimate Plains were close to meeting.
Colonel John Mackintosh Roberts organised the work as a military advance rather than as an ordinary civil engineering project. The constables moved cautiously and built defended encampments as the road progressed. Engineering work and operational reach therefore advanced together.[11]
By 1881 the coast road through the Waimate Plains and Parihaka Block had been completed sufficiently for wheeled traffic and more than half had been gravelled. The Public Works Statement openly described it as possessing special political importance.[12]
The distinction between a foot track and a dray road was critical. Infantry could march over ground unsuitable for bulk transport, but a force could not live indefinitely upon what its members carried. Food, ammunition, tents, blankets, tools, fuel and medical stores required wheeled or animal transport.
Road width, gradient, drainage and surface determined how heavily a vehicle could be loaded, how quickly it could travel and whether it could continue after rain. Culverts and bridges were therefore as important to the operation as rifles and ammunition.
Engineer Volunteers
The build-up also drew upon specialist Volunteer engineers.
As tensions increased, redoubts were reoccupied or built, more defensible posts were established at places including Opunake, and the engineer corps offered its services for Parihaka. Wellington submarine-mining engineer volunteers travelled north aboard the government steamer Hinemoa. Twenty-four Hauraki Engineers from Thames reached Auckland before their onward movement was cancelled.[13]
Their mobilisation reflected the anticipated need for personnel familiar with field works, tools, camp construction and technical duties. The precise specialist work performed by the Wellington engineers at Parihaka remains uncertain, but their inclusion demonstrates that the mobilisation was expected to require more than infantry manpower.
The chain of forward camps
Figure 3. Volunteer camp, Rahotu, Taranaki. Collis, William Andrews, 1853-1920 :Negatives of Taranaki. Ref: 10×8-1075-G. Alexander Turnbull Library, Wellington, New Zealand. /records/23030347
The advance towards Parihaka was supported through a succession of temporary camps.
During 1879 and 1880 the Armed Constabulary occupied positions at Kaipipi, Otakeho, Oeo, Oakura, Bayley’s Farm and Werekino. At each site, the men cleared flax, toetoe, and scrub, raised earthworks, dug rifle pits, and prepared the camp for defence. Cookhouses were constructed at Oeo and Oakura.[14]
A field camp required much more than tents. Ground had to be cleared and drained, water sources identified, latrines dug, cooking arrangements established and stores protected from weather and theft. Defensive works had to be completed before the camp could serve as a secure base for road parties, patrols and transport.
Once the force advanced farther along the coast, some camps were abandoned or reduced and the work repeated at a new location. The result was a moving system of temporary bases that progressively extended the government’s operational reach.
Pungarehu developed as the principal forward post. By 1881 it contained huts, tents, cookhouses, store buildings and defensive works. It stood approximately one and a half miles from Parihaka and was being strengthened by the construction of a blockhouse. Rahotu, five miles farther south, occupied a naturally strong position and became the principal concentration area for many of the Volunteer contingents.
Opunake possessed a redoubt capable of accommodating approximately 100 men, while Manaia had accommodation for about eighty.[15]
Opunake as the coastal supply hub
Figure 4. The coast road and forward camps supporting the advance on Parihaka.
The road system depended upon a maritime entry point, and Opunake became the principal coastal logistics hub for the forward area.
Roberts reported that a considerable amount of Armed Constabulary labour was consumed in discharging steamers there. Their cargoes consisted chiefly of stores for the Armed Constabulary, the Telegraph Department, and the Public Works Department. The ration contractor also landed several cargoes at Opunake.[16]
This reveals the interdepartmental character of the supply chain. The same landing operation handled military equipment, food, road-building material and telegraph stores.
Opunake lacked a sheltered harbour. Steamers anchored offshore and passengers and cargo had to be transferred into smaller boats before being taken through the surf. The operation depended upon weather, sea conditions, suitable boats and sufficient labour ashore.
By 1881 the landing arrangement had become a regular government function. A boat manned by Armed Constabulary personnel met arriving vessels and landed both government and civilian stores.[17]
After landing, cargo had to be sorted and loaded onto drays, wagons, or pack animals for inland transport. Every box of ammunition, bag of provisions, bundle of blankets, tent, coil of telegraph wire and road-building tool used in the forward area had to pass through this vulnerable transfer point unless it arrived overland.
Later military terminology described the place where bulk supplies were unloaded and reorganised into unit loads as a bulk-breaking point. A delivery point was the location where loads were transferred from one mode or level of transport to another.[18]
These terms were not used in 1881, but they accurately describe Opunake’s function.
The efficiency of the entire operation depended upon this transfer. Cargo could reach the Taranaki coast on time and still be delayed if the surf was too rough, boats were unavailable, landing parties were insufficient, or inland transport had not arrived.
Opunake was therefore not simply a port of arrival. It was the critical transfer point between the maritime and land components of the supply chain.
Samuel Cosgrave Anderson and Defence Stores
Samuel Cosgrave Anderson, the Defence Storekeeper, provides the clearest connection between the government’s central reserves and the field operation.
Anderson had been Defence Storekeeper since January 1877. His Wellington responsibilities included the custody and issue of arms, ammunition, accoutrements, clothing and other military equipment. He also became involved in wider supply arrangements for the Constabulary.
In July 1880 Anderson invited tenders for oats, bran, carrots, chaff, hay and straw, together with the supply and replacement of horseshoes, for the Wellington Armed Constabulary establishment.[19] Although the tender concerned Wellington, it illustrates the breadth of the Defence Storekeeper’s responsibilities and the range of commodities required to maintain a mounted force.
During the final concentration at Opunake in 1881, Anderson was directly involved in forwarding troops and stores. A contemporary report stated that Captain Taylor of the Armed Constabulary and Anderson were efficiently carrying out arrangements for landing and sending men and matériel towards the camps.[20]
This placed Anderson at the most vulnerable point in the operational supply chain. Stores and personnel arriving by sea had to be landed, sorted and moved inland before congestion developed on the beach. Delays at Opunake could affect the entire mobilisation.
Anderson’s subsequent recognition for clothing and rationing the Volunteers and Constabulary, and for assisting with the transport of Māori removed from Parihaka, reflected the breadth of his contribution.
Contractors as part of the operational system
The colonial government did not possess a permanent organisation large enough to provide every ration, horse, dray, item of forage or temporary service required by the field force.
Private contractors therefore became an extension of the military establishment.
Ration contractors supplied food to the camps. Farmers and merchants supplied forage. Shipowners and coastal shipping companies moved personnel and stores. Carriers provided horses, carts and drays. Local tradesmen supplied farriery and other services.
Contracts reduced the quantity that had to be permanently held in government stores, but they also created dependency. The operation relied upon local availability, commercial performance, contract supervision and private suppliers’ ability to meet a sudden increase in demand.
Modern doctrine recognises contracted support as a means of increasing a deployed force’s capacity without transporting every requirement from its permanent base.[21] The same principle was visible at Parihaka, although expressed through nineteenth-century government tenders and local purchasing.
Supplying food to the camps
Feeding the West Coast force was a continuous requirement from 1879 onwards.
The government relied upon ration contractors for much of the food required by the Armed Constabulary. Roberts confirmed that the contractor landed several cargoes at Opunake, although the surviving report does not identify the individual or firm involved.[22]
Bread or biscuit, meat, tea, sugar and other staples had to be delivered regularly. Fresh meat required local slaughtering or prompt distribution. Flour, biscuits, tea and sugar had to be protected from damp, vermin and loss.
The contractor system did not remove government responsibility. Officials still had to estimate requirements, inspect deliveries, verify quantities and arrange emergency supply when weather prevented a steamer from landing.
The supply chain remained vulnerable at several points:
vessels could be delayed by weather;
surf conditions could prevent unloading;
insufficient drays might be available at Opunake;
roads could deteriorate after rain;
stores could be delayed between the beach and the camps;
food could be present in bulk but fail to reach individuals in a usable form.
What did it take to supply 1,589 men?
The surviving records do not provide a complete manifest of every ration, blanket, cartridge or tent issued for the operation. Nevertheless, the official strength of 1,589 officers and men, combined with contemporary ration and ammunition practices, permits an estimate of the scale of the operation.
These calculations are not surviving issue totals. They indicate the probable order of magnitude.
Two days’ rations
Contemporary New Zealand Volunteer ration scales varied. Some camps provided approximately one and a half pounds each of bread and meat per man daily, while later scales were closer to one pound of bread, three-quarters of a pound of meat and one pound of potatoes.
Applying these ranges to 1,589 men for two days produces the following estimate:
Commodity
Estimated requirement for two days
Bread or biscuit
3,178–4,767 lb, approximately 1.44–2.16 tonnes
Meat
2,384–4,767 lb, approximately 1.08–2.16 tonnes
Potatoes
approximately 3,178 lb, or 1.44 tonnes
Sugar, at 3 oz per man daily
approximately 596 lb, or 270 kg
Tea, at ½ oz per man daily
approximately 99 lb, or 45 kg
Coffee, if issued at ½ oz daily
approximately 99 lb, or 45 kg
Salt, at 1 oz per man daily
approximately 199 lb, or 90 kg
Even the lower estimate represents more than four tonnes of bread, meat and potatoes. Once sugar, tea, salt, packaging, officers’ mess supplies and reserve provisions were included, the two-day food load may have approached five or six tonnes.
Not all of this necessarily travelled in one convoy. Contemporary reports state that the men carried two days’ provisions during the advance, while additional supplies were left in camp or transported.
Ammunition
The ammunition requirement can be estimated more firmly.
A report from Rahotu stated that Volunteers received eighty rounds of ball ammunition each. The official account recorded that the men carried forty additional rounds during the advance. A likely explanation is that forty rounds formed the normal pouch issue and another forty were added as an operational reserve.[23]
For 1,589 men:
forty rounds each represented 63,560 cartridges;
eighty rounds each represented 127,120 cartridges.
Not every member necessarily carried a rifle. Staff, medical, mounted and transport personnel may have held different scales. Even so, more than 120,000 rounds is a reasonable estimate of the personal ammunition issued or immediately available.
This was not the whole operational reserve. Additional ammunition accompanied the columns on packhorses, while a larger reserve remained at Pungarehu.
The total number of cartridges positioned in the operational area was therefore probably greater than 127,120.
The colonial reserve could support this demand. In April 1881 the Volunteer Force held 1,265,884 Snider rounds in store.[24] An issue of 127,120 rounds represented approximately one-tenth of that reserve.
Tents and accommodation
The exact number of tents sent to Taranaki has not been identified.
At a reasonable field scale of six to eight men per bell tent, accommodating all 1,589 personnel under canvas would have required:
approximately 199 tents at eight men per tent;
approximately 265 tents at six men per tent.
These figures cover sleeping accommodation only. Additional tents or marquees were needed for headquarters, officers, medical treatment, guards, stores, kitchens, messes and ammunition.
Allowing another ten to fifteen per cent for these functions raises the estimated requirement to approximately 220–300 tents and marquees.
Not all had to be newly issued. Huts, redoubts, cookhouses and store buildings at Pungarehu, Rahotu, Opunake and Manaia reduced the number sleeping under canvas.
Nevertheless, evidence indicates that the available camp equipment did not meet the theoretical requirement. A history of the Volunteer Force describes a serious shortage of camp equipment. The Nelson contingent arrived without its own camp gear and received only one blanket per man and tents that were far from watertight.[25]
The shortage was therefore not merely numerical. Some of the canvas supplied was unsuitable for prolonged exposure to Taranaki weather.
Blankets and waterproof sheets
Reports stated that the advancing troops carried a blanket, a coat or greatcoat and a waterproof sheet.
At a minimum scale of one per man, the force required:
1,589 blankets;
1,589 waterproof or ground sheets.
A ten per cent reserve for hospital use, damage, loss and late reinforcements would raise each requirement to approximately 1,750.
The Nelson experience demonstrates that even the one-blanket scale may have represented the maximum actually available rather than a comfortable allocation.
Blankets and waterproof sheets were bulky. Once wet, they became much heavier and required drying before they could be packed or reissued. The collapse of tents in bad weather placed bedding and clothing at particular risk.
Cooking and mess equipment
A force of 1,589 men could not be efficiently fed from individual cooking fires.
At a notional company or mess strength of eighty to one hundred men, at least sixteen to twenty cooking and ration-distribution groups were required. Each needed:
camp kettles or boilers;
meat hooks and knives;
cutting surfaces;
buckets and water containers;
ration bags and boxes;
fuel;
serving utensils;
pannikins, plates and cutlery.
Cookhouses had already been built at Oeo and Oakura, while Pungarehu contained cookhouses, storehouses and mess facilities. The permanent camp network therefore provided a foundation for the expanded force.
Contemporary complaints that some Volunteers lacked plates, pannikins, knives and forks show that mess equipment did not always match the number of men assembled.[26]
Food could be present within the supply system yet remain difficult to distribute or consume.
Water
The sources provide no formal daily water allowance, and even a restricted estimate of three to five litres per man for drinking and cooking would require approximately 4,800 to 7,900 litres each day.
This excludes water needed for washing, hospitals, cooking losses and animals.
For 1,589 men, one week of drinking and cooking water would therefore amount to approximately 34,000–55,000 litres.
Camp selection had to take account of reliable streams or other sources. The division of the force between Rahotu, Pungarehu and positions around Parihaka may partly have reflected the limits of local water supply as well as tactical requirements.
The thirty-three Volunteer corps
On 28 October 1881 the Governor’s proclamation called out no fewer than thirty-three Volunteer corps from the North Island and Nelson. So many additional offers were received that the government rejected some.[27]
This fragmented structure created a considerable administrative burden. The government was not receiving a single homogeneous formation but more than thirty separately organised units, each with its own officers, rolls, uniforms, arms, baggage, and standards of camp equipment.
The forward camps had to receive these corps, confirm their strength, complete equipment issues and integrate them into the two operational columns.
The Wellington contingent alone numbered 231. At a scale of six to eight men per tent, it required between twenty-nine and thirty-nine sleeping tents, in addition to at least 231 blankets, ground sheets and sets of eating equipment.[28]
Horses, forage and local military agriculture
Horses were essential to the operation.
Mounted constables carried messages, patrolled roads and escorted prisoners. Officers required mounts, packhorses carried reserve ammunition and draught animals hauled wagons and drays loaded with provisions, tentage and baggage.
The precise number of horses is unknown, so forage can only be presented as an illustrative scenario.
At approximately twenty-four pounds of combined hay, chaff and grain per horse daily:
Horses
Daily forage requirement
100
approximately 2,400 lb, or 1.09 tonnes
150
approximately 3,600 lb, or 1.63 tonnes
200
approximately 4,800 lb, or 2.18 tonnes
A force using 150 horses could therefore consume more than eleven tonnes of forage in one week if grazing did not reduce the requirement.
The 1881 Constabulary report shows that the government had deliberately developed local forage production:
twenty-three acres of oats at Waihi were cut for hay, converted into chaff and distributed among coastal stations;
thirty-four acres at Manaia were prepared for cultivation;
twenty-acre paddocks were established at Opunake and Pungarehu;
further paddocks were maintained or developed at Egmont, Okato and Pukearuhe.[29]
This amounted to a small military agricultural system. It reduced dependence upon stores landed at Opunake and provided grazing and fodder close to the camps.
The paddocks were as much a part of the military infrastructure as redoubts and magazines.
Wagons, drays and pack animals
The number of vehicles employed is also uncertain, but the estimated ration load helps convey the likely scale.
If a dray could carry between ten and fifteen hundredweight over imperfect roads, five tonnes of provisions alone required approximately seven to eleven dray loads.
That calculation excludes:
tents and marquees;
blankets and ground sheets;
ammunition reserves;
officers’ baggage;
camp tools;
cooking equipment;
hospital stores;
forage;
telegraph and engineering material.
The total number of vehicle movements required for mobilisation and continued occupation must have been considerably greater.
Some stores travelled in repeated shuttle runs between Opunake, Rahotu, and Pungarehu. Packhorses carried high-priority loads, including reserve ammunition, while wagons and drays handled bulk provisions and baggage.
Other vehicles had to remain available for casualties, prisoners, water and the removal of Māori from Parihaka.
A layered distribution system
Later military manuals described supply systems based upon depots, delivery points, pack trains and mobile reserves.[30] Although the terminology belongs to a later period, the surviving evidence suggests that the Parihaka system operated in comparable layers:
central reserves and procurement at Wellington and other districts;
coastal shipping to Opunake or New Plymouth;
transfer through the surf and sorting ashore;
forward stocks at Rahotu and Pungarehu;
mobile wagon and packhorse loads;
personal issues carried by each man.
This structure allowed the force to advance without carrying everything needed for a prolonged occupation. It also preserved reserves behind the columns.
The same arrangement created risk. A delay at any layer could affect the others. Coastal weather could interrupt shipping, insufficient drays could delay inland movement and poor unit distribution could create shortages even when bulk stocks were available.
Telegraph and information logistics
The telegraph was another component of the physical support system.
Telegraph communication required poles, wire, insulators, batteries, tools and trained operators. Roberts’s report that Telegraph Department cargo was landed at Opunake confirms that these materials passed through the same maritime supply chain as rations and military stores.[31]
By 1880 the coastal telegraph had connected the forward district more closely with New Plymouth, Hawera and Wellington.
The telegraph reduced the time required to request supplies, report developments and transmit orders, but it did not remove the need for mounted messengers and local orderlies. Messages still had to be distributed from telegraph offices to camp headquarters, detachments and road parties.
Information was another commodity that had to be moved, received and delivered.
Medical support
The permanent medical organisation was comparatively thin.
Serious cases from the West Coast camps were sent to a hospital established in part of the Immigration Barracks at New Plymouth. The hospital treated an average of approximately fourteen cases a month, while one medical officer supported the West Coast force.[32]
The temporary increase from 522 Armed Constabulary personnel in the district to a combined force of 1,589 placed additional pressure on this limited arrangement.
A later history of the Volunteer Force describes the medical support available during the occupation as rudimentary and unlikely to have coped with a significant number of casualties.[33]
Medical support required hospital tents or buildings, bedding, medicines, dressings, transport for the sick or injured, clean water, suitable food and attendants.
The medical organisation proved adequate principally because no battle occurred. Men nevertheless collapsed during the marches, and prolonged exposure to wet weather created risks of fever and respiratory illness.
Life under canvas
Much of the permanent West Coast force had already spent long periods under canvas.
The 1880 Constabulary report recorded that more than 700 men had been exposed to very wet weather while living largely in tents. Despite this, only one death from sickness was reported.[34]
Maintaining troops under canvas required tent poles, pegs, ropes, blankets, ground sheets and constant repair. Camps needed drainage, latrines, cooking areas and dry storage for provisions and ammunition.
The construction of cookhouses at Oeo and Oakura, and huts at Pungarehu, reflected the limitations of prolonged tented accommodation.
The final mobilisation intensified the problem. Newspaper reports described difficulty obtaining sufficient tents for the arriving Volunteers. A gale at Opunake reportedly flattened many of the Wellington Naval Volunteers’ tents shortly before the march.[35]
Such incidents increased the troops’ workload and put bedding, clothing, and equipment at risk.
Reception, staging and onward movement
Landing the Volunteers was only the first stage of mobilisation.
Units had to be reunited with baggage, supplied with ammunition and camp equipment, assigned accommodation and incorporated into the two operational columns.
In modern terminology this process would be described as reception, staging and onward movement.[36] The terminology is much later, but it accurately describes the sequence.
Opunake and New Plymouth received the units from coastal shipping. Rahotu and Pungarehu staged them while their equipment and ammunition issues were completed. The camps then released formed columns for the movement towards Parihaka.
These camps were not merely sleeping areas. They converted separately raised and transported corps into an organised field force.
Coastal shipping and the Hinemoa
Figure 5. The government steamer Hinemoa, Painting by Frank Barnes, 1911 -Online collections of the Museum of New Zealand (Te Papa Tongarewa), at: http://collections.tepapa.govt.nz/
During October and early November 1881, government and commercial vessels, including the Hinemoa, Stella, Huia and Manawatu, transported men and equipment to Taranaki.
On 25 October the Hinemoa embarked 205 personnel from Nelson and Marlborough, together with a six-pounder Armstrong gun. Approximately 4,000 people attended their departure from Nelson.
The vessel was intended to land the contingent at Opunake but was diverted to New Plymouth. The Volunteers then had to march south towards the front.[37]
The incident illustrates the flexibility required of the transport system. A change of landing place affected not only the troops but their baggage, rifles, ammunition, camp equipment and the field gun.
The six-pounder also confirms that the material burden was greater than rifles and personal baggage alone. The gun required its own crew, ammunition, equipment and transport.
Equipping the Volunteers
The rapid mobilisation produced inconsistencies in equipment.
Some corps arrived with complete local issues, while others required additional ammunition, blankets, clothing or camp equipment. One newspaper report alleged that Wellington Volunteers left the government store only partly equipped and that they initially held 40 rounds in their ball bags.[38]
A later account from Rahotu stated that eighty rounds of ball cartridge were issued to each Volunteer.[39]
The reports show that equipping the force was not a single event completed at the home station. Stores continued to be inspected, supplemented and redistributed after the contingents reached Taranaki.
The final concentration
The final force totalled 1,589 officers and men.
Major Charles Pitt commanded a Volunteer column of approximately 945, while Major Arthur Tuke commanded approximately 644 Armed Constabulary and Taranaki Volunteers.[40]
The force was broadly comparable in size to the population of Parihaka, which had exceeded 1,300 earlier in the year. This comparison helps explain the government’s intention to dominate the settlement through overwhelming numbers.
By late October the force had converged upon Rahotu and Pungarehu. The Volunteer component had been drawn from thirty-three separately administered corps and integrated into two battalions supporting the Armed Constabulary.
Figure 6.Armed Constabulary awaiting orders to advance on Parihaka Pa. Parihaka album 1. Ref: PA1-q-183-19. Alexander Turnbull Library, Wellington, New Zealand. /records/23044695.
Figure 7. The two columns converging on Parihaka, 5 November 1881.
On 5 November 1881, the two principal columns advanced from Pungarehu and Rahotu.
Contemporary reports stated that the men carried two days’ provisions, blankets, coats or greatcoats, waterproof sheets and ammunition. The official account recorded an additional forty rounds per man.[41]
The load was considerable. A rifle and eighty Snider cartridges represented significant weight. When food, bedding, clothing and personal equipment were added, the march became physically demanding.
Observers described Volunteers struggling in warm weather beneath heavy swags. Several men collapsed or required medical attention.
The individual load was only the first layer of supply. Reserve ammunition travelled on packhorses with the columns, while a larger reserve remained at Pungarehu.
The two days’ provisions represented only the initial operational load. They allowed the columns to leave camp without depending upon immediate replenishment, but they did not sustain the subsequent occupation.
Once the force dispersed around Parihaka, daily delivery of food, forage, fuel, water and other supplies again became necessary.
Friction within the system
The force reached Parihaka and completed its encirclement, but the mobilisation was not seamless.
One newspaper account claimed that seventy-eight Naval Volunteers received only about ten pounds of meat during part of their transport and that plates, pannikins, knives and forks had not been provided. Another contingent reportedly found only about twenty bunks for fifty-eight men.[42]
Such complaints require caution, but they illustrate the difference between holding supplies and delivering them effectively.
A successful system had to provide the right commodity, in the right quantity, at the right place and time, together with the means to use it.
Meat was of limited value without cooking facilities or utensils. Blankets offered little protection if tentage failed and became soaked. Ammunition at a rear depot could not support the force unless transport remained available.
The operation succeeded because the system possessed sufficient overall capacity, not because every part worked efficiently.
Sustaining the occupation
The logistical requirement continued after the troops entered Parihaka.
The force was dispersed among several camps around the settlement. Headquarters and Armed Constabulary elements occupied positions to the west and north-west, while Volunteer camps were established to the north, east and west.
The dispersed arrangement improved control but complicated supply. Provisions, fuel, water and orders had to be distributed among several positions. Ammunition and baggage left at Pungarehu and Rahotu remained under guard.
Fuel was partly obtained locally. In the days following the occupation, men were reported collecting firewood around the camps.[43]
The force also required working parties for searches, guards, escorts and demolition. Horses, carts and personnel had to be allocated among competing requirements.
Transporting prisoners and displaced families
The same transport network that brought troops and stores to Parihaka was also used to remove people from the settlement.
Te Whiti and Tohu were taken by wagon to Pungarehu under mounted escort. During November nearly 1,600 Māori men, women and children were sent under escort towards their home districts.[44]
Some groups were marched overland. Others were taken to Opunake and transported by sea.
The movement required:
groups to be organised by district;
escorts to be detailed;
routes to be selected;
wagons and drays to be allocated;
vessels to be scheduled;
provisions to be supplied during movement.
The transport burden therefore extended beyond supporting the colonial force. It included the coercive dispersal of a civilian population similar in size to the force itself.
Anderson’s recognised involvement in these arrangements demonstrates how closely Defence Stores and transport became connected with government policy.
Demolition as a logistical operation
During November and December 1881 Crown forces dismantled houses and destroyed fences and cultivations at Parihaka.
These actions required logistical organisation. Working parties needed axes, crowbars and other tools. Guards and supervisors had to be provided. Men required rations while engaged in the work, and transport had to remain available.
The destruction of crops was particularly significant. Parihaka’s population had been sustained through extensive gardens, pastures and communal production.
The government therefore sustained its own force while deliberately degrading the system by which Parihaka sustained itself.
Logistics at Parihaka had both a sustaining and a destructive dimension.
Demobilisation and the reverse supply chain
Once the settlement had been occupied and much of its population dispersed, the Volunteer contingents were progressively released.
The process reversed mobilisation. Units returned to Rahotu or Opunake, baggage was assembled, vessels allocated, troops embarked, and weapons, ammunition and equipment accounted for.
Rifles, unused ammunition, tents, blankets and other government property had to be returned, transferred to permanent posts or written off if lost or damaged.
By 20 November only the Taranaki Mounted Rifles remained on active service.[45] In approximately two weeks the support system had to reverse the concentration and return hundreds of Volunteers to their home districts.
Later ordnance manuals described return, inspection, repair, salvage and disposal as integral parts of the supply system.[46] The same principle is evident in contemporary financial records.
The 1880–81 public accounts recorded recoveries from the sale of Constabulary stores, clothing, accoutrements, troop horses and forage, as well as proceeds from Militia and Volunteer arms, ammunition and stores.[47]
Demobilisation therefore created a reverse supply chain. Equipment moved from units to camp stores, from the camps to Opunake and from the coast back to district or central custody.
The permanent Armed Constabulary remained, occupying posts and resuming road construction and patrol duties.
Destination, demand, distance, duration and dependency
The logistical difficulty can be summarised through five connected factors identified in later doctrine: destination, demand, distance, duration and dependency.[48]
Destination: Parihaka lay beyond the colony’s principal ports and railways. Final movement depended upon surf-landings, roads, drays and packhorses.
Demand: The supported military population increased from 522 Armed Constabulary personnel in Patea and Taranaki to 1,589 officers and men. The force also had to control and disperse a Parihaka population of more than 1,300.
Distance: Personnel and stores travelled from Wellington and other districts by rail and sea before transfer to road transport.
Duration: The requirement extended far beyond the two-day march. It included preparation since 1879, the November concentration, the occupation and the continuing Constabulary presence.
Dependency: The system depended upon commercial shipping, contractors, horses, roads, paddocks, telegraph communications and favourable weather at Opunake.
A failure in any one area could affect the whole operation.
The financial framework
The cost of preparing for and occupying Parihaka cannot be found in one account.
For 1880–81 the Consolidated Fund appropriations allocated £163,446 11s. 3d. to the Minister of Defence.[49] At the same time, the Public Works Fund included £154,000 for contingent defence, together with substantial votes for roads, telegraph extensions and public buildings.[50]
For 1881–82 the gross Defence vote was £217,014 12s. 2d., of which £75,000 was recoverable from loan funds, leaving a net Consolidated Fund charge of £142,014 12s. 2d.[51]
These figures did not represent Parihaka alone. They included wider expenditure on the Militia, Volunteer, Police, and Armed Constabulary. Nevertheless, they show that the operation drew upon both ordinary Defence appropriations and loan-funded infrastructure.
Its costs were dispersed among:
Armed Constabulary pay and allowances;
Militia and Volunteer expenditure;
arms and ammunition;
Defence Stores;
coastal shipping;
road construction;
telegraph extension;
public buildings and redoubts;
provisions and forage;
contingent defence;
transport and miscellaneous services.
The administrative separation concealed the extent to which these activities formed a single operational system.
Parihaka viewed as a logistical system
The operation can be understood as a series of connected support nodes.
Wellington provided personnel, arms, ammunition and central administration. Coastal shipping moved units and bulk supplies to Taranaki. Opunake acted as the maritime transfer and bulk-breaking point. New Plymouth served as an alternative landing point when weather prevented the use of Opunake. Rahotu and Pungarehu provided accommodation, staging and forward stores. Wagons and packhorses carried reserves towards the columns, while individual men carried the final personal load.
The system displayed considerable foresight. Arms were packed for rapid despatch, ammunition and stores were accumulated at principal stations, roads were opened for wheeled traffic, camps were established progressively along the coast, telegraph communications were extended, and paddocks were developed near the forward posts.
By November 1881, the government no longer needed to create a supply system from scratch. It enlarged and accelerated a network that had been under development since 1879.
The force’s operational reach was determined by the network’s reach.
Conclusion
The occupation of Parihaka on 5 November 1881 was not an isolated or improvised military event. It was the culmination of a logistical build-up that began during the West Coast emergency of 1879: two years spent concentrating personnel, accumulating weapons and ammunition, building roads, establishing camps, developing forage resources, extending telegraph communications and turning Opunake into a coastal supply point. By November 1881 the government did not need to build a supply system from nothing — only to enlarge and accelerate one already two years in development.
That system is why the numbers in this article are worth taking seriously, even as estimates rather than surviving issue totals. A force of 1,589 men required tonnes of food and forage, hundreds of tents, thousands of blankets, more than 100,000 rounds of ammunition, and a coastal supply chain that ran through open surf at Opunake. None of it arrived by accident, and none of it was inevitable — it was the product of deliberate choices made over two years, by identifiable officials, using identifiable roads and ships and contracts.
It was also, on its own terms, an imperfect system. The Nelson contingent, leaky tents, the diverted Hinemoa, and the missing plates and cutlery were all signs of a system under strain. It succeeded not because every part worked smoothly, but because it had enough capacity to absorb the parts that didn’t.
None of that capacity was neutral. The same roads that carried rations and ammunition to Rahotu and Pungarehu carried the wagons that took Te Whiti and Tohu into custody and dispersed nearly 1,600 people from their homes. The same working parties that built cookhouses and redoubts later dismantled houses and destroyed the gardens that had sustained Parihaka’s own, larger population. The government sustained its force and dismantled the community’s capacity to sustain itself using the same logistical apparatus, often the same men, in the same weeks.
That is the lesson Parihaka offers for New Zealand’s military logistics history: the systems that feed, clothe, transport and equip a force are never separate from the policy that force carries out. At Parihaka, that apparatus made possible not a battle, but the systematic occupation and dismantling of a peaceful community.
A note on the present
The five factors that shaped the Parihaka operation- destination, demand, distance, duration and dependency are not confined to 1881. They describe a structural problem New Zealand’s military still faces in its most probable operating environment: the Pacific.
Opunake had no harbour. Steamers anchored offshore, and every box of ammunition, bag of rations and coil of telegraph wire had to pass through surf boats before it reached dry land. That transfer point, not the road or the rifle, was the operation’s real constraint. The same problem persists in the Pacific today in different form: American logistics remain unmatched but depend on deep ports and long runways, both of which are scarce across the region, and current commentary on New Zealand’s defence posture argues this is precisely where investment should be directed — vehicles, ships and capabilities built for Pacific conditions rather than for the ports New Zealand’s larger partners can rely on elsewhere.[52] Anderson’s beach parties at Opunake and a modern sealift or littoral capability designed for undeveloped Pacific coastlines are answers to the same question, asked 140 years apart.
The Crown’s advantage in 1881 was not the size of the force it could raise in a crisis, but the network it had already built before the crisis arrived — camps, roads, forage paddocks and standing contracts, developed over two years so that the final concentration was an acceleration rather than a creation. Current strategic writing on New Zealand’s regional posture makes a comparable argument at Pacific scale: with the South China Sea heavily fortified, the less congested Pacific has become a more attractive arena for influence, and whoever secures logistics hubs there first will hold the advantage.[53] Read against Parihaka, this is not a new insight so much as a familiar one restated for a different theatre — pre-positioning and regional access are usually worth more than surge capacity assembled after the fact.
The paper’s account of the Defence Storekeeper’s dependence on contractors, forage, and shipping he did not control has a direct present-day analogue as well. New Zealand’s Defence Industry Strategy now explicitly builds toward shared regional repair capacity through the Partnership for Indo-Pacific Industrial Resilience, on the reasoning that the ability to repair equipment without returning to New Zealand is critical to operational effectiveness.[54] Contracted and locally sourced support extended the Crown’s reach at Opunake in exactly the way it is meant to extend the NZDF’s reach across the Pacific now — and it carried the same trade-off then as it does today: capacity gained through dependency is only as reliable as the party it depends upon.
None of this suggests a direct institutional lineage between the Armed Constabulary’s supply arrangements and NZDF planning today. The doctrine, the technology and the strategic context are entirely different. What carries over is the underlying structure of the problem: a small force, operating at the end of a long and interruptible supply chain, in a theatre with few deep harbours and fewer long runways, dependent on contractors, shipping and weather it cannot control. Parihaka is a reminder that this is not a new condition for New Zealand’s military to solve — only the latest occasion for solving it again.
Notes
[1] Australian Army, “Logistics,” Land Warfare Doctrine 4.0 (2018): 5, 9; U.S.G.U. Army, Field Manual FM 4-0 Sustainment Operations July 2019 (Washington, DC: Department of the Army, 2019), 1-1–1-8.
[2] Judith Binney and Aroha Harris Atholl Anderson, Tangata Whenua: An Illustrated History (Bridget Williams Books, 2014), 264-65.
[3] Atholl Anderson, Tangata Whenua: An Illustrated History, 264.
[11] Garry Clayton, The New Zealand Army: A history from the 1840’s to the 1990’s ([Wellington, N.Z.]: New Zealand Army, 1990, 1990), , 34-39; Paul William Gladstone Ian McGibbon, The Oxford companion to New Zealand Military History (Auckland; Melbourne; Oxford: Oxford University Press, 2000, 2000), .
[12] “Public Works Statement by the Honourable Minister for Public Works,” Appendix to the Journals of the House of Representatives 1881 Session I, D-01 (10 August 1881).
[13] Peter D. F. Cooke, Won by the spade: how the Royal New Zealand Engineers built a nation (Exisle Publishing Ltd, 2019), Bibliographies, Non-fiction, 114-15; Peter Cooke and John Crawford, The Territorials (Wellington: Random House New Zealand Ltd, 2011), 78-80.
[47] “Public Accounts of the General Government of New Zealand, for the Financial Year 1880-81 Commencing 1 April 1880 and Ending 31 March 1881,” Appendix to the Journals of the House of Representatives 1881 Session I, B-01 (9 October 1881), https://paperspast.natlib.govt.nz/parliamentary/AJHR1881-I.2.1.3.1.
[49] The Honourable J Ballance, The Colonial Treasurer, “Financial Statement By the Colonial Treasurer the Hon Major Atkinson 6th July 1881,” Appendix to the Journals of the House of Representatives, 1881 Session I, B-02 (1881), https://paperspast.natlib.govt.nz/parliamentary/AJHR1881-I.2.1.3.2.
Ian McGibbon, Paul William Gladstone. The Oxford Companion to New Zealand Military History. Auckland; Melbourne; Oxford: Oxford University Press, 2000, 2000. .
“Public Accounts of the General Government of New Zealand, for the Financial Year 1880-81 Commencing 1 April 1880 and Ending 31 March 1881.” Appendix to the Journals of the House of Representatives 1881 Session I, B-01 (9 October 1881). https://paperspast.natlib.govt.nz/parliamentary/AJHR1881-I.2.1.3.1.
“Public Works Statement by the Honourable Minister for Public Works.” Appendix to the Journals of the House of Representatives 1881 Session I, D-01 (10 August 1881).
The Colonial Treasurer, The Honourable J Ballance. “Financial Statement by the Colonial Treasurer the Hon Major Atkinson 6th Ju;Y 1881.” Appendix to the Journals of the House of Representatives, 1881 Session I, B-02 (1881). https://paperspast.natlib.govt.nz/parliamentary/AJHR1881-I.2.1.3.2.
Today, 12 July, would have been Corps Day for the Royal New Zealand Army Ordnance Corps. It also marks thirty years since the formation of the Royal New Zealand Army Logistic Regiment and, with it, the disestablishment of the RNZAOC. It is a fitting moment to look back, not with sentimentality but with appreciation for what the Corps actually was and what it left behind.
The RNZAOC was not lost so much as it moved into its next form. From the days of Henry Tucker onwards, the work of the Ordnance soldier was defined by one constant: continual adaptation. Its history is best understood not as that of a fixed institution that came to an end, but as one long process of change that continues today, under a different name.
Formed in war, tested by peace
The role of the Ordnance soldier expanded and contracted as the Army’s needs shifted around it. During the First World War, New Zealand Ordnance personnel served both at home and overseas, in Egypt, Gallipoli, Palestine, France, Belgium and the United Kingdom.
The interwar years brought progress alongside considerable uncertainty, including a period when the New Zealand Army Ordnance Corps came close to ceasing to exist altogether.
Mechanisation and a widening trade
The Second World War forced rapid adaptation once more. Ordnance soldiers served in every theatre in which New Zealand forces took part, adjusting to the demands of increasingly mechanised warfare. Bath and laundry services, ammunition support and specialist technical functions all became central to the Corps’ work during this period.
The later transfer of the Technical Trades to the New Zealand Electrical and Mechanical Engineers fits the same pattern rather than breaking from it. As military technology and technical specialisation advanced, responsibilities moved to where they made most sense — a recurring feature of the Corps’ story, not an exception to it.
A peacetime Corps that kept changing
Adaptation did not stop when the wars ended. Territorial Force personnel became an integral part of the RNZAOC, and the increasingly specialised management of technical stores gave rise to the Auto Parts trade. The Ammunition Technician trade evolved alongside the operational environment and, by the 1970s, had become the Army’s centre of expertise in explosive ordnance disposal.
Further change followed: the integration of women from the Women’s Royal New Zealand Army Corps, and then the transfer of the RNZASC supply trades into the RNZAOC in 1979. Less visibly, Ordnance personnel also adapted to the gradual introduction of electronic stores-management systems, progressing from early mainframe systems to the networked logistics systems in use by 1996.
The Corps at its height
By the mid-1980s, the RNZAOC had reached its peak. 1 Base Supply Battalion was, at the time, regarded as one of the most complex warehouse operations in New Zealand. Supply Companies were located at Hopuhopu, Waiouru, Linton and Burnham. Separately, stores sections were integrated within each RNZEME workshop, while an Advance Ordnance Depot maintained a New Zealand presence in Singapore. It was a Corps operating at scale, both at home and abroad.
That scale did not last. With the end of the Cold War came a peace dividend, and with it a gradual reduction in the size and reach of the Corps through the late 1980s and into the 1990s. This, too, was adaptation rather than decline for its own sake, the Corps reshaping itself to match a changed strategic environment, as it always had.
Towards Formed Deployments
RNZAOC soldiers had already deployed on operations in Korea, Malaya, Malaysia and South Vietnam, and others had served individually on peacekeeping missions. The 1990s added a further dimension, as Ordnance soldiers began deploying on operations as formed contingents, beginning with a Supply Detachment to Somalia, followed by two platoons, a shift that reflected both New Zealand’s changing military commitments and the increasingly integrated role of logistics support.
A Corps Spanning Generations
When the RNZAOC was disestablished in 1996, its youngest member was 17 years old and its oldest was 55. That span was more than a statistic. It represented a Corps that connected multiple generations of officers and soldiers, from those trained in long-established manual systems to those entering an increasingly digital and integrated logistics environment, within a single institution, at a single moment.
Continuity, Not Loss
The formation of the RNZALR did not erase the RNZAOC’s history; it became the next stage in a much longer process of adaptation. Titles, structures and trades changed, but the essential purpose held: to provide the Army with the equipment, ammunition, technical support and supply services needed to train, deploy and operate.
Thirty years on, the most fitting way to remember the RNZAOC is not to mourn its passing, but to recognise its enduring legacy, carried forward today within the RNZALR, particularly through its Supply trade. Adaptation was never evidence of weakness or decline. It was, and remains, one of the Corps’ defining strengths.
Logistics for New Zealand’s Motorised Infantry Future
From 1845 to the present, New Zealand’s military logistics system has continually adapted under pressure. Across the history of the Defence Stores Department, the New Zealand Army Service Corps, the New Zealand Army Ordnance Corps, the Royal New Zealand Army Ordnance Corps, Royal New Zealand Electrical and Mechanical Engineers and Royal New Zealand Corps of Transport and today’s Royal New Zealand Army Logistic Regiment, the pattern is consistent. Each generation entered conflict organised for one set of assumptions, then adapted its structures, equipment, trades and methods as war exposed the limits of the old system.
That pattern is visible across the long history of New Zealand military logistics. Colonial forces moved from ad hoc local supply to centralised control of stores. The late nineteenth century saw the creation of a system capable of supporting breech-loading artillery, harbour defence, and increasingly complex imported weapons. The First and Second World Wars forced expeditionary supply, transport, ordnance, movement control, field catering, mobile repair and ammunition systems to mature at scale. Later reforms adjusted stores accounting, entitlement control, field-force logistics, ration packs, mechanical support, combat clothing, and digital supply systems to suit new technology and new structures.
The lesson is simple. New Zealand Army logistics has rarely succeeded because it possessed mass. It has succeeded when it adapted faster than its circumstances collapsed around it.
That lesson now matters again.
In December 2025, the New Zealand Army formally amalgamated 1st Battalion, Royal New Zealand Infantry Regiment and Queen Alexandra’s Mounted Rifles at Linton Military Camp. The new unit retained the name 1 RNZIR and was organised as a Motorised Infantry Battalion, with one sub-unit retaining the QAMR name. NZDF described the change as enhancing the combat readiness of one of the Army’s key outputs, the Motorised Infantry Battle Group.[1]
The formation of 1 RNZIR as a Motorised Infantry Battalion at Linton provides the organisational trigger for rethinking how New Zealand Army logistics supports a more dispersed and agile force.
This is more than a unit name change. It is a force design signal. If the combat arm is reorganising around a motorised infantry model, then the sustainment system must be examined with the same seriousness. A motorised infantry battalion can only be as agile, lethal and survivable as the logistics system that fuels it, arms it, repairs it, feeds it, moves it and replenishes it.
The danger is that the Army could create a modern combat structure sustained by an older, more predictable and increasingly vulnerable distribution model.
The Future Battlefield and the Logistic Problem
The Future Land Operating Concept 2035 anticipated many of the challenges now visible in Ukraine and other contemporary theatres. It described the future land environment as increasingly connected and monitored, crowded, partnered, lethal and complex. It also acknowledged that, by international standards, the New Zealand Army would remain a small army with limited firepower and protection compared with medium or heavy forces. To remain relevant, it would need a qualitative edge built around agility, precision, interoperability, information advantage and force-multiplier strategies.[2]
That description fits the logistics problem exactly.
The modern battlefield is becoming more transparent. Drones, commercial satellites, electronic surveillance, social media, signals intelligence and persistent sensors make movement easier to detect. Convoys, vehicle parks, fuel points, ammunition dumps, replenishment points and headquarters are no longer safely “behind” the front line. They are part of the target set.
At the same time, forces are becoming more dispersed. Lethality drives dispersion, and dispersion drives logistic complexity. Smaller groups need to operate further apart, for longer, with fewer opportunities for large-scale replenishment. This increases demand for batteries, water, medical stores, ammunition, repair parts, communications equipment, drone components, fuel and specialist technical support at the tactical edge.
Ministry of Defence images of NZ Army personnel testing small UAS at Waiouru
For a large army, this problem may be partly solved by mass. For New Zealand, mass is not available. The answer must be a more intelligent, distributed and layered sustainment system.
Logistic drones should be part of that system.
But none of this is one-directional. A battlefield transparent enough to expose a fuel point is also transparent enough to reveal a drone charging station, an unmanned ground vehicle route, or a field 3D-printing node. Ukraine’s experience since 2022 shows how quickly forces adapt counter-drone measures, including layered air defence, electronic warfare, decoys and dedicated drone-hunting teams. Any New Zealand logistic drone system must therefore assume that the enemy will adapt to it, just as quickly as it seeks to outmanoeuvre the enemy.
Illya Sekirin makes the same point in Rise of the Machines. His central argument is not simply that drones are important, but that technology only becomes decisive when tactics, organisation, procurement, training and strategy are adapted around it. He compares the drone to the tank, noting that tanks existed in the First World War but did not become operationally decisive until armies learned how to organise and fight around them. The same warning applies to logistics. A drone purchased as equipment is not a capability. A drone integrated into sustainment, reconnaissance, protection, maintenance, counter-drone defence and command arrangements may become one.[3]
This is not theoretical. In March 2025, Reuters reported that the commander of Ukraine’s Unmanned Systems Forces warned that NATO armies were not ready for the scale and character of modern drone warfare. His warning was not simply about owning enough drones. It was about the way drones had overturned established doctrine, created a new cost-exchange problem, and forced rapid adaptation in electronic warfare, counter-drone defence, automated targeting and battlefield logistics.[4]
That matters for New Zealand because the point is not the size of Ukraine’s drone programme, which New Zealand cannot and need not copy. The point is the speed of adaptation. Drone warfare is not developing at the pace of traditional platform acquisition. It is developing at the pace of software, commercial manufacturing, field improvisation and battlefield feedback.
A Historical Parallel: The Ordnance Field Park
The New Zealand Divisional Ordnance Field Park of the Second World War provides a useful historical comparison. Formed in July 1941 after the lessons of Greece and Crete, the NZ OFP was a mobile mini ordnance depot supporting the 2nd New Zealand Division. It held spares for the Divisional Workshops and moved forward when workshop elements deployed to support brigades. Its stockholding included motor transport spares, weapon spares and signal stores, carried on vehicles and scaled to support a highly motorised division.[5]
The OFP was not a rear-area warehouse. It was a forward, mobile stockholding system designed to place repair parts and critical stores close enough to the point of need to sustain tempo. When the Division became more mechanised and incorporated an armoured brigade, the OFP reorganised to include separate infantry and armoured sections, later adding reserve vehicle and mobile advanced ordnance depot functions.[6]
The parallel is not exact. The OFP moved spares within a Second World War divisional system. It did not operate through contested, observed airspace under the kind of persistent surveillance now assumed for the future battlefield. Drone logistics inherits the OFP’s logic of forward, mobile stockholding, but it must solve for exposure in a way the OFP never had to.
That principle remains relevant. The OFP solved a problem created by mechanisation, how to keep a mobile force supplied with the spares and controlled stores it needed without waiting for the base depot. Drone logistics solves a related problem created by dispersion and battlefield transparency, how to move small, urgent and high-value items across the last tactical mile without exposing larger vehicles, drivers and replenishment points.
NZ Division OFP on the Move. Noel Kreegher Collection
In that sense, logistic drones are not a rejection of New Zealand Army logistics history. They are a modern expression of it.
Drones Are Not a Replacement for Trucks
The first point must be clear. Logistical drones will not replace trucks, containers, aircraft, ships, fuel tankers, forklifts, ammunition vehicles, recovery vehicles, or logistics specialists. Nor should they be presented as a miracle technology.
Their value lies elsewhere.
Drones offer a way to move small, urgent and high-value loads across the “last tactical mile”, the dangerous and inefficient gap between a combat service support node and the soldier, crew, section, troop or detachment that needs something now. A drone does not need to carry everything. It only needs to carry the thing that prevents the task from failing.
Logistic drones should not be seen as truck replacements. Their value lies in moving small, urgent and mission-critical loads across the final exposed gap.
That might be radio batteries, a replacement optic, a drone battery, a medical pack, blood products, morphine, water, rations, a weapon spare, a fuse, a small quantity of ammunition, a repair component, a cable, a cryptographic item or technical documentation.
Even here, the detail matters. Carrying medical items and ammunition as interchangeable small loads on the same platform class is not a purely logistical choice. Blood products and medical stores carried under recognised medical markings have a different legal status to ammunition. Any drone tasked across both roles will need clear rules on marking, tasking and interchangeability before it reaches the field.
Ukraine also shows that drone logistics is not theoretical. Sekirin notes that larger multirotor drones have been used to carry water, food and ammunition to encircled soldiers, while unmanned ground vehicles have been used to bring supplies forward, evacuate wounded, clear routes and reduce direct exposure of troops. These examples do not remove the need for conventional logistics, but they show how unmanned systems can fill dangerous gaps where trucks, soldiers or stretcher parties would otherwise be exposed.[7]
The scale of this shift should not be understated. General David Petraeus, drawing on repeated visits to Ukrainian units, has observed that armoured vehicles and infantry fighting vehicles are increasingly unable to survive if spotted by an observation drone, prompting some Ukrainian units to stop using human drivers on resupply routes altogether. Remotely driven vehicles instead carry ammunition, food, water and blood products forward and return with casualties.[8] This is not simply a refinement of last-mile delivery. It suggests that on the most exposed routes, the choice may shift from “driver plus drone support” to “no driver at all.”
In this sense, logistic drones are not bulk transport. They are precision distribution.
This has another historical echo. During the Second World War, New Zealand’s movement control system managed the complex movement of troops, stores and equipment by road, rail, sea and air. The 3rd Division’s Movement Control Unit in the Pacific handled 476 ships, averaging 20 vessels per week, with a staff that never exceeded 17 men. It operated in difficult conditions, often with limited port infrastructure, and adapted its methods to local circumstances.[9]
The modern equivalent is not simply moving more tonnage. It is using every available mode intelligently. Trucks, ships, aircraft, landing craft, forklifts, movement operators and drones all become part of a wider distribution network. The principle is not “drone instead of truck”. It is the right mode for the right load, at the right time, with the least exposure.
Logistic Drones as Multi-Role Systems
Logistic drones should not be thought of only as flying delivery vehicles. In many cases, the same platform that carries a small load can also provide information. A drone sent forward with batteries, medical stores or repair parts can confirm the condition of the route, identify damage to tracks or bridges, observe the proposed delivery point, check whether the receiving element has moved, and provide immediate feedback to the combat service support commander.
This gives logistic drones an ISTAR value. They can contribute to local intelligence, surveillance, target acquisition and reconnaissance by observing the ground over which replenishment must occur. Before a vehicle convoy moves, a drone could check a route. Before a replenishment point is opened, a drone could confirm whether the area is clear, concealed and usable. During replenishment, a drone could provide overwatch, detect movement, and warn of threats to the supported force or the logistic element.
Sekirin identifies four characteristics that make drones militarily disruptive: omnipresence, accurate direct fires, discardability and mobility. For logistics, the most important of these is not necessarily direct fire, but omnipresence and mobility. A logistic drone can move a small load, but it can also observe, confirm, warn and report. That means its value lies not only in what it carries, but in what it sees and how quickly it can be repositioned.[10]
This does not mean that every logistic drone should become a strike platform. The more useful model is a family of systems with common components, training, batteries, software and payload standards, but different payload options. Some drones would be optimised for carriage. Some would be optimised for surveillance. Some might carry electronic-warfare or communications relay payloads. A smaller number, under clear command authority, could be armed or fitted for suppressive fire against targets of opportunity that threaten a replenishment operation.
That distinction matters. A drone carrying blood products, medical stores or marked medical supplies raises different legal and ethical issues from a drone carrying ammunition or a weapon payload. Mixing those roles without clear rules would create confusion and risk. If the Army adopts multi-role logistic drones, it will need clear procedures for tasking, marking, payload changeover, authority to arm, control of fires, recovery of unused munitions and post-mission accountability.
For a Motorised Infantry Battalion Group, the most immediate value is probably not in turning supply drones into routine attack drones. It is in using them to support replenishment by seeing first, warning early and reducing exposure. A resupply task could therefore be supported by three drone functions: a reconnaissance drone to check the route and delivery point, a logistic drone to move the load, and, where the threat justifies it, an overwatch or armed drone controlled through normal command and fire-control arrangements.
The Australian-designed SYPAQ Corvo Precision Payload Delivery System provides a useful example of this logic. Developed as a low-cost fixed-wing payload-delivery system, the Corvo PPDS has been supplied to Ukraine and reportedly adapted for reconnaissance and attack roles as well as delivery. Its significance is not that New Zealand should simply buy the same system, but that the design of logistics drones should preserve modularity. Airframes, payload bays, mission software, batteries, training systems, and repair arrangements should enable controlled adaptation rather than lock a platform into a single, narrow role.[11]
A constructed SYPAQ Corvo PPDS drone, sitting atop a stack of flat-packed ones. SYPAQ
The broader lesson is that a drone designed only as a small flying box may quickly become obsolete. A drone family designed around carriage, observation, communications relay and controlled payload change may remain useful for longer.
This would fit the wider argument of this article. Drone logistics is not simply about moving small loads. It is about making sustainment less predictable, less exposed and better informed. A drone that delivers a battery is useful. A drone that delivers a battery and confirms the replenishment route is still usable is more useful. A drone system that can integrate carriage, reconnaissance, communications relay, and protective overwatch is even more useful, provided the roles are controlled rather than improvised.
Logistics in a Contested Drone Environment
Much is now said about operating in a contested environment, but the phrase needs to be understood in practical logistic terms. A contested environment is one in which friendly forces cannot assume that movement, communications, concealment, airspace, supply or evacuation will be uncontested. The enemy is not simply waiting to be engaged by combat troops. It is actively trying to find, disrupt and destroy the systems that allow those combat troops to keep fighting.
For logistics, this changes the problem. A replenishment point is no longer just a place where stores are issued. It is a potential target. A vehicle harbour is not just an administrative pause. It is a detectable pattern. A fuel point, ammunition transfer point, repair team, drone charging site, casualty collection point or field 3D-printing node may all become part of the enemy’s target list. The more predictable the logistic system becomes, the easier it is to find and attack.
Drones intensify this problem because both sides can use them. If friendly forces are sending drones forward to check routes, confirm delivery points, carry stores, and provide overwatch, the opposing force is likely to do the same. Enemy drones may be searching for logistic vehicles, identifying resupply nodes, tracking movement between hides and distribution points, locating command posts, observing unloading activity or waiting for troops to concentrate during replenishment. The danger is not only that a logistic drone may be shot down. The greater danger is that enemy drones may exploit the replenishment process itself to locate and attack the logistics system.
Sekirin describes this as the emergence of battlefield transparency, an operational condition in which movement near the front can be observed and countered. Although his analysis is drawn from Ukraine, the implication for logistics is clear. Supply points, repair nodes, ammunition transfer points, casualty collection points and drone launch sites are all exposed by the same transparency that allows friendly drones to find enemy targets. In that setting, concealment, dispersion and deception are no longer optional fieldcraft. They are logistic survival measures.[12]
The problem is already visible in Ukraine. Reuters has described drone-dominated areas of the front as a “kill zone”, with drones complicating movement, evacuation and routine battlefield activity.[13] Surveillance drones, bomber drones, kamikaze drones and drone-killing drones are all part of the same ecosystem. Both sides use them to find targets, disrupt movement and make routine activity dangerous. For logistics, that means the most dangerous moment may not be the fighting itself, but the pause when vehicles, stores and soldiers concentrate long enough to be seen.
This is why counter-drone protection cannot be treated as someone else’s problem. If logistics units are using drones to find routes and delivery points, enemy drones will look for the same patterns in reverse.
This makes counter-drone protection a logistic requirement. It cannot be treated only as an air defence or combat arms problem. Logistic units will need the ability to detect, avoid, deceive and, where authorised, defeat enemy drones. This may include camouflage, concealment, dispersion, movement discipline, electronic emission control, decoy positions, rapid unloading drills, hardened or concealed charging points, alternate replenishment sites, passive warning systems, electronic countermeasures and short-range physical protection.
Ukraine’s efforts against Shahed-type drones also show the cost-exchange problem. Reuters reported on Ukraine’s layered counter-Shahed effort, highlighting the growing importance of interceptor drones, electronic warfare, and lower-cost countermeasures, as using expensive missiles against cheap drones is economically unsustainable over time.[14] The tactical lesson is clear. Logistic units cannot rely only on high-end air defence. They need low-cost options for warning, concealment, deception, dispersion, and defeat built into their routine.
Physical hardening of routes is another low-cost measure now in routine use. Petraeus has described the main supply routes in Ukraine, which are covered with mesh netting along their entire length to stop drones from striking resupply vehicles, though footage has already shown drones penetrating gaps beneath the mesh.[15] The lesson for New Zealand is not that mesh tunnels are the answer, but that even improvised physical countermeasures are being defeated within months, reinforcing the assumption that any logistic counter-drone measure adopted now must be treated as temporary rather than final.
The old habit of building a replenishment point around convenience will not survive on a monitored battlefield. Logistic sites will need to be selected as tactical positions rather than administrative locations. They will need overhead concealment, covered approaches, rapid entry and exit routes, emission control, and protection against observation from above. Replenishment drills will need to be fast, rehearsed and dispersed, with vehicles and troops spending as little time as possible in one place.
This also affects the design of logistic drone operations. A drone launch site, recovery point or charging location must not become a fixed signature. Batteries, controllers, antennas, maintenance benches, spare parts, and additive manufacturing equipment all create detectable patterns. If these are concentrated in one obvious place, the drone system intended to reduce exposure may instead create a new target.
For the Motorised Infantry Battalion Group, the implication is clear. Drone logistics and counter-drone measures must be developed together. A battalion that can send a drone forward with medical stores but cannot detect an enemy drone observing its replenishment point has only solved half the problem. Likewise, a logistic element that can move stores by drone but cannot conceal, protect or rapidly displace its launch and recovery points may become more vulnerable, not less.
The answer is not to avoid drones. It is to integrate them properly into a contested logistic system. Friendly drones should help logistics see first, move smarter and reduce exposure. Counter-drone measures should help logistics survive when the enemy is trying to do the same. In the future battlefield, every logistics drone sortie should be planned with two questions in mind: what can we see, and what can the enemy see of us?
A Three-Tier Model for New Zealand
The New Zealand Army does not need to copy the drone logistics model of a much larger ally. It needs a small-army model suited to limited people, limited equipment, dispersed operations and an Indo-Pacific operating environment.
In outline, that model runs across three tiers. At the company and combat-team levels, small tactical drones would carry radio batteries, medical supplies, repair parts, documents, small rations, and lightweight ammunition, and would confirm local routes and delivery points. At the Motorised Infantry Battalion Group level, medium-lift drones would move ammunition boxes, larger medical loads, tools, replacement sights, and drone batteries, while also providing route reconnaissance, replenishment overwatch, and communications relay. At brigade or joint level, larger cargo drones and unmanned ground vehicles would move stores between dispersed logistic nodes, reinforce isolated detachments, support forward arming and refuelling, and provide emergency movement when roads are blocked, mined, flooded, observed or under fire.
None of this needs to be built alone. New Zealand’s coalition-dependent posture is exactly the setting in which interoperability multiplies a small army’s reach. Where Australian, United States, British, or Indo-Pacific partners already field logistics drone systems, New Zealand should first look to adopt or adapt those platforms, payload standards, and data links, rather than developing a bespoke architecture from scratch. A small army’s advantage lies in plugging into someone else’s scale, not in reinventing it.
This tiered approach would enable drone logistics to support both warfighting and population-support missions. In the Indo-Pacific, the same systems could assist after cyclones, earthquakes, floods, or volcanic activity, particularly where roads, bridges, wharves, or landing sites are damaged. For New Zealand, this dual-use value matters.
An Indo-Pacific Intra-Theatre Layer
The three-tier model should not exclude larger fixed-wing logistics drones. For New Zealand, the Indo-Pacific operating environment makes them a serious consideration. Many likely tasks will occur across wide maritime distances, dispersed islands, limited ports, short or damaged airstrips, and communities isolated by cyclones, flooding, earthquakes or volcanic activity. In those conditions, a fixed-wing logistic drone may provide a useful bridge between strategic lift and local tactical distribution.
The same geographic logic appears in U.S. Army thinking on Indo-Pacific sustainment. The region’s distances, limited infrastructure, reliance on maritime access and exposure to anti-access/area denial systems mean that ports, airfields and supply depots can no longer be treated as secure or guaranteed. In such an environment, unmanned aerial and ground systems, supported by AI-enabled route planning and predictive logistics, become part of a wider answer to distance, disruption and denied access.[16]
Its value would not lie in replacing C-130s, NH90s, ships, landing craft, or truck movements. It would be in filling the gap between them. A larger fixed-wing drone could move urgent, lightweight, high-value stores between islands, from a main support base to a forward relief point, or from ship to shore, where landing sites are constrained. Loads such as medical stores, radio batteries, water testing kits, satellite communications equipment, repair parts, blood products, mapping equipment or small command-and-control stores are exactly the type of items where speed and reach may matter more than weight.
For that reason, New Zealand should consider a fourth layer in the longer-term model: an intra-theatre fixed-wing logistics drone capability held at joint or operational level. This would sit above the Motorised Infantry Battalion Group model, but should be considered early so that payload standards, charging or fuel arrangements, data links, airspace control, maintenance and interoperability are not designed only around short-range tactical drones.
Tier
Echelon
Platform type
Example loads/roles
1
Company/combat team
Small tactical drones
Radio batteries, medical items, repair parts, documents, small rations, lightweight ammunition, local route checks and delivery-point confirmation
2
Motorised Infantry Battalion Group
Medium-lift drones
Ammunition boxes, larger medical loads, tools, replacement sights, drone batteries, ration modules, route reconnaissance, replenishment overwatch and communications relay
3
Brigade/joint
Larger cargo drones and unmanned ground vehicles
Movement between dispersed logistic nodes, reinforcement of isolated detachments, forward arming and refuelling support, emergency movement when roads are blocked, mined, flooded, observed or under fire
4
Joint/operational intra-theatre
Larger fixed-wing logistics drones
Inter-island movement of urgent medical stores, communications equipment, repair parts, water purification items, batteries, lightweight relief stores and wide-area route or landing-site reconnaissance
This does not change the starting point. The immediate trial should still focus on tier-one and tier-two systems capable of supporting the Motorised Infantry Battalion Group. However, the Indo-Pacific layer should shape the architecture from the beginning. If New Zealand starts with only short-range tactical drones in mind, it may later discover that its payload standards, batteries, data links, training systems and maintenance arrangements do not scale to the very environment in which New Zealand is most likely to operate.
Classes of Supply and the Distribution Network
Coalition logistics doctrine gives this model a sharper edge. The Australian Army’s Land Warfare Doctrine 4-0, Logistics, built on the NATO framework familiar to New Zealand logisticians, divides supply into ten classes, from subsistence through to ammunition, medical stores, repair parts and disaster-relief materiel.[17] That framework is a useful test of where drones add real value and where they do not.
Class
Description
Drone suitability
Comment
I
Subsistence, rations, water and welfare items
Good, limited
Useful for urgent top-ups to isolated posts, but not a substitute for bulk feeding
II
General stores, clothing, individual equipment, tools and maps
Good
Light items can be moved easily, although priority may be lower
III
Fuel and lubricants
Poor
Weight, volume and fire risk make this primarily a truck, tanker or pipeline task
IV
Construction and fortification materials
Poor
Usually too bulky or heavy, except for small tools or fixings
V
Ammunition and explosive ordnance
Good, controlled
Suitable for small urgent natures, not bulk ammunition resupply
VI
Personal demand items
Good, low priority
Light and low risk, but usually less urgent than medical, repair or ammunition loads
VII
Major end items, vehicles, weapons and major equipment
Not suitable
Beyond drone payload limits
VIII
Medical and dental stores
Strong
Often light, urgent and operationally critical
IX
Repair parts
Strong
Well suited to small, forecast-difficult, mission-critical items
X
Non-military programme materiel, including humanitarian and disaster relief stores
Good, selective
Useful in Indo-Pacific relief tasks where access is constrained
The pattern is clear. Drones earn their place where the load is light, time-critical and difficult to forecast. They have little to offer for loads that are heavy, bulky, or hazardous. That is not a weakness in the concept. It is the division of labour the model assumes: trucks and ships carry the mass, drones carry the urgent exception that would otherwise stop the mission.
Doctrine also describes the distribution network as a system of nodes and links, using both automatic “push” replenishment and demand-driven “pull” replenishment. Traditional delivery methods include direct delivery, unit collection, distribution or exchange points, and dumping. Drone delivery is best understood as an additional direct-delivery option layered onto that network. For predictable bulk flows, drones add little. For demand-driven requests for medical stores, repair parts or critical small stores, they may close the gap between the node and the soldier without committing a vehicle or establishing another exposed distribution point.
Aligning Drone Logistics with Doctrine
The case for drone logistics should not rest on novelty. It should be tested against the doctrinal architecture that already governs logistics, including the support dimensions, the functions of combat service support, the types of support, and the enduring principles of logistics.
Doctrine separates logistics into two dimensions. Capability support manages equipment and systems across their life cycle, including acquisition, in-service management, sustainment and disposal. Operations support, delivered as combat service support, provides the tailored resources a force requires to achieve a mission.[18]
Logistic drones sit across both dimensions. In operations, they are combat service support assets that move stores to soldiers. Before operations, they are capability systems that require proper acquisition, training, maintenance, configuration control, cyber protection, spares and disposal plans. A drone fleet that fails in capability support will eventually fail in operations support.
Within the functions of combat service support, drones do not contribute equally. Their strongest relevance is to supply support, maintenance support and health support. They can distribute selected classes of supplies, move urgent repair parts, and deliver time-sensitive medical supplies. They contribute to transport and movement as one mode among many, but they do not replace movement control. Their contribution to personnel services is limited, perhaps small urgent documents or low-volume welfare items. Their contribution to engineer sustainability is also limited, with drones able to move small tools or survey items but not bulk construction materials.
This unevenness is useful. It checks enthusiasm. Drone logistics is not a universal solution. It is a specific tool for supply, maintenance and health support at the tactical edge.
The three-tier model also maps onto doctrinal types of support. Company-level drones resemble integral support, held and operated within the sub-unit. Battalion-group drones provide close support, linking companies to the battalion’s combat service support system. Brigade or joint-level drones provide general support across a wider force. The proposed Indo-Pacific intra-theatre layer sits above this tactical model and belongs more naturally at joint or operational level. It would support movement between islands, bases, ships and forward relief points rather than provide immediate company-level resupply.
Drone logistics should also be judged against the enduring principles of logistics: responsiveness, simplicity, economy, flexibility, balance, foresight, sustainability, survivability and integration.[19]
Drones can improve responsiveness by closing the last tactical mile faster than a scheduled vehicle run. They support economy when they avoid committing a vehicle and crew to a very small load. They improve flexibility when a tiered model allows company, battalion and brigade options. They can improve survivability by reducing exposure of drivers and vehicles on dangerous routes.
But each advantage has a tension. A poorly standardised fleet adds complexity rather than simplicity. Battery, spares and training overheads may erode economy. Over-investment in drones at the expense of trucks and drivers would break balance. A drone charging site becomes a new target set. Integration with RNZALR structures, airspace control, allied data links, and maintenance systems must be deliberately designed.
Read this way, drone logistics is not a departure from established logistic principles. It is a test of whether those principles can be applied to a new technology before the battlefield forces the issue.
Risks and Limits
The risks are real, and they deserve more than a token mention.
Drones can be jammed, hacked, intercepted, shot down, misrouted or grounded by weather. They may expose friendly locations through electronic signatures or predictable flight paths. Payloads are limited. Batteries create their own resupply burden. Maintenance, software updates, cyber protection and operator training all require discipline.
Airspace control is not a footnote. Logistic drones will need to be deconflicted with artillery, aviation, allied forces and, in Indo-Pacific contingencies, civil air traffic. That is an institutional problem as much as a technical one, and it needs to be solved before fleets grow, not after.
Multi-role systems also create command and legal complexity. A drone used for logistics, ISTAR, and strike cannot be treated as a simple store-delivery platform. The Army would need clear rules for payload configuration, authority to arm, control of fires, medical marking, target confirmation, airspace coordination and accountability after the mission. Without those controls, the flexibility of a multi-role drone could become a source of confusion rather than advantage.
Sekirin’s analysis also reinforces the need to develop drone and counter-drone systems together. He argues that UAS and counter-UAS activity must be coordinated so that friendly drones are not jammed or shot down by friendly systems, and that enemy drones are consistently detected and defeated. For logistics, that means counter-drone measures cannot be excluded from the sustainment plan. They must be integrated into replenishment points, repair nodes, drone launch sites, charging areas and movement routes from the beginning.[20]
The contested drone environment also means that logistic units must be given active counter-drone responsibilities. It will not be enough to rely on higher-level air defence or assume that combat units will always provide protection. Replenishment points, repair nodes, casualty collection points, drone launch sites and charging areas will all need organic or closely integrated counter-drone measures. These do not need to begin as complex systems. They may start with detection, warning, concealment, decoys, drills, emission control and simple defeat options. But they must be built into logistic structures from the start, because the enemy’s drones will be hunting the same logistic patterns that friendly drones are trying to exploit.
The Indo-Pacific layer adds further risks. Long-distance fixed-wing drones require navigation resilience, weather tolerance, recovery options, airspace permissions, communications coverage, maintenance depth and reliable launch and recovery procedures. These are not simple tactical systems. They would require joint-level oversight, but the need to solve those problems is precisely why they should be considered early.
But these are not arguments against drone logistics. They are arguments for starting early, deliberately and with realistic expectations of what the first systems will and will not do.
Scaling the Capability
History warns that equipment alone is not capability. Major-General Mackesy’s 1939 report made this point before the language of modern Integrated Logistics Support existed. He was not simply asking whether New Zealand had enough weapons. He was asking whether equipment, ammunition, people, storage, workshops, transport, training and mobilisation arrangements could function as a wartime system.[21]
The same test should be applied to drones.
A drone without trained operators, maintainers, batteries, charging systems, spares, airspace procedures, payload packaging, electronic protection, safety rules and logistic doctrine is not a capability. It is an item on charge.
To avoid this, drone logistics must be scaled properly. The Army should define standard drone loads, standard packaging, standard carriage methods and standard replenishment tasks.
Load type
Possible contents
Platoon emergency resupply
Batteries, water, medical stores and ammunition
Casualty support
Dressings, analgesia, blood products and evacuation aids
Ammunition support
Fuzes, tools, packaging material, labels and inspection equipment
Maintenance support
Belts, filters, cables, optics, lubricants and small assemblies
Signals support
Batteries, antennas, handsets, cables and replacement components
Disaster-relief support
Water purification items, medical stores, communications equipment and lightweight relief supplies
Indo-Pacific intra-theatre support
Medical stores, satellite communications equipment, water testing kits, mapping equipment, repair parts, batteries and small command-and-control stores
This would move drone logistics from novelty to system. It would allow the Army to plan, train, account for, package, prioritise and replenish using drones as part of the sustainment architecture.
Dispersed Logistics for a Transparent Battlefield
A motorised infantry force will require fuel, ammunition, spares, water and maintenance. These are heavy, visible and predictable demands. On a monitored battlefield, predictability is dangerous.
The answer is not to abandon conventional replenishment, but to reduce concentration and increase options. Stores should be held in smaller, dispersed nodes. Replenishment should be more frequent, more varied and less predictable. Some movement should still be by truck, some by protected vehicle, some by foot, some by air, some by water and some by drone.
Drone logistics supports this by enabling smaller quantities to be moved as needed without committing a vehicle column to every task. It can reduce the number of soldiers exposed on routine but dangerous runs. It can support units operating away from main routes. It can help sustain dispersed observation posts, sensor teams, anti-armour teams, engineers, medical teams, communications detachments and dismounted infantry.
It also supports the logic of a motorised infantry battalion. The battalion’s combat power will depend on the ability to shift between mounted and dismounted activity. Its logistics must be able to do the same. Trucks and protected mobility vehicles can move bulk forward. Drones can then move selected stores across the final exposed gap.
In the Indo-Pacific, the same logic applies across distance rather than across the battlefield. A community cut off by a cyclone, an airstrip damaged by flooding or a small island with limited landing options presents the same basic logistic problem: a gap between where stores are held and where they are urgently needed. Fixed-wing logistics drones may help close that gap for selected loads, while ships, aircraft and landing craft continue to move the mass.
Reverse Logistics and the Return Journey
Drone logistics should not be thought of only as forward delivery. It also has a reverse logistics role.
The withdrawal of the 3rd New Zealand Division from the Pacific between 1944 and 1945 showed the scale and complexity of bringing equipment, stores and vehicles home. More than 50,000 ordnance items, 3,274 vehicles, 25 tanks, tonnes of ammunition and large quantities of NZASC supplies had to be recovered, inspected, sorted, repaired, redistributed or disposed of. This was achieved without modern material-handling equipment or information technology, relying instead on infrastructure, discipline, labour, and determined logistical control.[22]
Modern forces must still recover, inspect and redistribute equipment. In a future conflict, drones could assist with the small but urgent reverse movement of repairable components, classified stores, medical samples, damaged optics, electronic modules, batteries, intelligence items and technical evidence. They could also assist ammunition technical staff by moving small components, samples or documentation from forward locations to specialist support nodes.
This reverse flow matters. A distribution system that only pushes stores forward, but cannot recover repairable or accountable items, soon becomes wasteful and blind.
Procurement, Experimentation and Environmental Fit
The Army should not wait for a perfect drone logistics programme.
The history of New Zealand military logistics shows that wartime adaptation often compressed years of development into months. During the Second World War, New Zealand absorbed new vehicles, created workshop systems, expanded ammunition infrastructure, built depots, trained tradesmen, introduced ration systems and deployed new support organisations at a pace that would challenge modern peacetime procurement processes.
Nor was interwar New Zealand simply asleep before 1939. The Army had been updating doctrine, conducting training exercises, experimenting with motor vehicles and artillery modifications, ordering modern equipment and developing mobilisation scales. Its problem was not total ignorance, but the limits imposed by money, personnel and time.[23]
There is another lesson from New Zealand’s post-war history of clothing and equipment. The Army did not always get new equipment right the first time. Combat clothing, tropical uniforms and camouflage shelters were repeatedly trialled, modified, accepted, rejected or left to waste out as experience showed whether they suited New Zealand, Southeast Asia or operational conditions. The development of Drill Green uniforms, tropical combat clothing, DPM, and camouflaged lightweight shelters demonstrates that equipment had to be tested for climate, terrain, user acceptance, durability, camouflage value, local manufacture, and sustainment cost.[24]
That same principle applies to drones. A logistic drone that performs well on a manufacturer’s demonstration field may fail in the wind, rain, bush, dust, humidity, salt air, electromagnetic clutter or austere conditions in which New Zealand forces may operate. Payload claims may not survive rough handling. Battery endurance may collapse in cold weather. Noise and visual signature may expose supported units. A system that appears efficient in a trial may prove difficult to repair, recharge, transport, account for or integrate with existing logistic procedures.
The camouflage shelter trials of the 1960s offer a useful model. The Army did not simply select a pattern from a catalogue. Samples were tested in New Zealand and then by 1 RNZIR and 161 Battery in Southeast Asia under varying terrain, light and climate conditions. User feedback shaped the final direction of the project.[25]
The same method should be used for drone logistics. Soldiers and logisticians should test systems in the field, report what works, identify what fails and force the support system to adapt before procurement locks the Army into the wrong answer.
A better approach would be controlled risk. The Army should buy small numbers of different systems, test them hard, break them, discard weak options, adapt useful ones and scale what works. Trials should not be confined to demonstrations. They should be embedded in field exercises, live firing, logistic rehearsals, disaster relief training and Motorised Infantry Battalion Group development.
Ukraine’s procurement experience reinforces this point. In March 2025, Reuters reported that Ukraine planned to sharply increase purchases of domestically produced FPV drones in 2025, after purchasing more than 1.5 million the previous year. The important lesson for New Zealand is not mass for its own sake. It is the procurement rhythm: domestic adaptation, rapid production, battlefield feedback and the willingness to modify quickly when the enemy adapts.[26]
That procurement rhythm is now visible in Ukraine’s daily logistics and in its factories. Petraeus has described a Ministry of Defence–linked ordering platform, built with limited nonprofit funding rather than a major defence contract, through which units can order drones, components and optics from several hundred pages of listings and receive delivery within days.[27] Whatever New Zealand builds does not need to match this scale, but the underlying model, a fast, unit-facing ordering system tied directly to field feedback, is closer to the procurement rhythm this article is arguing for than a traditional annual bulk-buy cycle.
European militaries are drawing similar conclusions. Reuters reported in June 2026 that European defence leaders were calling for a shift toward mass-produced, lower-cost systems such as drones and interceptors, alongside electromagnetic warfare, air defence and faster procurement.[28] For a small army, that reinforces the need to buy small numbers early, test hard, avoid bespoke over-complexity and keep the learning cycle short.
Most importantly, logisticians and technical trades must be central to the process. New Zealand’s armourers evolved from civilian gunsmiths and part-time artificers into disciplined technical specialists because changing weapons technology demanded inspection, repair, maintenance and local expertise.[29] Drone logistics will require the same kind of technical foundation. Operators, maintainers, battery managers, electronic technicians, payload packers, software support personnel, ammunition specialists, movements staff and supply personnel must all be involved from the beginning.
Whether this becomes a distinct trade, an added skill set within the RNZALR, or a task shared across existing corps is a structural choice the Army will need to make early, before procurement, not after it. That choice will determine who trains whom, which units own the capability, and what current roles absorb the extra load.
Drone logistics is not just an aviation issue. It is a sustainment issue.
Maintenance, Additive Manufacturing and Repair Thresholds
Maintenance support must be integrated into RNZALR and unit support processes, including additive manufacturing where it is safe, economical, and tactically useful.
Drone fleets consume propellers, motors, bearings, arms, connectors, antennas, batteries, housings, landing skids, payload brackets and software updates at a tempo very different from traditional vehicle maintenance. Many of these items are light, fragile, frequently damaged and difficult to forecast accurately. A small stock of controlled spares will still be essential, but 3D printing could reduce downtime by allowing units to produce selected non-critical parts, such as protective housings, battery trays, cable clips, antenna mounts, payload adaptors, guards, brackets, training aids and repair jigs, without waiting for the normal supply chain.
This is not speculative. The United States Army has introduced drone training that includes 3D printing, printer maintenance, CAD and STL file handling, and building and repairing drones using printed components.[30] The United States Marine Corps has also demonstrated the potential of in-house drone production through its HANX project, a modular 3D-printed drone developed by 2nd Maintenance Battalion. Reporting on the project also notes that specialist infrastructure, assembly skills and calibration remain limiting factors.[31] More broadly, additive manufacturing is increasingly being treated as a way to shorten lead times, reduce dependence on long supply chains, and improve the availability of spare parts, particularly where the right digital files, materials, and quality controls are in place.[32]
For the New Zealand Army, the practical model should be controlled and tiered. At operator level, small systems should be maintained by trained users with controlled spares packs and simple replacement thresholds. At the battalion or brigade level, RNZALR-supported drone maintenance cells should carry field printers, approved print files, materials, inspection tools, and standard repair procedures. More complex parts, structural components, and any safety-critical items should remain under technical control, whether produced by an approved workshop, purchased through the supply system, or replaced as an assembly.
New Zealand should not attempt to maintain every cheap drone like a major fleet asset. Many smaller drones should be treated as semi-expendable, with rapid repair or replacement taking priority over prolonged workshop recovery.
Additive manufacturing also introduces risks that must be managed. A printed part is only as good as its material, file, printer settings, operator skill and inspection process. Research into additive manufacturing cyber risk has shown that compromised print files or printer firmware can weaken parts without obvious visual signs, including drone components.[33] For that reason, the Army would need an approved digital parts library, controlled printer settings, material traceability, basic inspection standards and clear rules on what may, and may not, be printed in the field.
Used properly, 3D printing would not be a shortcut around engineering discipline. It would be a way of pushing limited, controlled manufacturing closer to the tactical edge.
What This Would Take
None of this needs to wait for a perfect programme, but it does need a practical starting point.
A realistic first step would be a battalion-level trial of tier-one and tier-two systems within the next one to two years, run alongside Motorised Infantry Battalion Group training and Indo-Pacific disaster-relief exercises rather than as a standalone activity. It would need a small standing cell, likely single figures of trained operators and maintainers per battalion group initially, drawn from existing RNZALR and combat trades rather than a large new establishment. Numbers should be scaled only as trial results justify them.
It would also need a procurement approach that buys several competing systems in small numbers, rather than a single system in bulk, so the Army learns what breaks down before it commits to a fleet.
Australian experience is also relevant. The ADF’s recent investment in small uncrewed aerial systems indicates that regional partners are already moving toward broader adoption of tactical drones.[34] Australia is also investing in counter-drone systems, including low-cost interceptor drones and directed-energy options, in response to lessons from Ukraine and the Middle East.[35] New Zealand should use that momentum. The aim should be interoperability where possible, shared payload standards where practical, and sustainment arrangements that do not isolate New Zealand from the systems its closest partners are already adopting.
At the same time, the joint force should begin a parallel concept trial for larger fixed-wing logistics drones in Indo-Pacific-style scenarios. This does not need to be a major acquisition. It could begin as a proof-of-concept activity using a small number of systems to test inter-island payload movement, ship-to-shore delivery, airspace coordination, communication range, weather tolerance, and recovery procedures. The purpose would be to understand whether such systems can fill a genuine gap between strategic lift and local distribution, not to create another fleet before the requirement is proven.
Multi-role employment should also be included in the trial design. A replenishment serial should not only ask whether a drone can carry the load. It should ask whether the drone system can locate the delivery point, confirm the route, provide overwatch, relay communications, and, under controlled conditions, support the protection of the replenishment activity. The purpose would be to develop procedures before the pressure of operations forces improvisation.
Trial activity should also include enemy drone play. The trial should also include AI-enabled sustainment planning. The U.S. Army article notes that AI can assist logisticians by forecasting demand for fuel, ammunition, medical supplies and spare parts, integrating threat intelligence, terrain and weather data, optimising delivery routes, and helping planners model sustainment under contested conditions.[36]
This direction of travel matters specifically for logistics. Petraeus has argued that unmanned systems in Ukraine are moving from being remotely piloted to being algorithmically piloted, with the operator shifting from controlling each action to approving actions an AI system proposes under a given set of conditions.[37] For sustainment, that trajectory points toward logistics drones that increasingly plan their own routing and flag risks without a human directing every movement, which is a further reason for New Zealand to build its data links, payload standards, and command arrangements to accommodate more autonomy than today’s tactical drones require.
For New Zealand, the practical starting point need not be a large AI programme. It could begin with simple decision-support tools that help a battalion group compare replenishment routes, predict consumption, identify exposed nodes and test whether drone delivery, vehicle movement or pre-positioning is the better option.
Every replenishment serial should assume that opposing forces are using drones to locate, track and target the logistic system. This would force the trial to test concealment, dispersion, counter-drone warning, launch-site protection, rapid displacement and the discipline of operating without creating obvious patterns.
This is a modest first commitment, not a re-equipment programme. Its purpose is to generate the field evidence, on payload, endurance, maintainability, integration, trust, command arrangements, role separation and survivability in a contested drone environment, that the Army cannot get from a concept document alone.
Conclusion
There is a deeper continuity here. Colonial armourers, Defence Stores clerks, wartime ordnance parks, movement control teams and reverse logistics units all did more with less by adapting before failure became visible. Drone logistics is the next step in that same habit, not a break from it.
The creation of the Motorised Infantry Battalion at Linton gives the New Zealand Army an opportunity to rethink both sustainment and combat organisation.
If 1 RNZIR is to be more agile, adaptable, lethal and survivable, then its logistics must be more agile, adaptable, distributed and survivable as well. A motorised infantry force sustained only by predictable vehicle movement, centralised stockholding and traditional replenishment habits risks being organised for yesterday’s battlefield.
Drones will not solve every logistic problem. They will not replace the logistician, the combat driver, the storeman, the ammunition technician, the maintainer, the medic or the movement operator. But they can extend their reach. They can reduce exposure. They can increase responsiveness. They can help a small army make limited resources go further.
They can also make logistics better informed. A drone that delivers stores may also confirm the route, observe the delivery point, warn of threats and support the protection of the replenishment task. Under strict control, selected systems may also provide suppressive or defensive effect against threats of opportunity. That potential should be explored, but not confused with routine carriage. A medical drone, a supply drone and an armed overwatch drone are not the same thing simply because they may share airframes, batteries or software.
In the Indo-Pacific, larger fixed-wing logistics drones may also help close the gap between strategic lift and the final point of need. They should not distract from the immediate tactical requirement, but they should be considered early, as New Zealand’s most likely operating environment is maritime, dispersed, and infrastructure-limited.
But the most important point is that drones are not only a friendly advantage. If New Zealand can use drones to find routes, confirm delivery points and support replenishment, so can an adversary. Future logistic structures must therefore include counter-drone measures as part of their own survival. The logistician of the future will not only move stores. They will have to protect the movement, conceal the node, manage signatures, and understand what the enemy can see from above.
Sekirin’s argument that the drone is the new tank is a useful warning, but the New Zealand lesson is slightly different. The issue is not whether drones alone will decide wars. It is whether the Army can reorganise enough of its sustainment system to exploit them before an adversary exploits them against us. In that sense, the logistic drone is not merely a new delivery method. It is a test of whether a small army can adapt its doctrine, structures, trades, procurement and training quickly enough for the next battlefield.
The next adaptation should also be digital. Drones, counter-drone measures and AI-enabled sustainment should not be treated as separate projects. In a contested Pacific environment, they are connected parts of the same problem: how to move, protect, predict and prioritise sustainment when ports, airfields, roads, communications and supply chains are under pressure.
New Zealand’s logistic advantage has never been mass. It has been adaptation.
[15] David Petraeus, “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025).”
[20] Sekirin and Simms, Rise of the Machines: Drone Warfare in the Russia-Ukraine War – Tactics, Operations, Strategy.
[21] “Mackesy’s Warning: Modernisation, Mobilisation, and Early Integrated Logistics Thinking in the New Zealand Army,” “To the Warrior his Arms” History of the Royal New Zealand Army Ordnance Corps and its predecessors, 2026, accessed 1 July, 2026, https://rnzaoc.com/2026/05/10/mackesys-warning/.
[27] David Petraeus, “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025).”
[32] F. Marinho de Brito et al., “Design Approach for Additive Manufacturing in Spare Part Supply Chains,” IEEE Transactions on Industrial Informatics 17, no. 2 (2021),https://doi.org/10.1109/TII.2020.3029541.
[33] Hammond Pearce et al., “Flaw3d: A trojan-based cyber attack on the physical outcomes of additive manufacturing,” IEEE/ASME Transactions on Mechatronics 27, no. 6 (2022); Sofia Belikovetsky et al., “dr0wned–{Cyber-Physical} attack with additive manufacturing” (paper presented at the 11th USENIX workshop on offensive technologies (WOOT 17), 2017).
[36] Lydia Aguirre, “AI-Driven Sustainment in Contested Logistics — Preparing for LSCO in the Indo-Pacific.”
[37] David Petraeus, “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025).”
Australia’s Century-Long Tradition of Improving Things That Didn’t Need Improving
It is a truth universally acknowledged that Australia’s defence procurement philosophy can be summarised in six words: “Yes, but have you considered modifications?”
This proud tradition, it turns out, did not begin with the $1 billion Seasprite helicopter that couldn’t fly in bad weather, or the MRH-90 Taipan that was retired early and partially buried in the desert, or the M113 armoured personnel carrier that was upgraded so thoroughly it ended up unfit for combat. No, it stretches back at least to February 1915, when a New Zealand inventor named Captain J.F. Roberts demonstrated his travelling field kitchen at Broadmeadows Camp near Melbourne.
The Roberts cooker was a masterpiece of practical engineering. It had been exhaustively trialled in New Zealand, adopted as the sole field kitchen by the New Zealand Defence Department, and could feed 600 men from a unit designed for 250. Officers at Broadmeadows were full of praise. Captain Roberts was understandably pleased.
Then the Australian Defence Department got their hands on it.
Rather than use the proven two-vehicle limber-and-cooker arrangement, they mounted everything on a single lorry — facing the wrong way round, with the furnace doors at the front instead of the back, the oven doors blocked by the brake mechanism, the springs removed, the cook’s workspace reduced, and the elegant one-man turning system eliminated. Captain Roberts, with the restrained diplomacy of a man watching his life’s work being reassembled by a committee, observed politely that the Department had “not given his cooker a fair chance.”
Before our Australian neighbours bear the full weight of this gentle mockery, however, honesty compels several admissions.
To be fair, and fairness demands we acknowledge this, Australia has an enormous and capable military, and plenty of procurement decisions have worked out perfectly well. The F/A-18 Hornet and Super Hornet purchases were sound and delivered on time. The C-17 Globemaster heavy airlift fleet was delivered on schedule and within budget — a fact so remarkable it was specifically noted in defence reviews as an exception worth celebrating. The MH-60R Seahawk, acquired off-the-shelf from the United States, has been a straightforward success with the Royal Australian Navy. The M1A1 Abrams purchase gave the Australian Army a world-class main battle tank with minimal fuss. The P-8A Poseidon maritime patrol aircraft has been broadly regarded as a capable and appropriate choice. When Australia buys things sensibly and resists the urge to improve them into dysfunction, it does so very well indeed.
The failures, however, share a depressingly consistent profile. The Seasprite was a sound helicopter, but the decision to add an entirely new, untested, and uniquely Australian avionics suite was a mistake. New Zealand bought essentially the same aircraft without the bespoke modifications, and it worked fine, to the point where New Zealand later bought the helicopters Australia had abandoned and operated them successfully. The Collins-class submarine took a capable Swedish design, substantially enlarged it, mandated local construction through a newly created industry with no submarine-building experience, and integrated an American combat system never previously used in a submarine, producing boats that were, for years, described as “noisy as a rock concert” and that sometimes had five out of six vessels simultaneously out of service. The MRH-90 Taipan added local construction requirements and Australian-specific modifications to a European helicopter that was already challenging to support, ultimately producing a fleet so expensive to maintain and so unreliable in service that it was retired early and replaced by a modern version of the very Black Hawk it had been bought to supersede.
The pattern is not that Australia can’t buy equipment. It’s that Australia can’t resist improving equipment that already works — adding bespoke avionics, local-industry content requirements, novel combat systems, unique carriage arrangements, and Australian-specific modifications until the thing costs twice as much, arrives a decade late, and occasionally can’t open its oven doors while moving.
The impulse to tinker is not, however, uniquely Australian. It is arguably a standard feature of any peacetime military, where budgets exist, time is available, and there is no urgent operational reality to impose discipline on the requirements process. When armies are not actively fighting, the temptation to refine, improve, and customise is almost irresistible, and the consequences of over-engineering remain comfortably theoretical rather than immediately fatal.
Closer to home, New Zealand is not immune to the siren call of “Yes, but have you considered modifications?” We have had our own moments of requirements-creep, our own projects that drifted from elegant simplicity toward expensive complexity, and our own defence procurement decisions that looked better on paper than in practice. Those who live in glass houses, and so forth.
Which brings us back to Captain Roberts and why his story is something more than an amusing footnote. In February 1915, the modification of his field kitchen was an inconvenience. A well-designed piece of equipment was made awkward and less effective, but meals were still cooked, and soldiers were still fed. The cost of the institutional habit of improvement for its own sake was modest.
In an era of sharply rising strategic uncertainty, where the comfortable assumption that procurement timelines can stretch across decades is being stripped away with some speed, the Roberts cooker story carries a more pointed message. Programmes that might once have been refined over ten years of peacetime tinkering may now need to deliver capability in three or four years. Equipment that works adequately off the shelf may be considerably more valuable than equipment that works brilliantly in theory but spends years being modified to meet requirements that keep changing.
The lesson Captain Roberts could not quite bring himself to state directly in front of the assembled officers at Broadmeadows in 1915, that a good thing rendered complicated by committee is no longer a good thing, may be among the more important pieces of advice available to defence procurement officials in Wellington, Canberra, and well beyond, right now.
Some lessons from 1915 are worth taking seriously today. This might be one of them.
On 4 December each year, soldiers, gunners, and explosive specialists around the world pause to mark Saint Barbara’s Day. For New Zealand’s military ammunition community, the day has a special resonance. Saint Barbara was the patron saint of the Royal New Zealand Army Ordnance Corps (RNZAOC). Although the Corps was disestablished in 1996, she remains the spiritual patron of those whose work brings them closest to explosive risk, especially the current generation of Royal New Zealand Army Logistic Regiment (RNZALR) Ammunition Technicians.
This commemoration is not about imposing religious belief or expecting devotion in a modern, pluralist Army. Instead, it is about recognising shared values. Saint Barbara’s story, whether read as faith, legend, or metaphor, offers a powerful way of talking about courage, duty of care, and professionalism in dangerous work.
From Heliopolis to the Ordnance Corps
According to tradition, Barbara lived in the late Roman Empire at Heliopolis in Phoenicia, now associated with Baalbek in modern Lebanon. Born into a wealthy pagan household, she questioned the gods she had been taught to worship when she looked out from the tower in which her father kept her secluded and reflected on the ordered beauty of the world around her. In time, she converted to Christianity in secret. When her father discovered this, he handed her over to the authorities and ultimately carried out her execution himself.
Her refusal to renounce her convictions, even under torture, and the lightning that, according to legend, later killed her father and the official who condemned her, led to Barbara being associated with sudden death, lightning, and fire. As warfare evolved and gunpowder weapons became central to battle, she was adopted as patroness of artillerymen, armourers, military engineers, miners, tunnellers, and anyone whose livelihood involved explosives and the possibility of instant, catastrophic harm. The Legend of Saint Barbara
When the Royal Army Ordnance Corps (RAOC) adopted Saint Barbara as its patron, that tradition passed into the wider family of Commonwealth ordnance corps. The RNZAOC, with its own responsibility for ammunition supply, storage, and maintenance in New Zealand, in turn adopted her as patron saint.
Beyond 1996: Saint Barbara and the RNZALR
The disestablishment of the RNZAOC in 1996 and the formation of the RNZALR did not diminish Saint Barbara’s relevance to New Zealand soldiers. The work did not change; only the cap badge did. Ammunition Technicians, in particular, continue to live daily with the realities that made Barbara a symbolic figure in the first place: sudden danger, technical complexity, and the need for calm, disciplined action when things go wrong.
On paper, Saint Barbara is a figure from late antiquity. In practice, her patronage captures something very contemporary about the RNZALR Ammunition Technician trade:
Technical mastery under pressure – handling, inspecting, and disposing of explosive ordnance where a single lapse can have irreversible consequences.
Quiet, unshowy bravery – the kind that rarely makes headlines but underpins every live-fire activity, every range practice, and every deployment where ammunition is moved, stored, or rendered safe.
Duty of care to others – ensuring that everyone else can train and fight in relative safety because someone has accepted responsibility for the dangerous end of the supply chain.
In that sense, Saint Barbara’s Day is as much about the living as it is about any distant martyr. It is an opportunity for the wider Army to pause and acknowledge that the safe availability of ammunition, which is often taken for granted, depends on a small community of specialists and their support teams.
A Day Of Tradition, Not Testimony
In a modern New Zealand Army, not everyone is religious, and fewer still are likely to be familiar with the details of early Christian hagiography. That is not the point. Commemorations like Saint Barbara’s Day function as regimental and professional traditions, not as tests of personal belief.
Marking the day can mean different things to different people:
For some, it may be a genuine act of faith, honouring a saint whose story inspires them.
For others, it is a way of respecting the heritage of their trade and the generations of RNZAOC and now RNZALR personnel who have done this work before them.
For many, it is simply a moment to reflect on the risks inherent in explosive work, to remember colleagues injured or killed in training and operations, and to recommit to doing the job as safely and professionally as possible.
In that sense, the story’s religious origins are less important than the shared meaning it has acquired over time. Saint Barbara becomes a symbol of the values that matter in ammunition work: integrity, courage, vigilance, and loyalty to those you serve alongside.
Contemporary Relevance: Commitment In A Dangerous Trade
In the modern world, the management of ammunition and explosives is governed by detailed regulations, sophisticated science, and digital systems, ranging from hazard classifications and compatibility groups to electronic inventory control and safety management frameworks. Yet, at its core, it still depends on human judgment and ethical commitment.
Saint Barbara’s Day offers a valuable lens for talking about that commitment:
Commitment to safety – understanding procedures not as bureaucracy, but as the accumulated lessons, sometimes paid for in blood, of those who went before.
Commitment to team – recognising that no Ammunition Technician works alone, and that a strong safety culture depends on everyone feeling empowered to speak up, check, and challenge.
Commitment to service – remembering that, whether in training at home or on operations overseas, the work is ultimately about enabling others to succeed and come home alive.
When Ammunition Technicians and their colleagues mark Saint Barbara’s Day, they are not stepping out of the modern world into a medieval one. They are taking a moment within a busy, technologically advanced, secular military environment to acknowledge that some fundamentals have not changed: courage, conscience, and care for others still matter.
Keeping The Flame Alive
Although the RNZAOC passed into history in 1996, its traditions did not vanish. They were carried forward into the RNZALR and live on in the customs, stories, and professional identities of those who wear the uniform today. Saint Barbara is one of those enduring threads.
On 4 December, when a small group gathers in an Ammuniton depot, unit lines, a mess, or a deployed location to raise a glass or share a few words in her honour, they are standing in continuity with generations of ordnance soldiers, armourers, gunners, and explosive specialists across time and across the Commonwealth. They are also quietly affirming something vital about themselves.
In the end, Saint Barbara’s Day is less about religion and more about recognition: recognition of a demanding craft, of the people who practise it, and of the responsibility they carry on behalf of the wider Army. For the RNZALR Ammunition Technicians of today, as for the RNZAOC of yesterday, she remains a fitting patron for those who work, quite literally, at the explosive edge of military service.
New Zealand’s military logisticians are more likely to be harmed by the conditions they create than by enemy fire, and the records often don’t exist when illness appears decades later.
Introduction
We have spent years teaching soldiers to look up and out for threats. For logisticians, the danger is just as often down in the ground they’re ordered to seize and make work at speed. Bomb‑damaged ports, airheads, railheads, fuel farms, hard standing, and battered warehouses are where supply chains are wrestled back to life. They are also where dust, residues, and fluids leave a lasting fingerprint on human health.
The uncomfortable truth is latency. Low‑to‑moderate exposures, taken in with every sweep of a broom, every cut of a disc, every lift of a drum, every hour around fuels and degreasers, rarely trigger an incident report. They build quietly under heat and exertion. The bill often arrives 10–40 years later as chronic respiratory disease, cardiovascular problems, or exposure‑associated cancers (including haematological malignancies). By then, units have disbanded, notebooks have been boxed or binned, and the link between a dusty floor in a shattered shed and a midlife diagnosis is far harder to prove.
Operational realities widen this gap. Operational tempo prioritises throughput over sampling; industrial hazards are treated as background noise; and protection is a general issue, not task-specific. In many theatres, the ethos was to get the job done. Keeping the lines moving eclipsed health and safety. The result? Too many logisticians carry “silent” injuries, not the wounds of a firefight, but the legacy of the estate underfoot.
Latency‑linked conditions to flag (illustrative, not exhaustive)
Sarcoidosis (months–years; sometimes later): an inflammatory granulomatous disease with recognised associations to inhaled particulates and combustion by-products (e.g., burn-pit smoke, fuel/solvent aerosols, mineral/metallic dusts, silica). In military logistics contexts, credible exposure pathways include routine work around burn pits, JP-8/Avtur/Avgas combustion products, and dust-rich industrial sites.
Solvents & fuels (5–25 yrs): Benzene and organic solvents are associated with haematological malignancies (e.g., AML, MDS, NHL); some degreasers are linked in studies to kidney/liver effects.
PCBs/dioxins (incl. Agent Orange/TCDD) (5–30+ yrs): non‑Hodgkin lymphoma, some soft‑tissue sarcomas, type 2 diabetes, chloracne.
Metals (varies): chromium VI → lung cancer; lead → neurological/haematological effects; cadmium → renal dysfunction and some cancers.
These are associations, not diagnoses. Individual risk depends on dose, duration, task and personal factors. The point is to signpost credible possibilities so exposure logging and follow‑up aren’t dismissed as “speculative”.
Illustrative exposure pathways reported by NZ logisticians
JP-8/Avtur/Avgas used to burn excrement (latrine waste disposal) → mixed hydrocarbon and particulate inhalation.
Proximity to burn pits for waste/rubbish disposal → complex combustion plume with fine particulates and mixed toxicants.
Asbestos exposure in damaged facilities — notably Somalia and Timor-Leste.
Pyrethrin-based insecticide ‘fogging’ for mosquitoes — operators in PPE while nearby logisticians worked without task-specific respiratory protection.
Silica and heavy dusts from industrial sites — e.g., Bougainville, living/working inside a large copper-mine building.
Somalia shows how routine logistics create hidden exposures
From late 1992 to July 1994, New Zealand rotated a dedicated Supply Platoon (43-strong, with an attached infantry section) through Mogadishu. The job was prosaic and relentless: a warehouse on the airport’s north ramp, a standing stores presence inside the port, and long days pushing relief tonnage through shattered infrastructure, at one point over 1,000 tonnes in a single month.
The ground itself told the story. Movements threaded past the ruins of an oil depot and fuel farms; across coral-sand and concrete dust; through mixed cargo residues (fertiliser, cement) laminated with marine oils and solvents; past derelict aircraft still weeping fluids, plus the familiar companions of collapse: metals, asbestos fragments, and sewage-affected water.
Protection was largely standard kit, helmets, frag vests, uniforms, rather than any specialist respiratory or dermal protection you’d expect in an industrial clean-up. The then-issue light fragmentation vest was widely regarded as unsuitable for the operating environment: confidence-boosting, yes; protective against chronic industrial exposures, no. Dress and load carriage reflected the heat and tempo more than hazard control (UN blue caps/baseball caps, PASGT helmets variably covered; relaxed working dress; webbing often set aside to work in vehicles and warehouses).
That is why ordinary tasks, sweeping bays, slinging pallets, cutting and rigging, refuelling, and marshalling MHE on contaminated hard-standing, can have extraordinary consequences years later when no one records what’s in the dust.
A recurring pattern across theatres
This is not an anomaly; it is a template visible across a century of New Zealand service:
World Wars — depots, docks, railheads (1914–19; 1939–45). Coal soot, cordite fumes, leaded petrol and chlorinated solvents in workshops; asbestos in roofing and lagging; cement and lime dust from rapid rebuilds. Throughput trumped surveys: trains to marshal, ships to turn, vehicles to repair. Hygiene focused on infection and water; industrial toxicology barely featured, so exposure notes were rare.
Korea — Kure and the Commonwealth base (1950–53). A sprawling pre-existing industrial estate re-tasked for logistics: oils, solvents and paints in abundance, metals and asbestos in shipyard fabric. NZ personnel moved through a machine built for output; documentation captured receipts and readiness, not the air and dust they worked in.
Malaya, Borneo and Singapore–Malaysia (1948–66; presence to 1989). Workshops and airstrips required fuels, degreasers, and hydraulic fluids as routine background; insecticides/defoliants were widely used; accommodations and facilities were still in the asbestos era. These were “normal” garrison tasks under tropical conditions, with latency risks unrecognised, and site hazards seldom logged.
Vietnam — Vũng Tàu and beyond (1964–72). Waste burning near lines of communication, pervasive dust, fuels/solvents, and herbicide-affected environments. Integration into Australian support chains normalised the setting; recognition came decades later at the cohort level, while many individual exposure trails remained thin.
Bougainville (1990s). Accommodation and work areas inside a large copper-mine building exposed personnel to silica-rich and metallic dust under hot, enclosed conditions.
Balkans — Bosnia/Kosovo rotations (mid-1990s–2000s). Logistics hubs established inside bomb-scarred industrial zones: transformer yards with PCBs, refineries, vehicle plants; warehouses with demolition dust and solvent films. Early-entry imperatives (“get the flow moving”) routinely outpaced site characterisation.
Timor-Leste (1999–2002). Burnt-out Indonesian-era facilities with asbestos roofing, ad-hoc waste pits, and heavy cement/brick dust from rapid repairs. Logbooks recorded cargo and convoy timings; personal exposure records were typically maintained only in the event of an incident.
Afghanistan (2003–2013). High-altitude fine dusts, continuous diesel exhaust, widespread solvent degreasing, and transits through hubs with burn-adjacent histories. The hazards were familiar yet diffuse, cumulative, not catastrophic, and thus rarely captured in neat exposure sheets.
Iraq — Taji and hub transits (from 2015). Flightline dusts, fuels/solvents, and the legacy of burn pits at specific coalition bases; constant MHE movements on contaminated hard standing. Unit logs were excellent for consignments and training cycles; environmental notes were sporadic and incident-driven.
The common pattern
Occupy damaged or industrialised ground → work at pace → accept “background” contamination as the price of tempo. Ordinary logistic tasks, such as sweeping, cutting, rigging, refuelling, and marshalling MHE, become exposure pathways, and latency hides the bill until long after the paperwork stops.
Why proof is missing — and why that shouldn’t be fatal
Exposures often fail to appear in files because command salience sits with security and throughput; coalitions churn and records fragment; hygiene doctrine long prioritised infection and water over industrial toxicology; and latency outlasts memory. Compounding this, many hazards that are now recognised and routinely mitigated, legacy asbestos, diesel-exhaust particulates and cumulative solvent exposure were, even less than thirty years ago, poorly understood or not considered in planning, PPE issues, or environmental reconnaissance. That is why Parliament enacted the Veterans’ Support Act 2014 (VSA): a benevolent, merits-based scheme that requires decision-makers to act reasonably, apply natural justice, and ensure equal treatment of equal claims.
Two schemes, same principles
The VSA operates
Scheme One (older cohorts/legacy service) and
Scheme Two (modern deployments from 1 April 1974 onwards, with a stronger rehabilitation focus).
Both schemes operate under the Act’s principle of benevolence. New Zealand adopts medical-scientific Statements of Principles (SoPs) from Australia’s Repatriation Medical Authority. Each SoP lists causal factors that, if present, link a condition to service. Two standards of proof apply: Reasonable Hypothesis (RH) for warlike/non-warlike (operational) service, a pro-veteran, lower threshold; and Balance of Probabilities (BoP) for peacetime/routine service, a higher threshold.
How decisions should run in practice.
If a relevant SoP exists, Veterans’ Affairs New Zealand (VANZ) tests the claim against it.
If the RH test is met for qualifying operational service, the claim must be accepted.
If no SoP applies or a SoP cannot neatly capture cumulative exposure, **section 15** applies: VANZ must accept the claim if it is consistent with a reasonable hypothesis based on the facts, unless there are reasonable grounds to believe it is not service‑related. This is the statutory safety‑net for thin or fragmented records.
Where veterans get tripped up when making a claim
Here is where the machinery breaks down: a process that treats missing records as the veteran’s problem and turns a benevolent scheme into an adversarial grind.
Thin records → heavy proof load on the veteran. Requests for exposure logs, sampling data, or site surveys that never existed end up weaponising the gaps the system created.
SoPs treated as gates, not guides. Complex, cumulative or novel exposures (multiple deployments, solvents, PCB yards) don’t map neatly to Statements of Principles, yet section 15 isn’t used early to accept a reasonable hypothesis.
Insurer-style posture. The process can feel adversarial, with repeated demands for “more” evidence, credibility challenges, and narrow readings of medical reports, especially when records are scarce.
Delay as denial. Multi-stage reconsideration/review/appeal stretches months into years; terminally ill veterans can die before resolution, or families inherit the burden mid-grief.
The state holds the data, while the veteran bears the risk. VANZ sits within NZDF, the institution with the records and institutional knowledge; yet, the evidential burden often rests with the ill claimant.
Language and culture mismatch. Claims framed like welfare applications rather than an earned entitlement under a State-fault scheme erode trust and deter engagement (contemporary veteran uptake is reported as extremely low).
If New Zealand truly values those who keep the lines moving, Veterans’ Affairs and the NZDF must do better: shift their efforts from surge-time forms to credible post-tour evidence so that tomorrow’s veteran has a fair shot.
When proof is already thin: build a triangle of proof
Site history: industrial uses, conflict damage, spill/burn areas, foam pads, mining legacies, and why it was dirty.
Medical trajectory: onset windows, peers with similar issues, GP/specialist notes and screening results.
Conclusion
Operationally, the principal danger to military logisticians is often not incoming fire but the estate underfoot, ground that must be made serviceable at pace and under pressure. Somalia serves as a national wake-up call: ordinary logistics in extraordinary environments, mainly undertaken in general-issue kit, with little of the exposure ever documented. Many hazards now recognised and routinely mitigated, such as legacy asbestos, diesel particulates, PCB yards, and cumulative solvent loads, were poorly understood or not considered less than thirty years ago, which only widens today’s evidential gaps.
Even so, that counsel comes too late for many operations up to the early 2000s, when industrial hazards were poorly understood and exposure logs were uncommon. Even if the chaos of early entry cannot be redesigned, commanders and agencies can still complete the process correctly by creating a usable record. A succinct post-tour bundle, filed with personnel records and the unit archive, should include:
a task/location timeline,
sketch maps and photographs of sites worked,
a note of known or likely prior industrial uses,
brief witness statements,
unit diaries and load/consignment lists,
and GP/screening notes (e.g., spirometry where relevant).
Decades later, this modest package can be the difference between a fair hearing and a polite denial. Where no bundle exists for historic tours, assemble the best available reconstruction from diaries, photos, unit logs, site histories, and medical notes.
On the claims side, practice should match principle. Decision-making ought to reflect the benevolent, merits-based intent of the law; use multiple pathways (SoPs and reasonable-hypothesis routes); and adopt a culture that investigates rather than contests. Independent oversight, separate from VANZ and NZDF, would help ensure that the absence of paperwork does not become the absence of justice.
Too often in military writing, it looks as if logistics “just happens”: an army is raised, equipment appears, stocks refill, and movement unfolds as if by instinct. In truth, nothing “just happens”. Across history—from spear-carriers and baggage trains to War Establishments and to today’s financially risk-averse, resource-restricted ecosystem—the science and art of logistics have quietly driven everything. This study uses history as a working tool: we read past practice to extract durable principles so tomorrow’s logisticians can scale deliberately, not by habit. Scaling is the mechanism that turns intent into counted people, platforms, rations, ammunition, repair parts, and lift so units arrive equipped, stay maintained, and fight at tempo. Without scaling, logistics is only an aspiration.
This guide sets out that mechanism in plain English. Across the force, the same logic applies: decide who gets what, make equipment complete and auditable, package predictably for movement, size, repair, depth to reliability and lead time, and maintain theatre resilience. Peace and war establishments are simply the entitlement “switch”; in-scaling and out-scaling dial the system up and down; and sound master data keeps automation honest. We ground the method in British and Commonwealth doctrine and New Zealand practice, using short case studies to show what works, what doesn’t, and why—so logisticians can make the deliberate, evidence-based choices that turn plans into assured sustainment.
In- and Out-Scaling
Scaling is how the system is dialled up or down. In-scaling builds people, equipment, stocks and permissions to meet a new or larger task. Out-scaling winds the same back down, tidying books and kit so the force is ready for what follows. The levers are the same; they move in opposite directions.
When to scale up
New equipment or a role change.
Mounting for deployment/exercises.
Seasonal/theatre shifts or higher tempo.
When to scale down
End of operation/rotation.
Capability withdrawn or mothballed.
Restructure or budget-driven footprint reduction.
What actually changes
People & entitlements: switch Peace Entitlement →War Entitlement, or role, issue the correct allowance lists.
Equipment completeness: make kit complete; rectify shortages; test.
Consumables & ammunition: set straightforward block issues and first-line loads that match the plan.
Spares & repair: size unit/depot spares to likely failures and lead times; preserve kit for storage/return.
Movement & footprint: translate scales into real loads (pallets/containers/ULDs) and book lift.
Data, compliance & money: update masters, licences and registers; close work orders; reconcile ledgers.
Planned and evidence-based (not guesses)
Scaling is a scientific, planned discipline with explicit service levels. Holdings are set from demand, reliability and lead-time data. Rules of thumb—for example, “carry 10% spares”—are avoided in favour of sizing to the target service level.
Common Pitfalls (and the Scaling Fixes)
Scaling is part science, part art. Some of the traps are timeless:
Issuing too much– Forgetting to adjust entitlements to actual strength leads to waste.
Repair underestimates– Peacetime spares won’t cope with wartime tempo; you need to scale for climate, usage, and lead times.
Lift blindness– A plan that looks neat on paper may be impossible to move unless scales are mapped to pallets, containers, or aircraft loads.
Footprint risk– Piling too much stock too far forward makes units vulnerable. Balance depth with dispersion.
Deep Historical Context: From Hoplite to Legionary to Tümen
From antiquity to the steppe, Rome and—centuries later—the Mongol Empire show how standardised building blocks, fixed measures and modular kits turned formations into predictable logistics: the Romans through contubernia, rations and marching camps; the Mongols through decimal organisation, remounts and the yam relay.
Greek city-states (c. 6th–4th centuries BCE): The Phalanx as a Scale
Standard fighting load. The hoplite panoply (shield, spear, helmet, body armour) functioned as a personal equipment scale; city‑states enforced patterns so men fought as interchangeable blocks.
Rations and measures. Planning by standard measures (e.g., set grain issues per man per day) made food and water predictable, and hence movable.
Formation → sustainment. Dense heavy infantry implied slower roads and higher baggage/forage demand—an early proof that formation design fixes the sustainment scale (wagons, pack animals, camp followers).
Rome (c. 2nd century BCE – 3rd century CE): Scaling by Modular Blocks and Doctrine
Contubernium as the “unit set.” Eight soldiers shared a mule, tent, tools and cooking gear—a micro‑scale that multiplied cleanly to centuries, cohorts and legions.
“Marius’ mules.” Standardising the soldier’s carry (a first-line load) reduced trains forward, while heavier impedimenta marched to the rear—an ancestor of today’s 1st line vs 2nd line.
Daily ration and marching camp. Fixed grain allowances, routine camp layouts, ditch/stake quantities, and normalised road days enable staff to convert order of battle into tonnage, tools, time, and space—the essence of scaling.
State supply. The Annona, roads and depots added a strategic tier of standardised contracts, weights and distances—scaling endurance to seasons, not days.
The Roman Cohort Illustration by Peter Dennis. Credit: Warlord Games Ltd.
The Mongol Empire under Chinggis (Genghis) Khan (13th century): Decimal Organisation and Portable Sustainment
Decimal structure = instant multipliers. Arban (10), zuun (100), mingghan (1,000), tümen (10,000) created a universal grammar of scale: equip and feed an arban, and you can multiply to a tümen without changing the recipe.
Remounts as a ration of mobility. A scale of remount horses per warrior standardised range and resilience; spare mounts were the mobility equivalent of extra fuel cans.
Self-contained field kits. Common personal kits (bows in standard bundles, lariats, spare strings, tools, felt gear) and household tents/carts made each decimal block logistically modular.
The yam relay. A state courier/relay network with post‑stations and passes pre‑scaled communications and light logistics into predictable legs.
Task‑tailored attachments. Siege/engineering blocks bolted onto the cavalry core when required—early attachments on a standard base.
Genghis Khan’s empire and campaigns. Wikimedia
Throughline: A formation is a logistics equation. Standard measures enable standard issues. Modularity makes mass possible.
The Nineteenth‑Century Step Change — Britain’s Army Equipment System (1861–66)
In the reform decades after Crimea, the War Office published the seven‑part Army Equipment series (Artillery; Cavalry; Infantry; Royal Engineers; Military Train; Commissariat; Hospital).[1] Each volume tied official organisation to authorised equipment lists, weights, measures (often prices), transport tables, and packing/marking rules. Once you knew the unit—infantry battalion, artillery battery, engineer company, or Military Train echelon—you could multiply the lists and convert entitlements into lift and sustainment. Support arms were treated as modular blocks (e.g., Commissariat trades; Hospital sets) scaled to force size and role.
What changed: This turned scaling into a published operating system for logistics—standard nomenclature matched ledgers; weights and measures turned entitlement into tonnage; common patterns let staff scale issues, movement and maintenance simply by multiplying unit counts.
Example of a table from Army Equipment. Part V. Infantry 1865
Peace vs War Establishment — The Scaling “Switch”
Establishments are the authorised blueprints for people, vehicles, weapons, tools and key stores—held in two states:
Peace Establishment (PE): Cadre‑heavy and economical (training scales, minimal transport; many posts unfilled; war‑only items held centrally).
War Establishment (WE): Fully manned and fully equipped (complete Equipment and first/second‑line holdings; authorised transport and attachments—signals, medical, supply/transport, maintenance—baked in).
Mobilisation tops up PE to WE: fill personnel (Regulars/Reservists/Territorials), issues unit entitlement, builds lift and repair depth, loads first-line holdings, form attachments, and declares readiness. Because WEs link directly to scales, a unit can be multiplied and supported predictably. In service terms, the scaled package is then delivered through various types of support—integral, close, general, and mounting—each tailored to those entitlements and holdings.
Types of support.
Integral — organic, first-line support within the unit. (1st Line)
Close — formation troops forward, delivering time-sensitive commodities and quick repair/recovery. (2nd Line)
General — force-level support to the whole formation (bulk stocks, distribution, heavy repair). (3rd line; sometimes spans to 4th depending on the army)
Mounting — generating/equipping/marshalling the force before deployment. (a pre-deployment phase, not a “line”)
(Illustrative maxim) Alter one allowance, alter the lift: add a blanket per man, and you add wagons to the transport scale. Scaling is a system—inputs ripple into horses, drivers and wagons.
Late Victorian to 1914 — Scaling Rehearsed in Peace (NZ)
New Zealand did not drift into World War I. In the years following the war in South Africa and especially under the Territorial Force (from 1910), planners adapted British military establishments to practical peacetime scales and rehearsed them. Camp equipment was centralised and issued according to published scales for the 1913 brigade camps. Districts drew against these scales, and returns/refurbishment were managed according to plan. To ensure the issue/return machine functioned efficiently, temporary Ordnance Depots were established for the 1913 camps (and again for the 1914 divisional camps), staffed with clerks and issuers under regional storekeepers—so requisition, issue, receipt, and repair all followed a single process.[2]
Example of New Zealand Camp Equipment Scale 1913
In parallel, the Defence Stores professionalised: permanent District Storekeepers were appointed, and an intensive store management course produced Quartermaster Sergeants for every infantry and mounted regiment, tightening the link between unit ledgers and district depots. By early 1914, the force had been inspected and judged to be well-armed and well-equipped, and mobilisation regulations—adapted from British directives—were issued in March 1914, aligning establishments, ledgers, and stocks.[3] The result was a pre‑war system that treated scaling as a living routine, not an emergency improvisation.
World Wars & Interwar — Scaling at Industrial Tempo (UK & NZ), 1914–45
First World War (1914–18).
The British Army’s War Establishments and matching scales of equipment underwrote rapid expansion from Regulars to Territorials to Kitchener’s New Armies.[4] New formations could be raised and fitted out by template—weapons, tools, transport, ammunition, clothing, medical stores and repair parts, all mapped from the WE. For a smaller force such as New Zealand, alignment with British establishments and scales enabled swift mobilisation and five years of sustained operations.
Saddlers Toolkit – Handbook of Military Artificers 1915
Interwar (1919–39)
Rather than a pause, this period saw refinement and governance of scaling. G1098 (AFG1098) matured as the unit‑level ledger linking establishment to holdings; mobilisation store tables and Clothing/Equipment Regulations were revised; Dominion practice tightened accounting controls and depot procedures. From 1935, although New Zealand lacked a standing field army, planners tracked British developments closely—each new War Establishment, scale and entitlement as it was published—and adapted them to local conditions (manpower, industry, shipping distances and climate). Thus, when mobilisation began in 1939–40, New Zealand could raise, equip, and structure its forces on modern British templates, rather than through improvisation.
Second World War (1939–45)
Scaling went fully industrial. Theatre-specific clothing scales, bulk demand procedures for ordnance, formal first/second‑line holdings, and push vs pull replenishment methods were used to keep tempo while protecting scarce lift and stocks. Units continued to work to WE/scale templates, with depots, railheads and parks sized to the calculated flows.[5]
Ammunition Loads – Ordnance Manual (War) 1939
Case Study — Greece 1941: mis-scaled ordnance support
Context. In March 1941, the New Zealand Division deployed three Independent New Zealand Ordnance Corps (NZOC) Brigade Workshops and eleven LADs to Greece, with the attached British Royal Army Ordnance Corps (RAOC) 1 Ordnance Field Park (1 OFP) providing forward spares and stores.[6] Pre-deployment consultation was thin; scaling assumptions followed British fleet patterns rather than New Zealand holdings.
What went wrong (the scaling error).
Wrong spares mix. 1 OFP was scaled for Internationals and Crossleys; the NZ Division fielded neither in any number (only two Crossleys), so much of the forward lift didn’t match the fleet it had to support.
Assumptive, not analytical. Holdings mirrored generic expectations instead of the Division’s actual G1098s, failure rates, and service-level targets.
Coalition data gap. Equipment data and entitlement tables weren’t reconciled across national lines before movement.
Consequences in theatre.
Readiness lost at the point of need. Lift and time were consumed carrying low-utility spares forward.
Workarounds required. Support hinged on the subset that did match (e.g., Ford, 25-pdr, 2-pdr, spring steel, sheet/rod metals, compressed air, general items) plus local supplementation—enough to keep NZ Workshops going, but with friction and delay.
Campaign outcome. The Greek campaign collapsed into evacuation (and then Crete), compounding the cost of the initial scaling miss.
Fix and regeneration (the recovery).
Rebuild in Egypt. NZOC consolidated with RAOC/Maadi resources and formed the NZ Divisional OFP on 28 July 1941, explicitly scaled to NZ kits.
Deliberate scale-up. Through August–September the OFP built to scale, trained on ordnance accounting, and aligned data to reality.
Right-sized footprint. By late 1941 the OFP held 4 officers, 81 ORs and 27 three-ton lorries configured for OFP stores—turning scaling from assumption into a planned capability.
Practical fixes (what should have been done).
Make scaling scientific. Use master data, reliability/failure rates, demand and lead-time to size spares and blocks; set explicit service-level targets.
Don’t rely on rules of thumb. Ditch “10% spares” heuristics—scale to the actual fleet and mission.
Close coalition gaps early. Reconcile equipment and entitlement tables across partners before you book the lift.
Translate scales to footprint. Convert to pallets/containers/ULDs with correct packaging and documents; protect the lift.
Capture and apply lessons. After action, cleanse data, adjust, and rebuild to standard—exactly what the NZ Div OFP did after Greece/Crete.
Takeaway. Scaling only works when it’s fleet-true, data-driven and coalition-aligned. Get that right pre-deployment, and your forward park becomes a force multiplier rather than a passenger.
Post-War Evolution — From a Single List to an Integrated Entitlement System (NZ Focus)
Example of AFG1098 Accessories and Spares for Bren .303 M.G
Post-1945 fleets—communications, electrics, vehicles, and specialist plant—stretched the old, flat G1098 list. By the late 1950s–60s, practice matured into three coordinated instruments:[7]
Entitlement (Equipment) Tables— the core “who gets what” by unit role and establishment.
Complete Equipment Schedules (CES) — the “what is complete” list for each equipment set (every component, tool, accessory), doubling as the accounting document for that set.
Block Scales — pooled non-CES items and everyday consumables (stationery, training stores, domestic items) expressed as ready-to-issue blocks.
New Zealand’s tailored, Commonwealth-compatible model (1960s)
The New Zealand Entitlement Table (NZET) became the hub, explicitly incorporating New Zealand CES (NZCES) items (and their components), New Zealand Block Scales (NZBS) for non‑CES stores, and first‑line maintenance packs such as FAMTO (First Aid Mechanical Transport Outfit) and FATSO (First Aid Technical Stores Outfit) so operators could keep equipment serviceable between deeper repairs.[8]
By the early 1970s a further pillar emerged: New Zealand Repair Parts Scales (NZRPS). From the late 1960s, these began to replace earlier “spare parts lists,” folding FAMTO and FATSO in as first‑line modules of a wider repair‑chain planning scale—so unit Prescribed Load Lists (PLL) (days‑of‑cover + pipeline), formation Authorised Stockage Lists (ASLs) (service level over replenishment time) and theatre reserves were all sized from the same tempo/lead‑time/reliability factors. In short, repair provisioning became a single, scalable chain from operator kits through to depot depth.
Case Study — Malaysia & Vietnam (1965–1972): combined scaling to autonomy
Context. New Zealand kept a battalion in Malaysia/Singapore with 28 (Commonwealth) Brigade while rotating a rifle company into Vietnam under 1 ATF—three systems at once (British, Australian, NZ) with different entitlements, CES, paperwork and spares. The task was to turn them into one workable load for training in Malaysia and fighting in Phước Tuy.
What worked (the scaling approach).
One combined scale, three sources. Cross-walked UK/AUS entitlements to NZ holdings; set approved equivalents for non-matching items.
Climate-first. Tropical scales for clothing/boots/personal kit; higher replacement factors and wider size ranges.
CES by platform. Normalised vehicle/tool sets so workshops and lift could be planned regardless of source nation.
Local industrial equivalents. Qualified NZ-made clothing, boots, webbing and small stores to UK/AUS specs to cut lead-times and dependency.
Liaison & data discipline. NZ LOs embedded in 1 ATF/FARELF to keep demand, returns and credits clean; part codes aligned early.
People matched to plan. Increased NZ movements, supply and maintenance manning in Malaysia and in-theatre.
Results.
Seamless support in Vietnam. Routine sustainment via Australian pipelines; NZ-specific items flowed via Malaysia/Singapore with minimal friction.
Fewer workarounds, faster repair. Equivalence lists and aligned CES cut “near-miss” parts and sped turnarounds.
Why it mattered later.
As UK/AUS withdrew from Malaysia in the early 1970s, NZ’s habits—combined scales, clean data, boosted manning and a growing local supply base—left the battalion near-logistically independent.
NZ-made equivalents added depth and resilience, enabling New Zealand-led sustainment.
What to copy.
Build a cross-walk early and lock approved equivalents in SOPs.
Scale for climate and task (clothing, rations, POL, repair parts).
Embed liaison/data stewards with partners.
Man to the plan—grow workshops, supply and movements to match scale.
Qualify local industry to shorten lead-times and strengthen sovereignty.
Takeaway. Combine partner scales with NZ holdings, qualify local equivalents, and resource the logisticians—then a company can fight in Vietnam while a battalion trains in Malaysia, and the force is ready to stand on its own as partners draw down..
From Printed Tables to Digital Systems (1960s–today)
Until the 1980s, scaling was a manual staff drill: planners worked from printed tables, equipment series, mobilisation stores tables and unit instructions, doing the maths by hand—later with basic calculators—and re-checking totals across ledgers and load tables. With computer-based logistics, the arithmetic and cross-checks moved into software: entitlement look-ups, strength-based calculations, days-of-cover policies, lift planning from pack/weight data, and target-setting from demand history. The gains were speed, consistency, auditability and the ability to model scenarios.
Many forces—including New Zealand—progressed from electric accounting machines and mainframes to enterprise ERPs by the late twentieth century, with deployable tools to support entitlement planning. Automation expanded what staff could calculate quickly; it did not replace the need for clear, maintained scales.
Crucially, automation only works with sound data and governance. Organisations change, equipment is updated, and missions evolve; unless master data—organisational structures/establishments, item masters/part numbers, CES versions, block-scale definitions, repair parts scales and links to maintenance task lists—is kept current under change control, systems will produce inconsistent outputs. The principle is simple: keep entitlements, scales and planning factors aligned across supply, maintenance and movement. Contemporary doctrine reinforces this, emphasising information systems for visibility and decision-making, underpinned by disciplined data stewardship.
Case Study — Somalia 1993: when scaling wasn’t applied (and what changed)
Context. New Zealand contingents in Somalia (1992–94) deployed into extreme heat and vehicle-centred tasks, yet much of the kit reflected a temperate, barracks-oriented baseline—signs that entitlements and CES were not re-scaled for climate, role, or threat. To add insult to injury, the advance party deployed into an active conflict zone without weapons. Part of the reason it went wrong was that, at the time, the Army was not configured for rapid expeditionary operations.
What should have been scaled—but wasn’t. Hot-weather clothing and headgear; body armour matched to the threat; vehicle-friendly load carriage; and weapon accessories (e.g., pistol holsters) to match in-service weapons.
Consequences. Under-utilised scale (issued items set aside for improvised workarounds), inconsistent appearance/ID in theatre, and slower adaptation when the threat rose.
After-action learning—Bosnia as the correction. The Army was embarrassed by the Somalia experience and did learn. Subsequent Bosnia deployments were better resourced and equipped: theatre-specific clothing and boots were prioritised; body armour and load-carriage were selected for the task and climate; weapon ancillaries were matched before deployment; and theatre SOPs were clarified. In short, the levers of scaling were applied up-front instead of improvised in theatre.
Takeaway. Treat scaling as deliberate tradecraft before wheels-up: set climate-appropriate clothing scales, match armour and load-carriage to tasks, close ancillary gaps, and codify it all in SOPs. Do that, and the force arrives ready; skip it, and soldiers will improvise uneven fixes in contact.
Why Scaling Matters
Doctrinally, scaling underpins the core logistics principles—Responsiveness, Simplicity, Economy, Flexibility, Balance, Foresight, Sustainability, Survivability and Integration—by turning intent into standard, reusable units of effort.[9]
Budget reality. Scales translate limited resources into repeatable outputs. They allow commanders to make explicit trade-offs between cost, risk, and tempo, and they expose the carrying costs of options (people, stock, space, lift) before money is spent. In fiscally constrained settings, scales are the difference between a force that looks large and a force that lasts. (Then and Now)
Control. Replaces ad‑hoc estimates with standard, repeatable calculations.
Agility. Dial effort up for surge or down for economy without needing to rewrite plans.
Interoperability. Standard blocks and tables let allies plug in seamlessly.
Assurance. Creates an audit trail for readiness claims and expenditure.
Risk management. Ties stock depth and footprint to threat, distance and tempo.
Instruments of Scaling — Quick Guide
When logisticians talk about “scales,” they’re really talking about ways of turning entitlements on paper into real-world stocks, vehicles, or pallets. A few of the main ones are:
Tables of Entitlement – These are the official “allowance lists” for units. They can be adjusted depending on the number of people present, the role the unit is playing, or even the climate. They shape both the unit’s footprint and its initial kit issue.
CES (Complete Equipment Schedules) – Every vehicle or platform comes with a kit list. Multiply that by the number of platforms, add any mission-specific kits, and you get both the accounting baseline and a sense of what workshops and lift have to carry.
Block Scales – Think of these as pre-packed bundles: ammunition, rations, POL (petrol, oil, lubricants), water, consumables, even stationery. They’re designed in mission-length chunks that map directly onto pallets, containers, or sorties.
Ration Scales — Per-person, per-day entitlements (e.g., fresh, composite, MRE/24-hour packs). Sized by headcount and duration, with first-line holdings at unit level and theatre stocks behind them.
Fuel Scales (POL) — Daily fuel requirements derived from platform consumption and tempo (include generators/heaters). Planned as bulk and/or packaged supply with defined reserves.
Clothing & Personal Equipment Scales — Initial issue and replacement factors (boots, uniforms, cold-weather gear). Driven by climate and wear-rates; size ranges require buffer stock. Set climate-specific scales; use approved equivalents across NZ/Allied patterns
Repair Parts Scales – Units carry a few days’ worth of spares on hand, while second-line supply aims to hold enough to cover expected breakdowns over the lead time.
First-Line Ammunition – This is the starter load troops carry into action, balanced against how quickly resupply can arrive.
WMR/DOS (War Maintenance Reserve/Days of Supply) – Larger-theatre stockpiles held to cushion delays or enemy interdiction.
All of this contributes to the classic push versus pull distinction. Push works best when demand is predictable (e.g., food, water, combat supplies), while pull suits variable or diagnostic needs (e.g., spare parts, casualty evacuation). Each commodity sits somewhere on that spectrum, and stock policies need to reflect that.
Scaling in Practice — A Common Framework
The beauty of scaling is that it works at every level. The same levers—entitlements, CES, block scales, repair parts, first-line ammunition, and WMR/DOS—apply whether you’re supporting a corps or a rifle section. The only difference is the number of multiples and echelons involved.
In effect, the same logic sizes a divisional-level park to last a day and a platoon’s first-line to last an opening skirmish. A section’s water is just the smallest expression of the same logic. What matters is anchoring decisions to the wider continuum—tactical, operational, and strategic—so that what a company carries dovetails with what the theatre holds in depth.
Case Study – 3 NZ Div reverse logistics (out-scaling best practice)
Context & scale. When 3 New Zealand Division was withdrawn from the Pacific in 1944, New Zealand executed a full reverse lift and regeneration: over 50,000 line items, 3,274 vehicles (plus 25 tanks) and tonnes of ammunition and supplies were received, cleaned, repaired, repacked and re-issued or disposed of—without forklifts or computers. Mangere Crossing Camp (ex-US “Camp Euart”) became the hub, with 200,000 sq ft of warehousing and a rail siding that ran straight into the storage blocks, allowing trains to off-load directly under cover. Work parties manually handled 250,000 packages averaging 45 kg, and about 10,000 tonnes of mixed stores arrived in the first three months from August 1944; the whole evolution concluded by July 1945.[10]
Method—how it worked.
Pre-exit accounting. Quartermasters across 90 accounting units completed inventories and packing lists in New Caledonia before lift.
Reception & triage. On arrival at Mangere, loads were checked against documents, segregated by condition, and queued for cleaning/repair.
Restore for re-use. Items were cleaned, repaired and repacked to unit standard, then presented for inspection.
Audit & acceptance. Main Ordnance Depot staff and Defence auditors enforced exacting standards; discrepancies were explained and cleared before acceptance.
Disposition. Serviceable materiel moved to Trentham (Main Ordnance Depot) or Hopuhopu (Northern District); many vehicles to Sylvia Park for onward issue; surplus or damaged items were transferred to the War Assets Realisation Board for sale or disposal.
Constraints & workarounds. With no MHE or IT, the system relied on infrastructure (rail-to-warehouse flow), disciplined paperwork, and hard, organised labour. Quartermasters—often not career logisticians—proved adaptable under high audit pressure, demonstrating that well-designed processes can substitute for technology when needed.
Why this is out-scaling done right.
Treated dismantling as deliberately as build-up—planned reverse from theatre to home base.
Aligned supply, maintenance and movement tasks (clean/repair/repack embedded in the flow).
Used fixed infrastructure to compensate for missing tools (rail siding, large covered floors).
Kept data discipline central: inventories, packing lists and audits drove every hand-off.
Produced a regeneration effect—restored force elements, cleared accounts and returned value to the system—on a national scale.
Takeaway. Reverse logistics is not an afterthought. Plan the out-scaling from day one, resource the reception base, couple repair with receipt, and enforce documentation—then even a technology-light force can bring a division home cleanly and quickly.
3 NZ Division Tricks and Tanks parked at Main Ordnance Depot, Mangere Bulk Depot on their Return from the Pacific in 1944 (Colourised). Alexander Turnbull Library
Conclusion
From the hoplite’s panoply and Rome’s contubernium to the Mongol tümen; from the Victorian Army Equipment series to modern War Establishments and today’s Entitlement–CES–Block toolkit (including NZ’s FAMTO/FATSO), the lesson is constant: scaling is the lifeblood of logistics. It turns intent into counted people, platforms, ammunition, spares, and lift—precisely, repeatably, and at the tempo operations demand.
In practice, scaling provides a standard framework: entitlement tables specify who receives what; CES ensures equipment is complete and auditable; block scales package predictable consumables for movement; repair-parts scales establish first- and second-line resilience; and WMR/DOS provides theatre depth. The art is in balancing the push for predictability with the pull for diagnostic, variable demands.
This is not optional tradecraft. Every headquarters and every trade must treat scaling—and the data that underpins it—as core business. Keep establishments current, masters clean, and paper scales translated into real pallets, bookings and stocks so that automation amplifies judgment rather than propagating error. Do this and the force can surge, re-role and wind down cleanly; neglect it and you invite a modern reprise of the Crimean lesson—impressive on paper, unsustainable in contact. Scaling is how intent becomes assured movement and sustainment.
Notes
[1] The Secretary of State for War, “Part 2 – Artillery,” Manual of Army Equipment (1861), https://rnzaoc.files.wordpress.com/2018/08/army-equipment-part-2-artillery-1861.pdf; The Secretary of State for War, “Part 1 – Cavalry,” Manual of Army Equipment (1863); The Secretary of State for War, “Part 5 – Infantry,” Manual of Army Equipment (1865); The Secretary of State for War, “Part 6 – Commissariate Department,” Manual of Army Equipment (1865), https://rnzaoc.files.wordpress.com/2018/08/army-equipment-part-6-commissariat-department-1865-1.pdf; The Secretary of State for War, “Part 4 – Military Train,” Manual of Army Equipment (1865); The Secretary of State for War, “Part 7 – Hospital,” Manual of Army Equipment (1865); The Secretary of State for War, “Part 3 – Royal Engineers,” Manual of Army Equipment (1866).
[10] Francis Arthur Jarrett, “2NZEF – 2 NZ Divisional Ordnance Field Park – Report – F Jarret,” Archives New Zealand Item No R20109405 (1944); “QMG (Quartermaster-Generals) Branch – September 1939 to March 1944,” Archives New Zealand Item No R25541150 (1944); “HQ Army Tank Brigade Ordnance Units, June 1942 to January 1943,” Archives New Zealand Item No R20112168 (1943).
