Geo SCADA Database Configuration — Points, Groups, and the Object Hierarchy

Quick Answer

Geo SCADA uses a hierarchical object model stored in Microsoft SQL Server. Groups act as folders that organize points and other groups. Points represent individual data items (analog values, digital states, accumulators). Templates define reusable point configurations that propagate changes to all linked instances.

The Geo SCADA Object Hierarchy

The database is organized as a tree structure starting from a root node:

• Root — The top-level container for all objects
• Groups — Organizational containers (folders) that hold points and nested groups. Groups typically represent physical locations (sites, stations) or functional areas (communications, alarms).
• Points — Individual data objects representing process values, statuses, calculated values, or control outputs. Each point has a type (analog, digital, accumulator, string, time).
• Other Objects — Channels, devices, mimics, reports, scripts, and alarm configurations.

Creating and Organizing Groups

Right-click the parent group in the database explorer and select New > Group. Group naming should reflect the physical or logical structure of the monitored system. For pipeline SCADA, a common structure is:

Root
├── Communications
│   ├── DNP3_Channel_North
│   └── DNP3_Channel_South
├── Pipeline_North
│   ├── Station_001
│   │   ├── Pressure_Inlet
│   │   ├── Pressure_Outlet
│   │   └── Flow_Rate
│   └── Station_002
└── Pipeline_South

Point Templates and Inheritance

Templates are reusable point configurations. Create a template once with standard alarm limits, historian settings, and scaling parameters, then create instances that inherit from the template. When you update the template, all instances receive the changes automatically. This is essential for large deployments where hundreds of similar points (e.g., pipeline pressure transmitters) share identical configuration except for the device address.

Using the Database Explorer in ViewX

The database explorer in ViewX provides a tree view of the entire Geo SCADA database. Key operations:

• Navigate — Expand groups to browse points and sub-groups
• Properties — Right-click any object to view or edit its configuration
• Search — Use the Find function to locate objects by name or property value
• Drag and Drop — Move objects between groups to reorganize the hierarchy

Naming Conventions for Oilfield and Pipeline Projects

Consistent naming is critical for large Geo SCADA deployments. Recommended conventions:

• Use site or station identifiers as group names (e.g., STN_001, WHP_042)
• Use descriptive point names with measurement type (e.g., Pressure_Inlet_PSIG, Flow_Rate_MCFD)
• Include engineering units in point names for clarity
• Use consistent prefixes for device types (e.g., AI_ for analog input, DI_ for digital input)

Importing and Exporting Database Objects

Geo SCADA supports database import and export via CSV and its native database dump format. Use export to back up configurations before making changes, replicate configurations across similar sites, and migrate objects between development and production servers.

Backup and Restore Procedures

Since Geo SCADA uses SQL Server, standard database backup tools apply. Schedule regular SQL Server backups of the Geo SCADA database. For complete disaster recovery, back up both the SQL database and the Geo SCADA application configuration files in the installation directory.