 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 91: OSS Trouble Ticket API
Note that this JSR was completed under JCP 2.1. The following information has been updated from the original request. 2006.11.22: The Maintenance Lead role changed to Frox Communication and the JCP version changed to 2.6. Maintenance Lead: Michael Nidel E-Mail Address: michael.nidel Telephone Number: +41 55 254 1239 Fax Number: +41 55 254 1264 2005.10.28:Maintenance Lead: Axel Terfloth E-Mail Address: axel.terfloth Telephone Number: +49 231 47642 201 Fax Number: +49 231 47642 554 2005.02.25: The Maintenance Lead role changed from MetaSolv to IPValue.
Maintenance Lead: Thomas Schmal E-Mail Address: thomas.schmal Telephone Number: +49 231 47642 0 Fax Number: +49 231 47642 554 Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Nortel Networks Name of Contact Person: Pierre Gauthier E-Mail Address: yaic@nortelnetworks.com Telephone Number: +1 613 763 2281 Fax Number:
+1 613 765 7387
Specification Lead: Pierre Gauthier E-Mail Address: yaic@nortelnetworks.com Telephone Number: +1 613 763 2281 Fax Number: +1 613 765 7387 Co-submitters: Co-submitting Company: Clarify Expert Group Member: Diwakar Magadi E-Mail Address: dmagadi@nortelnetworks.com Telephone Number: +1 408 965 7336 Fax Number: +1 408 965 4632 Co-submitting Company: Ericsson Expert Group Member: Lar Tenfalt E-Mail Address: Lars.Tenfalt@emw.ericsson.se Telephone Number: +46 31 747 1974 Fax Number: +46 31 747 2942 Co-submitting Company: Motorola Expert Group Member: Frank Korinek E-Mail Address: frank.korinek@motorola.com Telephone Number: +1 847 576 1643 Fax Number: +1 847 538 5564 Co-submitting Company: NEC Corporation Expert Group Member:Hiroya Kawata E-Mail Address: h-kawata@bq.jp.nec.com Telephone Number: +81 45 939 2450
Fax Number: +81 45 939 2487 Co-submitting Company: Nokia Networks Expert Group Member:Stefan Vaillant E-Mail Address: Stefan.Vaillant@nokia.com Telephone Number: +49 211 9412-3973 Fax Number: +49 211 9412-3988 Co-submitting Company: Remedy Corporation Expert Group Member: Mark Buckallew E-Mail Address: mab@remedy.com Telephone Number: +1 650 254 4943 Fax Number: +1 650 903 9001 Co-submitting Company: Sun Microsystems Expert Group Member: Philippe Goujard E-Mail Address: philippe.goujard@uk.sun.com Telephone Number: +44 1276 689 414 Fax Number: +44 1276 677 121 Co-submitting Company: Telcordia Technologies Expert Group Member: Balakrishnan Dasarathy E-Mail Address: bdasarat@telcordia.com Telephone Number: +1 973 829 5038 Fax Number: +1 973 829 2645 Initial Expert Group Membership: Nortel Networks
Section 2: Request
Fault tracking and resolution is a time-consuming activity and one of the most useful tools available
to network and service managers is that of a trouble ticket system. Trouble tickets are essentially
fault
reports that are administered as documents. These documents are active
from the time a fault is reported, during its diagnosis, and until its eventual correction. They are then generally archived to provide statistical information. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Java 2 Platform, Enterprise Edition 2.3 What need of the Java community will be addressed by the proposed specification?There is a growing trend within telecommunications industry towards the use of J2EE for development of various aspects Operations Support Systems (OSSs). Without some form of standardization, there is a a risk of divergent specifications proliferating throughout the industry. 2.4 Why isn't this need met by existing specifications?There are no existing open Java API specifications for trouble ticket systems; existing API are vendor-specific. 2.5 Please give a short description of the underlying technology or technologies:he APIs will be defined on top of J2EE. The most important J2EE APIs for this JCP will be the following:
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)The prefix "javax.oss" will be used in all OSS JSRs, including those recently submitted, namely: "OSS Quality of Service API" and "OSS Service Activation API". Package names of all OSS JSRs will be co-ordinated to avoid ambiguous use. 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?The specification has no dependency on operating systems, CPUs, or I/O devices. 2.8 Are there any security issues that cannot be addressed by the current security model?None is anticipated 2.9 Are there any internationalization or localization issues?No. 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?No. 2.11 Please describe the anticipated schedule for the development of this specification.
|
