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.

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

Safran 

Safran Sending

1. This setting controls which set of Safran fields will be used for populating the following ILAP Core fields on upload:
   • EarlyStart/Finish,
   • LateStart/Fininsh,
   • ActualStart/Finish,
   • PlannedWorkHours,
   • PlannedProgress
     ----------------------
     Choices are:
     • Total,
     • Baseline,
     • Current,
     • Original Baseline
2. 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.
   • What is the purpose of this feature?
     The uploaded values in any of the structures can be used for appending values in receiving Safran schedule’s RFields (where you can map a structure to an existing RField), or a receiving P6 schedule’s (project specific) Activity Codes.
3. This setting is intended to select which RField or OutlineCode to be used for WBS structure in P6.
4. This setting allows for uploading any of the RFields 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 in Safran or ActivityCodes in P6)
5. When set, this will result in any activity with no predecessor to get “Start No Earlier Than” (SNET) constraint set using EarlyStart date.

Safran receiving

1. 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. Control if you wish to allow new activities to be appended (if unchecked, only existing activities will be updated)
3. 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. Control if you wish to allow appending RField values to existing RFields.
5. 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. 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. 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. 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. Specify (optionally) if you wish to prefix the calendar names. E.g “XXX_” will result in all calendar names having “XXX_” as prefix.

Primavera P6

P6 sending

1. 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. 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. 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.
2. 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.
3. Control if you wish to allow appending ActivityCode values to existing ActivityCodes.
4. Check this if you want to omit download of WBS structure.
5. 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.
6. 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.
7. 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:
   

Microsoft Project
 

MSProject sending

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

Systemanalyse Programmentwicklung (SAP)

SAP receiving

1. 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.
2. 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

ILAP Analytics receiving

1. Control which Revision Type to download. The available choices are:
   • Live
   • Original Baseline
   • Baseline
   • Current/Revised
     
     
2. 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.