PROPOSED REVISED TC CHARTER

Name of the TC
OASIS DCML Configuration Management Technical Committee 
Statement of Purpose
The Data Center Markup Language (DCML) is an XML-based specification for representing the contents of data centers and information used in managing those contents. The overall goal of the OASIS DCML TCs is to support the development of a holistic set of standards related to the automated management of data center infrastructure. This TC is part of the OASIS DCML Member Section.
The purpose of the OASIS DCML Configuration Management TC is to create a data model and format for exchanging information about the contents of data centers and other IT resources, and the information used in managing those contents. Particularly, the Configuration Management TC proposes to target DCML’s relationship representations and interdependencies of elemental IT resources in a heterogeneous and open instantiation that is representative of configuration management function of Information Technology process frameworks, such as the Information Technology Infrastructure Library (ITIL), or Enhanced Technology Operations Map (eTOM).  As these process frameworks provide a references and guidelines to implement an IT operational model, the OASIS DCML Configuration Management TC will create the associated implementation-ready configuration dynamics to be used in prospective implementations of the process frameworks as their use cases are developed.  
The OASIS DCML Configuration Management TC will integrate all DCML work, including planned sub-specficiations for applications, services, networks and servers, by providing a common base of structure and representation, leading to a holistic, elemental-to-relational method required for standardizing the configuration management needs of IT process frameworks.  The Configuration Management TC specification will be used as the foundation by other OASIS DCML TCs or Configuration Management TC subgroups in creating DCML sub-specifications aimed at representing specific types of information. The DCML Configuration Management specification will define the overall approach, concepts and structures fundamental to DCML's description and manipulation of data center elements and the policies governing their management. The Configuration Management TC will define the process by which other working subgroups and TCs provide additional relationship mapping to extend DCML definitions supporting specific classes of elemental, service oriented, and process oriented applications, such as relationships of elements to each other on behalf of a service or process, or process relationships that require configuration management interaction.
The goal of the OASIS DCML Configuration Management TC is to enable the systems and people managing data center and other IT environments to exchange configuration, policy and operating information in a reliable, standardized manner that works across a wide variety of elements, products, methods/processes and topologies. An abstract, unified set of descriptions will allow IT managers to
•	enable communication among the many IT Services management systems; 
•	swap out and replace components or elements; 
•	upgrade or augment functions, such as by adding IT resources or services; 
•	plan for and execute the configuration and reconfiguration of newly installed hardware, software, services, or processes; 
all using re-usable referents and methods across a IT enterprise as it grows and changes. Among other things, by cooperating in a common set of definitions and methods, vendors and users will facilitate improved management and visibility, and enable increased automation of data center management by describing environments in a format highly accessible to automated processing.
Scope of the TC
The scope of DCML Configuration Management TC is limited to defining a data format for describing components and information used to manage those components, use cases driving the format, and the process by which the data format can be extended. The configuration management specification will define rules and conventions for naming, extensibility, representation in XML, security, processing of DCML documents, referencing and incorporating outside information, versioning, and other fundamental concepts. However, DCML will be designed to interoperate with a variety of other models and methods potentially useful to a described IT enterprise of group of IT enterprises or systems.
To fully realize the goals described above, much more is needed. For example, data in DCML format must be transferred between systems using some kind of protocol; the data must be accessed using some kind of application program interface; and all this must happen within one or more implementation frameworks. In addition, successful implementation and adoption of the DCML standard may require the development of ancillary materials such as implementation guidelines and certification frameworks. Such things are important work areas for future TCs, but they are explicitly outside the scope of the OASIS DCML Configuration Management TC
List of Deliverables, with Completion Dates
The DCML Configuration Management TC will produce the following deliverables:
•	DCML Configuration Management Requirements Document to be completed by  [date]
•	DCML Configuration Management Use Case Document to be completed by [date] 
•	DCML Configuration Management Taxonomy Document - Provide a consistent Taxonomy (for content types, hierarchies, attributes and relationships between them) to go along with the standard data format. This is to provide a standardized framework of semantics for the data that will enable automation, management and optimization of the DC environment to be completed by [date]
•	DCML Configuration Management Specification v1.0 to be completed by [date] 
•	DCML Configuration Management Specification Users Guide to be completed by [date]
Audience
We anticipate the work of the OASIS DCML Configuration Management TC will be used by a number of groups:
•	Process frameworks looking to standardize the implementations of configuration management processing or process relationship mapping in an iteratively implemented manner, using DCML
•	Other TCs or subgroups defining DCML sub-specifications for particular DCML scenarios (e.g., process mapping, service mapping, metadata relationship mapping with DCML’s configuration management implementations, etc.) 
•	Future TCs tackling the out-of-scope work items mentioned above 
•	Enterprises looking to create implementations of configuration management and configuration artifacts in their IT operational models and process framework implementations
•	End users and vendors seeking to create bilaterally agreed upon DCML extensions for particular DCML applications
•	The general public with an interest in learning more about DCML, configuration management dynamics, and IT process framework implementation standardization
Language
The TC will conduct its business in English.