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

Functional design specification

If the DDS is not in the scope, then the content of the DDS will need to be part of the FDS.

The FDS document is supposed to work as a V&V document to be used in the FAT to make sure the OTS has been built correctly and that it is the right system for the contractor.

Please refer to the FAT section of this chapter to see what we need to achieve in the witnessed test, and then we need to address all these points in the FDS document.

So, what needs to be in the FDS?

In the FDS, we need to clearly specify the OTS scope in terms of hardware, software versions, and licenses. We list all the documents used to build the OTS, including P&ID versions, datasheets, C&E versions, FATed ICSS version, and the date of issue. All the deliverables will need to be listed so that they can be checked during the FAT.

A sample of the FDS document content can be found in Chapter 6, OTS Sample Documentation.