| Key | Value |
|---|---|
| Table | DS06 Resources |
| Severity | MAJOR |
| Unique ID | 1060261 |
| Summary | Is this FC resource missing among the BL resources? |
| Error message | Combo of task_ID, resource_ID, role_ID, & EOC (where schedule_type = FC) not found in DS06 (where schedule_type = BL). |
This DIQ check identifies forecast resource assignments that were not in the original baseline, flagging new resources or potential baseline data quality issues.
The check compares these four fields between forecast and baseline:
When this combination exists in forecast but not baseline, it indicates:
Some new resources are expected as projects evolve. However, if many resources are flagged, it may indicate:
To address: Review the volume of new resources. Some additions are normal for scope changes and replanning. Excessive additions suggest reviewing whether your baseline was properly resource-loaded initially.
This test serves as a data quality indicator while also tracking legitimate resource additions since baseline.
Why this check matters:
Expected vs. problematic patterns:
Common causes of excessive new resources:
As a MAJOR check, this helps identify both legitimate project growth and potential data quality issues. While some resource additions are inevitable, excessive additions often reveal problems with how the baseline was originally developed or maintained.
CREATE FUNCTION [dbo].[fnDIQ_DS06_Res_IsFCResourceMissingInBL] (
@upload_id int = 0
)
RETURNS TABLE
AS RETURN
(
with BLRes 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 = 'BL'
)
SELECT
FCR.*
FROM
DS06_schedule_resources FCR LEFT OUTER JOIN BLRes ON FCR.task_ID = BLRes.task_ID
AND TRIM(ISNULL(FCR.resource_ID,'')) = BLRes.ResID
AND TRIM(ISNULL(FCR.role_ID,'')) = BLRes.RoleID
AND FCR.EOC = BLRes.EOC
WHERE
upload_id = @upload_ID
AND schedule_type = 'FC'
AND BLRes.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. |