Page Comparison

...

Use Case Type

Use Case Detail

ISO Implementation

ADAPT Type

ADAPT Implementation

CommentAllocation CAN

Single Comment from a list allocated at a specific point and time

Code Block

language	xml

<CAN A="CCT3" B="CCL13">
	<ASP A="2003-08-20T08:00:20" D="4">
		<PTN A="51.23456" B="13.23456" D="2"/>
	</ASP>
</CAN>

Single FreeCommentText allocated at a specific point and time

Code Block

language	xml

<CAN C="bad driving conditions">
	<ASP A="2003-08-20T08:00:20" D="4">
		<PTN A="51.23456" B="13.23456" D="2"/>
	</ASP>
</CAN>

Continuous Comments - Continuous comments are logged in a binary file at

a default rate of 1 hz. ASP.A = the timestamp when the logging

is started and ASP.B is the time-stamp when the logging is stopped.

Code Block

language	xml

 A continuous CodedComment is started:
<CAN A="CCT6" B="CCL38">
	<ASP A="2003-08-20T08:00:20" D="4">
	<!—- A = start of continuous comment allocation, comment is active -->
		<PTN A="51.23456" B="13.23456" D="2"/>
	<!—-position at the start of the continuous comment allocation -->
	</ASP>
</CAN>

and about 35 minutes later the same continuous CodedComment is stopped:

<CAN A="CCT6" B="CCL38">
	<ASP A="2003-08-20T08:00:20" B="2003-08-20T08:35:45" D="4">
	<!—-A = start of continuous comment allocation -->
	<!—- B = end of continuous comment allocation, comment is complete -->
		<PTN A="51.23456" B="13.23456" D="2"/>
		<!—-position at the start of the continuous comment allocation -->
	</ASP>
</CAN>

Single Comment allocated globally

DeviceAllocation- DAN

Planned device allocation - The planned device allocation is created by the FMIS

and may or may not completely specify the device. If the exact device is not known

at the time of planning it is common to only specify the device class. Guideline: ASP.A is the timestamp when the plan was created.

Code Block
<DAN B="70FE000000000000" A="200A000000000000"> <ASP A="2003-11-12T08:00:00" D="1" /> </DAN>

Effective device allocation - After the task is loaded in the MICS the planned device allocation is completed by identifying the actual device to be used. The TC modifies the original DAN.A and DAN.B to specify the actual device and may optionally define a point location of the event. The TC should also change ASP.D = "1" to ADP.D ="4" and also add ASP.B = timestamp when the allocation is discontinued. Guideline question: Should the TC modify the original planned DAN or create a new DAN? If the original is modified should ASP.A (planned) = ASP.A (effective)? NOTE: The 2015-1-14 FDIS states that a new DAN should be created.

		Lookup	Value
Self Conf	TRUE
Industry Group	2	2	Agriculture and Forestry Equipment
Device Class Instance	0
Device Class	5	5	Fertilizers
Reserved	0		Equipment for applying mineral and/or organic fertilizers
Function	128	128	Fertilizer Rate Control
Function Instance	0		Control of the rate of product placed on or in the soil
ECU Instance	0
Manufacturer Code	102	102	AGCO GmbH & Co. Marktoberdorf, Germany
Identity Number	1067011

....................................................................................................................................

Code Block
<DAN B="70FE000000000000" A="0348D00C00800AA0"> <ASP A="2003-11-12T08:00:00" A="2003-11-12T08:05:00"D="4" /> </DAN>

WorkerAllocation -WAN

Planned worker allocation - Indicates the worker(s) that are planned to execute the task. These may be in addition to the "Responsible Worker" referenced in the TSK. In planned allocations ASP.A = the timestamp when the plan was created.

...........................................................................

Code Block
<WAN A="WKR1"> <ASP A="2003-0820T08:00:00" D="1" /> </WAN>

Effective worker allocation - The actual worker(s) allocated to a task. ASP.A is the start time of the allocation and ASP.B is the end time of the allocation. Guideline - If ASP.B is null then it is assumed that end time is the task end time.

Code Block
<WAN A="WKR1"> <ASP A="2003-0820T08:00:00" B="2003-0820T08:06:00" D="4" /> </WAN>

ProductAllocation - PAN

Effective product allocation - Allocates a crop input product (single or mixture) to a application task and a specific device.

PAN.A: A product identifier.
PAN.B: The hexadecimal form of the DDI that describes how the product is applied.
PAN.C: Quantity value. In a transfer product allocation this indicates how much product is being transferred; otherwise not specified.
PAN.D: Transfer mode.
PAN.E: Device element involved in the product allocation.
PAN.F: Value presentation ID. THis specifies how the numbers involved are to be shown to a user.

PAN has child elements of time ASP (Allocation stamp)

ASP.A = timestamp at the start of the allocation and
ASP.B = timestamp at the end of the allocation. Guideline - If ASP.B is null then it is assumed that end time of the product allocation is the task end time.
ASP.D = Specifies what the time means; a value of 4 indicates "effective".

.......................................................................................................

Code Block
<PAN A="PDT2" B="004B"C="20000" E="DET3" F="VPN1"> <ASP A="2003-11-12T08:00:00" D="4"/> </PAN>

Effective product transfer allocation - A specified product is transferred from one vehicle to another. For example from a combine to a grain cart. The ASP element may also contain 1-2 geo-referenced points.If one point is included it is the location at the start of the event if two points are included the second is the location at the end of the event. Guideline - If two points are included the first ASP.A = the timestamp of the start of the transfer event and ASP.B = timestamp of the end of the transfer event.

.........................................................................................................

Code Block
<PAN A="PDT2" B="004B"C="20000" D="2" E="DET3" F="VPN1"> <ASP A="2003-11-12T08:00:00" D="4"> <PTN A="54.588945" B="9.989209" D="3"/> </ASP> </PAN>

...

Versions Compared

Old Version 29

New Version 30

Key