Host System Parameters for each host system

Modified on Thu, 16 Oct at 3:08 PM

Table of Contents

Introduction
Safran
- Safran Sending
- Safran receiving
Primavera P6
- P6 sending
- P6 receiving
Microsoft Project
- MSProject sending
Systemanalyse Programmentwicklung (SAP)
- SAP receiving
ILAP Analytics (IA)
- ILAP Analytics sending
- ILAP Analytics receiving

Introduction

Host System Parameters (HSPs) are defined at Config level for each Host System, where Sending and Receiving Configs will have different specific settings to control upload/download.

When creating an IEA, the Config settings will be copied into the IEA and used as default settings to be overridden – allowing for IEA specific control.

Therefore, any changes made to HSPs in a config will not trigger an update indicator at IEA level, since we do not want the config to pass on its settings to IEA after initial creation.

This document describes each Host System’s HSPs for sending and receiving direction, and the TOC will provide a hyperlink to your specific case.

Each section will show a screenshot with "red numbers" for each of the controls, and below it there will be a table that explains what each of the numbered controls does.

Note:
MSProject only supports sending direction, and that SAP has no HSPs for sending (only for receiving direction)

Safran

Safran Sending

1: Export Scope	Controls which set of Safran fields to use when populating the following ILAP Core fields on upload: EarlyStart/Finish, LateStart/Fininsh, ActualStart/Finish, PlannedWorkHours, PlannedProgress ---------------------- Choices are: Total, Baseline, Current, Original Baseline
2: R Fields Export Option	Background: This controls if you want to include "used values" or "all values" for an R-Field to be included in the upload. These can then be used to append "missing values" to another Safran schedule's R-Fields or a P6 schedule's Activity Codes. Possible values: Export only values used: (Default) Only populate the uploaded structure(s) with RField values referenced by uploaded activities. Export all values in referenced RField: Populate the uploaded structure(s) with all RField values for any RField referenced by activity in the uploaded schedule.
3: WBS Structure	This setting is intended to select which RField or OutlineCode to be used for WBS structure in P6.
4: Other Structures	This setting allows for uploading any of the RFields or Outline Codes as a structure even if it is not referenced by any activity. These can then be used for appending values to any structure in receiving schedule (i.e RFields (not Outline Codes) in Safran or ActivityCodes in P6)
5: Use SNET when 'no predecessor'	When set, this will result in any activity with no predecessor to get “Start No Earlier Than” (SNET) constraint set using EarlyStart date.
6: Get activities in batch	Set to "on" to enable fetching activities in batch. The batch size is configured in the Connector and defaults to 10 000.
7: Enable non-ascii character analysis	Enable or disable (default) non-ascii character analysis. The reason for having default to "off" is that it does take some time for large schedules to execute this analysis. In case the analysis detects non-ascii characters, the upload will fail with indication of cause of failure.

Safran receiving

1: Allow Appending Calendars	Control if you wish to allow import of Calendars to receiving schedule. You will want to set this to unchecked if you map the calendar to an existing calendar in receiving schedule.
2: Allow Appending Tasks	Control if you wish to allow new activities to be appended (if unchecked, only existing activities will be updated)
3: Allow Appending Resources	Control is you wish to allow import of Resources. You will want to set this to unchecked if you map or hardcode the ResourceAssignment’s resource to an existing resource in receiving schedule.
4: Allow Appending Structures	Control if you wish to allow appending RField values to existing RFields.
5: Allow Update of Structure Description	Control if you wish to allow changing the alias of the RField from the structure name being imported from (mapped in table at top-right of this form).
6: Only Include Specified Mappings	Control if you wish to only affect the receiving schedule’s fields that are mapped. E.g If you only have a Core field mapping for “Description”, then no other fields in the host system will be affected.
7: Set Activity Duration Fit to False	Control if you want to force the “Duration Fit Flag” in Safran to false. Default is True, so this will ensure that the PlannedWorkHours is not affected (as it may be otherwise).
8: Link Options	Choices: Ignore links: No changes will be made to links in receiving schedule. Rebuild if both “TO” and “FROM” Acts exist (Default): Delete all links where both the Predecessor and Successor activities exist in the sending schedule and then Rebuild all links according to sending schedule. Rebuild if both “TO” or “FROM” Acts exist: Delete all links where either the Predecessor and Successor activities exist in the sending schedule and then Rebuild all links according to sending schedule.
9: Calendar Prefix	Specify (optionally) if you wish to prefix the calendar names. E.g “XXX_” will result in all calendar names having “XXX_” as prefix.
10: Enable conflict analysis	Enable conflict analysis: Default "on" to ensure that conflict analysis will be made on the download (and that the user can let them be resolved). For some large schedules, you may consider turning this "off" in order to save time.
11: Use synthetic resource in absence of resource assignment.	In case your sending schedule has defined planned hours on activity level only, i.e there are no resource assignments defined with the lower level planned hours, then you need to set this option to "on" in order to get the hours transferred to Safran. A Resource will be synthetically added, and for each activity there will be added one Resources Assignment that references this added Resource..
12: Button for adding new structure mapping	When pressed a new row will be added to the list (see 13 below).
13: Structure mappings	Mapping which source structure should append "missing values" to which destination structure. Can be any number of such mappings.

Primavera P6

P6 sending

A screenshot of a computer

AI-generated content may be incorrect.

1: WBS Structure	Specify which Activity Code (if any) to use as WBS structure in upload. Note that even if you do not specify anything here, the existing WBS structure will still be uploaded – so it is only to be used if you wish to override the existing one (for whatever reason).
2: Other Structures	Specify any other Activity Code values you wish to upload. These can be used in receiving config to append values to RFields in Safran, or other Activity Codes in other P6 schedule (Project specific – not Global).

P6 receiving

1: Allow appending tasks	Control is you wish to allow import of Tasks (activities). Default On.
2: Allow appending resource	Control is you wish to allow import of Resources. You will want to set this to unchecked if you map or hardcode the Resource Assignment’s resource to an existing resource in receiving schedule. Default On.
3: Allow appending calendars	Control if you wish to allow import of Calendars to receiving schedule. You will want to set this to unchecked if you map the calendar to an existing calendar in receiving schedule. Default On.
4: Allow appending structures	Control if you wish to allow appending ActivityCode values to existing ActivityCodes. Default On.
5: Do not import WBS	Check this if you want to omit download of WBS structure. Default Off.
6: Only include Specified Mappings	Control if you wish to only affect the receiving schedule’s fields that are mapped. E.g If you only have a Core field mapping for “Description”, then no other fields in the host system will be affected. Default Off.
7: Link Options	Choices: Ignore links: No changes will be made to links in receiving schedule. Rebuild if both “TO” and “FROM” Acts exist (Default): Delete all links where both the Predecessor and Successor activities exist in the sending schedule and then Rebuild all links according to sending schedule. Rebuild if both “TO” or “FROM” Acts exist: Delete all links where either the Predecessor and Successor activities exist in the sending schedule, and then Rebuild all links according to sending schedule.
8: Adjust Safran Lags	Default Off. If checked, the lags for links will be adjusted to preserve the dates in the P6 schedule after F9 is run (reschedule). IDE reads the P6 scheduling engine setting called “Calendar for scheduling Relationship Lag” and corrects the lags according to this in order to get as similar result as possible relative to the sending schedule link’s calendars:
9: Enable conflict analysis	Allow conflict analysis. Default On. You may want to turn this off to improve performance for large schedules.

MSProject sending

A screenshot of a computer

AI-generated content may be incorrect.

If checked, the summary tasks will be part of upload.
Optional: Select which user field to use as WBS structure if P6 is the receiver of the schedule.

SAP

SAP receiving

Control if you wish to only affect the receiving schedule’s fields that are mapped. E.g If you only have a Core field mapping for “Description”, then no other fields in the host system will be affected.
Control if you wish to enable conflict analysis (default "on"). If "On" there will be a slight performance hit, as data must be read from SAP before updates can be made.
You can define how statuses are set for both WorkOrders and Operations, and define the condition by which to set a specific status.
Here is a brief description of the columns in the grid where all this is defined:
- Index: Used to sort the list, and determine the order of execution (*).
  Object Type: Order / Operation
- Function Type: SystemStatus / UserStatus
- Context: Update / Create
- Condition Formula: If this evaluates to True, the function will be executed.

Note:
There are 2 special (but optional) variables that you may use here:
      - HasActuals (True when ActualWorkHours > 0)
      - OrderIsComplete (True when all operations have Progress=100%

Parameter: The value to set (string with no quotes). List of valid values may be specific to each SAP, and needs to be given by SAP Admin.
Inactive: If checked the row will be ignored.
(*) System Status functions are called first, then User Status function

Example of a formula: 
(OPR_ReadyForExecution == "x") && HasActuals

ILAP Analytics (IA)

ILAP Analytics sending

A screenshot of a computer

AI-generated content may be incorrect.

Control which Revision Type to upload. The available choices are shown in the expanded dropdown. Note: The most recently downloaded schedule of the selected Revision Type will be uploaded.

ILAP Analytics receiving

A screenshot of a computer

AI-generated content may be incorrect.

Control which Revision Type to download. The available choices are:
- Live
- Original Baseline
- Baseline
- Current/Revised
If checked, the Cutoff date in ILAP Analytics will be automatically determined, based on the “Cutoff Adjustment Types” (3):
1. Scheduled Transfer Date (default): Uses the transfer date of the IEA to determine the closest previous cutoff for IA, given its “Points in time type”:
2. Host System Cutoff: The Host system (only applies for Safran and MSProject, as the concept of cutoff only exists for these) has a defined cutoff date to use, and it should provide the basis for adjusting the cutoff date in IA by finding the nearest date (forwards and backwards), to allow adjustments based on the Report Schedule’s “Points in time type” (see above).

Example: 
The cutoff may be Sunday at 00:00, so the date will be adjusted to following Monday at 00:00 to match cutoff in IA.