Separator Control Challenge

The description states that Separator Control Challenge is an interactive browser-based process control game. It involves:

• Tuning two PID controllers:
  • Total liquid level controller (operates oil outlet valve)
  • Oil/water interface controller (operates water outlet valve)

• A 3D visualization of a separator with animated inventories and piping
• Deterministic scenarios including disturbances like feed changes, slugs, and sensor noise
• Live process trends, alarms, and performance metrics
• Scoring based on error minimization, stability, safety, and valve efficiency

The simulation runs client-side using fixed-step integration and Web Workers. It does not require external dependencies or runtime AI inference.

Inference The product is a self-contained educational tool designed to demonstrate control theory principles in an engaging way.

The author claims the project was inspired by doctoral research on oil-well operations and aims to make industrial process control more intuitive through visual, interactive learning.

Key claims:

• Industrial control problems can be turned into “engaging, visual, and playable web experience”
• The challenge is based on a technically meaningful control problem
• It provides an accessible way to understand PID tuning behavior

Inference This is positioned as an educational tool for engineers or students interested in process control. It does not claim commercial viability or market traction.

The description states that the project was built from personal academic experience and aims to teach industrial control concepts through simulation.

No explicit customer segments are mentioned, but inferred targets include:

• Engineering students
• Practicing engineers seeking refresher training
• Educators in process control or automation
• Developers interested in educational simulations

Inference The ICP is likely a niche audience within engineering education and professional development. No evidence of broader commercial targeting.

There is no mention of any business model, pricing strategy, monetization plans, or revenue streams.

The project is described as a hackathon submission with no indication of commercial intent or product-market fit beyond educational utility.

Inference No evidence of a business model or pricing structure; the tool appears to be non-commercial in nature.

The author states that the application was built using:

• Next.js, React, TypeScript
• Three.js, React Three Fiber, Drei for 3D rendering
• Recharts for data visualization
• Web Workers for simulation logic
• Vitest and Playwright for testing
• GPT-5.6 and Codex for development assistance

The simulation includes:

• Coupled liquid inventories with volume balance equations
• PID controllers with practical behaviors (output limits, anti-windup, derivative filtering)
• Deterministic scenarios with fixed seeds
• No runtime dependencies or backend services

Inference The technical stack suggests a modern frontend-heavy approach with strong focus on simulation fidelity and performance. AI was used for implementation but not in the final product.

There is no evidence of traction, users, customers, or adoption beyond the author’s own development effort.

The project is described as a hackathon submission and lacks any indication of deployment, usage metrics, or feedback from users.

Inference No signs of market traction or product maturity. The tool exists only in prototype form.

No direct competitors are named or described. However, the author references the general field of industrial control education and simulation tools.

The project is positioned as a simplified, interactive alternative to traditional static textbooks or complex engineering software.

Inference It competes within a niche space of educational simulations for process control. No evidence of existing players or competitive positioning beyond self-description.

• Lack of commercialization: The tool is described as a hackathon project with no indication of monetization or market strategy.
• Limited scope: Only one developer, and the simulation is reduced-order — not suitable for real-world applications.
• No external validation: No third-party reviews, user feedback, or performance data are provided.
• AI dependency in development but not runtime: While AI helped build it, there’s no indication of how this impacts long-term maintainability or scalability.

Inference The project is experimental and educational in nature. It does not appear to be a viable commercial product or scalable solution.

1. What was the intended audience for this tool beyond personal use?
2. Has there been any external testing or feedback from educators or engineers?
3. Are there plans to expand beyond the current scope (e.g., additional control loops, more complex systems)?
4. Is there any interest in integrating with formal education platforms or LMS tools?
5. How would you envision monetizing this if at all?