Glossary

Subscriptions are associated with a user and send information by e-mail at specific times, according to defined criteria (such as project filters). For example, the list of activity entries is sent each month.

You can also choose the frequency of e-mail alerts from 9 options, and activate or deactivate a subscription at any time.

🖇️

Read more : Subscription list

Platform attributes can only be created via the Platform.

These attributes represent the constants needed to create formulas, for example, and are prefixed with UP.

Attributes related to the various themes are managed in Administration > Field settings > Attributes.

Automations automate repetitive or unnecessary actions in the application.

They can be configured within a project or project template , and affect aspects such as scheduling, tasks and exchanges.

An automation is defined by a trigger event that will execute an automation on one or more projects.

The list of automations cannot be modified. You can view a diagram of an automation by clicking on its code.

Created according to need, these fields are found throughout the application, completing the description of an object. They can be used as analysis axes, report sorting and search criteria. Attributes can be of different types, such as numeric, document, list, etc. They can be mandatory or non-mandatory. They may or may not be mandatory. They can be set in the administration. Some technical attributes are inherent to the application.

The analytical axis consists in consolidating budget values.

Within a project, budget data can be grouped by analytical axis. This enables budgets to be analyzed differently for each budget envelope , category or project phase.

It can be combined with one of the Categories. It can be set as a filter criterion notion://custom_emoji/a24e5d14-db71-48bb-8066-1fd12a27b0c5/12a00e20-3c68-8063-ba13-007a6401ff44List of filter criteria

SAML2 authentication

SAML enables users to uniquely identify themselves to the various web applications they use.

In the SAML model, Project Monitor is a Service Provider. You need an Identity Provider (IDP), such as Okta / Shibboleth or ADFS - Microsoft Active Directory Federation Services.

A library is a grouping of reports. It can be named as you wish: by theme, by type of analysis... When a report is created, it must be added to one or more libraries.

representation a number of days during which the resource can work. Example: 22. ⚙️ Formula: capacity is calculated in the resource screen. Resources - Capacities and costs tab as well as via a resource calendar.

A category is used to parameterize a parameter (resource, budget, indicator or risk). A category must be linked to a parameter structure. Structures are in global budgets, while categories are in each project. It is the category that manages the display: the thresholds for displaying parameter alerts in the project. Categories budget) Categories (resource) Categories indicator) Categories risk)

This screen lists all the reports available on your platform. These reports show data from the themes used in the application. Reports

Background task control

A background task command is a command that is executed at the same time as other actions in the Project MonitorIt's a "backgroundtask ", because it takes time or substantial resources.

Examples of commands: platform creation, label export, reports, sending of summaries, reports, e-mail subscriptions, synchronization of Galilee)...

Calendar

There are many different types of calendar, and many different uses. A calendar can be defined for resources, for phases and milestones, and for financial documents.

It is possible to mark days that are worked and days that are not.

There are therefore 3 calendar elements:

• the platform calendar, used by default for all platform users, which defines, for example, days not worked as public holidays.
• the hierarchical calendar, a calendar specific to a structure perimeter
• the resource calendar, a calendar specific to the resource (part-time management, exceptional absences, etc.). The calendar can be adapted by the resource itself, unlike the platform and hierarchical calendars.

Platform calendar

A platform calendar is a calendar that applies to the entire platform: everything that is common to resources/milestones/phases/financial items.

Hierarchical calendar A hierarchical calendar applies to resources within a structure. For example, if a Geography structure exists, then a German calendar (with specific public holidays) can be associated with the structure value structures Germany structure value . Users attached to this structure level (and their associated resources) will then be able to have an appropriate calendar.

To apply it, therefore, we need to work not on the application of calendars to users, but on the structure link of the hierarchical calendar and on the structure link of resources (possible in mass modification). For the calendar to be applied, the structure link must be shared (calendar and resource) on the reference structure .

If an estimated date is entered: effective date = Estimated date If a target date is entered: effective date = target date If neither an estimated date nor a target date is specified for the object: effective date = Project date (For a milestone,effective date" = "project end date" / For a phase, "effective start date" = "project start date" and "effective end date" = "project end date").

If an estimated date is entered: effective date = Estimated date If a target date is entered: effective date = target date If neither an estimated date nor a target date is specified for the object: effective date = Project date (For a milestone,effective date" = "project end date" / For a phase, "effective start date" = "project start date" and "effective end date" = "project end date").

A request is an object containing a need, an idea.... A request can have attachments. Tasks can be created from a request. A project can be created from a request. A workflow can be applied to a request.

This screen allows you to create project reviews in the form of a slideshow. To do this, you can easily select projects and set parameters.

This review is based on the slideshow template created and linked to the portfolio via the Setting of a portfolio Slideshow templates

You can view the slideshow in draft mode to test it, or create and start the review.

In the journal, it is possible to:

• view the dashboard each project (defined in the slide show template)
• access the project with one click
• view project details
• Add comments for each project at the bottom of the screen, in the form of exchanges or tasks.

Datatalk allows you to query the platform's data and obtain results as a table. Simply select :

1. The theme (for example Resource, Budget or indicator)
2. period (all at once, or evolution over time)
3. Information to be displayed (example: the remaining workthe completedthe budget committedetc.)
4. The element(s) to be analyzed (by filtering on certain projects, budgets, resources or indicators)

Then click on Run and Datatalk displays a table with the requested data. You can :

• Save the order (search) for later use
• Export data to an Excel file
• Add this table to other screens (e.g. the home page)

It's a fast, personalized way of consulting all kinds of information, without the need for complex reports. You simply select the criteria, and Datatalk takes care of displaying the results.

Datatalk is accessible in a dedicated tab of the theme Reports.

This is the set of budget assumptions for the project: low, medium or high. Only one assumption can be validated in a version of a global budget plan .

⚙️ Formula: availability = capacity -remaining work + completed) The calculation is completed from the current period to the end of the phase. In manual scheduling mode, the monthly value is taken into account. The remaining schedule or overall remaining work have no influence on availability.

Allows you to define role authorizations to manipulate and consult data. They are separated as follows: ACT_CONSULTER right to view the object ACT_CREATE : right to create the object ACT_MODIFIER right to modify the object ACT_UTILISER right to use the object ACT_ACCEDER Access rights to a feature Application rights list : List of rights

Envelopes can be used to compare the amount allocated with the amount spent.

An envelope is attached to a perimeter: a project can use a budget on behalf of an envelope if it belongs to the envelope's perimeter. Budget envelopes The generalenvelope allows envelopes to be grouped together.

Pin

Pins provide quick access to three elements in the form of shortcuts: Activity entries, Knowledge Center and favourites.

Pinned items are always visible in the top right-hand corner of the screen, no matter what page you're viewing, offering quick, one-click access. You can also access them via the main menu. You have the choice of pinning or unpinning items according to your preferences; no rights are required.

Re-estimation of the total amount of project expenditure or revenue originally defined in the target. estimated vary over time.

12-month period that defines the accounting year. It begins at the start of a month in the calendar year.

Periods - Exercises tab

A filter allows you to display only certain data, according to certain criteria. These criteria are specific to Project Monitor. A user can set the default filter selected when logging in. There are two types of filter: static and dynamic.

• static filter A list of objects set manually by the user, which only changes if the user modifies it. This is a saved filter.
• dynamic filter a list that automatically updates itself according to predefined criteria (attributes, attachments, etc.), integrating new objects that meet these criteria.

Filters can be :

• Private: visible and usable only by their creator.
• Public: accessible and usable by all platform users.

The summary sheet brings together important information on a project, phase or milestone. It enables the user to quickly consult the information of interest, and export or print it if required.

Two formats are available:

Default settings (not available for new entries in beta version) :

• The format used can be defined in the project parameters (Settings - Display tab) or template (Project - General tab ).
• The platform configuration also lets you choose a default format (web or document) for project or milestone records. Global configuration - ‣

form view in which specific project attributes can be edited form. A form is used to describe a project, in particular with project attributes Projectwhich are themselves managed in groups.

You can add several forms to a project and change their order via Setting Display forms.

A form can also be added to a project template (creation or duplication). Project

A project template is a model containing key information: Project

It is possible to create a project from this template : projects will be created in a harmonized way. Certain information entered in the project template is copied into the project created via this template.

Once created, the template can be used to create a new project and/or insert new elements into an existing project.

A template can be applied to several projects at once.

The template is useful for managing the project lifecycle, in particular via the Workflows and Automations

Galilee is the "Business Intelligence" or data warehouse module of the application. It includes a data warehouse feeder. The data warehouse will contain data exported from the production database at a frequency to be determined (generally refreshed every working day). Its schema is organized so as to be easily exploitable and queryable without the need for in-depth knowledge of the model. Data export to a SQL manager / BI tool is configured in Galilee . Galilee

A structure is used to organize the platform by hierarchically grouping objects (projects, resources, etc.) or users. Hierarchies

Enables rights management and localization/partitioning of access to certain objects. This is known as a structure link.

Example: the geography structure contains continents on level 1, countries on level 2 and cities on level 3.

It is possible to associate a structure with a user group to restrict rights. By default, an object has unrestricted access, but if it is attached to a user group, only users belonging to this group can use the object.

status allows you to define the stage associated with it in the project lifecycle. They will be given labels such as In progress, Validated, Archived, etc., in order to be recognized by users and reflect business meaning.

Meta-statuses ⬇️

Assets The project is displayed in the quick search Search The project can appear in the activity entry (if the other conditions are met). Activity entries All data can be entered in the report Draft Meta status only for workflows Workflows Pending validation Project status cannot be changed manually, only by workflow. Workflows Framed Meta status used only when integrating with an external application: project characteristics will be locked. On hold Meta status only for workflows Workflows Refused Meta status only for workflows Workflows Completed Project does not appear in activity entry Activity entries The project does not appear in the quick search field at top right Search All data can no longer be entered Project can be deleted Meta status triggers closure process Cancelled Meta status for workflow only Workflows

Perimeter The scope defines characteristics that restrict the choice of : - subjects - dates - hierarchies... The scope will be used to produce a snapshot Perimeters A snapshot allows you to take a "photo" of data to remember what happened at a specific moment in time. Perimeters. The scope lets you choose the types of data for which you want to launch a snapshot.

For example, I define my perimeter on the following representations target and estimated for theBudget theme . I'll be able to launch my snapshot by adding projects via a filter or by selecting All projects. I'll then be able to visualize the values of these representations for my projects for a given date, and compare them with the values for another date.

It is this perimeter that defines the information saved in the snapshot. The snapshot saves the values of certain representations at a given time.

Financial documents are used to detail the content of entries on a budget line.

A plan is used to prepare a budget for one or more fiscal years. It is linked to a budgetcategory Categories and contains at least a budget version.

The project manager a budget request budget selecting a version of plan. They can enter amounts based on three scenarios (high, medium, low). Only one can be approved.

Documents and comments may be added if necessary.

Once the hypothesis has been validated (Validated), the amount granted may be distributed among the phases of the project.

Use in the project space

Budget plans are used in the tab Request.

The columns Draft, To be validated and Validated indicate the number of projects using each version. Clicking on this number takes you to the list of projects filtered by status.

Even if no amount is entered in a scenario, the project is counted in the column. Draft.

Budget plans can be exported. Budget plans

Every portfolio has its own reports, project review and dashboard.

A period designates a time interval for entering or consulting data.

To manage periods : Periods

• activeperiod : The most recent period in which entries can be made. At the end of each year, during the December platform initialization, an extra year is added to maintain active period years in the future of around 10 years.
• currentperiod : The period selected by the user to work with, whether it's the current period or a past period , chosen via the interface or for specific processing. This is the case for retroactive entry via the period selector.

All phases created in all projects can be found in the phase list. Phases

A phase can be the mother of another phase, which is therefore a phase.

Tasks and exchanges can be linked to phases or milestones: this is a dependency.

planned value for a project period . Granularity can be annual, quarterly or monthly.

The forecast total remainingforecast total is a representation for resources, used to control resource allocation. It corresponds to the forecast total for the last month after period initialization. This month must be included in the choice of period displayed in the capacity plan .

The forecast total works with a forecast rate (q).

⚙️ Formula : q = (sum of distributed forecasts for projects/phases to which the resource is allocated) / capacity

A resource is an entity used for a project, it carries a capacity : a number of days available to carry out an activity, and it can therefore be associated with a cost.

A resource may be associated with a certain hierarchical level, it may also have a profile (architect, project manager, developer...), and a type (internal, external...).

There are two types of resources:

• Named resource Assigned to a user identified and monitoring for the project. Users Most named resources are created automatically when the user is created. In some cases, however, it may be necessary to create the resource afterwards, in which case it's important to know that the CODE is what associates the user with the resource.
• Generic resource: Enables work capacity to be defined according to a chosen axis (skills, team, external resource). The generic resource is used when the identification of a named resource is impossible or unnecessary (at the start of a project, for example, when the need for an expert is known, but the name of the expert has not yet been identified).

risk It can be used to alert on various points (financial, resources, organization, environment, technology...).

Risks can be added to a project and evolve over time. Risks. The cockpits allow you to quickly visualize the criticality of the risk, based on both severity and probability. It is also possible to create a local risk within a project. This risk will not appear in this list of risks. It will only appear in the project where it was created.

Role type comparison table

role type	Range	Main application	Award method	Special features
🧩 General	The whole application	Global rights (admin, data entry, settings, etc.)	From the user file Users - Roles tab	role often "stronger" than others
📁 Project	One or more specific projects	Team member, project manager	From a project Setup - Team tab or from a user Users - Roles tab	Applies only to projects concerned
🏢 Hierarchical	One hierarchical level + levels below	Access conditional on an organizational perimeter	From the user file Users - Roles tab	Gives rights to objects attached to this level

• Roles are cumulative: a user can have several roles of different types. Rights are cumulative.
• generalrole priority: if a general role grants more rights than project or hierarchical roles, the latter become indicative.
• Non-attachable objects are fully visible as soon as a right is granted to them, regardless of the role type.

For budgets: representation corresponding to the amount of expenses booked (asInvoiced") For resources: representation of activity entries

For budgets: representation corresponding to the amount of booked expenditure accumulated since the start of the project (asInvoiced") For resources: representation of activity entries since the start of the phase

⚙️ Formula: Reestimated = Cumulative completed + Overall AFR It is interesting to compare this re-estimate (what has happened on the project) with the target (what was originally planned).

⚙️ Formula: RAF = capacity - completed For resource scheduling : this is the estimated number of working days remaining for the resource to complete its mission on the phase, from the scheduling date.

Quantity of work remaining to be done on a phase to which a resource is assigned, which is distributed automatically. The allocation is made on a monthly or daily basis. ⚙️ Formula: Smoothed detailed AFR = Overall AFR - Manual detailed AFR ⚙️ Formula: Daily value of RAFDL = (Global RAF - RAFDM) / (number of working days in the phase for which the resource is scheduled at the time of calculation - number of days for which RAFDM is entered)

Remains to schedule representation used only in manual scheduling mode for resources. ⚙️ Formula: Reste à schedule = remaining work - (∑ remaining work réparti).

break Configured as a break criterion, an attribute can be used to organize a list into "sub-categories".

• Define a framework (dates, expenses, budget)
• Identify the right projects and requests to include in the portfolio, based on the framework
• Dynamically select/deselect projects and requests
• Visually check that selected projects fit the framework
• Dynamically adjust the macro scheduling of portfolio projects and requests and dynamically see the impact on the framework
• Create a portfolio from a valid scenario
• portfolio scenarios are accessible via a hierarchical right

ALS SLA stands for Service Level Agreement: a commitment to guarantee a certain level of service. See ALS

By selecting a period, you can view the value of certain data recorded each month (project weather, completed resources/budgets).

It can be found in the contextual menu of Project Monitor for certain screens.

Entering activities

Users can enter activity data to view all workloads on a project or phase. This includes all the hours or days (depending on settings) entered by the user. Everything is consolidated at the level of the resource associated with the user on the project.

The timesheet entered is added to the theme Resources of the project once summed up by month, in representation completed. It is therefore possible to compare this representation with the target entered when the project was created.

There is a list of activity entries for all users: Activity entries

Access to activity entry can be pinned to the top right of the screen Pins.

dashboard consolidating project portfolio reports 1 dashboard = several blocks consisting of a header and a view

Functional activity enabled by the application On each platform, the themes determined at the time of purchase are activated: resources, risks, budgets, etc.

Tasks are actions to be carried out for the project (or a planning object). They can be assigned to users, have a deadline, a status, a type, etc.

It is possible to view all tasks on the platform via Tasks, all tasks in a project via Tasks, or my tasks My tasks

It is possible to display tasks in dashboard blocks dashboardList of tasksYour tasks

"Univers Projet" Jargon <> Plateforme Une plateforme contient plusieurs UP Une UP est caractérisée par son url

Webhook A webhook is a way of notifying a third-party application when an event defined in Project Monitor occurs. For example: you can trigger the creation of a SharePoint space when a new project is created in Project Monitor. See Webhook Webhooks memo

Workflow representation a sequence of tasks or operations assigned to a person or group of people by moving from one step to another Workflows

Validation workflows can be configured in Project Monitor. To do this, an add-on must be activated.