08.01.2014 Views

Forests Sourcebook - HCV Resource Network

Forests Sourcebook - HCV Resource Network

Forests Sourcebook - HCV Resource Network

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

expertise of the consultancy team<br />

experience and track record in similar FMIS projects<br />

proposed cost of development, implementation, and<br />

training<br />

estimated cost and requirements (especially those related<br />

to human resources) for continued operation of the<br />

system<br />

estimated ongoing maintenance and support costs<br />

technologies, protocols, and standards proposed (including<br />

facilitation of future development and evolution of<br />

the system)<br />

intellectual property ownership and rights<br />

realism of schedules<br />

realism and acceptability of commitment required of the<br />

client<br />

ability to provide long-term support<br />

Specific tasks<br />

Besides the work described above, specific tasks and operating<br />

methods are suggested as ways to increase the likelihood<br />

of success in an FMIS project. Most of these are related to<br />

education, communication, and participation.<br />

Phase I. Interview officials who are responsible for the strategic<br />

direction of the organization to gauge their clarity of purpose<br />

and understanding of modern forest management and<br />

the capabilities of IT. Undertake a review of the context in<br />

which the FMIS must fit. Based upon the results of these<br />

interviews and the evaluation of the context, design and hold<br />

a workshop that fills knowledge gaps and leads to a consensus<br />

on the objectives and strategies of the FMIS on the part of<br />

upper management. To ensure the outcomes of the workshop<br />

are appropriate:<br />

■<br />

for example) may maintain databases that could augment<br />

the FMIS and vice versa. It is not efficient, from an<br />

overall government perspective, to duplicate data-gathering<br />

and storage efforts or, even worse, to have agencies<br />

develop incompatible systems.<br />

After a consensus on objectives and strategies has been<br />

reached, present the conceptual design recommendations<br />

to upper management (articulating the needs, functionalities,<br />

and development strategy; estimating costs and time<br />

needed for the various development options and for the<br />

various functionalities; reviewing and disseminating<br />

information on the various turn-key options) for their<br />

approval. Upon receiving this approval, the conceptual<br />

design (with functionalities) should be presented to<br />

intended users of the FMIS, to get their feedback and suggestions<br />

for improvements. It is strongly recommended<br />

that a well-defined and stable user group sign off on the<br />

final design (and then monitor the development of the<br />

FMIS). An agreed on process of staged development and<br />

implementation is necessary to avoid future conflicts<br />

within the user group or between users and developers.<br />

Phase II. The design phase will require that interviews and<br />

workshops be held with all major user groups, first to help<br />

establish draft design specifications, then to gain acceptance of<br />

the final specifications and the major elements of the Development<br />

and Implementation TOR (including acceptance of<br />

their responsibilities in the development, testing, implementation,<br />

and training processes). Successful implementation of an<br />

FMIS will require, or will be undertaken in combination with,<br />

work process changes, which may necessitate a cultural change<br />

in an organization. The human resources management issues<br />

must be considered, both in terms of the FMIS requirements<br />

and their impacts upon the FMIS project.<br />

■<br />

■<br />

■<br />

■<br />

The various user groups in an organization need to be<br />

educated about what the new FMIS might do for them.<br />

Often they do not have a clear idea about how an FMIS<br />

might work and what it implies for their work processes.<br />

It needs to be made clear that the FMIS is not just about<br />

computerizing their existing manual processes. Existing<br />

work processes may need careful review and redesign as<br />

a prelude to the detailed design and development of the<br />

FMIS, which adds to the size of the task.<br />

The FMIS project design should recognize that the<br />

requirements of an FMIS will change over time, as will<br />

the technologies employed.<br />

It should be recognized that other government agencies<br />

(related to land and water management and agriculture,<br />

Phase III. An important element that should not be forgotten<br />

in the development, testing, implementation, and training<br />

phases is the ongoing communication and feedback processes<br />

that must be developed and maintained to ensure the best<br />

possible final product, reduction in lost time due to misunderstandings,<br />

and eventual buy-in from the users. It should<br />

be made clear to Phase III bidders that their proposals will be<br />

evaluated in part by how well they have responded to this<br />

requirement.<br />

Process and Reporting Arrangements<br />

Specify the line agency to which the consultants would<br />

report. That is, specify the agency that would be managing<br />

272 CHAPTER 7: MONITORING AND INFORMATION SYSTEMS FOR FOREST MANAGEMENT

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!