BESCAR PWS v5.docx
DOCX document 4 MB Posted
- Solicitation number
- 832572140
- Issued by
-
Defense Information Systems Agency
About this file
This is a Performance Work Statement (PWS) for the Basic Enabling Support for Collaboration, Analysis, and Research (BESCAR) Blanket Purchase Agreement, solicitation number 832572140, issued by the Air University Innovation Accelerator (AUiX) under the Air Education and Training Command. The PWS outlines a five-year BPA structure (one base year plus four option years) to support research, analysis, assessments, development, prototyping, testing, education, and training services that transform scholarly ideas into future force capabilities. The scope encompasses five main task areas: BPA and Call Order Management; Engineering Analysis and Prototyping; Field Studies and Analysis of Prototypes; Education, Innovation, and Exercise and Training Environment Development & Execution; and Information Technology System Design, Development, Integration, and Accreditation.
Performance will occur at both government and contractor facilities across multiple locations including Washington D.C., Nellis AFB Nevada, Hurlburt Field Florida, Wright-Patterson AFB Ohio, and Joint Base Lewis-McChord Washington, with occasional OCONUS travel. The contractor must provide an educational facility within 10 miles of Maxwell AFB Alabama with multiple classrooms, including a 50-person capacity room and specialized spaces for wargaming and laboratory work. Security requirements include Top Secret facility clearance with SCI and SAP access eligibility for personnel, and all work must comply with Section 508 accessibility standards. The contract structure includes firm-fixed-price CLINs for labor and cost-reimbursable CLINs for materials and travel, with performance standards requiring greater than 90% accuracy for all deliverables and resolution of revisions within one week.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| BESCAR_Sources_Sought.docx | DOCX document | |
| BESCAR_Sources_Sought.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Solicitation #TBR BESCAR
PERFORMANCE WORK STATEMENT (PWS)
| Award/Mod Effective |
| Version Date |
| Award |
| XX/XX/2025 |
Contract Number:
| Call Order Number: |
| Not Applicable (N/A) |
Contractor Name
| Tracking Number: |
| 832572140 |
| Follow-on to Previous Contract and Call Order Number: |
| N/A |
1. Contracting Officer’s Representative (COR).
a. Primary COR.
b. Alternate COR.
c. Property Administrator. N/A
2. Contract Title. Basic Enabling Support for Collaboration, Analysis, and Research (BESCAR)
3. Background.
Air University (AU) is a major component of the Air Force’s Air Education and Training Command (AETC). As the lead agent for Air Force education, AU provides the full spectrum of Air Force education to educate and develop air, space, and cyberspace warrior leaders in support of the National Defense Strategy (NDS). In April 2021, the Air University Innovation Accelerator (AUiX) was established as an idea and innovation accelerator to increase AU’s contributions to national security, global power completion, and the profession of arms. AUiX serves as a guide, coach, and mentor for AU students, faculty, and staff by connecting them with partners in Department of Defense (DoD), academia, and industry to take ideas “one step beyond” by collaborating to refine new ideas, problem sets, and concepts in order to become game-changing advancements with immediate warfighting utility. AUiX identifies opportunities for education, research, and engagement to develop new capabilities, strategies, and technologies to increase military effectiveness, ensuring ideas progress into deliverables by linking ideas to requirements. Through a process of exploration, concept development, and enterprise-wide integration across core functions, AUiX bridges the gap between strategy, innovation, and leadership by providing a future force design underscored by a need to quickly deliver novel ideas, material solutions, and education in support of national security.
4. Objectives:
The objective of this Blanket Purchase Agreement (BPA) is to collaborate with AU students, faculty, staff, DoD, Service, and Interagency partners to perform research, analysis, assessments, development, prototyping, testing, education, and training to refine and evolve scholarly ideas into future force capabilities. Ideas typically revolve around what AU idea owners (i.e., students and faculty) are teaching and researching, including computing, software and data integration and collection, knowledge management, education, wargaming and simulation, human performance, Intelligence, Surveillance and Reconnaissance (ISR), Artificial Intelligence (AI) and Machine Learning (ML), and systems improving miliary utility. Tasks performed will also involve engaging with AU stakeholders (including DoD, Service, and Interagency partners) through education innovation, collaboration, outreach, and future classroom services. The research, analysis, assessment, development, prototyping, testing, training, engagement, and support performed in this BPA shall enable AUiX to aggressively push forward change to support AU’s mission of enhancing national security and mission readiness through the pursuit of innovation. This BPA will be executed through the issuance of Call Orders (CO) that are determined to be within the scope and locations of this contract.
5. Scope.
The scope of this effort is to perform research, analysis, assessments, development, prototyping, testing, education, and training for AU and its DoD, Service, and Interagency partners.
The contractor shall perform services at CONUS sites at both Government and contractor facilities, with occasional Temporary Duty (TDY) OCONUS (e.g., United Kingdom) on a project-by-project basis.
6. Performance Requirements.
The following tasks may be included and/or specified in a CO.
| Task 1: BPA and Call Order Management |
| Task 2: Engineering Analysis and Prototyping |
| Task 3: Field Studies and Analysis of Prototypes |
| Task 4: Education, Innovation, and Exercise and Training Environment Development & Execution |
| Task 5: Information Technology System Design, Development, Integration, and Accreditation |
6.1 Task 1 – BPA and Call Order Management
6.1.1 Subtask 1 – BPA and Call Order Management. For each awarded CO, the contractor shall prepare a Call Order Management Plan (COMP) describing the overall technical approach, organizational resources and management controls to be employed to meet the cost, performance, and schedule requirements throughout CO execution. For each awarded CO, the contractor shall prepare a CO Monthly Status Report (MSR) monitoring the quality assurance, progress/status reporting, and program reviews applied to the CO.
The contractor shall prepare a BPA-level Quality Management Plan (QMP) to address how the contractor intends to implement quality control, quality assurance, and continuous process improvement.
Constraints: To be determined at the CO level.
Requirement: The contractor shall provide the COMP draft at 15 business days after CO award with the final at 30 business days after CO award. The COMP will be updated annually in accordance with (IAW) the CO option period awards. The contractor shall provide the CO MSR 30 business days after CO award with monthly updates provided, by the 5th business day of the following month.
The contractor shall provide the draft QMP 15 business days after BPA award and the final 30 business days after BPA award, with annual updates IAW the BPA option periods.
Deliverables:
| PWS Task# |
| Deliverable Title |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
| 6.1.1 |
| COMP |
| Contractor- Determined Format |
| Draft – 15 business days after CO award |
Final – 30 business days after CO award
| Standard Distribution* |
| Annually IAW the CO option period awards |
| 6.1.1 |
| CO MSR |
| Contractor- Determined Format |
| Initial – 30 business days after CO award |
| Two Copies to COR; Letter Only to Contracting Officer |
| Monthly, by the 5th business day of the following month |
| 6.1.1 |
| QMP |
| Contractor Determined Format |
| Draft – 15 business days after BPA award |
Final – 30 business days after BPA award
| Standard Distribution* |
| Annually IAW the ID/IQ option periods |
*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.
6.2 Task 2 - Engineering Analysis and Prototyping
6.2.1 Subtask 1 - Assess Technologies and Data Requirements. The contractor shall assess applicable systems to address mission needs for improved effectiveness and efficiency and research current technologies and performance metrics to develop recommendations to enhance those technologies and to develop recommendations for new technologies, derived requirements, and use cases. In researching system technologies and data requirements, the contractor shall perform Business Case Analysis (BCAs) and Analysis of Alternatives (AoAs) for methods and processes for developmental systems, operations systems, and decision systems. The contractor shall perform quality assessments and develop quality program plans for the selected systems, to include considering quality assessment criteria. The contractor shall identify technology trends that may impact these systems and discuss these trends in technical reports on systems that the Government selects for prototyping. The contractor shall research and assess technology for potential insertion or transfer to enhance planning systems, operations, and data decision systems.
6.2.2 Subtask 2 - Analysis, Design, and Development of System and Subsystem Prototypes. The contractor shall analyze, design, and develop prototype solutions for integration and automation of planning systems, operations systems, and data decision systems to address mission needs. The contractor shall conduct trade-off analyses and modeling and simulation to identify optimal solutions for prototyping and develop technical reports, interoperability documents, system specifications, and engineering drawings for the resulting prototypes. The contractor shall assemble a Technical Data Package (TDP) for each prototype and develop, modify, or validate the computer software and hardware associated with prototypes developed.
6.2.3 Subtask 3 - Computational Enhancement and Analysis. The contractor shall develop, modify, or validate the hardware and software used in prototypes and models of planning systems, operations systems, and data decision systems to address mission needs as well as the hardware and software used to collect and assess prototype test data. In addition, the contractor shall develop, modify, or validate user’s guides, programming guides, and diagnostic procedures, including procedures for error documentation associated with the hardware and software used for prototypes.
6.2.4 Subtask 4 - Development of Concepts of Operations and Tactics, Techniques, and Procedures for Prototypes. The contractor shall develop Concepts of Operations (CONOPs) and Tactics, Techniques, and Procedures (TTPs) for deploying and operating prototype systems and data platforms in demonstration venues as selected by the Government. The contractor shall assess characteristics such as workflow of a proposed prototype from the viewpoint of an individual user. The contractor shall identify how the prototype will operate to achieve its objectives, including any operational strategies, processes, or constraints that may affect how the prototype is developed. The contractor shall define the roles of all stakeholders throughout the prototyping process.
6.2.5 Subtask 5 - System Development and Integration. The contractor shall integrate subsystems, components, and subassemblies into assemblies for planning systems, operations systems, and data decision systems that the Government selects for prototyping. The contractor shall include development and integration of firmware, hardware, software, and inter-component and inter-system communications. The contractor shall develop engineering drawings and TDPs for systems and subsystems to be prototyped.
Constraints: To be determined at the CO level.
Requirement: To be determined at the CO level.
Deliverables:
| PWS Task# |
| Deliverable Title |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
| 6.2.1 |
| Business Case Analysis Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.1 |
| Analysis of Alternative Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.1 |
| Quality Assessment Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.1 |
| Technical Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Trade-Off Analysis Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Prototype Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Interface Control Documents |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Prototype System Design Specifications |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Engineering Drawings |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| TDPs |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.2 |
| Prototype Hardware & Software |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.4 |
| CONOPS |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.4 |
| TTPs |
| Contractor-Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.5 |
| Integration Engineering Drawings |
| Contractor-Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.2.5 |
| Integration TDPs |
| Contractor-Determined Format |
| 5th business day post completion |
| COR |
| As Required |
6.3 Task 3. Field Studies and Analysis of Prototypes
The contractor shall develop field operation plans for operating systems and data collection systems prototypes in the field. The contractor shall develop test execution and data collection plans to execute tests and gather resulting data in the field based on program requirements and information provided by the Government.
The contractor shall develop and deliver training concepts, courses, and related documentation for field operation of prototypes as well as the collection and analysis of prototype test data. The contractor shall develop and conduct training for systems, subsystems, and components developed or updated to inform the operation of the prototypes and any associated equipment necessary for the effective collection and analysis of prototype performance data.
The contractor shall perform site surveys and install, test, and perform ad hoc maintenance of communication, computer, and network equipment required for the accurate and timely collection of data during field studies and operations. The contractor shall conduct field assessments and studies, collect and analyze field data on prototype systems and subsystems, and document the findings in analysis reports. The contractor shall verify the operation and maintenance of prototype systems and subsystems during field operations, to include providing mechanisms for operators to report and troubleshoot problems.
Constraints: To be determined at the CO level.
Requirement: To be determined at the CO level.
Deliverables:
| PWS Task# |
| Deliverable Title |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
| 6.3 |
| Field Operations Plans |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.3 |
| Test Execution & Data Collection Plans |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.3 |
| Field Training Documentation |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.3 |
| Field Training Report |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.3 |
| Data Analysis Reports |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
6.4 Task 4. Education, Innovation, and Exercise and Training Environment Development & Execution
6.4.1 Subtask 1 - Education and Innovation. The contractor shall research, analyze, recommend, develop, conduct, and assess novel educational methodologies and materials to drive innovation through design thinking, continuous process improvement, strategy development, and leadership, including developing and executing student surveys and specifying recommendations to respond to lessons learned and identified gaps in training materials or methods. The contractor shall provide future classroom and educational technology and services to integrate lessons learned and innovative technologies and techniques.
6.4.2 Subtask 2 - Collaboration and Outreach. The contractor shall research and develop strategies, plans, and materials for innovation-type activities, include attending, planning, hosting, conducting, facilitating, documenting, and assessing leadership, innovation, and strategy engagements (e.g., meetings, conferences, and symposiums) focused on national security, defense, and military strategy; the Secretary of the Air Force (SECAF) seven operational imperatives; and Chief of Staff of the Air Force (CSAF) action orders. The Government estimates two to three engagement events per year with a typical duration of two to three days. Events may range from smaller events with approximately ten to 20 attendees to larger events with up to 100 attendees. Engagements may include collaboration activities with other schools, colleges, universities, industry, and joint and international partners in the exchange of ideas and concepts related to the education and research missions of AU.
6.4.3 Subtask 3 - Exercise and Training Environment Execution. The contractor shall research, analyze, recommend, develop, conduct, and assess suitability, utility, and limitations/constraints for integrated systems in exercises and training environments. The contractor shall provide mission trend analysis reporting, courses of action, and tactics, techniques, and procedures. The contractor shall examine courses of action associated with defining proposed changes and scope study efforts for establishing the proposed actions to execution. The contractor shall provide guidance for management of these actions while they are planned and executed. The contractor shall provide cyber and physical security services to support training environments. The contractor shall develop and execute training, scheduling, and evaluation processes in support of mission execution and analysis.
6.4.4 Subtask 4 – Modeling and Simulation and Wargaming. The contractor shall provide support for modeling and simulation activities, including multivariate modeling, statistics, mathematics and physics, and forming models to support simulations for decision-making across missions. The contractor shall support simulating real-world environments to provide realism to training and research activities and shall include new commercial tools where applicable to include AI. The contractor shall provide multidisciplinary support for analytic wargaming, leveraging design, forecasting, soft sciences and modeling techniques to introduce factors such as socio-political changes and test outcomes in advanced wargaming. The contractor shall support wargaming activities and efforts as follows:
· Plan, prepare, and design: arranging and managing venues, designing games and supporting workshops, crafting formats and agendas, developing scenarios, conducting research and modeling, literature reviews, acquiring and managing outside expertise and handling logistical activity.
· Execution: coordinating details, providing facilitation, managing and/or assisting with reservations and administration, staffing control team, oversight and ensuring objectives are met.
· Reporting: compiling post-game notes, compiling and delivering briefing materials, analyzing results and outcomes, preparing key findings, proceedings and insights customized by game.
· The contractor shall provide mission planning support, including conducting analysis, interviewing stakeholders, conducting literature reviews and research, hosting events such as conferences, workshops and games, creating analytic products, reports and briefings.
Constraints: To be determined at the CO level.
Requirement: To be determined at the CO level.
Deliverables:
| PWS Task# |
| Deliverable Title |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
| 6.4.1 |
| Innovation Education Materials |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.1 |
| Student Survey Report |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.2 |
| Outreach and Events Plans and Materials |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.2 |
| Event Report |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.3 |
| Training Plan |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.3 |
| Training Report |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.4 |
| Modeling and Simulation (or Wargame) Plan |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.4.4 |
| Modeling and Simulation (or Wargame) Report |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
6.5 Task 5 – Information Technology System Design, Development, Integration, and Accreditation
6.5.1 Subtask 1 - System Design. The contractor shall provide engineering and system design support for the development of improvements to existing IT capabilities and systems. The contractor shall design capabilities for critical operations, which include alterations to existing systems; integration and enhancements to systems and other system component interfaces; and development and modifications to new and existing software systems. The contractor shall perform technology and engineering analysis and evaluation of foreign systems, equipment, and technologies. The contractor shall perform design activities in support of new capability development that can be integrated into infrastructure. The contractor’s system design efforts shall detail how defined requirements will be implemented into the system. The contractor’s design specifications shall include how the system, component or new capability will be architected and built, as well as how the system will be integrated within the existing systems architecture or interfaced with external systems as applicable. The contractor shall include conducting fit/gap analysis, developing overarching technical architectures, and detailing specific functional elements and dependencies.
6.5.2 Subtask 2 - System Development. The contractor shall provide all engineering and development tasks required to build and test system capabilities and ensure the desired outcome can be traced back to design requirements. The contractor shall provide highly specialized system and network engineering services in support of the development of next generation operations infrastructure systems and network infrastructures. The contractor shall perform extensive system, network and software engineering, and technology validation and integration. The contractor shall develop unique capabilities and web-based solutions, which are required for the automation and optimization of network operations. The contractor shall modify, enhance, and/or remediate software code and applications from a wide range of commercial vendors to ensure system certification, accreditation, and effectiveness. The contractor’s solutions shall be centered on improving system performance while decreasing operations, maintenance, and sustainment requirements to ensure system affordability. The contractor shall provide engineering services to extend and expand existing system architectures. The contractor shall include adding new nodes and components to existing systems as well as integrating new technologies and capabilities. The contractor shall maintain both the existing as well as new components added to the system.
The contractor shall establish a test and evaluation process, which includes but is not limited to Independent Verification & Validation (IV&V) reviews, analysis, evaluations, inspections, and tests of the project’s technical capabilities, system behaviors, processes and interfaces, operational use, feasibility or practicality of the technology in a given operational environment, and durability of the system. Objectives of performing IV&V include:
| a. | Facilitate early detection and correction of cost and schedule variances |
| b. | Enhance management insight into process and product risk |
| c. | Support project life cycle processes to ensure compliance with regulatory, performance, schedule, and budget requirements |
| d. | Validate the project’s product and processes to ensure compliance with defined requirements |
6.5.3 Subtask 3 – Accreditation and Security. The contractor shall provide cybersecurity compliance, Information Assurance (IA) oversight & management, certification and accreditation, and the required security support services for current and future systems. These services shall be delivered using a systematic, disciplined approach to the evaluation of risk management, information security controls, and governing processes.
The contractor shall provide accreditation support based on the Risk Management Framework (RMF), applying risk management throughout the system lifecycle to identify, implement, assesses, and monitor all applicable security controls. The contractor shall author and develop all RMF artifacts required in support of accreditation including the Security Plan (SP), Security Assessment Report (SAR), Security Controls Traceability Matrix (SCTM), and Program Objectives, Actions, and Milestones (POA&M).
The contractor shall provide an Information System Security Officer (ISSO) to lead all IA efforts and act as the single point of contact for information system security matters for all stakeholders. The ISSO shall plan, execute and monitor the systems’ security posture and be supported by an Engineering team which provides a wide spectrum of RMF support including IV&V, configuration management, remediation, and documentation. The contractor shall design, develop, build, remediate and test systems to meet security controls and ensure cyber operations infrastructure systems are configured in accordance with applicable Security Technical Implementation Guides (STIGs).
The contractor shall implement security controls consistent with DoD IA architectures and policies, employing standard system engineering methodologies and security engineering principles. The contractor shall follow DoD STIG, Information Assurance Vulnerability Alert (IAVA) compliance, and National Institute of Standards and Technology (NIST) 800-53 standards to prevent and identify vulnerabilities and implement corrective actions.
Constraints: To be determined at the CO level.
Requirement: To be determined at the CO level.
Deliverables:
| PWS Task# |
| Deliverable Title |
| Format |
| Due Date |
| Distribution/Copies |
| Frequency and Remarks |
| 6.5.1 |
| Design Specifications |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.1 |
| Technical Architectures |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.2 |
| System Software |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.2 |
| System Hardware |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.2 |
| System Interfaces |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.3 |
| Network Test & Evaluation (or IV&V) Process |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.3 |
| SP |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.3 |
| SAR |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.3 |
| SCTM |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
| 6.5.3 |
| PO&AM |
| Contractor- Determined Format |
| 5th business day post completion |
| COR |
| As Required |
7. Performance Standards.
| Performance Standard |
| Acceptable Quality Level (AQL) |
| Surveillance Method |
| Task 1 – BPA and CO Management |
| Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions. |
Minimum Acceptable:
Contain required information, > 90% accuracy of all documents and reports, and delivered on time.
Any required revisions are:
| • | Resolved within 1 week |
| • | Accepted by COR |
| Calculation: |
100% review/inspection from the COR and/or Government Program Manager of delivered materials.
5% or less of error rate
| Task 2 – Engineering Analysis and Prototyping |
| Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions. |
Minimum Acceptable:
Contain required information, > 90% accuracy of all documents and reports, and delivered on time.
Any required revisions are:
| • | Resolved within 1 week |
| • | Accepted by COR |
| Calculation: |
100% review/inspection from the COR and/or Government Program Manager of delivered materials.
5% or less of error rate
| Task 3 – Field Studies and Analysis of Prototypes |
| Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions. |
Minimum Acceptable:
Contain required information, > 90% accuracy of all documents and reports, and delivered on time.
Any required revisions are:
| • | Resolved within 1 week |
| • | Accepted by COR |
| Calculation: |
100% review/inspection from the COR and/or Government Program Manager of delivered materials.
5% or less of error rate
| Task 4 – Education, Innovation, and Exercise and Training Environment Development & Execution |
| Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions. |
Minimum Acceptable:
Contain required information, > 90% accuracy of all documents and reports, and delivered on time.
Any required revisions are:
| • | Resolved within 1 week |
| • | Accepted by COR |
| Calculation: |
100% review/inspection from the COR and/or Government Program Manager of delivered materials.
5% or less of error rate
| Task 5 – Information Technology System Design, Development, Integration, and Accreditation |
| Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions. |
Minimum Acceptable:
Contain required information, > 90% accuracy of all documents and reports, and delivered on time.
Any required revisions are:
| • | Resolved within 1 week |
| • | Accepted by COR |
| Calculation: |
100% review/inspection from the COR and/or Government Program Manager of delivered materials.
5% or less of error rate
8. Incentives.
The identification of incentives (both positive and negative), if any, will be addressed at the CO level.
9. Place of Performance.
Mission Location: Maxwell AFB, Alabama (AL)
Place of Performance: Place of performance is CO dependent, but anticipated to be at Government and Contractor facilities including, but not limited to, Washington, District of Columbia (D.C.) National Capital Region (NCR); Nellis AFB, Nevada (NV); Creech AFB, NV; Hurlburt Field, Florida (FL); Eglin AF Base (AFB), FL; Honolulu, Hawaii (HI); Klamath Falls, Oregon (OR); Portland, OR; Montgomery, AL; Wright-Patterson AFB, Ohio (OH); and Joint Base Lewis-McChord, Washington (WA). Performance in other CONUS and OCONUS locations (e.g., United Kingdom) is anticipated, however, is currently anticipated to be accomplished with travel.
The contractor shall provide an educational and training space within 10 miles of Maxwell AFB, AL. It shall consist of multiple classrooms and suites (rooms) with one classroom with a minimum of a 50-person capacity, two larger suites for flexible teamwork exercises and events with minimum 15-person capacity, two smaller breakout classrooms with minimum capacity between 4-10 people, a suite for wargaming and modeling and simulation with a minimum 20-person capacity, and a laboratory suite with a minimum 4-person capacity. The contractor shall provide all necessary networking, information technology, furnishings, and supporting materials for the facility. This facility does not have a security requirement (e.g., unclassified space only is required).
Alternative work sites allow for regular telework or remote work flexibilities. Regardless of where work is performed, the Contractor shall ensure that work is completed effectively and that mission needs and requirements are met, without degradation of services. Also, the contractor may be required to account for the physical location of their personnel should this information be requested by the COR. The Contractor shall propose on-site rates for all work performed at an alternative work site. Incidental charges incurred while working at an alternative work site (e.g., electricity, internet) are not allocable to the contract and shall not be billed to the Government.
Local travel (defined as less than 50 miles) to and around the places of performance may be required throughout the period of performance. Local travel costs shall not be at the expense of the Government. Long distance travel within CONUS or OCONUS may be required to support the requirements of this PWS. Long distance travel within CONUS or OCONUS must be pre-approved in writing by the COR prior to the Contractor incurring the cost in support of this contract.
Secondary Place of Performance – Contingency Only. As determined by the COR, contractor employees may be required to work at a secondary place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, Government closure due to inclement weather). Additionally, the contractor may be required to account for the physical location of their personnel should this information be requested by the COR. Non-emergency/non-essential contractors should not report to a closed Government facility. The contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.
10. Period of Performance.
This contract will be a BPA with an ordering period of five years enabling COs with periods of one base year plus four option years.
Recognized Federal Holidays: The contractor is not required to perform services on Federal Holidays (as specified on the U.S. Office of Personnel Management website), unless otherwise specified by the COR.
Unplanned Federal Government Closure: In the event an authorized official, by either executive or legislative order, declares Federal offices closed (treated as a holiday for pay and leave purposes), the order only applies to Federal employees (unless otherwise stated in the order).
11. Security Requirements. This section supplements Block 13 of the Government provided DD Form 254, Contract Security Classification Specification. The following security requirements shall apply to this effort.
Each individual CO will have an associated DD-254.
The contractor shall coordinate visits with site Point of Contact (POC) providing at least a 72-hour notice (or according to each site security requirements) prior to any site access. Contractor personnel without security clearances performing any task under a CO PWS must be escorted by cleared Government personnel (civilian, military, or contractor).
References:
a. DoD Directive 5205.07, Special Access Programs Policy, 12 Sep 2024
b. DoD Manual 5205.07 Vol 1: DoD Special Access Program (SAP) Security Manual: General Procedures, 18 June 2015, Change 1, 12 February 2018
c. DoDM 5205.07V1_AFMAN 16-703V1_AFGM2020-01: Air Force Guidance Memorandum to DoDM 5205.07V1_AFMAN16-703V1
d. DoD Special Access Program (SAP) Security Manual: General Procedures, dated 16 January 2020 (Exp: 16 January 2021)
e. DoD Manual 5205.07 Vol 2: Special Access Program (SAP) Security Manual: Personnel Security, 24 November 2015, Incorporating Change 1, dated 12 February 2018
f. DoD Manual 5205.07 Vol 3: DoD Special Access Program (SAP) Security Manual: Physical Security, 23 April 2015, Incorporating Change 2, dated 12 February 2018
g. DoD Manual 5205.07 Volume 4: Special Access Program (SAP) Security Manual: Marking, 10 October 2013, Incorporating Change 1, dated 9 May 2018
h. DoDI 5205.11: Management, Administration, and Oversight of DoD Special Access Programs
i. Risk Management Framework (RMF) using the Joint Special Access Program Implementation Guide (JSIG) Rev 4, 11 April 2016, with the integrated Errata Sheet for JSIG, dated 8 October 2018
j. AF Policy Directive 16-7, Special Access Programs, 21 November 2017
k. AF Instruction 16-701, Management, Administration, and Oversight of Special Access Programs, 18 February 2014
l. Defense Federal Acquisitions Regulation Supplement (DFARS) 252.204-7012, revised 28 June 2019
m. US Air Force Security Marking Guide for Special Access Programs, Rev. 1, 16 October 2013, with FSE, dated 6 March 2015
n. DoD Manual 5200.01, Vol. 1 DoD Information Security Program: Overview, Classification and Declassification, 4 May 2018
o. DoD Manual 5200.01, Vol. 2 DoD Information Security Program: Marking of Classified Information, 14 May 2019
p. DoD Manual 5200.01, Vol. 3 DoD Information Security Program: Protection of Classified Information, 19 May 2013
q. DoD Manual 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017
r. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020
s. 32 CFR Part 117, “National Industrial Security Program Operating Manual (NISPOM)”, 24 February 2021
t. Security Executive Agent Directive 4, National Security Adjudicative Guidelines, 8 June 2017
u. DoDM 5400.07, Freedom of Information Act Program
v. DoDI 5230.24, “Distribution Statements for DoD Technical Information,” January 10, 2023
w. DoD Instruction 8510.01, “Risk Management Framework for DoD Systems,” July 19, 2022
x. DoD Manual 5105.21 Sensitive Compartmented Information Administrative Security Manual: Administration of Information and Information Systems Security
y. DoDI 5230.24, “Distribution Statements for DoD Technical Information,” January 10, 2023
z. DoD Issuances website where documents can be found is: https://www.esd.whs.mil/DD/DoD-Issuances/
aa. AF e-Publications website where documents can be found is: http://www.e-publishing.af.mil
11.1 Facility Security Clearance (FCL). Work performed under this contract/order is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) and Special Access Program (SAP) access eligibility for some personnel. Therefore, the company must have an interim or final Top Secret Facility Clearance from the Defense Counterintelligence and Security Agency Facility Clearance Branch.
11.1.2 Invalidated Facility Clearance. Companies with invalidated facility clearances (including those in partnerships, subcontracts, and Joint Ventures) are not eligible to bid on or be awarded any new or additional DISA classified contracts, subcontracts, or receive additional classified information except for information necessary for the completion of your current classified contracts. In addition, those companies with invalidated facility clearances will not be permitted access to all DISA networks. Performance on any DISA classified contracts, at any location, will not be authorized until it has been granted a FCL at the appropriate level by Defense Counterintelligence and Security Agency.
11.2 Security Clearance. All personnel performing on or supporting classified work on COs under this BPA in any way shall be U.S. citizens. Unclassified work including education and training may be performed by non-US citizens, following appropriate processes. The personnel security requirements for COs cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final security clearance eligibility delineated in the table below when performance starts.
The following table indicates the highest level of security clearance required (e.g., TOP SECRET//SCI). However, not all personnel working these tasks may require the highest level of clearance and may operate at unclassified or SECRET as applicable for the task and subtasks performed. The level of classified access also indicates the highest level of access and will be adjudicated via standard security procedures for granting those accesses. Furthermore, some tasking associated with education and training may be performed by non-US citizens.
| PWS Task / Subtask |
| Clearance Level |
| Level of Classified Access |
| Justification for Access to Classified |
| Task 1 – IDIQ and CO Management |
| Up to TOP SECRET |
| SCI, SAP, Alternative Compensatory Control Measures (ACCM) |
| Management of classified activities |
| Task 2 – Engineering Analysis and Prototyping |
| Up to TOP SECRET |
| SCI, SAP, ACCM |
Engineering analysis based on classified requirements or systems integration
| Task 3 – Field Studies and Analysis of Prototypes |
| Up to TOP SECRET |
| SCI, SAP, ACCM |
Analysis of classified requirements, systems, or field locations
| Task 4 – Education, Innovation, and Exercise and Training Environment Development & Execution |
| Up to TOP SECRET |
| SCI, SAP, ACCM |
| Training related to classified systems or at classified locations |
| Task 5 – Information Technology System Design, Development, Integration, and Accreditation |
| Up to TOP SECRET |
| SCI, SAP, ACCM |
| Information Assurance activities associated with classified data, networks, or at classified locations |
11.2.1 Individuals supporting CO Tasks / Subtasks that require(s) an interim or a final Top Secret security clearance will, immediately upon hire, require SCI access eligibility adjudicated by the DoD Consolidated Adjudication Facility or other federal adjudications facility to perform their duties. SCI processing for SCI eligibility will be coordinated with the supporting Government Security Manager and will begin immediately upon start of duty performance under the applicable CO.
All SCI* work under this BPA and COs will be monitored by COR/ACOR.
*The COR/ACOR must be indoctrinated into SCI to monitor the work.
11.3 Investigation Requirements. All personnel requiring Top Secret and SCI access under this ID/IQ contract and COs shall undergo a favorably adjudicated Tier 5 (T5) investigation (formerly known as a Single Scope Background Investigation (SSBI)) as a minimum requirement. Enrollment into Continuous Evaluation current within 5 years and reflected in Defense Information System for Security (DISS), would meet the requirement for a current Periodic Reinvestigation (PR).
11.3.1 All personnel requiring Secret access under this BPA and COs shall undergo a favorably adjudicated Tier 3 (T3) Investigation formerly known as a National Agency Check, Local Agency Check and Credit Check or Access National Agency Check and Inquiries as a minimum investigation. Enrollment into Continuous Evaluation current within 5 years and, reflected in DISS, would meet the requirement for a current PR.
11.3.2 The contractor is required to have personnel cleared with an interim or final Top Secret (as specified in the table located in section 11.2) at BPA and CO start date. If contractor personnel are replaced during performance of the contract/order, replacement personnel should also have interim or final clearance Top Secret (as specified in the table located in section 11.2).
11.4 Visit Authorization Letters (VAL). Visit requests shall be processed and verified through the Defense Information System for Security (DISS) by the specific CO organization’s Security Management Office (SMO). For AU COs, SCI visit notices will utilize DISS and be routed through the 42 Air Base Wing (42ABW) Information Protection Office (SMO CODE – SSO AU) and collateral non-SCI visit notices will be routed through the contractor security office.
11.4.1 VAR Package. VARs must be received via email and require pre-approval from the assigned COR five business days in advance of the report date. The VAL/Visit Authorization Request (VAR)/ Visiting Termination Notice (VTN) should be sent via email to the appropriate COR. The VAL/VAR/VTN should be sent using in a locked “Zip” file in one e-mail and then followed-up by another e-mail with the password to unlock the Zipped file, because it contains sensitive information covered by the Privacy Act.
Documents to include in the VAR Package:
1. Inter-office Memorandum (IOM)
2. DD Form 254 Prime and/or Subcontractor (Sub) (Good Standing approval emails for current option year)
3. Contractor VAL signed by the Contractor Facility Security Officer (FSO)
If DISS is not available, the VAL must contain the following information on company letterhead
· Company name, address, telephone number, facility security clearance
· CAGE CODE
· Contract/Order Number
· Name, social security number (SSN), date and place of birth, and citizenship of the employee intending to visit
· Certification of personnel security clearance and any special access authorizations required for the visit (type of investigation & date and adjudication date & agency)
· Name of COR/Alt COR
· Dates or period the VAL is to be valid
11.4.2 VTN Package. The Contractor will forward a VTN letter to the COR identified in the PWS/CO/Sub for all employees leaving the contract/CO/subcontract.
11.4.2.3 In addition, the CORs and security managers shall inform the AU Special Security Office when contractor personnel are removed for cause from a contract/order. This step is being added to prevent contractor personnel removed for security related issues from returning to the Government agency without appropriate vetting. This step will also provide security with pertinent information to make an informed decision regarding potential contractor employees’ access to secure facilities and sensitive information. “For Cause” is information regarding an individual that falls into one or more of the actions or incidents that are within one of the 13 adjudicative guidelines as cited in the Security Executive Agent Directive (SEAD) 4, which include:
· Allegiance to the United States
· Foreign Influence
· Foreign Preference
· Sexual Behavior
· Personal Conduct
· Financial Considerations
· Alcohol Consumption
· Drug Involvement and Substance Misuse
· Psychological Conditions
· Criminal Conduct
· Handling Protected Information
· Outside Activities
· Use of Information Technology
Other actions:
· Incidents involving violence in the workplace or harassment
· Misuse of time
· Inspector General or General Counsel related inquiries
· Failure to comply with security policies and procedures
· Other reasons that prompted removal of a contractor
The VTN must contain the following information on company letterhead
· Company name, address, telephone number, facility security clearance
· CAGE CODE
· Contract/Order Number
· Name, SSN, date and place of birth, and citizenship of the employee
· Date contractor Common Access Card (CAC) was collected
· Name of COR/Alt COR
· Termination Date
· Reason for Termination
11.5 Security Contacts. 42ABW Security Personnel can be contacted for Industrial or Personnel Security related issues at (334) 953-5008 or via email at tyrell.rice@us.af.mil.
11.6 Information Security and other miscellaneous requirements.
11.6.1 Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the Government facility.
11.6.2 Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic safety and security training and briefings will be provided by Government security personnel. Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor will not be able to provide service on this contract/order.
11.6.3. Contractor employees with an incident report in DISS who have had their access to classified suspended will not be permitted to fill positions requiring access to classified information on a DISA contract/order.
11.6.4 The Contractor shall not divulge any information, classified or unclassified, about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.
11.6.5 The authority for the contractor personnel to regain access must be granted by the 42 Air Base Wing (ABW) Information Protection Office.
11.6.5.1 The Government retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government.
11.6.5.2 The Government retains the right to revoke contractor personnel access to Government facilities and networks, who violates one or more of Security Personnel Adjudicative guidelines, harassment or violence in the workplace while assigned to a contract clearly conflict with the interest of the Government.
11.6.5.3 If contractor employee is accused of violating state or federal laws and/or Government professional conduct policies or regulations, then the Government may require that such contractor employee be removed from Government premises and/or that such contractor employee be removed from supporting this contract, pending the duration and outcome of a Government investigation if the Contracting Officer finds that the conduct or violation alleged has the potential to negatively interfere with contract performance or operations at a Government facility. Only the Contracting Officer can make such a request on behalf of the Government. Removal of contractor employee shall not negatively impact contract performance.
11.6.6 Contractor personnel will generate or handle documents that contain Controlled Unclassified Information (CUI) at the Government and/or contractor facility. Contractor personnel will generate or handle documents that contain Proprietary, Contract Sensitive, or similarly designated information at the Government and/or contractor facility. Contractor personnel will have access to, generate, and handle classified material in accordance with the DD-254, which will be updated as appropriate. All contractor deliverables shall be marked IAW DoDM 5200.01, Vol. 3, DoD Information Security Program: Protection of Classified Information; DoDI 5200.48, Controlled Unclassified Information (CUI); and DoDM 5400.07, Freedom of Information Act Program, unless otherwise directed by the Government. The contractor shall comply with the provisions of the DoD Industrial Security Manual for handling classified material and producing deliverables. The contractor shall comply with NIST SP 800-171 Protecting CUI in Nonfederal Systems and Organizations and DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.
11.6.7 The Contractor shall afford the Government access to the contractor’s facilities, installations, operations, documentation, databases and personnel used in performance of the contract/order. Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of data or to the function of IT systems operated on behalf of DoD, and to preserve evidence of computer crime.
11.6.8 For Technical Expert Status Accreditation (TESA) requests, the contractor shall coordinate with the COR and submit request via European Contractor Online Processing System (ECOPS): https://ecops.ext.eur.army.mil
12. Government Furnished Property (GFP)/Government-Furnished Equipment…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .