Naval Supply Systems Command Weapon Systems Support (NAVSUP WSS) described the work in a Defense Visual Information Distribution Service (DVIDS) story by Brian Jones, published November 20, 2026. Everything below about the workflow and its results comes from that account. I found no independent audit of the numbers.
What changed: the vendor stopped running the refresh
Under earlier contracts, the 36-month replacement cycle for leased Navy computers was run by commercial contractors. According to NAVSUP WSS, the prime vendor brought project managers who set schedules, tracked staging and ran the physical rollout over six to eight weeks.
The updated Navy End User Hardware contract ended vendor-led logistics. NAVSUP WSS says more than 100,000 Navy workstations still need replacing each year. Unboxing, validating, staging, scheduling and distributing the machines now falls to each command's activity customer technical representative (ACTR) team.
At NAVSUP WSS, that meant roughly 2,500 seats. The team also faced a hard rule. Once a new machine arrives, technicians have 30 days to deploy it before the user's old computer is permanently deactivated from the network. That is a Navy operating condition, not a general Windows or Microsoft 365 rule.
Summary: The contract change moved the project management work from the vendor to local IT staff. The 30-day cutoff made missed appointments costly.
The first attempt: Forms and forced scheduling
Ryan Hinchcliff, a NAVSUP WSS ACTR, said early workarounds used Microsoft Forms to poll availability and then assigned people to calendar slots. He put the success rate at "a mere 60% to 80%". He also said the team was stuck chasing no-shows, handling email and troubleshooting backups by hand.
Assigning appointments to busy people makes the technician's calendar tidy and gives the user no say in it. The reported no-show problem fits that pattern.
The rebuilt pipeline
Bookings for user-selected appointments
The team replaced assigned slots with Microsoft Bookings. Each user gets an automated link and picks a time inside the 30-day window. Per Hinchcliff, a user whose schedule changes can reschedule alone, and that change updates the ACTR master spreadsheet hosted in Microsoft Teams. NAVSUP WSS says the system also limits how many users can register for one slot and sends reminders as appointments approach.
Microsoft's documentation describes Bookings as a web-based booking page integrated with Outlook, and says notifications are meant to reduce no-shows. That makes the pattern plausible. It does not confirm how the Navy configured it, or how the Teams spreadsheet update is wired up.
Power BI Dataflows and Word Mail Merge for the back end
On the back end, the team uses Power BI Dataflows to pull inventory data from several systems and combine it with local asset logs. Hinchcliff said the system cross-references multiple internal asset databases to confirm that the right machine is mapped to the right user.
The validated data then feeds a Word Mail Merge template. It prints box labels showing the user's name, asset serials, operating system and assigned Contract Line-Item Number (CLIN) software. The same data produces daily checklists with exact Navy email addresses, which the team says removes typing errors during endpoint configuration.
This is the least glamorous part of the setup, and probably the most useful. A mislabeled box means a wrong-machine handoff and a repeat visit.
SharePoint and OneDrive for pre-appointment backup
Before the appointment, users are sent to SharePoint Online instructions on backing up local files to OneDrive. Christopher Chipps, another ACTR, said OneDrive syncs continuously in the background on Flank Speed, so users arrive with profiles already backed up.
I'd treat that last claim carefully. The source does not say what the backup covers, how sync status is checked, or whether restores are tested. Teams doing this elsewhere will want those answers before relying on it.
Summary: Each tool has one job. Bookings handles scheduling, Dataflows and Mail Merge handle asset accuracy, and SharePoint and OneDrive handle data preparation.
Reported results
NAVSUP WSS says appointment turnout rose from 60% to 99%. It also says the command consistently meets the 30-day retirement window without workstations dropping off the network.
Caveats:
- The story gives no measurement period, appointment count or definition of "turnout".
- It does not describe a controlled comparison.
- The figures are self-reported by the command.
The team is now consulting with and training other Navy Echelon III commands on the Power BI pipelines, Bookings and Teams deployment hubs. The story names none of those commands and gives no adoption count.
Not a turnkey recipe
The story contains no configuration steps, Windows versions, imaging or enrollment details, security controls, dataflow design or permission model. Anyone copying the idea should fill those gaps from their own environment.
Product availability matters too. Microsoft's Teams admin documentation is not part of my search results, but the Teams admin guidance supplied with the story says the Bookings app in Teams is not supported in GCC, GCC-High, DoD and sovereign clouds. That does not mean the Navy's workflow is impossible. NAVSUP WSS says it used Bookings within Flank Speed, but the story doesn't say which Bookings surface (the Teams app, the web app or something else) or what approvals were involved. Commercial tenants have fewer constraints. Government tenants should check their own cloud's feature list first.
Flank Speed background
Public Navy material from 2021 describes Flank Speed as the Navy's Microsoft 365 environment. It gives users access to one terabyte of OneDrive storage, Teams and the M365 productivity suite. Navy materials also list Power BI among the tools available in the environment. That supports the context for the NAVSUP WSS workflow, though not its specific configuration.
Takeaways for IT teams
- Let users pick their slot. The reported gain came from replacing forced assignments with self-service booking inside a fixed window.
- Validate asset-to-user mapping before the box moves. Labels and checklists generated from reconciled data reduce handoff errors.
- Prepare data before the visit. Pushing file backup ahead of the appointment shortens the desk-side time.
- Document the deadline. A hard cutoff, like the Navy's 30 days, is what makes this much automation worthwhile.
- Verify product availability first. Bookings surfaces differ by cloud and license.
The story is a modest success report rather than a technical blueprint. Still, it shows what happens when a contract change hands logistics to a small internal team: they built the process out of Microsoft 365 apps the Navy already had.
References
- NAVSUP WSS Technical Representatives Use Flank Speed to Keep Hardware Refreshes on Track - DVIDS DVIDS · Fri, 20 Nov 2026 12:32:00 GMT
- Microsoft Bookings | Microsoft Learn learn.microsoft.com
- Manage the Bookings app in Microsoft Teams - Microsoft Teams | Microsoft Learn learn.microsoft.com