| Key | Value |
|---|---|
| Table | DS06 Resources |
| Severity | MAJOR |
| Unique ID | 1060260 |
| Summary | Is this BL resource missing among the FC resources? |
| Error message | Combo of task_ID, resource_ID, role_ID, & EOC (where schedule_type = BL) not found in DS06 (where schedule_type = FC). |
This DIQ check identifies baseline resource assignments that have been changed or removed in the forecast schedule, flagging potential data quality issues when changes are excessive.
The check compares these four fields between baseline and forecast:
When this exact combination doesn't exist in the forecast, it indicates:
Some resource changes are normal and expected as projects progress. However, if many resources are flagged, it may indicate:
To address: Review the volume of changes. A few changes are normal project evolution. Widespread changes suggest reviewing your resource loading process and ensuring forecast schedules are fully resource-loaded.
This test serves as a data quality indicator by measuring resource planning stability between baseline and forecast schedules.
Why this check matters:
Expected vs. problematic patterns:
Common data quality issues found:
As a MAJOR check, this helps identify when resource planning has degraded between baseline and forecast. While some change is inevitable, excessive change typically indicates process or data issues requiring correction.
CREATE FUNCTION [dbo].[fnDIQ_DS06_Res_IsBLResourceMissingInFC] (
@upload_id int = 0
)
RETURNS TABLE
AS RETURN
(
with FCRes as (
SELECT task_ID, TRIM(ISNULL(resource_ID,'')) ResID, TRIM(ISNULL(role_ID,'')) RoleID, EOC
FROM DS06_schedule_resources
WHERE upload_id = @upload_ID AND schedule_type = 'FC'
)
SELECT BLR.*
FROM DS06_schedule_resources BLR LEFT OUTER JOIN FCRes ON BLR.task_ID = FCRes.task_ID
AND TRIM(ISNULL(BLR.resource_ID,'')) = FCRes.ResID
AND TRIM(ISNULL(BLR.role_ID,'')) = FCRes.RoleID
AND BLR.EOC = FCRes.EOC
WHERE
upload_id = @upload_ID
AND schedule_type = 'BL'
AND FCRes.task_ID IS NULL
)
| Date | Description of Changes |
|---|---|
| 2024-04-30 | Logic adjusted to account for the addition of subproject_id field. |
| 2025-08-20 | 'subproject_ID' field no longer required. Removed from test. |