Attachment 4 SATURN Arrangement Data Requirements List.xlsx

TAB1_READ ME

• Frequency, due dates, and review times are subject to change based on mission requirements.

• Government Approved Awardee Formatting subject to change based on mission requirements

Deliverables without this content will be considered incomplete

• Arrangment #

• Program/Project Name

• Awardee Name

• Identifier (indicate draft or final if applicable i.e. P_CSP_Draft )

• Deliverable Title

• Submission Date

• All technical data shall be marked I.A.W. DoDI 5230.24 with Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD awardees only; Critical Technology, [author fill in date of report (dd mmm yy)]. Other requests for this document shall be referred to Air Force Research Laboratory/RDxx, 3550 Aberdeen Avenue, SE, Kirtland AFB, NM 87117-5776.

• All financial performance data shall be marked IAW DoDI 5230.24 with Distribution Statement E: Distribution authorized to DoD components only; awardee Performance Evaluation, [author fill in date of report (dd mmm yy)]. Other requests for this document shall be referred to Air Force Research Laboratory/RDxx, 3550 Aberdeen Avenue, SE, Kirtland AFB, NM 87117-5776

• Export control warning: All technical data shall be marked as follows: "WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25."

• “DESTRUCTION NOTICE—CUI documents may be destroyed by means approved for destroying classified information or by any other means making it unreadable, indecipherable, and unrecoverable.”

• Preparer's Name, email, and signature

AO receives Transmittal letters for all PM Deliverables Electronic copies of the report shall be delivered on CD-ROM (CD-R), and shall be marked I.A.W. ANSI/NISO Standard Z39.18-2005 (R2010). CD-RW and other forms of rewritable media are not acceptable E-Mail transmittal is not permitted unless encrypted and secure, and requires prior Government approval.

DELIVERABLES

• The summary shall include a brief statement of the overall project status , covering the accomplished technical activities and development, objectives of efforts, summary results of efforts, identification of major problems/deficiencies with impact, and recommended solutions

2. BODY OF REPORT

The Status Report shall contain the following items, where applicable:

• Milestone/task status. The status of each milestone/task as defined by the statement of work or arrangement, as applicable:

- A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include an overall status of each milestone, task, or unit of work. Include update schedule sheets, milestone charts, or task synopsis sheets identifying phase of task and percentage of completion of each task, technical instruction, or order

- Effort expended on each task to date, and a brief description of technical developments and accomplishments

• A narrative of outstanding problems existing as of the previous status report, and their resolution status

• New problem areas encountered or anticipated, their effect on the overall work effort/project and steps being taken to remedy problem situations

• Any other information which may cause significant changes in the program schedule

• Itemized man-hours and costs. Itemized man-hour and cost expenditure incurred for the reporting period by category and task, total arrangement expenditures, and funds remaining as of the reporting date

• Estimated cost-to-complete. The estimated costs required to complete the work task from the reporting date to the date of completion. This estimate shall be defined by categories as follows:

a. Original negotiated arrangement. A summary of all cost elements associated with the original negotiated arrangements. This is defined as the Awardee's original cost proposal, as negotiated and accepted by the Government. It is that cost as it appears on the original arrangement document. Its elements shall contain the cost estimate breakdown by category (i.e., direct labor (Sr. Engineer, Jr Engineer, draftsman, engineer shop, etc.), burden/overhead, material/parts, travel, subsistence, fringe, General and Administration (G&A) fee, outstanding commitments, etc.), as provided in the accepted proposal. Items and amounts specified in this entry shall remain constant on successive reports during the term of the arrangement

b. Latest negotiated arrangement changes. A summary of the latest negotiated arrangement changes. It shall be a recapitulation of the data elements listed above in the original negotiated arrangement, reflecting all subsequent changes resulting for arrangement modifications. Breakdown by category shall be as provided in the original negotiated arrangement unless altered by a arrangement modification. Indicated “none” if revised proposal has no effect.

• Funds expenditure graph.

A funds expenditure graph shall be included. The graph shall be reproducible to enable periodic changes reflecting current arrangement funding status to be entered. The graph shall portray, on a periodic basis, the planned versus actual total dollar expenditures and the percentage of the total arrangement dollars that the expenditure represent (refer to DI-FNCL-80331A for reference)

• Work completed graph A work completed graph shall be included that reflects the percentage of work completed through the current reporting period. The graph shall plot actual completion versus planned completion, and shall be maintained current and be fully legible and reproducible (refer to DI-FNCL-80331A for reference)

3. DELIVERIES STATUS

• The status of each deliverable end item, including data deliverables, as required by the arrangement.

• Provide item and arrangement identification, shipping/transmittal data, acceptance status, security classification, and schedule due date information

4. REPORT PREPARER

• Name of person(s) preparing report and contact information (phone, email).

5. APPENDICES

• Appendices where applicable, for tables, references, charts, or other descriptive material

• Each appendix shall be identified and referenced in the appropriate area of the report

* All financial performance data shall be marked IAW DoDI 5230.24 with Distribution Statement E: Distribution authorized to DoD components only; awardee Performance Evaluation, [author fill in date of report (dd mmm yy)]. Other requests for this document shall be referred to Air Force Research Laboratory/RDxx, 3550 Aberdeen Avenue, SE, Kirtland AFB, NM 87117-5776

1. IDENTIFICATION

• Agreement Number and title • Awardee name, address, phone number, CAGE code • Awardee Program Manager and/or arrangements Manager if there are 2 different POCS, names, phone numbers, email addresses

• Government POC Names - Agreements Officer & Program Manager • Security Classification

2. DESCRIPTIVE MATERIAL

• Material, system, and process diagrams, sketches, photographs, tables, forms, graphs, worksheets, charts, drawings, etc. as required/requested by the Government

3. ORGANIZATIONAL STRUCTURE & PERSONNEL

• A description of the program's organizational structure to include sub-Awardees/sub-Awardees

• Job title/Labor Category, assignment of functions, duties, responsibilities, and associated task

• Procedures, policies, and reporting requirements established to initiate, monitor, control, complete, and report on activities/tasks/deliverables

• The plan shall identify the names and roles of personnel assigned to accomplish tasks/complete deliverables

• The plan shall show how the combination of people assigned to each task provides a sufficient knowledge or experience base for that task/deliverable

• This includes identifying any special education, training, experience, or skills of these individuals. Also, any special administrative support requirements shall be identified

4. ORGANIZATIONAL INTERFACES

• A description of all interfaces between the Awardee and the Government and between the Awardee and other Awardees or sub Awardees to include Associate Awardee/Awardee agreements , which are necessary to complete the assigned tasking

• A description of the applicable responsibilities and functional relationships between those organizations

5. METHODOLOGY

• The plan shall include a narrative description clearly defining the technical approach (or method) including tools, standards, and procedures to be used by the Awardee to accomplish the tasks to complete deliverables

• All documentation, activity, or decisions required from the Government or other Government Awardee shall be identified

6. SCHEDULE

** (Developed collaborate lively with the Government post-award)

• The plan shall include a milestone chart(s) graphically depicting the schedule of events associated

• The level of detail shall be sufficient to clearly show how each subtask shall be performed. This includes: Awardee activities, Awardee deliverances (interim and final), including briefings (if required), other program milestones as appropriate, periodic milestones to allow adequate Government review of Awardee progress

7. RESOURCES CHART

• The plan shall include a resources chart that graphically and numerically identifies the Awardee’s total planned labor-hour level of effort (LOE) and LOE by month for each subtask identified

• Proposed monthly subtask labor-hours shall be broken out by labor category

8. AWARDEE REQUESTED/SUGGESTED DATA

• The plan shall include the Awardee’s best assessment of any additional data required by the Awardee

• This list shall be as detailed as possible and shall include document titles, responsible Government organizations, and responsible Government Awardees

• The criticality of each data required shall be identified

9. DELIVERABLES

• The plan shall include a brief description of the contents of each deliverable to be provided

10. REPORTS

• The plan shall describe the Management methods the Awardee will employ to ensure meeting all preparations, format, and submittal requirements established by Government

DI-MGMT-81117A • ONCE

• UPDATES - ANNUALLY: UPDATES SHALL BE DELIVERED 30 CD AFTER THE LAST BD OF EACH ARRANGEMENT YEAR

• The format and content of the data listed on the DAL shall be as prepared by the Awardee to document compliance with the SOW Task and Arrangement requirements.

•The list shall include the identification number, title which shall describe content, security classification, and in-house release date.

• The list shall also identify the Government Rights to the data using the following codes:

GPR - Government Purpose Rights UR - Unlimited Rights LR Limited Rights RR Restricted Rights (computer software only) CLR - Commercial License Rights for commercial technical data CSLR - Commercial Software License Rights for commercial computer software and commercial computer software documentation SNLR - Specifically Negotiated License Rights •Once data is listed on the DAL the data shall be made available to the Government as cited in the arrangement

1. FORMAT

• The report shall be in an electronic .xls or .xlsx compatible format.

2. CONTENT

The report shall contain the following column headers (i.e., data fields):

A. Arrangement Number B. Agency or Service Asset Identification Number (GFP Only) C. Arrangement or Asset Identification Number D. Item Description E. Manufacturer Part Number F. Manufacturer Model Number G. Manufacturer Serial Number H. National Stock Number (NSN) (if applicable) I. Quantity J. Unit of Measure K. Unit Acquisition Cost L. Unique Item Identifier (if registered in the Item Unique Identification (IUID) Registry; GFP only) M. Asset Location N. Asset Sub-Location (if applicable) O. Type of Government Property (i.e., Government Furnished Property (GFP) or Arrangement or Acquired Property (CAP) P. Classification of Government Property (i.e., Communication Security (COMSEC), Equipment (EQP), Material (MAT), Special Test Equipment (STE), or Special Tooling (ST)) Q. Date of Last Physical Inventory R. Federal Condition Code

DI-MGMT-80441D INITIAL REPORT:

30 CD AFTER INCLUSION OF GFE/GFP/CAP IN ARRQANGEMENT

SEMI ANNUAL REPORTS:

EVERY 6 MONTHS AFTER BASELINE

CLOSEOUT:

DRAFT

90 CD PRIOR TO PERFORMANCE END DATE

FINAL

• Interim reports every twelve (12) months (or such longer period as may be specified by the Agreements Officer) from the date of the award, listing subject inventions during that period and stating that all subject inventions have been disclosed or that there are no such inventions

• Upon request, the filing date, serial number and title, a copy of the patent application and patent number, and issue data for any subject invention for which the Awardee has retained title

• Upon request, the Awardee shall furnish the Government an irrevocable power to inspect and make copies of the patent application file

• A final report, within three (3) months after completion of the work, listing all subject inventions or stating that there were no such inventions

• Upon request, the filing date, serial number and title, a copy of the patent application and patent number, and issue data for any subject invention for which the Awardee has retained title

The minutes shall include at a minimum the following information:

• Date

• Location or method of meeting i.e. telecom, CHES

• Identification of the acquisition (system, equipment, arrangement number) for which the meeting was held

• The name of the awardee and address to which the acquisition activity should acknowledge receipt of comments.

• Names of awardee and Government personnel participating to include name, rank, grade or position, activity represented, activity symbol/code, phone numbers, and emails, as appropriate.

• Subjects discussed i.e., telephone conversations, meetings, etc.

• summary of the discussions, decisions, agreements reached, and directions of the conference or individual subcommittees thereof.

• Action items resulting from the conference.

• Briefing charts/copies of presentation materials, if presented, shall be attached to the minutes for information only

DI-ADMIN-81308 CONFERENCE REPORT

DI-ADMN-81250B CONERENCE MINUTES

• Awardee format is acceptable with the exception that the Government must approve the use of any awardee insignia, trade names or symbols

• Shall include a text of any accompanying verbal material unless the verbal portion is included as part of the electronic presentation

• The following statements shall be included in all materials:

"The publication of this material does not constitute approval by the Government of the findings or conclusions herein. Wide distribution or announcement of this material shall not be made within specific approval by the sponsoring Government activity."

• THE REPORT WILL BE PUBLISHED WITH THE DEFENSE TECHNICAL INFORMATION CENTER (DTIC) BY AFRL STINFO OFFICE. Under no circumstances shall the awardee submit any version of the scientific and technical report to DTIC.

• GUIDANCE FOR PREPARATION OF THE REPORT: The Scientific and Technical Report shall be prepared I.A.W. the most current ANSI/NISO Standard Z39.18-2005, or most current AFRL ANSI report preparation guidance. The awardee shall complete the most current SF 298: Blocks 2-5a, 6, 7, 8 and 13 (if applicable), and 14-16c, and submit it with the report. Incomplete reports will be immediately returned to the awardee. Following AFRL technical and STINFO reviews, any revisions required will be returned to the awardee. NOTE: The report preparation guidance and SF 298 are available at: https://www.afrl.af.mil/RD/

• GUIDANCE FOR PREPARATION OF THE REPORT

The Scientific and Technical Report shall be prepared I.A.W. the most current ANSI/NISO Standard Z39.18-2005, or most current AFRL ANSI report preparation guidance. The Awardee shall complete the most current SF 298: Blocks 2-5a, 6, 7, 8 and 13 (if applicable), and 14-16c, and submit it with the report. Incomplete reports will be immediately returned to the Awardee. Following AFRL technical and STINFO reviews, any revisions required will be returned to the Awardee. NOTE: The report preparation guidance and SF 298 are available at: https://www.kirtland.af.mil/Units/AFRL-Directed-Energy-Directorate/ •The Awardee shall deliver two editable electronic copies of the report. The electronic copies shall be an editable .pdf file and the most current version of Microsoft Word. Submission via unencrypted or unsecure email is not permitted. If encrypted email is not available, please use: https://safe.apps.mil/.

• UPON NOTIFICATION OF ACCEPTANCE OF THE SCIENTIFIC AND TECHNICAL REPORT FROM THE PROGRAM OFFICE, the Awardee shall submit the final Receiving Report (DD Form 250) in WAWF. In preparing the final DD Form 250, code the shipment number with a “Z.” Do not upload the Scientific and Technical Report into WAWF or DTIC. NOTE: SUBMITTAL OF THE DD FORM 250Z PRIOR TO ACCEPTANCE NOTIFICATION WILL RESULT IN REJECTION OF THE DD FORM 250Z FINAL RECEIVING REPORT.

• All technical data (including electronic media/CD-R) shall be marked I.A.W. DoDI 5230.24 with Distribution Statement D, and other required markings, shown indented below:

“Distribution authorized to Department of Defense and US DoD Awardees only; Critical Technology, Export Controlled [Awardee fill in date of report (did mmm yy)]. Other requests for this document shall be referred to AFRL/RDxx, 3550 Aberdeen Avenue, SE, Kirtland AFB, NM 87117-5776.” (ADD THIS ENTIRE DISTRIBUTION STATEMENT TO THE BOTTOM OF EVERY PAGE OF THE REPORT EXCEPT THE SF 298.)

“WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751, et seq.) or the Export Administration Act of 1979, as amended. Title 50 U.S.C. App 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate I.A.W. the provisions of the DoD Directive 5230.25.” (ADD “WARNING: EXPORT CONTROLLED” TO THE BOTTOM OF EVERY PG OF THE REPORT EXCEPT THE SF 298.)

“DESTRUCTION NOTICE—CUI documents may be destroyed by means approved for destroying classified information or by any other means making it unreadable, indecipherable, and unrecoverable.”

• The Awardee shall deliver the Scientific and Technical Report, in final format, no later than the date specified in the Schedule. The USAF will review and, if necessary, return the report with comments no later than the date specified in the Schedule. If the report is returned to the Awardee with comments, the Awardee shall deliver the final copy of the report no later than the date specified in the Schedule.

• The awardee shall provide appropriate data files, including applicable software test environment/platform, and a description of the version and data products

• An agreed upon format/platform will be defined at the start of arrangement as to how to deliver these data products (i.e. CD-ROM, Air Force approved file transfer system, etc.)

• Documentation shall be tailored per agreement between the awardee and the government

1. GENERAL

• All documentation will be provided at a level of detail sufficient to provide a developer, with comparable levels of expertise, the ability to further develop the deliverable

2. CONTENT

The documentation shall contain:

• Full description of all software supplied.

•Instructions for using all routines and programs

• Listing of each program supplied

3. SOURCE CODE

• For each program

• For each routine

• Installed on Government specified computer and operating system

• Tested on Government specified computer and operating system **Compiled and execution ready object code for the Government specified computer and operating system

It describes the CSCI-wide design decisions, the CSCI architectural design, and the detailed design needed to implement the software. The SDD may be supplemented by Interface Design Descriptions (IDDs) (DI-IPSC-81436) and Database Design Descriptions (DBDDs) (DI-IPSC-81437) The SDD, with its associated IDDs and DBDDs, is used as the basis for implementing the software. It provides the acquirer visibility into the design and provides information needed for software support.

This Data Item Description (DID) contains the content and intended use information for the data deliverable resulting from the work task described in paragraph 6.3.1.4 of IEEE 15288.1, or by the specific and discrete task requirements as delineated in the arrangement.

The Awardee shall provide a Systems Engineering Management Plan (SEMP) as described in DI-SESS-81785A but tailored to the mission assurance/risk class and level of complexity of the specific development effort.

. Content.

Reference documents -

a. Office of the Secretary of Defense (OSD) Systems Engineering Plan (SEP) Outline.

b. IEEE 15288.1, IEEE Standard for Application of Systems Engineering on Defense Programs

c. IEEE 15288.2, IEEE Standard for Technical Reviews and Audits on Defense Programs

Format - The SEMP shall be consistent with and address all topics in the government SEP, if available. In the absence of a government SEP, the SEMP shall address the topics in the OSD SEP Outline active at the time of the Request for Proposal (RFP).

Minimally, the SEMP shall:

• Describe the Awardee's planned engineering approach to meeting the program’s arrangement, objectives, and overall technical and management approach

• Describe the Awardee's detailed operational plan for executing systems engineering, including integration of the specialty engineering disciplines.

• Describe planned technical solution activities, including:

a. Development, documentation, maintenance, and communication of the system architecture, including both internal and external interfaces.

b. Formal technical reviews and audits, as defined in IEEE 15288.2 or by the specific and discrete task requirements delineated in the arrangement, including the entry and exit criteria for each review/audit.

c. Trade studies for system requirements definition, architecture definition, design definition, integration, and verification/validation decisions.

d. Integration, verification, and validation down to the appropriate system element level.

• Describe related planning associated with application of the Awardee's systems engineering processes as tailored to meet the needs of the program and at a level of detail necessary for the Awardee to manage and execute the technical effort.

• Provide detail related to other areas deemed necessary to execute systems engineering to meet the program’s arrangement requirements, objectives, and overall technical and management approach.

DI-SESS-81785A • Once with annual updates

• See draft/final due dates

• Updates shall be delivered 30 CD after the last BD of each arrangement year 60 CD AAA PM 30 CD REVIEW AND COMMENT 15 CD AO PM

DROP DOWNS

/AS REQUESTED