CFSS_IVV_SOO - Final Draft.pdf

Statement Of Objectives For

Common Flight Safety System (cFSS)

Contract Number: TBD

Task Order: TBD

28 June 2024 TBD

Prepared by: AFLCMC/EBZ Eglin AFB FL, 32542

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and DoD Contractors, administration or operational use, XX XXX XXXX. Other requests for this document shall be referred to AFLCMC/EBZX, Eglin AFB FL 32542-6853.

Contract Number: Task Number:

Revision Record

Revision Date Comments

- 12 Mar 2024 Initial Draft

25 Apr 2024 Revised Draft

- 28 June 2024 Final Draft

1. INTRODUCTION: .

1. INTRODUCTION: The Armament Directorate (EB) seeks common systems and components to achieve rapid development, aircraft integration, testing, and fielding of air-launched weapons.

Currently, weapons programs can spend up to $8M to develop a flight safety termination system tailored to its unique application which can take 1-2 years to complete and is often on the critical path. Developing a Common Flight Safety System (CFSS) solution would reduce cost, schedule, and risk across the Weapons Enterprise. The CFSS solution shall provide qualified miniaturized components enabling adaptability to a wide range of weapon categories and form factors compatible with modern integration practices, supporting existing test range infrastructure, and provide the basis for a complete Flight Safety System solution. This family of components shall simplify Flight Termination System design and range tracking for accelerated weapons testing. As part of the certification process, an Independent Verification and Validation (IV&V) must address the CFSS Autonomous Flight Termination Unit – Miniaturized (AFTU-M) wrapper software and the Programmable Logic Device (PLD) designs.

The AFTU is a primary processing component in the vehicle Flight Termination System (FTS). The AFTU receives position, velocity, and health data from on-board vehicle tracking systems and makes flight termination decisions based on predefined software-based mission rules. Each launch vehicle utilizes a pair of AFTUs to provide redundancy in flight. The pair of AFTUs share a processor heartbeat signal for single fault tolerance. The AFTU implements a PolarFire SoC Programmable Logic Device (PLD). The PLD will be programmed in VHDL and instantiate a softcore Leon3 Spark processing architecture. The AFTU software contains the Core Autonomous Safety Software (CASS) algorithm provided by the CASS Steering Committee which includes Space Launch Delta (SLD) 30 SE, SLD 45 SE, and National Aeronautics and Space Administration (NASA) and is used unmodified. This software is considered Government Furnished Equipment (GFE) or Government Off The Shelf (GOTS). L3Harris is responsible for writing the wrapper code (aka CASS Wrapper) that instantiates the CASS Object, provides it sensor data, and processes its outputs. The software will be developed using embedded C (CASS Wrapper) and C++ (CASS Core software only and minimal core wrapper capability) for the CSCIs. The wrapper software is expected to contain 30,000 to 40,000 lines of code. The project team will employ design best practices to minimize verification complexity and improve future maintenance. CASS and the CASS wrapper software are unclassified, but the wrapper is considered proprietary to L3Harris and access to the code will be limited to only those parties completing the actual IV&V code review.

Table 1-1 – CSCI List Summary Embedded SW CSCI CASS Wrapper and Core

Software Embedded PLD PolarFire FPGA and associated

VHDL code

2. OBJECTIVES: The IV&V process is designed to verify system and operational requirements along with evaluating specifications for completeness, accuracy, traceability, and testability. The IV&V process is conducted by an independent contractor due to the importance of the system’s safe function, the benefit of evaluations from multiple technical perspectives, and the essential need for independent integrity. The contractor’s IV&V assessment will ensure the vendor’s system will meet all performance requirements, comply with all design specifications and defined requirements, verify any potential failure modes identified in the design and coding failure analysis, and ensure tests demonstrate system operation satisfies Range Safety requirements.

3. SCOPE OF WORK OR TASKS: The scope encompasses an independent assessment of the AFTU-M wrapper software and PLD; development of CFSS hardware and software continues under a separate contract. The term software in this document shall be understood to include both embedded software and PLD. IV&V of both the AFTU-M wrapper software and PLD components of the AFTU-M is required to comply with the RCC 319-19 and RCC-324-11. The IV&V effort supports qualification of the CFSS components being established by the USAF government team and the system vendor.

The contractor IV&V of the AFTU Wrapper Software and AFTU PLD shall include the following elements:

a. The contractor shall participate in tailoring phases of the MSFC-STD-3663, NPR- 7150.2, and RCC 319-19 Appendix A standardized assessment process to address the cFSS system and requirements as defined by Range Safety. This includes performing an assessment to determine appropriate level of effort in accordance with RCC 319-19 Appendix A.

b. The assessor shall develop, and deliver for approval, an IV&V plan developed in accordance with RCC-319-19 (MSFC-STD-3663 or NPR-7150-2 Class A as applicable) to Range Safety.

i. The plan shall address staffing, experience, tools, equipment, anomaly reporting database, and communications with Government stakeholders.

c. Execution of the approved IV&V plan shall be in accordance with RCC 319-19 Appendix A, to include:

i. requirements assessments.

ii. design assessments.

iii. development assessments.

iv. evaluation of operation and test assessments.

v. special safety assessments.

vi. software and document release assessments.

d. Range Safety Support: Throughout the assessment process, analysis support is provided to Range Safety to ensure that all operational and performance requirements are identified and are traceable through design, development, and developer testing.

i. The assessor shall deliver the results of the assessments and special studies to Range Safety at the completion of each assessment or study. Assessments shall not be prescreened by the developer prior to Range Safety; assessments may be delivered to the system vendor in parallel.

ii. The assessor shall report all anomalies throughout the development and operational implementation process to Range Safety in accordance with RCC 319-19 Appendix A.

e. The assessment contractor shall:

i. conduct design reviews and test readiness reviews for the assessment processes, criteria, and tools.

ii. participate in technical interchange and program management meetings with the development contractor/organizations, as required.

iii. participate in configuration control planning for existing and new systems.

iv. evaluate the configuration control of test and evaluation configuration items to ensure test articles are representative of the final delivered configuration.

4. MEETING SUPPORT: The contractor shall attend design meetings throughout the performance of the contract. The contractor shall review meeting agendas, data items, artifacts, and to provide constructive feedback at the level appropriate for the meeting type. The review shall verify the data against the requirements of the program and referenced requirements, standards, and guidelines contained in this SOO. Additional meeting support requirements are listed below:

a. The contractor will assume four (4) meetings/trips to Eglin AFB, FL per year during the contract period of performance consisting of approximately three (3) people per trip supporting 10-hours per meeting week to meet the requirements under this Statement of Objectives.

b. System Vendor Meeting Support- The contractor shall participate in design meetings, peer reviews, engineering review boards (ERBs), and Stage Gate Design Reviews.

Virtual participation is acceptable for these meetings.

c. Design Meeting- The contractor shall participate in sprint meetings. The Software Development cycle is on a 3-week sprint cycle. Virtual participation is acceptable for these meetings.

d. Peer Reviews- The contractor shall participate in scheduled Peer Reviews as dictated by the development sprint plan. Virtual participation is acceptable for these meetings.

e. Software Engineering Review Boards (ERBs)- The contractor shall participate in scheduled system vendor ERB process. The system vendor ERBs are focused on ensuring the engineering product is complete for the level of maturity, meets program requirements, and quality standards before proceeding to the next design phase and releasing products to the customer for review. ERBs are required Software design gates per the system vendor’s software development process. The contractor shall attend ERBs in-person at the system vendor’s facility in Mason, Ohio.

i. The following ERBs are planned:

1. Software Requirements Systems ERB

2. Preliminary Software Design ERB

3. Embedded Software Coding ERB

4. Detailed Software Design ERB

5. AFTU-M Preliminary Design ERB

6. AFTU-M Critical Design ERB

7. AFTU-M Test Readiness ERB

8. AFTU-M Post Verification ERB

f. Stage Gate Design Reviews- The contractor shall participate in scheduled CI design review stage gates. These are formal design reviews with the customer. The contractor shall assume travel to either Eglin, FL, or Mason, OH for these meetings. The contractor shall review, the L3Harris delivered data items, code, plans, procedures, and other artifacts/data as applicable to conduct a satisfactory review.

i. AFTU-M Preliminary Design Review

ii. AFTU-M Critical Design Review

iii. AFTU-M Test Readiness Review

g. Final Software Testing- The contractor shall participate in a final software testing review meeting. The IV&V verifies that the testing is according to the test plan procedures. The test plan procedures shall align with the previously mentioned system vendor meeting support, design meetings and ERBs.

5. PROGRAM AND FINANCIAL MANAGEMENT: The contractor shall provide programmatic, technical and systems management, and other functional representatives necessary to provide the support defined in this SOO.

a. The contractor shall utilize the financial management system in place to collect cost information that will allow for accurate monitoring of the cost performance of the contract (FA TBD). Contract data shall be delivered IAW the Contract Data Requirements List (CDRL) listed below:

Sequence Number Title

A001 Status Report (DI-MGMT-80368A)

A002 Integrated Master Schedule (DI-MGMT-81650)

A003 Scientific and Technical Reports (DI-MISC-80711A)

6. OPERATING CONSTRAINTS: All deliverables and all information required to integrate CFSS with a weapon system shall be Distribution Statement D (releasable to the DoD and all DoD Contractors per DoD Instruction 5230.24).

7. DELIVERABLES: The Contractor shall deliver electronic copies of the draft and final products as both unclassified and Distribution Statement D. Data deliverables shall be delivered to the Range, with copies provided to USAF EBZX Program Management team and system vendor. The contractor shall provide a monthly status report consisting of progress in the prior month, planned activity for the next 60 days, Risks, Opportunities, Integrate Master Schedule (CDRL A002) with variance explanations, and a detailed explanation of issues or blocking items (CDRL A001).

Contractor format is acceptable. All products shall be in accordance with RCC-319-19 (CDRL A003).

a. Assessment (IV&V) Process Plan

b. Assessment (IV&V) Test Plan and Procedures

c. Assessment (IV&V) Evaluation Reports

d. Assessment (IV&V) Anomaly Reports

e. Assessment (IV&V) Software and Documentation release

All software and PLD test benches, software test executables, PLD test executables, reports, and artifacts from the IV&V effort shall be delivered to government upon conclusion of the IV&V process. Conclusion is based on range approval of IV&V report.

8. Assumptions and Ground Rules: The CFSS vendor reserves the right to review any data item or discrepancy and provide feedback with a reasonable time period. In the event of an identified deficiency, the contractor shall notify system vendor of the deficiency with a description, explanation of the finding, and suggest a corrective action. The system vendor shall have the opportunity to review and/or comment. The feedback provided by the system vendor on the contractors input will be taken into consideration during determination of a closure path and final implementation of IV&V results/recommendations.

9. DATA RIGHTS: The Contractor shall provide unlimited data rights in accordance with the contract clause, Eglin-H004 Rights in Major System Interfaces (April 2023).

10. PERIOD OF PERFORMANCE: The Contractor shall execute the scope of work (to include RCC approvals) within 18 months from contract award.

11. REFERENCES:

Document Title Revision / Date

RCC-319-19 Range Commanders Council Document 319-19 Flight Termination Systems Commonality Standard, June

RCC-324-11 Range Commanders Council Document 324-11 Global Positioning and Inertial Measurements Range Safety Tracking Systems Commonality Standard, February

MSFC-STD-3663 MSFC Standards for Configurable Logic Device Developments

Baseline

NPR 7150.2 NASA Software Engineering Requirements A