Table of contents

• Allow blanks (content control)
• Code set
• Config
• Connector
• Content control
• Download
• Execution component
• Host field
• Host systems
• Host systems parameters
• ILAP Core Term
• ILAP ISO standard
• ILAP Term
• Owner
• Owner status
• Partner
• Planning object type
• Receiver
• Representatives
• ScheduleID
• Sender
• Setup admin
• Template
• Tenant
• Upload
• Value transformation

Find the definitions for concepts that are used throughout the ILAP Data Exchange application. In the table of contents to the right, you find the list of all the concepts covered in this article.

Allow blanks (content control)

When validating the content of an ILAP Term, the Allow blanks setting controls whether blank values (no value) are allowed or if only the listed content is valid. If Allow Blanks is turned on, then blank becomes a valid content, in addition to the defined list.

Code set

A Code Set is a definition of user fields present in a Host system. For example, defining how R-fields are used in Safran or user created fields are used in Primavera.

Config

The purpose of a Config is to specify how the information defined in a Template can be either pulled from or sent to a Connector.  For example, if we have the template “Small MMO Projects” that specifies a list of ILAP Terms that shall be included in transfers between two Safran systems:

• Sender must have a Config specifying which user-fields in their Safran that contain the requested information.
• Receiver must have a Config specifying which user-fields in their Safran that receive the information.

For more information, read the article about Configs.

Connector

A Connector is a definition of a specific location where a host system stores its data, including necessary authentication information to access the data. A connector will use an API to access planning data that is stored in a database or a file location to access planning data that is stored in a file.

For more information, read the article about Connectors.

Content control

To ensure quality, ILAP Data Exchange offers Content Control for ILAP Terms. Content control done by defining a list of valid values for the specific ILAP term. Content Control can be defined for all IDE users, for a Tenant, or for a Template, allowing some ILAP Terms to have identical content control while others vary between use cases.

For more information, read the article about Content control.

Download

A Download refers to the operation performed by the Execution Component when downloading schedule data from the Service and inserting it into a Host System.

Execution component

The Execution Component refers to the on-premise component all organisations participating in transfers must have installed within their own IT infrastructure.  The execution component that are available today are the Desktop client and the autonomous component.

Host field

A Host Fields is a data field present in a Host System. The Host Fields are available for IDE to extract data from and perform value transformations.

Host systems

Umbrella term for all scheduling systems.

Host systems parameters

Host system parameters are settings to control what is being uploaded or downloaded to or from a Host system. The parameters are different for each host system, as well between directions (upload and download) even if it relates to the same Host system.  

ILAP Core Term

ILAP Core Terms are the central planning fields defined by the ILAP Ontology for expressing a schedule. The Core Terms are always part of a transfer, even if they are not specifically defined in a Template.

ILAP ISO standard

The International Standard for the representation of process industries facility life-cycle information (ISO 15926-13:2018). It specifies an ontology for asset planning for process plants, including oil and gas production facilities. In addition, it specifies an XML schema, derived from the ontology, for exchange of data used for asset planning. More information can be found on the ISO website: https://www.iso.org/standard/70694.html.

ILAP Term

A schedule contains Planning Object Types (Links, Profile, etc.), each with properties. Some properties are general, like Start Date, while others are specific to a schedule, like Responsible. These properties are called “ILAP Terms”.

Some ILAP Terms are predefined, like Start Date for an Activity, and are called “Core Terms.” Others are created and managed within IDE for proper information transfer, including Content Control.

Owner

The Tenant that owns the IEA and is therefore the one that requests the transfers and initiates setting it up. An owner can be on either the sending or receiving end of the transfers.

Owner status

A status that a tenant can have, implying that user in that tenant can initiate the creation of an IEA and therefore be the Owner of an IEA. Owner status has to be obtain by request of the Tenant Admin.

Partner

The Tenant is invited into an IEA by the Owner. The partner is only concerned with their side of the transfer arrangement.

Planning object type

The Planning Object Type identifies the parent/type of an ILAP Term or Core Term. For example, if the Planning Object Type of Start is Activity, the Start is an Activity Start. If the Planning Object Type of Start is Schedule, the Start is a Schedule Start.

Receiver

The tenant that is receiving planning information. This can be either the Owner or the Partner on the IEA.

Representatives

People within the tenants that participate on the IEA. On each IEA there is at least one Owner representative and one Partner representative.

ScheduleID

The Schedule Identifier used by the Host System.

Sender

The tenant that is sending planning information. This can be either the Owner or the Partner on the IEA.

Setup admin

A user within a tenant that is responsible for setting up the configurations that enable the creation of ILAP Exchange Agreements.

Template

A template lists the ILAP Terms the Owner wants to transfer with a Partner. Typically, the Owner is the Receiver, making the Template the information to be received in the planning transfer. A Template is set up once and reused in multiple IEAs.

If any ILAP Terms in the Template delegate content control to Template Level, the Template must also include valid content for that ILAP Term.

Once created, a Template can be shared with other Tenants expected to use it in transfers.

Tenant

An organization that chooses to use the IDE becomes a tenant of the service, thus referred to as Tenant.  The Tenant is in most cases recognized by its domain (e.g. companyname.com) and can be set up to use authentication from the organization’s AzureAD, enabling the organization to control user access to the Service from it’s existing user access control systems.

Upload

An Upload refers to the operation performed by the Execution Component when uploading schedule data from a Host System to the IDE.

Value transformation

Transformation of the content in the scheduling data from or to the ILAP standard, applied during upload or download. This transformation is crucial for interoperability between scheduling systems.