 development. APIs and message structures are defined for each application by the implantation group SO that the OSS components can be devel- oped and assembled into complete solutions. APIs are specified and implemented as EJB components. OSS applications are developed using these APIs. OSS/J is emerging as a widely accepted OSS/BSS standard that helps Telco to realize standardization of interface, benefiting the service providers with vendor independence. OSS systems developed the integration approach and construction approach using J2EE technology. Integration approach is intended to integrate existing applications. Construction approach develops EJB-based applications, where both application and its serving components are in the container. Easier portability and rapid application development are possible through EJB. Based on the standardized APIs, it is possible to develop vendor independent EJB connectors for various protocols like CMIP, SNMP, TL1, and the knowledge can be reused for multiple OSS/J systems. Developing EJB connectors itself as COTs components offers many opportunities and the knowledge can be reused for devel- oping connectors for proprietary protocols also. OSS/J model can address the impact of the emergence of rapid service creation environments like IP multimedia subsystems (IMS) and service delivery platforms (SDP) on traditional OSS/BSS systems. OSS/J delivers standard functional OSS APIs, each including specifications, reference implementations, conformance test suites, and certification process and source codes. Open IT standards form the basis of OSS/J technology. Use of OSS/J leads to a market of interoperable and interchangeable OSS com- ponents. OSS/J APIs include EJB and XML/JMS profiles, WS profiles, and WSDL interfaces for the common API. Vendors can be compliant to OSS through Java API by supporting any one of these profiles. Though OSS/J is generic it can be specialized to be model and technology specific. It provides coverage throughout the eTOM processes. OSS/J can be exten