Case Study: Standard Work 2.0™ at a Defense ATE Contract Manufacturer

The client is a contract manufacturer of automated test equipment, ATE, and fixtures for highly regulated markets, including the Defense Industrial Base, in the greater Boston area. Their machines are the ones that qualify other manufacturers' hardware: test stations, fixtures, and the harnessing between them, built to print for programs that tolerate zero ambiguity.

Garrett Partridge LLC entered as Operations Architect and fractional COO to run the Standard Work 2.0™ initiative: the operating method that installs documented, followed, measured standard work across the floor and the systems that feed it, so the way work actually happens and the way the systems say it happens are the same thing.

The pressure was concrete. An extensive multi-million dollar production backlog. A major tier-1 defense prime contractor's on-time-delivery scorecard sitting at a critical underperforming rate. An assembly bench halt rate of 25 percent, meaning one build in four stopped mid-assembly waiting for a part, an answer, or a drawing. And a business run on disconnected, tribal-knowledge spreadsheets that no auditor and no prime could trace.

The engagement drove three things at once: rapid digital transformation, defense-grade data compliance, and tech-stack decisions aimed directly at that backlog. The four initiatives below are one program, not four projects.

The engagement opened with an audit of the client's existing IT infrastructure, because the fastest money in a turnaround is the money already leaving the building. The audit surfaced two decisions. Both were identified and executed as achieved cost avoidance, and they are the two hard-dollar figures in this study.

First, the migration that got halted. The client was headed into an expensive, inefficient legacy migration to an on-premise Microsoft Project Server. I stopped it and pivoted the company to modern, FedRAMP-compliant SaaS platforms, Smartsheet Gov and OnePlan among them. FedRAMP is the federal government's authorization baseline for cloud services, which matters here because a defense supplier's tooling has to clear that bar anyway. The pivot bypassed over $75,000 in migration fees and landed the company on platforms that already sit inside the compliance posture it needs.

Second, the license bottleneck. The client's ERP ran on 25 floating licenses, and the shop floor was queuing behind the front office to get one. The obvious fix, buying more licenses, carried a price of roughly $55,000 a year, forever. I built a custom data bridge instead: querying the SQL database directly at the server level through SSRS, the reporting service the client already owned, and surfacing the results in low-cost tracking overlays on the floor. Shop floor technicians gained 100 percent data visibility while consuming zero ERP licenses. The annual spend was avoided outright.

The client holds highly sensitive defense contracts, which means ITAR technical data and Controlled Unclassified Information, CUI, live in its systems. The usual response is to slow everything down and wrap the whole enterprise in the audit scope. I engineered a Data Border Strategy instead, built to protect the contracts while the floor keeps its speed.

The architecture divides the enterprise into two sides. The high side is a secure sovereign enclave, Microsoft 365 GCC High, the PDM system, and the ERP, and it holds the ITAR blueprints and the CUI. The low side is a visual scoreboard layer for high-speed project portfolio management: schedules, statuses, and priorities the floor and the front office run on all day.

Two controls make the border real rather than aspirational. A zero-file-upload policy acts as a strict behavioral firewall on the commercial tools: no engineering models and no CUI ever land on low-side servers, which sharply shrinks the CMMC 2.0 assessment scope, because systems that never touch CUI stop being assessment targets. And an obfuscated pivot identifier schema, a non-sequential primary key system of my own design, links high-side engineering data with low-side floor dashboards without exposing proprietary customer names or military program details on the side where they would count as a spill.

A backlog is not a demand problem. It is a flow problem, and this one was measured publicly: the tier-1 prime's on-time-delivery scorecard graded the client at a critical underperforming rate every month. The workflow engineering in this initiative targets the scorecard directly, because that scorecard is the document the prime's supply chain managers read before awarding the next package of work.

Underneath the backlog sat the real disease: disconnected spreadsheets holding tribal knowledge, each one a single point of failure with a person's name on it. The replacement is an automated, enterprise-wide digital thread, a connected data spine where a fact entered once flows to every record that depends on it.

The build uses a complete cross-sheet relational database architecture on FedRAMP-authorized tools. The system generates unique project IDs automatically, copies rows between sheets without human hands, and uses data mesh tooling to push dynamic information back to the original records, flipping project statuses with zero manual copy-paste. Every status a manager reads is the status the floor actually produced.

The roadmap runs four phases: integrating the core ERP, Smartsheet Gov, and OnePlan into an Azure Government SQL Data Lake. That architecture is the groundwork for a working digital twin of the factory, and for predictive orchestration on top of it, using Microsoft Copilot to run real-time resource simulations, such as re-leveling the factory floor the moment a key technician calls out. The twin is a roadmap deliverable, stated here as the plan it is, with the foundation phases in build now.

Read the four initiatives as one system and the pattern is visible. The cost line funds the build. The data border makes the build compliant. The floor cadence makes the build move product. The digital thread makes the build permanent, so it holds after the fractional engagement steps back. That is what Standard Work 2.0™ means in practice: the standard is in the workflow, not in a binder.

The engagement is live. The two software decisions are executed cost avoidance. The scorecard, halt-rate, and digital twin outcomes are targeted and anticipated, in the client's own words, with close-out expected within the next two quarters. This study will be updated when it closes.

The full method behind the program is documented at Standard Work 2.0, and the engagement models this work runs under, the 30-Day Operational Triage and the Fractional COO retainer, are laid out plainly. Every engagement is held under NDA, which is why this client is named by what they build, not by who they are.