Differenze tra le versioni di "Project configuration steps - Basic information"

Da itm wiki.
(Etichetta: visualeditor)
 
(18 versioni intermedie di uno stesso utente non sono mostrate)
Riga 1: Riga 1:
''[[glossary|Project]]'' master data are managed in its ''[[Glossary|General]]'' tab.
+
''[[glossary|Project]]'' basic information are managed in its ''[[Glossary|General]]'' tab.
 
[[File:Project General tab screen.JPG|none|thumb|850x850px|Project General screen]]Here, the following information can be managed.
 
[[File:Project General tab screen.JPG|none|thumb|850x850px|Project General screen]]Here, the following information can be managed.
  
Riga 11: Riga 11:
 
|-
 
|-
 
| <u>Op. Status</u> ||  It defines/shows the operational status of the ''[[glossary|project]]''.
 
| <u>Op. Status</u> ||  It defines/shows the operational status of the ''[[glossary|project]]''.
||See the [[Project configuration steps - Introduction|introductory section]] for more information on ''[[glossary|project]]'' status.
+
||See the [[Project configuration steps - Introduction|introductory section]] for more information on ''[[glossary|project]]'' operational status.
  
 
|-
 
|-
 
| <u>Currency</u> || It defines/shows the reference currency used to manage financial information about the ''[[glossary|project]]'' (e.g. budget).
 
| <u>Currency</u> || It defines/shows the reference currency used to manage financial information about the ''[[glossary|project]]'' (e.g. budget).
||The reference currency shall be among one of those defined for the ''[[glossary|company]]''.
+
||The reference currency shall be among one of those defined for the ''[[glossary|company]]''. See also [[ItmSUITE® - Introduction to basic configuration#Company master data|company preparation page]].  
  
 
|-
 
|-
| <u>Adm. Status</u> || ||
+
| <u>Adm. Status</u> || It defines/shows the administrative status of the ''[[glossary|project]]''.
 +
||See the [[Project configuration steps - Introduction|introductory section]] for more information on administrative ''[[Glossary|project]] ''status.
  
 
|-
 
|-
| <u>Project Type</u> || ||
+
| <u>Project Type</u> || It defines/shows the ''[[Glossary|project]]'' type attribute which is used for classification and filtering / reporting aims.
 +
||See the [[Project configuration steps - Master data|project master data]] page for more information.
  
 
|-
 
|-
| <u>Project Class</u> || ||
+
| <u>Project Class</u> || It defines/shows the ''[[Glossary|project]]'' class attribute which is used for classification and filtering / reporting aims. However, the ''[[glossary|project]]'' class drives the definition of the set of ''[[glossary|semaphores]]'' to be used for the ''[[glossary|project]]''.
 +
||See the [[Project configuration steps - Master data|project master data]] page for more information on ''[[glossary|project]] ''classes. See the [[semaphores]] page for more information on ''[[glossary|semaphores]]''.
  
 
|-
 
|-
| <u>Parent Project</u> || ||
+
| <u>Parent Project</u> || ''[[glossary|Projects]]'' may be organized in a hierarchy for reporting, analysis aims. This field allows to define the father ''[[glossary|project]]'' of the edited one.
 +
||
  
 
|-
 
|-
| <u>Statistical Project</u> || ||
+
| <u>Statistical Project</u> || It defines/shows the ''[[Glossary|project]] ''attribute which is used for classification and filtering / reporting aims.
 +
||See the [[Project configuration steps - Master data|project master data]] page for more information.
  
 
|-
 
|-
| <u>External Project Code</u> || ||
+
| <u>External Project Code</u> || This field enables to store an alternative identifier of the ''[[glossary|project]]'', for example the one used in an external accounting system.
 +
||
  
 
|-
 
|-
| <u>Name</u> || ||
+
| <u>Name</u> || The name of the ''[[glossary|project]]''.
 +
||
  
 
|-
 
|-
| <u>Short <Description</u> || ||
+
| <u>Short Description</u> || A short description of the ''[[glossary|project]]''.
 +
||
  
 
|-
 
|-
| <u>Objectives</u> || ||
+
| <u>Objectives</u> || A textual description of the objectives of the ''[[glossary|project]]''.
 +
||
  
 
|-
 
|-
| <u>Background and Reasons</u> || ||
+
| <u>Background and Reasons</u> || A textual description of the background and reasons of the ''[[glossary|project]]''.
 +
||
  
 
|-
 
|-
| <u>Comment</u> || ||
+
| <u>Comment</u> || A text field available for comments on the ''[[glossary|project]]''.
 +
||
  
 
|-
 
|-
| <u>Internal Operational Start Date</u> || ||
+
| <u>Internal Operational Start Date</u> || The date (included)from which it is possible to work on any activities of the ''[[glossary|project]]''.
 +
||This is also he date from which it is possible to add records of actual work (''[[glossary|timesheets]]'') on the ''[[glossary|project]]''. It cannot be later than the <u>Internal Operational End Date</u>.
  
 
|-
 
|-
| <u>Internal Operational End Date</u> || ||
+
| <u>Internal Operational End Date</u> || The date (included) to which it is possible to work on any activities of the ''[[Glossary|project]]''.
 +
||This is also the date from which it is possible to add records of actual work (''[[Glossary|timesheets]]'') on the ''[[Glossary|project]]''.
 +
 
 +
It cannot be earlier than the <u>Internal Operational Start Date</u>.
  
 
|-
 
|-
| <u>Actual Start Date</u> || ||
+
| <u>Actual Start Date</u> || The date on which the ''[[glossary|project]]'' actually started.
 +
||This is edited by an authorized ''[[glossary|user]]'' and can be different (typically later) than the <u>Internal Operational Start Date</u>, normally to arrange pre-project activities.
 +
It cannot be later than the <u>Actual End Date</u>.
  
 
|-
 
|-
| <u>Actual End Date</u> || ||
+
| <u>Actual End Date</u> || The date on which the ''[[glossary|project]]'' actually ended.
 +
||This is edited by by an authorized ''[[glossary|user]] ''and can be different (typically earlier) than the <u>Internal Operational End Date</u>, normally to arrange post-project activities.
  
|-
+
It cannot be later than the <u>Actual Start Date</u>.
| <u>Initial Expected Start Date</u> || ||
 
  
 
|-
 
|-
| <u>Initial Expected End Date</u> || ||
+
| <u>Initial Expected Start Date</u> || The date initially (e.g. at budget time) expected for ''[[glossary|project]]'' start.
 +
||This is edited by an authorized ''[[Glossary|user.]] ''It cannot be later than the <u>Initial Expected End Date</u>.
  
 
|-
 
|-
| <u>Current Expected Start Date</u> || ||
+
| <u>Initial Expected End Date</u> || The date initially (e.g. at budget time) expected for ''[[glossary|project]] ''end.
 +
||This is edited by an authorized ''[[Glossary|user.]]''It cannot be earlier than the <u>Initial Expected Start Date</u>.
  
 
|-
 
|-
| <u>Current Expected End Date</u> || ||
+
| <u>Current Expected Start Date</u> || The date currently (e.g. at'' [[glossary|estimation]]'' date) expected for ''[[glossary|project]]'' start.
 +
||This is edited by an authorized ''[[Glossary|user.]]''It cannot be later than the <u>Current Expected End Date</u>.
  
 
|-
 
|-
| <u>Project Manager</u> || ||
+
| <u>Current Expected End Date</u> || The date currently (e.g. at ''[[glossary|estimation]] ''date) expected for ''[[glossary|project]] ''end.
 +
||This is edited by an authorized ''[[Glossary|user.]]''It cannot be earlier than the <u>Initial Expected Start Date</u>.
  
 
|-
 
|-
| <u>Client</u> || ||
+
| <u>Project Manager</u> || This is a mandatory field (actually a list)) where it is possible to define one or more ''[[glossary|resources]]'' (typically one) playing the role of the project manager for the ''[[glossary|project]]''.
 +
||It is only possible to assign ''[[glossary|resources]]'' with <u>Status</u> "Active" associated with a ''[[glossary|user]]'' with <u>Status</u> "Active" and ''[[glossary|application level role]]'' equal to "pm" (project manager).
  
 
|-
 
|-
| <u>Contract Referent</u> || ||
+
| <u>Client</u> || The client asking for the ''[[glossary|project]].''
 +
||This field can be chosen among the list of ''[[glossary|clients]]''.
  
 
|-
 
|-
| <u>Contract Referent Role</u> || ||
+
| <u>Contract Referent</u> || A textual field which lets store the name of the ''[[glossary|project]]''<nowiki/>'s contract'' ''interface for the <u>Client</u>.
 +
||
  
 
|-
 
|-
| <u>Current Expected Start Date</u> || ||
+
| <u>Contract Referent Role</u> || A textual field which lets store the role of the ''[[glossary|project]]''<nowiki/>'s contract interface for the <u>Client</u>.
 +
||
  
 
|-
 
|-
| <u>Final Client</u> || ||
+
| <u>Final Client</u> || In some cases there can be a client of the <u>Client</u> which can be recorded in this field.
 +
||This field can be chosen among the list of ''[[glossary|clients]]''.
  
 
|-
 
|-
| <u>Project Referent</u> || ||
+
| <u>Project Referent</u> || A textual field which lets store the name of the ''[[glossary|project]]''<nowiki/>'s interface for the <u>Client</u>.
 +
||
  
 
|-
 
|-
| <u>Project Referent Role</u> || ||
+
| <u>Project Referent Role</u> || A textual field which lets store the role of the ''[[glossary|project]]''<nowiki/>'s interface for the <u>Client</u>.
 +
||
  
 
|}
 
|}

Versione attuale delle 21:45, 10 feb 2016

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.