TABLE OF CONTENTS

• Introduction
• The feature Corner Stones
• Connector
• Template
• IEA (ILAP Exchange Agreement)

Introduction

This article introduces the feature corner stones of ILAP Data Exchange (IDE) and explains how they work together to transfer of schedule data from one planning system to another.   The purpose of this article is NOT to make you understand every detail of how the corner stones work, but to give you an overview so that it becomes easier to learn about the details in other articles.

The feature Corner Stones

Connector

In order to transfer schedule data between planning systems, we need to access the schedule data where they are.  This is the purpose of the Connector.  If we want to transfer schedule data from a certain schedule that for example is stored in a Primavera database, we need to create a Connector that can access that Primavera database and expose all the schedule data contained therein for transfer via ILAP Data Exchange.

The Connector feature is used to register required information for both the sending and receiving planning systems.  They need a Connector each, so that we can identify both where the schedule data involved in a transfer is coming from and going to.

Read here to find out more about Connectors.

Template

The purpose of a Template is to specify which schedule data that is supposed to be included in our transfers.  Basic information (Core Terms) such as start, finish, calendar etc. are always included, but there can be a wide range of contextual information about the planning activities that we would like to include in the transfer (ILAP Terms).   Examples may be activity information such as responsible person, an area reference or some other technical data.

By creating a Template and sharing it with the other party in the transfer we can define the list of special information we expect.  Furthermore, the Template also allows specification of coding and validation rules.

Templates can be re-used for different transfers.

Read here to learn more about Templates.

Read here to learn more about Core Fields and ILAP Terms.

Config

The purpose of the Config is to specify exactly where we can find the information listed in a specific Template for a specific Connector.  If the Template defines that we shall transfer an area code for each activity, the Config allows us to specify the field that contains that area code within the database the Connector is pointing to.

Furthermore, the Config also allows us to specify data transformation so that we can make the schedule data included in the transfer compliant with any validation rules that are specified in the Template.

Read here to learn more about Config.

IEA (ILAP Exchange Agreement)

The IEA feature is used to set-up the actual transfer of schedule data.  We call it an “Exchange Agreement” because it allows two different parties to agree on what shall be transferred from where to where at which frequency.  The IEA refers to:

• A sending Connector to specify where schedule data is coming from
• A receiving Connector to specify where schedule data is going to
• A Template to specify which schedule data shall be transferred

For a Template to be available for selection, it needs to have a Config against both the sending and receiving Connectors.

Read here to learn more about IEAs.