 with a reduced cost of ownership. The Enterprise JavaBean (EJB) component architecture is designed to hide complexity and enhance portability by separating complexities inherent in OSS applications. Rapid integration and deployment of a new OSS application can be done by OSS through Java initiative's framework due to standard EJB components that are already equipped with connectors. Application integration capabilities are provided for server-side applications by APIs that are defined within the initiative using J2EE platform and EJB architecture. A standard set of APIs using Java technology for OSS and BSS can be defined and implemented by using OSS through Java initiative. Members of OSS/J are leveraging standards from 3rd Generation Partnership Project (3GPP), Mobile Wireless Internet Forum (MWIF), and the TeleManagement Forum (TMF) to Standard Interfaces implement common Java APIs and provide a source code that can be made freely available to the industry. OSS/J implementation groups include telecom equip- ment manufacturers, software vendors, and systems vendors that are formed to develop and implement interoperable and interchangeable components to build OSS applications. Addressing the lack of interoperable and interchangeable OSS applications for the OSS industry is the goal of the initiative. Developing and implementing com- mon APIs based on an open component model with well-defined interoperable protocols and deployment models serve to accomplish the goal. OSS/J initiative is performed under the open Java community process (JCP). Using JCP the initiative will develop the following for each application area: Specification documents: It details the interface APIs. Reference implementation (RI): This is a working version that facilitates use of the APIs. Technology compatibility kit (TCK): A suite of tests, tools, and documen- tation that will allow third parties to determine if their implementation is compliant with the specification. Production of demonstration systems to validate the OSS/J APIs agains