Drones, Distribution and the Small Army

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.

TierEchelonPlatform typeExample loads/roles
1Company/combat teamSmall tactical dronesRadio batteries, medical items, repair parts, documents, small rations, lightweight ammunition, local route checks and delivery-point confirmation
2Motorised Infantry Battalion GroupMedium-lift dronesAmmunition boxes, larger medical loads, tools, replacement sights, drone batteries, ration modules, route reconnaissance, replenishment overwatch and communications relay
3Brigade/jointLarger cargo drones and unmanned ground vehiclesMovement 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
4Joint/operational intra-theatreLarger fixed-wing logistics dronesInter-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.

ClassDescriptionDrone suitabilityComment
ISubsistence, rations, water and welfare itemsGood, limitedUseful for urgent top-ups to isolated posts, but not a substitute for bulk feeding
IIGeneral stores, clothing, individual equipment, tools and mapsGoodLight items can be moved easily, although priority may be lower
IIIFuel and lubricantsPoorWeight, volume and fire risk make this primarily a truck, tanker or pipeline task
IVConstruction and fortification materialsPoorUsually too bulky or heavy, except for small tools or fixings
VAmmunition and explosive ordnanceGood, controlledSuitable for small urgent natures, not bulk ammunition resupply
VIPersonal demand itemsGood, low priorityLight and low risk, but usually less urgent than medical, repair or ammunition loads
VIIMajor end items, vehicles, weapons and major equipmentNot suitableBeyond drone payload limits
VIIIMedical and dental storesStrongOften light, urgent and operationally critical
IXRepair partsStrongWell suited to small, forecast-difficult, mission-critical items
XNon-military programme materiel, including humanitarian and disaster relief storesGood, selectiveUseful 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 typePossible contents
Platoon emergency resupplyBatteries, water, medical stores and ammunition
Casualty supportDressings, analgesia, blood products and evacuation aids
Ammunition supportFuzes, tools, packaging material, labels and inspection equipment
Maintenance supportBelts, filters, cables, optics, lubricants and small assemblies
Signals supportBatteries, antennas, handsets, cables and replacement components
Disaster-relief supportWater purification items, medical stores, communications equipment and lightweight relief supplies
Indo-Pacific intra-theatre supportMedical 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.

The next adaptation should begin now.

Notes

[1] “NZ Army Evolves with Creation of New Motorised Infantry Battalion at Linton Military Camp,” 2025, accessed 1 July, 2026, https://www.nzdf.mil.nz/media-centre/news/nz-army-evolves-with-creation-of-new-motorised-infantry-battalion-at-linton-military-camp/.

[2] New Zealand Army, Future Land Operating Concept 2035: Integrated Land Missions (New Zealand Defence Force, 2026). https://www.nzdf.mil.nz/assets/Uploads/DocumentLibrary/Future-Land-Operating-Concept-2035-1.pdf.

[3] I. Sekirin and A. Simms, Rise of the Machines: Drone Warfare in the Russia-Ukraine War – Tactics, Operations, Strategy (Helion, 2026).

[4] “NATO armies unprepared for drone wars, Ukraine commander warns,” Reuters, 2025, accessed 1 July, 2026, https://www.reuters.com/world/nato-armies-unprepared-drone-wars-ukraine-commander-warns-2025-03-05/.

[5] “NZ Divisional Ordnance Field Park 1941–1945,” To the Warrior His Arms, History of the Royal New Zealand Army Ordnance Corps and it predecessors, 2018, accessed 1 July, 2026, https://rnzaoc.com/2018/12/10/nz-divisional-ordnance-field-park-1941-1945/.

[6] McKie, “NZ Divisional Ordnance Field Park 1941–1945.”

[7] Sekirin and Simms, Rise of the Machines: Drone Warfare in the Russia-Ukraine War – Tactics, Operations, Strategy.

[8] “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025),” Hudson Institute, 2025, accessed 1 July, 2026, https://www.hudson.org/events/david-petraeus-what-taiwan-can-learn-ukraines-battlefield-experience.

[9] “Unsung Enablers: A Snapshot of New Zealand’s Army Movements Control in World War II,” To the Warrior His Arms, History of the Royal New Zealand Army Ordnance Corps and it predecessors, 2024, accessed 1 July, 2026, https://rnzaoc.com/2024/11/17/unsung-enablers-a-snapshot-of-new-zealands-army-movements-control-in-world-war-ii/.

[10] Sekirin and Simms, Rise of the Machines: Drone Warfare in the Russia-Ukraine War – Tactics, Operations, Strategy.

[11] “Sypaq Corvo Precision Payload Delivery System,” Wikipedia, The Free Encyclopedia, updated 2026/07/06, 2026, https://en.wikipedia.org/wiki/Sypaq_Corvo_Precision_Payload_Delivery_System.

[12] Sekirin and Simms, Rise of the Machines: Drone Warfare in the Russia-Ukraine War – Tactics, Operations, Strategy.

[13] “Enter the kill zone: Ukraine’s drone-infested front slows Russian advance,” Reuters, 2025, accessed 1 July, 2026, https://www.reuters.com/business/aerospace-defense/enter-kill-zone-ukraines-drone-infested-front-slows-russian-advance-2025-07-17/.

[14] “Inside Ukraine’s drive to defeat the dreaded Shahed drone,” Reuters, 2025, accessed 1 July, 2026, https://www.reuters.com/business/aerospace-defense/inside-ukraines-drive-defeat-dreaded-shahed-drone-2026-04-29/.

[15] David Petraeus, “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025).”

[16] “AI-Driven Sustainment in Contested Logistics — Preparing for LSCO in the Indo-Pacific,” Army Sustainment, 2026, accessed 1 July, 2026, https://www.army.mil/article/290024/?fbclid=IwY2xjawS317dleHRuA2FlbQIxMABicmlkETFWNFJxTXRXemYzbXQ4V0JTc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHiPzttWAmnu0CoTnfavoODvZkI_UyYmc9gOH3uV14J4VOZazo9RZz8vQTLGP_aem_PbeTT4l-sv07R3nlkEtsKg.

[17] Australian Army, “Logistics,” Land Warfare Doctrine 4.0  (2018).

[18] Australian Army, “Logistics.”

[19] Australian Army, “Logistics.”

[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/.

[22] “Bringing the 3rd New Zealand Division Home: The Unheralded Triumph of New Zealand’s Greatest Military Reverse Logistics Operation,” “To the Warrior his Arms” History of the Royal New Zealand Army Ordnance Corps and its predecessors, 2024, accessed 1 July, 2026, https://rnzaoc.com/2024/09/05/bringing-the-3rd-new-zealand-division-home-the-unheralded-triumph-of-new-zealands-greatest-military-reverse-logistics-operation/.

[23] “Debunking the Myth of New Zealand’s Military Unpreparedness During the Interwar Period,” “To the Warrior his Arms” History of the Royal New Zealand Army Ordnance Corps and its predecessors, 2024, accessed 1 July, 2026, https://rnzaoc.com/2024/07/21/debunking-the-myth-of-new-zealands-military-unpreparedness-during-the-interwar-period/.

[24] “Development of NZ Army Combat Clothing, 1955–1980,” To the Warrior His Arms, History of the Royal New Zealand Army Ordnance Corps and it predecessors, 2023, accessed 20 March, 2026, https://rnzaoc.com/2023/02/11/development-of-nz-army-combat-clothing-1955-1980/.

[25] “NZ Army Camouflage 1949-1979,” To the Warrior His Arms, History of the Royal New Zealand Army Ordnance Corps and it predecessors, 2023, accessed 20 March, 2026, https://rnzaoc.com/2023/04/29/nz-army-camouflage-1949-1979/.

[26] “Ukraine to Sharply Raise Purchases of Home Produced FPV Drones in 2025,” Reuters, 2025, accessed 1 July, 2026, https://www.reuters.com/business/aerospace-defense/ukraine-sharply-raise-purchases-home-produced-fpv-drones-2025-2025-03-10/.

[27] David Petraeus, “David Petraeus on What Taiwan Can Learn from Ukraine’s Battlefield Experience” (event transcript, Hudson Institute, July 28, 2025).”

[28] “Europe Rethinks How It Fights War as Russian Threat Looms,” Reuters, 2025, accessed 1 July, 2026, https://www.reuters.com/business/aerospace-defense/europe-rethinks-how-it-fights-war-russian-threat-looms-2026-06-29/.

[29] “New Zealand Military Armourers, 1840–1900,” “To the Warrior his Arms” History of the Royal New Zealand Army Ordnance Corps and its predecessors, 2025, accessed 1 July, 2026, https://rnzaoc.com/2025/06/03/new-zealand-military-armourers-1840-1900/.

[30] “US Soldiers learn to 3D print and fly drones in new Army course — 3-week boot camp covers everything from printer maintenance to FPV operation,” Tom’s Hardware, 2026, accessed 1 July, 2026, https://www.tomshardware.com/3d-printing/u-s-soldiers-learn-to-3d-print-and-fly-drones-in-new-army-course-3-week-boot-camp-covers-everything-from-printer-maintenance-to-fpv-operation.

[31] “US Marine Corps develops first 3D printed drone with no China-sourced parts, dubbed HANX — modular design makes it quick to adapt from reconnaissance to one-way attack, and other duties,” Tom’s Hardware, 2026, accessed 1 July, 2026, https://www.tomshardware.com/3d-printing/us-marine-corps-develops-first-ndaa-compliant-3d-printed-drone-dubbed-hanx-modular-design-makes-it-quick-to-adapt-from-reconnaissance-to-one-way-attack-and-other-duties.

[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).

[34] “Australian government supports new drone radio production line,” Army Technology, 2025, accessed 1 July, 2026, https://www.army-technology.com/news/australian-drone-radio-line/?cf-view.

[35] “Albanese Government to invest up to $7 billion in counter drone defence,” Australian Government, 2026, accessed 1 July, 2026, https://www.minister.defence.gov.au/media-releases/2026-04-21/albanese-government-invest-up-7-billion-counter-drone-defence.

[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).”


The Evolution of Computerised Supply Accounting within the Royal New Zealand Army Ordnance Corps,  1958-1990

The Need for Change

The Royal New Zealand Army Ordnance Corps (RNZAOC) has historically played a crucial role in ensuring the efficient supply and management of military logistics. Operating in an era far removed from today’s advanced technological landscape, the RNZAOC initially relied on manual processes for stores and inventory accounting. These methods, virtually unchanged since the 1860s, required handwritten vouchers, ledgers, and ledger cards to track all transactions. The process was time-consuming, highly labour-intensive, and error-prone, requiring exceptional accuracy. As the demands of modern logistics increased, inefficiencies in RNZAOC accounting practices became a growing concern.

By the mid-20th century, military supply chains worldwide were beginning to embrace mechanisation and digitalisation to improve operational efficiency. Therefore, the transition to computerised supply accounting was a significant and necessary evolution, aligned with broader Defence modernisation efforts.

This article traces the RNZAOC’s journey from manual record-keeping, through the early use of Hollerith punched-card records from 1958, to the introduction of electric accounting machines and, eventually, fully integrated computer-based supply systems. It covers the staged evolution of military logistics automation in New Zealand from 1958 to 1990.

The Hollerith Precursor, 1958

Recent evidence indicates that the RNZAOC’s movement towards mechanised supply accounting began earlier than previously understood. By 1958, Hollerith punched-card records were being used, serving as an important precursor to the later Electronic Accounting Machine and Electronic Data Processing systems introduced during the 1960s.

The Hollerith system did not represent computerisation in the modern sense. Rather, it was a form of mechanised data processing in which information was recorded on punched cards and then sorted, counted, or tabulated by machine. Its significance lies in the fact that it introduced the Army supply system to the idea that stores information could be standardised, encoded, machine-read, and processed in bulk. This marked a clear departure from purely handwritten ledgers and manual card systems.

The 1958 use of Hollerith records therefore suggests that the 1964 feasibility study into electronic data processing was not the beginning of automation within Army supply accounting, but a later and more ambitious stage in an already developing process. The experience gained from punched-card record-keeping would have helped shape later thinking on machine-readable stock records, standardised item identification, centralised processing, and the eventual replacement of manual ledger-card accounting.

Seen in this light, the evolution of RNZAOC supply accounting was not a sudden leap from stubby pencils and ledger cards to computers. It was a staged progression from manual accounting to punched-card mechanisation to Electronic Accounting Machines and finally to mainframe-supported Defence supply systems.

Transition to the NATO Codification System and Evolution of Stores Accounting

Owing to the historical connections between the RNZAOC and the British Army, the RNZAOC initially employed the Vocabulary of Army Ordnance Stores (VAOS) system to categorise item part numbers. Nevertheless, as the relationship with the United States deepened, and more US equipment entered into service, a pivotal decision was made in 1968 to embrace the NATO Codification System. This transition replaced VAOS numbers with universally recognised NATO Stock Numbers (NSNs). NSNs are commonly associated with the United States Military as National Stock Numbers, which evolved from the Federal Stock Numbers developed during World War II. While the United States Government created the codification system, it has long been developed and augmented into a Global System by NATO.

Each Item of Supply is identified in the National Codification System by a unique 13-digit NSN. The NSN consists of three identifying parts:

  • A four-digit NATO Supply Classification (NSC), also known as “Group Class,” places an item into a group classification, such as generators or aircraft engines.
  • A Two-digit Nation Code (NC) identifying the country assigned the NATO Stock Number. Examples of NCs are:
    • 00 and 01 – United States.
    • 66 – Australia.
    • 99 – United Kingdom.
    • 98 – New Zealand.
  • A seven-digit Item Identification Number (IIN), together with the NZ, is unique to that item.
Example of pre 1972 New Zealand NSN using “NZ” instead of “98”. Robert McKie Collection

With the support of the United Kingdom, New Zealand gained admission to the NATO Codification community in 1969. Although the first official “98” NATO Stock Number (NSN) was assigned in December 1972,  NSNs with the “NZ” prefix had been in active use as far back as 1964. With many items still in the supply system with VAOS codes, it took time to harmonise and align the two codification systems. However, by the close of the 1970s, NATO Stock Numbers had been fully integrated into the New Zealand Army supply infrastructure.

Example of pre 1972 New Zealand NSN using “NZ” instead of “98”. Robert McKie Collection

Simultaneously, as New Zealand transitioned into the NATO Codification community, and considering that a significant portion of RNZAOC activities centred around procurement, provisioning, and store’s accounting, steps were taken in 1964 to modernise the processes related to store’s accounting.

The store’s accounting practices within the RNZAOC had evolved from the initial systems established by the New Zealand Defence Stores Department in the 1860s and incorporated lessons learned since then. The cornerstone of these records was the ledger card. In 1980, many of the ledger cards utilised by the RNZAOC had their roots in the Royal Army Ordnance Corps (RAOC) Visidex system. The Visidex system, introduced by the RAOC in the late 1930s, was designed as a straightforward ledger card system to replace complex mechanical ledger posting systems that had proven unsatisfactory.[1]  Initially implemented for wartime use within Ordnance Field Parks (OFPs), the Visidex system proved ideal due to its simplicity, requiring minimal staff training. Carbon-backed posting slips were used, enabling easy checks to be conducted. Each OFP section maintained a control office where all indents from units were received. The stock record was meticulously verified, the stock’s location within the OFP (where each truck served as a stock location) was identified, and the stock record was promptly updated. If the stock was available, it was immediately issued. When the stock was unavailable, it was recorded as “Dues Out,” and an indent was placed with the supporting Depot for replenishment, marked as “Dues In.”[2]  Each truck within an OFP also maintained its stock records, reconciled with each issue, receipt, and stocktake. The robustness and simplicity of the Visidex system made it the primary field stores accounting system within the New Zealand Army, a role it continued to fulfil well into the 1990s. In the context of the 1980s, the RNZAOC stores accounting system consisted of eight different ledger card systems:

  • MD 310 Ledger card. Used by 1 Base Supply Battalion, 1, 2, 3, and 4 Supply Companies, and the New Zealand Advanced Ordnance Depot Provision, Control and Accounts (PC&A) Sections to manage Defence Inventory, less, Ammunition, Rations and Fuel and Articles in Use (AiU).
  • MD 324 Loan Record Card. Used by Quartermaster Stores to manage AIU items on long term loan (7 Days or more) to individuals.
  • MD 329 Record of Stores Supplied on Temporary Loan. Used by Quartermaster Stores to manage AIU items on short term (7 Days or less) loan to individuals.
  • AFNZ 150 Stock Record Card. Used by RNZAOC Workshops Stores section to manage repair parts, assemblies and workshop material to suit the particular requirements of their parent workshops.
  • AFNZ 169P Ammunition Account Card and AFNZ 171P Ammunition Lot/Data Card. Used by the Ammunition Provision Control and Accounts (APCA) section to manage serviceable and unserviceable ammunition.
  • AFNZ 28 Supplies and FOL Ledger. Used by RNZAOC Supply Platoons to manage Foodstuffs, Fuel, oil and lubricants.
  • AFNZ 162 Stock and Provision Record Card. Based on the Visidex card, the AFNZ162 was used by RNZAOC Field units to manage stock in operational environments.
  • AFNZ 161 Store Ledger Card. Used by RNZAOC Quartermaster Stores to manage AIU items in-store or on distribution under an MD502 Distribution Record.

Journey Towards Electronic Data Processing

The journey to replace stubby pencils and erasers began in 1964 with a feasibility study on introducing electronic data processing into store accounting within the Army. By September 1965, a machine accounting system had been designed for Army use. However, the Army was not working in isolation—this was part of a broader Defence-wide initiative to introduce computerised accounting, with the Navy and Air Force developing parallel systems tailored to their specific needs.

The new system was intended to utilise electric accounting machines (EAMs) at ordnance depots and major camps. These machines updated records and punched data onto paper tape for processing at the Defence EDP Centre. However, at this stage, Defence did not yet have a central computer, so an arrangement was made to use the Treasury’s IBM 650 computer.

Treasury’s IBM 650. National Library

EAMs had arithmetic capabilities and could generate simultaneous, error-free postings, records, registers, and paper tape. Their introduction was expected to significantly reduce the number of documents required, operate much faster than manual methods, and minimise audit queries.

Once the central computer processed the information produced by the EAMs, a timely and wide range of data became available, including:

  • Daily provisioning information.
  • Quicker identification of surpluses.
  • Continuous extraction of shortfalls and bonuses.
  • Status reports on demand, including requirement-resource comparisons over any desired range.

For the first time, the system aimed to provide a more accurate prediction of stock levels, enabling faster and more efficient service to units.

Phased Introduction of the System

From November 1965, the new system was to be introduced in four phases:

  • Phase 1 – Main Ordnance Depot at Trentham
  • Phase 2 – District Ordnance Depots
  • Phase 3 – Main Camps and Logistic Support Group (LSG) Units
  • Phase 4 – Other units, either through Camp machine installations or by direct computer input

During Phases 1 and 2, the EAMs were to function as a self-contained system with central control, which would commence fully in Phase 3.

Implementation Timeline

  • November 1965 – Machines, ledger cards, and machine operators delivered to the Main Ordnance Depot. Card raising begins with a new type of ledger card.
  • June 1966 – Planning begins at District Ordnance Depots.
  • October 1966 – Balances machined on ledger cards at the Main Ordnance Depot. Automatic accounting commences, and output is prepared for the computer.
  • Early 1967 – Planning commences at Main Camps and LSG units.
  • June 1967 – Automatic operations begin at District Ordnance Depots.
  • 1968 – Units outside of main camps are integrated into the system.

Training of EAM Operators

Training of EAM Operators

EAM operators were to be known as Data Operators. The RNZAF conducted a twelve-week training course for data operators. By September 1965, the Army had two trained operators, with an additional four about to commence training.[3]

Early Progress

By June 1966, the overall design of the EAM system, reporting to a central computer installation, was well advanced. The target date for the Main Ordnance Depot (MOD) was now set a month ahead of the original schedule of October 1966. Army had 6 Data Processors, 5 at the MOD and one at CDOD at Linton,

Since November 1965, MOD data processors had been raising cards using Flexowriter machines, which also produced punched paper tape for computer input. The facilities at MOD had also been upgraded, with the machine room at Trentham completed and fitted with two NCR-33 accounting machines. Additionally, machine rooms were installed at Ngāruawāhia and Burnham, while a new facility at Linton was planned for completion in July 1966. Planning for machine rooms at Papakura and Waiouru had been finalised, but installation had not yet taken place.[4]

Proposals for a Defence computer installation were deferred in 1967, as the overall defence programming capability was weakened by the resignation of experienced staff who transferred to private industry. Initially, Defence policy aimed to advance computing in personnel, pay, and supply simultaneously. However, in 1967, priorities were reassessed, with supply taking precedence, followed by personnel and then pay.

The introduction of accounting machines at the Army’s Main Ordnance Depot (MOD) and the Navy’s and Air Force’s equivalent store depots meant that all three services were now operating with standard ledger cards and uniform procedures. This was a significant step forward toward a unified Defence supply system. Reliance on a mainframe computer continued, with the Treasury’s computer—now upgraded to an IBM 360—remaining in use.[5]

In July 1967, approval was granted for a Defence computer installation, and the rental of an International Computers and Tabulators (ICT) ICT-1902 was authorised for installation at the Defence EDP Division in Porirua. This necessitated Defence staff retraining and converting projects from the Treasury’s IBM 360 system to the new system. However, the priority of EDP work remained unchanged, with supply taking precedence, followed by personnel and finance.[6]

By September 1968, Defence’s ICT-1902 computer was fully operational, supporting standard Defence systems. The following supply systems were in production:

  • Stores Budgetary Control – Provided monthly reports by departmental expenditure code, detailing funds committed, paid, and outstanding for the Navy, Army, and Air Force. The system tracked approximately 400 vote code items and 90,000 stock lines.
  • Federal Stock – Recorded receipt, issue, consumption, and provisioning data for 78,000 line items of U.S.-supplied equipment. This record was expected to expand significantly with the acquisition of A-4K Skyhawks and increasing U.S.-supplied equipment for the Army.
  • Class A Stores – Tracked the location of all high-value and sensitive stores issued to Army units.
  • Vehicles – Maintained records of all vehicles by unit, including a catalogue detailing vehicle types and associated equipment, such as tyres.[7]

At this stage, the Air Force, with a relatively new fleet of American aircraft, took the lead in developing a Defence supply system. This system was envisioned to cover approximately 200,000 line items for the Air Force alone and would gradually be extended to the Navy and Army.[8]

1970–1990: Expansion and Modernisation

The Defence Force replaced the ICT-1902 mainframe with a more capable ICL 1903 mainframe in the early 1970s, which improved the capacity for handling Defence logistics. Some key supply systems introduced during this period included:

  • Stores Budgetary Control System – Monthly expenditure tracking for Army, Navy, and Air Force.
  • Federal Stock Control System – Managed 78,000 US-supplied military items, which was set to expand significantly with the acquisition of A-4K Skyhawks.
  • Class A Stores System – Tracked high-value and sensitive Army inventory.
  • Vehicle Fleet Management System – Monitored vehicle holdings, maintenance, and associated equipment.

A NCR 299 electronic accounting system from 1974https://computarium.lcd.lu/photos/albums/BONAMI_MISC/album/slides/P1030480.html

The Sperry Era

By 1981, the NZDF’s computing capability had fallen behind contemporary industry standards. A major overhaul took place when the ICL mainframe was replaced with a Sperry UNIVAC 1100/60E mainframe.[9]  Concurrently, a comprehensive data communications network was established, connecting major Defence locations to the computer at Porirua. This network featured 550 non-programmable (dumb) workstations across the defence infrastructure, each consisting of a keyboard and terminal.

The Sperry mainframe computer became fully operational by April 1982. However, as the S2 system was developed on an ICL 1903 computer, the conversion to the Sperry system proved difficult. The system suffered severe conversion problems with the programme, paving the way for implementing the Defence Supply System Retail (DSSR) project. The full implementation of DSSR was initially forecast for 1986/87. DSSR was conceived as a project to extend the mainframe’s technology to the depot and unit level, automating the functions conducted by the ICL system with minimal enhancements. The anticipated benefits of DSSR included:

  • A more responsive reporting facility.
  • An electronic data record in place of ledger cards.
  • Automatic production of vouchers.
  • Automatic updating of stock files.
  • An up-to-date central overview of the stock situation.
  • Automated production of statistics at both HQ and unit levels.
  • An instantaneous enquiry system at unit level.
  • Less dependence by units on higher Headquarters for stock information.

By 1983, RNZAF Base Auckland had implemented the DSSR system, with 1 Supply Company at Ngāruawāhia migrating their MD310s into the DSSR system. This concerted effort positioned 1 Sup Coy to input the ledger balances into the DSSR system once the necessary hardware, including terminals, keyboards, and printers, had been installed and the personnel of 1 Sup Coy had completed their training. These milestones were successfully achieved by late March 1984. As 1 Sup Coy went live, other RNZAOC units were cleansing their records in anticipation of integration into the DSSR system. The transition from the NCR Machines to DSSR was not seamless as the NCR machines were worn out and difficult to support by the vendor. Units such as NZAOD and 4 Sup Coy had by 1984 reverted to a manual accounting system. Although labour-intensive, manual accounting using the MD310 was found to be accurate, with stock figures held in PC&A Sections not too far out.[10]

DSSR represented just one of the computer applications employed by the RNZAOC. By 1988, the SPERRY Mainframe at Porirua supported additional applications alongside DSSR. Running on a third-generation programming language known as COBOL, the most well-known COBOL programs included:

  • POLI (Personnel On-line Inquiry).
  • AIRMAIL (Personnel On-line PON Input).
  • DSSR (Defence Supply Systems – Detail).
  • LOGIC (Logistics Inventory Control).
  • Finance Interrogation (RI) System.
  • Finance Expenditure (RS) System.
  • Finance Commitments (RC) System.

Another mainframe application utilised by the RNZAOC was the Maintaining, Preparing, Producing Executive Report (MAPPER) application. While it could be used for programming, it was resource-intensive, making it less favoured by computer production management staff. The RNZAOC, along with the RNZEME, were significant users of MAPPER, employing it for:

  • 1 BSB Stock Location System.
  • Army Defect Reporting System (ADRS).
  • Army Equipment Management System (AEMS).

The New Zealand Army Scales and Documentation Centre (NZASDC) Scales and Entitlements System Was introduced in 1986, automating the production of equipment scaling documents. The NZASDC system was based on a PRIME computer and incorporated data and graphics. One of the selling points for introducing this system was that it allowed the staff of NZASDC to overcome an estimated backlog of 150 man-years. The budget for this system in 1985 was $0.579m (2023 $1,835,352).

By 1988, access to the Defence Integrated Database System (DIDS)was introduced, allowing for enquiries against all overseas provided identification and technical information. This gave item managers access to other nation’s sources of supply.

Since the mainframe provided access to only limited applications and little scope for general computer familiarisation, the first Sanyo microcomputers were introduced into Defence in 1981. These offered access to programs for word processing, spreadsheets, and database access to Defence units. 1988 Defence expanded its microcomputer capability with a tender for a new range of microcomputers based on the IBM/MS-DOS standard. The selected machine was the 16-bit Compaq Deskpro 286. By the end of 1988, the number of Compaqs owned by Defence was over 700, with 140 installed within Army units. Standard software packages selected for these microcomputers include the following:

  • WordStar 2000 Plus (Word-processor)
  • dBase III Plus (Database)
  • Lotus 1-2-3 (Spreadsheet)
  • SuperCalc4 (Spreadsheet)
  • FrameWork 2 (Integrated package)
  • SideKick (Desktop assistant)

The Defence Supply System Development (DSSD) project was initiated in 1986 as the second phase to replace the NCR accounting machines and ledger cards in stockholding units, with the first phase, DSSR, implemented during 1983/5. Both DSSR and DSSD were considered interim solutions due to the urgency dictated by the inability to support the NCR accounting machines beyond 1988.

The Defence Supply Redevelopment Project (DSRP) was launched in 1986 to find a lasting solution. The goal was to replace the temporary DSSR and DSSD systems while tackling persistent issues like repairable item management and performance measurement.

Resource limitations made it impractical to develop both projects (DSSD & DSRP) in parallel and wasteful to develop both as interim solutions. Analysis of the fundamental problems with the supply system identified during the first phase of DSSR pointed to DSSD as a reasonable, simple and achievable data integrity and management solution.

DSSD was confirmed in 1987 as the baseline supply system for later enhancement by DSRP. This has involved a change in scope to allow repair processing and retail functions with DSSD replacing DSSR with more comprehensive processing. On completion of DSSD, it was intended to have a stable on-line supply system in place, containing each of the essential features required of a supply accounting and replenishment system in basic form, allowing the New Zealand military to meet its operating requirements. The planned implementation phases for DSSD were:

  • Construct item identification records and complete depot purification by March 1988.
    • 1 Base Supply Battalion (1BSB) trial and conversion by March 1989.
    • Enhance 1 BSB office facilities and convert Air and Navy depots by January 1990.
    • Retail prototypes by September 1990.
    • Enhanced retail facilities and complete conversion by January 1991.
    • Develop future DSRP modules such as performance measurement starting in 1990.

With DSSR rolled out to most RNZAOC Units by 1987. However, the DSSD development team encountered difficulties with the LINC development environment, delaying the pilot system rollout at 1BSB until late 1989.

To enhance field support capabilities, the RNZAOC initiated computer experimentation in 1988. A significant milestone occurred during the 1988 Force Maintenance Group (FMG) Annual Camp when a mainframe terminal was introduced to the 21 Supply Company, granting access to the DSSR. Another notable advancement at the FMG Annual Camp involved the trial of a computer-based Frequency of Issue (FOI) calculation system designed and coded using dBase III. This system drastically improved efficiency, enabling the Ration Platoon staff to complete forty-eight man-hours of work in just four hours. Following this success, the FOI program underwent a thorough evaluation by a Quality Review Team established by the Directorate of Ordnance Services (DOS). It was subsequently extensively redeveloped and renamed COMRAT.

Sergeant Gerry Rolfe and DSSR Terminal, FMG Annual Camp 1988. RNZAOC Collection

During the 1989 Exercise Golden Fleece, mainframe terminals were strategically placed in the exercise area to support 21 Supply Company, the Ordnance Support Group (OSG), and Workshop Stores Sections. Additional general-purpose terminals were deployed at the New Zealand Force and FMG Headquarters. Strong data communication links were established to the Defence mainframe through Telecon data circuits and RNZSigs radio relay facilities.

Furthermore, COMRAT was tested and evaluated by RNZAOC units deployed on Exercise Golden Fleece in New Zealand and on Exercise Taiaha Tombak X in Malaysia, utilising hardware in the form of a ‘ruggedised’ GRiDCASE laptop or Hewlett-Packard Portable Vectra CS laptop. These innovative approaches aimed to validate the procedures and facilities required to support logistics elements deployed alongside operational forces. However, the outcomes of these experiments were diverse, showcasing both successes and challenges. While progress was evident, it became clear that the ultimate goal of achieving a fully deployable logistics solution remained a work in progress.

NZAOD Hewlett-Packard. Portable Vectra CS, 1989. Robert McKie Collection

Conclusion: A Transformational Shift in Military Logistics

The evolution of supply accounting within the RNZAOC was not a sudden transformation that began with the electronic data processing studies of the 1960s. Evidence that Hollerith punched-card records were in use by 1958 shows that the Corps had already begun moving towards mechanised supply accounting before the formal Defence EDP programme emerged. This early use of machine-readable records provided an important bridge between manual ledger-card accounting and the electric accounting machines, paper-tape processes, and computer-based systems that followed.

From this foundation, the period from the late 1950s to 1990 saw the RNZAOC move progressively from labour-intensive manual accounting to increasingly centralised, standardised, and automated systems. Each stage reflected the same enduring requirement: to know what was held, where it was held, what was required, and how the Army could sustain itself more effectively. The adoption of NATO codification, the use of mechanised accounting methods, the development of Defence EDP, and the later introduction of more integrated computer-based supply systems were all part of this wider progression.

By 1990, the Corps had travelled a considerable distance from handwritten records, manual ledgers, and punched cards to computer-supported supply accounting. The change was not simply technical. It altered the way stores information was captured, processed, reported, and used for decision-making. In doing so, it laid the groundwork for the logistics information systems that would follow, and demonstrated the RNZAOC’s continuing ability to adapt its accounting practices to meet the changing needs of the New Zealand Army.

Notes


[1] Brigadier A.H Fernyhough C.B.E. M.C, History of the Royal Army Ordnance Corps 1920-1945 (London: Royal Army Ordnance Corps, 1965), 213.

[2] P.H. Williams, War on Wheels: The Mechanisation of the British Army in the Second World War (History Press Limited, 2016), 73.

[3] Army 246/1/12 Introduction of Electronic Data Processing into Stores Accounting Systems-NZ Army Dates 30 Sept 1965. “Stores – Account for General Instructions,” Archives New Zealand Item No R17188987  (1964 – 1967).

[4] Defence EDP Division 38/4/3 EDP Stores Accounting Systems Dated 28 June 1966. “Stores – Account for General Instructions.”

[5] “H-4 Report of the Ministry of Defence for the year ending 31 March 1967,” Appendix to the Journals of the House of Representatives  (31 March 1967 1967).

[6] “H-4 Report of the Ministry of Defence for the year ending 31 March 1968,” Appendix to the Journals of the House of Representatives  (31 March 1968 1968).

[7] “H-4 Report of the Ministry of Defence for the year ending 31 March 1969,” Appendix to the Journals of the House of Representatives  (31 March 1969 1969).

[8] “H-4 Report of the Ministry of Defence for the year ending 31 March 1970,” Appendix to the Journals of the House of Representatives  (31 March 1970 1970).

[9] New Zealand. Parliament, Parliamentary Debates: House of Representatives (1983).

[10] Major J.S Bolton, A History of the Royal New Zealand Army Ordnance Corps (Trentham: RNZAOC, 1992).