PWS_DRAFT.docx

PERFORMANCE WORK STATEMENT (PWS)

1. Contract or Task Order Title. Virtual Reality Training for a Gas Turbine Generator

2. Background.

Pearl Harbor Naval Shipyard & Intermediate Maintenance Facility (PHNSY&IMF) is developing its workforce in surface ship and submarine repair and maintenance. Elevating technical competence through training directly enhances shipyard capability, operational efficiency, and safety.

3. Objectives:

PHNSY&IMF requires a Contractor to develop and build a Virtual Reality (VR) training system leveraging commercial-off-the-shelf (COTS) technology for the use of a gas turbine generator. The Contractor shall deliver this system, complete with instructional animations to maximize and improve operational readiness and maintenance capabilities across all platforms. The VR animations must be user-driven and built according to specifications in the PWS.

4. Scope.

The Contractor shall provide all management, labor, transportation, tools, and equipment for the delivery of the VR hardware and VR software training system solution identified in the PWS. The delivery of the software training system must be completed by Close of Business (COB) November 1, 2027. Annual software and hardware maintenance for the system is required.

5. Performance Requirements.

5.1 TASK: VR Software Development (Standalone Training)

The Contractor shall:

a) Ensure all new software development uses modern software development methodologies (e.g., agile, Development, Security, and Operations (DevSecOps)) for rapid delivery of standardized, reliable, integrated and secure mission capabilities.

b) Gather system requirements, develop the architecture, design, integrate and test software modules and field the software for use by the PHNSY&IMF user community. Contractor shall:

1. Provide at least one (1) visit to PHNSY&IMF to facilitate software development.

2. Ensure VR software technical requirements are approved by and for Government use;

3. Ensure VR software training system (developed instructions and part of software subscription) is compatible and compliant with equipment authorized for use by PHNSY&IMF, Code 109;

4. Ensure VR software system has software protections for Controlled Unclassified Information (CUI) level data;

5. Ensure any photo, video, and three-dimensional (3D) scanning, if required to develop the training system, has compliant labeling and marking to expedite review process with PHNSY&IMF, Code 1120;

6. Include Department of Navy (DoN) specifications for the Gas Turbine Generator (450-480VAC);

7. Include the Auxiliary fuel tank environment and the Gas Turbine Generator environment in the software training system at minimum;

8. Include onsite procedures for use of the Gas Turbine Generator, including onsite procedure document and environment capture;

9. Include step-by-step procedures with real-time misstep detection for the Gas Turbine Generator, which consists of:

· Safety procedures;

· Set-up procedures;

· Pre-operational procedures;

· Manual startup procedures;

· Operational procedures;

· Manual shutdown procedures;

· Hand signals pertinent to the Gas Turbine Generator;

10. Include interactive gauges and indicators;

11. Include anomaly and troubleshooting scenarios for advanced proficiency;

12. Include multi-user capabilities for 4-5 simultaneous users in shared VR sessions.

c) Develop and build the VR software training system based on system requirements for use by the PHNSY&IMF user community. VR training shall include:

1. VR software requirements that are approved by and for Government use;

2. VR software (developed instructions and part of software subscription) that is compatible and compliant with equipment authorized for use by PHNSY&IMF, Code 109;

3. Software protections for CUI level data;

4. Photo and video with compliant labeling and marking approved by PHNSY&IMF, Code 1120;

5. 3D virtual model of the Gas Turbine Generator;

6. DoN specifications for the Gas Turbine Generator (450-480VAC);

7. Auxiliary fuel tank environment and Gas Turbine Generator environment;

8. Onsite procedures for use of the Gas Turbine Generator;

9. Step-by-step procedures with real-time misstep detection for the Gas Turbine Generator. Training instructions shall include:

· Safety procedures;

· Set-up procedures;

· Pre-operational procedures;

· Manual startup procedures;

· Operational procedures;

· Manual shutdown procedures;

· Hand signals pertinent to the Gas Turbine Generator

10. Interactive gauges and indicators;

11. Anomaly and troubleshooting scenarios for advanced proficiency;

12. The delivery of the software content must be completed by COB November 1, 2027.

d) Ensure that the software/application is free from all computer viruses, worms, time-outs, time bombs, back doors, disabling devices and other harmful or malicious code intended to or may damage, disrupt, inconvenience or permit access to the Software user's or another's software, hardware, networks, data or information. Notify the Government within 30 minutes of malicious activity embedded within one of the contractual deliverables.

e) Establish formal software development, code control and build processes for major and minor (patches) releases and full integration.

1. Track all revisions in the VR software training system;

2. Provide software configuration management of modifications.

f) Ensure the VR training system can be installed and operated by following these steps:

1. Validate VR training system and its instructions to verify accuracy and completeness in accordance with PWS requirements.

2. Modify VR training system and instructions upon Government request.

g) The Contractor shall provide a report detailing the nature of the services performed; upgrade modifications and other pertinent information concerning the condition of the equipment to Government. The Contractor shall submit the report within 10 business days after delivery of the software training system on November 1, 2027.

h) Option Year 1: Contractor shall provide

1. A Government Cloud solution that includes environment setup, hosting, and networking of the VR training approved by Government.

2. A collaborative training workshop for multi-users and capabilities for 4-5 simultaneous users in shared VR sessions compliant with Information Leve 5 (IL5) environment approved by Government.

TASK 6.1: VR Software Development

Software Development Task Elements-

a) Build VR software training system according to Task 6.1 PWS requirements and deliver by November 1, 2027

Performance/ Deliverables:

· 100% delivery of the VR software training content by November 1, 2027 and;

· Compliance with Task 6.1 PWS requirements

Inspection of delivered training system

5.2 TASK: VR Hardware

The Contractor shall:

a) Deliver five (5) Trade Agreements Act (TAA)-compliant HTC Vive Focus Vision VR headsets compatible with the VR training software solution provided by the Contractor. Hardware has 12-month manufacturer warranty.

b) Headsets shall have separate login accounts for admins and general users;

c) Ensure headsets are in working condition during delivery handoff to the Government;

d) Include all necessary VR headset accessories, such as dongles, hard carrying cases, and similar accessories that are required for the VR headset to operate with the training solution and to protect headset from physical damage to the Government;

e) Provide Government help with the setup, use, care, and operation of the headset.

f) Option Year 2: Contractor shall provide annual maintenance for VR headsets, as well as software and content updates.

g) Option Year 2: Contractor shall provide annual IL5 GovCloud hosting and networking support.

TASK 6.2: VR Hardware and Accessories

VR Hardware Task Elements:

a) Delivery of 5 TAA-compliant HTC Vive Focus Vision VR headsets

b) Headsets have separate login accounts for admins and general users

c) Headsets are in working condition

d) All VR headset accessories are included

e) Instructions with the setup, use, care, and operation of the headset was provided Performance/ Deliverables:

All 5 performance standards (a-e) were met

Inspection of delivered hardware and accessories

Deliverables:

6. Performance Standards.

Task 5.1: Software Development

Task Elements-

a) Build VR software training system according to Task 6.1 PWS requirements and deliver by November 1, 2027

Performance/Deliverables:

· 100% delivery of the VR software training system by November 1, 2027 and;

· Compliance with Task 6.1 PWS requirements

Calculation:

Upon inspection of delivered training system, system is operable and meets all Task 6.1 PWS requirements

Task 5.2:

VR Hardware and Accessories

a) Delivery of 5 TAA-compliant HTC Vive Focus Vision VR headsets

b) Headsets have separate login accounts for admins and general users

c) Headsets are in working condition

d) All VR headset accessories are included

e) Instructions with the setup, use, care, and operation of the headset were provided

Upon inspection of completed delivery of hardware and accessories,

· HTC Vive Focus Vision VR headsets are TAA-compliant and accessories provided;

· VR headsets work with appropriate login accounts;

· VR headset setup, use, care, and operation were provided by the Contractor.

6. Place of Performance.

Mission Location: Pearl Harbor Naval Shipyard & Intermediate Maintenance Facility located at Joint Base Pearl Harbor Hawaii.

Place of Performance: The Contractor shall develop the VR training system at the Contractor’s facility.

If required, perform 3D scanning at Government facility (Pearl Harbor Naval Shipyard), related to the Gas Turbine Generator, 450-480VAC Navy Specification.

Local travel to and around the mission location may be required throughout the period of performance; this travel will not be reimbursed. Long distance travel outside CONUS may be required for the requirements of this PWS. Long distance travel outside CONUS must be pre-approved in writing by the COR prior to the Contractor incurring the cost under this contract.

7. Period of Performance.

1 year after contract/TO award and 2 option years.

PHNSY&IMF regular working hours are between 6:30 AM (0630) 3:30 PM (1530) Monday through Friday. Additionally, the PHNSY&IMF will be closed from Dec 25th through January 1st.

Recognized Federal Holidays: The contractor is not required to perform services on Federal Holidays (as specified on the U.S. Office of Personnel Management website), unless otherwise specified by the COR.

Unplanned Federal Government Closure: In the event an authorized official, by either executive or legislative order, declares Federal offices closed (treated as a holiday for pay and leave purposes), the order only applies to Federal employees (unless otherwise stated in the order).

8. Security Requirements.

The Contractor shall pass a background check to gain access onto the base. The contractor will coordinate with PHNSY & IMF to obtain a gate pass at building 3455 Pass Office. It is not unusual for the pass process to take an hour or more. Contractor must be a U.S. Citizen and must pass a security background check. Only those individuals with favorable investigations shall be utilized on this contract. Prior to the start of work, the Contractor shall provide the COR (on company letterhead) a request for access and include the following information – full name of all personnel working on this contract; Social Security number; date of birth, place of birth, and citizenship. The Contractor shall state that information has been verified and shall have supporting records on file, if required for examination. Contractor’s employees must be a U.S. Citizen and registered with the Defense Biometric Identification System.

8.1 Contractor personnel must meet the requirements for unescorted entry, green badge, to PHNSY&IMF areas. Escorted access to CNIAs and NWAs must be coordinated with the cognizant Department Security Coordinator to ensure that the area is sanitized and the escort is properly briefed/knowledgeable of the area. The Contractor shall follow the applicable requirements listed below in “APPENDIX III - CONTRACTOR SECURITY REQUIREMENTS FOR PHNSY&IMF’S CONTROLLED INDUSTRIAL AREA, CONTROLLED NUCLEAR INFORMATION AREAS, NUCLEAR WORK AREAS AND/OR OTHER SENSITIVE AREAS 6-2021” and brief their personnel to ensure compliance. Non-compliance with applicable items in Attachments is a material violation of the contract. Should Contractor personnel receive or suspect they have learned unauthorized sensitive information, they shall identify and immediately report suspicions to the Government.

8.2 Should Contractor personnel receive or suspect they have learned of classified information beyond their level of clearance, the Contractor shall identify and report suspicions to the Government.

8.3 When performing work associated with this PWS, the Contractor shall make clear to all individuals they deal with that they are contract employees and not DOD employees.

8.4 Contractor employees shall clearly identify themselves as a Contractor (i.e. company shirt, pin, visible company identification) in a visible location on the front of exterior clothing and above the waist, (except when safety or health reasons prevent such placement) as to who their employer is. Identification badges shall be worn at all times when performing work, including while attending Government meetings and conferences that may take place outside the facility.

9. Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI).

9.1 GENERAL. The Government will provide the following services listed below:

a. FACILITIES. The Government will provide access to the affected work areas. The Government will provide electrical 110V wall outlets. Any damage that results from exceeding the rated circuit capacity of the outlets shall be borne by the Contractor.

10. Other Pertinent Information or Special Considerations. Specialized experience with using the HTC Vive Focus Vision and creating VR training modules. Familiarity with the naval shipyard environment is preferable.

a. Identification of Possible Follow-on Work. Upon completion and acceptance of the VR training solution created by Contractor, optional year tasking for training configuration at Government information level 5 will be exercised.

b. Identification of Non-Disclosure Requirements. The contractor shall obtain and maintain Non-Disclosure Agreements (NDA) for each employee assigned to the contract/TO. Initial NDAs shall be signed within one week of contract/TO award, and NDAs shall be kept current through the entirety of the period of performance as employee turnover occurs. The contractor shall ensure that all employees assigned to the contract have executed NDAs on file as of the date of the Monthly NDA Status Report, which shall include names and NDA status of all current employees assigned to the contract.

c. Supply Chain Risk Management (SCRM).

This contract and its associated delivery/task orders are subject to the Federal SCRM policies and regulations including DFARS 252.239-7017 Notice of Supply Chain Risk, DFARS 252.239-7018 Supply Chain Risk, DoD Instruction 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks, Section 806 of theFY2011 NDAA Requirements for Information Relating to Supply Chain Risk, and internal DISA SCRM Processes and Procedures.

The contractor shall submit a SCRM plan as part of its technical proposal that describes how the contractor will reduce and mitigate Supply Chain Risk using the security controls outlined below (further described in CNSSI 1253, Appendix D and NIST SP 800-53), as applicable to your contract.

Control Enhancement Name

DELIVERABLES:

SUPPLY CHAIN RISK MANAGEMENT PLAN UPDATE: The contractor shall provide an updated SCRM Plan to the COR and Program Manager within five (5) business days whenever there is a change that affects one or more security controls as described in the Committee on National Security Systems Instructions (CNSSI) 1253 Appendix D (companion publication to National Institute of Standards and Technology (NIST) Special Publication (SP)). At a minimum, the following events will require a SCRM Update: changes in company ownership, changes in senior company leadership, supplier changes, subcontractor changes, and Information and Communications Technology (ICT) supply chain compromises.

d. Training. Contractor employees may be required to take periodic mandatory training courses provided through the agency, such as records management training, Controlled Unclassified Information (CUI) training, and other training required by statute, regulation, DoD, or DISA policy. No other training of contractor personnel shall be provided by the Government unless authorized by the Contracting Officer.

e. Internet Protocol version 6 (IPv6). (CORs must certify when developing task orders against a DISA contract.) . The IPv6 compliance assessment will make an affirmative statement that the assessment has been performed and identify the applicable criteria listed below. Once the compliance assessment has been performed, the COR will retain the IPV6 compliance assessment with their Task Order (TO) requirements package checklist in their COR files.

(1) Internet Protocol (IP) Convergence efforts: This is a general requirement applicable to any effort where considerations for IPv6 (vs. IPv4) are identified in the task statement. There could be direct references using phrases such as "IP Convergence" or more generic phrases used in tasks focused on Internet transport networks that are based on Transmission Control Protocol/Internet Protocol (TCP/IP). There could also be direct references to DoD networks or programs such as the Defense Information System Network (DISN), Unclassified but Sensitive IP Router Network (NIPRNet), Secret IP Router Network (SIPRNet), DoD Teleport System (a collection of telecommunications capabilities and distribution points), and/or the Global Information Grid (GIG).

(2) Information Assurance (IA) and security related efforts: This is a general requirement applicable to any effort containing an IA component, especially if there is a requirement to inspect network traffic.

(3) Voice over IP and other real-time services efforts: Self-explanatory.

(4) Application layer services especially if the application relies upon Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS) and/or other services that are related to IP: Self-explanatory.

(5) DoD Information Technology Standards: This is a general requirement related to the DOD Information Technology Standards Registry (DISR) and/or Internet Engineering Task Force (IETF) Request for Comments (RFCs). As a rule of thumb, if a program has to abide by RFCs, it is likely to have to consider the IPv6 impact.

(6) Global Grid Forum efforts: This is a general requirement directly or indirectly related to the Global Grid Forum that is defining Grid computing standards (e.g., future grid-based networking) that has established the rules for "IP version independence", i.e., they do not want to use IPv4 hooks that would preclude IPv6 in the future or make it more difficult to migrate/transition to.

11. Section 508 Accessibility Standards.

E205.1 General. Electronic content shall comply with E205.

E205.2 Public Facing. Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

E205.3 Agency Official Communication. Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:

1. A. An emergency notification;

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

1. C. An internal or external program or policy announcement;

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

1. E. A formal acknowledgement of receipt;

1. F. A survey questionnaire;

1. G. A template or form;

1. H. Educational or training materials; or

1. I. Intranet content designed as a Web page.

E205.4 Accessibility Standard (WCAG 2.0). Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (Incorporated by reference, see 702.10.1).

E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents. For non-Web documents, wherever the term "Web page" or "page" appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term "document" shall be substituted for the terms "Web page" and "page". In addition, in Success Criterion in 1.4.2, the phrase "in a document" shall be substituted for the phrase "on a Web page".

E206 Hardware

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207 Software

E207.1 General. Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5.

Exception from E207.1 General: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

E208 Support Documentation and Services

E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E301 General E301.1 Scope. The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

503 Applications

503.1 General. Applications shall conform to 503.

602 Support Documentation

602.1 General. Documentation that supports the use of ICT shall conform to 602.

603 Support Services

603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

603.2 Information on Accessibility and Compatibility Features. ICT support services shall include information on the accessibility and compatibility features required by 602.2.

603.3 Accommodation of Communication Needs. Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

12. Cybersecurity Maturity Model Certification (CMMC)

This contract and its associated delivery/task orders are subject to the Federal CMMC policies and regulations including DFARS 204.371 Cybersecurity Maturity Model Certification, DFARS 252.204-7021 Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements, and 32 CFR §170, Cybersecurity Maturity Model Certification (CMMC) Program. The CMMC Program is designed to ensure implementation of cybersecurity practices for defense contractors and to provide DoD with increased assurance that Federal Contract Information (FCI) and CUI will be adequately safeguarded when residing on or transiting contractor information systems.

Enclosure 4a, PWS Page 1 of 11 Pages 2015/Version 9