| Änderungen von: | |
| bis: | |
| Typ: | |
 erste | letzte  |
The Project-Time module offers a variety of options for booking productive times on various occasions on specific service objects. Examples of such bookable service objects could would be:
How the project term concept is actually used can be defined flexibly. In principle, the bookable object does not always have to be explicitly a project, but in the following explanations the terms "bookable object" and "project" are equated for simplicity's sake. Each bookable object (project) is part of a "project structure" in order to group so that similar projects can be grouped in a tree. The examples The differentiations mentioned above could be used to define several project structures.
Within the project structure, the tree can be structured in a hierarchical manner as deep as desired, containing organized to any depth with projects, subprojects, or sub-...subprojects. It is configurable how How deep such a tree can get is configurable.
Additionally, booked Booked project times can also be connected with several additionally be linked to various other factors, for instanceexample:
When creating a new bookable project or a new project structure, Webdesk provides some organizational elements that can define the project or structure more closely and can make the recording of project time more concretespecific. All of these elements can be viewed are available as items in the Administrators menu of the "Project Time RecordingTracking" module and are briefly explained briefly below:
Elements necessary required for proper use:
|
Structures |
The structure is the highest organizational unit in project time |
|---|
|
tracking. Within a project structure, main projects, projects, and |
|
subprojects can be organized |
|
as |
|
desired. Structures are often organized |
|
by intended use, e.g., internal projects, customer projects, or product development. |
|
|
Projects |
Projects are the bookable objects and the main |
|---|
|
element in project time |
|
tracking. |
|
A project must always |
|
be selected when recording |
|
. |
|
Activities |
|---|
|
Freely selectable activity areas |
|
that are created independently of project structures and can be |
|
specified as "additional information" |
|
when booking project time |
|
--> "What do I do for project XY?" - "Programming, administration, marketing, etc. |
|
?" |
|
|
Element types |
The element type is an attribute including a logo and must be assigned to every bookable object. The element type specifies the characteristics of the object more closely, e.g. |
|---|
|
, as |
|
a subproject, |
|
planning, external project, etc. |
optional Optional elements:
|
Cost |
|---|
|
center |
These are identical to the cost center groups defined in the organizational structure. Booked project times can be automatically assigned to specific cost centers via the person booking. |
|---|---|
|
Cost |
|
object |
Here you can define specific cost objects (e.g., a specific product). A project can then be partially or completely assigned to this cost object. |
|---|---|
|
Customers |
|
Here you can create customers |
|
, which can then be |
|
assigned to a project. |
| Mime Type | text/xml |  | text/xml |
| Datei-name | | ||
| Größe (in Bytes) | 4125 |  | 4037 |
|
Version 5 von Mr. Ex-Mitarbeiter
am 29.11.18 15:39:24 Name: Organisation & Project Structure Variante: main - en Status: Veröffentlichung |  |
Version 6 von Gabriel Gruber
am 17.10.26 18:03:29 Name: Organization & Project Structure Variante: main - en Status: Veröffentlichung |
Vergleiche Versionen 4 und 5