ent time between the first run of analysis reports on the staging database and the start of UAT. This allows for several iterations of data cleansing and re-migration of any data that has "fallen out." This covers pipeline data, dynamic data coming over interfaces into the legacy systems and billing data impacted by bill cycles. SUPPORT ORGANIZATION AND COST Beyond migration and conversion, an IIC naturally must consider the long-term costs of supporting the OSS platform. Supporting it generally means maintaining a strong IT organization, which is a major cost The Ultimate Guide to Building and Delivering OSS/BSS component. The people and skills that make up this IT organization will vary depending on the IIC and it's OSS infrastructure, which in turn affects overall costs and cost break-down. 3.1 Examining the IT Organization The typical IT organization required to run, manage and support the OSS platform includes four components or groups, each assigned specific responsibilities: Application Development. This component includes the OSS implementation program resources, integration development and custom- solutions development, such as data warehouse and Web portals. Maintenance. Maintenance includes all ongoing support of deployed applications, tier 2 and 3 support (explained below) and upgrades. Operations. Operations typically include the data centers, system administrators, database administrators and a general help desk. Operations may also include some project management for new IT initiatives that are not OSS related, such as opening new offices or data centers. LAN/WAN and Desktop Support. This group includes all other IT deployment and maintenance functions that are unrelated to OSS. It handles network connectivity, intranets, Internet and desktop configuration and support. Maintenance Some of the resources required for maintenance are similar to what is required for implementation, namely application expertise, business process knowledge and an understanding of how process impacts application configura