ItEr46S06DocumentacionFormacionItEr45S06: User doc in English and some encoding modifications
This commit is contained in:
Xavier Castaño
Javier Moran Rua
parent
590f2385a1
commit
6d94ccc991
18 changed files with 96 additions and 96 deletions
|
|
@ -1,5 +1,5 @@
|
|||
Introduction
|
||||
############
|
||||
Introduction
|
||||
#############
|
||||
|
||||
.. contents::
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Criteria
|
||||
Criteria
|
||||
#########
|
||||
|
||||
.. contents::
|
||||
|
|
@ -10,7 +10,7 @@ Several operations can be carried out with criteria in the program:
|
|||
* Criteria administration
|
||||
* Allocation of criteria to resources.
|
||||
* 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".
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Calendars
|
||||
Calendars
|
||||
###########
|
||||
|
||||
.. contents::
|
||||
|
|
@ -114,7 +114,7 @@ The following must be carried out to set up a default calendar:
|
|||
|
||||
* Go to the *Administration* menu.
|
||||
* Click the *Configuration* procedure.
|
||||
* Where *Default calendar* appears, select the calendar to be used as the program’s default calendar.
|
||||
* Where *Default calendar* appears, select the calendar to be used as the program's default calendar.
|
||||
* Click *Save*.
|
||||
|
||||
.. figure:: images/default-calendar.png
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Progress
|
||||
Progress
|
||||
#########
|
||||
|
||||
.. contents::
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Management of resources
|
||||
Management of resources
|
||||
#######################
|
||||
|
||||
.. _recursos:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Orders and order elements
|
||||
Orders and order elements
|
||||
##############################
|
||||
|
||||
.. contents::
|
||||
|
|
@ -13,10 +13,10 @@ The following sections will describe the operations that users can carry out wit
|
|||
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 code
|
||||
* Order name
|
||||
* Order code
|
||||
* Total amount of order
|
||||
* Estimated start date
|
||||
* End date
|
||||
|
|
@ -211,7 +211,7 @@ Apart from the required criterion, one or various hour groups that are part of t
|
|||
* 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.
|
||||
* 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.
|
||||
* 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.
|
||||
|
||||
|
|
@ -253,7 +253,7 @@ Working with materials is carried out as follows:
|
|||
* 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.
|
||||
* 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
|
||||
:scale: 50
|
||||
|
|
@ -269,7 +269,7 @@ For subsequent monitoring of materials, it is possible to change the status of a
|
|||
* The program shows two rows with the material divided.
|
||||
* 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
|
||||
------------------------------------
|
||||
|
|
@ -290,7 +290,7 @@ To manage quality forms:
|
|||
* 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.
|
||||
* 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".
|
||||
* The program assigns the form chosen from the list of forms assigned to the order element.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Task planning
|
||||
Task planning
|
||||
#######################
|
||||
|
||||
.. _planificacion:
|
||||
|
|
@ -8,7 +8,7 @@
|
|||
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
|
||||
:scale: 35
|
||||
|
|
@ -34,7 +34,7 @@ The planning view combines three different views:
|
|||
* 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.
|
||||
|
||||
* 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.
|
||||
* 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.
|
||||
|
|
@ -56,20 +56,20 @@ In the project planning, users can carry out the following procedures:
|
|||
|
||||
* 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.
|
||||
* 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.
|
||||
* *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.
|
||||
|
||||
|
||||
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.
|
||||
* 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.
|
||||
* 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 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.
|
||||
* Print: Enabling users to print the Gantt chart being viewed at that moment.
|
||||
|
||||
Resource load view
|
||||
|
|
@ -94,7 +94,7 @@ The order list view allows users to go to the order editing and deleting options
|
|||
|
||||
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,4 +1,4 @@
|
|||
Assignment of resources
|
||||
Assignment of resources
|
||||
########################
|
||||
|
||||
.. asigacion_
|
||||
|
|
@ -11,7 +11,7 @@ The assignment of resources is one of the program's most important features, and
|
|||
|
||||
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.
|
||||
* Right click on the task to be planned.
|
||||
|
|
@ -37,7 +37,7 @@ To carry out either of the two types of resource assignment, the following steps
|
|||
.. figure:: images/resource-assignment.png
|
||||
:scale: 50
|
||||
|
||||
Resource assignment
|
||||
Resource assignment
|
||||
|
||||
* 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:
|
||||
|
|
@ -64,7 +64,7 @@ To carry out either of the two types of resource assignment, the following steps
|
|||
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:
|
||||
|
||||
|
|
@ -72,7 +72,7 @@ Specific assignment can be carried out on the screen shown in this image:
|
|||
.. figure:: images/asignacion-especifica.png
|
||||
: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).
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ Generic assignment occurs when users do not choose resources specifically, but l
|
|||
.. figure:: images/asignacion-xenerica.png
|
||||
:scale: 50
|
||||
|
||||
Generic resource assignment
|
||||
Generic resource assignment
|
||||
|
||||
The assignment system uses the following assumptions as a basis:
|
||||
|
||||
|
|
@ -105,19 +105,19 @@ 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.
|
||||
* 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.
|
||||
* 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.
|
||||
|
||||
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:
|
||||
|
||||
* 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 one or several assigned criteria, the program makes generic assignments from among the resources that fulfil the criteria assigned to the machine.
|
||||
|
||||
|
|
@ -125,14 +125,14 @@ Generic machine assignment functions in the same way as worker assignment. For e
|
|||
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:
|
||||
|
||||
* 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 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
|
||||
:scale: 45
|
||||
|
|
@ -153,12 +153,12 @@ The steps to follow in order to manage advanced assignments are:
|
|||
|
||||
|
||||
* 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%).
|
||||
* 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.
|
||||
|
||||
.. figure:: images/stretches.png
|
||||
|
|
|
|||
|
|
@ -1,25 +1,25 @@
|
|||
Work reports
|
||||
Work reports
|
||||
#################
|
||||
|
||||
.. contents::
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
.. figure:: images/work-report-types.png
|
||||
: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.
|
||||
|
||||
|
|
@ -45,16 +45,16 @@ Users can add new fields to the reports:
|
|||
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
|
||||
================
|
||||
|
||||
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.
|
||||
|
||||
.. figure:: images/work-report-type.png
|
||||
|
|
@ -68,8 +68,8 @@ As soon as the format of the reports to be incorporated into the system have bee
|
|||
* 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.
|
||||
* 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”.
|
||||
* Type of hours: Enabling users to choose the type of hour, e.g. “Normal”, “Extraordinary”, etc.
|
||||
* 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.
|
||||
|
||||
* Click "Save" or "Save and continue".
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Tags
|
||||
Tags
|
||||
#########
|
||||
|
||||
.. contents::
|
||||
|
|
@ -15,12 +15,12 @@ Tag types are used to group the types of tag that users want to manage in the pr
|
|||
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.
|
||||
|
||||
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
|
||||
:scale: 50
|
||||
|
||||
List of tag types
|
||||
List of tag types
|
||||
|
||||
From the list of tag types, users can:
|
||||
|
||||
|
|
@ -32,11 +32,11 @@ Editing and creating tags share the same form. From this form, the user can assi
|
|||
|
||||
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.
|
||||
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.
|
||||
v. Users enter a name for the tag.
|
||||
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
|
||||
:scale: 50
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Materials
|
||||
Materials
|
||||
##########
|
||||
.. _materiales:
|
||||
.. contents::
|
||||
|
|
@ -7,18 +7,18 @@
|
|||
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.
|
||||
|
||||
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 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.
|
||||
|
||||
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
|
||||
:scale: 50
|
||||
|
|
@ -27,7 +27,7 @@ If users want to insert a category into the category tree, they have to first se
|
|||
|
||||
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:
|
||||
|
||||
* Code: Material type code (this can be the external code from an ERP).
|
||||
|
|
@ -37,7 +37,7 @@ Users have to do the following to manage materials:
|
|||
* Category: Category to which it belongs.
|
||||
* 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".
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Quality forms
|
||||
Quality forms
|
||||
######################
|
||||
|
||||
.. _calidad:
|
||||
|
|
@ -19,8 +19,8 @@ Quality forms consist of a list of questions or sentences that indicate the task
|
|||
|
||||
Users must carry out the following steps to manage the quality forms:
|
||||
|
||||
* From the “Administration” menu, access the “Quality forms” option.
|
||||
* Click edit an existing form or “Create”.
|
||||
* From the "Administration" menu, access the "Quality forms" option.
|
||||
* Click edit an existing form or "Create".
|
||||
* The program shows a form with a name, description and type.
|
||||
* Select the type.
|
||||
* The program shows the fields that are allowed for each type:
|
||||
|
|
@ -28,7 +28,7 @@ Users must carry out the following steps to manage the quality forms:
|
|||
* Percentage: question and percentage.
|
||||
* Item: question.
|
||||
|
||||
* Click “Save” or “Save and continue”.
|
||||
* Click "Save" or "Save and continue".
|
||||
|
||||
.. figure:: images/quality.png
|
||||
:scale: 50
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Users
|
||||
Users
|
||||
########
|
||||
|
||||
.. _tareas:
|
||||
|
|
@ -17,27 +17,27 @@ Managing users
|
|||
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.
|
||||
|
||||
|
||||
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.
|
||||
* 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:
|
||||
|
||||
* User name.
|
||||
* Password
|
||||
* Authorised/unauthorised.
|
||||
* 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 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 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.
|
||||
|
||||
.. figure:: images/manage-user.png
|
||||
:scale: 50
|
||||
|
||||
Managing users
|
||||
|
||||
* Click “Save” or “Save and continue”.
|
||||
* Click "Save" or "Save and continue".
|
||||
|
||||
|
||||
Managing profiles
|
||||
|
|
@ -45,13 +45,13 @@ Managing 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.
|
||||
* 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:
|
||||
|
||||
* 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
|
||||
:scale: 50
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ Managing hour types worked
|
|||
|
||||
Users need to carry out the following steps to register hour types worked:
|
||||
|
||||
* Select “Manage hour types worked ” on the “Administration” menu.
|
||||
* Select "Manage hour types worked" on the "Administration" menu.
|
||||
* The program shows a list of existing hour types.
|
||||
|
||||
.. figure:: images/hour-type-list.png
|
||||
|
|
@ -37,7 +37,7 @@ Users need to carry out the following steps to register hour types worked:
|
|||
|
||||
Hour type list
|
||||
|
||||
* Click “Edit” or “Create”.
|
||||
* Click "Edit" or "Create".
|
||||
* The program shows an hour type editing form.
|
||||
|
||||
.. figure:: images/hour-type-edit.png
|
||||
|
|
@ -52,22 +52,22 @@ Users need to carry out the following steps to register hour types worked:
|
|||
* The default rate.
|
||||
* Hour type activation/de-activation.
|
||||
|
||||
* Click “Save” or “Save and continue”.
|
||||
* Click "Save" or "Save and continue".
|
||||
|
||||
Cost categories
|
||||
-------------------
|
||||
|
||||
Users need to carry out the following steps to register cost categories:
|
||||
|
||||
* Select “Manage cost categories” on the “Administration” menu.
|
||||
* Select "Manage cost categories" on the "Administration" menu.
|
||||
* The program shows a list of existing categories.
|
||||
|
||||
.. figure:: images/category-cost-list.png
|
||||
:scale: 50
|
||||
|
||||
Cost category list
|
||||
Cost category list
|
||||
|
||||
* Click “Edit” or “Create” button.
|
||||
* Click "Edit" or "Create" button.
|
||||
* The program shows a cost category editing form.
|
||||
|
||||
.. figure:: images/category-cost-edit.png
|
||||
|
|
@ -85,8 +85,8 @@ Users need to carry out the following steps to register cost categories:
|
|||
* Start and finish date (the latter is optional) for the period that applies to the cost category.
|
||||
* Hourly rate for this specific category
|
||||
|
||||
* Click “Save” or “Save and continue”.
|
||||
* Click "Save" or "Save and continue".
|
||||
|
||||
|
||||
The assignment of cost categories to resources is described in the chapter on resources. Go to the “Resources” section.
|
||||
The assignment of cost categories to resources is described in the chapter on resources. Go to the "Resources" section.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
Reports
|
||||
=======
|
||||
|
||||
“NavalPlan” is integrated with *JasperReports* to manage reports, which allows users to enter various reports to analyse available data in the program.
|
||||
"NavalPlan" is integrated with *JasperReports* to manage reports, which allows users to enter various reports to analyse available data in the program.
|
||||
|
||||
The defined reports are:
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
#
|
||||
|
||||
RST_HTML_FLAGS = --link-stylesheet --stylesheet-path=html/lsr.css
|
||||
RST_TEX_FLAGS = --documentclass=igaliabk --font-encoding=OT1
|
||||
RST_TEX_FLAGS = --documentclass=igaliabk --font-encoding=OT1 --output-encoding=utf-8
|
||||
OUTPUT_BASE = output
|
||||
|
||||
rst_srcs := $(filter-out index.rst,$(wildcard *.rst))
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
#######################################
|
||||
Documentación de usuario da aplicación
|
||||
#######################################
|
||||
#############################
|
||||
Navalplan: User documentation
|
||||
#############################
|
||||
|
||||
.. image:: images/logo.png
|
||||
:align: left
|
||||
|
||||
No seguinte documento proporciónase a documentación de axuda necesaria para utilizar a aplicación de xestión da produción do auxiliar do naval NavalPlan.
|
||||
Following document contains necessary help for using Navalplan, the application for production and planning management for Galician ancillary naval industry.
|
||||
|
||||
Esta documentación estó organizada do seguinte modo:
|
||||
This document is divided in three main sections:
|
||||
|
||||
En primeiro lugar descrébense os obxectivos fundamentais da aplicación e o comportamento global da mesma a modo introductorio e como contextualización xeral do uso da mesma.
|
||||
First, global goals and behaviour.
|
||||
|
||||
A continuación introdúcense as entidades básicas que será necesario administrar para poder empregar todas as funcionalidades de NavalPlan e que se mencionarán nas seguintes seccións da documentación.
|
||||
Second, basic entities to understand the minimum concepts to use Navalplan.
|
||||
|
||||
Posteriormente, detállanse os procesos completos de creación de pedidos e proxectos, planificación, asignación de recursos, imputación de avances e extración de resultados.
|
||||
Finally, complete processes description to create orders, projects, project planning, resources assignment, advance assignment and result extraction.
|
||||
|
|
|
|||
|
|
@ -5,12 +5,12 @@ Documentación de usuario da aplicación
|
|||
.. image:: images/logo.png
|
||||
:align: left
|
||||
|
||||
No seguinte documento proporciónase a documentación de axuda necesaria para utilizar a aplicación de xestión da produción do auxiliar do naval NavalPlan.
|
||||
En el siguiente document se proporciona la documentación de ayuda necesaria para utilizar la aplicación de gestión de la producción y planificación del auxiliar del naval Navalplan.
|
||||
|
||||
Esta documentación estó organizada do seguinte modo:
|
||||
Esta documentación está organizada del siguiente modo:
|
||||
|
||||
En primeiro lugar descrébense os obxectivos fundamentais da aplicación e o comportamento global da mesma a modo introductorio e como contextualización xeral do uso da mesma.
|
||||
En primer lugar se describen los objetivos principales de la aplicación, comportamiento global y contextualización general del uso y necesidades de la misma.
|
||||
|
||||
A continuación introdúcense as entidades básicas que será necesario administrar para poder empregar todas as funcionalidades de NavalPlan e que se mencionarán nas seguintes seccións da documentación.
|
||||
A continuación se introducen las entidades básicas que será necesario conocer para utilizar las funcionalidades de Navalplan.
|
||||
|
||||
Posteriormente, detállanse os procesos completos de creación de pedidos e proxectos, planificación, asignación de recursos, imputación de avances e extración de resultados.
|
||||
Finalmente, se detallan los procesos completos de creación de pedidos, proyectos, planificación de proyectos, asignación de recursos, imputación de avances y extracción de resultados.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue