Skip to main content

Configuration Attribute Checks

Category weight: 1% of overall score
Checks in this category: 5

Configuration checks validate that activities use approved Primavera attribute settings as defined by your organization's standards. These checks are especially useful for organizations that mandate specific activity types, percent complete methods, or constraint policies.

Configure the allowed values for each attribute in Quality Settings.

Activity Type Configuration

FieldValue
Check IDconfig-activity-type
DCMA Reference
Default ThresholdPer Primavera allowed values
SeverityMajor

Validates that every activity uses one of the approved Activity Type values. Activities with non-standard types may indicate import errors or inconsistent scheduling practices.

What triggers a finding: An activity whose Activity Type is not in the configured list of allowed values.

Common approved types: Task Dependent, Resource Dependent, Level of Effort, Start Milestone, Finish Milestone, WBS Summary.


Percent Complete Type Configuration

FieldValue
Check IDconfig-percent-complete-type
DCMA Reference
Default ThresholdPer Primavera allowed values
SeverityMajor

Ensures activities follow the organization's approved percent complete methodology. Mixing percent complete types within a schedule can lead to inconsistent progress reporting.

What triggers a finding: An activity whose Percent Complete Type is not in the configured list of allowed values.

Common types: Physical, Duration, Units.


Duration Type Configuration

FieldValue
Check IDconfig-duration-type
DCMA Reference
Default ThresholdPer Primavera allowed values
SeverityMajor

Checks whether activities use only approved duration type settings. The duration type controls how P6 recalculates activity duration when resources are modified.

What triggers a finding: An activity whose Duration Type is not in the configured list of allowed values.

Common types: Fixed Duration & Units, Fixed Units/Time, Fixed Duration & Units/Time, Fixed Units.


Constraint Type Configuration

FieldValue
Check IDconfig-constraint-type
DCMA Reference
Default ThresholdPer Primavera allowed values
SeverityMajor

Flags activities whose primary constraint is not in the approved list. Organizations often restrict which constraint types are permitted to prevent planners from overriding CPM logic.

What triggers a finding: An activity whose Primary Constraint Type is not in the configured list of allowed constraint types.

Common approved constraints: As Soon As Possible (ASAP), Start Not Earlier Than (SNET), Finish Not Later Than (FNLT). Hard constraints (Mandatory Start, Mandatory Finish) are typically restricted.


Secondary Constraint Type Configuration

FieldValue
Check IDconfig-secondary-constraint-type
DCMA Reference
Default ThresholdPer Primavera allowed values
SeverityMinor

Ensures that secondary constraint usage follows the organization's allowed settings. Secondary constraints are less common but can still override CPM calculations when present.

What triggers a finding: An activity whose Secondary Constraint Type is not in the configured list of allowed values.


Next Steps