Imports and Exports

Bring schedules, risks and cost models in, and take schedules and results out, in common project controls formats.

From an XER to a Board PDF

How It Works

  1. Schedule In

    Import a Primavera P6 XER, a P6 XML or an MS Project XML schedule into a project, or open one in the schedule editor and save it to the project.

  2. Register in and Out

    Export a folder of risks to Excel, edit it and import it back after a dry run.

  3. QRA Inputs

    Import and export risks, mappings, cost models, correlations and calendar risks as Excel workbooks. Bring a risk register in from Safran Risk or Primavera Risk Analysis, and send one out in Safran Risk’s template.

  4. Results Out

    Export result views to PDF and Excel, and schedules to XER, MS Project XML and UN/CEFACT NetworkSchedule.

Details

What You Get

  • Import reviews list what will change before anything is written.
  • Export to XER, MS Project XML and UN/CEFACT NetworkSchedule.
  • Export the risk register in Safran Risk’s risk import template (.xlsx), and import a risk register from Safran Risk.
  • Import risk mappings exported from Safran Risk, and cost models in Safran Risk’s cost import template (.xlsx).
  • Import Primavera Risk Analysis plans (.plan) and risk register exports (.rrx): risks and their task impacts and, from a plan, duration uncertainty, existence risks, probabilistic branches and links, and correlations.
  • An admin can upload the organisation’s own blank Safran Risk templates, and the register export fills the uploaded copy.

Limits and Conditions

  • A schedule from MS Project XML is stored as an XER, so lags shorter than an hour and lags in elapsed time are not kept.
  • No PowerPoint export of QRA results.
  • Only the risk register exports in Safran Risk’s template. Mappings and cost models export as RiskForesight workbooks.
  • The Safran Risk export leaves out duration uncertainty bands, calendar risks and logic, and writes recurring risks as their once-only equivalent.
  • Mappings and cost models from Safran Risk, and task impacts and correlations from Primavera Risk Analysis, come in after the register from the same project or file: their risks are recognised through it.
  • Activities are matched by Activity ID, so mapping files and plans must come from the same schedule.
  • A Primavera Risk Analysis plan brings its risk inputs, not its schedule: import the same schedule into the project separately.
  • Anything in a file the import cannot read is listed and left out.

Try RiskForesight for 14 Days.

No card needed.