Guide to Building and Delivering OSS/BSS End User Training System User Training Prepare Production Environment Prepare System Operational Operations Readiness Test Establish and Maintenance Configuration Control Cutover Move to Production Environment Operations Regression Testing Migration Strategy Data Analysis Data Migration Conversion Testing Data Migration Conversion Testing Data Migration Conversion Testing Data Migration Conversion Testing Figure 29. Migration Process Overview Typically, there are four tasks and readiness areas an IIC must undertake when moving or migrating its OSS platform to production: data conversion, release structure and configuration management, training and operational readiness and production readiness. Data Conversion. The Data Conversion process involves data identification, cleansing and migration into the new applications. Typically, only dynamic data, such as current orders, customers, trouble and network elements/circuits are migrated into the new OSS. Historical data, such as customer accounts that have been closed or orders that have already been fulfilled, is captured and stored separately. Release Structure and Configuration Management. Formal releases and integration cycles must be defined and communicated to the IIC's user community. This community can include internal personnel and external users, including wholesale customers or large corporate clients. Users must Chapter 7 - Supporting the Life of an OSS Integrated Platform understand what functionality is included in each release, both current and planned. The IIC must also establish a formal configuration management process to maintain control of changes to the platform from a hardware, software and functionality standpoint. It must also institute a change control process to provide business and IT users with the mechanism to request changes to the OSS platform's functions or processes. The change control process also provides executives with the means to evaluate and prioritize requests, often determining what to 