# Definite Scoring
{% hint style="info" %}
This is an older version of the document. To view the most recent version of the document, click [here](https://docs.opsmx.com/products/data-and-intelligence-module-autopilot/autopilot/scoring-algorithms/definite-scoring).
{% endhint %}
Definite scoring only considers the unexpected events in v2 and does not compare . These events may or may not be present in the baseline. Definite scoring is simple and easy to interpret. Definite scoring works based on the following factors:
* For every unexpected cluster that is in v2 and not in v1, the overall score is reduced.
* For all unexpected clusters present in both v1 and v2, overall score is reduced only when the number of logs of that cluster are higher in v2.
* There is no normalization, hence definite scoring may not work if the log file is too large.
* Score Reduction is higher at higher sensitivity levels.
* By default, definite scoring will give a score of 0 (fail) whenever there is a critical error.
Score Reduction is higher for clusters with higher criticality.
To set the Definite Scoring algorithm follow the steps below:
1. Click System Setup in the navigation menu as shown below:
**2.** The following screen appears:
**3.** Add/Edit an application. Click[ Add Application](https://docs.opsmx.com/application-management/add-application) and[ Edit Application](https://docs.opsmx.com/application-management/edit-application) to know more.
a. After entering the application details you need to add a service.
b. Enter the Service Name in the text box and click Save. Refer to the image below:
****
4\. Next, you get the option to select the type of service you want to add. The options are:
* Deployment Verification
* Visibility
* Release Management
Select Deployment Verification. The following options appear:
Click the + icon to add a log template.
5\. The create Template screen appears as shown below:
6\. Click Log Tags. Select Definite Scoring from the drop-down as shown below:
