A
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.
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 and will be updated with each new version of Project Monitor. You can view the schematic 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.
Attributes categorized as technical cannot be added to an attribute group.
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 List of filter criteria
B
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.
C
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)
It's essential to set up the measurement structures and categories beforehand. It's difficult to change everything afterwards. The structure is set, as are the representations, which are consistent with what you want to put in place; you don't change the settings again.
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.
For example, we can have a French calendar with public holidays such as May 8 or July 14, and create a new calendar specific to Alsace-Moselle, which has additional public holidays. You can also mark all Wednesdays as non-working days.
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 .
D
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.
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
Datatalk allows you to query the platform's data and obtain results as a table. Simply select :
- The theme (for example
Resource
,Budget
orindicator
) - period (all at once, or evolution over time)
- Information to be displayed (example: the
remaining work
thecompleted
thebudget committed
etc.) - 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.
Read more : Interrogating data with Datatalk
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.
E
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.
F
You can bookmark any page of Project Monitor like a project, a task, a report, a portfolio...
If you don't see favourites in the top right-hand corner of your screen, you can pin favourites via the main menu.
Pins
favourites can be sorted into groups.
favourites , on the other hand, are strictly user-specific.
favourites
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 updates automatically according to predefined criteria (attributes, attachments, etc.), integrating new objects that meet these criteria. List of filter 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:
- Web form
Project
Phase / milestone :
- is visible from different areas (project, planning, portfolio, etc.).
- is customizable with configurable information blocks.
- The document sheet
summary sheet
document summary sheets :
- is in Word or PowerPoint format
- displays information by key: attributes, hierarchical links, roles, etc.
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.
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
An attribute used in one form cannot be used in another.
G
Attributes categorized as technical cannot be added to an attribute group.
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
In a project, it is possible toSave as
as a project template . The properties and structure of this project will be transferred to a new template.
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
H
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.
I
The snapshot saves the values of certain representations at a given moment.
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.
Snapshot, perimeter and report Project budget review with snapshot (Excel) work together. Each time a snapshot is taken, a warning mail can be sent to a user.
J
Milestones are used to setdeadline for the project, and to indicate the project's level of progress.
Tasks and exchanges can be linked to phases or milestones: this is a dependency.
All milestones created in all projects are displayed in the milestone list. Milestones
L
Lists are called up by the properties or attributes of projects, resources, budgets... themes.
Lists can only be managed via this screen Lists.
On the other hand, attributes specific to each theme can be managed in Administration > Field settings >
Attributes
.
M
A status is a status that can be applied to a project, for example, and defines a behavior in the application.
Certain screens may or may not be displayed with certain meta-statuses.
Workflows are based on these meta-statuses.
A status can be used to define a weighting for calculating a project's earned value.
It is possible to have a status with several meta-statuses
Meta-status âŹïž
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 used only for Workflow 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 used only for Workflow Workflows
Refused
Meta status used only for Workflow 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
N
Notification
Notifications make it easier to collaborate in Project Monitorand be alerted by your colleagues to tasks, exchanges and comments.
There are several types of notification: directly in the application (push notification), in the Notification centerand by e-mail.
P
Blocks can be organized into groups. The maximum number of block groups is 5.
User or platform home page
The user home page can be customized or taken from a template.
Platform home page templates can be defined for a specific user, for a role or for an entire platform. homepage configuration
Platform.
In all cases, you can only access data for projects for which you have rights.
Project home page
A project welcome template is applicable to a project, and is applicable by default to a project template . Project.
Each type of project can have its own homepage, with different information. The aim of the project homepage is to give the user access to the information that interests him most when consulting a project.
portfolio home page
A portfolio welcome model is applicable to a portfolio.
The aim of the portfolio home page is to give users access to the information they are most interested in about the portfolio as a whole and the projects that make it up.
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.
Snapshot, perimeter and report Project budget review with snapshot (Excel) work together.
Every portfolio has its own reports, project reviews and homepage.
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.
â(distributed forecasts M, M+1, M+2, M+3...)
(sum of distributed forecasts for projects to which the resource is assigned).
representation for resources, used to manage resource allocation. It's a "general" scheduling at the monthly level, calculated automatically.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
R
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
- 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 | role often "stronger" than others |
đ Project | One or more specific projects | Team member, project manager | From a project | Applies only to projects concerned |
đą Hierarchical | One hierarchical level + levels below | Access conditional on an organizational perimeter | From the user file | 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.
The Super Administrator role is a specific role : it has full rights in the Project Monitor. Please note: its role cannot be changed.
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".
S
- 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.
Don't forget to return to the active period when you've finished viewing past data.
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.
T
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.
U
"Univers Projet" Jargon <> Plateforme Une plateforme contient plusieurs UP Une UP est caractérisée par son url
V
view
A view allows you to customize the display of a page, content or export. It lets you define what information is displayed and how it is formatted. Views are available on many screens (project list, Kanban task board, etc.).
List of view types
W
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
Validation workflows can be configured in Project Monitor. To do this, an add-on must be activated.
The file containing the workflow code, which is loaded into Project Monitor must have a .bpmn extension