↗
Reuse Existing OPC DA Tags
Automatically map local OPC DA Server tags into the OPC UA Server address space, significantly reducing duplicate setup and maintenance costs.
OPCTECHS OPC UA SERVER
Seamlessly extend existing OPC DA tags
and rapidly connect to next-gen OPC UA systems
Deploy an independent OPC UA Server to interface with existing OPC DA Servers, providing standardized data for upper-layer systems and accelerating smart manufacturing adoption.
PRODUCT ADVANTAGES
Empower existing industrial data with rapid OPC UA Server connectivity expansion
Expand standardized data interfaces without rebuilding existing OPC DA Server architectures, achieving low-cost system upgrades.
⇄
Seamless Coexistence of Legacy & Modern Systems
Legacy systems retain their original OPC DA interfaces while new systems access data directly via OPC UA, enabling a smooth architectural transition.
⌘
Simplified Cross-Network Architecture
Utilizes standard OPC UA TCP communication, eliminating complex legacy DA/DCOM distributed settings and drastically lowering firewall and network integration barriers.
▦
Seamless Integration with Upper-Layer Management Systems
Provides standardized interfaces for upper-layer systems—such as SCADA, MES, EMS, and IoT Gateways—to effortlessly connect with field device data.
HOW IT WORKS
Expand OPC UA data outlets seamlessly without altering existing data sources
OPC UA Server operates as an independent service. Once launched, it automatically reads configured data tags from the local OPC DA Server and delivers them to compatible Clients via OPC UA Endpoints.
- Maintain Existing Operations：Field equipment continues to be driven and sampled by the existing OPC DA Server.
- Automated Tag Mapping：OPC UA Server directly reads existing OPC DA Server data tags, minimizing redundant configuration tasks.
- Secure & Authorized Connectivity：OPC UA Clients establish connections and read authorized data via secure Endpoints. (For detailed data types and security mechanism support, please refer to the official product specification sheet.)
▤
PLC / Field Devices
Data Source
→
▣
OPC DA Server
Legacy Device Drivers & Tag Configurations
↓
Local Data Access & Tag Mapping
Standalone OPC UA Server Service
↓
⇄
OPC UA Endpoint
(For OPC UA Compatible Clients)
↓
SCADA／MES／EMS
System Monitoring, Production & Energy Applications
IoT Gateway / Platforms
Data Integration & Advanced Analytics
APPLICATIONS
Connect field data to empower diverse smart applications
Any upper-layer software equipped with OPC UA Client functionality can seamlessly integrate legacy equipment data to accelerate digital transformation.
▥
SCADA／HMI
Legacy monitoring systems maintain stable OPC DA operations, while new or upgraded systems can directly adopt OPC UA transmission for dual compatibility.
⚙
MES／ERP
Instantly connect device status, production data, and work orders to achieve process tracking, capacity optimization, and operational analytics.
ϟ
EMS (Energy Management Systems)
Efficiently aggregate data from power meters, inverters, and energy equipment for precise power monitoring and carbon tracking.
☁
IoT Gateway / Edge Platforms
Rapidly interface with edge gateways and IoT platforms via standard protocols, breaking down barriers between IT and OT data.
PRODUCT COMPARISON
Role Comparison:
OPC DA Server vs. OPC UA Server
They are not simply old-for-new replacements, but distinct interfaces chosen based on field data sources and upper-level system requirements.
| Feature | Existing OPC DA Server | New OPC UA Server |
|---|---|---|
| Primary Role | Directly connects to field hardware, collecting and serving DA data | Reads local DA data and translates it into an OPC UA interface |
| Data Source | Field devices like PLCs, inverters, and smart meters | Data tags from the local OPCtechs OPC DA Server |
| Protocol | OPC DA (COM / DCOM) | OPC UA via Endpoint-based secure communication |
| Target Systems | Legacy SCADA / HMI supporting OPC DA | SCADA, MES, EMS, and IoT Gateways supporting OPC UA |
| Existing Tags | Retains existing DA tag configurations in the project | Automatically maps existing DA tags, significantly reducing duplicate setup |
| Deployment | Requires configuring complex Windows DCOM security and network settings | Simpler setup via UA Endpoint, network access, and security configurations |
GETTING STARTED
4 Simple steps for rapid deployment and validation
From environment checks to OPC UA Client connectivity, achieve seamless integration step by step.
Verify Existing DA Environment
Check OPC DA Server version, tag projects, service status, and local access permissions.
Install & Launch UA Server
Refer to the installation guide to deploy the software, start the service, and configure basic connection parameters.
Configure Endpoint & Security Options
Set up Endpoints, communications ports, user authentication, and encryption options.
Verify via UA Client Connection
Perform a Node Browse to verify that data values, quality status, and refresh rates meet project requirements.
FAQ
FREQUENTLY ASKED QUESTIONS
Q1：We already run OPCtechs OPC DA Server on site. Do we need to reconfigure data tags to use OPC UA Server?
No re-configuration is required.OPC UA Server is an independently licensed software. Once installed, it automatically reads and interfaces with all existing tag configurations in your OPCtechs OPC DA Server without duplicate setup, enabling OPC UA connectivity with minimal time and cost.
Q2：How does OPC UA Server operate? Will it affect our running SCADA or OPC DA Server?
Not at all. Both operate stably in parallel.OPC UA Server runs as an independent service that reads data from the local OPCtechs OPC DA Server. Your local SCADA/HMI continues accessing OPC DA normally without interference.
Q3：Which OPC specifications and security standards are supported by OPCtechs OPC UA Server?
Fully supports standard OPC UA specifications and high-security encryption.Built on the standard opc.tcp:// architecture, it supports X.509 digital certificates, high-strength encryption (e.g., AES-256 / SHA-256), object-oriented data structures, and status metadata transmission.