Changes
/* Scopechange Details */
== Scopechange Details ==
As mentioned above, the client takes care to copy over relevant data from the parent workorder and duplicated operation, when appropriate.
* The '''Workorder Details ''' are copied over from the parent.* A unique '''Scopechange Number ''' is assigned by the server.* On the right side of the page, a longer '''Scopechange Description''', and attachments, can be added to further describe the work.
<br>
For new Scopechanges, the Activity Code of ''Scope Change (scocha)'' is assigned by default, and 4 digits for the Operation Number need to be assigned by the user.
For duplicated Scopechanges, the Activity Code, Operation Number, and Operation Description are copied over from the original.
* The '''Operation Description ''' should be altered to describe the work concisely.* The user should adjust the '''Operation Number''', adding + 4 digits for a sub-operation if required.** Example: 88290234 0040 0000 * The '''Activity Code ''' can be selected out of the full list of Activity Codes. '''Select only already used ones for this project, otherwise, it will be maybe not visualized.''' * The user's company is assigned as the '''Contractor'''.
==== Price Details ====
* '''Price Type ''' indicates whether the scopechange shall be billed on a ''Fix Price'', ''Unit Rate'', or ''Hourly'' basis.* The '''Estimated Cost ''' gives an indication of how much the work should cost overall.* The '''Early Start ''' date is copied over from the Workorder. It represents the earliest that work can begin on an operation and cannot be altered.* The '''Late Finish ''' date is also copied over from the Workorder, however, it can be altered.* The '''Affects Schedule ''' checkbox should be checked on, for yes, if necessary.
** '''If the Scopechange will indeed affect the schedule, it can be specified how many hours (Duration), multiplied by how many people (Resources) will be required. The total is calculated by the client.'''
<br>
