Skip to main content

🚀 Project Vision

How it started, how it grows, and where we want to go​

🌱 How It Started​

The winccoa-tools-pack project began with a simple observation shared by many WinCC OA developers and QA engineers:
the ecosystem lacked modern tooling, automation, and developer‑friendly workflows.

Everyday tasks in WinCC OA projects often required:

  • manual checks
  • repetitive QA steps
  • ad‑hoc scripting
  • inconsistent workflows
  • custom solutions hidden in team silos

There was no central place for:

  • repeatable CI/CD integrations
  • linting concepts
  • reusable automation blocks
  • standardized project management
  • shared best practices

The project started as an attempt to explore ideas for better tooling — nothing official, nothing commercial — just a personal wish to improve the daily life of WinCC OA developers.

🌿 How It Grows​

What began as a personal idea has slowly grown into a collaborative toolkit ecosystem.

Several topics emerged naturally:

  • CI/CD workflows for GitHub Actions, Jenkins, and Azure DevOps
  • Shared pipelines and reusable action blocks
  • Quality gates and automated review workflows
  • Documentation structures and project templates
  • Early concepts like OALint (a future linting engine)
  • Early ideas like OAPM (WinCC OA project management inspired by NPM)

More people started suggesting improvements, sharing ideas, testing workflows,
or simply using the patterns in their own projects.
This diversity of input is now a core part of what makes the ecosystem valuable.

The goal is not to build “one big tool,”
but to provide many small, reusable components
that teams can combine into their own workflows.

🌳 Where We Want to Go​

The direction is clear:
Enable modern, automated, reliable WinCC OA development — for everyone.

The future focus includes:

  • Better collaboration tools for developers and QA
  • A standardized rule system for CONTROL code quality (future OALint)
  • A modern, package‑style project management idea (future OAPM)
  • Reusable CI/CD components for all major platforms
  • Developer‑centric DX improvements like VS Code extensions, CLIs, and templates
  • Documentation, examples, and success stories others can learn from
  • A community space where contributions, ideas, and improvements can grow organically

The long‑term vision is to build an open toolbox, not a closed framework —
a place where WinCC OA developers can pick the tools they need and avoid reinventing the wheel each time.

🤝 A Collaborative Effort​

Even though the project started from a single idea,
it is continually shaped by the contributions, testing, feedback,
and creativity of many people.

Every improvement — big or small — helps move the ecosystem forward.

Thank you to everyone participating, sharing, and building together.
This project belongs to all of us who want better tools for WinCC OA.

Roadmap ideas​

Last update: 2026-06-13 06:24:12 UTC

Source of truth: GitHub Feature issues