Matthew Collaro

I am Matthew Collaro, a systems engineer. Platform Systems Architect at Vector Stream Systems LLC, and Senior Systems Engineer at Lucid Motors. Full professional history is on LinkedIn.

I have spent my career modeling, integrating, and verifying systems in environments where unverified artifacts do not ship: commercial aircraft networks, defense systems, naval concept architectures, and production electric vehicles. That work has run through Boeing Commercial Airplanes, two defense primes, Deloitte Government & Public Services, and Parker Hannifin Aerospace.

These days I split my time between vehicle systems integration and building the tooling I kept needing and never found: a governed engineering platform that keeps requirements, architecture models, and verification evidence linked to each other instead of drifting apart.

What I work on

Model-based systems engineering. SysML behavioral and interface modeling, requirements traceability, DoDAF and UAF viewpoints, and the unglamorous governance work that decides whether a model is an authoritative artifact or an expensive drawing.

Guardrails for generated engineering artifacts. Most of my career has been in places where you cannot merge something because it looks right. I apply the same posture to LLM output: generate, then check against constraints the generator cannot route around. Schema enforcement and constraint validation, not after-the-fact review.

Toolchain integration. Getting CATIA, Cameo, DOORS, JAMA, MATLAB, and Ansys to agree on what the system actually is, and exposing that context to automated tooling through controlled interfaces rather than open-ended access.

Currently

• Senior Systems Engineer, Lucid Motors, cross-domain integration of infotainment and driver feedback systems on autonomy-enabled vehicle builds.
• Platform Systems Architect, Vector Stream Systems LLC: building MBE3Dstudio, an AI assisted systems engineering platform. Patent pending.

See the full CV, what I have built, or get in touch.

Recent writing

• Why Requirements Traceability Breaks, and What Actually Fixes It: Traceability decays on real programs for structural reasons, not because engineers are lazy. A look at the actual failure modes and what a fix has to do.
• Model Governance for SysML Programs That Have to Certify: When the model is the certification artifact rather than a picture of one, governance stops being bureaucracy and becomes the thing that makes the model trustworthy.
• Interface Control Documents Should Be Models: The ICD is where integration problems are born. Treating it as a document instead of a model is why interfaces that pass review still fail on the bench.
• Guardrails for AI-Generated Engineering Artifacts: Reviewing generated requirements and models by reading them does not scale and does not work. The check has to be structural, and the generator must not be able to route around it.
• Model Context Protocol for Engineering Toolchains: Why exposing MBSE context through typed, governed operations beats dumping exported documents into a context window, and what the interface design has to get right.

All essays are listed on the writing page.

Background

Bachelor of Science in Mechanical Engineering, University of South Florida. Georgia Tech SysML 101/201 MBSE certificate, plus coursework in software architecture and computer networks.

I started on the factory floor at Parker Hannifin writing overhaul instructions for flight control actuators, which is a useful thing to have done before you start drawing architecture diagrams. It is harder to hand-wave an interface when you have had to physically test one.