安达信咨询方法与工具资料库convapch.docVIP

Basic Vegetable Products Business Process Simulation Conversion Approach Deliverables Doc: \ADMIN\PROJPROC\CONVAPCH.DOC Page PAGE 1 of NUMPAGES 1 Revised: DATE \l 2/28/95 - TIME 7:41 AM Note: Contents based on conversations with Lee DeNoya (AC Atlanta Office). The following are “best practices” Conversion Approach deliverables from a Conference Room Pilot phase: A. Project Level Conversion Approach Memo outlining: - overall data gathering techniques to be used (e.g. automated, report-based, manual forms, etc.) - overall data entry techniques to be used (using users over temps is best practice) - overall data verification techniques to be used (answers question “how do I know what my Production environment represents”) - entity management approach during conversion file builds - conversion tracking/control mechanism to be used (e.g. spreadsheet reference) - overall conversion task timeline - discussion of relation to other neighboring tasks (User Training, User Test and “Conversion Week”) B. File/Field Level Conversion Approach Memos, each one outlining, for a specific file: - approach to use for data gathering (source) - approach to use for data entry - approach to use for data verification - data approval (sign-off) requirements - for certain key files (e.g. Resource Master, Customer Master, etc.), details of how data for key fields will be gathered, entered, and verified - approach for on-going data maintenance - between initial data load and “go live” date - after implementation C. Conversion Tracking/Control Spreadsheet, showing for each file the: - conversion data “owner” or “owners” (e.g. KC vs. Modesto) - on-going data maintenance “owner(s)” - high-level approach (automated, manual, combined) - target/actual completion dates for: - approach completed - gather/enter/verify procedures developed - data gathered - data entered - data verified (sign-off obtained) - users trained on data gather/enter/verify p