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

Case study—the consultant's view


iOctane is a business process transformation company. They are a leading company in using ProVision® in Australia and New Zealand. I caught up with Gordon Lescinsky who has been using ProVision® for many years.

BA: What kind of work are you doing?

GL: We have been working with large companies by Australian standards. They have been automated for some time. If they work on one process, they work on a hundred. We have been working on projects where every single process has been affected because some system that underlies everything has been changed. It might have been put in for the first time, but most likely it has been changed. The context is 'big process project' where many processes are affected, not necessarily improved, but touched in some way.

BA: There are two extremes of context deploying ProVision®. At one end are the people responsible for creating a whole enterprise repository. At the other end are the people responsible for one project or program...