Differenze tra le versioni di "Project configuration steps - Others"
(→Issues/Risks) |
(→Issues/Risks) (Etichetta: visualeditor) |
||
| Riga 88: | Riga 88: | ||
|- | |- | ||
| − | | <u>Creation User</u> || || || || || || | + | | <u>Creation User</u> || || X |
| + | || X | ||
| + | || X | ||
| + | || X | ||
| + | || | ||
|- | |- | ||
| − | | <u>Creation Date</u> || || || || || || | + | | <u>Creation Date</u> || || X |
| + | || X | ||
| + | || X | ||
| + | || X | ||
| + | || | ||
|- | |- | ||
| − | | <u>Edit User</u> || || || || || || | + | | <u>Edit User</u> || || X |
| + | || X | ||
| + | || X | ||
| + | || X | ||
| + | || | ||
|- | |- | ||
| − | | <u>Edit Date</u> || || || || || || | + | | <u>Edit Date</u> || || X |
| + | || X | ||
| + | || X | ||
| + | || X | ||
| + | || | ||
|- | |- | ||
| − | | <u>Number</u> || || || || || | + | | <u>Number</u> || || X |
| + | || X | ||
| + | || X | ||
| + | ||X | ||
|- | |- | ||
| − | | <u>Close Flag</u> || || || || || || | + | | <u>Close Flag</u> || || X |
| + | || || || || | ||
|- | |- | ||
Versione delle 16:25, 31 mar 2016
In order to properly deal with a project, it can be needed/useful to manage additional information.
Indice
Agreements
These functionalities and related guide are currently under review. Refer to itmSUITE support for more information.
Cost Occurrences
In this section it is possible to enter actual cost occurences for the project. The budget for cost occurrence categories is defined in estimations (see the estimation guide section). Cost occurrences management is possible only if the FM - Financial Management module is active.
| Field | Description | Comment
|
|---|---|---|
| Description | This is the textual description of the cost occurrence. | |
| Competence Period | The competence period to which the cost occurrence refers. | The type of competence periods is defined for the project (see estimations guide). A competence period can be added among those specifically activated for the estimation (see estimations guide). |
| Activity | The project activity to which the cost occurrence refers. | Project activities are managed in the Activities section. |
| External Activity Code(s) | A read only text reporting the external activity code(s). | The external activity code can be used to match the cost occurrence with project activities. |
| Cost Occurrence Category | The category for the cost occurrence. | The cost occurrence category is a classification of the type of cost (e.g. hardware, software, services). The cost occurrence categories in General/Projects/Cost Occurrence Categories. |
| Occurrence Date | The date when the cost occurs. | This date is a convention. For example the date when the order to which the cost refers is issued is often used as the occurrence date. |
| Currency | The currency of the cost occurrence. | |
| Value | The amount of the cost occurrence in the Currency. | |
| Reference Number | A text which can be used to store a reference for the cost | |
| Supplier Name | A text where to store the name of the supplier of the cost occurrence. | |
| Accounting Order | A text where to store the order identifier to which the cost occurrence refers. | The order which is issued and sent to the supplier to which the cost occurrence refers. |
| Order Row | A text where to store the order row identifier to which the cost occurrence refers. | |
| Internal Order | A text where to store another order identifier to which the cost occurrence refers. | In some organizations an internal order is issued before an external (the one issued to the supplier) is done. |
| Reference User | A text where the name of the user owner of the cost occurrence can be entered. | |
| Cost Dimension | The cost occurrence dimension. |
Documents
In this section it is possible to manage documents specifically related to the project. See document management guide for more information on how to manage documents.
Daily Log
The Daily Log allows to enter logs about any events related to the project. Logs can be related to any to the key project entities (resources, project activities, project milestones, etc.). See managing records in standard mode for more information on how to manage the daily log records.
Issues/Risks
This section allows to manage project issues and project risks. They are both managed with a single entity which can be either a project issue, a project off-specs, a project RFC or a project risk.
Semaphores....
| Field | Description | Issue | Risk | Off-specs | RFC | Comment
|
|---|---|---|---|---|---|---|
| Creation User | X | X | X | X | ||
| Creation Date | X | X | X | X | ||
| Edit User | X | X | X | X | ||
| Edit Date | X | X | X | X | ||
| Number | X | X | X | X | ||
| Close Flag | X | |||||
| Category Name | ||||||
| Description | ||||||
| Estimated Date | ||||||
| Closure Date | ||||||
| Referent | ||||||
| Issue Subject | ||||||
| Issue Priority | ||||||
| Criticality Level | ||||||
| Value | ||||||
| Probability | ||||||
| Proximity | ||||||
| Weighed Value | ||||||
| Mitigation Actions | ||||||
| Comments |
History
In the History section the updates of project key data are logged.
Reports
Messages
In this section it is possible to manage messages specifically related to the project. See messages management guide for more information on how to manage messages.
Models
Sale Contracts
In this section, one or more sale contracts related to the project can be assigned. Sales contracts are use to bill or assign a value to project activities. Sales contracts can be fixed price or time&material. In any case only sales contracts for one project Client (defined in the General section) can be entered and they should not overlap (Term Start Date and Term End Date). For more information on sales contracts, see the client management guide.
To manage sales contract the FM - Financial Management module shall be active.
