Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Provide better dev/prod system integration

Geo SCADA and Remote Operations Devices Ideas

Use this portal to submit your innovative ideas to make Geo SCADA Expert and Devices such as SCADAPack, Trio and Realflo of greater value to you and to the SCADA & Telemetry community. Every idea will be individually reviewed by our team for merit and will be marked Under Consideration.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Remote Operations
  • Geo SCADA and Remote Operations Devices Ideas
  • Provide better dev/prod system integration
Options
  • Subscribe to RSS Feed
  • Mark as New
  • Mark as Read
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • SCADA 2
  • ViewX 2
  • Mimics 2
  • SCADAPack 2
  • Scripting 1
  • Virtual ViewX 1
  • Geo SCADA Expert 1
  • Efficiency 1
  • Configuration management 1
  • Modbus to WiStar 1
Idea Statuses
  • Submitted 9
  • Under consideration 126
  • Accepted 1
  • Declined 4
  • Partially delivered 0
  • Delivered 0
  • Abandoned 0
Related Products
Thumbnail of EcoStruxure™ Geo SCADA Expert
Schneider Electric
EcoStruxure™ Geo SCADA Expert
112
Thumbnail of SCADAPack 57x
Schneider Electric
SCADAPack 57x
2
Thumbnail of Accutech
Schneider Electric
Accutech
1
Load more
Completed Ideas
  • Accutech Modbus Master gateway to read Modbus devices and incorporate into WiStar net

  • Controller Key Enhancement

  • Restore "Embed Source Code for Upload" Option in Workbench (SP300 family)

  • DNP Outstation And DNP Master Diagnostics

View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
6 Likes

Provide better dev/prod system integration

Status: Under consideration Submitted by Lt. Commander du5tin on ‎2021-09-27 04:45 PM
3 Comments (3 New)

We have several customers with very large SCADA systems that are worked on by multiple integrators. We have a test/dev system setup and on the network with a production setup. We do our development on the test system and then export our changes and import on the production system.

 

This usually goes well and without much trouble. However, if some integrators don't follow a proper change management procedure (e.g. updating a template on test but forgetting to update it on production) then the two databases will drift over time. In an effort to reduce our admin and change management workload it would be excellent to be able to develop and test on the dev system and then have a "promote changes to prod" feature.

 

As an extension of this process it would be good for the system to evaluate parent objects (templates, embedded mimics) for changes and publish those to production before publishing any inherited objects. This could have a dialogue box similar to the delete dialogue. "Publishing to production will impact the following objects and make the following changes:" and list the impacted objects with the parent objects first and inherited objects last. 

 

Further expansion on the idea: have the ability to have a configuration field to prevent publishing certain objects. There are some cases where we always want test/production objects to be different. E.g. communications settings, system headers, etc..

Tags (6)
  • Find more ideas tagged with:
  • english
  • scada
  • SCADA app
  • SCADA software
  • SCADA tutorial
  • Telemetry and SCADA
Comment

Link copied. Please paste this link to share this article on your social media post.

  • Back to Idea Exchange
  • Previous
  • Next
3 Comments
Anonymous user
Not applicable
‎2021-09-27 05:12 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2021-09-27 05:12 PM

I really like this idea.

BevanWeiss
Spock BevanWeiss
Spock
‎2021-10-06 09:43 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2021-10-06 09:43 PM

It is a good idea 🙂

Although I think with DB authentication / authorisation differences between the Test/Dev and Production system it might be troublesome.

 It would also need to have ViewX type (i.e. Client) connections between the Test/Dev and Production systems, which can lead to some issues.

 

I did have an idea at some time for a 'Synchronise with remote system' 'object' (i.e. an extension of the CGroup object).  Such an object would maintain a local 'cached' copy of the CGroup in the 'child' database, but could be configured to prevent any changes to items beneath it, with all of those items being synchronised (not necessarily in real-time, but based on some configurable update rate) with the 'parent' database from a matching CGroup object (i.e. the !Config folders could be kept in sync across all systems from some master DB).

It wouldn't solve the Test/Dev situation, but it would solve the divergence issue... since it would not be possible for such integrators / users to modify synched items in these folders.

sbeadle
Kirk sbeadle Kirk
Kirk
‎2022-04-18 01:26 AM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2022-04-18 01:26 AM
Status changed to: Under consideration

Thank you for these suggestions, they will feed into our roadmap.

Best regards

Steve

Comment
Preview Exit Preview

never-displayed

Hint:
@ links to members, content
 
  • Back to Idea Exchange
  • Previous
  • Next
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of