[doc] Fixed encoding in some files. Now all files have UTF-8.
This commit is contained in:
Manuel Rego Casasnovas
parent
2343e68a26
commit
890542d370
10 changed files with 1027 additions and 1027 deletions
|
|
@ -1,117 +1,117 @@
|
||||||
Introduction
|
Introduction
|
||||||
#############
|
#############
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
The purpose of this document is to describe the features of NavalPlan and provide user information on how to configure and use the application.
|
The purpose of this document is to describe the features of NavalPlan and provide user information on how to configure and use the application.
|
||||||
|
|
||||||
NavalPlan is an opensource web application for project planning. Its main goal is to provide a complete solution for company project management.
|
NavalPlan is an opensource web application for project planning. Its main goal is to provide a complete solution for company project management.
|
||||||
For any specific information you may need about this software, please contact the development team at http://www.navalplan.org/contact
|
For any specific information you may need about this software, please contact the development team at http://www.navalplan.org/contact
|
||||||
|
|
||||||
|
|
||||||
<s>The program for the production management of the naval assistance sector mainly aims to solve planning problems for companies that work in the sector. This is why a series of tools has been developed to solve specific problems that have been identified during the analysis of the project. However, the solutions proposed for these problems are not exclusive to the naval sector, and can be useful for any company that applies the program's basic concepts.</s>
|
<s>The program for the production management of the naval assistance sector mainly aims to solve planning problems for companies that work in the sector. This is why a series of tools has been developed to solve specific problems that have been identified during the analysis of the project. However, the solutions proposed for these problems are not exclusive to the naval sector, and can be useful for any company that applies the program's basic concepts.</s>
|
||||||
|
|
||||||
|
|
||||||
.. figure:: images/company_view.png
|
.. figure:: images/company_view.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Company overview
|
Company overview
|
||||||
|
|
||||||
Company overview and view management
|
Company overview and view management
|
||||||
====================================================
|
====================================================
|
||||||
|
|
||||||
As can be seen in the program's main screen (shot given previously) and the company overview, users can see the list of planned projects to find out about the company's overall situation in relation to orders and the use of resources. The company overview contains 3 views:
|
As can be seen in the program's main screen (shot given previously) and the company overview, users can see the list of planned projects to find out about the company's overall situation in relation to orders and the use of resources. The company overview contains 3 views:
|
||||||
|
|
||||||
* Planning view: View that combines two points of view:
|
* Planning view: View that combines two points of view:
|
||||||
|
|
||||||
* View of orders and the time taken: Each project uses Gantt charts, which indicate the start and end date of the project. This information is combined with the chart showing the agreed deadline and then a comparison is made between a percentage of progress and time that is actually dedicated to each project. This information gives a clear picture of how the company is doing at a given time. This view is the program's opening page.
|
* View of orders and the time taken: Each project uses Gantt charts, which indicate the start and end date of the project. This information is combined with the chart showing the agreed deadline and then a comparison is made between a percentage of progress and time that is actually dedicated to each project. This information gives a clear picture of how the company is doing at a given time. This view is the program's opening page.
|
||||||
* Graph showing the company's use of resources: Graph that searches for information on the allocation of resources to projects, which also gives a summary on the entire company's use of resources: Green indicates that the allocation of resources is under 100%, the black line shows the available load of resources and yellow indicates that allocation of resources is above 100%. It is possible for allocation to be less than available resources and to have over allocation for specific resources at the same time.
|
* Graph showing the company's use of resources: Graph that searches for information on the allocation of resources to projects, which also gives a summary on the entire company's use of resources: Green indicates that the allocation of resources is under 100%, the black line shows the available load of resources and yellow indicates that allocation of resources is above 100%. It is possible for allocation to be less than available resources and to have over allocation for specific resources at the same time.
|
||||||
|
|
||||||
* Resource load view: Screen that shows the list of workers in the company and the load of specific allocation to tasks or generic allocation as the resource fulfils a list of criteria. See the following image. You need to click on *Overall load of resources* to access this view.
|
* Resource load view: Screen that shows the list of workers in the company and the load of specific allocation to tasks or generic allocation as the resource fulfils a list of criteria. See the following image. You need to click on *Overall load of resources* to access this view.
|
||||||
* Orders administration view. Screen that shows the list of company orders, where the user can carry out the following operations: filter, edit, erase, visualise planning or create a new order. You need to click on *Order list* to access this view.
|
* Orders administration view. Screen that shows the list of company orders, where the user can carry out the following operations: filter, edit, erase, visualise planning or create a new order. You need to click on *Order list* to access this view.
|
||||||
|
|
||||||
|
|
||||||
.. figure:: images/resources_global.png
|
.. figure:: images/resources_global.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Resource overview
|
Resource overview
|
||||||
|
|
||||||
.. figure:: images/order_list.png
|
.. figure:: images/order_list.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Order list
|
Order list
|
||||||
|
|
||||||
|
|
||||||
The view management commented on previously for the company overview is very similar to the management planned for a single project. A project can be accessed in several ways:
|
The view management commented on previously for the company overview is very similar to the management planned for a single project. A project can be accessed in several ways:
|
||||||
|
|
||||||
* By right clicking on the Gantt chart for the order and then selecting *Plan*.
|
* By right clicking on the Gantt chart for the order and then selecting *Plan*.
|
||||||
* By accessing the order list and clicking on the icon for the Gantt diagrams.
|
* By accessing the order list and clicking on the icon for the Gantt diagrams.
|
||||||
* By creating a new order and changing the current order view.
|
* By creating a new order and changing the current order view.
|
||||||
|
|
||||||
The program has the following views for an order:
|
The program has the following views for an order:
|
||||||
|
|
||||||
* Planning view. View where the user can visualise the task planning, dependencies, milestones, etc. See the *Planning* section for more information.
|
* Planning view. View where the user can visualise the task planning, dependencies, milestones, etc. See the *Planning* section for more information.
|
||||||
* Resource load view. View where the user can check the designated resource load for a project. The colour code is the same for the company overview: Green for a load less than 100%, yellow for a load equal to 100% and red for a load over 100%. The load may come from a task or a list of criteria (generic allocation).
|
* Resource load view. View where the user can check the designated resource load for a project. The colour code is the same for the company overview: Green for a load less than 100%, yellow for a load equal to 100% and red for a load over 100%. The load may come from a task or a list of criteria (generic allocation).
|
||||||
* Editing order view. View where the user can change the details of the order. See the *Orders* section for more information.
|
* Editing order view. View where the user can change the details of the order. See the *Orders* section for more information.
|
||||||
* Advanced resource allocation view. View where the user can allocate resources including advanced options: choosing hours per day or the allocated functions to be carried out. See the *Resource allocation* section for more information.
|
* Advanced resource allocation view. View where the user can allocate resources including advanced options: choosing hours per day or the allocated functions to be carried out. See the *Resource allocation* section for more information.
|
||||||
|
|
||||||
What makes NavalPlan useful?
|
What makes NavalPlan useful?
|
||||||
============================
|
============================
|
||||||
|
|
||||||
NavalPlan is an application that has been developed as a general purpose planning tool. It is based on a series of concepts discovered by analysing problems in industrial project planning that were not fully covered by any existing planning tool. Also the motivations for the development of NavalPlan were based on providing a free software alternative, and completely web, for existing privative plannig tools.
|
NavalPlan is an application that has been developed as a general purpose planning tool. It is based on a series of concepts discovered by analysing problems in industrial project planning that were not fully covered by any existing planning tool. Also the motivations for the development of NavalPlan were based on providing a free software alternative, and completely web, for existing privative plannig tools.
|
||||||
|
|
||||||
The essential concepts used for the program are as follows:
|
The essential concepts used for the program are as follows:
|
||||||
|
|
||||||
* Company and multi-project overview: NavalPlan is a program that has been developed specifically to provide information about projects that are being carried out in a company to users, therefore it is a multi-project program. It was decided that the program's focus would not be individual to each project. However, it is also possible to have several specific views, individual projects among them.
|
* Company and multi-project overview: NavalPlan is a program that has been developed specifically to provide information about projects that are being carried out in a company to users, therefore it is a multi-project program. It was decided that the program's focus would not be individual to each project. However, it is also possible to have several specific views, individual projects among them.
|
||||||
* View management: The company overview or multi-project view comes with the views on the information that is stored. For example, the company overview enables users to view orders and compare their status, view the company's general resource load and process orders. Users can also view the planning, the resource load, the advanced resource allocation view and the editing order view on the project view.
|
* View management: The company overview or multi-project view comes with the views on the information that is stored. For example, the company overview enables users to view orders and compare their status, view the company's general resource load and process orders. Users can also view the planning, the resource load, the advanced resource allocation view and the editing order view on the project view.
|
||||||
* Criteria: Criteria are a system entity that enables resources (both humans and machines) and tasks to be classified. Resources must fulfil criteria and tasks require criteria to be fulfilled. These are one of the program's most important aspects, as criteria are the basis of generic allocation in the program and resolve one of the most important problems for the sector: the long time taken in human resources and the difficulty in having long-term company load estimations.
|
* Criteria: Criteria are a system entity that enables resources (both humans and machines) and tasks to be classified. Resources must fulfil criteria and tasks require criteria to be fulfilled. These are one of the program's most important aspects, as criteria are the basis of generic allocation in the program and resolve one of the most important problems for the sector: the long time taken in human resources and the difficulty in having long-term company load estimations.
|
||||||
* Resources: There are two different kinds: humans and machines. Human resources are workers in a company that are used to plan, monitor and control the company's load. On the other hand, machines, dependent on the people that manage them, are resources that act in a similar way to human resources.
|
* Resources: There are two different kinds: humans and machines. Human resources are workers in a company that are used to plan, monitor and control the company's load. On the other hand, machines, dependent on the people that manage them, are resources that act in a similar way to human resources.
|
||||||
* Resource allocation: One of the key points of the program is having the possibility of two kinds of designation: specific and generic. Generic allocation is based on criteria that are required to carry out a task and must be fulfilled by resources that are capable of performing them. In order to understand generic allocation, the following case must be understood: John Smith is a welder. Generally, John Smith is allocated to the planned task, but "NavalPlan" offers the possibility of choosing a resource in general among welders in the company, not worrying if John Smith is the person who has been allocated the task.
|
* Resource allocation: One of the key points of the program is having the possibility of two kinds of designation: specific and generic. Generic allocation is based on criteria that are required to carry out a task and must be fulfilled by resources that are capable of performing them. In order to understand generic allocation, the following case must be understood: John Smith is a welder. Generally, John Smith is allocated to the planned task, but "NavalPlan" offers the possibility of choosing a resource in general among welders in the company, not worrying if John Smith is the person who has been allocated the task.
|
||||||
* Company load control: The program offers the possibility of controlling the company's resource load easily. The control is carried out in the mid and long term as current projects and future projects can be managed by the program. "NavalPlan" has graphics that indicate the use of resources.
|
* Company load control: The program offers the possibility of controlling the company's resource load easily. The control is carried out in the mid and long term as current projects and future projects can be managed by the program. "NavalPlan" has graphics that indicate the use of resources.
|
||||||
* Labels: These are elements that are used to label project tasks. With these labels, the user of the program can group tasks together according to concept, which can then be checked at a later date as a group or after being filtered.
|
* Labels: These are elements that are used to label project tasks. With these labels, the user of the program can group tasks together according to concept, which can then be checked at a later date as a group or after being filtered.
|
||||||
* Filters: As the system naturally has elements that label or characterise tasks and resources, criteria filters or labels can be used. This is very useful to check categorised information or to get specific reports based on criteria or labels.
|
* Filters: As the system naturally has elements that label or characterise tasks and resources, criteria filters or labels can be used. This is very useful to check categorised information or to get specific reports based on criteria or labels.
|
||||||
* Calendars: Calendars determine the available productive hours for different resources. The user may create general calendars for the company or input characteristics for more specific calendars, meaning that calendars for resources and tasks can be made.
|
* Calendars: Calendars determine the available productive hours for different resources. The user may create general calendars for the company or input characteristics for more specific calendars, meaning that calendars for resources and tasks can be made.
|
||||||
* Orders and order elements: Work requested by clients is treated by the application as an order, which is structured in order elements. The order and its elements adhere to a hierarchical structure of *x* levels. This element tree is the basis when planning work.
|
* Orders and order elements: Work requested by clients is treated by the application as an order, which is structured in order elements. The order and its elements adhere to a hierarchical structure of *x* levels. This element tree is the basis when planning work.
|
||||||
* Progress: The program can manage several kinds of progress. A project can be measured in a percentage that indicates its progress and also in units, the agreed budget, etc. Deciding what kind of progress is to be used to compare progress at upper stages of the project is the responsibility of the person who is managing the planning.
|
* Progress: The program can manage several kinds of progress. A project can be measured in a percentage that indicates its progress and also in units, the agreed budget, etc. Deciding what kind of progress is to be used to compare progress at upper stages of the project is the responsibility of the person who is managing the planning.
|
||||||
* Tasks: Tasks are the program's planning elements. They are used to programme works that are to be carried out. The most important characteristics of the tasks are: They have dependencies among themselves and may require criteria to be fulfilled in order to allocate resources.
|
* Tasks: Tasks are the program's planning elements. They are used to programme works that are to be carried out. The most important characteristics of the tasks are: They have dependencies among themselves and may require criteria to be fulfilled in order to allocate resources.
|
||||||
* Work reports: These are the reports of the companies' workers, which indicate the hours worked and also the tasks allocated to the hours a worker has worked. With this information, the system can calculate how many hours it took to complete a task in relation to the total number of hours that were budgeted. Progress can be compared with the use of actual hours.
|
* Work reports: These are the reports of the companies' workers, which indicate the hours worked and also the tasks allocated to the hours a worker has worked. With this information, the system can calculate how many hours it took to complete a task in relation to the total number of hours that were budgeted. Progress can be compared with the use of actual hours.
|
||||||
|
|
||||||
On top of the functions offered by the program, there are other features that make it stand out from similar programs:
|
On top of the functions offered by the program, there are other features that make it stand out from similar programs:
|
||||||
|
|
||||||
* Integration with ERP: The program imports information directly from companies' ERPs for orders, human resources, work reports and specific criteria.
|
* Integration with ERP: The program imports information directly from companies' ERPs for orders, human resources, work reports and specific criteria.
|
||||||
* Version management: The program can manage different planning versions and, at the same time, still allows users to check the information on every version.
|
* Version management: The program can manage different planning versions and, at the same time, still allows users to check the information on every version.
|
||||||
* History management: The program does not erase information, it only makes it invalid, so users can check older information using date filters.
|
* History management: The program does not erase information, it only makes it invalid, so users can check older information using date filters.
|
||||||
|
|
||||||
Usability conventions
|
Usability conventions
|
||||||
==========================
|
==========================
|
||||||
|
|
||||||
Information about forms
|
Information about forms
|
||||||
---------------------------------
|
---------------------------------
|
||||||
Before describing the various functions associated with the most important modules, we need to give a general explanation on how to browse and the forms.
|
Before describing the various functions associated with the most important modules, we need to give a general explanation on how to browse and the forms.
|
||||||
|
|
||||||
Essentially, there are 3 kinds of editing forms:
|
Essentially, there are 3 kinds of editing forms:
|
||||||
|
|
||||||
* Forms with a *Return* button. These forms are part of a wider picture and the changes that are made are stored in the memory. The changes are only applied when the user explicitly stores all the details on the screen from which the form came.
|
* Forms with a *Return* button. These forms are part of a wider picture and the changes that are made are stored in the memory. The changes are only applied when the user explicitly stores all the details on the screen from which the form came.
|
||||||
* Forms with the *Save* and *Close* buttons. These forms enable 2 operations to take place. The first one stores and closes the current window and the second one closes without saving the changes.
|
* Forms with the *Save* and *Close* buttons. These forms enable 2 operations to take place. The first one stores and closes the current window and the second one closes without saving the changes.
|
||||||
* Forms with the *Save and continue*, "Save" and "Close" buttons. These forms enable 3 operations to take place. The first one stores and continues the current form. The second one stores and closes the form. Lastly, the third one closes the window without storing changes.
|
* Forms with the *Save and continue*, "Save" and "Close" buttons. These forms enable 3 operations to take place. The first one stores and continues the current form. The second one stores and closes the form. Lastly, the third one closes the window without storing changes.
|
||||||
|
|
||||||
Standard icons and buttons
|
Standard icons and buttons
|
||||||
--------------------------
|
--------------------------
|
||||||
|
|
||||||
* Editing: In general, editing records in the program may be done by clicking on an icon consisting of a pencil on a white notebook.
|
* Editing: In general, editing records in the program may be done by clicking on an icon consisting of a pencil on a white notebook.
|
||||||
* Left indent: In general, these operations are needed for elements of a tree that intend to move into internal levels. This operation may be done by clicking the icon consisting of a green arrow pointing right.
|
* Left indent: In general, these operations are needed for elements of a tree that intend to move into internal levels. This operation may be done by clicking the icon consisting of a green arrow pointing right.
|
||||||
* Right indent: In general, these operations are needed for elements of a tree that intend to move from internal to external levels. This operation may be done by clicking the icon consisting of a green arrow pointing left.
|
* Right indent: In general, these operations are needed for elements of a tree that intend to move from internal to external levels. This operation may be done by clicking the icon consisting of a green arrow pointing left.
|
||||||
* Erasing: Users can erase information by clicking on the paper basket icon.
|
* Erasing: Users can erase information by clicking on the paper basket icon.
|
||||||
* Search: The magnifying glass is the icon that indicates that the text entry to the left is intended for searching for elements.
|
* Search: The magnifying glass is the icon that indicates that the text entry to the left is intended for searching for elements.
|
||||||
|
|
||||||
Tabs
|
Tabs
|
||||||
--------
|
--------
|
||||||
The program will have content editing and administration forms, which will be represented by graphic components based on tabs. This method is used to organise information from a comprehensive form into different sections that can be accessed by clicking on the names of the different tabs, the others keeping their status. In all cases, the save and cancel options affect the group of sub-forms on the different tabs.
|
The program will have content editing and administration forms, which will be represented by graphic components based on tabs. This method is used to organise information from a comprehensive form into different sections that can be accessed by clicking on the names of the different tabs, the others keeping their status. In all cases, the save and cancel options affect the group of sub-forms on the different tabs.
|
||||||
|
|
||||||
Explicit actions and context help
|
Explicit actions and context help
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
The program contains components that provide additional descriptions about the element when hovering over them for one second.
|
The program contains components that provide additional descriptions about the element when hovering over them for one second.
|
||||||
The actions the user may carry out in the program are stated on the button tabs and in the help texts about them, the browsing menu options and the options on the context menus that open out when right clicking on the planner area.
|
The actions the user may carry out in the program are stated on the button tabs and in the help texts about them, the browsing menu options and the options on the context menus that open out when right clicking on the planner area.
|
||||||
Furthermore, short cuts are given for the main operations by double clicking the listed elements or by associating key events with cursors and the enter key, which is how to add elements when moving through the forms.
|
Furthermore, short cuts are given for the main operations by double clicking the listed elements or by associating key events with cursors and the enter key, which is how to add elements when moving through the forms.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,62 +1,62 @@
|
||||||
Criteria
|
Criteria
|
||||||
#########
|
#########
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
Criteria are elements that are used in the program to categorise resources and tasks. Tasks need criteria and the resources fulfil them. The following sequence is an example of how to use criteria: A resource is designated the criterion of "welder" (that is the resource fulfils the "welder" category) and a task requires the "welder" criterion to be carried out. As a result, when resources are allocated to tasks, workers with the "welder" criterion are used when allocating resources generically (not applicable to specific allocation). See the chapter on allocating resources to find out more about the different kinds of allocation.
|
Criteria are elements that are used in the program to categorise resources and tasks. Tasks need criteria and the resources fulfil them. The following sequence is an example of how to use criteria: A resource is designated the criterion of "welder" (that is the resource fulfils the "welder" category) and a task requires the "welder" criterion to be carried out. As a result, when resources are allocated to tasks, workers with the "welder" criterion are used when allocating resources generically (not applicable to specific allocation). See the chapter on allocating resources to find out more about the different kinds of allocation.
|
||||||
|
|
||||||
Several operations can be carried out with criteria in the program:
|
Several operations can be carried out with criteria in the program:
|
||||||
|
|
||||||
* Criteria administration
|
* Criteria administration
|
||||||
* Allocation of criteria to resources.
|
* Allocation of criteria to resources.
|
||||||
* Allocation of criteria to tasks.
|
* Allocation of criteria to tasks.
|
||||||
* Filtering entities according to criteria. Tasks and order items can be filtered according to criteria to carry out operations in the program.
|
* Filtering entities according to criteria. Tasks and order items can be filtered according to criteria to carry out operations in the program.
|
||||||
|
|
||||||
Only the first function out of the three described above will be explained in this section. The two kinds of allocation will be dealt with later, the allocation of resources in the chapter on "Resource management" and the filtering function in the chapter on "Task planning".
|
Only the first function out of the three described above will be explained in this section. The two kinds of allocation will be dealt with later, the allocation of resources in the chapter on "Resource management" and the filtering function in the chapter on "Task planning".
|
||||||
|
|
||||||
|
|
||||||
Criteria administration
|
Criteria administration
|
||||||
===========================
|
===========================
|
||||||
Criteria administration can be accessed from the administration menu:
|
Criteria administration can be accessed from the administration menu:
|
||||||
|
|
||||||
.. figure:: images/menu.png
|
.. figure:: images/menu.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
First level menu tabs
|
First level menu tabs
|
||||||
|
|
||||||
The specific operation to manage criteria is *Manage criteria*. The criteria available in the system can be listed by using this operation.
|
The specific operation to manage criteria is *Manage criteria*. The criteria available in the system can be listed by using this operation.
|
||||||
|
|
||||||
.. figure:: images/lista-criterios.png
|
.. figure:: images/lista-criterios.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
List of criteria
|
List of criteria
|
||||||
|
|
||||||
The create/edit criterion form can be accessed by clicking on the *Create* button. A criterion can be edited by clicking on the edit icon.
|
The create/edit criterion form can be accessed by clicking on the *Create* button. A criterion can be edited by clicking on the edit icon.
|
||||||
|
|
||||||
.. figure:: images/edicion-criterio.png
|
.. figure:: images/edicion-criterio.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Editing criteria
|
Editing criteria
|
||||||
|
|
||||||
The following operations can be carried out using the criteria editing form shown in the previous image:
|
The following operations can be carried out using the criteria editing form shown in the previous image:
|
||||||
|
|
||||||
* Editing the name of the criterion
|
* Editing the name of the criterion
|
||||||
* Indicating whether several values can be allocated at the same time or just one element for the kind of criterion selected. For example, a resource that fulfils two criteria, welder and lathe operator.
|
* Indicating whether several values can be allocated at the same time or just one element for the kind of criterion selected. For example, a resource that fulfils two criteria, welder and lathe operator.
|
||||||
* Indicating the kind of criteria:
|
* Indicating the kind of criteria:
|
||||||
|
|
||||||
* Generic kind: A criterion that may be used for machines or workers alike.
|
* Generic kind: A criterion that may be used for machines or workers alike.
|
||||||
* Worker kind: A criterion that may be used only for a worker.
|
* Worker kind: A criterion that may be used only for a worker.
|
||||||
* Machine kind: A criterion that may be used only for a machine.
|
* Machine kind: A criterion that may be used only for a machine.
|
||||||
|
|
||||||
* Indicating whether the criterion is hierarchical or not. Sometimes criteria must be treated hierarchically, for example, the fact that a criterion has been allocated to an element does not mean that this criterion is automatically allocated to issues that stem from it. A clear example of criteria hierarchy is the location criterion as it is hierarchical, for example, a person who has designated Galicia as their location will belong to Spain.
|
* Indicating whether the criterion is hierarchical or not. Sometimes criteria must be treated hierarchically, for example, the fact that a criterion has been allocated to an element does not mean that this criterion is automatically allocated to issues that stem from it. A clear example of criteria hierarchy is the location criterion as it is hierarchical, for example, a person who has designated Galicia as their location will belong to Spain.
|
||||||
* Indicating whether the criterion is authorised or not. This is the way users erase criteria. As a criterion cannot be changed once it has been created and used in historic data, the criterion must be on the system. It can be invalidated to avoid the criterion from appearing in different selection elements.
|
* Indicating whether the criterion is authorised or not. This is the way users erase criteria. As a criterion cannot be changed once it has been created and used in historic data, the criterion must be on the system. It can be invalidated to avoid the criterion from appearing in different selection elements.
|
||||||
* Describing the criterion.
|
* Describing the criterion.
|
||||||
* Adding new values. A text entry with the *New criterion* button is on the second part of the form.
|
* Adding new values. A text entry with the *New criterion* button is on the second part of the form.
|
||||||
* Editing the name of existing criteria.
|
* Editing the name of existing criteria.
|
||||||
* Moving the criteria up or down the list of current criteria.
|
* Moving the criteria up or down the list of current criteria.
|
||||||
* Removing a criteria value from the list.
|
* Removing a criteria value from the list.
|
||||||
|
|
||||||
The criteria administration form responds to the characteristics of the forms described in the introduction as 3 operations (save, save and close, and close).
|
The criteria administration form responds to the characteristics of the forms described in the introduction as 3 operations (save, save and close, and close).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,302 +1,302 @@
|
||||||
Orders and order elements
|
Orders and order elements
|
||||||
##############################
|
##############################
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
Orders describe the work to be carried out by the users who use the program.
|
Orders describe the work to be carried out by the users who use the program.
|
||||||
Each order corresponds with the projects that the companies are going to offer their clients.
|
Each order corresponds with the projects that the companies are going to offer their clients.
|
||||||
|
|
||||||
An order consists of one or several order lines. Each order line corresponds with the planning the works on the order should follow when being implemented. Order lines are organised hierarchically without any limitations on depth. The fact that order lines are organised hierarchically shows how several inheritable features work, such as labels.
|
An order consists of one or several order lines. Each order line corresponds with the planning the works on the order should follow when being implemented. Order lines are organised hierarchically without any limitations on depth. The fact that order lines are organised hierarchically shows how several inheritable features work, such as labels.
|
||||||
|
|
||||||
The following sections will describe the operations that users can carry out with orders and order lines.
|
The following sections will describe the operations that users can carry out with orders and order lines.
|
||||||
|
|
||||||
Order
|
Order
|
||||||
======
|
======
|
||||||
|
|
||||||
An order is a project or work that a client requests from a company. The order for the planned works identifies the project in the company. The difference with comprehensive management programs such as "NavalPlan" is that they only need to use certain order details. These details are:
|
An order is a project or work that a client requests from a company. The order for the planned works identifies the project in the company. The difference with comprehensive management programs such as "NavalPlan" is that they only need to use certain order details. These details are:
|
||||||
|
|
||||||
* Order name
|
* Order name
|
||||||
* Order code
|
* Order code
|
||||||
* Total amount of order
|
* Total amount of order
|
||||||
* Estimated start date
|
* Estimated start date
|
||||||
* End date
|
* End date
|
||||||
* Person in charge
|
* Person in charge
|
||||||
* Description
|
* Description
|
||||||
* Assigned calendar
|
* Assigned calendar
|
||||||
* Automatic generation of codes. A field used to instruct the system to automatically generate order element and hour group codes.
|
* Automatic generation of codes. A field used to instruct the system to automatically generate order element and hour group codes.
|
||||||
* Preference between dependencies and restrictions. Users can choose dependencies or restrictions as priorities when applied in the event of conflict.
|
* Preference between dependencies and restrictions. Users can choose dependencies or restrictions as priorities when applied in the event of conflict.
|
||||||
|
|
||||||
However, the actual order has other entities that make it more complete:
|
However, the actual order has other entities that make it more complete:
|
||||||
|
|
||||||
* Hours assigned to the order
|
* Hours assigned to the order
|
||||||
* Progress attributed to the order
|
* Progress attributed to the order
|
||||||
* Labels
|
* Labels
|
||||||
* Criteria assigned to the order
|
* Criteria assigned to the order
|
||||||
* Materials
|
* Materials
|
||||||
* Quality forms
|
* Quality forms
|
||||||
|
|
||||||
Editing or creating an order can be carried out from various locations in the program:
|
Editing or creating an order can be carried out from various locations in the program:
|
||||||
|
|
||||||
* From the "order list" in the company overview.
|
* From the "order list" in the company overview.
|
||||||
|
|
||||||
* Editing is carried out by clicking the edit button on the chosen order.
|
* Editing is carried out by clicking the edit button on the chosen order.
|
||||||
* Creating a new order is carried out by clicking "New order".
|
* Creating a new order is carried out by clicking "New order".
|
||||||
|
|
||||||
* From an order in the Gantt chart and changing to the order details view.
|
* From an order in the Gantt chart and changing to the order details view.
|
||||||
|
|
||||||
|
|
||||||
Users can access the following tabs from the editing order option:
|
Users can access the following tabs from the editing order option:
|
||||||
|
|
||||||
* Editing order details. Users can edit basic order details on this screen. Currently these are:
|
* Editing order details. Users can edit basic order details on this screen. Currently these are:
|
||||||
|
|
||||||
* Name
|
* Name
|
||||||
* Code
|
* Code
|
||||||
* Estimated start date
|
* Estimated start date
|
||||||
* End date
|
* End date
|
||||||
* Person in charge
|
* Person in charge
|
||||||
* Client
|
* Client
|
||||||
* Description
|
* Description
|
||||||
|
|
||||||
.. figure:: images/order-edition.png
|
.. figure:: images/order-edition.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Editing orders
|
Editing orders
|
||||||
|
|
||||||
* Order element list. Users can carry out several operations from the order element list:
|
* Order element list. Users can carry out several operations from the order element list:
|
||||||
|
|
||||||
* Creating new order elements.
|
* Creating new order elements.
|
||||||
* Raising an order element in the hierarchy by one level.
|
* Raising an order element in the hierarchy by one level.
|
||||||
* Lowering an order element in the hierarchy by one level.
|
* Lowering an order element in the hierarchy by one level.
|
||||||
* Indenting an order element, which is the same as moving it down the hierarchy, by changing the element's level.
|
* Indenting an order element, which is the same as moving it down the hierarchy, by changing the element's level.
|
||||||
* Unindenting an order element, which is the same as moving it up the hierarchy, by changing the element's level.
|
* Unindenting an order element, which is the same as moving it up the hierarchy, by changing the element's level.
|
||||||
* Filtering order elements.
|
* Filtering order elements.
|
||||||
* Deleting order elements.
|
* Deleting order elements.
|
||||||
* Moving an element in the hierarchy by dragging and dropping.
|
* Moving an element in the hierarchy by dragging and dropping.
|
||||||
|
|
||||||
.. figure:: images/order-elements-list.png
|
.. figure:: images/order-elements-list.png
|
||||||
:scale: 40
|
:scale: 40
|
||||||
|
|
||||||
Order element list
|
Order element list
|
||||||
|
|
||||||
* Assigned hours. A screen that shows the total hours attributed to a project, consisting of a viewing screen where the hours entered in the order elements are grouped.
|
* Assigned hours. A screen that shows the total hours attributed to a project, consisting of a viewing screen where the hours entered in the order elements are grouped.
|
||||||
|
|
||||||
.. figure:: images/order-assigned-hours.png
|
.. figure:: images/order-assigned-hours.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Assigning hours attributed to the order by the workers
|
Assigning hours attributed to the order by the workers
|
||||||
|
|
||||||
* Progress. A screen where users can attribute types of progress and progress measurements relating to the order. See the "Progress" section to find out how it works.
|
* Progress. A screen where users can attribute types of progress and progress measurements relating to the order. See the "Progress" section to find out how it works.
|
||||||
|
|
||||||
* Labels. A screen where users can assign labels to an order and identify previously assigned direct and indirect labels. See the following order element editing section for an in-depth description of the label management procedure.
|
* Labels. A screen where users can assign labels to an order and identify previously assigned direct and indirect labels. See the following order element editing section for an in-depth description of the label management procedure.
|
||||||
|
|
||||||
.. figure:: images/order-labels.png
|
.. figure:: images/order-labels.png
|
||||||
:scale: 35
|
:scale: 35
|
||||||
|
|
||||||
Order labels
|
Order labels
|
||||||
|
|
||||||
* Criteria. A screen where users can assign the criteria they want to apply to all the tasks on an order. These criteria will be applied automatically to all order elements, except those that were explicitly invalidated. The hour groups of order elements, which are grouped by criteria, can also be viewed, enabling users to identify the criteria required for an order.
|
* Criteria. A screen where users can assign the criteria they want to apply to all the tasks on an order. These criteria will be applied automatically to all order elements, except those that were explicitly invalidated. The hour groups of order elements, which are grouped by criteria, can also be viewed, enabling users to identify the criteria required for an order.
|
||||||
|
|
||||||
.. figure:: images/order-criterions.png
|
.. figure:: images/order-criterions.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Order criteria
|
Order criteria
|
||||||
|
|
||||||
* Materials. A screen where users can assign available material to orders. The material can be selected from among the material categories available in the program. Materials are managed in the following way:
|
* Materials. A screen where users can assign available material to orders. The material can be selected from among the material categories available in the program. Materials are managed in the following way:
|
||||||
|
|
||||||
* Users select the tab shown in the lower part of the screen called "Search materials".
|
* Users select the tab shown in the lower part of the screen called "Search materials".
|
||||||
* Users can enter text to search for materials or select the categories for which they want materials.
|
* Users can enter text to search for materials or select the categories for which they want materials.
|
||||||
* The system then filters the results.
|
* The system then filters the results.
|
||||||
* Users select the materials they want (users can select more than one material on the list by pressing the "Ctrl" button).
|
* Users select the materials they want (users can select more than one material on the list by pressing the "Ctrl" button).
|
||||||
* Users then click "Assign".
|
* Users then click "Assign".
|
||||||
* The system then shows the list of materials that has already been assigned to the order.
|
* The system then shows the list of materials that has already been assigned to the order.
|
||||||
* Users select the units and the status they want to assign to the order.
|
* Users select the units and the status they want to assign to the order.
|
||||||
* Users then click "Save" or "Save and continue".
|
* Users then click "Save" or "Save and continue".
|
||||||
* If users want to manage the receipt of the material, they can click "Divide" to change the status of a partial quantity of material.
|
* If users want to manage the receipt of the material, they can click "Divide" to change the status of a partial quantity of material.
|
||||||
|
|
||||||
.. figure:: images/order-material.png
|
.. figure:: images/order-material.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Material associated with an order
|
Material associated with an order
|
||||||
|
|
||||||
* Quality. Users can assign a quality form to the order, which would then be completed to ensure that certain activities associated with the order are carried out. See the following section on editing order elements to find out about the management procedure for quality forms.
|
* Quality. Users can assign a quality form to the order, which would then be completed to ensure that certain activities associated with the order are carried out. See the following section on editing order elements to find out about the management procedure for quality forms.
|
||||||
|
|
||||||
.. figure:: images/order-quality.png
|
.. figure:: images/order-quality.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Quality form associated with the order
|
Quality form associated with the order
|
||||||
|
|
||||||
Editing order elements
|
Editing order elements
|
||||||
==============================
|
==============================
|
||||||
|
|
||||||
Editing order elements is carried out from the "Order element list" tab by clicking the editing icon, which shows a new screen from which the user can carry out the following:
|
Editing order elements is carried out from the "Order element list" tab by clicking the editing icon, which shows a new screen from which the user can carry out the following:
|
||||||
|
|
||||||
* Edit information about the order element.
|
* Edit information about the order element.
|
||||||
* View hours attributed to order elements.
|
* View hours attributed to order elements.
|
||||||
* Manage progress of order elements.
|
* Manage progress of order elements.
|
||||||
* Manage order labels.
|
* Manage order labels.
|
||||||
* Manage criteria required by the order element.
|
* Manage criteria required by the order element.
|
||||||
* Manage materials.
|
* Manage materials.
|
||||||
* Manage quality forms.
|
* Manage quality forms.
|
||||||
|
|
||||||
The following subsections describe each one of the operations in depth.
|
The following subsections describe each one of the operations in depth.
|
||||||
|
|
||||||
Editing information about the order element
|
Editing information about the order element
|
||||||
------------------------------------------------
|
------------------------------------------------
|
||||||
|
|
||||||
Editing information about the order element includes the editing of the following details:
|
Editing information about the order element includes the editing of the following details:
|
||||||
|
|
||||||
* Order element name.
|
* Order element name.
|
||||||
* Order element code.
|
* Order element code.
|
||||||
* Start date of the order element.
|
* Start date of the order element.
|
||||||
* Estimated end date of the order element.
|
* Estimated end date of the order element.
|
||||||
* Total hours of the order element. These hours can be calculated from the added hour groups or entered directly into this section, in which the hours have been distributed among the hour groups, and a new one created if the percentages do not coincide with initial percentages.
|
* Total hours of the order element. These hours can be calculated from the added hour groups or entered directly into this section, in which the hours have been distributed among the hour groups, and a new one created if the percentages do not coincide with initial percentages.
|
||||||
* **Hour groups**: It is possible to add one or several hour groups to the order element. **The purpose of these hour groups** is to establish the requirements of the resources that will be assigned to carry them out.
|
* **Hour groups**: It is possible to add one or several hour groups to the order element. **The purpose of these hour groups** is to establish the requirements of the resources that will be assigned to carry them out.
|
||||||
* Criteria: It is possible to add criteria that must be fulfilled to enable generic assignment to carry out the order element.
|
* Criteria: It is possible to add criteria that must be fulfilled to enable generic assignment to carry out the order element.
|
||||||
|
|
||||||
.. figure:: images/order-element-edition.png
|
.. figure:: images/order-element-edition.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Editing order elements
|
Editing order elements
|
||||||
|
|
||||||
Viewing hours attributed to order elements
|
Viewing hours attributed to order elements
|
||||||
------------------------------------------------------
|
------------------------------------------------------
|
||||||
|
|
||||||
The "Assigned hours" tab enables users to view the work reports associated with an order element and also how many of the estimated hours have already been carried out.
|
The "Assigned hours" tab enables users to view the work reports associated with an order element and also how many of the estimated hours have already been carried out.
|
||||||
|
|
||||||
.. figure:: images/order-element-hours.png
|
.. figure:: images/order-element-hours.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Hours assigned to order elements
|
Hours assigned to order elements
|
||||||
|
|
||||||
The screen is divided into two parts:
|
The screen is divided into two parts:
|
||||||
|
|
||||||
* Work report list: Users can view the list of work reports that are associated with an order element in order to check the date and time, resource and number of hours devoted to the task.
|
* Work report list: Users can view the list of work reports that are associated with an order element in order to check the date and time, resource and number of hours devoted to the task.
|
||||||
* Use of estimated hours: The system calculates the total number of hours devoted to a task and compares them with the estimated hours.
|
* Use of estimated hours: The system calculates the total number of hours devoted to a task and compares them with the estimated hours.
|
||||||
|
|
||||||
Managing progress of order elements
|
Managing progress of order elements
|
||||||
---------------------------------------------
|
---------------------------------------------
|
||||||
|
|
||||||
Entering types of progress and the management of order element progress has been described in the "Progress" chapter.
|
Entering types of progress and the management of order element progress has been described in the "Progress" chapter.
|
||||||
|
|
||||||
Managing order labels
|
Managing order labels
|
||||||
------------------------------
|
------------------------------
|
||||||
|
|
||||||
Labels, as described in the chapter on labels, enable users to categorise order elements. Consequently, users can group planning or order information based on them.
|
Labels, as described in the chapter on labels, enable users to categorise order elements. Consequently, users can group planning or order information based on them.
|
||||||
|
|
||||||
Users can assign labels directly to an order element or even to a previous order element in the hierarchy. From the moment a label from one of the two previous methods is assigned, the order element and the related planning task are associated with the label, and used for subsequent filtering.
|
Users can assign labels directly to an order element or even to a previous order element in the hierarchy. From the moment a label from one of the two previous methods is assigned, the order element and the related planning task are associated with the label, and used for subsequent filtering.
|
||||||
|
|
||||||
.. figure:: images/order-element-tags.png
|
.. figure:: images/order-element-tags.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Assigning labels for order elements
|
Assigning labels for order elements
|
||||||
|
|
||||||
As can be seen in the image, users can carry out the following procedures from the **labels** tab:
|
As can be seen in the image, users can carry out the following procedures from the **labels** tab:
|
||||||
|
|
||||||
* View the labels associated with an order element that were inherited from an order element that was higher in the hierarchy than the one that was directly assigned. The planning task associated with each order element has the same associated labels.
|
* View the labels associated with an order element that were inherited from an order element that was higher in the hierarchy than the one that was directly assigned. The planning task associated with each order element has the same associated labels.
|
||||||
* View labels that are directly associated with an order element by means of the following assignment form for lower-level labels.
|
* View labels that are directly associated with an order element by means of the following assignment form for lower-level labels.
|
||||||
* Assign existing labels: Users can assign labels by searching for a particular one from among the available labels on the form that is lower than the direct label list. To search for a label, users can click the magnifying glass icon or write the first letters of the label in the text box so that the system can show the available options.
|
* Assign existing labels: Users can assign labels by searching for a particular one from among the available labels on the form that is lower than the direct label list. To search for a label, users can click the magnifying glass icon or write the first letters of the label in the text box so that the system can show the available options.
|
||||||
* Create and assign new labels: Users can create new labels associated with a type of existing label from this form. In order to carry out the procedure, it is necessary to select a type of label to be associated and then enter the value of the label for the type selected. The system creates the label automatically and assigns the order element when "Create and assign" is clicked.
|
* Create and assign new labels: Users can create new labels associated with a type of existing label from this form. In order to carry out the procedure, it is necessary to select a type of label to be associated and then enter the value of the label for the type selected. The system creates the label automatically and assigns the order element when "Create and assign" is clicked.
|
||||||
|
|
||||||
|
|
||||||
Managing criteria required by the order element and hour groups
|
Managing criteria required by the order element and hour groups
|
||||||
--------------------------------------------------------------------------------
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
Both an order and an order element can be assigned criteria that need to be fulfilled for it to be carried out. Criteria can be direct or indirect:
|
Both an order and an order element can be assigned criteria that need to be fulfilled for it to be carried out. Criteria can be direct or indirect:
|
||||||
|
|
||||||
* Direct criteria: These are assigned directly to the order element. They are criteria that are required by the hour groups on the order element.
|
* Direct criteria: These are assigned directly to the order element. They are criteria that are required by the hour groups on the order element.
|
||||||
* Indirect criteria: These are assigned on order elements that are higher in the hierarchy and are inherited by the element that is being edited.
|
* Indirect criteria: These are assigned on order elements that are higher in the hierarchy and are inherited by the element that is being edited.
|
||||||
|
|
||||||
Apart from the required criterion, one or various hour groups that are part of the order element can be defined. It all depends on whether the order element contains other order elements as child nodes or if it is a leaf node. In the first case the information about hours and hour groups can only be viewed, but leaf nodes can be edited. The latter case works as follows:
|
Apart from the required criterion, one or various hour groups that are part of the order element can be defined. It all depends on whether the order element contains other order elements as child nodes or if it is a leaf node. In the first case the information about hours and hour groups can only be viewed, but leaf nodes can be edited. The latter case works as follows:
|
||||||
|
|
||||||
* The system creates an hour group by default, which is associated to the order element. The details that can be modified for an hour group are:
|
* The system creates an hour group by default, which is associated to the order element. The details that can be modified for an hour group are:
|
||||||
|
|
||||||
* Code for the hour group if it is not automatically generated.
|
* Code for the hour group if it is not automatically generated.
|
||||||
* Type of criterion. Users can choose to assign a machine or worker criterion.
|
* Type of criterion. Users can choose to assign a machine or worker criterion.
|
||||||
* Number of hours in the hour group.
|
* Number of hours in the hour group.
|
||||||
* List of criteria to be applied to the hour group. To add new criteria, users have to click "Add criterion" and select one from the search engine, which appears after clicking the button.
|
* List of criteria to be applied to the hour group. To add new criteria, users have to click "Add criterion" and select one from the search engine, which appears after clicking the button.
|
||||||
|
|
||||||
* Users can add new hour groups with features that are different from previous hour groups. An example of this would be when an order element must be carried out by a welder (30h) and a painter (40h).
|
* Users can add new hour groups with features that are different from previous hour groups. An example of this would be when an order element must be carried out by a welder (30h) and a painter (40h).
|
||||||
|
|
||||||
.. figure:: images/order-element-criterion.png
|
.. figure:: images/order-element-criterion.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Assigning criteria to order elements
|
Assigning criteria to order elements
|
||||||
|
|
||||||
Managing materials
|
Managing materials
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
Materials are managed in the projects as a list associated with each order line or an order in general. The list of materials is made up of the following fields:
|
Materials are managed in the projects as a list associated with each order line or an order in general. The list of materials is made up of the following fields:
|
||||||
|
|
||||||
* Code
|
* Code
|
||||||
* Date
|
* Date
|
||||||
* Units: Required units.
|
* Units: Required units.
|
||||||
* Type of unit: Type of unit used to measure the material.
|
* Type of unit: Type of unit used to measure the material.
|
||||||
* Price of the unit: Unit price.
|
* Price of the unit: Unit price.
|
||||||
* Total price: The price is calculated by multiplying the unit price by the number of units.
|
* Total price: The price is calculated by multiplying the unit price by the number of units.
|
||||||
* Category: Category to which the material belongs.
|
* Category: Category to which the material belongs.
|
||||||
* Status: Received, requested, pending, processing, cancelled.
|
* Status: Received, requested, pending, processing, cancelled.
|
||||||
|
|
||||||
Working with materials is carried out as follows:
|
Working with materials is carried out as follows:
|
||||||
|
|
||||||
* Users select the "Materials" tab on an order element.
|
* Users select the "Materials" tab on an order element.
|
||||||
* The system then shows two sub-tabs: "Materials" and "Search materials".
|
* The system then shows two sub-tabs: "Materials" and "Search materials".
|
||||||
* If the order element did not have assigned materials, the first tab will be empty.
|
* If the order element did not have assigned materials, the first tab will be empty.
|
||||||
* Users then click on "Search materials" in the lower left-hand part of the window.
|
* Users then click on "Search materials" in the lower left-hand part of the window.
|
||||||
* The system then shows the list of available categories and associated materials.
|
* The system then shows the list of available categories and associated materials.
|
||||||
|
|
||||||
.. figure:: images/order-element-material-search.png
|
.. figure:: images/order-element-material-search.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Searching material
|
Searching material
|
||||||
|
|
||||||
* Users select categories to search to refine searches for materials.
|
* Users select categories to search to refine searches for materials.
|
||||||
* The system shows the materials that belong to the selected categories.
|
* The system shows the materials that belong to the selected categories.
|
||||||
* From the materials list, users select the materials to assign to the order element.
|
* From the materials list, users select the materials to assign to the order element.
|
||||||
* Users click "Assign".
|
* Users click "Assign".
|
||||||
* The system shows the selected list of materials on the "Materials" tab with new fields to complete.
|
* The system shows the selected list of materials on the "Materials" tab with new fields to complete.
|
||||||
|
|
||||||
.. figure:: images/order-element-material-assign.png
|
.. figure:: images/order-element-material-assign.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Assigning materials to order elements
|
Assigning materials to order elements
|
||||||
|
|
||||||
* Users select the units, status and date of assigned materials.
|
* Users select the units, status and date of assigned materials.
|
||||||
|
|
||||||
For subsequent monitoring of materials, it is possible to change the status of a unit group of the received material. This procedure is carried out as follows:
|
For subsequent monitoring of materials, it is possible to change the status of a unit group of the received material. This procedure is carried out as follows:
|
||||||
|
|
||||||
* Users click the "Divide" button on the list of materials to the right of each row.
|
* Users click the "Divide" button on the list of materials to the right of each row.
|
||||||
* Users select the number of units they want the row to be divided into.
|
* Users select the number of units they want the row to be divided into.
|
||||||
* The program shows two rows with the material divided.
|
* The program shows two rows with the material divided.
|
||||||
* Users change the status of the row containing the material.
|
* Users change the status of the row containing the material.
|
||||||
|
|
||||||
The advantage of using this dividing tool is the possibility of receiving partial deliveries of material without having to wait to receive it all in order to mark it as received.
|
The advantage of using this dividing tool is the possibility of receiving partial deliveries of material without having to wait to receive it all in order to mark it as received.
|
||||||
|
|
||||||
Managing quality forms
|
Managing quality forms
|
||||||
------------------------------------
|
------------------------------------
|
||||||
|
|
||||||
Some order elements must certify that certain tasks have been carried out in order for them to be marked as complete. This is why the program has quality forms, which consist of a list of questions that can be considered important if they are answered positively.
|
Some order elements must certify that certain tasks have been carried out in order for them to be marked as complete. This is why the program has quality forms, which consist of a list of questions that can be considered important if they are answered positively.
|
||||||
|
|
||||||
It is important to mention that a quality form has to be created previously so that it can be assigned to an order element.
|
It is important to mention that a quality form has to be created previously so that it can be assigned to an order element.
|
||||||
|
|
||||||
To manage quality forms:
|
To manage quality forms:
|
||||||
|
|
||||||
* Go to the "Quality forms" tab.
|
* Go to the "Quality forms" tab.
|
||||||
|
|
||||||
.. figure:: images/order-element-quality.png
|
.. figure:: images/order-element-quality.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Assigning quality forms to order elements
|
Assigning quality forms to order elements
|
||||||
|
|
||||||
* The program has a search engine for quality forms. There are two types of quality forms: according to element or percentage.
|
* The program has a search engine for quality forms. There are two types of quality forms: according to element or percentage.
|
||||||
|
|
||||||
* Element: Every element is independent.
|
* Element: Every element is independent.
|
||||||
* Percentage: Every question increases progress in the order element by a percentage. It must be possible for percentages to be increased to 100%.
|
* Percentage: Every question increases progress in the order element by a percentage. It must be possible for percentages to be increased to 100%.
|
||||||
|
|
||||||
* Users select one of the forms created in the administration interface and click "Assign".
|
* Users select one of the forms created in the administration interface and click "Assign".
|
||||||
* The program assigns the form chosen from the list of forms assigned to the order element.
|
* The program assigns the form chosen from the list of forms assigned to the order element.
|
||||||
* Users click the "Edit" button on the order element.
|
* Users click the "Edit" button on the order element.
|
||||||
* The program displays the questions from the quality form in the lower list.
|
* The program displays the questions from the quality form in the lower list.
|
||||||
* Users mark the questions that have been carried out as achieved.
|
* Users mark the questions that have been carried out as achieved.
|
||||||
* If the quality form is based on percentages, the questions are answered in order.
|
* If the quality form is based on percentages, the questions are answered in order.
|
||||||
* If the quality form is based on elements, the questions can be answered in any order.
|
* If the quality form is based on elements, the questions can be answered in any order.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,100 +1,100 @@
|
||||||
Task planning
|
Task planning
|
||||||
#######################
|
#######################
|
||||||
|
|
||||||
.. _planificacion:
|
.. _planificacion:
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
|
|
||||||
Task planning
|
Task planning
|
||||||
=============
|
=============
|
||||||
|
|
||||||
Planning in "NavalPlan" is a process that has been described throughout all of the chapters of the user guide, the chapters on orders and the assigning of resources being particularly important in this respect. This chapter describes basic planning procedures after the order and the Gantt charts have been configured properly.
|
Planning in "NavalPlan" is a process that has been described throughout all of the chapters of the user guide, the chapters on orders and the assigning of resources being particularly important in this respect. This chapter describes basic planning procedures after the order and the Gantt charts have been configured properly.
|
||||||
|
|
||||||
.. figure:: images/planning-view.png
|
.. figure:: images/planning-view.png
|
||||||
:scale: 35
|
:scale: 35
|
||||||
|
|
||||||
Work planning view
|
Work planning view
|
||||||
|
|
||||||
As with the company overview, the project planning view is divided into several views based on the information it is analysing. The views of a specific project are:
|
As with the company overview, the project planning view is divided into several views based on the information it is analysing. The views of a specific project are:
|
||||||
|
|
||||||
* Planning view
|
* Planning view
|
||||||
* Resource load view
|
* Resource load view
|
||||||
* Order list view
|
* Order list view
|
||||||
* Advanced assignment view
|
* Advanced assignment view
|
||||||
|
|
||||||
Planning view
|
Planning view
|
||||||
----------------------
|
----------------------
|
||||||
The planning view combines three different views:
|
The planning view combines three different views:
|
||||||
|
|
||||||
* Project planning. Project planning can be viewed in the upper right-hand part of the program. It represents the planning in a Gantt chart. This is the view where users can temporarily move tasks, assign dependencies among them, define milestones and establish restrictions.
|
* Project planning. Project planning can be viewed in the upper right-hand part of the program. It represents the planning in a Gantt chart. This is the view where users can temporarily move tasks, assign dependencies among them, define milestones and establish restrictions.
|
||||||
* Resource load view. The resource load view is the image on the lower right-hand part, which shows the availability of resources according to the assignments that were carried out, as opposed to the assignments made to tasks. The information shown in the image is as follows:
|
* Resource load view. The resource load view is the image on the lower right-hand part, which shows the availability of resources according to the assignments that were carried out, as opposed to the assignments made to tasks. The information shown in the image is as follows:
|
||||||
|
|
||||||
* Purple area: Indicating a resource load under 100% of its capacity.
|
* Purple area: Indicating a resource load under 100% of its capacity.
|
||||||
* Green area: Indicating a resource load under 100%, resulting from the resource being planned for another project.
|
* Green area: Indicating a resource load under 100%, resulting from the resource being planned for another project.
|
||||||
* Orange area: Indicating a resource load over 100% as a result of the current project.
|
* Orange area: Indicating a resource load over 100% as a result of the current project.
|
||||||
* Yellow area: Indicating a resource load over 100% as a result of other projects.
|
* Yellow area: Indicating a resource load over 100% as a result of other projects.
|
||||||
|
|
||||||
* Graph view and value gained indicators. These can be viewed from the "Value gained" tab. The generated graph is based on the value gained technique and the indicators that are calculated for each of the workdays of the project. The calculated indicators are:
|
* Graph view and value gained indicators. These can be viewed from the "Value gained" tab. The generated graph is based on the value gained technique and the indicators that are calculated for each of the workdays of the project. The calculated indicators are:
|
||||||
|
|
||||||
* BCWS: accumulative time function for the number of hours planned up to a certain date. It will be 0 at the planned start of the task and the total number of planned hours at the end. As with all accumulative graphs, it will always increase. The function for a task will be the sum of the daily assignments until the calculation day. This function has values for all times, provided that resources have been assigned.
|
* BCWS: accumulative time function for the number of hours planned up to a certain date. It will be 0 at the planned start of the task and the total number of planned hours at the end. As with all accumulative graphs, it will always increase. The function for a task will be the sum of the daily assignments until the calculation day. This function has values for all times, provided that resources have been assigned.
|
||||||
* ACWP: accumulative time function for the hours attributed in the work reports up to a certain date. This function will only have a value of 0 before the date of the task's first work report and its value will continue to increase as time passes and work report hours are added. It will have no value after the date of the last work report.
|
* ACWP: accumulative time function for the hours attributed in the work reports up to a certain date. This function will only have a value of 0 before the date of the task's first work report and its value will continue to increase as time passes and work report hours are added. It will have no value after the date of the last work report.
|
||||||
* BCWP: accumulative time function that includes the resultant value of multiplying task progress by the amount of work that the task was estimated to require for completion. This function's values increase as time passes. Progress values also increase. Progress is multiplied by the total number of estimated hours for all tasks. The BCWP value is the sum of the values for the tasks that are being calculated. Progress is totalled when it is configured.
|
* BCWP: accumulative time function that includes the resultant value of multiplying task progress by the amount of work that the task was estimated to require for completion. This function's values increase as time passes. Progress values also increase. Progress is multiplied by the total number of estimated hours for all tasks. The BCWP value is the sum of the values for the tasks that are being calculated. Progress is totalled when it is configured.
|
||||||
* CV: Cost variation CV = BCWP - ACWP
|
* CV: Cost variation CV = BCWP - ACWP
|
||||||
* SV: Schedule variation SV = BCWP - BCWS
|
* SV: Schedule variation SV = BCWP - BCWS
|
||||||
* BAC: Budget at completion BAC = max (BCWS)
|
* BAC: Budget at completion BAC = max (BCWS)
|
||||||
* EAC: Estimate at completion EAC = (ACWP/ BCWP) * BAC
|
* EAC: Estimate at completion EAC = (ACWP/ BCWP) * BAC
|
||||||
* VAC: Variance at completion VAC = BAC - EAC
|
* VAC: Variance at completion VAC = BAC - EAC
|
||||||
* ETC: Estimate to complete ETC = EAC - ACWP
|
* ETC: Estimate to complete ETC = EAC - ACWP
|
||||||
* CPI: Cost performance index CPI = BCWP / ACWP
|
* CPI: Cost performance index CPI = BCWP / ACWP
|
||||||
* SPI: Schedule performance index SPI = BCWP / BCWS
|
* SPI: Schedule performance index SPI = BCWP / BCWS
|
||||||
|
|
||||||
In the project planning, users can carry out the following procedures:
|
In the project planning, users can carry out the following procedures:
|
||||||
|
|
||||||
* Assigning dependencies. Right click and choose "Add dependency" and drag the mouse pointer to the tasks that are to be assigned a dependency.
|
* Assigning dependencies. Right click and choose "Add dependency" and drag the mouse pointer to the tasks that are to be assigned a dependency.
|
||||||
|
|
||||||
* To change the type of dependency, right click on the dependency and choose the type to be assigned.
|
* To change the type of dependency, right click on the dependency and choose the type to be assigned.
|
||||||
|
|
||||||
* Creating a new milestone. Click the task before the milestone that is to be added and select the "Add milestone" option. Milestones can be moved by selecting the task with the mouse pointer and dragging it to the desired position.
|
* Creating a new milestone. Click the task before the milestone that is to be added and select the "Add milestone" option. Milestones can be moved by selecting the task with the mouse pointer and dragging it to the desired position.
|
||||||
* Moving tasks without disturbing dependencies. Right click the body of the task, and drag it to the desired position. If no restrictions or dependencies are disturbed, the system will update the daily assignment of resources to the task and place the task in the selected date.
|
* Moving tasks without disturbing dependencies. Right click the body of the task, and drag it to the desired position. If no restrictions or dependencies are disturbed, the system will update the daily assignment of resources to the task and place the task in the selected date.
|
||||||
* Assign restrictions. Click the task in question and select the "Task properties" option. A *pop-up* will appear with a "Restrictions" field that can be changed. Restrictions can conflict with dependencies, which is why each order states whether dependencies take priority or not over restrictions. The restrictions that can be established are:
|
* Assign restrictions. Click the task in question and select the "Task properties" option. A *pop-up* will appear with a "Restrictions" field that can be changed. Restrictions can conflict with dependencies, which is why each order states whether dependencies take priority or not over restrictions. The restrictions that can be established are:
|
||||||
|
|
||||||
* *As soon as possible*: Indicating that the task must start as soon as possible.
|
* *As soon as possible*: Indicating that the task must start as soon as possible.
|
||||||
* *Not before*. Indicating that the task must not start before a certain date.
|
* *Not before*. Indicating that the task must not start before a certain date.
|
||||||
* *Start on a specific date*. Indicating that the task must start on a specific date.
|
* *Start on a specific date*. Indicating that the task must start on a specific date.
|
||||||
|
|
||||||
|
|
||||||
The planning view also offers several procedures that ultimately function as viewing options:
|
The planning view also offers several procedures that ultimately function as viewing options:
|
||||||
|
|
||||||
* Zoom level: Users can choose the zoom level they require. There are several zoom levels: annual, four-monthly, monthly, weekly and daily.
|
* Zoom level: Users can choose the zoom level they require. There are several zoom levels: annual, four-monthly, monthly, weekly and daily.
|
||||||
* Search filters: Users can filter tasks based on labels or criteria.
|
* Search filters: Users can filter tasks based on labels or criteria.
|
||||||
* Critical path. As a result of using the *Dijkstra* algorithm to calculate paths on graphs, the critical path was implemented which can be viewed by clicking on the "Critical path" button from the viewing options.
|
* Critical path. As a result of using the *Dijkstra* algorithm to calculate paths on graphs, the critical path was implemented which can be viewed by clicking on the "Critical path" button from the viewing options.
|
||||||
* Show labels: Enabling users to view the labels assigned to tasks in a project, which can be viewed on screen or printed.
|
* Show labels: Enabling users to view the labels assigned to tasks in a project, which can be viewed on screen or printed.
|
||||||
* Show resources: Enabling users to view the resources assigned to tasks in a project, which can be viewed on screen or printed.
|
* Show resources: Enabling users to view the resources assigned to tasks in a project, which can be viewed on screen or printed.
|
||||||
* Print: Enabling users to print the Gantt chart being viewed at that moment.
|
* Print: Enabling users to print the Gantt chart being viewed at that moment.
|
||||||
|
|
||||||
Resource load view
|
Resource load view
|
||||||
--------------------------
|
--------------------------
|
||||||
The resource load view provides a list of resources that contains a list of tasks or criteria that generate workloads. Each task or criterion is shown as a Gantt chart so that the start and end date of the load can be seen. A different colour is shown depending on whether the resource has a load that is higher or lower than 100%:
|
The resource load view provides a list of resources that contains a list of tasks or criteria that generate workloads. Each task or criterion is shown as a Gantt chart so that the start and end date of the load can be seen. A different colour is shown depending on whether the resource has a load that is higher or lower than 100%:
|
||||||
|
|
||||||
* Green: load lower than 100%
|
* Green: load lower than 100%
|
||||||
* Orange: 100% load
|
* Orange: 100% load
|
||||||
* Red: load over 100%
|
* Red: load over 100%
|
||||||
|
|
||||||
.. figure:: images/resource-load.png
|
.. figure:: images/resource-load.png
|
||||||
:scale: 35
|
:scale: 35
|
||||||
|
|
||||||
Resource load view for a specific order
|
Resource load view for a specific order
|
||||||
|
|
||||||
If the mouse pointer is placed on the resource's Gantt chart, the load percentage for the worker will be shown.
|
If the mouse pointer is placed on the resource's Gantt chart, the load percentage for the worker will be shown.
|
||||||
|
|
||||||
Order list view
|
Order list view
|
||||||
---------------------------
|
---------------------------
|
||||||
The order list view allows users to go to the order editing and deleting options. See the "Orders" chapter for more information.
|
The order list view allows users to go to the order editing and deleting options. See the "Orders" chapter for more information.
|
||||||
|
|
||||||
|
|
||||||
Advanced assignment view
|
Advanced assignment view
|
||||||
----------------------------
|
----------------------------
|
||||||
The advanced assignment view is explained in depth in the "Resource assignment" chapter.
|
The advanced assignment view is explained in depth in the "Resource assignment" chapter.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,169 +1,169 @@
|
||||||
Assignment of resources
|
Assignment of resources
|
||||||
########################
|
########################
|
||||||
|
|
||||||
.. asigacion_
|
.. asigacion_
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
The assignment of resources is one of the program's most important features, and can be carried out in two different ways:
|
The assignment of resources is one of the program's most important features, and can be carried out in two different ways:
|
||||||
|
|
||||||
* Specific assignment.
|
* Specific assignment.
|
||||||
* Generic assignment.
|
* Generic assignment.
|
||||||
|
|
||||||
Both types of assignment are explained in the following sections.
|
Both types of assignment are explained in the following sections.
|
||||||
|
|
||||||
To carry out either of the two types of resource assignment, the following steps are necessary:
|
To carry out either of the two types of resource assignment, the following steps are necessary:
|
||||||
|
|
||||||
* Go to the planning of an order.
|
* Go to the planning of an order.
|
||||||
* Right click on the task to be planned.
|
* Right click on the task to be planned.
|
||||||
|
|
||||||
.. figure:: images/resource-assignment-planning.png
|
.. figure:: images/resource-assignment-planning.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Resource assignment menu
|
Resource assignment menu
|
||||||
|
|
||||||
* The program shows a screen in which the following information can be viewed:
|
* The program shows a screen in which the following information can be viewed:
|
||||||
|
|
||||||
* List of criteria that must be fulfilled. For each hour group, a list of hour groups is shown, each of which requires a list of criteria.
|
* List of criteria that must be fulfilled. For each hour group, a list of hour groups is shown, each of which requires a list of criteria.
|
||||||
* Task information: start and end date of the task.
|
* Task information: start and end date of the task.
|
||||||
* Type of calculation: The system allows users to choose the strategy to be used to calculate assignments:
|
* Type of calculation: The system allows users to choose the strategy to be used to calculate assignments:
|
||||||
|
|
||||||
* Calculate number of hours: This calculates the number of hours required to be devoted to the assigned resources, which are given an end date and a resource number per day.
|
* Calculate number of hours: This calculates the number of hours required to be devoted to the assigned resources, which are given an end date and a resource number per day.
|
||||||
* Calculate end date: This calculates the end date of the task based on the number of task resources and the total number of hours to finish the task.
|
* Calculate end date: This calculates the end date of the task based on the number of task resources and the total number of hours to finish the task.
|
||||||
* Calculate number of resources: This calculates the number of resources required to finish the task on a specific date and devotes a known number of hours to them.
|
* Calculate number of resources: This calculates the number of resources required to finish the task on a specific date and devotes a known number of hours to them.
|
||||||
|
|
||||||
* Recommended assignment: This option allows the program to gather criteria that must be fulfilled and the total number of hours from all hour groups, and then recommends a generic assignment. If there was a prior assignment, the system deletes it and replaces it with the new one.
|
* Recommended assignment: This option allows the program to gather criteria that must be fulfilled and the total number of hours from all hour groups, and then recommends a generic assignment. If there was a prior assignment, the system deletes it and replaces it with the new one.
|
||||||
* Assignments: A list of assignments that have been carried out. This list shows the generic assignments (the number will be the list of fulfilled criteria, and the number of hours and resources per day). Every assignment carried out can be explicitly removed by clicking the delete button.
|
* Assignments: A list of assignments that have been carried out. This list shows the generic assignments (the number will be the list of fulfilled criteria, and the number of hours and resources per day). Every assignment carried out can be explicitly removed by clicking the delete button.
|
||||||
|
|
||||||
.. figure:: images/resource-assignment.png
|
.. figure:: images/resource-assignment.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Resource assignment
|
Resource assignment
|
||||||
|
|
||||||
* Users select "Search resources".
|
* Users select "Search resources".
|
||||||
* The program shows a new screen consisting of a criteria tree and a list to the right of workers that fulfil the selected criteria:
|
* The program shows a new screen consisting of a criteria tree and a list to the right of workers that fulfil the selected criteria:
|
||||||
|
|
||||||
.. figure:: images/resource-assignment-search.png
|
.. figure:: images/resource-assignment-search.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Resource assignment search
|
Resource assignment search
|
||||||
|
|
||||||
* Users can select:
|
* Users can select:
|
||||||
|
|
||||||
* Specific assignment. See the "Specific assignment" section to find out what is involved when choosing this option.
|
* Specific assignment. See the "Specific assignment" section to find out what is involved when choosing this option.
|
||||||
* Generic assignment. See the "Generic assignment" section to find out what is involved when choosing this option.
|
* Generic assignment. See the "Generic assignment" section to find out what is involved when choosing this option.
|
||||||
|
|
||||||
* Users select a list of criteria (generic) or a list of workers (specific). A multiple-choice selection is performed by pressing the "Ctrl" button when clicking each worker/criterion.
|
* Users select a list of criteria (generic) or a list of workers (specific). A multiple-choice selection is performed by pressing the "Ctrl" button when clicking each worker/criterion.
|
||||||
|
|
||||||
* Users then click the "Select" button. It is important to remember that if a generic assignment is not marked, users need to choose a worker or machine to perform an assignment. If this is not done, it is sufficient for users to choose one or several criteria.
|
* Users then click the "Select" button. It is important to remember that if a generic assignment is not marked, users need to choose a worker or machine to perform an assignment. If this is not done, it is sufficient for users to choose one or several criteria.
|
||||||
|
|
||||||
* The program then shows the selected criteria or resource list on the list of assignments from the original resource assignment screen.
|
* The program then shows the selected criteria or resource list on the list of assignments from the original resource assignment screen.
|
||||||
|
|
||||||
* Users must choose the hours or resources per day depending on the assignment method used on the program.
|
* Users must choose the hours or resources per day depending on the assignment method used on the program.
|
||||||
|
|
||||||
|
|
||||||
Specific assignment
|
Specific assignment
|
||||||
===================
|
===================
|
||||||
|
|
||||||
This is the specific assignment of a resource to a project task, i.e. the user decides which specific "name and surname(s)" or "machine" must be assigned to a task.
|
This is the specific assignment of a resource to a project task, i.e. the user decides which specific "name and surname(s)" or "machine" must be assigned to a task.
|
||||||
|
|
||||||
Specific assignment can be carried out on the screen shown in this image:
|
Specific assignment can be carried out on the screen shown in this image:
|
||||||
|
|
||||||
|
|
||||||
.. figure:: images/asignacion-especifica.png
|
.. figure:: images/asignacion-especifica.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Specific resource assignment
|
Specific resource assignment
|
||||||
|
|
||||||
When a resource is specifically assigned, the program creates daily assignments in relation to the percentage of daily assigned resources selected, by previously comparing it with the available resource calendar. For example, an assignment of 0.5 resources for a 32-hour task means that 4 hours per day are assigned to the specific resource to fulfil the task (supposing a working calendar of 8 hours per day).
|
When a resource is specifically assigned, the program creates daily assignments in relation to the percentage of daily assigned resources selected, by previously comparing it with the available resource calendar. For example, an assignment of 0.5 resources for a 32-hour task means that 4 hours per day are assigned to the specific resource to fulfil the task (supposing a working calendar of 8 hours per day).
|
||||||
|
|
||||||
Specific machine assignment
|
Specific machine assignment
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
Specific machine assignment functions in the same way as that for workers. When a machine is assigned a task, the system stores a specific assignment of hours for the chosen machine. The main difference is that the system searches the list of assigned workers or criteria at the moment the machine is assigned:
|
Specific machine assignment functions in the same way as that for workers. When a machine is assigned a task, the system stores a specific assignment of hours for the chosen machine. The main difference is that the system searches the list of assigned workers or criteria at the moment the machine is assigned:
|
||||||
|
|
||||||
* If the machine has a list of assigned workers, the program chooses from those that are required by the machine for the assigned calendar. For example, if the machine calendar is 16 hours per day and the resource calendar is 8 hours, two resources are assigned from the list of available resources.
|
* If the machine has a list of assigned workers, the program chooses from those that are required by the machine for the assigned calendar. For example, if the machine calendar is 16 hours per day and the resource calendar is 8 hours, two resources are assigned from the list of available resources.
|
||||||
* If the machine has one or several assigned criteria, generic assignments are carried out from among the resources that fulfil the criteria assigned to the machine.
|
* If the machine has one or several assigned criteria, generic assignments are carried out from among the resources that fulfil the criteria assigned to the machine.
|
||||||
|
|
||||||
Generic assignment
|
Generic assignment
|
||||||
==================
|
==================
|
||||||
|
|
||||||
Generic assignment occurs when users do not choose resources specifically, but leave the decision to the program, which distributes the loads among the company's available resources.
|
Generic assignment occurs when users do not choose resources specifically, but leave the decision to the program, which distributes the loads among the company's available resources.
|
||||||
|
|
||||||
.. figure:: images/asignacion-xenerica.png
|
.. figure:: images/asignacion-xenerica.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Generic resource assignment
|
Generic resource assignment
|
||||||
|
|
||||||
The assignment system uses the following assumptions as a basis:
|
The assignment system uses the following assumptions as a basis:
|
||||||
|
|
||||||
* Tasks have criteria that are required from resources.
|
* Tasks have criteria that are required from resources.
|
||||||
* Resources are configured to fulfil criteria.
|
* Resources are configured to fulfil criteria.
|
||||||
|
|
||||||
However, the system does not fail when criteria have not been assigned, but when all resources fulfil the non-requirement of criteria.
|
However, the system does not fail when criteria have not been assigned, but when all resources fulfil the non-requirement of criteria.
|
||||||
|
|
||||||
The generic assignment algorithm functions in the following way:
|
The generic assignment algorithm functions in the following way:
|
||||||
|
|
||||||
* All resources and days are treated as containers where daily assignment of hours fit, based on the maximum assignment capacity in the task calendar.
|
* All resources and days are treated as containers where daily assignment of hours fit, based on the maximum assignment capacity in the task calendar.
|
||||||
* The system searches for the resources that fulfil the criterion.
|
* The system searches for the resources that fulfil the criterion.
|
||||||
* The system analyses which assignments currently have different resources that fulfil criteria.
|
* The system analyses which assignments currently have different resources that fulfil criteria.
|
||||||
* The resources that fulfil the criteria are chosen from those that have sufficient availability.
|
* The resources that fulfil the criteria are chosen from those that have sufficient availability.
|
||||||
* If freer resources are not available, assignments are made to the resources that have less availability.
|
* If freer resources are not available, assignments are made to the resources that have less availability.
|
||||||
* Over-assignment of resources only starts when all the resources that fulfil the respective criteria are 100% assigned until the total amount required to carry out the task is attained.
|
* Over-assignment of resources only starts when all the resources that fulfil the respective criteria are 100% assigned until the total amount required to carry out the task is attained.
|
||||||
|
|
||||||
Generic machine assignment
|
Generic machine assignment
|
||||||
--------------------------
|
--------------------------
|
||||||
|
|
||||||
Generic machine assignment functions in the same way as worker assignment. For example, when a machine is assigned to a task, the system stores a generic assignment of hours for all machines that fulfil the criteria as described for the resources in general. However, in addition, the system performs the following procedure for machines:
|
Generic machine assignment functions in the same way as worker assignment. For example, when a machine is assigned to a task, the system stores a generic assignment of hours for all machines that fulfil the criteria as described for the resources in general. However, in addition, the system performs the following procedure for machines:
|
||||||
|
|
||||||
* For all machines chosen for generic assignment:
|
* For all machines chosen for generic assignment:
|
||||||
|
|
||||||
* It collects the machine's configuration information: alpha value, assigned workers and criteria.
|
* It collects the machine's configuration information: alpha value, assigned workers and criteria.
|
||||||
* If the machine has an assigned list of workers, the program chooses the number required by the machine depending on the assigned calendar. For example, if the machine calendar is 16 hours per day and the resource calendar is 8 hours, the program assigns two resources from the list of available resources.
|
* If the machine has an assigned list of workers, the program chooses the number required by the machine depending on the assigned calendar. For example, if the machine calendar is 16 hours per day and the resource calendar is 8 hours, the program assigns two resources from the list of available resources.
|
||||||
* If the machine has one or several assigned criteria, the program makes generic assignments from among the resources that fulfil the criteria assigned to the machine.
|
* If the machine has one or several assigned criteria, the program makes generic assignments from among the resources that fulfil the criteria assigned to the machine.
|
||||||
|
|
||||||
|
|
||||||
Advanced assignment
|
Advanced assignment
|
||||||
===================
|
===================
|
||||||
|
|
||||||
Advanced assignments allow users to design assignments that are automatically carried out by the application in order to personalise them. This procedure allows users to manually choose the daily hours that are dedicated by resources to tasks that are assigned or define a function that is applied to the assignment.
|
Advanced assignments allow users to design assignments that are automatically carried out by the application in order to personalise them. This procedure allows users to manually choose the daily hours that are dedicated by resources to tasks that are assigned or define a function that is applied to the assignment.
|
||||||
|
|
||||||
The steps to follow in order to manage advanced assignments are:
|
The steps to follow in order to manage advanced assignments are:
|
||||||
|
|
||||||
* Go to the advanced assignment window. There are two ways to access advanced assignments:
|
* Go to the advanced assignment window. There are two ways to access advanced assignments:
|
||||||
|
|
||||||
* Go to a specific order and change the view to advanced assignment. In this case, all the tasks on the order and assigned resources (specific and generic) will be shown.
|
* Go to a specific order and change the view to advanced assignment. In this case, all the tasks on the order and assigned resources (specific and generic) will be shown.
|
||||||
* Go to the resource assignment window by clicking the "Advanced assignment" button. In this case, the assignments that show the resources (generic and specific) assigned for a task will be shown.
|
* Go to the resource assignment window by clicking the "Advanced assignment" button. In this case, the assignments that show the resources (generic and specific) assigned for a task will be shown.
|
||||||
|
|
||||||
.. figure:: images/advance-assignment.png
|
.. figure:: images/advance-assignment.png
|
||||||
:scale: 45
|
:scale: 45
|
||||||
|
|
||||||
Advanced resource assignment
|
Advanced resource assignment
|
||||||
|
|
||||||
* Users can choose the required zoom level they want:
|
* Users can choose the required zoom level they want:
|
||||||
|
|
||||||
* If the chosen zoom is more than one day. If users change the assigned hour value to a week, month, four-month or six-month period, the system distributes the hours lineally for all days throughout the chosen period.
|
* If the chosen zoom is more than one day. If users change the assigned hour value to a week, month, four-month or six-month period, the system distributes the hours lineally for all days throughout the chosen period.
|
||||||
* If the chosen zoom is one day. If users change the assigned hour value to a day, these hours only apply to a day. Consequently, users can decide how many hours they want to assign per day to task resources.
|
* If the chosen zoom is one day. If users change the assigned hour value to a day, these hours only apply to a day. Consequently, users can decide how many hours they want to assign per day to task resources.
|
||||||
|
|
||||||
* Users can choose to design an advanced assignment function. In order to do so, users have to:
|
* Users can choose to design an advanced assignment function. In order to do so, users have to:
|
||||||
|
|
||||||
* Choose the function on the selection list that appears at the side of each resource and click "Configure".
|
* Choose the function on the selection list that appears at the side of each resource and click "Configure".
|
||||||
* The system shows a new window if the chosen function needs to be specifically configured. Supported functions:
|
* The system shows a new window if the chosen function needs to be specifically configured. Supported functions:
|
||||||
|
|
||||||
* Segments: A function that allows users to define segments to which a polynomial function is applied. The function per segment is configured as follows:
|
* Segments: A function that allows users to define segments to which a polynomial function is applied. The function per segment is configured as follows:
|
||||||
|
|
||||||
|
|
||||||
* Date. Date on which the segment ends. If the following value is established (length), the date is calculated, alternatively, length is calculated.
|
* Date. Date on which the segment ends. If the following value is established (length), the date is calculated, alternatively, length is calculated.
|
||||||
* Defining the length of each segment. This indicates what percentage of the task's duration is required for the segment.
|
* Defining the length of each segment. This indicates what percentage of the task's duration is required for the segment.
|
||||||
* Defining the amount of work. This indicates what workload percentage is expected to be completed in this segment. The quantity of work must be incremental. For example, if there is a 10% segment, the next one must be larger (for example, 20%).
|
* Defining the amount of work. This indicates what workload percentage is expected to be completed in this segment. The quantity of work must be incremental. For example, if there is a 10% segment, the next one must be larger (for example, 20%).
|
||||||
* Segment graphs and accumulated loads.
|
* Segment graphs and accumulated loads.
|
||||||
|
|
||||||
|
|
||||||
* Users then click "Accept".
|
* Users then click "Accept".
|
||||||
* The program stores the function and applies it to the daily resource assignments.
|
* The program stores the function and applies it to the daily resource assignments.
|
||||||
|
|
||||||
.. figure:: images/stretches.png
|
.. figure:: images/stretches.png
|
||||||
:scale: 40
|
:scale: 40
|
||||||
|
|
||||||
Configuration of the segment function
|
Configuration of the segment function
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,75 +1,75 @@
|
||||||
Work reports
|
Work reports
|
||||||
#################
|
#################
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
Work reports enable the monitoring of the hours that existing resources dedicate to the tasks in which they are scheduled.
|
Work reports enable the monitoring of the hours that existing resources dedicate to the tasks in which they are scheduled.
|
||||||
|
|
||||||
The program allows users to configure new forms to enter dedicated hours, specifying the fields that they want to appear in these models, to incorporate reports from tasks that are carried out by workers and to monitor workers.
|
The program allows users to configure new forms to enter dedicated hours, specifying the fields that they want to appear in these models, to incorporate reports from tasks that are carried out by workers and to monitor workers.
|
||||||
|
|
||||||
Before being able to add entries for resources, users must at least specify a work report type that defines the structure, including all the rows that are added to it. Users can create as many work reports on the system as necessary.
|
Before being able to add entries for resources, users must at least specify a work report type that defines the structure, including all the rows that are added to it. Users can create as many work reports on the system as necessary.
|
||||||
|
|
||||||
Work report type
|
Work report type
|
||||||
================
|
================
|
||||||
|
|
||||||
A work report has a series of fields that are common to the whole report, and a set of work report lines with specific values for the fields defined in each row. For example, resources and tasks are common to all reports, however, there can be other new fields such as "incidents", which are not required in all types.
|
A work report has a series of fields that are common to the whole report, and a set of work report lines with specific values for the fields defined in each row. For example, resources and tasks are common to all reports, however, there can be other new fields such as "incidents", which are not required in all types.
|
||||||
|
|
||||||
Users can configure different work report types so that a company can design its reports to meet its own needs:
|
Users can configure different work report types so that a company can design its reports to meet its own needs:
|
||||||
|
|
||||||
.. figure:: images/work-report-types.png
|
.. figure:: images/work-report-types.png
|
||||||
:scale: 40
|
:scale: 40
|
||||||
|
|
||||||
Work report types
|
Work report types
|
||||||
|
|
||||||
The administration of the work report types allows users to configure this type of feature and add new text fields or optional tags. In the first tab for editing work report types, it is possible to configure the type for the obligatory attributes (if they are applicable to the whole report or if they are specified at line level), and add new optional fields.
|
The administration of the work report types allows users to configure this type of feature and add new text fields or optional tags. In the first tab for editing work report types, it is possible to configure the type for the obligatory attributes (if they are applicable to the whole report or if they are specified at line level), and add new optional fields.
|
||||||
|
|
||||||
The obligatory fields that must appear in all work reports are as follows:
|
The obligatory fields that must appear in all work reports are as follows:
|
||||||
|
|
||||||
* Name and code: ID fields for the name of the work report type and its code.
|
* Name and code: ID fields for the name of the work report type and its code.
|
||||||
* Date: Field for the date of the report.
|
* Date: Field for the date of the report.
|
||||||
* Resource: Worker or machine appearing on the report or work report line.
|
* Resource: Worker or machine appearing on the report or work report line.
|
||||||
* Order element: Code for the order element to which the performed work is attributed.
|
* Order element: Code for the order element to which the performed work is attributed.
|
||||||
* Hour management: Determining the hour attribution policy to be carried out, which can be:
|
* Hour management: Determining the hour attribution policy to be carried out, which can be:
|
||||||
* According to assigned hours.
|
* According to assigned hours.
|
||||||
* According to start and finish times.
|
* According to start and finish times.
|
||||||
* According to the number of hours and start and finish range (discrepancies are allowed and the number of hours takes priority).
|
* According to the number of hours and start and finish range (discrepancies are allowed and the number of hours takes priority).
|
||||||
|
|
||||||
Users can add new fields to the reports:
|
Users can add new fields to the reports:
|
||||||
|
|
||||||
* Tag type: Users can request the system to show a tag when completing the work report. For example, the client tag type, if the user wishes to enter the client, for which the work was carried out, in each report.
|
* Tag type: Users can request the system to show a tag when completing the work report. For example, the client tag type, if the user wishes to enter the client, for which the work was carried out, in each report.
|
||||||
* Free fields: Fields where text can be entered freely in the work report.
|
* Free fields: Fields where text can be entered freely in the work report.
|
||||||
|
|
||||||
.. figure:: images/work-report-type.png
|
.. figure:: images/work-report-type.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Creating a work report type with personalised fields
|
Creating a work report type with personalised fields
|
||||||
|
|
||||||
|
|
||||||
Users can configure date, resource and order element fields if they appear in the header of the report, which means they apply to the whole report, or if they are added to each of the rows.
|
Users can configure date, resource and order element fields if they appear in the header of the report, which means they apply to the whole report, or if they are added to each of the rows.
|
||||||
|
|
||||||
Finally, new additional text fields or tags can be added to the existing ones, in the work report header or in each line, by using the "Additional text" and "Tag type" fields respectively. Users can configure the order in which these elements are to be entered in the "Management of additional fields and tags" tab.
|
Finally, new additional text fields or tags can be added to the existing ones, in the work report header or in each line, by using the "Additional text" and "Tag type" fields respectively. Users can configure the order in which these elements are to be entered in the "Management of additional fields and tags" tab.
|
||||||
|
|
||||||
Work report list
|
Work report list
|
||||||
================
|
================
|
||||||
|
|
||||||
As soon as the format of the reports to be incorporated into the system have been configured, users can enter the details in the created form according to the structure defined in the corresponding work report type. In order to do this, users need to follow these steps:
|
As soon as the format of the reports to be incorporated into the system have been configured, users can enter the details in the created form according to the structure defined in the corresponding work report type. In order to do this, users need to follow these steps:
|
||||||
|
|
||||||
* Click the "New work report" button associated with the desired report from the list of work report types.
|
* Click the "New work report" button associated with the desired report from the list of work report types.
|
||||||
* The program then shows the report based on the configurations given for the type. See the following image.
|
* The program then shows the report based on the configurations given for the type. See the following image.
|
||||||
|
|
||||||
.. figure:: images/work-report-type.png
|
.. figure:: images/work-report-type.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Structure of the work report based on type
|
Structure of the work report based on type
|
||||||
|
|
||||||
* Select all the fields shown for the report:
|
* Select all the fields shown for the report:
|
||||||
|
|
||||||
* Resource: If the header has been chosen, the resource is only shown once, alternatively, for each line of the report, it is necessary to choose a resource.
|
* Resource: If the header has been chosen, the resource is only shown once, alternatively, for each line of the report, it is necessary to choose a resource.
|
||||||
* Task code: Code of the task to which the work report is being assigned. Similar to the rest of the fields, if the field is the header, the value is entered once or as many times as necessary on the lines of the report.
|
* Task code: Code of the task to which the work report is being assigned. Similar to the rest of the fields, if the field is the header, the value is entered once or as many times as necessary on the lines of the report.
|
||||||
* Date: Date of the report or each line, depending on whether the heading or line is configured.
|
* Date: Date of the report or each line, depending on whether the heading or line is configured.
|
||||||
* Number of hours. The number of work hours in the project.
|
* Number of hours. The number of work hours in the project.
|
||||||
* Start and finish times. Start and finish times for the work in order to calculate definitive work hours. This field only appears in the case of the hour assignment policies, "According to start and finish times" and "According to the number of hours and start and finish range".
|
* Start and finish times. Start and finish times for the work in order to calculate definitive work hours. This field only appears in the case of the hour assignment policies, "According to start and finish times" and "According to the number of hours and start and finish range".
|
||||||
* Type of hours: Enabling users to choose the type of hour, e.g. "Normal", "Extraordinary", etc.
|
* Type of hours: Enabling users to choose the type of hour, e.g. "Normal", "Extraordinary", etc.
|
||||||
|
|
||||||
* Click "Save" or "Save and continue".
|
* Click "Save" or "Save and continue".
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,57 +1,57 @@
|
||||||
Tags
|
Tags
|
||||||
#########
|
#########
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
Tags are entities used in the program to conceptually organise tasks or order elements.
|
Tags are entities used in the program to conceptually organise tasks or order elements.
|
||||||
|
|
||||||
Tags are categorised according to tag type. A tag can only belong to one tag type, however, users can create many similar tags belonging to different tag types.
|
Tags are categorised according to tag type. A tag can only belong to one tag type, however, users can create many similar tags belonging to different tag types.
|
||||||
|
|
||||||
Tag types
|
Tag types
|
||||||
===========
|
===========
|
||||||
|
|
||||||
Tag types are used to group the types of tag that users want to manage in the program. Here are some examples of possible tag types:
|
Tag types are used to group the types of tag that users want to manage in the program. Here are some examples of possible tag types:
|
||||||
|
|
||||||
i. Client: Users may be interested in tagging tasks, orders or order elements in relation to the client who requests them.
|
i. Client: Users may be interested in tagging tasks, orders or order elements in relation to the client who requests them.
|
||||||
ii. Area: Users may be interested in tagging tasks, orders or order elements in relation to the areas in which they are carried out.
|
ii. Area: Users may be interested in tagging tasks, orders or order elements in relation to the areas in which they are carried out.
|
||||||
|
|
||||||
The administration of tag types is managed from the "Administration" menu option. This is where users can edit tag types, create new tag types and add tags to tag types. Users can access the list of tags from this option.
|
The administration of tag types is managed from the "Administration" menu option. This is where users can edit tag types, create new tag types and add tags to tag types. Users can access the list of tags from this option.
|
||||||
|
|
||||||
.. figure:: images/tag-types-list.png
|
.. figure:: images/tag-types-list.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
List of tag types
|
List of tag types
|
||||||
|
|
||||||
From the list of tag types, users can:
|
From the list of tag types, users can:
|
||||||
|
|
||||||
i. Create a new tag type.
|
i. Create a new tag type.
|
||||||
ii. Edit an existing tag type.
|
ii. Edit an existing tag type.
|
||||||
iii. Delete a tag type with all of its tags.
|
iii. Delete a tag type with all of its tags.
|
||||||
|
|
||||||
Editing and creating tags share the same form. From this form, the user can assign a name to the tag type, create or delete tags and store the changes. The procedure is as follows:
|
Editing and creating tags share the same form. From this form, the user can assign a name to the tag type, create or delete tags and store the changes. The procedure is as follows:
|
||||||
|
|
||||||
i. Select a tag to edit or click the create button for a new one.
|
i. Select a tag to edit or click the create button for a new one.
|
||||||
ii. The system shows a form with a text entry for the name and a list of text entries with existing and assigned tags.
|
ii. The system shows a form with a text entry for the name and a list of text entries with existing and assigned tags.
|
||||||
iii. If users wish to add a new tag, they must click on the "New tag" button.
|
iii. If users wish to add a new tag, they must click on the "New tag" button.
|
||||||
iv. The system shows a new row on the list with an empty text box that users must edit.
|
iv. The system shows a new row on the list with an empty text box that users must edit.
|
||||||
v. Users enter a name for the tag.
|
v. Users enter a name for the tag.
|
||||||
vi. The system adds the name to the list.
|
vi. The system adds the name to the list.
|
||||||
vii. Users click "Save" or "Save and continue" to continue editing the form.
|
vii. Users click "Save" or "Save and continue" to continue editing the form.
|
||||||
|
|
||||||
.. figure:: images/tag-types-edition.png
|
.. figure:: images/tag-types-edition.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Editing tag types
|
Editing tag types
|
||||||
|
|
||||||
Tags
|
Tags
|
||||||
====
|
====
|
||||||
|
|
||||||
Tags are entities that belong to a tag type. These entities can be assigned to order elements. Assigning a tag to an order element means that all the elements descending from this element will inherit the tag to which they belong. Having an assigned tag means that these entities are filtered where searches can be carried out:
|
Tags are entities that belong to a tag type. These entities can be assigned to order elements. Assigning a tag to an order element means that all the elements descending from this element will inherit the tag to which they belong. Having an assigned tag means that these entities are filtered where searches can be carried out:
|
||||||
|
|
||||||
i. Search for tasks in the Gantt chart.
|
i. Search for tasks in the Gantt chart.
|
||||||
ii. Search for order elements in the list of order elements.
|
ii. Search for order elements in the list of order elements.
|
||||||
iii. Filters for reports.
|
iii. Filters for reports.
|
||||||
|
|
||||||
The assignment of tags to order elements is covered in the chapter on orders.
|
The assignment of tags to order elements is covered in the chapter on orders.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,44 +1,44 @@
|
||||||
Materials
|
Materials
|
||||||
##########
|
##########
|
||||||
.. _materiales:
|
.. _materiales:
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
|
|
||||||
Administration of materials
|
Administration of materials
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
Users can manage a basic database of materials, organised by categories.
|
Users can manage a basic database of materials, organised by categories.
|
||||||
|
|
||||||
The categories are containers that can be assigned specific materials and also more categories. They are stored in a tree structure as the materials can belong to leaf or intermediary categories.
|
The categories are containers that can be assigned specific materials and also more categories. They are stored in a tree structure as the materials can belong to leaf or intermediary categories.
|
||||||
|
|
||||||
Users have to do the following to manage categories:
|
Users have to do the following to manage categories:
|
||||||
|
|
||||||
* Go to the "Administration->Materials" option.
|
* Go to the "Administration->Materials" option.
|
||||||
* The program shows a tree of categories.
|
* The program shows a tree of categories.
|
||||||
* The user enters a category name in the text box and then clicks "Add".
|
* The user enters a category name in the text box and then clicks "Add".
|
||||||
* The program adds the category to the tree.
|
* The program adds the category to the tree.
|
||||||
|
|
||||||
If users want to insert a category into the category tree, they have to first select the parent category in the tree and then click "Add".
|
If users want to insert a category into the category tree, they have to first select the parent category in the tree and then click "Add".
|
||||||
|
|
||||||
.. figure:: images/material.png
|
.. figure:: images/material.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Material administration screen
|
Material administration screen
|
||||||
|
|
||||||
Users have to do the following to manage materials:
|
Users have to do the following to manage materials:
|
||||||
|
|
||||||
* Select the category to which materials are to be included and click "Add" to the right of "Materials".
|
* Select the category to which materials are to be included and click "Add" to the right of "Materials".
|
||||||
* The program adds a new empty row with fields to enter details about the material:
|
* The program adds a new empty row with fields to enter details about the material:
|
||||||
|
|
||||||
* Code: Material type code (this can be the external code from an ERP).
|
* Code: Material type code (this can be the external code from an ERP).
|
||||||
* Description: Description of the material.
|
* Description: Description of the material.
|
||||||
* Price of the unit: Unit price of each piece of material.
|
* Price of the unit: Unit price of each piece of material.
|
||||||
* Unit: Unit that is used to measure each unit of material.
|
* Unit: Unit that is used to measure each unit of material.
|
||||||
* Category: Category to which it belongs.
|
* Category: Category to which it belongs.
|
||||||
* Availability: Whether or not the material has been removed.
|
* Availability: Whether or not the material has been removed.
|
||||||
|
|
||||||
* Users complete the fields and click "Save".
|
* Users complete the fields and click "Save".
|
||||||
|
|
||||||
The assignment of materials to order elements is explained in the chapter on "Orders".
|
The assignment of materials to order elements is explained in the chapter on "Orders".
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,38 +1,38 @@
|
||||||
Quality forms
|
Quality forms
|
||||||
######################
|
######################
|
||||||
|
|
||||||
.. _calidad:
|
.. _calidad:
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
|
|
||||||
Administration of quality forms
|
Administration of quality forms
|
||||||
===============================
|
===============================
|
||||||
|
|
||||||
Quality forms consist of a list of questions or sentences that indicate the tasks or processes that should have been completed so that a task can be marked as complete by the company. These forms consist of the following fields:
|
Quality forms consist of a list of questions or sentences that indicate the tasks or processes that should have been completed so that a task can be marked as complete by the company. These forms consist of the following fields:
|
||||||
|
|
||||||
* Name
|
* Name
|
||||||
* Description
|
* Description
|
||||||
* Type of quality form. The type can have two values:
|
* Type of quality form. The type can have two values:
|
||||||
|
|
||||||
* Percentage: Indicating that the questions must have a logical order and affirmative answers to the questions indicate that the task is progressing. For example, a basic process for a task suggests that the task is 15% complete. Users need to answer a question beforehand to be able to go on to the next one.
|
* Percentage: Indicating that the questions must have a logical order and affirmative answers to the questions indicate that the task is progressing. For example, a basic process for a task suggests that the task is 15% complete. Users need to answer a question beforehand to be able to go on to the next one.
|
||||||
* Item: Indicating that the questions are not required to have a logical order and therefore can be answered as desired.
|
* Item: Indicating that the questions are not required to have a logical order and therefore can be answered as desired.
|
||||||
|
|
||||||
Users must carry out the following steps to manage the quality forms:
|
Users must carry out the following steps to manage the quality forms:
|
||||||
|
|
||||||
* From the "Administration" menu, access the "Quality forms" option.
|
* From the "Administration" menu, access the "Quality forms" option.
|
||||||
* Click edit an existing form or "Create".
|
* Click edit an existing form or "Create".
|
||||||
* The program shows a form with a name, description and type.
|
* The program shows a form with a name, description and type.
|
||||||
* Select the type.
|
* Select the type.
|
||||||
* The program shows the fields that are allowed for each type:
|
* The program shows the fields that are allowed for each type:
|
||||||
|
|
||||||
* Percentage: question and percentage.
|
* Percentage: question and percentage.
|
||||||
* Item: question.
|
* Item: question.
|
||||||
|
|
||||||
* Click "Save" or "Save and continue".
|
* Click "Save" or "Save and continue".
|
||||||
|
|
||||||
.. figure:: images/quality.png
|
.. figure:: images/quality.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Material administration screen
|
Material administration screen
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,63 +1,63 @@
|
||||||
Users
|
Users
|
||||||
########
|
########
|
||||||
|
|
||||||
.. _tareas:
|
.. _tareas:
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
|
|
||||||
Managing users
|
Managing users
|
||||||
==============
|
==============
|
||||||
|
|
||||||
"NavalPlan"'s system enables users to manage profiles, authorisations and users. Users belong to user profiles, which may have a series of predefined roles to access the program. Roles are defined authorisations in "NavalPlan". Examples of roles:
|
"NavalPlan"'s system enables users to manage profiles, authorisations and users. Users belong to user profiles, which may have a series of predefined roles to access the program. Roles are defined authorisations in "NavalPlan". Examples of roles:
|
||||||
|
|
||||||
* Administration: A role to which administrators must be assigned in order to be able to carry out administration operations.
|
* Administration: A role to which administrators must be assigned in order to be able to carry out administration operations.
|
||||||
* Web service reader: A role that users need to be able to consult the program's web services.
|
* Web service reader: A role that users need to be able to consult the program's web services.
|
||||||
* Web service writer: A role that users need to be able to write via the program's web services.
|
* Web service writer: A role that users need to be able to write via the program's web services.
|
||||||
|
|
||||||
Roles are predefined in the system. A user profile consists of one or several roles. Users must have certain roles to carry out certain operations.
|
Roles are predefined in the system. A user profile consists of one or several roles. Users must have certain roles to carry out certain operations.
|
||||||
|
|
||||||
Users have one or several profiles or one or several roles directly so that specific or generic authorisation can be assigned.
|
Users have one or several profiles or one or several roles directly so that specific or generic authorisation can be assigned.
|
||||||
|
|
||||||
It is necessary to carry out the following steps to manage users:
|
It is necessary to carry out the following steps to manage users:
|
||||||
|
|
||||||
* Go to "Manage users" on the "Administration" menu.
|
* Go to "Manage users" on the "Administration" menu.
|
||||||
* The program shows a form with a list of users.
|
* The program shows a form with a list of users.
|
||||||
* Click the editing button for the chosen user or click the "Create" button.
|
* Click the editing button for the chosen user or click the "Create" button.
|
||||||
* A form will appear with the following fields:
|
* A form will appear with the following fields:
|
||||||
|
|
||||||
* User name.
|
* User name.
|
||||||
* Password
|
* Password
|
||||||
* Authorised/unauthorised.
|
* Authorised/unauthorised.
|
||||||
* Email
|
* Email
|
||||||
* List of associated roles. Users need to search for one of the roles shown on the selection list and click "Assign" to add a new role.
|
* List of associated roles. Users need to search for one of the roles shown on the selection list and click "Assign" to add a new role.
|
||||||
* List of associated profiles. Users need to search for one of the profiles shown on the selection list and click "Assign" to add a new profile.
|
* List of associated profiles. Users need to search for one of the profiles shown on the selection list and click "Assign" to add a new profile.
|
||||||
|
|
||||||
.. figure:: images/manage-user.png
|
.. figure:: images/manage-user.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Managing users
|
Managing users
|
||||||
|
|
||||||
* Click "Save" or "Save and continue".
|
* Click "Save" or "Save and continue".
|
||||||
|
|
||||||
|
|
||||||
Managing profiles
|
Managing profiles
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
Users need to carry out the following steps to manage the program's profiles.
|
Users need to carry out the following steps to manage the program's profiles.
|
||||||
|
|
||||||
* Go to "Manage user profiles" on the "Administration" menu.
|
* Go to "Manage user profiles" on the "Administration" menu.
|
||||||
* The program shows a list of profiles.
|
* The program shows a list of profiles.
|
||||||
* Click the editing button for the chosen profile or click "Create".
|
* Click the editing button for the chosen profile or click "Create".
|
||||||
* A form appears in the program with the following fields:
|
* A form appears in the program with the following fields:
|
||||||
|
|
||||||
* Name
|
* Name
|
||||||
* List of roles (authorisations) associated with the profile. Users must select a role from the role list and click "Add" to add one that is associated with the profile.
|
* List of roles (authorisations) associated with the profile. Users must select a role from the role list and click "Add" to add one that is associated with the profile.
|
||||||
|
|
||||||
.. figure:: images/manage-user-profile.png
|
.. figure:: images/manage-user-profile.png
|
||||||
:scale: 50
|
:scale: 50
|
||||||
|
|
||||||
Managing user profiles
|
Managing user profiles
|
||||||
|
|
||||||
* Click "Save" or "Save and continue" and the system will store the created or modified profile.
|
* Click "Save" or "Save and continue" and the system will store the created or modified profile.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue