Schlumberger-Private

Copyright © 2020 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
Schlumberger-Private
 Techlog 2020.1 Synchronization Tool supports the Techlog model 2020.1 updates.
This version of Synchronization Tool maintains the functionalities covered by the previous Techlog
versions i.e. Send and Retrieve, Compare, Delete and Restore, Lock and Unlock, Refresh as well
as Data Admin workflow.

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

Schlumberger Public Synchronization Tool Deployment Guide Page 4 / 17

 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 2020.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 Public Synchronization Tool Deployment Guide Page 5 / 17

 1. Browse to the following folder: C:\Program Files\Schlumberger\Techlog 2020.1
\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 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 which could not be converted.

Schlumberger Public Synchronization Tool Deployment Guide Page 6 / 17

 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 Public Synchronization Tool Deployment Guide Page 7 / 17

 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 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.

Schlumberger Public Synchronization Tool Deployment Guide Page 8 / 17

 You select an empty folder to set as repository.

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
RrtConfig.xml file under data2016, 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 Public Synchronization Tool Deployment Guide Page 9 / 17

 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 read-only mode, the script cannot operate properly. Check the following
behavior no matter what 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 correct permission.

Schlumberger Public Synchronization Tool Deployment Guide Page 10 / 17

 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 Public Synchronization Tool Deployment Guide Page 11 / 17

 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 2020.x supports “/” “\” for the datasets name. However, these characters are not valid in
Repository due to Operation System’s limitation. You need to update the name in advance.

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

Error message
<No error message>
Workaround:
Due to XML file export limitation, 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:
1. Go to TechData+ > Data harmonization > Query list tool.

Schlumberger Public Synchronization Tool Deployment Guide Page 12 / 17

 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 Public Synchronization Tool Deployment Guide Page 13 / 17

 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 only appears when your
current project is linked to a shared repository or a Studio repository (see the page Set up
Collaboration Environment from Studio topic of the User Guide for more information).

Schlumberger Public Synchronization Tool Deployment Guide Page 14 / 17

Schlumberger Public Synchronization Tool Deployment Guide Page 15 / 17
 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 2016 of the Repository project folder.
2. Copy the RrtConfig.xml example file stored in the Techlog install > SynchronizationTool folder
in the Repository project > data 2016 > 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.

Can be retrieved from the repository to the local project but cannot be sent from the local project to
the shared repository
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 style.
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 Public Synchronization Tool Deployment Guide Page 16 / 17

 Note: SuperUser name is case insensitive.

Schlumberger Public Synchronization Tool Deployment Guide Page 17 / 17