MDT Software
AutoSave
X-Change 2007 User Group Conference
MDT Software
The Change Management Company
Jean-Claude Cornu
Implementation Engineer
AutoSave Overview
2
Overview
MDT Software is the world leader in change management solutions for
automated manufacturing assets.
We focus solely on software solutions for the industrial marketplace.
We empower our clients to:
• Gain visibility into changes in plant floor devices
• Detect unauthorized changes
• Comply with regulatory requirements
• Efficiently manage plant floor devices
• Maximize plant uptime and profitability
3
Proven Experience
We serve over 250 companies in a wide variety of industries.
Our customer list includes:
Pharmaceutical
Food & Beverage
Automotive
Brewing
3M
BAA
Brach’s Confections
Anheuser-Busch
Campbell Soup
Caterpillar
Chase Brass
ChevronTexaco
Coca-Cola
ConvaTec
Coors Brewing
Corn Products
CVRD
DaimlerChrysler
Dell
Delphi
DHL
Ford Motor Company
General Mills
General Motors Corporation
Hayes-Lemmerz
IAMS
Leprino Foods
Lawrence Livermore National Labs
Lorillard Tobacco
Mozal Aluminum
Mitsubishi
National Starch & Chemical
Michelin
Nestlé
New York Times
Newport News Shipbuilding
Phelps Dodge
Procter & Gamble
Roseburg Forest Products
Rustenburg Platinum
Sara Lee
SGM
SGMW
Snowy Hydro
Siemens Automotive
South African Breweries
Toyota Motor Company
Weyerhaeuser
4
Pulp & Paper
Metals
Oil & Gas
Ship Building
Change Management – Questions
Protection of Assets & Intellectual Property
Where is the latest version of your programs?
Reduced Downtime
What program is in the device?
Provide Audit trails for investigation
Who made the last changes, and why were they made?
Increase in Safety
What was last changed, and when was it changed?
Disaster Recovery
Hardware failure, Security, Sabotage; Am I prepared?
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
5
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
What program is in the device?
Provide Audit trails for investigation
Who made the last changes, and why were they made?
Increase in Safety
What was last changed, and when was it changed?
Disaster Recovery
Hardware failure, Security, Sabotage; Am I prepared?
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
6
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
Version Tracking & Automated Retreival
Provide Audit trails for investigation
Who made the last changes, and why were they made?
Increase in Safety
What was last changed, and when was it changed?
Disaster Recovery
Hardware failure, Security, Sabotage; Am I prepared?
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
7
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
Version Tracking & Automated Retreival
Provide Audit trails for investigation
Extensive Change Logs & Database Tracking
Increase in Safety
What was last changed, and when was it changed?
Disaster Recovery
Hardware failure, Security, Sabotage; Am I prepared?
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
8
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
Version Tracking & Automated Retreival
Provide Audit trails for investigation
Extensive Change Logs & Database Tracking
Increase in Safety
Detailed-Comparison Reporting system, identifying changes made
Disaster Recovery
Hardware failure, Security, Sabotage; Am I prepared?
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
9
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
Version Tracking & Automated Retreival
Provide Audit trails for investigation
Extensive Change Logs & Database Tracking
Increase in Safety
Detailed-Comparison Reporting system, identifying changes made
Disaster Recovery
Complete Data & System backup & recovery, integrated security
Regulatory Compliance
Are we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
10
Change Management & AutoSave
Protection of Assets & Intellectual Property
Fully Automated Program & Document Archival system
Reduced Downtime
Version Tracking & Automated Retreival
Provide Audit trails for investigation
Extensive Change Logs & Database Tracking
Increase in Safety
Detailed-Comparison Reporting system, identifying changes made
Disaster Recovery
Complete Data & System backup & recovery, integrated security
Regulatory Compliance
CFR21 Part 11 Compliant, as well as contributing to the process &
operational control requirements of Sarbanes-Oxley
11
MDT’s AutoSave
AutoSave
Plant Network
•
AutoSave is a central system that is
networked to the operation/machine
•
Captures changes as they are made
•
Documents the changes
•
Automatic checking of operation/machine
programs
•
Electronic notification of changes
•
Historical data of changes
•
Reporting on changes
•
Disaster recovery of operation/machine
programs
•
User Access and Security Control.
12
Making changes to a device
Typical Manual Process
AutoSave
Login to AutoSave
Find the Right Program!
Select Program
Verify user permissions
Verify client permissions
Lock program
Transfer from server to client
Comment files available
Launch Editor
Make Changes
Comment Prompt
Check-in program
New revision created
Saved on Server
Save and Exit Editor
Copy to Backup?
Logout of AutoSave
Note changes?
Server periodically verifies PLC
to Library copy and emails
difference report
13
MDT’s AutoSave
• Client/Server Based Architecture
• SQL Server Database-based Archive
Configure
Here
Backup
Here
The Central Location of the Software to which All
Agents, Personalities, and Clients Report – Master
Control Center
Edit
Here
Client Laptop
Server
Agent
The interface
through which the user interacts with
the AutoSave system.
PC-Based
Control
The Component of AutoSave that communicates
with the Device
Processors –
Gateway
Uploads/Downloads/Compares
Client Workstation
Edit
Here
Field bus
Robot
PLC
CNC
14
Typical Workflow
Current Copy
Local Copy
Ancestor Copy
SMTP
TCPIP
AutoSave Server
Agent
Client 1
TCPIP
Client 2
Agent
Profibus
15
Scheduled Compare
(1) Time-scheduled event
(2) Upload device
SMTP
(3) Compare to Current Version
(4) Email differences report
(5) Create new Current Version Backup
is difference exists (Optional)
TCPIP
AutoSave Server
Agent
Client 1
Client 2
Current Copy
Local Copy
Ancestor Copy
Processor Copy
Agent
Profibus
TCPIP
PLC Level
16
AutoSave
Screen Tour
X-Change 2007 User Group Conference
Program Status Information
User Interface
Program Information
Version Control & Tracking
Navigation
Program Search
Tree
Open Program Tabs
Device Network Configuration
18
User Interface
19
User Comments
Backup Ancestor
Method of Change
Client Station
User ID
Date and Time
Revision
Current Copy
Named Version
User Interface
Upload
Compare
Edit
20
Scheduled Compares
Why?
If Changes are Not made Via Client,
Time Scheduled Compares will monitor
and document the change
Maintain a Current Copy of your programs
Steps
1) Create Scheduled Compare Group(s)
2) Define Schedule
3) Select options for Results
4) Assign Programs / Areas
21
Additional Features
Classes: Pre-Defined privilege groups
Client Specific Settings
System Reporting
System Configuration Parameters
Device/Network Configuration
User Configuration
Approval Groups/Lists (21CFR Part 11)
22
Devices Supported
AutoSave supports the most comprehensive range of
devices and editors in the industry
PLCs
Robots
}
• Schneider
• Modicon
• Telemecanique
• Wonderware
• Allen-Bradley
• Rockwell Automation
• Siemens
• Mitsubishi
• GE
• Omron
Workstations
• Indramat
• FANUC / Kuka / ABB
Project Files
•Toyopuc
•iFIX / Fix32
CNCs
Welders
Drives
HMI's (OIT)
Documents
•Bosch/Rexroth
…to name a few!!
23
Approval and Workflow Enhancements
to support a more formalized change
control process
X-Change 2007 User Group Conference
Approval Process Workflow
Current
ECO-1
ECO-2
New changes follow
an approval process
prior to plant floor
implementation
Implemented
Edit
Implemented
Start New
Change
RFA
Validated
Testing
APV
25
Partial
Approval
Future Paths
X-Change 2007 User Group Conference
AutoSave 5.04 (2Q 2007)
Client
Support for Multi-Lingual Client
Find tab improvements
Drag-n-Drop moving of programs or areas
Program / Area names can contain spaces
Depends on support by 3rd party programs
Time Scheduled Compare
TSC Email to include summary information
Support a Processor to Version compare
Improvements to agent selection process
Pre-Kill Process INI File
AutoSave Licensing
Support for multiple machine ids
Support for demo licenses or trials of specific module types
New automated License Registration process
27
2007 Plug-In Update
Document Pack
Microsoft Word (DOC)
Microsoft Excel (XLS)
Microsoft PowerPoint (PPT)
Adobe Reader (PDF)
Drawing Files (DWG)
FTP Plugin Module (FTPWin)
Standard FTP with configurable filelist
GE iFIX Plugin Module
Supports GE iFIX v3.5
Wonderware InTouch v8-v9 Plugin Module
Support v9.5 New updates and bug fixes
Omron CX Programmer Plugin Module
Supports CX Programmer v6.0 - v6.1
Schneider ProWORX Plus Plugin Module
Schneider Unity XL Pro Plugin Module
New Beta of Unity-Diff in Development
Rockwell RSLogix 5000 v16 Plugin Module
Rockwell RSLogix 500 v5-7 Plugin Module
Now supports Forced-Bit comparison
Rockwell RSViewME v3.2-4.0 Plugin Module
Siemens Step7 5.4 Plugin Module
Siemens WinCC Plugin Module
Toyoda PCWin (toyopuc) Plugin Module
28
Web-based Reporting Tool
The new AutoSave Web-based reporting tool will allow customer to drill down into the
logs and AutoSave data for many additional customizable reporting of data. In addition,
reports can be scheduled and e-mail notification is possible.
29
AutoSave Geneva
Flexible Interface
AutoSave functionality will be readily
accessible outside of the standard
Client GUI, as well as
administration. This will allow
customers to develop their own
Client Interface, if desired.
Examples:
•
•
•
Web Browser Integration
HMI/SCADA Integration
Desktop Icons
30
AutoSave Geneva
AutoSave 6.xx will support a new highly functional scripting
language. This should allow customers to create custom
applications or executables to address any custom needs not
solved by current application interface.
Sample Script
1. Execute initial application
2. Download program from AutoSave
3. Process downloaded data using
using external application
4. Restore program back to AutoSave
31
Conclusion
AutoSave is the industry's most advanced feature-rich
change management software.
Today over 5,000 end users in a variety of industries
worldwide use our AutoSave software suite to
effectively manage change and minimize downtime.
We are dedicated to customer satisfaction.
Thank You!
www.mdtsoft.com
33
AutoSave for Highly
Regulated Industries
X-Change 2007 User Group Conference
continued in more
detail…
Starting the Change Process
Create a new version
within the appropriate
AutoSave Program
35
Starting the Change Process
Engineering /
Maintenance
personnel can now
develop the
appropriate set of
changes
Changes are made
offline
Any number of edit
sessions can be
performed
36
Making the change offline
Edit changes like
normal.
An update to the
version occurs
after a comment
is entered
You cannot
cancel a change
37
Starting the Approval Process
When the changes requested have been
developed, the user making the changes
initiates the approval process
Email sent to applicable users who can then
approve the change
Management
Email
Notification
38
Quality
Who Approves changes
Users who approve
changes are set up
once
administratively.
One user
representing each
group must approve
the change before
implementation can
occur
39
Approving Changes
An approver logs in and
selects role to approve the
change
A comment and control
number will be entered
AutoSave automatically
records all events and converts
the status to APV (Approved
Pending Validation) when one
user in each group in the
approval list approves the
change
40
Completing the Approval
When last approval is entered
Version automatically converted to APV (Approved Pending
Validation)
Allows for time lag to occur from approval to the start of
plant floor testing
41
Testing Changes Prior to Rollout
Testing is required to ensure that the approved changes
actually produce the desired product on the plant floor.
Product produced at this time is typically quarantined until such
time that the changes made have become validated.
Time lag from APV to Testing is very realistic due to the
need to coordinate the actual testing on the plant floor
When the status is switched, downloading of this
‘approved but not validated’ change is enabled.
The conclusion of the testing should be a switch either
back to the edit state (due to a reject) or a transition to a
validated state
42
The Validated Change
Software has passed all testing and is ready for
deployment
Often a time lag will occur from when the change
is validated to the time it is ready to be
implemented
An appropriate user can transition the change
from validated to implemented only at this point.
43
Implementing an Approved Change
Executed as a
command “Implement
Change”
Changes the selected
version from Validated
to Implemented
Enables this version for
download by those with
download privilege
Changes the previously
implemented version to
PA (Previously
Approved)
Logs all relevant events
in this process
44
Downloading an Implemented
Change
The change can now
be downloaded into
the device
If the device must
ever be reset, then
this implemented
version is the only
one that can be
used
45
Rejecting Changes During the
Process
Any user in the
approval cycle can
reject the change
anywhere during the
approval process
The change is sent
back to an “Edit” state
allowing the engineer
to make the necessary
changes.
Comments are added
by the person
rejecting the change.
46
Acquiring Real Time Updates
At any point
in the cycle,
a user can
double-click
on the
version and
see the
current state
of the
approval
process.
47