Produce Industry IT Standards Association

Produce Industry IT Standards Association

Master Data Structures for Pest Status Codes and Defect Codes

Document

Co Authors:John Bartley – Turners and Growers

Brendan O’Reilly (CSEL)

Created on 9/20/2004 4:53 PMPage: 1 of 6

Produce Industry IT Standards Association

Version Management

Version / Date / Owner / Description
0.1 / 27/08/2004 / J Bartley / Original draft sent to PNZ
0.2 / 16/09/2004 / J Bartley / Update to allow for Groups and Categories
0.3 / 8/10/04 / J Bartley / Revised for Certification Model and XML
1.0 / 17/11/04 / J Bartley / Final – Remove Declaration from Country Code

Table of Contents

1.1Preface

1.2General Concept

1.3Pest Status Codes by Country

General Concept

Data File Structure File

UN Country Codes – Example

Business Rules:

1.4Defect Matrix

Data File Structure Diagram

Business Rules:

1.5Data Model

1.6File Creation Timing and Transfer

File Creation Timing

File Transfer

1.7Data Security

1.1Preface

This document sets out to define the Master Data document structure specifications required to manage the new Pest Status Code and Reject Data collection requirements for 2005.This specification has been designed to support a comprehensive list of ‘Market Requirements’ that may berequired in the future. T

This Master Data will be incorporated into other Master Data from various sources to form a Master Data Set. This Set will be made available through PIITSA to any Pipfruit related industries that should require that data.

1.2General Concept

The general concept is that there is two new files:

  1. A standard master data text file for UN Country Codes that includes which countries require Phyto’s and permits
  1. A new XML file createdand maintained on the PIITSA Master Data site. This data will be subsequently published for industry usage by PIITSA registered Master Data Users. The usage will include any system used in the pipfruit supply chain that may require this data.

This file is made up of three key components:

  • Market Requirements: Defines the Market or Market Group
  • Defect Groups: Which is a mechanisms by which defects or pest can be categorised
  • Defects: Details the specific defects / pests and their scientific names.

These three groups are then related to each other with their associated thresholds for that Market Requirement.

It is envisaged that this file could be expanded in the future to tackle other Market specific requirements, e.g. Grade Standards, Production Programs (Euregap, IFP).

1.3Pest Status Codes by Country

General Concept

This file would detail the following information

  • UN Country Codes
  • Pest Status Codes (* = wild card)
  • Additional requirements for exporting

This file is used to define Pest Status requirement by country, this information could then be used to make decisions about which country product can go to or what is required to export product into specific countries.

Data File Structure File

Field Description / Type / Length / Mandatory / Optional / Comments
*Un Country Code / N / M / 001
*UN Country Short Description / A3 / M
Long Description / A50? / M
Pest Status Code Value / A20 / O / e.g. ****S, **[OA]**
Phytocert Required / A1 / Boolean / Y/N
Permit Required / A1 / Boolean / Y/N

UN Country Codes – Example

Numerical
code / Country or area name / ISO ALPHA-3 code
004 / Afghanistan / AFG
248 / Åland Islands / ALA
008 / Albania / ALB

Business Rules:

  • A Country can only have one record

1.4Defect Matrix

This file contains a list of defects that might be found in reject, grade and phyto inspections (including Pests). Phyto pests will be listed to a detailed level eg Leafroller - Green headed, but might also contain more summarised pests eg. Leafroller. The "unidentified" defect may take the fruit out of more markets than one of the specific variants. Defect groups define either Pest Groupings, e.g. Leafrollers or Grade Standard Defects, Spoilt / Cosmetic.

The last component of this file is the tolerance level for each Country or Market Group (Pest Status Code).

Thresholds could either be the "maximum number of a pest that is acceptable in a 600 fruit inspection sample" or the MPL (maximum pest levels).

Data File Structure Diagram

Business Rules:

  • A Requirement may have zero or many defect and zero or many groups.

1.5Data Model

The following diagram shows the relationship between the three main entities:

  • Requirement
  • Defect Group
  • Defect

All three tables are link to maintain a many to many relationship, e.g. a Requirement can have many Defects and a Defect may be for many Requirements.

The links define the Thresholds because it’s the association between either the Requirement and the Defect or the Requirement and the Group that determines the threshold.

1.6File Creation Timing and Transfer

File Creation Timing

As a minimum, these files need only be created when there is a change, be it an addition, a change to an existing record or a deletion. To simplify this process these files could be produced daily, say at midnight.

File Transfer

As a minimum these files could be E-mailed as attachments. The preferred standard utilized by PIITSA for Data transfer is FTP.

1.7Data Security

PIITSA accepts responsibility for the management of levels of Access to all Master Data under its control.

The data files provided by Pipfruit NZ will be passed directly by them to a single PIISTA approved Master Data Provider. That provider then does what is required to amalgamate data into a suitable Set for promulgation to the general Pipfruit industry.

Created on 9/20/2004 4:53 PMPage: 1 of 6