Traditional testing vs. SimServe

Test Your SCADA System. Not Just Your Screens.

Memory tags can animate graphics. A spare PLC can test a connection. SimServe helps you test more of your actual SCADA environment — using real protocols, simulated PLCs, and production-style configurations.

Three Ways to Test. One Big Difference.

Traditional testing approaches have their place. The question is how much of your production environment they actually allow you to validate.

SCADA Memory Tags

Good for testing screens. Not the full communication path.

Memory tags help animate graphics and validate basic SCADA functionality, but bypass the real PLC communication path.

Temporary configurations often need replacing before deployment.

A Single PLC

Real hardware. Limited coverage.

A physical or simulated PLC lets you test real communications, but one device can't represent your entire production network.

Broader testing may require more hardware or workarounds.

SimServe

Test more of your production environment, without all the hardware.

Simulate multiple PLCs using real EtherNet/IP or Modbus communications, production-style configurations, and changing process data.

Less time recreating the environment. More time testing the system.

What's Different With SimServe?

01

Test the Actual Communication Path

Your SCADA system uses its normal communication drivers to connect to simulated PLCs.

That means you're testing more than just changing tag values on a screen.

02

Work With Production-Style Configurations

Use the IP addresses, tag names, data types, and communication settings your application expects.

Reduce the number of temporary configurations that need to be changed when moving to production.

03

Simulate Realistic Operating Conditions

Use Python scripting to create changing process values, alarm states, heartbeats, and polling behavior.

Test how your application responds to more than a handful of static values.

04

Build a More Complete Test Environment

Simulate multiple devices and communication scenarios without needing a physical PLC for every controller in the production network.

Same SCADA System. Three Very Different Testing Environments.

Explore how the same eight-PLC system is represented in production, traditional testing, and with SimServe.

The complete production SCADA environment, with all eight PLCs and their associated connections.

Primary SCADA ServerSub Master 01Sub Master 02Remote PLC 01Remote PLC 02Remote PLC 03Remote PLC 04Remote PLC 05Remote PLC 06

Swipe the diagram sideways to see the full network.

Simulation covers the PLC devices and their communications, not radio propagation or the full PLC control logic.

See Exactly What's Different.

Compare traditional testing and SimServe across development, testing, and commissioning.

Partial indicates that a capability may be tested for a limited portion of the system. Actual coverage depends on the devices and configuration used.

See SimServe in Action

Want to see what this looks like in a real SCADA application?

Watch SCADAmatic founder James Parsons demonstrate EtherNet/IP PLC simulation, Python scripting, and live data in Ignition on The Automation Podcast.

Watch the Demonstration

Build a Better SCADA Test Environment

Whether you're developing a new SCADA application, preparing for factory acceptance testing, or getting ready for commissioning, SimServe helps you test with greater confidence.

Have a unique testing scenario? Talk to SCADAmatic about what you need to simulate.