Supplemental Information_ Area of Interest 02 Emerging Engineering Services for Technical data.docx

Supplemental Information

This document provides supplemental information to support the Area of Interest 02 - Emerging Engineering Services for Technical Data. It is intended to be a reference document providing additional context on the problem statement and workshop outcomes. Please note that proposed solutions briefs should be based on the information provided in the Area of Interest document and should not request additional information or pose questions regarding the supplemental information.

The J68 Tech Accelerator facilitated a workshop on 18-19 December 2024 at DLA Defense Supply Center Richmond to bring together stakeholders focused on the initial problem statement and next steps to release the Area of Interest.

The initial problem statement the workshop centered on was:

DLA Aviation Engineering needs a way to develop Technical Data Packages (TDPs) for government use in order to enable competitive procurement for parts that are considered hard to procure and/or non-procurable.

The updated problem statement at the end of the workshop was:

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 in order to enable competitive procurement for parts that are considered hard to procure and/or non-procurable.

Key takeaways from the workshop included:

· The project focuses on the proposer creating tech data and providing tech data to DLA in which traditional manufacturing methods may be leveraged.

· The initial Prototype Other Transactions Authorities (OTA) will lead to building and validating a model for developing TDPs (i.e., manufacturing capability for enabling TDP creation).

Overview The workshop focused on prioritizing and drafting sections for an Area of Interest based on the problem statement. The session began with a welcome from DLA Director of Aviation Engineering, who provided context on the value of Technical Data Packages that can be used for competitive procurement and the acquisition of non-procurable items to mitigate contested logistics challenges and support demand surges during conflict by expanding DLA’s sources of supply.

This was followed by a brainstorming exercise to generate questions and assumptions for potential sections of the contracting structure (e.g., Background, Desired Solution Features, Project Expectations, Intellectual Property, Schedule, etc.).

The group voted to decide on the most impactful sections to focus their efforts on during the workshop and prioritized the following:

· Project Expectations (9 votes)

· Desired Solution Features (7 votes)

· Problem Statement (5 votes)

· Intellectual Property (3 votes)

From there, the team worked in cycles to iteratively build out what the sections should include or consider, adding more detail each cycle. Between the cycles, the group stepped back to generate a learning backlog: a list of critical questions that required expertise not in the room. This ensured that questions and concerns are addressed without halting the progress of the workshop.

Before finishing Day 1, the team brainstormed the tasks and next steps to be included in the Plan of Actions and Milestones (POAM), which they further developed on Day 2.

Day 2 began with addressing the learning backlog and conducting an Ask the Experts session with Air Force Supply Chain Consortium Initiative (SCCI) OTA PMs and stakeholders to incorporate potential lessons learned into the draft contracting structure for Aviation Engineering.

The team then revisited the contracting structure sections from Day 1 and summarized key points, especially focusing on the Desired Solution Features and Project Expectations sections.

Day 2 Desired Solution Features and Project Expectations key takeaways are listed below. Refer to the Appendix for additional details.

Desired Solution Features Key Takeaways

· DLA Aviation Engineering seeks innovative solutions for the development of approved Level 3 Product Level TDPs for identified NIINs and concurrence with all users.

· The TDP pathway may include review points where specific engineering and program management deliverables are assessed, and necessary coordination is conducted.

· ESAs engage in the TDP development process early on and provide qualification requirements as well as approval.

Project Expectations Key Takeaways

· DLA, ESA, and vendor stakeholders will maintain coordination throughout the project with DLA as the approval authority with ESA.

· Expected deliverables include ESA-approved milestone deliverables at each identified phase (e.g., manufacturing method, initial testing) with the end deliverable being a complete ESA-approved Level 3 TDP. The performance work statement (PWS) will provide the detailed task and deliverables. .

· The type will either be a 2-Dimensional Technical Data Package (2D TDP) or a 3-Dimensional Technical Data Package (3D TDP). The 2D TDP includes two-dimensional engineering drawings in accordance with ASME Y14.100 series standards.

· The solution will ideally result in the acquisition (though OTA, R&D, CSO) of 3D TPDs delivered as 3D native models, 2D drawings derived from the 3D native models, 3D Intelligent (3Di) portable document format (pdf) viewable data derived from the 3D native models or neutral files derived from the 3D native models.

· DLA has the right to maintain some control or access for the technical data involved. It is anticipated that the resulting rights to the TDPs are at least Government Purpose Rights (GPR) or specially negotiated license rights (SNLR) that includes competitive procurement.

Day 2 wrapped up with defining three stakeholder teams and beginning to map out actions on a timeline starting from Now (Dec 19, 2024 - Jan 3, 2025) through the following 12 weeks to the end of March 2025. The workshop concluded with closing remarks from the Aviation Engineering Director along with workshop participants who provided insights on the decisions made for the problem statement, desired solution features, project expectations, etc.

Acronym Definitions:

CS: Computer software, which is computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer data bases or computer software documentation.

CSO: Commercial Solutions Opening is a competitive process to obtain solutions or new capabilities that fulfill requirements, close capability gaps, or provide potential technological advances. Products and services acquiring using a CSO shall be treated as commercial products or services. or CSO purposes, innovation is defined as: any technology, process, or method, including research and development, that is new as of the date of proposal submission; any application of a technology, process, or method that is new as of proposal submission DLA: Defense Logistics Agency, the Department of Defense agency that is the customer of this contract. Various organizations within DLA will be supporting this effort.

ESA: Engineering Support Activities, the cognizant engineering authority that has the authority to determine source acceptability for a system or platform.

GPR: Government Purpose Rights, which is the rights to use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes.

IP: Intellectual Property, which refers 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. The IP deliverables that are required to be delivered or provided to the U.S. Government by contract include TDP and may include computer software.

OTA: Other Transaction Authority, which is a procurement authority that allows for flexible and innovative partnerships between the government, academia, and industry.

ROM: Rough Order of Magnitude, which is an estimate of the cost or scope of a project SNLR: Specially Negotiated License Rights, which is the rights to use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and other Government’s rights for release or disclosure that are negotiated between the vendor and Government.

TRL: Technology Readiness Level, which is a measure of the maturity and readiness of a technology for use in a particular application. Additional guidance on technology readiness, https://www.cto.mil/wp-content/uploads/2023/07/TRA-Guide-Jun2023.pdf.

TDP: Technical Data Package, which is recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data financial, administrative, cost or pricing, or management information, or information incidental to contract administration.

J68 Tech Accelerator

image1.png