FA8650-17-S-6001-Atch1c.pdf
PDF 104 KB Posted
- Attached to
- Science and Technology for Autonomous Teammates (STAT) Federal contract opportunity
- Solicitation number
- FA8650-17-S-6001
About this file
This document contains a federal contract opportunity solicitation for the Science and Technology for Autonomous Teammates program. The solicitation seeks proposals to develop and demonstrate autonomy technologies that will enable various Air Force mission sets in the areas of multi-domain command and control, intelligence processing and dissemination, and manned-unmanned combat teaming. Technologies are sought to ingest and understand mission tasks and intent, respond appropriately to human direction and orders, and respond intelligently to threats and unplanned events. Chosen technologies should be open, reusable, adaptable, platform agnostic, secure, credible, affordable, and enduring. The program will integrate various technologies developed by the Air Force Research Laboratory and industry into technology demonstrations with all necessary software, hardware, and documentation to support modeling and simulation environments for future capability development. All technology development efforts must adhere to specified interface designs and standards.
AFRL Form 25
View the file
Other files for this federal contract opportunity
Show all 50
Science and Technology for Autonomous Teammates (STAT) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ALL PURPOSE CHECKLIST Paqe 1 of 1 Page(s)
TITLE/SUBJECT/ACTIVITY/FUNCTIONAL AREA
AFRL QUALITY FINAL TECHNICAL REPORT (TR)
OPR
AFRL/CSC
No. ITEM (Assign a paragraph number to each item. Draw a horizontal line between each major paragraph)
Contract No. or Local Identifier:_________________________________________________
Author
(Y/N/NA)
WU MGR
(Y/N/NA)
STINFO
(Y/N/NA)
1.
Is the TR a comprehensive description of the research and NOT just a journal article, briefing charts, collection of status reports, restatement of the statement of work, or a duplicated report submitted for another work unit?
2.
Does the TR contain the required elements of a scientific report per AFRL ANSI/NISO Standard Z39.18 -2005 (this includes methods, assumptions, procedures, results and discussion, conclusions, recommendations, and references)?
3.
Is the TR logically organized and developed in one file/one format (PER CDRL)?
4.
Is the writing clear and concise, accurately depicting all the data (positive and negative) and does the TR contain all the necessary information to duplicate the research, if necessary?
5.
Are all parties responsible for the data properly acknowledged for their contribution?
6.
Are all classified data properly marked and are markings properly placed (i.e., pages marked with highest classification, top/bottom, paragraphs marked, etc.)?
7.
Are data rights content properly identified (portion marked, etc.,) throughout the report per assertions rights at contract award?
8. Is data that is delivered with less-than-unlimited rights contained only in an appropriately marked appendix to the final report (except for contracts awarded under the SBIR or STTR program)? Is there a waiver to this requirement with written approval from the Technical Director?
9. Are all formulas and equations clearly presented?
10.
Are all technical terms defined in a glossary and are all acronyms, abbreviations, and symbols properly defined (if needed)?
11.
Are all references that are cited in the text listed with a full citation in the references list?
12.
Are there any supporting documents that need to be appended to the TR?
13.
Have there been any meetings with the Government in which notes were taken regarding the TR, has the author reviewed the notes to ensure that all requirements have been addressed?
14.
Is there a signed notice page that indicates correct data rights per the data rights section of the contract?
15. Are specific pages and/or sections marked in the “location of data rights” within the data rights legend?
16. Have all appendices been identified and included in the TR?
17.
Is the SF 298, Report Documentation Page, properly completed?
18.
Has a distribution statement and export control been addressed?
19. Does the distribution statement reflect the appropriate reason(s) and audience for the TR content?
COMMENTS (If additional space is needed, enter comments on back of form)
AUTHOR:(print)_________________________________Signature_____________________________________Date___________
WU MGR:(print)_________________________________Signature_____________________________________Date____________
STINFO:(print)__________________________________Signature_____________________________________Date____________
AFRL Form 25, Oct 10 PREVIOUS EDITIONS OBSOLETE Prescribing Directive, AFRLI 61-204
| Contract No. or Local Identifier: |
| Text2: |
| Text3: |
| Text4: |
| Text5: |
| Text6: |
| Text7: |
| Text8: |
| Text9: |
| Text32: |
| Text38: |
| Text47: |
| Text50: |
| Text53: |
| Text56: |
| Text12: |
| Text15: |
| Text21: |
| Text11: |
| Text14: |
| Text17: |
| Text18: |
| Text20: |
| Text22: |
| Text24: |
| Text25: |
| Text26: |
| Text27: |
| Text23: |
| Text29: |
| Text30: |
| Text33: |
| Text36: |
| Text39: |
| Text10: |
| Text34: |
| Text37: |
| Text40: |
| Text43: |
| Text52: |
| Text35: |
| Text44: |
| Text1: |
| Text13: |
| Text16: |
| Text19: |
| Text28: |
| Text31: |
| Text46: |
| Text55: |
| Text41: |
| Text42: |
| Text45: |
| Text48: |
| Text49: |
| Text51: |
| Text54: |
| Text57: |
| AUTHOR:(print: |
| Signature: |
| Date: |
| WU MGR:(print: |
| Signature: |
| Date: |
| STINFO:(print: |
| Signature: |
| Date: |
| TextField1: |
File details come from the government source that posted it. Updated .