Terms & Conditions

Data Security

We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect.

All data is stored in secure electronic systems accessible only to Oasys staff with both valid network login credentials and specific authorisation to access the system.  Our systems further limit data access by role to ensure data is available only to those who have a specific need to see it.

If at any point you suspect or receive a suspicious communication from someone suggesting they work for Oasys or a website claiming to be affiliated with Oasys, please forward the communication to us or report the incident by email to [email protected] or in writing to Oasys, 8 Fitzroy Street, London, UK, W1T 4BJ as soon as possible.

Data Security Notice Updated 27th February 2020

top ]


 

Website Terms and Conditions

The contents of this web site are protected by copyright and other intellectual property rights under international conventions. No copying of any words, images, graphic representations or other information contained in this web site is permitted without the prior written permission of the webmaster for this site.

Oasys accepts no responsibility for the content of any external site that links to or from this site.

top ]

 


 

Software Licensing Terms

Terms and Conditions of Purchase

The full conditions of purchase and maintenance for all Oasys desktop software are set out in the Oasys Software Licence and Support Agreement.

The full conditions of purchase and maintenance for Oasys Gofer and Oasys Giraphe are set out in the Gofer SaaS Agreement  and the Giraphe SaaS agreement.

All prices are subject to TAX at the current rate.

Prices and specifications are subject to change without notice – please ask for a written quotation.

Although every care has been taken to ensure the accuracy of all information contained herein, the contents do not form or constitute a representation, warranty, or part of any contract.

Superseded Versions of Terms and Conditions

Oasys keeps copies of all superseded versions of its terms and conditions.

Maintenance & Support Services

Support and maintenance is included with all subscription licences for their full duration.

Annual maintenance contracts are available for software under a perpetual licence, prices are based on a percentage of the most recent list price.

This service includes:

 

top ]

 


 

Cookies Policies

View available cookies policies below:

 

top ]

 

Practical Applications of the COM Interface to Oasys Geotechnical Analysis

01/07/17 12:30

This webinar will introduce you to the COM (Component Object Model) interface within Geotechnical software.

Webinar host

Zeena is the Senior Geotechnical consultant and University Liaison Manager at Oasys. She has worked as a Geotechnical Engineer in Arup for a number of years and taken a number of academic roles such as reviewing the ICE Civil Engineering Proceedings. She is a regular presenter of Oasys webinars and speaker at numerous engineering exhibitions throughout the world.

About this webinar

This webinar teaches you how to create data objects that allow external programs to pass information and instructions to and from Oasys Geotechnical programs. This feature has already been used in research and it will speed up the analyses in your geotechnical projects.

As well as an introduction into how to access and apply the COM interface, two Arup engineers, Mark Skinner and Matthew Brown, demonstrated how they have applied the COM interface to their design analyses in Oasys software, Alp and Greta.

By the end of the webinar, you will:

• Understand what the COM interface means
• Be able to access and apply the COM interface in Frew, Alp and Greta
• Learn how the COM interface is being used by engineers to increase their efficiency

Newsletter Sign up

Please fill out your details below to receive the latest oasys news.

  • This field is for validation purposes and should be left unchanged.