Which Indicator should be excluded from a Historic Data Collection because its scores cannot be accurately collected?

Indicators that measure the current state based on a relative time, such as 'Summed age of open problems,' cannot be collected accurately for past dates. A historical data collection job runs on the current date but collects data for a previous date. The age calculation uses the current date ('now') in its formula. Therefore, when the job runs, it will incorrectly calculate the age of a problem as of today, not as of the historical date being collected. This results in inaccurate historical scores.

A. 'Number of new requests' is based on the 'Created' date, which is a fixed timestamp and can be collected accurately for any past date.
B. 'Number of incidents resolved in time' is based on the 'Resolved' date, a fixed timestamp that allows for accurate historical collection.
D. This is based on the 'Updated' date. A historical job can accurately query for records not updated within 90 days relative to the collection date.

- ServiceNow Product Documentation, "Historical data collection." Performance Analytics and Reporting. The documentation warns, "Do not run historical collection on indicators that are based on relative dates, such as Age or 'Updated more than 30 days ago'."

- ServiceNow Performance Analytics (PA) Advanced Courseware, Module: "Data Quality and Historical Collection," Section: "Limitations of Historical Collection." This section explicitly uses "Age of Open Incidents" as a primary example of an indicator unsuitable for historical collection.