Project Charter

Project Name: Redefining Silviculture Information Requirements

Project Sponsor: Ralph Archibald, Director, Forest Practices Branch

Project Manager: Ian Miller, R.P.F., Senior Harvest Practices Forester, FPB

May 31, 1999

 


Contents

  1. Vision and Mission

  2. Rationale

  3. Project Objectives

  4. Scope
    4.1    In-scope
    4.2 Out of scope

  5. Success Criteria

  6. Priority

  7. Key Stakeholders

  8. Project Organization
    8.1   Project Sponsor
    8.2   Steering Committee
    8.3 Project Manager
    8.4 Project Team
    8.5 Reporting relationships

  9. Linkages to other groups or initiatives
  10. Project Plan
    10.1 Project Approach
    10.2 Deliverables/Milestones
    10.3 Final Report
  11. Project Budget
  12. Potential issues, constraints and critical success factors
  13. Approvals

1. Vision and Mission

The project is one part of the vision of ensuring the ministry’s silviculture data adequately meets current and expected forest management needs.

The mission of the project is to review, define and document the Ministry of Forests’ and forest industry’s current and expected business requirements for corporate silviculture attribute data, to recommend a realistic strategy for the migration of that data to the integrated corporate spatial and attribute database (INCOSADA) format, and to recommend the activities required to understand and address other silviculture information needs, by October 1, 1999.

Back to the top

2. Rationale

The Ministry of Forests is currently facing a number of challenges with respect to the management of silviculture data:

Back to the top

3. Project Objectives

The general project objective is to examine current silviculture attribute data to make strategic recommendations on the priorities for data migration and management of existing data, in light of business requirements, infrastructure, and staff and budget availability. The detailed objectives are:

Back to the top

4. Scope

This study will examine the current business requirements for silviculture attribute data, and determine which data elements are most critical for achieving the ministry’s forest resource stewardship mandate. This aspect of the study will be largely independent of the information technology used or planned to support the ministry’s silviculture business processes. The output will answer the question "what are the business needs?".

However, the other major focus of the study is on determining if, when, and how to migrate the current silviculture attribute data into the INCOSADA database format. This aspect must therefore account for the ministry’s information technology infrastructure plans. The output will answer the question "how do we start to meet the current business needs?"

Finally, some consideration will be given to recommending future management of software applications and business processes to support silvicultural aspects of forest management. This aspect of the study is more reliant on understanding our near-future business needs and technology capabilities. The output will answer the question "what are the next steps?".

Back to the top

4.1 In-scope:

Back to the top

4.2 Out of scope:

5. Success Criteria

The project will be a success when:

Back to the top

6. Priority

This project is seen as a high priority by Forest Practices Branch (the data custodian of silviculture data), by Information Management Group (IMG) and the partners in the INCOSADA project, and by Operations Division management. The INCOSADA project timeline requires data conversion in the near future; FPB must prioritize and plan for data conversion in full consideration of the business needs and the time, staff, funding and knowledge resources available.

Back to the top

7. Key Stakeholders

Key stakeholders include:

Back to the top

8. Project Organization

8.1 Project Sponsor

The sponsor of this project is Ralph Archibald, Director of Forest Practices Branch. As custodian of silviculture data, the director is responsible for determining, on behalf of the entire ministry, what information and/or applications are important for the ministry to use in a particular subject area. The data custodian is also responsible for validating that the ministry’s business interests are served by the investment in that information and/or application(s). John Ellis, Chief Information Officer, IMG as application custodian of MLSIS/ISIS, and Dave Gilbert, Director, Resources Inventory Branch, as data steward, have also indicated strong support for this initiative.

Back to the top

8.2 Steering Committee

A small inter-divisional group will act as the steering committee for this project. The steering committee is not expected to meet regularly; rather they will provide overall strategic direction to the project team, will assist with issue resolution, and may provide additional resources, where required. Specific members include:

Ralph Archibald, FPB, Chair

Jon Vivian, RIB

David Ford, IMG

One or two senior managers from OpsDiv (suggest RSM-IRM, DM, etc.)

Ian Miller, FPB (Chair, Project Team)

Back to the top

8.3 Project Manager

The project manager for this project is Ian Miller, R.P.F., Senior Harvest Practices Forester with Forest Practices Branch. The project manager will be assigned to this project on a 90% basis, to allow a few other priority projects to proceed concurrently.

 

8.4 Project Team

To achieve the objective in the time allotted, the core project team will be limited to about eight members. Team members are expected to regularly participate in team meetings, conference calls etc., and are expected to devote a substantial amount of time to the project until its completion. Various collaborators are also expected to work with the team to help complete certain tasks or activities, and are expected to be available for shorter periods. Input will be sought from a wide range of internal and external client groups.

The project team includes:

Collaborators include:

Back to the top

8.5 Reporting relationships

Back to the top

 

9. Linkages to other groups or initiatives

Back to the top

 

10. Project Plan

A detailed project plan will be developed once the project team has formed and determined the detailed work flow and other aspects of the project plan.. The overall project management functions, and the major project deliverables and/or milestones, are listed below:

10.1 Project Approach

Back to the top

 

10.2 Deliverables/Milestones

Draft project charter May 12, 1999
Present project overview to SC May 17, 1999
Outline project plan June 18, 1999
Complete project team June 30, 1999
Project charter sign-off by sponsor June 30, 1999
Document current situation July 9, 1999
Complete stakeholder survey September 3, 1999
Final report and recommendations October 1, 1999

Back to the top

10.3 Final Report

The report is expected to document:

Back to the top

 

11. Project Budget

There is no budget allocated to this project; all work will be done by in-house staff using existing resources. Staff travel will be the responsibility of the respective team member’s business unit.

 

12. Potential issues, constraints and critical success factors

Back to the top

 

13. Approvals

 

original signed June 28, 1999

Ralph Archibald

Project Sponsor (on behalf of the project steering committee)

 

original signed June 28, 1999

Ian Miller

Project Manager (on behalf of the project team)


For more information on this project, please contact Ian Miller, Forest Practices Branch, by phone at 250-387-8398 or by email at ian.miller@gems5.gov.bc.ca

This page was posted on July 5, 1999

Return to Top of Page | Forest Practices Branch Home page