Standard

1. The name of the specification

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

Implementing the CMDBf standard simplifies the process of managing related configuration data stored in multiple CMDBs and MDRs and supports the creation of an ITIL v3 Configuration Management System (CMS). It also provides IT personnel with a more complete picture of their entire IT environment, allowing them to more effectively manage the components in their IT environment and better utilize configuration data to streamline management tasks and resolve issues without the need of creating a single monolithic repository of configuration data.

With a standard way for vendors and tools to share and access configuration data, organizations can use their CMDBs to:

• Keep track of changes to an IT environment
• Better understand the impact of proposed changes to the IT environment.

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

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

5. URI for the normative text of the specification

SOURCE

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

7. URI for the SDO

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

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

SUBJECT

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

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

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 Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support

OPTIONAL

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

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

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

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

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

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

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

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

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

• : Please identify where reference specification is within SDO member organizations or not and current level of approval as the level of question.