The CPM Procedure
- Overview
- Getting Started
-
Syntax
-
DetailsScheduling Subject to Precedence ConstraintsUsing the INTERVAL= OptionNonstandard Precedence RelationshipsTime-Constrained SchedulingFinish MilestonesOUT= Schedule Data SetMultiple CalendarsBaseline and Target SchedulesProgress UpdatingResource-Driven Durations and Resource CalendarsResource Usage and AllocationRESOURCEOUT= Usage Data SetRESOURCESCHED= Resource Schedule Data SetMultiproject SchedulingMacro Variable _ORCPM_Input Data Sets and Related VariablesMissing Values in Input Data SetsFORMAT SpecificationComputer Resource Requirements
-
ExamplesActivity-on-Node RepresentationActivity-on-Arc RepresentationMeeting Project DeadlinesDisplaying the Schedule on a CalendarPrecedence Gantt ChartChanging Duration UnitsControlling the Project CalendarScheduling around HolidaysCALEDATA and WORKDATA Data SetsMultiple CalendarsNonstandard RelationshipsActivity Time ConstraintsProgress Update and Target SchedulesSummarizing Resource UtilizationResource AllocationUsing Supplementary ResourcesINFEASDIAGNOSTIC Option and Aggregate Resource TypeVariable Activity DelayActivity SplittingAlternate ResourcesPERT Assumptions and CalculationsScheduling Course - Teacher CombinationsMultiproject SchedulingResource-Driven Durations and Resource CalendarsResource-Driven Durations and Alternate ResourcesMultiple Alternate ResourcesAuxiliary Resources and Alternate ResourcesUse of the SETFINISHMILESTONE OptionNegative Resource RequirementsAuxiliary Resources and Negative RequirementsResource-Driven Durations and Negative RequirementsStatement and Option Cross-Reference Tables
- References
TAILNODE Statement
-
TAILNODE variable;
-
TAIL variable;
-
FROM variable;
The TAILNODE statement is required when data are input in AOA (arrow notation) format. It specifies the variable that contains the name of each node on the tail of an arc in the project network. This node is identified with the event that signals the start of the activity on that arc. The variable specified can be either a numeric or character variable since the procedure treats this variable symbolically. Each node must be uniquely defined.