Migration and Archive

Data migration will be executed in the following steps:

1. Data Extraction: This step involves the extraction of the data from BAA’s existing data stores into the staging area. This will involve the extraction of data from the data stores into either Microsoft Excel spreadsheets or CSV files, enabling them to be easily imported into the staging area.
2. Data Transformation and Preparation: This stage will involve the transformation of data in various formats into a common set as required either by the Target application or the Data Archive. The transformation of the data will include bringing all the date fields into a single format, single set of values for lists, etc. The data will then be prepared by checking for duplicates, incorrect values and orphan records. This will then be reported to the business for verification and cleansing of the data. The data will then be extracted into the formats required either by the Tranche 1 solution or the Data Archive as mentioned below:
   • All current and new projects in Q5 and projects due to start from April 2013 i.e. Q5+1 will be extracted in the Tranche 1 and data archive format files, and
   • Additional information for completed projects in the current Quinquennium (Q5) will be extracted into the Data Archive data format files.
3. Data Verification: The data will then be verified to check if it meets the format and required standards either of the Tranche 1 solution or the Data Archive. Then suitable changes will be made to the required software to ensure that the data is at acceptable standards.
4. Data Loading: Finally the transformed and prepared data is loaded into the Tranche 1 solution and the Data Archive as required. Initially this data will be loaded into the test area, where the business can check the data for its functionality and usage as a part of data migration testing before the final uploads.

The data migration workstream will be progressed in the following phases:

1. Design: This phase will include the analysis of all the data stores in scope and a detailed design of the data will be completed with the outcome going into the Data Migration Design document. The design document will identify all data sets, types of data – lists, calculated values, etc and map the data from the existing data stores to relevant fields within the acceptable data formats for the target data stores.
2. Build: The -data transformation and preparation software will be prepared in this phase and unit tested to ensure that they function without any defects or errors.
3. Testing: This phase will involve running the migration software in the test environment for the business to test the migrated data against the application to ensure that the data is functional and meets the needs of the business. The migrations will be repeated for a maximum of 3 cycles to ensure that all defects are eliminated to ensure a smooth migration. This will also be a precursor to the actual migration run while providing the business stakeholders with a view of the migrated data enabling them to test the application functionality to its full.
4. Implementation: This will be the final execution of the data migration software into the production environment as a part of the go-live process. The business stakeholders verify and sign off the data prior to its release for user access.

Data Migration approach for PPM Standalone

The approach for PPM data migration is to take information for the current concepts/proposals that are captured in the Business Case excel workbook and import it into PPM. This will be done using either PPM import or using PPM Scorecards, depending on the data quality delivered by the business. No data will be removed from the original spreadsheets, which will be retained by the business.

or Tranche 1 solution.

Since PPM Standalone is separate from Tranche 1, its data migration process will not be mentioned in the Data Migration Design Specification .