Opening Statement

asdasdd

General Problem

The broad adoption of precision agriculture (PA) is still limited by a lack of hardware/software systems interoperability.

The ADAPT project addressed this issue by creating a field operations common object model that satisfies data requirements contributed by a cross section of industry stakeholders.

The common object model meets requirements from AgGateway’s SPADE and PAIL projects, including compatibility with the ISO11783-10 standard (ISOXML) and participant companies’ own systems.

Current trends in sustainability, traceability, and compliance reporting demand an ever-increasing amount of data be gathered as part of everyday operations in modern production agriculture.

Specific requirements for what data is collected, how often, and in what format are constantly evolving and highly geo-political context dependent.

This makes fulfilling all the requirements for a common object model a moving target, unless it is possible to decouple the infrequently and frequently changing aspects.

The relatively static core components of the ADAPT framework are minimalist in nature, but contain placeholders for attaching Context Items (which are provided by a dynamic, data-driven system).

This same approach can be used to graft additional, sematically-rich data onto objects from other data models such as ISO 11783-10.

Specific Problem

Can include here the material about conflicting sets of requirements. The PPT can be found HERE. 

The need for the unified object model to simultaneously be

• simple and compact enough to be easily understood and used, but broad enough to not leave out something someone needs to conduct business (simple vs complete)
• generic enough to be accepted from an international perspective, but still be able to support the capture & communication of necessary region-specific data (generic vs specific)
• able to express data in a controlled vocabulary (so everyone can understand what it means), but still allow that controlled vocabulary to be continually changing to match the nature of data requirements (static vs dynamic)

Internationalization is important for this work, but conflicting requirements must be reconciled:

ADM developers must seek universality, staying free of regionally specific clutter. However, different geographies’ business processes involve context specific data (e.g., USA EPA product numbers.) If this data not accommodated, the ADM’s relevance suffers.

Additionally, it is desirable to use a controlled vocabulary. However, the dynamic nature of business and regulation requires this vocabulary to be easily extensible. If this controlled vocabulary is allowed to become "stale", again, the ADM’s relevance suffers.

General Goal (of the paper)

Demonstrate the proposed Context Item system as a method for satisfying these conflicting requirements.

Specific Objectives (of the paper)

asdasd

Section Breakout

 asdasdd