DRAFT JNWC IV Basic IDIQ Work Statement.pdf

UNCLASSIFIED

IDIQ WORK STATEMENT

WORK STATEMEMENT

WORK STATEMENT (WS)

FOR

JOINT NAVIGATION WARFARE CENTER IV IDIQ

DRAFT date: 6 April 2022

Revision History Version Description Date Draft Original Work Statement 6 April 2022

TABLE OF CONTENTS

1.0 DESCRIPTION OF REQUIREMENT: JOINT NAVIGATION WARFARE CENTER

(JNWC) SUPPORT AT KIRTLAND AIR FORCE BASE (AFB), NEW MEXICO

2.0 OVERVIEW OF REQUIREMENT

3.0 MANAGEMENT

4.0 GENERAL INFORMATION

5.0 HOURS OF WORK

6.0 BASE CLOSURE/GOVERNMENT MORALE AND RECREATIONAL

ACTIVITIES

7.0 CONTRACT TRANSITION

8.0 DELIVERABLES

9.0 REQUIREMENTS SUMMARY

10.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

11.0 PRODUCT OWNERSHIP

12.0 PROPRIETARY DATA

13.0 DATA RIGHTS

14.0 ENVIRONMENTAL SAFETY AND HEALTH

15.0 SECURITY REQUIREMENTS

16.0 WORK LOCATION AND ACCESS TO GOVERNMENT PROPERTY AND

FACILITIES

17.0 TRAINING

18.0 GOVERNMENT OFFICE PRODUCTIVITY SOFTWARE

19.0 REIMBURSEMENTS

1.0 DESCRIPTION OF REQUIREMENT: JOINT NAVIGATION WARFARE CENTER

(JNWC) SUPPORT AT KIRTLAND AIR FORCE BASE (AFB), NEW MEXICO

1.1 Background: The Joint Navigation Warfare Center (JNWC) is the Department of Defense (DoD) center of excellence for Navigation Warfare (NAVWAR). The JNWC exists to provide NAVWAR operational support to the joint warfighter; conduct operational assessments of mission-level operations that use positioning, navigation and timing (PNT) information and Tactics, Techniques, and Procedures (TTPs) in threat-representative environments; conduct NAVWAR engineering and analysis at mission, system and platform level; formulate NAVWAR policy and requirements; and collect and retain NAVWAR information.

1.2 The JNWC mission is to enable PNT superiority for the DoD, interagency partners, and the coalition. The JNWC executes three lines of effort to accomplish its mission: create NAVWAR knowledge for PNT superiority, operationalize PNT superiority, and institutionalize PNT superiority. Create NAVWAR knowledge for PNT superiority consists of conducting PNT operational field assessments; participating in command post and exercises conducted by other commands, participating in field events or observing field events conducted by other commands, performing engineering studies and analysis;, analyzing data provided by other personnel; assessing and disseminating intelligence;

maintaining an online Armory of NAVWAR information and tools at various levels of classification; and maintaining a central repository of DoD NAVWAR data.

Operationalize PNT superiority consists of providing NAVWAR planning and operations subject matter expertise to Combatant Commanders (CCMD), Services, interagency and coalition partners (as needed) to achieve PNT superiority. Institutionalizing PNT superiority consists of advocating DoD-wide activities to fully integrate NAVWAR into military policy, doctrine and operations and the future force structure in order to achieve PNT superiority. The JNWC is a joint Department of Defense organization within U. S.

Space Command (USSPACECOM) and as such, operates using established joint DoD processes. Contractor support is needed to support all three lines of effort and to provide basic mission support services to the organization.

1.3 The JNWC customer base includes joint and coalition operators and war fighters, deliberate and crisis action planners, mission planners, tactics developers, system developers, policy makers, trainers, testers, model/simulation users and developers, leadership personnel and interagency partners responsible for US national Critical Infrastructure/Key Resources (CI/KR).

1.4 On behalf of USSPACECOM, the JNWC provides oversight and coordination of USSPACECOM NAVWAR task priority issues among the DoD, governmental agencies, coalition and allied nations. The JNWC provides direct NAVWAR support to the warfighter, conducts field assessments of warfighter systems, equipment and operations, provides standards for NAVWAR analytical tools and methods, and integrates NAVWAR in formation, expertise, and analysis support across the assigned customer base. The JNWC Director reports to the Commander, Combined Force Space Component Command

- (CFSCC), and serves as the Commander's principal advisor and subject matter expert on

NAVWAR.

1.5 Objective: This contract is a research and development services acquisition. All support provided shall comply with Title 10, United States Code, Section 2383 (10 U.S.C. 2383), Defense Federal Acquisition Regulation Supplement, Procedures, Guidance, and Information subpart 207.503 (DFARS PGI 207.503), and Department of Defense Instruction 1100.22 (DoDI 1100.22), which pertain to inherently governmental functions.

1.5.1 This contract is designed to ensure, when possible, that contractors are given freedom to determine how to meet the Government's requirements and that all appropriate performance quality levels are achieved.

1.6 Place of Performance. Performance under this contract shall be required both within the Continental United States (CONUS), and outside the Continental United States (OCONUS), as situations may dictate. The majority of the work shall be performed at Kirtland Air Force Base, New Mexico with full-time support at Colorado Springs (CO), National Capital Region (NCR) and Vandenberg Space Force Base (CA). Support is also required at various locations throughout the United States and outside of the continental U. S. (CONUS) on a temporary basis.

2.0 OVERVIEW OF REQUIREMENT

2.1 To accomplish the JNWC mission and operations, the contractor shall provide Research & Development (R&D) and R&D services to support in the following areas: administrative, security, engineering, operations research and analysis, modeling and simulation, warfighter operations, training, exercises, war gaming, plans and policies, intelligence analysis, data management, information technology, logistics, and equipment and facilities management.

2.2 General Requirements. The Contractor shall:

Commented [GRJCUSS1]: This will be updated to include overview of any/every possible requirement that would come from this IDIQ.

2.2.1 Provide a program management capability to manage the Indefinite Delivery Indefinite Quantity (IDIQ) contract. Identify any key personnel/ Principal Investigators (PI) deemed critical to managing the overall performance of the IDIQ contract.

2.2.2 Provide a primary point of contact to work with the Government on all JNWC IV issues.

2.2.3 Respond to Contracting Officer (CO), Government Team Lead or Program Manager (PM) requests as directed.

2.2.4 Notify the CO of direction received from Government personnel that the Contractor considers outside the scope of WS requirements (or TO PWS/WS/SOO) prior to performing the work.

2.2.5 Notify the CO of any known details regarding current or prior performance of the same work

2.2.6 The Contractor shall attend all kick-off meetings with the Government Team Lead and the CO (or representative) responsible for award and administration of the TO. All kick-off meetings will occur within 30 calendar days of TO award, or sooner as dictated by the TO requirement.

3.0 MANAGEMENT

3.1 Contractor Program Manager

The Contractor shall appoint a Task Lead/Program Manager (PM) who shall coordinate with the Contracting Officer and Government Team Lead to obtain and clarify contract and TO requirements and who will be responsible for the daily control and supervision of Contractor’s employees. The PM shall ensure the Contractor’s employees understand the prohibitions imposed on the U.S. Government regarding, for example, personal services contracts and shall immediately report to the Contracting Officer where the Government attempts to control or supervise Contractors’ employees. The Contractor shall ensure its personnel do not perform Inherently Governmental activities. The Contractor shall ensure its personnel do not attempt to represent the Government of the United States to any other person or entity, U.S., or foreign, except for delivering a Government-approved message or position.

3.2 Onboarding of New Contractor Personnel

When the Contractor requires new personnel to be onboarded to the contract (after completion of the Transition Phase In period), onboarding actions are to be completed within 3 business days of arrival. JNWC government personnel will provide the necessary forms required for its onboarding activities such as those already stated above (NIPRNet, SIPRNet, CAC ID badge, electronic key card) and those not listed herein but required as necessary for the Contractor’s specific position (secure compartmentalized information facility badges, specialized information technology accounts). The Contractor shall ensure that a “sponsor” is assigned to the newly hired individual and will follow the JNWC Onboarding Guidelines SPI to ensure that the onboarding timeline of 3 business days is met.

3.2.1 Human Resource Management. The Contractor shall:

3.2.1.1 Personnel Qualifications. Provide qualified personnel at TO start that meet or exceed the stated Knowledge, Skills, and Abilities (KSA) qualification requirements in the TO, or as stated in the proposal when considered as an evaluation factor relevant to an award decision and incorporated into the resulting TO award.

3.2.1.2 Personnel Maintenance. Maintain minimal personnel turnover throughout the life of the TO. Ensure continuation of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Once a Contractor knows that an employee is leaving and will no longer support a task, the Contractor shall provide written documentation to the CO and Government Team Lead within 3 business days of the employee advising the Contractor of his/her intent to leave. This written notification shall include the date and time the position will be vacant, the reason the employee will no longer work on the task, anticipated replacement date, and what management action will be taken to ensure task mission completion. Position vacancies shall not exceed 14 calendar days unless approved in writing or otherwise coordinated in advance by the CO. Sick/vacation related is permissible while ensuring Government is notified prior to execution of Personal Time Off (PTO), to minimize disruption of mission.

3.2.1.3 Coordination of Personnel Time-Off. The contractor will ensure recordation of company personnel on Paid Time-Off (PTO), or company-provided time-off for coordination (not approval) with the Government Team Lead to ensure all mission objects are adequately maintained. At minimum, the contractor will maintain an accurate personnel status in the JNWC Personnel Tracker, to include personnel off-site for PTO, exercises and associated support, academics, training, outreach, and any other events that affect mission execution. The Government shall not approve leave requests.

3.2.1.4 Replacement/Substitution. Prior to replacing/substituting key personnel, which will be identified at the TO level, the Contractor shall provide a sufficiently detailed qualification summary/resume of proposed key personnel for Government coordination, to include the leadership of the affected division(s). The Government may also request coordination of qualification summaries/resumes on proposed personnel replacing or substituting for non-key positions. This paragraph shall also apply when, at or prior to the start of TO performance, the Contractor provides any personnel for work who were not part of or who replace any personnel submitted and evaluated as part of a TO proposal.

3.2.1.5 Removal of Personnel at Government Request. The Government may request removal (permanent or temporary) of personnel on a TO for security, safety or health reasons, upon discovery of fraudulent resume documentation, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person. The Contractor shall provide a sufficiently detailed qualification summary/resume of proposed personnel for Government coordination prior to replacing/substituting personnel under these circumstances.

3.2.2 Financial Management.

3.2.2.1 Billing. Invoices/cost vouchers, as applicable, shall be submitted and processed in Wide Area Work Flow (WAWF) IAW Section G of the JNWC IDIQ contract. Any variations from the requirements for invoicing in Section G must be approved, in writing, by the CO. Invoicing for travel shall be billed for the entire trip (inclusive of all costs associated with the trip) on a single invoice. Billing for a single trip shall not be broken out into various component billings spread across multiple invoices/cost vouchers, unless otherwise approved, in writing, by the CO for extenuating circumstances.

3.2.2.2 Purchasing. The Contractor shall not purchase any material billable to the Government without prior written consent of the CO or Government Team Lead, as specified in the TO PWS/WS/SOO.

3.2.3 Deliverables Management. The Contractor shall provide the following deliverables as specified below. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last business day prior to the due date. The IDIQ deliverable requirements are as follows:

3.2.3.1 Contractors Progress, Status & Management Report. Provides the progress of work against the established baseline/milestones, the status of the program and of assigned tasks, reports cost data including actual vs planned, and informs of existing or potential problem areas impacting contract cost, schedule and performance. This deliverable should address all relevant performance captured in the WS throughout the reporting period to include achievements, issues, and recommended resolutions. Additionally, the report should identify any significant changes to the contractor’s organization or method of operation.

3.2.3.2 Presentation Material. Presentation materials are audiovisual aids such as PowerPoint presentations, photographs, charts, excel files or any other electronic equivalent. They are to be used to present information during reviews, briefings, and similar activities involving more than one person. The need for this information as a deliverable will be determined during the discussion with the CO, Government Team Lead or Government representative requesting assistance in the development of the material.

3.2.3.3 Technical Reports/Study Services. As a minimum, the technical report provides fully documented results of studies or analyses performed including complete and detailed descriptions of analytic results. The need for this information as a deliverable will be determined during the discussion with the CO, Government Team Lead or Government representative requesting assistance in the development of the material.

3.2.3.4 Small Business Subcontracting Plan. (large businesses only) Each JNWC IV Contractor’s Small Business Subcontracting Plan submitted as part of the JNWC IV IDIQ Technical Volume will be incorporated in the JNWC IV contract per section J.

3.2.3.5 Individual and/or Summary Subcontracting Report (ISR/SSR) - (large businesses only). Contractors shall submit ISR/SSR using the Electronic Subcontracting Reporting System (eSRS) semi-annually IAW FAR Part 19, paragraph 19.704(a)(10)(iii)(A).

3.2.3.6 Organizational Conflict of Interest (OCI) Plan. Disclose all cross-teaming arrangements and provide an OCI Plan for detecting, disclosing, avoiding and mitigating OCI issues/risks at the JNWC IV IDIQ contract and TO levels. Plan shall address OCI resulting from cross-teaming arrangements, as well as process for dealing with OCI identified in the course of contract execution. When cross-teaming, the OCI Plan shall address separate physical locations, separate work forces, separate management, separate computer systems, and a representation that there will be no “cross-talk” or information shared between the two affiliates in connection with all TOs. The OCI Plan shall be turned into the Government for review/approval within 30 calendar days of IDIQ contract award.

3.2.3.7 Subcontractor List (as required). Disclose new teaming partners/subcontractors prior to that entity’s participation in response to a TO solicitation. The Contractor shall receive CO acceptance prior to adding or deleting subcontractors from the prime’s subcontractor list. The Contractor shall provide notification to the CO of any acquisitions or mergers that impact this contract. If a subcontractor is contracted to perform the work on a JNWC IV requirement, a DD Form 254 between the primary Contractor and subcontractor must be signed and provided to Government CO before the subcontractor begins performance on any JNWC IV TO, unless otherwise approved in writing by the CO.

3.2.4 Quality.

3.2.4.1 Quality Control. The Contractor shall develop, implement, and maintain a comprehensive inspection system that assures compliance with all requirements and deliverables of this contract and its associated TOs IAW FAR Part 46, Quality Assurance.

3.2.4.2 Performance Evaluation. Contractor performance is subject to Government surveillance to ensure IDIQ WS and TO PWS/WS/SOO compliance. The Contractor shall comply with the following:

3.2.4.2.1 Access. The Contractor shall permit the CO, Government Team Lead or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, Government Team Lead, state, federal, and other designated personnel in the performance of their official duties. Access shall be provided as soon as possible, but not to exceed 1 business day after the request.

3.2.4.2.2 Non-conformances. Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence. Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time-frames specified by the CO. This contract identifies two types of non-conformances: Minor and Major.

3.2.4.2.2.1 Minor Non-conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. It normally does not increase risk to the Government. Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.

3.2.4.2.2.2 Major Non-conformance. A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form with a suspense date for the Contractor’s corrective action plan. As a minimum, the Contractor’s corrective action plan will address:

-Action taken to fix the immediate problem

-Root cause analysis of the problem to determine cause

-Corrective action on the cause of the problem

-Actions taken to prevent recurrence

3.2.5 Program Management Reviews (PMR). Attend scheduled PMRs, as notified by the Government. The CO, PM, Government Team Lead and other Government personnel, as appropriate, will meet periodically with the Contractor to review performance. PMRs will be held at least annually, alternating between Government and Contractor locations, as appropriate.

The first year the Government reserves the right to conduct PMRs semi-annually if deemed necessary. PMRs will cover status and feedback on performance measures, Contractor performance, and any significant events. PMRs are intended to serve as an opportunity for open and frank discussions on the current status of the contract and applicable TOs. The Government will provide advance copies of PMR agendas, seeking Contractor input/discussion items, and will provide meeting minutes for Contractor review and approval prior to making them official.

The Contractor shall provide written notice to the PM identifying any areas of non-concurrence.

3.2.6 Performance Reviews. In addition to PMRs, the Government may meet with the Contractor, at Government or Contractor request, to discuss Contractor-specific or TO-specific issues, with the Government Team Lead being notified prior to the meeting.

4.0 GENERAL INFORMATION

The Contractor shall observe Federal holidays and other days identified in this section.

4.1 The Government observes the following days as holidays:

• New Year’s Day

• Birthday of Martin Luther King Jr. Day

• President’s Day

• Memorial Day

• Juneteenth Day

• Independence Day

• Labor Day

• Columbus Day

• Veterans Day

• Thanksgiving Day

• Christmas Day

• Inauguration Day (National Capitol Region only)

4.1.1 If these Federal Holidays fall on Saturday, the preceding Friday will be observed. If these Federal Holidays fall on Sunday, the following Monday will be observed.

4.1.2 In addition to the days designated as holidays, the Government may also observe any day designated by Federal Statute; Executive Order; or President’s Proclamation

4.1.3 Notwithstanding holidays and Government closures, The Contractor shall perform in accordance with the terms established in this contract.

4.2 Teleworking. “Teleworking” is defined as authorization for a Contractor employee that normally works at the Government location, to work at an alternate location (at the employee’s residence or other Contractor location) either permanently or temporarily.

“Contractor location” is defined as Contractor-approved place of performance for certain employees that is not an employee’s residence or Government location. For closures affecting the availability of the Government site (e.g., weather closures, a National Day of

Mourning, etc.), the Government will notify the Contractor through normal means such as the Snow Call Line and local news outlets, or via email from the Government Team Lead or CO. During such closures, Contractor personnel may telework if they have a Government Team Lead-approved telework request in place. The Government Team Lead may approve Contractor personnel to telework on a case-by-case basis. The Contractor shall obtain Government approval prior to any teleworking. To obtain approval for teleworking, the Contractor shall submit a teleworking request with appropriate rationale to the Government Team Lead in writing. This request shall include the Contractor’s [“lead’s”, “Project Manager’s”, “Task Lead’s”, etc.] approval, as well the primary Government customer’s approval – if different than the Government Team Lead – when the request is submitted for approval. If approved for teleworking, the Contractor shall support Government core hours in the same manner they would if they were working at a Government location. Although the Government may allow the contractor to use Government computer resources for teleworking, all other teleworking expenses for internet, telephone connectivity, and other equipment services are the responsibility of the Contractor. Classified work is not authorized under telecommuting/telework. Authorized teleworking does not abrogate the Contractor’s requirement to protect information IAW applicable requirements in this WS and TO PWS/WS/SOOs, the DD Form 254 or other Government regulations applicable to this contract.

5.0 HOURS OF WORK

5.1 On-site Contractor support shall be available during customer agency normal operating hours, 0730 - 1630. Work shall generally consist of 40-hour workweeks, Monday through Friday, excluding Federal holidays. Contractor personnel shall observe all Federal holidays. The Contractor shall provide for non-standard duty hours support on an as-directed basis (e.g. DTS support, help desk, JNOC). Additional hours are anticipated during TDYs. TO PWS/WS/SOO shall indicate if work hours are anticipated to vary.

6.0 BASE CLOSURE/GOVERNMENT MORALE AND RECREATIONAL

ACTIVITIES

6.1 Situations may arise where Government facilities may not be available for performance of requirements (i.e., base closure due to weather, force protection conditions, etc.). There may also be occasions when support Contractors are invited to participate in morale and recreational activities (e.g., holiday parties, going-away lunches, and other various social events). Under these circumstances, Contractor employees shall comply with individual company policy in accordance with company compensation system. Because the Government does not have an employer/employee relationship with Contractor employees, it is not authorized to grant administrative leave or expend Government resources to compensate Contractor employees for hours expended on activities not included in the TO PWS/WS/SOO.

6.2 Shutdown. In events such as a base shutdown due to severe weather or security issues (e.g.: September 11, 2001), IAW FAR Clause 52.249-14, Excusable Delays, the Contractor will work with the Government to determine payment terms and any payments will be subject to CO approval. For official USAF/USSF and subordinate unit family days, or holidays granted by Executive Order, the Government is not liable for the Contractor’s costs incurred for work at the locale affected by the shutdown on other than Firm Fixed Price (FFP) contracts. In all cases, if Government personnel are not available in the building/location of work to oversee Contractor activities, Contractor personnel shall leave the premises. Costs incurred for work will not be reimbursed, unless the option for alternate work locations, or teleworking arrangements are specifically addressed in the individual TO PWS/WS/SOO, coordinated with the Government Team Lead and approved by the CO.

6.3 Services and Performance during crisis. Each task order will identify any required research and development services to be provided during crisis.

7.0 CONTRACT TRANSITION

7.1 TRANSITION PHASE-IN

The Contractor shall complete the following actions prior to contract start for overlap, access, account setup, equipment transfer, and knowledge transfer:

7.1.1 The Contractor shall cooperate with the Government Team Lead to ensure a smooth and orderly transition. Identify any conflicts to the Contracting Officer (CO).

7.1.2 The Contractor’s Security Manager shall coordinate with JNWC Government security personnel for access needed to facilities and to obtain Security Management Office (SMO) Codes. The Contractor shall ensure all employees obtain a DoD Common Access Card (CAC) identification badge (ID badge)/electronic key card through JNWC government security personnel.

7.1.3 The Contractor shall obtain any required Non-secure Internet Protocol Router Network (NIPRNet), Secure Internet Protocol Router Network (SIPRNet), and Joint Worldwide Intelligence Communications System (JWICS) access. Submit requests to JNWC Government CSA or CSR to obtain access to the SIPRNet.

The contractor shall obtain or initiate the process for SAP/STO access as applicable to what specific TO PWS/WS/SOO requirements individuals are supporting.

7.1.4 The Contractor shall conduct a “kick-off” meeting with, at a minimum, the Program Manager (PM), CO, and Government Team Lead. The kick-off meeting shall include identification of key personnel, outline of specifics, and status of preparedness for contract start.

7.2 TRANSITION PHASE OUT

The Contractor shall complete the following actions to ensure a smooth and orderly transition of Government equipment, if utilized and services prior to contract completion:

7.2.1 The Contractor shall provide continuous support while the contract is transitioning. The Contractor shall work with the New Contractor Team to ensure a seamless transition. Identify any conflicts to the CO.

7.2.2 The Contractor shall ensure all employees turn in their DoD Common Access Card (CAC) identification badge (ID badge) to the trusted agent or Government Team Lead on the last day of the contract, or sooner if not needed.

7.2.3 The Contractor shall attend the kick-off meeting with the Incoming Contractor Team if required. The Contractor shall brief status of preparedness for contract end.

8.0 DELIVERABLES

a) Monthly Status Report (See Attachment B).

b) Trip Report (See Attachment B).

c) IT Software Request (Will be located at Attachment B)

d) Training Documentation (As required in completed certificate format)

9.0 REQUIREMENTS SUMMARY

9.1 The following deliverables may be required at the TO level:

Identifier Name WS # Schedule Distribution

1.2.4.1

Contractor’s Progress, Status & Management Report

To Be Determined at the TO level

Monthly

1.2.4.2 Presentation

Material

To Be Determined at the TO level

Upon occurrence

1.2.4.3 Technical

Report/Study Services

To Be Determined at the TO level

Upon occurrence

1.2.4.4 To Be

Determined at the TO level

Upon occurrence

1.2.4.5 Semi/Annual

Contract Management Review

Every 6 months until determined to move to every 1 year

Commented [GRJCUSS2]: These will be updated

Commented [GRJCUSS3]: Update with required contract surveillance… eg: look at risk assessment for topics to surveille. One might be security clearance violations.

1.2.4.6

10.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

10.1 GOVERNMENT FURNISHED PROPERTY (GFP)

None on the contract. GFP might be identified on individual task orders.

10.1.1 HARDWARE

None

10.1.2 SOFTWARE

None

10.2 GOVERNMENT FURNISHED INFORMATION

Government personnel shall be available for technical exchanges with the Contractor.

Government personnel shall provide technical input, answer questions, review and accept completed work, and provide feedback regarding Contractor efforts.

10.3 GOVERNMENT FURNISHED RESOURCES

10.3.1 Facilities and Supplies

Contractor personnel working in a Government facility shall be provided working space, communications equipment and network access consistent with contract requirements.

11.0 PRODUCT OWNERSHIP

All products produced by the Contractor in the performance of this contract are the property of the Government.

12.0 PROPRIETARY DATA

12.1.1 The Contractor shall request Government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. Request documentation shall be provided to the appropriate division chief or designated representative and JNWC/J6 for authorization. (Deliverable: IT Software Request memorandum)

12.1.2 The Government shall provide the Contractor access to information required to accomplish assigned tasks commensurate with security clearance and on a need-to-know basis.

12.1.3 The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the appropriate office of primary responsibility.

12.1.4 The Government has unlimited rights to all deliverables developed under this contract.

The Contractor shall not use any materials pertaining to this contract for business development or any other vendor strategic purposes. However, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

13.0 DATA RIGHTS

13.1.1 Pursuant to the contract, the Government has unlimited rights to all deliverables of this contract. The Government shall obtain custody of all records associated with contractor deliverables and shall have exclusive control in the distribution of all products and services provided and/or developed by the Contractor.

13.1.2 Computer Code. Computer code developed under direction of government will retain government purpose rights and unlimited data rights. Code shall not be retained by contractor for any purposes other than support to current JNWC contract

14.0 ENVIRONMENTAL SAFETY AND HEALTH.

14.1 Environmental Requirements. The Contractor shall comply with all applicable federal, state and local environmental statutes, instructions, manuals, handbooks, regulations, guidance, policy letters and rules (including all changes and amendments), and all Presidential Executive Orders in effect on the date of issuance of each TO. The Contractor shall comply with the highest degree of environmental protection where any disagreements exist. For OCONUS work, the Contractor shall also comply with all applicable host nation statutes and agreements. In addition, the Contractor shall comply with the following publications: the DoD Overseas Environmental Baseline Guidance Document (OEBGD) or the Final Governing Standards (FGS), if adopted for a particular location.

14.2 Safety and Health Requirements. The Contractor shall comply with all applicable Occupational Safety and Health Administration (OSHA) and Air Force Occupational Safety and Health (AFOSH) standards, technical orders, regulations and referenced publications both within and outside of the United States. The Contractor shall comply with the highest degree of safety protection where any disagreements exist.

15.0 SECURITY REQUIREMENTS

15.1.1 Security clearance requirements will be identified on individual TOs. Unless identified separately on the task order, security clearances are required for all Contractor personnel prior to starting work on this contract.

15.1.2 For all TO requirements with classified work or access to classified information, the Contractor shall:

15.1.2.1 Clearance Requirements - DD Form 254. Comply with, coordinate and complete a DD Form 254, Department of Defense Contract Security Classification Specification requirements. Upon execution of award, the CO will sign the DD Form 254 for incorporation into the IDIQ. The customer/requiring activity will provide security classification guidance for contract performance. The Government will oversee handling and storage of classified information and provide appropriate storage capability for all classified material. All classified information shall be returned to the government upon termination of the TO.

15.1.2.2 The Contractor shall request security clearances (submit clearance paperwork to the Defense Security Service) for personnel requiring access to classified information within 15 calendar days after receiving a facility clearance or, if the Contractor is already cleared, within 15 calendar days after contract award. Due to costs involved with security investigations, requests for Contractor security clearances shall be kept to an absolute minimum necessary to perform contract requirements. Contractor personnel shall have appropriate clearances prior to commencing work on any TO unless otherwise approved in writing by the CO. The Contractor shall also complete visit requests for each individual that will be performing work on a TO in the Defense Counterintelligence and Security Agency (DCSA) Defense Information System for Security (DISS) prior to performance start unless otherwise approved in writing by the CO.

15.1.2.3 The Contractor shall notify the servicing Information Protection Office of contract award within 30 calendar days after basic contract award. The notification shall include:

-Name, address, and telephone number of company representatives

-The contract number and contracting agency

-The highest level of classified information to which Contractor employees require access

-HQ USSPACECOM Industrial Security guidelines stipulate that facility clearances must be specific and that Contractor employee security clearances cannot be higher than the facility clearance of the company. Facility clearances shall match the clearance level required of Contractor employees. For example, if a TO effort requires Contractor employees to have Top Secret clearances, then the company facility clearance shall be Top Secret and shall be upgraded prior to performance on the TO, unless otherwise directed by the CO. Local security clearance requirements will apply to each TO.

15.1.2.4 The Government assumes costs and conducts security investigations for facility security clearances.

15.1.2.5 Access to classified material up to the Secret/TS/SCI level is anticipated and will be required in accordance with the Contract Security Classification Specification, DD Form

254. The Contractor will be given access to applicable documentation to include requirements, plans, specifications, studies, and analyses up to and including Secret/TS/SCI classification. Unless otherwise specified, Contractor personnel proposed to work on this contract must be U.S. citizens. All personnel will ensure the protection of classified information and controlled unclassified information (CUI).

15.1.3 The Government will provide the appropriate security access to the Contractor for the supported programs, as required.

15.1.3.1 Contractors shall at minimum obtain an Interim SECRET clearance, with a path towards obtaining a Current Top Secret Clearance with SCI eligibility.

15.1.3.2 Specific positions, as outlined in TO PWS/WS/SOO, require Current Top Secret Clearance with SCI eligibility for incoming and incumbent personnel.

15.1.3.3 Eligibility for access to Special Access Program Information will be initiated if required based on JNWC mission needs.

15.1.4 The Contractor shall safeguard Personally Identifiable Information (PII) IAW the policies and procedures in AFI 33-332, Communications and Information, Air Force Privacy and Civil Liberties Program.

15.1.5 The Contractor shall maintain accountability records/receipts for classified material to include transfer and destruction of material.

15.1.6 The Contractor may be requested to provide a Sensitive Compartmented Information Facility (SCIF) to accommodate personnel and store/process material. Access to a teammate/joint venture partner/Subcontractor-provided SCIF is acceptable.

15.1.7 The Government provides guidance to Prime Contractors for contracts requiring access to classified material by incorporating DD Form 254, DoD Contract Security Classification Specification, into the contract. The DD Form 254 tells the Contractor what needs to be protected and to what degree. The DD Form 254, with its attachments and incorporated references, is the only authorized means for providing security classification guidance.

15.1.8 Visitor Group Security Agreement (VGSA)/ Visitor Authorization Request (VAR) is entered into by the Contractor and the installation commander and prescribes the specific actions to be taken by the Contractor's personnel and the Department of Defense to properly protect classified defense information involved in Contractor performance for contracts being performed on Peterson Space Force Base (SFB).

15.1.9 All contractor personnel must be eligible for the appropriate security clearance based upon the nature of the work being performed and the associated security requirements. As part of the security requirements in some areas, contractor personnel may be required to submit to a polygraph exam.

15.1.10 Reporting Requirements. Report to an appropriate authority (i.e., CO, PM, Government Team Lead) any information or circumstances which they are aware of that may pose a threat to the security of DoD personnel, Contractor personnel, resources and classified or unclassified defense information.

15.1.11 Controlled/Restricted Areas. Implement local base procedures for entry to Air Force controlled or restricted areas where Contractor personnel shall work. The Government will complete an AF Form 2586, Unescorted Entry Authorization Certificate, completed and signed by the sponsoring agency’s Security Manager, before a Restricted Area Badge will be issued.

Contractor employees shall have a favorably completed National Agency Check plus written Inquiries investigation before receiving a Restricted Area Badge. Interim access may be granted IAW AFI 31-501, Personnel Security Program Management. Contractor personnel must have appropriate clearances prior to commencing work on any TO unless otherwise approved in writing by the CO.

15.1.12 Key Control. Establish and implement procedures to ensure all keys issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall not duplicate any keys issued by the Government.

15.1.13 The Contractor shall immediately report to the CO, Government Team Lead or PM any occurrences of lost or duplicated keys within two business days of occurrence.

15.1.14 In the event keys are lost or duplicated, the Contractor may be required, upon written direction of the CO, to re-key or replace the affected lock or locks with no additional cost to the Government. The Government may replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the Contractor.

15.1.15 The Contractor shall not loan issued keys to any other persons nor allow access by use of issued keys to other persons not associated with performance of work at the contract work site.

15.1.16 Lock Combinations. Control access to all Government-provided lock combinations to prevent unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government Team Lead. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

15.1.17 Theater/Country Clearances. Obtain special theater and/or country clearances, and comply with theater/country specific requirements, for applicable OCONUS work. These requirements will be identified in the TO PWS/WS/SOO. The Electronic Foreign Clearance Guide at https://www.fcg.pentagon.mil/fcg.cfm states the requirements for travel to specific countries.

15.1.18 Restricted/Formerly Restricted Data. Obtain a final U.S. Government clearance at the appropriate level before obtaining access to RESTRICTED DATA and FORMERLY

RESTRICTED DATA.

15.2 Operations Security (OPSEC)

15.2.1 The Contractor shall adhere to DoD and local Operations Security (OPSEC) guidance:

15.2.1.1 Be familiar with the organization’s Critical Information and Indicator List (CIIL) and OPSEC Plan. Protect critical and sensitive information from disclosure. The Government will provide the CIIL, OPSEC Plan, and AFI 10-701, OPSEC, to include conducting initial OPSEC training by the OPSEC PM/Signature Manager within (per the AFI, 10-701 this is not to exceed 90 calendar days but may be sooner to fit contractor needs) of contract award.

15.2.1.2 Complete annual and event-driven/mission specific OPSEC training provided by the respective OPSEC PM/Signature Manager IAW AFI 10-701, Chapter 4.

15.2.1.3 When necessary, assist the OPSEC PM/Signature Manager in conducting OPSEC internal assessments to ensure sufficient protection measures are in place to protect critical and sensitive information.

15.3 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access will be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances.

Such information is not releasable to personnel holding only reciprocal clearances.

16.0 WORK LOCATION AND ACCESS TO GOVERNMENT PROPERTY AND

FACILITIES

16.1 The primary work location for this contract will be JNWC buildings at Kirtland AFB with some work occurring at Vandenberg AFB (California), Offutt AFB (Nebraska) and within the Colorado Springs (Colorado) area. Alternative work areas may be identified by the Government Team Lead and must be approved by the CO prior to the Contractor performing work in those locations. The Contractor shall be allowed unescorted access to work locations consistent with the contract requirements. Access to Government facilities, documents and systems shall be in accordance with the contract award DD Form 254 and Visitor Group Security Agreement (VGSA) and/or Visitor Authorization Request (VAR).

16.2 Pass and Identification Items. Ensure the pass and identification items required for contract performance are obtained for employees and non-Government owned vehicles prior to the TO start date.

16.3 Retrieving Identification Media. Retrieve all identification media, including vehicle passes, when the contract expires or from employees who depart for any reason before the contract expires, e.g., terminated for cause, retirement, etc.

16.4 Traffic Laws. Ensure all Contractor employees comply with base traffic regulations.

16.5 Weapons, Firearms and Ammunition. Not possess weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on any installation or any office/working location covered under this contract (unless otherwise authorized by local law, regulation, policy or directive).

16.6 Local Area Network (LAN). Unless otherwise stated in the TO, the Contractor with a valid National Agency Check (NAC check), shall be provided access to the host base’s unclassified computer network and its inherent capabilities including, but not limited to:

Internet access, electronic mail, file and print services and dial-in network access. The Contractor shall be aware of and abide by all Government regulations concerning authorized use of the Government's computer network including the restriction against using the network to recruit Government personnel or advertise job openings.

16.7 Workspace/Supplies. Unless otherwise specified in the TO, the Government will provide the Contractor adequate workspace and all office supplies necessary to perform the requirements of the TO.

16.8 Publications and Forms. The following publications and forms are used within the JNWC’s standard program of work. This list is current as of April 2022, but is not all-inclusive.

-NSDD Number 298, National Operations Security (OPSEC) Program, dated 22 Jan 88 -Implement Globally Integrated Operations in the Information Environment (IE) Execution Order, dated 15 May 18 (S) -DoDD 3020.40, Mission Assurance, dated 11 Sep 18 -DoDD 3115.18 DoD Access to and Use of Publicly Available Information (PAI), dated 11 Jun 19 -DoDD 3600.01, Information Operations (IO), dated 4 May 17 -DoDD 5205.02E, DoD Operations Security (OPSEC), dated 11 May 18 -DoDI 3020.45, Mission Assurance Construct, dated 14 Aug 18, -DoDI 3600.02, Information Operations (IO) Security Classification Guidance, dated 28 Nov 05 (U//FOUO) -DoDI S-3604.01, DoD Military Deception (MILDEC), dated 5 Nov 18 (S) -DoDI 3608.11, Information Operations (IO) Career Force, dated 4 Nov 05 -DoDI 3608.12, Joint Information Operations (IO) Educations Change 1, dated 6 Dec 11

-DoDI 5230.29, Security and Policy Review of DoD Information for Public Release, dated 13 Aug 14 -DoDI 8170.01, Online Information Management and Electronic Messaging, dated 2 Jan -DoDI 8550.01, DoD Internet Services and Internet-Based Capabilities (IBC), dated 11 Sep 12 -DoDI 8560.01, Communication Security (COMSEC) Monitoring, dated 22 Aug 18 -DoD O-3607.02, Military Information Support Operations (MISO), dated 13 Jun 16 -DoDM 5205.02-M, DoD Operations Security (OPSEC) Program Manual, dated 3 Nov -CJCSI 3100.01D, Joint Strategic Planning System, dated 20 Jul 18 -CJCSI 3110.01K, Joint Strategic Campaign Plan (JSCP), 22 Mar 19 (S//NF) -CJCSI 3110.05F, Military Information Support Operations (MISO) Supplement to the Joint Strategic Capabilities Plan, dated 7 Apr 17 -CJCSI 3211.01F, Joint Policy for Military Deception (S//NF)-Limited Distribution, dated 14 May 15 -CJCSI 3213.01C, Joint Operations Security, dated 17 Jul 08 -CJCSM 3213.02D, Joint Staff ACCM Program Management Manual, dated 16 Aug 16 (S) -CJCSI 8501.01B, Chairman of the Joint Chiefs of Staff, Combatant Commanders, and Joint Staff Participation in the Planning, Programming, Budgeting, and Execution Process, dated 12 Aug 12 -CJCSM 3130.03A, Planning and Execution Formats and Guidance, Change 1, dated 18 Oct 19 -Joint Staff Military Deception Security Classification Guidance, dated 18 May 12 (S) J-oint Concept For Operating in the Information Environment (JCOIE), dated 25 Jul 18 -JP 1, Doctrine for the Armed Forces of the United States (Incorporating Change 1), dated 12 Jul 17 -JP 2-0, Joint Intelligence, dated 22 Oct 13 -JP 3-0, Joint Operations Incorporating Change 1, dated 22 Oct 18 -JP 3-13, Information Operations (IO) (Incorporating Change 1), dated 20 Nov 14 -JP 3-13.2, Military Information Support Operations (MISO), dated 21 Nov 14 -JP 3-13.3, Operations Security (OPSEC), dated 6 Jan 16 -JP 3-13.4, Military Deception (MILDEC), dated 14 Feb 17 -JP 3-13-4 APP C, Military Deception (MILDEC) - Appendix C, Supplemental Guidance, dated 14 Feb 17 (S) -JP 5-0, Joint Planning, dated 16 Jun 17 -DoDI 7730.66 Guidance for Defense Readiness Reporting.

-DoDI 7730.66, DoDD 7730.65, CJCSI 3401.02B.

-DoDI 4650.08, and JP 3-14 -DoD Instruction (DoDI) 8320.02, Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense.

-DoDI 2000.16, DoD Antiterrorism (AT) Standards

16.8.1 All Contractor personnel shall identify themselves as such when conversing with Government or other Contractor personnel during business meetings, over the telephone, in video teleconferences or via electronic mail to avoid any perception that they may…