Table of contents

• Why use ILAP Data Exchange?
  
• How does ILAP Data exchange work?
• The ILAP ISO Standard
• ILAP exchange agreements
• The transfer configuration
• How to get started?
• Suggested further readings on introductory topics

ILAP Data Exchange (IDE) is a service that enables scheduled transfers of planning data between actors and across different scheduling systems. The service paves the way to a world of interoperable scheduling data.

Conceptual visualization of ILAP Data Exchange as the link between actors and across planning systems.

Why use ILAP Data Exchange?

Today, many different planning software are being used, even by companies that work closely together. Planning data is not compatible between the different software, making data collection a time-intensive and error-prone process.

IDE is the first software to automate planning data exchange across scheduling systems. This not only improves efficiency and quality of the data exchange, but it also opens the doors for large-scale data analysis and optimization.

How does ILAP Data exchange work?

To understand how IDE works, you need to understand a few core concepts. These are listed below with a short explanation.

The ILAP ISO Standard

At the centre of IDE you will find the ILAP ISO standard. It specifies an ontology for asset planning for process plants, including oil and gas production facilities. In addition, it specifies an file schema, derived from the ontology, for exchange of data used for asset planning. By having this standard, companies only have to relate the data that they use to the ILAP standard. Once this is done, they will be able to exchange data with any company that has done the same.

Conceptual visualization of how data becomes interoperable when actors with different planning systems relate their data to the ILAP standard.

ILAP exchange agreements

ILAP exchange agreements (IEAs) are agreements between actors that are typically created at the beginning of a project. At the core, an IEA is the definition of what data is to be transferred, when and between which parties. This needs to be defined once, after which transfer events will be created at the desired intervals. A one-click Upload, followed by a one-click Download is all that is needed to transfer high quality and interoperable planning data from this point on.

The transfer configuration

Behind the IEAs, there is a more complicated configuration that makes the transfers possible. This configuration is managed by Setup users. All that regular users need to know is that Setup users can create Templates (read more about template here), Connectors (read more about connectors here) and Configs (more about configs here). With these three elements in place, all users can easily create IEAs and start exchanging data.

How to get started?

Which of these 4 choices best describe your situation ("I want to..."):

1. Execute schedule transfers which have already been set up
   
2. Set up IDE so that planners can upload schedules
3. Sign up to IDE on behalf of my company and transfer schedule(s)
4. Set up IDE so that planners can receive schedules from planners elsewhere

...or you may want to read more here on general instructions for how to set up a transfer in IDE.   

Suggested further readings on introductory topics

Understand the concept of ILAP exchange agreements (IEAs) 

Understand the basic terms used in this document in Glossary