EDM™ AutoSync Server Software Version...

EDM™ AutoSync Server Software Version 5000.1.10.2

Release Notes

What’s In This Release .............................................................................................. 2

Introduction ................................................................................................................ 3

System Requirements ............................................................................................... 9

Third Party Applications ........................................................................................... 11

International Trade Compliance ............................................................................... 12

Installation .................................................................................................................. 14

Enhancements and New Functionality .................................................................... 15

Integration with AutoSync Client ............................................................................. 18

Integration with ZetaAnalytics™ .............................................................................. 19

Integration with OpenWells® Mobile for Workovers .............................................. 20

Fixed Issues ............................................................................................................... 21

Known Issues ............................................................................................................. 25

Contacting Landmark Customer Support ............................................................... 27

5000.1.10.2 Page 1 of 31 July 2013

EDM™ AutoSync Server Software Release Notes

What’s In This ReleaseEDM™ AutoSync Server software is an application that supports database synchronization of versions 2003.16.1.15 and higher, and 5000.1.0 and higher of the shared EDM™ data model. AutoSync is also used to synchronize high frequency high volume data from WITSML servers to a qualified data warehouse.

New functionality and enhancements for the EDM AutoSync Server 5000.1.10.2 release:

• Support for ZetaAnalytics™ WITSML Server 5000.0.0

For details of EDM AutoSync Client and EDM AutoSync Server integration, see A Message from the Product Owner/Manager

To go directly to the enhancements and new features, integration with AutoSync Client, fixed issues, and known issues, click on the links below:

Enhancements and New Functionality

Integration with AutoSync Client

Fixed Issues

Known Issues

An Introduction to the AutoSync Server software Release and System Requirements are provided in this document.

For information on installation, setting up AutoSync users and policies see the EDM AutoSync Server 5000.1.10.2 Administrator Guide.

For installation requirements of EDM AutoSync Client see EDM AutoSync Client 5000.1.10.1 Administrator Guide.

For information on OpenWells Mobile see OpenWells Mobile for Workovers Administration Guide.

For general overview of using EDM AutoSync Client see EDM AutoSync Client Rig Supervisor Guide.

For general overview of high frequency high volume data transfer see ZetaAnalytics™ WITSML Server Software Version 5000.0.0 Installation Guide.

5000.1.10.2 Page 2 of 31 July 2013

EDM™AutoSync Server Software Release Notes

Go To “What’s in this Release?”

Introduction5000.1.10.2

This version supports ZetaAnalytics™ WITSML Server 5000.0.0

5000.1.10.1

This release supports OpenWells® Mobile for Workovers and the upgrade to Java 7 64-bit (Oracle notifies Java 6 end-of-life for November 2012)

5000.1.10

This release supports the shared EDM data model version 5000.1.10 and addresses customer and internal reported issues.

5000.1.9

This release of EDM AutoSync Server supports the EDM 5000.1.9 data model and fixes some customer reported issues.

5000.1.7

This release of EDM AutoSync Server continues to build on the solid functionality of bidirectional synchronization with support for EDM database version 5000.1.7. Functionality has been added in AutoSync Server to provide for email notification of events when used in conjunction with EDM AutoSync Client. Data errors or incomplete synchronizations can now be reviewed by the Office. Additionally, customer and internally reported issues have been resolved.

5000.1.6

A Message from the Product Owner/Manager

Hi and welcome to the 5000.1.6 Release of EDM AutoSync Server and EDM AutoSync Client. I am very excited about the new enhancements in this release. We understand the challenges you face as an EDM Administrator trying to maintain all of the disconnected databases you have on your rigs. It is difficult to keep them in sync utilizing the many rich customization options available to OpenWells and the rest of the EDT suite.

Deploying this release of server and client working in conjunction with each other, you as an Administrator can use the AutoSync Server software to check out the latest reference data from the production database. Complete your picklist, data dictionary, output report, layouts, etc… in your local sandbox. Next, the changes can be fully tested in the affected EDT software applications. Then, check the changed data back in to the main production database via the AutoSync Client software.

5000.1.10.2 Page 3 of 31 July 2013



Then, the next time your rig supervisor connects to send in his well data updates for the day, the EDM AutoSync Server with which he connects will automatically send all of the updates you have made. As an EDM Administrator you also have the option of making the updates directly on the production database. So whichever way you work, you can rest assured that when your changes are in the production database, your rigs will soon be up to date without you having to manually update them either at the site, remotely, or by sending a package to the rig supervisor and asking him to manually do it. I feel that this feature is going to save you, my clients, many hours of work and much effort in trying to manage this logistical challenge.

As an EDM Administrator there are special privileges which you may grant yourself through the EDM Administration Utility token system to allow you and others you designate to check in picklist and configuration changes. All others (i.e. the typical rig users) will only be getting these updates pushed to them without the ability to push any picklist or system configuration changes back in. If you wish the rigs to be able to contribute to picklist content, you can set the tokens individually or at an EDM group level for a group of users to control what changes you want to accept into your production system. The workflow is up to you, each of my clients. The technology is there to support you.

In addition to being able to manage the picklist and system configuration data to your rigs seamlessly, this version of EDM AutoSync Server and EDM AutoSync Client employs a stronger level of point to point security, using https protocol and digital certificates for secure socket connections. The data is also compressed on the EDM AutoSync Client side while the data is secured by the protocol. Finally, some low level architecture changes should prove that the actual data transfer is faster between points than ever before.

I am very excited to offer these great new features to you and trust that in utilizing these new tools you will continue to derive greater and greater value from the Landmark EDT solution as a whole.

5000.1.5

Welcome to EDM™ AutoSync Server software. This software’s functionality greatly enhances the value of an EDM™ database, and the EDT™ applications used in a globally dispersed client environment. The primary focus of this updated EDM functionality is “Global Data Aggregation”. This term refers to an engine that allows an EDT suite client, with multiple EDM databases distributed in separate locations in one country or around the world, to automatically post all changes made to a central EDM repository or EDM data warehouse. A typical EDT client architecture consists of a large global Oracle database in a central Corporate location which handles management reporting or global benchmarking. Company-wide dashboards, or automated executive updates and iWellFile™ software, may run against this database to help facilitate data harvesting. Within the Regional locations, SQL Server or Oracle databases host the wells operated by the region, and the daily updates from rigs it manages. Prior to AutoSync Server software, the ability to “publish” all of the changes in those databases to a centralized corporate data store was not fully automated.

5000.1.10.2 Page 4 of 31 July 2013



Connections to multiple Regional instances of AutoSync Server software are easily configured, and include settings such as controlling the frequency of data transfer events into the Corporate instance. Each connected Regional instance can also set multiple time periods during the day when data changes are not published to the Corporate datastore. This suspension of synchronization allows time to review daily reports, or accommodates scheduled database backups.

With no human intervention, databases literally stay in nearly real-time sync while transferring updates as often as once every ten seconds. Whether the data is imported, sent from a rig, or changed manually by an office engineer, changes are automatically pushed to the Corporate warehouse. AutoSync Server software follows the same logical model inherent to EDT applications for managing updates. For example, if a survey is updated in COMPASS™ software, that survey and its stations are communicated in a tiny update to the Corporate instance of AutoSync Server, which writes the change into its database. Likewise, if a casing report is created or edited within OpenWells® software, that report and wellbore assembly are pushed to the Corporate instance. Or, if a BHA is deleted from an existing report from within OpenWells software, the “delete” is pushed to the Corporate datastore as a report update.

Deletes have a higher level of control by the Corporate datastore. AutoSync Administrators can designate which types of object deletes 1) push through without any action, 2) push through but are backed up, and 3) which ones are simply not allowed.

Email notifications can be set up for deletions of any type of object. For instance, if a Regional database user mistakenly deletes an entire site, this deletion is disallowed, and an EDM Administrator can choose to receive an email about the original user’s attempted action. The system also allows for objects to be restored from “backup” if they were deleted and that was not the correct action. If a user in the Regional database mistakenly deletes an event from within a Well, and that action was allowed, the Corporate EDM Administrator can use the AutoSync Server software interface to restore the event and all of its children reports. To restore the data, the Administrator could then export it via one of the EDT applications to make it available again in the Regional database.

Logging and auditing are robust features within AutoSync Server software. The EDM Administrator can query the database and the file system to track all insert, update, or delete events in their database on a given object from its Regional equivalent. For the IT staff and network administrators, AutoSync Server software allows the Administrator to control the refresh rate and network throughput to help control network traffic. The architecture will minimize the network packet size because only the small logical changes are written across the network, not the entire event or Wellbore for instance.

The AutoSync Server logical model reflects the way people update data within their EDT applications. With this release, all common data, and all data exposed through OpenWells and COMPASS software, is synchronized. Data synchronization eliminates wasted time that users spent in the past to keep the Corporate datastore current (e.g. manually updating databases, or calling someone to inform them of a delete they performed within their Regional database).

5000.1.10.2 Page 5 of 31 July 2013



Some “Corporate” standard data is designed to be pushed out to Regional databases. The new AutoSync Server software system currently publishes all Corporate Lithologies and Catalogs into the Regional databases. This functionality is enabled when the Regional AutoSync Server instance “subscribes” to the Corporate AutoSync Server instance through a connection.

AutoSync Server software is extremely robust and secure. The system will retry repeatedly to overcome synchronization failures until the data is moved, while sending notifications via email about the failure condition. If the database becomes unavailable, the system automatically restarts synchronization when the database becomes available again. If a large synchronization is interrupted, AutoSync Server software restarts synchronization where it left off, and continues. The AutoSync Server web interface is EDM security enabled so that only authorized users can log into the system. Additionally, database connections between two AutoSync Server instances are secured by EDM authentication, and by security tokens to ensure no unauthorized process can request information from an AutoSync Server.

EDM AutoSync software Administrators are kept informed of system activity. Additions of objects, deletions of objects, and failures can be defined as EDM AutoSync events and directed to an email account. Also a complete change history is kept within the EDM database; and tables can be queried via the Data Analyzer™ application.

This AutoSync Server software delivers great value to existing EDT software global deployments. It also lays the foundational framework for future enhancements, which will allow more robust workflows that extend the reach of AutoSync software to a broader federation of databases.

Integration with AutoSync Client

AutoSync Client is focused on providing bi-directional updates between Rig and Regional EDM databases. By ensuring the data from the Rig is updating the Regional database, these changes are then automatically pushed to the Corporate database by AutoSync Server.

AutoSync Server addresses the problem of discrepancies in data updates between the Rig and the Regional Office and determines whose data to keep by way of policies set at the Regional level. These policies are configurable by EDM Administrators to conform to company policies. Several policy templates are provided as starting points; configurations may be saved and imported to apply to new Rig connections.

The synchronization process is truely bi-directional in that the Regional office can send any changes to wells under AutoSync control to the Rig upon synchronization. Only data that is changed is transmitted. Additionally, Rigs may choose to accept Read Only Control to be kept aware of changes to a well at the Regional level.

Regional offices updated with OpenWells 5000.1.5 can make direct well assignments to the AutoSync Client user. Otherwise, the EDM Administrator can assign permissions to an AutoSync

5000.1.10.2 Page 6 of 31 July 2013



Client user to browse the connected database and select wells to be placed under AutoSync Control.

For installation and integration procedures for AutoSync Client, see AutoSync Client 5000.1.7 Release Notes.

Overview of System Architecture

The initial release of AutoSync allowed you to synchronize multiple remote Regional EDM databases with one instance (e.g. Head Office database) for COMPASS and OpenWells data. This release of EDM AutoSync Server extends the synchronization of remote Rig EDM databases with a selected EDM Regional database.

In order to synchronize data between EDM databases, AutoSync Server software should be installed on a machine in the location where the Regional database resides.

The system architecture, and how data flows between synchronized databases, is shown in the example below. Notice that all data flows from the Rig databases to Regional Offices and then to the Corporate office. The Corporate office can publish selected data to the Regional EDM databases. The flow of data between the Rig and the Regional database is bi-directional.

EDM AutoSync Server and Client

5000.1.10.2 Page 7 of 31 July 2013



Service-oriented Architecture (SOA)

EDM AutoSync Server software is built upon a Service-oriented architecture (SOA), which is a collection of services that communicate with each other, for the purpose of establishing a federated database system.

The SOA architecture does not rely on the operating system and/or application resources. Since EDM AutoSync Server software is based on a service-oriented architecture, the impact to the existing EDT installation is minimal.

EDM AutoSync Server software uses a Windows Service to manage the business processes needed for remote EDM data transfers to an EDM database at the Head Office. EDM AutoSync’s SOA, represented in the graphic below, shows the coupling of services that form the basic architecture of the application.

5000.1.10.2 Page 8 of 31 July 2013



System RequirementsAutoSync Server software is installed on a machine running Windows® 2008 Server.

Install all Critical and Recommended Windows Updates before installing AutoSync Server software.

Platform Requirements

Platform requirements for AutoSync Server software on Microsoft 2008 R2 Server

Space Requirements

The table below shows the minimum disk space requirements for the EDM AutoSync Server 5000.1.10 installation..

Recommended for Windows 2008 Server, 64-Bit Platform

Minimum for Windows 2008 Server, 64-Bit Platform

• Windows® 2008 Server, SP1, 64-Bit • Windows® 2008 Server, SP1, 64-Bit

• 2 GHz or higher • 1.5 GHz processor

• 8 GB RAM or greater • 4 GB RAM

• VGA Color Monitor • VGA Color Monitor

• 106-key Windows-ready integrated keyboard • 106-key Windows-ready integrated keyboard

• MS-compatible mouse or pointing device • MS-compatible mouse or pointing device

• TCP/IP based network connection 100 Mbps • TCP/IP based network connection 10 Mbps

• 20 - 40 GB or better free disk space • 20 - 40 GB or better free disk space

• CD-ROM drive (not required if installing from a network location)

• CD-ROM drive (not required if installing from a network location)

Application Approximate Disk Space Needed to Install

EDM AutoSync 1 GB

5000.1.10.2 Page 9 of 31 July 2013



Screen Resolutions/Video

If you experience display problems when running AutoSync Server software, upgrade your video driver to the latest version.

Recommended Minimum

• 1024 x 768 or higher • 1024 x 768

5000.1.10.2 Page 10 of 31 July 2013



Third Party ApplicationsLandmark uses various third-party applications in the development of its software.

Landmark acknowledges that certain third party code has been bundled with, or embedded in, Landmark’s software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following location:

\Third_Party.pdf.

The following table describes the third party applications in EDM AutoSync Server 5000.1.10.2

.

Product/Package Version

Apache® Tomcat Server Tomcat version 6.0.33 64-bit

Apache® Axis2 Apache license, version 2

Java SE Runtime Environment Sun MicroSystems jdk1.7.0_03 x64

Hibernate Hibernate version 3.2.6

SourceForge.Net JTDS 1.0

Echo+ExtraNG+EchoExtra Echo version 2.2

Oracle® Database Drivers Oracle 11g Driver version 11.1.06.0

5000.1.10.2 Page 11 of 31 July 2013



International Trade ComplianceThis application is manufactured or designed using U.S. origin technology and is therefore subject to the export control laws of the United States. Any use or further disposition of such items is subject to U.S. law. Exports from the United States and any re-export thereafter may require a formal export license authorization from the government. If there are doubts about the requirements of the applicable law, it is recommended that the buyer obtain qualified legal advice. These items cannot be used in the design, production, use, or storage of chemical, biological, or nuclear weapons, or missiles of any kind.

The ECCNs provided in Release Notes represent Landmark Graphics' opinion of the correct classification for the product today (based on the original software and/or original hardware). Classifications are subject to change. If you have any questions or need assistance please contact us at mailto:[email protected]

Under the U.S. Export Administration Regulations (EAR), the U.S. Government assigns your organization or client, as exporter/importer of record, responsibility for determining the correct authorization for the item at the time of export/import. Restrictions may apply to shipments based on the products, the customer, or the country of destination, and an export license may be required by the Department of Commerce prior to shipment. The U.S. Bureau of Industry and Security provides a website to assist you with determining the need for a license and with information regarding where to obtain help.

The URL is: http://www.bis.doc.gov

5000.1.10.2 Page 12 of 31 July 2013

[email protected]@halliburton.comhttp://www.bis.doc.gov



Definitions

CCATS (Commodity Classification Automated Tracking System) - the tracking number assigned by the U.S. Bureau of Industry and Security (BIS) to products formally reviewed and classified by the government. The CCATS provides information concerning export/re-export authorizations, available exceptions, and conditions.

ECCN - Export Control Classification Number - The ECCN is an alpha-numeric code, e.g., 3A001, that describes a particular item or type of item, and shows the controls placed on that item. The CCL (Commerce Control List) is divided into ten broad categories, and each category is further subdivided into five product groups.

The CCL is available on the EAR Website at http://www.access.gpo.gov/bis/ear/ear_data.html#ccl

Product/Component/R5000 ECCN Number LicenseCCATS Number

Last Date Updated

EDM AutoSync Server 5D002 G066893 05/12/2010

5000.1.10.2 Page 13 of 31 July 2013

http://www.access.gpo.gov/bis/ear/ear_data.html#ccl



InstallationRefer to the “Installation” section of the EDM AutoSync Server Software 5000.1.10.2 Administrator Guide.

5000.1.10.2 Page 14 of 31 July 2013



Enhancements and New FunctionalityThe EDM AutoSync Server enhancements and new features for releases 5000.1.0 through 5000.1. 10.2 are described below:

5000.1.10.2

This release of AutoSync supports the implementation of the ZetaAnalytics™ WITSML Server 5000.0.0 to facilitate the movement of high frequency high volume data from a WITSML server to a qualified data warehouse.

5000.1.10.1

This release supports OpenWells® Mobile for Workovers. Data entry for Workovers can be performed in a connected or disconnected environment directly to an iPad®. Integration with AutoSync Server allows for synchronization with the Corporate/Regional EDM database once back in range of the network.

5000.1.10

This release of EDM AutoSync Server provide support for the EDM database version 5000.1.10.

5000.1.9

This release of EDM AutoSync Server provides support for EDM database version 5000.1.9.

5000.1.7.2

This release supports EDM 5000.1.7.1 data model and customer and internally reported issues.

5000.1.7

This release of EDM AutoSync Server provides support for EDM database version 5000.1.7. Functionality has been added in AutoSync Server to provide for email notification of events when used in conjunction with EDM AutoSync Client. Data errors or incomplete synchronizations can now be reviewed by the Office in a timely fashion.

Additionally, customer and internally reported issues have been resolved.

5000.1.6

This release supports new administrative functionality where EDM Administrators may make configuration and picklist changes via the EDM Administration Utility or directly in a local database and publish the changes to the connected Regional EDM database via AutoSync Server. These changes will be pushed to local Rig/Field AutoSync Clients at the next synchronization for well data.

5000.1.10.2 Page 15 of 31 July 2013



EDM AutoSync Server and EDM AutoSync Client employ a stronger level of point to point security, using https protocol and digital certificates for secure socket connections. The data is also compressed on theEDM AutoSync Client side while the data is secured by the protocol.

5000.1.5

The EDM AutoSync Server software release supports automated data replication (synchronization) of EDM databases for Landmark’s COMPASS™ and OpenWells® software products. Any data changes made to remote/regional databases are replicated and seen almost immediately in the local/corporate database. For example, new reports (or changes to existing reports) uploaded from Rig to Regional office can be available to the corporate office in a matter of seconds.

With the installation of AutoSync Client software, changes from the Rig to Regional EDM databases can be managed bi-directionally.

• Integration with EDM AutoSync Client - see Integration with AutoSync Client

• Integrated with EDM security through the “AutoSync.start” and “AutoSync.remoteConnect” application tokens added to the EDM database security model

• Implementation and management of policies to control updating and overwriting of data between Rig and Regional databases.

• In EDM AutoSync Server applications that are updated to OpenWells 5000.1.5, wells to place under AutoSync Control by an AutoSync Client user can be directly assigned in OpenWells.

• EDM Admins can assign tokens to allow AutoSync Client user to browse a connected database to select wells to place under AutoSync control.

• AutoSync Client users register with an EDM AutoSync Server in a simple log in procedure. Only one registration at a time is supported.

• Policy Template export and import for propogating configuration choices with another EDM AutoSync Server.

• Several policy choices shipped with the installation for multiple set ups based on company profiles

• Large International Multisite with much office engineer interaction in daily data needs

• Medium-sized independent with some regional imput

• Small independent where most all data is controlled by the rig

5000.1.0

5000.1.10.2 Page 16 of 31 July 2013



• Web-based Administrative graphical interface allows EDM AutoSync software to be configured in order to synchronize remote databases

• Streamlined and simplistic configuration of database connections with immediate synchronization after the connections are established

• Multi-type and version support for synchronization of EDM 2003.16.1.15 and higher, and 5000.1.0 and higher databases

• Built-in scheduling of synchronization suspension for scheduled database maintenance or events that require the database to be in steady state (e.g. generation and collation of Daily Reports) between the Regional and Corparate databases.

• Automatic identification of all new and newly modified data, with replication to another database as modular data objects, rather than moving entire objects (e.g. Well, Wellbore, Event, etc.)

• Robust data recovery mechanism that corrects synchronization errors created by interruptions caused by network failure or user intervention

• Behind the scenes “silent” synchronization of all data captured in Landmark's COMPASS and OpenWells software applications

• Simple slider type optimization controls that maximize synchronization efficiency

• SMTP email with configurable settings that support event notifications and data recovery actions

• Dynamic transparent auditing to help maintain data integrity and support data validation during synchronization

• Easily accessed debug logging of EDM AutoSync software and databases

• Flexible Synchronization Policy that helps prevent inadvertent data loss through email notification, delete control, and recovery mechanisms

• Quick restoration of data flagged by EDM AutoSync software for backup

5000.1.10.2 Page 17 of 31 July 2013



Integration with AutoSync ClientAutoSync Server supports the registration of remote AutoSync Client instances. A registered AutoSync Client may browse the database or download wells from a list. Wells may also be assigned to specific AutoSync Client instances using OpenWells® 5000.1.5. or later versions.

The EDM AutoSync Server web interface will allow the implementation of policies to control data updates and overwrites via templates that can be saved and applied to other connections. EDM lock policies work as normal unless the Rig policies are set to overwrite.

New with version 5000.1.7 is the ability to setup email notifications for events with EDM AutoSync Client as well as EDM AutoSync Server.

For installation and integration procedures for AutoSync Client, see EDM AutoSync Client 5000.1.10.1 Administrative Guide and EDM AutoSync Client 5000.1.10.1 Release Notes.

5000.1.10.2 Page 18 of 31 July 2013



Integration with ZetaAnalytics™See the EDM™ AutoSync Server Installation Guide for information in setting up AutoSync Server for use with ZetaAnalytics™.

5000.1.10.2 Page 19 of 31 July 2013



Integration with OpenWells® Mobile for WorkoversSee OpenWells Mobile for Workovers Administration Guide for information on setting up and using AutoSync Server with an iPad®.

5000.1.10.2 Page 20 of 31 July 2013



Fixed IssuesThe following issues fixed for versions 5000.1.5 through 5000.1.10.2 are described below:

Release 5000.1.10.2

Release 5000.1.10.1

Release 5000.1.10

Defect ID Description

903547 File system resource cache is not being managed leading to issues related to disk space

906514 AutoSync is deleting new reports when they are synchronized with the mobile interface

906523 AutoSync Server cannot generate PDF output reports for mobile service


835775 Polylines do not sync between Client and Server

859774 Cannot process large attachments/files


verified Support for EDM 5000.1.10 data model

864825 Pe-role config file missing from server in 5000.1.9.0

878994 AutoSync 5000.2.9.1 constraint for sync_resource_root needs to be altered

5000.1.10.2 Page 21 of 31 July 2013



Release 5000.1.9.1 Hotfix

Release 5000.1.9


871819 Solution required to increase speed of the Master Synchronization between client and server around configuration items.- “Users” seem particularly slow. This is a performance issue and will require a change. Changes made to the axis2.war file (replaced)


860820 Volume of contents in ‘work’ folder increases on each start up of AutoSync Server eventually leading to disk space issues

861838 Add support for expanded client customization capability tables.

Support for additional configuration items. Changes to config_mapping.xml and tablemapping.xml.

· MD_SYS_PICKLIST_SCRIPT

· MD_SYS_SCRIPT

· MD_SITE_CONFIG_FILES new `PLUG_INS type discriminator

856778 Child resources not synchronized as expected where one of the parent nodes has been deleted

861837 System Picklists and associated EDM meta data are not transferred by AutoSync

Verified Support for EDM 5000.1.9 data model

5000.1.10.2 Page 22 of 31 July 2013



Release 5000.1.7.2 Patch


841275 COMPASS recalculation on locked Survey / Design updates, after SAM notification, causes well to be listed under a permanenet warning condition

845938 Oracle NUMBER (10,1) data type fields with null values tranferred to the SQL Express as INT with 0 (zero) value

844707 'varchar' data type text fields in custom picklists are created on the Client side database without defining the collation.

843313 Output Report's using long file names (for RPT, XML….) cause error when corresponding record in MD_SITE_CONFIG_FILES is updated

836860 Spelling mistakes within AutoSync Client code

841302 Flushing of resource files from Publish cache causes AutoSync Server to fail to provide for those resources when requested.

847582 Add method to allow HEAD_OFFICE to request missing resource references from LOCAL_OFFICE

Verified Support for EDM 5000.1.7.1 Data Model

• "Changes to delta tables script to allow drop SYNC_table statements to work more efficiently and changes to SYNC_CHANGE_LOG

• "Changes to autosync.xml to weed out entries not specific to Client/Server [easier for support]

• "Changes to hibernate.cfg.xml to correct entries generating [non-critical] errors on start up [hibernate.byte.code.use_reflection_optimizer] -bytecode not cglib [org.hibernate.dialect.Oracle9iDialect] or [org.hibernate.dialect.Oracle10gDialect] - Oracle9Dialect redundant

5000.1.10.2 Page 23 of 31 July 2013



Release 5000.1.7

Release 5000.1.6

Release 5000.1.5


Verified Support for EDM 5000.1.7 data model

Integration with AutoSync Client for mail notifications of various events


833660 Handle blackout periods on remote connections with informational message in logs instead of current ERROR message

832061 Enhancement: EDM AutoSync Client - would like the ability to notify regional office if sync failure occurs

818472 International characters appear as “?” in synchronization dialogs

5000.1.10.2 Page 24 of 31 July 2013



Known IssuesThe following outstanding issues are known, but are not thought to prevent users from achieving efficiency gains provided by EDM AutoSync Server software. These issues will be addressed in future releases, together with any additional issues reported by our clients.

Caution: To avoid unintended transfers of WellPlan data such as fluids, definitive surveys and/or cases from Rig locations to regional offices there are three recommendations:

• Configure Conflict rules for the three datatypes to ensure the Regional Office always wins on a conflict.

• Configure rules for the three datatypes to respect Locking, and then use Design Locking in the Regional Office to protect well plan design data.

• Revoke the application tokens for COMPASS and the engineering applications (WellPlan, Casing String, Stress Check and WellCat) on the Rig assuming there is not intent for Rig users to perform workflows in these applications.

For details on User Permissions and Application Tokens see the EDM AutoSync Server Administration Guide and for information on Conflict Rules see the EDM AutoSync Client Administration Guide.

Using the above three layers of configuration should provide adequate protection to prevent the unintended transfer of design information from Rig Offices to Regional Offices.

Defect Id Defect Type Subject Version

817847 DEFC Client/Server search functionality can return wells from Server that are in projects or sites that the user does not have tight group access to even though they have access to the well tight group

5000.1.5

795120 DEFC Delete of DmReportJournal_Ddr also removes related DCDFluidT entry, but restore of DmReportJournal_Ddr does not put back the associated DCDFluidT entry

5000.1.0

803535 DEFC Separate log files for each remote connection

5000.1.0

5000.1.10.2 Page 25 of 31 July 2013



5000.1.10.2 Page 26 of 31 July 2013



Contacting Landmark Customer Support

Landmark software operates Technical Assistance Centers (TACs) in Australia, the United Kingdom, and the United States. Additional support is also provided through regional support offices around the world.

• Support Via Web Portal

• Technical Assistance Centers

• Regional Offices

• Helpful Links

Support Via Web Portal

Support information is always available on the Landmark Customer Support internet page. You can also submit a support request directly to Landmark Customer Support though the Landmark Customer Support Portal:

http://css.lgc.com/InfoCenter/index?page=home

To request support in the Landmark Customer Support Portal:

1. In the PIN and Password text boxes in the Please Sign In area, enter your registered personal identification number and password.

2. Click the Sign In button.

3. In the Case & Defect Information area, click the Create A New Case link.

4. In the Create Case area, fill in the necessary information. Provide details about your technical concern, including any error messages, the workflow steps where the problem occurred, and attachments of screen shots that display the problem. To help understand the concern, you can also attach other files too, such as example data files.

5. Click the Submit button. A support analyst in the nearest Technical Assistance Center will respond to your request.

5000.1.10.2 Page 27 of 31 July 2013

http://css.lgc.com/InfoCenter/index?page=home



Technical Assistance Centers

Regional Offices

For contact information for regional offices, see the Contact Support page located at:

http://css.lgc.com/InfoCenter/index?page=contact&section=contact

If problems cannot be resolved at the regional level, an escalation team is called to resolve your incidents quickly.

Helpful Links

Asia, Pacific8:00 am - 5:00 pm Local TimeMonday-Friday, excluding holidays

61-8-9481-4488 (Perth, Australia)Toll Free 1-800-448-488Fax: 61-8-9481-1580Email: [email protected]

Europe, Africa, Middle East9:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

44-1372-868686 (Leatherhead, UK)Fax: 44-1224-723260 (Aberdeen, UK)Fax: 44-1372-868601 (Leatherhead, UK)Email: [email protected]

Latin America (Spanish, Portuguese, English)7:00 am - 5:00 pm Local Time

713-839-3405 (Houston, TX, USA)Fax: 713-839-3646Email: [email protected]

North America7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

713-839-2200 (Houston, TX, USA)Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 713-839-2168Email: [email protected]

Name Website Address

Landmark Software & Services home page http://www.halliburton.com/landmark

Landmark Support Portal http://css.lgc.com/InfoCenter/index?page=home

5000.1.10.2 Page 28 of 31 July 2013

mailto:[email protected]:[email protected]:[email protected]:[email protected]://css.lgc.com/InfoCenter/index?page=contact&section=contacthttp://www.halliburton.com/landmarkhttp://css.lgc.com/InfoCenter/index?page=home



© 2013 HalliburtonAll Rights Reserved

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:

Halliburton | Landmark Software & Services2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA

P.O. Box 42806, Houston, Texas 77242, USAPhone:713-839-2000, FAX: 713-839-2015Internet: www.halliburton.com/landmark

Trademarks3D Drill View, 3D Drill View KM, 3D Surveillance, 3DFS, 3DView, Active Field Surveillance, Active Reservoir Surveillance, Adaptive Mesh Refining, ADC, Advanced Data Transfer, Analysis Model Layering, ARIES, ARIES DecisionSuite, Asset Data Mining, Asset Decision Solutions, Asset Development Center, Asset Development Centre, Asset Journal, Asset Performance, AssetConnect, AssetConnect Enterprise, AssetConnect Enterprise Express, AssetConnect Expert, AssetDirector, AssetJournal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, AssetOptimizer, AssetPlanner, AssetPredictor, AssetSolver, AssetSolver Online, AssetView, AssetView 2D, AssetView 3D, Barrier Assurance Monitoring, BLITZPAK, CartoSnap, CasingLife, CasingSeat, CDS Connect, CGMage Builder, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataServer, DataStar, DataVera, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace Atomic Meshing, DecisionSpace Base Module, DecisionSpace Desktop, DecisionSpace Geosciences, DecisionSpace GIS Module, DecisionSpace GRC Module, DecisionSpace Nexus, DecisionSpace Reservoir, DecisionSuite, Deeper Knowledge. Broader Understanding., Depth Team, Depth Team Explorer, Depth Team Express, Depth Team Extreme, Depth Team Interpreter, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery 3D, Discovery Asset, Discovery Framebuilder, Discovery PowerStation, Discovery Suite, DMS, Drillability Suite, Drilling Desktop, DrillModel, DrillNET, Drill-to-the-Earth-Model, Drillworks, Drillworks ConnectML, Drillworks Predict, DSS, Dynamic Frameworks to Fill, Dynamic Reservoir Management, Dynamic Surveillance System, EDM, EDM AutoSync, EDT, eLandmark, Engineer’s Data Model, Engineer’s Desktop, Engineer’s Link, ENGINEERING NOTES, eNotes, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, ezValidator, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, Frameworks to Fill, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, Geologic Interpretation Component, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97, GesFull, GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon Generation, I2 Enterprise, iDIMS, iEnergy, Infrastructure, iNotes, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software), Landmark Decision Center, LandNetX, Landscape, Large Model, Lattix, LeaseMap, Limits, LithoTect, LogEdit, LogM, LogPrep, MagicDesk, Make Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as a service), Nexus (as software), Nexus View, Object MP, OneCall, OpenBooks, OpenJournal, OpenLink, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server, OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, Operations Management Suite, PAL, Parallel-VIP, Parametric Modeling, Permedia, Petris WINDS Enterprise, PetrisWINDS, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PLOT EXPRESS, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, Power Interpretation, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production, Production Asset Manager, PROFILE, Project Administrator, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMax 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF, Quickwell, Quickwell+, Quiklog, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-time View, Recall, Reference Data Manager, Reservoir, Reservoir Framework Builder, RESev, ResMap, Resolve, RTOC, SCAN, SeisCube, SEISINFO, SeisMap, SeisMapX, Seismic Data Check, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio, SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, Smart Change, Smart Deploy, Smart Flow, Smart Skills, Smart Start, Smart Sustain, Smart Transform, Smart Vision, SmartFlow, smartSECTION, smartSTRAT, Spatializer, SpecDecomp, StrataMap, StrataModel, StratAmp, StrataSim, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SurfNet, SynTool, System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, T-Grid, The Engineer’s DeskTop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Trimmed Grid, Tubular Basic, Turbo Synthetics, Unconventional Essentials, VESPA, VESPA+, VIP, VIP-

5000.1.10.2 Page 29 of 31 July 2013



COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, vSpace, vSpace Blueprint, vSpace Onsite, WavX, Web Editor, Well H. Clean, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellSolver, WellXchange, WOW, Xsection, You’re in Control. Experience the difference., ZAP!, ZEH, ZEH Plot, ZetaAnalytics, Z-MAP, Z-MAP Plus, and ZPS are trademarks, registered trademarks, or service marks of Halliburton.

All other trademarks, service marks, and product or service names are the trademarks or names of their respective owners.

NoteThe information contained in this document is subject to change without notice and should not be construed as a commitment by Halliburton. Halliburton assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you.

5000.1.10.2 Page 30 of 31 July 2013



Third Party Licenses and AttributionsHalliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following location:

PathNameInInstallationDir/Third_Party.pdf

DisclaimerThe programs and documentation may provide links to external web sites and access to content, products, and services from third parties. Halliburton is not responsible for the availability of, or any content provided on, third party web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Halliburton is not responsible for: (a) the quality of third party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Halliburton is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

5000.1.10.2 Page 31 of 31 July 2013

What’s In This ReleaseIntroductionSystem RequirementsThird Party ApplicationsInternational Trade ComplianceInstallationEnhancements and New FunctionalityIntegration with AutoSync ClientIntegration with ZetaAnalytics™Integration with OpenWells® Mobile for WorkoversFixed IssuesKnown IssuesContacting Landmark Customer Support

Date post:	14-Feb-2021
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

EDM™ AutoSync Server Software Version...

Documents