Forests Sourcebook - HCV Resource Network

Forests Sourcebook - HCV Resource Network Forests Sourcebook - HCV Resource Network

hcvnetwork.org
from hcvnetwork.org More from this publisher
08.01.2014 Views

Box 7.14 FMIS in Bosnia and Herzegovina The following planning steps were employed in an FMIS project in Bosnia and Herzegovina that involved developing a unified network-based system: a) Conduct a gap analysis of the planning capacity of the various enterprises and agencies. b) Organize workshops to agree on approach with the stakeholders. c) Organize an FMIS Working Group (FMIS-WG)— comprising foresters, IT specialists, business managers, and inspection and planning officers—who would function as a process advisory group to define the basic data (including the minimum data needs for central planning and control functions) needed by the Cantonal Forest Management Companies (CFMCs). d) The FMIS-WG should organize a workshop to demonstrate the power of a comprehensive FMIS and to agree on the basic data needs and on the overall development process. State-of-the-art software providers (such as ESRI and Oracle), as well as users (for example, the Hungary forest enterprise association, the Polish State Forest Management Agency) should be invited to give presentations. Key representatives of the CFMCs and the ministerial and cantonal administrations should be invited to participate and the conclusions and recommendations should be recorded and disseminated. The main product of this workshop should be an agreed on concept of a centralized system as well as a process for developing that system. Agreement also needs to be reached as to the overall coordination of the process and on the “home” for the central database. Time required: three months planning and implementation. Coordinated by the Forest Development and Conservation Project’s (FDCP) project implementation unit (PIU) with help from the FMIS-WG. e) Designate the institutional coordinator for the FMIS development process and establish the institutional home for the central database. This is the responsibility of the ministry. All further development depends on this key step to designate and equip the “FMIS coordinator.” f) Prepare the tender package for designing the FMIS (international consultant, working with the FMIS- WG). At a minimum, the terms of reference (TOR) should include (i) an analysis of the existing situation and review of the data needs; (ii) a comparative analysis of international experience with similar systems to ensure the most cost-effective approach; (iii) the final design of the data module, the data format, and the presentational standards, taking into account any relevant government IT policy; and (iv) the programming, communications, hardware, and software customization. Time required: five months contracting and preparation. Coordinated by the FMIS coordinator, with input from the FMIS-WG. g) Organize a follow-up workshop to agree on the FMIS tender package, and to seek funding sources. Invite possible donors as well as government officials to agree on the TOR and to secure funding. Coordinated by the FMIS coordinator, with help from the international consultant and the FMIS-WG. h) Tender the development phase per the agreed TOR. Time required: eight months. i) Design the database system. Time required: six months. j) Tender the remaining hardware and software. k) Install the system, including training. In this case, the overall development process was estimated to take about two years. Source: Robak and Kirmse 2007. Technology specifications. The specific technologies 3 to be employed depend on the conceptual design and performance specifications, which should, in turn, take into account the infrastructure and resources (human, technical, and financial) that are available to the organization, internally or from service organizations with a local (or, more often these days, online) presence. Additional considerations include the following: ■ ■ ■ The programming language of the software should be one that is most appropriate and ideally, widely used. The databases and software should be able to handle the large number of transactions, ensure the security required in some applications, have the necessary long-term technical support, and not become obsolete in the short-term. 4 The total cost of operation, rather than the initial startup costs, should be the focus over the life of the project. 266 CHAPTER 7: MONITORING AND INFORMATION SYSTEMS FOR FOREST MANAGEMENT

■ If the application specifications are more complex, the most cost-effective approach would normally be to consider an already developed application or integrated multi-application system, where the provider is capable of adapting that system to the special needs of the client. 5 Developers or providers should not be forced to adopt one development environment. Instead, data interchange and interoperability rules should be adopted and enforced, allowing the replacement of old applications or addition of new ones in a “plug-and-play” 6 approach to system evolution. System detailed design and development. The application of an iterative design and development process may be more effective in producing an end product that finds widespread acceptance in a large organization. Coupled with a well-thought-out prototyping approach or the use of mockups, the risk of large project failures is greatly reduced and the likelihood of end user buy-in is greatly increased. System implementation and training. For implementing complex systems in large forestry organizations, the application of a pilot area approach, followed by phased roll-outs of the tested system, seems to be an effective strategy. End users should be involved in the design and development process to facilitate their understanding of and sense of ownership in the software and reduce implementation problems and training time. Training of the end users (especially foresters and other professionals) should focus on the process that the system is supposed to support. If the system (and user interface) is well designed, a good understanding of the processes that it is meant to support will ensure that the system will be used properly. LESSONS LEARNED AND RECOMMENDATIONS FOR PRACTITIONERS FMIS has recently become a popular component of World Bank projects (such as in Argentina, Bosnia and Herzegovina, Kazakhstan, Russia, Romania), but the development and implementation of these systems has been slow. Hence, there is inadequate experience from which to build standard design, development, and implementation protocols or compilations of lessons learned within the context of World Bank projects. Previous FMIS projects in India (Madhya Pradesh and Uttar Pradesh) have a longer track record, although they were also plagued with missed milestones and eventual loss of focus. Some key lessons follow: Constancy with respect to FMIS responsibility within the bureaucracy. Given the frequency of personnel transfers in bureaucratic systems, it is helpful to develop a cadre of specialists to provide long-term technical support for FMIS implementation and operation. Understanding and buy-in regarding modern forest management and its requirements at critical levels of the management hierarchy. It is important that managers realize that an FMIS should not simply “computerize” the traditional management processes. Reasonable goals for the initial development phases. While it is always necessary to keep in mind the nature and capabilities of the FMIS that must be developed, eventually, to support good forest management, the goals of the project must recognize the constraints and capabilities of the organization. It is far better to set realistic near-term goals within the context of a well-articulated, long-term development plan than to attempt to turn around an entire bureaucracy in one go. Vision or agreement as to what form such systems should take. The focus should be on spatial decision making and not on acquisition and maintenance of data, that is, let the process drive the system design. Time and effort must be spent on formulating a vision and strategy for the IT system and the new management processes that it is intended to serve, and on defining very specific objectives. Only after those have been defined can a TOR be formulated (see annex 7.2B to this note) and the detailed design and development phase begin. Realistic, phased development for a large, complex system. This is necessary for a bureaucracy to have time to adapt to new management processes and gain confidence from a series of “mini-successes.” Given the rapid development of FMIS technology, the development process should include two critical considerations: (i) the contracting of an FMIS specialist to lead the overall decision making and design process; and (ii) a comparison of the cost effectiveness of developing a system from scratch or adapting an already designed system (that is, procuring a turnkey system, in which the company would install the system and provide training). The turnkey approach would probably cost a fraction of what it would cost to develop a system from scratch and would take much less time, hence addressing some of the development problems mentioned above (see box 7.15). The value of a tested NOTE 7.2: ESTABLISHING FOREST MANAGEMENT INFORMATION SYSTEMS 267

Box 7.14<br />

FMIS in Bosnia and Herzegovina<br />

The following planning steps were employed in an<br />

FMIS project in Bosnia and Herzegovina that involved<br />

developing a unified network-based system:<br />

a) Conduct a gap analysis of the planning capacity of<br />

the various enterprises and agencies.<br />

b) Organize workshops to agree on approach with the<br />

stakeholders.<br />

c) Organize an FMIS Working Group (FMIS-WG)—<br />

comprising foresters, IT specialists, business managers,<br />

and inspection and planning officers—who<br />

would function as a process advisory group to<br />

define the basic data (including the minimum data<br />

needs for central planning and control functions)<br />

needed by the Cantonal Forest Management Companies<br />

(CFMCs).<br />

d) The FMIS-WG should organize a workshop to<br />

demonstrate the power of a comprehensive FMIS<br />

and to agree on the basic data needs and on the overall<br />

development process. State-of-the-art software<br />

providers (such as ESRI and Oracle), as well as users<br />

(for example, the Hungary forest enterprise association,<br />

the Polish State Forest Management Agency)<br />

should be invited to give presentations. Key representatives<br />

of the CFMCs and the ministerial and<br />

cantonal administrations should be invited to participate<br />

and the conclusions and recommendations<br />

should be recorded and disseminated. The main<br />

product of this workshop should be an agreed on<br />

concept of a centralized system as well as a process<br />

for developing that system. Agreement also needs to<br />

be reached as to the overall coordination of the<br />

process and on the “home” for the central database.<br />

Time required: three months planning and implementation.<br />

Coordinated by the Forest Development<br />

and Conservation Project’s (FDCP) project implementation<br />

unit (PIU) with help from the FMIS-WG.<br />

e) Designate the institutional coordinator for the FMIS<br />

development process and establish the institutional<br />

home for the central database. This is the responsibility<br />

of the ministry. All further development<br />

depends on this key step to designate and equip the<br />

“FMIS coordinator.”<br />

f) Prepare the tender package for designing the FMIS<br />

(international consultant, working with the FMIS-<br />

WG). At a minimum, the terms of reference (TOR)<br />

should include (i) an analysis of the existing situation<br />

and review of the data needs; (ii) a comparative<br />

analysis of international experience with similar<br />

systems to ensure the most cost-effective approach;<br />

(iii) the final design of the data module, the data<br />

format, and the presentational standards, taking<br />

into account any relevant government IT policy;<br />

and (iv) the programming, communications, hardware,<br />

and software customization. Time required:<br />

five months contracting and preparation. Coordinated<br />

by the FMIS coordinator, with input from the<br />

FMIS-WG.<br />

g) Organize a follow-up workshop to agree on the<br />

FMIS tender package, and to seek funding sources.<br />

Invite possible donors as well as government<br />

officials to agree on the TOR and to secure funding.<br />

Coordinated by the FMIS coordinator, with<br />

help from the international consultant and the<br />

FMIS-WG.<br />

h) Tender the development phase per the agreed TOR.<br />

Time required: eight months.<br />

i) Design the database system. Time required: six<br />

months.<br />

j) Tender the remaining hardware and software.<br />

k) Install the system, including training.<br />

In this case, the overall development process was<br />

estimated to take about two years.<br />

Source: Robak and Kirmse 2007.<br />

Technology specifications. The specific technologies 3 to<br />

be employed depend on the conceptual design and performance<br />

specifications, which should, in turn, take into<br />

account the infrastructure and resources (human, technical,<br />

and financial) that are available to the organization, internally<br />

or from service organizations with a local (or, more<br />

often these days, online) presence. Additional considerations<br />

include the following:<br />

■<br />

■<br />

■<br />

The programming language of the software should be<br />

one that is most appropriate and ideally, widely used.<br />

The databases and software should be able to handle the<br />

large number of transactions, ensure the security required<br />

in some applications, have the necessary long-term technical<br />

support, and not become obsolete in the short-term. 4<br />

The total cost of operation, rather than the initial startup<br />

costs, should be the focus over the life of the project.<br />

266 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!