PWS Implementation of Advanced Government Simulation Capabilities (IAGSC) MAC.pdf

i

PERFORMANCE-BASED WORK STATEMENT (PWS)

IMPLEMENTATION OF ADVANCED GOVERNMENT SIMULATION

CAPABLITIES (IAGSC)

FOR

AFSC/SWX

2/24/2025 ii

TABLE OF CONTENTS

1 Introduction

1.1 Purpose

1.2 Background

1.3 SCOPE

2 BASIC SERVICES

2.1 Contract Program Management

2.2 Software Engineering Services

2.3 Cybersecurity

2.4 System Administration

2.5 Training and Tactics, Techniques, and Procedures Support

2.6 Materials

2.7 Qualifications

2.8 Security Services

2.9 Administration Support Services

2.10 Wide Area Workflow (WAWF) Data

3 SERVICE SUMMARY

4 CDRL SUMMARY

4.1 CDRL Information

4.2 Government Inspection and Acceptance of Deliverables

5 Travel

5.1 Anticipated Travel

5.2 Travel Pre-Approval/Post Trip Report

6 PLACE / PERIOD OF PERFORMANCE

6.1 Place of Performance

6.2 Period of Performance

6.3 Days and Hours of Operation

6.4 Management of Personnel

6.5 Contractor Employees

6.6 Personnel Roster

6.7 Safety

6.8 Voluntary Protection Program (VPP)

6.9 Obtaining Identification

iii

6.10 Removal of Contractor Personnel

6.11 Network Access:

7 security

7.1 General Security Requirements

7.2 Security Clearance

7.3 Display of Identification

7.4 Obtaining/Returning Identification

7.5 Computer/Local Area Network (LAN) Access

7.6 Contractor Common Access Card (CAC)

7.9 In/Out Processing

7.10 Security Incidents

7.11 Reserved

7.12 Communications Security (COMSEC)

7.13 Operations Security (OPSEC)

7.14 Antiterrorism (AT) Requirements

7.15 Contractor Training

8 Program management

8.1 Data Rights Management

8.2 Intellectual Property (IP)

8.3 Cybersecurity and Data Protection Plan

8.4 Government Furnished Equipment (GFE)

8.5 Inherently Government Functions/Personal Services

8.6 Quality Control Plan

8.7 Quality Assurance

8.8 Safety and Health Standards

8.9 Manpower Reporting:

9 Transition plan

9.1 Phase-Out Plan

10 CONFLICTS OF INTEREST

11 ENVIRONMENTAL CONTROLS

11.1 Hazardous Work Environment

11.2 Safety Program

12 Contracting officer Representative

Appendix A – Acronym iv

Appendix B – NDA

Appendix C – SAFETY

1 INTRODUCTION

The purpose of this Performance of Work Statement (PWS) is to define the tasks required for the

Implementation of Advanced Government Simulation Capabilities (IAGSC). The objective of this effort is to deliver non-personal services to support government development and integration of software products into Department of Defense (DoD) systems for the Air Force Sustainment

Center’s (AFSC) Software Development Directorate, Experimentation Division (AFSC/SWX).

1.1 Purpose

The mission of AFSC/SWX is to lead the way with early system and experimental software, driving innovation and accelerating capability development to enhance warfighter effectiveness.

1.2 Background

The AFSC/SWX develops software products and integrates modeling and simulation capabilities into various DoD platforms and systems. They provide technical support and software development for Space, Aircraft, Threat Modeling, Command and Control (C2), Joint Simulation

Environment (JSE), Test, Training, Experimentation, and Intelligence Surveillance and

Reconnaissance (ISR) programs and activities. AFSC/SWX operates in various government-owned and operated software development and integration environments, supporting multiple security levels to meet the diverse needs of its customers. Customers supported by this effort include 4th and 5th generation aircraft platforms, advanced and experimental weapons systems, and simulators and simulated environments that enable high-end / advanced testing, training, and

TTP development. These advanced systems include programs identified as Operational

Imperatives by the Secretary of the Air Force.

1.3 SCOPE

The scope of this contract is to provide non-personal services to work with government personnel to perform the following tasks:

- Software development for various DoD customers

- Integration of modeling and simulation capabilities into software and hardware environments

- Research and development of advanced software and hardware capabilities for integration into DoD systems

- Cybersecurity activities necessary to perform software development and integration

- Lifecycle software testing including Validation and Verification of modeling and simulation capabilities

- Integration of Intel Community (IC) developed information into threat representative capabilities

- Systems Engineering support for related activities

- Physical security services for facilities, working with Program Security Office, maintain personal security files.

- Provide professional administrative support services.

2 BASIC SERVICES

2.1 Contract Program Management

2.1.1 Program Management

2.1.1.1 The contractor shall be responsible for managing all aspects of the contract to include cost, schedule, contract management, and risks as they pertain to contract requirements identified in the entirety of this

PWS.

2.1.2 Program Management Review (PMR) (CDRL A003)

2.1.2.1 The contractor shall prepare for and brief via a PMR the technical status of program management, details of funding execution, relevant personnel actions, accomplishments, risks and issues.

2.1.2.2 The contractor shall conduct the PMR quarterly with the government which will be conducted in person and or virtually. At a minimum one

PMR per year shall be attended in person by all members.

2.1.2.3 The contractor shall submit the proposed topics and agenda for government approval two (2) weeks prior to the meeting.

2.1.2.4 The contractor shall provide the government meeting charts in contractor format no later than (NLT) two (2) business days before the meeting.

2.1.2.5 The contractor shall provide meeting minutes in contractor format to the government within three (3) business days of the meeting (CDRL A011)

2.1.3 Monthly Status Updates

2.1.3.1 The contractor shall provide to the government updates on contract execution, including funding, and any major changes to contract risks and issues.

2.1.3.2 The contractor shall conduct a status update meeting with the government monthly. (CDRL A001)

2.1.3.3 The contractor shall submit status of funding and any other meeting artifacts in contractor format to the government within 1 business day of the meeting. (CDRL A001)

2.1.4 Meeting Support

2.1.4.1 The contractor shall provide programmatic and technical support to regularly occurring weekly and ad-hoc meetings as requested by the government.

2.1.5 Staffing Management

2.1.5.1 The contractor shall manage the staffing of personnel required to perform the activities laid out in this PWS as requested by the government assigned Technical Lead.

2.1.5.2 The Contractor shall maintain a stable workforce while minimizing the impact of any turnover and/or disruptions to the Government and/or mission.

2.1.5.3 Upon notification of a pending vacancy, the Contractor shall provide written documentation to the CO, COR, and PM at least two (2) weeks in advance of vacancy or sooner when possible.

2.1.5.4 In the case of a no-notice departure, the Contractor shall notify the CO, COR, and PM in writing within 24-hours.

2.1.5.5 This written notification shall include the date and time the position will be vacant, anticipated replacement date, and management plan and correction action, if needed, to ensure task mission is not impacted or degraded.

2.1.5.6 The Contractor shall fill the vacancy within 45 calendar days.

2.1.5.7 If the vacancy cannot be filled within the required 45 calendar days, the

Contractor shall provide written notification to CO, COR, and PM.

2.1.5.8 In addition, the Contractor shall provide temporary backfill with qualified personnel, for any vacancies greater than two weeks that occur for any reason. If Contractor is unable to provide backfill approval must be sought from the CO upon becoming aware of the inability to backfill.

2.1.5.9 The contractor shall ensure that personnel performing work under this

PWS are qualified and possess the required security clearance. All contractors shall obtain and maintain at a minimum a SECRET security clearance.

2.1.5.10 The PWS will require access to classified data. Refer to the DD Form

254 attached to the contract for additional security instructions, guidance, policies and restrictions. The Contractor shall pass down tailored security requirements, as stated in the contract, to all subcontractors.

2.2 Software Engineering Services

2.2.1 Software Engineering / Development

2.2.1.1 The contractor shall provide software engineering services alongside the government technical team in a government DevSecOps environment, including but not limited to software sustainment, and modeling and simulation integration into software products for experimental and operational systems

2.2.1.2 The contractor shall execute all work under section 2.2. of this PWS on government owned and directed systems.

2.2.1.3 The contractor shall provide unlimited data rights to all software developed and delivered on the government owned and directed systems. (CDRL A004)

2.2.1.4 The contractor shall NOT introduce any proprietary data, code, software, information, etc., into the government code-base or onto government systems without the written consent of the on-site government technical lead (CDRL A017)

2.2.1.5 The contractor shall provide Agile and DevSecOps operations expertise and management to integrate with the government technical team to perform management of software development activities to meet assigned tasks and requirements.

2.2.1.6 The contractor shall conduct Research and Development (R&D) activities needed to integrate advanced models / simulations, advanced software capabilities, and advanced hardware capabilities into new and legacy

Air Force platforms and systems.

2.2.1.7 The contractor shall conduct software sustainment activities, including code refactoring, necessary to sustain code baselines (CDRL A004).

2.2.2 Systems Engineering

2.2.2.1 The contractor shall provide systems engineering services to support all activities laid out in sections 2.2, 2.3, and 2.5 of this PWS.

2.2.3 Software Integration

2.2.3.1 The contractor shall provide integration support to integrate advanced technologies and other software products into new and legacy Air Force platforms and systems. Examples include but not limited to: JSE, VATS, and F-16.

2.2.3.2 The contractor shall provide software and hardware integration and installation support at various worldwide military facilities for activities laid out in section 2.2 of this PWS.

2.2.4 Software Testing

2.2.4.1 The contractor shall support life-cycle testing of software products.

2.2.4.2 The contractor shall prepare and deliver software test plans for government approval as requested by the government assigned

Technical Lead. (CDRL A012)

2.2.4.3 The contractor shall deliver software test reports as soon as practicable, but no later than 30 days after completion of a software test event.

(CDRL A005)

2.2.4.4 The contractor shall provide support to generate and document deficiencies discovered during formal testing activities.

2.2.4.5 The contractor shall conduct cybersecurity related testing on government software products to inform activities in section 2.3 of this PWS (CDRL

A006).

2.2.4.6 The Contractor shall conduct software validation and verification testing activities as directed by the on-site Government Technical Lead (CDRL

A013)

2.3 Cybersecurity

2.3.1 Cybersecurity Oversight

2.3.1.1 The contractor shall lead the development and processing of security related approvals and efforts, to include Interim Authority To Test

(IATT), and Authority to Operate processes on various Information

Technology (IT) and mission related systems.

2.3.1.2 The Contractor shall provide Risk Management Framework (RMF) services to support the cybersecurity requirements for the Government's information systems and networks. In accordance with DoD Instruction

8510.01, "Risk Management Framework (RMF) for DoD Information

Technology (IT)," and NIST Special Publication 800-37, "Risk

Management Framework for Information Systems and Organizations," the Contractor shall perform the following RMF services: conducting risk assessments and vulnerability scans; developing and implementing system security plans (SSPs) and continuous monitoring plans;

providing security control implementation and testing; and conducting security assessments and authorization to operate (ATO) support.

2.3.1.3 The Contractor shall also provide support for RMF documentation, to include system security plans, security control implementation plans, and plan of action and milestones (POA&M) documents. (CDRL A006)

2.3.1.4 The Contractor shall ensure that all RMF services are performed in accordance with DoD and NIST guidelines, and shall maintain the confidentiality, integrity, and availability of the Government's information systems and networks.

2.3.1.5 The Contractor shall provide services to support the requirements of the

Joint Special Intelligence Operating Policies and Procedures (JSIG) for the protection of Sensitive Compartmented Information (SCI) and

Special Access Programs (SAPs).

2.3.1.6 In accordance with the JSIG, the Contractor shall ensure that all personnel with access to SCI and SAPs are properly indoctrinated and trained on

JSIG requirements; that all SCI and SAP facilities and systems are properly accredited and certified; and that all SCI and SAP information is properly marked, handled, and stored.

2.3.1.7 The Contractor shall also provide support for JSIG-compliant security inspections and assessments, to include facility security inspections, information system security assessments, and security awareness training.

2.3.1.8 The Contractor shall ensure that all JSIG-related services are performed in accordance with the JSIG and other applicable security policies and procedures, and shall maintain the confidentiality and integrity of all

SCI and SAP information.

2.3.1.9 The contractor shall provide qualified and certified (ie level II and level III

Information Assurance Manager certifications) personnel as needed to perform cybersecurity duties on the following enterprise and standalone government networks to include but not limited to: NIPR, CUI, SIPR, SECRET, JWICS, TS/SCI, TS/SCI/SAR and various SAP networks levels. As well as Cyber security certifications include those from DoD

8140 Cyber Workforce Qualification Program (CWQP) and DoD 8570

Information Assurance (IA) Program Transition to DoD 8140

CWQP8570 to 8140.

2.3.1.10 The contractor shall work with assigned Security Control Assessor

Representatives (SCARs), IT Approving Officials (AOs), and their staff to provide all information necessary to accredit various networks and IT infrastructure.

2.3.1.11 The contractor shall analyze evaluate, and document cybersecurity aspects of software and IT infrastructure to identify, manage, and mitigate cybersecurity risks and vulnerabilities to assigned government systems. (CDRL A006)

2.3.1.12 The contractor shall report any major risks or issues to the government

Technical Lead and higher-headquarters’ assigned cybersecurity experts for appropriate reporting and tracking purposes. (CDRL A006)

2.3.2 Cyber Security

2.3.2.1 The contractor shall provide program management of the activities described in section 2.3 of this PWS.

2.3.2.2 The contractor shall provide schedules and weekly updates of the tasks needed to execute section 2.3 of this PWS in contractor format. (CDRL

A006)

2.3.2.3 The contractor shall incorporate these into PMRs, Status Updates, and other regularly schedule meetings as needed. (CDRL A001)

2.4 System Administration

2.4.1 Systems Administration

2.4.1.1 The contractor shall provide System Administrators and IT specialists to monitor, maintain, configure and support the IT systems needed to execute the activities outlined in this PWS.

2.4.1.2 The Contractor shall provide information technology (IT) network and systems administration services to support the Government's requirements for reliable, secure, and efficient IT operations.

2.4.1.3 The Contractor shall provide expertise in IT network and systems administration, including but not limited to, network architecture, network security, system administration, and help desk support.

2.4.1.4 The Contractor shall ensure that all IT networks and systems are properly configured, maintained, and upgraded to meet the Government's requirements for performance, security, and reliability.

2.4.1.5 The Contractor shall also provide support for IT network and systems administration, including but not limited to, monitoring, troubleshooting, and repair of IT networks and systems.

2.4.1.6 The Contractor shall deliver IT network and systems administration services that meet the Government's requirements for quality, reliability, and security.

2.4.1.7 The Contractor shall provide classified network administration services to support the Government's requirements for secure and reliable IT operations on classified networks.

2.4.1.8 The Contractor shall provide expertise in classified network administration, including but not limited to, network architecture, network security, system administration, and help desk support for classified networks.

2.4.1.9 The Contractor shall ensure that all classified networks are properly configured, maintained, and upgraded to meet the Government's requirements for performance, security, and reliability.

2.4.1.10 The Contractor shall also provide support for classified network administration, including but not limited to, monitoring, troubleshooting, and repair of classified networks.

2.4.1.11 The Contractor shall deliver classified network administration services that meet the Government's requirements for quality, reliability, and security, and shall comply with all applicable security regulations and guidelines, including but not limited to, the National Industrial Security

Program Operating Manual (NISPOM) and the Intelligence Community

Directive (ICD) 503.

2.4.1.12 The Contractor shall ensure that all personnel working on classified network administration have the required security clearances and are familiar with the security requirements for classified networks.

2.4.1.13 The contractor shall provide expertise needed to design, document, implement and accredit new government owned networks as requested by the government assigned Technical Lead.

2.4.1.14 The contractor shall support life-cycle operations of IT systems, including install, repair, replace, remove and destruction of IT equipment at the appropriate classification levels and facilities according to the 88th Air Base Wing Information Protection office.

2.4.1.15 The contractor shall perform Data Transfer Authority duties and responsibilities on government owned networks as requested by the government assigned Technical Lead.

2.4.1.16 The contractor shall provide qualified and accredited certified (ie security plus) personnel as needed to perform network administration duties and responsibilities on the following government networks to include but not limited to: NIPR, CUI, SIPR, SECRET, JWICS, TS/SCI, TS/SCI/SAR and various SAP networks.

2.4.1.17 The contractor shall have experience with Windows, Redhat

Linux[PD5] , VMware administration, Kubernetes, Microsoft Office

Suite, SCCM, WSUS, Redhat Satellite, VMWare Orchestrator, podman, docker, docker images, helm charts, git, Visual Studio, Openshift.

2.5 Training and Tactics, Techniques, and Procedures Support

2.5.1 Tactics, Techniques, and Procedures (TTPs) support

2.5.1.1 The contractor shall provide operational TTP Subject Matter Expertise to ensure modeling, simulation, and software products are integrated into operationally relevant and useful capabilities. The Contractor shall provide multi-domain operations training and subject matter expertise services to support the Government's requirements.

2.5.1.2 The contractor shall consult with client to define the need or problem, supervises studies, and leads surveys to collect and analyze data to provide advice and recommend. All issues and solutions will be provided in the MSR. (CDRL A001)

2.5.2 Training

2.5.2.1 The contractor shall provide subject matter expertise to conduct ad-hoc training for combined contractor / government teams.

2.5.2.2 The Contractor shall work closely with the Government to develop and deliver customized training programs that address specific multi-domain operations requirements and objectives.

2.5.2.3 The Contractor shall also provide support for the development of multi-domain operations doctrine, tactics, techniques, and procedures (TTPs), and shall participate in multi-domain operations exercises and experiments to test and evaluate new concepts and technologies.

2.5.2.4 The contractor shall provide Agile and DevSecOps expertise for ad-hoc training at the request of the government assigned Technical Lead.

2.5.2.5 The contractor shall provide multi-domain warfighting operationally relevant subject matter experts for ad-hoc training at the direction of the local government Technical Lead.

2.5.2.6 The contractor shall provide operationally relevant subject matter experts for ad-hoc training at the guidance of the government assigned

Technical Lead

2.5.2.7 The contractor shall provide training materials in contractor format seven

(7) days prior to a planned training event for government approval.

(CDRL A007)

2.5.2.8 The contractor shall provide written and verbal assessment of simulation products.

2.5.2.9 The contractor shall assist in agile software development meetings to assist in workload prioritization

2.5.2.10 The contractor shall perform operational scenario development in collaboration with modeling and simulation personnel to develop and validate operationally relevant simulation scenarios.

2.6 Materials

2.6.3 The Contractor shall provide all hardware, software, and testing material required to perform the requirements of this PWS as requested by the government

Technical Lead. All material purchases shall be approved by the PM and COR.

2.7 Qualifications

2.7.1 JUNIOR: A Junior labor category has up to 3 years experience and a BA/BS degree. A Junior labor category is responsible for assisting more senior positions and/or performing functional duties under the oversight of more senior positions..

2.7.2 JOURNEYMAN: A Journeyman labor category has 3 to 10 years of experience and a BA/BS or MA/MS degree. A Journeyman labor category typically performs all functional duties independently.

2.7.3 SENIOR: A Senior labor category has over 10 years of experience and a MA/MS degree. A Senior labor category typically works on high-visibility or mission critical aspects of a given program and performs all functional duties independently. A Senior labor category may oversee the efforts of less senior staff and/or be responsible for the efforts of all staff assigned to a specific job.

2.7.4 SUBJECT MATTER EXPERT (SME): A Subject Matter Expert is an individual whose qualifications and/or particular expertise are exceptional and/or highly unique. Subject Matter Experts do not have specific experience/education qualifications but are typically identified as recognized Industry leaders for a given area of expertise. Subject Matter Experts typically perform the following kinds of functions: Initiates, supervises, and/or develops requirements from a project’s inception to conclusion for complex to extremely complex programs;

Provides strategic advice, technical guidance and expertise to program and project staff; Provides detailed analysis, evaluation and recommendations for improvements, optimization development, and/or maintenance efforts for client-specific or mission critical challenges/issues; Consults with client to define need or problem supervises studies and leads surveys to collect and analyze data to provide advice and recommend solutions.

2.7.5 The ideal candidate should possess the degrees identified above a from an accredited institution. However, applicants with approved relevant years of professional experience in lieu of a degree will also be considered. Waivers to the above-mentioned degrees must be submitted to the PM or COR.

Education and Work Experience

Degree: Work Experience

Substitute:

Work and Experience

Substitute:

Work and Experience

Substitute

Bachelor’s

Degree

6 years of work experience may be substituted for a

Bachelor’s Degree.

Associate’s Degree plus 4 years work experience may be substituted for a

Bachelor’s Degree.

N/A

Master’s

Degree

12 years work experience may be

Master’s Degree.

Bachelor’s Degree plus

8 years work experience may be

N/A

Master’s Degree.

Doctorate’s

Degree

20 years work experience may be

Doctorate’s Degree

Bachelor’s Degree plus 16 years work experience may be

Master’s Degree plus 12 years work experience may be substituted for a

AFSC/SWX anticipates the approximate manning outlined in Table 1 for identified requirements in Section 2 of this PWS.

Table 1: Requirement Manning at Contract Start

Requirement Approximate FTEs

2.1 Program Management 1.5

2.2 Software Engineering Services 23

2.3 Cyber Security 9

2.5 Training and Tactics, Techniques and Procedures 1.5

2.9 Security Services 1

2.10 Administration 1

2.8 Security Services

2.8.1 The contractor shall provide security services.

2.8.2 The contractor shall manage physical security to the facilities, including, but not limited to, entry points, visitor requests and badges, and access authorizations.

2.8.3 The contractor shall support various Collateral, Sensitive Compartmented

Information, and Special Access Program projects, programs, and activities

(including investigations).

2.8.4 The contractor shall work with the assigned Program Security Officer.

2.8.5 The contractor shall process inbound/outbound classified mail and receipt records, maintain logs for a variety of administrative functions associated with document control. All work shall be performed at its appropriate classification level.

2.8.6 The contractor shall assist in maintaining personnel security files, provide inputs to and enforce local Standard Operating Procedures, and provide support for security-related training.

2.8.7 The contractor shall perform destruction of classified materials in accordance with local area guidance.

2.9 Administration Support Services

2.9.1 The contractor shall provide professional administrative support services.

2.9.2 The contractor shall support management by performing activities, such as, but not limited to, managing management calendars, scheduling meetings, creating and maintaining meeting minutes, preparing organizational charts, updating rosters, and coordinating visits with external organizations.

2.9.3 The contractor shall provide daily office management support, such as, but not limited to, managing office supplies, providing assistance with conference room management, managing unclassified mail, supporting the tracking of organizational and administrative processes, managing taskers and organizational action items (including ensuring completion).

2.9.4 The contractor shall lead the aspects of administrative operations of events to include attendee lists; invitations; venue setup; logistics for presentation materials, transportation, and attendee check-in.

2.9.5 The contractor shall manage compliance with Electronic Records Management.

2.10 Wide Area Workflow (WAWF) Data

The Contractor shall submit a contract invoicing and payment report to the COR, CO, and PM 5 business days prior to WAWF submission. (CDRL A002) DI-

MGMT-81651)

3 SERVICE SUMMARY

PWS

Paragraph Performance Objective

Performance Threshold

2.1.2 Program Management Review (PMR)

PMR shall be held quarterly.

Meeting agenda will be approved 2 weeks prior. Charts shall be delivered 2 days prior. PMR meeting minutes shall be delivered within 3 business days of meeting.

Satisfactory if PMR is held 90% of the time.

2.1.5.6, 2.1.5.7

Staffing of personnel required to perform the activities laid out in this

PWS

Contractor shall provide written documentation to the CO, COR, and

PM at least two (2) weeks in advance of vacancy or sooner when possible. The Contractor shall fill the vacancy within 45 calendar days

100% of the time.

2.5.1.2

Tactics, Techniques, and

Procedures (TTPs) support issues

The contractor consults with client to define need or problem supervises studies and leads surveys to collect and analyze data to provide advice and recommend. All issues and solutions provided in the MSR.

Satisfactory is 90% of the time

2.5.2 Training and Training materials

The contractor shall provide training and training materials 7 days prior to training events Satisfactory if delivered 95% on time.

2.2.4.2 Software Test Report

Shall deliver software test reports as soon as practicable, but no later than

30 days after completion of a software test event. 100% deliverable required.

2.3.1 Cyber security

Develop and update mission criticality analysis vulnerability assessments, risk evaluations, and identification and counter measurement implementations for mission-critical functions. Provide weekly updates of the tasks needed to execute section 2.3. 98% deliverable.

6.6.1 Personnel Roster

Contractor personnel roster shall be submitted NLT 15 calendar days

ARO and NLT the 10th calendar day of each month. Satisfactory if delivered 90% on time.

4.1.4 CDRL Delivery Schedule

The contractor shall submit CDRLs according to the due date indicated and have no more than one CDRL per quarter submitted after the identified due date. Satisfactory if delivered 95% on time.

4 CDRL SUMMARY

4.1 CDRL Information

4.1.1 Contract data shall be delivered electronically IAW the corresponding requirement for each Data Item listed in Table 4-1 (below). The contractor shall prepare and deliver data to the Government in contractor format except where specific forms are required. Data shall be formatted IAW the requirements specified for each Data Item listed in Table 4-1.

4.1.2 If there is a discrepancy in due dates between the PWS and the DD Forms 1423, this PWS shall take precedence. Due dates falling on non-working days

(Saturdays, Sundays, and recognized national (legal) holidays) shall be construed to mean the next regular working day. All due dates [i.e., 30 calendar Days After

Contract (DAC)] are calendar counted unless designated otherwise.

4.1.3 The contractor shall ensure all technical data, including drafts and working papers, are marked and controlled IAW appropriate distribution statements and export control warning notices.

4.1.4 The contractor shall submit CDRLs according to the due date indicated and have no more than one CDRL per quarter submitted after the identified due date.

Mistakes shall be corrected within two working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Table 4-1

Exhibit Title PWS Paragraph

Delivery

A001

Monthly status report

2.1.3.2, 2.1.3.3, 2.3.2.3, 2.5.1.2,5.2.2

By the 10th day of each month

A002 Contract Invoicing and

Payment Report

2.10.1 5 days prior to invoice submittal into WAWF

A003

Meeting Agenda

2.1.2 Meeting agenda

delivered 2 weeks prior to PMR. Meeting charts delivered 2 days prior to

PMR. Meeting minutes delivered 3 days after

PMR

A004

Software Sustain

2.2.1.3, 2.2.1.7 The contractor shall request by written consent for any code refracturing, necessary to sustain code baselines

A005 Software Test Report

2.2.4.3 30 days after completion of a software test event

A006 Cybersecurity

Vulnerability Report

2.2.4.5, 2.3.1.3, 2.3.1.11, 2.3.1.12,2.3.2.2 due by COB on Thursday of each week

A007 Training Material

2.5.2.7 7 calendar days prior to planned training

A008

TCIR/DART

8.8.3 Annually, NLT than 15

January

A009 Mishap Report

6.7.2, 11.2.2 3 calendar days after injury/mishap

A010 Personnel Roster

6.6.1 10th calendar day of each month

A011 Meeting Minutes

2.1.2.5 3 business day following the meeting

A012 Test Scheduling Report

2.2.4.2 5 business days prior to

Government approval

A013 Verification and

Validation

2.2.4.6 5 days after testing

A014

Safety Plan

6.7.1,8.8.4 30 days after contract award and 30 days after each option award

A015

Intellectual Property

8.2.2, 8.3.1 Incidents affecting

Government data shall be reported to within 72 hours

A016 Quality Control Plan

8.6.1 30 days after contract award

A017

Proprietary Software

Information

2.2.1.4 Written consent required

prior to introducing any proprietary data, code, software information.

A018 Phase-Out Plan 9.1.1 30 days after CO request.

4.2 Government Inspection and Acceptance of Deliverables

Data and documentation deliverables shall be delivered IAW this PWS, and the Contract Data

Requirements List (CDRL) Form DD1423s attached to the contract unless otherwise specified by the Government PM, and CO through a contract modification or CO letter. The Government has the inherent right to disapprove any data item. Therefore, the Government PM will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Government PM, with coordination with the COR will notify the

Contractor in writing of the specific reasons why the deliverable was rejected. The Contractor shall have fifteen (15) calendar days, or as outlined in the table in section 4-1 (whichever is shorter) or unless designated otherwise through a CO letter, to correct the rejected deliverable and resubmit to the Government PM for re-inspection. The Government must approve final versions of data deliverables

5 TRAVEL

Travel is required under the performance of this contract.

5.1 Anticipated Travel

5.1.1 Contractor personnel may be required to travel to locations as needed to support the objectives of this PWS. Locations include but are not limited to: Lexington, MA; Edwards AFB, CA; Nellis AFB, NV; Patuxent River, MD; Hill AFB, UT

5.1.2 The CLIN type for travel shall be on a Cost Reimbursement No FEE (CRNF).

The contractor shall coordinate with the Government Program Manager, Contracting Officer Representative (COR), and/or the Contracting Officer to establish a process on how approvals, reports, and reimbursements shall be completed.

5.1.3 Airfare for travel and per diem shall be billed IAW Joint Travel Regulations

(JTR) or Federal Travel Regulation (FTR) as applicable. Contractor travel policies and procedures must be best business practices IAW FAR 31.205-46, Travel Costs. Contractor must use the DoD JTR or FTR as a guide regarding air fares, per diem, allowances, and reimbursement of travel expenses. First class air travel is not authorized. The Government reserves the right to disallow unreasonable travel costs. Travel must be billed as a separate line item on all invoices.

5.1.4 The contractor shall be responsible for making all necessary travel arrangements.

All travel requests in support of this contract shall be submitted to the COR or

CO and PM for approval 14 days prior to traveling.

5.1.5 The contractor shall propose all estimated travel costs for each occurrence at the time of request.

5.1.6 The contractor shall travel to conferences, in support of this PWS as approved by the PM and COR.

5.2 Travel Pre-Approval/Post Trip Report

5.2.1 The contractor is responsible from making all necessary travel arrangements. The

Contractor shall obtain written approval to travel from the PM, and COR at least fourteen (14) business days in advance before traveling. Request for approval shall include the following:

• Date and Location of Travel

• Event (Purpose of Travel)

• Number of Travelers

• Name and Title (Labor Category) of Travelers

• Goals and Desired Outcomes of Trip

• Why Alternate Methods are not Viable Options

• (ie, Video Teleconference (VTC), Telecom, etc. are not options to accomplish purpose and goals of trip)

• Total Estimated Cost of Trip

• Anticipated Itinerary with Associated Estimated Costs (ie, Airfare, hotel, rental car, etc.)

5.2.2 As part of the monthly report, upon completion of any travel, during the month reported the Contractor shall submit a trip report describing the actual activities, accomplishments, and any relevant information learned on the trip. (CDRL

A001)

6 PLACE / PERIOD OF PERFORMANCE

6.1 Place of Performance

6.1.1 All support for this effort shall be on-site at Wright-Patterson Air Force base for this effort.

Work shall be performed at the following Government locations:

2303 8th St. Bldg 802

Wright-Patterson AFB, OH 45433

6.2 Period of Performance

6.2.1 The overall period of performance for this contract shall not exceed 30 months from date of contract award. Task Orders shall not exceed 12 months.

6.3 Days and Hours of Operation

6.3.1 Normal Hours of Operation: Work shall be performed at the government location, workdays are Monday through Friday except Federal Holidays Hours of operation are between 0600- 1700.

6.3.2 Federal Holidays: Unless otherwise required by the Government, the contractor shall not have access to the Government facilities on the following federal holidays:

New Year’s Day 1 January

Martin Luther King’s Birthday Third Monday in January

President’s Day Third Monday in February

Memorial Day Last Monday in May

Juneteenth National Independence 19 June

Independence Day 4 July

Labor Day First Monday in September

Columbus Day Second Monday in October

Veteran’s Day 11 November

Thanksgiving Day Fourth Thursday in November

Christmas Day 25 December

If a holiday falls on Saturday, it is observed on Friday and working hours are

Monday through Thursday for that week. If the holiday falls on a Sunday, it is observed on Monday and working hours are Tuesday through Friday for that week. Any other circumstances that may prompt base closure, such as weather closures or Days of National Mourning, may also restrict opportunity to perform.

On these days, the contractor shall not generally be required to work and the

Government shall not be billed for work not performed.

6.4 Management of Personnel

6.4.1 The Contractor shall assign all tasks to their internal staff. Specific projects with time constraints and priority will flow through the Contractor's project lead from the Government Technical Lead.

6.4.2 The tasks in this PWS do not include providing acquisition assistance to efforts associated with this, or any other program. Contractors participating in acquisition activities will generally be prevented from providing the resulting service IAW Federal Acquisition Regulations (e.g., FAR 9.505, General Rules).

6.5 Contractor Employees

6.5.1 Contractor’s employees shall be required to identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. Contractor’s employees shall identify themselves as

Contractor employees in telephone conversations and in formal and informal written correspondence. Contractor’s employees shall identify themselves in meetings by adding the word “Contractor” by their names on sign-in sheets.

6.6 Personnel Roster

6.6.1 The Contractor shall submit a Personnel Roster within fifteen (15) business days after Task Order issue, ten (10) calendar days from the beginning of each month, and at the COR’s request (CRDL A010).

6.7 Safety

6.7.1 General Safety Requirements: The Contractor shall implement a safety program that ensures protection of Government and contractor personnel and property.

(CDRL A014).

6.7.2 Record and report promptly (within one hour) to the COR or all available facts relating to each instance of damage to government property or injury to either contractor or government personnel. (CDRL A009)

6.7.3 If the government elects to conduct an investigation of the accident/mishap, the contractor shall cooperate fully and assist government personnel in the conduct of investigation until the investigation is completed.

6.8 Voluntary Protection Program (VPP)

6.8.1 Wright Patterson, along with the entire Air Force, has adopted the VPP as recognized by Occupation Safety and Health Administration (OSHA).

Consequently, VPP impacts all “applicable contractors” operating on Air Force

Installations. It is the contractor’s responsibility to ensure its on-site employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. Detailed information on VPP is available on the OSHA website (http://www.osha.gov/dcsp/vpp/index.html). Contractors, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, must follow the safety and health rules of the installation or VPP site.

6.8.2 VPP requirements apply to contractors whose employees work more than 1,000 hours quarterly. The Contractor shall flow down these requirements to all subcontractors who qualify as applicable contractors under this contract.

6.9 Obtaining Identification

6.9.1 During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel. Upon the termination or completion of the contract, or in the case of an employee who no longer requires access to the work site, the contractor shall be responsible for promptly returning credentials to the SWX Mission Partner Affiliate Sponsor

(MPAS). Lost badges shall be reported to the MPAS within one (1) working day of the badge being lost.

6.9.2 For a Common Access Card (CAC) to be issued to the contractor, the contractor shall complete and submit CAC application form for each of the firm's employees who must have access to the installation and equipment. Individual begin this process with the SWX MPAS

6.10 Removal of Contractor Personnel

6.10.1 The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any Government property, facility, and installation at the sole discretion of competent Government authority if that authority determines such action is necessary to protect or preserve

Government property, safety, and security, or to maintain good order and discipline.

6.11 Network Access:

6.11.1 The Contractor must meet the same security and training requirements as government employees for access to WPAFB's network or Automated

Information Systems (AIS).

6.11.2 For those contractor employees who require government computer access only, a

National Agency Check with written Inquiries (NACI) must be accomplished through the government.

6.11.3 Contractor employees requiring a government provided e-mail account shall annually complete the Information Assurance Awareness training. Interim access may be granted by Designated Approving Authorities only after submission of the NACI and favorable finger print determination has been received by the applicable Security Manager (SM).

6.11.4 Contractors who no longer need network or AIS access shall report within 3 business days to the appropriate security manager and the Functional System

Administrator.

7 SECURITY

7.1 General Security Requirements

7.1.1 The contractor shall comply with all Security, Force Protection, and

Antiterrorism requirements enforced at each installation.

7.1.2 The contractor shall comply with local unit in and out-processing procedures for all contractor personnel to ensure proper security-related briefings and debriefings are accomplished. Specific in- and out-processing checklists may be included at the task order level.

7.1.3 Contractors shall not use any other form of identification to access any

Government installation or facility while working on this contract except the issued credentials associated with the awarded contract or task order. Example:

using a military retiree card to access an installation to work on a contract.

7.2 Security Clearance

7.2.1 At a minimum, a SECRET clearance, current within five years, shall be required for all personnel. Personnel security clearances shall be processed through the contractor’s Facility Security Office (FSO) and shall have a relationship established in Defense Information System for Security (DISS).

7.2.2 The Contractor shall not reveal the specific nature of work being performed under this contract, or any details thereof, except when authorized in writing by the Government PM.

7.2.3 Contractor personnel performing work under this contract shall have an active

SECRET security clearance at time of award and shall maintain this level of security clearance through the entire period of performance.

7.2.4 Individuals awaiting final adjudication of a security clearance may work temporarily (not to exceed 90 calendar days) from building Bldg 802 at Wright-

Patterson AFB or another area as approved by the Government PM, and CO or

COR.

7.2.5 The contractor shall obtain security clearances within 90 days for all of their employees after hiring.

7.2.6 The contractor shall prepare a subcontractor DD Form 254, if a subcontractor is used.

7.2.7 Security Requirements for SECRET or Higher Level Clearance and Access

7.2.7.1 Contractor employees requiring a higher level of investigation shall be submitted for a Tier 3 (initial) or a Tier 3R for (Reinvestigations) if over

10 years. A Single Scope Background Investigation (SSBI) for Top

Secret, must be submitted IAW DoDM 5200.02_AFMAN 16-1405, Air

Force Personnel Security Program. The contractor’s Facility Security

Officer (FSO) shall be responsible for initiating the required level of investigation for a T3, T5 background investigation for a classified contract, and ensuring all investigations are current. The contractor shall meet the same security requirements as Government employees for access to the Automated Information Systems (AIS) network and connections to office printers, office supplies, and any other items necessary to complete the assigned tasks. The contractor shall only have access and use of the office equipment as mentioned in the DD254 or

SOW/PWS. The organization’s Government supervisor along with the equipment custodian will monitor the accountability of the Government

Furnished Equipment (GFE) provided for the contractor employee’s use. Removal of any GFE is not authorized without a letter signed by the supervisor and the SWX Information System Security Officer

(ISSO) approval.

7.2.7.2 Contractors with a current T3, T3R, T5, or T5R type security clearance with SECRET eligibility shall adhere to the Security Executive Agent

Directive (SEAD) 3 and 4 reporting requirements. Cleared contractors shall complete, initially and annually, cleared personnel training.

7.3 Display of Identification

7.3.1 Air Force-issued identification badges and any contractor badges shall be worn at or above the waistline during the individual’s duty hours when not in a production or designated Foreign Object Damage (FOD) hazard area.

7.4 Obtaining/Returning Identification

7.4.1 During performance of the contract, the contractor shall be responsible for obtaining required identification for newly-assigned personnel. Returning of credentials shall be done on the last day of the contract when the PoP has ended or the requirement is considered complete. At the completion or termination of the contract, the contractor shall have three business days to out-process and terminate all their network user accounts and to return all access cards and base identification badges to the MPAS.

7.5 Computer/Local Area Network (LAN) Access

7.5.1 Contractors requiring access to a Government AIS shall have background investigations and Cyber Awareness Challenge training completed after contract award but prior to logical access.

7.5.2 A CAC must be issued prior to accessing a Government IT system. Reference section 7.7 for requirements for CAC issuance and process.

7.5.3 All contractors accessing a Government computer network or Government IT system shall complete the following and any other required forms or training:

7.5.3.1 Government-provided DoD IAA Cyber Awareness Challenge training prior to accessing Government computer networks.

7.5.3.2 Government AFMAN 17-1301, Addendum A Rules of Behavior and

Acceptable Use Standards for SWX Information Technology, prior to accessing Government Computer Networks.

7.5.3.3 Government DD Form 2875, System Access Authorization Request, for

NIPR access and each Government IT System; a separate DD Form

2875 must be submitted for each contractor employee employed on this contract. Contractor supervisors and employees are not authorized to sign the DD Form 2875.

7.6 Contractor Common Access Card (CAC)

7.6.1 CAC Cards

7.6.1.1 Credentialling Contractors: CACs are issued/adjudicated based off the

DoDM 1000.13, DoDI 5200.46, DoD Investigation and Adjudicative

Guidance for Issuing the Common Access Card (CAC). If a logical need is not determined for access to information systems, a DBIDS will be issued to the contractor.

7.6.1.2 CACs will be issued based on the PWS by the Government supervisor if access to Government IT systems is required to perform the job. CACs will not be issued for training purposes only. CACs will not be issued to

Foreign Nationals (FN) unless they meet the requirements defined in

AFI 31-113, Installation Perimeter Access Control (CUI). The Wright-

Patterson AFB Foreign Disclosure Office will be the office of responsibility.

7.6.1.3 The contractor shall comply with Air Force Federal Acquisition

Regulations (AFFARS) clause 5352.242-9001. It should be noted that this process may take four weeks to complete; it is critical that

Contractors consider these instructions before award (i.e., when preparing a proposal in response to a FOPR) and prior to changing contractor personnel after award.

7.6.1.4 The contractor will be given two weeks to complete the online investigation questions and complete fingerprinting, prior to being submitted for a T1 and receiving a CAC. Fingerprints are required for all investigations and must be within 120 days. Contractors who do not complete the questionnaire and fail to meet the suspense dates will be removed from the installation immediately. All Government credentials will be recovered and returned to the issuing SM. At no time shall the contractor use other Government-furnished credentials to perform work on a Government contract or they will be reported to 88th Security

Forces and barred from the installation.

7.6.1.5 Closed investigations, with favorable results, must be within last two years from previous Government employment, or appointment, to be used in lieu of submitting a new background check or security clearance.

7.6.1.6 Lost badges shall be reported to the SWX Security Office within one working day of loss.