MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
244
Once MKS Integrity is active system-wide, you cannot convert back to DesignTracker.
However, for existing DesignTracker users, provisions are available for enabling select users
to use DesignTracker temporarily. Future upgrades of Implementer automatically consider
and retain the settings you define.
Conversion Methods
Implementer provides two methods for converting issue management systems from
DesignTracker to MKS Integrity: system conversion without data retention or system
conversion with data retention. The latter method includes a feature that, after converting to
MKS Integrity, allows you to convert DesignTracker design requests (DRs) and service
requests (SRs) to MKS Integrity issues.
To determine which conversion method fits your business requirements, you need to answer
the following question:
Is DesignTracker in use with any DRs you want to keep?
If no, simply convert to MKS Integrity as described in “Converting Without Data
Retention” on page 244. This is the case for new installations of Implementer.
If yes, convert to MKS Integrity as described in “Converting With Data Retention” on
page 247, and optionally convert DRs and SRs to MKS Integrity issues as described in
“Converting DesignTracker Data to MKS Integrity” on page 431.
NOTE Prior installations of Implementer automatically installed demonstration DRs
and SRs. If these are the only requests present, you can delete them. You can also
delete any requests from a pilot project.
Converting Without Data Retention
The tasks described in this section perform a conversion that allows you to convert issue
management systems—that is, switch from using DesignTracker to using MKS Integrity,
without retaining any existing DesignTracker data. Converting to MKS Integrity without
regard for existing data is straightforward and allows you to quickly begin using
MKS Integrity.
This conversion method is applicable when DesignTracker is not used for issue management,
or if it has been used but you do not need to preserve any DRs or SRs that may exist from the
prior use. This conversion method deletes all existing DRs, SRs, DR entity lists, and any DR
references on current locks and lock history. It does not delete the actual locks or lock history.
This is a one time task. Once the conversion successfully completes, you can begin using the
integration.
Your user profile must have authority to System Control Maintenance to perform this task.