Data are an organization's sole, non-depletable, non-degrading, durable asset. Engineered right, data's value increases over time because the added dimensions of time, geography, and precision. To achieve data's full organizational value, there must be dedicated individual to leverage data as assets - a Chief Data Officer or CDO who's three job pillars are: Dedication solely to leveraging data assets, Unconstrained by an IT project mindset, andReports directly to the business

Once these three pillars are set into place, organizations can leverage their data assets. Data possesses properties worthy of additional investment. Many existing CDOs are fatally crippled, however, because they lack one or more of these three pillars. Often organizations have some or all pillars already in place but are not operating in a coordinated manner.

The overall objective of this book is to present these pillars in an understandable way, why each is necessary (but insufficient), and what do to about it.
Uncovers that almost all organizations need sophisticated, comprehensive data management education and strategies.Delivery of organization-wide data success requires a highly focused, full time Chief Data Officer.Engineers organization-wide data advantage which enables success in the marketplace

Concepts and terms are critical to a clear understanding of any complex subject. Data management, database, enterprise database, and business information systems are such subjects and they use a dizzying quantity of terms and concepts. Some that are the same mean different things. Some that are different mean the same thing. This book, Concepts and Terms, comprehensively provides, defines, and illustrates uses of over 900 terms and concepts that critical to data management, database, enterprise database, ANSI Database Standards, DBMS Standards including SQL, and business information systems. This book also serves as the one-book concepts and terms source for all the Whitemarsh Information Systems Corporation data management product line.

The Data Semantics Management book is divided into two volumes. Volume 2, this volume, addresses Deployment. Volume 1 addresses Rationale, Requirements, and Architecture. The approach embraced by these two volumes is founded on the idea of top-down and centralized architecture, engineering, policies, and procedures, but bottom-up, distributed accomplishment. If attempted only top-down, the outcomes will mirror familiar centralized czar-like failures of the past. If accomplished only bottom-up, the outcomes will be the vast forests of semantic stove pipes. Volume 2 presents these key topics: Data element architecture and engineering via the ISO Standard 11179; development of data models of concepts to be used as templates for manufacturing database data models; the development of "logical" data models from concept data model templates; the development of "physical" data models from one or more "logical" data models; the engineering of view data models including generation of XML schemas and Service Oriented Architecture (SOA); Database object class models that includes data structure, process, and state; work plans for accomplishing data semantics management within a project, organization, function, and enterprise; and an overall two-volume summary including a chapter by chapter explanation of how the two interoperability and shared data error classes have been eliminated or severely reduced. Each chapter concludes with an extensive set of questions and exercises.

The Data Semantics Management book is divided into two volumes. Volume 1, this volume, addresses Rationale, Requirements, and Architecture. Volume 2 addresses Deployment. This volume justifies why accomplishing data semantics management is so critical to the overall success of data interoperability and shared data. The approach embraced by these two volumes is founded on the idea of top-down and centralized architecture, engineering, policies, and procedures, but bottom-up, distributed accomplishment. If attempted only top-down, the outcomes will mirror familiar centralized czar-like failures of the past. If accomplished only bottom-up, the outcomes will be the vast forests of semantic stove pipes. Volume 1 presents these key topics: Rationale, Data Semantics Components, Failures and Lessons Learned, Engineering, Successful Name Construction, Semantic Hierarchies including taxonomies and ontologies, Value Domain Managememnt, and the Business Fact Specification cases including Business Rule engineering. The book identifies and describes the two error classes that prevent data interoperability and sharing. Each chapter addresses how these two classes are addressed. Each chapter concludes with an extensive set of questions and exercises.

The last dogma defined by the Church is the Assumption of the Blessed Virgin Mary into heavenly glory. This dogma is the gateway to answer one of the greatest problems that has ever faced the human race. What is the meaning of life? Is death the end of everything? Mary's Assumption tells us that eternal life with God is the final evolution of every man and woman who dies in the friendship of God. At the end of time all will be taken up and transformed, the body and the soul, the corporeal and the spiritual. For all that God created is sacred and loved. Where Mary is, all the elect will be. Whoever contemplates this mystery learns much about God, Christ, Mary, the Church and oneself. The Virgin Mary is one who walked in the darkness of faith and never despaired, one who obeyed and never deserted, one who loved and was never unfaithful. She is an example of the perfect disciple. Mary was Jesus' first and the most perfect disciple of Christ. The Virgin Mary, taken up into heaven after her earthly life, remains for us the symbol of all that we should be, and of all that we will be, if only we are faithful to Christ. She is the woman in the life of Christ and the woman in the life of all who follow him. On earth Mary was the mother of Jesus and his wholehearted companion, his comfort and joy. Now in heaven close to Jesus, she watches over us with a mother's care and intercedes for us. She is our life, our sweetness and our hope. She is our shining example. Where she is, we shall be. God knows we need the woman clothed in glory. The purpose of this book is to contemplate the Virgin Mary in her heavenly glory. The book's reflections go beyond the mystery of the Assumption in itself to contemplate the Mother of God in glory in relation to Christ and the Church. For Mary in glory is close to Christ and the people of God. We hope to penetrate more deeply this twofold mystery. To facilitate this task, the book is divided the study into two parts: The Assumption in the Mystery of Christ, and the Assumption in the Mystery of the Church. The first part follows the model of Chapter eight of the Constitution on the Church of the Second Vatican Council. There as here, Mary is considered first in the mystery of Christ and then in the mystery of the Church. The first part is actually a commentary on the Apostolic Constitution Munificentissimus Deus that defined the dogma of the Assumption. It is here we perceive that the Assumption is not an isolated privilege granted to Mary, but one that is intimately joined with the person and mission of Christ. Her triumphal entrance into glory is part of Christ's victory over sin and death. The second part goes beyond the Constitution and ponders the Immaculate Virgin in heaven in relation to the mystery of the Church. The first consideration is Mary in heaven as the model, image and beginning of the pilgrim Church. This is followed by her relation to the suffering and heavenly Church. The final chapter ponders the texts of the liturgical feast of the Assumption. It is in the liturgy of the feast that we experience God's love for the human family; Mary's inseparable union with Christ her Son and Savior, and the joy that we are called to experience once our pilgrimage of faith is over. For, taken up to heaven we join Mary in the communion of saints in union with Christ our Lord.

It is common for information systems development projects to be late, exceed budget projections, and contain significantly fewer features than proposed. This book provides a strategy whereby these problems can be resolved. This strategy is based on techniques and methods that have been proven over 30+ years. This book is based on data-driven requirements strategy, and the use of prototyping to evolve the business information system's design until all the fundamental requirements have surfaced, been tested, and been agreed to by users. Then and only then can implementation proceed. The production system can directly proceed from the prototype. All the techniques in the book are based on a real metadata repository and a business information system generator. Screen shots from both are included.

The Data Interoperability Community of Interest Handbook provides the: * Rationale for Shared Data Environments across the Enterprise * Blueprint for Collaborative Data Sharing * Why Communities of Interest are Ideal Organizational Structures * How Communities of Interest are Best Engineered * Step-by-Step Strategies to Build Common Data Architectures * Methodology & Plan to Create Focused Organizations * Strategies for Meetings, Decision Making, and Voting * And Much, Much More!

The Data Interoperability Community of Interest Handbook provides the: * Rationale for Shared Data Environments across the Enterprise * The Unbeatable Business Case * Blueprint for Collaborative Data Sharing * Why Communities of Interest are Ideal Organizational Structures * How Communities of Interest are Best Engineered * Step-by-Step Strategies to Build Common Data Architectures * Methodology & Plan to Create Focused Organizations * Strategies for Meetings, Decision Making, and Voting * And Much, Much More!

Enterprises grow, stagnate, or even die by the quality of their archtiectures. May businesses have inappropriate or even wrong information systems technology because these technologies are not properly engineered. The first step is to understand that many businesses are built on the knowledge worker. A framework for the knowledge worker is important. Within this framework exists five critical architectures: the Enterprise's Archiecture, the Database Objects Archtiecture, the Data Architecture, the Resource Life Cycle Architecture, and the Information Systems Planning Architecture. These five architectures overlap and are interlinked. If the work products created for these architectures stand alone, much time and resources will have been wasted. A Metadata management systems is critical to interrelate these architectures thus making their work products non redundant. Properly engineered, these architectures enable the enterprise to thrive and to be able to change in the face of business adversity and changing technologies. This books sets out the five architectures, shows the interrelationships among all the work products and describes the metadata repository system needed to be successful.