Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

eCROP data exchange

back to

Linktoparent

Submitted dateLast Update DateVersionApproval Project Proposal StatusProject Page
Date Picker
defaultClick to set the submissions date
idsubmitted_date
requiredtrue
2013-10-01
Date Picker
defaultClick to set the latest update date
idlatest_updated_date
2015-07-17 
Text Field
defaultClick to set the version number
idversion_number
requiredtrue
0.31
SP Page Status
dateNov 26, 2015 11:55
hidetrue
width25%
userGianguglielmo
statusofficial

eCROP data exchange

 

 

Project Purpose

Text Area
default<click here to edit>
idproject_purpose
The purpose of the project is to create Business Process Models and Business Class Diagrams for documenting the business scenarios and business transactions involved in the electronic exchange of the data involved in the process of cultivation of crops (arable farming and horticulture) and the electronic exchange of crop cultivation data along the supply chain.
The process is described by several use cases:
- To send a request and the report about plant production such as the cropping schema , crop advice services, field operations and crop and soil monitoring data (nearby and remote sensing) between one or more partners
- To send the request and the report of crop cultivation data between one or more partners.

The output will be used to obtain and validate the XML messages to support the business process.

Project Scope

Text Area
default<click here to edit>
idproject_scope
The objective of this project is to standardize the Business Processes, the Business Transactions and the Information Entities of the electronic exchange of the crop cultivation data along the supply chain.
This project will describe the business processes for the electronic exchange of
- data involved in the process of plant production farming, between farmer and his suppliers, service providers, the customers and competent authorities, vise versa, and
- the crop cultivation data along the supply chain.
The project focuses on horticulture, fresh fruits, vegetables and arable farming crops.
The supply chain consist in parties involved from retail until the grower including cooperatives and producer organization, auctions, packers and traders,
The data involved in the plant production process messages contains
- Information about the crop fields, the planned and or actual cropping schema, treatment, plant health, soil and water situation, crop monitoring data, supplies (seed, fertilizer, plant protection), operation advices and operation instructions and the logging report about operations.
The information is used by the farmer and his partners to insure sustainable farming , food quality and food safety.
The crop cultivation message contains
- Information about the production of the crop (Information about treatment (pesticides, fertilizers, use of energy and water)
- Information about labor (organizing of the labor in the companies in the supply chain level)
- Information about certificates
The information is used by a partner in the supply chain to insure food quality and food safety.

Project Deliverables

Text Area
default<click here to edit>
idproject_deliverables
The project deliverables include:
a. A Business Requirements Specification (BRS) document containing Business Process Models covering electronic business processes
b. A Requirements Specification Mapping (RSM) document describing the message structures (as class diagrams) for the business transactions
c. XML Schemas to implement the message structures for the business transactions

Exit Criteria

Text Area
default<click here to edit>
idexit_criteria
The exit criteria that will indicate the deliverable has been completed, are specified in the table below.
a. A Business Requirements Specification (BRS) document containing Business Process Models covering electronic business processes
- Completed BRS.
- Public review and logs showing how comments have been addressed.
b. A Requirements Specification Mapping (RSM) document describing the message structures (as class diagrams) for the business transactions
- Completed RSM.
- Public review and logs showing how comments have been addressed.
c. XML Schemas to implement the message structures for the business transactions
- Completed XML Schemas.
- Public review and logs showing how comments have been addressed.

Project Team Membership and Required Functional Expertise

Text Area
default<click here to edit>
idproject_membership
Membership is open to experts with broad knowledge in the area of plant production and crop management within all countries, UN/CEFACT projects and the functions of UN/CEFACT, and its groups. In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct.

Initially the project team is composed of:
- Henk ZWINKELS
- Johan DEN ENGELSE
- Frans VAN DIEPEN
- Giorgos GEORGIANNAKIS

Head of Delegation Support

Text Area
default<click here to edit>
idhead_of_delegation
Heads of delegation of Austria, The Netherlands and US supporting this project.

Geographical Focus

Text Area
default<click here to edit>
idgeographical_focus
The geographical focus covers the globe, initial contribution is expected from European Union Member States and all countries interested.

Initial Contributions

Text Area
default<click here to edit>
idinitial_contributions
The following contributions are submitted as part of this proposal. It is understood that these contributions are only for consideration by the project team and that other participants may submit additional contributions in order to ensure that as much information as possible is obtained from those with expertise and a material interest in the project.

- Crop Data Sheet ( eDAPLOS) – CCL08B
- eLabs – CCL 12B
- eCert.- CCL8A
- Rapid Alert System for Feed and Food ( RASFF) - CCL13B
- The Crop Reference Model ( AgroConnect and Wageningen University, the Netherlands)

Resource Requirements

Text Area
default<click here to edit>
idresource_requirements
Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE secretariat.

Project Leadership

Text Area
default<click here to edit>
idproject_leadership
Project Leader: Henk ZWINKELS
Editors and other persons (to be decided) : Frans Van DIEPEN

Milestones

 

DELIVERABLE NAME

Project

Inception

Expected Completion Date

Requirements

Gathering

Expected Completion Date

Draft

Development

Expected Completion Date

Public

Review

Expected Completion Date

Project

Exit

Expected Completion Date

Publication

Expected Completion Date

Maintenance

Expected Completion Date

Text Field
default<click here to edit>
iddeliverable_name1
Business Requirements Specification
Select2
defaultSELECT
idyesno_odp1
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp1
2015-07-22
Select2
defaultSELECT
idyesno_odp2
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp2
2015-09 30 
Select2
defaultSELECT
idyesno_odp3
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp3
2015-12-31 
Select2
defaultSELECT
idyesno_odp4
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp4
2016-03-31 
Select2
defaultSELECT
idyesno_odp5
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp5
2017-12-21 
Select2
defaultSELECT
idyesno_odp6
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp6
2016-05-31 
Select2
defaultSELECT
idyesno_odp7
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp7
2016-06-30 
Text Field
default<click here to edit>
iddeliverable_name2
Requirements Specification Mapping
Select2
defaultSELECT
idyesno_odp11
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp11
2015-07-22 
Select2
defaultSELECT
idyesno_odp22
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp22
2016-02-28 
Select2
defaultSELECT
idyesno_odp33
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp33
2016-02-28 
Select2
defaultSELECT
idyesno_odp44
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp44
2016-05-31 
Select2
defaultSELECT
idyesno_odp55
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp55
2017-12-21 
Select2
defaultSELECT
idyesno_odp66
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp66
2016-06-30 
Select2
defaultSELECT
idyesno_odp77
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp77
2016-07-31 
Text Field
default<click here to edit>
iddeliverable_name3
XML Schemas
Select2
defaultSELECT
idyesno_odp111
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp111
2015-07-22 
Select2
defaultSELECT
idyesno_odp222
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp222
2016-08-31 
Select2
defaultSELECT
idyesno_odp333
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp333
2016-08-31 
Select2
defaultSELECT
idyesno_odp444
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp444
2016-09-30 
Select2
defaultSELECT
idyesno_odp555
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp555
2017-12-21 
Select2
defaultSELECT
idyesno_odp666
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp666
2016-12-31 
Select2
defaultSELECT
idyesno_odp777
selectedYES
  • YES
  • NO
Date Picker
defaultNO DATE SELECTED
idexpdate_odp777
2017-03-31 

Project Proposal Files

Attachments
oldfalse