orm For example, the format an application uses for customer account numbers may not agree with the IIC's existing database. If account number formats cannot be configured into the system, it could take custom coding to alter the application. Customization can also be highly complex, such as adding a custom module to the application to add necessary functionality. In general, customization is more time consuming and expensive than configuration, making graphically configurable packages attractive. It is rare that an IIC will deploy an OSS platform without performing some customization on its various components. One of customization's most serious implications is a corresponding increase in the Total Cost of Ownership (TCO). Customization not only requires more effort to implement, but also needs more maintenance support once implemented. As the OSS platform changes and evolves, those pieces that have been customized must change as well, creating development and cost issues in the long run. Unlike periodic vendor releases and upgrades, the IIC will not share the cost of maintaining its customized components across a broad customer base. 3.2 Packages, Frameworks and Toolkits, and End-to-End Solutions Some OSS vendors offer solutions that are 80 to 90 percent complete on delivery. They require some configuration to implement but very little, if any, customization. Generally, these applications are highly specialized and focus on one or a few related areas, such as interconnection or ATM activation. Being designed for integration as one piece of an overall OSS architecture, they tend to have robust APIs as well. Companies that offer such "out-of-the- box" systems tend to use or partner with systems integrators to handle installation and implementation, allowing them to focus on product support and development. Rather than full-blown applications, some vendors offer frameworks or toolkits that require heavy customization and/or configuration. These products generally come with some kind of core engine around which oth