Franchise Code: This is the prime key to the table, which consists of a combination of the three-digit franchise code.
Model Code: Up to 10-digit alpha numeric code for the specific model.
Warning: Extreme caution should be exercised with regard to the deletion of model codes that have been on file for any measurable length of time due to the possible ramifications of deleting one from the master table which has already been attributed to other records elsewhere, such as in CRM or vehicle records.
The Details tab contains the following data:
Description: The description of the model, including the franchise name (if required), which will then be displayed when searching for model codes, and can also be printed and/or displayed in any user defined reports or enquiries set up via report generator or the ad-hoc enquiries facility.
Current model: This is a check box, which is either set to a tick for yes, or un tick for No. The check box should be set according to whether the vehicle is currently in production or on sale as a new model. Again this can be used as a test in various reports or enquiries to display either only current models, or only display old models.
Model Launch Date: A date can be entered here to mark the launch of a new model. The model will be available to sell from this date.
The David Henley facility is for the UK only. It is a Franchise Data method.
Our Of Production: A date can be entered here to mark, the out of production of a model.
Chassis prefix: If the chassis numbers of all vehicles within this model group all commence with certain consistent digits, then those digits can be entered here. If any value is entered here, then all vehicle records maintained in either Vehicle Administration or CRM with this model code will have to contain this value at the start of their chassis numbers. The chassis prefix can be held either here at the model level if all variants are allocated the same chassis prefix, or it can be held at a variant level, if there are different chassis prefixes for different variants within the same model range. If no code is found on the variant record, then the CRM Vehicle record maintenance program will look at this field on the Model record.
Manufacturer's code: If the model code being used as a key to this table is not the same as the manufacturer's identification code, then the manufacturer's code can be held here, and subsequently retrieved for any manufacturer required information or communication. This code is up to 20 characters long whereas the model code key to the table is only 10 digits.
Lead time: This information is text only and can be used again in reports and enquiries, or in the format of a vehicle quotation if required, to advise on the normal delivery time-scale for a vehicle not in stock, for example 6 weeks or 2 months.
Service model group: This code is used in the Service Point-of-Sale system to determine the correct allowed time for a specific operation. It can be held as a cross-reference either at the model level if all variants are allocated the same Service model group, or it can be cross-referenced at a variant level. If there are different times for the same operation within the same model range. If no code is found on the variant record, then the CRM Vehicle record maintenance program will look at this field on the Model record.
MS Company Number: This is a two letter code identifying the name of the company.
Model analysis code: This code is used to provide broad model analysis regardless of specific model code. In a multi-franchise environment it can be used to group all compact vehicles, as opposed to small saloons, medium saloons, executive saloons, sports, etc. Even in a single franchise environment it can provide continuity across model changes such as Vauxhall Nova being replaced by Vauxhall Corsa, or Ford Sierra being replaced by Ford Mondeo, etc. In that way, using the model analysis code, vehicle park and sales analysis data across different specific model life-times is possible.
Note: The search facility can be used by clicking the
button.
Additional dealer costs: This field is no longer used. It should be left with a value of zero.
Margin %: If the discount applied by the manufacturer off the retail price, to calculate the dealer cost, is different to the standard margin for the whole franchise, then it can be held at model level where it varies from the franchise standard. If it is consistent with the franchise standard, this field can be left as zero, as the franchise standard value (see' Franchise codes - Margin %') will be applied where the model value is equal to zero. It is also possible to set the specific amount of discount which the dealer receives for a particular vehicle at the variant level (see ' Variant codes - Margin).
Option Margin %: This represents the dealer option margin or discount off. Again this is exclusively to vehicles.
VS posting code: Used to facilitate a new Posting table mechanism within Autoline - VSB.
Finance group code: In 'Finance schemes', a particular type of finance can have a finance group code applied to it. In this way, particular finance schemes can be applied, either to all vehicles, vehicles of a particular franchise, or if necessary, one or more particular models. The way that this is achieved is by storing a finance group code against each model which relates to the finance group code of the schemes that can be applied to the model. Normally it would be a single alpha-numeric character which equates to the finance group of a scheme either already held on file, or which will be set up in the future. If no finance schemes apply to a given model then this field can be left blank.
Default finance code: This parameter is used in conjunction with the finance group code to specify the preferred finance scheme for this particular model of vehicle. It will relate to a finance scheme either already held on file, or which will be set up in the future, and this will be the first finance scheme displayed in a list, as part of the CRM vehicle quotations procedure. If no one scheme is preferential to any other then this parameter can be left blank.
Sequence Number:This allows the users to sequence the way the Model code is shown in the search listing.
The Service\Warranty tab contains the following data:
Manufacturer warranty (months): This field holds the default period of manufacturer's warranty for this model. The warranty expiry date for all CRM Vehicle records created with this model code will be based on the date first registered plus this number of months.
Mileage: This field holds the default mileage warranty for this model.
Manufacturer body warranty (months): This field holds the default period of manufacturer's body warranty for this model. The body warranty expiry date for all CRM Vehicle records created with this model code will be based on the date first registered plus this number of months.
Mileage: This field holds the default mileage body warranty for this model.
Warranty group: This field hold the default warranty group.
Maker code: This field holds the maker code of this vehicle.
1st Service at (months): This field holds the default 1st service interval in months and allows users to enter the services required in months, thereafter which will be allocated to all CRM Vehicle records created with this model code.
1st Service at (Miles): This field holds the default 1st service interval in miles or kilometers and allows users to enter the services required in miles, thereafter, which will be allocated to all CRM Vehicle records created with this model code.
1st MOT at (months): This field holds the default period before the first MOT test will be due for this model. The MOT renewal date for all CRM Vehicle records created with this model code will be based on the date first registered plus this number of months. This field can also be maintained at a model variant level. If no value is found at the variant record level, then the CRM Vehicle record maintenance program will look at this field on the Model record.
Timing belt Mileage: This field holds the default timing belt intervals in miles or kilometers which will be allocated to all CRM Vehicle records created with this model code.
Timing belt months: This field holds the default timing belt interval in months which will be allocated to all CRM Vehicle records created with this model code.
This allows the users to define between models and variants. For example: The sub-model code could be MPV, you would then attach this sub-model to the variant(s) applicable. When creating a VSB record, and after selecting the model and sub-model this would show variants attached to this sub-model.
The fields within this tab are as follows:
Code: Up to a 10 digit alpha / numeric code can be entered here, to define the sub-model
Description: This allows you to enter a more defined description of the submodel.
Used: This defines whether is currently being used or not.
Add Group: Allows users to add a sub-model, complete the code and descriptions fields to create the sub-model required.
Edit Group: Allows users to edit any sub-model duly created.
Delete Group: Allows users to delete any sub-models created.
Rebuild: Will re-create the sub-models listing from DD.varia and will remove any un-used entries from the list.
This allows you to write any notes about the model.
The Fleet Details tab contains the following data:
Manufacturer bonus table: This field shows details of the Manufacturer bonus table, if any.
Years of manufacture: This field shows details of the Years the model was manufactured, and may be especially useful if the model is no longer made.
The Model Picture tab contains the following data:
Show picture: This check box is ticked to show a picture of the model, if one exists. Leave the check box unset, if no picture is required.
Buttons:
Create: Create a new model record.
Amend/Delete: Amend/Delete an existing Model.
Tip:The search facility is activated by clicking the