Modernize Your SCADA and More
Protect your Investments and Modernize
We help protect your investment in existing SCADA and Process Data by upgrading and rearchitecting where needed to save money and enhance data access and get longevity. Why not get cost savings and decrease maintenance by thinning out or virtualizing your architecture. Go thin, mobile, virtualize.
Modernization to Save Money and Improve
- Upgrade and Thin out your Architecture
- Update your legacy SCADA and Historians
- Improve Real-Time Data Access
- Connect to the Enterprise and Cloud
- Improve Security
- Access via the Web and Mobile
A Modern SCADA System Should:
- Be Industry 4.0 Ready
- Support a Unified Namespace
- MQTT and OPC UA
- Easily Integrate to SQL and NoSQL
- Connect to any Machine or Device
- Autodiscover Tags and Models
- Security at the Core
- Powerful Extensibility
- Support scripting
No Charge SCADA Evaluation
INS3 offers a complimentary Evaluation of your Existing SCADA, HMI and/or Historian systems:
- Start with a quick 30-minute Discovery Web Meeting
- Onsite walkthrough visit (if possible)
- Our Engineers review current system details
- Create a plan to fit your needs
- Provide options with cost estimates
- Complete Project and Provide Results, like:
- Updated SCADA, OS, and
- Standardize and develop disaster recovery plan
- Implement data and alarm management
- Model-based and high-performance HMI
- Better data access for Analytics
Industry 4.0 Workshop
Join us at our Workshop to learn how Industry 4.0 can help you lower Production Costs and Optimize your Process!
VMWare is by far the most utilized in our customer base with the servers on premise and the largest growing area is virtual servers in the cloud. The reality is most applications do run on any of the architectures, and the key items is what your team (whether in-house IT, cloud provider, or you yourself) can support and maintain. Internally INS uses the VMWare platforms.
The most common modern architectures are consolidating the systems back into a server farm, and pushing thin clients out to the devices on the floor. Manufacturing software typically is staying on-premise (although data may be mirrored in the cloud)
INS has helped many of our customers in this decision process, and the results varied from customer to customer. The key variables to take into considerations are software costs, engineering costs, risk, and long term annual costs. Software upgrade / replacement costs are the easiest to calculate as they can be quoted. The engineering cost of replacing a system may or may not be cost-effective. It is very important to take into consider future annual costs and risks of having legacy software versus modern software.
The most common driver for modernization of systems is the availability of computers, and the obsoleting of operating systems. Eventually every digital system will either be a security risk or availability of spare parts becomes not cost effective, and they will need to be replaced or upgraded. In today’s connected world, air-gapping a system to protect it from cyber security risks is becoming less of a possibility.
The idea of “thinning down” mostly has to do with not maintaining personal computers on the plant floor, and move the floor computers to something that has very little maintenance at the machine. For example a zero-deploy thin client terminal or a small Linux device that connects to a Terminal Server, Web Servers, or Thin-Client manager. It is about moving the maintenance of the system into a server room, and limiting or eliminating any maintenance on the floor.
The short answer is yes. It can be done by thinning down the current system through a modernization effort and re-architecture. It can be done by layering new technology on top of and integrated with the legacy system. Any movement to mobile or web views of manufacturing data, must take into account cyber security requirements to protect the systems that run the plants.