Attachment 21 Technology Transition Plan Guidance.pdf

Navy ManTech Program

REV P OCT24

Technology Transition Plan (TTP) Guidance

Attachment:

1. Navy ManTech Technology Transition Plan Template

A. PURPOSE

As part of each Navy ManTech project, the Center of Excellence (COE) or the lead COE for joint projects coordinates with the relevant Navy and industry representatives to identify all the requirements that will ensure transition and implementation of the successfully completed project. For Navy ManTech purposes, the following definitions are used:

Transition: Point when the technology meets customer (Program Office / industry) criteria for implementation and the technology has been transferred to the industrial / naval organic facility.

Implementation: Actual use of the ManTech results for the manufacture or repair of a platform / weapon system.

The intent of the Technology Transition Plan (TTP) is to clearly and concisely document what ManTech will complete with ManTech funds and specify where and when the results of the ManTech project will be used. ManTech cannot ensure implementation alone, but a well-defined TTP will assist the acquisition Program Office, the Program Executive Office (PEO), and, if appropriate, industrial / naval organic facility management in the transition and resourcing to achieve implementation. The TTP specifies the Navy need for the technology developed by the project, the specific event that will signify ManTech transition, the criteria that the project must meet for transition, the requirements for implementation, and the schedule.

B. REQUIRED TIMELINE

New projects: COEs are required to submit an unsigned draft TTP as an addendum to the technical proposal / project plan for all new ManTech projects,. A TTP, signed by the cognizant parties, is required to be submitted to the Program Officer (PO) / Contracting Officer’s Representative (COR) as specified in the COE contract or within 90 days of project start.

Active projects: COEs are required to review the TTP for all active projects annually on 31 Jul. Revisions to the TTP are required if changes in implementation factors, such as requirements, approvals, schedule, or project scope occur. Note: New projects initiated in the preceding six-month timeframe (Jan-to-Jun) are not subject to the annual review.

TTPs are not required for Rapid Response, Repair Technology Rapid Response, and 6.2 Manufacturing Applied Research standalone projects. Other special cases, such as Capability Acceleration and feasibility studies, may warrant waiving the requirement for a TTP. In all cases, confirmation that the plan is not required must be agreed to in writing by the PO / COR.

Confirmation that the TTP was waived by the PO / COR must also be emailed to the Navy ManTech Support Team.

C. PROCESS / APPROVAL CYCLE

COEs are responsible for coordinating with the Navy and industry entities who will be involved in the implementation of the manufacturing technology to develop a TTP. In particular, communication should be conducted among the COE, the Technical Assistant (TA), the Program Office / PEO representative of the platform / weapon system and/or the industrial / naval organic facility management representative, the prime contractor, and, if applicable, its vendors or subcontractors, and other Navy personnel who will be key to the acceptance of the manufacturing process, including the appropriate Technical Warrant Holders (TWHs), if applicable. While identifying all requirements / approvals necessary for implementation during the project proposal phase may be difficult, COEs should make every effort to identify all steps required as early as possible. The PO / COR for the project should be the last signatory obtained for the TTP so that he can easily see the edits made by all of the reviewers.

When new factors that impact implementation, such as requirements, funding, approvals, schedule, or project scope, become known, COEs should revise the TTP and resubmit it for signature as soon as possible.

The TTP is also required to be reviewed annually and updated if changes to the project impact implementation, such as requirements, funding, approvals, schedule, or project scope. COEs should discuss all changes that impact implementation with the PO / COR to determine whether a revision to the TTP is required. New projects initiated within six months of the Jul review are not subject to the annual review.

The steps below outline the process to submit the initial draft and signed TTPs, as well as for the annual review:

1. COE submits an unsigned, draft version of the TTP with the project plan. (If the TTP is not submitted, the project may not be initiated.)

2. PO / COR reviews the TTP as part of project plan review process and sends comments back to the COE to resolve.

3. Once comments are resolved, the COE uploads a Microsoft Word version of the draft (unsigned) TTP to the appropriate folder under the Projects tab of the Navy ManTech Projects Database (NMPD). The COE also e-mails the PO / COR and the Navy ManTech Support Team (navymantech@bcsallegient.com) when the TTP has been uploaded to the NMPD and includes the file location.

a. If the database is unavailable, COEs will use one of the acceptable submission methods shown below to submit the TTP, as well as notify the PO / COR and Navy ManTech Support Team of the method used to submit the TTP.

Acceptable Submission Methods:

DoD Safe – https://safe.apps.mil/ COE File-Sharing Site E-mail with encryption

b. Navy ManTech Support Team will upload the TTP to the database.

4. Within 90 days of project start, COE uploads the signed TTP in PDF format to appropriate folder under the Projects tab of the NMPD. (See steps 3a and 3b for instructions if the NMPD is unavailable.)

5. COEs review the TTPs for all applicable active projects and discuss the TTPs with the PO / COR.

a. If a TTP requires changes:

COEs should revise the Word version of the TTP using track changes and submit it to all parties for signature, ensuring that the PO / COR is the last signature secured.

Once the TTP is signed by all parties, COEs should complete the Annual Review Form (Changes to the TTP section; see Attachment 1), by adding the date, file name, and reason(s) for the change(s) to the table and by checking and signing the “Changes to the TTP” box. Note all changes should also be summarized in section 3g “Changes to the TTP since it was last approved.”

COEs should then upload the TTP to the appropriate folder under the Projects tab of the NMPD, notify the PO / COR that the TTP has been uploaded, and request that he sign the Annual Review Form (Changes to the TTP section).

Once the form is signed, COEs should save the revised signed TTP as a PDF file and upload it to the appropriate folder under the Projects tab of the NMPD and notify the PO / COR and Navy ManTech Support Team that the TTP has been uploaded. See the instructions in 3a and 3b if the NMPD is unavailable.

b. If a TTP requires minor changes:

COEs should revise the Word version of the TTP using track changes. New signatures are not required.

COEs should complete the Annual Review Form (Minor Changes to the TTP section; see

Attachment 1), by adding the date, file name, and reason(s) for the change(s) to the table and by checking and signing the “Minor Changes to the TTP” box. Note all changes should also be summarized in section 3g “Changes to the TTP since it was last approved.”

COEs should then send the Word version of TTP to the PO / COR and request that he sign the Annual Review Form (Minor Changes to the TTP section).

Once signed, COEs should then save the Word document as a PDF file using the same name, revision letter, and date as the current signed TTP and add “MINOR CHANGES” and the current date to the file name.

COEs should upload the TTP to the appropriate folder under the Projects tab of the NMPD and notify the PO / COR and Navy ManTech Support Team that the TTP has been uploaded. See the instructions in 3a and 3b if the NMPD is unavailable.

c. If a TTP does not require changes:

COEs should complete the Annual Review Form (see Attachment 1) by adding the date and the file name to the table, and by checking and signing the “No Change to the TTP” box.

COEs should then send the Word version of TTP to the PO / COR and request that he sign the Annual Review Form (No Changes to the TTP section).

Once signed, COEs should then save the Word document as a PDF file using the same name, revision letter, and date as the currently signed TTP and add “NO CHANGE” and the current date to the file name.

COEs should upload the TTP to the appropriate folder under the Projects tab of the NMPD and notify the PO / COR and Navy ManTech Support Team that the TTP has been uploaded. See the instructions in 3a and 3b if the NMPD is unavailable.

D. FORMAT (See Attachment 1: Navy ManTech Technology Transition Plan Template) Table of Project Information and Points of Contacts (POCs): Fill in as necessary. For all POCs, indicate name and organization. If the project has a lead COE, list the lead COE first with “(Lead)” in parentheses after the COE acronym. Supporting COEs should be listed following the lead COE.

1. Overview: The first paragraph in the template should remain intact in every plan. Entries should be inserted in the second paragraph as indicated. This includes the complete official title of the ManTech project and the specific platform / weapon system and/or industrial / naval organic facility targeted for implementation. The second paragraph should be tailored, as appropriate, for the specific project.

2. Overview of the Transition and Implementation Strategy: Summarize entire TTP (not the project) in about 100 words. Include key items from Sections 3 through 7.

3. Navy Need / Deliverable(s) / Benefits / Schedule / Funding: Complete Sections a through g.

Identify why this project is needed, what will be delivered, and the benefits that will accrue from its successful completion. If this project will reduce costs, provide an estimate of the cost reduction projected per ship or aircraft. Indicate when implementation is required and/or scheduled, and be specific about who will be funding the implementation of the project results.

4. Transition Event Defined: In order to minimize any misunderstandings as to what will be accomplished by the ManTech project and the timeframe, the specific point at which ManTech will declare successful transition to the platform / weapon system and/or industrial / naval organic facility should be clearly defined. This “Transition Event” should be defined through communication with all of the stakeholders.

5. Transition Strategy: This section should contain an overview of the ManTech project. The Exit Criteria table should be completed, including the thresholds and goals for each exit criteria. This should not be a repeat of the project plan but rather a clear demonstration that the ManTech technical effort is focused on the needs of the platform / weapon system and/or industrial / naval organic facility and that the project will be completed in time to meet those requirements. To the extent possible, risks should be identified and the plans to mitigate those risks should be presented. This section identifies how the ManTech project will achieve the transition event defined in Section 4 above.

6. Implementation Strategy and Requirements: In order for the results of a ManTech effort to be adopted on a specific platform and/or weapon system or at an industrial / naval organic facility, qualification testing must be conducted, certification requirements met, and approval received from the entities and authorities responsible for the acceptance of specific items and materials.

This section of the plan is intended to capture all of the requirements that will be completed using funding or resources provided by non-ManTech entities. For each, identify the responsible entity and, to the extent possible, the resource commitment, including the amount of money, manhours, equipment, etc. and source (responsible organization and name of POC). Any requirements that were completed as part of the ManTech project should be included in Transition Strategy, Section 5, above, and not in this section. As part of the development of this plan, the COE should confer with all the entities who are part of this process related to the ManTech project. This will typically include the acquisition Program Office / PEO, industry, the TWH for specific components and processes, and others. It is anticipated that the project TA will assist in facilitating these discussions. Note: The ultimate ManTech Program goal is to implement all technically successful ManTech projects. Conversely, the ManTech Program has a strong mandate to terminate projects as soon as it is known that they will not implement. Some projects will not implement due to a failure to meet the required exit criteria. This is an acceptable outcome since there should be technical risk in the program. Failure to implement technically successful ManTech projects is not an acceptable outcome.

7. Timeline: Do not include a project Gantt chart showing project tasking. The purpose of the timeline is to align the completion of ManTech project activities and the implementation requirements conducted and/or funded by other organizations with the insertion window of the intended platform / weapon system. If implementation will occur at an industrial / naval organic facility, indicate the schedule for implementation. The timeline should include the significant activities of the ManTech project, including a clear indication of the end point of the ManTech project, and the major implementation requirements, such as testing, certification, and approvals that will be conducted and/or funded by non-ManTech entities. It must be obvious that all key steps will be completed in sufficient time to meet implementation on the specific build of the targeted platform or weapon system and/or to meet the specific schedule needs of the industrial / naval organic facility. If this project is being conducted to support a platform / weapon system, a top-level schedule for the platform / weapon system should be included noting the hull or aircraft number, production start date, and scheduled completion date of the platform.

8. Tracking Implementation: Although it is not part of the ManTech project for the COE to track the implementation of the technology after project completion, it is important for ManTech to obtain this information. Based on discussions that the COE has conducted with the acquisition Program Office / PEO and/or the industrial / naval organic facility management representative, industry, the project TA, and others to define this TTP, it is anticipated that recommendations on how to track the project’s implementation can be obtained. To the extent that the COE can obtain commitments from these other entities to support such tracking, they should do so. This section should be specific to each project.

9. Signatures: The TTP should be signed by the Director or Technical Director of the ManTech COE, with the lead COE signing first followed by supporting COEs, when applicable; the industrial / naval organic facility management representative; Program Office / PEO representative of the platform / weapon system; and ManTech PO / COR. The signature of the ManTech PO / COR should be secured last. The intent is that senior leadership of the organizations responsible for achieving the “Transition Event” and for implementing the resulting technology indicate his/her agreement and understanding of what ManTech is responsible for completing and what will be conducted by others to achieve implementation. For all projects, the platform / weapon system Program Office / PEO representative should sign this document since the ManTech investment is specifically supporting the manufacturing technology needs of that Program Office / PEO. At the discretion of the ManTech PO / COR, additional signatories may be required depending on the particular ManTech project and its intended implementation. For example, a new process to manufacture a component for a ship may require the signature of the appropriate NAVSEA TWH to increase the likelihood that the process will actually be implemented.

If a specific item is not applicable to the ManTech project, the item should be noted “Not Applicable.” In addition, the TTP may be tailored, within reason, to accommodate the specific COE and/or project. Such tailoring requires the concurrence of the ManTech PO / COR.

E. REPORTING

COEs are responsible for reporting the status of the TTP and the implementation requirements when projects are briefed during platform program review meetings.

F. FILE NAME AND REVISION REQUIREMENTS

1. Revision Requirements:

All Navy ManTech TTPs will have both a Rev letter and Month Year “stamp” in the right footer in the following format: REV {letter} ({MMMYY}). Update each subsequent revision accordingly. The initial plan submitted with the Project Plan should be Rev A.

i.e., REV A (APR22)

2. File Name Convention:

File names for Technology Transition Plans should be in the following format: {COE acronym} TTP {official project number} {complete official title of project} Rev {letter} {MMMYY}.

Unsigned plans should be submitted as Microsoft Word documents:

o i.e., CMTC TTP M2740 F-35 Blind Fasteners Rev A DEC17.docx Signed plans should be submitted as PDF files:

o i.e., CMTC TTP M2740 F-35 Blind Fasteners Rev B JUL18.pdf Signed plans with no change after the annual review should be submitted as PDF files:

o i.e., CMTC TTP M2740 F-35 Blind Fasteners Rev B JUL18 NO CHANGE 26JUL19.pdf

REV {letter} ({MMMYY})

Attachment 1: Navy ManTech Technology Transition Plan Template

Remove all blue font directions before submitting

Technology Transition Plan

Date of Plan:

Project Title (full official title):

Project Number:

Period of Performance:

Center(s) of Excellence:

COE Project Manager:

Program Officer / COR:

Platform / Weapon System:

Program Office / PEO Representative:

Industrial Facility Management Representative:

Technical Assistant (TA):

Technical Warrant Holder

(TWH):

Other Stakeholders:

1. Overview:

In developing needed manufacturing technology for key acquisition platforms, Navy ManTech ensures that technologies to be implemented are both producible and affordable. ManTech alone, however, cannot ensure implementation in a system. As part of each project, the lead Navy ManTech Center of Excellence (COE) coordinates with the relevant Navy and industry representatives to identify all the requirements that must be met to ensure ManTech transition and to achieve implementation on the platform / weapon system and/or at an industrial / naval organic facility.

Upon successful and timely completion of the [Insert complete official title of ManTech project] project and the successful acceptance of the technology by the acquisition Program Office / Program Executive Office (PEO) and/or the management representative of the industrial / naval organic facility and the relevant Navy technical codes, the results will be implemented on / at the [Insert specific platform / weapon system on which, or industrial / naval organic facility at which, implementation is planned]. The balance of this document specifies the Navy need for this technology, the specific event that will signify ManTech transition, the exit criteria that the ManTech project must meet for transition, the requirements for implementation, and the schedule. [Tailor this paragraph for the specific project.]

2. Overview of the Transition and Implementation Strategy:

Provide a brief summary that includes the key points of the transition and implementation strategy from Sections 3-7. Limit this section to about 100 words. Note: This is not a summary of the project.

3. Navy Need / Deliverable(s) / Benefits / Schedule / Funding:

This section should list the reason the Navy needs the technology, the project deliverable(s), the project benefits, the quarter and fiscal year that implementation is planned, the targeted platform or site for implementation, and the source(s) of implementation funding.

a. Navy need for ManTech project / objective: Briefly explain the Navy need for the ManTech project and state the project objective.

b. Description of deliverable(s): Concisely describe the product(s) and/or process(es) that will be delivered if the ManTech project is successfully transitioned.

c. ManTech will deliver: Check all that apply.

☐ Improved production processes / Description ☐ Improved production planning and scheduling tools / Description ☐ Improved component design for manufacturability / Description ☐ Improved component design for life-cycle and maintenance performance / Description ☐ Knowledge Product (Technical reports, technical data packages, facility optimization, etc.) / Description ☐ Capability enhancement and/or acceleration / Description ☐ Other / Description

d. Benefits: Indicate the benefits to the platform / weapon system or industrial / naval organic facility, the Navy, and/or the warfighter that the Program Office / PEO and/or industrial / naval organic facility management representative are expecting from the successful completion of this effort. If the project will reduce costs, provide an estimate of the cost reduction projected on a per ship or aircraft basis.

e. Schedule of implementation: Indicate when implementation is required by the Program Office / PEO, e.g., provide the ship hull or aircraft number on which implementation is planned and the estimated quarter and fiscal year. For those ManTech projects with technology insertion schedule risk (i.e., missing a specific platform insertion date), indicate when implementation is required by the Program Office / PEO and provide the ship hull, aircraft number, or platform designator (i.e., UUVs) on which implementation is planned and the estimated quarter and fiscal year. For those projects that are manufacturing process-related and the OEM can implement at any time and realize ROI/cost savings, (i.e., cognizance of industry or AME applications, etc.), indicate where the implementation will occur (industrial facility) and the first ship hull, aircraft number, or platform designator (i.e., UUVs) on which implementation is planned and the estimated quarter and fiscal year.

f. Implementation funding: Specifically state the origin of the funding that is needed to implement the results of the ManTech project, e.g., name of Program Office, Program Objective Memorandum (POM), CAPEX, name of industrial / naval organic facility, etc.

g. Changes to the TTP since it was last approved: Any change to the ManTech TTP, including minor changes, must be documented in this section. Changes include requirements, funding, approvals, schedule, or project scope. If the effort has been de-scoped due to technical issues, modified to accommodate acquisition program requests, or expanded to reach additional acquisition customers, include a discussion here. If this is the initial TTP or if no changes have been made to the TTP, insert N/A.

4. Transition Event Defined:

Briefly describe the specific event that designates that the transition for the ManTech project will be achieved. This section should specifically indicate the definitive point at which the effort funded by the ManTech project has been successfully completed. Since ManTech does not implement the technology, ManTech transition will normally be the point at which the platform or weapon system Program Office / PEO and/or industrial / naval organic facility or supporting industry have accepted the technology for qualification testing and subsequent implementation.

5. Transition Strategy:

Provide an overview of the strategy to achieve the transition event. Define exit criteria that demonstrate that the project is focused on the attributes needed by the Program Office / PEO of the platform / weapon system or the industrial / naval organic facility. Where appropriate, specify the goals and thresholds for the exit criteria attributes. Goals should include both product and process goals, if applicable. Product goals are attributes that enable the customer to use the results of the ManTech project. (Examples of product goals include weight, flatness, power consumption, product cost, process maturity / risk, mean time between failure, etc.)

Process goals are the ManTech technical goals that must be achieved to meet the product goals.

(Examples of process goals are yield, tolerance, process cost reduction, process variables [time, temperature, and pressure], number of defects, reduction of trace elements, simulation accuracy, etc.) Include a description of the technical and/or schedule risks and plans to mitigate. This section is a description of what ManTech will do to achieve the Transition Event defined in Section 4 above.

a. Exit criteria Exit criteria identified below will be used to determine technical success:

Criteria Starting Value Threshold Value Objective Value (Goal)

b. Changes to exit criteria since TTP was last signed: If the performance requirements for the deliverables have changed since the last TTP was signed, the changes need to be documented here. If no changes to the exit criteria, insert N/A.

Organization FY19 FY20 FY21 FY22 FY23 Total $K $K $K $K $K $K

$K $K $K $K $K $K

6. Implementation Strategy and Requirements:

This section should provide a clear indication of what must be done to implement the technology that ManTech has developed. Do not include requirements that were completed as part of the ManTech project, which should be included in Section 5, above.

a. Description of the implementation strategy: This section should provide sufficient detail to illustrate that the ManTech project has a clear implementation strategy and recognizes the requirements for implementation, that ManTech understands the activities that must be conducted after completion of the project to achieve implementation, and that sources of funding or resources provided by organizations other than ManTech to implement the technology have been identified and are committed to implementation.

b. The ManTech project will integrate into the program of record via: Check all that apply.

☐ Industry-approved process change ☐ Externally-approved process change ☐ Production facility upgrade ☐ Temp Alt / Ship Alt ☐ Engineering change proposal ☐ Governing document update (Product drawing change, specification change, etc.)

☐ Placement on a Qualified Product Database (QPD) ☐ Other ____________________________________________________

c. Implementation requirements: In the table below, indicate the specific requirements needed for implementation after completion of the ManTech project. Requirements may include qualification, testing, certification, approvals, and other activities that must be completed to achieve implementation on the platform / weapon system and/or at the industrial / naval organic facility. For each entry, indicate the responsible entity (Navy organization, industrial / naval organic facility, etc.) and a point of contact (POC / name of person) as well as the resource commitment ($, manhours, equipment, etc.).

Requirement Organization Responsible for Requirement /

POC

Resource Commitment

7. Timeline:

Provide a timeline that aligns the achievements of the ManTech project and the implementation requirements listed in Section 6c with the production schedule of the platform / weapon system or industrial / naval organic facility. Indicate the ManTech transition event and when implementation is planned. Clearly illustrate that all key activities will be completed in sufficient time to implement on the specific build of the targeted platform or weapon system and/or to meet the specific production schedule at the industrial / naval organic facility. Include all significant activities of the ManTech project and the implementation requirements that are required and/or funded by non-ManTech entities, and show the end point of the ManTech project as well as the conclusion of all implementation requirements.

8. Tracking Implementation:

Tracking the transition from ManTech through to implementation is important to demonstrate the overall success of ManTech. This section should provide a recommended approach for tracking the implementation of the results of this project after project completion. It is anticipated that the approach recommended will be different for every project. Innovative suggestions for each project are encouraged. In the case of implementation at an industrial / naval organic facility, this section should provide the recommended approach for tracking the actual benefits achieved at the facility. (Note: It is not the responsibility of the COE as part of this project to actually conduct the tracking after project completion.)

9. Signatures:

The TTP should be signed by the following signatories: (1) Director or Technical Director of the ManTech COE, with the lead COE signing first followed by supporting COEs, when applicable, (2) the industrial / naval organic facility management representative, (3) Program Office / PEO representative of the platform / weapon system, and (4) the ManTech PO / COR.

As noted in the guidance, the signature of the PO / COR should be secured last so that he can see the edits made by all of the reviewers, and additional signatories may be required by the ManTech PO / COR.

I concur with the terms of the TTP, specifically the deliverables(s), exit criteria, transition and implementation strategies, and implementation requirements described in this document.

Name Date Director / Technical Director Name of Navy ManTech Center of Excellence

Name of Industrial / Naval Organic Facility Management Representative Date Title Organization

Title Program Office / PEO

ManTech Program Officer / COR Office of Naval Research, ManTech Program, Code 332

Annual Review Form

Revisions:

Date File Name Summary of Change(s)

☐ Changes to the TTP I have reviewed the TTP for the name of ManTech project project and determined that there are changes to the TTP that impact implementation. I have discussed the TTP with Name of ManTech Program Officer / COR.

Name Date Director / Technical Director Name of Navy ManTech Center of Excellence

☐ Changes to the TTP I have reviewed the TTP for the name of ManTech project project and concur that there are changes to the TTP that impact implementation.

☐ Minor Changes to the TTP I have reviewed the TTP for the name of ManTech project project and determined that there are minor changes to the TTP; however, they do not impact implementation. The changes are tracked in the TTP and summarized in the table above. I have discussed the TTP with Name of ManTech Program Officer / COR.

Name Date Director / Technical Director Name of Navy ManTech Center of Excellence

☐ Minor Changes to the TTP I have reviewed the TTP for the name of ManTech project project as well as the changes summarized in the table above. I concur that there are only minor changes to the TTP that do not impact implementation.

☐ No Change to the TTP I have reviewed the TTP for the name of ManTech project project and determined that there are no changes to the TTP that impact implementation. I have discussed the TTP with Name of ManTech Program Officer / COR.

Name Date Director / Technical Director Name of Navy ManTech Center of Excellence

☐ No Change to the TTP I have reviewed the TTP for the name of ManTech project project and concur that there are no changes to the TTP that impact implementation.