on. Naming standards are used to facilitate identification. In order to maintain appropriate version control for large, complex projects or for multiple, small projects or systems, a version control tool is recommended. Tools are typically used to promote versions from one environment to another (e.g. from test to production), and to manage configuration events, which include formal check-out, check-in, promotion, fallback and build processes down to the software component level. Release management focuses on packaging many changes within a single rollout. In general, as product development progresses, there are more constraints imposed on implementing changes in the product that often require the approval of higher authorities for requested changes. Maintenance Models Based on the significant cost to run and operate the OSS platform, many companies are looking for alternatives to in-house maintenance. Generally they consider models from outsourcers and Application Service Providers (ASPs). The question that arises is whether these solutions are realistic. For the ASP model to work financially for both suppliers and customers, there must be a one-to-many model SO that cost sharing is realized and Chapter 7 - Supporting the Life of an OSS Integrated Platform economies of scale are developed among many parties. In other words, the ASP must be able to provide a standard OSS package. Unfortunately, the full OSS suite is not well-suited to a one-to-many model. Companies have different business models, different business rules within their embedded processes, different product catalog structures, and different network configurations. All of these variables add complexity to the OSS suite. Further, if OSS is to be a key differentiator, then using a common platform that one's competitors might also use simply is not logical. Aspects of the OSS platform can be modeled into an ASP, such as interconnection gateways, and even billing systems, which typically operate somewhat independently from business processes and tend to 