Hello Fred,
I outlined both Services and Processes as
target points. Configuration Management is a Process under ITIL, and as
such directly in the purview of the DCML efforts for creating interfaces to. In
the Enterprise Management space (which I deal with daily), the mapping of
processes, services, and capabilities with interfaces must be achieved in
various manners, so as we look to approach both Services AND Processes for the
sake of taking the most prescriptive intelligence on a service or particular
process (in our case, the IT Process Frameworks are where we're initially focused, and we'll
work our way UP from that) – so, IMHO, I think we're
looking to formulate baseline process engineering and requirements for
processes and services, and in particular, direct reference implementations of
processes on specific process frameworks, beginning with ITIL and in parallel
SOA.
And, since I'm
looking for the group to discover/verify/document the generally approved best
practices as defined by SMEs in an area (Robin, EDS ITIL SMEs, and input from
the itSMF, OGC, and so forth – who BTW should be able to certify/verify
such information) – which are then to be used by the
Interfaces/Implementation subgroup for codification – the exercise is not
to be done in a vacuum. I don’t think we're
trying to provide an ISV with their OWN personal implementation of a
domain-based tool, but a prospective choreographer or orchestrator WILL use the
RIs we provide as a starting point – which is what we should strive to
achieve. In addition, the ITIL framework is a best practice of IT Service
management processes, but its NOT the only one, even in the IT Space. its
just a very dominant one in the industry now, and therefore makes a lot of
sense to provide RIs for a good starting point for the industry. From my experience
with clients and implementers, it will be WELL received if we do…
Regards,
jDT
J. Darrel Thomas
Distinguished SE
Chief Technologist, Datacenter Services Portfolio
Electronic Data Systems Corporation
5400
Legacy Drive
Mail Stop H3-5A-34
Plano, Texas
75024
972-797-9695 (Office)
972-679-5943 (Cell)
(Email)
"Of all the things I've lost, the one I miss the most is my
mind..."
This message is for the designated
recipient only and may contain privileged, proprietary, or otherwise private
information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email by you is
prohibited.
From: Cummins, Fred A
Sent: Monday, October 31, 2005
8:23 AM
To: Thomas, Darrel;
;
Subject: RE: [dcml-frame]
Definition of Process Subgroup
Darrel,
This seems much too ambitious to me.
The key to defining DCML standards is to define the interfaces to services.
The most valuable thing the process group is to define the services and their
input/output requirements (in general terms). These should then be
considered in terms of business value and market acceptance. This is
critical input to for definition of interfaces by the interface group.
Note that we should not be defining best
practices processes, nor the implementations of tools/service solutions. Best
practices are the domain of ITIL, and implementations are the domains of
product vendors. The interfaces define how they fit together and should
be the domain of DCML/OASIS specifications.
Fred
From: Thomas,
Darrel [mailto:]
Sent: Monday, October 31, 2005
1:01 AM
To:
;
Subject: [dcml-frame] Definition
of Process Subgroup
Importance: High
Hello All,
As promised (and it’s a bit late by my standards), I'm attaching thoughts on the work
efforts of the Process Subgroup. Please reply with comments and suggestions
for additional work function and outputs....Robin, please review and provide
input, as I think you have a lot to add here..
Regards,
jDT
The Process subgroup is tasked with defining the standard processes,
interdependencies, and requirements for the Interfaces/Implementation Subgroup
to use to create DCML standard implementations and reference models. This
include the definition of inputs and outputs, best practice workflows and
process flows, and inter-process dependencies from one targeted process
framework to another. Prospective processes to be defined and mapped
include:
·
The Processes of the ITIL Process Framework
·
Service-Oriented Processes
·
Business Processes
Outputs from the mapping and modeling work by the Process subgroup will
include:
-
Process diagrams and models outlining each process to be
implemented by the Implementation/Interfaces subgroup
-
Use cases to accompany process models and diagrams, as well as
prescriptive relevance to industry usage
-
Specifications on interrelationships for a process to other
processes
-
Other interfaces and dependencies on non-process oriented
artifacts, if any, to accompany process outputs
-
Detailed description and definition of process to be
mapped/modeled
-
Detailed project plan with milestones and dates
-
User Guides and Documentation
J. Darrel Thomas
Distinguished SE
Chief Technologist, Datacenter Services Portfolio
Electronic Data Systems Corporation
5400 Legacy Drive
Mail Stop H3-5A-34
Plano,
Texas 75024
972-797-9695 (Office)
972-679-5943 (Cell)
(Email)
"Of all the things I've lost, the one I miss the most is my
mind..."
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
