X-Change 2007 User Group Conference MDT Software AutoSave.
-
Upload
gerald-hicks -
Category
Documents
-
view
223 -
download
1
Transcript of X-Change 2007 User Group Conference MDT Software AutoSave.
2
MDT SoftwareThe Change Management Company
Jean-Claude CornuImplementation Engineer
AutoSave Overview
3
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
4
Proven Experience
3MBAA
Brach’s ConfectionsAnheuser-BuschCampbell Soup
CaterpillarChase Brass
ChevronTexacoCoca-ColaConvaTec
Coors BrewingCorn Products
CVRDDaimlerChrysler
DellDelphiDHL
Ford Motor CompanyGeneral Mills
General Motors CorporationHayes-Lemmerz
IAMS
Leprino FoodsLawrence Livermore National Labs
Lorillard TobaccoMozal Aluminum
MitsubishiNational Starch & Chemical
MichelinNestlé
New York TimesNewport News Shipbuilding
Phelps DodgeProcter & Gamble
Roseburg Forest ProductsRustenburg Platinum
Sara LeeSGM
SGMWSnowy Hydro
Siemens Automotive South African BreweriesToyota Motor Company
Weyerhaeuser
Pharmaceutical
Food & Beverage
Automotive
Brewing
Pulp & Paper
Oil & Gas
Ship Building
Metals
We serve over 250 companies in a wide variety of industries. Our customer list includes:
5
Change Management – Questions
Protection of Assets & Intellectual PropertyWhere is the latest version of your programs?
Reduced DowntimeWhat program is in the device?
Provide Audit trails for investigationWho made the last changes, and why were they made?
Increase in SafetyWhat was last changed, and when was it changed?
Disaster RecoveryHardware failure, Security, Sabotage; Am I prepared?
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
6
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeWhat program is in the device?
Provide Audit trails for investigationWho made the last changes, and why were they made?
Increase in SafetyWhat was last changed, and when was it changed?
Disaster RecoveryHardware failure, Security, Sabotage; Am I prepared?
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
7
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeVersion Tracking & Automated Retreival
Provide Audit trails for investigationWho made the last changes, and why were they made?
Increase in SafetyWhat was last changed, and when was it changed?
Disaster RecoveryHardware failure, Security, Sabotage; Am I prepared?
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
8
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeVersion Tracking & Automated Retreival
Provide Audit trails for investigationExtensive Change Logs & Database Tracking
Increase in SafetyWhat was last changed, and when was it changed?
Disaster RecoveryHardware failure, Security, Sabotage; Am I prepared?
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
9
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeVersion Tracking & Automated Retreival
Provide Audit trails for investigationExtensive Change Logs & Database Tracking
Increase in SafetyDetailed-Comparison Reporting system, identifying changes made
Disaster RecoveryHardware failure, Security, Sabotage; Am I prepared?
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
10
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeVersion Tracking & Automated Retreival
Provide Audit trails for investigationExtensive Change Logs & Database Tracking
Increase in SafetyDetailed-Comparison Reporting system, identifying changes made
Disaster RecoveryComplete Data & System backup & recovery, integrated security
Regulatory ComplianceAre we in compliance? (i.e. Sarbanes-Oxley, CFR21 Part 11)
11
Change Management & AutoSave
Protection of Assets & Intellectual PropertyFully Automated Program & Document Archival system
Reduced DowntimeVersion Tracking & Automated Retreival
Provide Audit trails for investigationExtensive Change Logs & Database Tracking
Increase in SafetyDetailed-Comparison Reporting system, identifying changes made
Disaster RecoveryComplete Data & System backup & recovery, integrated security
Regulatory ComplianceCFR21 Part 11 Compliant, as well as contributing to the process & operational control requirements of Sarbanes-Oxley
12
MDT’s AutoSave
• 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.
AutoSave
Plant Network
13
Making changes to a device
Launch Editor
Make Changes
Save and Exit Editor
Copy to Backup?
Note changes?
Typical Manual Process
Find the Right Program! Login to AutoSave
AutoSave
Verify user permissionsVerify client permissionsLock programTransfer from server to clientComment files available
Comment PromptCheck-in programNew revision createdSaved on Server
Server periodically verifies PLC to Library copy and emails difference report
Logout of AutoSave
Select Program
14
MDT’s AutoSave
Configure Here
Edit Here
Edit Here
BackupHere
Client Workstation
Agent
Client Laptop
Server
• Client/Server Based Architecture• SQL Server Database-based Archive
CNC
Robot
PLC
Gateway
Field bus
PC-BasedControlThe Component of AutoSave that
communicates with the Device Processors – Uploads/Downloads/Compares
The interface through which the user interacts with the AutoSave system.
The Central Location of the Software to which All Agents, Personalities, and Clients
Report – Master Control Center
15
Profibus
Agent
SMTP
AutoSave ServerAgent Client 1 Client 2
TCPIP
TCPIP
Current CopyLocal CopyAncestor Copy
Typical WorkflowTypical Workflow
16
Profibus
Agent
SMTP
AutoSave ServerAgent Client 1 Client 2
TCPIP
(1) Time-scheduled event
(2) Upload device
(3) Compare to Current Version
(4) Email differences report
(5) Create new Current Version Backupis difference exists (Optional)
TCPIP
PLC Level
Current CopyLocal CopyAncestor CopyProcessor Copy
Scheduled CompareScheduled Compare
18
User Interface
NavigationTree
Program Search
Open Program Tabs
Device Network Configuration
Program Information
Version Control & Tracking
Program Status Information
19
User Interface
Revis
ion
Date
an
d T
ime
User ID
Clie
nt S
tatio
n
Meth
od
of C
han
ge
User C
om
men
ts
Current Copy
Backup AncestorNamed Version
21
Scheduled Compares
1) Create Scheduled Compare Group(s)
2) Define Schedule
3) Select options for Results
4) Assign Programs / Areas
Steps
If Changes are Not made Via Client, Time Scheduled Compares will monitor
and document the change
Maintain a Current Copy of your programs
Why?
22
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)
23
Devices Supported
AutoSave supports the most comprehensive range of devices and editors in the industry
• Schneider
• Telemecanique
• Allen-Bradley
• Siemens
• GE
• Indramat
•Toyopuc
•Bosch/Rexroth
• Modicon
• Wonderware
• Rockwell Automation
• Mitsubishi
• Omron
• FANUC / Kuka / ABB
•iFIX / Fix32
…to name a few!!
PLCs
Robots
CNCs
Welders
Drives
HMI's (OIT)
Workstations
Project Files
Documents
}
X-Change 2007 User Group Conference
Approval and Workflow Enhancements to support a more formalized change control process
25
CurrentECO-1ECO-2
Edit
RFA
Partial Approval
APV
Testing
Validated
Implemented
Implemented
Approval Process Workflow
New changes follow an approval process prior to plant floor implementation
Start New Change
27
ClientSupport for Multi-Lingual ClientFind tab improvementsDrag-n-Drop moving of programs or areasProgram / Area names can contain spaces
Depends on support by 3rd party programs
Time Scheduled CompareTSC Email to include summary informationSupport a Processor to Version compareImprovements to agent selection processPre-Kill Process INI File
AutoSave LicensingSupport for multiple machine idsSupport for demo licenses or trials of specific module typesNew automated License Registration process
AutoSave 5.04 (2Q 2007)
28
Document PackMicrosoft 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 ModuleSupports GE iFIX v3.5
Wonderware InTouch v8-v9 Plugin ModuleSupport v9.5 New updates and bug fixes
Omron CX Programmer Plugin ModuleSupports CX Programmer v6.0 - v6.1
Schneider ProWORX Plus Plugin ModuleSchneider Unity XL Pro Plugin Module
New Beta of Unity-Diff in Development
Rockwell RSLogix 5000 v16 Plugin ModuleRockwell RSLogix 500 v5-7 Plugin Module
Now supports Forced-Bit comparison
Rockwell RSViewME v3.2-4.0 Plugin ModuleSiemens Step7 5.4 Plugin ModuleSiemens WinCC Plugin ModuleToyoda PCWin (toyopuc) Plugin Module
2007 Plug-In Update
29
Web-based Reporting ToolThe 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.
30
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
31
AutoSave Geneva
AutoSave 6.xx will support a new highly functional scriptinglanguage. This should allow customers to create custom
applications or executables to address any custom needs notsolved by current application interface.
1. Execute initial application2. Download program from AutoSave3. Process downloaded data using
using external application4. Restore program back to AutoSave
Sample Script
33
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
X-Change 2007 User Group Conference
AutoSave for Highly Regulated Industries
continued in more detail…
36
Starting the Change Process
Engineering / Maintenance personnel can now develop the appropriate set of changesChanges are made offlineAny number of edit sessions can be performed
37
Making the change offline
Edit changes like normal.
An update to the version occurs after a comment is entered
You cannot cancel a change
38
Starting the Approval Process
When the changes requested have been developed, the user making the changes initiates the approval processEmail sent to applicable users who can then approve the change
EmailNotification
Quality
Management
39
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
40
Approving Changes
An approver logs in and selects role to approve the changeA comment and control number will be enteredAutoSave 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
41
Completing the ApprovalWhen 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
42
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 floorWhen 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
43
The Validated Change
Software has passed all testing and is ready for deploymentOften a time lag will occur from when the change is validated to the time it is ready to be implementedAn appropriate user can transition the change from validated to implemented only at this point.
44
Implementing an Approved Change
Executed as a command “Implement Change”
Changes the selected version from Validated to ImplementedEnables this version for download by those with download privilegeChanges the previously implemented version to PA (Previously Approved) Logs all relevant events in this process
45
Downloading an Implemented Change
The change can now be downloaded into the deviceIf the device must ever be reset, then this implemented version is the only one that can be used
46
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.