eCROP data exchange
back to
Submitted date | Last Update Date | Version | Project Proposal Status | Project Page |
---|---|---|---|---|
2013-10-01 | 2015-07-17 | 0.31 |
Project 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
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
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 transactionsExit 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
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 GEORGIANNAKISHead of Delegation Support
Heads of delegation of Austria, The Netherlands and US supporting this project.Geographical Focus
The geographical focus covers the globe, initial contribution is expected from European Union Member States and all countries interested.Initial 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
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
Project Leader: Henk ZWINKELS Editors and other persons (to be decided) : Frans Van DIEPENMilestones
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 |
Business Requirements Specification | YES | 2015-07-22 | YES | 2015-09 30 | YES | 2015-12-31 | YES | 2016-03-31 | YES | 2017-12-21 | YES | 2016-05-31 | YES | 2016-06-30 |
Requirements Specification Mapping | YES | 2015-07-22 | YES | 2016-02-28 | YES | 2016-02-28 | YES | 2016-05-31 | YES | 2017-12-21 | YES | 2016-06-30 | YES | 2016-07-31 |
XML Schemas | YES | 2015-07-22 | YES | 2016-08-31 | YES | 2016-08-31 | YES | 2016-09-30 | YES | 2017-12-21 | YES | 2016-12-31 | YES | 2017-03-31 |
Project Proposal Files