l processes rather than to create a fully integrated platform for B2B/B2C transactions. Even if they want to pursue eBusiness, ILECs may be limited by their current level of internal integration - and what it can or cannot provide. Some IICs thought about their OSS needs ahead of time and are better prepared for eBusiness. Still, systems are tough to integrate for any IIC. Newer OSS products are better designed for integration, but that does not make it simple to bring systems from different vendors together. For example, lots of failures have occurred based on a lack of APIs within applications, a lack of functionality within the APIs that are provided, and sometimes a disconnect between business processes and integration design. Furthermore, many IICs have integrated systems point-to-point to get things up and running. As they grow, they migrate to enterprise integration technologies, thus installing a flexible foundation on which to build eBusiness functions. Even with such integration, all OSS software does not support all of the new services rolling out. Application versions and releases only can keep up with SO many new technologies and equipment types. Consequently, there always might be some need for manual intervention. Engineers working with proprietary provisioning interfaces might remain in the mix. Most IICs, however, simply have not yet developed from a process and technology point of view to where they are entirely ready to adopt eBusiness other than in rudimentary ways. Chapter 3 - Automating the Internet Infrastructure Supply Chain 2.1 Why the Focus on Technology? We've returned time and again to discuss all of the technology problems IICs face. It seems that every barrier is a technology issue. It is fair to wonder why the industry is not more orderly. Why isn't there more cooperation in developing systems and processes? One issue is that there is simply a lack of commonly accepted standards governing technology development in the OSS market. Standards have not been developed nor have they taken