From the Waikato Commissariat to SAP, battlefield management systems and unmanned distribution.
The next major transformation in New Zealand Army logistics may not be defined by autonomous vehicles or drones, but by Defence’s logistics systems’ ability to connect operational requirements with the resources needed to sustain deployed forces. Autonomous technologies offer new means of transporting supplies, but their operational value will depend on how well they are incorporated into established logistics arrangements.
In July 2026, Drones, Distribution and the Small Army: Logistics for New Zealand’s Motorised Infantry Future examined how unmanned aerial systems might transform supply delivery to New Zealand soldiers operating on dispersed and contested battlefields. The article considered the vulnerability of conventional replenishment arrangements and the opportunities presented by autonomous technologies.[1]
Developments since then have made the subject more immediate. Singapore’s experimentation with its Next Generation Infantry Battalion during Exercise Wallaby 2026, together with New Zealand’s unmanned-vehicle trials, suggests that autonomous systems are becoming a practical question for military capability development.
An unmanned vehicle does not, by itself, transform military logistics. It provides another means of distribution, but it must operate within a system that identifies requirements, manages resources, sets priorities and coordinates support.
For the New Zealand Army, this raises a broader question: how might Defence’s enterprise logistics systems, tactical digital capabilities and movement-management arrangements evolve to support increasingly automated distribution?
The question is not new. Successive generations of New Zealand logisticians have confronted the same problem of coordinating supply, transport, information and accountability, and how they addressed it offers a useful foundation for thinking about the Army’s future.
An Old Problem in a New Form
Whatever the technology, the underlying challenge has been consistent: an army must obtain resources, organise their distribution and keep enough control over both to sustain its operations.
During the Waikato campaign of 1863–64, British forces relied on roads, river transport, animal-drawn vehicles and forward depots to sustain troops advancing south from Auckland. As Richard J. Taylor shows in his study of British logistics during the New Zealand Wars, the campaign depended as much on the organisation and coordination of these resources as on the transport equipment itself.[2]
Deputy Commissary-General Humphrey Stanley-Jones supervised a distribution system that used bullock wagons, horse-drawn vehicles, steamers, barges, and canoes. Taylor records that some stores were handled as many as sixteen times between Auckland and Ngāruawāhia, with each transfer creating additional work and increasing the risk of damage, loss, or errors in accountability.

An organisational disagreement in 1864 brought the issue into sharp focus. After the 4th Battalion Military Train arrived, its commander proposed absorbing the Commissariat Transport Corps into the Military Train. Senior Commissariat officers opposed the proposal, maintaining that the organisation responsible for obtaining and distributing supplies needed effective control over how they reached the troops. General Cameron ultimately retained separate responsibilities, with the Military Train undertaking selected transport duties while the Commissariat Transport Corps continued supporting much of the forward distribution system.[3]
The disagreement raised a question that remains relevant: should the organisation operating transport equipment determine how it is employed, or should the logistics system responsible for meeting operational requirements coordinate its employment?
Autonomous vehicles present the same problem in a new form. A drone might be operated by infantry, a logistics organisation or a specialist unmanned-systems element, but responsibility for operating the platform does not necessarily confer authority to establish supply priorities independently of the wider distribution system.
The technology has changed since 1864. The requirement to coordinate supply and movement has not.
From Movement Control to Computerised Supply Accounting
The expansion of New Zealand’s expeditionary commitments during the twentieth century progressively increased the complexity of military distribution. Deploying and sustaining forces overseas required coordination between depots, ports, airfields, staging areas and deployed units, frequently involving several modes of transport.
Specialist movement-control, terminal and air-dispatch capabilities developed because military movement involved more than providing vehicles, ships or aircraft. It also required managing capacity, priorities, destinations and documentation.[4]
A comparable transformation occurred in stores administration. For much of its history, the Royal New Zealand Army Ordnance Corps (RNZAOC) relied on handwritten records, vouchers and ledger cards to manage inventories. Although these arrangements provided accountability, they were labour-intensive and depended on accurate and timely manual transactions.
The introduction of Hollerith punched-card records in 1958 marked an important step towards mechanised supply accounting. Electronic accounting machines and computerised systems subsequently improved transaction processing and the production of inventory information.[5]
The Defence Supply System Retail (DSSR), introduced during the 1980s, and the subsequent Defence Supply System Development (DSSD) continued this progression. Both initiatives sought to improve inventory management and reduce delays and inconsistencies associated with earlier arrangements.

Nevertheless, computerisation introduced new challenges. Personnel required training, records had to be converted, and procedures revised. The usefulness of information also depended on how promptly transactions were completed. A central computer might hold extensive inventory records, but those records could become outdated when activity at a supply unit was not reflected quickly enough.
These limitations became particularly evident when computerised logistics support was extended into the field. During Exercise Golden Fleece in 1989, the Army experimented with providing deployed logistics organisations access to Defence supply information through mainframe terminals. The COMRAT ration-management application was also trialled on portable computers, demonstrating how relatively modest technology could reduce repetitive administrative work and assist field planning.[6]

These experiments brought logistics information closer to deployed organisations while highlighting the difficulties of transferring systems developed for established facilities into environments where communications, equipment reliability and technical support imposed additional constraints. Improvements in information processing proved most useful when matched by procedures and equipment suited to the conditions in which soldiers operated.
Project Fusion, SAP and the Integration of Army Logistics
During the 1990s, the New Zealand Defence Force (NZDF) undertook a wider transformation of financial, inventory and maintenance-management systems.
Project Fusion, initiated in 1994, introduced SAP enterprise resource planning software to integrate functions previously managed through separate applications. Financial management entered operation in 1996, followed by inventory and logistics management in 1998 and plant maintenance in 1999.[7]
The new environment provided opportunities to connect stock holdings, equipment records, maintenance activities and associated financial transactions through more consistent information and business processes.
Technological reform coincided with significant organisational change. On 9 December 1996, the Royal New Zealand Army Logistic Regiment (RNZALR) was formed by amalgamating the RNZAOC, the Royal New Zealand Corps of Transport (RNZCT) and the Royal New Zealand Electrical and Mechanical Engineers (RNZEME).[8] The regiment brought together the principal supply, transport and maintenance functions, recognising the increasing interdependence of activities previously undertaken by separate corps.
Although Project Fusion and the formation of the RNZALR were distinct initiatives, both reflected the same requirement: closer coordination between logistics functions. SAP integrated the information; the RNZALR integrated the people and trades.
Neither reform eliminated complexity. Inventory accuracy still depended on disciplined transactions, while an integrated computer system did not automatically produce an integrated organisation. Nevertheless, both laid foundations for later improvement.
Singapore and the Next Generation Infantry Battalion
Singapore offers a useful comparison because it, too, must generate military capability from a limited personnel base, and it is actively integrating new technology into its force rather than simply acquiring it.
During Exercise Wallaby 2026 in Queensland, the Singapore Armed Forces tested elements of its Next Generation Infantry Battalion (NGIB), an evolving concept combining revised organisation, digital command systems and unmanned platforms. Singapore’s Ministry of Defence describes a battalion incorporating dedicated unmanned-systems elements, including reconnaissance and attack drones, supported by integrated command-and-control arrangements.[9]

The NGIB’s significance lies not in the drones themselves but in building unmanned technologies into the organisation and operating methods of infantry formations, redistributing tasks between soldiers and machines rather than treating unmanned systems as supplementary equipment.
That is the lesson for New Zealand. The NZDF’s unmanned-systems trials are a necessary start, but trialling platforms is not the same as integrating them. Singapore is changing organisation, command arrangements and operating methods alongside the equipment, and New Zealand will need to do the same if autonomous systems are to deliver more than isolated demonstrations. The NGIB is not an autonomous logistics system, and conventional combat service support remains essential. It does, however, show the deliberate, whole-of-force approach that New Zealand Army logistics will need.
There is also an important distinction between remotely operated, supervised autonomous and more fully autonomous systems. A remotely operated vehicle may remove a driver from immediate danger while retaining a substantial operator workload. A supervised autonomous system may undertake some navigation or movement functions independently but still require human oversight and intervention. Greater autonomy raises further questions of reliability, decision-making authority and accountability.
Integration is also less about replacing logistics personnel than about examining whether new technologies can improve their effectiveness. Any assessment must consider the complete workload, including operators, maintainers, communications specialists and recovery personnel, rather than simply counting the drivers a particular journey might no longer require.
The Digital Gap Between the Battlefield and the Supply System
The NZDF already possesses much of the digital infrastructure on which future logistics capabilities could be built. SAP supports key aspects of inventory, maintenance, and resource management, while the Army’s Network Enabled Army (NEA) programme is introducing tactical communications, information-sharing, and battlefield management capabilities.
The Ministry of Defence identifies SitaWare as the Battle Management System acquired through NEA, alongside deployable servers, digital devices and communications infrastructure intended to improve situational awareness and information exchange.[10]
These systems serve different purposes. SAP manages Defence resources and their associated records, while SitaWare supports tactical command and coordination. Their functions are complementary, but public information does not show how far logistics requirements and inventory data can pass between them. That matters when deployed units need supplies.
From Operational Requirement to Logistics Response
Consider a hypothetical motorised infantry company operating 40 kilometres from its supporting logistics element. One of its vehicles becomes unserviceable because of a failed component, creating an urgent requirement for a replacement.
The company communicates its requirement to the supporting logistics organisation, which must identify the component, confirm availability, determine priority, and arrange delivery. Depending on the procedures and systems available, these activities may involve separate communications, manual coordination and transactions across different applications.
A more closely integrated arrangement could allow an authorised requirement to enter a governed logistics workflow, with relevant status information returned to the supported unit as the demand progresses. This would give commanders improved visibility without requiring them to operate the enterprise inventory system directly.
The example’s value lies in identifying what information operational decisions require and which systems should provide it.
Enterprise systems should remain authoritative for the records they are designed to maintain, while tactical applications should present information appropriate to their users. Any exchange between them would require suitable security, authorisation, data governance and technical arrangements.
The principal question is therefore not whether SAP should be replicated within a battlefield management system, but what logistics information commanders require and how it can be made available reliably.
Future ERP: An Opportunity to Consider Operational Logistics Integration
The relationship between enterprise logistics information and battlefield requirements matters now because the NZDF is preparing another transformation of its resource-management systems.
In September 2026, the NZDF issued an advance notice concerning its Future Enterprise Resource Planning (ERP) Programme, outlining plans for a more integrated enterprise-wide capability. The programme identifies SAP S/4HANA as the intended technology and includes systems integration, business integration and independent assurance among its major areas of work.[11]
Project Fusion sought to bring separate administrative and logistics functions into a common information environment. Future ERP provides an opportunity to examine how that environment should support Defence activities in the coming decades.
The procurement notice does not indicate that integration with SitaWare or support for autonomous logistics is within the programme’s scope, and Future ERP should not be assumed to provide them.
The more useful question is whether the operational information requirements associated with deployed logistics have been sufficiently identified to inform future enterprise-system design and related capability development.
Who is responsible for ensuring that the information requirements of deployed Army logistics are appropriately reflected across enterprise systems, tactical digital capabilities and future distribution technologies?
Different programmes, organisations, and funding arrangements are developing the capabilities involved. Without an agreed understanding of operational requirements, individual systems could meet their own objectives while leaving gaps in support for deployed forces.
DSSR, DSSD and Project Fusion all showed that successful technological change depends on aligning systems, procedures, responsibilities and the people who use them, not only on new software. Future ERP should therefore be seen within the wider evolution of Defence logistics, not merely as the replacement of an ageing enterprise application.
Digital Freight Management and the Movement of Supplies
The NZDF’s continuing digitisation of freight management provides another potential foundation for future distribution capabilities.
Freight management concerns a different aspect of logistics information from inventory accounting or tactical command. Its principal responsibilities include documenting consignments, identifying destinations, recording handling requirements and coordinating movement between locations.
Digital freight processes offer opportunities to reduce manual paperwork, improve the consistency of movement documentation and strengthen consignment visibility. These functions would remain relevant whether supplies were transported by conventional vehicles, aircraft, or autonomous platforms.
For autonomous distribution, particular attention would need to be given to consignment identification, the information required to task a transport resource and the means of confirming receipt. Standardised data and appropriate tracking arrangements could allow different transport platforms to operate within established movement-management procedures.
An autonomous vehicle would not, however, be automatically compatible with existing freight applications; any interface would need to be assessed for technical feasibility, operational requirements, security and organisational responsibility.
Movement control offers the precedent: as noted earlier, specialist movement organisations emerged because coordinating movement required skills and procedures distinct from operating the transport itself. The same distinction should inform the employment of autonomous distribution systems. Their introduction would expand available transport options without removing the need for effective movement coordination and accountability.
New Zealand’s Autonomous Systems Experimentation
New Zealand’s question is how to move from trial to integration. On 26 February 2026, the New Zealand Government announced that the NZDF would trial several unmanned systems supplied by New Zealand company Syos Aerospace, including the SG400 unmanned ground vehicle. The experimentation included potential applications involving supply movement, reconnaissance and other military tasks, alongside examining integration between unmanned technologies and existing Defence systems.[12]

The value of these trials should not be judged solely by whether a vehicle can travel between two locations or carry a specified payload. A more meaningful logistics assessment would examine how effectively the equipment performs an assigned distribution task within established military procedures.
Such an assessment would consider tasking, load preparation, delivery, recovery and the personnel required to support the platform. It would also determine whether autonomous equipment offers measurable advantages in speed, safety, reliability, or personnel use.
Subsequent experimentation could introduce multiple destinations, competing priorities, difficult terrain, degraded communications and the presence of opposing unmanned systems.
The choice of transport resource should remain subordinate to the operational requirement. A small aerial system may suit an urgently required component, an unmanned ground vehicle a heavier local load, and conventional transport bulk supplies or longer distances. The aim should be to expand distribution options, not to replace established transport simply because a new technology is available.
Sustaining the Systems That Sustain the Army
Autonomous systems would create additional technical and organisational responsibilities. Unmanned ground vehicles and aerial platforms depend on batteries, motors, sensors, communications equipment, electronic components, and software that require maintenance and support.
Some components may be replaced rather than repaired, while others could require specialist facilities, diagnostic equipment, technical expertise or manufacturer assistance. These requirements raise questions about Army trades and the future responsibilities of the RNZALR.
Routine servicing might be undertaken by operators, while more complex repairs could fall to appropriately trained technicians. Software support, configuration management, component traceability and the recovery of damaged platforms would also need consideration.
For a comparatively small army, the support burden could become significant if limited fleets from several manufacturers required different spare parts, diagnostic tools, training arrangements and technical support.
The benefit of autonomy must therefore be assessed against the personnel and resources required to sustain it.
New Zealand Army logistics history provides repeated examples of technological improvements creating new trades, specialisations and support requirements. Motor transport, electronic equipment and computerised supply systems changed the nature of logistics work but did not eliminate the requirement for trained personnel. Autonomous technologies are likely to follow a similar pattern. The challenge for the RNZALR will be to determine how these systems can be sustained within an organisation already responsible for supporting an increasingly complex range of military equipment.
Operating in the Pacific and on a Contested Battlefield
Much contemporary discussion of autonomous logistics draws on developments in Ukraine and European military experimentation. However, the Pacific presents distinct challenges, including dispersed islands, steep terrain, heavy rainfall, limited road networks, restricted infrastructure and substantial distances between logistics locations.
A platform that performs effectively in a prepared training area may struggle on narrow island tracks or in heavily vegetated terrain. A small aerial system may be constrained by weather, endurance, payload and the availability of suitable launch or recovery locations.
Autonomous systems also introduce vulnerabilities related to communications, navigation, software, and electronic warfare. Jamming, spoofing, cyberattack or equipment failure may interrupt operations. Repeated movement along predictable routes could disclose the locations of supply points and supported units, while charging and maintenance facilities could become additional targets.
Logistics organisations must therefore be able to operate with degraded communications. Deployed personnel must retain the ability to identify requirements, manage local stock, coordinate essential movement and record deliveries when central systems are unavailable.
Locally retained information, predefined authorisations and procedures for reconciling transactions once communications are restored may provide useful resilience, although they introduce risks involving outdated records and duplicate demands.
The Army’s experience of extending computerised supply systems into the field in the 1980s is a useful parallel: technology improves access to information only so far as it remains reliable under field conditions. A future autonomous distribution system should enhance the resilience of Army logistics rather than create a dependence on uninterrupted digital connectivity.
Building the Next Stage of Army Logistics
Mechanised accounting, DSSR, Project Fusion and SAP each required changes to organisation, procedures and training, not just new equipment or software. Autonomous distribution will be no different. Three areas warrant attention as the NZDF develops its future logistics capabilities.
Understanding Existing Processes
First, establish how deployed logistics requirements are currently communicated, authorised, and fulfilled, including the systems and procedures involved. This would help identify manual interventions, existing interfaces and opportunities to improve the availability of operational information.
Defining Information Requirements
The second is to determine what information commanders and logisticians need from enterprise and tactical systems, and which organisations should maintain authoritative records. These requirements could inform Future ERP, Network Enabled Army and related capability planning.
Evaluating Complete Logistics Activities
The third is to assess autonomous distribution through realistic military logistics tasks rather than isolated demonstrations of vehicle performance. Trials should examine reliability, personnel requirements, maintenance, communications resilience and the effectiveness of the supporting procedures, as well as payload and mobility. Such assessments would help establish where autonomous technologies offer practical advantages over conventional arrangements.
For the RNZALR, the underlying challenge is familiar. Future technologies will introduce new methods and responsibilities, but their successful employment will still depend on coordinating supply, transport and maintenance.
Conclusion: Beyond the Last Tactical Mile
New Zealand military logistics history shows that adaptation has always been central to sustaining a relatively small force.
During the Waikato campaign, the Commissariat coordinated several transport methods across difficult terrain. A century later, expeditionary commitments encouraged the development of specialist movement-control and terminal capabilities. Mechanised and computerised supply accounting improved inventory management, while Project Fusion and the formation of the RNZALR brought previously separate logistics functions into more closely integrated systems and organisations. Each development reflected the military requirements and technological possibilities of its time.
Autonomous ground vehicles and drones now offer another opportunity to improve military distribution. Singapore’s Next Generation Infantry Battalion shows what deliberate integration of unmanned technologies into a military organisation looks like. New Zealand’s experimentation is the starting point for doing the same in its own operational circumstances.
The established SAP environment, Network Enabled Army and digital freight management provide foundations to build on. Future ERP is an opportunity to decide how enterprise information should support operational requirements.
As the RNZALR approaches its thirtieth anniversary in December 2026, it is worth recalling its origins. The regiment was created by bringing together supply, transport and maintenance functions that had become increasingly interdependent; autonomous technologies are another stage in that continuing evolution.
The technologies available to the Army will continue to change. The fundamental responsibility of military logistics will not: ensuring that the right resources reach the right place, at the right time, in a condition that allows the force to accomplish its mission.
The next major transformation in New Zealand Army logistics may therefore be defined not by the machines carrying supplies, but by the logistics system’s ability to connect the entire journey from demand to delivery.
That would be consistent with more than 160 years of adaptation in New Zealand military logistics.
Notes
[1] Robert McKie, “Drones, Distribution and the Small Army: Logistics for New Zealand’s Motorised Infantry Future,” To the Warriors Their Arms, 8 July 2026, https://rnzaoc.com/2026/07/08/drones-distribution-and-the-small-army/.
[2] Richard J. Taylor, British Logistics in the New Zealand Wars, 1845–66 (PhD diss., Massey University, 2004), 129–45
[3] Taylor, British Logistics in the New Zealand Wars, 171–74.
[4] Robert McKie, Accuracy Under Pressure: The New Zealand Army Movement Operator Trade (2025), https://rnzaoc.com/wp-content/uploads/2025/12/New-Zealand-Army-Movement-Operator-Trade.pdf.
[5] Robert McKie, “The Evolution of Computerised Supply Accounting within the Royal New Zealand Army Ordnance Corps, 1958–1990,” To the Warriors Their Arms, 20 September 2023, https://rnzaoc.com/2023/09/20/the-evolution-of-computerised-supply-accounting-within-the-royal-new-zealand-army-ordnance-corps-1970-1990/.
[6] McKie, “Evolution of Computerised Supply Accounting,” discussion of Exercise Golden Fleece 1989 and COMRAT.
[7] Robert McKie, “The NZDF’s Evolution of Inventory Management from DSSR to SAP, 1984–1998,” To the Warriors Their Arms, 14 November 2024, https://rnzaoc.com/2024/11/14/the-nzdfs-evolution-of-inventory-management-from-dssr-to-sap-1984-1998/; “Outsourcing for Better Army Logistics,” Army Logistician 36, no. 2 (March–April 2004): 31, https://d34w7g4gy10iej.cloudfront.net/pubs/pdf_67339.pdf.
[8] Robert McKie, “Three Traditions, One Regiment: The Supply Trades That Formed the RNZALR, 1911–1996,” To the Warriors Their Arms, 26 July 2026, https://rnzaoc.com/2026/07/26/three-traditions-one-regiment/.
[9] Singapore Ministry of Defence, “Fact Sheet: Overview of Exercise Wallaby 2026,” 23 October 2026, https://www.mindef.gov.sg/news-and-events/latest-releases/23oct26-fs/; “Fact Sheet: Next Generation Infantry Battalion (NGIB),” 26 October 2026, https://www.mindef.gov.sg/news-and-events/latest-releases/26oct26-fs/.
[10] New Zealand Ministry of Defence, “Network Enabled Army C4 Project,” accessed 28 October 2026, https://www.defence.govt.nz/our-work/equip/capability-projects/network-enabled-army-nea-c4/; “Network Enabled Army Programme – An Overview,” https://www.defence.govt.nz/our-work/equip/capability-projects/network-enabled-army-nea-programme/.
[11] New Zealand Defence Force, “Future ERP – System Integrator, Business Integrator, and Quality Assurance,” Government Electronic Tender Service, 17 September 2026, https://www.gets.govt.nz/NZDF/ExternalTenderDetails.htm?id=34952898.
[12] Judith Collins, “Kiwi Drones to Boost Defence Capability,” New Zealand Government, 26 February 2026, https://www.beehive.govt.nz/release/kiwi-drones-boost-defence-capability.

































































































































