Forests Sourcebook - HCV Resource Network
Forests Sourcebook - HCV Resource Network Forests Sourcebook - HCV Resource Network
ANNEX 7.2A MODEL TERMS OF REFERENCE The TOR for a specific FMIS project should be drawn up only after the vision and strategy for the desired system have been developed. Nevertheless, the following may help form the basis of a TOR. TERMS OF REFERENCE DEVELOPING A NATIONAL FMIS Summary and Instructions This section should provide an executive summary of the project, including a description of the broad objectives and scope of the FMIS project; the sources and timing of financing; and the project management responsibilities and protocols. Background This section sets the broad context for the FMIS project and provides justification for the goals and scope of the FMIS project and the development approach to be taken. In most cases, an FMIS project is intended to do more than provide new IT support for existing forest management processes; it will require and support new management and decision processes. However, any intended “re-engineering” of management processes should be made explicit, otherwise resistance to change will be difficult to overcome and FMIS design will lack focus. Specific Objectives of the Assignment An FMIS project should normally be divided into at least two (and possibly three) phases and contracts that would involve 1) the identification of the forest management decision processes that the FMIS is intended to support, with a detailed description of the context that should inform the project management process and drive and constrain the design and development phases, and a broad description of the functionalities of the proposed FMIS; 2) a system design process resulting in clear design specifications that are justified in terms of that context and project goals; and 3) a system development and implementation process based upon the design specifications and the project management process. Objectives and Context—Phase I. The first contract would manage the consultative process for developing the detailed objectives that the FMIS will support and clearly defining the context of the system. The contextual information that should be provided would include a) a summary of the forest inventory, categorized and characterized in terms of uses, values, tenure, and management structures; b) the status of current forest policies, strategies, and plans at the national, regional, district, and individual forest areas; c) the current state of knowledge concerning the status and dynamics of the forest resources to be managed; d) a summary of the major influences on and challenges to good management (including knowledge gaps, public policy trends, land use and tenure issues, public attitudes, and illegal activities); e) current uses and values (economic, environmental, and social) of the forest and an identification of the beneficiaries and stakeholders; f) the laws, regulations, and regulatory and management structures (including but not limited to the organization of the forest service) that influence and direct forest management; g) the status of the communication and IT infrastructure (including data quantity and quality) in the country, classified by region and according to the forest service hierarchy; h) internal and external technical support capabilities with respect to the IT and communication infrastructure; i) human resources policies that may have an impact on developing an IT cadre in the forest service (even if much of the work is outsourced, there needs to be a core of management that understands and directs IT development over the long term); and j) the current level of knowledge and capacities regarding forest management, business (or organizational) management, and information technologies in the forest service and other allied or support organizations that are involved in the analysis, planning, implementation, and control of forest resources and forest management activities. Based upon the above context, the FMIS design objectives and project management modalities should be clearly described and explicitly justified. This work should include a description of functionalities, an identification of users 270 CHAPTER 7: MONITORING AND INFORMATION SYSTEMS FOR FOREST MANAGEMENT
(direct and indirect) and usage patterns and processes, as well as a description of the data requirements and data sources. If the FMIS development is to coincide with management process changes, the links between the FMIS project and process change initiative should be clearly delineated. Detailed Design—Phase II. The main tasks of this phase of the work are to a) develop the detailed design specifications for the FMIS; b) review and analyze existing FMIS and support technologies in relation to the specifications; c) review possible methods for the development of the FMIS (adapting existing technologies, developing components “from scratch” using in-house or external expertise) 1 ; d) recommend (with justification) the preferred development method (which may well include a combination of the above); e) estimate the human resources requirements (including commitment from client personnel), time, and cost of the installed FMIS; and, f) consolidate the above information into a document that outlines the critical elements of the Development and Implementation TOR. In principle, it should not be the task of this consultant to recommend the specific development environment or database and support technologies to be used because the design specifications and the context description (especially those related to local IT capabilities) should be clear enough that any inappropriate technologies would not be proposed or, if proposed, would not be chosen. However, the design consultant should develop a draft Development and Implementation TOR that recommends the software development, quality assurance, and project management standards and protocols that should be used by the developer, including those that facilitate future system evolution and compatibility with other national and international forestry and environmental systems. Development and Implementation—Phase III. The following is a list of issues that would likely need to be addressed in the Development and Implementation TOR: ■ Software design specifications and performance criteria, including those related to specific functionalities; national and international data standards that must be ■ ■ ■ ■ ■ ■ ■ ■ followed (such as European numerical data standards); reports to be produced; spatial visualization and modeling capabilities; data entry protocols; security and access; description of users (including working language) and usage patterns (including multiuser and web-enabled capabilities); integration among FMIS components; interfaces and integration with existing or proposed non-FMIS systems; minimum data auditing and data recovery; and back-up and archiving requirements. Characteristics of software technologies to be employed, including recommendations concerning which elements should be built from scratch and which should be adapted from existing technologies. This should also address issues concerning the flexibility and resiliency of any system being proposed, including its degree of adherence to “plug-n-play” principles and open source 2 standards. Hardware specifications (including those related to operating environment, health, and ergonomics) and rules and regulations that govern hardware acquisition. Description of data preparation work required, including (as appropriate) data migration and conversion; preparation of base and thematic maps; forest and land recharacterization; and acquisition, analysis, and incorporation of remote sensing imagery and data. Description of the current forest management and IT knowledge of proposed users and internal IT support personnel, and the level that is desired. This means that, where appropriate, the TOR must specify the education and training required to use the system to maximize the benefits, not simply train people about “which buttons to push.” Minimum requirements related to implementation and training, technical and user documentation, and system support. Minimum software and project management quality assurance protocols to be employed. Description of the minimum level of long-term support that will be required to be provided by the development and implementation contractors. Description of the commitment from the clients with respect to the engagement of its people in the development, testing, implementation, and training processes. Evaluation Criteria Tender documents should be evaluated according to the quality of the tender in relation to the requirements of the TOR and then according to the following criteria: NOTE 7.2: ESTABLISHING FOREST MANAGEMENT INFORMATION SYSTEMS 271
- Page 220 and 221: allow for each country’s differen
- Page 222 and 223: limited in the coverage and duratio
- Page 224 and 225: Box 6.12 The Use of DPLs to Support
- Page 226 and 227: Box 6.13 Using DPLs in Lao PDR for
- Page 228 and 229: OPCS. 2004. “Good Practice Notes
- Page 230 and 231: OPERATIONAL ASPECTS Prioritizing th
- Page 232 and 233: orientation of the DPL operations c
- Page 234 and 235: Indicators are helpful in these sit
- Page 236 and 237: ANNEX 6.3A SELECT TOOLS TO ASSIST S
- Page 238 and 239: NOTE 6.4 Assessing Cross-Sectoral I
- Page 240 and 241: Box 6.16 The Forests Component in t
- Page 242 and 243: Considering the above issues, an in
- Page 244 and 245: Box 6.19 Implementation of the Keny
- Page 246 and 247: World Bank SEA Web resources: http:
- Page 248 and 249: Box 7.1 Monitoring Promotes Changes
- Page 250 and 251: collected via remote sensing rather
- Page 252 and 253: Discussions and proposals on how to
- Page 254 and 255: Assessment (www.millenniumassessmen
- Page 256 and 257: FAO. 2004. “Manual for Environmen
- Page 258 and 259: ■ ■ ■ enables implementation
- Page 260 and 261: selecting the technology. Technolog
- Page 262 and 263: USFS Field Guides: www.fia.fs.fed.u
- Page 264 and 265: Box 7.13 System Architecture of a S
- Page 266 and 267: Box 7.14 FMIS in Bosnia and Herzego
- Page 268 and 269: and client-rich system, which would
- Page 272 and 273: ■ ■ ■ ■ ■ ■ ■ ■ ■
- Page 274 and 275: NOTE 7.3 Spatial Monitoring of Fore
- Page 276 and 277: ■ ■ ■ ■ Availability of ref
- Page 278 and 279: Box 7.19 Selecting the Appropriate
- Page 280 and 281: Table 7.4 Existing Satellite Remote
- Page 282 and 283: Tropical Ecosystem Environment Obse
- Page 285: PART II Guidance on Implementing Fo
- Page 288 and 289: forestry activities was counterprod
- Page 290 and 291: waterways, or the quantity or quali
- Page 292 and 293: ■ ■ ■ ■ ■ an independent
- Page 294 and 295: ■ In the case of forest harvestin
- Page 296 and 297: ■ ■ harvesting supported by Wor
- Page 298 and 299: However, some of the World Bank’s
- Page 300 and 301: ■ ■ ■ ■ ■ ■ Examine the
- Page 302 and 303: Box 9.2 Participation Strategy To m
- Page 304 and 305: Box 9.5 Process Framework for Invol
- Page 306 and 307: Box 9.8 Market Analysis A market an
- Page 308 and 309: “no-project” option); and recom
- Page 310 and 311: Box 9.16 Environmental Management P
- Page 312 and 313: ■ ■ ■ ■ ■ ■ ■ ■ ■
- Page 314 and 315: the detailed Biodiversidade Brasile
- Page 316 and 317: ■ ■ management plan—prepared
- Page 319 and 320: CHAPTER 10 Consultation and Communi
ANNEX 7.2A<br />
MODEL TERMS OF REFERENCE<br />
The TOR for a specific FMIS project should be drawn up<br />
only after the vision and strategy for the desired system have<br />
been developed. Nevertheless, the following may help form<br />
the basis of a TOR.<br />
TERMS OF REFERENCE<br />
DEVELOPING A NATIONAL FMIS<br />
Summary and Instructions<br />
This section should provide an executive summary of the<br />
project, including a description of the broad objectives and<br />
scope of the FMIS project; the sources and timing of<br />
financing; and the project management responsibilities and<br />
protocols.<br />
Background<br />
This section sets the broad context for the FMIS project and<br />
provides justification for the goals and scope of the FMIS<br />
project and the development approach to be taken. In most<br />
cases, an FMIS project is intended to do more than provide<br />
new IT support for existing forest management processes; it<br />
will require and support new management and decision<br />
processes. However, any intended “re-engineering” of management<br />
processes should be made explicit, otherwise resistance<br />
to change will be difficult to overcome and FMIS<br />
design will lack focus.<br />
Specific Objectives of the Assignment<br />
An FMIS project should normally be divided into at least two<br />
(and possibly three) phases and contracts that would involve<br />
1) the identification of the forest management decision<br />
processes that the FMIS is intended to support, with a<br />
detailed description of the context that should inform<br />
the project management process and drive and constrain<br />
the design and development phases, and a broad description<br />
of the functionalities of the proposed FMIS;<br />
2) a system design process resulting in clear design specifications<br />
that are justified in terms of that context and<br />
project goals; and<br />
3) a system development and implementation process<br />
based upon the design specifications and the project<br />
management process.<br />
Objectives and Context—Phase I. The first contract<br />
would manage the consultative process for developing the<br />
detailed objectives that the FMIS will support and clearly<br />
defining the context of the system. The contextual information<br />
that should be provided would include<br />
a) a summary of the forest inventory, categorized and characterized<br />
in terms of uses, values, tenure, and management<br />
structures;<br />
b) the status of current forest policies, strategies, and plans at<br />
the national, regional, district, and individual forest areas;<br />
c) the current state of knowledge concerning the status and<br />
dynamics of the forest resources to be managed;<br />
d) a summary of the major influences on and challenges to<br />
good management (including knowledge gaps, public<br />
policy trends, land use and tenure issues, public attitudes,<br />
and illegal activities);<br />
e) current uses and values (economic, environmental, and<br />
social) of the forest and an identification of the beneficiaries<br />
and stakeholders;<br />
f) the laws, regulations, and regulatory and management<br />
structures (including but not limited to the organization<br />
of the forest service) that influence and direct forest<br />
management;<br />
g) the status of the communication and IT infrastructure<br />
(including data quantity and quality) in the country,<br />
classified by region and according to the forest service<br />
hierarchy;<br />
h) internal and external technical support capabilities with<br />
respect to the IT and communication infrastructure;<br />
i) human resources policies that may have an impact on<br />
developing an IT cadre in the forest service (even if much<br />
of the work is outsourced, there needs to be a core of<br />
management that understands and directs IT development<br />
over the long term); and<br />
j) the current level of knowledge and capacities regarding<br />
forest management, business (or organizational) management,<br />
and information technologies in the forest service<br />
and other allied or support organizations that are involved<br />
in the analysis, planning, implementation, and control of<br />
forest resources and forest management activities.<br />
Based upon the above context, the FMIS design objectives<br />
and project management modalities should be clearly<br />
described and explicitly justified. This work should include a<br />
description of functionalities, an identification of users<br />
270 CHAPTER 7: MONITORING AND INFORMATION SYSTEMS FOR FOREST MANAGEMENT