Data Storage and Renditions

• Base Vehicle Name that will include Year, Make, and Model attributes
• Base Equipment Name that will include Manufacturer, Equipment Model, and Vehicle Type

The Data Normalization is performed based on the attributes and the attribute values defined in the imported file.

Year Range Expansion

If the application record with a specified "Year" (from and to) range is imported into the system, then the submitted application explodes to each year keeping all other information same across applications.

For example, consider the application Suzuki Aerio is uploaded with the year range "2002-2003". The system refers to the VCdb database and checks the part for the specified make, model, and year range. Based on the year, make, and model, each application record is exploded into multiple applications.

<?xml version="1.0" encoding="UTF-8"?>
<ACES version="3.2">
 <Header>
 </Header>
	<App action="A" id="1">
	 <Years from="2002" to="2003"/>
	 <Make id="1"/>
	 <Model id="1"/>
	 <!-- 2002 Suzuki Aerio -->
	 <Qty>1</Qty>
	 <PartType id="1005"/>
	 <!-- Windshield Wiper Blade -->
	 <MfrLabel>ICON</MfrLabel>
	 <Position id="1"/>
	 <!-- Front Right -->
	 <Part BrandAAIAID="BBHV">1878B3</Part>
	 <AssetName>IC_Hook1</AssetName>
	</App>
	<Footer>
	 <RecordCount>1</RecordCount>
	</Footer>
</ACES>

Region and Sub-Model Expansion

If the application record with "Base Vehicle ID" is imported into the system, then the submitted application record explodes multiple applications based on the id, region, and submodel keeping all other information same across applications.

The system refers to VCdb database and checks the part for the base vehicle id 118567. For the specified vehicle id, the system checks for the combination of region and submodel. For respective submodel and region combinations, the individual application record is exploded into multiple application records accordingly.

<?xml version="1.0" encoding="UTF-8"?>
<ACES version="3.2">
	<Header>
		<Company>Bosch</Company>
		<SenderName>Jonathan Motley</SenderName>
		<SenderPhone>708 865 5326</SenderPhone>
		<TransferDate>2018-04-18</TransferDate>
		<DocumentTitle>WIPER_BLADES_ICON</DocumentTitle>
		<DocFormNumber>WB_2018_04_01</DocFormNumber>
		<EffectiveDate>2018-04-01</EffectiveDate>
		<ApprovedFor>
			<Country>US</Country>
			<Country>CA</Country>
		</ApprovedFor>
		<SubmissionType>FULL</SubmissionType>
		<MapperEmail>jonathan.motley@us.bosch.com</MapperEmail>
		<VcdbVersionDate>2018-03-30</VcdbVersionDate>
		<QdbVersionDate>2018-03-30</QdbVersionDate>
		<PcdbVersionDate>2018-03-30</PcdbVersionDate>
	</Header>
		<App action="A" id="1">
		<BaseVehicle id="1"/>
		<!-- 2002 Suzuki Aerio -->
		<Qty>1</Qty>
		<PartType id="1005"/>
		<!-- Windshield Wiper Blade -->
		<MfrLabel>ICON</MfrLabel>
		<Position id="1"/>
		<!-- Front Right -->
		<Part BrandAAIAID="BBHC">1878B3</Part>
		<AssetName>IC_Hook1</AssetName>
	</App>
	<Footer>
		<RecordCount>1</RecordCount>
	</Footer>
</ACES>

For example, consider Base vehicle id = 1. The system checks the VCdb database for specified base vehicle id and gets the list of base vehicle IDs, submodels, and regions. For the Base Vehicle ID, regions, and submodels, the application records are exploded into multiple Apps accordingly.

List of Vehicle Ids for Base Vehicle – 1 and Sub Model - Base,

Application Compression

If the ACES XML file is imported with "Base Vehicle ID" into the system, then the submitted application record with vehicle attributes does not explode based on region, instead, an attribute Regions is populated with all the possible regions for that base vehicle.

For example, consider Base vehicle id = 1845. The system checks the VCdb database for specified base vehicle id and gets the list of base vehicle IDs, submodels, and regions. For the Base Vehicle Id, there are 4 sub-models and 2 regions in the VCdb database and the expansion is as follows:

• The system creates 1 Application Group for that vehicle and merges the region values to the attribute Regions (Multivalued Attribute) and 4 applications are created for each sub-model.

• Currently, the system combines the regions and only 1 Application Group is created after compression instead of 2 Application Groups, and 4 Applications are created instead of 8 Applications.