Term Description
Activity An activity is attached to a Project. Examples can be 'Customer visit’, 'Cold calling’, 'Internal tasks’, 'Sick leave’, etc. You define these yourself.
Activity types Used for grouping activities. The only rule is that there has to be at least one type, since an activity needs to be connected with a type. An example could be “Billable Hours”, “Non Billable Hours”, etc.
Application ID Application ID is used in conjunction with a Foreign Key. If entries are imported via DataBridge, you should define a common Application ID to identify the source. The Application ID and the Foreign Key is used to link information in TSR together when it does not originate from typing the information into TSR.
Appointment In TSR terms and appointment is the same as a Time Entry. Please see the glossary entry for Time Entry for further information
Approval/Rejection Approval/Rejection is the process where an approver will approve a time entry made by a user. The approving user must be a member of the approver group connected to the project. When an appointment gets approved, it will be locked for future use and marked as approved. If an appointment is rejected, it gets unlocked so the originating user or the substitute submitter can make changes to it.
Approver An approver is a user who is a member of the user group responsible for approving or rejecting projects. The approvers are specified individually per project.
Calendar Please see 'Working Hours’ further down.
Communication Detail Types Communication Detail Types are used to set up communication information with organizations. Examples of types could be: Phone number, Cell Phone and Email.
Contact Types Contact Types are used to group the contact persons that can be connected to an organization. That could be “IT Manager”, “CEO” and so on.
DataBridge DataBridge is the common name for a set of utilities that will help you to import data into TSR and export data from TSR.
DataBridge Runtime DataBridge Runtime is a utility that makes predefined DataBridge profiles as defined in DataBridge Setup available from a command line for use in BAT files or other scripts.
DataBridge Setup A tool in the web interface used to define DataBridge Profiles.
DataBridge Profile A DataBridge Profile is a description of format and functionality that is defined in DataBridge Setup. The DataBridge Profile can be used from either DataBridge Runtime or DataBridge via the web interface to ease the process of getting data to and from TSR.
Expenses You can add expenses, such as mileage, products, etc. to your time entries in TSR. These can be added and submitted via WebAdmin and via the TSR Outlook User Agent. They also have an optional approval workflow like time entries.
Foreign Key Used to connect data that origins from external sources, typically data that is imported via DataBridge. Under normal circumstances the Foreign key is not visible and is maintained automatically via DataBridge.
Hosted TSR The hosted version of TSR means that we host the server part for you, so you only need to install the Outlook user agent. If you don’t have a Microsoft Server environment or just want to keep things simple, this is the solution for you.
License In technical terms a license is a string of characters that is used to put the TSR Features at disposal.
Localization TSR comes in several languages and the translation is done via localization. It is possible to create own localization or change the predefined languages. IMPORTANT: We do not encourage you to make changes to the predefined languages, since these changes could be overwritten when the system is upgraded. If you need to change some labels in TSR, we encourage you to export the language that comes closest, make the necessary corrections and import as a new user defined language.
Mail Server Settings Information on the mail server that you will be using for sending out notifications to users.
Notifications This function makes it possible to send reminders to staff that have not reported the number of hours they’re supposed to. You can setup one or more calendars, and define each day of the week regarding how many hours should be reported there, and also include exceptions for example for holidays, etc. You then attach users to this calendar. Then when it suits you, you can use the notification function and users that have not reported enough hours (defined by their attached calendar) will get a notification and you will get a collected report with all missing entries. You can create different calendars for different user groups, for example full-time employees, part-time, interns, etc.
On-Premise TSR The on-premise solution means that you host the server part yourself. If you have a Microsoft Server environment, have minimum 1,000 users, and want to handle the server part yourself, then this is the solution for you.
Organization Projects and activities are connected to organizations. An organization can be your own organization or for example customer organizations.
Project Activities are attached to projects. Examples of projects can be 'Internal Projects’, 'Customer A Project’, 'Marketing’, etc. You define these yourself.
Project Types Used to group projects. A project needs to be connected with a type so the system must hold at least one project type. An example could be “Non billable projects”, “Projects for monthly billing”, “Projects for weekly billing” and so on.
Reporting Administrators can also easily generate standard reports, to get all sorts of information. For example time spent on a specific project, compare time entries for different users, compare time spent on different projects, time spent on a specific organization, etc.
Roles Used to define the privileges for user groups. It can be all from next to nothing to full administrative privileges regarding TSR.
Submit When you have finished an appointment and attached the proper TSR information (Organization, Project and Activity) you can submit it. It will then be sent to a supervisor that can either approve or reject the entry.
Substitute Submitter Users with the right privileges can create, edit and submit time entries for other users, via the web interface. Such users are called Substitute Submitters.
Synchronization The process of synchronizing TSR information between the TSR server and the local cache/off-line database.
Time Entry Also known as an appointment. A time entry is an appointment generated from the TSR Outlook User Agent or the Timesheet Management in the web interface. A time entry is not visible for the TSR Server before it carries TSR information such as Organization, Project, Activity and/or submit flag.
TimeSheet Management A web interface to handle TimeSheets directly via the web browser. If the agent is set up correctly, timesheets changed, deleted or created will be synchronized to the user’s Outlook.
TSR Server This is the server part of TimeSheet Reporter, which among other things include the web interface.
TSR Services A set of web services installed on the TSR server that enables the communication between the user agent, the web interface and the TSR Server.
TSR User Agent This is the TSR Outlook User Agent, which is the plugin you install in your Microsoft Outlook, and makes the TSR functionalities available here.
TSR Web Interface You can access TSR via a web interface. This goes for administrators and users with the right privileges, for example supervisors and substitute submitters.
Types This is the common denomination for the types that are used to describe elements in TSR.
User Groups Used to assign privileges to users and connect users with projects and other components of TSR. A user must belong to at least one group.
User Settings A managed way to set up individual or all users’ User Agents.
Users A person or an account that is using TSR.
Working Hours Working Hours are used in connection with notifications. You can setup one or more Working Hours Profiles, and define each day of the week regarding how many hours should be reported there, and also include exceptions for example for holidays, etc. You then attach users to this profile. Then when it suits you, you can use the notification function and users that have not reported enough hours (defined by their attached Working Hours Profile) will get a notification and you will get a collected report with all missing entries. You can create different Working Hour Profiles for different user groups, for example full-time employees, part-time, interns, etc.

 

On 2013/06/24   /   Glossary   /   Leave a comment
Tags: , ,

Leave a Reply