In CCS, you can set a limit on the duration for which a collection-evaluation-reporting (CER) job runs. For a typical CER job, the major part of the duration is consumed by the collection activity. Therefore very often a CER job times out while the collection activity is still in progress. In such a case, the data collected from assets on which the data collection was complete, is not used for evaluation and report generation and the CER job is run again on the complete set of scoped assets.
Apply the Quick Fix (QF) 10508 to resolve this issue. Now CCS has added another parameter in the existing CER job called Limit Collection Duration. Using this feature you can achieve the following:
Set a limit on the duration of the collection activity of a CER job
Use data collected on assets before the CER job is timed out for evaluation and report generation.
For a CER job that is timed out, the Messages tab provides details of the assets and the duration for which data was being collected for those assets. This information can be used while scheduling CER jobs in future.
The Limit Collection Duration parameter can be used with the existing parameters to achieve the following:
Avoid duplicate data collection by using already collected data. You can specify a parameter to collect data for assets only if it is not collected for ‘X’ days.
Ensure that the latest data is used for evaluation by setting the Use Latest Data for Evaluation parameter.