Project developing aid

The project of an open SCADA system "OpenSCADA" is largely developed on the enthusiasm of professional developers, who do not receive direct compensation for it and pay for their work and efforts, based on self-interest and principles of the open source software. Although the part of work is done by the scheme of providing the commercial services like support and target development, there are situations when it is impossible to implement a particular extension or function due to limitations of time and material resources of developers.In this situation you can help:

  • If you have experience in software development, designer instincts, knowledge of languages that are not supported by OpenSCADA, as well as the desire to improve the project, you can join the development team and contribute. You can offer your help on the project's forum or by contacting the main project's developer Roman Savochenko.

  • To make a donation, thus thanked the developers for their work and contributed to more active development of the project and its infrastructure subsequently. You can make the remittance using the following here link.

  • To buy a package of technical support, thereby guaranteeing yourself prompt assistance in solving possible problems in both: the development of solutions and the operation of stable versions of OpenSCADA. To read about and buy a package of technical support you can by following the link.

  • To order a consultation for using or learning for work into OpenSCADA environment. To read about and order you can by the link.

  • To order the development of extension; functional the creation; the creation of customized solution and product; the creation of a complex turn-key solution of tasks of the automated control systems (ACS) with OpenSCADA in their basis. To read about and order you can by the link.

In this context I would like to mention one important point! Software development based on a policy of openness and freedom brings to the philosophy of software using new features. Thus, the distinction between the user and the developer is smeared because the developer-user creates the software to solve his tasks, while the simple user in one or another way motivates the creation of the necessary functions and tasks by the developer. Conclusion: The absence of any function (feature) it is just a temporary state of free software, while there was no user who needs this function (feature), which means the software optimally solves the tasks of its present users. Any criticism of the lack of a functional in this case breaks by its uselessness to the users or by the unwillingness of most users, which often criticize the lack of a functional, to do anything to solve their problem!