Gareth Isaac<\/a>, Director and Principal Consultant, Ortecha<\/a>, a DCAM<\/span> Authorized Partner
Mark McQueen<\/a>, EDM Council, Senior Advisor-DCAM<\/p>\n\n\n\n
Overview<\/h1>\n\n\n\nProcess Design Framework<\/h2>\n\n\n\n
The EDM Council industry standard<\/span> process<\/span> design utilizes a 6-level model<\/span> as defined below. Practically, an industry standard<\/span> can only design to Level 3. Beyond Level 3 a standard<\/span> becomes organization and role specific.<\/p>\n\n\n\n Data Management Practitioners (Reference: Data Management Functional Construct<\/a>)<\/p>\n\n\n\n The driver for the design of the Level 2 Data Domain<\/span> Management process<\/span> was the development of a best practice tied to the identification of Critical Data Elements (CDEs). The process<\/span> of prioritizing data based on criticality was determined to be contained within the Data Domain<\/span> Management process<\/span>. (See: Prioritizing Data Based on Criticality: Critical Data Elements (CDEs) in Context<\/a>)<\/p>\n\n\n\n The following process<\/span> design presents a complete Level 2 Data Domain<\/span> Management process<\/span>. Only four of the Level 3 processes were developed as they were the processes required to represent the activities of the process<\/span> to prioritize data.<\/p>\n\n\n\n The Level 2 process<\/span> is presented at the Component level with alignment back to DCAM<\/span> Framework Capabilities and Sub-capabilities.<\/p>\n\n\n\n The table below represents the DCAM<\/span> Components that are required to execute the Data Domain<\/span> Management process<\/span>.<\/p>\n\n\n\n The Data Domain<\/span> Management Process<\/span> is where the DCAM<\/span> Framework Components of Data Governance, Data Architecture<\/span>, and Data Quality<\/span> are brought together to execute on a specific set of data in the Data Control Environment.<\/p>\n\n\n\n
\n\n\n\nStakeholders<\/h2>\n\n\n\n
Scope<\/h2>\n\n\n\n
DCAM Component Alignment<\/h2>\n\n\n\n
Component<\/strong><\/td> Capability Requirement<\/strong><\/td><\/tr><\/thead> 7.0 Data Control Environment<\/td> ● The process<\/span> of data domain<\/span> management is in the Data Control Environment Component.
● The process<\/span> of prioritizing data based on criticality resides within the data domain<\/span> management process<\/span>.<\/td><\/tr>3.0 Business & Data Architecture<\/span><\/td> ● The process<\/span> of prioritizing data based on criticality is dependent on defining requirements for data, identifying data, defining data, and profiling<\/span> data.<\/td><\/tr> 5.0 Data Quality<\/span> Management<\/td> ● The process<\/span> of prioritizing data based on criticality does not require the Data Quality<\/span> Management Component. Data Quality<\/span> Management is part of the overall Data Domain<\/span> Management and will be integral to the process<\/span> of managing the implications of criticality.<\/td><\/tr> 6.0 Data Governance<\/td> ● The process<\/span> of prioritizing data based on criticality leverages the Data Governance Component for approving the metadata<\/span> and the criticality designation.<\/td><\/tr><\/tbody><\/table>\n\n\n\n Level 2 1.0: Data Domain Management Process<\/h1>\n\n\n\n
Summary<\/h4>\n\n\n\n
Process Flow<\/h4>\n\n\n\n
![\"\"](\"https:\/\/i1.wp.com\/www.dcamportal.org\/wp-content\/uploads\/2020\/02\/L2-1.0-Data-Domain-Management-Process-scaled.jpg?fit=699%2C333\")
<\/a>