192 Yer Pe I35 0014

Yanbu Export Refinery Project
PROJECT DESIGN BASIS 198B.1 SPECIFICATIONS Project Specification for Operator Training Simulator (OTS) Document No.: 192-YER-PE-I35-0014 Revision No.: FF Issue Date: 07 May 2008
TABLE OF CONTENTS 1.0 2.0 2.1 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 4.0 4.1 4.2 5.0 5.1 5.2 6.0 6.1 6.2 6.3 6.4 PURPOSE................................................................................................................... 4 SCOPE........................................................................................................................ 4 General........................................................................................................................ 4 REFERENCE DOCUMENTS & STANDARDS ........................................................... 5 Conflicting and Deviations........................................................................................... 5 YERP Reference Documents...................................................................................... 5 Saudi Aramco Engineering Standards ........................................................................ 5 Project Specification and Drawings............................................................................. 6 American National Standards Institute (ANSI) / National Fire Protection Association (NFPA) ..................................................................................................... 6 International Organization For Standardization........................................................... 6 American Nuclear Society ........................................................................................... 7 DEFINITIONS & ABBREVIATIONS ............................................................................ 7 Definitions.................................................................................................................... 7 Abbreviations............................................................................................................. 10 PROJECT ADMINISTRATION.................................................................................. 11 Project Personnel ...................................................................................................... 11 Models and Scenarios............................................................................................... 11 PROJECT EXECUTION............................................................................................ 12 Fabrication................................................................................................................. 12 OTS Model Design Review and Testing ................................................................... 12 OTS Hardware and standard Software Design Review and Testing ........................ 13 Training ..................................................................................................................... 13
General Confidential Page 2 of 40

6.5 7.0 7.1 7.2 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9
Documentation .......................................................................................................... 14 SOFTWARE REQUIREMENTS ................................................................................ 15 Software Licensing .................................................................................................... 15 Hardware and Software............................................................................................. 15 FUNCTIONAL REQUIREMENTS ............................................................................. 16 General...................................................................................................................... 16 Dynamic Process Modeling Module .......................................................................... 17 Scenario Building Module.......................................................................................... 20 Instructor Module....................................................................................................... 24 Operator Training Module ......................................................................................... 27 Evaluation and Certification Module.......................................................................... 29 Graphical User Interface (GUI) Module..................................................................... 32 Integration Module..................................................................................................... 36 System ...................................................................................................................... 37
APPENDIX A: OTS SYSTEM ARCHITECTURE ........................................................................ 40

1.0
PURPOSE The purpose of this Functional Specification Document is to describe the minimum requirements for the design, materials, manufacture, supply and testing of Operator Training Simulator (OTS) to be installed, as part of the Process Automation System (PAS) for the Yanbu Export Refinery Project (YERP), Saudi Arabia. The Yanbu Export Refinery Project (YERP) is the development and installation of a new Grassroots full conversion refinery in the Kingdom of Saudi Arabia that will process Arabian Heavy crude into gasoline, diesel, and LPG products. As currently defined, the refinery will also modify existing terminal facilities for import of crude feed and export of products. The refinery will be located in Yanbu Industrial City on the west coast of Saudi Arabia on the Red Sea. The OTS will be used to train, certify, and re-certify operations personnel to proficiently operate the Yanbu Export Refinery Facilities. The Plant Overview, Process Description, Process Risk Area and Operating Philosophy shall be as specified in the 192-YER-PE-I35-0001 Main Automation Contractor (MAC) Scope Definition and 192-YER-PE-I35-0002 Project Specification for Process Automation System.
2.0 2.1
SCOPE General The OTS shall be used to enhance the skills and knowledge of the control room operators as well as to certify and re-certify these operators. The OTS and its components shall be approved by YERP PMT. The MAC shall demonstrate or provide a list of existing installations using the same OTS offering. The MAC shall provide the engineering, services, and other supplies necessary to fully satisfy the requirements defined in this specification and to provide a complete operational OTS system. This shall include but not be limited to: Development of a Detailed Design Specification for the system. Development, configuration, and testing of all modules of the OTS system. All documentation for OTS configuration, setup, use, maintenance, models development, exercise development, etc.
YERP PMT shall review OTS design and progress to ensure compliance with this Specification and project detailed schedule.

The MAC shall be responsible for planning, manpower, and management of the activities within his scope of work such that the overall Project schedule can be achieved. The OTS shall provide an identical representation of the operating process using the actual YERP Process Automation System (PAS) operator interface, consoles, graphics and keyboards. Operator Trainees shall learn how to start-up the process, operate it under normal operating conditions, shutdown the process, handle malfunctions and process disturbances, respond to infrequent emergencies, and to meet and maintain product quality standards. The MAC shall be responsible for updating all models to reflect final design. The OTS will be split into phases in order to meet schedule constraints. All requirements such as Preliminary Design Review, Critical Design Review, Model Verification Test (MVT), Pre-Factory Acceptance Testing, System Readiness Review, Factory Acceptance Test (FAT), Site Acceptance Test (SAT), Plant DCS Alignment Test (PDAT), etc. of this specification shall apply to all phases. The OTS Hardware (including Consoles, PCs & Servers, Network equipment and accessories) and standard software will be a part of the MAC Common scope of supply. The application model software, model configuration and testing will be part of individual EPC CONTRACTOR(s) scope. The EPC CONTRACTOR(s) shall provide all required information, as mentioned in the subsequent sections, to MAC to meet the objective of delivering the OTS system. 3.0 3.1 REFERENCE DOCUMENTS & STANDARDS Conflicting and Deviations If any inconsistency or conflict exists between this specification, and other project or YERP PMT documents, industry standards or drawings, the inconsistency shall be brought to the attention of the YERP PMT. The YERP PMT will resolve the inconsistency/conflict. 3.2 YERP Reference Documents The design, materials and construction of the equipment described herein shall be in accordance with the latest revision of the documents listed below which are part of this specification. 3.3 Saudi Aramco Engineering Standards YERP-SAES-Z-001 Process Control Systems

YERP-SAES-Z-010 YERP-23-SAMSS-010 YERP-34-SAMSS-623 YERP-23-SAMSS-060 3.4
Process Automation Networks Connectivity and Security Distributed Control Systems Programmable Controller Based ESD Systems Applications Integration Middleware
Project Specification and Drawings 192-YER-PE-I35-0001 192-YER-PE-I35-0002 192-YER-PE-I35-0003 192-YER-PE-I35-0004 192-YER-PE-I35-0005 192-YER-PE-I35-0006 192-YER-PE-I35-0007 192-YER-PE-I35-0017 192-YER-PE-I35-0018 192-YER-PE-I35-0023 Main Automation Definition Contractor (MAC) Scope
Project Specification For Process Automation System Main Automation Services Contractor (MAC) Supplier
Project Specification For Emergency Shutdown System (ESD) Project Specification System (VMS) For Vibration Monitoring
Project Specification For Compressor Control System (CCS) Project Specification For Advanced Control System (APC) MAC Roles and Responsibilities Matrix PAS Console Requirements Process Automation System Architecture Drawing
3.5
American National Standards Institute (ANSI) / National Fire Protection Association (NFPA) ANSI/NFPA 70 National Electric Code (NEC).
3.6
International Organization For Standardization ISO 9000 Quality systems Model for quality assurance in design/development, production, installation and servicing.

3.7
American Nuclear Society ANS 3.5 Nuclear power plant simulator for use in operator training and examination.
4.0 4.1
DEFINITIONS & ABBREVIATIONS Definitions Company Project Management Team (PMT): The Company Project Management Team (PMT) is the group responsible for the management of the entire project and is dedicated to the overall success, development and execution of the work and to ensure alignment across the numerous project interfaces. The PMT consists of Aramco Services Company and ConocoPhillips team members, partner(s), agency personnel, and contractors. These project management resources will form a cohesive, seamless team responsible for the project execution. Saudi Aramco (SA): Saudi Aramco as used in this procedure shall mean Saudi Arabian Oil Company and its affiliated companies, including, but not limited to Aramco Services Company. ConocoPhillips (COP): ConocoPhillips as used in this procedure shall mean ConocoPhillips Company and its affiliated companies, including but not limited to ConocoPhillips Yanbu Ltd. Yanbu Export Refinery Project (YERP): The Yanbu Export Refinery Project (YERP) as used in this procedure, shall also mean the Yanbu Export Refinery Company and its affiliated companies. It is also named as the COMPANY. Contractor or Contractors: Any Design, Construction or Service Contractor(s); Manufacturer(s); Vendor(s); Government Agencies; and other similar organization(s) having a contractual relationship or a prospective contractual relationship with the Company. When used in this or referenced documents the following words are used in the manner described below: Shall and must are used in the imperative sense. Will is used in the preferred sense. May is used in a permissive sense to state authority or Permission to do the act prescribed or provide the function being defined in the prescribed manner, and the words no person may. Or a person may not. mean that no person is required, authorized, permitted to do the act prescribed, and the words a may not . mean that the item being described is not required, authorized, or permitted in the prescribed manner.

Includes means includes but not limited to. The following are terms whose meanings may not be obvious from their usage in this document. Terms that have special meaning are capitalized. Advanced Regulatory, Multi-variable, constraint and optimizing controls. Controls that fall into this category will be those that are supervisory in nature, i.e., they normally, but not always, output to the set points of other control loops rather than to the final control element directly. The restoration of OTS to a previous set of conditions which have been automatically recorded at designated time intervals or have been manually saved using Snapshot. A simulation of a digital instrumentation system providing displays, keyboard and control functions which are similar to those of the actual system. Operation of the simulation at a faster rate than real time (time factor = multiple of real time) A condition whereby the dynamic simulation will be interrupted and remain static until the simulation is taken out of the "freeze" mode, at which time the dynamic simulation resumes. A previously established plant condition stored in OTS and capable of selection by the instructor at any time. A keyboard and monitor used by the instructor to control the training session, monitor trainee performance, and perform remote actions. The person who trains operators using the OTS. An equipment failure or process disturbance initiated by the instructor. Malfunctions may be discrete or continuous. The process specification simulator specified in this
Advanced Control
Backtrack
Emulation
Fast time Freeze
Initial Condition
Instructor Station
Instructor Malfunction on line
Operator Training Simulator Operator Trainee
The person who is not trained in PAS and process operations on OTS.

Parameter
A value or status for some feature of the process model which may be changed by the engineer, instructor, or trainee. Examples: valve coefficient, controller mode, BTU value of fuel. Characteristic of a process such temperature, pressure or analysis. as flow,
Process Variable Real Time
Simulation of dynamic performance in the same time base relationships, sequences, durations, rates and accelerations as the dynamic performance of the plant. (Time factor = 1.0) An operator function required for procedures which would normally be performed from outside OTS workstation, such as the manual operation of valves. These functions shall be operable from the Instructor Station and from the Engineer Station. The review of all or part of a training session from a backtracked condition forward. All trainee and instructor actions are repeated. A configured series of remote actions, malfunctions, initial conditions etc. that are automatically activated according to pre-set time intervals. Operation of the simulation at a slower rate than real time (time factor = fraction of real time). The instantaneous storage of existing conditions at any selected point in time. The stored condition then becomes a temporary initialization point and may be called up repeatedly. The rate of simulation expressed as a factor of real time (time factor for real time = 1.0) A station consisting of one or more keyboard and monitors that allows the trainee to monitor and operate the simulated process.
Remote Actions
Replay
Scenario
Slow Time Snapshot
Time Factor Trainee Station

4.2
Abbreviations APC API ANSI ASME CCB CCS CMS DCS E&C ESD EPC FAT FGS GUI ID IDP IFAT MAC MVT NMR PAS OTS OPC PDAT PFDs P&IDs PMT SAT SME Advanced Process Control American Petroleum Institute American National Standards Institute American Society of Mechanical Engineers Central Control Building Compressor Control System Condition Monitoring System Distributed Control System Evaluation and Certification Emergency Shutdown System Engineering Procurement Contractor Factory Acceptance Test Fire and Gas System Graphical User Interface Identification Individual Development Program Integrated Factory Acceptance Test Main Automation Contractor Model Verification Test Non-Material Requirements Process Automation System Operator Training Simulator Object Linking and Embedding (OLE) for Process Control Plant DCS Alignment Test Process Flow Diagrams Piping & Instrumentation Diagrams Project Management Team Site Acceptance Test Subject Matter Expert

UPS VMS YERP 5.0 5.1
Uninterruptible Power Supply Vibration Monitoring System Yanbu Export Refinery Project
PROJECT ADMINISTRATION Project Personnel The MAC shall assign a single Project Lead responsible for this part of the PAS project and empower him to marshal all necessary MAC resources for the successful completion of the work in compliance with the requirements and schedule. The OTS Project Lead shall have demonstrated experience in the successful completion of similar simulator projects. At least one member of the OTS design team for this project shall be a part of the MACs team responsible for installation, SAT, and PDAT.
5.2
Models and Scenarios The YERP OTS system shall have the following specific Refinery Facility Models: a. Crude Distillation Unit (CDU) b. Hydrocracker (HCK) c. Distillate Hydrotreater (DHT) d. Hydrogen Generation Unit (HGU) e. CCR Reformer (CCR) f. Naphtha Hydrotreater (NHT) g. Benzene Extraction Unit (BEU) h. Isomerization Unit (ISM) i. j. l. Delayed Coker Unit (DCU) Amine Regeneration Unit (ARU) Sour Water Stripper (SWS)
k. Sulfur Recovery Unit (SRU) m. Utilities, Flare and Waste Water Treatment n. Tank Farm, Shipping and Blending The MAC may provide suggestions and recommendations on the number of models, model boundaries, and model scenarios as it sees beneficial.

The OTS environment shall support and the MAC shall include engineering time and resources to setup fifteen (15) scenarios per model as a minimum. The MAC shall include engineering time and resources to setup fifteen (15) evaluation and certification criteria per model as a minimum. 6.0 6.1 PROJECT EXECUTION Fabrication The MAC shall be responsible for fabricating the OTS system and conducting all required hardware and software configuration to provide a complete operational system. The MAC shall manage the OTS delivery schedule such that the OTS can be on site tested, functional, SAT accepted and available for use according to schedule requirements. Available for use shall be taken to mean completion of PDAT or SAT, whichever is later. 6.2 OTS Model Design Review and Testing a. The OTS Model Design Review and acceptance Test requirements shall apply to the OTS system that is supplied in accordance with this specification. These shall be conducted for each EPC CONTRACTOR responsible for the corresponding OTS model, as provided below. b. A separate Kick-off meeting with each EPC, YERP PMT and MAC shall be held to initiate OTS model design. This meeting shall define the Project schedule, the various deliverables for the defined models and review the scope & responsibilities of all the parties concerned. c. The Design Review of the OTS model shall be performed during the Preliminary Design Review (PDR) and Critical Design Review (CDR) stages. The deliverables required for the PDR and CDR shall be defined at the Kick-off meeting. d. When Modeling activities are being performed, the Model Verification Test (MVT) shall be carried out to check the steady state of each model. This is conducted for each of the OTS Models after it is built. e. The OTS Models Factory Acceptance Test (FAT) shall be conducted after the PAS FAT/IFAT has been completed. This is required so that the OTS can be aligned with the latest PAS system data, to ensure that the PAS configuration used for the OTS is the latest version. f. The OTS Models shall undergo a functional and operational Factory Acceptance Test (FAT), as per the FAT procedure. This is conducted for each of the OTS Models.

g. Upon completion of the FAT, the OTS Models software shall be shipped to site and the Site Acceptance Tests (SAT) carried out, for each of the OTS models. h. The OTS Models shall be re-aligned with the PAS system after the PAS SAT is completed. This is the final Plant DCS Alignment Test (PDAT) and shall be conducted for each of the OTS Models. i. The MVT, FAT, SAT and PDAT shall be witnessed and approved by the YERP PMT and EPC Contractor(s) representatives.
6.3
OTS Hardware and standard Software Design Review and Testing a. The OTS Hardware / standard Software are common for the OTS system and independent of the OTS Models. These are a part of the MAC Common scope of supply and include Consoles, PCs & Servers, Network equipment and accessories. The OTS Hardware / standard Software Design Review and Acceptance tests shall be conducted with YERP PMT. b. The OTS Hardware / standard Software design shall be initiated with a Kick-off meeting between the MAC and YERP PMT. This meeting shall define the Project Schedule, the various deliverables and also review the scope and responsibility. c. The Design Review of the OTS Hardware / standard Software shall be performed during the Preliminary Design Review (PDR) and Critical Design Review (CDR). The deliverables required for the PDR and CDR shall be defined at the Kick-off meeting. d. The OTS Hardware / standard Software Factory Acceptance Test (FAT) shall be conducted when the pre-FAT is completed. This FAT is conducted independent of the OTS Models FAT. e. Upon completion of the OTS Hardware / standard Software FAT, the system shall be released for the OTS Models FAT. The system shall be shipped to site upon the completion of the FAT for all the OTS Models. f. The Site Acceptance Test (SAT) shall be conducted for the OTS Hardware / standard Software system. Upon completion of the SAT, the system shall be released for the OTS Models SAT and PDAT.
g. The OTS Hardware / standard Software FAT and SAT shall be witnessed and approved by YERP PMT. 6.4 Training a. The MAC shall make available to the YERP PMT comprehensive training courses in the use of the OTS by instructors and operators. All aspects of

operation of the OTS and associated software procedures by the instructor and operator shall be covered during the courses. b. The MAC shall make available to the YERP PMT training courses in the engineering and configuration of the OTS and models. Training must include, but not limited to, all aspects of model development, customization, maintenance, and deployment, simulation lesson development. All aspects of engineering support for the OTS shall be covered during the courses. c. The MACs Curriculum Analyst and/or Developer shall participate in the development of training courses for both instructor and engineering to make the training more specific to the YERP OTS in the areas of administration, model maintenance and program reliability. d. The MAC shall provide all training materials in hardcopy and electronic format (*.DOC, *.PPT, *.PDF). e. The MAC shall permit the YERP PMT to use or otherwise incorporate the OTS training and reference materials in YERP PMTs site training curricula or programs of instruction. Copy-right abatement shall be provided by the MAC and their sub-suppliers for this activity. 6.5 6.5.1 Documentation The MAC shall furnish as a minimum the following OTS documents, in hard copy and electronic formats, during/ after the design per the project NMRs: a. Equipment layout drawings, dimensions, weights, power requirements, heat dissipation, wiring, cabling schedules/block diagrams and termination details. b. Descriptive list of equipment being supplied with model numbers. c. FAT and SAT procedures d. List of all spare parts for start up and 1 year operation, test equipment and special tools required. e. Project manuals/data books shall be provided to cover the full extent of hardware and software supplied. They shall include complete and detailed system description, operating procedures, software description, test and maintenance schedule and procedures, and all system drawings including overall architecture drawing of the system. f. Users manuals shall be provided for instructors and operators on all their respective functions.
g. The MAC shall update the OTS and provide as-built drawings, incorporating the final PAS and process modifications resulting from the project acceptance testing.

6.5.2
At PDR, the MAC shall provide a list of all known OTS system problems with discovery dates (bug list). This list should include information related to proposed release dates for correcting the hardware/software problems. SOFTWARE REQUIREMENTS Software Licensing The MAC shall provide the software license in the following format. a. Source code for all specific models in this scope shall be provided to the YERP PMT under the same license agreement. b. The license shall not limit models expansion. c. Hardware-based security keys are NOT acceptable. d. All PAS software and hardware required must match the plant YERP PAS (Version No., License etc.).
7.0 7.1
7.2
Hardware and Software The MAC shall specify and purchase as part of this project all necessary hardware, software and licenses to supply the specified OTS. Two operator consoles (Type-A) and Instructor Station consoles shall be provided for OTS. The detail requirement is specified in the Console requirement document 192-YER-PE-I35-0018. The training consoles operator screens, operating graphics, control database and logic shall be the same as that in the PAS. All PAS console operating graphics, including but not limited to those hosted by the DCS, VMS, CMS, CCS or other auxiliary PAS subsystems, shall be available in the OTS. Required PAS hardware and software provided as part of the OTS shall match the plant PAS hardware (model No., version no. etc.). Two Instructor Stations shall be provided for the Instructor to monitor and impart training to the Operator Trainees. All PCs/Servers (like Modeling Stations, DCS/ESD Simulation stations and DCS/ESD Engineering stations) shall be installed within locked cabinets. These cabinets shall have a LCD Monitor/Keyboard/Mouse to operate the PCs/Servers within that cabinet. See Appendix A for an overview of the OTS System Architecture.

8.0 8.1 8.1.1
FUNCTIONAL REQUIREMENTS General The YERP OTS system shall include, but is not limited to: a. OTS system and modeling server software and hardware. b. OTS software and hardware simulating the PAS. c. OTS engineering software for system and PAS. d. License for 4 concurrent OTS users/sessions on the same or different models.
8.1.2
The following documents are provided to define the scope of supply: a. Process Flow Diagrams b. Process Descriptions & Plant Overview
8.1.3
EPC CONTRACTOR(s) will provide the required information during Detail Design to enable the MAC to meet his objective of delivering a fully functional OTS system. This shall include but not be limited to: a. PFDs (marked-up with the information that is required for OTS). b. P&IDs (marked-up with the information that is required for OTS). c. Heat and Material Balance (at design conditions). d. Streams and compositions. e. Process Descriptions. f. Cause and Effects diagrams. g. Control Philosophy with description of complex loop. h. Equipment datasheets and drawings. i. j. l. Control and Safety Valves specification. Relief Valves specification. Piping configurations and sizing.
k. Interlock Logic Diagrams (DCS, ESD, VMS, CCS) and narratives. m. Reaction kinetics and other process licensors information for detailed modeling of proprietary equipment. n. Vendor Package documents (heat and mass balance, equipment data and drawings, descriptions, any associated control/logic narratives/diagrams).

8.2 8.2.1
Dynamic Process Modeling Module The dynamic process modeling module shall provide data validation during development for erroneous configuration such as data entry, range violation, information, and commands. The modeling module shall be able to support different data types as detailed for the PAS (i.e. discrete, analog/real, Foundation Fieldbus, calculated), as well as different controller attributes (i.e. setpoint, process variable, and mode). The modeling module shall be based on mathematical equations that are solved by open equation techniques, sequential techniques, or hybrid approach. The MAC shall describe the modeling techniques used in the OTS and the impact of these techniques on time to converge a solution and the ability to handle initial conditions. The modeling module shall include and provide realistic values of simulated parameters (whenever possible) so that operators cannot distinguish any meaningful difference between the response of the OTS and the expected response of the process unit. The MAC shall provide the degree of realism of the simulated parameters stipulated in the scope. The modeling module shall include and provide the ability to respond to changes in the simulated PAS controllers (including Foundation Fieldbus device level control) that perform in the same manner as and shall have the same functions as the actual PAS controllers. It shall provide all PAS inputs, outputs, and clamps including input, output, and bypasses of ESD, VMS and CCS. The modeling module shall include and provide the ability to respond to malfunctions (i.e. process equipment failures, instrument failures, and process disturbances) for each model. The MAC shall describe the details of these malfunctions. The modeling module shall include and provide the ability to respond to remote actions that are simulations of field-operated devices (i.e., valve, motors, and turbines) that can be activated or deactivated. The MAC shall describe the details of these remote actions. The modeling module shall include and provide the ability to modify (on-line) and tune model parameters that accurately reflect normal and transient conditions. Model parameters shall include but are not limited to the following: a. Dimensions and characteristics of equipment b. Fouling parameters c. Reaction kinetics d. Boundary conditions
8.2.2
8.2.3
8.2.4
8.2.5
8.2.6
8.2.7
8.2.8

8.2.9
The modeling module shall respond to parameter changes initiated by an Instructor or otherwise preconfigured for a specific training scenario, including but not limited to the following: a. Ambient conditions for summer / winter conditions (i.e. temperature and humidity) b. Thermodynamics c. Feed and utility temperature and pressure d. Feed and utility composition and flow e. Product temperature, pressure, composition, and flow f. Battery limit variables g. Catalyst selectivity, reactivity, and fouling h. Chemical characteristics
8.2.10
The modeling module shall continuously and accurately represent the dynamics (transient responses and real time) for all operating ranges of the simulated process units including but not limited to: a. Start ups (Hot and Cold) b. Steady state operations c. Emergency shutdown (ESD), Vibration Compressor Control System (CCS). d. Load change e. Shutdown under normal and emergency conditions f. Malfunctions g. Operator error Monitoring (VMS) and
8.2.11
The modeling module shall incorporate conventional instrument and equipment configuration standards as specified by API, ANSI, or ASME. All modeled control valve loops must include linear manual bypass valves, sized appropriately. The modeling module shall be stable and robust where it can handle +/-20% deviation (disturbances) from steady state. Calculated variables shall be accurate within 5% of emulated instrument range. The process model shall preserve the dynamic accuracy throughout all operating procedures for startup, shutdown, emergency operation, special procedures, and abnormal situation management. Energy and material balances shall be accurate to within 5% (five percent) of instrument range.
8.2.12 8.2.13 8.2.14
8.2.15

8.2.16 8.2.17
The modeling module shall allow for the generation of scenario results used to process trainee performance. The modeling module shall provide a library of thermodynamics that covers a wide range of products with its K-values and other thermodynamic parameters according to the scope. The modeling module shall accommodate up to fifty (50) sets of initial conditions for each model. At least twenty (20) of these initial conditions shall be protected from accidental modification or deletion. The modeling module shall allow for display of simulated and control parameters on a graphical user interface. The modeling module shall be built with an intuitive modeling technique including but not limited to the following: a. Flow Sheeting b. Open architecture to utilize existing and/or third party models through generation of an interface to such models c. Structure based modeling techniques with hierarchical decomposition of process into networks of elementary systems and physical connections.
8.2.18
8.2.19 8.2.20
8.2.21 8.2.22 8.2.23 8.2.24
The MAC shall specify the technique(s) used in the modeling methodology and provide detailed justification for the technique, including commented examples. The modeling module shall use a modular approach of building blocks that can be used for standard models and/or large-scale customized models. The MAC shall specify the library of model blocks for standard and customized models that can be re-usable. The modeling module shall be designed and integrated with other components using standard tools that allow for ease of modification, expanding, and/or reducing training modules by means of re-configuration while avoiding custom coding. The modeling module must permit unrestricted model maintenance to reflect changes in YERP PMTs operational philosophy or equipment/instrument configurations. No black box or gray box modeling shall be used that restricts or otherwise prevents the YERP PMT from configuring, re-configuring, or re-engineering OTS process models.
8.2.25
8.2.26

8.2.27
The modeling module shall use the same naming conventions employed in the corresponding facility subject to prevailing limitations in naming. This includes but is not limited to: a. Tag names b. Control loops c. Equipments d. Instruments
8.3 8.3.1
Scenario Building Module The scenario building module shall enable scenario development by programming a sequence of time-tagged or event-driven steps that is used for an automatic training session. The steps of the sequence shall initiate individual malfunctions at specific time or events, activate remote actions, or capturing parameters of trainee performance monitoring. The scenario module shall have the ability to build an unlimited number of scenarios for each model where each scenario shall be capable of a minimum of thirty (30) individual function steps. Each standard model shall include a set of standard scenarios. The following information as a minimum shall be available to the instructor for each scenario module: a. Scenario number and name b. Description of the scenario c. Status of the scenario (active/inactive) d. Elapsed time of the scenario when running e. Details for each step in the scenario f. Current step in active scenario g. Scenario start/stop function
8.3.2
8.3.3 8.3.4
8.3.5
The scenario module shall be configured for and display at each step within a scenario with the following information as a minimum: a. Step number or name b. Delay until step is executed following initialization of the scenario or execution of the previous step c. Function to be performed at this step (specific remote action, malfunction identifier, Trainee Performance Monitoring function, or other scenario)

d. Status for discrete variables e. Target value for analog variables f. Time interval for reaching target for analog variables g. Engineering units and description for analog variables 8.3.6 The scenario module shall tailor the OTS model initial conditions to the training scenarios. This shall include the following: a. The ability to initialize the simulation with a set of initial conditions. Upon initialization, the simulation database shall be restored to the initialized conditions. The active malfunctions in the previous training sessions shall be removed, and the model functions shall be reset to the appropriate status. b. The ability to generate and save unprotected initial conditions during a training session. 8.3.7 8.3.8 The scenario module shall include different types of malfunctions (discrete and analog) for instantaneous step, noise, offset, and/or ramping. Each scenario model shall be able to handle unlimited malfunctions. Typical malfunctions include but are not limited to the following: a. Motor trip b. Loss of signal to valves c. Loss of air to valves d. Faulty instrument readings e. Total instrument failure (i.e. instrument air compressor) f. Valve plugging g. Any ESD initiated activity h. Hi level, pressure, temperature, vibration, and flow switches i. j. l. Valves sticking Equipment plugging or fouling Bad switches and transmitters
k. Column high differential pressure m. Loss of power 8.3.9 The scenario module shall configure each malfunction with the following information as a minimum: a. Malfunction numbers or names

b. Descriptions c. Malfunction status d. Target value for analog variables e. Time interval for reaching target for analog variables f. Engineering units for analog variables g. Discrete (on/off) h. Delay time before malfunction is activated 8.3.10 The scenario module shall include types of different remote actions of a model, ability to perform simulated field operator functions on field devices or changes in model boundary conditions with instantaneous step and/or ramping. Each model shall be able to handle unlimited remote actions. Typical remote actions include but are not limited to the following: a. Remote start/stop pump b. Switch from auto to manual c. Speed control from local panel d. Shutdown switch from local panel e. Remote open/close valve f. Environment temperature rise g. Feed pressure dropping h. Local switch bypass 8.3.12 The scenario module shall have the ability to configure each remote action with the following information as a minimum: a. Remote Action number or name b. Description c. Remote Action status for discrete d. Target value for analog e. Time interval for reaching target for analog f. Engineering units for analog g. Time to transit (control valves) h. Variable damping (control valves) 8.3.13 The scenario module shall allow for management of the following: a. Ability to change Initial Conditions (save, delete, modify, rename).
8.3.11

b. Ability to incorporate malfunctions from library within a specific preprogrammed scenario. c. Ability to create other malfunctions as required for future use of new scenarios and linked to an existing sequence of scenarios. d. Ability to set malfunctions within scenarios to fail high, fail low, and fail at value. 8.3.14 The scenario module shall automatically save instantaneous values of the model database variables (snapshot). The frequency of the snapshots shall be configurable by the Developer/Instructor for any time period up to thirty minutes. The scenario module shall store up to one hundred (100) snapshots for each model. The Model calculations shall not be interrupted during recording of snapshot values. The scenario module shall have the ability to backtrack to any of the saved snapshot conditions and either restart the simulation from that point or replay the events of the training session. The replay shall recreate the actions of the simulation for the operator and/or Instructor. Replay timing (real time, slow time, or fast time) shall be adjustable while the replay is in progress. While the replay is on, the OTS shall preserve the controller response as viewed by the Trainee during the original simulation session. The scenario module shall stop or suspend (freeze) the simulation at any time by entering the appropriate command or by pressing a keyboard button (or use of mouse). During suspension, all modeled variables are static. Controller outputs and Trainees control actions shall be ignored by the OTS. All OTS screen displays will continue to be available when OTS is suspended (frozen). Administrative functions such as printing will remain enabled. The scenario module shall replay actual operator actions as scenarios from actions collected and extracted from history journal files. The scenario module shall establish initial conditions to recreate and evaluate cause and effect of process upsets experienced in the process with the benefit of simulation engineering displays and debugging tools (freeze, step, backtrack, alarm and event monitor, process monitor, trend history data).
8.3.15
8.3.16
8.3.17 8.3.18 8.3.19 8.3.20
8.3.21 8.3.22 8.3.23 8.3.24

8.3.25
The scenario module shall expand the training curriculum by introducing captured process upsets into the program to teach operators to avoid repeat occurrences while sharing these experiences with peers. Instructor Module This section includes the functions and features required for the Instructor module. The instructor module shall be a subset of the larger set of functions granted to Engineers. The instructor module shall enable customized operator training objectives, dynamic simulation practice exercises, and interactive quizzes delivered in elearning format. The instructor module shall allow a remote Instructor complete control over the OTS training session, which includes the following: a. The ability to access and interact with the following functions and features as a minimum for model tuning: Model selection functions Model parameters Boundary condition
8.4 8.4.1 8.4.2 8.4.3
8.4.4
b. The ability to access and interact with the following functions and features as a minimum for parameter changes: Process variables Initial conditions Malfunctions Remote actions
c. The ability to access and interact with the following functions and features as a minimum for training scenarios: 8.4.5 The instructor module shall have different modes of running simulation / training sessions. These shall include the following: a. The capability to run several training sessions sharing the same model. b. The capability to run several distinct/similar models from the same instructor locations.

8.4.6 8.4.7
The MAC shall specify all constraints associated with the above capabilities. The instructor module shall allow the Instructor / Developer / Engineer to manage the Initial Conditions. This shall include the following functionality: a. The ability to enable or disable initial condition protection. b. The ability to initialize the simulation with a set of Initial Conditions. Upon initialization, the simulation database shall be restored to the initialized conditions. The active malfunctions in the previous training sessions shall be removed, and the remote functions shall be reset to the appropriate status. c. The ability to generate and save unprotected initial conditions or snapshots by a command during a training session. This feature shall prompt the Instructor / Developer / Engineer for a name and description of the saved initial conditions. d. The requirement to perform additional confirmation action shall be required to overwrite conditions that have previously been saved. e. The ability to use any saved initial conditions in the future. f. The discretion to give the operator access to initial conditions menus.
8.4.8
The instructor module shall consist of, but not be limited to, the following Initial conditions sets: a. cold startup (no inventories, all utilities blocked, all valves closed, minimum system pressure, and all mechanical equipment stopped) b. warm or hot startup (startup or recovery from spurious trips of major plant equipment or upstream/downstream process flow interruptions) c. steady state (smooth, non-trending process operation at design conditions) d. saved Snapshots reconfigured as a new initial conditions set e. predefined and user-defined Scenarios
8.4.9
The instructor module shall allow the Instructor to invoke the different malfunctions of a model, and create as many malfunctions as required for future use. The instructor module shall allow the Instructor to invoke the different remote actions of a model, enabling him to perform simulated field operator functions on field devices. The Instructor/Developer/Engineer shall be able to modify and create remote actions as required. The instructor module shall provide the Instructor/Developer/Engineer the ability to load existing scenarios and to build and modify scenarios as necessary.
8.4.10
8.4.11

8.4.12 8.4.13
The Instructor shall be able to activate and deactivate a scenario. The Instructor / Developer / Engineer shall be able to modify the sequence, add steps, and delete steps interactively to scenarios. They shall be able to save and restore scenarios using removable media. The instructor module shall be capable of automatically saving instantaneous values of the model database variables (snapshot). The Instructor shall be able to activate the snapshot function automatically, and the function shall be transparent to both the operator Trainee and Instructor. The Instructor shall also be able to issue a command at any time to save the database variables (manual snapshot). The instructor module shall provide the Instructor the ability to backtrack to any of the saved snapshot conditions and either restart the simulation from that point or replay the events of the training session. The Instructor shall be able to stop the replay at any time and restart the training session from the point where the replay is interrupted. The instructor module shall provide the Instructor the ability to stop or suspend (freeze) the simulation at any time by entering the appropriate command or by pressing a keyboard button (or use of mouse). When the simulation is suspended, the Instructor shall be able to perform the snapshot function, resume simulation, initialize the simulation, initiate a replay from saved conditions, or terminate simulation. The Instructor shall be able to freeze and unfreeze the model for a desired period of time from the present simulation time. At the completion of this time, and/or while the model is in freeze mode, other displays of the Instructor interface shall still be available. The instructor module shall allow the Instructor/Engineer the ability to experiment with the process and practice operations simulation techniques. The instructor module shall allow Operations/Engineering/Maintenance to download a steady state plant initial condition and to be able to insert their own operating parameters, or to alter/tune control loops, run what if scenarios, changes to process control strategies, in order to test alternative concepts. The instructor module shall allow the Instructor to create scenarios and objective exercises from single-point faults. Model virtual equipment and emulated instrument lists shall comprise the base library for single-point faults.
8.4.14 8.4.15
8.4.16
8.4.17 8.4.18
8.4.19
8.4.20
8.4.21 8.4.22
8.4.23 8.4.24

8.4.25 8.4.26 8.4.27 8.4.28
The instructor module shall allow the Instructor to activate and inactivate scenarios dynamically during a simulator session. A scenario shall be configured to activate and inactivate at defined events or points in time in the training session. The Instructor shall be able to invoke a scenario manually at any time and/or to specify a fixed time limit for resolution of the scenario. The instructor module shall allow the Instructor to have complete control over the OTS and monitor the Operators performance in real time when Instructor and Operator are connected in a synchronous training session. Operator Training Module This section includes the functions and features required for the Operator Training Module. The operator module shall be accessible from a specific OTS console(s) and shall permit the operator to select a training course, choose interactive scenarios, access YERPs general instructions and learning resources, receive interactive training, and receive objective performance feedback from evaluation. The operator module shall utilize a simulation model engine that simulates nearreal-time within the tolerances prescribed by engineering specification. Operators must be able to monitor typical process variables and manipulate process controls without delay in the model(s). The simulator must react promptly to process transients to avoid multiple corrective actions from the operator that could inadvertently compound an upset, or create an abnormal condition because of time-lag in displayed process information. The operator module shall allow the training programs in all the following environments: a. Local interactive training (Instructor/Operator training and mentoring). b. Direct OTS connectivity through the OTS console. c. PAS emulation providing full PAS functionality and features through an OTS operator workstation.
8.5 8.5.1 8.5.2
8.5.3 8.5.4 8.5.5
8.5.6
8.5.7
The operator module shall provide the ability to review snapshots of scenarios by operator for remedial purposes.

8.5.8
The operator module shall provide training scenarios for operators that include but are not limited to: a. steady state operation b. cold start-up c. hot start-up d. process upsets e. load changes f. scheduled and emergency shutdown g. random alarms/failures h. off-spec product i. j. over limit PVs feed content changes
8.5.9
The operator module shall allow for different speeds at which the simulation can run (e.g., in real time, slow time at one-tenth real time and fast time at ten times real time). This feature shall be displayed on the users screen. This function shall cause all aspects of the simulation to run at the selected speed, including process variable displays, variable trends, and trainee performance monitoring, if active. All OTS screen displays will continue to be available when the OTS runs at a different speed. Trainee performance monitoring, if active, shall run at the corresponding speed. Administrative functions such as printing will remain enabled. The OTS system shall be a stand-alone system with no connection or access to YERPs intranet or the PAS PIN Network. Third-party audio and video resources must be called from and run in a separate window within the browser during authenticated OTS training sessions. The operator module shall allow the Operator to perform the following functions, at the discretion of the Instructor or Developer: a. Load process models b. Start, pause or stop simulation session c. Take snapshots or backtracks of process conditions d. Replay active simulation session e. Print hardcopy output of all screens and logs (except during assessments)
8.5.10
8.5.11 8.5.12 8.5.13

f.
Trend all process variables for the active model in real time and historically
g. Access malfunctions h. Access remote actions i. j. 8.5.14 View scenario progress Change speed of the simulation
The operator module shall allow the Operator to control the process model using operator functions identical to the PAS Operator Interface functions and information available in the actual process plant, including but not limited to: a. Plant graphic displays b. Instrument tag names, configurations, scale ranges, loop descriptions c. Direct-acting and reverse-acting controllers and valves, control functions. d. Alarm messaging management actions typically permitted to the Operator.
8.6 8.6.1
Evaluation and Certification Module This section includes the functions and features required for the Evaluation and Certification (E&C) Module. The module is used to evaluate and certify the Operator trainee. The E&C module must allow Individual Development Program (IDP) Evaluators to select curriculum levels and assign them to Operators to perform certification or recertification. The E&C module shall allow for Operator trainee performance monitoring groups/levels, which are organized in the model databases on a per model basis, with up to thirty (30) variables for each performance group. Performance limits and criteria shall be different from those of process alarms messaging. The E&C module shall provide a 100% objective-based performance assessment and shall execute on industry-standard algorithms. Performance results shall be reported on a normalized basis of 0-100%, and pass/fail threshold shall be selectable by the Instructor/Developer. The E&C module shall allow for the performance evaluation of the Operator trainee during a training exercise according to set criteria. These criteria shall be specified as follows: a. Simple performance criteria that include but are not limited to the following information:
8.6.2
8.6.3
8.6.4
8.6.5

Deviations of Process Variables and parameters (integral absolute error) Excursions outside limits (extremes or integral time) Number of alarms (active, acknowledged, return-to-normal) Correct or incorrect actions
b. Advanced performance criteria that include but are not limited to the following information: Severity of the deviation (integral reckoning with normalization) Number of non-acknowledged alarms Number of deviations per minute. Time process variables stayed in deviation (first-out to time out). Economic performance criteria that include but are not limited to the following information. Mass balance Economic Meter (process efficiency measured by price rations between feeds, utilities and products and adjusted to real-time dollars).
8.6.6 8.6.7
It shall be possible for a scenario to enable and disable performance monitoring and specific criteria during a training session or event. The E&C module shall provide the ability to assign a weight factor for simple and/or advanced performance criteria with the ability to enable/disable altering the weight distribution. The E&C module shall provide the ability to score the operator/trainee performance based on the pre-assigned criteria to the extent of violating the targets of the above simple and advanced criteria. The E&C module shall provide the ability to certify operation on low level entry for plant operation of major equipment, low to medium operation level on standard models, and medium to high operation level on plant specific models. The E&C module shall provide the ability of storing certified employee scenario records. The E&C module shall provide a statistical report identifying the Operator, the model, the initial condition that started the session, the performance group, and the time and date of the session. It shall also include value and status of all the information in the criteria, including but not limited to: a. Variable name and number
8.6.8
8.6.9
8.6.10 8.6.11

b. Variable monitor type (excursion, target, trajectory) c. High and low limits d. Score basis (high, low, total time out or total deviation) e. Number of points earned f. Maximum number of points possible g. Percentage score for variable h. Total score for all variables in points i. j. l. 8.6.12 8.6.13 8.6.14 8.6.15 8.6.16 Maximum possible score in points Total percentage score Pass grade
k. Pass percentage set by Instructor
The E&C module shall have the ability to provide a secure method of certification testing for individual operators. The E&C module shall not be accessible to operators and its activities shall be transparent to the operators. The E&C evaluators shall have the same access right as the instructors since evaluation is typically done by the instructor. Evaluators shall have the ability to administer operator certification and recertification tests configured and validated at the Evaluator level. The E&C module shall include functionality to generate a diagnostic report of Operator performance and event logging (for operator actions.) In addition, it shall provide a condensed certification report. Operator performance statistical report shall contain the following fields as a minimum: a. Performance group or table ID b. Model selected c. Date/time (system clock) d. Instructor name/ID (if required) e. Evaluator name/ID (if required) f. Operator name/ID g. Snapshot status (model initial condition) h. No. of variables tracked in performance table i. j. Start clock time (simulator clock) End clock time (simulator clock)

k. Log on time (system clock) l. 8.6.17 8.6.18 Log off time (system clock)
The E&C module shall maintain records about individual trainee's performance and certified employees (historical information). The E&C module shall provide the ability to produce and print certificates with scores and performance results of an Operator using export and a well established report generator. The E&C module shall include functionality to create performance tests using an unlimited selection of malfunctions and scenarios preconfigured for the associated process model. Graphical User Interface (GUI) Module The OTS shall employ a graphical user interface (GUI) for all interactions with the simulator. The GUI shall adhere to standards compatible with deployment in a typical Windows based environment. This section describes the required functions and features for the Graphical User Interface Module. The module shall provide the following capabilities: a. Full windows capabilities and multi-windows. b. Graphical user interface as opposed to a command line interface. c. Object-Oriented capabilities for process streams and equipment to encapsulate attributes and methods for the ease of building and modifications of graphics. d. Historical multi-trending facility with trend screens available for users at any time. Trends shall have the capability of trending several continuous or discrete process variables. e. Trending shall be available for up to 1000 variables at any given time. The OTS shall provide industry-standard trend features including but not limited to the following: Simultaneous multi-color PV trace display (minimum of four per display) Dynamic adjustment of high and low range scales and time span Real-time screen refresh and update Dynamic cross-hair cursor to isolate variable data in trend.
8.6.19
8.7 8.7.1 8.7.2 8.7.3 8.7.4

8.7.5
Alphanumeric variable fields identifying the variables, and status flags indicating whether the trend trace is ON or OFF.
The module shall provide flow sheet model development: a. Import and export features to and from Microsoft office (e.g. Excel) with minimal effect on speed. b. Capability of drag and drop feature. c. Capability of running third party proprietary models through generation of an interface to such models. d. Capability of building and modifying control strategies including MVC and APC. e. Capability of adding and updating new models.
8.7.6
The GUI module shall provide the following specific GUI features: a. Display header with at least the following information as applies to instructor, evaluator, Operator or model developer: Date and time (real clock time) Engineering/Instructor mode Simulation time Freeze/Unfreeze status Simulation time scale (Time factor) Model information, including name, initial conditions Display Name Graphic name Type of evaluation report Snapshot
b. Access to process variable list in tabular format. The list shall be capable of displaying, in real time, the value or status of any variable in the model database. It shall be capable of displaying up to 500 variables. The Instructor shall have the capability to assign variables to this list interactively. c. Access to malfunctions. The list shall support a minimum of 150 malfunctions and shall be scrollable to enable viewing all available malfunctions for the model. The list shall indicate the status of all malfunctions, and shall not segregate analog and discrete malfunctions. d. Access to remote field actions in a separate window. e. View scenario progress.

f.
Ability to navigate with: drop-down list manual screens for entering data shortcut keys/commands dialogue boxes dashboards graphics
8.7.7 8.7.8 8.7.9 8.7.10
The GUI module shall generate logs and reports of user (Operator, Instructor, developer, and engineer) and/or system events. Events shall be stored and displayed automatically in chronological order and stamped with the simulation time. While the logs are on screen, the display shall be refreshed with new information as it occurs. The events display shall display alarms or any conditions that indicate the model is being operated beyond reasonable fidelity limits. It shall be possible to print a log of these events, archive them and display them. These logs shall include the following: a. Instructor actions (and Operator actions if enabled by Instructor), as a minimum: Instructor name and ID number Inserted malfunctions (manually or automatically). Inserted remote actions (manually or automatically). Start, freeze, or unfreeze model execution Selected model Selected initial conditions Speed up/Slow down Activate scenario Replay started or stopped Snapshot selected.
b. The log shall contain the following Operator actions, as a minimum: Operator name and ID number Alarm acknowledgement

Controller mode change (auto, manual, cascade) Controller setpoint change Controller output change while in manual mode Discrete output changes (valves open/close, pumps and motors start/stop)
c. The log shall contain the following OTS events as a minimum: 8.7.11 8.7.12 Process alarms Discrete input or output changes (valves open/closed, pumps and motors start/stop) System alarms OTS system faults or error messages
The GUI module shall provide a set of control faceplates to provide accurate and consistent control behavior of the simulated models. The GUI module shall provide a profile for the Instructor view that consists of several displays depicting the Instructor functionalities mentioned above in the Instructor section. The GUI module shall provide a profile for the Operator view that consists of several displays depicting the Operator training functionalities mentioned above in the operator training section. The GUI module shall provide a profile for the Engineers to develop, maintain, tune, test, train on, and proliferate models via an interactive graphical system. The GUI module shall provide a comprehensive, context-sensitive help feature. The GUI HELP dialog must be available to instructor and Operator at all times, and accessed from a scenario, hot button, and menu entry in the simulator command bar. User assistance categories must include specific instructions in operation of the simulator, provided by OTS Supplier. Model-specific assistance must include relevant categories provided by YERP PMT Subject Matter Experts (SMEs).
8.7.13
8.7.14 8.7.15 8.7.16
8.7.17 8.7.18

8.8 8.8.1 8.8.2
Integration Module This section describes the required functions and features for the Integration Module. The integration module shall include tools and utilities to fully emulate the YERP PAS. Display graphics, control loops, trend displays, summary logs, etc. shall be included in the emulation. The integration module shall have the ability to emulate control strategies of the PAS. It shall provide the capability of viewing and modifying these features. The integration module shall have import features that provide the import of PAS displays and control strategies including but not limited to the DCS, ESD, FGS, VMS, CCS systems. The integration module shall provide the ability of including these displays and control strategies in the OTS application to provide an off-line training environment. The integration module shall provide the capability to modify the imported displays and control strategies. OTS Integration shall provide the ability to interface and/or emulate other systems including but not limited to: a. Shutdown strategies and functions from ESD, VMS, CCS system b. Fail-safe devices (trips, interlocks, emergency isolation valves, prealarms, logic interrupts, and abnormal situation sequencing) c. Advanced control strategies that include but are not limited to DMC+, RMPT, SMOC, Connoisseur, etc. d. Different types of Historians (i.e. PI, PHD, iHistorian, etc.).
8.8.3 8.8.4
8.8.5
8.8.6 8.8.7
8.8.8
The integration module shall have an open architecture that provides the ability to import third party: a. Modeling packages through generation of an interface to such packages. b. Automatic controller tuning packages.
8.8.9 8.8.10
The integration module shall have the capability and compatibility of interfacing with OPC compliant systems. The integration module shall allow the performance and evaluation modules to capture the operators response, evaluate performance objectively, and to

maintain a record of their progress in an automated, accurate, and consistent manner. 8.8.11 The integration module shall allow the Instructor and/or Engineer to: a. Maintain and configure Operator performance criteria with an option to retrieve previous criteria. b. Retrieve Operator performance statistics during or after a training session. c. Enable/disable the Operator performance automatically (within a scenario.) function manually or
d. Operator performance monitoring, if active, shall also be suspended when the OTS is paused or frozen. 8.9 8.9.1 8.9.2 8.9.3 8.9.4 System This section describes the required systematic functions and features for the OTS system. The OTS shall include developers tools and utilities to develop, build, customize and maintain simulated process models. All simulator models created are the sole property of YERP, without royalty or other perpetual commission. The OTS system shall provide a secure and functional separation for discrete user groups. User groups shall consist of: a. Engineers b. Developers and Instructors c. Evaluators d. Operators 8.9.5 8.9.6 8.9.7 8.9.8 Each group shall be permitted restricted access to a specified domain of OTS features and functionality required for that user group. Curriculum developers shall be granted access to all Engineer functions to ensure model integrity and intended functionality. The OTS system must require all users to log on and authenticate to the system. The OTS system must have the capability of printing all screens, displays, summaries, and logs.

8.9.9 8.9.10
The OTS system shall be based on standard software with minimum code customization. The OTS system software that runs within or on behalf of the OTS shall not be specific to or constrained by the network or desktop operating system revision level at time of initial installation. The OTS system shall allow for seamless migration/upgrade of OTS system application to accommodate progress in version levels of operating systems, core OTS system software, and other OTS system software. The MAC shall be responsible for performing such migration. The OTS system shall have the capability for remote secured access for remote Supplier maintenance and support purposes consistent with YERP IT computer asset security policies. The OTS system shall allow for efficient utilization of CPU and memory with the following criteria: a. Response time of less then two (2) seconds from activation. b. Update dynamic fields on displays at least once every two (2) seconds. c. Change from one model to another within less than two (2) minutes. d. Simulation execution speed shall be selectable (real time, slow time in increments of one-tenth real time and fast time in increments of 1 up to 10 times real time). The OTS shall be configured with a no-wait state option to dedicate unallocated processor capacity to simulation execution time. e. Simultaneous execution of models as per the number of concurrent users stipulated in the Scope section of this document. f. At the completion of SAT, OTS system shall have 50% spare disc capacity.
8.9.11
8.9.12
8.9.13
g. At the completion of SAT, OTS system shall have 50% memory expansion capacity for future.
8.9.14
OTS system shall be available for 97% of the time. The MAC shall specify the requirements to achieve this availability. The OTS system will be powered from an Uninterruptible Power Supply (UPS) system. The OTS system shall comply with the following standards: Cape Open or OPC for interfacing with third parties.
8.9.15

8.9.16
The OTS system's computational cycle time and sequence shall be such that simulated transients have the same time dependence as that observed in the actual process. The MAC shall specify the minimum system requirements for large specific models.

APPENDIX A: OTS SYSTEM ARCHITECTURE

192 Yer Pe I35 0014

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

192 Yer Pe I35 0014

Uploaded by

Copyright:

Available Formats

Yanbu Export Refinery Project

Yanbu Export Refinery Project

APPENDIX A: OTS SYSTEM ARCHITECTURE ........................................................................ 40

General Confidential Page 3 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 5 of 40

Yanbu Export Refinery Project

YERP-SAES-Z-010 YERP-23-SAMSS-010 YERP-34-SAMSS-623 YERP-23-SAMSS-060 3.4

General Confidential Page 6 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Fast time Freeze

Instructor Malfunction on line

Operator Training Simulator Operator Trainee

General Confidential Page 8 of 40

Yanbu Export Refinery Project

Process Variable Real Time

Slow Time Snapshot

Time Factor Trainee Station

General Confidential Page 9 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

UPS VMS YERP 5.0 5.1

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 15 of 40

Yanbu Export Refinery Project

8.0 8.1 8.1.1

General Confidential Page 16 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

8.2.12 8.2.13 8.2.14

Yanbu Export Refinery Project

8.2.21 8.2.22 8.2.23 8.2.24

General Confidential Page 19 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

8.3.17 8.3.18 8.3.19 8.3.20

8.3.21 8.3.22 8.3.23 8.3.24

Yanbu Export Refinery Project

8.4 8.4.1 8.4.2 8.4.3

General Confidential Page 24 of 40

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

8.4.25 8.4.26 8.4.27 8.4.28

8.5 8.5.1 8.5.2

8.5.3 8.5.4 8.5.5

General Confidential Page 27 of 40

Yanbu Export Refinery Project

8.5.11 8.5.12 8.5.13

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

k. Pass percentage set by Instructor

Yanbu Export Refinery Project

8.7 8.7.1 8.7.2 8.7.3 8.7.4