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


In the FAT, the supplier will need to verify and show the contractor that they have built the system right.

In the FAT, the OTS supplier will need to show the contractor the following:

  • All model issues from the MAT have been addressed.
  • All the correct documentation has been used to build the OTS.
  • All the correct software versions have been used to build the OTS.
  • All the correct hardware has been used to build the OTS.
  • All the correct software licenses have been installed and are working on the OTS.
  • All the agreed ICs have been delivered and are working correctly on the OTS.
  • The system can perform the agreed process operations, and they are usually as follows:
    • Normal plant shutdown
    • Normal plant startup
  • Agreed model stress tests (such as emergency shutdown and 12-hour OTS runs).
  • Agreed instructor functionality checks.
  • Agreed contractor custom tests.

All the preceding points will need to be signed off by the contractor so the FAT...