Schlumberger-Private

Copyright © 2018 Schlumberger. All rights reserved.

This work contains the confidential and proprietary trade secrets of Schlumberger and may not be copied or stored in an
information retrieval system, transferred, used, distributed, translated or retransmitted in any form or by any means, electronic or
mechanical, in whole or in part, without the express written permission of the copyright owner.

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and services described
herein are either trademarks, trade names or service marks of Schlumberger and its licensors, or are the property of their
respective owners. These marks may not be copied, imitated or used, in whole or in part, without the express prior written
permission of Schlumberger. In addition, covers, page headers, custom graphics, icons, and other design elements may be
service marks, trademarks, and/or trade dress of Schlumberger, and may not be copied, imitated, or used, in whole or in part,
without the express prior written permission of Schlumberger. Other company, product, and service names are the properties of
their respective owners.

An asterisk (*) is used throughout this document to designate a mark of Schlumberger.

The software described herein is configured to operate with at least the minimum specifications set out by Schlumberger. You
are advised that such minimum specifications are merely recommendations and not intended to be limiting to configurations that
may be used to operate the software. Similarly, you are advised that the software should be operated in a secure environment
whether such software is operated across a network, on a single system and/or on a plurality of systems. It is up to you to
configure and maintain your networks and/or system(s) in a secure manner. If you have further questions as to
recommendations regarding recommended specifications or security, please feel free to contact your local Schlumberger
representative.
Schlumberger Private – Customer Use
Techlog 2018.2 Synchronization Tool supports the Techlog model 2018.2 updates.
This version of Synchronization Tool maintains the functionalities covered by the previous Techlog
versions: Send and Retrieve, Compare, Delete and Restore, Lock and Unlock, Refresh as well as
Data Admin workflow.
To use the Synchronization tool in Techlog 2018, the current project should be upgraded to 2018
version of project format.

The repository must be in a shared location to which all users have read/write access. To perform
the conversion:
 Use the Repository converter utility: this includes a data checkup before the conversion.
This is the recommended solution.
 Use the Synchronization tool embedded in Techlog.

Schlumberger Private – Customer Use

The Repository converter exports all objects of a Techlog project (data and non-data objects) to
create a repository Techlog project format.

 Before starting the conversion, install Techlog.

 All the projects you convert to Repository should be Techlog 2018.x format. If not, upgrade
them.
 At the end of the conversion, the previous format is not deleted: ensure that enough disk
space is available.
 During the conversion process, Techlog opens and closes automatically: ensure that at least
one license seat is available.

Schlumberger Private – Customer Use

 1. Browse to: C:\Program Files\Schlumberger\Techlog 2018.2 \RepositoryConverter\ or other
installation folder\RepositoryConverter\.
2. Open the projectList.csv file, and then enter the full path of the project into cell A1.
3. Save the file.
4. Close the project on your machine and launch the RepositoryConverter (located next to the
CSV file) to start the conversion.
If you want to convert more than one project, list all the project paths in the CSV file into the
first column A.

Important: If you encounter issues on projects because their associated project path contains special
characters (¤, &, :, \, /, *, ?, ", <, >, |, .), rename the project path to remove the special characters
and solve the issue.

5. The command prompt window opens and is on stand-by.

6. From Windows explorer browser, select a folder for the repository projects storage.
You can use this folder as a storage folder for all the repository projects.

Important: Once the link between the project and the repository is broken, all items are displayed as in
conflict. At the end of the conversion process, the project that was used is linked to the newly
created repository. If you change the name of the repository folder, or the location of the
repository, the link is broken. Next time that the project is linked to the same repository, there will
be a conflict on all data items.

At the end of the conversion, the outputLog.htm pops-up with the default Internet browser. It is
created in a folder named with the current date and time. This new file contains the conversion
status of each project listed in the CSV file and all items names that could not be converted.

Schlumberger Private – Customer Use

Note: It is assumed that Techlog is already installed.

1. Open a Windows command prompt.

2. Go to the Repository Converter tool using “cd” command.
Example: “cd C:\Program Files\Schlumberger\Techlog xxxx.x\RepositoryConverter”.
3. Run the RepositoryConverter.bat with 2 arguments:
 First argument is the project to convert
 Second argument is the destination repository folder
Example:
C:\**\RepositoryConverter>RepositoryConverter.bat “C:\Techlog-projects\MyProject1.tlp”
“C:\RepositoryProjects”.
This example converts the Techlog project MyProject1 located in the folder:
“C:\Techlog-projects”.
The repository is created into the subfolder MyProject1 located in the folder
“C:\RepositoryProjects”.
You have two more options to add:
3rd argument: “Path to the report folder”. If it is not defined, report folder is the location of the
RepositoryConverter.bat
4th argument: -silent. This is to operate in silent mode, meaning no output.log will pop-up.
Example:
C:\**\RepositoryConverter\RepositoryConverter.bat “C:\Techlog-projects\MyProject1.tlp”
“C:\RepositoryProjects” “D:\Report” -silent

Note: The RepositoryProjects must exist before you run the converter. The double quotes are
mandatory for a path containing a space such as "C:\Techlogprojects\My Project 1.tlp".

Schlumberger Private – Customer Use

The project conversion with the Synchronization tool is performed by sending data from a local
project or a newly created repository. This is a fast solution and there are no data integrity
verifications on it.

1. Create on your network drive a repository folder which is accessible to all users.
2. Check that no other user is connected to this project.
3. Open the project with Techlog.
The project that was previously “multi-user” is opened in a “single-user” mode.
4. Go to the Utility tab > Synchronization group and select Synchronization tool.

5. Synchronization tool saves your current project when it starts. If you can save the project and
open the Synchronization tool, click Yes.

6. In the Synchronization tool window, click Link and browse to the repository folder where the
repository project is created and stored.

You select an empty folder to set as repository.

Schlumberger Private – Customer Use

A Warning pop-up window informs you that the local project is not empty.

7. Techlog requests if you want to become a Data Admin. If you click Yes, Techlog creates the
RrtConfig.xml file under data 2018, then Settings folder in the Repository.

8. Select all the objects in your local project (selecting the “Content” automatically selects all
the data items).
9. Click the arrow to start the data transfer.

Schlumberger Private – Customer Use

The following outputs are provided:
Log – outputLog.htm.
It is created in a folder named with the current date and time. This new file contains
the conversion status of each project listed in the CSV file and all item names that could not be
converted.
Note: Your Repository is in read-only mode, the script cannot operate properly. Check the
following behavior whatever the output displays:
Repository is Read-Only
Repository is not created but the Output files are. The ConversionLog.html is empty. Go to your
Repository and give the appropriate permission.

Schlumberger Private – Customer Use

Access the repository project only with Techlog.
The w\1 d\2 item contains characters forbidden in common operating systems (“\” and “/”) and it
must be renamed before being sent to the repository.

 Do not modify any file stored on the file system without Techlog
 Once a collaborative project was created, do not re-use the original project

Schlumberger Private – Customer Use

Error message:
The item WellName DatasetName must be renamed before sending to the repository as it
contains characters that are forbidden by the common operating systems ('\' , '/' )
Workaround:
Techlog supports “/” “\” for the datasets name since 2014. However, these characters are not valid
in Repository due to Operation System’s limitation. You need to update the name in advance.

Error message:
RRT config : the name of the item ‘xxx ‘ (type ‘PythonScript’) is not valid
Workaround:
The Python script name contains space at the end of the name, for example, ‘script1 .py’. This is
no longer valid since Techlog 2014. To avoid this message, go back to Techlog 2013.x, change
the script name so that it does not contain spaces at the end of the name, send them to the
Repository. If you are a Data Admin or contact your Data Admin, delete the existing script with
invalid name.

Error message
<No error message>
Workaround:
Techlog 2018.x allows the user to create a well without a dataset. However, the mechanism of
Repository keeps Well information in each dataset, and the well without dataset cannot be seen in
the Synchronization tool or sent to Repository. To send the well, make sure that you have a
dataset under the well.

Error message
<No error message>
Workaround:
Due to XML file export limitation, the variable name length should be up to 99 characters. If you
send/retrieve the variable with the longer name than 99 characters, the value will be missing.
To detect the variable name with 100+ characters:

Schlumberger Private – Customer Use

1. Go to TechData+ > Data harmonization > Query list tool.

2. For Query list tool, set the Regular expressions type as complex (UNIX/Perl) in Properties.

3. Set the Object type: Variable name, type .{100,} for Name: and hit Find.
The variable with 100+ characters will be listed in the tool.
4. Rename the variable to shorten the name.

Schlumberger Private – Customer Use

 Changing the Reference repository of an existing project is not recommended and causes the
loss of the link between the local project and the Reference repository. We recommend that you
create a new project to link to a different repository.

Important: Linking a project to a different repository results in loss of repository state information. Even if
items are identical, or if the project is linked again to the same repository, all the items are in
conflict and you need to solve them.

1. Click the Project tab, select Options.

2. Go to Parameters.
3. Click Advanced.
4. Click Unlink the current project from its shared repository
The Confirm unlink window opens.
5. Click Yes to confirm.
6. Click OK on both windows to validate.

Note: The Unlink the current project from its shared repository option is only displayedwhen
your current project is linked to a shared repository or a Studio repository (refer to Set up
Collaboration Environment section available in Techlog online help).

Schlumberger Private – Customer Use

You can use the existing repository created by previous Techlog versions. However, several
structural changes have been made in the newer version and the repository needs to be
upgraded. Details of the changes are as follows:

Changes starting from Techlog 2014 compared to previous versions and applied with Techlog
2018:
 The folder structure in a repository used by Techlog 2018.2 is updated for item type
“LayoutTemplate” and “WorkflowTemplate”.
 The item type “Mineral Inversion”, “LogPetro”, “External File”, “Well Groups” are legacy
objects and no longer supported by Techlog 2018.2. Those objects need to be moved
specifically.
Changes starting from Techlog 2018 compared to previous versions: the data folder structure is
under a folder named data2018.

Schlumberger Private – Customer Use

 The Repository upgrade is integrated into the Synchronization tool of Techlog 2018. It enables to
upgrade Repositories of any older versions to the 2018 format.
A backup of the repository is made as part of the upgrade process and will need to be manually
deleted when it becomes unnecessary.
The Synchronization tool allows the upgrade of the repository when you open it from a project
already connected to an older version or when you try to link to a Repository of an older version.
The Repository upgrade can be done only by a user registered as SuperUser in RrtConfig.xml file
of the Repository. Users not registered as a SuperUser will get an error message when they will
try to access the Repository and they will be prevented to connect.
The upgrade process performs the following changes:

 Moves all the items folders to data2018 folder.

 Saves a backup of the initial Repository with the name <RepositoryName>_backup_yyyy-
mm-dd hh-mm-ss.
 In the event of a Repository version older than 2014, it will move the item type
“LayoutTemplate” to LayoutTemplate folder and “WorkflowTemplate” to QuantiTemplate
folder.
 In the event of a Repository version older than 2014, it will move the item type
“MineralInversion”, “LogPetro”, “External File”, and “Well Groups” to a
LegacyObject_[Date][Time] folder.

Note: Techlog 2018 does not support the repository accessed by previous Techlog versions and
Techlog 2018 at the same time. Once you have upgraded the Repository, all the Techlog projects
accessing to the Repository should be in 2018.

How to upgrade a repository:

From a new Techlog project:

1. Go to the Utility tab > Synchronization tool and open the Synchronization tool.
2. Link to the repository in the old version.
3. Accept to upgrade the repository by clicking OK.
4. The repository is upgraded to 2018 format and a backup of the previous repository is kept
with the name <RepositoryName>_backup_yyyy-mm-dd hh-mm-ss

From an existing project:

1. Open the Techlog project in 2018, upgrade the project if necessary.
2. Go to the Utility tab > Synchronization tool and open the Synchronization tool.
3. Accept to upgrade the repository by clicking OK.

Schlumberger Private – Customer Use

 The Repository is upgraded to 2018 format and a backup of the previous repository is kept
with the name <RepositoryName>_backup_yyyy-mm-dd hh-mm-ss

Important: Before running the upgrade, make sure that:

 You have permission of full control on the Repository from Windows security setting on the
folder and folder or files under it.
 The location of the Repository has enough free space to contain the backup of the Repository
that will be built during the upgrade process.

After the upgrade, all users can connect to the 2018 Repository. The backup of the repository can be deleted if not
required anymore.
Upgrade success is reported in the output window. In any case of error, the upgrade is roll backed to its initial state.

Some Techlog versions were used to create the Repositories with a Repository.IdentityFile as read-only.
An error message pops up.
To solve the limitation:
1. Go to the Repository location, right-click on the Repository.IdentityFile and click Properties.
2. Unselect the read-only checkbox and then click OK.

Schlumberger Private – Customer Use

The conversion time might vary with the project size. After all conversions are performed, the
report automatically opens. You can see the following outputs:
 STATUS: PARTIALLY OK
XX items were not exported due to:
 Without child. Dataset is not converted.
 Not square. Dataset is not converted.
 Missing tldata. Dataset is not converted.
 Unknown reason.
Other information: there are some variables with missing headers: Type 2 inconsistencies
were detected.
 STATUS: CANCELLED
 Database integrity issues were detected. Type 3 inconsistencies were detected.
 Contact your local support for assistance. A project assistance must be run.
 STATUS: OK
Other information: there are some variables with missing headers. Type 2 inconsistencies
were detected.

Schlumberger Private – Customer Use

 The Data administrator can access the following additional functionalities by configuring a specific
text file:
Remove the lock of other users
Delete permanently Reference repository objects from the bin
Define specific datasets as read-only
Define specific datasets to be automatically retrieved
The procedure is as follows:
1. Create a Settings folder in the folder data 2018 of the Repository project folder.
2. Copy the RrtConfig.xml example file stored in the Techlog install > SynchronizationTool folder
in the Repository project > data 2018 > Settings folder.
3. Update the RrtConfig.xml file with the specific settings for this Repository project.
4. The update settings will be effective when the Synchronization tool is reopened.

Note: An example of RrtConfig.xml file is available under Install folder > SynchronizationTool folder.

It can be retrieved from the repository to the local project but cannot be sent from the local project
to the shared repository. They are displayed as grayed out.

Note: The Data administrator (Super User of the configuration file) can send and overwrite
read-only datasets.

Automatically retrieved regardless of which data is selected from the specific well (for example,
you can configure the Index dataset to be retrieved automatically when users transfer other data
logs, zones etc.).
Displayed in italic.
You can see from the following example that:
Index dataset is defined both in read-only and automatic retrieve
Zonation is set as automatic retrieve
Survey is read-only

Schlumberger Private – Customer Use

Note: From Techlog2014.2, SuperUser name is case insensitive.

Schlumberger Private – Customer Use