Safeguarding Your Plant with AutoSave Change Management Software

WHAT IS AUTOMATION CHANGE MANAGEMENT?

A Change Management System (CMS) is a centralized system that tracks and identifies changes to program logic for devices such as PLCs, CNCs, HMIs, PC control systems, robots, etc. and provides methods for backup and recovery.

WHY DO PROGRAM CHANGES NEED TO BE MANAGED?

Automation devices are complex and incorporate a large amount of plant data in their operation. Adjustments to variables/logic may be minor individually, but are directly linked to machine throughput and uptime.

Make a program change you wish you had not?

If program changes are not managed correctly and the current device program and configuration are lost, it can result in:

Downtime Decreased machine performance Increased safety hazards Decreased quality/visibility

AUTOMATION CHANGE MANAGEMENT SYSTEM KEY FEATURES

• Common central repository of all program changes with automated retrieval The key to rapid recovery is the ability to access and download the correct automation program to the device.

• The ability to detect and notify users of program changes An effective CMS has the ability to interrogate devices and compare the program running in the device to a reference copy in the CMS.

• Secured user and workstation access Each user should be authenticated by the CMS.

• A historical record of changes A CMS will also record details of changes, such as who made the change, when, and from where it was made.

• Non-networked device management

THE MDT AUTOSAVE CHANGE MANAGEMENT SYSTEM

• MDT Software is the inventor of Change Management Software for Programmable Devices.

• For nearly 30 years MDT Software has delivered automation change management and version control solutions for the world’s leading manufacturers.

• Today end-users around the world have selected MDT AutoSave to effectively manage the increasing array of software on the plant floor and minimize downtime associated with plant floor automation.

• More partnerships with automation manufacturers around version control ensures close coordination on the latest technologies.

• The broadest range of editor and device support in the industry.

HOW DOES AUTOSAVE DO ALL OF THIS?

Let’s look at how a change management system works in a networked environment.

Real World Scenarios

A day in the plant…

Plant Engineer

Things happen…

contractor

New Hire

Accident

No record of source code changes

Decrease in performance / quality

Loss of source code in processor = downtime!

What now?

!

No record of source code changes

Decrease in performance / quality

Loss of source code in processor = downtime!

contractor

An effective CMS: Uploads Compares Identifies differences Analyzes Notifies Updates (optional)

AutoSaveServer

Agent

!

Wonderware InTouch Compare Report

Rockwell RSLogix 5000

Siemens STEP 7

AND the CMS will: Performs comparisons Provides an UNDO!

Employees: Login Select program Perform edits

A good CMS will: Verify user permissions Keep changes

User activity is secured and managedAutoSave

Server

Client

!Agent

Quickly recover from hardware failure

Accident

Simply repair and download!

AutoSaveServer

Client

Agent

AutoSave for System Platform

Change management for objects including graphics, templates, instances and more, within the Wonderware System Platform environment. 

• Compare versions  of objects

• Identify details of differences

• Remove undesired changes

• See an objects associations

• Restore object changes following a Galaxy restoration.

Why do you need A4SP?• Complements your Wonderware System Platform solution with unparalleled change management, lowering risk and increasing 

control. 

• Extends the System Platform audit tracking capability with significant extra value.

• Ensures that intellectual property in the system design is retained.

• Allows for greater experimentation to be done during design phases to test new ideas with rapid rollback of undesirable changes.

GR

DevStudio IDE

AutoSave

AutoSave forSystem Platform

Revision 1

Change OccursChange Occurs

Galaxy Object

Revision 1 Revision 2Revision 3

Full Revision History & Availability

Full Revision History & Availability

Revision 2Revision 3

Galaxy Repository

AutoSaveRepository

Revision StoredRevision Stored

A4SP in action

Revision StoredRevision Stored

QUESTIONS & ANSWERS