Automatic Configuration with Dynamic User Interface
Open Automation Software offers OEMs full programmatic setup for their end users. This method greatly reduces the potential for human error in the setup process. Deployment of custom applications can be implemented from predefined scripts using SharePoint, Excel or a number of other methods. Time is saved both in deployment and in troubleshooting because of the decreased likelihood for error and the speed that you can deploy new and update existing projects.
The video below demonstrates how to use the Automated HMI Example that is included in the installation of Open Automation Software. The application automatically sets up data source configurations, trending, data logging and alarm limits. The HMI clients will adapt themselves automatically based upon what data source is defined.
.NET Programmatic Server Configuration
.NET Users can programmatically define all OAS configurations including tags and data logging as demonstrated in this video above. The OASConfig .NET Standard 2.0 assembly for .NET 5, .NET Core 2.o or greater, .NET Framework 4.61 or greater, Xamarin.iOS 10.14 or greater, Xamarin.Android 8.0 or greater, and UWP 1.0.0.16299 or greater or the OPCSystems assembly for .NET Framework 4.6 or less. The components are free to use and can be included in Windows Services, Web Services, ASP.NET or .NET MVC Web Applications, WinForm Applications, WPF Applications, and .NET Core Console applications. The assemblies can be used to communicate and setup local and remote services. Learn More…
REST API
The OAS Platform REST API allows developers to read and write real time Tag data, read real time and historical Alarms and Trends, and even create or update Tag configurations. It utilizes JSON data over HTTP(s) and can be used by any virtually any development platform or language. Learn More…