oneDAFWA 31 July 2016 - Agriculture and Food Web viewAPPENDIX 1 – EXAMPLE DAFWA PestFax MAP...

Pest & Disease Reporting Data Exchange Interface

Information Tool Kit for Applicants

oneDAFWA 31 July 2016

About this information toolkit

This toolkit describes what is involved in applying for funding from the eConnected Grainbelt project, and what will be required if your application is successful. This information toolkit provides important information on the following:

Introduction.......................................................................................................................1

PestFax Map Project Overview................................................................................................1

Part 1: Grant submission guidelines....................................................................................1

Expression of Interest..............................................................................................................1

Online submissions.................................................................................................................2

Two-stage Selection Process....................................................................................................2

Part 2: Priorities for funding...............................................................................................2

The scope of the service required will include the following:...................................................3

The scope will not include:......................................................................................................3

Part 3: Application process.................................................................................................4

Pre-Qualifying Eligibility Criteria..............................................................................................4

Essential Criteria.....................................................................................................................4

Desirable Criteria....................................................................................................................4

What we will do for you..........................................................................................................5

Respondent Questions............................................................................................................5

How Application will be assessed............................................................................................5

Key Dates................................................................................................................................6

Further information................................................................................................................7

Part 4: Grant Funding Information for Grant Recipients......................................................7

Developing your funding agreement.......................................................................................7Step 1: Satisfy any conditions placed on the agreement......................................................................7Step 2: Supplying some additional information....................................................................................7Step 3: Signing the funding agreement.................................................................................................8Step 4: Receiving the funding...............................................................................................................8

Managing your project............................................................................................................8

Reporting requirements..........................................................................................................9Progress report and annual audited financial statement......................................................................9Final report and audited financial statement.......................................................................................9Acknowledging DAFWA, the Department of Regional Development and Royalties for Regions..........9Providing photographs.......................................................................................................................10

oneDAFWA Page of

IntroductionPestFax Map Project OverviewPestFax Map is a web based map interface to the PestFax and PestFacts newsletters, which compile reports of insect pests of crops across the southern grain growing regions of Australia as well as reports of crop disease in Western Australia.

PestFax Map began operation in Western Australia the 2011 growing season. In its first year 4638 pest and disease maps were produced by a total of 340 users. In the second year 914 users generated 12,367 maps, an increase of about three times. In 2013 PestFax map was expanded to operate across South Australia, Victoria and New South Wales.

DAFWA have developed a set of PestFax APIs and are seeking to engage with a Farm Management Solution (FMS) provider to develop the functionality of the APIs and to implement Pest and Disease reporting to PestFax Map and the PestFax newsletter from their system.

It is anticipated that the successful FMS provider will develop, test and release as part of their standard product offering, the ability for their customers to retrieve pest, disease and host specification data from DAFWA’s PestFax Map and send data from their FMS to the PestFax Map utilising these APIs, as described in Appendix 1.

Funding for this initiative is being provided by DAFWA’s eConnected Grainbelt Royalties for Regions project.

Part 1: Grant submission guidelines Applications close 9am, Friday 2 December 2016.

Expression of Interest The eConnected Grainbelt project is wanting to work with one or more suitably experienced Farm Management Solution (‘FMS’) provider(s) to establish a successful data exchange between the DAFWA’s Pest and Disease Reporting application (‘PestFax Map’) and the provider’s own farm management solution.

Round 1 Expressions of interest (EoI) are now open.

Up to $200,000 will be invested in this EoI process.

Individual grants are available between $50,000 - $100,000.

Before submitting your application, please read this ‘Information toolkit for applicants’ which provides additional details, including what to expect if your application is successful.

oneDAFWA Page 2 of 23

Online submissionsApplicants are encouraged to use the online templates for submitting their expression of interest to partner with DAFWA on this sub-project. Those who are unable to use this can contact Roena Hooper (see below for contact details) for a MS Word template.

Expressions of interest must be submitted using the SmartyGrants application form: www.agric.smartygrants.com.au

All applicants will be notified by email that their application has been received.

Two-stage Selection Process A two stage selection process will be used to assess applicant’s eligibility to deliver on the sub-projects objectives:

Stage 1 Expression of Interest – proponents will need to address all criteria in the proposal template available online. Preliminary proposals will be shortlisted by a selection panel. Applications close 9am, Friday 02 December 2016

Stage 2 Full Project Plan – shortlisted proponents will be invited to submit a more detailed Project Plan for assessment by a selection panel (online template will be provided).

Projects may be wholly or partly funded, and may have conditions or recommendations attached that need to be addressed before funding is granted.

Before submitting your application, please read Part 3 “Grant Application Process” for what to expect if your application is successful.

All applicants, whether successful or not, will be notified in writing. Decisions on funding are final.

Part 2: Priorities for funding The Department of Agriculture and Food Western Australia (DAFWA) have an application, PestFax Map, which stores information on reported pests and diseases. This application is available through the websitewww.agric.wa.gov.au/diseases/pestfax-map.

PestFax Map provides a map view of reported diseases and pests and provides the facility for users to report pests or diseases that have been observed at a specific location. DAFWA produces an informative newsletter based on observations and other information. This newsletter is available on DAFWA’s web site on www.agric.wa.gov.au/crop-diseases/pestfax-newsletter.

oneDAFWA Page of

http://www.agric.wa.gov.au/crop-diseases/pestfax-newsletter

http://www.agric.wa.gov.au/diseases/pestfax-map

http://www.agric.smartygrants.com.au/

DAFWA is implementing a standard framework for the exchange of agricultural data, including reporting of plant pests and diseases. This framework will proved a standard way by which service providers of Farm Management Solutions (FMS’) can facilitate the reporting of pest and disease observations to DAFWA’s PestFax Map application.

The intention is to develop and publish a standard web service (REST API) for PestFax Map to allow service providers to implement the API in their application and demonstrate how it can interact with grower’s on-farm and in real time. To achieve this, DAFWA is first of all implementing facilities whereby external parties can retrieve data from or post data to DAFWA via the use of defined REST APIs.

The objective of this grant process is to test the implementation of this data exchange framework by engaging Farm Management Solution provider(s) to implement a solution in their product that utilises the DAFWA API which provides information on observations of pests and disease to the existing DAFWA PestFax Map application. This will allow DAFWA and the selected third party software provider(s) to test the data exchange mechanism.

Once proven to work, DAFWA will then publish its APIs for anyone to consume. In time more APIs will be developed allowing for an easy exchange of data.

Other organisations will be encouraged to utilise a similar data exchange mechanism.

The scope of the service required will include the following:a). A specification that will provide an agreed method for the exchange of data

through the use of a standard DAFWA API that can be utilised by anyone who to exchange pest and disease reporting information with DAFWA;

b). Development and Implementation of an application, or enhancement of an existing application, that utilises the DAFWA API and will allow input of relevant information from paddocks/locations to the PestFax Map database; and

c). Testing of the application, showing successful interaction between a commercial farm management system and the PestFax Map decision tool.

Note: DAFWA has developed the PestFax Map API.

The scope will not include:Any agreement for subsequent developments of the PestFax Map API by DAFWA or any enhancement to the Respondent’s application.

oneDAFWA Page of

Part 3: Grant Application processPre-Qualifying Eligibility Criteria Only incorporated organisations with the ability to receive funds (ABN provided) are eligible to apply.

Essential CriteriaApplicants must demonstrate that they have an established track record in the provision of farm management solutions to growers within Western Australia, including:

1. Providing information regarding their software, including but not limited to, details on its current Pest and Disease recording functionality; and

2. Describing their current customer base in Western Australia (WA). This should include details such as the number of growers and consultants in WA currently utilising their software.

Applicants must demonstrate that they have the organisational capacity to develop, test and implement enhancements to their farm management solution, including:

1. Describing their commercial and organisational structure, which includes the identity of all key entities expected to be engaged in the delivery of a Pest and Disease Management Reporting data exchange between DAFWA and their farm management solution. This is to include any sub-contractors and all members of a consortium, if applicable;

2. Describing their resource capacity relevant to the scope of services required;3. Describing their product development processes. Details should include:

a. What changes, if any, would be required to their system to enable interaction with the PestFax Map API; and

b. The anticipated length of time/ resources required to undertake the changes.

4. Describing their proposed approach to testing and implementation. The Respondent should describe how they propose to work with DAFWA project staff.

5. Describing their ability and willingness to deploy and make available the Pest and Disease Reporting functionality delivered as part of these requirements to their customers (i.e. the WA growing community); and

6. Describing their ability and willingness to maintain the Pest and Disease Reporting functionality once implemented.

Desirable CriteriaIt is desirable that the applicant be based in Regional WA.

It is desirable that the applicant undertake development work in Regional WA.

oneDAFWA Page of

What we will do for youDAFWA will provide expert consultation in data architecture and programming for:

Negotiation of the detailed scope, timing and pricing for the project;

Implementing the DAFWA API to read or update data from or to PestFax Map; and

Collaborative testing of the API and use of API in the service provider’s application.

Appendix I provides briefs of specifications describing the various APIs that will be available to implement the proposed solution. More APIs may be required and/or may require changes.

Respondent QuestionsRespondents may ask questions of the PestFaxMap Project Manager – (Art Diggle) in relation to the EOI documentation from the date it is advertised up to 5pm (WST) Monday 14 November 2016. Questions will not be accepted after this time. The purpose of setting this date is to allow Art Diggle time to respond to any final questions raised and to provide sufficient time for Respondents to consider that information prior to the closing time for the submission of the EOI.

All questions should be placed in writing, preferably in the form of an email, and sent to Art Diggle using the detail provided in the Further Information section of this document. The email must reference the EOI with its relevant number in the subject field.

If any questions raised by Respondents result in the provision of additional information, this information will also be provided to all other prospective Respondents by way of an addendum to the EOI. Art Diggle will endeavour to respond as quickly as possible post receipt of any question. However, the nature and extent of the question(s) will determine the timeframe within which responses will be made.

How Application will be assessedDAFWA will appoint an expert selection panel (3-5 members) to provide industry, technical and scientific expertise in the assessment of applications and make recommendations to the eConnected Grainbelt fund Steering Committee.

A two-stage selection process will be used:

Stage 1 Expressions of interest – an expert selection panel will assess each application and recommend a shortlist of projects to progress to Stage 2.

Stage 2 Full Project Proposal – shortlisted applicants will be invited to submit a detailed proposal for assessment by the expert selection panel.

The expert selection panel will take into account factors including:

oneDAFWA Page of

A demonstrated established track record in the provision of farm management solutions to growers within Western Australia;

Demonstrated organisational capacity to develop, test and implement enhancements to their farm management solution; and

A base in regional Western Australia and undertaking development work in regional Western Australia

Following consideration of the expert selection panel’s assessments of the full project proposals, the eConnected Grainbelt fund Steering Committee will make recommendations to the Project Sponsor on:

which applications are suitable for funding the level of funding for each successful applicant any conditions that are to apply to any offer of funding.

Before submitting your application, please read ‘Part 4: Grant Funding Information for grant recipients’ for what to expect if your application is successful.

Successful applicants will be sent a letter of offer setting out details of the funding and any conditions that must be addressed before the offer can be accepted or that will apply to the funding.

Unsuccessful applicants will be advised in writing and provided an opportunity for further feedback.

Decisions on funding are final.

Key Dates

Stage Key Event/Milestone Indicative Completion Date

1 EoI ProcessEoI Open date 31 Oct 2016Period for Respondent Questions 11 Nov to 14 Nov 2016EoI Close date 2 Dec 2016Short-listed Respondent(s) notified 9 Dec 2016

2 Full Project ProposalRequest Issue date (to short-listed respondent(s) 9 Dec 2016Request Close date 17 Feb 2017Evaluation of Responses 22 Feb 2017

3 Contract FormationPreferred Respondent (s) notified 24 Feb 2017Due Diligence and Negotiations completed (if required)

10 March 2017

Contract awarded 17 March 2017Contract commencement date 20 March 2017

*Applicants will be advised of any changes to scheduled dates in writing.

oneDAFWA Page of

Further informationScope of FundingContact Art Diggle, Senior Research Officer, DAFWA:Email: [email protected] telephone: +61 (0)8 9368 3563

EoI Smarty Grant Application processContact Roena Hooper, Executive OfficerEmail: [email protected] telephone: +61 (0)8 9368 3906

Part 4: Grant Funding Information for Grant Recipients This section describes what is involved in being a recipient of eConnected Grainbelt funding.

Everyone in your project (including third parties) should apply this information to ensure you meet the requirements of your funding agreement.

This section outlines:

the process involved in developing your funding agreement; requirements for acknowledging the funding source; expectations of how the project will be managed; and reporting requirements.

Developing your funding agreementOnce you receive notification that your Stage 2 full project proposal application was successful, a funding agreement between your organisation and DAFWA will need to be developed.

Step 1: Satisfy any conditions placed on the agreementConditions are sometimes placed on recipients to:

confirm information on proposed activities ensure costs are justified provide evidence of support from project collaborators, supporters, participants (if

not provided when your application was submitted) ensure linkages with other research are made.

If your offer has conditions attached, you need to demonstrate that you can satisfy these before a funding agreement can be developed.

oneDAFWA Page of

mailto:[email protected]

mailto:[email protected]

Step 2: Supplying some additional informationYou may be asked to provide:

proof of legal entity status; proof of insurance (including public liability, personal accident and professional

indemnity insurance); banking, Australian Business Number and GST registration details.

Step 3: Signing the funding agreementYou will receive two copies of the funding agreement. Both should be signed and returned to DAFWA.

DAFWA will counter-sign and date both copies and return one to you.

Step 4: Receiving the fundingFunding will be provided on delivery of milestones. The first milestone will be the signing of the funding agreement, and this would normally trigger the first payment.

You will be asked to complete a Supplier Creation and Maintenance Form. Once this information has been received and processed, you will receive a Purchase Order number.

You will need to send a tax invoice to DAFWA to trigger the payment of funds. The tax invoice must state the Purchase Order number and include GST.

Managing your projectThe eConnected Grainbelt funding is an investment made by the state government using public money.

Receipt of this funding comes with the responsibility of ensuring it is used for public benefit and managed in a way that achieves the best outcome for the Western Australian agriculture and agrifood industry.

Acting with integrity, transparency and accountability is key to this, as is sharing information about your project with people who might be affected by it.

Below is an overview of how fund recipients and others involved in your project are expected to operate when managing a project funded by the Royalties for Regions program.

Good governance practices are used. The rights of the people involved in your project are respected, including the

consideration and management of safety, health and welfare issues. Good records are kept and regularly maintained. Records must be kept for six

years. Transparent and accessible financial management. Note that unspent funds must

be returned to DAFWA at the end of your project.

oneDAFWA Page 9 of 23

Best practice techniques are applied to ensure project activities are conducted in the most effective and safe manner.

Formal variations to the funding agreement can be made if unforeseen circumstances mean that you cannot run your project as planned.

Reporting requirements

Progress report and annual audited financial statementKey performance indicators (KPI) for the delivery of the work funded will be defined by the project manager of the eConnected Grainbelt in the funding scope of work requirements.

Progress reports allow you to demonstrate that you are achieving the agreed milestones, outputs and KPI’s, and spending funding according to your funding agreement.

Monthly/Quarterly reports are required throughout the granting period. These reports maybe verbal or written and will be confirmed by the eConnected Grainbelt project manager, and defined in the funding agreement;

Reporting templates will be made available to funding recipients, with notification sent before the due date of any report.

If you believe that your project may not be able to meet its milestones and outputs, discuss options with eConnected Grainbelt project manager as soon as possible.

Final report and audited financial statementAt the end of your project, you must submit paperwork to demonstrate that your project has been completed in line with the funding agreement and that the funding has been spent accountably.

A final report is required within three months of the end of your project. The reporting template will be sent to you when you notify us that your project has concluded.

An audited financial statement must be submitted with the final report. This should be prepared by a suitably qualified person who has not been directly involved in the project.

The audited financial statement must include evidence of all expenditure. Expenditure must be attributed to milestones. This should include expenditure of funding by third parties.

oneDAFWA Page of

Acknowledging DAFWA, the Department of Regional Development and Royalties for RegionsDAFWA, the state government Royalties for Regions program and the Department of Regional Development (DRD) must be acknowledged on all material and at all announcements relating to the project including newsletters, media statements, presentations, speeches, milestone celebrations, publications and correspondence.

Authorised and appropriate use of DAFWA, DRD and the Royalties for Regions logo on all promotional material including signage, banners, plaques, websites and advertising.

Actively provide opportunities to promote the funded project and the Royalties for Regions program including official launches, openings, stakeholder forums and project displays, in consultation with DAFWA and DRD.

Providing photographsPhotographs provide evidence of the benefits of your project over time and help to promote your activities and the eConnected Grainbelt project as a whole.

We encourage sending photos with your progress reports. Images may be used on the website to promote your project, in annual reporting

and in publicity materials. It will be assumed that you have sought the permission of anyone pictured in your

photos (particularly people under the age of 18) and we will not seek further permission before using the images.

oneDAFWA Page of

APPENDIX 1 – EXAMPLE DAFWA PestFax MAP APIs

APPENDIX 1 – EXAMPLE DAFWA PestFax Map APIs The brief specifications below describe the various APIs that will be available to implement the proposed solution. More APIs may be required and/or may require changes.

Users can currently make an on-line report of an occurrence of pests on https://www.agric.wa.gov.au/diseases/pestfax-map (click “Make an on-line report”).

The proposed APIs will allow similar functionality to be developed by third parties and post observations to the central PestFax database so that all observations can be shared.

API EndpointsDisorder Hosts

Summary

Get the list of disorders and the associated hosts

EndpointResponse Format(s)

HTTP Method Authentication

[domain]/v1/pestfaxmap/disorderhosts.[format] JSON, XML GET API Key

Input Parameters

Name Type Description

disorderId Number Disorder id to filter or leave blank for all

Output Parameters


disorder Object disorder Item for each record

disorder_id Number Unique disorder identifier

disorder_name String Disorder name

disorder_taxon_id Number Associated taxon id for future use of organisms web services

hosts Array Array of the associated hosts for the disorder

disorder_host_id Number Identifier of the disorders host

host_id Number Host unique identifier

host_name String Host name

Response example(s)

JSON

oneDAFWA Page of

https://www.agric.wa.gov.au/diseases/pestfax-map


{ "result": [ { "disorder": { "disorder_id": 120, "disorder_name": "ARGT/Twist fungus", "disorder_taxon_id": null, "hosts": [ { "disorder_host_id": 8, "host_id": 5, "host_name": "Pasture" }, { "disorder_host_id": 453, "host_id": 21, "host_name": "Weeds" }, { "disorder_host_id": 902, "host_id": 11, "host_name": "Weeds (grasses)" }, { "disorder_host_id": 172, "host_id": 18, "host_name": "[none/unknown]" } ] } }, . . . ]}

XML

<response> <result> <item> <disorder> <disorder_id>120</disorder_id> <disorder_name>ARGT/Twist fungus</disorder_name> <disorder_taxon_id/> <hosts> <item> <disorder_host_id>8</disorder_host_id> <host_id>5</host_id> <host_name>Pasture</host_name> </item> <item> <disorder_host_id>453</disorder_host_id> <host_id>21</host_id> <host_name>Weeds</host_name> </item> <item> <disorder_host_id>902</disorder_host_id> <host_id>11</host_id> <host_name>Weeds (grasses)</host_name> </item> </hosts> </disorder> </item> </result></response>

oneDAFWA Page of


Disorder Life stages

Summary

Get the list of disorders and the associated life stages



[domain]/v1/pestfaxmap/disorderlifestages.[format] JSON, XML GET API Key

Input Parameters


disorderId Number Disorder identifier filter or leave blank for all records

Output Parameters


disorder Object disorder Item for each record

disorder_id Number Unique disorder identifier

disorder_name String Disorder name

disorder_taxon_id Number Associated taxon id for future use of organisms web services

life_stages Array Array of the associated life stage for the disorder

disorder_life_stage_id Number Identifier of the disorders life stage

life_stage String Description of the life stage

Response example(s)

JSON

{ "result": [ { "disorder": { "disorder_id": 120, "disorder_name": "ARGT/Twist fungus", "disorder_taxon_id": null, "life_stages": [ { "disorder_life_stage_id": 62, "life_stage": "Eggs" }, { "disorder_life_stage_id": 63, "life_stage": "Larvae / Juvenile" }, ] }, . . . ]}

oneDAFWA Page of


XML

<response> <result> <item> <disorder> <disorder_id>120</disorder_id> <disorder_name>ARGT/Twist fungus</disorder_name> <disorder_taxon_id/> <life_stages>

<item> <disorder_life_stage_id>62</disorder_life_stage_id> <life_stage>Eggs</life_stage></item><item> <disorder_life_stage_id>63</disorder_life_stage_id> <life_stage>Larvae / Juvenile</life_stage></item>

</life_stages> </disorder> </item> </result></response>

oneDAFWA Page of


Host Growth stages

Summary

Get the list of hosts and associated growth stages



[domain]/v1/pestfaxmap/hostgrowthstages.[format] JSON, XML GET API Key

Input Parameters


hostId Number Host identifier filter or leave blank for all records

Output Parameters


host Object host Item for each record

host_id Number Unique host identifier

host_name String host name

growth_stages Array Array of the associated growth stage for the host

growth_stage_id Number Identifier of the hosts growth stage

growth_stage String Description of the growth stage

Response example(s)

JSON

{ "result": [ { "host": { "host_id": 1, "host_name": "Wheat", "growth_stages": [ { "growth_stage_id": 1, "life_stage": "Pre-sowing" }, { "growth_stage_id": 2, "life_stage": "Germination (GS0.0 – 0.9)" }, ] }, . . . ]}

XML

oneDAFWA Page of


<response> <result> <item> <host> <host_id>120</host_id> <host_name>ARGT/Twist fungus</host_name> <growth_stages>

<item> <growth_stage_id>1</growth_stage_id> <growth_stage>Pre-Sowing</growth_stage></item><item> <growth_stage_id>2</growth_stage_id> <growth_stage>Germination (GS0.0 – 0.9)</growth_stage></item>

</growth_stages> </host> </item> </result></response>

oneDAFWA Page of


Host Varieties

Summary

Varieties for hosts



[domain]/v1/pestfaxmap/hostvarieties.[format] JSON, XML GET API Key

Input Parameters


hostId String Unique identifier for a host leave blank for all hosts

Output Parameters


variety Object host variety item

variety_id String Unique identifier for the variety

host_id String Unique identifier for a host

variety String Description of the variety

oneDAFWA Page of


Response example(s)

JSON

{ "result": [ "variety": { "variety_id": "101", "host_id": "1", "variety": "Clearfield" }, "variety": { "variety_id": "656", "host_id": "3", "variety": "Bass" }, . . . ]}

XML

<response> <result> <variety> <item> <variety_id>101</variety_id> <host_id>1</host_id> <variety>Clearfield</variety> </item> </variety> <variety> <item> <variety_id>656</variety_id> <host_id>3</host_id> <variety>Bass</variety> </item> </variety> </result></response>

oneDAFWA Page of


PestFax Occurence

Summary

Upload a PestFax occurrence to the main database



[domain]/v1/pestfaxmap/pestfaxoccurence.[format] JSON, XML POST API Key

Input Parameters


occurrence_date Date Occurrence date in the format yyyy-mm-dd

disorder_host_id Number Host identifier : see disorder hosts

latitude Decimal Latitude of occurrence

longitude Decimal Longitude of occurrence

host_growth_stage String Note: String value of growth stage posted to the service

disorder_life_stage String Note: String value of life stage posted to service

Output Parameters


occurrence_id Number Identifier for the reported occurrence

oneDAFWA Page of


Response example(s)

JSON

{ "result": { "occurrence_id": 101 }}

XML

<response> <result> <occurrence_id>101</occurrence_id> </result></response>

oneDAFWA Page of


Upload Photograph

Summary

Allows an image to be uploaded in BASE64 format and attached to occurrence.



/v1/pestfaxmap/uploadphoto.json JSON, XML POST API Key

Input Parameters


occurenceId Number Identification of the occurrence that the image should be associated

imageData String BASE64 Image data

Output Parameters


occurrence_Id Number Unique identifier for the occurrence that the image has been attached associated with.

Image_id String Unique Identifier for the image that’s been uploaded

Response example(s)

JSON

{ "result": { "occurrence_id": 1, "image_id": 1 }}

XML

<response> <result> <occurrence_id>1</occurrence_id> <image_id>1</image_id> </result></response>

oneDAFWA Page of

oneDAFWA 31 July 2016 - Agriculture and Food Web viewAPPENDIX 1 – EXAMPLE DAFWA PestFax MAP...

Documents

Transcript of oneDAFWA 31 July 2016 - Agriculture and Food Web viewAPPENDIX 1 – EXAMPLE DAFWA PestFax MAP...