Pennsylvania Department of HUMAN SERVICES

<System Name>

Conversion or Data Population Plan

<System Name>

Conversion or Data Population Plan

<Version #>

Revision History

Date	Version	Description	Author

Table of Contents

1.	Introduction	3

2.	Conversion Overview	3

2.1	Manual Conversion	3

2.2	Automated Conversion	3

2.3	<Work Order Name – WO-xxxx> Conversion	3

2.4	Assumptions	3

3.	Conversion Process	3

3.1	Data Elements, Rules and Mapping - Scenario 1	3

3.2	Triggering Events and Conditions	3

3.3	Subsequent Events and Conditions	3

3.4	Business Service Level Agreement	3

3.5	Exception and Error Handling	3

3.6	Non-functional requirements	3

4.	Conversion Approach	3

4.1	Pre-Process Preparation	3

4.2	Data Preparation and Cleansing	3

4.3	Mock Conversion Testing and Set-up	3

4.4	Phased Conversion	3

4.5	Post Process Clean-up	3

5.	Conversion Timeline	3

6.	Appendices	3

Introduction

[Summarize document content highlighting the key points in each section – no more than 1 page]

Conversion Overview

Manual Conversion

[Describe manual conversion processes here.]

Automated Conversion

[Describe automation conversion processes here.]

<Work Order Name – WO-xxxx> Conversion

[Describe the conversion processes required for this work order.]

Assumptions

[Describe conversion assumptions here.]

Conversion Process

[Outline the requirements and functional design for a scenario. Specify the data flow between source and target data store in the form of diagrams >

Data Elements, Rules and Mapping - Scenario 1

[Specify the source data elements, target data elements, properties of these data elements and mapping rules.]

Source	Target
Data Element	Description	Allowable Values	Field Type	Field Length	Cardinality	Mapping Rule	Data Element	Field Type	Field Length
<State>	<Description>	<CA, TX>	<String>	<2>	<Mandatory>	<Map to full state name>	<State>	<String>	<255>
<Employee.Name>	<The first name and last name delimited by space of the employee that approved the case. >	<Any alphabets>	<String>	<50>	<Mandatory>	< One to one mapping between Employee. Name and Person.FirstName. Segregate the first name to store it in Person.FirstName>	<Person.FirstName>	<String>	<50>

Triggering Events and Conditions

[Specify the events and conditions that will result in execution of the data conversion process.

Example:

This section describes the business events and rules that trigger the data conversion program to load customer data from CRM database to Finance database.

New customer accounts are created

Customer accounts are disabled

Accounts are delinquent

Customer requested to close the accounts]

Subsequent Events and Conditions

[Specify the events that will happen after the execution of the data conversion process.

Example:

This section describes the business events and rules that happen after the data conversion program updated the Finance database with latest customers’ data.

Delinquent accounts are sent to the collection department

Account balance is calculated for the customers]

Business Service Level Agreement

[Specify the SLA requirements such as frequency, latency and data volume associated with this data conversion process.

Example:

This section describes the SLA that the data conversion program should meet.

The program should load one million accounts into Finance database in less than two hours

The program should run once a day during off peak hours]

Exception and Error Handling

[Specify the exception and error handling requirements associated with this data conversion process.

Example:

This section describes the error handling requirements for the data conversion program.

The program should throw an exception when there are multiple entries for the same employee in the database

The program should roll back all records in a batch if a single record is not loaded completely]

Non-functional requirements

[Specify the auditing, logging, monitoring, scalability, and security non-functional requirements associated with this data conversion process.

Example:

This section describes the non-functional requirements for the data conversion program.

The design should allow parallel execution of multiple conversion program instances.

The design should allow use of load balancing capabilities of the data conversion engine]

Conversion Approach

Pre-Process Preparation

[Describe processes here.]

Data Preparation and Cleansing

[Describe processes here.]

Mock Conversion Testing and Set-up

[Describe the mock conversion testing and set-up processes here.]

Phased Conversion

[Describe the process for completing a phase conversion – if applicable.]

Post Process Clean-up

[Describe the process for conducting post process clean-up of the data, if applicable – these could be automated or manual.]

Conversion Timeline

Appendices