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..1 ⇩
Season Id 0..1
Notes 0..1
Document Correlations 0..1
Time Scopes 0..1 ⇩
Version 0..1
Crop Ids 0..1
Estimated Area 0..1
Field Ids 0..1
Crop Zone Ids 0..1
Operations 1..1 ⇩
UML Class Model
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/version Version]]
}
class Id {
[[/docs/id details]]→
}
class ContextItems {
[[/docs/context-items details]]→
}
class Notes {
[[/docs/notes details]]→
}
class DocumentCorrelations {
[[/docs/document-correlations details]]→
}
class TimeScopes {
[[/docs/time-scopes details]]→
}
class CropIds {
[[/docs/crop-ids details]]→
}
class EstimatedArea {
[[/docs/estimated-area details]]→
}
class FieldIds {
[[/docs/field-ids details]]→
}
class CropZoneIds {
[[/docs/crop-zone-ids details]]→
}
class Operations {
[[/docs/operations details]]→
}
Plan o-d- "1...1" Id
Plan o-r- "0...1" ContextItems
Plan o-u- "0...1" Notes
Plan o-l- "0...1" DocumentCorrelations
Plan o-d- "0...1" TimeScopes
Plan o-u- "0...1" CropIds
Plan o-d- "0...1" EstimatedArea
Plan o-u- "0...1" FieldIds
Plan o-d- "0...1" CropZoneIds
Plan o-u- "1...1" Operations
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 1.0.0