Print page  PDF Datasheet   Request Information    
  

 

 

 

 

SECURED PROGRAM ACCESS

Only authorised personnel are able to access programs and make changes. Access is controlled via user logins and passwords and via a transparent filter that screens privileges according to the class of the user (e.g., maintenance, engineering, supervisor, etc.). Divide your plant into areas, such as Manufacturing, Raw Materials, Finishing, etc. Assign devices to each area. Privileges are designated by area and/or by device for each user class. For example, plant engineers may have the privilege to edit logic and documentation, but only the supervisor has the privilege to update the Master Copy. Unauthorized changes are minimized, greatly reducing costly errors. In addition, because the only functions displayed on screen are those for which the user has assigned privileges, training time is significantly reduced.

 

top

 

VERSION CONTROL

Version control features make it easy to maintain accurate records of which software version is in use, when changes were made and who made the changes.

Maintain A Current Copy

In the AutoSave client/server environment, the server stores the device program files in their native file format, (e.g., A.I., 6200, RSLogix, ProWORX, Step5), depending on the type of program. When the client requests a program from the server, a copy of the files, along with the latest documentation, is sent to the program panel for use by the client. A lock is created so that other users are advised of who else is using the program, when and where. When the files are sent back to the server, the client compares them to previous versions, and if changes are detected, specified users can be notified. Since the Current Copy is stored on the server, authorized users can access the latest copy, enhancing productivity and safety. (When a device program is downloaded, all users can be sure they are downloading the most recent "known" version.) In addition, the need for floppy disk backups is eliminated, greatly reducing the problems caused by viruses.

Support And Control Multiple Versions

AutoSave automatically maintains a designated number of previous copies, called Ancestors. Utilizing an Ancestor setting of "4", for example, maintains the Current Copy, as well as the three preceding copies. When a change is made, a new Current Copy is saved and the oldest copy is deleted. Of course you can maintain as many copies as required (up to 9,999). To ensure that all copies are retained for as long as needed, it is also possible to set a minimum amount of time during which Ancestors will be maintained (e.g., one week, one month, or more). Any Ancestor can be recalled quickly. For some PLC types, the logic/data/register/force table of each copy can be compared to its preceding copy or the processor and the results of each compare can be displayed.

Heighten Version Security

For optimum security, user-saved, named Versions cannot be created automatically. Each Version must be created and described by authorized users with appropriate privileges. Only authorized users can compare and recall Versions. A maximum number of desired Versions can be specified for a program or device. If that number is exceeded, users are notified via e-mail.

 

top

 

AUTOMATED ARCHIVES/COMPARES

This is one of the most powerful AutoSave features. Compare and backup procedures can be initiated on a scheduled basis. You can be sure the most up-to-date program is always in use at each station and that a current backup is readily available. Groups of programs from the floor can be uploaded automatically. In addition, comparisons can be made among any of the following copies:

  • Current
  • Ancestor
  • Version
  • Processor
  • Local Client


Detailed, logic-to-logic and selected data table value comparison reports are generated and users are notified of miscompares or upload failures via e-mail. These e-mailed results, generated for scheduled, program, check-in or demand compares, are viewed via a Web browser that features hypertext links to detailed logic and documentation differences.

AutoSave supports standard plant networking protocols.

You can also direct-connect to the device or communicate via radio frequency (RF) link.

 

top

 

FULL AUDIT TRAILS

Industry and risk management requirements for archiving data are easily supported with AutoSave. Every step of the programming change process is documented and validated, and a detailed history of each version is maintained.

 

 

QUICK DISASTER RECOVERY

AutoSave maintains the latest copy of all device programs. If a processor faults, the correct program can be restored quickly. Disaster is averted.

 

 

AUTOMATIC CHANGE NOTIFICATION

Whenever a change is made to a program, designated users are immediately notified via e-mail. This enhances communication and productivity and saves time.

 

top

 

REGULATORY COMPLIANCE ASSISTANCE

AutoSave assists in Part 11 validation, FDA, OSHA, EPA and ISO compliance. You get the necessary help to meet guidelines for safety and quality assurance.

 

 


MODULAR CONFIGURATION

Modular configuration enables you to start small and add AutoSave modules as your needs grow.

 

 

CLIENT/SERVER ARCHITECTURE

MDT Software's client/server architecture provides seamless integration between AutoSave and your program panel software. The client is a secured, intuitive Windows 95/98/NT/2000-based application program on the programming node. The client can store and retrieve information on an as-needed basis and provide access to all the features of the server. The server acts as the master control center, coordinating all change-related activities from one central location.

 

top

 

PRINTOUTS AND REPORTS

In addition to audit trail reports, AutoSave provides other documents via a Web browser that help you manage your automation software more effectively.