Combines general information about a project KPI (e.g. revenue) over time (500€ in the first year, 700€ in the second year) with timing information (2 projects start in 2018, 5 in 2019).


SCHEDULEPROJECTS(ProjectKPI, TimingNode [, TimeLevel])


  • ProjectKPI: Contains the project KPI data over time (e.g. revenue).
  • TimingNode: Contains data for the starting points of projects. This node is typically a simulation node to simulate different starting points for projects.
  • TimeLevel: Specifies the time level (Month, Quarter, Year) in which the offset is given in the ProjectsNode. If this parameter is omitted, ProjectKPI is assumed to be on the lowest time level in the TimingNode.


In this example a company offers two projects (Small, Large) which both run two years and will generate different amounts of revenue in the first and second year.

Input ProjectKPI

Project Sequence Measure (Revenue)
Small Project 1 500
Small Project 2 700
Large Project 1 8,000
Large Project 2 9,000

The Sequence column describes that the Small Project will generate 500€ of revenue in the first year and 700€ in the second year. Instead of year also month or quarter can be used by having a different time column in the TimingNode or by specifying the TimeLevel parameter.

Input TimingNode

Project Year Measure (Number of projects)
Small Project 2018 2
Small Project 2019 5
Large Project 2018 0
Large Project 2019 10

Here we specify how many projects start when. Two "Small Project" will start in 2018, while five "Small Project" and ten "Large Project" will start in 2019.

Output SCHEDULEPROJECTS('ProjectKPI', 'TimingNode')

Project/Year 2018 2019 2020 2021
Small Project



3,500(5) 0
Large Project 0 80,000(10) 90,000(10) 0
Training Model T02 Hochlaufkurven in Training Modelle

Was this helpful?

Yes | Somewhat | No