Aid in the project developing

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 in the ground 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. You can make the remittance using the following 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 to learn of work into the OpenSCADA environment. To read about and to order you can by the link.
To order development of an expansion, implementation of a functional, creation of a specialized solution and product, creation of a comprehensive solution to the tasks of Automated Control Systems (ACS) with OpenSCADA on 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 the policy of openness and freedom brings to the philosophy of software using new features.Thus, the boundary between the user and the developer blurs, because the user-developer creates software to solve their own tasks, while the average user, in one way or another, motivates the creation of the necessary functions by the developer. The conclusion — the lack of this or that possibility is simply the temporary status of free software, when there was no user to whom this function is needed, respectively, this software at the moment optimally solves the problems of its users. Any criticism about the absence of this or that functional, in this case, breaks down on the need for its users or not the desire of these same users, often criticizing the lack of a functional, to do anything to solve their own question!