Safran Risk has released v22.1.0. Read about all the exciting new features.
May 3, 2023
Written by Ian Nicholson
Safran Risk has released v22.1.0. Read about all the exciting new features.
New Features
Automatic Report Package Generator - Functionality to generate a report package that contains a number of output chart images, a Word report, and an Excel report. The report package can be run and customized from the analyze tab.
The UI of the sensitivity analysis tab has been updated. It now also allows you to run sensitivity against a schedule summary and against the schedule types duration and start date.
Cost Module - It's now possible to have more than one top node and to set the type for each top node.
The import of external files now allows three options when updating an existing project: overwrite, update, and append.
Distribution Graph - It's now possible to set the target to the value of a user field. This allows you to set up target dates for all the activities in the schedule.
Enhancements
Hammock to Hammock links are now allowed by the Safran Risk scheduler.
Mode added to distribution graph information.
Recent projects are now opened with the same access level as they were opened last time.
Added option to grouping in the cost tab to see the whole path in the summary ID field.
Added Total Float, Free Float, and Calendar to the Activity Information tab in Risk Mappings.
Risk Mean Start and Risk Mean Finish columns added to the schedule.
Added option for image size for all the output charts. This allows for consistent size of the generated images regardless of the state of the Safran Risk window.
In this article I will visit some of the data a user may be utilizing in Primavera P6 and how it is handled or not handled in Oracle Primavera Cloud (OPC). These are some of the differences found that may be of interest to current Primavera P6 users.
There are many approaches to creating reports from your P6 data, and while free always sounds like the right price, we all know that you get what you pay for. Before you choose an approach, you owe it to yourself to fully assess its strengths and weaknesses. In this article, we’ll compare reporting using XER files versus our own tool: P6-Reporter.
In executing any type of project, whether it’s a turnaround, construction, manufacturing or other project type, they all benefit from access to quick and current reporting in an easy to digest format. This not only improves project reporting but project communication as well, keeping the team up-to-date with project progress and any issues. With access to self-serve dashboard reporting, the user can easily filter to display the exact data they need to focus on. To deliver reporting for your projects, a reporting tool that is quick to deploy and offers a number of standard reports makes roll out easy. The tool should allow you to produce reports easily on spread data as well, which allows you to compare forecasts captured at different points in time. P6-Reporter offers all of this and more.
Your project schedule has been created with no resource curves incorporated. (Resource curves are not always required.) Suddenly, during project execution and reporting, the project is displaying issues. Budget labor, actual labor units and at completion labor units are out of sync. In checking your schedule, it is one section of the schedule which looks to be displaying the issue. You find one of the schedulers has added resource curves to activity resources. At the time of the change, a number of the activities already had progress posted to them. What can happen when resource curves are added or changed after progress has been posted to activities? (Please note this is an example of what can happen given the settings and information scenario that was present at the time. My intent is purely to share what can happen.)
Green up reports can be configured on the specifics required by your project. By using P6-Reporter self-serve dashboards, you and your project teams can have current, easy to digest project information including overall status and highlights for issues requiring immediate attention. Keep in mind that the green up dashboard examples below are meant as food for thought. These examples may be reflecting exactly the items you need to track in your project(s), or you may need to track entirely different elements. Green up reports can be created for the specifics your project teams require whether it is easily tracking manufacturing stages, distribution status, inventory completion status, machine service cycle completions…the list goes on. A green up report can be configured to track many different schedule items.
Above is an example of a Portfolio Dashboard available in P6-Reporter that is displayed using Power BI. Self-serve dashboards provide easy access to data in a very easy to digest format. Notice the gradient color coding in these Portfolio screen shots that help focus on issues quickly. Easily re-sort column data by simply clicking on the column headers. Select graph elements and the column elements that are connected to it automatically filter to highlight on the dashboard. (see below)
Your project schedule will be created in P6, and you are looking to provide the best schedule tools for your project team. What can you add to your team tool kit to assist the project team, address building the schedule, monitor schedule quality, utilize options for updating the schedule and make reporting quick and easy? Let’s look at a few examples for some food for thought.
Do you have project critical path status information at your fingertips? Your project teams need current criticality information to make timely, informed project decisions. Delayed decisions or basing decisions on old information can be costly to your projects.
Using the new criticality report now available with P6-Reporter, the current criticality information will always be at your fingertips. Use the filters to choose the file and snapshot required. Keep in mind, the snapshot process can be carried out manually or be automated.
In P6, identifying each specific project using each UDF in a quick, consolidated, easy to use manner can be very challenging. With ten subject areas where UDFs can be created and the ability to create an unlimited number of UDFs, the complete list of UDFs in a P6 database can be very large. The ability to quickly create a consolidated report telling you exactly which project each UDF is being used in can be very useful.
Often on a Turnaround, or any large project, you need to report resource availability and requirements in your schedule by Craft (trade) and Company. But often, that’s not how the resource dictionary hierarchy is set up. How do we solve this problem? Well, an easy solution to the reporting requirement is using resource codes.
Can you readily monitor commodities on your P6 projects? For example, if your business is oil and gas, can you readily track the requirements of casing or the production levels of oil? For tracking your projects, consider self-serve dashboards for your portfolio of projects.
