The CPM Procedure
- Overview
- Getting Started
-
Syntax
Functional Summary Dictionary of Options PROC CPM Statement ACTIVITY Statement ACTUAL Statement ALIGNDATE Statement ALIGNTYPE Statement BASELINE Statement CALID Statement DURATION Statement HEADNODE Statement HOLIDAY Statement ID Statement PROJECT Statement RESOURCE Statement SUCCESSOR Statement TAILNODE Statement -
Details
Scheduling Subject to Precedence Constraints Using the INTERVAL= Option Nonstandard Precedence Relationships Time-Constrained Scheduling Finish Milestones OUT= Schedule Data Set Multiple Calendars Baseline and Target Schedules Progress Updating Resource-Driven Durations and Resource Calendars Resource Usage and Allocation RESOURCEOUT= Usage Data Set RESOURCESCHED= Resource Schedule Data Set Multiproject Scheduling Macro Variable ORCPM Input Data Sets and Related Variables Missing Values in Input Data Sets FORMAT Specification Computer Resource Requirements
-
Examples
Activity-on-Node Representation Activity-on-Arc Representation Meeting Project Deadlines Displaying the Schedule on a Calendar Precedence Gantt Chart Changing Duration Units Controlling the Project Calendar Scheduling around Holidays CALEDATA and WORKDATA Data Sets Multiple Calendars Nonstandard Relationships Activity Time Constraints Progress Update and Target Schedules Summarizing Resource Utilization Resource Allocation Using Supplementary Resources INFEASDIAGNOSTIC Option and Aggregate Resource Type Variable Activity Delay Activity Splitting Alternate Resources PERT Assumptions and Calculations Scheduling Course - Teacher Combinations Multiproject Scheduling Resource-Driven Durations and Resource Calendars Resource-Driven Durations and Alternate Resources Multiple Alternate Resources Auxiliary Resources and Alternate Resources Use of the SETFINISHMILESTONE Option Negative Resource Requirements Auxiliary Resources and Negative Requirements Resource-Driven Durations and Negative Requirements Statement and Option Cross-Reference Tables
- References
| ALIGNTYPE Statement |
- ALIGNTYPE variable ;
- ALIGN variable ;
- ATYPE variable ;
The ALIGNTYPE statement is used to specify whether the date value in the ALIGNDATE statement is the earliest start date, the latest finish date, and so forth, for the activity in the observation. The values allowed for the variable specified in the ALIGNTYPE statement are specified in Table 4.2.
Value |
Type of Alignment |
SEQ |
Start equal to |
SGE |
Start greater than or equal to |
SLE |
Start less than or equal to |
FEQ |
Finish equal to |
FGE |
Finish greater than or equal to |
FLE |
Finish less than or equal to |
MS |
Mandatory start equal to |
MF |
Mandatory finish equal to |
If an ALIGNDATE statement is specified without an ALIGNTYPE statement, all of the activities are assumed to have an aligntype of SGE. If an activity has a nonmissing value for the ALIGNDATE variable and a missing value for the ALIGNTYPE variable, then the aligntype is assumed to be SGE. See the section Time-Constrained Scheduling for information about how the ALIGNDATE and ALIGNTYPE variables affect project scheduling.