Portal Business Drivers and High Level Requirements

 

Description

 

The output is a list of motivating reasons for the implementation of an Enterprise Portal (e.g. eliminate paper-based processes, rekeying of data by utilizing end-to-end process automation, reducing administrative costs and cycle times, introduce automated workflow and approval processes to reduce cycle times…).

The output should also derive the high level functional requirements from the identified business drivers.

The following list represents some examples:

 

·         Requirement for a customized system user interface with broad user acceptance and low training needs (including simplified and secure logon procedures)

·         Need for reduced information retrieval time

·         Need for reduced administration/process costs (e.g. by providing employee self services)

·         Requirement for improved and faster business decisions (e.g. by providing a better information basis)

·         Requirement for reduced IT service cost (e.g. by changeover to portal based “thin clients” or by replacing existing KM solutions)

·         Requirement for reduced information distribution costs (e.g. by avoiding printed material)

·         Requirement for a consolidated existing IT landscape

·         Requirement for enhanced (e.g. webbased, mobile…) system access

·         Requirement for integration of external business partners

·         Requirement for knowledge management and collaboration functions

 

Process

 

Refer to the Reference tab below for information on method of output creation.

 

Additional Information

 

It is critical to identify and define the business drivers at the beginning of the project. Business drivers are used to establish some of the standards by which the success of the implementation project is measured.

Some of the drivers could also be used as the basis of the projects value proposition.