Knowledgebase
Trading Software > Help Desk > Knowledgebase

Search help:


Projects Overview

Solution

 

2019-10-11: Created : Work in progress. Not all functionality is currently live
 
 

Overview of Trading Software Projects.

 

Trading Software Projects

TSL Projects allows you to keep track of discreet projects within your organisation, carry sup-projects and collect activity against them. TSL Projects leverages existing Calendar / Event management which incorporates user assignment and an ability to link disparate database entities together.

In brief... Projects contain Sub-Projects which contain activities which contain task-time records

  • Sub Projects help to keep track of where you are in a Project's evolution
  • Activities are captured as part of the TSL event diary.
  • Task-time records are use to calculate what a project has cost, what can be billed and what to charge internally.
    • For instance, you might pay staff based on activity on specific projects.

 

The Project

These are your projects. Create them for anything that you need to be on top of. You can collect billable and chargeable time against a project or just keep track of what resources you have consumed.

The Project Entity:

  • can be colour coded
  • canbe archived as a project template
  • can be copied
  • can carry an overriding Billing SKU
  • can carry unlimited Sub-Projects

 

 The Sub-Project

These are discreet elements that make up a project. For instance, if your project was to build a house, sup-projects might include

  1. find an architect and get some plans
  2. dig foundations
  3. build some walls
  4. choose the curtains

Sub Projects can carry dependencies. This allows TSL to graphically present an overview of your overall project showing what must be done before you an move on. So, with your house building project, Digging Foundations is dependent upon the Architect Sub-Project being complete.

The Sub-Project

  • can carry an billing SKU that trumps the Project Level Billing SKU
  • carries a description
  • carries a progress narrative

Activities

These are the things that are done to complete a sub-project. You can simply list the activities or you can record time-spent (see below)

Activities are contained within the wider TSL event management system and interface with your calendar and task list. You can assign an activity to a specific individual from your contact list - The Activity ACTIONER

Activities carry their own narrative that can appear on an invoice if you BILL the sub-project (see below)

Incomplete activities on a sub-project render the parent Project 'ACTIVE'

Task Time

While working on an activity you can start a TIMER to record time-spent on a given task. Time-spent can be assigned to specific individuals from your contact list - The Task ACTIONER

Task time records are created by users that click the TIMER START button on an activity. The timer is stopped when the TIMER STOP button is clicked or when the activity is closed.

Hours worked are calculated as follows:

  • Where the start and stop date is the same day, the system simply calculates the difference in [hours : minutes : seconds] 
  • Where the start date is earlier then the end date the system will calculate an daily hour total for working days between the 2 dates.

You can specify the parameters to use when calculating time-spent, as part of Project Configuration

  • Daily Start-Time: When the working day starts '09:00:00'
  • Daily End-Time: When the working day ends '17:00:00'
  • Daily Break Allocation: The amount of time allocated to breaks in a day (1 1/2 hours) '01:30:00'

 

Billing

Billing is based on the following data

  • Time Spent
  • A project or sub-project billing SKU
  • Activities that are linked to a sub-project
  • Activities that are complete
  • Activities that have no ORDER-link already

Qualifying activities are presented in a dedicated interface.

Billed activities can be displayed on an invoice as 'notes' if you choose. This can be useful in preventing double keying of invoice line descriptions. By default invoice line descriptions contain the Project / Sub-Project / Activity reference.

NOTE:

  • An activity should only be billed when it is complete.
  • Part-billing a given activity is not possible.
  • To part bill, duplicate an activity.

 

Project Purchase Requests (Costs)

You can bill purchased items through a project.

Direct costs are captured against a project as Purchase Requests, and fulfilled as part of your purchasing process. Purchases can be linked to a Project Purchase Request and billed through the project it is linked to as part of the Billing Process. Purchases can also be billed directly to a customer in the usual way, but still be recorded against a project a Project Purchase.

More Information Here: Link

 

Charging

Charging is a way to accumulate internal costs for a given activity / sub-project / Project.

Project specific purchases can be listed against the Project and billed individually.

Charging is based on the following data

  • Time Spent
  • Activities that are linked to a sub-project
  • Activities that are complete
  • Activities that have no JOURNAL-link already

Qualifying activities are presented in a dedicated interface.

Charging is performed by creating a Journal Entry in your accounts from a Charging Control Account into a user specific Nominal Account.

The charge rate is specified at the Sub-Project level. To record time (hours) set the charge rate to 1 (default).

NOTE:

  • An activity should only be charged when it is complete.
  • Part-charging a given activity is not possible.
  • It is not possible to set a charge rate for each Task ACTIONER

More Information Here: Link

 
Was this article helpful? yes / no
Related articles Project Purchase Requests (Costs)
Project Charging
Project Billing
2.02.##.1125
FireList Archive
Article details
Article ID: 242
Category: Projects
Rating (Votes): Article rated 3.5/5.0 (11)

 
« Go back

 
Powered by Help Desk Software HESK, brought to you by SysAid