Selection criteria for tools

The decision-support tools for managing climate that are listed on this website were assessed by a panel of experts against a set of criteria.

 

What criteria must the tool meet?

The panel defined the following criteria:

  1. The tool must meet clearly apparent user needs, answering questions of importance to farmers and agribusiness consultants as they incorporate climate risk management in their decision making.
  2. Simple tools are often better because the logic is easy to understand.
  3. If a tool is complex, the logic must be well articulated, peer reviewed in terms of science quality and generally the underlying algorithms, models and methods should be of high scientific calibre.
  4. The tool must be cost-effective to implement i.e. the data and effort required to run the tool should lead to benefits well exceeding these input costs.
  5. The tool must be accessible, preferably on the web.
  6. Support must be provided for the tool and its application. It is likely to include:
    • training
    • inclusion in extension programs
    • nominated contact officers to answer questions of clarification
  7. Farmers and/or agribusiness consultants should have been involved in the design and in ongoing application/modifications.
  8. Data inputs must be reliable, well specified and appropriate.
  9. Appropriate climate data must be incorporated in the tool, recognising that:
    • most tools are based on the analogue year concept
    • many tools are unlikely to incorporate the outputs of dynamical climate modelling
    • the implications of climate change will also affect the tool’s accuracy
  10. The tool must be explicit in its applicability, specifying any spatial and temporal limitations and potential errors in the outputs as a function of the nature of the input data and the algorithms used.

Back to top

How do I propose a tool for inclusion on Climate Kelpie?

If you know of a tool that you believe meets the criteria, please let us know.

 

Back to top

 

 

•H ow do I propose a tool for inclusion?
Who selects the tools?
A panel of agricultural scientists with experience in climate applications selects the tools:
•Brendan Cullen
•David Freebairn
•Peter Hayman
•Zvi Hochman
Back to top
What criteria must the tool meet?
The panel defined the following criteria:
1.The tool must meet clearly apparent user needs, answering questions of importance to farmers and agribusiness consultants as they incorporate climate risk management in their decision making.
2.Simple tools are often better because the logic is easy to understand.
3.If a tool is complex, the logic must be well articulated, peer reviewed in terms of science quality and generally the underlying algorithms, models and methods should be of high scientific calibre.
4.The tool must be cost-effective to implement i.e. the data and effort required to run the tool should lead to benefits well exceeding these input costs.
5.The tool must be accessible, preferably on the web.
6.Support must be provided for the tool and its application. It is likely to include:
•training
•inclusion in extension programs
•nominated contact officers to answer questions of clarification
7.Farmers and/or agribusiness consultants should have been involved in the design and in ongoing application/modifications.
8.Data inputs must be reliable, well specified and appropriate.
9.Appropriate climate data must be incorporated in the tool, recognising that:
•most tools are based on the analogue year concept
•many tools are unlikely to incorporate the outputs of dynamical climate modelling
• the implications of climate change will also affect the tool’s accuracy
10.The tool must be explicit in its applicability, specifying any spatial and temporal limitations and potential errors in the outputs as a function of the nature of the input data and the algorithms used.
Back to top
How do I propose a tool for inclusion?
If you know of a tool that you believe meets the criteria, please let us know [link to contact page].
Back to top

 

JRegistry Object
(
    [data:protected] => stdClass Object
        (
            [pathwaypage] => 0
            [pathwaytype] => 1
            [scale] => 
            [topic] => Various - see individual tools
            [cost] => Various
            [summary_commodity] => Various
            [summary_region] => Various
            [tabledisplayscale] => 0
            [tablesubpagetitle] => Page
        )

)


JRegistry Object ( [data:protected] => stdClass Object ( [pathwaypage] => 0 [pathwaytype] => 1 [scale] => [topic] => Various - see individual tools [cost] => Various [summary_commodity] => Various [summary_region] => Various [tabledisplayscale] => 0 [tablesubpagetitle] => Page ) )

Print page