 Okay, I'm going to start the presentation, the first maybe ten slides or nine slides, and then turn it over to Susan. In addition to Susan and I being editors, Debra Henderson is the program director of the DM Box 2, she was for 1, 2. Also Eva Smith handles our technology end that we are going to get into. Well it's kind of exciting to evolve this framework, I mean this DM Box 2. And the framework that's coming out actually today or yesterday, I'm not sure technically it's still, it's working right, so give it a chance if it doesn't work right. But the framework has an outline for the next version and we're asking for commentary. So let me just say that we're going to talk about the chronology of the DM Box and then also the framework and then how to get involved. For those of you that have been around a long time, and I was when we started this. So I'm an oldie moldy. Back in the early days at Damus Chicago, when I was president I approached Damus Chicago because they wanted to put a guide together and I said let Damo International publish it. And that was the beginning, you know the model for data resource management standards came out in 88, 94 and then it morphed the guidelines for implementing data resource management and then two versions of that kept getting bigger and bigger and bigger. Then about 2004, 2006 timeframe, I don't know when, Debra went to Damus Chicago again and talked about putting together a body of knowledge because they were thinking about updating their versions of the guidelines. And so we had volunteers step up, Mark Mosley stepped up to be editor and I don't know, you came in later I think. Anyways, Mark put out a framework back then and if you remember it, it kept going through versions and versions, but it wasn't open up to the Damo public. It was a select group that would review the document, which is okay. First time around they didn't know what to expect. And that particular framework ended up being translated into a lot of languages, as you can see right up here. Ben Hu over here had the Chinese version translated. So we have a lot of colleagues around the world that are willing to do this work. The first EMBOP came out in 2009 and the dictionary came out, I think it was first, wasn't it? The dictionary was first. Okay. Mark put, well what was happening was there was a need for defining terms. And so Mark spun off the dictionary and then the EMBOP came together, took four years to publish from conception all the way out to publication. And now it is available in many different formats through our colleagues, Steve Holberman, who is here at this conference. He's our publisher. Translations are occurring, which you know about right now. Peter mentioned Japanese, the Portuguese versions coming out in 2011. And I believe the Chinese version is still being worked on, isn't it, the translation? July. Excellent. Wow. So it's really, really great to see this. And to be honest with you, the penetration in companies has been fantastic. And if you go to some of the presentations at the conference, you will hear how companies are adopting the body of knowledge in their companies to structure the data-managed practice. And even when I interviewed at this upstate, you know, upstate New York health care insurance company, you know, my goodness, they had the framework up. They knew about it. And I thought, oh, this is something. It's penetrated into a smaller, you know, a medium-sized company. And I thought, this is fantastic that, you know, we're getting traction all over the world. The new dictionary came out last year. Susan was the editor. She put a lot of work into it. And it greatly expanded. One of the reasons I did is because we looked at the CDMP exams and picked up terms from there. And I think there were other sources, too, right, for the expansion. But it's quite a bit bigger. And that's also been well-received. And I'm going to turn it over to Susan. She's going to continue. And then later on, we'll look at the framework. Okay. What I usually do is I will try and find out all the commentary. I've been doing a lot of presentations, looking for commentary. I've been going to DAMA chapters and asking for commentary. I basically go over a chapter and say, okay, now, what can we do better about this? What do we stop? What do we start? And what do we continue? And I want you to get your feedback now. This is audience participation time. Wake up now. For the DIMBAC, what are the main things that you can see that would make the next version better? Yeah. Well, let's just get a list of the things and then we can see if we covered them when we go to the framework. Okay. I think you had. Okay. So better communication with the authors. Okay. Okay. It's going to be probably me, but we're going to, when we get to the author part of the show, we have to get the framework going. And then once we have the framework pretty solid, then we're going to start piecing it out to who gets to write what. Okay. Yeah. Okay. Let me see you and then you. Oh, yeah. It was a weird year. That's not going to happen again. It's not going to happen again. I do data modeling. I wasn't happy with it either. Yes. We can talk about it. If you see in the framework that there is more detail in certain areas, it kind of levels it out. Because before, the first version was inconsistently detailed in some ways. And so we want to try and get it down to the same level of detail across the board. Yes. Yeah. Okay. Yeah. And I know Eva suggested what, splitting out the knowledge areas into individual books. Turning it into an encyclopedia with different topics that the whole thing together is like this tall. I don't think it'll be this version. No. Maybe the next one. Yeah. In the future. Yes. Right. Right. Okay. Ben. Okay. Well. Yeah. Yes. Okay. You and then. You're going to be happy too. Yeah. Right. And it is in the framework outline. Definitely you're going to have your chance. Yes. Right. Right. One of the things we did work on was a set of complete author instructions to give to all the authors that outlines exactly what we expect back. So that. Plus the template. And there's going to. Yeah. And then there's a template too that you just kind of fill in. So. The formatting is there. It makes my life a little bit easier. Can you. Let me just talk about the author instructions because also besides the template and the instructions, we're expecting the authors to have to follow the outline that's going to be solidified in the framework. And that was not done last time by many authors. They kind of went on their own way. The reason I, you know, we did this was because I know as an author last time for the Dan Bach one, we really didn't have instructions. And so that's part of the reason that, you know, there's inconsistency and whatever. Now we're trying to, you know, put more process around it. And the other thing is, you know, please let me know if you're interested in authoring a chapter or a section. We are, we have a committee that'll look in and decide who, you know, which of the authors will select. We have some chapters that everybody wants to offer. For example, data governance. And we have some that, you know, nobody wants to author. So, you know, and then how do we select and how do we be fair? So we've got those coming. Those issues coming up. Okay. Gordon and then those two. And then we'll have to move on. Yes. Yeah. And I'm good with but no. Well, yeah. Yeah. Yeah. Okay. So there's a need to get there are differences in the community in the field. And we can highlight those differences. And here's the other new point. Go to the source of the reference. We did it in some places. Like there's the Kimbell Inman thing that that's. Yeah. I put that in. Don't forget to this box is only going to be as good as the people who write it and the people who respond and comment and comment on it. And right. That is that is in our authoring instructions this time to have footnotes and definitely like I said, we were not given really good set last time. Yeah. And so I'm a firm believer is if you don't tell them what you want, you're not going to get what you know. So tell you what we want in the first place. What's what's easy. Yeah. I think I think we're going to encourage it. Yeah. I mean, I it's it's mentioned proper, proper literary. Yeah. Authoring. Yeah. It's a different group this time. Yeah. And Rod has a. Oh, I don't know who was next. Those two. Yes. You'll be happy to find out. Yes. Yes. Yeah. I am. I am available for sure. We and I have to tell you, Glenn, in addition to the new knowledge area, we're going to call them knowledge areas this time too, by the way, we have a new one called data integration and interoperability. And on top of that, we've got some input into that particular knowledge area. We are also developing a CDMP exam in that area right now. And I'll have to tell you the reason why is because TDW is pushing for it. And they started it through, and then we found out through the ICCP. And we said, I mean, we're, we're saying to ourselves, wait a minute, wait a minute, this is Daimler's domain. We don't jump into it now. We're not going to have an influence on this exam. So you know, TDW I put together an outline for the exam. We looked at it and we said, I don't think so. So it was good, but not good enough. We thought, and so I put together an outline for that exam and we're working on that. So that's going to come up as a beta exam this summer. But the thing is, that's what's happening in that, that particular knowledge area. So. Okay. One more from Robin, then we're going to move on. Sure. Mm-hmm. Maturity levels. Yes. We're, we're going to have. Yes. We're going to be very happy. All right. Let's move on. Yeah. Go ahead. Do you want me to move? Sure. We don't have a clicky. Okay. So. Yeah, we do. This is the, these are the new wheels. Change on the left. We start with data architecture at the top. Of course, data governance is in the center. Oh. The top button. Oh, yay. Wee. Okay. Cool toys. So we've reordered a couple of the things. We've taken management out of the titles because it was kind of redundant. But basically, there's data architecture, data development, when I first looked at it and I'm like, what the heck is that? So it's now data modeling and design. Excellent. Yeah. I love it. It's the one up there and it comes together. What? Data architecture is the, how all of the moving parts fit together. And I think we're going to divide it up into an enterprise level and project level. Yes. Sure. So this, this, the data architecture section will contain stuff like the, the data column of Zachman's framework, things like that. Data modeling will have all of the modeling stuff, how you design, how the data lives within your ecosystem. Data storage is used to be data operations. Now it's really just storage. There's database and file based storage. All that's going to be in there. So some of the big data stuff is going to wind up in here. Data security, that's pretty much, that hasn't changed a whole lot. Data integration and interoperability, all the pieces that used to be in the other sections are now here together. Documents and content. That's the, it was the document and content management includes records, paper based data, things like that. How we manage the stuff that isn't electronically stored or is stored in things that have uncommon structures like audio and video and things like that. Content stuff for web. Reference and master data, that's pretty much the same thing. Data warehousing and business intelligence, metadata and data quality. So this is going to be the new wheel pending all of your commentary over the next few months. The other thing we did was we took the environmental elements and we added the process, the people and the technology to kind of bring a grouping to it that's commonly used everywhere. So now you can say, okay, the people, that's really the organization, the roles and responsibility. Process is the activities and the practices and techniques and then there's the tools and then deliverables under technology because a lot of the things we deliver include tools and technology. So, and then the goals and principles is still in the center as the foundation of all of that. The knowledge areas, yes, yes and we'll get into the detail for each of those things. So that's the new wheels pending all of your commentary and now I expect everybody that gets up at 7.30 in the morning is going to go to the website and comment. Dama.org. Come on. You can go to Dama.org. We will have the draft up if it isn't already in PDF with line numbers so that everything can get commented and make my life hell by commenting the heck out of it. I'm the one that gets to pull all this together and turn it into a nice new draft that then everybody can use and then translate and yadda yadda yadda. And it will. Oh, I agree. Well, we learned a pound. We have lessons learned from the first time and it helps that Dama was around the first time around. I was around because I wrote two chapters and I knew what we were going through from the author's perspective. And I knew what the book went through and she knows what the book went through. So it helps. We learned a lot. Now, did we learn absolutely everything to change? We never do. No, that's why we're putting this framework out for comment to make sure that we didn't miss anything or get something a little skewed. We need your help. We need your help. Yes. Yeah. Yay. Within two months by the end of June, we're going to cut, yeah, we're going to cut off review by the end of June. End of June. And then the rest of my. The framework itself, yes. Yes. Right. Well, like I said, if you're interested in authoring, please let me know or let Susan know. Yeah. Well, she's the one that's carelling all the authors. So yeah. And so hopefully putting more process around it. I'm carelling the text. She carels the people. I don't think so. You can comment. Definitely. Yeah. But to make contributing. I don't think so. I mean, we're going to, one thing that's going to change from last time. And I insisted on, I know some other authors, was the fact that we're going to have attribution. If you wrote chapter nine at the end of the book, that, you know, D&B II, we're going to say so-and-so wrote chapter nine. Or contributed to. Or contributed to. Or whatever. Plus the reviewers. Now, you know, that means you have to go all the way through the whole life cycle. You know, if you're just going to write a paragraph or two, don't necessarily expect your name at the end of the chapter, at the end of the book. So it's got to come in. Yes. Yes. And those are going to be in the chapters. Okay. So let's move on. So the first knowledge area is data governance. So that's the plan of the oversight and control over the data management and use. That's pretty much the same as it always has been. Data architecture. This is as an integral part of the enterprise architecture. All the moving parts, how they fit together. Data modeling and design was data development. So that's the analysis design and modeling. Yes. Everything. Modeling. Physical. Logical. The whole shebang. We will. Okay. At the project level. Okay. All right. So Mike, go under project architecture then. Yeah. We made, yes, data architecture, but then the subsection would probably be the project level. So I expect a comment from you when you see it. We want to stop that. Okay. Yeah. Yeah. All right. Excellent. Like I said, we're trying to divide it up into enterprise and the project level. What you do at each. Right. Right. Okay. Got you. Don't worry. I'm going to tag you too. That's going to be covered under, well, let's just go over the, and then you'll see the chapter structures and then things will become clear. Okay. So there's data storage, data security, data integration, operability. I basically talked to this already. Okay. So then the environmental elements, the same thing. Those haven't changed much. So the first big change that we're going to see in the new DIMBOK is this is the context diagram for a knowledge area. So what we're doing is making the, before it was like a little PowerPoint slide and there was limited real estate and everything had to be teeny weeny text. So we're going to use a different tool to put this together so that we can have more real estate and more organization around what we're doing and it maps more directly back to the environmental elements, these things. So this is what we have and we're going to keep this at a very high level. So we're going to try and not have 45 different things in any one box. And we're going to roll them up to a logical thing that's going to be consistent across the knowledge areas. So we're going to have, we have the definition at the top, which is going to be one or two sentences. That's it. And then there's going to be the goals, which we have in the original context diagrams. But then underneath here, we're putting all of these things into the process. We've got the inputs into the process, the deliverables out of the process. But things that affect the process are the government regulations and industry standards. So we're going to pretty much mention them and then move on because they're all described in detail, but you need to know they exist so that you can go find that greater detail somewhere else. We also have underneath the things that are coming in. So you've got your ins, outs, rules and tools, the typical IDF kind of. And underneath here, we've got the tool sets, the techniques and best practices. We're going to be limited to just a couple of them, really widely known ones. And then the metrics. There's going to be metrics for every single one of these knowledge areas because I know that wasn't consistently done before and everything can be measured in some way. So we need to show you how to do it. I think we want to mention it as important for each of the areas where it does apply. I'm not sure that I personally know where it should go. So I need your help to comment on this to make sure that it gets put in properly. Yes. Right. Right. No, but he wants a linkage. He wants a linkage. Right? I mean, yeah. So I think it would be nice to add to our loss of thought that they, oh, I'll let the next one. Okay. Under here. We've got these roles here to try and map to Racy. Right. So yeah, if you have a suggestion on how to make like a skinny down version of something like this, then yeah, please send it in because that we could, we can potentially do something like that. Yes. Okay. So we need a middle level in between this and that. Okay. Okay. No. Okay. That's, that's cool. The principles are, we're in the text. Oh, the, yeah, the goals and principles were here in the old context diagram. We took the principles out because those were also in the text and there were like two versions of them and it was confusing. So we figured we'd just put it in the text and be done. Okay. So maybe that would be the form of the middle, format of the middle context diagram. Okay. All right. That's really good. Okay. So next is here's the chapter out. Here's the list of chapters and we're going to, some of these chapters are going to be big and we're going to piece them out into sections. So we've got your introduction. There's going to be an entire chapter right in the front, how to use the DINBOC. That's going to contain a bunch of the information about how to sell it, how to make it real for your organization. Yes. Yes. Chapter 15. Your chapter's in there. I mean your section's in there. Whatever. Yeah. Okay. Chapter 15 has a lot of different topics. So we have how to use the DINBOC and then we have the overall process of data management which is the very high level, this is what we're doing. Then each knowledge area gets a chapter and then there's a chapter on data management supporting topics that the original DINBOC has the ethics and section and certification and we've added a bunch more sections to that, right? Because we're putting this out for comment that means that things might change. Yeah. Yes. Okay. So each chapter will have one or more sections intended to focus on a particular topic within the knowledge area before it was kind of everything in there was in there. Now we're going to make a little more organization down there. So for example, chapter 12 is the data warehousing and business intelligence. There's going to be a section specific for data warehousing and a section specific for business intelligence. We all know that people have skills for the back office or skills for the front office and it's not just one big, you can do data warehousing which automatically means you do business intelligence too. That's not right. And each chapter will have a section at the end dedicated to discovering the governance of that knowledge area specific to that knowledge area. So for chapter 12, that's reporting strategies, appropriate use of interpretation of data, architecture, compliance, training and competencies, others. Yeah. I think so. Well, there's a section for data governance and we can definitely discuss the difference and then each particular chapter will have a section on data governance and stewardship and that we see is the glue between all the chapters, the integration and interoperability part is the governance. You wouldn't believe how we've gone round and round and round on that topic. Circles round and round. Yeah. You know, the whole idea was to keep the logo because it's so well known in the industry right now. We can change the order of the slices though if it makes more sense to do that. If it makes more sense. We can move it over to the other side of the wheel. We acknowledge that metadata and data quality and data governance touch all the areas. Yeah. We thought about being big concentric circles and we said, there's a life cycle involved but that's pretty much it. It's a wheel. Yeah. How do you best show all this? And so we decided to stay with the concept of our two symbols. But if you've got a better mousetrap, by all means share it. All right. I'm a reality. Whichever one ends up last, we'll all have things to discuss. All right. Well, yeah. Okay. So we will, please comment and we'll see about maybe rearranging the wheel. We'll revisit it. We have a committee and we'll collaborate on this. So for here. So chapter, this is all the supporting topics for data professionals, professional development which we had before, business data requirement development, how to get good data requirements and deliverable verifications for those requirements. Communicating data management value to the business, that's one of the things that came up earlier. Data management cost control, some data management organizations, how some, what seem to be common patterns for how the org structures for data organizations. And then a section on facilitation for data management professionals to help do those conversations, have those conversations with non-data professionals. Another little, okay. Isn't that part of section two though? That it would be? Well, we'll find out. So anyway, this is where we can go. You can go to get the framework and check it out. And here's all those different kinds of places that you can get to us directly and have conversations. Here's the paths email address, here's my email address that you can use. And now we can actually, if you want to bring up the actual thing. Okay. Just give me a minute. They can get a taste of what it looks like. Yes. There it is. It's in PDF, so I don't know if the remote will work. I don't think so. How do we want to start? Well, look at the long revision list for one. And look when we started in 2010. I started working on this back last November because I was like, okay, if we're, yeah. Because if we're going to do this, we need to figure out how to do it. Yeah. Yeah. And we need to start with the framework. Otherwise we're sunk. In the history, we have the introduction, the goals, a lot of the goals are the same. And then the proposed wheel and the knowledge areas and again, the same kind of diagram you just saw, the knowledge area diagram and the expansion of the second goals, the environmental elements. And then a book knowledge. We have a book outline and we have a chapter outline. And this is where we get the process part. The book outline is what we just went through. And you can see the subsection, so we put down there based on a lot of input that Susan obtained, all of us obtained, and we put out there. And this is what we want you to comment on by line number, please. And so there's quite a bit to look at. Then what we're trying to do is the process for chapter structure and that is that we would have an executive summary and then the business drivers, the processes input. And then we would start going through inputs and outputs and technical drivers and people. So if we had like an intermediate diagram, that might be part of the executive summary bit. Yeah, for each chapter, perhaps. And then this would be just an overall structure of the chapter, how it would look, just conceptually. And then we would have a concordance between the additions. Every box seems to do that. And then we have the next steps, which of course, you know, you're getting your input. So that's kind of it in the nutshell. This is the framework out there, damod.org, and we welcome your input for the next two months. And then we welcome it all. They came out wrong. About what? But after that comes the part, and I'll give you a timetable, we're going to then assign authors and then get them up and rolling in terms of writing. And then ideally, we hope to have a draft of the DMBoc 2 at the conference next year. I don't know what it is, April. Yeah, April. It's April in San Diego. And it'll be launched then, so we can say that we'll launch the commentary period. Right, the commentary period. Again. Again. And then we will have, then we'll incorporate everything. And then maybe by the end of 2013, we'll have a new DMBoc 2, or if not, then 2014 early at the conference. At the conference. So that's roughly our timetable. We've been working at it for quite a while. It becomes a second job to volunteer. And at some point, you have to say, let it go, let people look at it. And that's what happened the last time, and that's why it's not perfect. And will it be perfect this time? Nothing ever is. But it'll be better. But we're going to try to have a little more structure around it this time, and based on what we learned from the last time. That's usually in the organization section. The, the, the, the, the, the data, the data, the data. Right, so in the, in the, in the yellow wheel, there's the organization section. And part of the chapter structure is we're actually going to have that more formal than just a list of questions and answers, like in the first DMBoc. And that's where a discussion of outsourcing for each of the wheel sections would go. Canonical modeling? Yeah, I think we've got that listed under data modeling. Yeah. And design. Yeah, please go and, I mean, in an hour, we can't go over the whole thing, and I think we're out of time anyway, so.