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)
1
Section 1: Introduction, Definitions, and Classifications
3
Section 2: Best Practices for the Development of OTS Systems
6
Section 3: OTS' Future, Training Model, and Reference Documents

Examples of best use

In this section, we will show how best to use the OTS and make it a digital twin rather than a training tool only.

Project build

During the project build, the supplier will integrate the model into the recently FATed ICSS and will try to start the plant for the first time in a fully integrated system. This will be the best time to find engineering issues related to the following:

  • Control and safety systems.
  • Process systems.
  • Experience has shown that in all projects, the FATed ICSS will still have many bugs for many reasons.
  • Some control strategies can only be tested dynamically. An ICSS FAT usually uses static systems to test the controls.
  • Static testing is when signals are tied back, so a pump start command will be fed back as a pump running signal or done via an I/O that is operated by a testing engineer that will make the pump running status active when the pump command is issued. While this test is okay for a stand-alone pump,...