openIndu Community Roadmap
Build together: share field knowledge, create reusable engineering assets, and connect tools through verifiable practice
From Shared Knowledge to Validated Practice
These stages describe our community's development direction, not release dates or completed milestones. Repository releases, tests, and validation records show actual progress.
Share Field Knowledge
Bring practical problems into the forum. Record context, constraints, process knowledge, and validation methods so others can contribute and review.
Build Reusable Assets
Turn reviewed experience into guides, templates, mappings, and engineering workflow artifacts that can be reused and checked.
Connect Project Tools
Develop collaboration across vision, engineering workflows, connectivity, and industrial data, with explicit interfaces and capability boundaries.
Validate Real Scenarios
Use reproducible cases to check tool collaboration. Share supported versions, results, and limitations before extending a capability claim.
Explore the openIndu Projects
Forum + openIndu-vision + openIndu-studio + openIndu-cim & openIndu-platform + PLC Experiment
Forum(Content)
Community knowledge across industrial control, automation, manufacturing processes, and industry observations. Topics can remain open as evidence evolves.
Industrial Vision(openIndu-vision)
Exploration of cross-camera, cross-algorithm inspection and workflow orchestration. Support depends on repositories, versions, and validation records.
Engineering Assets(openIndu-studio)
Engineering workflows around electrical modules, diagrams, BOM, I/O planning, and PLC/HMI intermediate artifacts.
Connectivity and Data(openIndu-cim + openIndu-platform)
Connect equipment, manufacturing systems, and industrial data for collection, traceability, and analysis. Protocols are validated per driver, version, and environment.
Open Control Experiment(PLC Experiment · E0)
RK3588 + openEuler + RTOS/real-time Linux + EtherCAT exploration. Real-time, HIL, endurance, and fault-recovery evidence is not complete.
How the Directions Work Together
📐 From Knowledge to Engineering Assets
1️⃣ Record：The forum preserves field context, constraints, validation steps, and known boundaries
2️⃣ Review：Reviewed experience can become guides, templates, mappings, or experimental cases
3️⃣ Reuse：Tools reuse those assets only within explicit status and evidence boundaries
🧭 Tool Collaboration
openIndu-vision：Visual inspection and workflow exploration
openIndu-studio：Organises engineering assets and generation workflows
openIndu-cim + openIndu-platform：Connects equipment, manufacturing systems, and industrial data
🧪 Experimental Boundary
PLC Experiment remains Experiment / E0. It is not production-ready without real-time, HIL, endurance, and fault-recovery evidence.
How We Communicate Maturity
| Dimension | Common misunderstanding | openIndu approach |
|---|---|---|
| Project map | A direction means a finished product | Direction, status, and evidence are shown separately |
| Forum articles | Content coverage means delivery capability | Content is labelled as Content, without delivery claims |
| Repositories | Code means engineering validation | README, releases, tests, and limitations define status |
| Licensing | One license describes the whole ecosystem | Each repository LICENSE and dependency obligation is authoritative |
| Soft PLC | An experiment can replace a hardware PLC | Experiment / E0 and the next evidence gates are explicit |