Assignment Add IG - Vehicle Damage Assignment with Multiple Memos

Assignment Home / Assignment Use Case / Assignment Add IG

Implementation Guide - Multiple Memos on an Assignment

Assignment memo text is included in the original appraisal assignment received by Staff Appraiser1. Staff Appraiser1 adds additional assignment memo comments and reassigns the appraisal to Staff Appraiser2. The additional <AssignmentMemo> text is shown in reverse chronological order.

Data Dictionary Reference(s)

Assignment

Section 4 - Description of Assignment

Section 4.1 - Common Data Aggregates for Assignment

Section 4.2 - Assignment Add Request

Common Elements and Aggregates

Section 3 is the Elements and Aggregates that are common to the Collision Industry messages.

The hyperlinks in the Type Colum will help you navigate to the Aggregates and messages.

<ctrl> click on hyperlink will take you to the Aggregate

<alt> and back arrow will take you back to hyperlink

Data Dictionary Help

Section 2 describes the architecture behind the schemas. This includes definitions, data types, building blocks, naming conventions, and versioning.

Test Instance
AssignmentAdd Rq_VehicleDamageAssignment_With_Multiple_Assignment_Memo

Data Recommendations

Aggregate	Aggregate or Element	Usage
<RqUID>		Required
<DocumentInfo>		Required
	<BMSVer>	Required; must be populated with a value from the BMS Version Code List
	<DocumentType>	Required; must be populated with a value from the Document Type Code List
	<CreateDateTime>	Required
<EventInfo>		Required; all data is optional inside of <EventInfo>
<EventInfo> / <AssignmentEvent>		Recommended
	<CreateDateTime>	Recommended. The second <AssignmentEven> will not have this value because the date and time the assignment was created in the systems of origin has not changed.
	<SendDateTime>	Recommended
	<ReceivedDateTime>	Recommended
<AdminInfo>		Required; all data is optional inside <AdminInfo>; the following aggregates of <Estimator>, <Receiver> and <Sender> are recommended for this IG
<AdminInfo> / <Estimator>		Recommended; has required fields inside this aggregate that are not listed in this example. See Party
<AdiminInfo> / <Receiver>		Recommended; has required fields inside this aggregate that are not listed in this example. See Party
<AdminInfo> / <Sender>		Recommended; has required fields inside this aggregate that are not listed in this example. See Party
<ClaimInfo>		Required, all aggregates are optional inside of <ClaimInfo>. <ClaimInfo>, <OrderInfo> and/or <FleetInfo> is allowed.
<VehicleDamageAssignment>		Required; <VehicleDamageAssignment>, <RenentalAssignment>, <GlassAssignment>, <SubrogationAssignment>, <PropertyDamageAssignment>, <TowAssignment> can be used, but only one.
	<AssignmentMemo>	Recommended; repeating element represented in reverse chronological order. (Last memo appears first in group).
	<AdjusterMemo>	Recommended
<VehicleDamageAssignment> / <EstimatorIDs>		Recommended
	<CurrentEstimatorID>	Required or <RoutingIDInfo>
<VehicleDamageAssignment> / <EstimatorIDs> / <EstimatorHistory>		Recommended
	<EstimatorId>	Required or <FirstName> or <LastName>
	<DocumentVerCode>	Required; must be populated by a value from the Document Version Code List
	<DocumentVerNum>	Required
<VehicleDamageAssignment> / <VehicleInfo>		Required; all data inside <VehicleInfo> is optional

Master Code List

Code List are identified in the Type Column with Open Enum or Closed Enum in the Data Dictionary. For a list of all the codes, please use the Data Dictionary and the Master Code List.

Code List	Value	Description
BMS Version	6.4.0	Release Version
Document Type	A	Document Type for Vehicle Damage Assignment
Document Version Code	EM	Original Version