Plan

Document collecting operational intent for a growing season. A plan may define a collection of intended Crop Zones, defining a crop for each field/partial field and may further define dates and intended operations (WorkItems). Alternatively, a Plan may simply define a number of acres of a given crop to be planted across the operation. Multiple mutually exclusive plans may exist for a single season to allow for runtime flexibility. A plan documents management intent.

Child Components

Id 1..1
Name 1..1
Description 0..1
Context Items 0..∞
Season Id 0..1
Note 0..∞
Document Correlations 0..∞
Time Scopes 0..∞
Version 0..1
Crop Id 0..∞
Estimated Area 0..1
Field Id 0..∞
Crop Zone Id 0..∞
Operations 1..∞

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml Plan

class Plan {
    String [[/docs/name Name]]
    String [[/docs/description Description]]
    String [[/docs/season-id SeasonId]]
    String [[/docs/note Note]]
    String [[/docs/version Version]]
    String [[/docs/crop-id CropId]]
    String [[/docs/field-id FieldId]]
    String [[/docs/crop-zone-id CropZoneId]]
}

class Id {
    [[/docs/id details]]→
}

class ContextItem {
    [[/docs/context-item details]]→
}

class DocumentCorrelation {
    [[/docs/document-correlation details]]→
}

class TimeScope {
    [[/docs/time-scope details]]→
}

class EstimatedArea {
    [[/docs/estimated-area details]]→
}

class Operation {
    [[/docs/operation details]]→
}

Plan o-d- "1...1" Id
Plan o-r- "0...∞" ContextItem
Plan o-u- "0...∞" DocumentCorrelation
Plan o-l- "0...∞" TimeScope
Plan o-d- "0...1" EstimatedArea
Plan o-u- "1...∞" Operation

hide circle
@enduml

Where Used

Following is a list of components that have Plan as a child component.

Feedback

AgGateway and its members welcome your feedback.

UUID: a5581f93e0254dabb0b0686e8b87575f

ADAPT Standard Version 2.0.0