Hello everyone, I am currently working on a rehabilitation project where a standalone InTouch 2014 HMI is being used as a SCADA system, although it is quite basic. One major issue is the presence of outdated and cumbersome 1995 schematics pages that serve as P&ID drawings. While these are nice to have, they are not practical for day-to-day operations, especially since InTouch does not support vector scaling, making it difficult to utilize them effectively in a 16:9 format. I have taken it upon myself to create new operational pages for the commissioning process, as the existing setup leaves much to be desired. Recently, the customer expressed a desire to retain the P&ID pages as their team struggles to interpret P&ID DWGs. I am considering placing them in pop-ups or leaving them unscaled, but this would result in a disjointed testing process during commissioning. Additionally, the customer has requested that all analog values boxes (approximately 100-120 values) be able to open pop-ups displaying detailed information about the value. While this feature may have been useful in a different context, it does not add significant value to this particular unmanned station, where operators are restricted from altering most values. The customer has also mentioned a WW report generation solution, which I have not encountered before. I am unsure if this solution is compatible with InTouch Standalone or a Galaxy system. Considering the customer's evolving needs and the desire for a comprehensive SCADA system, I am contemplating the transition to a Galaxy platform, despite the inherent challenges and learning curve associated with it. In conclusion, I am seeking advice on how to proceed with implementing the requested features, such as the "faceplate" pop-up for analog values, and whether transitioning to a Galaxy system would be a more suitable long-term solution. Additionally, any insights on the compatibility of the WW report generation solution with the existing setup would be greatly appreciated. Thank you for your help.
Utilizing Alisis tags and some scripting allows for the implementation of popups on your website. When it comes to viewing P&ID's, consider using Acrobat as a viable option. In terms of transitioning a system from 2017 to 2024 using Galaxy, the consensus suggests that the cost outweighs the benefits unless starting from scratch. In fact, we observed that incorporating Galaxy slowed down the project and extended failover times significantly, particularly with twin servers. The primary drawback was the high cost of licensing compared to the minimal advantages gained.
Instead of embedding bitmap images, consider creating an HTML version of the drawings and loading it in a web browser window using a window script like the following: Code:#Explorer1.Navigate("C:\Drawings\DWG1.htm"). Quick functions can streamline indirect scripting processes. In this case, the quick function "AnalogQF" is used, with IO tags "AinXY123_LL" and "AinXY123_SP". When clicking a button with actionCode:CALL AnalogQF ("Thingie", "XY123"), different arguments are passed to the quick function. The AnalogQF arguments include Name and Input, where the PopupTitle is set to display the Name followed by "Parameters". The indirect tags are then set to show the values of the AinXY123 tags with the title "Thingie Parameters" in the AnalogPopup.
When deciding between using Standalone InTouch or System Platform Galaxy, the key factor to consider is the approach you want to take. Standalone InTouch involves creating Indirect tags for analog faceplate popups and linking them to the faceplate in WindowMaker. On the other hand, System Platform requires creating template objects with all the necessary attributes and creating instances of these templates for each analog device. With Standalone InTouch, using tools like DBDump/DBLoad and Excel can help in building the tag database efficiently. In contrast, System Platform offers a more structured approach to creating and maintaining graphics and templates. Overall, transitioning to System Platform may require a significant investment in learning how to bind objects to PLC tags effectively. However, if done correctly, it can result in a more sustainable system compared to the limitations of Standalone InTouch's "Smart Tags." It's important to recognize that any changes requested by the customer may go beyond a simple software upgrade and instead require a complete overhaul of the existing system. This could potentially come with a hefty price tag, but it's ultimately a part of the business of keeping systems up-to-date and functional.
Thank you for your message, it aligns with my thoughts. We are currently working on two units that are 99.9% similar, and the SP aspect is also intriguing. In our industry, the WW App Server is not as widely used as in other sectors, so we have limited experience with it. However, I have been interested in learning more about it for quite some time. While I had some exposure to it in 2012 while working on a WW system, my main focus has been on Citect for the past six years. Now, due to licensing costs, our primary client is considering a switch to VT SCADA. I personally view this as a downgrade, but we will see how it unfolds. I had a discussion with Aveva earlier today, and they were able to provide information on their licenses. Currently, AppServer and Aveva Reports for Operations are not covered, but for a similar cost, our local distributor could make it happen. As you mentioned, this would involve some commercial considerations and project management responsibilities. We are also exploring the timeline for transitioning to SP2023 with assistance from our integrator license providers. I am uncertain about the feasibility of starting from scratch, especially in terms of reusing existing work done in Standalone InTouch. While embarking on a fresh project sounds exciting, I am wary of potential setbacks. It is crucial to deliver a functional system without unnecessary embellishments. Despite the client's preference for reusing PLC modules, budget constraints may limit extensive customization. Moreover, our workload is already substantial. We will need to carefully evaluate the project scope and timeline. Your insights are greatly appreciated. PS: The P&IDs are not traditional DWG files; instead, they are interactive windows displaying the P&ID with minimal animations.
It sounds like you're in the middle of quite a complex rehabilitation project! Regarding your customer's requests, I agree with your hesitation about historical P&ID drawings - they can be nice to reference, but may not be as effective for day-to-day operations. Maybe you can compromise by creating simplified schematic pages for operational use, and keep the full P&ID pages for reference. For the analog values boxes, if you don't see the "faceplate" pop-ups adding value, I'd suggest having a candid conversation with your customer to understand the usefulness of this feature from their perspective. Transitioning to the Galaxy platform could indeed be a wise long-term solution. Even though it has a learning curve, it may ease integration with future updates or expansions and thereby provide a more sustainable route that better aligns with the customer's evolving needs. About the WW report generation solution, it's best to directly consult with Wonderware tech support or their documentation if available, as they will have the definitive information related to compatibility with InTouch Standalone or Galaxy system. Last but not least, sometimes customers don't realize the complexity involved in implementing certain features, so good communication is key. Best of luck with the project!
You're dealing with quite a complex situation here. Traditional PID schematics won't play nice with a 16:9 format, generally, so I understand your struggle. Your idea of having them as pop-ups could be a decent compromise to retain them without hampering the functionality of the REMADE pages. As for the "faceplate" request, perhaps some simple explanatory text with crucial values might be more appropriate, leaving the intrinsic details for a separate, deeper dive. Not sure about WW report compatibility, but you could check the Wonderware website for detailed compatibility insights. Transitioning to a Galaxy platform could indeed be beneficial for future proofing and scaling, though I'd recommend running a thorough cost-benefit analysis to be sure it justifies the investment of time and resources. The learning curve is there, but in long run it could present an efficient, integrated solution compatible with modern needs. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Consider placing the P&ID pages in pop-ups or leaving them unscaled, but be mindful of potential challenges in the testing process during commissioning.
Answer: Answer: While it is possible to create pop-ups for analog values, ensure that the feature aligns with the operational needs of the station to avoid unnecessary complexities.
Answer: Answer: Transitioning to a Galaxy system may offer enhanced functionality but comes with challenges and a learning curve. Evaluate the long-term benefits against the immediate needs of the project before making a decision.
Answer: Answer: Verify the compatibility of the WW report generation solution with both the existing InTouch setup and the potential Galaxy system before proceeding with implementation.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.