Schedule and cost risk analysis on the plan you already have.
Tamara imports your schedule from Primavera P6, Microsoft Project or Microsoft Planner Premium, adds the uncertainty and risk events your team describes, and simulates the whole plan thousands of times. You get a finish date and a budget with a confidence level attached, such as a P80 date (one the project has an 80% chance of meeting), and a ranked list of what drives them. Your original schedule file is never changed.
Timings measured by Vose Software on real project plans.
Tamara turns the schedule your planners already keep into a risk model. Import it and fix what the Schedule Audit flags. Say how uncertain the work is, add the risks from your register, and simulate the plan thousands of times. You get a finish date and a budget with a confidence level, and the risks that drive them.
Tamara reads your schedule from Primavera P6, Microsoft Project or Microsoft Planner Premium, including nested and inter-connected projects, so the analysis starts from the real plan. While importing, it runs a Schedule Audit. This checks that the schedule is suitable for Monte Carlo simulation and scores its quality against goals you can edit.
Illustrative audit of a 412-task Primavera P6 schedule. Green values meet the goal and red ones do not. You can edit every goal, and selecting a metric lists the tasks behind it.
Example levels for a 20-day task. You name the levels and set the ranges.
You do not type a three-point estimate into every task. You answer simple questions instead: how sure are we about the amount of work, how fast will this kind of work go, how firm is this cost or resource rate? Define a few levels once, give each task, cost or resource a level, and Tamara turns them into ranges.
Tamara models risk events separately from everyday uncertainty. Each has a chance or a frequency and a range of impact, and can be a threat or an opportunity. There are six kinds, including weather. We designed them with a dozen project risk and planning experts, from cases other tools could not describe properly.
A risk that delays one task: a late delivery, a repair, a contractor arriving late.
Steel delivery late: 30% chance, 1 to 3 weeks. In this iteration it happens, and everything after the delivery moves.
One risk on a set of identical tasks. Each task can be hit or missed on its own.
Concrete pump breakdown: 15% chance on each of five pours. Here it hits pours 2 and 4.
A risk that changes how fast a type of work goes, so every task of that type stretches.
Night-work ban on the marine contractor: 20% chance, marine work 15 to 30% slower. Both marine tasks stretch; the yard does not.
Work that may have to be added to the plan, such as a redesign. Also called probabilistic branching.
Design rejected at review: 20% chance of a 3-week redesign before construction.
An event that stops all or part of the project for a while: a fire, an inspection, a spill. Every task running at the time is delayed.
Site shutdown after an incident: two weeks lost from week 8. Only the tasks running then stop; their successors move with them.
Bad weather that stops exposed work for a while: storms, high winds, heavy rain or frost. Weather has its own risk type in Tamara, so you model it directly.
High winds stop crane work for two weeks from week 7. Steel erection is held up and the roofing moves with it; the indoor fit-out carries on.
Each section is drawn on its own, so delays and early finishes cancel out. The total looks precise: the P80 is only 5 days above the 40-day estimate.
5,000 iterations. The example comes from our review of project risk analysis tools.
One productivity factor for the fencing crew drives all ten sections. A slow crew is slow everywhere: the P80 is 49 days, 4 more than the independent version.
Tasks often share causes: the same contractor, the same weather, the same approvals. If a model treats them as independent, their delays cancel out and the finish date looks more certain than it is. Tamara asks for the shared causes instead of correlation coefficients, and the correlation follows from them.
Fast enough to run the master schedule itself, so there is no cut-down copy to maintain. Most real schedules have between 1,000 and 10,000 tasks. A 40,000-task schedule runs 10,000 iterations in under five minutes, and Tamara has been tested on real plans of up to 80,000 tasks.
Times measured by Vose Software on real project plans.
Every task, summary and milestone gets results for its start, finish, duration and cost. Charts can show several scenarios at once, and the table beside each chart gives the date or cost at every confidence level. The tornado ranks what drives the result, and the stochastic Gantt shows each task’s likely dates.
Finish date of the whole project, with and without mitigation. The table reads the 80% line: 18 October 2027 Managed, 29 October 2027 Unmanaged. The planned date, 19 September 2027, is met in only 7% of Unmanaged iterations.
Illustrative project: nine tasks, four risks, 5,000 iterations. Managed adds the four mitigations from the next section.
Tick the mitigations to include. Each lowers the chance of one risk and adds its cost to the budget.
No mitigations selected: this is the Unmanaged scenario.
Yes. A scenario can switch risks on or off, change their chance or impact, or change a productivity factor. Compare scenarios on one chart to find the mitigations that buy the most certainty for the money, and to show why the others are not worth it.
A risk model that must be rebuilt at every schedule update gets done once and then forgotten. Tamara keeps the risk data attached to the schedule, so an update takes one click, and reports come from templates you design once. Getting from an updated schedule to reports in people’s inboxes can take as little as a minute.
Planners update the schedule in their scheduling tool as usual.
Tamara re-imports it and carries every risk and assignment across.
Run the simulation on the updated plan.
Each report is generated from its template as a PDF.
Example templates. Charts and statistics can also be copied into Word, PowerPoint or Excel.
Yes. Not every cost sits in the master schedule, and not every risk fits a task. Tamara has a built-in spreadsheet with the ModelRisk modelling tools: 136 probability distributions, 34 time series models and 14 copulas. Use it to describe inputs in more detail, and to work out what the schedule result means for the business.
Illustrative values. Each iteration takes the handover date from the schedule simulation; the ModelRisk functions add the uncertainty outside the plan.
Tamara sits between the scheduling tool your planners use and the places the results are needed: the risk register, the business case and the reports to the board. It reads Primavera P6, Microsoft Project and Microsoft Planner Premium schedules, exchanges risks and results with Pelican, and passes simulation results to ModelRisk models in Excel.
Pull risks and mitigations from the Pelican risk register, and send each milestone’s likely cost and date back to its dashboards.
Save results as SID files for ModelRisk, to feed Excel models such as a business case.
Example models to start from, and help tutorials on good practice in schedule and cost risk analysis.
A step-by-step guide to rebuilding a PRA model in Tamara on your current P6 schedule.
Everything on this page is included in every Tamara licence.
Tamara is sold as an annual licence, for a single user or as a network licence, with every feature on this page included and a fully functional 15-day trial. Current prices and discounts are on the pricing page. Our comparison of six project risk analysis tools lists the prices other vendors publish.
No. Tamara keeps the risk model with its own copy of the imported schedule and never modifies the original file. When the plan changes, one click updates Tamara’s copy and carries the risk information across.
No. Tamara works from the schedule your planners maintain in Primavera P6 or Microsoft Project. Make logic changes there, then update Tamara in one click, so there is only ever one version of the plan.
No. You describe uncertainty with levels you name yourself, and risks with a chance and a range of impact. Tamara comes with example models, and the help file has tutorials on good practice in schedule and cost risk analysis. The spreadsheet’s distributions are there when you need more detail.
Tamara is a 64-bit desktop application for Windows 10 and 11, built on .NET 8. It is licensed for a single computer or across a network. Full details are on the system requirements page.
Yes. The 15-day trial is fully functional and imports your own P6 or Microsoft Project schedule, so you can run your first analysis on a project you are working on.
The full product: import your own schedule and see its Schedule Audit, P-dates and drivers. See prices and discounts