Attachment 01 - 20240402 - D3I2 D1 SOW.pdf

W9113M24R0070 Attachment 01 Statement of Work (SOW) Design, Development, Demonstration and Integration II (D3I2) Domain 1

02 APR 2024 (REV 00)

STATEMENT OF WORK (SOW)

FOR

DESIGN, DEVELOPMENT, DEMONSTRATION, AND INTEGRATION II (D3I2)

PROGRAM

SPACE, HIGH ALTITUDE, AND MISSILE DEFENSE DOMAIN

02 APRIL 2024 (REV00)

Prepared by:

United States Army Space and Missile Defense Command (USASMDC)

Redstone Arsenal, AL

TABLE OF CONTENTS

1.0 OVERVIEW

1.1 MISSION

1.2 BACKGROUND

2.0 PROGRAM OBJECTIVE

2.1 OBJECTIVE

2.2 ANCILLARY SUPPORT

2.3 SECURE ENVIRONMENT CONTRACTING

2.4 PERSONAL SERVICES/INHERENTLY GOVERNMENTAL FUNCTIONS, CLOSELY

ASSOCIATED WITH INHERENTLY GOVERNMENTAL FUNCTIONS

3.0 TECHNICAL REQUIREMENTS

3.1 TECHNICAL SUPPORT AREAS

3.2 PERFORMANCE REQUIREMENTS

4.0 GENERAL REQUIREMENTS

4.1 PROGRAM MANAGEMENT

4.2 KEY PERSONNEL

4.3 REPORTS AND DATA DELIVERABLES

4.4 PROGRAM STATUS REVIEWS (PSRs)

4.5 OPTIONAL ORDERING PERIOD

4.6 RAMP ON/RAMP OFF

4.7 MID-PROGRAM REVIEW AND NEW ENTRANT PROCESS

4.8 COMPLETION NOTICE

4.9 TASK ORDER OMBUDSMAN

4.10 SERVICES DURING CRISIS

4.11 IDENTIFICATION OF CONTRACTOR EMPLOYEES

4.12 DEMILITARIZATION, DISPOSAL, RECYCLING AND POLLUTION PREVENTION

4.13 NON-DEVELOPMENTAL ITEMS and COMMERCIAL PROCESSES

4.14 SAFETY

4.15 ENVIRONMENTAL REQUIREMENTS

4.16 QUALITY CONTROL

4.17 CERTIFICATION

5.0 SECURITY

5.1 SECURITY REQUIREMENTS

5.2 ADDITIONAL SECURITY REQUIREMENTS/TRAINING

5.3 ACCESS CONTROL

6.0 PLACE OF PERFORMANCE/DUTY HOURS/TRAVEL

6.1 PLACE OF PERFORMANCE

6.2 DUTY HOURS

6.3 TRAVEL

7.0 CONTRACTOR RESOURCES

7.1 GFP/GFE/GFI/GFS/GFF

7.2 CONTRACTOR-ACQUIRED PROPERTY

8.0 CONTRACTOR MANPOWER REPORTING

9.0 DATA RIGHTS ASSERTIONS AND INTELLECTUAL PROPERTY

9.1 CDRLs

9.2 DEFERRED ORDERING

9.3 ASSERTIONS

9.4 SPECIAL WORKS

9.5 REPORTING "SUBJECT INVENTIONS”

10.0 PRODUCT OWNERSHIP

11.0 REPORTING AND DATA DELIVERABLES

12.0 DISTRIBUTION STATEMENTS TO CONTROL TECHNICAL AND OPERATIONAL

INFORMATION DATA

13.0 PUBLIC RELEASE OF INFORMATION

14.0 QUALITY

14.1 QUALITY ASSURANCE SURVEILLANCE PLAN

14.2 PERFORMANCE OBJECTIVES/METRICS

TABLE 1 – LIST OF CDRLS

1.0. OVERVIEW.

1.1. MISSION.

USASMDC develops and provides current and future global space, missile defense, and high altitude (HA) capabilities to the Army, joint force, and allies and partners, to enable multi-domain combat effects; enhance deterrence, assurance, and detection of strategic attacks; and protect the Nation. USASMDC also serves as the Army operational integrator for global missile defense and conducts mission-related research and development in support of Army strategic, operational, and tactical missions.

1.2. BACKGROUND.

1.2.1. USASMDC requires a contractual vehicle that will fulfill a gap in the ability to design, develop, demonstrate and integrate products focused on space, space control, ground-based missile defense, and HA capabilities. The requirement includes support to space and missile defense operations, planning, integration, control and coordination of Army forces and capabilities in support of U.S. Northern Command (USNORTHCOM), U.S.

Space Command (USSPACECOM) and U.S. Strategic Command (USSTRATCOM) missions (deter aggression/conflict, defend United States [U.S.]/allied interests, deliver space combat power, develop ready and lethal joint warfighters, conduct strategic deterrence, integrated missile defense, situational awareness, and space operations). In addition, USASMDC requires support for research and development (R&D) of material solutions, as well as combat development solutions in support of U.S. Combatant Commands (CCMDs) for space, missile defense, and HA missions; and mission-related R&D in support of Title 10 responsibilities; and other requirements identified in the basic contract SOW or individual task order (TO) performance work statements (PWSs) (or elsewhere in the contract) that enable the Warfighter to effectively support USNORTHCOM, USSTRATCOM, USSPACECOM, other CCMDs, Department of Defense (DoD), other Services and other Government agencies in the technical support areas (TSA) listed within Section 3.1.

1.2.2. TSAs listed in Section 3.1 are representations and not all-encompassing or exclusive. It is anticipated that this SOW will provide USASMDC with the ability to meet its mission requirements as outlined in Section 1.1 above.

2.0. PROGRAM OBJECTIVE.

2.1. OBJECTIVE.

In support of the D3I2 Program, the Government may issue individual TOs to fulfill performance requirements identified in Section 3.2 related to the TSA requirements identified in Section 3.1. Note that except as noted in Section 7.0 of this SOW the contractor is required to provide all personnel, material, equipment, and other items to meet these performance requirements identified in Section 3.2 as they relate to the TSAs identified in Section 3.1.

2.1.1. The basic contract performance requirements that may be supported by TOs are set forth in Section 3.2. These requirements are not meant to be definitive, but rather represent, in summary form, the general areas to be supported. Therefore, this SOW is deemed to be a basic expression of the contract requirements. Specific performance requirements will be set forth in individual TOs issued during the course of the basic contract’s ordering period.

2.1.2. This is an R&D services contract. The performance requirements defined herein include (but are not limited to) technology gap identification, design, development, modernization, fabrication, integration, modification, and testing of limited quantity production, prototypes, systems, subsystems, components, sub-components, technologies, innovations, processes, and architectures. In addition, the requirements include delivery, product transition, fielding, sustainment, operations, and maintenance of R&D projects, R&D systems and sub-systems, and prototypes. These requirements are applicable for the TSAs described above and as further delineated below.

2.1.3. The TO requirements can encompass a full range of R&D work from technology search and requirements generation through prototyping and production, as well as encompassing systems engineering and integration and support of USASMDC missions and functions. The TO requirements under the D3I2 Program can be applicable to live, virtual and simulated environments and will be inclusive of hardware, software, documentation and all required deliverables.

2.1.4. Each TO will contain additional specific details that will further define the required services and/or deliverable products to include (but not limited to) technology benefit/regression analysis, retrofit requirement analysis, technology investment, and feasibility issues for all performance requirements.

2.1.5. Performance of TO requirements may call for solutions that cross over multiple disciplines, include ancillary support, and require commercial and/or non-commercial items that utilize a variety of TO types and/or contract line item numbers/sub-contract line item numbers (CLIN/SLIN) including fixed price (all types), cost reimbursement (all types), time and materials/labor hour, or a hybrid mix of TO and/or CLIN/SLIN types.

2.2. ANCILLARY IN-SCOPE SUPPORT; INCIDENTAL ADVISORY AND ASSISTANCE

SERVICES (A&AS).

At the TO level, ancillary in-scope support is a service that is integral and necessary as part of a proposed total integrated solution, but for which there is not a labor category specified in Attachment 02, titled “D3I2 Labor Category Descriptions and Minimum Requirements.” Ancillary in-scope support may also include allowable other direct costs such as travel, materials, equipment, subcontractors, senior mentors, or subject matter experts, etc. required to obtain a total solution at the TO level.

2.2.1. Ancillary in-scope services. For TO level specialized professional and non-professional services labor for which the expertise required or duties performed are within the scope of this SOW but are so specialized that they are not explicitly defined in any labor category description in Attachment 02, titled “D3I2 Labor Category Descriptions and Minimum Requirements.” The TO contracting officer (KO) may allow, and the contractor may propose, a labor category(ies) at the TO level not identified in Attachment 02, titled “D3I2 Labor Category Descriptions and Minimum Requirements”, provided that the contractor complies with all applicable basic contract clauses and labor laws, including the Service Contract Labor Standards or Construction Wage Rate Requirements, if applicable.

2.2.1.1. Professional services are those services requiring a professional license or other legal authorization.

2.2.1.2. Non-professional services are those services not specially identified as professional services, as well as manual laborers or other “blue-collar” workers (e.g., work involving repetitive operations with their hands, physical skill and energy; employees in such positions such as production, maintenance, construction and similar occupations such as carpenters, electricians, mechanics, plumbers, iron workers, craftsmen, operating engineers, longshoremen, construction workers and laborers).

2.2.2. Ancillary in-scope supplies. A TO level ancillary commercial or non-commercial supply or product that is integral and necessary to complete a total solution. When providing ancillary support for IT services and/or components, the contractor shall promote IT initiatives and best practices that support Federal Government operational requirements for standardized technology and application service components, to include facilitate integration requirements for broad Federal IT and E-Gov initiatives, as well as promote the sharing, consolidation, and re-use of business processes and systems across the Federal Government. The contractor shall promote the use of open-source solutions and open technology development where practicable to enable this re-use.

2.2.3. Incidental A&AS. A&AS requirements are considered ancillary in-scope support and can be performed at the TO level when they are incidental to, and in support of, the primary purpose of a TO issued under this basic contract; a TO that is only for A&AS or is predominately an A&AS TO is not authorized under this basic contract. See Federal

Acquisition Regulation (FAR) Subpart 37.2 (as supplemented by the Department of Defense Federal Acquisition Regulation Supplement [DFARS] and the Army Federal Acquisition Regulation Supplement [AFARS]) for further information and limitations regarding A&AS.

2.3. SECURE ENVIRONMENT CONTRACTING (SEC).

The basic contract authorizes TOs to be issued and subsequently performed under SEC conditions. It is the contractor’s full responsibility to adhere to Army Regulation (AR) 715- 30 (Secure Environment Contracting), as well as USASMDC and customer policies. See Section J, Attachment 04, titled “Special Contract Instructions.”

2.4. PERSONAL SERVICES/INHERENTLY GOVERNMENTAL FUNCTIONS, CLOSELY

ASSOCIATED WITH INHERENTLY GOVERNMENTAL FUNCTIONS.

2.4.1. This requirement identifies services that are strictly non-personal in nature and do not involve personal services or inherently governmental functions. However, while performance of this effort does not require services that are inherently governmental functions, it may include functions that are closely associated with inherently governmental functions as defined in Title 10, U.S. Code, Section 4508. Appropriate DoD military or civilian personnel cannot reasonably be made available to perform these functions. However, appropriate military or civilian personnel of the DoD will: (1) oversee contractor performance of the contract; and (2) perform all inherently governmental functions associated with the efforts to be performed under this contract.

2.4.2. In performance of this effort, the contractor shall be required to perform expert experienced-based mentoring, teaching, training, advice, and recommendation to senior military officers, staffs, and students as they participate in war games, warfighting courses, operator training, operational planning, operational exercises, decision-making exercises, technical interchanges, map exercises, and other system and acquisition support activities.

2.4.3. Under this contract, the contractor, as an independent contractor and not an agent or employee of the Government, shall furnish the Government with all necessary labor, services, supplies, equipment, and materials, except as specified to be furnished by the Government.

3.0. TECHNICAL REQUIREMENTS.

3.1. TSAs.

3.1.1 TSA 1, Space and HA.

The Space and HA TSA includes all aspects of military, civil and commercial space operations to include launch, space segment (platform and payload), HA segment (platform and payload), ground segment communications between the ground segment and space or HA segments (platform and payload), ground segment, space related user segment, and management of information derived from space or HA and aerial layer sources. The space support area also includes space force enhancement, space control, space support and space force application, to include the design, development, and integration of components that are integral to conducting testing, assessments, or a development event. The following sub-areas fall under the Space and HA TSA.

3.1.1.1. Platforms (for example, but not limited to, high altitude airships, high altitude aircraft, delivery systems, satellites, satellite buses, very low Earth orbit hybrid buses, surveillance and reconnaissance, electronic warfare, nuclear effects, survivability, etc.).

3.1.1.2. Payloads, including small satellites and high-altitude payloads (for example, but not limited to sensors, surveillance and reconnaissance, electronic warfare, communications, Positioning/Navigation/Timing, nuclear effects, survivability, software-based payloads, etc.).

3.1.1.3. Ground Stations (for example, but not limited to mission command, data processing centers, antennas, networks, mission software, etc.).

3.1.1.4. Communications (for example, but not limited to, mission command, data transmission, voice transmission, electronic warfare, nuclear effects, survivability, etc.).

3.1.1.5. Space power Disciplines/Space Control (for example, but not limited to offensive and defensive counter space and space situational awareness).

3.1.2. TSA 2, Missile Defense.

The global integrated missile defense support area includes all aspects of missile defense (including ballistic, non-ballistic, and cruise missiles) to include detection and characterization of air and missile threats, mission command, active defense and passive defense and attack operations. This support area also includes all aspects of global strike objectives. This support area further includes offensive operations, elimination operations, interdiction operations, active defense, passive defense, weapons of mass destruction consequence management, security cooperation and partner activities, and threat reduction cooperation. The following sub-areas fall under the Missile Defense

TSA.

3.1.2.1. Platforms (for example, but not limited to, Unmanned Aircraft Systems (UAS), Unmanned Aerial Vehicles, low and mid altitude airships, low and mid altitude aircraft, surveillance, and reconnaissance, etc.).

3.1.2.2. Ground Systems (for example, but not limited to, battle management control, mission command, launchers, mobile ground systems, telescopes, power systems, cooling systems, fire control, etc.).

3.1.2.3. Sensors (for example, but not limited to, radars, laser radars, passive camera systems, other devices used to measure physical phenomena, surveillance, and reconnaissance, etc.).

3.1.2.4. Missile Systems (for example, but not limited to, aerodynamic (cruise missiles, glide vehicles, etc.) ballistic (Short Range Ballistic Missile, Medium Range Ballistic Missile, Intercontinental Ballistic Missile, etc.), kill vehicles, kill enhancements, rockets and re-entry vehicles, targets, delivery systems, rocket motors, countermeasures, seekers).

3.1.2.5. Directed Energy (DE) Systems and Components (for example, but not limited to, laser beam controllers, high powered microwave (including non-space related threats posed by small UAS (sUAS) and Improvised Explosive Devices), pulsed power, and non-space related R&D of existing and emerging high energy laser technologies).

3.1.2.6. Operational and Range Testing (for example, but not limited to, telemetry, lethality, kill assessment, flight termination, etc.).

3.1.2.7. Survivability and Nuclear Effects (for example, but not limited to, devices, nuclear monitoring, nuclear effects catalog/environments, etc.).

3.1.2.8. Communications (for example, but not limited to, mission command, data transmission, voice transmission, electronic warfare, nuclear effects, survivability, etc.).

3.2. PERFORMANCE REQUIREMENTS.

3.2.1. REQUIREMENTS DEFINITION, CONCEPT/ARCHITECTURE DEVELOPMENT,

AND TECHNOLOGY SEARCH.

The requirements specified in Section 3.2.1 are intended to be incidental to efforts performed under Sections 3.2.2 through 3.2.13; therefore, a TO will not be issued under this contract solely for the purpose of requirements definition, concept/architecture development, or technology search. Specific TO requirements may include (but are not limited to) technology gap identification, digital engineering, model-based system engineering, design, development, modernization, fabrication, integration, modification, and testing of limited quantity production, prototypes, systems, subsystems, components, sub-components, technologies, innovations, processes, and architectures; delivery, product transition, fielding, sustainment, operations, and maintenance of R&D projects, R&D systems and sub-systems, and prototypes; R&D work from technology search and requirements generation through prototyping and production, as well as encompassing systems engineering and integration; and technology benefit/regression analysis, retrofit requirement analysis, technology investment, and feasibility issues in support of the listed task areas in the following paragraphs.

3.2.1.1. Requirements definition.

3.2.1.1.1. The contractor shall support the definition of technical requirements and the search for technologies that could meet the needs of the warfighter for the TSAs as required by the specific TO. Contractor performance may include (but is not limited to) the definition of performance, system architecture and quality requirements;

product/component specifications; and applicable technologies both evolutionary (non-disruptive) and revolutionary (disruptive).

3.2.1.1.2. The contractor shall develop a technical requirements verification matrix, which articulates how technologies will be verified by either test, inspection, demonstration, or other means. The technical requirements shall be traced and prioritized when required by the TOs.

3.2.1.1.3. The contractor shall conduct an evaluation of performance requirements from an economical, operational, and technical approach in respect to feasibility, practicality, and functionality accepted constraints, to include system of system interactions, utilizing the Joint Capabilities Integration and Development System (JCIDS) or equivalent documentation guidelines.

3.2.1.1.4. The contractor shall conduct a technical examination of system deficiencies, technological needs, and analysis of current technology candidates and identification of technology investment areas.

3.2.1.2. Concepts, Architectures, and Capabilities Development.

3.2.1.2.1. The contractor shall flow top level requirements down to systems, subsystems, components, and lower levels which the requirements are to be used for design and development of material or combat development solutions.

3.2.1.2.2. The contractor shall participate in or conduct JCIDS or equivalent analysis and prepare supporting documentation for development of such as (but not limited to);

the Functional Area Analysis, Functional Needs Analysis, Functional Solutions Analysis, Abbreviated Capability Development Document, Initial Capability Document, and Capability Development Document. This participation is meant to assist other contractors responsible for this work to ensure they accurately analyze the technology.

3.2.1.2.3. The contractor shall identify and develop requirements against objectives that include future potential for upgrades and possibilities for new requirements based on project research and flexibility. The contractor shall include potential growth alternatives outside its current objectives as part of the technical examination of the project.

3.2.1.2.4. The contractor shall participate in Military Utility Assessment (MUA) or Joint- MUA activities and prepare supporting documentation for development and completion of such as part of Joint Capability Technology Demonstrations (JCTD).

3.2.1.3. Technology Search.

3.2.1.3.1. The contractor shall identify, investigate, research, analyze and report available capabilities, technologies, and research that will potentially meet current and emerging Warfighter needs. Examples of TO requirements include but are not limited to: (1) identify capability gaps; and (2) investigate technology solutions ready for use in an operational or tactical environment from a variety of sources such as Government laboratories and materiel developers, academia, foreign and multi-national environments, commercial sector, open source, Government-off-the-shelf, and commercial-off-the-shelf (COTS).

3.2.1.3.2. The contractor shall assess and report technology solutions for potential benefit.

3.2.1.4. The contractor shall develop, refine, and provide input to Army and Joint concepts, architectures, and capabilities documents. Examples of TO requirements include (but are not limited to) the tasks described below.

3.2.1.4.1. The contractor shall provide input to Joint Concepts, Joint Integrating Concept Capability-based Assessments, Training and Doctrine Command (Army) capstone, operating concepts, and functional concepts and concept capability plans.

3.2.1.4.2. The contractor shall develop architectures such as operational, technical, functional, systems, information, and others.

3.2.1.4.3 The contractor shall identify, assess, and document Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P) solutions, which produce force capabilities and attributes prescribed in approved Joint and Army concept documents.

3.2.1.4.4 The contractor shall provide input to the development and refinement of Joint and Army capability documents to include, but not limited to, the concept for Army theater space support in Joint operations, Army space operations concept capability plan, and global ballistic missile defense concept capability plan.

3.2.1.4.5 The contractor shall develop input to identify space and missile defense requirements and participate in the Joint and Army Integrated Capability Development Teams.

3.2.2. DESIGN.

The contractor shall possess an in-depth understanding of the detailed intricacies of system construction, component construction, and technologies, and the design details of the fundamental parts that make up a system to include understanding of interdependencies, platform or architecture physical constraints, available energy, integration, input and output limitations, and others. The contractor shall produce a design for hardware and/or software systems as defined in TO requirements. The contractor shall utilize Computer Aided Design and Computer Aided Systems Engineering (CASE) software (or other software if directed by a task order or approved by the cognizant contracting officer) to develop architectural models. As required by the individual TO, the contractor shall create and provide all documentation and reporting for the design. Specific TO requirements may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.2.1. The contractor shall conduct research and technical examination of technological needs, component or subcomponent enhancements, and system requirements to increase functionality and/or performance.

3.2.2.2. The contractor shall articulate, define, and select system technical components; analyze existing or current technology candidates; use theoretical and practical insight to narrow potential options based on practicality and feasibility; define performance metrics and pass/fail criteria; and develop schedules with associated cost analysis and implementation issues.

3.2.2.3. The contractor shall analyze components to determine alternatives; develop and refine approaches or solutions to address the shortfalls and create a solution-based approach which increases system functionality and/or system performance or reduces life-cycle costs and sustainability requirements.

3.2.2.4. The contractor shall examine innovations and/or enhancements based on solving system/component inadequacies and analysis of potential current technology candidates by identification of technology maturity level and associated impact to form, fit, function, and performance.

3.2.2.5. The contractor shall explicitly identify details that aid in decisions to proceed with sub-component bench testing, prototype development or fabrication.

3.2.2.6. The contractor shall identify coupled designs using existing systems into a new architecture or design of new and future products.

3.2.2.7. The contractor shall identify technology readiness level challenges and provide risk analysis/mitigation plans in terms of technical complexity, cost, schedule, special material development and alternative technology development paths.

3.2.2.8. The contractor shall identify technology maturity levels relevant to current and past uses or demonstrations; relevant to performance, functionality, and implementation interfaces; and relevant to retrofit interface modification requirements.

3.2.2.9. The contractor shall develop detailed system alteration schemas or new design approaches that are focused on advancing theoretical concepts, technology enhancement ideas, innovations, existing designs, or conventional component coupling in order to create higher fidelity system designs. The contractor shall be able to describe the new system of modules, components, technologies, or subsystems with varying levels of fidelity and maintain traceability between system requirements, analysis, and system design.

3.2.2.10. The contractor shall develop designs (inclusive of systems, components, and sub-components) and systems architectural models using Systems Modeling Language (SySML) (or other software if directed by a task order or approved by the cognizant contracting officer) to meet TO design requirements using, sciences, mathematics, engineering sciences, and other scientific means in an iterative process.

3.2.2.11. The contractor shall provide documentation such as technical data packages (TDPs), flow charts, schematics, drawings, training plans, test plans, source code, block diagrams, activity diagrams, parametric diagrams, and presentations, etc., as required by each TO.

3.2.2.11.1. The contractor shall define TDP maturity as required by each TO. TDP are generally classified into four maturity levels, from least to most mature they are Conceptual, Developmental, Product, and Commercial. TDPs define the physical and functional characteristics of the accepted configuration of the item and its subordinate assemblies, subassemblies, and parts.

3.2.2.11.2. The contractor shall provide digital copies of engineering modification orders, modification instructions, and modification drawings. The contractor shall deliver technical design packages in accordance with Military Standard 31000B as required by each TO. Technical design packages shall include (but are not limited

to) as-built drawings, specifications, parts/data lists, wiring lists, application lists, software designs, computer software code (executable/operating/source code), software/firmware development tools, firmware, algorithms and software operating manuals, and special packaging instructions.

3.2.3. DEVELOPMENT.

The contractor shall possess an in-depth understanding of the requirements, designs, and enhancement methods used for developing products and/or architectures for the purposes of demonstrating functionality, performance, or feasibility of capability. The contractor shall develop hardware and/or software systems necessary to build/fabricate prototypes or limited production quantities of systems as defined in each TO utilizing modern software development methodologies with continuous integration/continuous delivery (such as Agile and development, security, and operations [DevSecOps]) to support rapid delivery and to demonstrate functionality, performance, or feasibility of a mission capabilities. The contractor shall create and provide all documentation and reporting for the developed system as required by each TO. Specific TO requirements may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.3.1. The contractor shall provide theoretical versus practical performance, and determination of ability to meet functional/objective design metrics.

3.2.3.2. The contractor shall define, propose and/or conduct technology development initiatives suitable for meeting enhancement needs for desired functionality or performance and technology areas for exploration.

3.2.3.3. The contractor shall assess and evaluate the component enhanced end product’s ability to meet intended objectives and performance requirements.

3.2.3.4. The contractor shall plan and implement upgrades, technology refresh, and technology insertions.

3.2.3.5. The contractor shall translate designs, plans, and architectures into sub-systems and/or systems that will allow qualitative and/or quantitative analysis of feasibility, functionality, performance, and/or utility of use and/or integration into a system.

3.2.3.6. The contractor shall develop prototypes of varying levels of fidelity using designs and analytical solutions, potentially leveraging augmented and virtual reality approaches and technologies when feasible.

3.2.3.7. The contractor shall create Digital Twins of systems that replicate or emulate the as-built system to facilitate system upgrades and fixes throughout the lifecycle.

3.2.3.8. The contractor shall develop one or more technical approaches within cost and schedule. The contractor shall also articulate the theoretical increased fidelity of technology to a level where determination of performance and functionality based on cost, and implementation are further defined within the materiel solution. Materiel solutions shall be defined or proposed using current technology and/or development modifications suitable for component enhancement, technological availability, and suitability yet is mindful of integration issues.

3.2.3.9. The contractor shall identify quality control measures, integration interfaces, and manufacturing process details.

3.2.3.10. The contractor shall develop, fabricate, or modify components or sub-components for the purpose of integration into a broader system.

3.2.3.11. The contractor shall modify, change, or enhance existing components or sub-components focused on meeting requirements and/or goals with the intent to increase functionality and performance or decrease life-cycle costs and sustainability requirements.

3.2.3.12. The contractor shall provide configuration management (CM) planning and support.

3.2.3.13. The contractor shall provide certification and accreditation support for material solutions identified in individual TOs.

3.2.3.14. The contractor shall provide operations, maintenance, training, and integrated logistics support for operational prototypes until logistical transition or other disposition is complete.

3.2.3.15. The contractor shall provide documentation such as TDPs, flow charts, schematics, drawings, training plans, test plans, source code, presentations, CM, verification, validation, and evaluation plan, etc. as required by each TO.

3.2.4. INTEGRATION.

The contractor shall possess an in-depth understanding of the overall system architecture, system design, and functionality requirements to include system of systems integration interfaces. Specific TO requirements tasks may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.4.1. The contractor shall develop, fabricate, manufacture, and/or modify systems to meet specific performance requirements and/or goals. The contractor shall identify all modifications to the component or system.

3.2.4.2. The contractor shall develop products that meet integration and interface requirements focused on meeting system performance objectives without adversely affecting the broader systems’ performance.

3.2.4.3. The contractor shall develop, fabricate, and build a system or group of systems designed to meet specific or broadly defined objectives of performance or functionality based on mission requirements, designs, and/or enhancement needs.

3.2.4.4. The contractor shall identify all issues associated with the ability to achieve the planned or desired system and/or sub-system performance specifications. The ability of the system, sub-systems, or components to meet the performance specifications shall be measured in terms of the desired functionality, performance, cost, schedule, and physical constraints or limitations. Associative risk mitigation plans shall also be developed, maintained, and followed as required.

3.2.4.5. The contractor shall provide engineering expertise to analyze system concept, system design and interoperability, and provide recommendations for optimization. The contractor shall furnish systems engineering, software engineering, model-based system engineering, and integration support. Examples of TO requirements include, but are not limited to, the listed task areas in the following subparagraphs.

3.2.4.5.1. The contractor shall integrate components into systems and furnish user follow-up support.

3.2.4.5.2. The contractor shall integrate multiple systems into systems-of-systems and furnish user follow-up support.

3.2.4.5.3. The contractor shall integrate systems and/or systems-of-systems into an operational environment and furnish user follow-up support.

3.2.4.5.4. The contractor shall develop communications protocols and interoperability between separate information sources or software systems and furnish user follow-up support.

3.2.4.5.5. The contractor shall provide systems engineering services in data correlation, mining, management, administration, integration, storage, and dissemination.

3.2.4.5.6. The contractor shall develop, modify, or implement multilevel security for information systems.

3.2.4.5.7. The contractor shall re-host data and applications across platforms such as hardware, operating systems, and security domains, service-oriented architecture, etc.

3.2.4.5.8. The contractor shall integrate analog and digital information and communications technologies.

3.2.4.5.9. The contractor shall develop a wired and/or wireless, self-assembling mesh network for a tactical operations center.

3.2.4.5.10. The contractor shall design, develop, operate, and sustain testbeds in support of systems and software engineering efforts such as the Joint Friendly Force Tracking Mission Management Center Testbed, the Joint Air Defense Operations Center – Developmental, and the HA Test Bed.

3.2.4.5.11. The contractor shall provide CM, certification and accreditation support for testbeds, operations centers, and other systems and/or software developed under this contact.

3.2.4.5.12. The contractor shall maintain software to include (but not limited to) fixing defects, application software, tools, capabilities, and databases for the software applications, related functionality, and upgrade and patch support and dissemination in response to changes in the operating environment.

3.2.4.5.13. The contractor shall develop and implement tools to enhance situational awareness, information visualization, and knowledge management.

3.2.5. DEMONSTRATION, TESTING, AND EXPERIMENTATION.

The contractor shall possess an in-depth understanding of the specific test objectives and performance characteristics of system or sub-system to include other components that are involved in the testing event. Further, the contractor shall possess an in-depth understanding of testing resources, test ranges, test equipment (hardware and software) and testing methods appropriate for the specific test objectives or item under test. The contractor shall demonstrate, test, and perform experiments with the prototypes and/or products specific to the individual TO requirements. The contractor shall obtain all approvals, licenses, certificates, or other approvals such as frequency allocation, Federal Aviation Administration (FAA), and Federal Communications Commission approvals or others as required prior to the test approval event. Specific TO requirements may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.5.1. The contractor shall develop plans, schedules, execution approaches, and cost to meet a variety of testing objectives.

3.2.5.2. The contractor shall conduct test execution that may include (but is not limited

to) materials testing, coupon sample testing, scaled testing, flight testing, ground testing, acceptance testing, component testing, algorithm testing, software testing, anti-tamper component-level verification testing, hardware-in-the-loop testing, and/or full system or product testing. The contractor shall ensure attention is provided to data collection, range considerations and impacts to the ability to execute as well as mitigation alternatives to ensure test execution success including the following tasks. The contractor shall utilize a set of best practices that combines DevSecOps (or similar process) during software testing.

3.2.5.2.1. The contractor shall perform data collection and analysis planning. This includes, but is not limited to, leveraging big data analytics, artificial intelligence, quantum computing, and machine learning to conduct analyses of data sets generated from demonstrations, testing, and experimentation activities.

3.2.5.2.2. The contractor shall perform data collection, data reduction and data analysis.

3.2.5.2.3. The contractor shall develop test reports for approval and presentation.

3.2.5.3. The contractor shall identify and understand range/facility capabilities and coordinate issues associated with multiple ranges located within the U.S. and as required, throughout the world.

3.2.5.4. The contractor shall execute the full range of test execution activities, including the development of cost, schedule, risk assessment, and test event activities tied to range and or facility availabilities.

3.2.5.5. The contractor shall identify, design, develop and/or procure special test infrastructure, tools, and equipment, ordnance and/or test articles necessary to achieve the test objectives and perform application testing for Command, Control, Communication, Computers, Cybersecurity, Intelligence, Surveillance, and Reconnaissance (C5ISR).

3.2.5.6. The contractor shall identify skill sets and numbers of personnel for specific test execution responsibilities commensurate with their training, experience, and education.

3.2.5.7. The contractor shall provide logistical support for the planning, set-up, execution, data-collection, and breakdown of test or demonstration event activities tied to a range or facility.

3.2.5.8. The contractor shall formally and informally demonstrate capabilities to be assessed for military or operational utility, or for future capability development activities that address Warfighter needs. This includes planning for, participation in, and execution of warfighting experiments and warfighting demonstrations to include all required documentation. Examples of TO requirements include (but are not limited to) the listed task areas in the following subparagraphs.

3.2.5.8.1. The contractor shall execute JCTDs according to TOs.

3.2.5.8.2. The contractor shall support all designated manager functions (e.g., operational, technical, transition) for JCTDs and rapid technology insertions.

3.2.5.8.3. The contractor shall coordinate and integrate USASMDC mission areas into the Office of the Secretary of Defense (OSD), CCMDs, the Services, Interagency, and Multinational demonstrations.

3.2.5.9. The contractor shall explore concepts and capabilities to be assessed through operational analysis and military or operational utility of Army and joint experimentations.

Experiments can be conducted in live, virtual, or synthetic environments as specified in the TO. Support includes planning for, participating in, and execution of joint and Army Warfighter experimentation venues, as well as operational prototype experimentation.

Examples of TO requirements include (but are not limited to) the listed task areas in the following subparagraphs.

3.2.5.9.1. The contractor shall coordinate and integrate USASMDC mission areas into OSD, CCMDs, Service, Interagency, and multinational experiments.

3.2.5.9.2. The contractor shall conduct a concepts-to-experiments crosswalk.

3.2.5.9.3. The contractor shall develop experiment objectives.

3.2.5.9.4. The contractor shall develop experimentation plans.

3.2.5.9.5. The contractor shall provide force-on-force strategic, tactical, and/or operational modeling and simulation (M&S) support.

3.2.5.9.6. The contractor shall perform qualitative and quantitative analysis to include MUAs, Analysis of Alternatives, Cost Benefit Analyses, and operational utility assessments.

3.2.5.9.7. The contractor shall perform data collection and analysis planning.

3.2.5.9.8. The contractor shall perform data collection, data reduction, data analysis and construct databases to evaluate data.

3.2.5.9.9. The contractor shall develop test reports for approval and presentation.

3.2.5.9.10. The contractor shall provide input, based on experimentation and lessons learned, to concepts, operational and organizational documents, and to force development, force management and other DOTMLPF-P organizations.

3.2.6. ASSESSMENT, EVALUATION, VERIFICATION, AND WARGAMING.

The contractor shall possess an in-depth understanding of operating requirements, design constraints, capabilities, and acceptability requirements of systems or components.

Further the contractor shall be capable of analyzing and/or interpreting test data to predict or define the performance, form, fit, and function in relation to the task objectives, specifications, or requirements. The contractor shall possess the ability to update and run statistical, stochastic, deterministic, force-on-force (FOF), operator-in-the-loop and closed loop M&S and other analytical tools to execute required analysis activities. Models include, but are not limited to Extended Air Defense Simulation (EADSIM), System Effectiveness Analysis Simulation (SEAS), Future Force Experimentation Air Defense Simulation (FFEADS), Reconfigurable Tactical Operations Simulator (RTOS), Command and Control, Battle Management, and Communications (C2BMC) Planner, Systems Toolkit (STK), Satellite Orbit Analysis Program (SOAP), Advanced Framework for Simulation, Integration, and Modeling (AFSIM), High Energy Laser Consolidated Modeling Engagement Simulation (HELCoMES), High Energy Laser Synthetic Capabilities and Player Environment (HELSCAPE), Global Positioning System Interference and Navigation Tool (GIANT), Automated Cost Estimating Integrated Tools (ACEIT), Space Wargaming Analysis Tool (SWAT), and ExtendSIM. When required, the contractor shall possess the ability to design, develop, and implement M&S and other analytical tools. Specific TO requirements may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.6.1. The contractor shall assess performance and/or functionality of systems, subsystems, components, or subcomponents against pre-defined criteria, metrics, specifications, or requirements. Develop the criteria or metric for which the performance and/or functionality will be assessed. Describe the pass or fail values for each criterion or metric.

3.2.6.2. The contractor shall conduct pre-test analyses and assessments prior to demonstrations and test events and provide post test data analyses and assessments after completion of a demonstration or test events.

3.2.6.3. The contractor shall identify any alternative methods/approaches to conducting examination (non-destructive testing, sub-component interrogation, coupon testing, etc.), which are focused on providing data that supports evaluation of acceptability either statistically or deterministically.

3.2.6.4. The contractor shall develop processes and plans aligned with incremental program milestones that are focused on quantitative and/or qualitative examination of requirements, mission needs and development strategies against development progress to ensure developments meet acceptable metrics. (e.g., entry and exit criteria and performance for particular phases of development).

3.2.6.5. The contractor shall deliver detailed assessments and/or evaluations to examining activities of product development to determine if performance, form, fit, and function meets pre-defined requirements or functionality of a system’s ability to meet program objectives.

3.2.6.6. The contractor shall assess the feasibility of emerging ideas, approaches, and potential capabilities and/or technology solutions through participation in service, joint, interagency, and multinational assessment events or wargames. This includes planning for, participating in, and executing Joint, Army and command wargaming venues. Examples of TO requirements include, but are not limited to, the listed task areas in the following paragraphs:

3.2.6.6.1. The contractor shall develop strategic direction (vision) to be vetted in wargames (Service, Joint, Interagency, and multinational).

3.2.6.6.2. The contractor shall perform assessments of national and strategic guidance in order to identify command linkages and ensure congruence of command strategy to national guidance and vision.

3.2.6.6.3. The contractor shall prepare overarching command guidance for input to joint documentation.

3.2.6.6.4. The contractor shall identify emerging and future technology trends and prepare vision documents, white papers and strategic studies.

3.2.6.6.5. The contractor shall plan and execute scenario development, wargame event design, facilitation of event, data collection, data reduction, data analysis, and reporting of findings.

3.2.6.6.6. The contractor shall provide associated operational FoF M&S support.

3.2.7. LIMITED QUANTITY PRODUCTION.

The contractor shall possess an in-depth understanding of manufacturing techniques and equipment, production schedules, quantity requirements, and system/sub-system fabrication needs, and shall maintain access to production facilities, manufacturing machines, and personnel. Manufacturing performance will also require substantial knowledge concerning production of a system or subsystem in limited quantity to provide articles for the purposes of research, development, and/or test and evaluation to establish an initial production technology baseline, or to permit an orderly increase in the production rate upon determination to proceed to higher rate of production. This SOW supports all testing and production activities short of a full rate production decision.

Specific TO requirements may include (but are not limited to) the listed task areas in the following subparagraphs.

3.2.7.1. The contractor shall produce systems and sub-systems in accordance with production rate schedules and quality requirements; funding profiles; and compliance with all applicable Federal, State, and local codes and standards, including safety and occupational health requirements, as well as any additional specific requirements invoked by this contract, or appropriate TO, if applicable.

3.2.7.2. The contractor shall develop and/or coordinate facility availabilities for the fabrication, assembly, integration, and test required for production to include necessary quality assurance plans and requirements verification checks.

3.2.7.3. The contractor shall identify required Government furnished equipment; facilities;

property; and all specialized materials, special test production equipment and fabrication equipment.

3.2.8. INFORMATION SUPERIORITY.

The contractor shall possess an in-depth understanding of information superiority and cyber and electromagnetic activities (CEMA), to include the capability to collect, process, and disseminate an uninterrupted flow of information, and enabling system resiliency while exploiting or denying an adversary's ability to do the same. All systems developed under this contract shall be secure, reliable, interoperable, and able to communicate across a universal IT infrastructure, to include national security systems (NSS). This IT infrastructure includes the data, information, processes, organizational interactions, skills, and analytical expertise, as well as systems, networks, and information exchange capabilities. Information superiority inherently depends on program design, but equally depends on the readiness of the implemented technology to provide direct user capabilities and the readiness of the supporting infrastructures that apply these technologies to be successfully employed. Specific TO requirements may include (but are not limited to) the listed task areas in the following paragraphs.

3.2.8.1. Information interoperability.

The contractor shall have an in-depth understanding of information interoperability and shall design, develop, and test products that interoperate with each other. The contractor may be required to characterize information interoperability, as applicable, within a family of systems, a mission area, and a mission; verify and maintain information interoperability; and participate in interoperability and supportability M&S assessments.

3.2.8.2. Mission Command, Communications and Computers.

The contractor shall have an in-depth…