Attachment XX. Final Report Guidance REV L OCT24.docx

Navy ManTech Program

REV L OCT24

Final Report Guidance Attachments:

None

A. PURPOSE

The project Final Report describes the technical results of a Navy ManTech project and is submitted after project completion.

B. REQUIRED TIMELINE

Final Reports for Navy ManTech projects are due by the date specified in the Center of Excellence (COE) contract or 30 days after the project end date. The status and anticipated submittal date of Final Reports for any recently completed project or any project to be completed within the next quarter should be included in the Quarterly Report (refer to the Quarterly Report Guidance). A final Quad Chart for the project, with Supplemental Supporting Data, should also be submitted when the Final Report is submitted (see Project Quad Chart Guidance).

C. PROCESS / APPROVAL CYCLE

COEs are expected to upload the Final Report to the respective project folder of the Projects tab of the Navy ManTech Projects Database (NMPD) by the date specified in their contracts or within 30 days of completion of the project. COE contracts also specify the required recipients of project Final Reports. Because all recipients may not have access to the NMPD Projects page, the Final Report may need to be submitted using another secure method, such as encrypted email, DoD SAFE (https://safe.apps.mil/), a COE SharePoint site, or the Defense Technical Information Center (DTIC).

If the NMPD is unavailable, COEs will use one of the acceptable submission methods shown below to submit the Final Report, as well as notify the PO / COR and Navy ManTech Support Team of the method used to submit the report:

· DoD Safe – https://safe.apps.mil/

· COE File-Sharing Site

· E-mail with encryption The Navy ManTech Support Team will upload a copy of the Final Report to the database.

Note: The Navy Authorizing Official of the U.S. Fleet Cyber Command has approved the NMPD for Controlled Unclassified Information (CUI), including export controlled.

D. FORMAT

Final Reports are mandated as deliverables under COE contracts, and the specified formats may vary. However, Final Reports are documents prepared in Word, and the topics shown below are considered to be the minimum required. If there is a topic listed below that is not included in the Final Report format specified in a COE contract, the COE’s Final Report format must be amended to include the required topic. However, this guidance does not mandate that each COE change its format to exactly match the structure outlined below. This is a list of the minimum requirements. Each COE may continue to use its established format as long as the PO / COR has approved the format, and all information shown below is included. For those COEs that have no established Final Report format, the format below should be used. COEs are encouraged to include graphics and video clips, as appropriate, in the Final Report. A PowerPoint presentation is not acceptable as a Final Report.

Minimum Requirements

1. Cover Page (Complete Official Title of Project, Date, Project Number, Performing Activity, Project Team Members, and Contact Information)

2. Executive Summary / Abstract

3. Table of Contents

4. Background / Problem Statement

5. Objective(s)

6. Technical Approach (by task)

7. Technical Activities Performed

8. Results and Discussions

9. Benefits Analysis

a. Categorize and prioritize the project’s accomplishments in one or more of the following areas and include quantifiable data to support benefit analysis:

· Cost avoidance / savings

· Capability acceleration

· Warfighter readiness

· Improved performance

· New product / process development to meet critical performance requirements

· Environmental compliance With current Navy ManTech Program emphasis on ship and aircraft affordability, it is expected that the emphasis will be on cost-reduction benefits.

10. Implementation (Progress / Status)

d. Identification of organizations / personnel responsible for major milestones leading to full implementation.

For every project that has a Technology Transition Plan (TTP), this section of the Final Report should address the status of the planned implementation and highlight any changes from the TTP. Updated recommendations to track the actual implementation(s) should be included.

11. Conclusions and Recommendations

12. References, as applicable

E. REVISION REQUIREMENTS AND FILE NAME

2. File name convention:

File names for Final Reports should use the following format: {COE acronym} FINAL {official project number} {complete official title of project} {MMMYY}.

· i.e., CMTC FINAL A2587 Automated Material Mixing for F-35 MAY15.docx