4. PPDM Meta Data
Meta data is all about what is populated, where is it populated, how is it populated and why is it populated. Pretty simple, right?  So where do you start?
Well, creating a metadata repository is probably where to do it.  This metadata repository should be something that captures data (from processes), integrates it into information (at a departmental level) and then be available to all business users to distil it up to knowledge that becomes a corporate asset.
And what better place to start than the PPDM (Professional Petroleum Data Management, not Public Petroleum Data Model) Association with it's 3.8 release.  The PPDM has it's roots in the oil and gas industry,  creating initially a standardized well module and then expanding it out,  both to other content modules such as seismic, land, business  associate as well as creating consistency across modules, so naming  conventions, architectural principles used and re- used.
PPDM's advantage is that it has over 35 upstream oil and gas modules in place and are tied in with the 15 or so support modules.  It's these support modules that are the strength of PPDM.  They are used in each and every one of the business modules.  These provide instant integration.  There is an interesting correlation between the change of the name of PPDM from Data Model to Data Management and the requirements that we (as corporate IT architects) have.  The promise of this website is that we will start with the explanation of how the data model is tied together and can be made to work and then to move on to how to manage the following domains found within your company:
- Business Strategy
- Business Architecture
- Application Architecture
- Data Architecture
- Technical Architecture
Each domain is a section of an enterprise meta- model.  By detailing the make-up of each component, we can see how the PPDM based metadata repository can be populated and more importantly maintained.  Along the way, we will also explore in how today's business world, knowledge is king. But what is knowledge other than information distilled with experience. And what is information other than data that reduces uncertainty around making a decision.  And a decision is an answer to a question. Questions like:
- where (and when) does each data type originate from? for both  processes and applications?
- how often is data updated and is it updated by the right process/application?
- is the right data getting to the right person at the right time?  
- are you able to plan upgrades, implementations or integrations with confidence?
Chances are you can answer some of each question but not any one completely.  Your ability to make an informed decision is compromised; but not with a metadata repository.  At the end of book, project managers to technical leads to developers should be able to understand where to start to implement the PPDM model and the implications of doing so.