IBM 7 Release 5 Maximo Adapter User Guide

IBM Maximo Adapter for Primavera
Version 7 Release 5
User Guide
Note
Before using this information and the product it supports, read the information in “Notices” on page 25.
Compilation date: April 2011
This edition applies to version 7, release 5 of IBM Maximo Adapter for Primavera and to all subsequent releases
and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2011.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. Configuring Maximo Adapter
for Primavera . . . . . . . . . . . . 1
Configuring Primavera API connection .
Configuring the adapter parameters . .
Configuring security options . . . . .
Maximo Adapter for Primavera cron tasks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
2
3
Chapter 2. Setting project data
preferences . . . . . . . . . . . . . 5
Data transfer requirements and restrictions . .
Primavera craft options . . . . . . . . .
Primavera site options . . . . . . . . .
Defining custom mappings . . . . . . .
Assigning custom mappings to sites . . . .
Resources by work location . . . . . . .
Setting up user data and connection preferences
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
6
6
7
8
8
9
Chapter 3. Data mapping . . . . . . . 11
Work breakdown structures (WBS).
Activities data map . . . . . .
Enterprise project structure (EPS) .
© Copyright IBM Corp. 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11
. 12
. 14
Export of resource pools .
.
.
.
.
.
.
.
.
. 15
Chapter 4. Integrating Maximo Asset
Management and Primavera data . . . 17
Creating relationships between tasks in projects
Linking to an existing project . . . . . .
Importing data from Primavera. . . . . .
Transferring work orders from Maximo Asset
Management to Primavera . . . . . . .
Exporting work orders to Primavera . . .
Appending work orders into a project . .
Deleting projects. . . . . . . . . .
Data transfer requirements and restrictions .
Data transfer exceptions . . . . . . .
.
.
.
. 17
. 17
. 18
.
.
.
.
.
.
.
.
.
.
.
.
18
18
19
19
19
20
Chapter 5. Synchronizing Data . . . . 23
Updating work orders in Primavera .
Refreshing projects . . . . . . .
.
.
.
.
.
.
.
.
. 23
. 23
Notices . . . . . . . . . . . . . . 25
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 26
iii
iv
IBM Maximo Adapter for Primavera 7.5: User Guide
Chapter 1. Configuring Maximo Adapter for Primavera
After you install Maximo® Adapter for Primavera, you must complete
configuration tasks.
Configuring Primavera API connection
You need to configure the connection between Maximo Adapter for Primavera and
Primavera before you can transfer data between the applications.
Procedure
1. In the Organization (PV) application, from the Select action menu, click
Primavera Options > Primavera API Connection.
2. Insert a row and specify a name and description for the API connection.
3. Specify the network address of the Integration API server in the Primavera API
server name or IP address field.
4. Optional: To connect in remote mode:
a. Specify the Integration port in the Primavera API port field.
b. Specify the time zone of the server that hosts the API in the API Time zone
field.
5. Select the name of the Primavera database from the Primavera DB Name list.
6. Optional: To prevent work orders being exported to multiple projects, select the
option Deny the Creation of duplicated projects in Primavera.
7. To test that the connection is working, enter the user name and password that
the adapter uses to sign on to Primavera and click Test Connection.
8. Click OK to save the connection information.
Configuring the adapter parameters
You configure IBM® Maximo Adapter for Primavera parameters in IBM Maximo
Asset Management to determine how data is handled during export.
Before you begin
You must configure the Primavera API connection details in the Organization (PV)
application of Maximo Asset Management before configuring the adapter
parameters.
Procedure
1. In Maximo Asset Management, click System Configuration > Platform
Configuration > System Properties.
2. Select the parameter that you want to configure and specify its value. You can
configure the following parameters:
© Copyright IBM Corp. 2011
1
Parameter
Description
Valid Values
mxe.primavera.
nodesc
Sets up the description of a work
order when no description is
provided. You can also use this
parameter to name a project
when no project description is
provided.
Text enclosed in double
quotation marks. The default
value for this parameter is “NO
DESCRIPTION”.
mxe.primavera.
leadingzero
Indicates whether leading zeros
on work order numbers are
removed when the work orders
are exported to Primavera.
v Y (default) - The leading zeros
are removed.
mxe.primavera.
exportcalendars
v N - The leading zeros are not
removed.
Indicates whether Maximo Asset v Y (default) - Maximo Asset
Management calendars are
Management calendars are
exported to Primavera.
exported.
v N - Maximo Asset
Management calendars are not
exported.
mxe.system.globallog Indicates whether the user name v Y (default) - The user name is
of each user is logged before
logged.
their messages in the adapter log
v N - The user name is not
file.
logged.
mxe.primavera.
collectstatistics
Collects system performance
statistics, recording when
adapter processes start and
finish, and calculating how long
the processes take.
v 0 (default) - Statistics
collection is disabled.
v 1 - Statistics collection is
enabled.
Configuring security options
You can authorize user groups in IBM Maximo Asset Management to use the
Maximo Adapter for Primavera functions. To transfer data between the two
applications users must also have corresponding privileges in Primavera.
Procedure
In the Security Groups application, configure the following security options:
2
Option
Description
PLUSVEXPORT
Authorizes users to export projects to
Primavera.
PLUSVUPDATE
Authorizes users to update projects in
Primavera.
PLUSVAPPEND
Authorizes users to append work orders to a
project.
PLUSVREFRESH
Authorizes users to refresh data in
Primavera projects.
PLUSVDELETEA
Authorizes users to delete projects in
Maximo Asset Management and Primavera.
PLUSVPROJECTLINK
Authorizes users to link projects in
Primavera with data in Maximo Asset
Management.
IBM Maximo Adapter for Primavera 7.5: User Guide
Maximo Adapter for Primavera cron tasks
Cron tasks are behind-the-scene jobs that run automatically and on a fixed
schedule. There are three cron tasks installed with Maximo Adapter for Primavera.
Table 1. Maximo Adapter for Primavera cron tasks
Cron task
Description
PlusVProjectCron
The project cron task updates existing
Primavera projects with Maximo Asset
Management data.
PlusVRevalidatecache
The revalidate cache cron task synchronizes
the Maximo Adapter for Primavera cache.
PlusVWOExpCronTask
The work order export cron task transfers
selected work orders from Maximo Asset
Management to Primavera.
Chapter 1. Configuring Maximo Adapter for Primavera
3
4
IBM Maximo Adapter for Primavera 7.5: User Guide
Chapter 2. Setting project data preferences
You can configure the adapter to determine how your project data is transferred
between Maximo Asset Management and Primavera. You can set your preferences
to determine what information related to work orders and resources is exported to
Primavera.
Data transfer requirements and restrictions
IBM Maximo Adapter for Primavera limits what data can be transferred and how,
based on the type of data that is being transferred. You can set the export block
size limit. You can also set limits for exporting and appending work orders.
Table 2. Data transfer requirements and restrictions
Data
transferred
Requirements and restrictions
Preventive
Maintenance
(PM) records
To transfer PM records from Maximo Asset Management to Primavera,
configure the following settings in the Preventive Maintenance (PV)
application:
v The Estimated Next Due Date (located in the Time Based Frequency
subtab of the Frequency tab) must be set to a future date.
v The Extended Date in the Frequency tab must be equal to the current
date.
v Adjust Next Due Date must be selected.
All PM records and job plans that you want to export must be active.
Purchase order If a work order is on a purchase order line and the work order is exported
lines
to a project in Primavera, the purchase order line becomes a constraint
activity in Primavera with a Finish-Start relationship to the work order
activity. For example, in Maximo Asset Management, PO 1068 line 1 refers
to work order 1032. When the project is exported, both the PO line and
the work order become activities in Primavera. The PO activity is created
with a Finish-Start relationship to activity 1032.
© Copyright IBM Corp. 2011
Labor, crafts,
and tools
All labor, crafts, and tools are exported to Primavera the first time there is
an export from Maximo Asset Management. If a resource changes in
Maximo Asset Management, the corresponding record in Primavera
changes on the next export from Maximo Asset Management.
Calendars
If the mxe.primavera.exportcalendars parameter is set to Y in the System
Properties application, all calendars are exported to Primavera the first
time there is an export from Maximo Asset Management. If a calendar
changes in Maximo Asset Management, the corresponding calendar in
Primavera changes on the next export.
5
Table 2. Data transfer requirements and restrictions (continued)
Data
transferred
Dates
Requirements and restrictions
Actual start, actual finish, scheduled start, scheduled finish, and constraint
dates are the date fields that are exported from Maximo Asset
Management to Primavera. Projects that are imported back into Maximo
Asset Management update the scheduled or actual dates depending on
the status of the activity in Primavera.
v If the activity is not started, the scheduled dates are changed to the
values that are imported from Primavera.
v If the activity is started, the actual dates are changed to the values that
are imported from Primavera.
Target dates are never affected by importing a project into Maximo Asset
Management.
Primavera craft options
Resource records are updated or created in Primavera whenever an export occurs.
You can control if the craft availability is calculated and exported to Primavera,
based on IBM Maximo Asset Management calendars and shifts.
Craft availability is the mechanism that IBM Maximo Adapter for Primavera
provides to calculate the amount of labor resources available. The availability is
calculated per unit of time per craft record, based on Maximo Asset Management
calendars and shifts. The Craft Availability Options window in the Organizations
(PV) application provides you with the details to determine how to calculate that
amount.
Primavera site options
Different sites within an organization can operate under different business rules.
Therefore you can control how purchasing and preventive maintenance constraints
are exported to Primavera at the site level.
The following tables describe the options available in the Primavera Site Options
window in the Organizations (PV) application.
Table 3. Site level options for exporting purchase constraints.
Transfer Purchase Constraints To
Primavera Based On
6
Result
purchase line item
The adapter creates a milestone activity in
Primavera representing the purchase line item. The
required date of the purchase line is the constraint
date.
requisition line item
The adapter creates a milestone activity in
Primavera representing the purchase requisition line
item. The required date of the purchase requisition
is the constraint date.
both
The adapter creates a milestone activity in
Primavera representing both purchase and
requisition line. The required date of the purchase
or requisition line is the constraint date.
IBM Maximo Adapter for Primavera 7.5: User Guide
Table 3. Site level options for exporting purchase constraints. (continued)
Transfer Purchase Constraints To
Primavera Based On
Result
none
The adapter does not create any milestone activity
in Primavera based on purchase line items or
purchase requisition line items.
constraint type
Select if the type of constraint applies to purchase
or requisition milestone activity.
Table 4. Site level options for exporting preventive maintenance constraints.
Transfer PM Constraints To
Primavera Based On Target Dates
Result
create constraint
The adapter sets the work order constraint date
based on the target date of the preventive
maintenance.
constraint type
Select the type of constraint to be applied to
preventive maintenance work order, only when the
constraint type is not specified on the job plan.
Table 5. Site level options for exporting tools and material data.
Optional Export
Header
Tools
The adapter assigns the planned tools as activity
resources in Primavera.
material reservation dates
The adapter imports the schedule start date from
Primavera and sets it as the material required date
in the planned work order task detail. The material
required date is then used to generate the inventory
reservation when the work order is approved.
Defining custom mappings
Custom mappings are user-defined fields that transfer extra information between
Maximo Asset Management and Primavera. Custom mappings are exclusive to the
Primavera API of the current user. To define custom mappings you must be
authorized to access the Primavera API.
Procedure
1. In the Organizations (PV) application, select the organization that you want to
work with on the List tab.
2. From the Select Action menu, select Primavera Custom Maps.
3. In the Primavera Custom Maps window, select the API Connection for which
you want to define the custom mapping.
4. Click New Row and specify the required information.
5. To create custom fields in Primavera click OK.
Results
After you define the custom mappings, they are available to be assigned to
individual sites on the Sites tab of the Organizations (PV) application.
Chapter 2. Setting project data preferences
7
Assigning custom mappings to sites
As different sites in an organization can operate under different business rules, you
assign custom mappings at site level.
Procedure
1. On the Sites tab of the Organizations (PV) application, select the site that you
want to work with.
2. Click Select custom mappings.
3. Select the required custom mappings from the list and click OK.
Results
The custom mappings are used during the next export of data between Maximo
Adapter for Primavera and Primavera.
Resources by work location
If a resource record exists in Primavera for a craft that you are exporting, the
resource record is updated. If a resource record does not exist in Primavera, one
can be created during the export procedure.
Select the Schedule by Work Location check box to determine the resource records
created in Primavera.
During an export procedure, resource records are handled in one of the following
ways:
v If a resource record exists in Primavera for a craft that is being exported, the
resource record is updated.
v If the Schedule by Work Location check box is not selected, a resource record is
created in Primavera for the specified craft record. The craft standard rate is
included in the resource record. In a multi-organization environment where
duplicate crafts with different standard rates could exist, only the first craft
record is exported to Primavera.
v If the Schedule by Work Location check box is selected, the location specified in
the task is checked for a work location prefix value. If a prefix exists, the prefix
is added to the beginning of the craft to create a resource record in Primavera. If
the task location does not have a work location prefix, the location of the parent
is checked for a work location prefix. If the parent location has a work location
prefix, the work location of the parent is appended to the specified craft to
create the resource record. The craft standard rate is included on the resource
record.
This example shows how resource records are exported to Primavera if the
Schedule by Work Location check box is selected.
The BEDFORD site has 3 work locations, ADDR01, ADDR02 and ADDR03. Each
work location has a prefix.
Table 6. Work location prefix
8
Work location
Prefix
ADDR01
MX1
ADDR02
MX2
IBM Maximo Adapter for Primavera 7.5: User Guide
Table 6. Work location prefix (continued)
Work location
Prefix
ADDR03
null
The resource information on the work order to be exported is:
v Craft planned is MECH.
v Resource location is ADDR01.
The following resource records are exported to Primavera:
v BEDFORD-MECH
v MX1-MECH
Setting up user data and connection preferences
You can modify the labor record of a user in Maximo Asset Management to specify
data which the user does not want exported to Primavera. You can also specify the
Primavera API the user connects to and test this connection.
Procedure
1. On the List tab of the Labor (PV) application, select the labor record of the user
whose data and connection preferences you want to specify.
2. On the Primavera tab, specify the type of data that you want to exclude:
Option
Description
Exclude the current labor record from the
craft availability calculation
The current labor record is not included in
the craft availability calculation when
exporting to Primavera.
Export the current labor record to
Primavera
Select this option to export the current labor
record to Primavera as a valid resource.
Allow user to manage resource pool in
Primavera
Select this option if the current labor record
is not authorized to manage the resource
pool in Primavera. The labor record will be
added to the existing Primavera resources. It
will not create or update the existing
resource pool.
Exclude milestone generation
The Work Breakdown Structure (WBS) is
created but not the start and finish
milestones.
Exclude time exporting
The time portion of the date field in Maximo
Asset Management is not exported to
Primavera.
3. Specify the Primavera API to connect to, and the user name and password. The
user name must exist in Primavera and have permission to access the specified
Primavera Integration API.
4. Test the connection to the Primavera API by clicking Test Connection.
Chapter 2. Setting project data preferences
9
10
IBM Maximo Adapter for Primavera 7.5: User Guide
Chapter 3. Data mapping
You can define the data mapping between IBM Maximo Asset Management and
Primavera to determine how that information is imported or exported. However,
changes made directly into Maximo Asset Management data transfer tables are
reserved to the database administrator.
Work breakdown structures (WBS)
Primavera work breakdown structures are imported into IBM Maximo Asset
Management as a work order hierarchy. WBS activities are imported as work order
tasks.
In Maximo Asset Management, a work order hierarchy consists of a top-level
parent work order and many related work orders. Terminal work orders are the
last level in the hierarchy and contain tasks.
You can set the target start and finish dates on terminal work orders in Maximo
Asset Management to be the start and finish milestones in Primavera. Alternatively,
Primavera can generate start and finish milestones for the WBS node that
represents the terminal work order. You can specify that all parent, child, and task
work orders in Maximo Asset Management must become activities when they are
exported to Primavera. In this case, no WBS nodes are created. If you import this
project back into Maximo Asset Management you must specify import criteria.
Work order hierarchies from Maximo Asset Management are exported as WBS
nodes or activities to Primavera.
Table 7. How work orders are mapped to work breakdown structures when they are
exported to Primavera
Maximo Asset Management
column
Primavera object
Primavera column
Work order number
WBS
WBS code
Work order number of the
parent work order
WBS
Parent WBS code
Description
WBS
WBS name
WBS nodes are imported from Primavera to the Work Order Tracking (PV)
application. Projects that are created in Primavera as a result of an export of
preventive maintenance records from Maximo Asset Management are not imported
back into Maximo Asset Management.
Table 8. How WBS objects are mapped to work order objects when they are imported from
Primavera
© Copyright IBM Corp. 2011
Primavera object
Primavera column
Maximo Asset
Management column Notes
WBS
Actual start date
Actual start
The earliest actual
start date of all
activities in the work
breakdown structure.
11
Table 8. How WBS objects are mapped to work order objects when they are imported from
Primavera (continued)
Primavera object
Primavera column
Maximo Asset
Management column Notes
WBS
Actual end date
Actual end
The latest actual
finish date of all
activities in the work
breakdown structure.
WBS
Duration percent
complete
Percent completed
Summary of the
actual duration
percent of all
planned durations of
the activities under
this work breakdown
structure.
WBS
At completion
duration
ESTDUR
Total working time
from the activity start
date to the finish
date.
WBS
Remaining duration
REMDUR
Total working time
from the work
breakdown structure
remaining start date
to the remaining
finish date.
WBS
Start
Schedule start
The earliest estimated
start date of all
activities in the work
breakdown structure.
WBS
Finish
Schedule finish
The latest finish date
of all activities in the
work breakdown
structure.
The project in Primavera must be summarized on all its WBS nodes so that the
adapter can receive the information and import it to Maximo Asset Management.
Activities data map
IBM Maximo Asset Management tasks are exported to Primavera as activities.
Activities are imported from Primavera as work order task records in Maximo
Asset Management.
Export tasks as activities
Work orders are exported to Primavera as activities. The following table provides
the correlations between Maximo Asset Management tasks and the activities that
are created in Primavera during the export process.
Table 9. Exported tasks
12
Maximo Asset Management column
Primavera column
Work order number
Activity ID
Work order description
Activity name
IBM Maximo Adapter for Primavera 7.5: User Guide
Table 9. Exported tasks (continued)
Maximo Asset Management column
Primavera column
Activity type
Activity type
Duration type
Duration type
Complete type
Percent complete type
Percent completed
Percent completed
Primary constraint type
Primary constraint
Primary constraint date
Primary constraint date
Estimated duration
Original duration
Time remaining
Actual duration
Estimated duration
At complete duration
Actual start
Actual start date
Actual finish
Actual finish date
Schedule start
Planned start date
Import activities
Activities are imported from Primavera to Maximo Asset Management as work
order task records. The following table provides the correlations between
Primavera activities and the work order task records that are created in Maximo
Asset Management during the import process.
Table 10. Imported activities
Primavera table
object
Primavera column
Maximo Asset
Management column Notes
Activity
Activity ID
Work order number
Activity
Description
Description
WBS
WBS code
Work order parent
number
Activity
Activity type
Activity type
Activity
Actual start date
Actual start
Activity
Actual end date
Actual end
Activity
Percent completed
Percent completed
Activity
Planned start date
Schedule start
Activity
Planned end date
Schedule finish
Activity
Original duration
Estimated duration
If the value does not
exist in Maximo
Asset Management,
this activity was
created in Primavera.
This value can be
used to create a task
work order record.
Used to identify to
which work order
this activity belongs.
Chapter 3. Data mapping
13
Table 10. Imported activities (continued)
Primavera table
object
Primavera column
Maximo Asset
Management column Notes
Activity
Remaining duration
Time remaining
Stores the remaining
duration of the
activity. Remaining
duration is the total
working time from
the activity
remaining start date
to the finish date.
The remaining
working time is
computed using the
activity calendar.
Before the activity
starts, the remaining
duration is the same
as the planned
duration. After the
activity is completed,
the remaining
duration is zero.
Import logic
Predecessor and successor constraints are imported from Primavera to Maximo
Asset Management as work order logic records. The following table provides the
correlations between Primavera constraints and the work order logic records that
are created in Maximo Asset Management during the import process.
Table 11. Imported logic
Maximo Asset Management
column
Primavera table object
Primavera column
Activity relationship
Predecessor ID
From reference work order
number
Activity relationship
Successor ID
To reference work order
number
Activity relationship
Lag
Lag
Activity relationship
Relationship type
Type
Enterprise project structure (EPS)
The enterprise project structure (EPS) in Primavera contains details of the projects
that are in the database and the ownership of those projects. When a project is
created, it is assigned to an EPS node. You must select an EPS node to open the
Export section on the Export tab. You cannot export data if you do not select an
EPS node.
Target EPS
If the target EPS node does not exist, you must create the EPS node in Primavera
and then import the EPS node into IBM Maximo Asset Management. You must
keep the EPS node details up-to-date in Maximo Asset Management.
14
IBM Maximo Adapter for Primavera 7.5: User Guide
Refresh EPS
Refresh the EPS node details in the Work Order Tracking (PV) application before
any transfer operation. You can refresh the EPS node details on the Primavera
Export tab.
Export of resource pools
You can export resources (crafts, labor and tools) from IBM Maximo Asset
Management to Primavera. Mapping rules are applied to the exported resources
and then associated with projects in Primavera.
Export craft as roles
When Maximo Asset Management crafts are exported as roles, they are collected
under the Primavera role heading, MAXCRAFT.
Table 12. Table for exporting craft roles
Maximo Asset
Management
application
Maximo Asset
Management
column
Primavera
Primavera object column
Roles
Role parent ID
Crafts
Craft code
Roles
Role ID
Crafts
Craft name
Roles
Role name
Notes
Set to
MAXCRAFT
Export labor and craft as resources
Labor and crafts are collected under the Primavera role heading, MAXLABOR.
Table 13. Craft mapping
Maximo Asset
Management
application
Maximo Asset
Management
column
Primavera
Primavera object column
Crafts
Craft code
Resources
Resource ID
Crafts
Craft name
Resources
Resource name
Resources
Resource type
Set to LABOR
Resources
Parent resource
ID
Set to
MAXLABOR
Notes
Table 14. Labor mapping
Maximo Asset
Management
application
Maximo Asset
Management
column
Primavera
Primavera object column
Labors
Labor code
Resources
Resource ID
People
Display name
Resources
Resource name
Resources
Role
Notes
Set to the
Primavera Role
ID that
corresponds to
the CRAFT
Chapter 3. Data mapping
15
Table 14. Labor mapping (continued)
Maximo Asset
Management
application
Maximo Asset
Management
column
Primavera
Primavera object column
Notes
Resources
Resource type
Set to LABOR
Resources
Parent resource
ID
Set to
MAXLABOR
Export tools as resources
Maximo Asset Management tools are collected under the Primavera role heading,
MAXTOOLS.
Table 15. Tool mapping
16
Maximo Asset
Management
application
Maximo Asset
Management
column
Primavera
Primavera object column
Tools
Item number
Resources
Resource ID
Tools
Description
Resources
Resource name
Resources
Resource type
Set to Non Labor
Resources
Parent resource
ID
Set to
MAXTOOL
IBM Maximo Adapter for Primavera 7.5: User Guide
Notes
Chapter 4. Integrating Maximo Asset Management and
Primavera data
You can create work orders in Maximo Asset Management using activities in
Primavera. You can track the progress of work orders. You can update Maximo
Asset Management with new schedules, logic relationships, and activities in
Primavera.
Creating relationships between tasks in projects
The relationships between tasks in projects are called logic in IBM Maximo Asset
Management. You can create relationships in Primavera and import them to
Maximo Asset Management where they can be viewed on the Logic tab.
About this task
All dates that are based on the relationships generated in Primavera can be
imported and stored in Maximo Asset Management. You can create logic in
Maximo Asset Management, but the visual component in Primavera shows the
relationships graphically. The Logic tab in the Job Plans (PV) application and the
Logic tab in the Work Order Tracking (PV) application provide the same
functionality. You can begin this task from either application.
Procedure
1. In the Job Plans (PV) or Work Order Tracking (PV) application, select the job
plan or work order for which you want to create logic.
2. On the Logic tab, in the Logic for Job Plan section or Logic for Work Order
section, click New Row.
3. Specify the relationship between the tasks.
4. Optional: In the Lag field, specify the number of hours that are required before
the subsequent activity can start.
5. Optional: In the Relationship field, specify the relationship type.
6. Save your changes.
Linking to an existing project
Generally you create new project in Primavera and import it into Maximo Asset
Management. However you can reuse an existing project in Primavera by linking it
to Maximo Asset Management. When you link to a project, you can import its data
into Maximo Asset Management. You can also append new work orders to it.
Procedure
1. On the Primavera tab of the Work Order Tracking (PV) application, select the
EPS node that contains the project you want to link to.
2. On the Link tab of the Project, select the project you want to link to.
3. Click Link Project.
© Copyright IBM Corp. 2011
17
Importing data from Primavera
You can use Maximo Adapter for Primavera to import data from Primavera into
Maximo Asset Management. You can import logic, activities, activity codes,
schedule dates, actual dates, resource assignments, and Primavera user-defined
fields.
About this task
Primavera activities are imported as work order tasks. Primavera work breakdown
structures (WBS) are imported as work orders. The default work order number for
the imported work orders is the Primavera activity ID. However you can replace
the activity ID with the next available Maximo Asset Management autonumber by
selecting the Allocate new work order number automatically option.
Procedure
1. In the Work Order Tracking (PV) application, on the Projects tab of the
Primavera tab, select a project for which you want to import information.
2. On the Import tab, specify options for the import process.
3. Click Import.
Transferring work orders from Maximo Asset Management to
Primavera
You can add work orders from IBM Maximo Asset Management to project
schedules in Primavera by exporting the work orders to projects in Primavera.
When you export work orders to Primavera you can create a project based on the
details of the work order. You can append work orders to existing projects. You can
update projects.
Before you begin
The enterprise project structure (EPS) node and the organizational breakdown
structure (OBS) must be defined in Primavera and then imported into Maximo
Asset Management. You must keep the EPS node detail up-to-date in Maximo
Asset Management.
Before any transfer operation, refresh the EPS node details from the Work Order
Tracking (PV) application. To refresh the EPS node details, go the Primavera EPS
tab and click Refresh EPS.
Exporting work orders to Primavera
You can create Primavera projects that include work orders from Maximo Asset
Management by exporting the work orders to Primavera. The project logic
establishes the relationships between the work orders you have exported.
Procedure
1. On the List tab of the Work Order Tracking (PV) application, run a query to
select the work orders that you want to export.
2. From the Export EPS tab of the Primavera tab, select the EPS node where you
want to create the project.
3. Select the options in the Primavera EPS Detail tab to reflect how you want
your work orders to be exported.
18
IBM Maximo Adapter for Primavera 7.5: User Guide
4. Click your required export type Work order export or Project export.
Appending work orders into a project
You can add work orders to an existing project. When you append work orders to
a project, you create new work breakdown structures and activities in Primavera.
Procedure
1. On the List tab of the Work Order Tracking (PV) application, run a query to
select the work orders you want to append to the project.
2. On the Projects tab of the Primavera tab, expand the project to which you want
to append the selected work orders.
3. On the Append tab, click Append.
Deleting projects
When you delete a project the relationship between its associated work orders is
deleted. The work orders are not deleted from Maximo Asset Management. You
can delete a project from only Maximo Asset Management, or from both Maximo
Asset Management and Primavera.
Procedure
1. On the Project tab of the Primavera tab, select the project that you want to
delete. Expand the project details.
2. On the Delete tab:
Option
Result
Delete in Maximo only
Deletes the project in Maximo Asset
Management only. The work orders are not
deleted but relationships between them are
deleted. The project remains in Primavera. It
can be linked to again from Maximo Asset
Management.
Delete in Maximo and Primavera
Deletes the project in both Maximo Asset
Management and Primavera. The work
orders are not deleted but relationships
between them are deleted.
Data transfer requirements and restrictions
IBM Maximo Adapter for Primavera limits what data can be transferred and how,
based on the type of data that is being transferred. You can set the export block
size limit. You can also set limits for exporting and appending work orders.
Chapter 4. Integrating Maximo Asset Management and Primavera data
19
Table 16. Data transfer requirements and restrictions
Data
transferred
Requirements and restrictions
Preventive
Maintenance
(PM) records
To transfer PM records from Maximo Asset Management to Primavera,
configure the following settings in the Preventive Maintenance (PV)
application:
v The Estimated Next Due Date (located in the Time Based Frequency
subtab of the Frequency tab) must be set to a future date.
v The Extended Date in the Frequency tab must be equal to the current
date.
v Adjust Next Due Date must be selected.
All PM records and job plans that you want to export must be active.
Purchase order If a work order is on a purchase order line and the work order is exported
lines
to a project in Primavera, the purchase order line becomes a constraint
activity in Primavera with a Finish-Start relationship to the work order
activity. For example, in Maximo Asset Management, PO 1068 line 1 refers
to work order 1032. When the project is exported, both the PO line and
the work order become activities in Primavera. The PO activity is created
with a Finish-Start relationship to activity 1032.
Labor, crafts,
and tools
All labor, crafts, and tools are exported to Primavera the first time there is
an export from Maximo Asset Management. If a resource changes in
Maximo Asset Management, the corresponding record in Primavera
changes on the next export from Maximo Asset Management.
Calendars
If the mxe.primavera.exportcalendars parameter is set to Y in the System
Properties application, all calendars are exported to Primavera the first
time there is an export from Maximo Asset Management. If a calendar
changes in Maximo Asset Management, the corresponding calendar in
Primavera changes on the next export.
Dates
Actual start, actual finish, scheduled start, scheduled finish, and constraint
dates are the date fields that are exported from Maximo Asset
Management to Primavera. Projects that are imported back into Maximo
Asset Management update the scheduled or actual dates depending on
the status of the activity in Primavera.
v If the activity is not started, the scheduled dates are changed to the
values that are imported from Primavera.
v If the activity is started, the actual dates are changed to the values that
are imported from Primavera.
Target dates are never affected by importing a project into Maximo Asset
Management.
Data transfer exceptions
Errors can occur as project data is transferred between Maximo Asset Management
and Primavera. These errors are called transfer exceptions. Transfer exceptions are
related to invalid work order or project data and can be viewed and deleted in the
Exceptions tab.
On the Exception tab of the Primavera tab, you can view a list of transfer
exceptions. You can delete exceptions from the list.
20
IBM Maximo Adapter for Primavera 7.5: User Guide
Table 17. Data transfer exception attributes
Attribute
Description
Primavera exception
The error from the Primavera Integration
API.
Maximo Exception
The Maximo Asset Management version of
the Primavera exception.
Created Date
The transfer error occurred at this date and
time.
Created By
The user who exported the project to
Primavera.
Chapter 4. Integrating Maximo Asset Management and Primavera data
21
22
IBM Maximo Adapter for Primavera 7.5: User Guide
Chapter 5. Synchronizing Data
You can keep the project data in Maximo Asset Management and Primavera
consistent. You can refresh the project data. You can update the project work orders
in Primavera. You can delete the project. When you delete a project the relationship
between its associated work orders is deleted. The work orders are not deleted
from Maximo Asset Management.
Updating work orders in Primavera
When you update a project, you transfer new data from Maximo Asset
Management to the project in Primavera. The update process changes only the
project work orders and tasks that were changed in Maximo Asset Management.
About this task
Child work orders are transferred to Primavera only as part of a hierarchy. Child
work orders on the List tab are not transferred to Primavera.
The following changes are transferred to Primavera:
v
v
v
v
All activity resource assignments
Maximo Asset Management named activity codes
Standard work order and task activity fields
Custom mapped site fields
Tip: If you need to make extensive changes to the structure of a project or to
transfer a new hierarchy from Maximo Asset Management, create a new project.
Procedure
1. On the List tab of the Work Order Tracking (PV) application, run a query to
select the required work orders.
2. From the Projects tab of the Primavera tab, select the project that you want to
update.
3. On the Update tab, select the type of update.
Refreshing projects
You can refresh projects to keep the data in Maximo Asset Management and
Primavera consistent. When you refresh a project, existing work breakdown
structures (WBS) and activities that satisfy the project export criteria are updated.
New WBS and activities consistent with the project export criteria are appended to
the project. The project definition and details, such as notes and logs, are kept.
Data that is not consistent with the project export criteria is removed from
Primavera.
About this task
The following items are replaced when you refresh a project:
v Work Breakdown Structure (WBS)
v Activities
© Copyright IBM Corp. 2011
23
v
v
v
v
Resource assignments
Activity codes
Predecessor and successor logic
Primavera user-defined fields
When you refresh a project that was previously exported, the project definition is
unchanged, but the project contents are refreshed.
Procedure
1. In the Work Order Tracking (PV) application, on the Projects tab of the
Primavera tab, select the project that you want to refresh.
2. From the Refresh tab, select your refresh options and click Refresh.
24
IBM Maximo Adapter for Primavera 7.5: User Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
© Copyright IBM Corp. 2011
25
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE: This information contains sample application programs in
source language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in any
form without payment to IBM, for the purposes of developing, using, marketing or
distributing application programs conforming to the application programming
interface for the operating platform for which the sample programs are written.
These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any
kind. IBM shall not be liable for any damages arising out of your use of the sample
programs.
© Copyright IBM Corp. 2007, 2011. All rights reserved.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.
26
IBM Maximo Adapter for Primavera 7.5: User Guide
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other product and service names might be trademarks of IBM or other companies.
Notices
27
28
IBM Maximo Adapter for Primavera 7.5: User Guide
Printed in USA