Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

Important Announcement: WELCOME to the new Schneider Electric Community! Community is now no longer part of Exchange, and is now rebranded under se.com. If you have any bookmarks and links saved, we request you to update them to ensure that you continue accessing our community from this new location. For any issues that you might encounter as part of this change, please reach out to SchneiderCommunity.Support@se.com, and the team will help to get your issues resolved.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

Geo SCADA v6.81

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.


Geo SCADA v6.81



I hope you're well. 


What is the underlying Database technology used GeoSCADA v6.81.  Is it Schneiders own technology,  an open source database or can customer choose their own database technology from their favourite vendor?  


I've working with a client to find a way to export the GeoSCADA v6.81 schema/meta-date into a data governance tool. 




James Taulbut

Tags (1)
1 Reply 1
Commander Commander

Re: Geo SCADA v6.81

Hi James,


It is a proprietary but with open interfaces, see https://community.exchange.se.com/t5/Geo-SCADA-Knowledge-Base/Supported-Interface-and-Protocol-Versi... for some details as well as the product help.


For what you're trying to do, my guess is you'll want to parse the schema which by default is at https://localhost/schema on the server (it is simple XML but dynamically generated based on what modules you install and what your configuration/metadata is) which will provide you the database structure, and then for the data part you have lots of options depending on what type of data you actually need (configuration, events, historic, etc) and if real-time or batch/reactive.