Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By : Bill Aronson
Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By: Bill Aronson

Overview of this book

Open Text ProVision® (formerly known as Metastorm ProVision®) is an Enterprise Architecture (EA) solution allowing for effective planning and decision making throughout the enterprise. It enables an organization to have a central repository of information about the business, reducing organizational risks and better optimizing business resources. Implemented well, it enables better and more actionable decisions exactly when you need them.This book combines theory and practice to provide a step- by- step guide to building a successful customer- centric model of your business. The approach is simple and down to earth, and along the way, with various real-world examples, you will learn how to make a business case, use a framework, and adopt a methodology with Open Text ProVision®. This book draws on the experience of ProVision® experts around the world. By combining theory with practice from the field you can avoid common mistakes and develop a successful customer centric strategy for implementing ProVision®. Each chapter builds on the previous one to give you the confidence to implement a central repository, dealing with both the technical and human issues that you might face.
Table of Contents (16 chapters)
Open Text Metastorm ProVision® 6.2 Strategy Implementation
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
References
Index

Modeling a governance structure with ProVision®


We said earlier that 'governance is a set of policies, procedures, and processes that ensures that work is done effectively'. Let's look at how we can use ProVision® to model these.

Policies and procedures

All organizations have policies and procedures. In some organizations they are written down. In others, they are not documented because the organization is too small to warrant them. Often, nobody has the time to create and maintain procedure manuals. If you don't know something, just ask someone who does.

As an organization grows, the argument for documenting policies and procedures gets stronger. Again, we must look at the context. Why document? We see two contexts and they lead to very different conclusions.

The first context is compliance. The purpose of the documentation is to demonstrate that you have effective and consistent policies and procedures. The more documentation, the more compliant you are. If there is a failure, then you can...