SETAII_PWS_Draft4 formatted_11122024.pdf

CUI FA7146‐25-X-XXXX

CUI

PERFORMANCE WORK STATEMENT

FOR

Scientific Engineering & Technical Assistance (SETA)

II

Collaboration with DoD Cyber Crime Center (DC3), Air Force Office of Special Investigations (AFOSI), and Secretary of the Air Force/ Concepts, Development, and

Management (SAF/CDM)

November 12, 2024

DRAFT IV

Controlled by: AFDW/PK CUI Categories: PROCURE Distribution/Dissemination Controls:

FEDCON AFTER AWARD

POC: CO NAME (240-612-xxx)

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

1.2 Objectives

1.3 Scope 4

1.4 Standard of Conduct

SECTION II

2.0 TASK DESCRIPTIONS

2.1 Engineering and Technical Analysis Support

2.2 Sustainment Engineering

2.3 Change Management and Release Management

2.4 Integration Environment Support

2.5 Architecture

2.6 Studies, Analysis and Assessments

2.7 Process Improvement and Transition Planning

2.8 Test Engineering

2.9 Cyber Operations Analysis

2.10 Developmental Technical Project Support (R&D):

2.11 Surge Support

2.12 Other Direct Costs

SECTION III

3.0 SERVICE SUMMARY

3.1 Purpose

3.2 Components

3.3 Right to Surveil

SECTION IV

4.0 DELIVERABLES AND REPORTING

4.1 Financial Report

4.2 Status Report

4.3 Incident Reports

4.4 Meeting Minutes

4.5 Trip Reports

4.6 Final Report

4.7 Specialized Report

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services

5.2 Contractor Acquired Property

SECTION VI

6.0 GENERAL INFORMATION

6.1 Core Duty Hours and Base Shutdown/Inclement Weather

6.2 Kickoff Meeting/Orientation Meeting

6.3 Emergency Operations/Mission Essential Personnel

6.4 System for Award Management (formerly CMRA)

6.5 Security

6.6 TRAVEL

6.7 Employee Accountability & Turnover

6.8 Miscellaneous Paragraphs

SECTION VII

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General: The Department of Defense (DoD) Cyber Crime Center (DC3) is designated as a Federal Cyber Center, is the Department of Defense (DoD) Center of Excellence for Digital and Multimedia (D/MM) forensics and serves as the operational focal point for the Defense Industrial Base (DIB) Cybersecurity program. To fulfill its mission, DC3 has collaborated with The Secretary of the Air Force, Concepts, Development, and Management (SAF/CDM) Office and the Air Force Office of Special Investigations (AFOSI) Headquarters, Cyber Division (AFOSI/XRY) to bring complex cyber operational capabilities to the Air Force. SAF/CDM explores new concepts, develops emerging opportunities, and manages high-priority projects and programs to provide innovative solutions to Air Force and Department of Defense (DoD).

AFOSI/XRY is responsible for organizing, training, and equipping the Air Force Law Enforcement (LE) and Counterintelligence (CI) cyber mission against criminal and foreign intelligence threats. To meet current and projected workload requirements DC3, its current partners SAF/CDM and AFOSI, and adjacent stakeholders must augment its military and civilian workforce with appropriate, highly skilled, analytic, and cyber oriented technical professional services support. Specifically, Scientific Engineering & Technical Assistance (SETA) II support to apply knowledge of cyber operations, LE/CI concepts, architectures, systems, hardware / software components & protocols, and technologies to analyze proposals, project plans and deliverables for accuracy, compliance, security, and completeness for the Government.

1.2 Objectives: The SETA II support team is expected to draft, edit and fully coordinate technical projects across multiple stakeholders and organizations to include plans that permit the integration of cyber capabilities into infrastructure baselines following legal, regulatory and security requirements.

• 1.2.1 The SETA II support team conducts project planning to include development and management of technical requirements, budget forecasts and estimates, and schedules for project government leads.

• 1.2.2 The SETA II team members are considered a key part of a multi-discipline project team, integrating technical knowledge with operational and threat intelligence information to create holistic capability proposals for transition to operational use.

1.3 Scope: The SETA II support team requires extensive expertise in systems engineering, Cyber LE/CI/Counterespionage (CE) tools and techniques, as well as a deep understanding of cyber operations, cyber threats, risk mitigation, government acceptance testing, program management, and financial management. Specific tasks encompass technical analyses for trade studies, cyber capability assessments, lab testing, tool evaluations, support for field test demonstrations, system performance tracking and documentation, vendor market surveys, supportability technical data development, training, transition planning, and implementing new capabilities within a flexible enterprise system architecture environment.

This support also involves developing workflow solutions for the enterprise service management infrastructure, utilizing both classified and unclassified system data sources for the AF Cyber system architecture. This includes improving processes and introducing technical innovations to display operational system and support data for end-users, support providers, and Government stakeholders.

Furthermore, the Contractor will provide engineering and technical enterprise service support, including feasibility studies, analysis of alternatives, technical services during planning, construction or installation phases, inspection, and evaluation of engineering projects to including independent validation and verification and penetration testing as necessary, and related services to support platform, tools, or capability instantiation. Throughout these tasks, adherence to relevant DoD and AF guidance and Instructions is paramount.

1.4 Standard of Conduct: The Contractor shall adhere to and operate within imposed government official policies, regulations, instructions and directives; completing all steps required to achieve systems accreditations at various levels, to include: design, design documentation, technical development, developmental and operational testing, security assessments, and operational documentation (operating manuals, user and administrator manuals, software design description, functional design/description document) through various certifications (e.g., security Assessment & Authorization, Joint Interoperability Test Command). It is critical for the contractor to ensure the documents are completed throughout the project in a way that will satisfy the accreditation reviews at the end of the project.

SECTION II

2.0 TASK DESCRIPTIONS

Administrative & Management Support Services (NAICS 541611) Engineering and Support Services (NAICS 541330)

2.1 Engineering and Technical Analysis Support: The Contractor shall provide engineering and technical enterprise service support, including, but not limited to, the preparation of feasibility studies, analysis of alternatives, provision of technical services during the planning, construction or installation phase, inspection and evaluation of engineering projects, and related services supporting platform, tools, or capability instantiation. The Contractor shall make use of relevant DoD and AF guidance and Instructions during the execution of these tasks.

• 2.1.1 The Contractor shall develop a rigorous vendor evaluation process that assesses the capabilities, financial stability, and performance history of potential technology suppliers, which may include Request for Proposal (RFP) development and vendor performance assessment. Additionally, they will advise clients on procurement strategies, including contract negotiation, pricing, and terms to optimize value for money while ensuring compliance with relevant regulations. Furthermore, the Contractor will assist clients in defining clear and precise technical specifications and requirements to guide vendors and ensure successful procurement, development, and delivery of technology solutions. They will also develop and implement robust contract management processes to ensure contracts are executed as per agreed terms and to oversee vendor performance throughout the contract lifecycle.

2.2 Sustainment Engineering: The Contractor shall provide engineering services that include but are not limited to system and technical in-service design, infrastructure (lifecycle refresh, addition, modification and retirement), communications, physical and logical components of services, and supporting software to improve reliability, maintainability, and affordability.

Support tasks include, but are not limited to, production and implementation of technical service management models and appropriate AF documentation, support to technical review process standards and adaptation (e.g., AF Form 1067), and the implementation of prototype agile delivery models to rapidly modernize or update the global AF Cyber enterprise system.

Contractor efforts will promote collaborative interaction between the System Program Office, operational sites, other contractors, service providers and Mission Partners. In doing so, the Contractor shall utilize a consistent and time-sensitive approach to the supportability design of mission essential services that are effective and efficient, adhere to DoD and AF requirements, and consider industry best practices. Contractors must apply the following: AF Strategic Plan, AF Master Standards List, AF Agile Center of Excellence, AF Risk Management; AF ACAT Level 3 Life Cycle Sustainment Plan (LCSP) Version 1.0, AF Blue Baseline and OTB (Own the Baseline), AF RMF Process, and Security Impact Analysis.

2.3 Change Management and Release Management: The Contractor shall provide engineering services that involve but are not limited to the necessary planning and coordination to take a new or changed service, or a service to be decommissioned, through Change Management and Release Management and into the production environment. Contractors should apply best systems engineering practices, including applicable DoD system engineering guides, Project Management Professional Book of Knowledge (PMBOK) processes, and SAFE Agile principles for change management, integration, configuration control, and implementation of the Risk Management Framework.

2.4 Integration Environment Support: The Contractor shall provide engineering services that include but are not limited to engineering Subject Matter Expert (SME) support for AF Cyber operations and Cyber LE/CI integration environments. SME support includes day-to-day process and system infrastructure operations, Root Cause Analysis (RCA) to eliminate recurring incidents and to minimize the impact of incidents that cannot be prevented, and Problem Management, including the activities required to diagnose the root cause of incidents, determining the resolution to those problems, and providing workarounds. It is important to note that certifications related to the SAFE Agile process, while relevant to this scope of work, are not strictly required of prospective offerors. The Government anticipates that the DC3, AFOSI, and CDM Program Offices will provide the successful offeror with steady guidance relevant to SAFE implementation strategies and practices. The ultimate goal is to provide mission-effective engineering and technical support within a continuous integration environment and meeting established process quality performance measures.

2.5 Architecture: The Contractor shall support and provide recommendations for future architecture modifications including coordinated modernization and execution of AF Cyber operations and Cyber LE/CI architecture and integration tasks in close association with Mission Partners/Owners. The architecture recommendations should enable implementation of industry-standard and or best architecture practices, as directed by the Government. The contractor shall support update of operational and system views, maintain standards lists and facilitate integration of architecture initiatives across DoD and in close collaboration with other DoD/IC Mission Partners. Contractors must be familiar with Model Based System Engineering (MBSE) and how it can benefit architecture security.

2.6 Studies, Analysis and Assessments: The Contractor shall provide engineering services to develop an efficient and effective methodology for assessing and evaluating technology solutions during the life cycle of DC3, AFOSI, and CDM managed segments of the AF Cyber operations enterprise and AF Cyber LE/CI systems. These services include, but are not limited to, assessments and evaluations in support of AF Cyber enterprise systems supporting multi stakeholder environments as well as Cyber-LE/CI specific tools and capabilities. The Contractor shall identify and evaluate current and emerging Government and commercial technologies and procedures that may offer improvements to capabilities and assist in the planning and implementation of technology insertions. Technology solutions and designs shall consider the operational constraints and limitations of the receiving or requiring activity/customer. If applicable, design concepts shall include provisions for continuous technological improvement to maximize opportunities for product and capability improvement available from emerging technological advances in the Government and commercial marketplace. The Contractor shall provide systems engineering services to develop methodologies to enable OCEA to monitor commercial technology sectors for emerging risks to DoD. These services include, but are not limited to, assessments of available Government and commercial technical solutions.

• 2.6.1 The Contractor will assess the security design of systems and networks to ensure effective implementation of security measures. They will also remain up to date with the latest security protocols and compliance standards (e.g., NIST, ISO, DoD) and aid clients in adopting and implementing these standards for data protection. Additionally, the Contractor will define and utilize state-of-the-art penetration testing methodologies, tools, and frameworks to identify vulnerabilities in systems, networks, and applications. They will conduct simulated cyberattacks to test the defensive capabilities of client systems, enabling proactive vulnerability mitigation. Furthermore, they will support clients in developing robust incident response plans and conduct tabletop exercises to ensure readiness in managing and recovering from cybersecurity incidents. The Contractor will identify and catalog vulnerabilities and weaknesses, prioritize them based on potential impact, and offer recommendations for remediation.

• 2.6.2 The Contractor shall assess encryption methodologies and data protection measures to safeguard sensitive information to include DoD Zero Trust framework and relevant post quantum encryption migration requirements.

• 2.6.3 The Contractor will conduct a thorough examination of the Operations Information Environment (OIE) and associated Information Warfare (IW) functions to bolster support for the client's mission objectives. This entails analyzing the structure, interconnectivity, and vulnerabilities of the OIE, alongside assessing current IW functions such as electronic warfare, cyber warfare, psychological operations, and deception operations within the OIE framework. The Contractor will also evaluate emerging technologies and adversary tactics to devise mitigation strategies, collaborate with stakeholders to validate findings, and produce comprehensive reports with recommendations for enhancing OIE resilience and IW capabilities. Additionally, they will provide technical expertise to inform strategic planning and decision-making processes, contributing to the client's situational awareness and operational effectiveness in the information warfare landscape.

2.7 Process Improvement and Transition Planning: The Contractor shall provide quality assurance for technical services as follows:

• 2.7.1 Innovative processes and procedures to ensure system operation is optimally effective, efficient and affordable supportable operational capability. Plans shall fully evaluate areas such as enterprise asset management and licensing considerations, how and when various levels of validated Government requirements would be met.

• 2.7.2 Transition plans that identify how an initial prototype or pilot demonstrations could rapidly evolve to full system functionality and a supportable operational capability. Plans shall fully evaluate areas such as enterprise asset management and licensing considerations and how and when various levels of validated Government requirements would be met.

• 2.7.3 Engineering or technical services to correct or improve system issues with the goal of maintaining the required effective operations and maintenance performance of the weapon system, or to provide direct support to the weapons system that is essential to production, sustainment, integration, interoperability, and configuration management.

2.8 Test Engineering: The Contractor shall provide full system life-cycle test engineering capability support including:

• 2.8.1 The Contractor shall have relevant expertise in AF, traditional, Scrum and scaled agile software development techniques, automated test processes in transition to a continuous integration environment leading to DevOps environment.

• 2.8.2 The Contractor shall coordinate training in best practices, perform operational and developmental tests and evaluation, verification testing with new/modernized automated test software applications, support technical exchange meetings (TEMs) and participate in quick reaction teams for time critical failure analysis and mishap investigation activities, coordinate risk assessment activities, mitigation and corrective action plans. Contractors must be familiar with the following: [Applicable AF standards for development, test, integration and delivery (i.e., AFSPCI 10-170 RTO&I, eMASS and XACTA docs, etc.)]

• 2.8.3 The Contractor shall conduct comprehensive government acceptance testing to verify and validate the functionality, performance, and compliance of the delivered system or software solution. This testing process will include rigorous examination of all system components, features, and functionalities outlined in the project specifications and requirements documentation. The Contractor shall develop detailed test plans, test cases, and test scripts to systematically assess the system's adherence to specified criteria and standards.

Testing activities will encompass functional testing, performance testing, security testing, usability testing, and compatibility testing across relevant platforms and environments. The Contractor shall collaborate closely with government stakeholders to ensure alignment with acceptance criteria and facilitate timely resolution of any identified issues or discrepancies.

Upon completion of testing, the Contractor shall provide comprehensive test reports documenting test results, observations, and recommendations for any necessary corrective actions or enhancements.

2.9 Cyber Operations Analysis: The Contractor shall provide full spectrum intelligence analysis, collections, production support to DC3, AFOSI, and CDM cyber capabilities. This includes but is not limited to the following: The Contractor shall perform intelligence analysis utilizing allsource intelligence data and employing a variety of techniques as can be found in, “Structured Analytic Techniques for Intelligence Analysis” (Heuer, McPherson), Intelligence Analysis: How to Think in Complex Environments” (Hall), “Intelligence Analysis: A Target-Centric Approach” (Clark), “Analyzing Intelligence: A National Security Practitioners’ Perspectives” (George, Bruce) among others. The Contractor shall identify and document gaps in intelligence data from all source reporting. The Contractor shall generate, staff and monitor the results of intelligence collection requirements as they are communicated across the intelligence community. The Contractor shall generate, staff and monitor the results of intelligence production levied against NASIC or other relevant intelligence production organizations according to the DIAPP. The Contractor shall generate on an as needed or more frequent basis a variety of internal intelligence products. These may include “quick looks”, designed to answer relatively superficial or introductory level consumer requirements as well as “deep dives’, involving significantly more involved explanations of highly complex and detailed subject matter. Periodic updates as they may pertain to specific technologies, projects or threats may be also required, depending on the needs of the customer. The Contractor shall provide intelligence analysis that will be used to identify the potential outcomes of tools under development. This will include defining what observable effects may be collected by the intelligence community – based on the various technical capabilities and limitations, locations and times those systems may be employed. The Contractor will also provide the customer with identifying additional opportunities for development of tools, in terms of 'branches and sequels' of related vulnerable systems, adversary capabilities and weapons that the original cyber capability could be modified to affect.

2.10 Developmental Technical Project Support (R&D): Contractor shall provide engineering and technical enterprise project development support, including, but not limited to, the development of a holistic approach to instantiation of a multidomain effects environment in the conduct of R&D activities, Development Test and Evaluation (DT&E) and Operational Test and Evaluations (OT&E), preparation of feasibility COA analysis for tradeoff and risk drivers in development of installation and activities in the conduct of R&D projects, analysis of alternatives, formation and integration of technical requirements for proof of concept demonstrations during development of constructs supporting multi-domain effects. The contractor shall inspect and evaluate engineering projects to meet cyber/radio frequency spectrum effects requirements, and related integration of supporting platform, tools, or capability instantiation to create new capabilities. The Contractor shall make use of relevant DoD and AF guidance and Instructions during the execution of these tasks.

2.11 Surge Support: The Government may require surge support during the period of performance and will do so by performing the Surge Labor CLINs identified in the Schedule if exercised. The Contracting Officer may exercise an optional surge CLIN by written notice to the Contractor within 30 days. Delivery of added surge labor shall continue at the same rate as like labor negotiated in the order, unless the parties otherwise agree.

2.12 Other Direct Costs: The Government may necessitate other direct costs (ODC) associated with systems engineering, covering expenses like equipment rental, hardware, software licenses, subcontractor services, and other essential costs for task completion, utilizing an ODC CLIN.

The contractor is responsible for seeking prior approval from the Contracting Officer or designated authority for any pre-authorized expenses required in task performance. All ODCs must adhere to the principles of reasonableness, allocability, and allowability as outlined in applicable regulations. Regular reporting on ODC expenditures, along with forecasts for future phases, shall be submitted to the Contracting Officer or designated authority. Moreover, the Contractor must ensure compliance with audit requirements related to ODCs, cooperating fully with auditors by providing necessary documentation and explanations. Through meticulous ODC management, the Contractor will maintain transparency, accountability, and contractual compliance throughout the duration of this contract.

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “ACCEPTABLE” or “UNACCEPTABLE” basis. These thresholds are critical to mission success.

3.1 Purpose: The Services Summary (SS), Table 1 Services Summary Table, lists performance objectives for the required services the Government will surveil. The absence of any contract requirement from the SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses entitled “Inspection of Services” or “Inspection” or “Default” in Section E and Section I of the contract.

3.2 Components: The SS states the performance objective (required service), and threshold (performance standard, accept and reject points (if applicable)) in either a qualitative or quantitative fashion for each critical success factor.

3.3 Right to Surveil: The Government reserves the right to surveil all services and requirements called for in this PWS IAW FAR Part 52.246-4 to determine whether the Contractor is meeting performance objectives and goals. The SS reflects the objectives and thresholds used to track Contractor performance for the contract.

SECTION IV

4.0 DELIVERABLES AND REPORTING

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change, but actual dates, may need to be revised depending on actual contract start date. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date. After contract award, SAF/MG will provide information and access on where to post all deliverables. The Government COR shall be notified when deliverable(s) are made available for review/approval.

The Contractor shall provide the Government with a monthly report to include a summary of all incidents to include alarms, response time, and personnel reporting status. If there are no alarms or incidents during the month the contractor shall state this in their report.

DELIVERABLE PWS

PARA

DUE DATE DELIVERY

Financial Reports 4.1 Monthly See Below Status Reports 4.2 Monnthly-10th of the

Month See Below

Incident Reports 4.3 ASAP See Below Meeting Minutes 4.4 As Required See Below Trip Reports NLT five business days after completion of travel.

See Below

Specialized Report 4.7 As Required See Below

Performance Objective PWS Paragraph Performance Threshold Method of

Surveillance

SS-1

SS-2

SS-3

DELIVERABLE PWS

PARA

DUE DATE DELIVERY

Final Report 4.6 30 days before end of PoP See Below

4.1 Financial Report: Delivered monthly, including, at a minimum, labor and other direct costs (ODCs) incurred for the current period, cumulative costs for the contract period, remaining funds available, and labor hours expended; include graphics (e.g., line charts) showing actual costs against planned costs and explain all variances exceeding 5%.

4.2 Status Report: The monthly activity report shall include progress toward major milestones, significant accomplishments, and convey areas of risk or concern and mitigating strategies. In addition, the contractor shall include other information as requested by the Government Technical Manager and information which has been directed and/or authorized by the Contracting Officer (CO). The monthly status reports shall cover monthly project activities, development results, and projected schedules for each task requirement when applicable. The report shall be delivered every 30 days following contract award by the 10th calendar day of each month for work accomplished the previous month.

4.3 Incident Reports: Delivered no later than (NLT) 1 hour event: The contractor shall report mishaps or incidents exceeding $1000 (material and labor) to USAF property entrusted by this contract within one hour during normal day shift hours. All other incidents will be reported as soon as possible, but NLT the next normal working day. Accidents/mishaps shall be reported to the CDM USG Project Lead, through the COR.

4.4 Meeting Minutes: Delivered NLT one (1) week after meeting. The Contractor shall provide, and upon USG approval, disseminate meeting minutes for key forums such as Technical Exchange Meeting, Monthly Meetings and InProgress Reviews. The meeting minute reports document will be in a format agreed to by the PM/COR.

4.5 Trip Reports: The Contractor shall submit a brief written report of the visit. Each report shall include, at a minimum, the date and duration of the visit; the purpose, audience, location of the presentation, and a brief summary of activities, and any recommendations and/or observations.

4.6 Final Report: Shall be delivered NLT one month prior to the end of the Period of Performance (PoP). The contractor shall deliver to the PM/COR a Final Summary report of all activities that captures findings, lessons learned, and best practices, recommendations for future courses of action and all requirements.

4.7 Specialized Report: Specialized documentation, data, and reports shall be delivered as specified and outlined in the applicable with respect to project planning, technical diagrams, COA analysis, briefing slides, concepts of operation, or issue white paper.

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services: The Government will provide workspace, Contractor shall provide all the equipment necessary to accomplish objectives IAW the PWS.

5.2 Contractor Acquired Property: Contractor shall provide all the equipment necessary to accomplish objectives IAW the PWS.

SECTION VI

6.0 GENERAL INFORMATION

The Contractor shall have access to Government facility five (5) business days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however, the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime; but overtime pay is prohibited without COR and CO approval. Federal Holidays shall be observed in accordance with Office of Personnel Management policy. The following Federal holidays are observed under this contract:

Holiday Date 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 19 June (or observed date)

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

Inauguration Day 20 January (NCR only)

6.1 Core Duty Hours and Base Shutdown/Inclement Weather: Core duty hours are 0800 – 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/.

6.2 Kickoff Meeting/Orientation Meeting: The Contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, OFFICE (SAF/# or AF/#), key Government representatives, and the COR.

The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following:

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both Contractor and

Government)

• Discussion of draft Program Management Plan (PMP)

• Travel notification and processes

• Government-furnished information (GFI)

• Security requirements (Building access, badges, Common Access Cards (CAC)

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g., Monthly Status Report (MSR)

• Point of Contacts (POCs)

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process, timeframes, and status.

• Prioritization of Contractor activities http://www.opm.gov/status/

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

• 6.2.1 Agenda: The Contractor shall provide a draft copy of the agenda NLT three (3) days after contract award for review and approval by the COR prior to finalizing. The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present.

• 6.2.2 Kickoff Meeting Location: The location of the Kickoff Meeting will be held at the

(Government's or Contractor’s) facility or another designated location and the date and time will be mutually agreed upon by both parties.

6.3 Emergency Operations/Mission Essential Personnel

• 6.3.1 Continuation of Essential Contractor Services During Crisis: All services in this PWS

HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”

6.4 System for Award Management (formerly CMRA): The Contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the System for Award Management (SAM) data collection site. The Contractor is required to completely fill in all required data fields at http://www.SAM.gov. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. The UIC for AFDW is FF16M0. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The Contractor may direct questions to the System for Award Management help desk.

• 6.4.1 Subcontractor Input in SAM: Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into SAM but will enter their information into a Bulk Loader spreadsheet available from the SAM helpdesk. Subcontractor shall fill in columns A-C then return it to the SAM helpdesk after it's completed, and a technician team will enter the information into SAM.

6.5 Security: The researchers will have escorted access and will complete Non-Disclosure Agreements (“NDAs”) for all contractor and subcontractor employees with access to vulnerability information. NDAs must be submitted to the COR five (5) business days after contract award to ensure all candidates meet the requirements.

• 6.5.1 Physical Security: The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property http://www.sam.gov/ requirements contained in this contract. At the end of each workday, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

• 6.5.2 Access Control: The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced, or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. 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.

• 6.5.3 Pass and Identification Items: The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

• 6.5.4 Retrieving Identification Media: The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

• 6.5.5 Traffic Laws: The Contractor and its employees shall comply with base traffic regulations.

• 6.5.6 Weapons, Firearms, and Ammunition: Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on the premises of any military installation or military facility.

• 6.5.7 Communications Security (COMSEC): Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account.

Access shall 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. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

• 6.5.8 Contractor Identification: All Contractor personnel shall always wear the Air Force issued CAC when away from their immediate work area to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a Contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, Contractors occupying collocated space with their government program customer should identify their workspace area with their name and company affiliation or as a minimum “Contractor” after name.

• 6.5.9 Drug, Tobacco, and Alcohol Use Policy: The consumption of alcoholic beverages or illegal drugs by Contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

6.6 Travel

• 6.6.1 Local Travel: Local travel to attend meetings or events may be required at no cost to the Government. Travel within the National Capital Region commuting vicinity is considered a cost of doing business and shall not be separately reimbursed.

• 6.6.2 CONUS Travel: Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip.

• 6.6.3 OCONUS Travel: (e.g., to EUCOM and/or PACOM Area of Responsibility) Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 20 business days prior to trip. Theater Business Clearances shall be obtained, as necessary, prior to travel. Further guidance for Contractor travel can be found at https://www.defensetravel.dod.mil/site/faqctr.cfm.

• 6.6.4 Trip Reports: Following each trip, the Contractor shall prepare and deliver Trip/After

Action Reports to the COR IAW AFH 33-337. The trip report shall be completed in accordance with OFFICE (SAF/# or AF/#) guidance.

6.7 Employee Accountability & Turnover

• 6.7.1 Staffing of Contractor Personnel: Contractor shall provide a stable workforce, throughout the duration of the contract, by maintaining a 25% or less employee turnover rate.

No positions shall remain vacant for more than sixty (60) calendar days. The government shall not be billed for positions left vacant over zero (0) working days unless the vacancy is due to government delay and otherwise approved by the CO.

• 6.7.2 List of Employees: The Contractor shall maintain a current listing of employees assigned under this contract to include key personnel as defined below. The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Contracting Officer, Program Manager, and Servicing Security Activity. An updated listing shall be provided upon request.

https://www.defensetravel.dod.mil/site/faqctr.cfm o 6.7.2.1 DC3 Key Personnel Work Role: Senior Cybersecurity Engineer Project Supported: DC3 ADO Program Responsibilities: Cyber mission manager for the acquisition and deployment strategy for network sensors that aim to identify and counter the efforts of Foreign Intelligence Entities to steal critical technologies from the Defense Industrial Base. Coordinate with Military Department Counterintelligence Organizations (MDCO) for strategic and operational planning efforts to increase the throughput and customer base for automated data obfuscation capabilities to enable cyber-CI operations. Establish and maintain liaison contacts within DoD cyber entities, Combatant Commands, CI Organizations, and the Joint Staff to support national priorities and DC3 strategic guidance. Lead efforts to integrate technical knowledge with operational and threat intelligence information to support the use of commercial and open-source tools in cyber threat analysis.

Required Experience:

A minimum of 10 years of experience in military CI operations A minimum of 10 years of experience in the Intelligence Community, CCMD

(J2X/3X), or in a Cyber-CI capacity Extensive knowledge on the use of commercially available and classified databases to enrich network traffic data Experience preparing executive level briefings and operational proposals for C-Suite equivalent Senior Military and Civilian Leaders Certified Ethical Hacker (CEH) Graduate of an accredited CI Special Agent credentialing training academy Graduate of Advanced Foreign CI Operations Course (AFCIOC) and experience in support of DoDI S-5250.09 activities Required Education: Master’s Degree Other Required Qualifications: TS/SCI and CI polygraph or ability to obtain one

Work Role: Senior Cybersecurity Engineer Project Supported: DC3 Enhanced Sensor Program Responsibilities: Responsible for the comprehensive technical task management of the commercial awardee executing a government contract, encompassing an array of complex systems engineering principles. Advise on system engineering complexities, provide in-depth technical analysis, and oversee planning and coordination, including the creation of strategy and governance frameworks to ensure project success, to include the development of a robust project strategy that aligns with the organization's goals and government requirements and establishes effective governance structures. Conduct research of a technical nature to support operations, produce essential legal, technical, operational, and contractual documentation necessary for this high visibility program.

Required Experience:

A minimum of 10 years leading U.S. and DoD Cyber Programs A minimum of 5 years conducting both offensive cyber operations and defensive cyber operations in support of strategic DOD objectives

A minimum of 5 years of experience managing technical programs valued at over $30M annually

Demonstrated experience with Data Science and Data Analytics Demonstrated experience in Military Intelligence

Other Required Qualifications: TS/SCI

Work Role: Senior Test and Evaluation Engineer Project Supported: DC3 Independent Validation & Verification Program Responsibilities: Play a pivotal role in ensuring the effectiveness and reliability of DC3 cybersecurity systems and tools. Primary responsibility is to lead the testing and evaluation efforts for cyber operations tools used to protect critical technologies. Work closely with cross-functional teams to assess, test, and optimize these tools to maintain the highest level of security and operational effectiveness.

Required Experience:

A minimum of 10 years of experience with testing and quality analysis Demonstrated proficiency in quality assurance methodologies, test planning, and test case development.

Strong understanding of software and systems testing, including functional, performance, and security testing.

Exceptional analytical and problem-solving skills.

Project Management Professional Certification CompTIA Security+ Certified Information Security Manager

6.7.2.2 AFOSI Key Personnel

Project Supported: Copper Castle Responsibilities: Provide subject matter expertise in CI Cyber Operations Tools and Acquisitions. Play a critical role in enhancing and maintaining the cyber operations posture of AFOSI and associated partner organizations. The primary responsibility is to evaluate, implement, and support cybersecurity tools and technologies while actively contributing to the strategic acquisition and integration of new security solutions. Work closely with cross-functional teams to ensure efficient, robust, and secure cyber operations that protect AFOSI ability to gain and maintain and advantage in cyberspace.

Required Experience:

A minimum of 10 years of experience in military CI operations A minimum of 10 years of experience with Air Force technical collections platforms A minimum of 5 years of experience managing complex research and development programs with a focus on cyber operations tools

A minimum of 5 years of experience managing technical programs valued at over $30M annually

Project Management Professional Certification Data Security and Privacy Certification

Project Supported: Cyber Capabilities Cloud Responsibilities: Provide subject matter expertise in all areas of Information Assurance as related to operational platform security. Play a critical role in the execution of infrastructure assessments, the development of readiness exercises, and ensure compliance postures are documented. The primary responsibility will be the production of policy regarding Information Assurance, as well as the implementation of the controls associated with those policies and the remediation of findings contrary to accepted security posture. Responsible for the operations of all three phases of protect, detect, and respond.

Required Experience:

Minimum of 10 years in Incident Response, specifically targeting the protection of assets against Advanced Persistent Threats Minimum of 10 years evaluating cybersecurity products to ensure fit within security posture, overall compliance, and mission operations Minimum of 5 years writing cybersecurity policies with focus on DoD compliance and NIST Risk Management Framework Minimum of 5 years in planning, coordinating, or executing penetration testing.

Experience must include the remediation of the findings associated with the assessment.

Certified Information Systems Security Professional (CISSP) or IAT Level III equivalent

CompTIA Security+ or IAT Level II equivalent Required Education: Master’s Degree in Cybersecurity or related field

6.7.2.3 CDM Key Personnel

Work Role: Senior Operations Research Analyst Project Supported: Operations in the Information Environment Responsibilities:

Provide technical program management and system engineering support for integration and alignment of CDM OIE efforts. Support development of CDM strategies and technology roadmaps providing OIE solutions. Develop Phoenix Challenge agendas, capture and track issues, gaps and tasks and progress against them, on behalf of OUSD(I&S). Support OUSD and Headquarters Air Force (HAF) elements on build of annual response to Congress on OIE improvement progress. Advance development of multi-domain operations OIE live, virtual, and constructive training design concepts initiatives in line with HAF information warfare objectives.

Required Experience:

10 years Joint/Service intelligence or operations support planning; at least 3 years at the national support level 10 years Systems Engineering support 3 years Support to Service/Joint to OIE related activities Joint Military Planning Experience or Education Security+ Certification Required Education: Master's Degree in Systems Engineering

• 6.7.3 Contractor Professionalism: The Contractor shall present a professional appearance, maintain professional demeanor, and always conduct. Conduct their work assignments IAW project schedules. Function effectively and efficiently during extended periods of high pressure and stress. Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

6.8 Miscellaneous Paragraphs

• 6.8.1 Freedom of Information Act (FOIA): All official Government…