Project configuration steps - Basic information

Project basic information are managed in its General tab.

Project General screen

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 also he date from which it is possible to add records of actual work (timesheets) on the project. It cannot be later than the Internal Operational End Date.
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 an authorized user and can be different (typically later) than the Internal Operational Start Date, normally to arrange pre-project activities. It cannot be later than the Actual End Date.
Actual End Date	The date on which the project actually ended.	This is edited by by an authorized user and can be different (typically earlier) than the Internal Operational End Date, normally to arrange post-project activities. It cannot be later than the Actual Start Date.
Initial Expected Start Date	The date initially (e.g. at budget time) expected for project start.	This is edited by an authorized user. It cannot be later than the Initial Expected End Date.
Initial Expected End Date	The date initially (e.g. at budget time) expected for project end.	This is edited by an authorized user.It cannot be earlier than the Initial Expected Start Date.
Current Expected Start Date	The date currently (e.g. at estimation date) expected for project start.	This is edited by an authorized user.It cannot be later than the Current Expected End Date.
Current Expected End Date	The date currently (e.g. at estimation date) expected for project end.	This is edited by an authorized user.It cannot be earlier than the Initial Expected Start Date.
Project Manager	This is a mandatory field (actually a list)) where it is possible to define one or more resources (typically one) playing the role of the project manager for the project.	It is only possible to assign resources with Status "Active" associated with a user with Status "Active" and application level role equal to "pm" (project manager).
Client	The client asking for the project.	This field can be chosen among the list of clients.
Contract Referent	A textual field which lets store the name of the project's contract interface for the Client.
Contract Referent Role	A textual field which lets store the role of the project's contract interface for the Client.
Final Client	In some cases there can be a client of the Client which can be recorded in this field.	This field can be chosen among the list of clients.
Project Referent	A textual field which lets store the name of the project's interface for the Client.
Project Referent Role	A textual field which lets store the role of the project's interface for the Client.