We signed a Memorandum of Understanding with Poelis at Space Meetings Veneto last week. I want to explain what's behind it, because "two companies sign MoU" is not normally a sentence worth reading.
The honest version is this: we had already built the integration before we signed anything. A shared customer needed a live connection between Poelis's design data environment and Connektica's test execution platform. Our engineer Flavien built it in eight hours using the Poelis Python SDK. It worked. The customer got 30 to 60 minutes of manual AIT validation removed per cycle, and version consistency enforced automatically at the sequence level instead of by the engineer doing their best under schedule pressure.
The MoU is what happens after you've built something together and both decided it's worth going further.
The product side is the most concrete part. Poelis structures and versions design data across the engineering lifecycle. Connektica runs assembly, test execution, and quality control in a single environment. The gap between those two things is a real problem for aerospace and defense manufacturers: design data and test execution living in separate systems, with engineers manually bridging the two on every cycle. The API integration we built closes that gap at the sequence level. The MoU commits both companies to deepening that integration as we bring it to more customers.
The go-to-market side is straightforward. We'll work shared leads together, run joint webinars, and build content around real customer deployments. The first webinar is June 25th. If you're running AIT and the design-to-test fragmentation problem sounds familiar, that's the right place to start.
I spent time at Space Meetings Veneto talking to engineering teams across the space and defense supply chain. The fragmentation problem is not specific to one customer or one product type. Design data lives somewhere. Test execution lives somewhere else. The connection between them is usually a human with a spreadsheet and a deadline.
The integration we built with Poelis is one answer to that. It won't fit every stack, but the architecture is open: API-based, decoupled, built so both platforms stay independent. That's how integrations should work, and it's rarely how they do.
Michele Genoni, who co-founded Poelis after years running AIT at Airbus Space on telecommunications satellites, put it well when we were building the first integration: the mission is to close the gap between where the source of truth lives and where the engineer actually works. That's what we're both trying to do. The MoU is just the formal version of that shared direction.
June 25th webinar with Poelis. We'll walk through the integration architecture, the customer deployment, and what it takes to connect design data to test execution in practice. Registration details coming soon.
In the meantime, the full case study is here.