PWS Phase III SBIR IDIQ-SIMSA -18 Feb 26_FINAL.pdf

SMALL BUSINESS INNOVATION RESEARCH (SBIR) PHASE III

INDIFINITE DELIVERY-INDEFINITE QUANTITY (IDIQ)

PERFORMANCE WORK STATEMENT (PWS)

FOR

SPACE INTEGRATED MODELING, SIMULATION, & ANALYSIS (SIMSA) FOLLOW-

ON

IN SUPPORT OF

UNITED STATES SPACE FORCE (USSF), UNITED STATES SPACE COMMAND

(USSPACECOM), UNITED STATES SPACE FORCE COMBAT FORCES COMMAND

(CFC), SPACE SYSTEMS COMMAND (SSC), OTHER DEPARTMENT OF DEFENSE

(DOD) ENTITIES, THE INTELLIGENCE COMMUNITY (IC), AND OTHER RELATED

UNITED STATES GOVERNMENT AGENCIES

18 February 2026

Version 1.0

Contract No. XXXX

NAICS 541715

[Contract Name] IDIQ Contract Number:

Table of Contents

1.0 Background

2.0 Scope

3.0 Performance Objectives

3.1. Objective 1 – Program Management

3.2. Objective 2 – Rapid Analysis and Prototyping Toolkit for Resiliency

3.3. Objective 3 – Systems Analysis & Design

3.4. Objective 4 – Systems Operations & Sustainment

3.5. Objective 5 – Systems / Technical Assessment Integration

3.6. Objective 6 – Analytical Infrastructure

4.0 Other Requirements

4.1. Proprietary Data and Software

4.2. Documentation and Data Rights

4.3. Data Retention

4.4. Government Furnished Information

4.5. Security

4.6. Common Access Card (CAC)

4.7. Operations Security (OPSEC)

4.8. Controlled Unclassified Information (CUI)

4.9. Government Furnished Equipment (GFE)

4.10. Technical Guidance

4.11. Material and Other Direct Costs (ODC)

4.12. North American Industry Classification System (NAICS)

4.13. Places of Performance

4.14. Travel

4.15. Organizational Conflict of Interest (OCI)

4.16. Ordering Period

5.0 Directives and Deliverables

5.1. Applicable Directives

5.2. Deliverables

1.0 Background

The United States Space Force (USSF), Combatant Commands, their Department of Defense (DOD), Intelligence Community (IC), and other United States Government (USG) partner organizations are responsible for acquiring, delivering, fielding, maintaining, and sustaining adaptive and resilient war fighting capabilities to protect our nation’s strategic advantage. These USG entities work in partnership with industry, government agencies, academia, and allied organizations to accelerate innovation, outpace emerging threats, and to deter and dominate any future contest.

2.0 Scope

The USSF and its mission partners require cross-domain and joint insight fueled by analytics to accelerate strategic decision-making, prepare and defend Force Designs, conduct operational assessment and planning, and enable responsive digital and mission engineering and cross-domain / joint / allied partner / commercial integration. The innovative technology developed by the contractor, the Rapid Analysis and Prototyping Toolkit for Resiliency (RAPTR) tool, extended under Phases I, II, and III of the Small Business Innovation Research Program (SBIR), SBIR Topic AF192-001 / FA8808-20-C0003 – COA Planning & Analysis for the Space Warfighter, will continue development towards commercialization. The contractor shall leverage RAPTR to realize some, or all, of the following benefits:

• Provide simulation, prototyping, analysis, and modeling using the RAPTR tool to advance data analytics and visualizations, and visual storytelling to bring data to life, providing cross-domain and joint mission awareness.

• Use RAPTR to rapidly iterate use cases to enable operational mission assessment and planning and responsive development of countermeasures to emerging threats (i.e., Course of Action assessment and planning).

• Use RAPTR to provide a holistic view of every domain (e.g., sea, ground, air, cyber, and space, etc.) to enable warfighters to evolve a more comprehensive strategy for action.

• Use RAPTR to provide data driven insights into acquisition trade space analysis to include Total Obligation Authority (TOA) trades and analyses.

• Using RAPTR, conduct analyses that enable design, development, and sustainment of resilient, responsive solutions.

• Using RAPTR, simulate, at the appropriate fidelity, air, cyber, ground, maritime, and space systems as required to support the customer’s analytical, assessment, and/or training objectives. This includes the emerging Lunar environment and all orbital regimes as well as terrestrially based regimes.

• Integrate Artificial Intelligence and Machine Learning into modeling, simulation, prototyping, analysis, operational planning, wargame and exercise, and other associated mission analysis, design, and planning activities as required and approved by the customer.

• Provide Mission/Systems Engineering assessments of commercial and/or government missions, systems, etc., as required and approved by the customer, to support acquisition, development, fielding, and operations of systems intended to meet the United States Government’s war fighting objectives.

RAPTR may be applied to address challenges across a broad spectrum of domain and mission challenges to include, but not limited to, orbital warfare; electronic warfare; space data transport;

space domain awareness; multi-domain effects, battle management, wargaming exercises;

operational planning; positioning, navigation, and timing; and testing, training, and evaluation, and logistics as well as the service and joint kill chains / webs required to meet national objectives.

During performance of this effort, Task Orders (TOs) may be defined as either severable or non-severable efforts.

3.0 Performance Objectives

3.1. Objective 1 – Program Management

The Contractor shall provide program management support, responsible for leading and executing efforts directly related to RAPTR projects, including quality, staffing, and financial and subcontractor management (if necessary). The program manager (PM) shall have the authority to make decisions regarding contract work, schedule, and accommodating Government direction. This may include additional program/project support staff as required to ensure delivery of contract or task order requirements. During this effort, the contractor shall provide administrative, financial, and technical management functions directly related to the RAPTR efforts, such as:

• Scheduling activities and milestones.

• Describing and reporting contract and task order status, as appropriate and/or required.

• Outlining Contractor activity and progress toward accomplishment of objectives.

• Planning, forecasting, reporting, and making recommendations on funding and funding changes.

• Program control and planning.

• Risk & Opportunity management.

• Staffing.

• Contract/Task Order technical direction.

• RAPTR Product management and technical direction.

Deliverables will be provided as described below.

Task Order Management Plan – The Contractor shall produce detailed Task Order Management Plans to be presented at the Contract Kickoff meeting to be conducted within one month of contract award. Additionally, the Contractor shall produce detailed project plans describing the budget, scope, work plan, deliverables, schedule, milestones, and resources required to accomplish requirements as informed by the applicable Task Order government lead.

The Government may require planning products that enable the Government to integrate Contractor activities with other related activities the Government is leading or managing. The Government may require the Contractor to interface their plans with various Government project management techniques/tools (e.g., Kanban, Agile, Scrum, waterfall, etc.). The Government may require plans to be coordinated and/or approved before executing and/or throughout execution.

Task Order Kickoff Meeting – The Contractor shall conduct a Kickoff meeting within 30 days of task order award. The Contractor shall support other technical, work status, and administrative meetings as required.

Monthly Status Report (MSR) – Each month the Contractor shall provide an MSR containing sufficient up-to-date detail on the SIMSA Follow-on IDIQ, its Program Management, and each ongoing Task Order including completed and outstanding key products/artifacts/deliverables, costs incurred with actual and projected financial status, travel summary and projections, proposed or pending contract modifications, and significant upcoming activities, changes, or problem areas. This report shall also include an executive summary section highlighting significant contract activities, changes to the Contractor’s organization, method of operation, project management network, actual or potential areas of opportunity and concern. These reports shall be organized to fulfill management needs for the IDIQ as well as individual Task Orders.

Program Management Review (PMR) – On a Semi-annual basis, at minimum, or as directed by the PCO or COR, the Contractor shall provide a comprehensive PMR including a summary overview with supporting data for the overall vehicle/program and each ongoing Task Order; this will include topics described in MSRs: completion status, expenditure status, and potential or actual risk factors and opportunities. These reviews will be organized to fulfill management needs for the IDIQ and individual Task Orders.

Final Cumulative Report – Upon completion of individual Task Orders or the IDIQ vehicle, the Contractor shall provide a summation report. Contents shall include summary narratives, Task Order completion dates, and key products/deliverables.

Deliverables

• A001 Task Order Kickoff Meeting.

• A002 Task Order Management Plan.

• A003 Monthly Status Report (MSR).

• A004 Program Management Review (PMR).

• A005 Final Cumulative Report.

3.2. Objective 2 – Rapid Analysis and Prototyping Toolkit for Resiliency (RAPTR)

The Contractor shall reuse / apply and refine and/or further-develop SBIR Topic AF192-001 / FA8808-20-C0003 – COA Planning & Analysis for the Space Warfighter to enable responsive digital engineering (DE); mission engineering (ME); force design and/or solutions development;

wargame and exercise planning and execution; training; operational assessment; and modeling, simulation, prototyping & analysis (MSP&A) in support of government objectives. Activities will include product management, development, deployment, security compliance, and maintenance / modernization as required to ensure ongoing relevance and ease-of-use, and to maximize cross-customer integration and utility. Information derived through use of RAPTR shall inform and support subsequent Performance Objectives:

• Objective 3 – Systems Analysis & Design.

• Objective 4 – Systems Operations & Sustainment.

• Objective 5 – Systems / Technical Assessment & Integration.

• Objective 6 – Analytical Infrastructure.

3.3. Objective 3 – Systems Analysis & Design

The Contractor, using RAPTR, shall provide Digital Engineering, Mission Engineering, and/or MSP&A support and/or software development with emphasis to discover, analyze, and assess and/or defend and validate designs and design trades to inform customer force designs, acquisition and/or employment recommendations, architectural trades, and system designs and/or employment. These activities can support Science & Technology (S&T) / Research & Development (R&D), capability/mission area force design analyses, requirements definition, program/system acquisition, and other related activities.

The Contractor may be required, with government approval, to provide any combination of reports, papers, presentations, simulations, models, and data packages, hardware, software, etc.

Artifacts may also include optimization routines, algorithms, machine learning (ML), and artificial intelligence (AI) programs, software tools, and user manuals. Artifacts will be delivered or provided to the Government in the format and timeline specified in requirements and will require Government approval as specified in the task order.

3.4. Objective 4 – Systems Operations & Sustainment

The Contractor, using RAPTR, shall provide Digital Engineering, Mission Engineering, and/or MSP&A support and/or software development to discover, analyze, and validate customer systems operations and sustainment. These activities can include systems concept, TTP development, analysis, training, education, exercise, and wargaming support, test support, domain or multi-domain operations analyses and/or planning. These activities may also involve support to operationalize, train, transition and/or sustain prototyped analysis and/or planning tools.

The Contractor may be required, with government approval, to provide any combination of reports, papers, presentations, simulations, models, and data packages, hardware, software, etc.

Artifacts may also include optimization routines, algorithms, machine learning (ML), and artificial intelligence (AI) programs, software tools, and user manuals. Artifacts will be delivered or provided to the Government in the format and timeline specified in requirements and will require Government approval as specified in the task order.

3.5. Objective 5 – Systems / Technical Assessment Integration

The Contractor, using RAPTR, shall apply Digital Engineering, Mission Engineering, Systems Engineering, and/or MSP&A principles as either stand-alone support or to accompany DE, ME, SE, and/or MSP&A activities described in Objectives 2 and/or 3. These technical assessment and/or integration activities involve supporting or managing systems DE, ME, SE, and/or MSP&A definition and/or integration across teams and/or efforts in support of Government objectives. These activities may also involve unbiased analyses and/or systems engineering support to assess tools/environments and provide recommendations, define requirements, or operationalize, train, transition and/or sustain prototyped analysis and/or planning tools.

The Contractor may be required, with government approval, to provide any combination of reports, papers, presentations, simulations, models, and data packages, hardware, software, etc.

Artifacts may also include optimization routines, algorithms, machine learning (ML), and artificial intelligence (AI) programs, software tools, and user manuals. Artifacts will be delivered or provided to the Government in the format and timeline specified in requirements and will require Government approval as specified in the task order.

Before simulation informed analysis commences, the contractor shall review all agents programmed in the RAPTR software with the government to verify completeness and correctness. The Contractor shall provide SysML representations of classes and behaviors of agents instantiated in simulation using block definitions (for class attributes) and state machine diagrams to document behaviors for review and verification by government personnel. After review for completion of verification for orbital warfare, electronic warfare, space domain awareness, multi-domain effects algorithms, spectrum warfare, multi-domain sensing, concepts, agents, scenario, and behavior, and then the authority to proceed to analytic runs for record will be granted by respective Programs’ Director(s), Deputy Director(s), Technical Director(s), or Deputy Technical Director(s).

3.6. Objective 6 – Analytical Infrastructure

The Contractor shall provide an analytical infrastructure to support OBJECTIVES 2 – 5. This analytical infrastructure may involve Government and/or analytical partner co-use agreements.

The Contractor may be required, with government approval, to provide any combination of reports, papers, presentations, simulations, models, and data packages, hardware, software, etc.

Artifacts may also include optimization routines, algorithms, machine learning (ML), and artificial intelligence (AI) programs, software tools, and user manuals. Artifacts will be delivered or provided to the Government in the format and timeline specified in requirements and will require Government approval as specified in the task order.

4.0 Other Requirements

4.1. Proprietary Data and Software

The Contractor shall request and obtain Government approval prior to including any proprietary data or proprietary software tools within the requirements to be fulfilled under this contract.

4.2. Documentation and Data Rights

This SBIR Phase III IDIQ/Task Order is, by its nature, a SBIR/STTR award and therefore incorporates the appropriate data rights clause for a SBIR award set forth at DFARS 252.227- 7018, Rights in Other Than Commercial Technical Data and Computer Software—Small Business Innovation Research (SBIR) Program (July 2023) (Deviation 2020-O0007).

4.3. Data Retention

The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the appropriate office of primary responsibility. If there is any conflict between this requirement and other requirements associated with this contract, this requirement takes precedence.

4.4. Government Furnished Information

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

4.5. Security

Security and Safety – Contractor shall apply required personnel, physical, information, and industrial security, and safety standards.

U.S. Citizens Only – All Contractor personnel proposed to work on this contract must be U.S.

citizens.

Personnel Security/Special Access – Contractor personnel security clearance requirements will be stated at the TO level. Personnel may require Secret, Top Secret (TS) clearances, and/or Special Access Program/ Special Access Required (SAP/SAR). Contractor personnel that require a TS clearance shall have eligibility for access to Sensitive Compartmentalized Information (SCI) as of contract start date. If required, contractor is responsible for submitting SCI Nominations and coordinating indoctrinations through the appropriate Special Security Office (SSO), and the Government is responsible for submitting Program Access Requests (PAR) for

SAP/SAR.

DD Form 254 – All Contractor employees working under this IDIQ must meet the specific security requirements stated in this Security section as well as specific instructions and guidance listed in the DD Form 254, DoD Security Classification Specification.

Polygraphs – If required, Contractor personnel must consent to and successfully complete a counter-intelligence scope polygraph.

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

4.6. Common Access Card (CAC)

Certain contract and task order personnel will require a Common Access Card (CAC) to access Government systems. CAC permits installation and Non-classified Internet Protocol Router Network (NIPR) access to all contract employees.

4.7. Operations Security (OPSEC)

The Contractor shall adhere to OPSEC guidance as defined in AF Instruction 10-701, OPSEC.

Be familiar with the organization’s Critical Information and Indicator List (CIIL) and ensure indicators & vulnerabilities are protected from Unauthorized Disclosure (UD) per HQ Space Combat Force Command’s (CFC’s) countermeasures/measures. The Contractor shall complete OPSEC in-processing training to include complete follow-on OPSEC training such as event-driven and annual OPSEC training as required provided by the CFC Program Manager per DoDD 5205.02E, DoD OPSEC; DoD 5205.02, DoD OPSEC Manual; CJCSI 3213.0D, Joint OPSEC; and AFI 10-701, OPSEC.

4.8. Controlled Unclassified Information (CUI)

All information provided and marked as CUI via this contract will be safeguarded IAW DoDI 5200.48, Controlled Unclassified Information (CUI). If the Contractor generates any CUI information, it shall protect and disseminate that information per the controls required by DoDI

5200.48. The Contractor shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall immediately report the potential classification of aggregated or compiled CUI to the PCO, COR, and the ACOR. Any subcontractors or consultants used by the Contractor to fulfill these requirements must comply with this paragraph in its entirety. The Contractor shall know how to create, mark, handle, and disseminate classified information including but not limited to Controlled Unclassified Information (CUI) per DoDI 5200.48.

4.9. Government Furnished Equipment (GFE)

The Government will furnish equipment and workspaces required for performance at government facilities. Furnished equipment will be considered incidental to performance onsite.

The Government will provide computer equipment for use in performance under specific task orders. This equipment is authorized for transaction of official Government business only and shall not be used for personal business. They are to be used and turned in as directed by the CO.

4.10. Technical Guidance

Government personnel will provide technical guidance, input, clarification, review/approve completed technical artifacts or deliverables, and provide feedback regarding Contractor efforts as appropriate. The requirement owner is the primary source of technical guidance for this PWS.

4.11. Material and Other Direct Costs (ODC)

If the Contractor is required to purchase reimbursable items, such purchases shall be submitted with a purchase request form for approval by the COR (if under $10k) with prior coordination of the responsible ACOR and government requirement owner prior to the purchase. Any purchases over $10K will have to be coordinated with the COR, ACOR, and government requirement owner, and approved by the PCO. ODCs will be paid on a reimbursable basis, inclusive of G&A and/or overhead costs.

4.12. North American Industry Classification System (NAICS)

The NAICS code for this acquisition is 541715: Research and Development in the Physical, Engineering, and Life Sciences. This U.S. industry comprises establishments primarily engaged in conducting research and experimental development (except nanotechnology and biotechnology research and experimental development) in the physical, engineering, and life sciences, such as agriculture, electronics, environmental, biology, botany, computers, chemistry, food, fisheries, forests, geology, health, mathematics, medicine, oceanography, pharmacy, physics, veterinary and other allied subjects.

4.13. Places of Performance

The work to be performed under this task order will be performed in Government and Contractor facilities. Contractor locations are identified on the DD-254 Form. For collaborative work between Contractor and Government team members, the appropriate Government Task Order Lead will determine optimal worksite breakout, full government in-person facility, full in-person Contractor facility, or any combination thereof. Task Order Lead will weigh the classification requirements, contractor access to Government facility, IT and logistical suitability of Contractor facility and make appropriate determination best suited to the needs of the Government. All facility arrangements deemed necessary beyond ad-hoc or impromptu needs, will be captured by Task Order Lead in a Memorandum of Agreement (MOA) signed by Government Program Director and commensurate Contractor PM.

4.14. Travel

Costs associated with Contractor travel shall be in accordance with FAR Part 31.205-46, Travel Costs. Travel will be reimbursed on a cost reimbursable basis, inclusive of G&A and/or overhead costs. No profit will be paid.

4.15. Organizational Conflict of Interest (OCI)

FAR 9.5 Organizational and Consultant Conflicts of Interest, prescribes responsibilities, general rules, and procedures for identifying, evaluating, and resolving organizational conflicts of interest; provides examples to assist contracting officers in applying these rules and procedures to individual contracting situations; and implements section 8141 of the 1989 Department of Defense Appropriation Act, Pub. L. 100-463, 102 Stat. 2270-47 (1988).

The general rules in FAR 9.505-1 through 9.505-4 prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating organizational conflicts of interest that might otherwise exist in the stated situations. Conflicts may arise in situations not expressly covered in FAR section 9.505 or in FAR section 9.508. Each individual contracting situation should be examined based on its particular facts and the nature of the proposed contract. The exercise of common sense, good judgment, and sound discretion is required in both the decision on whether a significant potential conflict exists and, if it does, the development of an appropriate means for resolving it. If a task order requires activity that would create an actual or potential conflict of interest, the procedures in FAR 9.506 Procedures, are applicable to resolving such conflict.

4.16. Ordering Period

The Ordering Period for this IDIQ shall be 60 months from the date of award. Performance of Task Orders (TO) awarded under this IDIQ may extend beyond the ordering period. However, a TO may not have a period of performance (PoP) that extends beyond 5 years from the date of TO award.

5.0 Directives and Deliverables

5.1. Applicable Directives

The Contractor shall comply with the most current version of all documents listed below as directive and referenced under paragraph 4.5 Security. The Directive/Guidance (D/G) column indicates the extent of Contractor compliance with the publication that is prescribed. A “D” in the column means the publication is a “directive publication,” requiring mandatory compliance by the Contractor. A “G” in the column means the publication is a “guidance publication”, and compliance is optional. If there is any conflict between the directive referenced in SOO/PWS paragraph 4.5 and the reference listed in the tables below, the reference in SOO/PWS paragraphs

4.5 takes precedence. The Contractor shall immediately bring to the attention of the PCO, COR, and ACOR (requirement owner), any discrepancies in this list, the SOO/PWS, or any task/delivery orders.

Table 1 - Applicable Directives

Compliance Directives – The Contractor shall ensure all deliverables meet DoD Information Assurance Certification and Accreditation Process (DIACAP)/DoD Risk Management Framework (RMF) Accreditation, Intelligence Community Directive (ICD) 503 requirements, or the most current applicable standards and guidance. This includes Certification and Accreditation (C&A) activities.

The Contractor shall adhere to DoD and Intelligence Community (IC) Public Key Infrastructure (PKI) policies.

D/G Title PWS Paragraph

G AFI 10-701 4.7

G DoDD 5205.02E 4.7

D Joint Publication 3-13.3 Operations Security (OPSEC) 4.7

D CJCSI 3213.01D 4.7

D AFI 10-701 Operations Security (OPSEC) 4.7

D DODI 5200.48 Controlling Unclassified Information 4.8

D National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 R5

4.8

D NIST SP 800-37 R2 4.8

D Committee of National Security Systems Instruction (CNSSI)

4.8

D NIST SP 800-53A R4 4.8

D DoD 8570.01-M R4 4.8

D DoDD 8570.01 4.8

D ICD 503 4.8

Contractor development and solutions shall be protected and compliant with Cybersecurity Maturity Model Certification (CMMC) certified systems at the lowest classification of the information.

If a Task Order customer believes a development activity may migrate or transition to an operational environment or system for operational decision making (e.g., mission or campaign planning) and/or operations, it should consider including a requirement for the Contractor to apply the “certification to field” process/methodology; this ensures the confidentiality and integrity of the system/application use, and builds security into the development efforts (e.g., using STIGS, code scanning, supply chain source code validation, etc.).

The Contractor shall conduct and execute activities to make applications PK-enabled (PKE) to achieve standardized, PKI-supported capabilities for, digital signatures, encryption, identification, and authentication.

Contractor solutions shall comply with National Institute for Standards and Technologies (NIST), Federal Information Processing Standards (FIPS), or IC standards as applicable, to include Security, Privacy and Cybersecurity concerns. The Contractor shall provide solutions that meet confidentiality, data integrity, authentication, and non-repudiation requirements. Anyone performing Information Assurance activities shall hold appropriate technical or management certifications. The Contractor shall assist in defining user and registration requirements.

The Contractor shall ensure personnel are compliant with DoD 8570.01-MR4, Information Assurance Workforce Improvement Program, 10 November 2015 (or most current version), and Department of Defense Directive (DoDD) 8570.01, Information Assurance Workforce Training, 01 August 2004, Certification and Workforce Management.

5.2. Deliverables

The Contractor shall provide deliverables as described in the IDIQ PWS and individual Task Orders. Format and delivery schedule for deliverables are outlined in the table below.

All program management deliverables (A001 - A005) shall be in a Microsoft Office or Adobe Acrobat-compatible application format, and distributed by an electronic method (e.g., email) unless otherwise specified. DE, ME, and/or MSP&A artifact or project schedule deliverables may specify the application format.

Contractor format/template is acceptable unless a specific format is identified.

Days referenced shall be calendar days, unless otherwise noted. For recurring Deliverables, if the due date falls on a holiday or a weekend the Deliverable shall be sent on the following business day.

If Deliverables contain CUI or classified information or data, the Contractor shall mark/disseminate/protect accordingly.

Table 2 - Deliverables Contract Deliverables

Deliverable CDRL PWS Reference Frequency

Task Order Kickoff Meeting Presentation A001 3.1

Within 30 calendar days of contract start date

Task Order Project Management Plan A002 3.1

Within 30 calendar days of contract start date

Monthly Status Report A003 3.1 Monthly

Program Management Review A004 3.1

Semi-annual, commencing 6

Months after contract award; or as required.

Final Cumulative Report A005 3.1 Upon completion of individual Task Orders and contract

SysML Representations (to include block definitions and state machines) A005 3.5

Documenting the attributes and behaviors of the orbital warfare, electronic warfare, space domain awareness, multi-domain effects concepts, systems, agents, components, spectrum warfare, multi-domain sensing, and kill-chains instantiated used in the RAPTR simulation to inform analysis as needed