Attachment 1 - SOW.pdf

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Contents

C.1 Title of Project C.2 Background C.3 Objective C.4 Scope of Work/Tasks C.5 Reporting Requirements

C.5.1 Monthly Letter Status Report (MLSR) C.5.2 Final Report

C.6 List of Services/Deliverables C.7 Required Materials/Facilities C.8 Release of Publications C.9 Place of Performance C.10 Recognized Holidays C.11 Hours of Operation C.12 Certification and License Requirements C.13 Key Personnel Qualification Requirements C.14 General – Contractor Personnel C.15 Contractor Travel C.16 Data Rights C.17 Incremental Development for Software C.18 Section 508 – Information and Communication Technology Accessibility C.19 Applicable Publications (Current Editions) C.20 Government-Furnished Property

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

(Completion-type)

C.1 Title of Project

TTC Simulator Support

C.2 Background

The Nuclear Regulatory Commission (NRC) uses several full-scope and part-scope nuclear power plant simulators at the Technical Training Center (TTC) in Chattanooga, TN, to implement the TTC simulator program. The program is used to train a variety of NRC staff, including operating license examiners, inspectors, and other technical staff, as well as to facilitate NRC research, outreach, and various staff developmental activities. The simulators are a key part of the NRC training mission, providing the NRC staff with hands-on nuclear power plant operational experience and knowledge.

A nuclear power plant simulator is a complex machine used to replicate in real-time and with high fidelity the controls, indications, and performance of a nuclear power plant. A simulator is comprised of thousands of switches, meters, controllers, recorders, display devices, power supplies, high-speed input/output (I/O) systems, human machine interface devices, data, software, networking systems and computer systems. A full-scope simulator provides a human machine interface (HMI) representative of an entire nuclear power plant control room. A part-scope simulator provides an HMI representing only a portion of plant controls or functionality.

The TTC has five full-scope control room simulators representing the Babcock and Wilcox (B&W), General Electric (GE), Combustion Engineering (CE), Westinghouse four-loop, and Westinghouse advanced reactor designs, and a full scope glass panel simulator. The TTC also has two part-scope severe accident simulators for training on severe accident management guidelines. These simulators are implemented using various vintages of software and hardware, some of which has been upgraded to utilize more modern development tools. Simulator components include legacy and upgraded Input/Output (I/O) systems; legacy hard panel bench boards, control panels, and information displays; soft-panel HMI’s and information displays; Windows servers and workstations; backup power supply systems; a backbone network with subnets for each simulator; legacy FORTRAN code modules; GSE tools and GSE tool-developed code/applications, CORYS tools and CORYS developed code/applications, ProcSee information displays, a server backup and imaging system, and a version control system.

A simulator configuration control program is used to manage maintenance and change activities to ensure that each simulator’s functional and physical attributes are consistent with requirements. The program utilizes hardware, software, general, and expert support for configuration control activities. Simulator support requires highly specialized skills and complex, sometimes proprietary, tools to use, repair, adjust, modify, maintain or replace simulator components and systems. The Contractor shall track all warranties for purchases made during the duration of this contract and provide warranties to the COR upon request.

Simulator support has been provided by contractors since the first simulators were installed at the TTC in 1985. Staff simulator engineers manage the TTC Simulator Configuration Control Program and provided software, general, and expert support, and contractors have provided hardware, software and general support. Due to the complexity and full training schedules, contractor support for all types of configuration control activities is again required.

Non-Personal Services

It is expressly agreed and understood that this is a non-personal services contract as defined in Federal Acquisition Regulation 37.101, under which the services performed by the Contractor are rendered in its capacity as an independent contractor. The Government will evaluate the quality of the service provided but retains no control over the Contractor’s employees or agents. The Contractor is solely liable for and shall expressly agree to indemnify the Government with respect to any liability producing acts or omissions by it or by its employees or agents.

Kickoff Meeting

The Contractor shall be required to attend a kick-off meeting with the COR and CO within seven (7) calendar days of contract award. Periodic meetings will be scheduled as needed by the COR. The Contractor may request meetings whenever a discrepancy exists, and no mutual resolution is apparent.

The purpose of the kickoff meeting will be to ensure that all parties involved have a common understanding of the goals and expected results, as defined in the contract.

C.3 Objective

The objective of this contract is to obtain support services for the TTC Simulator Configuration Control Program, which enables the NRC training program for inspectors, license examiners, and others which, in turn, supports the NRC’s mission to provide reasonable assurance of adequate protection of public health and safety, to promote the common defense and security, and to protect the environment.

The goal of this contract is to supply TTC Simulator Configuration Control Program support for all simulators currently located at the TTC or that may be installed at the TTC during the term of this contract.

Hardware support shall include various hardware preventative maintenance, corrective maintenance, and modification activities. The activities will include troubleshooting, testing, component installation, vendor support, network administration, hardware modifications, and hardware configuration management including the use of an administrative configuration control system.

Software support shall include software modification activities. The activities will include issue identification, troubleshooting, modifications, testing, updates, and software configuration control including the use of an administrative configuration control system.

General support shall include activities to support simulator operations, component control, and documentation. The activities will include simulator component purchases and component control; and documentation of simulator configurations and maintenance activities.

Simulator engineering expert support shall include activities to supplement on-site and off-site support when requested and as needed to perform advanced simulator hardware and software work. Expert support activities may include changes to the I/O interface or model changes to the various core and thermal hydraulic methods employed in the simulators (e.g. RELAP, MELCOR, JTopmeret, REMARK).

C.4 Scope of Work/Tasks

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items, resources, and non-personal services necessary to perform TTC Simulator Configuration Control Program support as defined in this Statement of Work (SOW), except for those items specified as Government-furnished property and services. The Contractor shall perform to the standards in this SOW.

The Contractor shall provide support services for all simulators presently located at the TTC, and any additional simulators which may be installed at the TTC as specified. The Contractor shall provide support services during the core support hours as defined in Section C.11, unless otherwise noted. In addition to the routinely required combined 40 hours of on‑site hardware and general support each week, the Government anticipates a temporary need for up to 80 additional hours of support. These additional support hours shall be requested and approved in accordance with this SOW.

The Contractor shall provide off-site software support when requested by the Contracting Official Representative (COR). The software support will be used as needed for specific tasks that, in the judgment of the COR, have a scope or difficulty beyond the capability of current simulator engineering support functions. Any use of simulator software support shall be approved by the COR prior to commencing any work activity.

The Contractor shall provide off-site simulator engineering expert support when requested by the COR. The expert support will be used as-needed for specific tasks that, in the judgement of the COR, have a scope or difficulty beyond the capability of Hardware / Software support functions outlined in Section C.4.1.1 and C.4.1.2. The Contractor may only begin simulator engineering expert support activities after receiving approval from the COR.

The software support, detailed by the previous two paragraphs, shall be performed on-site in limited circumstances when agreed upon by the Contractor and COR. On-site work shall be limited to activities that are unable to be performed remotely, such as troubleshooting issues that require I/O or use of equipment that must remain at the TTC. Travel funds shall be paid by the NRC under the scope of this contract.

The Contractor shall provide up to 480 hours of off-site simulator software support during each performance period.

The Contractor shall provide readily available resources sufficient to perform up to 240 hours of simulator engineering expert support during each performance period.

C.4.1 Work Requirements

The Contractor shall supply on-site simulator hardware and general support functions, and off-site software and simulator engineering expert support functions as specified.

The information and communication technology (ICT) accessibility requirements, as stated in section C.18 of this SOW, shall not conflict with the essential need for the simulators to replicate in real-time and with high fidelity the controls, indications, and performance of a nuclear power plant. Therefore, unless accessibility requirements are specified in a task below, the COR will notify the contractor when, and for what features, a deliverable must conform to the requirements in section C.18.

C.4.1.1 Hardware Support Functions

The Contractor shall provide simulator hardware preventative maintenance, network administration, corrective maintenance, and modifications as specified. All such activities will be controlled as required by the TTC Simulator Configuration Control Program.

C.4.1.1.1 Hardware Preventative Maintenance

The Contractor shall provide routine hardware preventative maintenance for the TTC simulators. Preventative maintenance shall include activities to inspect, test, correct, and document simulator hardware conditions to prevent faults and ensure proper operation. Examples of simulator hardware preventative maintenance activities include checks of functions, indications, controls, recorders, alarms, power supplies, labels, and physical conditions including cleanliness. Preventative maintenance activities shall also include entry of any condition requiring corrective maintenance into the configuration control system when required.

C.4.1.1.2 Hardware Corrective Maintenance

The Contractor shall provide hardware corrective maintenance for the TTC simulators.

Corrective maintenance shall include activities to identify, isolate, repair, replace, test, and document faulted or failed components such that the simulator is restored to a fully operational condition. Examples of simulator hardware corrective maintenance are repairs to or replacement of such things as:

• power supplies,

• chips or modules,

• bench board equipment,

• input/output equipment,

• annunciators,

• wires or cables,

• hand switches,

• relays,

• pins and connectors,

• analog simulation equipment,

• displays,

• computers,

• network equipment, and

• additional hardware-related problems as identified by simulator users and documented through the NRC’s Simulator Configuration Control system.

C.4.1.1.3 Hardware Modifications

The Contractor shall perform hardware modifications for the TTC simulators. Hardware modifications shall include activities to change, upgrade, or replace simulator components to improve performance, reduce costs, or meet new requirements.

Examples of simulator hardware modifications include such things as replacement of analog components with digital components, upgrades to input/output chassis, or replacement of displays with newer technology.

C.4.1.1.4 Simulator Network Administration

The Contractor shall provide support for the TTC simulator network. Network administration shall include activities to operate and maintain the simulator network.

Examples of network administration activities include the configuration and maintenance of:

• the various routers used within the simulator network,

• the simulator network’s Domain Naming Service (DNS) database and the DNS servers,

• the simulator network’s Dynamic Host Configuration Protocol (DHCP) server,

• accounts on various simulator computers, servers, and other network equipment,

• simulator access authentication and authorization,

• network topologies and documentation, and

• network controls in compliance with applicable agency cyber security requirements.

C.4.1.1.4 Simulator Computer Administration

The Contractor shall provide routine administration for computers associated with the TTC simulators. Computer administration shall include activities to maintain the confidentiality, integrity, availability, resiliency, and documentation of simulator computer systems (including servers, instructor stations, panel graphics PCs, etc) required for proper operation. Some examples of computer administration activities include:

• configuration and installation of software or BIOS settings on simulator servers and workstations;

• installation of software updates and patches;

• performance of scans to ensure proper system configurations and software installation;

• use of automated and manual backups (such as disk images and file backups) to ensure simulator computer configurations are captured and can be quickly restored in the event of a failure;

• use of the simulator knowledge management system to capture steps necessary to restore or initially configure a simulator computer.

C.4.1.2 Software Support Functions

The Contractor shall provide for simulator software modifications as specified. All such activities will be controlled as required by the TTC Simulator Configuration Control Program.

C.4.1.2.1 Software Modifications

When directed by the COR, the Contractor shall provide software modifications for the TTC simulators. Software modifications shall include activities to change, upgrade, or enhance simulator software or applications to improve performance, reduce costs, or meet new requirements.

Examples of simulator software modification activities include:

• determining the relationship among changes in simulator performance, input/output values, application state, code, and data;

• applying first principles to the reference power plant model;

• using common commercial codes, scripts, or databases such as Fortran, C++, Visual Basic, PHP, and Access;

• using simulator engineering applications and codes such as SimExec, JADE, Thor, MELCOR,RELAP, and JTopmeret;

• compilation and rebuilding simulation modules to support implementing and testing of changes;

• create or modify various displays used in each simulator to operate and display information for the students;

• documentation of changes made using the simulator software configuration control system;

• commitment of changes using the simulator version control system; and

• evaluation of the impact of changes on simulator performance and coordination with the simulator lead instructor when required.

C.4.1.3 General Support Functions

The Contractor shall provide for simulator operations, component control, and documentation. All such activities will be performed as required by the TTC Simulator Configuration Control Program by the on-site hardware technician.

C.4.1.3.1 Simulator Operations

The Contractor shall provide simulator operations support for the TTC simulators.

Operations support shall include activities to ensure the simulators are available and perform properly when required for use, maintenance activities do not interfere with operations, and simulators are secured in an orderly fashion when not in use.

Examples of simulator operations support activities include:

• communicating simulator status to affected NRC staff either verbally, through email, or signage / annotations at the impacted simulator;

• reporting any issues requiring action to the simulation engineering staff and documenting the issues in the discrepancy tracking database;

• scheduling simulator use and maintenance periods;

• performing simulator startup and testing / DORT activities;

• assisting with simulator training by performing instructor station(“booth operator”) activities if requested.

C.4.1.3.2 Simulator Component Control

The Contractor shall provide simulator component control for the TTC simulators.

Component control shall include activities to obtain, inventory, control, and dispose of simulator program items. Simulator program items include items such as simulator components, replacement components, tools, test equipment, and other items as necessary to support the operation and maintenance of TTC simulators. Examples of simulator program items are:

• new identical components,

• refurbished components,

• components with a similar function,

• components of a newer or different design to replace existing, obsolete components,

• components that combine the function(s) of existing components,

• software to enable the use of, or that programs, components,

• components used to perform tests or analysis of simulator systems, and

• other parts or equipment needed by simulator engineers to support maintenance of simulator software

The Contractor shall procure simulator components, tools, test equipment, and consumables, with the prior written approval of the COR, as necessary to perform the tasks in this SOW.

Each order for simulator components, tools, test equipment, vendor support, and other items procured by the Contractor shall be submitted to the NRC COR on a contractor-generated form for review and approval prior to any order being placed. The Contractor shall make every effort to procure simulator components, tools, test equipment and vendor support at the lowest available price. This effort shall include identification of multiple suppliers for all orders, where possible. When multiple suppliers are not available, the reasons for selecting a single source shall be provided. The Contractor shall include any discount or rebate in the cost of the simulator components, tools, and test equipment or services provided to the NRC.

The contractor shall ensure that each ICT purchase conforms to the accessibility requirements in section C.18 of this SOW, unless one or more Section 508 exceptions apply, are documented, and are approved in writing by the COR before procurement.

To receive Government reimbursement for components and equipment purchased by the Contractor, for each purchase, the Contractor shall provide a copy of the invoice/receipt as an attachment to the monthly invoice submitted to the NRC. The Contractor will not be reimbursed for parts or equipment purchased without this supporting documentation.

The Contractor shall maintain accurate records of all purchases and shall track the total cost of all purchases, including any shipping or handling fees. All parts, tools, test equipment, and other items procured by the Contractor and reimbursed by NRC shall become and remain the exclusive property of the Government.

The Contractor shall develop and maintain a component control system to account for and control simulator components as required by the TTC Simulator Configuration Control Program. Items tracked by the program shall include all GFP used by the Contractor in the performance of the contract. Requirements for the component control system include providing details sufficient to determine item identity, configuration, location, source, age, cost, associated systems, reorder points, and status. For simulator network components and computer systems, the component control system shall additionally track details such as installed software, installed hardware, software configuration, and network diagrams. The Contractor shall conduct a verification of component inventory each year and provide a written inventory report of the results to the COR. The Contractor shall also produce a simulator status report listing selected components and their status when requested by the COR.

The Contractor shall remove and dispose of failed simulator equipment or components that are no longer usable. All such equipment shall be disposed of in accordance with applicable Federal requirements such as GSA Bulletin FMR B-34, “Disposal of Federal Electronic Assets”. The Contractor shall receive COR authorization prior to component disposal and shall provide an annual report of disposed items to the COR along with the annual inventory report.

C.4.1.3.3 Documentation

The Contractor shall provide documentation of support activities and shall maintain other simulator program documentation as required by the simulator configuration control program. Examples of documentation include:

• simulator inventory verification reports,

• simulator status reports,

• monthly reports to the COR,

• disposal report,

• support outage contingency plan,

• simulator configuration control system entries,

• entries in the simulator program knowledge management system,

• updates to system documentation, and

• updates to simulator wiring lists and diagrams.

The contractor shall ensure that documentation that is created or revised is accessible in conformance with the requirements in section C.18 of this SOW.

C.4.1.4 Simulator Engineering Expert Support Functions

The Contractor shall provide off-site support for simulator engineering expert functions.

Expert support will be used as requested by the COR for simulator support issues beyond the capability of on-site support. This support may be subcontracted by the Contractor with COR approval as necessary. Examples of simulator engineering expert support include:

• advanced levels of simulator software support functions,

• expert development and maintenance of simulator engineering codes to the following types of models: core, neutronics, and severe accident response such as MELCOR, RELAP, S3R, JTopMeret, and REMARK;

• advanced work interfacing simulator engineering code with full-scope simulator input/output systems;

• expert development and modification of graphical displays and human machine interfaces for commercial nuclear power plant simulators.

C.4.2 Support Outages

The Contractor shall notify the COR of known planned or unplanned outages of simulator support. The Contractor shall document all support outages as part of the Contractor’s regular reports to the COR. The Contractor shall not invoice the government nor shall the Contractor be paid for hours during which support services are not provided.

C.4.2.1 Planned Support Outages

Planned support outages (i.e., outages that are controllable and predictable) shall be approved by the COR prior to the outage. Notification shall be provided to the COR at least 1 business day before the outage.

C.4.2.2 Unplanned Support Outages

Unplanned support outages (i.e., outages that are not controllable or not predictable) shall be discussed with the COR in a timely manner (within 1 hour during business hours). The Contractor shall provide the COR with a contingency plan for minimizing unplanned support outages and submit this report to the COR at the beginning of each performance period. The Contractor shall ensure that unplanned support outages are remedied within an established timeframe in collaboration with the COR.

C.4.3 Changes/Additions to Support Hours

Normally, simulator support shall be provided during core support hours. However, when the COR determines there is an operational or training need, the COR may authorize and the Contractor shall provide simulator support outside of core hours. For example, during periods of heavy simulator use, simulators are sometimes scheduled for training during an evening shift and the COR might authorize the Contractor to provide up to eight consecutive hours of simulator support between 4:00 PM and midnight.

The support may be provided by shifting support from the usual core support hours or by authorizing additional support hours. The COR will notify the Contractor as soon as practicable of the need to change or provide additional support hours and will authorize the change prior to the Contractor providing the support hours. The Contractor shall document all support hours worked outside of core hours as part of the Contractor’s regular reports to the COR.

C.4.4 On-Site Manager / Lead Contact

The Contractor shall designate one staff member as the on-site manager / lead contact.

This individual shall be the point of contact with the COR for communications concerning day-to-day performance of the contract.

The Contractor’s on-site manager/lead contact shall coordinate simulator support requirements and changes to support hours with the COR, and ensure that work performed is authorized in the Simulator Configuration Control Program.

C.4.5 Status Meetings

The Contractor’s on-site manager/lead contact shall meet weekly with the COR to discuss planned support activities and tasks to be performed during the subsequent period. This is not an implication of personal services; rather, the purpose of such a meeting is to coordinate software and hardware work with the simulator schedules.

C.4.6 On-Call Support

To the maximum extent possible, support functions shall be performed during the core support hours. When unplanned issues that affect simulator availability occur and support outside core hours is required, the Contractor shall provide on-call support.

The Contractor shall provide support within one hour of notification. Historically there are fewer than five on-call support requests per year with an average duration of two hours per request.

All occurrences of such on-call support must be pre-authorized by the COR.

C.5 Reporting Requirements

C.5.1 Monthly Letter Status Report (MLSR)

The Contractor shall provide a Monthly Letter Status Report which consists of a technical progress report and financial status report. This report will be used by the Government to assess the adequacy of the resources proposed by the Contractor to accomplish the work contained in this SOW and provide status of the Contractor’s progress in achieving tasks and producing deliverables. The report shall include contract/order summary information, work completed during the specified period, milestone schedule information, problem resolution, travel plans, and staff hour summary.

C.5.2 Kickoff Meeting Summary with Transition-In Plan

Following the kickoff meeting, the Contractor shall submit a summary of items discussed at the kickoff meeting and a written Transition-In Plan. This Transition-In Plan shall include a detailed description of the Contractor’s time-phased activities, resources, staff onboarding, and transfer of knowledge, services, and associated data to ensure that at completion of the transition-in period, the Contractor shall have responsibility for all requirements covered under this contract. The Contractor’s Transition-In Plan shall identify risks and mitigation strategies to ensure there is minimum service disruption to vital NRC operations.

C.5.3 Transition-Out Plan

If director by the COR, the Contractor shall provide a Transition-Out Plan to the COR within 30 calendar days of contract expiration date to describe how the services provided to the government during the phase-out period shall ensure knowledge transfer. The Transition-Out Plan shall include access to documentation detailed in section C.4.1.3.3 and any product developed during required work of this contract. The government reserves the right to perform inspections on services provided to the extent deemed necessary to protect the government’s interests. The Contractor shall control the quality of the services and deliverables provided in support of the tasks/services above and maintain substantiating evidence that services conform to contract quality requirements and furnish such information to the government, if requested.

C.6 List of Deliverables

Section # Deliverable Due Date Format Submit to C.5.2 Kickoff Meeting

Summary with Transition-In Plan

No Later Than (NLT) 5 business days following the kickoff meeting

Word or Adobe PDF Document

COR

C.5.1 Monthly Letter Status Report

10th of the following month

Word or Adobe PDF Document

COR

C.5.3 Transition-Out Plan

30 calendar days prior to contract expiration

Word or Adobe PDF Document

COR

C.4.2.2 Support Outage Contingency Plan

First month of each performance period

Word or Adobe PDF Document

COR

C.4.1.3.2 Annual Inventory Verification Report

By the end of the last month of each performance period or when requested

Word or Adobe PDF Document

COR

C.4.1.3.2 Annual Component Disposal Report

By the end of the last month of each performance period

Word or Adobe PDF Document

COR

C.4.1.3.2 Simulator Status Report

When requested Excel Spreadsheet

COR

C.7 Required Materials, Facilities, and Hardware/

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items, resources, and non-personal services necessary to perform TTC Simulator Configuration Control Program support as defined in this SOW, except for those items specified as Government-furnished property and services.

C.8 Release of Publications

Any documents generated by the Contractor under this contract/order shall not be released for publication or dissemination without CO and COR prior written approval.

C.9 Place of Performance

For software support, most of the work will be offsite. For on-site, hardware support, most of the work will be performed at the TTC.

Address:

NRC Technical Training Center (Osborne Office Center) 5746 Marlin Rd. Suite 200 Chattanooga, TN 37341

In the event of Government facility closure as described in C.11, the COR may authorize off-site support to be performed by in lieu of on-site support. Off-site work to be performed under this contract will be primarily performed at the Contractor’s facility.

C.10 Recognized Holidays

Contractor personnel shall not be required to perform on the Federal holidays identified below.

Contractor personnel shall comply with their company’s policies and procedures regarding their work status on these days or the federal holidays listed on the Office of Personnel Management (OPM)’s website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

C.11 Hours of Operation The Contractor shall provide required support during core support hours, 7:30 am to 4:15 pm (local time), Monday to Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.12 Certification and License Requirements

N/A

C.13 Personnel Qualification Requirements

The following labor category is defined as key personnel:

1. On-site Manager/Lead Contact

C.13.1 On-Site Hardware Support Qualification Requirements (Lead)

The Contractor shall provide an on-site Manager/Lead Contact with sufficient qualifications to perform the hardware support specified in this SOW. This person shall possess a combination of education/training and experience that demonstrates competence in the maintenance of full-scope power plant simulators or equivalent full-scope aviation or industrial simulators. Competence shall be demonstrated by meeting each of the following requirements:

• Completion of training/educational program on the maintenance of full-scope simulator hardware and computer systems. Acceptable training includes technical or trade schools, military training, and commercial training programs;

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

• A minimum of two years of work experience related to the maintenance of complex electronic systems. Systems meeting this requirement must include an electronic I/O system or data acquisition system. This person is identified as Key Personnel and shall meet this requirement through experience on full-scope nuclear power plant simulator hardware;

• Experience with configuring and maintaining Microsoft Windows and Windows Server operating systems;

• A minimum of 4 years of work experience demonstrating the ability to troubleshoot complex electronic equipment utilizing test equipment such as oscilloscopes, multi-meters, and related equipment; and

• Strong communication skills and experience delivering technical customer service.

C.13.2 On-Site Hardware Support Qualification Requirements

The Contractor shall provide personnel with sufficient qualifications to perform the hardware support specified in this SOW. This person shall possess a combination of education/training and experience that demonstrates competence in the maintenance of electronic control systems and computer/network equipment. Competence shall be demonstrated by meeting each of the following requirements:

• Experience with configuring and maintaining Microsoft Windows and Windows Server operating systems;

• A minimum of two years of work experience related to the maintenance of complex electronic systems. Systems meeting this requirement must include an electronic I/O system or data acquisition system.

• A minimum of 4 years of work experience demonstrating the ability to troubleshoot complex electronic equipment utilizing test equipment such as oscilloscopes, multi-meters, and related equipment; and

• Strong communication skills and experience delivering technical customer service.

C.13.3 Off-Site Software Support Qualification Requirements

The Contractor shall provide personnel with sufficient qualifications to perform the software support activities specified in this SOW. All software support personnel shall possess a combination of education/training and experience that demonstrates competence in the programming and maintenance of full-scope power plant simulator software. Competence shall be demonstrated by meeting each of the following requirements:

• Completion of a bachelor’s degree in an Accreditation Board for Engineering and Technology, Inc. accredited engineering program or equivalent training and education that includes differential and integral calculus, linear algebra, fluid mechanics/hydraulics, thermodynamics, electrical systems and circuits, and control systems;

• A minimum of four years of work experience related to the simulator engineering as applied to real-time commercial nuclear power plant simulators;

• A minimum of two years of experience with the development and application of simulator engineering codes to the following types of models: thermal-hydraulic, electrical, and control;

• A minimum of two years of experience and proficiency using nuclear power plant simulation commercial tools such as SimExec or TRex, as well as associated simulation variable database and debugging tools;

• Experience using commercial code and applications such as FORTRAN, C++, Access, Visual Studio, and PHP.

• Experience problem solving and troubleshooting performance issues related to complex, interrelated code modules;

• Experience using version control software;

• Strong communication skills and experience delivering technical customer service;

• Basic familiarity with the application of simulator engineering codes to the following types of models: core, neutronics, and severe accident response such as MELCOR, RELAP, S3R, JTopmeret, and REMARK.

• Basic familiarity with interfacing simulator engineering code with full-scope simulator input/output systems; and

• Basic familiarity with developing and maintaining graphical displays and human machine interfaces for commercial nuclear power plant simulators.

C.13.4 Off-Site Simulator Engineering Expert Qualification Requirements

The Contractor shall provide personnel who, in aggregate, have sufficient qualifications to perform the simulator engineering expert support activities specified in this SOW. All simulator engineering expert support personnel shall possess a combination of education/training and experience that demonstrates competence in the programming and maintenance of full-scope power plant simulator software. Competence shall be demonstrated by meeting each of the requirements in Section C.13.2 and the following requirements:

• Demonstrated expertise with the application of simulator engineering codes to the following types of models: core, neutronics, and severe accident response such as MELCOR, RELAP, S3R, JTopmeret, and REMARK.

• Demonstrated expertise with interfacing simulator engineering code with full-scope simulator input/output systems; and

• Demonstrated expertise developing and maintaining graphical displays and human machine interfaces for commercial nuclear power plant simulators.

C.14 Contractor Travel

Except for on-site hardware support, travel to the TTC is anticipated to be infrequent. It may be required for software support functions that cannot be performed off-site, as authorized by COR.

The Government is responsible for reimbursement of the Contractor’s travel costs for on-site software support if asked to travel more than 50 miles. It is not expected to exceed one trip to the TTC with a duration of a full work week (Monday through Friday) per performance period.

Location: NRC Technical Training Center (Osborne Office Center) 5746 Marlin Rd. Suite 200 Chattanooga, TN 37341

C.16 Data Rights

The NRC shall have unlimited rights to and ownership of all deliverables provided under this contract/order, including reports, recommendations, briefings, work plans and all other deliverables. All documents and materials, to include the source codes of any software, produced under this contract/order are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without prior written authorization from the CO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

C.17 Incremental Development for Software

The Contractor shall provide simulator software and all tools necessary to perform software maintenance. Software support shall include software modification activities such as issue identification, troubleshooting, modifications, testing, updates, and software configuration control. The Contractor shall utilize an administrative configuration control system, including processes necessary to ensure proper documentation, traceability, and management of software changes. These activities shall be performed consistent with the related Information and Communication Technology (ICT) requirements, as applicable.

C.18 Section 508 – Information and Communication Technology Accessibility

C.18.1 Introduction

In December 2000, the Architectural and Transportation Barriers Compliance Board (Access Board) pursuant to Section 508(2)(A) of the Rehabilitation Act Amendments of 1998, established electronic and information technology (EIT) accessibility standards for the federal government.

The Standards for Section 508 of the Rehabilitation Act (codified at 36 CFR § 1194) were revised by the Access Board, published on January 18, 2017 and minor corrections were made on January 22, 2018, effective March 23, 2018.

The revised 508 standards have replaced the term EIT with ICT (Information and Communication Technology). ICT is information technology (as defined in 40 U.S.C. 11101(6)) and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to:

Computers and peripheral equipment; information kiosks and transaction machines;

telecommunications equipment; customer premises equipment; multifunction office machines;

software; applications; Web sites; videos; and, electronic content.

The text of the Standards for Section 508 of the Rehabilitation Act can be found in 36 CFR §

1194.1 and in Appendices A, C and D to Part 1194 (https://www.ecfr.gov/current/title- 36/chapter-XI/part-1194?toc=1).

C.18.2 General Requirements

To help the NRC comply with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. § 794d) (Section 508), the Contractor shall ensure that its deliverables (both products and services) within the scope of this contract/order are

1. in conformance with, and

2. support the requirements of the Standards for Section 508 of the Rehabilitation Act, as set forth in 36 CFR § 1194.1 and in Appendices A, C and D to Part 1194.

The Standards for Section 508 of the Rehabilitation Act reference the Web Content Accessibility Guidelines (WCAG) version 2.0, Level A and Level AA Success Criteria and Conformance Requirements. However, it is desirable that the contractor support the latest WCAG version (currently 2.2), when possible.

C.18.3 Applicable Provisions of the Standards for Section 508 of the Rehabilitation Act

The following is an outline of the standards that identifies what provisions are always applicable and which ones may be applicable. If “Maybe” is stated in the table below, then those provisions are applicable only if they are within the scope of this acquisition.

Applicable to the Contract/Order? Provision of 36 CFR Part 1194

Yes 1) Revised 508 Standards http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title40-section11101&num=0&edition=prelim https://www.ecfr.gov/current/title-36/chapter-XI/part-1194?toc=1 https://www.ecfr.gov/current/title-36/chapter-XI/part-1194?toc=1

Applicable to the Contract/Order? Provision of 36 CFR Part 1194

Yes

a) Appendix A to Part 1194 – Section 508 of the Rehabilitation Act:

Application and Scoping Requirements

Yes

i) 508 Chapter 1: Application and Administration - sets forth general application and administration provisions

Yes

ii) 508 Chapter 2: Scoping Requirements - containing scoping requirements (which, in turn, prescribe which ICT – and, in some cases, how many – must comply with the technical specifications)

Yes (see the Exceptions to the Standards section below)

(1) E202 General Exceptions

Yes (see the Other section below)

(2) E203.2 User Needs

Yes (see the Accessibility of

Electronic Content section below)

(3) E205 Electronic Content

See below

b) Appendix C to Part 1194 – Functional Performance Criteria and

Technical Requirements

Yes

i) Chapter 3: Functional Performance Criteria – applies to ICT where required by 508 Chapter 2 (Scoping Requirements) and where otherwise referenced in any other chapter of the Revised 508 Standards

Maybe ii) Chapter 4: Hardware

Maybe iii) Chapter 5: Software

Maybe

iv) Chapter 6: Support Documentation and Services (applicable to, but not limited to, help desks, call centers, training services, and automated self-service technical support) https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.a&rgn=div9 https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.a&rgn=div9 https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.c&rgn=div9 https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.c&rgn=div9

Applicable to the Contract/Order? Provision of 36 CFR Part 1194

Yes

v) Chapter 7: Referenced Standards - the standards referenced here apply to ICT where required by Section 508 Chapter 2 (Scoping Requirements) and where referenced in any other chapter of the Revised 508 Standards

Maybe (see the Legacy ICT section below)

2) Appendix D to Part 1194 – Electronic and Information Technology Accessibility Standards as Originally Published on December 21, 2000

Refer to 508 Chapter 2 (Scoping Requirements) first to confirm what provisions in Appendix C apply in a particular case.

Section E203.2 applies only to the NRC, except as specified below.

C.18.4 Exceptions to the Standards

C.18.4.1 Legacy ICT

Unless a deliverable of this contract/order is identified in this contract/order as Legacy ICT, use by the Contractor of the Legacy ICT general exception (section E202.2 of 36 CFR § 1194) shall only be permitted on a case-by-case basis for applicable legacy ICT and with advance written approval from the COR.

C.18.4.2 National Security Systems

Based on the definition at 40 U.S.C. 11103(a), the National Security Systems general exception (section E202.3 of 36 CFR § 1194) is not applicable to this contract/order.

C.18.4.3 Incidental ICT

ICT acquired by the Contractor incidental to this contract/order shall not be required to conform to the revised 508 standards.

Note: This only applies when the Contractor is procuring the ICT, only the Contractor personnel will access or use the ICT, and ownership of the ICT will remain with the Contractor upon completion of the contract/order.

C.18.4.4 ICT Functions Located in Maintenance or Monitoring Spaces

The Contractor shall confirm with the COR that an ICT deliverable of this contract/order will be located in maintenance or monitoring spaces before assuming that the ICT Functions Located in Maintenance or Monitoring Spaces general exception (section E202.5 of 36 CFR § 1194) https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.d&rgn=div9 https://www.ecfr.gov/cgi-bin/text-idx?SID=8955408cf446edc7ae4a66a5261c22b3&mc=true&node=ap36.3.1194_12.d&rgn=div9 http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title40-section11103&num=0&edition=prelim applies.

Note that this exception does not apply to features of the ICT (such as Web interfaces) that can be accessed remotely, outside the maintenance or monitoring space where the ICT is located.

C.18.4.5 Undue Burden

The Undue Burden general exception (section E202.6 of 36 CFR § 1194) is not expected to be applicable to work performed by the Contractor. If there are questions about potential application of this exception please discuss with the CO.

C.18.4.6 Fundamental Alteration or Best Meets

If the Contractor wishes to use the Fundamental Alteration (section E202.6 of 36 CFR § 1194) or Best Meets (section E202.7 of 36 CFR § 1194) general exceptions the Contractor shall do the following:

1. provide the COR with information necessary to support the agency’s documentation requirements, as identified in sections E202.6.2 and E202.7.1 of 36 CFR § 1194, respectively

2. request and obtain written approval from the COR for development and/or use, as applicable to the scope of the contract/order, of an alternative means for providing individuals with disabilities access to and use of the information and data, as specified in sections E202.6.3 and E202.7.2 of 36 CFR § 1194, respectively.

C.18.5 Additional Accessibility Requirements

C.18.5.1 Notification Due to Impact from NRC Policies, Procedures, Tools and/or ICT Infrastructure

If and when 1) the Contractor is dependent upon NRC policies, procedures, tools and/or ICT infrastructure for standards-conformant delivery of any of the products or services under this acquisition, and 2) the Contractor is aware that conformance of products or services will be negatively impacted by capability gaps in NRC policies, procedures, tools and/or ICT infrastructure, the Contractor shall inform the COR so that the NRC can both be aware and take corrective action.

C.18.5.2 Accessibility of Electronic Content

At a minimum, the standards require electronic content that is Public Facing or Agency Official Communication (as defined in sections E103 and E205.3 of 36 CFR § 1194, respectively) to be conformant with section E205.4 of 36 CFR § 1194.

• Public Facing content: Content made available by an agency to members of the general public.

• Agency Official Communication. Electronic content that is not public facing, when such content constitutes official business and is communicated through one or more of the following:

a. An emergency notification;

b. An initial or final decision adjudicating an administrative claim or proceeding;

c. An internal or external program or policy announcement;

d. A notice of benefits, program eligibility, employment opportunity, or personnel action;

e. A formal acknowledgement of receipt;

f. A survey questionnaire;

g. A template or form;

h. Educational or training materials; or

i. Intranet content designed as a Web page.

However, if not Public Facing nor Agency Official Communication the NRC may still have a requirement that the electronic content deliverable be conformant with section E205.4 of 36 CFR § 1194, but only if the deliverable is identified in this contract/order as having the requirement to be accessible.

The NRC may choose, for its own reasons, to take responsibility for the final conformance of an electronic content deliverable or a class of electronic content deliverables by explicitly identifying the deliverable or class of deliverables through one of the following means:

1. Identified in this contract/order, or

2. Identified in writing to the Contractor by the COR, with a copy to the CO.

C.18.5.3 Other

It is desirable that the contractor address the applicable accessibility requirements from the very beginning of the design and…