December 20, 2009

..ISP and BP..

Today, enterprise database is deployed on distributed, heterogeneous hardware and systems software environments.2 The hardware platforms are both multiple-vendor and multi-tiered, with different architectures. In short, most businesses have embraced some form of downsizing, decentralization, and distributed processing. Critical to the enterprise database environment is the capture of the business model and the implementation of the enterprise's memory: its data architectures. Once the data architectures are
implemented in a sophisticated, generalized manner, software tools can be quickly and effectively deployed to create the necessary business systems to collect, update, and report critical business data.

The business systems can be implemented through a network of databases across different computing platforms. To make database a success, each must be carefully defined, deployed along with high-quality processing systems, and effectively utilized through high-level natural languages. To have database success is to be organized. And with an organized enterprise, the past can be researched, the present can be mastered, and plans for the future can be set into place.

Before going deeply into the relationship between the business plan and Information System(IS), let us first discuss the description of each parties.

Business Plan

A business plan is a formal statement of a set of business goals, the reasons why they are believed attainable, and the plan for reaching those goals. It may also contain background information about the organization or team attempting to reach those goals.

The business goals may be defined for for-profit or for non-profit organizations. For-profit business plans typically focus on financial goals, such as profit or creation of wealth. Non-profit and government agency business plans tend to focus on organizational mission which is the basis for their governmental status or their non-profit, tax-exempt status, respectively—although non-profits may also focus on optimizing revenue. In non-profit organizations, creative tensions may develop in the effort to balance mission with "margin" (or revenue). Business plans may also target changes in perception and branding by the customer, client, tax-payer, or larger community. A business plan having changes in perception and branding as its primary goals is called a marketing plan.

Business plans may be internally or externally focused. Externally focused plans target goals that are important to external stakeholders, particularly financial stakeholders. They typically have detailed information about the organization or team attempting to reach the goals. With for-profit entities, external stakeholders include investors and customers. External stake-holders of non-profits include donors and the clients of the non-profit's services. For government agencies, external stakeholders include tax-payers, higher-level government agencies, and international lending bodies such as the IMF, the World Bank, various economic agencies of the UN, and development banks.

Internally focused business plans target intermediate goals required to reach the external goals. They may cover the development of a new product, a new service, a new IT system, a restructuring of finance, the refurbishing of a factory or a restructuring of the organization. An internal business plan is often developed in conjunction with a balanced scorecard or a list of critical success factors. This allows success of the plan to be measured using non-financial measures. Business plans that identify and target internal goals, but provide only general guidance on how they will be met are called strategic plans.

Operational plans describe the goals of an internal organization, working group or department. Project plans, sometimes known as project frameworks, describe the goals of a particular project. They may also address the project's place within the organization's larger strategic goals.

Business plans are decision-making tools. There is no fixed content for a business plan. Rather the content and format of the business plan is determined by the goals and audience. A business plan should contain whatever information is needed to decide whether or not to pursue a goal.

For example, a business plan for a non-profit might discuss the fit between the business plan and the organization’s mission. Banks are quite concerned about defaults, so a business plan for a bank loan will build a convincing case for the organization’s ability to repay the loan. Venture capitalists are primarily concerned about initial investment, feasibility, and exit valuation. A business plan for a project requiring equity financing will need to explain why current resources, upcoming growth opportunities, and sustainable competitive advantage will lead to a high exit valuation.

The format of a business plan depends on its presentation context. It is not uncommon for businesses, especially start-ups to have three or four formats for the same business plan:

* an "elevator pitch" - a three minute summary of the business plan's executive summary. This is often used as a teaser to awaken the interest of potential funders, customers, or strategic partners.

* an oral presentation - a hopefully entertaining slide show and oral narrative that is meant to trigger discussion and interest potential investors in reading the written presentation. The content of the presentation is usually limited to the executive summary and a few key graphs showing financial trends and key decision making benchmarks. If a new product is being proposed and time permits, a demonstration of the product may also be included.

* a written presentation for external stakeholders - a detailed, well written, and pleasingly formatted plan targeted at external stakeholders.

* an internal operational plan - a detailed plan describing planning details that are needed by management but may not be of interest to external stakeholders. Such plans have a somewhat higher degree of candor and informality than the version targeted at external stakeholders.

Typical structure for a business plan for a start up venture[8]

* cover page and table of contents
* executive summary
* business description
* business environment analysis
* industry background
* competitive analysis
* market analysis
* marketing plan
* operations plan
* management summary
* financial plan
* attachments and milestones

(http://en.wikipedia.org/wiki/Business_plan)

Information System Plan

Characteristics of a Quality ISP

A quality ISP must exhibit five distinct characteristics before it is useful. These five are presented in the table that follows.

  • Timely
The ISP must be timely. An ISP that is created long after it is needed is useless. In almost all cases, it makes no sense to take longer to plan work than to perform the work planned.

  • Useable
The ISP must be useable. It must be so for all the projects as well as for each project. The ISP should exist in sections that once adopted can be parceled out to project managers and immediately started.
Maintainable The ISP must be maintainable. New business opportunities, new computers, business mergers, etc. all affect the ISP. The ISP must support quick changes to the estimates, technologies employed, and possibly even to the fundamental project sequences. Once these changes are accomplished, the new ISP should be just a few computer program executions away.

  • Quality
While the ISP must be a quality product, no ISP is ever perfect on the first try. As the ISP is executed, the metrics employed to derive the individual project estimates become refined as a consequence of new hardware technologies, code generators, techniques, or faster working staff. As these changes occur, their effects should be installable into the data that supports ISP computation. In short, the ISP is a living document. It should be updated with every technology event, and certainly no less often than quarterly.

  • Reproducible
The ISP must be reproducible. That is, when its development activities are performed by any other staff, the ISP produced should essentially be the same. The ISP should not significantly vary by staff assigned.


The ISP Steps

The information systems plan project determines the sequence for implementing specific information systems. The goal of the strategy is to deliver the most valuable business information at the earliest time possible in the most cost-effective manner.

The end product of the information systems project is an information systems plan (ISP). Once deployed, the information systems department can implement the plan with confidence that they are doing the correct information systems project at the right time and in the right sequence. The focus of the ISP is not one information system but the entire suite of information systems for the enterprise. Once developed, each identified information system is seen in context with all other information systems within the enterprise.

The following are the steps in Information System Planning:

  • Create the mission model
The mission model, generally shorter than 30 pages presents end-result characterizations of the essential raison d=etre of the enterprise. Missions are strategic, long range, and a-political because they are stripped of the who and the how.

  • Develop a high-level data model
The high-level data model is an Entity Relationship diagram created to meet the data needs of the mission descriptions. No attributes or keys are created.

  • Create the resource life cycles (RLC) and their nodes
Resources are drawn from both the mission descriptions and the high level data model. Resources and their life cycles are the names, descriptions and life cycles of the critical assets of the enterprise, which, when exercised achieve one or more aspect of the missions.

  • Allocate precedence vectors among RLC nodes
Tied together into a enablement network, the resulting resource life cycle network forms a framework of enterprise=s assets that represent an order and set of inter-resource relationships.

  • Allocate existing information systems and databases to the RLC nodes
The resource life cycle network presents a Alattice-work onto which the Aas is@ business information systems and databases can be Aattached. See for example, the meta model in Figure 2. The Ato-be databases and information systems are similarly attached. ADifference projects between the Aas-is and the Ato-be are then formulated. Achievement of all the difference projects is the achievement of the Information Systems Plan.

  • Allocate standard work break down structures (WBS) to each RLC node Detailed planning of the Adifference projects entails allocating the appropriate canned work breakdown structures and metrics. Employing WBS and metrics from a comprehensive methodology supports project management standardization, repeatability, and self-learning.

  • Load resources into each WBS node
Once the resources are determined, these are loaded into the project management meta entities of the meta data repository, that is, metrics, project, work plan and deliverables. The meta entities are those inferred by
8.Schedule the RLC nodes through a project management package facilities. The entire suite of projects is then scheduled on an enterprise-wide basis. The PERT chart used by project management is the Resource Life Cycle enablement network.

  • Produce and review of the ISP
The scheduled result is predicable: Too long, too costly, and too ambitious. At that point, the real work starts: paring down the suite of projects to a realistic set within time and budget. Because of the meta data environment , the integrated project management meta data and because all projects are configured against fundamental business-rationale based designs, the results of the inevitable trade-offs can be set against business basics. Although the process is painful, the results can be justified and rationalized.

  • Execute and adjust the ISP through time.
As the ISP is set into execution, technology changes occur that affect resource loadings. In this case, only steps 6-9 need to be repeated. As work progresses, the underlying meta data built or used in steps 1-5 will also change. Because a quality ISP is Aautomated@ the recasting of the ISP should only take a week or less.
(http://www.tdan.com/view-articles/5262)

As a summary, any technique employed to achieve an ISP must be accomplishable with less than 3% of the IT budget. Additionally, it must be timely, useable, maintainable, able to be iterated into a quality product, and reproducible. IT organizations, once they have completed their initial set of databases and business information systems will find themselves transformed from a project to a release environment.

The continuous flow environment then becomes the only viable alternative for moving the enterprise forward. It is precisely because of the release environment that enterprise-wide information systems plans that can be created, evolved, and maintained are essential.

Now, the relationship between IS plan and business plan is that IS planning is dependent on the business plan of a firm or company, in which IS plan needs to function as how the firm needs it and how will it able to increase the capacity of the firm. The business plan can also become a guide for the project team in order for them to make an Information System that would be very much close to fit the firm perfectly.






No comments:

Post a Comment