Defense Operations & Engineering Solutions (DOES)
DOES and LTS Use Model-Based Systems Engineering and Nondestructive Testing to Accelerate Defense and Nuclear Technology Transition

In aerospace, defense, nuclear, and other mission-critical industries, the “Valley of Death” is not a mystery. It is the predictable gap between a technically plausible idea and a fieldable capability, where requirements are incomplete, verification is deferred, manufacturability is assumed, and the evidence package is too weak to survive program scrutiny. The physics may work. The transition often does not.

Defense Operations and Engineering Solutions (DOES) and Leak Testing Specialists (LTS) are building a different transition path: a coordinated set of university collaborations that shift left the hard parts of deployment by integrating Model-Based Systems Engineering (MBSE) and industrial-grade nondestructive testing (NDT) into research and development earlier than most teams can tolerate. We are engaging with Florida Institute of Technology, Temple University, Yale University, and Boston University to produce publishable, sponsor-grade work products and evidence packages that reduce risk, shorten cycle time, and make prototypes defensible.

This is not partnership theater. It is an evidence-based program.

Compliance note for readers: public communications focus on non-sensitive methods, evidence packaging, and transition process. We do not disclose export-controlled information, customer-sensitive operational details, or proprietary build-to technical data.

Why this matters now: Mission assurance is becoming the bottleneck
Modernization is accelerating, but assurance has not kept pace. Autonomy, distributed power, and advanced manufacturing expand the attack surface for failure modes: seal integrity, pressure boundaries, quality escapes, latent defects, and unverified interfaces. In regulated and high-consequence environments, “interesting prototypes” do not transition. Audit-ready evidence does.

Our operating thesis is blunt: in regulated or mission-critical systems, evidence is the product. MBSE provides the structure. NDT provides the ground truth. Together, they produce the verification backbone required for real adoption.

What MBSE and NDT integration means in practice

This is not MBSE as a buzzword. It is MBSE as a production system for transition artifacts. Across the coalition, we are creating tangible outputs that a program manager, prime contractor, or regulator can review without guessing.

Examples of the artifacts we prioritize include:

• Operational scenarios and concept of operations framing, with clear assumptions

• Requirements hierarchies, interfaces, and measurable acceptance criteria

• Verification crosswalks that connect requirements to tests and evidence

• Test procedures and repeatable evidence package templates

• Data dictionaries and controlled datasets suitable for review and reuse

The goal is simple: reduce ambiguity early, so teams do not discover late that the “requirements” were opinions and the “test plan” was a wish.
Florida Institute of Technology: prototype velocity with real constraints

Florida Institute of Technology brings speed and hands-on prototyping. We structure the work around capstone-level prototypes and demonstrators that force clarity on real constraints such as maintainability, testability, and failure modes. The goal is to turn promising concepts into review-ready artifacts with clear requirements, verification steps, and defensible evidence.

A common academic pitfall is treating sealing and integrity as afterthoughts. LTS corrects that by injecting industrial NDT discipline into the design cycle. Students learn a career-saving lesson early: “waterproof” is not a requirement. Verifiable integrity is. When integrity evidence is designed in rather than bolted on, prototypes become defensible assets for further maturation, not disposable experiments.

Temple University: publishable, sponsor-grade outputs with execution discipline
Temple University strengthens the pipeline by supporting publishable, sponsor-grade work products that translate well into proposal and program environments. The focus is practical: disciplined documentation, traceability, and workflows that can be reviewed, repeated, and defended. The value of academic work in this context is not novelty alone. It is producing artifacts that survive scrutiny and reduce downstream rework.

Boston University: the business physics of resilience and reshoring
Great engineering still fails if it cannot scale, sell, or survive procurement reality. Boston University supports the commercialization layer: the logic that turns evidence into something a buyer will purchase.

Our Boston University aligned work addresses industrial resilience challenges where the cost of quality drives offshoring and fragility. The thesis is practical: automation and verification discipline can reduce labor-heavy quality burdens and improve competitiveness when quality requirements are non-negotiable.

By modeling how automated inspection and integrity verification change cost, risk, and cycle time, the collaboration generates outputs that matter to decision makers: which workflows to automate, what the return looks like, and how evidence products shorten qualification timelines. This is the difference between a promising tool and an inevitable purchase.
Yale University: independent verification and validation that builds credibility
In systems engineering, grading your own homework is a predictable failure mode. Yale’s role is independent peer review, independent verification, and validation support. They stress test assumptions, methods, and failure modes before projects scale.

This matters because serious transition partners do not fund optimism. They fund credible evidence and repeatable process. Independent scrutiny improves technical quality, strengthens verification logic, and increases trust in the outputs produced by the pipeline.

University participation reflects educational and research collaboration and does not constitute institutional endorsement of commercial products.

How DOES and LTS make the coalition coherent
The coalition works because the roles are unambiguous.

DOES is the systems integrator. We build the architecture, maintain the digital thread, and ensure requirements, interfaces, and verification plans remain connected as prototypes evolve. We translate academic output into sponsor-grade deliverables that a program office, prime contractor, or regulated customer can actually use. This includes disciplined requirements engineering, test planning, configuration control, and traceability.

LTS is the assurance backbone. As President of LTS, my focus is to ensure theoretical designs are grounded in containment reality: test procedures, acceptance criteria, calibration discipline, and evidence packages that stand up to scrutiny. Across nuclear, aerospace, maritime, and regulated manufacturing, integrity boundaries are where theory meets consequences.

Where DOES provides the structure, LTS provides the proof.

What success looks like in the next 12 to 18 months
We operate in a concept-to-prototype window, with prototyping and testing maturing over the next 12 to 18 months. The near-term goal is not hype. It is reviewable proof.

Deliverables are structured to include:

• A small set of pilot-grade demonstrators that enforce real constraints early

• Standardized test procedures and acceptance criteria for integrity boundaries

• Evidence package templates suitable for stakeholder review

• Requirements to test traceability artifacts that reduce ambiguity

• Sanitized datasets and documentation that support repeatability and scale

This is how you bridge the Valley of Death: not with more slides, but with artifacts that make transition easier than non-transition.

Workforce development: the hidden deliverable
The defense industrial base faces a talent squeeze hiding inside a retirement cliff. We need engineers who can model and validate, who understand that a computer-aided design model without evidence is an opinion.

By embedding MBSE discipline and NDT reality into university work, we are building a pipeline of graduates who think in lifecycle terms: verification, sustainment, configuration control, and mission assurance. That workforce is as strategic as the technology.

The future belongs to the teams that can ship credibility, not just concepts. DOES and LTS intend to do exactly that.