Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Oracle Primavera P6
with
TILOS
Linear Scheduling Software
1 Introduction ........................................................................................................... 4
2 Installation notes .................................................................................................. 6
3 Work flow ............................................................................................................... 7
3.1 Push data from TILOS to Primavera.............................................................. 7
3.2 Push data from Primavera to TILOS.............................................................. 8
3.3 Sample profiles .............................................................................................. 9
4 Filtering data ....................................................................................................... 11
4.1 Filter on TILOS Export ................................................................................. 11
4.2 Filters on Primavera Export ......................................................................... 11
5 Category (Code) libraries ................................................................................... 12
6 Resource library data ......................................................................................... 13
7 Task data exchange ............................................................................................ 13
7.1 Task Identification ........................................................................................ 13
7.2 Order ............................................................................................................ 14
7.3 Task Template ............................................................................................. 14
7.4 Calendar ...................................................................................................... 16
7.5 Task planned resources .............................................................................. 17
7.6 Progress information .................................................................................... 18
8 Links ..................................................................................................................... 19
Library items
Calendars
Units
Account items
Resources items
Code libraries
Planning
Tasks
Links
Planned resources
Planned expenses
Code assignments
The exchange is an exchange between 2 different applications using different data and
management models. This document should give some helpers to get best results from the
exchange.
TILOS has more task calculation options than Primavera. Exporting a profile based task to P6
and back will lead to a case that the profile calculation gets overwritten by the import and is no
more alive in the task. The same applies to distance specific link options in TILOS.
In all cases one program should be the leading one where the major edits are done. The other
is than mainly used to visualize the data. This can be applied for the part projects: E.g. in a big
road project, the linear tasks are planned in TILOS, while the non-linear are planned and
managed in Primavera such as Bridges or all the procurements.
The installs can be downloaded from your e-delivery account. If you are unsure about
licensing and installation please contact your IT department or your Oracle support.
The calling mode for the database has to be local. The remote mode is not supported.
After having installed the API you may test the API based on the installed sample programs
from Primavera. All the sample programs are copied to the API folder and start with word
Demo*. If these work OK, then the connection will also work with the TILOS integration.
If there are any problems with the sample applications, contact your IT department or your
Oracle support.
Install the TILOS Exchange tools. Make sure that the installation is made to the correct API
folder. TILOS detects only the first installation folder for the API due to registry settings. If you
have reinstalled the Primavera API is always stored to a new folder. Our setup does not
recognize this.
The exchange needs in all cases a profile, which controls the data exchange by parameters
and the settings which objects and attributes are to be exchanged.
On export a data file is created while on import the data file from the other application is read
and imported.
File based: Here you need to export the data first from one application and then
import that data file using the same profile or another. So it takes always
2 steps. Since TILOS 8 during creation of the data file the profile can be
added as well to the data file.
TCP/IP: The exchange module connects directly with the current TILOS session.
The exchange is controlled only by the exchange module then. TILOS
acts in this case as a server reading and providing the xml data based on
its TCP/IP interface.
The temporary data files for the exchange are stored in the folder
…\AppData\Roaming\Tilos8 in your user area of your windows
installation.
Step 2: If TCP/IP = On: This step is not needed. Continue with steps 3.
In TILOS export the project as XML using the menu option: File / Export. This is
described in the help system of TILOS. Use a profile that is designed for data
exchange with Primavera (our samples have Primavera a part of the name.)
Remember which profile was used and which data file was created.
Step 3: Start the exchange program from your windows menu and select the option: Import
to Primavera.
Step 4: If TCP/IP = On: This step is not needed. The file opened in TILOS is shown. If no
project is opened in TILOS, then an error is shown. Continue with step 5.
Select the data file that you want to import. If the data file contains a profile, then you
can check the option: Use profile from data file (pre-selected) and continue with
step 6. If you do not want to use the embedded profile, continue with step 5.
For later reuse you may save the file configuration. Press button “Save settings”.
If TCP/IP = On: In the background the data file for the exchange is now generated
based on the profile settings.
Step 7: Select the project in Primavera to which you want to import the data to. The default
Project-ID is taken from the TILOS project ID if the project info section has been
added to the data file.
If you want to create a new project, press the + Button to create a new project.
Step 1: If TCP/IP = Off: This step is not needed at this point. Continue with step 2.
Start TILOS and open the file in TILOS to which that you want to export the data to.
There should be only one instance of TILOS running at this time. If there are multiple
running the first found instance will be used.
Step 2: Start the exchange program from your windows menu and select the option: Export
to TILOS.
Step 3: If TCP/IP = On: This step is not needed. The file opened is TILOS is shown. If no
project is opened in TILOS, then an error is shown. Continue with step 4.
Select the data file that you want to use for export. If the profile should be added to
the data file, select the option: Add profile to data file.
Step 4: Select the profile that you want to use for the export.
You can edit the profiles in TILOS using the menu point: Tools / XML profile editor.
Select the filter that you want to use for export. If no filter is set, then all task data
will be exported. If no filter is selected, then no code libraries are exported. However,
task attributes being converted to code libraries get always exported.
Otherwise import the data to TILOS using the Menu File / Import.
This profile exchanges tasks, links and WBS information. The location is taken from 2 user
defined fields DistanceStartText and DistanceEndText. Text fields have been choosen to
support formats containing “+” symbol.
The task template is exchanged to the code library TILOSTemplate by default. The matching
item is the Name of the task template that need to match with the code description.
If you export from TILOS to Primavera, the whole TILOS template library gets exchanged. If
you transfer from Primavera to TILOS, then only the name of the task template to be used is
exchange as a task attribute, not the code library. Missing items in TILOS are automatically
created. To create a complete template library from Primavera codes is not possible as too
few arguments are supported.
If you use a different code library to match with TILOS template, then you need to change the
profile.
WBS gets exchanged with TILOS WBS. In the parameters the option: Project ID is part of
exchange WBS has been switched of. So the project ID is not part of the WBS.
This works the same as above, but in addition, cost and resource data are exchanged.
The name of the applied filter gets stored in the profile. The filter itself is stored in the TILOS
file.
Activities This filter allows to filter the activities to be exported. All activity attributes in the
combo list can be used.
Not all operators can be used for all fields. For codes and UDF fields we can only
apply positive filters as only is this case we can select the activity and later the
links.
UDF Text Fields: Equal, Greater than or Equal. No other operator will work.
To get all tasks where a UDF field has been edited, use Greater than or Equal =
! This is a very low character in ASCII table, so all edited field will be added to
filter result.
Codes By default no code libraries are exported. Only those that are nominated in the
code filter list. Each Code filter line is independent. They work as or.
Resources In general all used resources are exported if the profile specifies also to export
resources. However using a filter that may include also user defined field allow to
take only specific resources that should be shown in TILOS.
To enable the exchange for codes and its assignments, you need to add 3 items to the profile:
In the sample above, only the code library with the name “CodeEPS” gets exported.
Category Allocations are only exported for those items where the library itself is also exported.
On Export: First check if Project Code library with that name exists. If not test EPS, If not test
global. The first found is taken.
On Import: First check if Project Code library with that name exists. If not test EPS, If not test
global. If no matching item is found, a new project related is created. This can later be
converted to a global one in Primavera.
In Primavera a code is used for defining the sections inside the project. In TILOS there is a
sector library with that values. This 2 fields should be matched.
The TILOS attribute Sector is referenced to the code library POS (Position) in Primavera. The
name of the code library has to be announced in Extra parameter.
There are 2 functions, one is based on the path information (01.01) the other on the
descriptions.
TILOS resources can be transferred to the Primavera resource list and versa.
GUID The GUID (Global Unique ID) field is a simple text field assigned to each
task inside TILOS. It is a long 32 characters string calculated at run time.
- If content of UID does not match with any GUID of TILOS, a new task is
created. This gets the imported GUID value assigned. A new TASK-ID is
generated and assigned to this task.
- User has full control of those fields, he can overwrite this at any time, but
this might affect future updates.
- The GUID field of TILOS can be made visible in the task general tab in
the section other attributes.
To work with GUID, the parameters in the profile need to be synchronized both for TILOS and
for P6.
The tag parent UID is not needed for the Primavera data exchange as it has no summary
structure.
7.2 Order
For TILOS exports the field order can be used to export the natural sort order for the activities.
This field can be mapped with any numeric field in P6 and can be used as sort field.
If the imported template does not exist, then a new entry is generated. If the attributes of this
template are edited and the button Adjust Task to Task Template is pressed in the Task
Template library, all tasks will be updated to the new settings.
You need to add either Task Template Name or Task Template ID to your exchange profile.
For import you should have only one set.
The easiest way of defining the task template name is to set a text field containing the names.
Inside the profile editor you need to link TILOS template with this user defined field. Here we
recommend to use task template name.
As the code library contains a path and description, both, ID or template name can be used for
exchange. In this case the name of the code library has to be set in Extra parameter.
7.4 Calendar
TILOS has a Calendar-ID and a calendar name. Primavera only calendar name. So name and
ID of TILOS write to the same attribute in Primavera.
The UID length has been expanded from 25 to 32 characters and now has the same length as
the field name.
If CalendarID = Name and Name is changed, then CalendarID is always set to name.
Day definitions names, that are imported from others applications have a special names
generated from the working shifts.
AccountID This defines the account to which the costs are allocated.
Setting the parameter “Resource import mode” in the TILOS application parameters dialog box
in the XML profile editor. Parameter: Resource import mode = Simple.
In this mode, only simple resource values are exchanged and not the advanced models from
TILOS. This allows a simple exchange of resource data with other programs. The following
data fields are evaluated:
Quantity This value contain the total consumption or effort of the resource.
TILOS can read this value only if progress modell = „Simple %“. In TILOS it is recommended
to have the following settings in tools options:
The deactivated option: Allow to change tasks with simple progress makes sure that
progressed tasks coming from Primavera are not moved at all during reschedule in TILOS and
keep therefore their position.
If progress is recorded in TILOS and should be transferred to P6 all types of progress method
can be applied. Make sure that the parameter:
This groups the part tasks created from progress entries into one single tasks while calculating
the progress.
If Progress > 0 then the status is set to Started and the actual start date is set to imported
start date from TILOS. The % finished value is set and Exp. Finish is set to value imported for
end date from TILOS.
Lag type Working = Working time and Elapsed means calendar time.
Export links to not exported sub-projects: Check this box to export even those links that are
related to any other Sub-Project that is not in
export scope (see also Task Links).
Delete not updated local links: If this option is set, all remaining not updated
Local Links during import get deleted after import.
Delete not updated external links: Same as above, but for External Links.
Support TILOS link attributes Yes means that any additional TILOS link
attribute, if defined in a profile, are exported.