Defining the External Scheduling Interface

To set up the External Scheduling functionality, you must define the required parameters using the Project Planning Parameters (tppss0100s000) session.

To define the parameters

In the Project Planning Parameters (tppss0100s000) session, on the External Scheduling Interface tab, you can specify the default settings for the external scheduling package:

  1. Select the Integration External Scheduling Package check box to specify if the scheduling package integration is implemented. In the group box, specify this information:
    1. Currency: Specify the currency in which the planner of the External Scheduling Package (ESP) can view the resource cost rates and the activity or budget line costs.

      Note:

      • The LN application supports multiple currency systems. Usually an ESP supports only one currency.
      • The XML for the ESP requires an ISO currency code. You can configure the ISO Currency Code using the Currencies (tcmcs0102m000) session.
      • Costs that are displayed in the scheduling packages, only indicate that these costs are converted based on the Currency Rates when the XML file is exported to the ESP. The Costing functionality in most scheduling packages is limited. Therefore, the costs are maintained by the LN application and are not considered when imported.
    2. Time Unit for Hours: Specify the quantity or number of resources assigned (cost objects such as equipment, labor, or subcontracting), expressed in units of time. These cost objects must be converted to a time unit of the ESP (resource time and amount of work). The Time Unit for Hours is the reference to the ESP Time Unit. Note: Use the Conversion Factors (tcibd0103m000) session to convert the time unit of the resource to the Time Unit for Hours. External Scheduling Packages often use hours or seconds (Hours * 60 minutes * 60 seconds) as the Time Unit.
    3. Date Type for Scheduling in ESP: Select the data type that must be used to schedule activities in the application. The available options are Early Dates or Scheduled Dates.
    4. Export Actual Spent Hours: The actual spent hours are calculated based on the hours of the cost objects such as labor, equipment, and subcontracting. LN exports the data for actual hours spent to the external scheduling package. If this check box is cleared, the progress information is not displayed and the hours related data is not exported.

    5. You can use Export Actual Spent Hours check box to include the actual hours spent during the export of data from LN to display the progress in the ESP. This functionality is applicable for all hours related to Budget Lines and Cost History for these Budget Types/ Cost Objects:

      • Labor
      • Equipment
      • Subcontracting (subcontracting such as subcontracting of items based on pieces is not included)
    6. Repository Location: Specify the location where the project XML files must be copied. This file is required as the ESP can include additional planning related internal administration requirements for the project than can be configured in the application. Therefore, this copy is the reference file for all the synchronization processes. Note: The Repository Location is not mandatory, if not specified LN determines a default location on the server.
  2. In the Transfer Resource group box, select the type of resource data that must be transferred to the ESP. Note: Budget Line resources can be of the cost type Material, Labor ( Employees, Trade Group, and Labor Cost Object), Equipment, Subcontracting, and Sundry Cost. For Labor, you can select Employees, Trade Group, or both. Alternatively, you can use the Labor Cost Object for the task.
  3. In the Transfer Assignment group box, based on the cost type, you can configure the level of the assignment that can be defined as the default value for the External Scheduling Interface (tppss2231m000) session. In the application, the resources are linked to Budget Lines, and the Budget Lines are linked to Activities. In the ESP, Budget Lines and Activities can be considered as tasks; or only the Activities are considered as tasks and the resources are directly linked to the Activities.
  4. Select the Export OBS check box to export the organization breakdown structure data of the project to the ESP. If this option is used, you must select the Outline code to be included as part of the export to the XML file.
  5. In the Activity group box, specify the activity related data based on which the task name of the ESP and the custom fields are defined:
    1. Select the Custom fields to be used. The Microsoft Project XML file allows for customs fields, which can be used to transfer additional data. For example, if the value in the field Activity Code is 2, the Activity Code, Budget Line Object Code or both must be specified in the ESP custom Text 2 field. Note: This flexibility to select a custom field is required, as a specific custom field can already be in use by customer.
    2. Save the parameters.
    3. In the Calendar Parameters (tcccp0100m000) session, specify the Default Availability Type for ESP that is used in combination with the configured calendar codes.
    4. In the Calendars for External Packages (tcccp0181m000) session, specify the required information to ensure that the central calendars are available to the ESPs for planning.

    Note: For resources, the Used in Schedule option must be selected, in the related sessions, to ensure that these resources can also be used in the ESP.

  6. In the Calendar Parameters (tcccp0100m000) session, specify the Default Availability Type for ESP that is used in combination with the configured calendar codes. In the Calendars for External Packages (tcccp0181m000) session, specify the required information to ensure that the central calendars are available to the ESP for planning.