Column Label | Description |
Timesheet Period Start | Range of time periods to display filtered by start date |
Timesheet Period Finish | Range of time periods to display filtered by finish date |
Resource | Resource(s) to display |
Type | Note on a timesheet or time entry (task specific) |
274 results
-
The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task. This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
-
The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task. This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
Column Label Description Timesheet Period Start Range of time periods to display filtered by start date Timesheet Period Finish Range of time periods to display filtered by finish date Resource Resource(s) to display Type Note on a timesheet or time entry (task specific) -
This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched. For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below:
- wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
- xogBatchSize: The XOG batch size. This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
- username: The resource name that the process uses for uploading data. The default is set to admin.
- It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
- Notes field should not be modified in Script nor should be worked upon by any other process.
- All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
-
Most organizations struggle with collaborating across frameworks. Those managing FinOps activities, the TBM office, and Agile delivery teams are operating in silos, but there is a better way forward. In this class we’ll go through some strategies of bringing teams together to improve business outcomes through collaboration.
-
Many organizations have a goal to understand, track, and control the TCO of applications or services, but it can be challenging to accomplish. In this session, we'll discuss what makes TCO so important, important decisions you'll need to consider along the way, and some best practice guidance on reaching your TCO goal.
-
Do you want to report on TCO for your organization by business function, application, or service? This should be the financial management goal of every organization. This class will discuss a path and some architecture choices to make this a reality. We will highlight want some customers are doing today and share some best practices on the journey.
-
Discover the growing trend of organizations adopting the FinOps methodology and its integration with the TBM framework. In this session, we'll explore how the TBM office and FinOps teams can collaborate effectively to achieve desired outcomes, fostering a synergistic relationship between them, and leveraging the combined capabilities of Apptio and Cloudability for optimal results.
-
Discover the growing trend of organizations adopting the FinOps methodology and its integration with the TBM framework. In this session, we'll explore how the TBM office and FinOps teams can collaborate effectively to achieve desired outcomes, fostering a synergistic relationship between them, and leveraging the combined capabilities of Apptio and Cloudability for optimal results.