COMPAS Solutions Logo

Real Solutions. Real Impact.

Explore how we apply systems engineering to solve industry-specific challenges with measurable results.

Agrotech

Smart Greenhouse Development

Challenge: Utilization of multi disciplinar domains to develop a cost effective and robust smart Greenhouse system with cross-country teams.

Solution: We developed an MBSE-driven smart greenhouse system integrating sensors, irrigation control, and light automation, ensuring optimal growing conditions.

Technologies Used: SysML, Arduino, IoT integration, V&V strategy

Impact: Increased yield stability by 30% and enabled remote management capabilities for urban growers.

Read full case study +

Case Study: MBSE-Driven Architecture for a Multi-Disciplinary Smart Greenhouse System

Executive Summary

Developing modern, automated agricultural systems requires the seamless integration of hardware, software, and environmental science. A global client sought to build a cost-effective, robust, and automated smart greenhouse tailored for urban growers. Facing the challenge of coordinating cross-country engineering teams across multiple technical disciplines, they partnered with us to establish a rigorous, model-based system architecture from concept to prototype validation.

The Challenge: Cross-Domain & Cross-Country Fragmentation

Designing an IoT-enabled smart greenhouse demands tight synchronization between hardware structure, sensor integration, automated irrigation, and control software. The project faced two primary hurdles:

  • Multi-Disciplinary Complexity: Bridging the gaps between agronomic needs, electronic hardware, and automated software algorithms.
  • Geographical Dispersion: Aligning cross-country engineering teams to prevent design drifts, incompatible interfaces, and costly integration delays.
Our Solution: End-to-End Systems Engineering & MBSE

We acted as the foundational technical anchor, providing full Model-Based Systems Engineering (MBSE) and requirements engineering. This structured approach managed systemic complexity, allowing the client's internal teams to focus entirely on their core strengths: hardware production and software development.

ConOps & Scenarios System Capabilities Functional & Layout Analysis
V&V / Prototype Testing SW/HW Domain Dev SRATS & HRS Requirements

1. Concept of Operations (ConOps) & Capability Definition
We initiated the lifecycle by defining the Concept of Operations (ConOps) and mapping out operational scenarios for automated light, climate, and irrigation control. From these scenarios, we derived high-level system capabilities, establishing a clear, client-approved baseline before any engineering began.

2. System Analysis & Functional Layout
Utilizing SysML, we conducted a thorough system analysis to define core functions, logical interfaces, and the overall architectural layout. This step ensured all physical components and software blocks would integrate seamlessly.

3. Requirements Cascade, Domain Allocation, & EU Compliance
To translate the architecture into actionable tasks for the engineering domains, we established a strict requirements hierarchy:

  • System-Level Requirements: Documented the overarching performance and environmental criteria.
  • EU Regulatory Mapping: Directly linked system requirements to harmonized European standards to streamline future CE Certification paths (including Machine Safety and Radio Equipment directives).
  • System Requirements Allocated to Software (SRATS): Defined precise parameters for the automated control algorithms.
  • Hardware Requirements Specification (HRS): Specified the sensor thresholds, power distribution, and component constraints.

4. Verification & Validation (V&V) Strategy
Parallel to requirements definition, we authored targeted Test Cases tied directly to the system requirements. This enabled rigorous validation during the assembly of Prototype 1, ensuring the integrated system met all functional and operational benchmarks.

Technologies Used
  • Systems Engineering & Modeling: SysML, Robust Requirements Engineering
  • Hardware & IoT: Arduino prototyping, Sensor Integration (Climate, Moisture, Light Automation)
  • Regulatory & Compliance Strategy: CE Marking Alignment (Machinery Regulation 2023/1230, RED, EMC), ISO 14982 (Agricultural EMC standards verification)
  • Methodology: Full V&V (Verification & Validation) Strategy, ConOps-driven design
The Impact: Accelerated Prototyping & Enhanced Yield

By decoupling system architecture from domain-level execution, we streamlined the development pipeline for the international team, delivering significant business and technical outcomes:

  • 30% Increase in Yield Stability: Precision automation algorithms ensured optimized, predictable growing conditions.
  • Accelerated Path to EU Market Entry: By embedding CE compliance and agricultural equipment safety standards directly into the SysML model and test cases, we minimized regulatory redesign risks and shortened the timeline for market certification.
  • Seamless Global Collaboration: The SysML model acted as a single source of truth, eliminating cross-border design friction.
  • Remote Management Ready: Successfully validated IoT capabilities, empowering urban growers with remote monitoring and control.
  • Resource Optimization: Enabled the client to focus 100% of their engineering capacity on execution rather than architectural or regulatory troubleshooting.
Aerospace

Capella Integration for UAV Manufacturer

Challenge: Fragmented product development process hindered scalability and cross-team alignment.

Solution: We integrated the Capella MBSE tool into the UAV manufacturer's development pipeline, aligning requirements, architecture, and simulation models.

Technologies Used: Capella, Simulink, Polarion, MBSE process tailoring

Impact: Reduced design inconsistencies by 45% and improved traceability across engineering artifacts.

Read full case study +

Case Study: Optimizing UAV Development with Tailored Capella MBSE Integration

Executive Summary

A leading Unmanned Aerial Vehicle (UAV) manufacturer faced operational bottlenecks due to a fragmented product development process. As the engineering team scaled, a lack of cross-team alignment and disconnected engineering artifacts risked design inconsistencies. We successfully integrated the Capella MBSE (Model-Based Systems Engineering) tool into their development pipeline, harmonizing requirements, architecture, and models to ensure seamless scalability.

The Challenge: Disconnected Pipelines & Scalability Bottlenecks

In complex aerospace and defense engineering, alignment is everything. The client's existing product development lifecycle suffered from fragmentation. Without a unified source of truth, the team faced:

  • Siloed engineering artifacts across requirements and architectural models.
  • Traceability leaks that risked design inconsistencies during rapid scaling.
  • Cross-team misalignment on complex system interfaces and workflows.
Our Solution: A Strategic, Human-Centric MBSE Implementation

Rather than just delivering tools, we engineered a comprehensive transformation process divided into three distinct phases:

1. Capability Building & Cultural Alignment
We initiated the project with targeted peer-to-peer lectures to establish a deep, shared understanding of the Capella modeling environment across the client's engineering teams, ensuring rapid tool adoption.

2. Deep-Dive Gap Analysis
We analyzed the client's existing "way of working" to identify critical process leaks, trace pathway gaps, and architectural inconsistencies.

3. Tailored Workflow Engineering & Automation
After mapping the gaps, we presented a matrix of strategic solutions. The client selected a preferred path focused on deep pipeline integration:

  • Unified Lifecycle Management: Coordinated the implementation of robust configuration and documentation management workflows.
  • Toolchain Synchronization: Integrated Capella with Jira and Git, ensuring models, requirements, and tasks evolve in lockstep.
  • Process Tailoring & Automation: Developed targeted automation scripts to streamline data exchange, drastically reducing manual engineering overhead.
Technologies Used
  • MBSE Environment: Capella
  • Lifecycle & Version Control: Git, Jira
  • Methodology: Custom MBSE process tailoring & automation
The Impact: A Single Source of Truth

The integration of Capella transformed the client's engineering culture from document-centric to model-based, delivering measurable operational improvements:

  • Eliminated Design Inconsistencies: Bridged the gap between high-level requirements and physical architecture.
  • End-to-End Traceability: Established clear, unbroken trace pathways across all engineering artifacts.
  • Future-Proof Scalability: Equipped the development team with a repeatable, automated pipeline ready to handle next-generation UAV variants.

Ready to transform your system development?

Get in touch with us today →