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

Project #5—building Organization models


Project #5 develops an Organization model of the business units and positions that participate in the critical processes. Other critical element models can be added as appropriate.

We have already seen that we can make models of actors and their business units using an Organization model. Actors also show up as swim lanes in Workflow models. The Business Interaction model shows us the high-level relationships between markets and organizations, either to deliver a product or service, or, one level down, looking at a specific process. Fairly quickly the same actors will show up in a number of different models.

How can we understand all of these relationships? If you want to plot an actor against one specific object then an Association Grid is a good option. Alternatively, a Navigation model is a better alternative if you want to trace indirect relationships that involve multiple object types.

In the following example we use the Association Grid wizard...