Table of contents

• How an ILAP exchange agreement works
• Being part of an ILAP exchange agreement: Owner and Partner
• The IEA in detail
  • The IEA Info
  • The event log
  • Host system parameters

An ILAP exchange agreement (IEA) is an agreement that enables the scheduled transfer of planning data between actors and across different scheduling systems. In essence, the IEA defines (a) the scheduling of the transfers, (b) the parties involved in the transfers and (c) what data to transfer. In combination with configurations in the background, this allows for seamless exchange of interoperable planning data.

How an ILAP exchange agreement works

An IEA contains all the information to transfer planning data from one actor to another, even when they use different planning systems. This is possible because the data from the planning systems is mapped to a common standard: ILAP ISO standard.

By creating an agreement, users are enabled to transfer data for a long as they want through transfer events. In the current version of the ILAP Data Exchange (IDE), the transfers can be completed with one click to upload and one click to download. In the near future, it will even be possible to fully automate this.

Being part of an ILAP exchange agreement: Owner and Partner

IEAs can be created by users within a Tenant that has an Owner status. Other users can participate on an IEA as a Partner. The Owner of the IEA controls most of the settings on the IEA such as the scheduling and the Template. Both partner and owner are responsible for their own configuration such as the Connector and representatives. Both owner and partner can be either Sender or Receiver of data.

The IEA in detail

IEAs contain a lot of information. Here we will briefly explain everything that is in an IEA, starting the IEA Info page

The IEA Info

The IEA Info page of and IEA, broken down into 4 sections.

On top you find the main information (A). This includes the following:

• ID: the unique identification number of the IEA.
• Title: the title that the owner has given to the IEA.
• Status: indicating if the IEA is active (transfer events are being created), new (start date has not arrived yet or IEA is not complete yet) or Expired (end date has passed and transfer events are no longer created).
• Template: a list of ILAP Terms that will be transferred.
• Sender: the tenant that is sending data.
• Receiver: the tenant that is receiving data.
• Activity filter: an optional filter applied to the activities to be transferred.
• Labels: optional pieces of information to organise and easily find IEAs.
• The options button: the button that opens the menu with all the actions with regards to the IEA.
• The navigation tabs: the buttons to switch between the three pages on the IEA.

On the first page of the IEA you will find the IEA info. This has three section: General (B), Owner configuration (C) and Partner configuration (D).

The general information consists of the following:

• Start date: the date that transfer events will start to be generated according to the frequency.
• Expiration date: the date that transfer events will no longer be generated and the IEA moves to the archive.
• Frequency: the rate and time at which transfer events are generated (e.g. daily at 12.00).
• Successor IEA(s) (if applicable): IEAs for which transfer events will be generated as soon as this IEA has completed a transfer. This enables chains of data transfers.
• Comments: notes specific to this IEA.

The Owner and Partner configuration consist of the same information but applying to the one of the two parties.

• Tenant: the ID and name of the organisation.
• Exchange role: indication of whether the party is sender of receiver of data.
• Connector name: the definition of the specific location where the Host system stores its data, including necessary authentication information to access the data.
• Schedule identifier: the identifier used by the Host System.
• Host system: the scheduling system used by the tenant
• Execute component: an on-premise component within a tenant's IT infrastructure that is required to perform transfers to and from ILAP Data Exchange.
• Config: files that specify how the information defined in a Template can be either pulled from or sent to a Connector.
• Representatives: people within the tenants that participate on the IEA.

The event log

On the Event log page of an IEA, you can keep track of all the data transfers. Every row contains information about one transfer. For both the upload and the download you will find the specifics in the detail log, making it is easy to keep track of the transfers and spot any errors quickly.

The Event log page of an IEA

Host system parameters

On the last page you will find the Host system parameters. These are setting that can be set, depending on the host system in use, to control the data that is transferred.

The Host system parameter page of an IEA