RFQ Amendment N0018926QL2020001 Conformed.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3

AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

Solicitation/Contract Form Continuation

Persistent Cyber Training Environment (PCTE) Support

N0018926QL2020001

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Base Year - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

Option Year I - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

Option Year II - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

Option Year III - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

Option Year IV - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

FAR 52.217-8 - Persistent Cyber Training Environment Services shall be provided in accordance with the PWS.

Pricing Arrangement: Firm Fixed Price

6 Months

Continuation of Description

Performance Work Statement

Naval Information Warfighting Development Center (NIWDC) Persistent Cyber Training Environment (PCTE)

1. SCOPE OF WORK:

Naval Information Warfighting Development Center (NIWDC) desires service to maintain and or develop virtual training in support of the CNO's visions for Live, Virtual, and Constructive (LVC) training environments to provide network and software engineering support, and to leverage contractor subject matter expertise (SME) to advise and train NIWDC Warfare Tactics Instructors, staff, and exercise participants using virtual training development (VTD/PCTE) or LVC.

2. ADMINISTRATIVE:

2.1 WORKING HOURS:

Working hours are Monday through Friday between the hours of 0730 and 1730 local time.

2.2 HOLIDAYS:

The contractor is generally not required to provide services on these days.

New Year's Day Labor Day

Martin Luther King Jr.'s Columbus Birthday Day

President's Veteran's Day Day

Memorial Day Thanksgiving Day

Juneteenth Christmas Day

Independence Day

3. PLACE OF PERFORMANCE:

3.1 Primary Government Facilities:

Work performed in accordance with this PWS shall be at Naval Information Warfare Advanced Weapons School (NIWAWS) at Northwest Annex, Building 14 in Chesapeake, VA; the Naval Information Warfighting Development Center and its subordinate Mission Areas (MAs): NIWDC Headquarters location, Naval Support Activity Hampton Roads (7941 Blandy Road, Building NH-139, Norfolk, VA 23551); and the Naval

.Information Warfare Training Group Norfolk HQ, Little Creek (2555 Amphibious Drive, Virginia Beach, VA 23455)

3.2 Telework Authorization:

In accordance with FAR 7.108, the Government does not discourage the use of telework for the execution of this contract. While the primary physical locations are listed in Section 3.1, the Contractor may utilize telework arrangements for its personnel to perform eligible tasks, provided all security, performance, and deliverable requirements are met.

3.3 GFE and Network Dependency:

The Government acknowledges that Contractor personnel performing via authorized telework are dependent on the availability, connectivity, and performance of Government-Furnished Equipment (GFE) and Government-managed networks (e.g., Virtual Desktop Infrastructure [VDI] and VPNs).

The Government retains responsibility for ensuring that provided GFE and networks are suitable for their intended use.

3.4 Excusable Delays & Outage Reporting:

In the event of GFE hardware failure, Government network outages, or VDI degradation that prevents teleworking Contractor personnel from performing their duties, the Contractor shall notify the Contracting Officer's Representative (COR) via email within two (2) hours of the initial outage.

Documented and properly reported downtime caused by Government infrastructure failures shall constitute an excusable delay. The Contractor shall not be held financially liable for missed milestones or idle time directly resulting from verified Government system unavailability.

3.5 Contractor Responsibilities:

The Contractor remains solely responsible for ensuring its teleworking employees maintain continuous, adequate commercial internet service provider (ISP) connectivity and a suitable physical workspace. Outages caused by the Contractor's local ISP or residential power failures do not constitute an excusable delay under this clause.

4. SECURITY REQUIREMENTS:

SECURITY: The CONTRACTOR SHALL be responsible for adhering to all DOD, Department of the Navy, and specific Command instructions, guidance, orders, directives, and supplements relative to performing tasks set forth in this PWS. The CONTRACTOR SHALL not disclose and must safeguard procurement sensitive information, computer systems and data, Privacy Act data, and Government personnel work products that are obtained or generated in the performance of this contract. This includes dissemination of protocols and papers not generally available through the public literature. Neither the CONTRACTOR nor any of its contract service providers SHALL disclose or cause to disseminate any information concerning operations of military activities. Such action(s) could result in violation of the contract and possible legal actions.

The contractor is responsible for acquiring and maintaining security clearances at the level(s) required under this contract. All positions in the PWS require a TOP SECRET / SENSITIVE COMPARTMENTED INFORMATION (TS/SCI) clearance as designated on the Contract Security Classifications Specifications (DD254). The contractor shall pre-clear new employees prior to starting on the contract and must obtain clearance validation from the command security office in order to obtain a security badge. Information systems used by contractor personnel shall be operated in accordance with DOD 5220.22-M National Industrial Security Program Operating Manual (NISPOM). Contractor personnel shall comply with Department of Defense, Department of Navy and local installation security requirements.

The government will provide access to information and data on an 'as needed' basis. The Contractor may require access to a wide range of IW related documentation in meeting the requirements of this PWS ranging in classification from UNCLASSIFIED to TS/SCI. The Government will grant contractor personnel access to Government furnished information only after contractor personnel have signed a Non-Disclosure Agreement. Access to classified information must be granted in accordance with the terms and conditions contained in DOD Manual 5220.22-M National Industrial Security Program Operating Manual and DD Form 254 (Contract Security Classifications Specifications).

All information / documentation provided to or developed by a contractor to assist in the performance of their task shall be considered the property of the Government and will be returned to the designated representative or technical point of contact (TPOC) upon completion of the task.

The Contractor shall be responsible for obtaining any and all Government-issued identification cards from employees who are no longer authorized or no longer have a requirement for access to Government facilities and systems. Identification cards shall be collected immediately (within one hour) of change of employee status. Government-issued identification cards must be turned over to the respective Command Security Officer or TPOC within two (2) business days.

Contracting companies awarded a Contract as part of this effort SHALL not:

1) Brand (or make any references to award) on their corporate (private or public facing) web site(s), any information that references any of the following information:

-Award of Contract

-Location(s) of performance

-Duration of performance

-Type(s) of work performed

-Government customer name(s)

-Contract, CONTRACTOR personnel end strength(s)

2) Advertise award of Contracts via any media outlet (or by any other means) to anyone, including:

-Corporate stock holders

-Banks, or other Investment firms

-Any contract employee that does not possess a valid need to know, e.g., (a) any contract employee that is not physically assigned to a position on an awarded contract, (b) any prospective (not yet hired) contract employee, or (c) any contract employee that is not assigned to handle Logistics, Facility Security, Payroll, Travel, or Human Resources working in a role directly supporting CONTRACTOR personnel working as a part of this effort.

Contracting companies awarded a Contract as part of this effort SHALL deliver onboarding Contract CONTRACTOR information, to the Contracting Officer Representative (COR) NLT 96 hours before reporting to the Contract site. Incoming CONTRACTOR information SHALL be sent via Signed and Encrypted email, and SHALL contain the following information on each incoming CONTRACTOR:

a) Company Name

b) Full Name

c) Date of Birth

d) Contract Position assigned

e) Social Security Number

f) Level of Clearance

g) Email Address

h) Phone Number

Access will be granted to Government facilities as required in support of the tasking. CONTRACTOR personnel performing work under this contract must meet all requirements for gaining access to US Government installations. The CONTRACTOR SHALL conform to all DoD, DoN, and local (base/installation) security instructions (refer to CONTRACTOR Unclassified Access to Federally Controlled Facilities, Sensitive Information, provided below).Information Technology (IT) Systems or Protected Health Information (July 2013)

The scope of work requires access to TOP SECRET/SENSITIVE COMPARTMENTED INFORMATION (TS/SCI) access for specified personnel.

CONTRACTOR personnel SHALL have the appropriate security clearance as of the first day of the period of performance. The following SHALL be considered before assigning any/all proposed CONTRACTOR staff as a part of any contract:

-Personnel who possess TS/SCI clearance SHALL currently be fully adjudicated, and eligible for transfer in status, upon report on first day of Contract /Contract award. Interim TS//SCI clearances SHALL NOT be accepted for any position

-Personnel who possess Final TS/SCI clearances SHALL be registered in DISS and/or JPAS by the CONTRACTOR's company, before the CONTRACTOR reports to his/her prospective Contract work location, NLT 96 hours in advance

-CONTRACTOR personnel who possess Final TS//SCI clearances SHALL NOT be sent to any command if they are reflected as "RED" in DISS /JPAS e.g. if they have been flagged as having an issue with their clearance

-Contracting company's Program Manager(s), and/or Facility Security Officer's SHALL initiate contact to work with the COR, to develop DD-254 forms, NLT 96 hours before any Contract CONTRACTOR personnel arrive on site to start work

-Contracting Program Manager(s), and/or Facility Security Officer's SHALL ensure that all incoming Contract CONTRACTOR personnel have had their Common Access Cards (CAC) from their last job REVOKED, NLT 48 hours before directing them to contact NAVIFOR Trusted Agents (TA) for issuance of new CAC credentials

All work is to be performed in accordance with DOD and Navy Operations Security (OPSEC) requirements and in accordance with the OPSEC attachment to the DD254.

All building security identification badges SHALL be turned into the SSO that issued the credential, and all CAC cards SHALL be turned into the COR that issued the credential, if the CONTRACTOR employee departs during normal daytime working hours. In the event that the CONTRACTOR employee checks out at the end of an evening, or mid shift, then both the building security badge, and the CAC credential, SHALL be turned over to the CONTRACTOR's Government lead before final departure, as the CONTRACTOR IS REQUIRED to "read out/be debriefed" regarding their clearance, by the servicing SSO, before their departure e.g. they will have to physically come in during normal working hours on the next SSO work day.

The CONTRACTOR SHALL comply with all applicable federal, state and local laws and ensure performance is secure while protecting material, equipment, and supplies from damage and loss. Government security personnel SHALL have the express right to inspect work spaces, email accounts, and operating systems, for security violations at any time during the term of the contract.

The CONTRACTOR SHALL be responsible for safeguarding all government equipment, information and property provided for CONTRACTOR use.

At the close of each work period, government facilities, equipment and materials SHALL be secured.

The Government CONTRACTOR CAC card serves as the primary method of identification for the CONTRACTOR employees, as well as providing the basis of Public Key Infrastructure (PKI) access to the Navy/Marine Corps Intranet (NMCI), and numerous Navy web sites, which may also require PKI access. The COR SHALL assist in providing the CONTRACTOR the appropriate documentation for obtaining CAC cards. The CONTRACTOR SHALL be responsible for obtaining any Government issued identification cards from former employees or employees whose access has been terminated off of the Government site and to turn those items over to the COR upon termination of employment or access.

Contract personnel SHALL wear a badge that clearly identifies them as a CONTRACTOR employee. The badge will be issued by the COR, via the Special Security Office (SSO), and will contain a personal picture, name of employee, and CONTRACTOR's name. While working on the Government site, CONTRACTOR employee badges SHALL be worn on the outer garment, above the waist, in full view at all times, attached to the outer shirt or jacket pocket by a button or clip or worn around the neck secured by an appropriate identification card lanyard.

CONTRACTOR personal SHALL not, at any time, access or attempt to access the following from Government IT assets:

a) Corporate Email Accounts

b) Personal Email Accounts

c) Corporate Portals

d) Any Social Networking Site

e) Any Web Based News Site

f) Any Music Streaming Media Site

g) Any Web Based site, that does not directly relate to the assigned job, task, or mission

5. PRIVACY ACT COMPLIANCE:

The CONTRACTORs may be in contact with data and information subject to the Privacy Act of 1974 (Title 5 of the U.S. Code Section 552a). The CONTRACTORs SHALL ensure that its employees assigned to this effort understand and adhere to the requirements of the Privacy Act and to Department of Defense and Department of the Navy regulations that implement the Privacy Act. Department of Navy policy and procedures implementing the Privacy Act are detailed in SECNAVINST 5211.5E (Department of the Navy Privacy Act (PA) Program). The CONTRACTORs SHALL identify and safeguard data, information and reports accordingly. In addition, the CONTRACTORs SHALL ensure that CONTRACTORs employees assigned to the contract are trained on properly identifying and handling data and information subject to the Privacy Act prior to commencing work.

6. GOVERNMENT FURNISHED INFORMATION:

GFI will be provided to CONTRACTOR employees as needed to complete the tasks set forth in this performance work statement. Access to classified information must be granted in accordance with the terms and conditions contained in DOD Manual 5220.22-M and DD Form 254 (Contract Security

Classification Specification). The CONTRACTOR SHALL comply with all current information assurance awareness, information security policies, procedures, and statutes applicable to DOD information technology; including the July 3, 2007 DOD CIO Policy Memorandum on Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage.

7. GENERAL/ADMINISTRATIVE MATTERS:

CONTRACTOR SHALL only conduct business with designated government personnel listed as points of contact (POCs). Names of authorized personnel SHALL be provided to the CONTRACTOR by the government COR, in writing, and updated as necessary throughout the contract period.

All inquiries, comments or complaints arising from any matter observed, experienced, or learned of as a result of or in connection with the performance of this contract, the resolution of which may require the dissemination of official information, SHALL be directed to the COR and the Contracting Officer (KO).

STAFFING: The CONTRACTOR SHALL provide a fully qualified work force on the first day of contract performance.

All contract personnel attending meetings, answering Government telephones, and working in other situations where their CONTRACTOR status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by CONTRACTOR are suitably marked as CONTRACTOR products or that CONTRACTOR participation is appropriately disclosed. Additionally, they must clearly indicate on email title blocks their company name and that they are CONTRACTOR personnel. Specifically, contracting companies who perform on the contract SHALL ensure that their CONTRACTOR staff identify themselves in the following manner:

1) Phone - CONTRACTOR personnel SHALL answer the phone clearly and succinctly stating:

a) First and last name

b) That they are a CONTRACTOR, who is working for "X" command, and the capacity in which they perform

2) Email - CONTRACTOR personnel SHALL have a title block, on ALL internal and external email conversations, which clearly and succinctly states:

a) First and last name

b) Contracting company

c) Work telephone number

d) Capacity in which they perform

3) Meeting attendance - CONTRACTOR SHALL identify themselves by announcing, either spoken or via attendance sheet, their:

a) First and Last Name

b) Contracting Company name

c) Their role in the meeting

STAFFING REPORT: The CONTRACTOR SHALL provide a staffing report to the COR monthly. The staffing report SHALL be in a format prescribed by the CONTRACTOR, but at a minimum, SHALL address the percentage of Contract staffing, and whether those objectives were or were not achieved. If not achieved, the circumstances preventing the accomplishment of the objective SHALL also be provided.

STAFFING LEVELS: CONTRACTOR SHALL maintain consistent Contract staffing levels exceeding 90%, for the entire base year, as well as 90% for all option years, executed against each individual Contract award.

DATA RIGHTS: It is the government's intent to retain unlimited rights to all software, documentation, and data first produced in performance of the task.

U.S. Government records, copies of original results and reports, verified original data, corrected data, and corrected supporting final reports are maintained by the CONTRACTOR, but remain the property of the U.S. Government. These files/results must be surrendered to the COR immediately upon demand.

CONTRACTOR QUALITY ASSURANCE: The CONTRACTOR SHALL develop and maintain a Quality Assurance Plan (QA Plan) to ensure only qualified personnel, as stipulated in Section 3, are assigned to fulfill the requirements stated in this PWS. The CONTRACTOR SHALL detail in its quality assurance plan how it intends to maintain personnel qualifications and ensure contract employees have up-to-date training and knowledge in their respective areas of endeavor.

This QA Plan SHALL detail the methodology to be used by the CONTRACTOR to monitor and grade the performance of its personnel as they carry out the requirements of this PWS. The QA Plan SHALL address the CONTRACTOR's courses of action to address under-performing employees.

GOVERNMENT QUALITY ASSURANCE SURVEILLANCE: The Government SHALL evaluate the CONTRACTOR's performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the CONTRACTOR is performing in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

COMPLAINTS LOGGED AGAINST CONTRACTOR PERSONNEL: If a complaint is made regarding the conduct or ability of CONTRACTOR personnel, the individual receiving the complaint will contact the COR. The COR will notify the CONTRACTOR Lead. The Contract PM Lead and COR will cooperate in investigating complaints made against CONTRACTOR employees. If the results of the investigation prove the complaint(s) to be valid, the CONTRACTOR Lead SHALL have a maximum of three (3) working days to propose a corrective plan for resolving the matter and preventing future similar occurrences. This plan SHALL be submitted in writing to the Contracting Officer and COR. In the event that the Government deems the corrective plan insufficient for resolution of the problem, a written response to the CONTRACTOR Manager SHALL be provided within three (3) working days.

OFFICE SPACE: The Government will provide workspace, desk, chair, and common office supplies. In addition to workspace, each CONTRACTOR employee SHALL be provided with access to government computers and telephones, but not cellular phones, for official use only. Under no circumstances will CONTRACTOR-provided personal computers, or any personal electronic devices (e.g., cell phones, tablets, Fitbits), be connected to any Government IT system, including but not limited to the Navy/Marine Corps Intranet (NMCI). CONTRACTOR personnel SHALL comply with all DOD and Navy IT regulations, policies and procedures including those concerning internet usage and cybersecurity.

STATEMENT OF NON-PERSONAL SERVICE: CONTRACTOR employees performing services under this contract will be controlled, directed, and always supervised by management personnel of the CONTRACTOR. CONTRACTOR management SHALL ensure that employees properly comply with the performance work standards outlined in the PWS. CONTRACTOR employees SHALL perform their duties independent of, and without the supervision of, any Government official. The tasks, duties, and responsibilities set forth in this contract SHALL not be interpreted or implemented in any manner that results in any CONTRACTOR employee creating or modifying Federal policy, obligating the appropriated funds of the United States Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR) http://farsite.hill.af.mil/vffar1.htm . The Government SHALL control access to the facilities and SHALL perform the inspection and acceptance of completed work.

OBJECTIVE: The objective of this effort is to procure non-personal CONTRACTOR support services under a single contractual Contract.

8. SUPPORT SERVICES/QUALIFICATIONS/DUTIES:

This PWS provides for services and support of these lines of operation that include both short term and annual support in some or all the following CO tasks. Part of this tasking, based on the nature of NIWDC mission, may include deliverables at the TS-SCI level. They include but are not limited to:

8.1 Task I - PCTE Development: The Contractor shall provide expertise and assistance in the development of operational procedures, and advanced tactical IW Cyberspace Operations training events. Support shall include assisting the CO MA with but not limited to/by:

8.1.1 - The Contractor shall participate in VTD/PCTE/PCTE-related planning conferences and exercises/events.

8.1.2 - The Contractor shall provide subject matter expertise to NIWDC in developing training curriculum.

8.1.3 - The Contractor shall develop, validate, document, and deliver constructive, interactive, and virtual models for use in VTD/PCTE analysis and test exercises/events.

8.1.4 - VTD/PCTE subject matter expertise for all supported missions, support to the planning and execution of VTD/PCTE-related exercises/events to facilitate and ensure appropriate representation of USN and Joint capabilities consistent with all applicable military service doctrine, DoD directives, authoritative guidance, and DoD regulations.

8.1.5 - The Contractor shall support product development, evaluations and create recommendations for the acceptance of instructor-led and self-paced training supporting NIWDC-sponsored cyber/IT-related courses.

8.1.6 - Subject matter expertise of planning processes by which all VTD/PCTE-related training exercises are developed following specified timelines.

8.1.7 - Subject matter expertise at the planning and execution of Government-selected event(s) leveraging VTD/PCTE.

8.1.8 - Prepare, document, and maintain after action reports (AAR) for each event supported.

8.1.9 - Apply specialized subject matter expertise of VTD/PCTE systems in the community and identify operational use cases to further increase efficiency and assessment accuracy.

8.1.10 - The contractor shall provide configuration management of any deliverable supplied to the Government to ensure stability and consistency of the training products.

8.1.11 - Given a specified configuration requirement (i.e., a specific U.S. ship or shore-based local area network configuration) supporting an operational or training need, the Contractor shall manage and adjust system (virtual) configuration to satisfy the operational need according to stated measures of effectiveness.

8.1.12 - The Contractor shall provide technical and engineering services to install and integrate new and existing simulators and simulations, equipment, and other training and support equipment onto the VTD/PCTE physical and virtual systems as required.

8.1.13 - The Contractor shall provide engineering and technical support in conducting training systems and software test and evaluation of all operational and functional aspects of VTD/PCTE simulations, simulators, and equipment.

8.1.14 - The Contractor shall be responsible for documenting and delivering the required customer documentation, to include, but not limited to user's guides, release notes, etc.

8.1.15 - The Contractor shall deliver all software code and deliverables implemented for each release and ultimately, prior to the end of the contract period of performance for review/acceptance by the Government.

8.1.16 - All source code deliveries and documentation artifacts, for all software developed in support of VTD/PCTE, shall be submitted to the Government by the Contractor unless otherwise directed. The Contractor must include all the necessary artifacts (i.e., build instructions, installation and configuration instructions, executable files, etc.) and a delivery form indicating individual changes. Individual deliveries will be inspected for completeness and conformity.

8.1.17 - All deployments shall be coordinated with Government officials and/or VTD/PCTE customers to ensure standard operating procedures of the identified command (e.g., NIWDC, etc.) are followed.

8.1.18 - The Contractor shall work with Government personnel to optimize the performance of the existing system and services.

8.1.19 - The Contractor shall assist with coordinating the training delivery schedule consistent with product selection and the approved fielding schedule.

8.1.20 - The Contractor shall assist NIWDC with identifying and assessing training support requirements, computer-based training (CBT) modules, scenario/Master Scenario Events List (MSEL) development, table-top exercises, and/or other training materials that will ensure user proficiency and product/equipment supportability and effectiveness.

8.1.21 - The Contractor shall assist NIWDC in preparing and conducting workshops, seminars, and study groups directly pertaining to leveraging VTD /PCTE capabilities.

8.1.22 - The Contractor shall conduct post exercise effectiveness analysis and evaluations on all cyber-related exercises leveraging VTD/PCTE capabilities.

8.1.23 - The Contractor shall provide lessons learned input to NIWDC, as well as any Navy or other Joint Service components, Service Headquarters, or any Federal, State, and local Government organizations participating in and conducting integrated operations leveraging VTD/PCTE as required by the Government POC. These lessons learned programs will be designed, developed, executed and managed as directed by the Government.

8.2 Task II - Fleet Support: The Contractor shall provide expertise and assistance in the development of operational procedures, and advanced tactical IW Cyberspace Operations training events. Support shall include assisting the CO MA with but not limited to/by:

8.2.1 - Review intelligence analysis on threats impacting CO to support Urgent Operational Needs Statements (UONS).

8.2.2 - Day-to-day management of assigned tasks and projects. Coordinate efforts with DoD, Service, Federal, and Agency Research Centers as needed to meet advanced training requirements.

8.2.3 - Perform analysis of adversary Offensive CO capability and development of tactics to mitigate threats and exploit adversary vulnerabilities.

8.2.4 - Perform CO readiness analysis in support of HBSS, ESS, ACAS, and VRAM operational requirements, to include scenario development for Strike Group Optimized Fleet Response Plan (O-FRP) cycles.

8.2.5 - Develop strategic concepts and advanced exercises for HBSS, ESS, ACAS, and VRAM capabilities aligned with current Navy tactics and operations.

8.3 Task III - Fleet CO and WTI Training: The Contractor shall provide support, assistance, and analysis for identifying and documenting Fleet CO training requirements. This support shall include assisting the CO MA with but not limited to/by:

8.3.1 - Develop event cards / training for basic, intermediate, and advanced exercises (AE) including but not limited to the following areas:

Department of Defense Information Network (DODIN) OPS, Defensive Cyberspace Operations (DCO), Assured Compliance Assessment Solution (ACAS), Host Based Security System (HBSS), Endpoint Security Solution (ESS), and Vulnerability Remediation Asset Manager (VRAM), Deliverables will include AE and event card scenarios in required format with referenced documentation NTTPs / NTAs / XMs required for training and assessment.

8.3.2 - Conduct target training audience analysis (needs assessment) for HBSS, ESS, ACAS, and VRAM, including traditional classroom instruction and pier side training. Identify specific target audience training requirements associated with rank, existing experience level(s), and assigned work role (s), to include: Warfare Tactics Instructor (WTI) candidate formal instruction, pier side/ Fleet basic and advanced training, Information Professional (IP) Basic training, Independent Deployer Assessment Training (IDAT), and Train the Trainer events for Fleet Training Agents.

8.3.3 - Develop, refine, and provide advanced Fleet HBSS, ESS, ACAS, and VRAM training in support of: WTI candidate formal instruction, pier side / Fleet basic and advanced training, Information Professional (IP) Basic training, IDAT, and Train the Trainer events for Fleet Training Agents.

8.3.4 - Coordinate with major Fleet training stakeholders to assess, analyze, and implement CO training improvements which align across the Optimized Fleet Response Plan (O-FRP).7.2.5 - Provide threat capabilities analysis to support advanced CO WTI training.

8.3.5 - Identify critical OFRP advanced training deficiencies for current and developing capabilities.

8.3.6 - Provide HBSS, ESS, ACAS, and VRAM subject matter expertise to coordinate with major research, laboratory, and training stakeholders to support and implement Fleet Synthetic Training and other training systems for use at the unit and battle group levels.

8.3.7 - Provide HBSS, ESS, ACAS, and VRAM subject matter expertise to Fleet exercises including consultation on how to expand the role of HBSS, ESS, ACAS, and VRAM and better utilize existing capabilities and incorporate emerging technology advancements.

8.3.8 - Provide HBSS, ESS, ACAS, and VRAM subject matter expertise to Fleet exercises to include participation onboard Navy bases.

8.3.9 - Coordinate with major research stakeholders and Space and Naval Warfare Systems Command (SPAWAR) for the development of training and advanced tactics related to emerging HBSS, ESS, ACAS, and VRAM equipment technology advancements.

8.3.10 - Coordinate with other Training Agents and Warfighting Development Centers to develop, implement, review and validate existing and emerging HBSS, ESS, ACAS, and VRAM Training Continuum.

8.3.11 - Develop and establish a training event feedback mechanism to collect student / trainee input, enabling continuous training improvement and instructional material and delivery method refinement.

8.3.12 - Research and develop the following ESS-specific topics for afloat training initiatives: ePO, permissions management, policy management, McAfee / Trellix Agent, McAfee / Trellix Endpoint Security, Rogue System Detection (RDS), Policy Auditor (PA), disaster recovery, data loss prevention (DLP), maintenance, Endpoint Security (ENS) Threat Prevention (TP) - including Access Protection, Exploit Prevention, On-Access Scan, On-Demand Scanners, and Adaptive Threat Prevention (ATP) - ENS Firewall (FW) Web Control, cybersecurity, analysis, dashboard management, and Nessus.

8.4 Task IV - Experimentation/Doctrine: The Contractor will provide support, assistance, and analysis for the CO experimentation process and development of CO doctrine. This support shall include assisting the CO MA with but not limited to/by:

8.4.1 - Collaborate with CO community subject matter experts and key stakeholders to gather insights and perspectives on doctrinal requirements and /or updates to SYSCOM and the Fleet.

8.4.2 - Identify gaps or deficiencies in existing HBSS, ESS, ACAS, and VRAM doctrine and propose mitigative solutions.

8.4.3 - Develop, update, or validate doctrine to include CONOPs, TAMEMO, NTTP, NTRP, TACBUL or theoretical works as needed to support training, AEs, or tactics, including but not limited to the following areas: DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM, or as needed to meet fleet demand signals.

8.4.4 - Provide analytical work, such as gap analysis related to DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM or as needed to meet Fleet demand signals.

8.4.5 - Author and revise HBSS, ESS, ACAS, and VRAM doctrine, policy, and preplanned responses designed to reconcile identified gaps.

8.4.6 - Review and update Joint and Naval doctrine pertaining to HBSS, ESS, ACAS, and VRAM.

8.4.7 - Produce HBSS, ESS, ACAS, and VRAM tactical decision aids, tailored analyses, and other documents to support deployed and Forward Deployed Naval Forces (FDNF).

8.4.8 - Research and develop the following ESS-specific publications (e.g., NTRP, TACBULs, or TACMEMOs) to support operational mission and afloat personnel: ePO, permissions management, policy management, McAfee Agent, McAfee Endpoint Security, Rogue System Detection (RDS), Policy Auditor (PA), disaster recovery, data loss prevention (DLP), maintenance, Endpoint Security (ENS) Threat Prevention (TP) - including Access Protection, Exploit Prevention, On-Access Scan, On-Demand Scanners, and Adaptive Threat Prevention (ATP) - ENS Firewall (FW) Web Control, cybersecurity, analysis, dashboard management, and Nessus.

8.4.9 - Conduct simulations, exercises, or tabletop exercises to test and evaluate the effectiveness and applicability of HBSS, ESS, ACAS, and VRAM-related doctrine, ensuring alignment with Fleet requirements and operations.

8.5 Task V - Readiness Reporting: The Contractor shall provide technical support, assistance, and training for readiness reporting tools that provide the Navy's readiness statuses. This support shall include assisting the CO MA with but not limited to/by:

8.5.1 - Input data into Defense Readiness Reporting System-Navy (DRRS-N).

8.5.2 - Defining and refining the Navy Mission Essential Task (NMET) within the DRRS-N System.

8.5.3 - Defining and refining the Navy Tactical Tasks (NTA) within DRRS-N to include RE, CE, and XM alignment with required doctrine and training.

8.5.4 - Reviewing and revising DRRS-N and any follow-on readiness reporting tool to effectively and accurately report CO readiness.

8.5.5 - Recommendations for development of a follow-on readiness reporting tool.

8.5.6 - CO readiness reporting, doctrine and requirements within Operational Capabilities/Projected Operational Requirements (ROC/POE).

8.6 Task VI - Cyberspace Operations Mission Area Directorate Support:

8.6.1 - Participate in weekly staff planning meetings, briefings, and VTCs as required. Attend meetings, conferences, and workshops regarding current and future doctrine/requirements, advanced tactics development, and systems integration. Contractor will attend meetings, conferences, and workshops for informational purposes only and not as an official representative of NIWDC. This may include weekly ship visits to local ports to validate Fleet requirements and Navy doctrine.

8.6.2 - When requested, the Contractor shall prepare and maintain a Plan of Action and Milestones (POA&M) and oral briefings with visual aids (power point slides) to update command leadership on current initiatives and deliverables.

8.6.3 - Develop a monthly report that documents contractor performance measures that allow NIWDC to assess progress against its plans and mission priorities.

Labor Categories

Labor Categories Clearance Location Number of Personnel

Sr. Software Engineer TS/SCI Hampton Roads 2

TOTAL 2

III - Subject Matter Expert (C2/CO):

Experience: Minimum twelve (12) years of recent experience in CO preferred, to include performing responsibilities at the Navy Enlisted E-6 or above. Shall have knowledge and understanding of applicable technical concepts and practices in order to support CO readiness across DOTMPLF (Doctrine, Organization, Training, Materiel, Personnel, Leadership, and Facilities).

Education: Bachelor's Degree preferred. Twelve years of additional CO experience may be substituted for bachelor's degree or equivalent cyber security workforce certificates S+, N+, CISSP, CCNA, CASP etc.

Master Training Specialist preferred.

Clearance: TS/SCI clearance required.

9. TRAVEL REQUIREMENTS:

There are no travel requirements for this contract.

10. DELIVERABLES:

The Government and the CONTRACTOR SHALL jointly establish due dates specific to individual work products (ex., drafts of documentation identified in the Scope of Work section, reports, presentations, analysis, etc.). Deliverables SHALL be prepared in CONTRACTOR's format where not otherwise specified by the Government. Deliverables SHALL be provided to the COR. All final deliverable submissions SHALL remain the property of the U.S. Government. All revisions will be due in the specified timeframe as identified by the Government. All methodologies and recommendations SHALL be reviewed and approved by the Government prior to submission/implementation.

CONTRACTOR QUALITY ASSURANCE PLAN: Due within 30 days of period of performance start date and updated annually thereafter (refer to General/Administrative Matter Section).

MONTHLY STATUS REPORT: The CONTRACTOR SHALL provide the COR a monthly In Progress Review (IPR) no later than the 20th day of the month. The IPR SHALL be a formal review whereby the CONTRACTOR will discuss matters such as project requirements, current and planned project activities, contract personnel status, and problems encountered or anticipated that may impact scheduling. The report SHALL contain the following information at a minimum:

a. Task/project status (include originator/customer, personnel assigned to complete, goal/end-state, estimated completion date, percent complete)

b. Personnel issues

c. Upcoming impacts to contract support

d. Anticipated activity for next reporting period

PERSONNEL: During the first ninety days of performance, the CONTRACTOR SHALL make no substitutions of personnel unless the substitution is necessitated by illness, death, or termination of employment. The CONTRACTOR SHALL notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide any necessary information. After the initial 90-day period, the CONTRACTOR SHALL submit the information to the Contracting Officer at least 15 days prior to making any permanent substitutions for any CONTRACTOR personnel. No personnel substitutions will be executed without Government approval by the COR.

SPECIFIC WORK PRODUCTS: The following specific work products are anticipated to be delivered by the CONTRACTOR to the Government during the base period of performance.

This list does not constitute a definitive list of all work products to be delivered.

Specific Deliverable Title Due date

Contract staff will develop cyberspace operations-based scenarios and lessons within the VTD/PCTE/PCTE environment.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Develop VTD/PCTE/PCTE-related courseware and updates as required IAW the Performance Work Statement, as needed by the Government.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Technical development and design documentation, test plans, specification and procedures.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Plan of Action and Milestones (POA&M) Briefs (updates as appropriate) ISO VTD/PCTE/PCTE training development.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Training workshop, seminar and study group materials related to VTD/PCTE/PCTE Human/Computer Interface (HCI) as directed by COR or government POC.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Post exercise analysis and evaluations (lessons learned) for cyber-related events and warfare tactics instructor training courses.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Monthly / Quarterly Integrated Master Schedule for VTD/PCTE/PCTE usage.

Monthly / Quarterly as agreed at tune if assignment.

Draft within 3 to 6 months and final product within 9 to 12

Develop or update WTI Cyberspace Operations (CO) Baseline, and Advanced blocks of instruction including blocks of instruction including but not limited to the following areas, DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM, or as needed to meet Fleet demand signals.

months. Continue to revise as required.

Priority of training topics to be agreed upon at time of assignment.

Develop or update Doctrine to include Concept of Operations (CONOP), Tactical Memorandums (TAMEMO), Concepts of Employment (CONEMP), NTTPs, NTRPs, TACBUL, or theoretical works as need to support CO training, AEs or tactics, including but not limited to the following areas, DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM, or as needed to meet Fleet demand signals.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of AEs to be agreed upon at time of assignment.

Develop or update basic, intermediate and advanced exercises (AE) including but not limited to the following areas:

DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM. Deliverable will include AE scenarios in required format with referenced documentation (e.g., NTTPs / NTAs / XMs) required for training and assessment.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of AEs to be agreed upon at time of assignment.

Support basic, intermediate and advanced CO exercises (AE) including but not limited to the following areas DODIN OPS, DCO, ACAS, HBSS, ESS, and VRAM. Deliverable will include AE scenarios in required format with referenced documentation (e.g., NTTPs / NTAs / XMs) required for training and assessment.

Support shipboard, underway, or worldwide training and exercises as assigned.

Develop gap analysis and deliverables PO&M related to Fleet training and implementation of tactics including but not limited to the following areas: DODIN OPS, DCO, ACAS, HBSS, ESS and VRAM, or as needed.

Draft within 3 to 6 months and final product within 9 to 12 months. Continue to revise as required.

Priority of documents to be agreed upon at time of assignment.

Support cybersecurity and shipboard/shore network capability-related meetings and discussions on a weekly basis, or as required. Specific meetings to include named exercises (TRIDENT WARRIOR XX) or operational processes (CPCONS etc.).

Weekly, or as agreed at time of assignment.

Develop CO MA capability related technical reports, conference minutes, briefing material, monthly status reports (MSR), and supporting documentation, as required to support the mission.

Monthly, or as agreed at time of assignment.

Participate in meetings relevant to CO MA mission requirements. Provide after action reports (AAR), as required.

As assigned meetings attendance requires.

STAFFING REPORT: The CONTRACTOR SHALL provide a staffing report to the COR monthly. The staffing report SHALL be in a format prescribed by the CONTRACTOR, but at a minimum, SHALL address the percentage of Contract staffing, and whether those objectives were or were not achieved. If not achieved, the circumstances preventing the accomplishment of the objective SHALL also be provided.

MONTHLY FINANCIAL REPORT: The Monthly Financial Report SHALL be submitted not later than 10 business days after end of the month reported on. The report SHALL contain the following information at a minimum:

a. Current month travel expenses per trip and contract to date travel expense

b. Invoices submitted but not paid

Deliverable Product Format: All reports and documentation will be developed using recent versions of Adobe Acrobat, Microsoft Office Professional Products to include Word, Excel, PowerPoint, etc. unless otherwise specified by the COR. Electronic submission SHALL be made via email, unless otherwise agreed upon with the COR. Oral status reports may also be requested periodically.

The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the CONTRACTOR accepted proposal. In the event of a rejected deliverable, the CONTRACTOR SHALL be notified in writing by the COR of the specific reasons for rejection. The CONTRACTOR SHALL have five (5) workdays to correct the rejected deliverable and return it per delivery instructions.

11. SERVICE CONTRACT REPORTING (SCR):

The CONTRACTOR SHALL report required SCR data fields using the SCR section of the System for Award Management (SAM) at following web address: Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year https://sam.gov/SAM/.

(FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31…