Book Image

Operator Training Simulator Handbook

By : Joseph Philip
Book Image

Operator Training Simulator Handbook

By: Joseph Philip

Overview of this book

Operator training simulators in the process industry have been around since the 1970s, but you may not find a book that documents the development of these systems and the standard best practices. The Operator Training Simulator Handbook covers best practices for OTS engineering and OTS training development and delivery, starting from the basic the jargon and the different types of OTS systems. It will take you through the best approaches to project specification as well as building, maintenance, planning, and delivering these systems by sharing real-life experiences and dos and don’ts. As you advance, you'll uncover the various challenges in the planning and delivery of operator training models and understand how to address those by working through real-world projects. This book helps in specifying the best fit for purpose, choosing a cost-effective system when acquiring an OTS. You'll also learn how you can turn your OTS projects into digital twins before finally learning all about documentation in a typical OTS project, covering the sample structure that you can use as a starting point in your projects. By the end of the book, you'll have learned best practices for developing operator training simulator systems and have a reference guide to overcome common challenges.
Table of Contents (11 chapters)
Section 1: Introduction, Definitions, and Classifications
Section 2: Best Practices for the Development of OTS Systems
Section 3: OTS' Future, Training Model, and Reference Documents

SAT document template

SAT in this example, is a travel-well test only. The software would have been tested in the FAT. Hardware visual testing is done in the SAT.


A brief introduction to the SAT will be required, with typical subsections including the following:

  • Purpose
  • Scope
  • Holds
  • Abbreviations

The purpose of this section is to list what needs to be achieved by the end of this test. We did say that in this example, we will use this test as a travel-well test. The document scope should list what needs to be tested/checked in this test.


Typical subsections here include the following:

  • SAT location
  • Responsibilities
  • Nominated persons
  • Agenda

The test location is usually the final location for the system at the end users' premises. Every participant in the test needs to be assigned a responsibility that is clearly stated in this section. All participant contact information should be noted here...