EPIC Statement of Work DRAFT.pdf

AIR FORCE RESEARCH LABORATORY

INFORMATION DIRECTORATE

ROME, NEW YORK

STATEMENT OF WORK (SOW)

FOR

ENTERPRISE PROTOTYPE INITIATIVE CONSORTIUM (EPIC)

RFI-RFZF-B001

21 APR 2026

TABLE OF CONTENTS

1.0 OBJECTIVE 3

2.0 SCOPE 4

3.0 BACKGROUND 4

4.0 TECHNICAL REQUIREMENTS 5

1.0 Objective:

1.1 The objective of this Other Transaction Agreement (OTA) is for the Recipient to perform a coordinated prototyping and testing program in conjunction with the Government that speeds the ability to rapidly prototype Government, industry and academia capabilities across all technology areas of interest relevant to the Air Force Research Laboratory (AFRL) proposed to be acquired or developed by the Department of War (DoW) to sustain U.S. military technological advantage.

Additionally, this OTA will serve as a vital tool to help DoW achieve military integration that is critical to reducing the cost of defense information systems technologies.

2.0 Scope:

2.1 The scope of this OTA encompasses the development, testing, evaluation, measurement, demonstration, integration, delivery of prototypes, acquisition of test articles, recurring

Operational Test and Evaluation (OT&E), and procurement of prototypes and technologies spanning the full breadth of AFRL mission sets, including those that may emerge and evolve during the period of performance. See Appendix 1 to the Statement of Work titled EPIC Areas of

Interest for a list of current technology areas.

2.2 Project-Level Orders (PLOs) will be issued under this OTA. Through these efforts the Other

Transaction (OT) Lead and Project-Level Performers (PLPs) will iteratively prototype, modify, enhance, test, measure, document and integrate next-generation Open System Approaches (OSA) for capabilities and tools that satisfy requirements for open-architecture (hardware, software, applications).

2.3 These prototypes will provide new innovative capabilities that provide measurable improvements in performance, function, delivery, flexibility, cost, etc. for rapid transition and use in the field.

3.0 Background:

3.1 AFRL/RI has awarded two previous OTAs, (OSAI (Open Systems Acquisition Initiative) and

OTAFI (Open Technology and Agility For Innovation) both which were OTPs (Other Transaction for Prototypes). These efforts were focused on producing prototypes in command, control, communications and cyber, intelligence, surveillance, and reconnaissance (C4ISR) technological focus areas that increased the efficiency and capabilities of information systems proposed to be acquired or developed by the DoW. These OTA projects utilized numerous vendors to include

Non-traditional Defense Contractors (NTDCs), small businesses, nonprofit organizations, and commercial firms. Majority of projects been awarded and are led by NTDCs with others including significant NTDC participation. These OTA projects have met the Air Force (AF) goals of development, test, measurement, demonstration, integration, and delivery of prototypes related to

C4I&C information sharing information systems. AFRL/RI is now seeking to leverage its expertise in utilizing OT consortiums to facilitate the expansion of this innovative vehicle across the entirety of AFRL operations.

4.0 Technical Requirements:

4.1 The Recipient and Project Level Performers shall execute coordinated prototyping efforts spanning the full breadth of AFRL mission sets, including those that may emerge and evolve during the period of performance. Prototyping is currently defined under Title 10 U.S.C. §4022.

Examples of prototyping include but are not limited to:

4.1.1 Agile Engineering, Development & Transition: Develop, demonstrate, implement and transition prototype technologies, systems, concepts and designs that address the broad and diverse capabilities in agile prototyping, testing, advanced engineering development and training for modernized systems or subsystems to achieve greater levels of resiliency, autonomy and security.

Related areas of interest include but are not limited to: development of modern application services, service-based data architectures and designs, high-performance computing technologies, mobile sensors, Multi-Level Security domain information sharing and collaboration technologies, rapid prototyping and development of emerging technologies.

4.1.2 Capability Performance Analysis: Develop, demonstrate, research and prototype to improve hardware and software performance concepts and designs that address system engineering and integration services for information systems, research and development programs, modeling and simulation, and using data to develop, improve and refine products and analysis tools. Related areas of interest include but are not limited to: development of technologies and prototype systems that identify vulnerabilities and key technology gaps.

4.1.3 Capability Ecosystems: Develop, demonstrate, research and prototype to improve concepts and designs that address information technology needs, including: information systems support and development, data architecture and design, enterprise solutions, product lifecycle management and training. Related areas of interest include but are not limited to: development of information systems that support client/server architecture, open system portability and scalability, Multi-Level

Security mechanisms among and between security domains, improved mobile systems and automated application platforms.

4.1.4 Information Systems Security: Develop, demonstrate, research and prototype to balance information security with information sharing. This includes: cyber-warfare (both offensive and defensive); and cyber security tools, concepts and designs to address threats, vulnerabilities, and cyber security requirements of systems, and applications. Related areas of interest include but are not limited to: research into, and development of prototype software, on systems using applied system security engineering processes that enforce risk mitigation as well as implementing cost effective countermeasures not limited to information assurance controls, software protection products, effective rigorous software development processes as well as enforcing software design rigor and information protection measures.

4.1.5 Information Systems Supportability: Develop, demonstrate, research and prototype information technologies to improve engineering design, technical support data and software support services while lowering lifecycle management costs. Related areas of interest include but are not limited to: supportability design and analysis, engineering process improvement, field support, obsolescence, rapid prototyping, systems engineering, and technology insertion.

4.1.6 Assured and Trusted Cyber Infrastructure: Develop, demonstrate, research and prototype to provide assured and trusted cyber infrastructure. Assured and trusted cyber infrastructure begins with proven-correct designs that are technologically immune to threats and have an autonomous ability to modify the cyber domain to avoid unforeseen attacks and emerging threats. Related areas of interest include but are not limited to: mission assurance in a zero trust environment, information operations, securing the space mission, Command and control of small lethal UAS swarms and 5G for military applications.

4.1.7 Cyber Operations Technologies: Develop, demonstrate, research and prototype to enhance cyber operations. Cyber operations technologies are used to safeguard, secure, or target computer networks, systems, or information. These operations include defensive cyber operations (DCO) and offensive cyber operations (OCO). Related areas of interest include but are not limited to:

methods of improving cyber coordination, advancing capabilities to conduct cyberspace operations, operational and contingency planning, Signals Intelligence (SIGINT) and Electronics

Warfare (EW).

4.1.8 Open System Architectures for Trusted and Agile Platforms: Develop, demonstrate, research and prototype current and emerging Open System Architecture (OSA) standards and approaches to ensure information exploitation interoperability. Related areas of interest include but are not limited to: cognitive waveform generation, machine learning/artificial intelligence, network control and analysis, network layer simulation and network control evaluation.

4.1.9 Advancing Computing Technologies: Develop, demonstrate, research and prototype computational capabilities with greater sophistication, autonomy, intelligence, and assurance for addressing dynamic mission requirements. Related areas of interest include but are not limited to:

emerging technologies that can provide revolutionary computational capabilities which enable greater system adaptability, high performance embedded computing that supports on-board processing, advanced machine learning applications, robust and secure machine learning, and non-conventional systems and applications,

4.1.10 Neuromorphic Computing Technologies: Develop, demonstrate, research and prototype to advance the understanding and development of computationally intelligent systems towards increased perception, adaptability, resiliency, and autonomy for energy efficient, technologies.

Related areas of interest include but are not limited to: hardware component of energy efficiency, utilization of advancements in computational neuroscience, nanoelectronics and nano photonics, embedded deep learning, trusted and robust machine learning, pattern recognition and signature analysis, autonomous adaptive operations, human-machine collaboration, and neural control of complex-systems,

4.1.11 Space Domain Technologies: Develop, demonstrate, research, and prototype to produce hardware and software solutions for space domain technical challenges. Related areas of interest include but are not limited to: space object detection and characterization; tracking and imaging;

rapid, on-demand orbit determination; multi-phenomenology sensor integration (e.g. optical, radar, passive radiofrequency); ranging to space objects; techniques, algorithms, architecture designs, etc.

for collaborative autonomous telescope networks; uncorrelated track association; machine learning algorithms to advance the state-of-the-art SSA; quantum communications/networking; advanced laser communication technology; and other integrated space base and/or ground based SDA solutions to contribute to 24/7 space domain awareness.

4.1.12 Recurring Operation Test and Evaluation (OT&E) (generally performed after required approval for procurement or production for the purpose of continuing performance acceptance):

Evaluate items for operational, doctrinal, or organizational purposes. Related areas of interest include: recurring OT&E from systems under paragraphs 4.1.1- 4.1.11 to estimate a system’s operation suitability, conduct operational testing after accepting an item for operation use and operational tests to demonstrate how the item operates or to develop operational tactics.

4.1.13 Prototype Support, Associated Articles and Manpower: Develop supporting articles, regularly procured, to meet established general requirements which are not consumed during testing. Utilize existing manpower and operational services to support operational testing in the course of normal operations. Related areas of interest include prototype support for systems under paragraphs 4.1.1- 4.1.11

4.2 Provide for proposal preparation and – following Government selection of successful proposal(s) – execute and administer individual prototype project agreements with consortium members. Conduct and submit to the Government a cost and price analysis using the Government provided guide. Make arrangements for timely performance and payment in accordance with project deliverables/milestones.

4.3 Perform pre-delivery testing and verification of claimed performance attributes for individual

Project Level Agreements.

4.4 Collaborate and cooperate with the Project-Level Performers and the Government’s technical and agreements teams to continuously refine and improve the business and technical processes outlined in the OTA. As appropriate, work with the Government to formalize process refinements in the Agreement.

4.4.1 Submit feedback from Project-Level Performers at completion of each project, including (1) how key technical goals of a project were met; (2) satisfied success metrics incorporated into the

Prototype OT; or (3) accomplished a particularly favorable or unexpected result that justifies the transition to production and then provide feedback on what went well with the process to get a successful prototype and what during the process could have been improved such as requirements, scope and access to information.

4.5 At the direction of the Government, accomplish the following technical objectives, in cooperation with Project-Level Performers:

4.5.1 Develop designs, processes, tools and equipment for cost effective implementation of novel/new control unit systems, information automated systems, information system security, software performance strategies, field support and training, obsolescence, rapid prototyping and technology insertion.

4.5.2 Conduct prototyping activities, including but not limited to development and maturation of information system technologies, innovative information assurance, cyber tools acquisition, secure mobile, multi security domain file sharing, access, and collaboration and related technologies in a manner that enables effective transition of the prototypes to programs of record via early consideration of life-cycle support aspects (affordability, manufacturability, training, testing, etc.).

4.5.3 Pursue AFRL emerging and mature information system technologies to include air and space domain technologies, cyberspace and electronic warfare domains, human performance, advanced materials and manufacturing, sensors, directed energy, propulsion, munitions, and cross-cutting or emerging multidisciplinary technologies that support demonstrating the technology in a

Government-identified operationally relevant environment.

4.5.4 Deliberately mature specified emerging technologies to the point of demonstrating the technology in a Government-identified operationally relevant environment.

4.6 Accomplish the following business objectives:

4.6.1 Actively promote the OTA to non-traditional vendors to increase participation over the life span of the OTA.

4.6.2 Seek out new and innovative COTS products or prototypes and vendors that have solutions that are amenable to solving information system Government requirements, work within modernized open architectures, and are mature enough for rapid transition with reduced lifecycle management costs.

4.6.3 Mentor and guide participants in individual development projects to develop their ideas from concept through integration within the information systems and assist them in proposing their ideas and in managing the Project-Level Agreements through completion.

4.6.4 Provide an environment of cooperation and openness for all prospective Project-Level

Performers (including both current and prospective consortium members). Provide advertising of current membership; and, if required, establishing fair and reasonable membership fees (examples might include fees that are based on vendor size, income, and/or business type (traditional vs. non-traditional)).

4.6.5 Ensure the nature of the consortium membership agreement facilitates and eases the entry of commercial, small, and non-traditional companies, academia, etc. into this sector of the defense market.

4.6.6 Provide and publish a membership agreement template to promote ease of entry for all potential participants.

4.6.7 Provide rapid turn-around time from technical selection to submission of work package for individual development agreements to the Government Agreement Officer Representative (AOR) within 1 week.

4.6.8 Facilitate access to and safeguarding of classified information in support of prototype development. Activities include but are not limited to coordinating visit requests to Government

Installations where classified information may be shared with Project-Level Performers, coordinating clearance verification, access, and safeguarding of required classified resources.

Tracking and disposition of this support will be the OT Lead’s responsibility upon conclusion of the individual project effort(s).

4.6.9 Seek out and engage with potential third-party funding sources to partner with funding the development of prototypes as required.

4.6.10 Facilitate teaming and take necessary actions to address member issues that arise in order to ensure successful completion of the project.

4.7 Accomplish the following outreach objectives:

4.7.1 Promote membership for new Project-Level Performers that have products or ideas that improve legacy information systems in new and innovative ways using Open Systems

Architectures and modernized development standards and processes.

4.7.2 Leverage insights obtained via collaborative planning between the Government, OT Lead, and vendors so that: (a) the Government is better informed on emerging information system technologies from the private sector, and (b) industry achieves greater understanding of emerging

DoW operational needs that can be addressed with selected technology solutions.

4.7.3 Provide a collaboration presence (Web-site, Wiki, e-mail, etc.) on the Internet that describes the OTA, its goals, the OT Lead and Project-Level Performers, how vendors can participate, and on-going opportunities throughout the lifespan of the OTA.

4.7.3.1 Develop, maintain and update an interactive website for consortium members and government entities containing new events, whitepapers, templates, Consortium Membership

Agreement template, forms, job aids, instructions, contacts and other identified information by the

Agreements Officer Representative (AOR).

4.7.4 Plan, promote, attend, and staff bi-annual EPIC Consortium Showcases in cooperation with

AFRL personnel. The following are specific tasks required for each Consortium Showcase:

4.7.4.1 Publication of Consortium Showcase dates to consortium members at least eight (8) months prior to the event.

4.7.4.2 Recruitment of vendors from consortium members for the following areas:

4.7.4.2.1 Demonstration of innovative or unique technology or process.

4.7.4.2.2 Presentation of innovative or unique technology or process.

4.7.4.2.3 Staffing a booth.

4.7.4.3 General attendance at Consortium Showcase.

4.7.4.4 Recruitment of third party funding source representation.

4.7.4.5 Management of attendee, vendor, and speaker registration at event.

4.7.4.6 Development of event schedule and layout in coordination with AFRL personnel.

4.8 Reporting and Documentation.

4.8.1 Continually determine the status of the effort and report progress made toward accomplishment of Agreement requirements in monthly performance status reports. Any probable performance issues should be reported to the Project Level Order Government AOTR within 5 days of knowledge of such issues.

4.8.2 On a quarterly basis, conduct oral presentations at such times and places at the discretion of the Project Level Order AOTR. Presentation topics and invitees should be discussed with and approved by the AOR Attendees should be government only with limited attendance of project level vendors and new potential OT users. Provide status of technical progress made to date in performance of this Agreement during presentations as well as success stories.

4.8.3 On a bi-annual basis, document all technical work accomplished, and information gained during performance of this acquisition. Document the system concepts, analysis, models, and the results of analysis, implementation, testing, and demonstrations. Cross-reference each design, engineering, and process specification delivered to permit full understanding of the techniques and procedures used in evolving the technology or processes developed. Include all pertinent observations, nature of problems, positive and negative outcomes, and design criteria established where applicable. Document procedures followed, processes developed, “lessons learned,” user comments and additional requirements to be fulfilled prior to transition to the user community, user documentation as an appendix, and other useful information.

4.8.3.1 At the conclusion of each R&D Project Level Order , document the items described in paragraph 4.8.3 in a final report to be published and archived by the Defense Technical

Information Center (DTIC).

4.8.4 For each non R&D Project Level Order document the accomplishments, problems encountered, issues and recommendations in a brief summary report at the completion of the

Order.

4.8.5 Provide published reports quarterly that include the following (items that do not require updating do not need to be provided):

4.8.5.1 Stakeholder meeting minutes

4.8.5.2 Open membership roster that includes a description of the membership’s core competencies

4.8.5.3 By-laws

4.8.5.4 Board membership

4.9 Software, Hardware, and Artifacts.

4.9.1 Deliver all software, hardware, and artifacts developed, assembled, or acquired to the

Government in accordance with the Agreement schedule, each Project-Level Order and the following:

4.9.1.1 Deliver software developed under this effort as source and object (executable) code, if specified in the Project-Level Order, delivered on electronic media with all necessary instructions.

Include the commented source listings and source code.

4.9.1.2 Delivered software under this effort is to be completely maintainable and modifiable with no reliance on any non-delivered computer programs or documentation. The requirement for delivered software to be completely maintainable and modifiable does not apply to software that is delivered under the license provisions listed in the “Identification and Assertions of Restrictions on

Government, Use, Release or Disclosure of Technical Data” attached to each Project-Level

Agreement.

4.9.1.3 Provide any non-commercially available tools required for use of the prototype tool(s).

4.10 Obtain and maintain the Cybersecurity Maturity Model Certification (CMMC) level required by individual Request for Project Proposals and Statements of Work for individual PLOs.

4.11 Comply with all Government foreign travel requirements as specified by this Agreement and in individual PLOs. Additional information and/or training may be required on a country by country basis.

4.12 Adhere to cloud computing requirements as set forth in individual PLOs including some or all of the following tailored to the applicable data types for each PLO:

4.12.1 When the PLO will require or allow the Recipient or Project Level Performer access to

Privacy Information. Content contained within the cloud services is subject to the Privacy Act. As much, the recipient shall adhere to the privacy Act, Title 5 of the U.S. Code, Section 552a, and applicable agency rules and regulations.

4.12.2 When the PLO will require or allow the Recipient or Project Level Performer access to

Level 2 Public or Non-Controlled Unclassified Information. Content contained within the cloud services is subject to the Freedom of Information Act (FOIA). As such, the Recipient shall adhere to the FOIA regulations, and applicable agency rules and regulations. This level accommodates

Non-CUI information categorizations based on CNSSI (Committee on National Security Systems)

Instruction 1253 up to low confidentiality and moderate integrity (L-M-x).

4.12.3 When the PLO will require or allow the Recipient or Project Level Performer access to

Level 4 Controlled Unclassified Information, including “Export Controlled,” and “For Official

Use Only” data, and non-National Security Systems (NSSs). Content contained within the cloud services is subject to the Freedom of Information Act (FOIA). As such, the Recipient or Project

Level Performer shall adhere to the FOIA regulations, and applicable agency rules and regulations.

This level accommodates CUI information categorizations based on CNSSI (Committee on

National Security Systems) Instruction 1253 up to moderate confidentiality and moderate integrity

(M-M-x).

4.12.4 When the PLO includes work on this effort will require or allow the Recipient or Project

Level Performer access to Level 5: Higher Sensitivity CUI, Mission Critical Information, and

NSSs. This CUI requires a higher level of protection as deemed necessary by the information owner, public law, or other Government regulations, such as information related to unclassified

NSSs. This level accommodates NSS and CUI information categorizations based on CNSSI

(Committee on National Security Systems) Instruction 1253 up to moderate confidentiality and moderate integrity (M-M-x).

4.12.5 When the PLO includes access to Level 6 data types hosted by external cloud service providers: Work on this effort will require or allow the Recipient or Project Level Performer access to Level 6: Classified Information up to SECRET which includes information that has been determined to be classified national security information or Restricted Data (RD). This impact level requires a higher level of protection and accommodates classified information categorizations up to moderate confidentiality and moderate integrity (M-M-x).

4.12.6 When the PLO includes access to information above SECRET level to essentially acknowledge that the DoW Cloud Computing Security Requirements Guide (SRG) does not apply to this level of information: Work on this effort will require or allow the Recipient or Project

Level Performer access to classified information above SECRET which includes information that has been determined to be classified national security information or Restricted Data (RD). Use cloud services approved for the classification and information categorization in accordance with applicable DoW and Intelligence Community policies.

4.12.7 Data Ownership. All Government data, Government-related data, and metadata is and shall remain the exclusive property of the U.S. Government.

4.12.8 Disposition. Provide for the transition of data in commercially available, or open and non-proprietary format (and for permanent records, in accordance with disposition guidance issued by

National Archives and Record Administration). The Cloud service provider shall ensure that the

Government retains access and download capability of all Government data, and Government-related data, on demand within one week of request, in an open format (e.g., ASCII, CSV, XML). “Open format” means platform independent, machine readable, and made available to the public without restrictions that would impede the re-use of that information.

4.12.9 When a third-party may have access to, and use and disclosure of, Government data and

Government-related data: Provide appropriate limitations and requirements regarding Recipient, Project Level Performer and third-party access to, and use and disclosure of, Government data and

Government-related data.

4.12.10 Support applicable inspection, audit, investigation, or other similar authorized activities specific to the relevant types of Government data and Government-related data, or specific to the type of cloud computing services being acquired. Ensure the CSP is able to supply the agency with audit trails, exception reports and transaction logs, if requested.

4.12.11 Support and cooperate with applicable system-wide search and access capabilities for inspections, audits, and investigations.

4.12.12 Coordinate with the responsible official as provided by the AOTR to respond to any spillage occurring in connection with the cloud computing services being provided under this effort.

4.12.13 Store all Government data within the 50 states, the District of Columbia, or outlying areas of the United States, unless the Government data is physically located on DoW premises or the

Recipient, including Project Level Performer, is otherwise authorized in writing by the Agreement

Officer.

4.13 Security Risk Review – AFRLI 61-113

4.13.1 Recipient and PLP employees during the performance of this effort may be required to have access to Critical Technology Elements (CTE), Enabling technologies, Critical Program

Information (CPI) or other potential sensitive information. The Recipient and PLP employees will be required to protect this information from disclosure to unauthorized personnel and companies.

4.13.1.1 Provide a security plan to comply with the requirements of protection for this sensitive information when requested by the Government AOTR. (See ADRL, Security Plan)

4.13.1.2 Notify the Government immediately within 24 hours of all security incidents involving loss, compromise, or suspected compromise of CTE/CPI IAW DoDM 5200.01-V3, Enclosure 6.

CTE/CPI involved in the incident shall be specifically identified in inquiry and investigation reports.

4.13.1.3 Recipient and PLP Employees shall be required to accomplish an initial “Research and

Related Senior/Key Person Profile (Expanded)”. Provide an initial report of personnel working on the agreement and any resulting PLO’s at time of award. Provide an updated R&R Senior/Key

Person Profile Update on an annual basis and be required to provide an updated list anytime new personnel join. (See ADRL, R&R Annual Update)

4.13.1.4 If, at any time, during performance of this award, the Recipient and PLPs, learns that its

Senior/Key Research Personnel (including any sub awardee personnel who receives this designation) are or are believed to be participants in a Foreign Government Talent Program or have Foreign Components with a strategic competitor or country with a history of targeting U.S.

technology for unauthorized transfer, the Recipient will notify the Agreements Officer within 5 business days of awareness.

4.13.1.5 In the event a security risk is identified, and the government has determined the security risk exceeds the acceptable threshold, the Recipient will be notified and informed of the termination/decline of award. Government will be only required to provide a general statement of the reasoning due to government OPSEC measures.

4.13.1.6 Recipient will be required to flow down this provision to all PLP sub awardees who have personnel designated as Senior/Key Research Personnel as a result of their involvement in the performance of the research.

4.13.2 If Controlled Unclassified Information (CUI) and associated Critical Information is involved in this Agreement and any resulting PLO’s, CUI shall be protected to prevent adversary collection and exploitation. Comply with DoDI 5200.48 CUI.

4.13.2.1 If requested by the Government AOTR, provide a security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of the

Safeguarding Covered Defense Information Article listed in this Agreement and in accordance with National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations” in effect at the time the solicitation is issued or as authorized by the Agreement Officer, to describe the Recipient and PLP’s unclassified Information System(s)/network(s) where Covered Defense

Information (CDI) is associated with the execution and performance of this Agreement and is processed, is stored, or transmitted. (See ADRL Security Plan)

4.13.2.2 If applicable, ensure that all personnel involved in this Agreement and any resulting

PLO’s take CUI training through MyLearning https://lms-jets.cce.af.mil/moodle/ (if they have

CAC) or through CDSE at https://securityawareness.usalearning.gov/cui/index.html.

4.13.3 Operations Security (OPSEC). In accordance with AFI 10-701, implement OPSEC measures, which shall include ensuring employees receive training and follow appropriate OPSEC measures during the performance of the agreement. Implement OPSEC measures and must be an integral part of the daily activities.

4.13.3.1 If requested by the Government AOTR, develop and implement an OPSEC Standing

Operating Procedure (SOP) for review and approval by the Government (AOTR and AFRL/RIOF) in accordance with the ADRL. (See ADRL, Security Plan)

4.13.3.2 OPSEC Training: This program requires that the Recipient and Project Level Performer personnel maintain OPSEC posture through training for all agreement personnel involved in this effort. Ensure that employees complete Level I OPSEC training within thirty (30) calendar days of joining the project team. Employees must also complete annual OPSEC awareness training.

5.0 FUNDING

5.1 Applicable Funding Methods. Under this OTA, PLOs may be funded with any of the below appropriations, under the given conditions:

5.1.1 Research, Development, Test & Evaluation (RDT&E). A prototype good or service, including Commercial Off-the-Shelf (COTS) or Non-Developmental Items (NDI) subject to a non-recurring evaluation to determine military suitability, prior to required approval for acquisition or production, will be funded with RDT&E. A prototype considered operationally unsuitable for military purposes, and requiring design or development to bring the prototype into a suitable military configuration will also be funded with RDT&E.

5.1.2 Operational & Maintenance (O&M) and Procurement. Recurring operational test and evaluation (performed after required approval for procurement or production for the purpose of continuing performance acceptance) will be funded with O&M. Similarly, evaluation of items for operational, doctrinal, or organizational purposes will be funded with O&M (or procurement) subject to expense and investment criteria, including commercial or NDI where not subject to modification or testing for military utility.

5.1.2.1 Prototype support articles regularly procured to meet established general requirements

(e.g., operational training, operational use, or inventory) which are not consumed during testing will be funded with O&M or procurement, subject to expense and investment criteria.

5.1.3 Follow-on production efforts resulting from a PLO will be funded by the proper appropriation used for acquisition, either RDT&E, O&M, or procurement.