Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ

APPENDIX A

Working With Primavera

bl e
fe r a
ans
Objectives n - t r
a no
h a s
❑ Briefly describe the process of importing a Primavera project plan into
Primavera Risk Analysis
m ) deฺ
l ฺ c o Gui
c h te ent
@ be Stud
e z 1 this
e nd use
( m m to
i t ed cense
Lim li
te l
e c h
B

© 2009 All rights reserved. No part of this publication may be reproduced without prior written permission of Oracle Primavera. 235
 Appendix A: Working With Primavera

Working With Primavera

Primavera Risk Analysis can import project plans from a Primavera P3 or P6
database and feed the analysis results back into the database. It can also
Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ

import a P6 or P5 XER file or a P3 PRX file.

Data imported from an XER file cannot be sent back into the P6 or P5 database
after analysis. The P3 PRX file can be renamed to an EXE file after analysis and
sent back into the P3 database.

Defining Data Fields

bl e
When importing a project plan from any version of Primavera, it is important ftoe r
to a
create custom data fields in the Primavera project prior to the import n s
and
- tra
map those fields to the appropriate fields in the Primavera RisknAnalysis
application. The custom fields are where uncertainty will a nostored in
be
Primavera P6. h a s
m ) deฺ
l ฺ
Once the custom fields are created, dialogc i
oboxesGinuPrimavera Risk Analysis will
t e
h Primavera
help you map them to the appropriate t
n Risk Analysis fields during the
import process. e
b Stu c d e
z 1 @ is
e t h
Menu-Driven
e nd use
( m m to
e itself is menu-driven. In the Primavera Risk Analysis File
nsprocess
edThe cimport
i t e
li click Primavera. Secondary menu choices will guide you through
l Lim menu,
c h te selection and appropriate data mappings for the type of Primavera project you
B e are importing.

If you are connecting to a P6 database for the first time, run the Connection
Wizard first.

Monitoring the Import

Links from the project being imported to other projects in Primavera may
cause warnings on the import. Such warnings should be investigated to ensure
that the other projects do not constrain or otherwise interfere with the
imported project.

Planning units can also be an issue. If the Primavera project uses more than
one calendar, the project should be imported into Primavera Risk Analysis
using hours, rather than days.

236 © 2009 All rights reserved. No part of this publication may be reproduced without prior written permission of Oracle Primavera.
 Appendix A: Working With Primavera

Following the import, Primavera Risk Analysis will display an Import Check
sheet in the workspace identifying any potential problems with the import.

Primavera Risk Analysis imports only a copy of the Primavera schedule, so you
do not have to worry about corrupting live Primavera data.
Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ

It is usually advisable to import the WBS project structure along with the
project plan if available. Be sure to mark the Import the WBS Project Structure
checkbox in the Primavera Enterprise Import Settings dialog box.

Remember to define Custom Data Items in Primavera, in which to store the

minimum/most likely/maximum uncertainty estimates, and map them to the
appropriate fields in Primavera Risk Analysis prior to the import. Then, verify
bl e
the import with the Import Check sheet in the Primavera Risk Analysis
fe r a
workspace.
ans
n - t r
o
s an
) ha eฺ
c o m uid
t ฺ
el nt G
h
ec tude
b
@ is S
z 1
e e th
n d
e o us
m
(m se t
i d
te licen
Li m
te l
e c h
B

© 2009 All rights reserved. No part of this publication may be reproduced without prior written permission of Oracle Primavera. 237
Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ

bl e
fe r a
an s
n - t r
o
s an
) ha eฺ
c o m uid
t ฺ
el nt G
h
ec tude
b
@ is S
z 1
e e th
n d
e o us
m
(m se t
i d
te licen
Li m
tel
e c h
B

238 © 2009 All rights reserved. No part of this publication may be reproduced without prior written permission of Oracle Primavera.