Logo
  • Other versions
  • Virage Group
  • Espace Magenta
  • Support ticket
  • Strat Monitor documentation
Project Monitor v7.7 Knowledge Center
Project Monitor v7.7 Knowledge Center
/Technical memos
Technical memos
/Memo Office Sheets
Memo Office Sheets
Memo Office Sheets

Memo Office Sheets

‣
Table of contents
‣
history modifications
‣
Download appendices
🚀

The new-generation summary sheets are now available in beta version on Project MonitorProject Monitor. To find out more : Use summary sheets (Word/Powerpoint)Use summary sheets (Word/Powerpoint)

1. Purpose of the document

The purpose of this document is to explain how to create an office file in Project MonitorProject Monitor.

Office sheets are summary documents on a project, phase or milestone. They can then be opened and modified in word-processing software (Word, Libre Office, OpenOffice...).

Office files are generated from a template, or file model, created by the user or by Virage GroupVirage Group during parameterization. These forms determine the formatting of the file, as well as its various components (attributes, structure link, etc.).

The objectives of the document are as follows:

  • present the creation of an office file template ;
  • show how to set up an office-type view summary sheet ;
  • suggest best practices.

2. Prerequisites

The office data sheet can be used to trace most of the elements that characterize a project, a phase or a milestone.

To create the model, it is essential that the attributes, hierarchies, phases and milestones created in Project MonitorProject Monitor have a code.

3. Creation of an office file template

Depending on the office software, templates can be created to automatically generate project sheets. These sheets use the same composition elements and call up the same fields and codes.

The layout of the template differs, however. Word uses merge fields, whereas PowerPoint only needs to insert the codes to be called up in its content. Images are also handled differently.

3.1 Word template

3.1.1 document format

The template can be created in Libre Office Writer, OpenOffice Writer or Microsoft Word.

It must be saved in .docx.

3.1.2 Creating text merge fields

The office project sheet can only be edited in Word (not in Libre Office).

In order for the model to retrieve Project MonitorProject Monitorto create merge fields in the document.

Example: To retrieve my project label in my office automation file, I need to insert a merge field in my document that will retrieve the project label (see the list of codes for the various elements in the table below).

A merge field is always preceded by the symbol $.

To create my fusion field, I press Ctrl + F9.

I then right-click on my field and click on Field modification :

image

I open a window Field. In the left-hand column, I select MergeField then in Field propertiesI enter my field code in the field name. Then I click on OK.

image
✅
Once these steps have been completed, my merge field is created. If I wish to modify my code, I return to the field modification screen to change the field name.

3.1.3 Inserting an image

A link can be created to retrieve the project logo and place it on the DOCX file.

To do this, first add an image to the document.

3.1.3.1 In Microsoft Word

3.1.3.1.1 An image of an image attribute

  1. I click on Insertion > Images and select the image to insert.
  2. I click on the image, go to the tab Insertion in Word and click on Bookmark.
  3. The window Bookmark opens.

  4. I enter the name of my bookmark, then click on Add. Mémo Fiches Office - 3.3 List of fields and corresponding codesMémo Fiches Office - 3.3 List of fields and corresponding codes
  5. 🚨
    Caution: do not use $ in front of the bookmark name.
image
image

3.1.3.1.2 A list attribute icon

  1. Insert an image.
  2. On this image, insert a bookmark.
  3. The window Bookmark opens.

  4. I enter the name of my bookmark Mémo Fiches Office - 3.3 List of fields and corresponding codesMémo Fiches Office - 3.3 List of fields and corresponding codes
  5. 🚨
    Caution: do not use $ in front of the bookmark name.

    2 ways to put this icon :

    The bookmark name can be attribute if there are no merge fields with the same code, i.e. no merge fields attribute

    The bookmark name can be attribute in all cases

    The bookmark name MUST be attribute if there is a merge field with the same code i.e. attribute (otherwise only the merge field is replaced, not the image)

  6. I click on Add.
image

3.1.3.1.3 A theme color indicator

  1. Insert an image in the template, which will be replaced by the colorindicator .
  2. On this image, insert a bookmark.
  3. The " Bookmark "opens.

  4. I enter the name of my bookmark.
  5. I click on Add.
🚨
Caution: do not use $ in front of the bookmark name.

The bookmark name must follow the codes below according to theindicator to be sent up:

  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT

Only the exchangeindicator is not concerned, as it has no relevance.

3.1.3.1.4 The Gantt :

  1. I click on Insertion > Images
  2. I choose the image to insert.
  3. Once the image has been inserted, I click on it and go to the Insertion in Word and click on Bookmark.
  4. The window Bookmark opens.

  5. Enter bookmark name PROP_GANTTthen click on Add.
🚩
Note: The generated Gantt takes up all the space of the dimensioned image in the office file. If it's illegible, it's because the dimensions are not initially adapted in the template.
image
image

3.1.3.2 On LibreOffice Writer or OpenOffice Writer

  1. In the menu bar, I click on Insertion > Image > From a file.
  2. I choose the image to insert.
  3. Once the image has been added, I right-click on it and click on Image
  4. The menu Image opens.

  5. I click on the Options.
  6. In the Name of the image, I enter the code for my logo. Mémo Fiches Office - 3.3 List of fields and corresponding codesMémo Fiches Office - 3.3 List of fields and corresponding codes.
  7. I click on OK.
image
image
image

3.1.4 Inserting a table

For some elements, you'll want to display a list of values of variable size. For example, I'd like to display a list of indicator labels linked to a project.

To do this, I use a code like this: LIST_INDICATORS.LABEL. This code can be broken down into two parts:

  1. LIST_INDICATORS The first part tells me what type of element I want to reassemble. In this case, I want to bring up anindicator list element.
  2. LIBEL The second part tells me which element I want to lift. In this case, I'd like to move up my indicator label.

Visit . between INDICATORS and LIBEL indicates that I'd like to have the list of indicator labels. By inserting this value in a table line, when the office form is published, a line will be created for each indicator.

Similarly, the $LISTE_INDICATEURS.CODE will return the list of indicator codes, the code $BUDGETS_LIST.TARGET_REP will send me the list of budget targets, etc. (Mémo Fiches Office - 3.3 List of fields and corresponding codesMémo Fiches Office - 3.3 List of fields and corresponding codes.

Example:
Example: Template for a form where I want to display the project label and the list of indicators.

This document will give me the following result:

image

If I want to have the label, target and completed of the indicators in the same table, I enter the merge fields for the three elements on the same line and in a different column, as shown below:

image

For example, this model sends me the following sheet:

image

3.1.5 phase / milestone level cards

In milestone records, milestone information can be displayed in the same way as for projects.

For example, a merge field with the code $PROP_LIBELLE will return the phase label on a phase form, and the project label on a project form. The object label is always used.

It is also possible to display project information in the phase sheet, by prefixing the merge field codes with PROJECT_.

For example, in a phase record, if you want to bring up the phase label and the project label, simply add the following merge fields:

  • Project name : $PROJET_PROP_LIBELLE
  • phase name : $PROP_LIBELLE

This applies to all fields: project properties, attributes, budgets, risks, etc. can be displayed in a phase form.

3.2 PowerPoint template

3.2.1 document format

The template can be created in PowerPoint.

It must be saved in .pptx.

3.2.2 How it works

The codes are the same as for the .docx.

🚨

Please note: The format of rich attributes and " message " properties (= exchange) is not reflected on the form.

Create the project sheet template, inserting text boxes for fixed field labels and text boxes with field codes, preceded by a $. The board is very practical.

3.2.2.1 For a text field

If a text field is to be reassembled in a PowerPoint project sheet, it must be preceded by $.

Ex : $PROP_LIBELLE
Ex : $PROP_LIBELLE

3.2.2.2 For an image

To bring up an image in a PowerPoint project file, you need to use the code of the field to be brought up, which must be positioned in the PowerPoint image description (see screenshot of the file template).

Insert the images and embed the corresponding codes in the Description. When the project sheet is generated, the image will be replaced by the project image with the same code.

‣

Why aren't the images displayed correctly in my PowerPoint file?

3.2.2.2.1 To bring up a property image

Example with the project logo property
Example with the project logo property PROP_LOGO

3.2.2.2.2 To bring up an attribute image

The imageattribute code is ILLUSTATION. This works in the same way as for attributes. You must therefore insert attribute before theattribute code. So : attribute in this case. The question mark will be replaced by the image present in the project when the project sheet is generated.

Ex: To bring up an image attribute .
Ex: To bring up an image attribute .

3.2.2.2.3 Bringing up an icon from a list attribute

Theattribute code is attribute. This works in the same way as for attributes. You must therefore insert attribute before theattribute code. So : attribute in this case.

The green frog in the model will be replaced by the weather icon entered in the project.

🚩
Images present in the project sheet template, which are to be replaced by real values when the project sheet is generated, must not have the same name.
Ex: weather attribute .
Ex: weather attribute .

3.2.2.2.4 To raise a theme's colorindicator

Insert an image in the template, which will be replaced by the theme 's colorindicator when the office file is generated.

Right-click on the image and select Image format / Replacement text and in the description indicate the code of the cockpit to be brought up:

  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT
  • COCKPIT

Only the exchangeindicator is not concerned, as it has no relevance.

3.2.2.2.5 Bringing up a Gantt chart image :

Insert an image, then right-click and select Edit replacement text. In the description field, enter the code PROP_GANTT.

Here's the result
Here's the result
image

3.2.3 Limitation

There is one limitation to the implementation of the xdocreport for PowerPoint. This means that the wording of an exchange is not opposite the message linked to it, unlike the representation in the Word file.

3.3 List of fields and corresponding codes

The following fields and codes apply to the creation of Word and PowerPoint project sheet templates.

3.3.1 Note on the previous version

V5.4.3 of Project MonitorProject Monitor integrates the following groups of fields in addition to those of V5.4.1 :

  • Tasks filtered by type
  • Project information in phase / milestone sheets
🚨
Please note that for rich text attributes, font colors and table border colors are not transferred. Some formatting of rich text attributes (line feeds in tables, bulleted lists in tables) is suppressed when the office file is generated, as it causes errors.

3.3.2 List of fields

The table below lists the codes to be entered for the merge fields.

🚩
Reminder:
  • To display project information in a phase sheet, it must be prefixed with PROJECT_. attribute thus becomes $PROJET_ATTRIBUT_xxx.
  • Listed properties, with or without filters, only work if they're in a table. The table format is therefore MANDATORY.
ELEMENTS
CODE
current period
$PERIOD
PROPERTIES
Code
$PROP_CODE
Wording
$PROP_LIBELLE
Long label
$PROP_LIBELLE_LONG
Description
$PROP_DESCRIPTION
Start date (project)
$PROP_DATE_DEBUT
End date (project)
$PROP_DATE_FIN
status
$PROP_STATUT
project manager (project)
$PROP_PROJECT_MANAGER
Logo (image bookmark) (project)
PROP_LOGO (no $ symbol for bookmarks)
Father project
$PROP_PROJET_PERE
target start date (for phases)
$PROP_TARGET_GOAL
target end date (for phases and milestones)
$PROP_END_TARGET
Estimated start date (for phases)
$PROP_DEBUT_ESTIME
Estimated end date (for phases and milestones)
$PROP_FIN_ESTIME
manager (for phases and milestones)
$PROP_RESP_PHASE
ATTRIBUTES
All attribute (except image)
attribute (where xxx is theattribute code)
attribute (image)
attribute
structure link AUX HIERARCHIES
structure link
$structurestructure link (where xxx is the structure code)
Breadcrumb trail
$FIL_ARIANE_XXX (where XXX is the structure code) Retrieves the structure's tree structure. In return, the structure 's level values are displayed, separated by the separators below: > between the different levels of the breadcrumb trail / between two different Ariadne threads , between two level values on the same breadcrumb trail
TEAM
role
$LISTE_EQUIPES.ROLE_LIBELLE
First name
$LISTE_EQUIPES.USER_PRENOM
Name
$TEAM_LIST.USER_NAME
Retrieve team information by role
Each information above can be limited to 1 given role , by inserting the role code. - $LISTE_EQUIPES_XXX.ROLE_LIBELLE - $LISTE_EQUIPES_XXX.USER_PRENOM - $LISTE_EQUIPES_XXX.USER_NOM (where XXX is the role code)
PLANNING
Code
$LISTE_PLANNING.CODE
Libelle
$LISTE_PLANNING.LIBELLE
Parent
$LISTE_PLANNING.PARENT
Type
$LISTE_PLANNING.TYPE
Assigned
$LISTE_PLANNING.ASSIGN
Status
$LISTE_PLANNING.ETAT
Message
$LISTE_PLANNINGMESSAGE
Synchronization dates
$LISTE_PLANNING.DATES_SYNCHRO
Start target
$LISTE_PLANNING.DEBUT_TARGET
estimated start
$LISTE_PLANNING.DEBUT_ESTIME
End date
$LISTE_PLANNING.FIN_TARGET
Estimated end date
$LISTE_PLANNING.FIN_ESTIME
milestoneattribute
$PLANNING_LISTattribute (where xxx is theattribute code)
module attribute
$LISTE_PLANNING.PROJET_XXX (where xxx is theattribute code)
Current phase label
$PLANNING_PHASE_ACTUAL.LIBELLE
target start date of current phase
CURRENT_PHASE_PLANNING.TARGET_START_DATE
target end date of current phase
CURRENT_PHASE_PLANNING.TARGET_END_DATE
Estimated start date of current phase
$PLANNING_PHASE_ACTUAL.DATE_DEBUT_ESTIME
Estimated end date of current phase
$PLANNING_PHASE_ACTUAL.DATE_FIN_ESTIME
Objects filtered by phase and milestone planning type/type
$LISTE_PLANNING_XXX.LIBELLE (where xxx is the code of the phase type list value or the phaseattribute ) Ex: $LISTE_PLANNING_TYPE_ETUDE.LIBELLE
Next milestones of a given type
$PLANNING_NEXT_MILESTONE_XXX.LIBELLE (where XXX is the code of the milestone type list value) Ex: $PLANNING_PROCHAIN_CADRAGE.LIBELLE
Estimated end date of next milestones of a given type
$PLANNING_NEXT_MILESTONE_XXX.ESTIMATED_END_DATE (where XXX is the code of the milestone type list value) Ex:$PLANNING_PROCHAIN_CADRAGE.DATE_FIN_ESTIMEE
Gantt
Create bookmark with name PROP_GANTT
exchange
Subject
$EXCHANGE_LIST.SUBJECT
Message
$EXCHANGE_LISTMESSAGE
Transmitter
$LISTE_ECHANGES.EMETTEUR
Type
$EXCHANGE_LIST.TYPE
Declared date
$EXCHANGE_LIST.DATE_DECLARED
Planning link
$EXCHANGE_LIST.PLANNING_LINK
Participants
$LISTE_ECHANGES.PARTICIPANTS
exchangeattribute
$CHANGES_LISTattribute (where xxx is theattribute code)
SPOTS
Subject
$LISTE_TACHES.SUJET
Message
$LISTE_TACHESMESSAGE
Transmitter
$LISTE_TACHES.EMITTER
category
$LISTE_TACHES.CATEGORIE
Status
$LISTE_TACHES.ETAT
Priority
$LISTE_TACHES.PRIORITE
Assigned
$LISTE_TACHES.ASSIGNE
Start target
$LISTE_TACHES.DEBUT_TARGET
deadline target
$LISTE_TACHES.ECHEANCE_TARGET
Started on
$LISTE_TACHES.DEBUTE_LE
The
$LISTE_TACHES.TERMINE_LE
Load
$LISTE_TACHES.LOAD
Planning link
$LISTE_TACHES.LIEN_PLANNING
Participants
$LISTE_TACHES.PARTICIPANTS
Parent
$LISTE_TACHES.PARENT
task attribute
$TASK_LISTattribute (where xxx is theattribute code)
Information of a given task type
Each information below can be limited to 1 task type, by inserting the task type code. For example, if the arbitration task type has the code ARBITRAGE, then the code of the merge field to obtain the list of arbitration task subjects is $LISTE_TACHES_ARBITRAGE.SUJET
INDICATORS
Wording
LIST_INDICATORS.LABEL
target
$INDICATOR_LIST.TARGET_REP
Expected development
$LISTE_INDICATEURS.REP_EVOLUTION_STOCK
Reference
$LISTE_INDICATEURS.REP_REFERENCE
completed cumulated
$LISTE_INDICATEURS.REP_REALISE_CUMUL
completed sur la period
$LISTE_INDICATEURS.REP_REALISE
module attribute
$LISTE_INDICATEURS.PROJET_XXX (where xxx is theattribute code)
indicatorPhase
$LISTE_INDICATEURSPHASE
BUDGETS
Wording
$LISTE_BUDGETS.LIBELLE
target
$BUDGETS_LIST.TARGET_REP
Invoiced on the period
$LISTE_BUDGETS.REP_MANDATE
Invoiced cumulated
$LISTE_BUDGETS.REP_MANDATE_CUMUL
committed sur la period
$LISTE_BUDGETS.REP_ENGAGE
committed cumulated
$LISTE_BUDGETS.REP_ENGAGE_CUMUL
completed sur la period
$LISTE_BUDGETS.REP_REALISE
completed cumulated
$LISTE_BUDGETS.REP_REALISE_CUMUL
estimated
$BUDGETS_LIST.REP_ESTIMATE
remaining work
$LISTE_BUDGETS.REP_RAF
planned pour la period
$LISTE_BUDGETS.REP_PLANIFIE
module attribute
$BUDGETS_LIST.PROJECT_XXX (where xxx is theattribute code)
budgetPhase
$LISTE_BUDGETSPHASE
budgetcategory
$BUDGETS_LIST.CATEGORY
budget type
$BUDGETS_LIST.TYPE
RESOURCE
Wording
$RESOURCE_LIST.LABEL
Type
$RESOURCE_LIST.TYPE
category
$RESOURCE_LIST.CATEGORY
Phase
$RESOURCE_LISTPHASE
Profile
$RESOURCE_LIST.PROFILE
target
$RESOURCE_LIST.TARGET_REP
completed
$LISTE_RESSOURCES.REP_REALISE
completed cumulated
$LISTE_RESSOURCES.REP_REALISE_CUMUL
estimated
$RESOURCE_LIST.REP_ESTIMATE
remaining work
$RESOURCE_LIST.REP_RAF
planned pour la period
$LISTE_RESSOURCES.REP_PLANIFIE
module attribute
$RESOURCE_LIST.PROJECT_XXX (where xxx is theattribute code)
RISKS
Wording
$RISK_LIST.LABEL
Type
$RISK_LIST.TYPE
category
$RISK_LIST.CATEGORY
Phase
$RISK_LISTPHASE
Gravity
LIST_RISKS.GRAVITY
Probability
RISK_LIST.PROBABILITY
Criticality
LIST_RISKS.CRITICALITY
risk module attribute
$RISK_LIST.PROJECT_XXX (where xxx is theattribute code)
riskPhase
$RISK_LISTPHASE
RELATED PROJECTS
Wording
$LISTE_PROJETS_LIES.LIBELLE
Code
$LISTE_PROJETS_LIES.CODE
RELATED PROJECT INDICATORS
Project code
$LISTE_PROJETS_LIES_INDICATEURS.CODE_PROJET
indicator label
$LISTE_PROJETS_LIES_INDICATEURS.LIBELLE
target
$LISTE_PROJETS_LIES_INDICATEURS.REP_TARGET
Expected development
$LISTE_PROJETS_LIES_INDICATEURS.REP_EVOLUTION_STOCK
Reference
$LISTE_PROJETS_LIES_INDICATEURS.REP_REFERENCE
completed sur la period
$LISTE_PROJETS_LIES_INDICATEURS.REP_REALISE
completed cumulated
$LISTE_PROJETS_LIES_INDICATEURS.REP_REALISE_CUMUL

3.3.3 Single cockpits

3.3.3.1 Single Cockpit Budget / Resources / indicator

Simple cockpits can be inserted. They correspond to the information contained in the colorindicator at the top of the project.

For budgets, resources and indicators, it is necessary to identify the nature of the cockpit budget / resource / indicator), the category to be taken into account and then the desired representation (REP_CIBLE, REP_RAF...).

Consolidation by cockpit type

Single cockpits can be filtered by gender (eg: GENRE_INTERNE). All representations can be filtered.

Consolidation by cockpit analytical axis

For budgets, it is possible to filter single cockpits by analytical axis (eg: AXIS_SERVICE_DSI). All representations can be filtered.

🚨
Please note: codes must be separated by dashes, not dots, as with other merge fields. It is necessary to provide a box in the office automation file for all the information that can be uploaded. If a project does not have this information, the form will indicate - -. Example: if the Alpha project mobilizes internal resources and not generic resources, then the boxes corresponding to the estimated completed load information will indicate - -.
BUDGETCOCKPIT
Cockpit
COCKPIT
category code
CODECATEGORY
representation
REP_CIBLE REP_ESTIME REP_ENGAGE REP_ENGAGE_CUMUL REP_MANDATE REP_MANDATE_CUMUL REP_REALISE REP_REALISE_CUMUL REP_RAF REP_PLANIFIED REP_PLANIFIÉ_REPARTI REP_PREVISIONNEL_1 REP_PREVISIONNEL_2 REP_FORECAST_3 REP_VISIONNEL_REPARTI_1 REP_PREVISIONNEL_REPARTI_2 REP_PREVISIONNEL_REPARTI_3
Gender code
CODEGENRE
Analytical axis code
CODEAXE
Budget target
$COCKPITCODECATEGORIE-REP_CIBLE
Budget estimated
$COCKPITCODECATEGORIE-REP_ESTIME
Budget completed
$COCKPITCODECATEGORY-REP_REALISE
Cumulativecompleted Budget
$COCKPITCODECATEGORIE-REP_REALISE_CUMUL
Budget committed
$COCKPITCODECATEGORIE-REP_ENGAGE
Cumulativecommitted Budget
$COCKPITCODECATEGORIE-REP_ENGAGE_CUMUL
Budget Invoiced
$COCKPITCODECATEGORIE-REP_MANDATE
Budget Invoiced cumulated
$COCKPITCODECATEGORIE-REP_MANDATE_CUMUL
Budget remaining work
$COCKPITCODECATEGORIE-REP_RAF
Budget planned
$COCKPITCODECATEGORIE-REP_PLANIFIED
Budget planned distributed
$COCKPITCODECATEGORIE-REP_PLANIFIE_REPARTI
Budget forecast total 1
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_1
Budget forecast total 2
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_2
forecast total Budget forecast total 3
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_3
forecast total allocated Budget forecast total 1
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_REPARTI_1
forecast total allocated Budget forecast total 2
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_REPARTI_2
forecast total Budget forecast total allocated 3
$COCKPITCODECATEGORIE-REP_PREVISIONNEL_REPARTI_3
Consolidated Budget by gender (e.g. " target " representation )
$COCKPITCODECATEGORIE-REP_CIBLE-CODEGENRE
Consolidated Budget by analytical axis only (e.g. " forecast total 1" representation )
COCKPITCODECATEGORY-REP_PREVISIONNEL_1-ALL-CODEAXE The "ALL" code disables the gender filter.
Consolidated Budget by type and analytical axis (e.g. " planned " representation )
COCKPITCODECATEGORY-REP_PLANIFIE-CODEGENRE-CODEAXE
SINGLE RESOURCE COCKPIT
Cockpit
COCKPIT
category code
CODECATEGORY
representation
REP_CIBLE REP_RESOURCE_REESTIME REP_REALIZED REP_REALISE_CUMUL REP_RESOURCE_RAF
Gender code
CODEGENRE
Consolidated target load by gender
$COCKPITCODECATEGORIE-REP_CIBLE-CODEGENRE
Consolidated re-estimated load by gender
$COCKPITCODECATEGORIE- REP_RESSOURCE_REESTIME-CODEGENRE
Consolidated actual expense by gender
$COCKPIT CE-CODECATEGORIE-REP_REALISE-CODEGENRE
Cumulative consolidated expense by gender
$COCKPITCODECATEGORIE-REP_REALISE_CUMUL-CODEGENRE
Consolidated remaining work workload by gender
$COCKPITCODECATEGORIE- REP_RESSOURCE_RAF-CODEGENRE
Charge target
$COCKPITCODECATEGORIE-REP_CIBLE
Load Re-Estimated
$COCKPITCODECATEGORIE- REP_RESSOURCE_REESTIME
Actual
$COCKPITCODECATEGORY-REP_REALISE
Cumulative actual expense
$COCKPITCODECATEGORIE-REP_REALISE_CUMUL
remaining work workload
$COCKPITCODECATEGORIE- REP_RESSOURCE_RAF
COCKPIT SIMPLE indicator
Cockpit
COCKPIT
category code
CODECATEGORY
representation
REP_CIBLE REP_ESTIME REP_REALIZED REP_REALISE_CUMUL REP_RAF
Gender code
CODEGENRE
indicator target consolidated by gender
$COCKPIT CODECATEGORIE-REP_CIBLE-CODEGENRE
indicator estimated consolidated by gender
$COCKPITCODECATEGORIE-REP_ESTIME-CODEGENRE
indicator completed consolidated by gender
$COCKPITCODECATEGORIE-REP_REALISE-CODEGENRE
indicator completed cumulated consolidated by gender
$COCKPITCODECATEGORIE-REP_REALISE_CUMUL-CODEGENRE
indicator remaining work consolidated by gender
$COCKPITCODECATEGORIE-REP_RAF-CODEGENRE
indicator target
$COCKPIT CODECATEGORIE-REP_CIBLE
indicator estimated
$COCKPITCODECATEGORIE-REP_ESTIME
indicator completed
$COCKPITCODECATEGORIE-REP_REALISE
indicator of cumulative completed
$COCKPITCODECATEGORIE-REP_REALISE_CUMUL
indicator in remaining work
$COCKPITCODECATEGORIE-REP_RAF

3.3.3.2 Single cockpits Planning

It is possible to insert simple planning cockpits. They correspond to the information contained in the coloredindicator at the top of the project.

🚨
Please note: This cockpit has no category or gender. Codes must be separated by dashes, not dots, as in other cockpits. Representation codes are also different.
COCKPIT SIMPLE PLANNING
Cockpit
COCKPIT
representation
ADVANCE_REP REP_ADVANCEMENT_TARGET REP_POURCENT_ADVANCEMENT REP_FORWARD_TARGET
Merging field
COCKPIT.CODEREPRESENTATION
target advancement rate (%)
COCKPIT
Rate of advancement completed in
COCKPIT
target progress rate (number of milestones)
COCKPIT
completed progress rate (no. of milestones)
COCKPIT

4. Create a summary sheet view (docx or pptx)

  1. Click on AdministrationAdministration > Model settings > ViewsViews > summary sheetsummary sheet or summary sheet phase / milestonesummary sheet phase / milestone.
  2. Complete the information and add the model to summary sheet template.
  3. To generate the Gantt as well, check Gantt generation.
  4. Save view.
image

In the project area, you can run the various forms available in your environment, and not just the one set by default.

  1. Access your project area.
  2. Click on the contextual menucontextual menu.
  3. Select the type of plug to be executed, here summary sheet document.
  4. The list of available records is then displayed.

  5. Select the project sheet corresponding to your needs.
  6. In the case of a form including a Gantt, a pop-up window will appear to validate the display of the Gantt. You can then filter the phases or milestones to be displayed.

✅
The file is loaded in .docx or .pptx in your browser's downloads.
Generate a summary sheet from the project contextual menu
Generate a summary sheet from the project contextual menu

5. List of common errors

Error
Example
Typo in the code
$PROP_LIBBELLE instead of $PROP_LIBELLE
Get confused . and _
$LISTE_INDICATEURS_REP_CIBLE instead of $INDICATOR_LIST.TARGET_REP
Forgetting a code element
$BUDGETS_LISTtarget instead of $BUDGETS_LIST.TARGET_REP
Forgetting a $ at the beginning of the code (except for images)
PROP_CODE instead of$PROP_CODE
Add the structure link to a structure where the project is not attachable.

6. Template sheets

Download sample templates: Word project sheet, Word phase sheet and Powerpoint project sheet Mémo Fiches Office - Downloadable appendicesMémo Fiches Office - Downloadable appendices

🚨

Warning: for images, never use the " " sign. $ ".

Logo

Produced by Virage Group