FA8650-18-S-2001-Atch6.pdf

FA8650-18-S-2001

Attachment 6

STATEMENT OF OBJECTIVES (SOO)

TASK ORDER 0002

Software Engineering for Airframe Digital Twin

1.0 BACKGROUND: AFRL/RQVS has taken delivery of an initial version of software for Probabilistic and Prognostic Individual Aircraft Tracking (P2IAT) which is a new concept forecasting the fatigue damage in the metallic structure in an airframe. Individual Aircraft Tracking assesses the structural integrity of the airframe and is required for sustaining an airframe with condition-based maintenance. The P2IAT software is a developmental code scripted in Python. It is not well documented, nor is it optimized for performance. The code needs to be documented and packaged so that other organizations, besides the developer, can contribute to the further development of P2IAT. Optimization of the code is desired to enable more rapid decision making.

2.0 OBJECTIVE: The objective of this task order is to further develop the P2IAT software. This is to be accomplished through (1) creating software builds that enable easy distribution of the code to potential users and developers, (2) organizing the software for easy understanding of process flow, and (3) documenting the software including the process flow to facilitate future enhancements to the software.

3.0 TECHNICAL REQUIREMENTS:

Tasks may performed at RQ facilities or contractor facilities. Bi-weekly progress/status meetings, at a minimum, are required. These meetings may be in person or via teleconference.

The focus of work performed will be continuing development and refinement of the SAFER- P2IAT software for probabilistic fatigue tracking of individual aircraft. This software provides new capability for sustainment and condition-based maintenance.

Activities include, but are not limited to:

• Establish version control on the software and a repository for the various versions.

• Create executable software builds for the latest version of the software. Ensure these builds are available to government identified users.

• Determine and document the connections between the various routines and modules that make up SAFER-P2IAT. Create interface control documentation so that new routines and modules can be easily added to or substituted into the software. Create Software User Manuals to provide instructions regarding installations of the P2IAT software and detailed explanation of model inputs and geometry.

• Identify improvements that can be made to the software to improve performance and robustness. These improvements will be implemented as funding and manpower allow.

4.0 DELIVERABLES: The Contractor shall generate and provide data in accordance with the following Contract Data Requirements List (CDRL), DD Form 1423-1:

A001 – Scientific and Technical Reports – Final Report, DI-MISC-80711A/T, One/R

A002 – Scientific and Technical Reports – Spend Plan, DI-MISC-80711A/T, Monthly A003 – Funds and Man-Hour Expenditure Report, DI-FNCL-80331A/T, Monthly A008 – Status Report, DI-MGMT-80368A/T, Monthly A009 – Presentation Material, DI-ADMN-81373/T, As Required

The contractor shall propose additional deliverables for the TO as appropriate. In addition, software and hardware (including source code, firmware, libraries, and executables) developed under this TO shall be delivered with unlimited rights. All software developed under this task order shall be delivered in a format acceptable to both parties. The contractor shall identify any restrictions on the type of rights to be provided with software and hardware delivered but not developed under this TO, with full disclosure of any dependencies upon third party software/hardware.

5.0 GOVERNMENT FURNISHED INFORMATION: The SAFER-P2IAT source code currently in the government’s possession will be provided to the contractor. Any updates or modification to the software during the Airframe Digital Twin (ADT) Spiral 1 program will also be provided to the contractor.

6.0 FOREIGN PARTICIPATION: Foreign participation is not permitted on this task order.

7.0 PERIOD OF PERFORMANCE: The total period of performance for this effort is 36 months. This corresponds to 33 months of technical effort and 3 months for reporting.

8.0 SECURITY:

8.1. Operations Security. Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this contract be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this SOO. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of the contract.

8.2. Access to classified. All requested personnel for this effort will require at least a Secret clearance (Tier 3).

8.3. Sub-contracting. If the prime contractor sub-contracts work out; the prime contractor must submit a DD Form 254 for all assigned subcontractors within 30 calendar days of establishment of the contract or agreement to the Industrial Security Manager listed on the DD 254. Once an effort is over the contractor and subcontractors must account for all classified hardware and material given, used or generated during this effort. The contractor will submit an encrypted non-classified list of all materials and/or hardware in their position to the Government Contracting Officer. In the list of items the contractor should outline what items they wish to keep and the justification. The Government Contracting Officer and the Industrial Security Manager will determine if the material will be destroyed or returned back to the government. However, if there is a follow on effort a final DD form 254 must be issued to the contractor authorizing the contractor to retain the classified material, access, hardware for a specified time period.

8.4. Protecting information. The contractor shall not divulge any information regarding files, data, process activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors will require access to Government Automated Information Systems (AIS) and shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or contractor personnel leave work on this project, they will have three (3) days to terminate all their network user accounts and to return all access cards and base identification badges.

Contractors shall encrypt all emails containing technical data or other critical information for this program. The use of products such as Encryption Wizard and Amrdec Safe are highly encouraged for safe guarding information when transmitting information via email. Contractors shall comply with DoD 5400.7‑R/Air Force Manual 33‑302, DoD Freedom of Information Act (FOIA) Program, requirements. Unclassified information not approved for public release on non-DoD Information Systems shall be protected IAW DoDI 8582.01, Security of Unclassified DoD Information on non-DoD Information Systems, Enclosure 3, and the Program’s Security Classification Guide.