Background
General Dynamics is one of the largest defense contractors in the United States, with operations spanning ground combat systems, shipbuilding, aerospace, and information technology. Their manufacturing environments — producing military vehicles, combat systems, and naval vessels — operate under regulatory, security, and accountability requirements that fundamentally shape what technology is and is not permissible.
This case study covers a VX-Olympus deployment at a General Dynamics manufacturing facility focused on production readiness: specifically, the operational challenges of maintaining equipment visibility, reducing unplanned downtime, and managing government property accountability in a controlled manufacturing environment.
Note: Specific facility identifiers, classified production programs, and technical details that are security-sensitive have been omitted. The operational IoT challenges and VX-Olympus deployment approach are described at an appropriate level of detail.
The Challenge
Defense manufacturing environments present a specific set of constraints that commercial IoT platforms routinely fail to address:
Constraint 1: Data Cannot Leave the Facility
Cloud-connected IoT platforms are categorically excluded from most defense manufacturing environments. ITAR (International Traffic in Arms Regulations), contractual DFARS clauses, and facility security protocols all restrict data handling.
An IoT platform that requires cloud connectivity for core functionality is not a viable option. The platform must run entirely within the facility’s controlled network environment.
Constraint 2: Government Property Accountability
Equipment used in defense manufacturing that is government-furnished property (GFP) or government-owned equipment requires specific accountability documentation: current location, current status, maintenance history, and chain of custody. Manual property accountability processes are labor-intensive, error-prone, and inadequate for large equipment inventories.
The DoD’s property management requirements for government property at contractor facilities are enforced through Property Management Systems Approval (PMSA) processes — and documentation gaps create compliance risk that extends beyond operational issues to contract performance.
Constraint 3: Standard Industrial Complexity
Beneath the defense-specific constraints, the operational challenge is the same as any large manufacturing environment: mixed equipment vintages, heterogeneous communication protocols, reactive maintenance patterns, and limited operational visibility across production shifts.
General Dynamics’s facilities include equipment ranging from state-of-the-art CNC machining centers with full OPC-UA connectivity to legacy manufacturing equipment from the 1980s and 1990s that has no digital output at all.
The Solution
On-Premises Deployment
VX-Olympus was deployed entirely on-premises within the facility’s controlled network environment. No outbound data connectivity. No cloud dependency for any core platform function.
The deployment runs on the facility’s existing server infrastructure. Updates and maintenance are performed through controlled, scheduled access. The platform operates in an environment with no internet connectivity to external Viaanix systems.
This architecture is a fundamental requirement, not an accommodation. VX-Olympus’s ability to run on-premises without feature compromise was the primary technical qualification for the deployment.
Equipment Monitoring
Legacy equipment connectivity: The facility’s oldest equipment — relay-logic-controlled presses, manual machine tools, and older automated systems — connected through current transformer monitoring on motor feeder circuits. Running status, fault status, and energy consumption were derived from the electrical signatures rather than from control system data. No equipment modification required.
Mid-generation equipment: Equipment with PLCs but without modern communication interfaces connected via discrete I/O — running status, cycle complete, and fault relay contacts wired to industrial IoT input gateways. Contact I/O is universal across equipment vintages.
Modern equipment: CNC machining centers and newer automated systems with OPC-UA or Modbus TCP connectivity provided full process data: spindle speed, feed rates, actual vs. commanded positions, alarm registers, production counts.
All three connectivity paths fed into VX-Olympus’s protocol layer — each device reported to the same data model regardless of the underlying connection method.
Government Property Accountability Integration
VX-Olympus device records were structured to serve dual functions: operational IoT monitoring AND property accountability tracking.
Each piece of government property received:
- A VX-Olympus device record with the government property tag number as the primary identifier
- Physical location tracking via RTLS (BLE tags at zone level) within the facility
- Maintenance history logging through VX-Olympus work order records
- Transfer documentation when equipment moved between facility areas or went off-site for calibration/service
The VX-Olympus property record did not replace the formal government property management system — it fed into it via API export, providing real-time location and status data that enriched the property management system’s records with operational context.
Property audits — verifying that government property was present, in the expected location, and in the recorded condition — transitioned from a physical inventory walk (labor-intensive, conducted 1–2 times per year) to a real-time verification process (RTLS location confirms presence; VX-Olympus operational status confirms condition).
Multi-Shift Visibility
The facility operates three shifts. Shift handoffs were historically a verbal process supplemented by written notes — the outgoing shift lead briefing the incoming lead on equipment states, any issues that occurred, and any known concerns for the coming shift.
VX-Olympus shift-end reports generated automatically: all equipment events in the past 8 hours, active alerts at shift end, maintenance actions completed, and production counts by line. The incoming shift lead started with a complete documented picture of the shift’s events rather than a verbal briefing that may or may not include every relevant detail.
The Results
Equipment Visibility Across Shifts
Active downtime events now reach maintenance on a sub-3-minute timeline regardless of which shift is operating. The shift supervisor’s dashboard shows current production floor status from their office rather than requiring a floor walk to establish situational awareness.
The RTLS component of the deployment provided a specific benefit that was not fully anticipated pre-deployment: quick location confirmation for equipment that was temporarily moved for tooling setups, maintenance activities, or production floor reorganizations. In a large facility, “where is the calibration fixture for Station 12” is a real question that previously required a floor walk or a phone call to the maintenance lead.
Government Property Accountability Efficiency
The labor associated with scheduled property inventory audits dropped significantly. The pre-deployment process required 2–3 days of property team labor to physically locate, verify, and document each piece. Post-deployment, the location data from VX-Olympus RTLS provided a real-time starting point.
The facility’s property management officer estimated that audit preparation time dropped by approximately 65% — from 2–3 days to less than 1 day — with higher accuracy and a complete electronic audit trail.
Maintenance Response Improvement
The pattern of maintenance response improvement mirrored other factory deployments: mean time to maintenance notification dropped from 20–35 minutes (time from failure to maintenance team aware) to under 5 minutes in most cases.
Specific to the defense manufacturing context: maintenance work orders generated from VX-Olympus included the government property record number for government equipment — creating the documentation chain between equipment failure, maintenance response, and property accountability record that compliance requirements expect.
The Deployment Challenge: Security Review
The most significant deployment challenge was not technical — it was the facility security review process. A new IT system introduced to a controlled manufacturing environment goes through a review process that commercial deployments do not:
- Platform architecture review for data handling and potential exfiltration vectors
- Network traffic analysis requirements to verify no unauthorized outbound communication
- Vendor security documentation and CMMC (Cybersecurity Maturity Model Certification) alignment review
VX-Olympus’s on-premises architecture — no cloud dependency, no external network connectivity required — simplified the security review considerably. The review still required 6 weeks of documentation exchange and technical review sessions with the facility’s security team. This timeline should be factored into any defense manufacturing deployment plan.
Conclusion
General Dynamics’s VX-Olympus deployment demonstrated that industrial IoT capabilities applicable to any manufacturing environment are achievable within the constraints of a controlled defense manufacturing facility — when the platform can genuinely operate without cloud connectivity and is architected to run on-premises from day one.
The deployment addressed operational challenges (equipment visibility, maintenance response, shift continuity) and compliance challenges (government property accountability documentation) through a single platform that met the facility’s security requirements.
For defense manufacturers evaluating IoT deployments, the starting question is not “which IoT platform is best” — it is “which IoT platforms can actually operate in our environment.” VX-Olympus answers that question affirmatively.
Talk to our team about an industrial IoT deployment for defense manufacturing or other controlled environments.