System configurations
Deployments adapted to context, environment, and monitoring objectives.
The Microdeep platform is deployed in configurations defined by operational constraints rather than fixed product variants.
Each configuration is built on the same core platform and adapted to usage conditions, integration requirements, and long-term monitoring goals.
Laboratory configuration
Designed for controlled environments, development work, and validation studies.
Typical characteristics:
• Bench-top or laboratory installation
• Controlled environmental conditions
• Flexible workflows for experimentation and method development
• Direct access to raw data and intermediate outputs
This configuration is commonly used during early evaluation phases, research programs, or when validating monitoring strategies prior to wider deployment.
Industrial / process configuration
Designed for integration into operational environments and continuous workflows.
Typical characteristics:
• Enclosed or cabinet-based installation
• Continuous operation alongside industrial processes
• Robust operation under variable conditions
• Integration with existing monitoring or control systems
This configuration supports ongoing surveillance, process optimization, and early detection of deviations in production or treatment lines.
Outdoor / remote configuration
Designed for autonomous operation in field or remote environments.
Typical characteristics:
• Ruggedized enclosure
• Autonomous operation with limited human intervention
• Remote access and monitoring
• Long-term deployment in variable environmental conditions
This configuration is used for surface water monitoring, distributed observation networks, or sites where access is limited or intermittent.
One platform, multiple deployments
All configurations are based on the same Microdeep platform architecture.
Differences lie in enclosure, autonomy level, integration, and operational constraints — not in measurement principles.
This ensures:
• continuity across deployments
• comparable datasets over time
• smooth transition from pilot to scaled deployment
Configuration definition
Final system configurations are defined jointly during pilot or deployment phases, based on:
• monitoring objectives
• environmental constraints
• operational requirements
• data integration needs
This approach avoids premature specification and ensures that each deployment remains aligned with its intended use.
Next steps
If you are considering a pilot or deployment, we can help assess the most appropriate configuration for your context.