Configure Time Slices

HID_admin_configure_time_slices
ccppmop142
HID_admin_configure_time_slices
Contents
A time slice is a flat table that contains data that is derived from a sliced binary large object (BLOB). A BLOB is a collection of binary data that is stored as a single entity in a database. You can use a BLOB to store curve and calendar data.
The data model contains several BLOBs that most reporting tools cannot read. Configure a time slice request to specify the objects and fields, the slicing frequency, and the granularity to store the data. Once defined, the Time Slicing job extracts data and displays a readable flat table that is based upon the criteria you set in the time slice request. You can then query the time slice to run reports.
For more information, see
CA PPM Studio Development
.
The following objects require time slicing:
  • prAllocCurve
    The percentage of a resource availability that is allocated for a project (as a rate curve).
    Source table
    : PRTeam
  • prActCurve
    Actuals posted to an assignment.
    Database Column:
    prExtension
    Source table
    : PRAssignment
  • prEstCurve
    Estimates for an assignment.
    Database Column:
    prExtension
    Source table
    : PRAssignment
  • prBaseCurve
    Baselines for an assignment.
    Database Column:
    prExtension
    Source table
    : PRAssignment
  • prAvailCurve
    The resource availability (as rate curve).
    Source table
    : PRResource
  • prValue
    Work time information, such as shifts, days off, and holidays. While this table calculates resource availability and allocation, you cannot select the table for time slicing.
    Source table
    : PRCalendar
  • prAllocCurve
    Values on timesheet time entries.
    Source Table
    : PRTimeentry
For more information, see
Technical Reference
.
Create a Time Slice Request
The initial time slicing process can take several minutes. Once you write time-slice data, the next time the job runs, it only checks for updated objects. The time slice updates whenever the content of an object changes. For example, adding ETC to an assignment.
Between the time that you create a time slice request and then refresh it, many database transactions can occur. To preserve systems resources, disable temporarily transaction logging. Verify with your database administrator before changing a time slice request or anything that can cause a large number of database transactions to occur.
For more information, see
CA PPM Studio Development
.
Follow these steps:
  1. Open Administration, and from Data Administration, click Time Slices.
  2. Click New.
  3. Complete the following fields:
    • Time Slice Name
      Defines the name for time slice request.
    • Rollover Interval
      Defines the frequency that the From Date updates for processing an updated time slice request. Define the option when doing ongoing reports, such as end-of-month reports.
      Values:
      • Daily -- Updates the time slice every calendar day.
      • Weekly -- Updates the time slice every week.
      • Bi-Weekly -- Updates the time slice every 14-calendar days.
      • Monthly -- Updates the time slice every calendar month (recommended frequency).
      • Bi-Monthly -- Updates the time slice every two calendar months.
      • Quarterly -- Updates the time slice every three calendar months.
      • Semi-Annually -- Updates the time slice every six calendar months.
      • Yearly -- Updates the time slice every year.
      • None -- The time slice never updates.
      Default:
      Daily
      For ad-hoc reporting:
      None
    • From Date
      Defines the date from when the time slice period begins.
      Example:
      To have time slice data start the first day of each month, enter the first day of the month. Then, select Monthly as the slice period.
    • Slice Period
      Specifies the period to use for each time slice request.
      Values:
      • Daily
      • Weekly -- Seven calendar days.
      • Bi-Weekly -- 14 calendar days.
      • Monthly -- One calendar month.
      • Bi-Monthly -- Two calendar months.
      • Quarterly -- Three calendar months.
      • Semi-Annually -- Six calendar months.
      • Yearly -- 12 calendar months
      • None
    • Number of Periods
      Defines the number of periods for each time slice request.
      Example:
      12 (months), 52 (weeks), and 5 (years).
    • Item
      Defines the object, or data element, to time slice.
      Values:
      • Actuals -- Defines the hourly time posted for an assignment on a project. The element sets up by default.
      • Estimates -- Defines the hourly estimate for an assignment on a project. The element sets up by default.
      • Baseline -- Defines the baseline (in hours) for a project assignment. The element sets up by default.
      • Availability -- Defines the hours per day that a resource is available to work on a project. The element sets up by default.
      • Allocation -- Defines the percentage time that a resource allocates to a project. The element sets up by default.
      • Time Entries -- Defines the time entry value for a timesheet.
      • Current -- Data identified for the current baseline. For example, when you have multiple baselines, select the baseline to consider the current baseline for each project.
      • Non-Current -- Data not identified for the current baseline.
    • Expiration Date
      Use the field for ad-hoc reports. Specifies the date when data gets deleted from the database. The date automatically displays for rollover time slices.
  4. Save the changes.
    The new time slice request records and time slicing begins immediately.
How to Query Time Slices to Run Reports
Once the Time Slicing job performs time slicing, you can query the time slice to run reports. Each record in the time slice table contains an object ID that corresponds to a data element. The report writer uses the object IDs to identify the resource that is associated with the slice record.
Follow these steps:
  1. Create the time slice request.
  2. Schedule to run the Time Slicing job.