Query Studio / Report Studio

For an example of a report created from data in the Resource Requirement group, see Resource Requirements Crosstab Report.

Important: Work from top to bottom in the Resource Management data structure in order to get consistent and logical results. Query subjects are nested logically and related to one another based on the structure of the folder.

The data model is designed so that you should rarely need to use data from more than one logical (top-level) folder in any given report. If you do need to combine data from more than one logical grouping, create a Join relationship in Report Studio. For more information, see the Report Studio training and User guide.

• Resource Management

• Resource Management Date Groups
   

  Date group query items are useful for reporting trends over time. If you include a date group item and pivot your report on that item, you can see how something is trending over time.

  • Resource Week—The first day of the week in dd/mm/yyyy format (for example, 9/2/13).
  • Resource Month—The month and year (for example, Oct 2013).
  • Resource Quarter—The quarter and year (for example, Q4 2013).
  • Resource Year—The year (for example, 2013).

   

• Requirements 
  
  • Project Name—The name of the project for which the resource requirement.
    Note: Only projects with outstanding resource requirements will be included.
  • Project Type Name—The project type for the project.
  • Requirement Resource Type Name—The resource type name for the requirement.
  • Requirement Resource Type Description—The resource type description for the requirement.
  • Requirement Resource Type Active—Whether or not the requirement resource type is active. Options are Yes and No.
  • Status—The status of the resource type requirement. Options are Open and Filled.
  • Requirement Created By—The name of the user who created the requirement for the resource type.
  • Requirement Date—Date or time period of the resource requirement for a given project.
  • Requirement Hours—The number of hours for the resource type for the requirement.
  • Requirement Cost—The cost of the requirement, based on the resource type billing rate.
    Note: (Requirement Hours * Inherited Internal Billing Rate)
  • Requirement Estimated Cost—The estimated cost of the requirement, based on the allocation billing rate(s) and the requirement type billing rate if there are unallocated hours.
    Note: ((Allocation Hours * Inherited Internal Billing Rate) + (remaining Requirement Hours * Inherited Internal Billing Rate)).
    
    Billing rate inheritance differs for allocations and requirements. See Billing Rates in Resource Allocation.
  • Internal Billing Rate—The inherited internal billing rate of the requirement. Rate precedence is Requirement rate (if one exists), then Resource Type rate (if a Requirement rate is not defined).
  • External Billing Rate—The inherited external billing rate of the requirement. Rate precedence is Requirement rate (if one exists), then Resource Type rate (if a Requirement rate is not defined).
  • Requirement Created On—The date the requirement was created.
  • Requirement Updated On—The date the requirement was last updated.
  • IDs

    Note: IDs are included in the data model so you can join to other queries. Also, grouping on an ID can help separate different items with identical names.

    • ResourceTypeID
    • EnterpriseID
    • InternalBillingRateID
    • ExternalBillingRateID
    • ResourceRequirementID
    • WorkspaceID
    • CreatedByID

     

  • UTC Dates

    Note: UTC dates are shown in Coordinated Universal Time format. UTC is also known as Greenwich Meridian Time (GMT).

    • Reqmnt Created On (UTC)—The date the requirement was created.
    • Reqmnt Updated On (UTC)—The date the requirement was updated.

     

• Resource Allocations / Capacity
  Note: Include a Requirements query item before adding information from this folder.
  • Allocations
    • Allocation Date—Date or time period assigned to specific resource or resource type allocations.
    • Allocation Hours—Hours of the resource allocation.
    • Allocated Cost—The planned cost of the resource allocation.
      Rate precedence to calculate the cost (using the first assigned rate found): Requirement rate, Member rate, Member Resource Type rate, Requirement Resource Type rate.
    • Allocation Created By—The name of the user who created the resource allocation.
    • Allocation Created On—The date the resource allocation was created.
    • Requester—The name of the project manager who created the allocation request. Note: This is blank when Status is not Pending.
    • Requested From—Name of the resource manager from whom the resource or resource type was requested.
    • Status—The status of the allocation. Valid values are Unsent, Pending, and Approved.
    • Numeric Codes
      • Status (numeric)—The numeric code for Status. Valid values are 0 (approved), 1 (pending), and 3 (unsent).

       

    • IDs

      Note: IDs are included in the data model so you can group on an ID if you have multiple items with the same name. Grouping on the ID can help separate different items with identical names.

      • ResourceAllocationID
      • Res Alloc ResourceRequirementID
      • EnterpriseMemberID
      • Res Alloc CreatedByID
      • RequestedFromID

       

    • UTC Dates

      Note: UTC dates are shown in Coordinated Universal Time format. UTC is also known as Greenwich Meridian Time (GMT).

      • Alloc Created On (UTC)—The date the allocation was created.

     

  • Allocation Filters
    • Pending Allocations—Limits the report to allocation requests that have a Status of "Pending".
    • Approved Allocations—Limits the report to allocation requests that have a Status of "Approved".
  • Requirement Remaining Hours—The number of hours for the requirement that have not been allocated (Requirement Hours - Allocation Hours).
  • Resource Member and Type
    • Member Type Name—The name of the resource type.
    • Member Type Description—The description of the resource type for the resource member.
    • Member Name—The name ( First + Last) of the resource member assigned to the resource type.
    • Capacity and Availability
      • Capacity Hours—The capacity (in hours) of the resource member (nonworking time has not been subtracted).
      • Nonworking Time Hours—The nonworking time (in hours) of the resource member (includes both any applicable global nonworking time and personal nonworking time).
      • Net Capacity Hours—The net capacity in hours of the resource member ( Capacity Hours - Nonworking Time Hours).
      • Scheduled Work Hours—The scheduled work hours (Task Work Hours) of the resource member. This includes work for all projects the resource member is a member of.
      • Availability—The net availability of the resource member (Capacity Hours - Scheduled Work Hours).
      • Net Availability—The net availability of the resource member (Capacity Hours - Scheduled Work Hours).
      • Scheduled Utilization %—The percentage utilization of the resource member (Scheduled Work Hours / Net Capacity Hours).
      • Actual Work Hours—The actual work hours for the resource member.
      • Actual Utilization %—The actual utilization percentage of the resource member (Actual Work Hours / Net Capacity Hours).
      • Type Requirement Hours—Resource Requirement Hours / Type Member Count.
      • Type Member Count—The total number of members of this resource type.
      • Allocated Utilization %—The percentage allocated utilization of the resource member (Allocation Hours / Net Capacity Hours).

       

     

   

Related Topics:

• PPM Reports Overview—About PPM Reports and reporting options.
• Reporting Data Presentation Model—About the PPM Reports data model.
• Reports Data Model Icons—About the icons used in the reporting data model.

Copyright © 2018 Daptiv Solutions, LLC. All Rights Reserved