Open knelson-farmbeltnorth opened 1 year ago
Initial discussion in 11 Jan 2023 meeting. Several objections to removing guidance since this is data that some FMIS systems are maintaining today.
I agree with keeping the guidance information as we have it now.
As for the others: I suspect there is value in keeping the "device" Model and Series to help in defining the identity of the "device", in the same way we use Manufacturer and Brand. We will need some kind of simplified configuration object for the "device" that would allow us to express things like a fixed GPS location, association with a Field, or association with other "devices".
Agreement in 1 Feb 2023 meeting to remove all above except Guidance, Device Model & Device Series.
Proposal #74 led to a re-examination of the role of ADAPT in reporting machinery-specific data. At a high level, the team has agreed to step away from wrapping ISO11783-10 functionality (data from the point of view of the machinery) inside ADAPT. Instead, machinery data within ADAPT should be limited to identifying separate high level machines and limited configuration data (see #77).
As a result, the following components within ADAPT are candidates for removal:
Device Objects Device Model Device Element Device Series Device Element Use (data variables are listed on the Asset Configuration, totals on the Field Operation) Device Element Configuration Machine Configuration Implement Configuration Section Configuration GPS Receiver Offsets Reference Point Offsets
Equipment Connection Data Hitch Point Connection Equipment Configuration Equipment Configuration Group (connected Assets are grouped by Work Record Data)
Prescription Data Data Log Triggers (any implementation would move to ISOv4Plugin)
Guidance Data All
Irrigation Configuration Data Endgun Configuration Endgun Table Endgun Table Entry IrrSectionConfiguration IrrSystemConfiguration (We intend to integrate Irrigation into Field Operations in a future release)