Operational use

Managed Android phones for training, movement and unit tasks.

W.O.L.F provides approved users with messaging, files, location awareness and device-management functions on managed Android phones.

Potential uses include training, movement, logistics, events, distributed working and communications fallback. Each use remains subject to the task, information, connectivity and approval position.

  1. 01Training and exercises
  2. 02Convoys and movement
  3. 03Logistics support
  4. 04Events and contingency tasks
  5. 05Distributed working
  6. 06Communications fallback
Use cases
06
Device issue
Managed
User services
Selected
Devices and access
Recoverable

Use-case overview

Six potential use cases show where W.O.L.F could support unit activity.

  1. 01

    Training and exercises

    Managed messaging, exercise information, location awareness and temporary phone issue for approved training.

  2. 02

    Convoys and movement

    Shared routes, location updates, incident reporting and movement coordination where authorised.

  3. 03

    Logistics support

    Planned reporting of holdings, shortages, resupply requirements and update times.

  4. 04

    Events and contingency tasks

    A prepared package of managed phones, accounts and selected services for temporary activity.

  5. 05

    Distributed working

    Approved messaging, file access and command updates for users working in different locations.

  6. 06

    Communications fallback

    A prepared alternative for suitable tasks when primary systems are unavailable and an approved communications route remains available.

Training and distributed working

W.O.L.F can give training and distributed users the same managed phone setup while the unit retains control of devices and accounts.

Training and exercises

Potential functions

  • Managed group messaging
  • Exercise orders and updates
  • Approved file access
  • Location awareness where authorised
  • Temporary phone and account issue
  • Recovery and rebuild after activity

Outcome Users receive familiar phones and selected services, while the unit retains a repeatable issue and recovery process.

Distributed working

Potential functions

  • Team messaging
  • Approved files and documents
  • Command updates
  • Selected collaboration services
  • Phone status and user registration
  • Access removal when no longer required

Outcome Users can reach selected services from different locations without relying on unmanaged personal applications.

Convoys and movement

Where authorised, W.O.L.F could support shared information and communication during movement activity.

User functions

  • Shared routes and movement information
  • Vehicle or call-sign location
  • Incident and delay updates
  • Group messaging
  • Selected files and instructions

Unit functions

  • Registered users and phones
  • Phone status and check-in
  • Temporary access assignment
  • Access removal after activity
  • Recovery of returned phones

Location sharing and route information remain subject to task approval, information sensitivity and available connectivity.

Planned function

Logistics support

Planned

W.O.L.F Sustain is planned to let users report holdings, shortages and resupply needs to authorised commanders.

For users

Report:

  • Location
  • Equipment holdings
  • Quantities
  • Shortages
  • Resupply requirements
  • Last update time

For authorised commanders

Review:

  • Information by user, call sign or vehicle
  • Reported holdings
  • Quantities and shortages
  • Reporting freshness
  • Resupply requirements

Reporting flow

  1. 01

    User update

    The user records location, holdings, shortages and resupply needs.

  2. 02

    Controlled submission

    The information is submitted through W.O.L.F.

  3. 03

    Commander view

    An authorised commander reviews the latest report.

  4. 04

    Review or resupply action

    The information supports validation, follow-up or resupply decisions.

CURRENT POSITION Sustain has not yet been developed. Reporting measures, permissions, offline handling and evidence requirements must be defined and tested against KUR 4 before any deployment decision.

Events and fallback communications

Prepared phones and selected services could provide a temporary communications package for approved events, contingency tasks and fallback activity.

Events and contingency tasks

Potential functions

  • Preconfigured managed phones
  • Temporary named accounts
  • Group messaging
  • Approved files and updates
  • Recorded issue and recovery
  • Rebuild and reuse after the task

Communications fallback

Potential functions

  • Prepared alternative communications
  • Selected services through an approved bearer
  • Temporary access for authorised users
  • Controlled phone issue
  • Recoverable accounts and phones
  • Access removal after use

W.O.L.F does not replace formal tactical CIS. Fallback use depends on the task, approved information handling, available connectivity and relevant authority.

How it works

How W.O.L.F is delivered

Each use case follows the same process for preparing, issuing, controlling, recovering and reissuing phones.

  1. 01

    Prepare

    Apply the approved phone setup and selected applications.

  2. 02

    Issue

    Assign the phone and managed account to a named user.

  3. 03

    Operate

    Provide the services required for the approved task.

  4. 04

    Recover

    Return the phone, remove temporary access and review its status.

  5. 05

    Rebuild

    Wipe or rebuild the phone and restore the approved setup where required.

  6. 06

    Reissue

    Assign the recovered phone to another approved user or task.

A W.O.L.F deployment may include

  • Prepared Android phones
  • Named user accounts
  • Private platform access
  • Messaging and file services
  • Location awareness where authorised
  • Control Centre visibility
  • Guardian device check-in
  • Recovery and rebuild procedures

Decision context

Conditions for use

W.O.L.F can be used only where the task, information, connectivity, support and approval position are suitable.

  1. 01

    Task approval

    The intended use must be agreed by the appropriate task and capability owners.

  2. 02

    Information handling

    The information must be suitable for the approved platform and operating procedures.

  3. 03

    Connectivity

    The task requires a suitable approved bearer or communications route.

  4. 04

    User preparation

    Users require the correct briefing, account, phone and operating instructions.

  5. 05

    Support and ownership

    Phone issue, account management, recovery and technical support require named ownership.

  6. 06

    Security and assurance

    Classification, assurance, risk acceptance and authority to operate remain separate Defence decisions.

Listing a potential use does not approve W.O.L.F for that activity.

Next phase

What happens next?

The next phase is a controlled trial to determine whether these uses are valuable, reliable, manageable and supported by sufficient security evidence.

  1. 01

    User and commander value

    Confirm that users can complete the required tasks.

  2. 02

    Service reliability

    Test messaging, files, location and management functions during controlled activity.

  3. 03

    Phone and account management

    Evaluate issue, access removal, recovery, rebuild and reissue.

  4. 04

    Security evidence

    Collect the evidence needed for governance, risk and assurance decisions.