none
Why is the task for the "Constraint Type" automatically set to the type "Start No Earlier Than (SNET)?" RRS feed

  • Question

  • There are two tasks - "Task1", ​​"Task2".
    Tasks have "Constraint Type" = "As Soon As Possible (ASAP)".
    I set the start date for the task Task2.
    In the "Constraint Type" field, "Start No Earlier Than (SNET)" is automatically set.

    Questions

    1. Is it possible to make the stouts “As Soon As Possible (ASAP)” remain in the “Constraint Type” field in my situation?
    2. Status "Constraint Type" = "Start No Earlier Than (SNET)" does it have any dangerous features besides those described in the documentation?
    3. Maybe it somehow affects the allocation of resources?
    4. Or this task will then somehow especially influence:
      - to calculate the durations of other tasks related to this task?
      - to calculate the "remaining" "costs", "durations"?
    Quote from the documentation:
    "The task starts on or after a specific date.".
    "A task with this restriction cannot be started earlier than the specified date. This restriction is imposed automatically if you specify the start date of the task in the project with the formation of a schedule from the start date of the project."


     
    Thursday, January 9, 2020 7:37 PM

Answers

  • prog1003,

    The documentation clearly states that the SNET constraint will be set automatically IF the user enters a start date. And no, there is no way to enter a start date and have an ASAP constraint.

    When the Project Start Date is set, any task that does not have a predecessor will automatically move to that date. In a VERY few cases the user may need a task to start no earlier than a particular date. Such a case might be when the "driver" for a task is dependent on a particular resource but that resource is not available until after a certain date.

    Best practice is that semi-hard constraints (SNET, FNLT, etc.) and hard constraints (MSO, MFO) should not be used if at all possible. The project plan should be driven by a logical sequence of tasks linked with predecessors and successors. Constraints negate a dynamic plan and can interfere with critical path analysis.

    Hope this helps.

    John

    • Marked as answer by prog1003 Thursday, January 9, 2020 9:16 PM
    Thursday, January 9, 2020 8:01 PM

All replies

  • prog1003,

    The documentation clearly states that the SNET constraint will be set automatically IF the user enters a start date. And no, there is no way to enter a start date and have an ASAP constraint.

    When the Project Start Date is set, any task that does not have a predecessor will automatically move to that date. In a VERY few cases the user may need a task to start no earlier than a particular date. Such a case might be when the "driver" for a task is dependent on a particular resource but that resource is not available until after a certain date.

    Best practice is that semi-hard constraints (SNET, FNLT, etc.) and hard constraints (MSO, MFO) should not be used if at all possible. The project plan should be driven by a logical sequence of tasks linked with predecessors and successors. Constraints negate a dynamic plan and can interfere with critical path analysis.

    Hope this helps.

    John

    • Marked as answer by prog1003 Thursday, January 9, 2020 9:16 PM
    Thursday, January 9, 2020 8:01 PM
  • John, even that example about the resource not available until a certain date does not require a SNET constraint if the limitation can be set in the resource calendar.
    Thursday, January 9, 2020 11:14 PM
  • I think you worry too much, or perhaps are over-thinking it.

    Regarding your point 3, no.

    Regarding your point 4, definitely not either of those.

    See task information, advanced, constraint type to see the 8 possible date constraints. If you type a start date into the start field, you get a SNET. If you type a date in the finish field you get a FNET. Avoid all date constraints except ASAP (which is not really a constraint at all).

    ALAP

    ASAP

    FNET

    FNLT

    MFO

    MSO

    SNET

    SNLT

    Thursday, January 9, 2020 11:20 PM