Resource Data Sheet MOD0099DT

• PM Administration Master Data -->Resources Click on the New button (to create a new resource) or on other buttons (to edit existing resources) Resource Data Sheet
• PM Administration Master Data Administration panel Persons Click on the All button to have all persons displayed, or on the respective letter button if you are looking for a person with a particular name Expand the tree structure in the person record Click on the link on the person resource name.
• Resource Management Info and Status ModulesNEW Resource Structure (Display) Click on the link on the name of the required resource

• PM Administration Master Data -->Resources Click on the New button (to create a new resource) or on other buttons (to edit existing resources) Resource Data Sheet
• PM Administration Master Data Administration panel Persons Click on the All button to have all persons displayed, or on the respective letter button if you are looking for a person with a particular name Expand the tree structure in the person record Click on the link on the person resource name.
• Resource Management Department Planning Resource Structure (Display) Click on the link on the name of the required resource

• Enter the resource ID (e.g. his/her initials) in the Resource ID field in the blank resource data sheet.
• Enter the resource name in the Resource name field.
• Define further mandatory data
  • Resource type
    • A person has to be assigned to resources of the = 1I or 1E resource type (Internal employee and External employee). To do this, select a person from the Person listbox. If you do not fill this field, you will not be able to save.
      • To make this clearly visible, the Person field is marked as a mandatory field as soon as the 1I or 1E resource type has been selected for a resource to be newly created.
    • For resources of other resource types, the Resource name field has to be filled. If no name has been allocated, the Mandatory input not made, saving canceled message is displayed.
  • Default cost center
  • Default cost type
  • When you open the module, Start and End period are preset with today’s date automatically and must be adjusted according to the definition of the resource planning horizon. For this purpose, see the following "Create, Edit, Delete Resource Periods" chapter.
• Save.

• NEW If a new resource is created but no periods are defined for it at first, a period record with the date of creation of the resource is created in accordance with the entries in the start period/end period fields which are automatically filled with today’s date when a new resource is created.
• The Start and End period fields of the resource cannot be changed or filled if no resource calendar has been selected. If you try to do so regardless, a message is output, indicating this.
• If a date which is later than the last date of the selected calendar is entered in the End period field, the following message is displayed: Endperiod is later than the end of the selected calendar or Start period is earlier than the start of the selected calendar.
• If the available capacity of the child resource is summarized to the parent resource (Summarize periods parameter), the available capacity of the parent resource is adjusted automatically if changes are made to the periods of the child resource.
• Outside the planning horizon, the capacity scheduling calculates resources with default values from the Resource Data Sheet.
• The planning horizon range influences the computing time and the space required by the database.

• The save exit which is responsible for the creation of the periods has been replaced by the Python code.
  • If individual copies of the Resource Data Sheet and Resources modules have been created before, their customizing should be adjusted according to the respective default modules (new: macro and module subclass).

• After period records have been created for the defined period, individual records can be edited/changed in the Availability module if necessary; e.g. if a setting is to apply to individual period records which deviates from the settings in the Resource Data Sheet (e.g. defining bridging days as non-working days, etc.).
• If changes are made to resource master data in the Resource Data Sheet afterwards (e.g. Available capacity for periods) or to the calendar assigned to the resource, they are not automatically copied to the existing period records but are only applied to the newly created ones. In order for the changes to have an effect on existing periods as well, NEW the period records must be updated for the required period. For this purpose, see the procedure below.
  • This procedure also applies to the definition of several periods (also initial, not only retroactively) with different planning parameters within a planning horizon of a resource and therefore represents a time saving alternative to manually changing the parameters in the individual period records in the Availability module.

Update periods for a particular period NEW

• Do the following in the Resource Data Sheet module:
  • Change the required parameter.
  • Define the required time period in the from and to fields.
  • Click on the Update periods button.
    • In doing so, the new parameter values are copied to all period records of the defined period (to be checked in the Availability module).
  • Decide whether the changed parameter values are to apply to future periods, i.e. for all newly created periods, or whether new periods are to be reset to the initial value.

Example

• A person has a planning horizon from 01/01/2017 to 12/31/2018 and an availability of 8h a day. Periods for the entire planning horizon already exist. The person will work a reduced amount of hours from 07/01/2017 and have an availability of 4h a day.
  • Enter 07/01/17 in the from and 12/31/18 in the to field and save.
  • Click on the Update periods button.
    • In doing so, the availability in the (Unit/period) field in the period records from 07/01/17 to 12/31/18 is changed from 8 to 4.

Note

• When you change the parameter for particular periods, you have to note that there is currently no option for tracking changes.

• After period records have been created for the defined period, individual records can be edited/changed in the Availability module if necessary; e.g. if a setting is to apply to individual period records which deviates from the settings in the Resource Data Sheet (e.g. defining bridging days as non-working days, etc.).
• If changes are made to resource master data in the Resource Data Sheet afterwards (e.g. Available capacity for periods) or to the resource calendar, they are not automatically copied to the existing period records, but are only applied to the newly created ones. In order for the changes to have an effect on existing periods as well, they must be deleted and created anew for the same period. For more information, see the "Delete Periods" chapter.
  • This procedure also applies to the definition of several periods (also initial, not only retroactively) with different planning parameters within a planning horizon of a resource and therefore represents a time saving alternative to manually changing the parameters in the individual period records in the Availability module.

Example

• A person has a planning horizon from 01/01/2017 to 12/31/2018 and an availability of 8h a day. Periods for the entire planning horizon already exist. The person will work a reduced amount of hours from 07/01/2017 and have an availability of 4h a day.
  • Step 1: set the end period to 6/30/2017 and save.
    • As a result, all period records later than 6/30/2017 are deleted.
  • Step 2: change the value in the Unit/day field from 8 to 4.
  • Step 3: set the end period to 12/31/2018 and save.
    • As a result, new period records with the new availability (Unit/period) are created for the period from 07/01/17 to 12/31/18.

• In order to delete the created periods completely, you have to click on the Delete periods button in the Resource Data Sheet module.

• Vacation and absence
  • Vacation or/and absence data of the resources which are saved in individual period records are also deleted when the periods are deleted and must be created anew for newly created periods. NEW If you want vacation and absence data to be retained, you have to update periods instead of deleting them and creating them anew. For more information, see the Edit Periods section
• Resource planning
  • If there is actual data when the resource periods are deleted, these hours are not deleted.
  • The remaining data is not deleted either, however, this is due to missing periods,
    • for resources with CAP load profile this is done on a day which equates to the calculated start date of the respective task.
    • resources with BLD load profile or without load profile, it is allocated evenly throughout the entire duration of the task.

• If resource parameters are changed after period records have already been created, the changes are not copied to the existing period records automatically, so that they NEW must be updated manually. NEW As a result, an info message indicating this to the user is expressly displayed after the changes have been saved.
  • For this purpose, see the Edit Periods section.

• When "putting on" child resources,
  • the available capacity of the parent resource(s) is adjusted accordingly.
  • the utilization of the immediate parent resource is adjusted automatically, that of the upper level parent resource is not.
  • In order to ensure an update on all structure levels, you have to unload and subsequently replan all projects in the Replanning (Calculation of All Planning Objects) module.
• Since in PLANTA project resource structure codes are used to control access to resources, access settings for users must be checked and possibly be adjusted when changes are made to resource structure codes.

• When "putting on" child resources,
  • the available capacity of the parent resource(s) is adjusted accordingly.
  • the utilization of the immediate parent resource is adjusted automatically, that of the upper level parent resource is not.
  • In order to ensure an update on all structure levels, you have to unload and subsequently replan all projects in the Replanning (calculation of all projects) module.
• Since in PLANTA project resource structure codes are used to control access to resources, access settings for users must be checked and possibly be adjusted when changes are made to resource structure codes.