Area of Interest 03 Emerging Engineering Services for Technical data.docx
DOCX document 22 KB Posted
- Attached to
- DLA Commercial Solutions Opening (CSO) FY2026
- Solicitation number
- SP4701-24-S-C001
- Issued by
-
Defense Logistics Agency
About this file
This document is an Area of Interest (AOI) attachment for a DLA Commercial Solutions Opening (CSO) solicitation focused on emerging engineering services for technical data. DLA Aviation Engineering seeks a contractor to develop Engineering Support Activities (ESA) approvable Level 3 Technical Data Packages (TDPs) for hard-to-procure or non-procurable parts when existing item data is unavailable or obsolete. The desired solution involves creating a proof-of-concept model for obtaining information and developing TDPs for three items of varying complexity (easy, moderate, and complex), with an initial project timeline of 16-26 weeks from award.
Key project expectations include developing innovative tools and methodologies for reverse engineering, building partnerships across the defense industrial base, mitigating supply chain vulnerabilities, and establishing a comprehensive framework for intellectual property rights. The solution should be at approximately Technology Readiness Level 6 or above, with a preference for technologies already piloted in commercial or federal settings. Solution briefs are due by April 15, 2025, at 5:00 PM EDT, to be submitted via email to Thomas Walsh. The government is seeking a solution that can rapidly develop technical data packages to support competitive procurement and enhance logistics capabilities for military supply chains.
View the file
Other files
Show all 17
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT 1: SOLICITATION TOPICS AREAS/AREAS OF INTEREST
1.0 Problem Statement
DLA Aviation Engineering needs a way to develop Engineering Support Activities (ESA) approvable level 3 TDPs per MIL-STD-31000 and ASME Y14.100 for government use when item data is not available, obsolete and/or there is no DLA stock on hand in order to enable competitive procurement for parts that are considered hard to procure and/or non-procurable.
2.0 Background
As the nation’s logistics combat support agency, the Defense Logistics Agency (DLA) manages the end-to-end global defense supply chain – from raw material to end user disposition – for the five military services, 11 combatant commands, other federal, state and local agencies, and partner and allied nations.
DLA’s mission is to “deliver readiness and lethality to the Warfighter Always and support our nation through quality, proactive global logistics.” To accomplish this mission, DLA has a staff of about 25,000 employees divided into multiple supply chains that contract for materiel and services across the military classes of supply: subsistence (food/water), clothing and textiles, bulk petroleum and other energy products, construction materiel and equipment, personal demand items, medical materiel and equipment, and repair parts for land, sea and air systems. (Defense Logistics Agency, 2024) DLA Aviation engineering provides program management and technical expertise for engineering programs for the Aviation Supply Chain (ASC). DLA Aviation engineering mission is to improve the quality and lead time of DLA Aviation’s Products/Services through source development, product improvement, reverse engineering, organic manufacturing, sustainment and reliability initiatives and other technical services. DLA Aviation Engineering is seeking to address a capability gap in the development of technical data for items where existing data is unavailable, obsolete, or where DLA stock is not currently available. As a result, the submission should address risk to mitigate contested logistics challenges and support demand surges during conflict. Submissions should describe unique aspects of your solutions that fill capability needs as it related to the problem statement. The level of detail provided for each desired solution feature or the order in which they appear is not intended to convey any information regarding relative priority.
3.0 Desired Solution Features
3.1 In support of completing ESA approvable Level 3 TDPs when item data is not available, obsolete and/or there is no DLA stock on hand. Develop a proof-of-concept model for obtaining information and/or items needed for developing, coordinating and approving Technical Data Packages (TDPs), (i.e., manufacturing capability for enabling TDP creation) when existing engineering pathways are counterproductive. Specifically, how the data and/or items will be sourced to support 3.2.
| 3.2 | Develop ESA approvable Level 3 TDPs for 3 items. For estimating purposes, please anticipate 1 easy, 1 moderate, and 1 complex item. Complexity presumably would be number of measurable features on the item. Without an item to determine complexity from, the following measurable features per complexity level can be used for estimate purposes: | ||
| 3.2.1 | Easy – 10 measurable features | ||
| 3.2.2 | Moderate – 50 measurable features | ||
| 3.2.3 | Complex – 100 measurable features |
4.0 Project Expectations
| 4.1 | Provide an initial proof-of-concept to rapidly develop and demonstrate a process to develop and deliver technical data for jointly selected candidate parts for specific weapon systems 16-26 weeks from award. |
| 4.2 | Create and develop innovative tools, methodologies, and qualification frameworks that accelerate future efforts when item data is not available, obsolete and/or there is no DLA stock on hand to support a reverse engineering effort. |
| 4.3 | There is no specific Technology Readiness Level (TRL) requirement; however, proposed solutions should be approximately TRL 6 and above to enable assessment of the technical feasibility, responsiveness, viability, and desirability of the proposed solution and support a rapid transition into operation. We're seeking solutions that are developed and proven enough to be quickly adaptable for use in real-world situations. Ideally, your technology has already been successfully piloted or deployed in a commercial or federal setting. This will allow us to effectively evaluate its potential for national security applications and ensure a smooth transition into active use. |
| 4.4 | Build and strengthen partnerships (traditional or non-traditional contractors) across the global defense industrial base and increase alignment with ESAs. Engage innovative non-traditional suppliers that do not work with the government. |
| 4.5 | Assess and shape the risk: identify and mitigate supply chain vulnerabilities within the global Defense Industrial Base. |
| 4.6 | Collaborative workshop participation. Participate in a shared development space with other vendors, operators and government developers to rapidly iterate on solutions. Solutions providers may be asked to collaborate and/or participate in cross functional efforts that may exist under previously established contractual vehicles. |
| 4.7 | Clear and comprehensive framework for obtaining and managing intellectual property (IP) rights for the technical data packages, with a focus on government purpose rights. This is necessary to ensure that the government has the rights to use, modify, and distribute the technical data packages for government purposes, including procurement and sustainment activities while also ensuring that the rights of IP owners are respected and protected |
5.0 Intellectual Property
At a minimum, DLA anticipates acquiring Intellectual Property:
5.1 Identify and describe any technical rights, including intellectual property rights, that are part of the proposed solution. This includes, but is not limited to, information, products, or services that are protected by law as intangible property, including data (e.g., technical data and computer software), technical know-how, inventions, creative works of expression, and trade names. Minimum Rights in Technical Data and Computer Software including marking requirements will be outlined in the resultant Performance Work Statement.
| 5.2 | Technical data for the solution: |
| 5.2.1 | Necessary for operation, maintenance, or training; |
| 5.2.2 | That describes the required overall physical, functional, and performance characteristics (along with the qualification requirements, if applicable) of an item, component, or process to the extent necessary to permit identification of physically and functionally interchangeable items. This is often called ‘form, fit, and function’ data (see 48 C.F.R. § 252.227-7015(a)(3)); and |
| 5.2.3 | The primary purpose of the resulting procurement is to develop Engineering Support Activities (ESA) approvable level 3 TDPs per MIL-STD-31000 and ASME Y14.100 for government use in order to enable release to the public for competitive procurement of parts that are considered hard to procure and/or non-procurable. |
| 5.2.4 | The IP rights are fully negotiable; however, the project goal is to develop TDPs for competitive procurement, which includes Government Purpose Rights, Specially Negotiated License Rights, and Unlimited Rights for the U.S. Government partner. |
6.0 Foreign Ownership and Control; Foreign Access to Technology
| 6.1 | The Responder shall provide details of any foreign ownership or control that may exist within their corporate structure. |
| 6.2 | The Responder shall have the ability to create and store export-controlled data in accordance with export control regulations. |
7.0 Rough Order of Magnitude (ROM)
Proposer solution brief must provide a ROM with an estimated total cost for each desired solution feature in section 3 above. To ensure alignment with our budget, please provide a ROM cost breakdown for your proposed solution using the template below. We are particularly interested in understanding the cost drivers within each workstream/phase and require the ability for scope adjustments to meet our budgetary needs.
| Desired Solution Features |
| Estimated Total Cost |
| Expected Timeline |
| 3.1 – |
| $ |
| days |
| 3.2 – |
| $ |
| days |
| TOTAL |
| $ |
| Weeks + days |
8.0 Submission Instructions
Solutions Briefs are due no later than April 15, 2025, at 5:00PM EDT. Please submit the Solution Briefs via email to Thomas Walsh Thomas.Walsh@dla.mil.
File details come from the government source that posted it. Updated .