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

The SOR

The SOR should be written when an OTS is needed. It should be given to the OTS supplier with clear statements that will help the supplier to come up with a clear technical offer and price for the OTS.

The SOR should define the scope of the OTS. The best way is to add the Piping and Instrumentation Diagrams (P&IDs) to the SOR so the OTS' scope is clear.

The SOR should include the scope of the control systems and the minimum hardware performance needed. The contractor should clearly state the KPIs that will make the project a success. This will help the supplier to come up with a solution that is fit for purpose.

What should be in the SOR, then? Please refer to Chapter 6, OTS Sample Documentation, to see an example of an SOR.