Differenze tra le versioni di "Project configuration steps - Master data"
Da itm wiki.
(Etichetta: visualeditor) |
(Etichetta: visualeditor) |
||
| (27 versioni intermedie di uno stesso utente non sono mostrate) | |||
| Riga 1: | Riga 1: | ||
''[[glossary|Projects]]'' use some specific master data which can be found managed in '''''General/Projects'''''. | ''[[glossary|Projects]]'' use some specific master data which can be found managed in '''''General/Projects'''''. | ||
| − | + | Therefore, it is recommended to setup theses data before starting to work on ''[[glossary|projects]]''. | |
| − | The | + | {| class="wikitable sortable" |
| + | ! '''''Field''''' !! '''''Purpose''''' !! '''''Comments''''' | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Activity Priorities''''' || This function enables to manage the prioritization attribute, which is used to categorize the ''[[glossary|project activity]]'' priority (e.g. "Low", "Medium" and "High"). | ||
| + | ||The categorization may be used to highlight, sort, filter, ''[[glossary|project activities]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Activity Statuses''''' || This function enables to manage the possible statuses of ''[[glossary|project activities]]''. | ||
| + | ||The status may influence the possibility of entering ''[[glossary|timesheets]]'' on ''[[glossary|project activities]]''. This is set through the <u>Disable for TS</u> parameter (if set, no ''[[glossary|timesheet]]'' can be entered for ''[[glossary|project activities]]'' in this status). | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Activity Types''''' || This function enables to define the possible types for a ''[[glossary|project activity]]'' (e.g. "Analysis", "Implementation", "Test"). | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|project activities]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Cost Occurrences Categories''''' || This function enables to defines the possible types for a ''[[glossary|cost occurrence]]'' (e.g. "HW", "SW", "Services", etc.). | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|cost occurrences]]''. However, it has to be noted that budgeting ''[[glossary|cost occurrences]]'' in ''[[glossary|estimations]]'' is done based on these categories (e.g. "100" for "HW"). | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Issue Priorities''''' || This function enables to define the possible priorities for a ''[[glossary|project issue]]'' (e.g. "Low", "Medium", "High"). | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|project issues]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Risk Proximity''''' || This attribute is used to categorize ''[[glossary|project risks]]'' proximity (e.g. "Immediate", "Soon (months)", "Late (year)"). | ||
| + | ||The categorization may be use to highlight, sort, filter ''[[glossary|project risks]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Issue Subjects''''' || This function is used to define the topics to which a ''[[glossary|project issue]]'' may be related. | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|project issues]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Milestones''''' || This function is used to manage (create, update, delete) the possible types of ''[[glossary|project milestones]]'' (e.g. "Start", "Closure", etc.). | ||
| + | ||For ''[[glossary|project milestones]]'' it requires to define the allowed types of ''[[glossary|project milestones]]'' predecessors. In ''[[glossary|projects]]'', It won't be possible to create a milestone of a specific types if its temporary predecessor is not belonging to an allowed type. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Project Types''''' || This function enables to define the possible types for a ''[[glossary|project]] ''(e.g. "Regulatory", "Business critical", etc.). | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|projects]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Project Classes''''' || This function enables to define the possible ''[[glossary|projects]]'' classification. | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|projects]]''. For each ''[[glossary|project]]'' class it is possible to associate a set of ''[[glossary|project semaphores]]'' which will be used instead of the standard definitions (see '''''General/Projects/Semaphores''''' next). | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Semaphores''''' || This function enables to manage generic ''[[glossary|project semaphores]].'' | ||
| + | ||Generic ''[[glossary|project semaphores]]'' are used in reports if specific ''[[glossary|project semaphores]]'' for each ''[[glossary|project]]'' class (see '''''General/Projects/Project Classes''''') are not defined. See also [[semaphores]] page for more information. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Categories''''' || This function enables to define the possible ''[[Glossary|projects]]'' categorization. | ||
| + | ||The categorization may be used to highlight, sort, filter ''[[glossary|projects]]''. | ||
| + | |||
| + | |- | ||
| + | | '''''General/Projects/Delivery Impact''''' || This function enables to define the possible ''[[glossary|project delivery]]'' impacts (e.g. "Low", "Medium", "high"). | ||
| + | ||This categorization may be used to highlight, sort, filter ''[[glossary|project deliveries]]''. | ||
| + | |||
| + | |} | ||
Versione attuale delle 11:34, 10 feb 2016
Projects use some specific master data which can be found managed in General/Projects.
Therefore, it is recommended to setup theses data before starting to work on projects.
| Field | Purpose | Comments |
|---|---|---|
| General/Projects/Activity Priorities | This function enables to manage the prioritization attribute, which is used to categorize the project activity priority (e.g. "Low", "Medium" and "High"). | The categorization may be used to highlight, sort, filter, project activities. |
| General/Projects/Activity Statuses | This function enables to manage the possible statuses of project activities. | The status may influence the possibility of entering timesheets on project activities. This is set through the Disable for TS parameter (if set, no timesheet can be entered for project activities in this status). |
| General/Projects/Activity Types | This function enables to define the possible types for a project activity (e.g. "Analysis", "Implementation", "Test"). | The categorization may be used to highlight, sort, filter project activities. |
| General/Projects/Cost Occurrences Categories | This function enables to defines the possible types for a cost occurrence (e.g. "HW", "SW", "Services", etc.). | The categorization may be used to highlight, sort, filter cost occurrences. However, it has to be noted that budgeting cost occurrences in estimations is done based on these categories (e.g. "100" for "HW"). |
| General/Projects/Issue Priorities | This function enables to define the possible priorities for a project issue (e.g. "Low", "Medium", "High"). | The categorization may be used to highlight, sort, filter project issues. |
| General/Projects/Risk Proximity | This attribute is used to categorize project risks proximity (e.g. "Immediate", "Soon (months)", "Late (year)"). | The categorization may be use to highlight, sort, filter project risks. |
| General/Projects/Issue Subjects | This function is used to define the topics to which a project issue may be related. | The categorization may be used to highlight, sort, filter project issues. |
| General/Projects/Milestones | This function is used to manage (create, update, delete) the possible types of project milestones (e.g. "Start", "Closure", etc.). | For project milestones it requires to define the allowed types of project milestones predecessors. In projects, It won't be possible to create a milestone of a specific types if its temporary predecessor is not belonging to an allowed type. |
| General/Projects/Project Types | This function enables to define the possible types for a project (e.g. "Regulatory", "Business critical", etc.). | The categorization may be used to highlight, sort, filter projects. |
| General/Projects/Project Classes | This function enables to define the possible projects classification. | The categorization may be used to highlight, sort, filter projects. For each project class it is possible to associate a set of project semaphores which will be used instead of the standard definitions (see General/Projects/Semaphores next). |
| General/Projects/Semaphores | This function enables to manage generic project semaphores. | Generic project semaphores are used in reports if specific project semaphores for each project class (see General/Projects/Project Classes) are not defined. See also semaphores page for more information. |
| General/Projects/Categories | This function enables to define the possible projects categorization. | The categorization may be used to highlight, sort, filter projects. |
| General/Projects/Delivery Impact | This function enables to define the possible project delivery impacts (e.g. "Low", "Medium", "high"). | This categorization may be used to highlight, sort, filter project deliveries. |
