Project configuration steps - Basic information
Da itm wiki.
Versione del 10 feb 2016 alle 12:22 di Maxime.sottini (discussione | contributi)
Project basic information are managed in its General tab.
Here, the following information can be managed.
| Field | Purpose | Comments |
|---|---|---|
| Code | The numeric identifier of the project. | Automatically generated by the system. |
| Op. Status | It defines/shows the operational status of the project. | See the introductory section for more information on project operational status. |
| Currency | It defines/shows the reference currency used to manage financial information about the project (e.g. budget). | The reference currency shall be among one of those defined for the company. See also company preparation page. |
| Adm. Status | It defines/shows the administrative status of the project. | See the introductory section for more information on administrative project status. |
| Project Type | It defines/shows the project type attribute which is used for classification and filtering / reporting aims. | See the project master data page for more information. |
| Project Class | It defines/shows the project class attribute which is used for classification and filtering / reporting aims. However, the project class drives the definition of the set of semaphores to be used for the project. | See the project master data page for more information on project classes. See the semaphores page for more information on semaphores. |
| Parent Project | Projects may be organized in a hierarchy for reporting, analysis aims. This field allows to define the father project of the edited one. | |
| Statistical Project | It defines/shows the project attribute which is used for classification and filtering / reporting aims. | See the project master data page for more information. |
| External Project Code | This field enables to store an alternative identifier of the project, for example the one used in an external accounting system. | |
| Name | The name of the project. | |
| Short Description | A short description of the project. | |
| Objectives | A textual description of the objectives of the project. | |
| Background and Reasons | A textual description of the background and reasons of the project. | |
| Comment | A text field available for comments on the project. | |
| Internal Operational Start Date | The date (included)from which it is possible to work on any activities of the project. | This is tlso he date from which it is possible to add records of actual work (timesheets) on the project. |
| Internal Operational End Date | The date (included) to which it is possible to work on any activities of the project. | This is also the date from which it is possible to add records of actual work (timesheets) on the project.
It cannot be earlier than the Internal Operational Start Date. |
| Actual Start Date | The date on which the project actually started. | This is edited by the user and can be different (typically later) than the Internal Operational Start Date, normally to arrange pre-project activities |
| Actual End Date | ||
| Initial Expected Start Date | ||
| Initial Expected End Date | ||
| Current Expected Start Date | ||
| Current Expected End Date | ||
| Project Manager | ||
| Client | ||
| Contract Referent | ||
| Contract Referent Role | ||
| Current Expected Start Date | ||
| Final Client | ||
| Project Referent | ||
| Project Referent Role |
