DCML CfM TC Use Cases
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
911
On Slideshare
911
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • On the title slide, the title should always be 28 pt font, and the subtitle (or name of speaker) should be 18 pt font, both in Arial. Arial is now the preferred corporate font for presentations. Please use Arial for titles, bullet text, charts and any other text on each slide. The photo on the title slide can be changed to an appropriate photo for your customized presentation. When using photographs, please remember the following: Photos should show interesting points of view Photo colors should be desaturated if possible, for a more subtle effect.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • In MOD we define the services required by the organization and manage all of the components as they relate to the services being consumed. The services can be IT services like email or bandwidth or they can be business services like the customer acquisition service or the plane departure service. Now services can be created and managed that relate IT to the business processes that drive an organization bringing IT and business operations closer together. When IT monitors and manages change at the business service level business operations will receive better service. It is this alignment between the two factions that we have been trying to achieve for so many years.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • If you choose to use plain text on a slide without photos or graphs, choose this layout. Subtitles should be 28 pt Arial.
  • This is the final slide in the presentation deck. If you do not have additional contact or URL information, delete all text except “eds.com”.

Transcript

  • 1. DCML: Use Cases in IT Service Management J. Darrel Thomas Chief Technologist, Hosting Electronic Data Systems Corporation
  • 2. Data Center Markup Language (DCML)
    • The only open, XML-based standard designed to achieve interoperability by providing a systematic, vendor-neutral way to describe an IT Service environment
    • Universal language that describes elemental, process, and service-oriented relationships between IT service entities and policies governing the management of such environments
    • Handles heterogeneous and semantic information required to manage at the service level
  • 3. The Problem DCML Helps Solve
    • IT Services Management requires a multi-dimensional approach
    • Mapping of interdependencies and inter-relationships at the elemental, process, and services level does not currently exist
    • Complex, heterogeneous environments require interchange standardization between management systems
    • DCML helps bridge this disparity using ontological and “like” meta-relationships
  • 4. IT Services Management Standardization Has Varying Domain-Based Initiatives to Address Its Dimensions… Service Desk Incident Problem Configuration Change Release Service Level Financial Capacity Continuity Availability Many standards have been or are being developed to address the INDIVIDUAL DOMAIN issues… Servers (CIM-SMASH) IPMI WS-* Storage (CIM-SMIS) WS-* Interface Elemental Business Process (BPEL, ebXML) Application (.NET, Java, SOA WS, UDDI, etc.) Industry (MDA, HIPPA, etc.) IT Foundation (LDAP, SMTP, etc) Purposeful Infrastructure (WSDM2.0, WS-*) Operating Systems (CIM-SMASH) IT Domain-Specific Elemental Etc. Network (CIM) WSDM2.0, WS-* Applications (CIM?) WSDM2.0/WS-* Service-Oriented IT Process Frameworks & Standards (ITIL, COBIT, BS15000, CMMI) IT Integral Packaging (OGSA/I, etc.)
  • 5. But, There is STILL Confusion with Possibly The Most Import IT Services Dimension – Interrelationships, Configurations, and Dependencies… Assistance? Un/Planned Events? Crises? Relationships? Adjustments? Production-ize? Guarantees? $$$$? Resourcing? Recovery? Accessibility? This area still looms as the enterprise/service provider’s most important inhibitor for standardizing IT Services Management. Servers Storage Interface Elemental Business Process Application Industry Infrastructure Purposeful Infrastructure Operating Systems IT Domain-Specific Elemental Etc. Elemental Relationships Operational Intelligence Service Dynamics Network Applications Service-Oriented IT Process Frameworks Process Dynamics IT Integral Packaging IT Domain/Element Relational Elemental Relationship Intelligence Service-to-Element Relationship Intelligence
  • 6. DCML Enables IT As A Service Employees
  • 7. Process Use Case: Instrumenting ITIL’s CMDB
    • Problem Statement
      • The Information Technology Infrastructure Library is a process-oriented framework expressing the best practices and components of IT Service Management and how to implement it. Customers require implementations of ITIL, and disparity in the ways in which it is implemented inhibits rapid standardization and adoption. DCML proposes to electronically instantiate the key relational aspects of the primary interdependency and relational process of ITIL, Configuration Management, as well as further instrumenting the process relationships that are iteratively used in the ITIL framework according to expected, patterned, and natural interactions.
  • 8. Process Use Case: Instrumenting ITIL’s CMDB
    • Success Criteria
      • Prospective enterprises looking to implement standardized operational models that use the ITIL framework directly use DCML to build Configuration Items (CIs) within their Configuration Management Database (CMDB), as well as roadmap all IT elements from a company’s ITIL-framed Definitive Software Library (DSL) and Definitive Hardware Store (DHS)
      • DCML would be used to create the data model and relationship schema for the DHS, DSL, and CI/CMDB entities of ITIL
      • DCML would also instrument standardized relationship mappings between ITIL processes, specifying their natural invocations as services are run across them.
  • 9. Process Use Case: Instrumenting ITIL’s CMDB
    • Solution Overview
      • Prospective enterprise develops CMDB, uses DCML’s schema and data model to create interrelated CIs for CMDB
      • CMDB stores CI with relationship mappings between DHS and DSL components, as well as interfaces, attributes, and parameters to create running services, systems inter-ITIL process communications.
      • Operational Model includes orchestration of CMDB-DCML components via management tooling and integration framework
      • Enterprise uses DCML’s meta-mapping of other elemental standards to gather elemental component characteristics and relate them to services and processes with integrations
      • Enterprise uses DCML to standardize the mapping of its existing and new resources into its relational/interdependent CMDB and operational model.
  • 10. Transformation Use Case: Discovering Configurations for CMDB Population
    • Problem Statement
      • Outsourcers need to be able to discover existing configurations in order to enable transformation and standardization of enterprises to emerging IT technologies and paradigm changes. In order to accomplish the task, tools or methods of relationship, interdependency, elemental/resource usage, and existing processes and workflows must be derived. DCML’s configuration/relationship mapping characteristics are ideal to be implemented in either tooling or operational processes to obtain relational information and existing
  • 11. Transformation Use Case: Discovering Configurations for CMDB Population
    • Success Criteria
      • Prospective enterprises looking to implement standardized operational models that use the ITIL framework directly use DCML to build Configuration Items (CIs) within their Configuration Management Database (CMDB), as well as roadmap all IT elements from a company’s ITIL-framed Definitive Software Library (DSL) and Definitive Hardware Store (DHS)
      • DCML would be used to create the data model and relationship schema for the DHS, DSL, and CI/CMDB entities of ITIL
      • DCML would also instrument standardized relationship mappings between ITIL processes, specifying their natural invocations as services are run across them.
  • 12. Transformation Use Case: Discovering Configurations for CMDB Population
    • Solution Overview
      • Prospective enterprise develops CMDB, uses DCML’s schema and data model to create interrelated CIs for CMDB
      • CMDB stores CI with relationship mappings between DHS and DSL components, as well as interfaces, attributes, and parameters to create running services, systems inter-ITIL process communications.
      • Operational Model includes orchestration of CMDB-DCML components via management tooling and integration framework
      • Enterprise uses DCML’s meta-mapping of other elemental standards to gather elemental component characteristics and relate them to services and processes with integrations
      • Enterprise uses DCML to standardize the mapping of its existing and new resources into its relational/interdependent CMDB and operational model.
  • 13. Service Oriented Use Case: Instantiating SOA Thru DCML and IT Services Management
    • Problem Statement
      • Outsourcers need to be able to discover existing configurations in order to enable transformation and standardization of enterprises to emerging IT technologies and paradigm changes. In order to accomplish the task, tools or methods of relationship, interdependency, elemental/resource usage, and existing processes and workflows must be derived. DCML’s configuration/relationship mapping characteristics are ideal to be implemented in either tooling or operational processes to obtain relational information and existing
  • 14. Transformation Use Case: Discovering Configurations for CMDB Population
    • Success Criteria
      • Prospective enterprises looking to implement standardized operational models that use the ITIL framework directly use DCML to build Configuration Items (CIs) within their Configuration Management Database (CMDB), as well as roadmap all IT elements from a company’s ITIL-framed Definitive Software Library (DSL) and Definitive Hardware Store (DHS)
      • DCML would be used to create the data model and relationship schema for the DHS, DSL, and CI/CMDB entities of ITIL
      • DCML would also instrument standardized relationship mappings between ITIL processes, specifying their natural invocations as services are run across them.
  • 15. Transformation Use Case: Discovering Configurations for CMDB Population
    • Solution Overview
      • Prospective enterprise develops CMDB, uses DCML’s schema and data model to create interrelated CIs for CMDB
      • CMDB stores CI with relationship mappings between DHS and DSL components, as well as interfaces, attributes, and parameters to create running services, systems inter-ITIL process communications.
      • Operational Model includes orchestration of CMDB-DCML components via management tooling and integration framework
      • Enterprise uses DCML’s meta-mapping of other elemental standards to gather elemental component characteristics and relate them to services and processes with integrations
      • Enterprise uses DCML to standardize the mapping of its existing and new resources into its relational/interdependent CMDB and operational model.
  • 16. Interoperability Use Case: Metamapping DCML and SDM Through Developmental Modeling
    • Problem Statement
      • Outsourcers need to be able to discover existing configurations in order to enable transformation and standardization of enterprises to emerging IT technologies and paradigm changes. In order to accomplish the task, tools or methods of relationship, interdependency, elemental/resource usage, and existing processes and workflows must be derived. DCML’s configuration/relationship mapping characteristics are ideal to be implemented in either tooling or operational processes to obtain relational information and existing
  • 17. Interoperability Use Case: Metamapping DCML and SDM Through Developmental Modeling
    • Success Criteria
      • Prospective enterprises looking to implement standardized operational models that use the ITIL framework directly use DCML to build Configuration Items (CIs) within their Configuration Management Database (CMDB), as well as roadmap all IT elements from a company’s ITIL-framed Definitive Software Library (DSL) and Definitive Hardware Store (DHS)
      • DCML would be used to create the data model and relationship schema for the DHS, DSL, and CI/CMDB entities of ITIL
      • DCML would also instrument standardized relationship mappings between ITIL processes, specifying their natural invocations as services are run across them.
  • 18. Interoperability Use Case: Metamapping DCML and SDM Through Developmental Modeling
    • Solution Overview
      • Prospective enterprise develops CMDB, uses DCML’s schema and data model to create interrelated CIs for CMDB
      • CMDB stores CI with relationship mappings between DHS and DSL components, as well as interfaces, attributes, and parameters to create running services, systems inter-ITIL process communications.
      • Operational Model includes orchestration of CMDB-DCML components via management tooling and integration framework
      • Enterprise uses DCML’s meta-mapping of other elemental standards to gather elemental component characteristics and relate them to services and processes with integrations
      • Enterprise uses DCML to standardize the mapping of its existing and new resources into its relational/interdependent CMDB and operational model.
  • 19. Model-Based Management
    • Knowledge drives management
    • System Definition Model: a modeling language that is used to capture a formal model of a system
    • Includes all information pertinent to deployment and ongoing operations
  • 20. SDM Concepts
    • The boxes: systems, subsystems, components
    • The lines: relationships
      • Containment with rich compositing semantics
      • Hosting with specific semantics
      • Several types of communication and dependency
    • An extensible class hierarchy
    Extensible Œ  Ž
  • 21. Domain-Specific Knowledge
    • Model contains “ all information pertinent to deployment and operations”
      • System topology
      • Developer constraints
      • IT policy
      • Installation directives
      • Health model
      • Monitoring rules
      • Service Level Agreements
      • Reports
    Extensible
  • 22. Applications of Model
    • Provisioning of distributed systems
    • Desired configuration management
    • Health monitoring, root cause analysis, impact analysis
    • End-to-end service level management
    • Capacity planning
    • VM and workload management
    Extensible
  • 23. Scale of Model
    • Hardware components inside a computer
    • Applications and server roles in one computer
    • Server farm
    • Distributed service
    • Services across trust domains
  • 24. Sources of Model and Policy Information
    • Development environment (Visual Studio)
    • IT staff through management tools
    • Discovery
    • Operational Monitoring
    • Error reporting
    • Model lives in XML manifest, travels with application
    Extensible
  • 25. SDM and DCML
    • DSI and SDM are broad platform initiatives
      • Modeling framework
      • Development tools
      • Stores, replication systems
      • Integration in the whole stack (SW and HW)
      • Management systems
      • A platform for the ecosystem
    • DCML is a heterogeneous inter-relationship mapping and representation format
      • Interchange format
      • IT Services CMDB standardization specification and heterogeneous dynamically updated model representation – both discovery-based and pre-instantiated
      • Multi-dimensional relationship and interface mapping between other standards and models (including feeds to other upper layer standards and initiatives)
  • 26. Thank You!
    • QUESTIONS AND ANSWERS
  • 27. Darrel.Thomas@EDS.Com