PWS_RA_Final.docx

Performance Based Statement of Work Future Fleet Wargames – Post Wargame Experimentation and Analysis Systems Engineering Dept.

Naval Postgraduate School

1.0 Background/Introduction:

The NPS educational research team is working to develop an experimentation environment based on an executed computer assisted exercise (CAE). The CAE will first be transformed into an automated computer assisted wargame (CAW). TThe NPS research team has received permission from PACOM to use the Cobra Gold 2018 (CG18) scenario and database. This CAE will be the analytical backbone for the automated CAW and the planned experimentation environment for N9. CG18 utilizes the Joint Theater Level Simulation (JTLS) as the primary modeling and simulation (M&S) program to train over 5,000 military personnel from joint and coalition commands.

In transforming the CAE into an automated CAW, the NPS research team requires the technical knowledge and training associated with the JTLS from the publisher of JTLS. The results of this project will provide the Navy's N9 Warfare Systems Directorate with innovative methods to analyze the composition of the future fleet. The experimentation environment enables the Directorate to insert new capabilities in the CG18 scenario (which includes numerous Navy and Marine operations) and examine how they impact mission success. Such studies provide analytics for the naval community to develop credible cost positions during budgetary debates. The vision for this project is to conduct research for the Future Fleet Wargames.

2.0 Scope:

JTLS focused contractor support is required for technical consultation, knowledge share, and support of the NPS developed CAE. The contractor shall provide technical consultation and support of the decision matrices that will be a critical foundation of the automated orders in JTLS. Concentration includes, but is not limited to, retracing the CAE and sectioning of the CAE into a CAW. The contractor shall support the NPS developed preliminary design of software that will interface with the contractor’s proprietary existing JTLS software. The contractor shall technically assist and support the NPS development, testing, and retesting of the CAW based on a reconstruction of CG18.

3.0 Tasks:

Contractor support will be utilized to understanding JTLS operations and to unravel the CAE after it is executed. The NPS team must “piece” the exercise together as a CAW and will need the technical expertise and consultation of the contractor. All contractor support shall be actionable, and support the progress toward an automated CAW and an experimental environment.

The contractor shall provide technical support and expert consultation to the NPS development team for constructing an automated CAW from the JTLS CAE, CG18. The contractor shall provide continuous training, education on the technical aspects of simulation operations and orders generation, construction of the exercise architecture for implementing JTLS, as well as in the development of scenario databases.

3.1 The contractor shall provide JTLS technical expertise and consultation in support of the following:

3.1.1 access to JTLS inner workings, documents, databases, scenario development tools, and data analysis

3.1.2 consultation to address technical questions from the NPS development team

3.1.3 access to workspace in vendor facilities to operate and study JTLS

3.1.4 technical knowledge to NPS students in the operations of JTLS to support sponsored research thesis work

3.2 Technically assist with the installation and configuring JTLS-GO on a NPS single, stand-alone computer to serve as a testbed for the closed-loop simulation environment. This testbed will be used to test current, modified, and newly developed software tools that will be needed to programmatically (no human-in-the-loop; also known as "batch") modify the simulation input and extract desired output and define the template for the final closed-loop simulation. The contractor shall provide knowledge share and document the installation and configuration specifications.

3.3 Software Support and Assistance: Technically support and assist with the development of new software tools, modifying current tools, to programmatically modify simulation input and extract simulation output. Modifying JTLS-GO flat files and Oracle database input. The contractor shall document and;

3.3.1 The contractor shall write software (code/scripts) that can be run in batch and from the command line, and to set up the foundation for running multiple, concurrent instantiations of the closed-loop simulation over a distributed computing network. To include assisting with developing code/scripts to merge output from multiple excursions and runs into a single data warehouse to ease analysis.

3.3.2 The contractor shall assist with the NPS development of new software tools to take input from the exercise and translate automatically into a form, either JTLS-GO flat files or database tables, that can be used by the closed-loop simulation environment, including orders and other exercise input, as required, to convert the CAE into a usable CAW.

3.4 Provide technical guidance on JTLS inputs that would be both feasible to automate and of high relevance/importance to the analytic goals of the exercise. The contractor shall consult and technically assist the SEED Team in determining the set of factors (variables) to be used in the experimental design(s) that are used to transform the exercise into a closed-loop simulation. The consultation and technical assistance shall provide guidance on which section(s) to automate for the post-exercise analysis, including specifics on how to implement. All consultation, guidance, developed factors, and sections shall be documented.

3.5 Upon development of the NPS SEED Team’s experimental design(s), the contractor shall provide technical assistance with understanding any dependencies between the inputs in the experimental design and other simulation inputs/parameters.

3.6 Technical consultation and assistance in identifying and extracting the most relevant output metrics. To include context and other knowledge of high-level decisions or recommendations that were made at CG18 as a result of being shown CG18 output.

3.7 Simulation consultation, technical support, and expertise for the NPS SEED Team development and testing of the closed-loop simulation and experimental framework, provide input on the results obtained, to support verification and validation activities. Support shall also be given to the NPS SEED team works through the mechanics of turning the exercise scenario and supporting database into an automated environment.

4.0 Deliverables:

The cntractor shall be responsible for providing the following deliverables:

4.1 All technical support and consultation in regards to the contractor published JTLS shall be documented in a mutually agreed upon editable format.

4.2 Most recent version of JTLS for installation at NPS on a single computer, all user, installation, and configuration associated documentation. The fully installed testbed system. The contractor shall fix all bugs and provided any updates.

4.3 All software code, modified code, tools, and simulations in support of tasks 3.3, 3.3.1, 3.3.2. Deliverables are to be documented, saved, and stored on Government provided drives and files.

4.4 CG18 complete scenario database; coordinated with PACOM and PWC. All data collected and documentation resulting from CG18 shall be on a mutually agreed upon editable format. Contractor shall document all game decisions, orders, and decisions matrices.

4.5 All technical guidance, discussions, and consultation in regards to task 3.4 and the automation of the JTLS order shall be documented in a mutually agreed upon editable format.

4.6 Documentation of all technical support and identified dependencies referenced in task 3.5 to include records of CAE checkpoints and corresponding documents for wargame development.

4.7 Identification and extraction of output metrics to include all updated to JTLS from the findings from CG18 in accordance with task 3.7 in a mutually agreed upon editable format.

4.8 All support given to the NPS SEED team shall be documented and address the elements of tasks 3.7. All steps and mechanics of the exercise and automation must be documented.

Performance Measurement - Quality Assurance Plan

3.2 Assist with installing and configuring JTLS-GO on a single, stand-alone computer to serve as a testbed for the closed-loop simulation environment. This testbed will be used to test current, modified, and newly developed software tools that will be needed to programmatically (no human-in-the-loop; also known as "batch") modify the simulation input and extract desired output. It will also be used to define the template for the final closed-loop simulation.

Professional Academic Quality Course Materials in the agreed upon format

100% Inspection of Deliverables

Once a month

3.3

Assist with developing new software tools, or modifying current tools, to programmatically modify simulation input. This includes modifying JTLS-GO flat files as well as Oracle database input. The goal of this task is to write software (code/scripts) that can be run in batch and from the command line, and to set up the foundation for running multiple, concurrent instantiations of the closed-loop simulation over a distributed computing network.

Completion of task.

Verify reasonable output values based on input. Subject matter expertise on naval operations will provide assessment.

As needed

3.4

Assist with developing new software tools, or modifying current tools, to programmatically extract simulation output. This includes extracting data from the Oracle database or other output files. The goal of this task is to write software (code/scripts) that can be run in batch and from the command line. If output is in a database, assist with developing code/scripts to merge output from multiple excursions and runs into a single data warehouse to ease analysis

Completion of task

Verify 100 % of data extraction on parsed data. reflect information that exists in simulation reports such as an air tasking order or situational report.

3.5

Assist with developing new software tools to take input from the exercise and translate automatically into a form, either JTLS-GO flat files or database tables, that can be used by the closed-loop simulation environment.

This would include orders and other exercise input, as required, to convert the CAE into a usable CAW.

Completion of task

Verify that automated data input will result in reasonable JTLS orders. Recorded JTLS exercise provides actual orders that can be compared with the automated order generation tool.

As needed, but no less than twice a month

3.6

3.7

Post-exercise, provide guidance on JTLS inputs that would be both feasible to automate and of high relevance/importance to the analytic goals of the exercise. This guidance will help the SEED Team determine the set of factors (variables) to be used in the experimental design(s) that are used to transform the exercise into a closed-loop simulation. Additionally, provide guidance on which section (for example, 12-18 hour period) to automate for the post-exercise analysis, including specifics on how to implement.

Test recommended factors with available information from JTLS database and CG18 recordings. This is an ongoing dialogue that refines the period that the team will automate.

3.8

Once the SEED Team develops the experimental design(s), provide assistance with understanding any dependencies that may be involved between the inputs in the experimental design and other simulation inputs/parameters. For example, if a simulation input is changed via the experimental design at time t, how does this affect embedded orders/scripts that resulted from the CG18 simulation exercise after time t? Are there other dependencies/constraints to consider?

Verify that 100% of all changes in the experimental design translates to changes in CG18 database parameters and that ensuing orders are reasonable based on the input data.

3.9

Provide assistance in identifying and extracting the most relevant output metrics. This assistance should include context and other knowledge of high-level decisions or recommendations that were made at CG18 as a result of being shown CG18 output.

Verify that extracted 100% of information matches available information from CG18 recording.

3.10

As the SEED Team develops and tests the closed-loop simulation and experimental framework, provide input on the results obtained, to support verification and validation activities. Additionally, provide simulation expertise, as needed, as the SEED team works through the mechanics of turning the exercise scenario and supporting database into an automated environment.

Verify that extracted 100% of information matches available information from CG18 recording.

If performance falls below the AQL defined above, the Contracting Officer’s Representative (COR) shall document the instance(s), coordinate with the Contracting Officer and advise the Contractor. The Contractor will be requested to review the documentation and provide a written response on how performance will be corrected in the future. Re-performance of any work for failure to perform in accordance with the specified AQL or task requirement shall be completed at the Contractor’s own expense and at no additional cost to the Government.

5.0 Minimum Technical Requirements:

· Must have 10 years of experience with JTLS

· Must have served as senior technical controller in a JTLS exercise within the last 2 years

· Must be a senior database engineer

6.0 Period of Performance: From date of award – December 31, 2018

7.0 Place of Performance:

The contractor must perform on-site at NPS in Monterey, California. The contractor shall have facilities within Monterey, California for the Government to collaborate about the JTLS.

8.0 Government Furnished Property:

The Government will provide all existing data collected to be used in the performance of this requirement. The testbed computer will be Government equipment the contractor will utilize in task 3.2 and will remain in Government possession. The contractor will be given access to Government provided storage for the deliverables, software development, and all documentation.

9.0 Work Week and Hours of Operation:

The Contractor shall provide services during normal working hours excluding federal holidays. Normal working hours are 0730-1630, Monday through Friday, unless requirements dictate otherwise. Exceptions can be permitted by the COR upon request and at the COR’s discretion.

Following is a list of holidays observed by the Government.

If any of the above holidays occur on a Saturday or a Sunday, then such holiday shall be observed by the Contractor in accordance with the practice as observed by the assigned Government employees at the using activity

10.0 Travel: Not Applicable

Travel will be in accordance with the Joint Travel Regulations (JTR) and will be reimbursed by the government on an as-incurred basis.

11.0 Transition Activities:

It is essential to the Government that services required under this PWS are performed without interruption. At the conclusion of any performance period, including option periods or extensions, the services provided under this PWS may be awarded to another contractor. The contractor in place shall be required to assist in the transition activities.

12.0 Security Requirements: Unclassified

Contractor Key Personnel must be U.S. Citizens.

Contractors performing on this contract are required to familiarize themselves with, and participate in, the Naval Postgraduate School’s OPSEC program. Must be familiar with and comply with NPSINST 3432.1B, the NPS Critical Information List, DOD Directive 5205.02E and their applicable references. The contractor will be required to complete OPSEC and counter-intelligence training within 30 days of beginning the work, or provide proof of OPSEC and counterintelligence training completed within the previous 12 months. The contractor may not publicly release any information about developmental work or curriculum at NPS without prior written approval from the Principal Investigator (PI).

13.0 Human Subject Research:

Contractor personnel performing work under this contract may not support, advise, or conduct research involving human subjects. If at any time during the period of performance of this contract the tasks involve human subject research, the Contractor shall immediately notify the Contracting Officer. The contract must be amended in accordance with DoDD 3216.02 and DFAR 252.235-7004 in the event human subject research is proposed.

14.0 Privacy Act Statement:

“Pursuant to Title 5 United States Code 552a(m)(l), the contractor and all employees of the contractor working under this contract are required to comply with the requirements of 5 U.S.C. 552a (“The Privacy Act of 1974”).”

15.0 Identification of Contractor Employees:

In accordance with DFAR 211.106, there shall be a clear distinction between Government employees and service contractor employees. Service contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel. Contractor personnel will be required to obtain and wear badges or other visible identification for meetings with Government personnel to provide a clear distinction between service contractor employees and Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

16.0 Non-Personal Services Statement:

Contractor employees performing services under this order will be controlled, directed, and supervised at all times by management personnel of the contractor. Contractor management will insure that employees properly comply with the performance work standards outlined in the SOW. Contractor employees will perform their duties independent of, and without the supervision of, any Government official or other Defense Contractor. The tasks, duties, and responsibilities set forth in the task order may 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, or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will control access to the facility and will perform the inspection and acceptance of the completed work.

17.0 SUPTXT 204-9400 Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (Jan 2017)

Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type Memorandum (DTM) 08-006 – “DoD Implementation of Homeland Security Presidential Directive – 12 (HSPD-12)” dated November 26, 2008 (or its subsequent DoD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.

APPLICABILITY

This clause applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DoN or DoD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information, provide support associated with fiduciary duties, or perform duties that have been identified by DON as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.

Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

ACCESS TO FEDERAL FACILITIES

Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Navy Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.

ACCESS TO DOD IT SYSTEMS

In accordance with SECNAV M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information Assurance Manager.

Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation, which is a higher level investigation than the National Agency Check with Law and Credit (NACLC) described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor.”

The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

INTERIM ACCESS

The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

DENIAL OR TERMINATION OF ACCESS

The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

CONTRACTOR’S SECURITY REPRESENTATIVE

The contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity’s Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE DUTIES Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non-Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:

· SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

· Original Signed Release Statements

Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the Command’s Security Manager upon arrival to the command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Employees requiring IT access shall also check-in and check-out with the Navy Command’s Information Assurance Manager. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date.

The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take JPAS “Owning” role over the contractor employee, the Navy Command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc.) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:

· Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and

· Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.

To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:

· SF-85 Questionnaire for Non-Sensitive Positions

· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

· Original Signed Release Statements

The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM

Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

* Consult with your Command Security Manager and Information Assurance Manager for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.

Office of Contracting and Logistics Management Revised 04 Aug 17