STANDARD

1. The name of the specification.

NGOSS (New Generation Operations Systems and Software)

2. A short statement (<100 words) of the purpose and function of the specification.

An integrated framework of technical specifications which may be used to develop Operation Support Systems (OSS and BSS) / Management Systems for the Communications / Telecommunications Industry.

3. The version number (or other distinct identifier) of the most recently approved version of the specification.

Release 4.5 - November 2004 (Usually, two Releases of NGOSS are produced each year - often a point and major Release) Release Notes accompanying Release 4.5 supplied with this form - for further information

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

NGOSS (New Generation Operations Systems and Software)

5. URI for the normative text of the specification.

www.tmforum.org

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

TeleManagement Forum

7. URI for the SDO.

www.tmforum.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Approved for Industry Release

9. The language or languages in which the specification is available.

English only at present - some parts of NGOSS available in other languages - eg eTOM

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

• Fault Management: Fixing broken resources.
• Configuration Management: Controlling a resource's operational parameters.
• Accounting Management: Recording and analyzing resource use.
• Performance Management: Controlling speed and efficiency of resource use.
• Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

• Physical layer
• Data link layer
• Network layer
• Transport layer
• Session layer
• Presentation layer
• Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

• Policy
• Management Infrastructure
• Physical Networks
• Logical Networks
• Physical Systems
• Logical Systems
• Physical Devices
• Logical Devices
• Applications

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

• Proposed work
• Contributions received
• Preliminary SDO draft
• Initial public review
• Final approval
• Product availability

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

As per TMF general IPR agreements

16. URI for the SDO's posting location, if any, for notices from participants or individuals regarding claims under number 15.

N/A

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

Compliance testing is part of the NGOSS Release

18. Known implementations of the specification (by owner name or URI).

Information on TMF web site www.tmforum.org

19. A list (or URI pointer to same) of the other specifications that are normatively referenced in the specification.

GB921 - enhanced Telecom Operations Map (business process framework)

GB921P - An eTOM Primer

GB921T - eTOM / ITU-T M.3400 Mapping Application Note

GB922 - SID (Shared Information and Data) framework - Concepts, Principles and Business Entities,

GB922 - Addendum 1C, a SID model of the NGOSS Lifecycle Business View Contract

GB927 - NGOSS Lifecycle and Methodology

20. A list (or URI pointer to same) of the other specifications that are explicitly referenced in the specification (except the ones listed in number 19).

NGOSS Release 4.5 provides the SID UML model in XMI, HTML, and Rational Rose.

21. A list (or URI pointer to same) of otherspecifications with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

N/A

22. A list (or URI pointer to same) of other specifications. (Whether or not substitutable.)

N/A