DevX Annoucement_W911NF-26-S-0040.pdf

ARMY APPLICATIONS LAB

OPEN CALL SOLICITATION FOR

INNOVATIVE AUS SOLUTIONS

W911NF-26-S-0040

30 December 2025 – 31 August 2026

ISSUED BY:

U.S. Army Contracting Command Aberdeen Proving Ground

Research Triangle Park Division P.O. Box 12211

Research Triangle Park, NC 27709-211

TABLE OF CONTENTS

I. Introducing DevX Autonomy 3 II. What is DevX Autonomy? 3 III. What are the goals of DevX Autonomy? 3 IV. Who can participate in DevX Autonomy? 3 V. Why Participate in DevX Autonomy? 3 VI. DevX Autonomy Focus Areas 4 VII. Submission Instructions 4 VIII. DevX Autonomy Assessment Process 8 IX. Resubmissions 8 X. Reserved 9 XI. Important Information for Participants and Prospective Participants 9 XII. Handling / Licenses Granted 9 APPENDIX A: Technology Readiness Level Descriptions 11 APPENDIX B: Assessment Criteria and Ratings 12

I. Introducing DevX Autonomy Transformation and Training Command (T2COM) and Army Applications Laboratory (AAL) are initiating this long-term, open call solicitation for technology solutions to advance research, development, testing, procurement, and sustainment of autonomy and unmanned systems-related hardware and software solutions. This announcement is being solicited in accordance with DFARS 212.70 and DFARS 235.016. Specifically, AAL seeks to obtain solutions or potential capabilities that fulfill requirements, close capability gaps, or otherwise advance the state of the art in autonomy and unmanned systems. This initiative, entitled “DevX Autonomy,” will solicit, collect, assess, and curate Autonomous Unmanned System (AUS) solutions and make those solutions available through rapid acquisition pathways.

II. What is DevX Autonomy?

DevX Autonomy is a digital environment of award-ready video demonstration/pitches submitted to the Army Application Laboratory Open Call for Innovate AUS Solutions solicitation. The solution videos housed within DevX Autonomy have been assessed through competitive procedures that conform to the competition requirements of 10 USC 4021, 10 USC 4022, 10 USC 3458, FAR Part 35, DFARS Part 235, DFARS Subpart 212.70, and DFARS 206.102-70, and are thus readily available to be viewed, selected, negotiated, and awarded by the U.S. Government, without further competition. For industry, academia, and individual developers, DevX Autonomy is a valuable tool to promote AUS products and services to the Government in an environment with multiple rapid acquisition contracting pathways.

III. What are the goals of DevX Autonomy?

The goals of DevX Autonomy are to establish a centralized location where the Government can assess the state of the art in available AUS solutions, and where industry, academia, and individual developers can promote their research, technologies, and related products and services to the Government. Further, the structure of the publication and assessment functions of DevX Autonomy allow for streamlined procurement of available autonomy solutions for the Government. Finally, by leveraging the statutory and regulatory authorities available, DevX Autonomy provides a technology transition pathway from idea to research, research to prototype, prototype to test and evaluation, through production, fielding, and sustainment of a given solution.

IV. Who can participate in DevX Autonomy?

U.S.-based companies, traditional and nontraditional defense contractors, large and small businesses, universities, non-profit companies, non-profit research institutions, and individuals are welcome to participate. In addition, foreign universities, research institutions, and entities may submit video demonstrations/pitches for their related solutions provided that such submissions are compliant with international law, including export laws for both the country of origin of the technology provider and the United States.

V. Why Participate in DevX Autonomy?

DevX Autonomy is the premier entry point for industry, academia, and individuals to propose technology solutions, service solutions, ongoing research efforts, and future development activities that are relevant to the U.S. Government.

DevX Autonomy allows the Government to quickly identify award-ready solutions to solve autonomy challenges.

Participating entities will have their proposed solutions assessed by Government Subject Matter Experts (SMEs) and will receive feedback on the technical merit of their solution (see Appendix B for assessment criteria). Further, by submitting against this open call for solutions, all submitted solutions that are deemed award-ready by the Government Selecting Official (GSO) will have met competition requirements under 10 USC 4021, 10 USC 4022, 10 USC 3458, FAR Part 35, DFARS Part 235, DFARS Subpart 212.70, and DFARS 206.102-70, and will be eligible for future awards without further competition. Benefits of DevX Autonomy include:

• Visibility of technology and service solutions to relevant government stakeholders.

• Simplified submission process that requires minimal organizational and technical information.

• Submission assessed with feedback.

• Negotiable award terms.

• Opportunity for multiple awards per submission.

VI. DevX Autonomy Focus Areas Army Applications Laboratory is seeking video pitches for innovative AUS related solutions and research efforts relevant to one or more of the focus areas below. These focus areas may evolve as the Army’s needs change. For each focus area, development work may include, but is not limited to, decreasing cognitive load, reducing human demand in operations, providing dynamic control, assuring cybersecurity, decreasing network reliance, increasing repairability, and/or overcoming limitations in size, weight, power, and cost (SWaP-C). Solutions should have an open architecture modular open systems approach (MOSA), and be supportable, scalable, and repairable.

• Platforms. Development or improvement of autonomous platforms that operate in the air, ground, and maritime domains.

• Payloads. Development of hardware and/or software that provide mission-specific autonomous capabilities.

Examples include sensors, effectors, communication devices, or other specialized tools.

• Mission-Enabling Solutions. Development of hardware and/or software that enable autonomous systems to operate cohesively with humans and other systems, interpret mission objectives, and generate plans that can be adjusted dynamically based on changes in the environment or mission priorities.

• Lethal Capabilities. Development of autonomous solutions aimed at enhancing the lethal capabilities of existing platforms and introducing new capabilities for current or future platforms. This includes improvements to existing lethal effects and the delivery of novel effects across domains such as explosives, kinetic systems, safety mechanisms, fusing technologies, guidance systems, and other critical components.

• Sustainment Solutions. Development of hardware and/or software that enhances the use of autonomous systems, including solutions for charging, fueling, deploying, and recovering autonomous systems, and maintenance solutions that automate diagnostics, plan maintenance, or enable rapid repair.

• Subcomponents. Development of subcomponents such as motors, sensors, or controllers that enable or improve capabilities of autonomous systems.

• Other Disruptive Autonomy Solutions: Development of hardware and/or software that markedly modifies, improves, or disrupts currently known autonomous technologies and capabilities.

VII. Submission Instructions

a. Submission, Assessment, and Notification Deadlines

i. DevX Autonomy is continuously open for submission of solutions during the period of this

Open Call (December 30, 2025 – July 31, 2026).

ii. Submissions are collected monthly, unless otherwise noted (e.g., June 1st through June 30th).

This is referred to as the “monthly collection period.”

iii. The cutoff for submissions is the final day of each monthly collection period at 12:00 (Noon)

Eastern Standard Time (EST). Submissions received after 12:00 (Noon) EST on the final day of each monthly collection period will be considered submitted in the subsequent monthly collection period.

iv. Compliant submissions (see sec. VIII for compliance (responsiveness) information) received during a given month (the monthly collection period) will be assessed in the following month with results available within 30 days of the end of the relevant collection period (e.g., for collection period ending June 30th 12:00 (Noon) EST, assessment results will be distributed no later than July 30th (subject to flexibility for instances of high volume).

b. Submission Eligibility. Solution videos and form information must be unclassified, and not include any proprietary information, export-controlled information, or controlled unclassified information (CUI).

Solution videos must not contain any restrictive markings other than a valid copyright notice. Each video submission shall provide a single hardware, software, or service solution. Each solution video submission must be accompanied by a fully completed submission form (automated form populated during the video submission process). Elements of the required submission form include:

i. Submitting Entity Name (or Individual Name). Use your full legal company/organization/individual name. It should match your SAM.gov profile if you have an existing SAM.gov profile at time of video submission.

ii. Website (if available). Identify your current website address.

iii. Unique Entity ID (UEI) (if available). The Unique Entity ID (UEI) is a 12-character alphanumeric ID assigned to an entity by SAM.gov, and is required to be eligible for any type of award. If you do not have a SAM.gov profile at time of video submission, leave this field blank.

iv. Business Size. Identify either large or small business size. Business size is defined by the Small Business Administration (SBA) in accordance with 13 CFR Part 121 Small Business Size Regulations. This classification is based upon average annual receipts or the average number of employees. The definition of “small” varies by industry, which is classified by the North American Industry Classification System (NAICS) code relevant to the solution submitted.

v. Traditional/Non-Traditional Defense Contractors Characterization. Definition: As defined in 10 USC 3014, "nontraditional defense contractor", with respect to a procurement or with respect to a transaction authorized under section 4021(a) or 4022 of this title, means an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of War for the procurement or transaction, any contract or subcontract for the Department of War that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.

vi. Small Business Program Designation(s) (if applicable). Select all applicable small business program designations your entity currently holds. This designation must match your SAM.gov account.

vii. Country. Select the appropriate country for your entity.

viii. Address. Location of principal place of business (Street Address, City, State, ZIP)

ix. DevX Focus Area. The purpose of the focus areas is to collect solutions which are relevant to AAL and its customers. Often, a given solution may fit within multiple focus areas. The focus area selected for your solution has no impact on the assessment of your solution. The focus areas are used to filter searches within DevX Autonomy for award-ready video solutions. If you are in doubt as to the proper fit for your technology or believe it spans multiple focus areas, select the “Other Disruptive Autonomy Solutions” category.

x. Technology Readiness Level (TRL). Select the current TRL of your solution. A description of the TRL definitions is available in Appendix A of this document as well as in a tooltip during the submission workflow process. Assure that you select the appropriate level for the current maturity of your solution at time of submission. The purpose of including the TRL as part of the submission requirements is to help customer organizations understand what types of efforts and funding your company is seeking for future engagements (research, development, prototyping, test and evaluation, production, or sustainment). The TRL is not used to determine whether solutions are assessed as award-ready or not. It is important to select the relevant TRL for your solution to align with the proper potential customer organizations and funding.

xi. Include at least five relevant keywords that describe your solution. These will help government stakeholders locate it more efficiently. Separate each keyword with a comma.

xii. Video submission point of contact and alternate (POC), email address, and phone number.

These are the POCs that will receive the assessment results and any inquiries about the submission.

xiii. Submission Title (max 128 characters).

xiv. Abstract (max 1,500 Characters). Use this section to describe your video solution. It will appear in DevX Autonomy for the Government user to easily understand your solution prior to watching the video. The purpose of this narrative is to support potential future customers in understanding information about your firm. Use this space to identify information that a prospective customer may want to know (e.g., certifications, approved accounting system, GSA schedules, existing contracts, etc).

xv. Submission Type. Under this section, submitting entities must select the appropriate submission type from the available list. Submissions are categorized into one of two available submission type categories:

1. New DevX Autonomy Submission – This submission category is appropriate for first time video submissions, as well as submissions that have previously failed a compliance check which has been corrected. The New DevX Autonomy Submission category is not appropriate for solutions which have been assessed as non-awardable.

2. DevX Autonomy Resubmission – This submission category is appropriate for those solutions that have previously been submitted as a New DevX Autonomy Submission, completed the peer assessment process, and were deemed non-awardable. (See section IX for more information on DevX Autonomy Resubmissions).

xvi. Security and Authorization Status. Select the appropriate response for each field to indicate your current Facility Clearance Status (FCL); Foreign Ownership, Control, or Influence (FOCI); Authority(ies) to Operate (ATO); Impact Level (IL); and Federal Risk and Authorization Management Program (FedRAMP) status. These responses are not part of the assessment process. These responses are intended to inform future prospective customers of your firm’s security and cybersecurity status if your solution is assessed as award-ready and placed into DevX Autonomy.

c. Video Submission Format Requirements. Solution video submissions shall conform with the following format requirements or will be deemed noncompliant and returned for revision:

i. Videos must be no longer than six minutes (6:00) in length.

ii. Minimum video production requirements:

1. Resolution: HD 1920x1080.

2. Encoded for streaming as a .mp4 file under 1.0gb.

3. Color Space: Rec709 or sRGB.

iii. Videos shall contain no restrictive markings limiting their use or distribution other than a valid copyright notice. Video submissions that contain restrictive markings other than those expressly permitted herein will not be assessed. Submitters will be notified that their video submission contains unauthorized restrictive markings and must be revised.

d. Video Submission Content Requirements. There are four required elements that each video must address, in increasing order of importance: (1) Defining the Problem; (2) Company and Key Personnel Qualifications; (3) Technical Merit; and (4) Technical Approach and Agency Alignment. Instructions for addressing the required video content requirements are as follows:

i. Defining the Problem. Begin your video pitch with a clear description of the problem(s) you solve for your customers (or prospective customers). Explain the problem thoroughly but leave time to address all video submission elements. Is this a common problem across the Government? Is it a universal problem across Government and commercial markets? Is it specific to a program, platform, or service, or does it have impacts across the DoW? Even if your existing use cases are at a smaller scale, focus on explaining the broader applicability and potential impact of your solution.

ii. Company and Key Personnel Qualifications. Qualifications of the proposed Principal Investigators/Project Managers, supporting staff, and consultants. Describe how your company’s business model works. The way your business model is explained will be dependent on the structure of your business. NOTE: THIS SECTION IS NOT REQUESTING NON-

PUBLIC PRICING. DO NOT SUBMIT RATES OR OTHER PROPRIETARY PRICING

INFORMATION. Items to consider for your submission include:

1. Outline the qualifications of those that will be involved with the proposed effort.

2. Explain the general structure. For example, do you offer fixed-price licenses, fixed-price services, time and materials services, etc.? Is your business model variable based on volume, complexity, or other factors? Do you offer range pricing or quantity discounts? Are you seeking funding for development work? If your business model includes variable components, describe how you estimate the scope of work to determine contract pricing.

3. If your solution is a commercial product, indicate whether the same business model is used for both commercial and Government buyers. Where possible, provide evidence that your model is viable in either or both commercial and Government markets.

4. Assure that your business model aligns with the current maturity (TRL) of your technology or service solution.

5. If you have publicly available commercial pricing, include that here.

iii. Technical Merit. Each video must focus on one solution, though it may relate to multiple focus areas (you may submit additional videos to present other solutions). Fully describe your solution and the technical scientific reasoning behind how it addresses the identified problem. Use relevant, properly cited data to strengthen your argument and establish credibility. Identify how your solution addresses the problem you’ve defined. If other technologies (such as hardware, software, licenses, or services) are required to use your solution, identify such dependencies and how technical risk and/or dependencies are managed. Identify how your solution aligns to the DevX Autonomy Focus Area(s). If your solution is at a lower Technology Readiness Level (TRLs 1-5) and needs further development or test, explain your plan to mature the solution to better address the problem. If your solution is at a higher Technology Readiness Level (TRLs 6-9), provide a demonstration within your video of the product or case study of your service.

Forgot what TRLs are? Check Appendix A.

iv. Technical Approach and Agency Alignment. Explain how adoption of your solution would impact the current state of technology/services used by the DoW. In what ways does your proposed solution introduce innovations or advanced research efforts that significantly enhance the DoW’s capabilities? If you are already providing your solution to DoW or other Federal Agencies, state that here and explain the impact it has had. Identify current customers using your solution including Government and commercial entities. Is your solution saving your customers time? Saving money? Reducing risk? These are just some examples of potential customer impacts. Identify and discuss alternatives to solving the identified problem, and why they are less desirable. Provide information to support assertions and/or claims made. Explain how your proposed solution aligns with the following Army objectives: open architecture1, supportable2, scalable3, and repairable4, or identify a pathway/plan to become open, supportable, scalable, and repairable.

1 Open Architecture. An open architecture is a technical architecture that adopts open standards supporting a modular, loosely coupled and highly cohesive system structure that includes publishing of key interfaces within the system and full design disclosure.

2 Supportable. Support functions required to field and maintain the readiness and operational capability of covered autonomy and unmanned systems, subsystems, and components, including all functions related to covered system readiness.

3 Scalable. The ability of a piece of hardware and/or software to easily expand to meet future government needs.

4 Repairable. An item of a durable nature that has been determined by the application of engineering, economic, and other factors to be the type of item feasible for restoration to a serviceable condition through regular repair procedures.

e. Where to Submit a Video Solution. All solutions must be submitted through https://aal.mil/devx-autonomy. No hard copy or physical submissions (CD/DVD/Blu-Ray) will be accepted.

DevX Autonomy Compliance Check and Notification Process The DevX Autonomy internal execution team strives to provide compliance (responsiveness) checks in a timely manner (within approximately one (1) business day from submission date) to allow submitting companies the opportunity to revise their videos if deemed non-compliant. The scope of review of the compliance check is as follows:

1. Review that the video submission is no longer than 6:00 minutes in length.

2. Review that the video can be viewed and is audible.

3. Review that any graphics/charts displayed within the video are legible.

4. Review that the video does not contain any prohibited markings.

5. Review that the video conforms to the resolution, file type, and color space requirements.

6. Review that the video contains all required submission content as detailed in Section VII of this DevX Autonomy announcement.

7. Review the submission form data for completeness and accuracy.

8. Review accuracy of business size and traditional/nontraditional characterization using SAM.gov (where applicable).

9. Review that the effort fits within one of the DevX Autonomy focus areas.

Upon completion of the compliance (responsiveness) review, those solutions which conform to the requirements of Section VII of this announcement will be placed into the queue for the next scheduled assessment. Those solutions which contain one or more deficiencies will be notified via email and asked to correct the deficiency and complete a new submission. Submissions on the final day of any monthly collection period may not receive notice of any noncompliance prior to closing of the monthly collection, so solution providers are urged not to wait until the final day of the collection period to submit solutions.

VIII. DevX Autonomy Assessment Process Solution videos submitted against this open call will be assessed in accordance with the assessment criteria and ratings included as Appendix B and rated as award-ready or not for the given assessment round. Solutions are assessed by a peer panel of Government Subject Matter Experts, with final decisions made by the Government Selecting Official (GSO). By submitting a video solution, you authorize the video to be distributed and used for this purpose. In conformance with statutory and regulatory requirements for the authorities leveraged by DevX Autonomy (10 USC 4021, 10 USC 4022, 10 USC 3458, FAR part 35 and DFARS Part 235, DFARS Subpart 212.70, and DFARS 206.102- 70), the Government will develop a written assessment of each submission applying the established assessment criteria, and ratings, which is included at Appendix B of this document. Relative importance of evaluation factors are Technical Merit, Technical Approach and Alignment which are equal importance to each other and are greater importance than Company and Key Personnel Qualifications, and Defining the Problem which are of equal importance to each other. Determination of fair and reasonable pricing will be established during negotiation and prior award. The recommended ratings, and comments for each video solution are presented monthly by the Peer Panel as recommendations to the designated Government Selecting Official (GSO). The GSO is ultimately responsible for determining a solution’s award-ready characterization for the rating period.

Artificial Intelligence (AI) tools may be used to support administrative tasks during the evaluation process, such as document organization, summarization, or data sorting. AI will not independently determine evaluation ratings, make award-ready recommendations, or replace evaluator judgement. AI will assist, but not replace, GSO judgment. All evaluation findings, ratings, and source selection decision will be made exclusively by the Peer Panel and GSO personnel in accordance with the solicitation and applicable regulations.

https://aal.mil/devx-autonomy

IX. Resubmissions DevX Autonomy accepts resubmissions of solutions previously deemed as non-awardable at any time while the DevX Autonomy Announcement remains active. To improve chances of being deemed award-ready, it is recommended that submitting entities carefully review ratings and assessor comments/suggestions, which are delivered at the conclusion of each monthly assessment. Additionally, the DevX Autonomy Manager provides weekly feedback sessions where submitting entities can review assessor comments from a prior unsuccessful solution video during DevX Autonomy office hours. The purpose of feedback sessions (which are available weekly) is to develop a strategy to address weaknesses identified through the assessment process and prepare a resubmission with a higher likelihood of being assessed as award-ready. It is highly recommended that solution providers participate in feedback sessions to maximize the potential for a successful resubmission. Information on these office hours can be found at https://outlook.office365.us/book/DevXAutonomyOfficeHours@theari.us/?ismsaljsauthenabled=true

A solution provider may resubmit a previously deemed non-awardable solution in any subsequent collection period, and may continue to resubmit, if unsuccessful, in multiple collection periods while the DevX Autonomy Announcement remains active. When submitting a solution as a resubmission, it is important to identify that the submission is a resubmission. Within the solution submission workflow, select “DevX Autonomy Resubmission” under the field labeled “Submission Type”. Please note that solutions which have been determined “non-compliant” and returned for some technical deficiency (over 6:00 minutes in length; improper markings; missing content; etc) remain a “New DevX Autonomy Submission” when corrected and submitted. “DevX Autonomy Resubmissions” are only those solutions that undergo a peer assessment and are deemed a non-awardable.

X. Reserved

XI. Important Information for Participants and Prospective Participants All costs of preparing and submitting solution videos and submission forms are the responsibility of the submitting entity and not eligible for funding or reimbursement by the Government.

Assessment as award-ready and placement into DevX Autonomy does not guarantee any current or future award.

Solution providers may submit one or multiple video submissions while this announcement remains open.

Ratings and assessor comments will be provided for both award-ready and non-awardable submissions at the end of each assessment round. All submitting entities can request a feedback session to review the ratings and comments related to their solution by reserving a time slot during office hours at.

https://outlook.office365.us/book/DevXAutonomyOfficeHours@theari.us/?ismsaljsauthenabled=true

Feedback Sessions are conducted by the DevX Autonomy Manager and are intended to assist solution providers in addressing weaknesses identified in the assessor ratings and comments for the purpose of revising any non-awardable solutions, and resubmitting to a subsequent collection period. Any dispute regarding final ratings may be addressed to the Government Selecting Official (GSO). DevX Autonomy does not provide names, contact information, or any other personal information of the SME assessors themselves.

Any questions related to this announcement or related DevX Autonomy matter may be sent to devx-help@aal.army.

More information related to DevX Autonomy can be found at: https://aal.mil/devx-autonomy.

XII. Data Handling / Licenses Granted https://outlook.office365.us/book/DevXAutonomyOfficeHours@theari.us/?ismsaljsauthenabled=true https://outlook.office365.us/book/DevXAutonomyOfficeHours@theari.us/?ismsaljsauthenabled=true mailto:devx-help@aal.army

a. Solutions videos placed within DevX Autonomy are viewable by all Federal Government accounts (.mil / .gov) and by the submitting entity or individual. The submitting entity/individual remains the owner of the video and the associated submission data and may request the video and associated submission data be removed from DevX Autonomy at any time. By participating in the DevX Autonomy initiative, each submitting entity grants the following Government-wide, non-exclusive, fully paid up, non-assignable, non-royalty bearing licenses in both the video solution submission and the accompanying submission data:

i. A license for the Government to view, review, research, comment, and share the video solutions and associated submission data within the Government and to covered Government support contractors for the purposes of performing assessments of the solution; performing market research; supporting requirements development; considering/planning for procurement;

negotiating for award; and making an award of the solution at any time while the video solution and associated submission data remain active within DevX Autonomy.

ii. A license for the Government to view, review, research, and share the video solution and associated submission data within the Government and to covered Government support contractors, whether assessed as ready for award, for the purposes of improving/revising the submission, assessment, and/or selection processes, submission criteria, assessment criteria and ratings, or user interface/user experience, in perpetuity.

iii. A license for the Government and its covered Government support contractors to transcribe the video for the purposes of improving the search functionality of DevX Autonomy, to address accessibility requirements, to support marketing of the solution for potential award, to support Government reporting, performing market research, and supporting requirements development.

The entity/individual grants and the Government retain a perpetual license in the transcription data itself for the purpose identified within this paragraph.

iv. A license for the Government and its covered Government support contractors to use the video solutions and associated submission data for Government training purposes including training in the planning, implementation, execution, and administration of the DevX Autonomy model, processes, assessment criteria and ratings, research, conducting feedback sessions, award of solutions, and other such related Government training.

APPENDIX A

Technology Readiness Level Descriptions

Level Definition DoW Defense Acquisition Guidebook (DAG) Description

1 Basic principles observed and reported. Lowest level of technology readiness. Scientific research begins to be translated into applied research and development.

Examples might include paper studies of a technology’s basic properties.

2 Technology concept and/or application formulated.

Invention begins. Once basic principles are observed, practical applications can be invented. Applications are speculative and there may be no proof or detailed analysis to support the assumptions. Examples are limited to analytic studies.

3 Analytical and experimental critical function and/or characteristic proof of concept.

Active research and development is initiated. This includes analytical studies and laboratory studies to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative.

4 Component and/or breadboard validation in laboratory environment.

Basic technological components are integrated to establish that they will work together. This is relatively “low fidelity” compared to the eventual system. Examples include integration of “ad-hoc” hardware in the laboratory.

5 Component and/or breadboard validation in relevant environment.

Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so it can be tested in a simulated environment.

6 System/subsystem model or prototype demonstration in a relevant environment.

Representative model or prototype system, which is well beyond that of TRL 5, is tested in a relevant environment.

Represents a major step up in a technology’s demonstrated readiness.

7 System prototype demonstration in an operational environment.

Prototype near, or at, planned operational system. Represents a major step up from TRL 6, requiring demonstration of an actual system prototype in an operational environment such as an aircraft, vehicle or space.

8 Actual system completed and qualified through test and demonstration.

Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications.

9 Actual system proven through successful mission operations.

Actual application of the technology is in its final form and under mission conditions, such as those encountered in operational test and evaluation. Examples include using the system under operational mission conditions.

APPENDIX B

Assessment Criteria and Ratings