A communiqué from Ben Eng (Nortel) reports on "a significant XML Schema effort that has been underway in the 'OSS Through Java Initiative' for the past year. The first three API specifications being developed are for Service Activation, Trouble Ticketing, and Quality of Service; extending across all OSS through Java specifications is a common J2EE Design Guidelines document. All three API specifications are currently in Community Review ending April 16, 2001, at which time they will be promoted to Public Review status. We specify APIs in three styles: EJB session interfaces with Java Value Types, EJB session interfaces with XML Value Types, and XML messaging (transportable by JMS, ebXML/SOAP, or whatever). There is functional equivalence between the styles. Each OSS API will specify all three styles of APIs; specifying one automatically generates the other two. The latter two styles of interfaces are specified in XML Schema."

From the web site:

The Trouble Ticket API specification will address ... the specification of the XML-based messages that may be sent to, and received from, a trouble ticket system and the specification of the strongly-typed object-based events and XML-based events emitted by a trouble ticket system..."

To meet the ever-increasing need for bandwidth in communications services areas, service providers need a new approach to providing operations support system (OSS) solutions. Current OSS technology cannot cope with the rapidly increasing scale of networks, the diversity of communications technology, shortened time to market for new services, and heightened expectations for availability and reliability. In short, service providers need carrier-grade OSS solutions in Internet time. The members of the OSS through Java Initiative are convinced that the fastest and most flexible way to develop OSS solutions is to embrace a multi-tier architecture, based on reusable components and container technology, with client access either by tightly or loosely coupled mechanisms. Furthermore, they believe that Java 2 Enterprise Edition technology (J2EE) is the simplest and most reliable means of embracing such an architecture. To promote the adoption of a component-based approach to developing OSS solutions, the members of the Initiative aim to kick-start a component marketplace that can ultimately offer interchangeable, interoperable components that can be rapidly assembled into OSS solutions. Moreover, they are convinced that such an approach has benefits for all stakeholders along the value chain: equipment vendors, independent software vendors (ISVs), system integrators, and service providers.

From the announcement: "the OSS through Java[tm] Initiative. This is a new industry process to define and implement Java technology-based APIs for Operations Support Systems (OSS) and Business Support Systems (BSS). ADC Telecommunications, Crosskeys, Cygent, Infovista, Objective Systems Integrators, and Remedy are already participating with the founding members of this Initiative, adding resources to the work in progress in their specific areas of expertise. The initial focus of the Initiative will be to address the application areas of Trouble Ticket, Quality of Service and Service Activation for 3G wireless networks. Innovative OSS solutions are needed for 3G wireless networks in order to operate new applications supporting both voice and data, and delivering end-to-end services. The OSS through Java Initiative is designed to accelerate the development of new OSS components. By complying with standard APIs, these new components should be easier to integrate faster with new network equipment, as well as between each other to facilitate rapid rollout of 3G networks and services. Under the Initiative, the development of demonstration systems is planned, to prove the ability of the APIs and to demonstrate the applicability of Java 2 Enterprise Edition (J2EE) technology for OSS solution integration. Leveraging the success already provided by J2EE technology in the areas of enterprise and e-commerce, can help service providers to jumpstart the deployment of seamless OSS systems in which all applications function together. Currently service providers face a fragmented OSS market, filled with proprietary systems that cannot function together without costly integration work..."