Hard Constraints - Constraints That Prevent Activities Being Moved Section of the Schedule Check Report Dialog BoxOverview Use this section to view activities with hard constraints. Hard constraints override logical relationships and thereby prevent activities from being scheduled according to the logic. Hard constraints should only be used when they reflect real dates. Examples of hard constraints are Mandatory Start and Mandatory Finish. If possible, replace hard constraints with logical relationships. Only a subset of all the activities in the open projects are checked. WBS summary activities, activities with an actual finish date, and Level of Effort activities are removed from the subset to create a list of activities that are checked for Hard Constraints. Start constraints are ignored if they are on activities that have an actual start. The Actual percentage is calculated as the number of activities found that match the check divided by the total number of subset activities checked. Screen Elements Project ID field The unique identifying code of the project containing the activity which failed the check. Activity ID field The unique identifying code of the activity which failed the check. Activity Description field The brief description of the listed activity. Constraint Type field The type of constraint that is preventing the activity from being moved. Hard constraint types include: Mandatory Start and Mandatory Finish. Soft constraint types include: Finish On, Finish On or After, Finish On or Before, Start On, Start On or After, and Start On or Before. Constraint Date field The date, if applicable, to which the activity must adhere. Position field The constraint position: primary or secondary. Getting Here
|
|