PPDM DATA MANAGEMENT

From PPDM Wiki
Jump to: navigation, search

Contents

Introduction

The management of data, and having the tools to manage and execute the various Business Processes in this Business Module offers great opportunity and efficiencies to stakeholders in data management. This module, previously known as Meta Model, has expanded in functionality from release PPDm3.7 to include many other aspects of data management for our clients.

Data Management Module Overview

Purpose

The purpose of this Business Module is to offer a data structure that will facilitate a number of Business Processes in the area of Data Management.

Description

Key Business Sub-Modules

PPDM – System Data Storage Meta Data

Meta data; data about the data, is often difficult to understand and work with. The purpose of the next four sub- modules is to present meta data in a data storage system of the three types; database, XML and EDI, in a format that makes usage of this information much easier for the business of data management.

The benefits of meta data in a form that can be easily used is enormous! It can lead to better understanding of a data storage system implementation through a host of reports that can be created. It can lead to automation, either in full or in part, of documentation for an implementation of a data storage system.

The PPDM data model is one such implementation; captured in an sql 92 compliant database. The meta data about the PPDM data model has been extracted from the model database into this module for easy business use. Staff at PPDM Association make use of this module extensively to create user documentation for the PPDM data model.

A number if items in this module can be defined in a group of like objects, or within a group of other objects in which the client wants to create the association to satisfy a business need. See Sub Module – Groups for details.


This includes tables in the PPDM 3.8 Roadmaps, section Data Management, titles PPDM Schema, PPDM Tables, PPDM Columns, PPDM Constraints.

See Tables for details.

PPDM – Rules

Documentation in progress....

See Tables for details.

PPDM – Code

Documentation in progress....

See Tables for details.

PPDM – Audit History

Audit of changes in values of items of data within a data storage system by applications has always been a fundamental part of data capture. However the information about an item change has been limited to a general understanding of when and who has made the change through the use of standard audit columns.

Rarely is information captured about the details of “why” the change was made; who authorized it, who approved the change, who verified the change, what was the “before” value, how is the quality of data been controlled, and so on.

This module offers a generalized solution to capture the “why” of data change at the data store level (table) and the attribute level (column). The client can define the data stores (tables) and the data attributes (columns) they feel require this level of audit information capture. The selection candidates are found in the “System Data Storage Meta Data”. (would like to Scroll to this topic with in the page)

For example, one may have a governing body provide values for attributes that your organization must use in a calculation. They change this number and your organization is obliged to use this new value in your calculations from an effective point in time. Typically this data could be kept in a data store. The client has deemed that it is important to know the details of the data value change. The client would define this attribute as one in which the details of the change are required in this module. Detailed audit information can now be captured for a change in this attribute’s value.

See Tables for details.

PPDM – Metric

This sub-module allows a data management team to define a business function in order that statistics about the execution of the business function can be collected. Various reports can be created to present the statistics for analysis purposes. Having this analysis information at hand can lead to action items that improve the performance of execution of a business function.

For example, a metric may be set up for loading of wells into a database. Once this data capture commences, a number of things can be determined by the data management team. For example, knowing the rate of progress can allow for accurate estimates of work effort and costs to complete the business function.

These statistics may lead to the definition of performance levels to be expected on a business function. If the task is one of a repeatable nature, future work effort and cost may be more accurately estimated using the expected performance level determined from the statistics.

Performance measurement of individuals could be collected and compared against the expected performance level. Analysis of individual performance levels may lead to identification of training opportunities for staff or lead to staff allocation changes to increase performance level in the execution of the business function.

Another example might be a data quality initiative. One may want to collect statistics on business rule violations occurring on a column being populated in a table. A metric can be set up so statistics can be collected and analysed. Analysis of the data may result in action items being taken to reduce these violations.

In many metrics, observations of the statistics after action has been taken may reveal the success level of the actions taken.

Information regarding the system, a particular metric, components of a metric, an identification of columns and tables involved in the metric, and metric values are captured in this module.

See Tables for details.

PPDM – System Mapping

In the management of data an important function is the movement of data from one data database, extensible mark-up language (XML) schema, or electronic data interchange (EDI) schema to another. This can be within, or across these types of data storage systems.

Often data is sourced from external data storage systems and needs to be moved into corporate or master data storage systems. Movement of data within a company is also required to satisfy the various business functions making use of a data storage system.

This module allows for a formal definition of a mapping of data from one data storage system to another. Once this formal mapping of data between data storage systems is defined, automated procedures can be written to read data from one data storage system; apply the mapping rules, and load data in the proper place in another data storage system.

Information regarding the system, a particular mapping, an identification of columns and tables involved in the mapping, and the rules and transformations of mapping is captured in this module.

See Tables for details.

PPDM – Groups

There can be a need to define a set of entities (objects) that can be grouped together to satisfy a business function. The client may determine many business functions in this area of data management can be satisfied by creating groups. This module facilitates the definition of groups to meet a business function requirement within data management.

For example, one may want to know all the procedures that make use of a table. A group would be created, the table would be identified as an object in the group, as would all the procedures that access the table. This can be useful in determining what procedure would need to be re-compiled as a result of a change of any sort in a table.

Another example, one may want to know all columns in tables that are used in a specific procedure. A group will be created, the procedure identified as an object, as would all the columns involved in the procedure.

Other aspects of database meta data may also be defined in groups for a variety of business functions to be satisfied.


The client has the ability to add to the set of objects to be involved in a grouping through the use of the table extension function. The PPDM user group will, from time to time determine what objects from the clients extensions will be promoted for general use by the PPDM client base.

See Tables for details.

Sub Module – Vertical Tables

Documentation in progress...

Retrieved from "http://www.ppdm.org/wiki/index.php/PPDM_DATA_MANAGEMENT"
Personal tools