What is the meaning of the "Work start" and "Work end" fields on a Change? How do they differ from "Planned Start Date" and "Planned End Date" ?

[rsworden]

What is the meaning of the "Work start" and "Work end" fields on a Change? How do they differ from "Planned Start Date" and "Planned End Date" ?

[Mark Stanger]

Planned start and end are reflective of the anticipated times and duration of the change.   They can be used to generate a forward schedule of change.   Work start and work end gives you the actual times and duration for the change.   You might have a planned window of 3 hours, but an actual implementation duration of 30 minutes...or 4 hours.   It's the plan versus the actual.

[Bryan Campbell]

We actually use these fields in our environment but added some automation that would trigger the Change to go through PIR if the Work Start and Work End is outside of the window of the Planned start and End time.

[Michael Fry1]

Planned Start/End defines the window when the work is expected to be completed. Work start/end is supposed to be populated by the agent when the work actually starts and when the work actually ends.

In our environment, we don't use those fields since most of the work is completed in the change tasks.

[meera4]

Hi Roger

We actually use them for actual change window time but there is another attribute called "Actual Start time " and no "Actual End time" so we used these attributes for the use and not sure about the attribute "Work Start and end "   real meaning .

It purely depends on your design and requirement