Did you forget your: Username / Password ?

Microsoft

TechWell

Home

CM Basics

The Differences Between CM and DM

Written by Cynthia Hauer

Sunday, 11 July 2004 16:00

There are many differences – and they are vast! This topic comes up quite often, and again in a recent discussion thread in the Forums at CM Crossroads. So, it seems like a good opportunity for us to hash it out.

As a reference point, let’s return to the most recent exchange wherein one person asked “Does anyone know what is the difference between Data Management and Configuration Management, according to CMMI?” The question fueled an exchange wherein several points were made:

CM is inclusive of DM, DM is inclusive of CM;
DM is evolving in the CMMI, even as we speak;
Who cares about the CMMI?
Data managers maintain the problem reporting systems, control boards, document control, and identifies, controls, traces the changes, report status, and audits those activities;
CM is basically limited to the capture and control of product data (and other kinds of data);
CM is responsible for the BOM;
CM is responsible for much more than the BOM;
DM is a tool that CM uses to accomplish tasks, and is, thus, a subset of CM;
DM is broader than product data and also includes data at the enterprise level;
CM, DM, and PMI are interrelated and potentially redundant;
CM and DM are enterprise level tasks, more and more; and,
CM and DM are not enterprise level tasks, and appropriately so.

Lots of food for thought, huh? And many complementary and conflicting views of DM, CM, and their respective roles in the organization. Since we all do CM and DM, let’s try to provide a better and more thorough response, and in the process, learn something ourselves.

DM has had to assume a lot of new responsibilities, with the advent of digital data and its delivery or access, instead of delivery. CM is used to having DM perform what I would term “traditional” functions – those that CM is comfortable with, and those that – let’s face it – CM doesn’t particularly like to do. That has hampered DM’s progress a little bit – breaking out of its place has been tough. It had to “grow up,” and reach to define new ways to help in the enterprise.

What I’ve noticed for the past 3-4 years, as we’ve reinvented DM, is that CM is frequently the least happy of all of our functional partners to see the progress we’ve made in DM – and though we’ve struggled to provide a better complement and support to CM, in our efforts, CM hasn’t always been a willing partner in our success, now or in the past. Why is that, do you think? Is it that DM is really perceived as so needless and inept that no improvement is really deemed possible or desirable, by CM? Is it true that, as we in DM have striven to tackle enterprise data challenges, CM feels that the craft of CM doesn’t really need to be extended to business data, and/or the enterprise? Why is that, if it’s true? Should DM remain bonded to its filing cabinets, its CDRLS and SDRLS, its deliveries, and status accounting functions? Is the DM function so “clerical” that “anybody can do it” – or is it really that once DM evolves to a better place, that the fear is that “anybody” cannot do it, after all? Is CM “comfortable” with DM’s traditional role? Does CM, and rightfully so, perhaps, “fear” DM’s success? Because we, in DM, don’t fear our failure, and we don’t even fear our current and future success.

If you think I’m smacking you upside the head with these questions, in an assertive way, you’re right! I want to provoke a dialogue that will provide some real guidance, some essential feedback, and some thought from all of you – and depending on the answers that I get, it’s going to influence our next big challenge in DM: reintegrating ourselves with CM – or NOT doing that. Because if we cannot define the new intersection of our complementary roles, then DM needs to simply move on .. eclipse CM, do an end-run, and leave those who cannot and will not “believe” in the dust of their own failures and myopia. So tell me what you think! When we can, amongst ourselves in our two complementary disciplines, define what we think – we can then work to a future that means the most success for both CM and DM.

Cynthia C. Hauer is the Chief Executive Officer of Millennium Data Management, in Huntsville, Alabama. She has 21 years of experience in Information Technology which includes extensive involvement in CM, DM, data base design, user interface, data storage, CALS and all facets of system design and implementation. Ms Hauer holds a Bachelor of Science in Computer Science and is certified as CMIIC and CCDM, certifications in both ICM/CMII and NDIA, respectively. Cynthia is an occasional contributing editor for the CM Journal and writes a regular "rant" for the CM Basics newsletter.

You can reach Ms. Hauer by email at chauer@cmcrossroads.com.

Set as favorite

Bookmark

Email this