Active Plan is the simulation in which conceivers of the plan are currently working.
An allocation (of a resource to a task) is the result of the automatic scheduling process. “To allocate” is a process by which resources are assigned to tasks.
A calendar is a range of dates and/or days during which a task can be planned (or not), or some resources will be available (or not).
The capacity curves display the real and the theoretical capacities of resources regarding the planned tasks.
Capacities are calendars and coefficients that can be applied to task requirements and/or resources.
A category is complementary information that can be associated to a task and/or resource. This information can be used to filter data displayed in the different views and screens of the application.
A coefficient is a set of values applied to tasks and/or resources to simulate the impact of events or factors which will affect its feasibility, availability or efficiency.
There are 3 types of date constraints: start-date constraint, end-date constraint and target end-date (goal).
A dependency is a chronological link between two elements of a project. It represents sequential constraints which can be created between elements such as tasks, milestones, task groups and projects.
There are 4 types of dependencies: end-start, start-start, end-end and start-end.
The duration is the estimation of (calendar) days necessary to achieve a task when all required resources are allocated to the task.
The Manual Gantt illustrates, in a bar chart, the project structure presented at infinite capacity (this means without resource restrictions and without coefficient effects and calendar interruptions).
Key Performance Indicators are indicators which allow measure the quality or performance of a planning & scheduling solution toward some goals (profit, # tasks planned, …).
A lag is a duration formulated in days or following a task accomplishment percentage. A lag adds duration between the two elements referenced in a task dependency.
A level is a grade or experience that can be associated with an efficiency level.
The load is the number of working days (person days) that are necessary to achieve a task. The load is synonym of effort.
Master Data is any information that is considered to play a key role in the core operation of PlanningForce. Master data include data about projects and templates, resources, roles, calendars, coefficients, … Master data is typically shared by multiple users and must be therefore agreed upon view across the organization.
A milestone is a task with zero or instant duration. Milestones are used as markers in a project to set up production points, tasks or moments of synchronization, dates of billing or reporting, and markers or junctions of results.
The min duration means that a resource will not work on the task on a specific day for less than this value. The task could still be done by another resource or be postponed.
The Output Gantt represents a workable and realistic planning without resource over usage. This diagram displays tasks, but also the allocated resources according to roles.
Plan is the phase which leads to the elaboration of a published plan.
Planning is the action of conceiving the WBS and associating all the related requirements (roles, calendars, dates, priorities, …).
Within the planning horizon, you can define the start date and the end date of the project folder.
Persons who will be able to see the plan. They get a read-only view on the results tab.
Program Manager Officer (PMO)
The PMO (Program Manager Officer) is a person in charge of creating and managing: plans, progress status, simulations, projects, resources, PMs, PLs and Resources.
The precision determines the way how to view projects and tasks within the Output Gantt.
A predecessor is an activity that must be completed (or be partially completed) before a specified activity can begin.
Progress is the phase which leads to the progress update of the published plan (see ‘published plan’).
A project is composed of tasks and milestones which can be regrouped and/or interdependent.
Project Leaders (PLs) (PLANNINGFORCE WEB ACCESS REQUIRED)
Persons that are the delegates of the PMs. They manage the day-to-day work, including change request and task progress and they make sure that resources encode their progress on tasks.
Publication (PLANNINGFORCE WEB ACCESS REQUIRED)
The publication process is used by the PMO to publish data on PlanningForce Web Access.
Published Plan (or baseline)
Published plan is the simulation that has been selected by the conceivers to be shared by all the shareholders.
Project Managers (PMs)
Persons to whom you delegate projects and resources. They don’t have rights on simulations (creating, deleting) but can access the projects they are in charge of. They can’t alter the description of resources (roles, skills, calendars).
Reports help the user to evaluate the impact of the scheduling. Reports are printable views of the results, available in different formats (i.e. PDF or HTML).
A repetitive task is a task that is repeated several times over time.
A resource represents a person, a group of people who can be scheduled on one or several tasks.
Resources (PLANNINGFORCE WEB ACCESS REQUIRED)
Persons who get their allocations from updated timesheets. They are notified of eventual changes and encode their daily progress on tasks.
The Resource allocations tab displays a calendar grid which shows all resource allocations on planned tasks.
“Stability of resources” is a feature that helps promoting the resource that has worked the most on a project, a task or a group of tasks. The interest is to ask the application to reuse this resource wherever possible, but it may occur that a resource is not available.
The Resource usage tab displays curves which give a global view of the proportions in which resources are employed. It displays resource workload regarding their calendars.
A role is a main competence associated to a person; it also expresses what is required for a task to be done. The role is used to describe task requirements and people.
Scheduling is the action of finding the suitable and available resources which match the project WBS and its planning requirements (dates, roles, …).
A skill is an additional competence. Skills are not mandatory but they allow users to define task requirements and resource profiles more precisely.
Simulation is a copy of Master data in which a different planning solution is elaborated and tested.
A task is an activity which is carried out by resources within a definite duration.
The Task allocations tab displays a calendar grid which shows all resource allocations on planned tasks.
A task group is a phase of project or sub-project which contains tasks and milestones.
A task requirement is composed of one or more resources that are necessary for the achievement of the task.
A template is a model of a Project (Project template) or a Task Group (Task Group template).
Validate an item consists in “freezing” the way tasks and resources have been planned; items validated won’t be altered any more by subsequent scheduling processes. This is the key rule that allows parallel planning processing.
WBS is a decomposition of a project into smaller components. It defines and groups a project’s discrete work elements in a way that helps organize and define the total work scope of the project.