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.
From the Waikato Commissariat to SAP, battlefield management systems and unmanned distribution.
The next major transformation in New Zealand Army logistics may not be defined by autonomous vehicles or drones, but by Defence’s logistics systems’ ability to connect operational requirements with the resources needed to sustain deployed forces. Autonomous technologies offer new means of transporting supplies, but their operational value will depend on how well they are incorporated into established logistics arrangements.
In July 2026, Drones, Distribution and the Small Army: Logistics for New Zealand’s Motorised Infantry Future examined how unmanned aerial systems might transform supply delivery to New Zealand soldiers operating on dispersed and contested battlefields. The article considered the vulnerability of conventional replenishment arrangements and the opportunities presented by autonomous technologies.[1]
Developments since then have made the subject more immediate. Singapore’s experimentation with its Next Generation Infantry Battalion during Exercise Wallaby 2026, together with New Zealand’s unmanned-vehicle trials, suggests that autonomous systems are becoming a practical question for military capability development.
An unmanned vehicle does not, by itself, transform military logistics. It provides another means of distribution, but it must operate within a system that identifies requirements, manages resources, sets priorities and coordinates support.
For the New Zealand Army, this raises a broader question: how might Defence’s enterprise logistics systems, tactical digital capabilities and movement-management arrangements evolve to support increasingly automated distribution?
The question is not new. Successive generations of New Zealand logisticians have confronted the same problem of coordinating supply, transport, information and accountability, and how they addressed it offers a useful foundation for thinking about the Army’s future.
An Old Problem in a New Form
Whatever the technology, the underlying challenge has been consistent: an army must obtain resources, organise their distribution and keep enough control over both to sustain its operations.
During the Waikato campaign of 1863–64, British forces relied on roads, river transport, animal-drawn vehicles and forward depots to sustain troops advancing south from Auckland. As Richard J. Taylor shows in his study of British logistics during the New Zealand Wars, the campaign depended as much on the organisation and coordination of these resources as on the transport equipment itself.[2]
Deputy Commissary-General Humphrey Stanley-Jones supervised a distribution system that used bullock wagons, horse-drawn vehicles, steamers, barges, and canoes. Taylor records that some stores were handled as many as sixteen times between Auckland and Ngāruawāhia, with each transfer creating additional work and increasing the risk of damage, loss, or errors in accountability.
British military activity at Pukerimu on the Waikato River, April 1864. Steam-powered river transport was a key part of the distribution network that sustained British operations during the Waikato campaign. Alexander Turnbull Library Reference: E-047-q-046 by Joseph Osbertus Hamley
An organisational disagreement in 1864 brought the issue into sharp focus. After the 4th Battalion Military Train arrived, its commander proposed absorbing the Commissariat Transport Corps into the Military Train. Senior Commissariat officers opposed the proposal, maintaining that the organisation responsible for obtaining and distributing supplies needed effective control over how they reached the troops. General Cameron ultimately retained separate responsibilities, with the Military Train undertaking selected transport duties while the Commissariat Transport Corps continued supporting much of the forward distribution system.[3]
The disagreement raised a question that remains relevant: should the organisation operating transport equipment determine how it is employed, or should the logistics system responsible for meeting operational requirements coordinate its employment?
Autonomous vehicles present the same problem in a new form. A drone might be operated by infantry, a logistics organisation or a specialist unmanned-systems element, but responsibility for operating the platform does not necessarily confer authority to establish supply priorities independently of the wider distribution system.
The technology has changed since 1864. The requirement to coordinate supply and movement has not.
From Movement Control to Computerised Supply Accounting
The expansion of New Zealand’s expeditionary commitments during the twentieth century progressively increased the complexity of military distribution. Deploying and sustaining forces overseas required coordination between depots, ports, airfields, staging areas and deployed units, frequently involving several modes of transport.
Specialist movement-control, terminal and air-dispatch capabilities developed because military movement involved more than providing vehicles, ships or aircraft. It also required managing capacity, priorities, destinations and documentation.[4]
A comparable transformation occurred in stores administration. For much of its history, the Royal New Zealand Army Ordnance Corps (RNZAOC) relied on handwritten records, vouchers and ledger cards to manage inventories. Although these arrangements provided accountability, they were labour-intensive and depended on accurate and timely manual transactions.
The introduction of Hollerith punched-card records in 1958 marked an important step towards mechanised supply accounting. Electronic accounting machines and computerised systems subsequently improved transaction processing and the production of inventory information.[5]
The Defence Supply System Retail (DSSR), introduced during the 1980s, and the subsequent Defence Supply System Development (DSSD) continued this progression. Both initiatives sought to improve inventory management and reduce delays and inconsistencies associated with earlier arrangements.
Nevertheless, computerisation introduced new challenges. Personnel required training, records had to be converted, and procedures revised. The usefulness of information also depended on how promptly transactions were completed. A central computer might hold extensive inventory records, but those records could become outdated when activity at a supply unit was not reflected quickly enough.
These limitations became particularly evident when computerised logistics support was extended into the field. During Exercise Golden Fleece in 1989, the Army experimented with providing deployed logistics organisations access to Defence supply information through mainframe terminals. The COMRAT ration-management application was also trialled on portable computers, demonstrating how relatively modest technology could reduce repetitive administrative work and assist field planning.[6]
Hewlett-Packard Portable Vectra CS used by New Zealand Army logistics personnel in 1989. Portable computers were among the technologies evaluated as the RNZAOC sought to extend computerised supply and ration-management capabilities into the field. Robert McKie Collection.
These experiments brought logistics information closer to deployed organisations while highlighting the difficulties of transferring systems developed for established facilities into environments where communications, equipment reliability and technical support imposed additional constraints. Improvements in information processing proved most useful when matched by procedures and equipment suited to the conditions in which soldiers operated.
Project Fusion, SAP and the Integration of Army Logistics
During the 1990s, the New Zealand Defence Force (NZDF) undertook a wider transformation of financial, inventory and maintenance-management systems.
Project Fusion, initiated in 1994, introduced SAP enterprise resource planning software to integrate functions previously managed through separate applications. Financial management entered operation in 1996, followed by inventory and logistics management in 1998 and plant maintenance in 1999.[7]
The new environment provided opportunities to connect stock holdings, equipment records, maintenance activities and associated financial transactions through more consistent information and business processes.
Technological reform coincided with significant organisational change. On 9 December 1996, the Royal New Zealand Army Logistic Regiment (RNZALR) was formed by amalgamating the RNZAOC, the Royal New Zealand Corps of Transport (RNZCT) and the Royal New Zealand Electrical and Mechanical Engineers (RNZEME).[8] The regiment brought together the principal supply, transport and maintenance functions, recognising the increasing interdependence of activities previously undertaken by separate corps.
Although Project Fusion and the formation of the RNZALR were distinct initiatives, both reflected the same requirement: closer coordination between logistics functions. SAP integrated the information; the RNZALR integrated the people and trades.
Neither reform eliminated complexity. Inventory accuracy still depended on disciplined transactions, while an integrated computer system did not automatically produce an integrated organisation. Nevertheless, both laid foundations for later improvement.
Singapore and the Next Generation Infantry Battalion
Singapore offers a useful comparison because it, too, must generate military capability from a limited personnel base, and it is actively integrating new technology into its force rather than simply acquiring it.
During Exercise Wallaby 2026 in Queensland, the Singapore Armed Forces tested elements of its Next Generation Infantry Battalion (NGIB), an evolving concept combining revised organisation, digital command systems and unmanned platforms. Singapore’s Ministry of Defence describes a battalion incorporating dedicated unmanned-systems elements, including reconnaissance and attack drones, supported by integrated command-and-control arrangements.[9]
Singapore Army personnel prepare a fixed-wing unmanned aerial vehicle during Exercise Wallaby 2025 in Queensland, Australia. Singapore’s continuing experimentation with unmanned systems forms part of its broader efforts to improve infantry effectiveness and integration. Singapore Ministry of Defence.
The NGIB’s significance lies not in the drones themselves but in building unmanned technologies into the organisation and operating methods of infantry formations, redistributing tasks between soldiers and machines rather than treating unmanned systems as supplementary equipment.
That is the lesson for New Zealand. The NZDF’s unmanned-systems trials are a necessary start, but trialling platforms is not the same as integrating them. Singapore is changing organisation, command arrangements and operating methods alongside the equipment, and New Zealand will need to do the same if autonomous systems are to deliver more than isolated demonstrations. The NGIB is not an autonomous logistics system, and conventional combat service support remains essential. It does, however, show the deliberate, whole-of-force approach that New Zealand Army logistics will need.
There is also an important distinction between remotely operated, supervised autonomous and more fully autonomous systems. A remotely operated vehicle may remove a driver from immediate danger while retaining a substantial operator workload. A supervised autonomous system may undertake some navigation or movement functions independently but still require human oversight and intervention. Greater autonomy raises further questions of reliability, decision-making authority and accountability.
Integration is also less about replacing logistics personnel than about examining whether new technologies can improve their effectiveness. Any assessment must consider the complete workload, including operators, maintainers, communications specialists and recovery personnel, rather than simply counting the drivers a particular journey might no longer require.
The Digital Gap Between the Battlefield and the Supply System
The NZDF already possesses much of the digital infrastructure on which future logistics capabilities could be built. SAP supports key aspects of inventory, maintenance, and resource management, while the Army’s Network Enabled Army (NEA) programme is introducing tactical communications, information-sharing, and battlefield management capabilities.
The Ministry of Defence identifies SitaWare as the Battle Management System acquired through NEA, alongside deployable servers, digital devices and communications infrastructure intended to improve situational awareness and information exchange.[10]
These systems serve different purposes. SAP manages Defence resources and their associated records, while SitaWare supports tactical command and coordination. Their functions are complementary, but public information does not show how far logistics requirements and inventory data can pass between them. That matters when deployed units need supplies.
From Operational Requirement to Logistics Response
Consider a hypothetical motorised infantry company operating 40 kilometres from its supporting logistics element. One of its vehicles becomes unserviceable because of a failed component, creating an urgent requirement for a replacement.
The company communicates its requirement to the supporting logistics organisation, which must identify the component, confirm availability, determine priority, and arrange delivery. Depending on the procedures and systems available, these activities may involve separate communications, manual coordination and transactions across different applications.
A more closely integrated arrangement could allow an authorised requirement to enter a governed logistics workflow, with relevant status information returned to the supported unit as the demand progresses. This would give commanders improved visibility without requiring them to operate the enterprise inventory system directly.
The example’s value lies in identifying what information operational decisions require and which systems should provide it.
Enterprise systems should remain authoritative for the records they are designed to maintain, while tactical applications should present information appropriate to their users. Any exchange between them would require suitable security, authorisation, data governance and technical arrangements.
The principal question is therefore not whether SAP should be replicated within a battlefield management system, but what logistics information commanders require and how it can be made available reliably.
Future ERP: An Opportunity to Consider Operational Logistics Integration
The relationship between enterprise logistics information and battlefield requirements matters now because the NZDF is preparing another transformation of its resource-management systems.
In September 2026, the NZDF issued an advance notice concerning its Future Enterprise Resource Planning (ERP) Programme, outlining plans for a more integrated enterprise-wide capability. The programme identifies SAP S/4HANA as the intended technology and includes systems integration, business integration and independent assurance among its major areas of work.[11]
Project Fusion sought to bring separate administrative and logistics functions into a common information environment. Future ERP provides an opportunity to examine how that environment should support Defence activities in the coming decades.
The procurement notice does not indicate that integration with SitaWare or support for autonomous logistics is within the programme’s scope, and Future ERP should not be assumed to provide them.
The more useful question is whether the operational information requirements associated with deployed logistics have been sufficiently identified to inform future enterprise-system design and related capability development.
Who is responsible for ensuring that the information requirements of deployed Army logistics are appropriately reflected across enterprise systems, tactical digital capabilities and future distribution technologies?
Different programmes, organisations, and funding arrangements are developing the capabilities involved. Without an agreed understanding of operational requirements, individual systems could meet their own objectives while leaving gaps in support for deployed forces.
DSSR, DSSD and Project Fusion all showed that successful technological change depends on aligning systems, procedures, responsibilities and the people who use them, not only on new software. Future ERP should therefore be seen within the wider evolution of Defence logistics, not merely as the replacement of an ageing enterprise application.
Digital Freight Management and the Movement of Supplies
The NZDF’s continuing digitisation of freight management provides another potential foundation for future distribution capabilities.
Freight management concerns a different aspect of logistics information from inventory accounting or tactical command. Its principal responsibilities include documenting consignments, identifying destinations, recording handling requirements and coordinating movement between locations.
Digital freight processes offer opportunities to reduce manual paperwork, improve the consistency of movement documentation and strengthen consignment visibility. These functions would remain relevant whether supplies were transported by conventional vehicles, aircraft, or autonomous platforms.
For autonomous distribution, particular attention would need to be given to consignment identification, the information required to task a transport resource and the means of confirming receipt. Standardised data and appropriate tracking arrangements could allow different transport platforms to operate within established movement-management procedures.
An autonomous vehicle would not, however, be automatically compatible with existing freight applications; any interface would need to be assessed for technical feasibility, operational requirements, security and organisational responsibility.
Movement control offers the precedent: as noted earlier, specialist movement organisations emerged because coordinating movement required skills and procedures distinct from operating the transport itself. The same distinction should inform the employment of autonomous distribution systems. Their introduction would expand available transport options without removing the need for effective movement coordination and accountability.
New Zealand’s Autonomous Systems Experimentation
New Zealand’s question is how to move from trial to integration. On 26 February 2026, the New Zealand Government announced that the NZDF would trial several unmanned systems supplied by New Zealand company Syos Aerospace, including the SG400 unmanned ground vehicle. The experimentation included potential applications involving supply movement, reconnaissance and other military tasks, alongside examining integration between unmanned technologies and existing Defence systems.[12]
A Syos Aerospace unmanned ground vehicle. In February 2026, the New Zealand Government announced that the NZDF would acquire and trial the company’s SG400 unmanned ground vehicle as part of an examination of potential military applications, including the movement of supplies. Photo: SYOS Aerospace
The value of these trials should not be judged solely by whether a vehicle can travel between two locations or carry a specified payload. A more meaningful logistics assessment would examine how effectively the equipment performs an assigned distribution task within established military procedures.
Such an assessment would consider tasking, load preparation, delivery, recovery and the personnel required to support the platform. It would also determine whether autonomous equipment offers measurable advantages in speed, safety, reliability, or personnel use.
Subsequent experimentation could introduce multiple destinations, competing priorities, difficult terrain, degraded communications and the presence of opposing unmanned systems.
The choice of transport resource should remain subordinate to the operational requirement. A small aerial system may suit an urgently required component, an unmanned ground vehicle a heavier local load, and conventional transport bulk supplies or longer distances. The aim should be to expand distribution options, not to replace established transport simply because a new technology is available.
Sustaining the Systems That Sustain the Army
Autonomous systems would create additional technical and organisational responsibilities. Unmanned ground vehicles and aerial platforms depend on batteries, motors, sensors, communications equipment, electronic components, and software that require maintenance and support.
Some components may be replaced rather than repaired, while others could require specialist facilities, diagnostic equipment, technical expertise or manufacturer assistance. These requirements raise questions about Army trades and the future responsibilities of the RNZALR.
Routine servicing might be undertaken by operators, while more complex repairs could fall to appropriately trained technicians. Software support, configuration management, component traceability and the recovery of damaged platforms would also need consideration.
For a comparatively small army, the support burden could become significant if limited fleets from several manufacturers required different spare parts, diagnostic tools, training arrangements and technical support.
The benefit of autonomy must therefore be assessed against the personnel and resources required to sustain it.
New Zealand Army logistics history provides repeated examples of technological improvements creating new trades, specialisations and support requirements. Motor transport, electronic equipment and computerised supply systems changed the nature of logistics work but did not eliminate the requirement for trained personnel. Autonomous technologies are likely to follow a similar pattern. The challenge for the RNZALR will be to determine how these systems can be sustained within an organisation already responsible for supporting an increasingly complex range of military equipment.
Operating in the Pacific and on a Contested Battlefield
Much contemporary discussion of autonomous logistics draws on developments in Ukraine and European military experimentation. However, the Pacific presents distinct challenges, including dispersed islands, steep terrain, heavy rainfall, limited road networks, restricted infrastructure and substantial distances between logistics locations.
A platform that performs effectively in a prepared training area may struggle on narrow island tracks or in heavily vegetated terrain. A small aerial system may be constrained by weather, endurance, payload and the availability of suitable launch or recovery locations.
Autonomous systems also introduce vulnerabilities related to communications, navigation, software, and electronic warfare. Jamming, spoofing, cyberattack or equipment failure may interrupt operations. Repeated movement along predictable routes could disclose the locations of supply points and supported units, while charging and maintenance facilities could become additional targets.
Logistics organisations must therefore be able to operate with degraded communications. Deployed personnel must retain the ability to identify requirements, manage local stock, coordinate essential movement and record deliveries when central systems are unavailable.
Locally retained information, predefined authorisations and procedures for reconciling transactions once communications are restored may provide useful resilience, although they introduce risks involving outdated records and duplicate demands.
The Army’s experience of extending computerised supply systems into the field in the 1980s is a useful parallel: technology improves access to information only so far as it remains reliable under field conditions. A future autonomous distribution system should enhance the resilience of Army logistics rather than create a dependence on uninterrupted digital connectivity.
Building the Next Stage of Army Logistics
Mechanised accounting, DSSR, Project Fusion and SAP each required changes to organisation, procedures and training, not just new equipment or software. Autonomous distribution will be no different. Three areas warrant attention as the NZDF develops its future logistics capabilities.
Understanding Existing Processes
First, establish how deployed logistics requirements are currently communicated, authorised, and fulfilled, including the systems and procedures involved. This would help identify manual interventions, existing interfaces and opportunities to improve the availability of operational information.
Defining Information Requirements
The second is to determine what information commanders and logisticians need from enterprise and tactical systems, and which organisations should maintain authoritative records. These requirements could inform Future ERP, Network Enabled Army and related capability planning.
Evaluating Complete Logistics Activities
The third is to assess autonomous distribution through realistic military logistics tasks rather than isolated demonstrations of vehicle performance. Trials should examine reliability, personnel requirements, maintenance, communications resilience and the effectiveness of the supporting procedures, as well as payload and mobility. Such assessments would help establish where autonomous technologies offer practical advantages over conventional arrangements.
For the RNZALR, the underlying challenge is familiar. Future technologies will introduce new methods and responsibilities, but their successful employment will still depend on coordinating supply, transport and maintenance.
Conclusion: Beyond the Last Tactical Mile
New Zealand military logistics history shows that adaptation has always been central to sustaining a relatively small force.
During the Waikato campaign, the Commissariat coordinated several transport methods across difficult terrain. A century later, expeditionary commitments encouraged the development of specialist movement-control and terminal capabilities. Mechanised and computerised supply accounting improved inventory management, while Project Fusion and the formation of the RNZALR brought previously separate logistics functions into more closely integrated systems and organisations. Each development reflected the military requirements and technological possibilities of its time.
Autonomous ground vehicles and drones now offer another opportunity to improve military distribution. Singapore’s Next Generation Infantry Battalion shows what deliberate integration of unmanned technologies into a military organisation looks like. New Zealand’s experimentation is the starting point for doing the same in its own operational circumstances.
The established SAP environment, Network Enabled Army and digital freight management provide foundations to build on. Future ERP is an opportunity to decide how enterprise information should support operational requirements.
As the RNZALR approaches its thirtieth anniversary in December 2026, it is worth recalling its origins. The regiment was created by bringing together supply, transport and maintenance functions that had become increasingly interdependent; autonomous technologies are another stage in that continuing evolution.
The technologies available to the Army will continue to change. The fundamental responsibility of military logistics will not: ensuring that the right resources reach the right place, at the right time, in a condition that allows the force to accomplish its mission.
The next major transformation in New Zealand Army logistics may therefore be defined not by the machines carrying supplies, but by the logistics system’s ability to connect the entire journey from demand to delivery.
That would be consistent with more than 160 years of adaptation in New Zealand military logistics.
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.
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).”
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.
In the popular telling of New Zealand’s military history, the country is often cast as a recipient of overseas innovation, dependent on British or Allied designs to meet its military needs. However, overlooked in the archives is the story of Charles Loomes, a Defence Stores official whose early 20th-century inventions demonstrated both ingenuity and a deep understanding of local operational conditions.
In 1910, as New Zealand established a modest domestic military manufacturing base—primarily focused on converting local wool into standard British-pattern uniforms—Loomes submitted two proposals to the War Office in London: one for a new entrenching tool and another for an improved infantry equipment system. Both designs were intended to enhance the practicality and comfort of New Zealand soldiers in the field.
Although his ideas were ultimately not adopted, Loomes’s efforts exemplify a quiet but essential tradition of military innovation in New Zealand—one that deserves far greater recognition.
A Life of Service and Practical Insight
Charles Loomes was born in 1857 in Whittlesey, England, and emigrated to New Zealand, where he entered public service. By the early 1900s, he was working with the New Zealand Defence Stores Department in Wellington, a precursor to today’s logistical branches of the NZDF. He was not a military commander or weapons engineer, but rather a public servant embedded in the practicalities of supply and equipment. His proximity to returning troops from the South African War (1899–1902) gave him rare insight into the shortcomings of British military kit in colonial conditions. This combination of technical competence and frontline empathy shaped his two major design proposals.
The Entrenching Tool: A Tool for the Dominion, Not the Empire
At a time when British military orthodoxy remained firmly anchored in European conditions, Charles Loomes’ 1910 entrenching tool design stood out as a locally informed innovation. New Zealand troops had just returned from the South African War, bringing lessons hard learned in the scrublands and semi-arid terrain—lessons not adequately reflected in British-issue tools. The shortcomings of the British entrenching tool were increasingly evident: it was heavy, ill-suited for bush work, and cumbersome in combat conditions that demanded speed, versatility, and improvisation.
Loomes, drawing upon feedback from returning veterans and his knowledge, designed a hybrid tool that merged the capabilities of a spade and a tomahawk. His model featured a shorter shaft for easier handling in confined environments and a reinforced blade capable of cutting through vegetation and lifting compact earth. He noted that the tool was designed to remove intact clumps of soil, making it ideal for quickly constructing makeshift sangars, foxholes, or low parapets. This capacity reflected an understanding of the semi-permanent, fast-moving trench systems standard in irregular warfare and mobile operations environments where New Zealand soldiers often found themselves.[1]
According to the 1910 Defence Council report, New Zealand was reforming its defence organisation in anticipation of Lord Kitchener’s review. This included transitioning to a field force more attuned to national conditions. Loomes’ proposal arrived at a critical moment—just as local military leaders and policymakers were beginning to contemplate how New Zealand’s needs might diverge from Britain’s. The fact that the War Office in London reviewed and formally responded to Loomes’ tool submission, thanking him and returning the sample, underscores the event’s rarity. Colonial submissions were often ignored or lost in bureaucracy; Loomes’ treatment was an outlier.
This modest response, while not leading to adoption, highlights the credibility of the proposal and its alignment with growing imperial awareness of environment-specific military needs. The reality, however, was stark: New Zealand had little indigenous arms production capability at the time, and the cost of tooling up to produce such implements locally was seen as prohibitive. The result was that practicality bowed to imperial standardisation.
Nonetheless, Loomes’ design prefigures later developments. As early as the Second World War, entrenching tools would again be reconceptualised for jungle, bush, and close terrain operations, validating Loomes’ insight.
Reimagining Load Carriage: A Soldier-Centred, Modular System
In December 1910, Loomes followed up with a second design submission: improved infantry and mounted infantry equipment to address the long-standing challenge of balancing soldier load, accessibility, and operational effectiveness. This system is compelling because of its technical design and thought, which were born from operational realities and adapted to New Zealand’s hybrid mounted-infantry character.
Loomes proposed a “heads and tails” ammunition pouch system capable of carrying 200 rounds of rifle ammunition—120 in the front, 80 in the rear. Unlike the British webbing designs of the time, which often created imbalance or restricted movement, Loomes’ design allowed soldiers to access ammunition from either end of each pouch. Rounds could be withdrawn in prone and standing positions without awkward adjustments. Once the front pouches were emptied, reserve pouches could be rotated forward, maintaining weight balance and ensuring the soldier remained combat-effective throughout prolonged engagements.[2]
This solution anticipated later 20th-century load-carrying principles—particularly modularity, distributed weight, and quick-access ammunition positioning. Loomes’ notes also specify that his design intentionally left the chest and upper arms unencumbered. This would have improved ventilation and mobility—vital in warm or uneven terrain—and eased firing in prone positions.
Just as important was the equipment’s versatility. Loomes’ harness could be configured for:
Light marching order (with minimal ammunition and essentials)
Full field service (including blanket, water bottle, greatcoat, and rations)
Mounted use (tailored to New Zealand’s mounted rifle units)
Loomes understood that mounted infantry—New Zealand’s dominant expeditionary force model at the time—required unobtrusive, stable, and balanced carriage. This was vital for the rider’s comfort and maintaining combat readiness while mounted. Unlike the clumsy Slade-Wallace or even early Mills webbing gear, which could interfere with movement on horseback, Loomes’ system was designed with the horse in mind.
His proposal was technically sound, cost-conscious, and straightforward to manufacture using leather or woven webbing. Though not accepted, the offer to supply working samples reflected his confidence in the design’s utility.
The Defence Reports of 1911 and 1912 offer valuable context here. The reorganisation of the New Zealand Military Forces was in full swing: the new Territorial system was replacing the old Volunteer model, a permanent instructional staff was being built, and procurement systems were beginning to prioritise local efficiency.[3] Yet, despite a growing awareness of the need for New Zealand-specific solutions, structural constraints—particularly reliance on British-standardised procurement—remained a barrier. The Quartermaster-General’s 1912 report notes that equipment tenders were focused on uniformity and scale, with mills’ pattern marching-order sets being bulk-ordered from the UK.[4]
In short, while Loomes’ system was conceptually ahead of its time, the institutional apparatus to support its adoption did not yet exist.
Innovation Ahead of Infrastructure
Though neither of Loomes’ designs entered service, their rejection reflected institutional inertia rather than any lack of merit. Britain retained tight control over military equipment standardisation, and New Zealand, then a Dominion with no significant defence manufacturing base, had little ability to produce its designs at scale. Loomes was ahead of his time: his submissions anticipated the kind of adaptations that would only become common decades later.
His submissions challenged the notion that innovation flowed from the metropole to the periphery. Loomes proved that original thought could emerge from within New Zealand’s institutions—even if the machinery to adopt it lagged.
A Precursor to Later Innovations: A Quiet Tradition of New Zealand Military Ingenuity
Charles Loomes was not alone in his efforts to design military equipment better suited to New Zealand’s conditions and constraints. While his 1910 submissions may be among the earliest formal proposals from within New Zealand’s defence establishment, they were by no means the last. His spirit of pragmatic, ground-up innovation reappeared throughout the 20th century in a series of unique, often overlooked, and sometimes extraordinary developments—each born of necessity, local ingenuity, and limited resources.
Among the most celebrated examples of New Zealand military innovation was the Roberts Travelling Kitchen, developed on the eve of the First World War by Captain W.G. Roberts of the New Zealand Army Service Corps. Designed in direct response to the challenges of feeding troops in dispersed, mobile operations, the Roberts Kitchen was a self-contained, horse-drawn field kitchen capable of preparing hot meals under austere and constantly shifting field conditions. Constructed with a robust metal chassis and mounted stoves, it could boil water, cook stews, or heat rations while on the move or in static positions without requiring a fixed base of operations. Its compact and modular layout allowed it to be easily deployed by small support teams, providing a dependable solution at a time when maintaining nutrition and morale was often as critical to battlefield effectiveness as ammunition and arms.
What set the Roberts Kitchen apart was not just its portability, but its simplicity, durability, and adaptability—qualities that earned it significant praise both within New Zealand and abroad. It was exported to Australia and trialled by the Australian Army, where it was quickly recognised for its practicality and efficiency. In theatres where standard British Army cookhouses were too bulky or unsuitable for forward areas, the Roberts Kitchen filled a critical gap. It supported mobile columns and supply echelons across difficult terrain and under variable weather, making it ideal for forces operating far from fixed infrastructure. Though mechanised and industrially mass-produced wartime kitchens would later overshadow it, the Roberts Travelling Kitchen stands as a pioneering achievement that anticipated modern mobile field catering and embodied the soldier-centred ethos of New Zealand’s approach to military logistics.[5]
Roberts 2a Oven (Travelling) for 250 Men. Archives New Zealand R22432833 Cookers – Field- Roberts travelling
Then came the New Zealand Battle Ration, one of the most straightforward and most successful examples of locally designed and manufactured military innovation explicitly tailored to the needs of New Zealand troops. Developed during the Second World War, the Battle Ration emerged in response to a growing awareness that the ration packs issued by Britain and the United States were ill-suited to the operational conditions of the Pacific theatre, where New Zealand soldiers were increasingly deployed.
New Zealand forces faced extreme humidity, dense jungle environments, and logistical constraints during campaigns in the Solomon Islands, New Caledonia, and other island chains. Standard British rations—often based on tinned meats, hard biscuits, and fatty components—were prone to spoilage, hard to digest in hot climates, and culturally misaligned with New Zealanders’ eating habits. Similarly, early U.S. C-Rations were heavy and included items with unfamiliar or unpalatable flavours. Soldiers frequently discarded parts of these rations, resulting in unnecessary waste and reduced nutritional intake.
In contrast, the New Zealand Battle Ration was designed from the ground up with science, environment, and soldier morale in mind. Drawing on nutritional research and advice from local food technologists and military dieticians, the ration incorporated lightweight, dehydrated components that could be quickly reconstituted with water. This made the ration more portable and shelf-stable and reduced the bulk of what troops had to carry on long patrols or amphibious movements.
Typical components included:
Compressed or dehydrated vegetables, often in powder or cube form;
High-calorie itemssuch as chocolate, sweetened condensed milk powder, and dried fruit;
New Zealand-produced biscuitsformulated to remain edible in heat and humidity;
Beef extract or bouillon tablets, providing both flavour and salts for hydration;
Tea and sugar, consistent with New Zealand soldiers’ dietary and morale preferences.
The result was a compact, nutritionally complete, and culturally familiar ration pack that troops could rely on. Its ease of carriage and reduced spoilage rates made it ideal for small-unit operations, reconnaissance patrols, and units cut off from resupply in remote jungle areas.
The Battle Ration was also locally produced, reducing dependency on vulnerable international supply chains. New Zealand manufacturers, working with the Defence Department and scientific institutions, were able to source, process, and package the components within the country. This had the dual benefit of supporting the national economy during wartime and ensuring higher quality control for frontline provisioning.
The Battle Rations’ success did not go unnoticed. It earned positive recognition from allied observers, particularly American nutritionists and quartermasters who saw in it a viable model for regional adaptation. In some cases, its components were studied as part of broader Allied efforts to improve ration systems in the Pacific, and small-scale adoption of similar food technologies followed.
More than a stopgap solution, the New Zealand Battle Ration represented a fully integrated, homegrown logistical system that placed the soldier’s lived experience at the centre of its design. It remains a landmark example of how a small nation, facing unique environmental and operational challenges, could outpace its larger allies in terms of applied military food science and practical innovation.[6]
But New Zealand’s ingenuity extended beyond food and field comforts.
In 1941, as global supply chains strained and frontline weapons were scarce, Philip Charlton devised the Charlton Automatic Rifle—a fully automatic conversion of obsolete bolt-action Lee–Metford and Lee–Enfield rifles. Intended as a stopgap substitute for the unavailable Bren and Lewis light machine guns, the Charlton was produced primarily for the New Zealand Home Guard. Its rugged construction, semi-automatic default operation, forward pistol grip and bipod (in the New Zealand model) made it an effective emergency solution.[7] Around 1,500 were produced; today, surviving examples are exceedingly rare, but they remain a testament to New Zealand’s wartime adaptation amid global resource shortages.
Charlton Automatic Rifle. 1941, New Zealand, by Charlton Motor Workshops. Gift of Mr Philip Charlton, 1965. CC BY-NC-ND 4.0. Te Papa (DM000451/1-3)
Less successful, but no less revealing, was the Mitchell Machine Carbine, a prototype submachine gun developed by New Zealander Allen Mitchell and submitted for testing in Britain in 1943. Though ultimately rejected due to faults in the trigger mechanism, stock, and excessive barrel heating, the weapon represented an attempt to produce a cost-effective domestic submachine gun using local materials and simple blowback operation. A second, improved prototype was submitted in 1944 but was again declined. Only four Mitchell SMGs were ever built; all remain in New Zealand collections. Despite its flaws, the project underscored the determination to establish a sovereign capacity for weapons development, however limited.[8]
Perhaps the most striking and tragic example of New Zealand’s wartime ingenuity is the story of Colonel John Owen Kelsey and the Kelsey Swivel-Stock Rifle. Drawing from his extensive service as an ordnance and engineering officer during the Second World War, Kelsey developed a novel modification of the Sten submachine gun in the early 1950s. Rather than attempting a curved barrel like the German Krummlauf, Kelsey’s design allowed the weapon to be fired around corners via a swivel-stock and periscopic sight, enabling an operator to shoot while remaining in cover. The concept was tested successfully at Waiouru and forwarded to the War Office in London.[9]
Shooting around a corner from cover with he experimental Mk5 Sten “Swivel Butt Carbiner”. Courtesy MoD Pattern Room Library
Kelsey believed the design could be adapted to other weapons and took out international patents. However, he received no further response, and amid growing personal hardship, he died by suicide in 1954.[10] Though the design never progressed beyond a prototype, it serves as a sobering reminder of the often-overlooked costs of service and the post-war fate of veterans whose talents went underutilised.
Perhaps the most unusual case in New Zealand’s military innovation archive is that of Victor Penny, an Auckland bus mechanic and amateur radio enthusiast who, in the years before the Second World War, persuaded defence authorities that he could build a “death ray” capable of disabling enemy vehicles, aircraft, and electronics. Penny’s device, reportedly a directed electromagnetic energy weapon, earned him state support and near-total secrecy. He was relocated to Somes Island in Wellington Harbour—used during the war as an internment and quarantine facility—where a laboratory was constructed solely for his use. Though the project yielded no proven battlefield capability, it remains an intriguing episode in the country’s history of experimental defence projects and an indicator of how seriously New Zealand’s government once considered homegrown science and technology, even of the most speculative kind.[11]
Radio enthusiast Victor Penny was kept under guard on Matiu Somes Island in Wellington Harbour in 1935 as he worked on his mysterious invention.FILE / Dominion-Post
An Innovation Ethos Born of Need
What binds together the remarkable and diverse stories of Charles Loomes’ entrenching tool and load-carrying equipment, the Roberts Travelling Kitchen, the New Zealand Battle Ration, the Charlton automatic rifle, the Mitchell submachine gun, Victor Penny’s speculative “death ray,” and Colonel Kelsey’s swivel-stock rifle is not institutional power, budgetary scale, or industrial might. Instead, they emerged from a humbler yet uniquely resilient source: necessity—the mother of invention in a small, geographically isolated nation.
These were not the products of a formal military-industrial complex. They came from soldiers, field engineers, ordnance officers, public servants, hobbyists, and workshop innovators. Each worked from within or alongside New Zealand’s military system, often without formal research backing, institutional commissions, or manufacturing infrastructure. They responded to pressing operational needs, adapting or reinventing equipment that didn’t suit the environment or realities faced by New Zealand troops—whether in the South African veldt, the Italian alleys of WWII, the Pacific or the cold training grounds of Waiouru.
Despite the quality and relevance of these designs, many were either dismissed by imperial authorities or faded from memory in the post-war era, overshadowed by the need to adhere to British and later American standardisation. Yet many were contextually brilliant. The Roberts Kitchen and Battle Ration were internationally recognised. The Charlton rifle filled a vital gap in local defence. Kelsey’s adapted Sten gun may not have been adopted, but it represented forward-thinking soldier survivability in urban combat. Even Victor Penny’s electromagnetic weapon, though more speculative, illustrates the willingness of New Zealand’s authorities to explore radical ideas when the stakes were high.
Together, these stories reflect a recurring national pattern: when strategic isolation, global conflict, or supply chain fragility forced New Zealand to look inward, the country proved more than capable of producing its answers. Innovation in New Zealand has historically been less about prestige and more about practicality—a can-do, field-driven ingenuity that quietly delivered effective solutions under adverse conditions.
Charles Loomes, then, should not be seen as a lone innovator ahead of his time, but rather as the first in a long and under-recognised lineage. This lineage stretches from the trenches of South Africa and Gallipoli, through the fields of Italy, and into workshops, depots, and paddocks across the country. These innovators turned limitations into opportunities and ensured New Zealand could solve its military problems independently despite its small population and modest resources.
The legacy of this ethos remains deeply relevant today. New Zealand’s past offers historical insight and a blueprint for future resilience as the global security environment becomes more uncertain and supply chains more contested.
Notes
[1]From: Charles Loomes, Defence Stores Date: 1 August 1910 Subject: Entrenching tool invented by himself, asks that it be forwarded to Imperial, Archives New Zealand Item ID R24759083, (Wellington: New Zealand Archives, 1910).
[2]Charles Loomes, Wellington Date: 24 December 1910 Subject: Improved Equipment for use of Infantry and Mounted Infantry, Archives New Zealand Item ID R24759941, (Wellington: New Zealand Archives, 1910).
[3] “H-19 Defence Forces of New Zealand: Report of the General Officer Commanding the Forces for the period from 7th December 1910 to 27th July 1911,” Appendix to the Journals of the House of Representatives (1 January 1911), https://paperspast.natlib.govt.nz/parliamentary/AJHR1911-I.2.4.2.30.
[4] “Defence Forces of New Zealand: Report of the General Officer Commanding the Forces for the period 28 July 1911 to 27th June 1912,” Appendix to the Journals of the House of Representatives, 1912 Session II, H-19 (27 June 1912), https://paperspast.natlib.govt.nz/parliamentary/AJHR1912-II.2.4.2.37.
[5] “Cookers – Field- Roberts travelling,” Archives New Zealand Item No R22432833 (1915).
[6] “DSIR [Department of Scientific and Industrial Research] World War 2 Narratives. No. 10. Dehydrated Foods and Ration Packs. Copy No. 1,” Archives New Zealand Item No R1768268 (1948).
[11] D. Downs and J. Bridges, No. 8 Re-wired: 202 New Zealand Inventions That Changed the World: 202 New Zealand Inventions That Changed the World (Penguin Random House New Zealand, 2014).
As 12 May 2025 marks the 115th anniversary of the New Zealand Army Service Corps (NZASC), it is fitting to reflect on the pioneering figures who laid its foundations and shaped New Zealand’s military logistics capability. Although New Zealand had established military logistics organisations as early as 1862, the formation of the NZASC in 1910 represented the first uniformed logistics branch within the New Zealand military, laying the groundwork for a more structured and professional approach to sustainment and support. This foundational move was later followed by the creation of the New Zealand Army Ordnance Corps (NZAOC) in 1917 and the New Zealand Electrical and Mechanical Engineers (NZEME) in 1942, further expanding and diversifying the nation’s military logistics capabilities.
Originally published in the July 2024 issue of the New Zealand Journal of Military History, this article explores the life and enduring legacy of Brigadier General Henry Owen Knox. It traces his journey from the ranks of the British Army to his critical role in the early development of the NZASC, highlighting his pivotal leadership in reorganising and modernising New Zealand’s military logistics. Knox’s contributions provided a lasting legacy that continues to influence the structure and effectiveness of the Royal New Zealand Army Logistic Regiment (RNZALR) today.
Brigadier General Henry Owen Knox: The Architect of New Zealand Military Logistics and the Formation of the NZASC
The inception of the Royal New Zealand Army Logistic Regiment (RNZALR) in 1996 serves as a testament to the visionary decisions made in 1909, a pivotal moment when the New Zealand Military underwent a comprehensive reorganisation and reequipping initiative under the guidance of Major General Alexander Godley. The primary objective was to elevate the New Zealand Military into a capable, modern force ready to contribute to a broader Imperial defence scheme.
Brigadier General Henry Owen Knox: The Architect of New Zealand Military Logistics and the Formation of the NZASC
Major Henry Owen Knox emerged as a central figure in this transformative journey, leaving an indelible mark on the logistics landscape of the New Zealand Army. Serving under the leadership of Godley, Knox, in collaboration with a cadre of seconded imperial officers, elevated New Zealand’s military capabilities to align with those of the United Kingdom, Australia and Canada. Major Knox’s noteworthy contributions include the establishment of the New Zealand Army Service Corps (NZASC), aligning it with the latest British military logistics innovations.
This article explores the life and enduring legacy of Knox, an esteemed military figure whose unwavering commitment to service and leadership left an indelible mark on the British, Indian, and New Zealand Armies. Knox’s remarkable journey unfolded amidst a dynamic world, spanning continents and pivotal historical periods. His significant contribution in laying the foundations of the NZASC initiated a series of transformative changes, shifting New Zealand Military Logistics from a static to an operational model. This operational framework proved crucial in sustaining New Zealand’s Forces throughout the conflicts of the 20th century, ultimately culminating in the establishment of the Royal New Zealand Army Logistic Regiment (RNZALR). Major Knox’s enduring impact on New Zealand’s military logistics history is firmly solidified through these historical developments.
Henry Owen Knox, born on 16 January 1874 in Lambeth, Surrey, was the eldest son of the Rt Hon Ralph Knox, later Sir Ralph Knox KCB, who served as the Permanent Under-Secretary of State for War from 1897 to 1901, and Georgina Augustus Chance. Educated at Dulwich, Knox commenced his military journey by being commissioned as Second Lieutenant in the 4th Battalion South Staffordshire Regiment on 8 April 1893.
Transitioning to the Army Service Corps (ASC) as a Probationary Second Lieutenant from the South Staffordshire Regiment in 1896, Knox’s career saw swift advancements, with promotion to Lieutenant on 21 October 1897. While stationed at the ASC’s Portsmouth’s Colewort Barracks, he married Muriel Lucy Roberts, the daughter of Sir Owen Roberts, at London Paddington’s Christ Church on 6 July 1899.
Knox’s commitment extended to the South African War, where he earned promotions and commendations, achieving the rank of captain on 1 January 1901 and receiving the Queen’s South Africa Medal with four clasps on 1 September 1901. His journey led him to the Indian Supply and Transport Corps, where, in 1903, he assumed the role of officer in charge of supplies at Rawul Pindee, now Rawalpindi, Pakistan, often likened to the Aldershot of India. Accompanied by his wife, Knox welcomed the birth of their first son, Ralph Peter Owen Knox, on 5 August 1903.
Returning to the United Kingdom in 1907 after completing his five-year term in India, Knox resumed duties as a peacetime ASC officer. However, amidst what should have been a joyous period, tragedy struck with the birth of his second son, Henry Owen Murray Knox on 5 March 1909, followed by the untimely passing of Knox’s wife the next day. Despite this heart-wrenching loss, Knox found solace in a new chapter of his life, remarrying Elsie Caroline Harker on 28 May 1910.
New Zealand
After the conclusion of the South African War, the Military Forces in New Zealand embarked on a series of reforms to enhance the organisation and capability of the nation’s military, enabling it to contribute effectively to a broader Imperial Defence scheme. In 1910, at the request of the New Zealand Government, Field Marshal Viscount Kitchener inspected New Zealand’s Forces. Kitchener provided several recommendations concerning the ongoing reforms, emphasising the need for a professional Staff Corps to administer the force.
The momentum for these reforms gained further impetus with the appointment of Major General Alexander Godley as the New Zealand Military Forces Commandant in December 1910. Godley was pivotal in revitalising New Zealand’s military organisational framework in his first year, making critical command and staff appointments, promulgating the (Provisional) Regulations for the Military Forces of New Zealand, and making plans to build up the NZASC, which, although gazetted on 12 May 1910 as a designated component of the Defence Forces of New Zealand, remained a paper corps.[1]
The proposed NZASC envisaged eight Transport and Supply Columns, comprising four Mounted Brigade and four Mixed Brigade Transport and Supply Columns, one of each earmarked for allocation to one of New Zealand’s four Military Districts. Despite the existence of the Defence Stores Department, which had fulfilled commissariat functions in New Zealand since 1869, there was a lack of an ASC nucleus from which these new units could evolve.
Acknowledging the highly specialised nature of ASC duties, distinct from combatant staff and regimental officers, and the absence of suitably qualified officers in New Zealand, Godley recommended to the Minister of Defence on 4 January 1911 the lending of services of an experienced Imperial ASC Senior Captain or Major to organise and train New Zealand’s transport and supply services for three years. The Minister of Defence endorsed this recommendation with the Prime Minister cabling the New Zealand High Commissioner in London on 10 January 1910 to approach the Army Council for the:
Services of experienced Army Service Corps major or senior captain required to organise New Zealand Army Service Corps. Engagement for three years. Salary £600 a year consolidated. Pay to include house allowance. Travelling allowance of 12/6d a day and allowance for one horse if kept, will also be granted. [2]
Within two months of receiving New Zealand’s request for an ASC Officer, the Army Council promptly and affirmatively responded to the call. Having already sanctioned nine additional officers to assist Godley, the Council selected Knox, then serving in C (Depot) Company ASC at Aldershot, for service in New Zealand to organise the NZASC. New Zealand agreed to cover the costs of Knox’s secondment, encompassing first-class travel and accommodation for his family. Despite this, Knox, with a desire for a nurse for his children and a motorcar as part of his household, accepted the responsibility for these supplementary expenses. Anticipating the scale of the work required, Knox approached the New Zealand High Commissioner and requested that an ASC Clerk accompany him to assist with the upcoming tasks. However, the New Zealand High Commissioner declined this request. Bestowed with the rank of Temporary Major during his tenure as the Director of Supplies and Transport (DST), New Zealand Forces, Knox departed London with his family, nurse and a motorcar on 13 April 1911 aboard the SS Turakina, arriving in Wellington on 31 May 1911.
Under the guidance of New Zealand Adjutant and Quartermaster-General Colonel Alfred Robin, Knox assumed his duties as the New Zealand DST at the Army General Staff Offices on Wellington’s Buckle Street. His responsibilities encompassed a wide range of functions, including quarters, tender and contracts, personal and freight movement, and presidency on two standing committees related to Drill sheds and the storage and distribution of clothing and equipment to the forces.[3]
Recognising Knox’s extensive duties, he was granted the Temporary Rank of Lieutenant Colonel on 6 September 1911. With Colonel Robin’s appointment as the New Zealand representative at the War Office in London in 1912, Knox assumed the additional role of Quartermaster General (QMG).[4] Despite Knox diligently fulfilling the role of QMG and DST, progress on the formation of the NZASC was slow.
During his tenure as QMG and DST, Knox maintained a functional and collegial relationship with the New Zealand Director of Equipment and Ordnance Stores (DEOS) and head of the Defence Stores Department, Major H. James O’Sullivan. Unlike Knox, O’Sullivan was not an imported Imperial Officer but a long-serving member of the New Zealand Defence Department who had progressed through the ranks from Armed Constabulary Trooper to DEOS. It is assumed that O’Sullivan offered Knox valuable advice on the New Zealand approach to various matters.
Despite Knox’s initial request for an ASC clerk being declined, in September 1912, Knox approached Godley, suggesting the enhancement of the NZASC formation by sending four New Zealand Warrant Officers to England for training or seconding four ASC Warrant Officers to the New Zealand Forces. The latter option was accepted, and four ASC Senior Non-Commissioned Officers (SNCOs) were chosen and dispatched to New Zealand in time for the 1913 Easter camps. [5] These camps were acclaimed as the most administratively and economically successful thanks to Knox and his four ASC NCOs.
With an additional four ASC officers approved for secondment arriving in New Zealand in February 1914, Knox, having completed twenty years of service and with his three-year secondment nearing its end, began preparations for his return to the United Kingdom in June 1913.
By 1914, Knox had established 16 NZASC companies of approximately 30 men each across the four New Zealand Military Districts, with the new ASC officers serving as Assistant Directors of Supply and Transport (ADST) in each District Headquarters. [6] Although Knox had departed by the time of the 1914 divisional camps, the Inspector General of Imperial Forces, General Sir Ian Hamilton, noted following his inspection that:
The very highest credit is due to the Army Service Corps officers and their men. They have done a first-class service, although as a rule undermanned to an extent that would fill a labor union with horror. When the Army Service Corps units are up to their normal strengths, a suitable system of calling the men up to camp in relays will enable the necessary duties to be carried out as efficiently and with much less strain on the personnel.[7]
Upon departing New Zealand on 13 February 1914, concluding his three-year tour of duty, Knox left behind an uncertain legacy. Possibly due to his commitment as Quartermaster General, Knox had not significantly improved the staffing levels of the NZASC. However, he had laid a framework for improvement, passing the leadership and future growth of the NZASC to the cadre of ASC Officers and NCOs who prepared the NZASC for the challenges of the 1914-18 war. The NZASC emerged from the war with an exemplary record of service.
Knox left New Zealand with a testimonial from New Zealand’s Governor General, acknowledging his “entire satisfaction in the execution of his duties as Quartermaster General and done valuable work during the time that he has been employed by the New Zealand government.”[8]
War Service
After returning home to the United Kingdom via the United States and taking a brief leave of absence, Knox officially retired from the British Army with the rank of Major on 22 July 1914. However, the United Kingdom’s declaration of war upon Germany on 4 August 1914 prompted Knox’s recall to the colours. He was appointed to command the British Expeditionary Force (BEF) Advance Base Depot, to be stationed at Le Havre, France, where he would achieve the lasting honour of being the first soldier of the BEF to set foot in France.[9]
Departing from Newhaven on the SS Brighton at 2 pm on 9 August 1914, Knox, accompanied by five Officers and 13 Other Ranks of ASC Depot of Supply unit No 14, arrived off Boulogne at 6:15 am on 10 August Faced with the absence of a pilot and uncertainty about their identity, the SS Brighton’s Captain, who had never entered that harbour before, was assisted by Knox’s 2IC, Captain C.E. Terry, an enthusiastic yachtsman familiar with the landmarks.[10] As later recalled by Lieutenant (QM) C. Bagg in 1940, as soon as the SS Brighton was tied up, Knox swiftly disembarked, heading for unknown destinations, making him the first British soldier of the BEF to set foot onshore in France.[11]
Knox continued his service in France until he was invalided to England on 1 December 1914 due to bronchitis. Following a swift recovery, Knox then deployed to Egypt. On 4 January 1914, he was appointed to the General Staff as AQMG (Assistant Quartermaster General) to the Australian and New Zealand (ANZAC) Corps. Knox undoubtedly resumed and utilised the many connections he had established during his three years in New Zealand.
Gazetted as a Temporary Lieutenant Colonel on 1 February 1915, Knox retained the position of ANZAC Corps AQMG throughout the ill-fated operations on Gallipoli. Despite being wounded in action on 11 August, he remained present during the evacuation. Mentioned in Dispatches twice, Knox was awarded the Most Distinguished Order of Saint Michael and Saint George Third Class (CMG) on 8 November 1915.
Gallipoli Peninsula, Turkey. c May 1915. An officer, believed to be Colonel H. O. Knox sitting outside two dugouts smoking a cigarette. The dugout on the right belongs to the Assistant Quartermaster General. AWM P02648.002.
Following a stint on the staff of General Headquarters (GHQ) Home Forces, Knox was dispatched to Mesopotamia on 18 August 1916 as the DQMG (Deputy Quartermaster General) with the rank of Temporary Brigadier General of the Mesopotamian Relief Force. This force successfully recaptured Kut and captured Baghdad. Knox received mention twice in dispatches and was appointed as an additional Companion to the Most Eminent Order of the Indian Empire (CIE) on 25 August 1917. On 13 November 1917, Knox was promoted to Lieutenant Colonel in the Regular Army with the Honorary Rank of Brigadier General.
Postwar
Upon Knox’s return home in 1918, he joined the Civil Engineer-in-Chief’s department at the Admiralty. He represented the department on the Naval Inter-Allied Commission, overseeing the dismantling of fortifications on Heligoland.
In recognition of his services during the war, Knox was appointed to the Most Excellent Order of the British Empire (CBE) on 17 October 1919.
Knox experienced another joyous occasion with the birth of a daughter on 23 June 1921. Returning to the retired list as a Colonel (Honorary Brigadier General) on 1 March 1922, limited information about Knox’s post-war life is available. On 16 January 1929, having reached the age limit exempting him from recall, he ceased to belong to the Reserve of Officers.
On 5 May 1955, at a nursing home in Tonbridge, Kent, England, Knox passed away at the age of 81.[12]
Conclusion
In conclusion, Brigadier General Henry Owen Knox is an influential architect of transformation in New Zealand military logistics, leaving an enduring legacy that shaped the evolution of the RNZALR. His journey, spanning continents and crucial historical periods, reflects a life dedicated to unwavering service and leadership across the British, Indian, and New Zealand Armies.
Knox’s crucial involvement in forming the NZASC amid extensive military reorganisation highlights his visionary contributions. Despite enduring personal tragedies, including the untimely loss of his wife, Knox’s resilience solidified his unwavering commitment to service. His leadership in New Zealand from 1911 to 1914 was central in shaping the NZASC and aligning it with cutting-edge British military logistics innovations. Despite initial challenges and a gradual beginning, Knox’s dedication and collaboration with local and imperial officers ultimately resulted in the successful establishment of the NZASC.
Knox’s return to active duty during World War I showcased his continued commitment, where he played a crucial role in the BEF as the ANZAC Corps AQMG at Gallipoli and later as DQMS in Mesopotamia, his services recognised with numerous commendations, including the CMG, CIE and CBE.
[1] Based on the British logistics system the NZASC was to be responsible for the Transport and the supply of forage, rations and fuel. The supply and maintenance of all small-arms, ammunition, accoutrements, clothing, and field equipment Stores was to remain a responsibility of the Defence Stores Department which in 1917 became the New Zealand Army Ordnance Corps. Robert McKie, “Unappreciated duty: the forgotten contribution of New Zealand’s Defence Stores Department in mobilising the New Zealand Expeditionary Force in 1914: a thesis presented in partial fulfilment of the requirements for the degree of Master of Arts in History at Massey University, Manawatu, New Zealand” (Massey University, 2022).
[2] “Henry Owen Knox – Major, New Zealand Staff Corps [Army Service Corps] “, Archives New Zealand – R22203157 (Wellington) 1911.
[3] 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, 1997), 44.
[4] The Quartermaster-General was the appointment responsible in the British Army of the early 20th century for those activities, which provided support to combat forces in the fields of administration and logistics. In the 21st Century these activities are described as Combat Service Support (CSS) and comprise Logistic Support, Equipment Support, Medical Support, Administrative Support and Logistic Engineering. In Hierarchical terms a Quartermaster General (QMG) was placed at the Army level, A Deputy Quartermaster General (DQMG) at Corps with Assistant Quartermaster General (AQMG) supporting both QMG and DQMG. Clem Maginniss, An unappreciated field of Endeavour Logistics and the British Expeditionary Force on the Western Front 1914-1918 (Helion, 2018), xxiii.
[5] The ASC SNCOs were; Quartermaster Sergeant John Wass and Staff Sergeant Major John Walter Frederick Cahill from the Horse Transport Branch and Staff Quartermaster Sergeant Philip Petty and Staff Sergeant Frank Ostler of the Supply Branch. Millen, Salute to service: a history of the Royal New Zealand Corps of Transport and its predecessors, 1860-1996, 45-46.
[6] The ASC Officers that arrive in 1914 were; Captain Norman Chivas Hamilton, Captain Annesley Craven Robinson, Lieutenant Hubert Harvard Wright and Captain Hector Gowans Reid. Millen, Salute to service: a history of the Royal New Zealand Corps of Transport and its predecessors, 1860-1996, 48.
[8] “Henry Owen Knox – Major, New Zealand Staff Corps [Army Service Corps] “.
[9] According to the Entente Cordiale, the United Kingdom had a diplomatic agreement with France to jointly address potential military aggression from the German Empire in Europe. In anticipation of a conflict between the UK and Germany, comprehensive plans were formulated for the British Army to send a “British Expeditionary Force” to France. This force would initially comprise of six infantry divisions and five cavalry brigades with the main body disembarking in France from 13 August 1914.
[10] C.E Terry, “The Britannia Monument,” RASC Journal, September, 1938.
[11] C. Bagg, “Correspondence ” RASC Journal, January, 1941.
“Wars are won by logistics.” – General Omar Bradley, United States Army
Lightsabers and Supply Chains
Every saga needs heroes. In the Star Wars universe, our gaze is drawn to the Jedi’s calm resolve, the roar of X-Wings in formation, and the clash of empires in the stars. But behind every act of heroism lies a less glamorous, often invisible force—logistics. Whether it’s fuelling starfighters, feeding battalions, or evacuating casualties under fire, logistics is the backbone of every conflict in the galaxy.
This reality mirrors our own. Logistics has always underwritten armies ‘ success from ancient campaigns to modern joint operations. Star Wars, while fantastical, often reflects the unspoken truth of warfare: that victory depends not just on courage and firepower but also on the capacity to sustain the fight.
Galactic Warfare Demands Galactic Logistics
Star Wars operates on a staggering scale. Fleets traverse parsecs in seconds. Planetary invasions occur with blitzkrieg speed. Yet such operations imply a logistical tail that’s as complex as it is colossal.
Star Destroyers the size of cities require fuel, oxygen, food, and spare parts.
Stormtrooper legions need rations, ammunition, transport, and medical support.
Rebel bases operate in secrecy but still need to power life support, fabricate equipment, and plan for evacuation.
Without the effort of countless anonymous logisticians—pilots, engineers, technicians, clerks, and droids—the machinery of war grinds to a halt. The unsung heroes of Star Wars are not only those who fly or fight, but those who fix, move, and sustain.
The Empire: Industrial Efficiency and Fragile Overreach
The Galactic Empire reflects the classic paradigm of a centralised military machine—impressive in might, but vulnerable in complexity. Its logistics system is massive, standardised, and heavily dependent on control of infrastructure.
Centralised Production: Planets like Kuat, Fondor, and Corellia are naval shipyards, constructing capital ships on assembly lines.
Fleet Supply Chains: Star Destroyers often act as autonomous bases, capable of deploying TIE squadrons, supporting troops, and conducting repairs. Yet they still rely on regular resupply convoys, garrison worlds, and fuel stations.
Clone and Conscription Models: The transition from the clone army to a conscripted stormtrooper corps signals a shift from precision to scale. Training, equipping, and deploying millions requires standardised logistics, but at the cost of adaptability.
Ultimately, the Empire’s strength is also its weakness. Like any overstretched power, it struggles with local unrest, regional shortages, and bureaucratic inflexibility. The Death Star—icon of ultimate control—was a logistical black hole, requiring vast resources to build, man, and maintain. Its destruction at Yavin wasn’t just symbolic—it devastated Imperial supply planning and morale.
The Rebellion: Logistics by Necessity
The Rebel Alliance, by contrast, is a textbook case in asymmetric logistics. Operating with limited resources, it employs decentralised, improvised, and resilient methods to survive and strike back.
Patchwork Fleets: Rebel ships are a mix of old models, captured craft, and converted civilian freighters. Their maintenance depends on scavenging, skilled technicians, and a culture of adaptability.
Mobile Bases: From Dantooine to Hoth, rebel headquarters are short-term, self-contained hubs. They must be defensible, resource-accessible, and easily evacuated.
Underground Supply Networks: Smugglers, sympathetic systems, and covert contractors serve as lifelines. Think of it as a galaxy-wide version of the WWII French Resistance’s logistics web.
These constraints breed innovation. At Scarif, rebel logisticians coordinate a high-risk infiltration to secure the Death Star plans. At Endor, limited forces are supported by maximum terrain exploitation. The Rebellion’s logistical doctrine is fluid, mission-specific, and centred on sustaining morale and momentum over material supremacy.
Case Study: The Battle of Hoth
The Rebel base on Hoth provides a rich example of the interplay between logistics, terrain, and combat.
Environmental Adaptation: The extreme cold forces unique solutions, such as thermal regulation, environmental suits, and animal transport (tauntauns) due to droid freezing.
Sustainment: Every supply item had to be brought in by smuggling freighters. Food, fuel, spare parts, and medical supplies were constantly in short supply.
Evacuation Planning: Using GR-75 transports with fighter escorts, the escape plan exemplifies prioritised withdrawal under duress—a classic logistician’s challenge.
Hoth is a triumph of ingenuity but also a reminder of risk. Without enough time or redundancy, even the best-laid logistical plans can be scuppered by surprise, attrition, or weather.
Droid Labour and Supply Chain Automation
Droid labour is one of the most understated but powerful assets in the Star Wars universe. Logistics droids serve in roles from inventory control and loading to starship maintenance and medical triage.
MSE-6 Mouse Droids scurry about starships with repair orders or encrypted data.
Gonk Droids serve as portable power units, sustaining machinery in remote environments.
Protocol and Astromech Droids assist with translation, navigation, and tactical computing—functions akin to modern command support tools.
This automation enables leaner human footprints, faster operations, and reduced fatigue. In modern military terms, this parallels using autonomous vehicles, digital inventory systems, and AI-powered logistics forecasting.
The Clone Wars: Large-Scale Conventional Logistics
During the Clone Wars, the Grand Army of the Republic represents conventional logistics on a galaxy-wide scale. Its campaigns mirror real-world total war scenarios, such as WWII or Cold War-era NATO doctrine.
Standardisation: Clones used the same kit, flew standardised craft, and operated under unified command. This enabled predictability in supply, training, and repairs.
Integrated Support: Republic naval forces functioned as mobile forward operating bases. Venator-class Star Destroyers provided logistics, medical aid, and reinforcements.
Contract Manufacturing: Systems like Kamino and Geonosis provided clone soldiers and droid enemies on industrial scales, raising ethical supply chains and issues of military-industrial dependence.
One aspect that is often overlooked is the role of medical and recovery operations. Scenes of med stations, bacta tanks, and casualty evacuation by LAATs reveal the vital role of health services in sustained operations.
Strategic Vulnerabilities: Logistics as a Target
Throughout Star Wars, we witness the targeting of logistics as a strategic priority:
Rogue One’s mission to steal the Death Star plans was a classic case of logistics intelligence gathering.
The Rebel assault on the Death Star’s exhaust port targeted a vulnerability in systems design.
In The Last Jedi, the First Order’s hyperspace tracking depleted the Resistance’s fuel reserves, cutting off their mobility and forcing attritional withdrawal.
Disruption of supply, denial of movement, and exploitation of logistical weaknesses are hallmarks of effective strategy. Star Wars echoes timeless truths from Hannibal’s destruction of Roman depots to the modern doctrine of Anti-Access/Area Denial (A2/AD).
Moral Logistics: Sustaining Sentients, Not Just Systems
Military logistics is not just about materiel—it’s about people. Troopers need food, shelter, rest, and psychological support. Fighters, medics, engineers, and even commanders need more than blasters to endure campaigns.
Casualty Care: Scenes of bacta tanks, surgical droids, and field hospitals show a robust but underrepresented aspect of war.
Morale and Rotation: Clone troopers often fought long campaigns without leave, while rebels rotated between fronts and support tasks. Sustaining morale is a strategic imperative.
Civilian Impact: Wars fought across star systems disrupt trade, displace populations, and trigger humanitarian crises. Relief logistics—though seldom depicted—are implied by the political backdrop.
Modern logisticians understand that sustainability includes welfare, ethics, and long-term planning. This is the soul of responsible operations.
The Forgotten Heroes of the Galaxy
Behind every cockpit and command post stands a silent corps of logisticians. They don’t feature on posters but keep ships flying and armies moving.
The deck chief who patches an X-Wing.
The loader who moves a crate onto a freighter.
The technician who calibrates hyperspace coordinates under fire.
The pilot flying an unarmed supply run through a contested sector.
These figures echo real-world logisticians—from Monte Cassino’s mule drivers to today’s digital supply coordinators. They are the pulse of operations, embodying flexibility, precision, and resolve.
Conclusion: May the Force Sustain You
Star Wars dazzles with spectacle. But underneath the lightsabers and blaster fire lies a truth every military professional knows: you cannot win what you cannot supply.
The galaxy’s wars are not just tales of good and evil—they’re narratives of fuel lines, convoy routes, maintenance bays, and depot clerks. Here, in the shadows of strategy, logistics quietly writes the outcome of every battle.
On this Star Wars Day, let us honour the unseen—the quartermasters, the movement controllers, the fixers and feeders, both fictional and real. Whether in a galaxy far, far away or on Earth today, their mission is the same:
